How do you fix DNS_PROBE_FINISHED_NXDOMAIN?

If a requested website is un­avail­able or un­reach­able, the browser often displays the ad­di­tion­al message DNS_PROBE_FINISHED_NXDOMAIN. What this error means and how you can fix it are explained in the following article.

What is behind the DNS_PROBE_FINISHED_NXDOMAIN message?

When Google Chrome un­suc­cess­ful­ly tries to access a website and sub­se­quent­ly displays the error message DNS_PROBE_FINISHED_NXDOMAIN, it indicates a problem with the name res­o­lu­tion by the reg­is­tered DNS server. Specif­i­cal­ly, the message means that the “DNS probe finished” with no suitable IP address found for the domain to be resolved. As a result, Chrome or the name­serv­er clas­si­fies it as a “non-existent (nx) domain.”

Possible causes of DNS_PROBE_FINISHED_NXDOMAIN

The error DNS_PROBE_FINISHED_NXDOMAIN occurs when the browser cannot resolve the IP address of a domain. This usually means there is an issue with the DNS settings or the con­nec­tion on either the website owner’s or the user’s side.

From the per­spec­tive of website owners, the following causes can lead to the error:

• Incorrect DNS settings, causing the domain to not correctly point to the server IP.
• Expired or im­prop­er­ly reg­is­tered domain, pre­vent­ing the DNS name servers from providing a valid response.
• Incorrect name server con­fig­u­ra­tion or in­suf­fi­cient prop­a­ga­tion after changes, making new DNS records not yet globally available.

Also, from the per­spec­tive of users, issues can arise that prevent DNS res­o­lu­tion. These differ from the problems on the website owner’s side:

• DNS server is not func­tion­ing properly or does not respond to requests.
• DNS client on the device is mal­func­tion­ing or disabled.
• Incorrect DNS settings in the operating system, browser, or router, such as manually entered servers that are not reachable.
• Incorrect Chrome settings, par­tic­u­lar­ly ex­per­i­men­tal features that can affect or block DNS res­o­lu­tion.
• Outdated entries in the DNS cache of the operating system or browser, providing old IP addresses and causing conflicts.
• VPN or antivirus software or firewall block DNS requests or prevent con­nec­tion es­tab­lish­ment.
• Ty­po­graph­i­cal errors in the URL or ac­ci­den­tal­ly incorrect domain names that the DNS server does not recognize.

How to diagnose the DNS_PROBE_FINISHED_NXDOMAIN error with tools and online checks

If you want to analyze the DNS_PROBE_FINISHED_NXDOMAIN error, various tools and online check services can be very helpful. They allow you to quickly narrow down DNS issues without having to ex­ten­sive­ly check settings on your own device. Services like IntoDNS, MXToolbox, or DNSCheck­er check, for example, if the DNS entries of a domain are correctly set, if name­servers respond, and if the prop­a­ga­tion is working worldwide. Simple online ping or tracer­oute services can also show if the domain is generally reachable or if there are packet losses or routing issues.

For local checks, you can use tools like nslookup, dig, or the Windows command prompt with ping and tracert to directly test name res­o­lu­tion. Many browser ex­ten­sions or desktop apps also offer real-time DNS checks and show which server is re­spond­ing to the request.

How to fix the DNS_PROBE_FINISHED_NXDOMAIN error

To sys­tem­at­i­cal­ly narrow down and fix the cause of the error, it is advisable to go through the following steps in sequence. The table provides a concise overview:

Step 1: Check URL

Often, the error is simply caused by typos in the URL. Carefully check whether the address is entered correctly, it contains no spaces or special char­ac­ters, and the correct top-level domain (.com, .net, etc.) is used. Even small typos can cause the DNS server to not find the domain.

Step 2: Test other websites

Open a few other websites to determine whether the problem affects only one domain or the internet con­nec­tion in general. If all sites work, the error likely lies with the website operators. If multiple sites are affected, the cause is usually the local device or network.

Step 3: Empty DNS cache

The so-called DNS cache can also be re­spon­si­ble for the error. This cache, which other operating systems such as Linux or macOS also create au­to­mat­i­cal­ly, contains entries for web addresses that have been suc­cess­ful­ly resolved over time. Browsers use this storage to deliver pages as quickly as possible, but this can lead to issues such as the DNS_PROBE_FINISHED_NXDOMAIN error when the retrieved entries are no longer up to date. In this case, the solution is to perform a DNS flush, which clears the cache.

On Windows, for example, this works as follows:

1. Open the Command Prompt.
2. Enter the command ipconfig /flushdns and confirm with the Enter key.
3. A message will inform you that the clearing process was suc­cess­ful.

Step 4: Restart DNS client

