The “dns_probe_finished_nxdomain” error code is not common but it can happen while you are trying to surf the internet. This is an error that is associated with the DNS (Domain name System/ Service). It basically restricts your browser from loading a particular web page or whichever web page. No matter how many times you try to reload the page, you get the same error every time. Bearing in mind that your internet connection is okay.
Communication on the internet is governed by IP address. For a website to be visible on the internet, its domain name needs to have a corresponding IP address. What you key in on the address bar is the domain name. On the other hand, for your browser to locate a particular website, the domain name has to be resolved to the corresponding IP address. This is done by domain name service. If you get “dns_probe_finished_nxdomain” error it means the service has encounterearticular OS platform. It can happen while you are surfing with your android device. For that reason, we have listed a few known fixes for each platform. Jump to whatever platform you are facing this issue on. Don’t forget to check out the general fixes at the end in case the solutions for your platform don’t resolve the error.
Table of Contents - Article Hierarchy
- Fix “dns_probe_finished_nxdomain” error in Windows
- Solution 1. Clear local DNS cache
- Solution 2. Reset Winsock
- Solution 3. Switch to a faster public DNS
- Solution 4. Reset Windows 10 Hosts file
- Fix “dns_probe_finished_nxdomain” error in Mac
- Fix “dns_probe_finished_nxdomain” error in Android
- Fix “dns_probe_finished_nxdomain” error in Linux
- General fixes
Fix “dns_probe_finished_nxdomain” error in Windows
Solution 1. Clear local DNS cache
Windows usually perform DNS caching in your computer in order to resolve DNS requests quickly. The operating system temporarily stores relevant domain information of all the recently visited sites. At times it may interfd a problem of some kind. It may exist locally on your computer, from your ISP or someplace else.
This error is not specific to chrome browser alone. Neither is it specific to a pere with how your computer interprets domain lookups. For example, if the real-time information is not the same as what is stored in DNS cache. Maybe due to a recent change with the domain name.
Here is how to clear local DNS cache in windows:
- Type in “cmd” in the search bar. Right-click on the first result then select “run as administrator”.
- Command prompt window should open with administrative privileges. Type in “ipconfig /flushdns” then hit Enter key. Note that there is a single space between “ipconfig” and “/flushdns”.
- Refresh the site and check if the error is resolved.
Solution 2. Reset Winsock
Winsock (Windows Socket) is an inbuilt API that defines the interface for which windows applications can access the internet. It basically bridges the gap between native applications and the World Wide Web. If the settings for Winsock were tampered with, it can result in “dns_probe_finished_nxdomain” while surfing the internet. We are going to reset to the default settings.
Here is how to reset Windows sockets:
- Open the command prompt with administrative privilege as we did above.
- While in the command prompt window, type in “netsh winsock reset” then hit Enter key.
- Wait for the process to complete. You will then have to restart your PC for the reset to take effect.
- Go ahead and restart then check whether the problem is fixed.
Solution 3. Switch to a faster public DNS
In most cases, resolving domain names is carried out by your ISP. The problem may lie from the DNS service provided by your internet service provider. You can change to a different DNS server which is much faster, secure and efficient. The popular ones are OpenDNS and GoogleDNS. We will switch to the latter.
Here is how to switch to a different DNS server:
- Right-click on the WiFi icon at the system tray. Select “Open Network & Internet settings”.
- Scroll down and select “Network and sharing center”.
- Next, click on the network SSID you are currently connected to.
- A dialog box should appear. Go ahead and click on the “properties” button.
- The properties dialog for the selected WiFi network will appear. Look for “internet protocol version 4” and click on it to make sure it is selected with the blue bar.
- Next, click on the “properties” button.
- On the next dialog box, make sure you are on the “general” tab. Select “Use the following DNS server addresses” by clicking on the radio button. This should reveal two input fields. Key in 188.8.131.52 for “Preferred DNS server” and 184.108.40.206 for “Alternate DNS server”. Input numeric without the periods. Click the “ok” button when done.
- Next, clear DNS cache as we did in solution 1 above.
- Refresh the webpage.
Solution 4. Reset Windows 10 Hosts file
This file contains lines of text that map readable hostnames to their numeric IP addresses. If the file’s default settings were somehow tampered with, it can cause connectivity issues. Note the following instructions are for windows 10.
Here is how to reset hosts file as directed by Microsoft:
- Open your text editor preferably Notepad and paste in the text below.
# Copyright (c) 1993-2006 Microsoft Corp.
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
# 220.127.116.11 rhino.acme.com # source server
# 18.104.22.168 x.acme.com # x client host
# localhost name resolution is handle within DNS itself.
# 127.0.0.1 localhost
# ::1 localhost
- Save the file with the name “hosts”. Save it to a location that is easy to find such as the desktop. Close notepad when done saving the file.
- Go to the search bar and type in %WinDir%\System32\Drivers\Etc or simply copy & paste then click on the result.
- Next, right-click on the “hosts” file in that directory and rename it to “hosts.old”.
- Move the hosts file that you previously created to %WinDir%\System32\Drivers\Etc directory. Click on the “Continue” button if you are asked to provide administrative permission. The files in the directory should look like this:
- Refresh the page and see if the problem is resolved.
Fix “dns_probe_finished_nxdomain” error in Mac
Solution 1. Clear local DNS cache
Flushing Local DNS cache in Mac is as easy as opening the terminal and typing in a few commands. Here is how you do it:
- Just open the terminal and type in the first command as follows then hit enter:
- For the second command, type in as follows and hit enter:
sudo killall –HUP mDNSResponder
- Refresh your browser and see if the problem is resolved.
Solution 2. Switch to a faster public DNS
If the problem is likely to be the DNS service provided by your ISP, here is how you can change to GoogleDNS while on Mac:
- Go to “system preferences”.
- While on the system preference window, click on “Network”.
- You should see the WiFi network you are connected to. Go ahead and click the “advanced” button.
- Next, make sure you are on the “DNS” tab.
- On the DNS server column, click on the plus sign at the bottom. You should now be able to input text in the box above. Enter 22.214.171.124 then followed by 126.96.36.199. Press the “ok” button to save the changes.
- Refresh your browser and see if the issue is resolved.
Fix “dns_probe_finished_nxdomain” error in Android
Switch to a faster public DNS
You should note that changing the DNS server on your android device can only be done on the WiFi network you are connected to. It is not possible for a cellular network. Furthermore, the changes you make apply on a per-network basis. When you connect to a different network, the previous changes will not be applied to the new network.
Here is how to change DNS server address on android:
- While in your android device, go to setting and select “WiFi”. Conversely, swipe down the toolbar and long-press the WiFi icon.
- Next, long press on the WiFi network you are currently connected to reveal extra options. Go ahead and select “modify network”.
- Expand the “advanced options”.
- Right under “IP settings” change from DHCP to Static.
- Scroll further down to where there is DNS 1 and DNS 2. If you want to use GoogleDNS, type in 188.8.131.52 & 184.108.40.206 while if you want to use OpenDNS, type in 67.222.222 & 220.127.116.11. Try both of them one at a time in case one does not solve the problem. Don’t forget to save when done.
Fix “dns_probe_finished_nxdomain” error in Linux
Solution 1. Clear local DNS cache
Many Linux distros nowadays do not come with a caching daemon installed. If the following commands don’t work on your system then its means no caching application is installed. If it is installed, you are either running on nscd, BIND or dnsmasq.
- If your system is running on nscd daemon, open the terminal and type in the following command to clear DNS cache:
service nscd reload
- If your system is running on BIND daemon, type in the following command and hit enter:
- If your system is running on dnsmasq, open the terminal and type in the following command and hit enter:
service dnsmasq restart
- After flushing, refresh your browser to check if it worked.
Solution 2. Fix resolv.conf file
This is a text file that contains the DNS server addresses. Without it, your machine cannot resolve host requests. This file should contain at least one nameserver line. In some instance, this file may be corrupt. Also, you will notice changes made to the file get overwritten. To fix this. Go to the directory etc/resolv.conf and delete that file. Using a text editor, create another file with the name “resolv.conf” and save on the same location. You will then need to add nameservers to that file.
Add the nameservers even if the file was not previously corrupt. The file can be okay but at the same time doesn’t have the nameservers. Here is how to add DNS server in resolv.conf file:
- Open the terminal and type in “sudo nano /etc/resolv.conf”. This will open resolv.conf file using the nano editor.
- Use direction arrows to move the cursor. Add the following lines to use GoogleDNS:
- Save the changes and exit.
Refresh your browser and see if the problem is resolved.
Solution 3. Fix dhclient.conf file (Ubuntu)
This solution fixes “dns_probe_finished_nxdomain” while on Ubuntu.
- Start off by opening the terminal and type in:
sudo nano /etc/dhcp/dhclient.conf
- The nano editor should open the dhclient.conf file. Next, add the following line to the file and save the changes:
supersede domain-name-servers 18.104.22.168;
- Next, restart the network manager using the following command:
sudo service network-manager restart
- Refresh the web page.
These solutions are for minor issues that you might have overlooked but at the same time have the potential to cause “dns_probe_finished_nxdomain” error.
Empty browser cache and history
- Navigate to chrome options on the top right of the screen and select “settings”.
- Scroll down the settings options and expand “advanced”.
- Look for “Clear browsing data” right under “Privacy and security” then select.
- Select all the three checkboxes and tap on the “Clear data” button.
- Refresh the page once again to see if the issue is resolved.
Update your browser
- Navigate to chrome options as shown
- Select “help” then “About Google Chrome”. Chrome should then search for the latest version and download. Relaunch Google Chrome to complete the update.
- Refresh the page that was affected by the error.
Double-check the URL you entered
Keying in the wrong address will result in “dns_probe_finished_nxdomain” error code. Confirm if the address you entered is correct.
Disconnect or Disable your VPN
In some cases, using a VPN service to encrypt your traffic can cause this error. The problem may lie in the proxy server operating the service. Go ahead and disable virtual private network then refresh the page.
Flush DNS cache in the router
DNS caching not only happens locally in your computer but also in the router. Most modern routers come with a DNS cache. It may sound hard to flush DNS cache in your router but it’s not. To clear DNS cache from your router, just unplug it from the power source then power it on again. All cache will then be cleared. That explains why rebooting is always effective when troubleshooting routers.