Troubleshooting: DNS_PROBE_FINISHED_NXDOMAIN in Chrome?

I recently tried accessing a website through Google Chrome, but unfortunately the connection was not established. Rather, I was greeted with that dns_probe_finished_nxdomain Error message. When I investigated further I found that the problem was with the DNS and IP address search.

The role of the Domain Name Server is to translate the website name into a numeric IP address. For the end users entering an IP such as 192.168.0.1 instead of www.example.com would always be a tough job. However, the web still needs the numeric address for each website rather than its plain text format.

So if you enter a URL, the request goes to the DNS, which then looks for the IP address of the associated URL in its data set and sends it back to the server. The server will then forward this request and the desired connection will then be established.

However, if there is a problem during the whole process, the browser will throw a DNS-related error including the NXDOMAIN.

Troubleshooter: Site cannot be reached, Server IP could not be found?

Short form for the non-existent domain, is displayed if the DNS cannot find the associated IP address in its record book that corresponds to a specific URL.

How could a user fix this underlying problem? Well, this is where this guide is supposed to help you.

contents

The basic fixes

Before we move on to the slightly more advanced ones, let’s try a few basic fixes that are usually known to work. Consequences:

Check the url again

If you have entered an incorrect URL, DNS will not be able to determine the associated IP address and will therefore display the error mentioned above. So make sure again that there is no typo.

Deactivate Chrome Flags

Chrome Flags are experimental in nature and are used for testing beta Features before their final release. These flags span a broad domain, and some are network-only.

So if you have such a network related flag enabled, try getting it from the chrome: // flags Page. Most likely the one default Status.

7+ best Google Chrome Flags to try out!

Release and renew your IP address

Problems with the IP address can also be the reason for this DNS error. With that in mind, you could release your current IP address, clear all the cache it left, and then request that your system be assigned a new IP address by DHCP.

Here are the steps for releasing and renewing the IP address in the Windows operating system:

  1. Go over to the begin Menu,
  2. Search for cmd, and start it as a Administrator.
    Run command prompt as administrator
  3. Run the following three commands in sequence:
    ipconfig/release
    ipconfig/flushdns
    ipconfig/renew

The first command releases the currently assigned IP, the second clears the DNS cache of this address and the third and last command replaces it with a new IP address.

Once all three commands are done, restart your PC and see if it gives favorable results or not.

Reset winsock

Windows Socket is a term for the data stored on your PC that is responsible for successfully establishing a connection between an app / software and the network.

Sometimes problems have arisen when the WiFi is working fine but a particular device is still unable to access the internet. In such cases, the problem is usually with the winsock and it is best to reset it.

Here are the steps to reset Windows Socket or Winsock:

  1. begin command prompt as an administrator.
  2. Enter the following command in the Command Prompt window:
    netsh winsock reset

    netsh winsock reset command in Windows operating system

  3. Hit on Enter Keyboard key.

There’s no major problem with resetting Winsock, but make sure you don’t get into the habit of fixing network issues with this tweak. This is because if this need occurs regularly then there may be other (serious) problems with your PC Network adapter that needs a fix.

Change DNS server

The DNS servers you are currently using are assigned by your ISP. However, they are not fixed and you can redirect them to other servers as well.

In this regard is that Google DNS and Cloudflare DNS are usually the two preferred options, of which we would move on to the former.

Here are the steps to change the DNS server address in Windows:

  1. Start the Switchboard of the begin Menu.
  2. Open that Network and sharing center.
  3. Click on Change adapter settings from the left menu bar.
    Change adapter settings in the Windows operating system
  4. Right click on the network you are currently connected to and select Properties.
    Network connections Properties of WLAN or Internet modem
  5. Scroll and select Internet protocol version 4 (TPC / IPv4), and click properties Button.
    Internet connection characteristics WiFi IPv4.
  6. Choose Use the following DNS server addresses Radio button.
  7. Enter Follow the Google DNS addresses:
    Preferred DNS server: 8.8.8.8
    Alternative DNS server: 8.8.4.4
    Use the Google DNS settings in the Internet Properties option
  8. Hit on OK to save the changes.

Now try to access the website and see if the DNS_PROBE_FINISHED_NXDOMAIN Problem has been fixed or not.

If you’d rather use Cloudflare DNS instead, replace the preferred and alternate DNS with 1.1.1.1 and 1.0.0.1 respectively.

Check the hosts file

A hosts file is used to map a connection between the web address and its IP address. However, it could also be used to block access to a specific website.

This is usually done by assigning a loopback IP address (for example, 127.0.0.1). So you should check the hosts file and make sure that the affected site is not blackened out.

Here are the steps to check the hosts file in Windows:

  1. Start the File manager, and go to the following location:
    C:WindowsSystem32driversetc
  2. You should find a hosts file, open it with the notepad App.
    Windows network hosts file
  3. Scroll to the bottom and see if your site is mentioned along with the localhost address – 127.0.0.1.
    Delete the Line to Unblock website in the hosts file
  4. Delete all blocking entries and save the file with Ctrl + S. Keystroke.

Now try to access the site and the problem should be resolved after unblocking the site url.

Conclusion: Fixing the NXDOMAIN error in Chrome

So that was all of this guide to fixing the error This page is unreachable because of DNS_PROBE_FINISHED_NXDOMAIN in Chrome. We shared a total of six different fixes – two basic and four of slightly advanced fixes.

In my case, flushing the DNA did the trick. Over time, a lot of temporary data has accumulated about my current IP address. So deleting this and then assigning a new IP address to the DHCP worked.

How to fix Chrome: RESULT_CODE_HUNG error?

So in the comments section, let us know what success you saw in fixing the DNS_PROBE_FINISHED_NXDOMAIN error.

Finally, here are the recommended web browsers for your computer and mobile phone that you should try.

windowMac OSiOSAndroidLinux
Chrome windowChrome MacChrome iOSChrome AndroidFirefox Linux
Firefox windowSafari MacSafari iOSEdge AndroidChrome Linux
Edge windowFirefox MacEdge iOSSamsung internetEdge Linux

If you have any thoughts on this Troubleshooting: DNS_PROBE_FINISHED_NXDOMAIN in Chrome?, feel free to stop by downstairs Comment box. If you find this article helpful, consider sharing it with your network.

Please also subscribe to ours BrowserLike YouTube Channel for helpful video tutorials.

Related Posts