So, you open your desktop and you type in a search phrase and the results have loaded. You then go ahead and click a search result and you see an error saying “DNS PROBE FINISHED NXDOMAIN” in Google Chrome.
The website doesn’t load, and you can’t view the content you were looking for. Google errors are very common, and they can be extremely annoying. You must be sick and tired of these Google Chrome errors as they always stop you from loading up websites.
The Reason you’re Seeing “DNS PROBE FINISHED NXDOMAIN”
When you see this error, you’re told that ‘This webpage is not available’, then the error code is down below. This is going to show up regardless of which website you try and visit.
It’s similar to when you have no internet, you’re going to get an error message regardless of which webpage you try and visit.
The DNS Can’t Resolve the Webpage
Whenever you visit a webpage, the domain name you’re trying to visit needs to be matched with the servers IP address. Each live website is hosted on a server and each server has an IP address.
When you visit a webpage, the DNS has to resolve the domain name to the servers IP address. When the DNS fails to resolve the domain name to its servers IP address, you’re going to see the error code in Google Chrome.
Flush DNS Using Command Lines
The first and most reliable way to fix this is to use a command lines to flush the DNS.
Your aim is to flush the DNS with these command lines.
A command prompt allows you to communicate with your Windows operating system using certain command lines.
To flush the DNS using a command line:
- Click on the Windows button at the bottom left screen
- Search for command prompt
- Right click and click ‘Run as administrator’
- A command prompt window will pop up
- Copy and paste the commands below
ipconfig /releaseipconfig /allipconfig /flushdnsipconfig /renew netsh int ip set dns netsh winsock reset
You’ll need to run the commands one by one, don’t run them together.
After you’ve run all of the commands, you’ll need to restart your windows desktop.
Once you’ve done this, you can try and visit the webpage and you won’t see the DNS_PROBE_FINISHED_NXDOMAIN message anymore.
This is the most reliable step by step method to fix this problem.
If this didn’t work, use the next most reliable method.
Restart DNS Client
The next most reliable method you’ll want to try is the restart the DNS Client.
This is a very easy step and it should solve the problem.
The DNS Client caches DNS names and registers the full computer name for your computer.
If the service is stopped, DNS name will continue to resolve, meaning you’ll continue to see the Google chrome error code.
Therefore, you’ll need to restart the DNS Client.
To restart the DNS Client:
- Hold the Windows key + R to run command
- Enter services.msc and click ok
- You’ll see a list of local services and look for ‘DNS Client’
- Right click and select ‘restart’ (If this is greyed out, try the next step)
The DNS Client will now restart, and this may take a few minutes.
Once it’s done, you should be able to browse web pages freely without anything blocking you.
If you can visit other web pages and only one specific domain is showing the error, the problem is on the webmaster’s side and you’ll just have to wait for them to fix the problem.
Use Google Public DNS
If the step above didn’t work, the next step that you’ll need to take is to use Googles public DNS. This process involves changing your DNS and using Googles instead.
If you’re using a Windows computer, this is going to be very simple and you should have no issues.
To use Googles DNS:
- Click on the Windows icon
- Go to your Control panel
- Click on Network and internet then go to Network and Sharing Centre
- Select Change Adapter settings
- Click on the network that allows you to connect to the internet
- Right click and click on ‘Properties’
- Click on ‘internet protocol 4 (TCP/IPv4)’
- Enter Googles DNS 8.8.8and 22.214.171.124
After you’ve done this, you should be able to visit web pages without any issues.
Reset Chrome to Default
The next step you need to take if the step above didn’t work is to reset Chrome to its default settings.
Sometimes, this error can be caused by a change in Chromes settings which means that you’ll need to change Chromes settings back to how it was.
To reset Chrome to its default:
- Search Chrome://flags/ in the address bar
- Click Enter
- Select Reset all to default
After you’ve done this, you can try and visit a webpage in the hope that the Chrome DNS_PROBE_FINISHED_NXDOMAIN error doesn’t come up again.
Turn off any Firewalls
If you have a firewall turned on, you’ll need to turn it off.
Anti-virus software can also cause the DNS not to resolve.
Their aim is to prevent your device from getting viruses and to find potential viruses.
If the firewall installed in your Windows pc thinks that the webpage you’re trying to visit is potentially dangerous, it could cause the error to pop up.
To turn off firewalls on your Windows PC:
- Open the Control Panel
- Click on Windows Firewall
- To turn it off, in the left navigation pane, click on Turn Windows Firewall off
- In the Customize Settings window, select Turn off Windows Firewall and click OK
After you’ve turned off the firewall or VPN, you can try visiting the webpages or webpage again and you should notice that the problem resides.
Go Back to the Old Windows OS
One last main reason why you’ll see the DNS_PROBE_FINISHED_NXDOMAIN error is because your default settings have changed after updating to a new operating system.
If you know that you’ve recently updated your Windows PC, you’ll need to go back to the old operating system in order to stop this Google Chrome error.
To go back to the old OS:
- To get started, click Start and then Settings
- Click on Update & security
- In the sidebar, choose Recovery
- Click the Get Started link under Go back to the previous version of Windows 10
- Select why you’d like to go back to a previous build and click Next
- Click Next once more after reading the prompt
Or, you can reset your PC to the default settings.
After you’ve tried these steps, you should visit a web page and you shouldn’t see the error message again.