For Windows users dealing with the DNS_PROBE_FINISHED_NXDOMAIN error, solving the con­nec­tion issue may involve restart­ing the system’s DNS client. Acting as a link between the browser and the DNS server, this service plays a critical role in name res­o­lu­tion—even though, the­o­ret­i­cal­ly, it should work even if the DNS client crashes or is turned off. However, there’s always the chance that a client issue could neg­a­tive­ly impact the func­tion­al­i­ty of browsers like Chrome. To check the status of the DNS service and restart it if needed, follow these steps:

1. Open the Start menu and access the “Run” dialog from there.
2. Type services.msc and confirm the entry by clicking “OK”.
3. Look for the entry “DNS Client” and check the line labeled “Status”.
4. If the service is not running, right-click the DNS Client entry and select “Restart”.

Step 5: Check/Change DNS server

If the exchange between your device and the chosen or provider-assigned DNS server is not working, there may be two reasons: First, the entered IP addresses may be incorrect or no longer valid. Second, the server may be tem­porar­i­ly un­reach­able. In both cases, Chrome may display the error message DNS_PROBE_FINISHED_NXDOMAIN to inform you of the issue. Another solution option is to check the DNS settings or change the DNS server. As a Windows user, you can do this as follows:

1. Right-click on the Windows logo and select “Network con­nec­tions.”
2. Click on “Change adapter options” and then right-click on the network con­nec­tion for which you want to change the DNS server.
3. Click on “Prop­er­ties” and then on the entry “Internet Protocol Version 4 (TCP/IPv4)”.
4. Check the entered addresses under “Preferred DNS server” and “Alternate DNS server”.
5. Enter the correct IP addresses of the desired servers or the addresses of new servers like the Google DNS server (8.8.8.8 and 8.8.4.4).

Step 6: Check network settings

Check if your device is properly connected to the internet and if there is a stable network con­nec­tion. Ensure that no incorrect proxy settings or ex­per­i­men­tal browser features are active that could affect DNS res­o­lu­tion. Also, verify your network con­fig­u­ra­tion, es­pe­cial­ly if the IP address and DNS server are set to obtain au­to­mat­i­cal­ly. In many cases, restart­ing the router can help eliminate temporary network dis­rup­tions or cached errors.

Domain Name Reg­is­tra­tion

Build your brand on a great domain

• Free Wildcard SSL for safer data transfers 
• Free private reg­is­tra­tion for more privacy
• Free Domain Connect for easy DNS setup

Check

Step 7: Tem­porar­i­ly disable VPN tools and other security software

If you use VPN software to browse the internet anony­mous­ly and securely or to transfer data through virtual networks, it may well be re­spon­si­ble for the DNS_PROBE_FINISHED_NXDOMAIN error. This applies to both external tools and VPN ex­ten­sions you have installed in Chrome. The same is true for any security software you use, such as antivirus programs or firewalls. These ap­pli­ca­tions are essential for pro­tect­ing your system, but they are also known to oc­ca­sion­al­ly block con­nec­tions without a valid reason.

If you encounter a name-res­o­lu­tion problem, try tem­porar­i­ly disabling the mentioned software first. If the target page loads correctly afterward, you have iden­ti­fied the cause of the error and can then look for a suitable solution to eliminate the blockage caused by the re­spon­si­ble tool. Al­ter­na­tive­ly, you may consider switching to different software.

Step 8: Check hosts file

In your system’s hosts file, you can manually assign IP addresses to specific domains. Incorrect or outdated entries can prevent a domain from being resolved correctly, even if it actually exists. Carefully check this file on your system. On Windows, you can usually find it under C:\Windows\System32\drivers\etc\hosts. Remove or correct any entries that block the desired domain or point it to the wrong IP address. Then save the file and restart your browser or DNS client to apply the changes.

Step 9: Reset Chrome flags to “Default”

Chrome is es­pe­cial­ly popular because of its advanced features. To allow users to test these features before their official release, Google offers many potential new functions and settings as flags in an ex­per­i­men­tal state. Some are activated au­to­mat­i­cal­ly when the browser updates, while others must be switched on or off manually. Since these features are still in the testing phase, they can oc­ca­sion­al­ly cause con­nec­tion problems such as the DNS_PROBE_FINISHED_NXDOMAIN error. If the previous trou­bleshoot­ing steps have not been suc­cess­ful, you should try restoring all flags to their default state (enabled/disabled):

1. Start Google Chrome.
2. Type chrome://flags into the address bar and press Enter.
3. Click the “Reset all” button.
4. Then click the displayed “Relaunch” button to restart the browser and apply the changes.

Step 10: Contact website operators

If the error persists and only a specific domain is affected, the cause is very likely on the website operator’s side. This may be due to faulty name servers, in­cor­rect­ly con­fig­ured DNS records, or an expired domain.

In such cases, website operators should check whether the DNS con­fig­u­ra­tion is correct and make the necessary ad­just­ments to ensure that the domain becomes reachable again. In some sit­u­a­tions, it may be necessary to contact the hosting provider or domain registrar.