If you are running a website you will probably encounter an occasional error. Most of them come from either either at the server level or at the application level (in WordPress). However, sometimes you will encounter an error such as "DNS_PROBE_FINISHED_NXDOMAIN " which comes from your computer settings.
In this article , we're going to talk about how to identify DNS_PROBE_FINISHED_NXDOMAIN error and go over all the ways to deal with it.
Let's get to work!
What Is DNS_PROBE_FINISHED_NXDOMAIN error?
To explain what DNS_PROBE_FINISHED_NXDOMAIN is, we need to review the concept of a domain name system (DNS). A DNS is a database of IP addresses mapped to domain names.
Each server has an IP address, which isused to identify websites saved on this computer. However, instead of entering an IP address into your browser to access web content, you can simply use its corresponding domain name.
A DNS can identify the IP address to which a domain name points. When you enter a URL, it searches its database for the site you are trying to access.
However, in some cases DNS servers may not be able to retrieve the desired information. If you get the DNS_PROBE_FINISHED_NXDOMAIN error, this is what happened:
- You tried to access a website using its domain name (which you know is 'it should work).
- Your computer has submitted your query to DNS which it uses to map domains to IP addresses they can connect to.
- The DNS server has told your computer "This domain does not exist! ", hence the " NXDOMAIN "part of the error.
When this happens you will see an error message that looks like this (if you are using Chrome) :
The wording may vary a bit depending on the browser you are using, but the basics are still the same. For example, here is the same error in Firefox:
If you meet the DNS_PROBE_FINISHED_NXDOMAIN error, take a second to verify if you are typing in the correct domain. Assuming the domain exists and you entered it correctly, the problem is usually with your computer configuration.
How to fix DNS_PROBE_FINISHED_NXDOMAIN error (3 possible solutions)
There are many ways you can fix the error in question depending on the root cause. Unfortunately, this can be difficult to identify.
However, each of the fixes below should only take you a few minutes to implement. If you follow our instructions and make one fix after the other, the DNS_PROBE_FINISHED_NXDOMAIN should be out of your hands soon. path.
1. Renew your IP address and clear / restart your cache
One of the first things you should try if you are having local connectivity issues (besides restarting your router) is to renew your IP address. The process varies slightly depending on your operating system (OS), so we have included instructions for both Windows and Mac users.
If you are using Windows, you can renew your IP address by opening the command prompt with administrator privileges. To do this, go to the Windows Start menu and type "cmd", then select the corresponding option:
Once it is open, follow the following three command steps one by one, pressing the Enter key after each to run it:
- ipconfig / release
- ipconfig / renew
- ipconfig / flushdns
These three commands will free your IP address, renew it, then flush your local DNS cache.
Another option to clear the local cache is to use the following two commands:
- net stop dnscache
- net start dnscache
These prompts stop and restart the Windows service that manages your local DNS c poorly. After running both sets of commands, try to access the problematic website again to see if the error persists.
On macOS, you can renew your IP address without using commands. To do this, follow these instructions:
- Go to System Preferences.
- Go to Network, select your active connection, and click on the Advanced button.
- Go to TCP / IP and select the Renew DHCP option.
However, you will need to use Terminal to flush the DNS cache. Open it (Go> Utilities) then enter the following prompt:
You are now ready to try to access the URL again incriminated. If that still doesn't work, go to the next fix.
2. Configure your computer to use another DNS server
By default, your computer will decide which DNS server to automatically connect to. In some cases, this DNS server may not have the best response times. Or, it may not be available, resulting in errors such as DNS_PROBE_FINISHED_NXDOMAIN.
One way to determine if this is the source of the problem is to configure your connection to use a different DNS server. Let's see how to do this in Windows and macOS.
Open the Windows Start menu and type “Network Status”. Select the first result that is displayed and on the next screen click on Change settings adapter options:
A new one window will appear with icons for all connections configured on your computer:
Identify your active Internet connection, then follow these steps:
- Right click on the active connection and select Properties.
- Look for Internet Protocol Version 4 (TCP / IPv4 ), select it and open its Properties setting.
- Select the Use the optionnext DNS server address.
You should then see this screen, only without any number in Preferred DNS Server and Alternate DNS Server Fields:
In the example above, we are using Google's public DNS servers. To do the same, enter "22.214.171.124" as your preferred DNS server and "126.96.36.199" for your alternate DNS server.
There are many more options when it comes to public DNS servers, so feel free to try one of them. However, Google is generally a safe choice.
If you are already using a custom DNS server and encounter the DNS_PROBE_FINISHED_NXDOMAIN, try using the reverse approach. That is, go back to the default settings to see if that fixes the problem.
Changing the DNS server for your active connection on macOS works much the same as it does on Windows. Here's what you need to do:
- Go to System Preferences.
- Go to Network and select your
- Click on the buttonAdvanced in the settings of your active connection.
- Select the DNS tab and add the addresses you want to use.
In the fourth step, you should see a screen like this:
Just like with Windows, you can use any DNS server you want. Once you are done, check if the DNS_PROBE_FINISHED_NXDOMAIN error persists.
3. Check your computer's hosts file
Your computer's hosts file allows you to manually map IP addresses to domains. This can be useful for local web development, for example, as you can map local sites to custom domains without registering them.
In some cases, programs may modify your hosts file without your knowledge. This can lead to errors such as DNS_PROBE_FINISHED_NXDOMAIN. Here's how to fix it.
First, locate and open your hosts file. You can find it by going to the local directory C: WindowsSystem32driversetc:
Open the file using your favorite text editor. Remember that you may need todefine administrative privileges to modify it.
In your hosts file, you will probably have at least a few custom mappings configured. Make sure that none of the entries match the domain name you tried to access.
If the target domain is listed, remove the entry and save the changes to your hosts file. Then try to access the site again.
The easiest way to edit your hosts file on macOS is to use Terminal. First, open the application and enter the following command:
Nano text editor with administrative privileges. If you are more comfortable with another editor, youcan override this part of the command.
Examine the file to see if the domain that returns the DNS_PROBE_FINISHED_NXDOMAIN error is present. If so, remove this mapping and save your changes to the file.
There are many ways to fix DNS_PROBE_FINISHED_NXDOMAIN error. Fortunately, most of the fixes are remarkably easy to implement. If you know what to do, you should be able to regain access to the website you are trying to reach within minutes.
If you encounter DNS_PROBE_FINISHED_NXDOMAIN error, here is what you can to fix it:
- Renew your IP address and clear / restart your cache.
- Configure your computer to use another DNS service.
- Check your computer's hosts file.
Do you have questions on how to fix DNS_PROBE_ errorFINISHED_NXDOMAIN in WordPress? Let's talk about it in the comments section below!
Image from Visual Generation / shutterstock.com