DNS_PROBE_FINISHED_NXDOMAIN is a common error message that you get while browsing internet through Google Chrome. Not only DNS Probe Finished nxdomain error but also several other errors were there. Each errors have its own meaning and we should handle them in a variety of way. So today we are discussing about how to solve this nxdomain error message once you got it on your computer.
We had received this mail from Joe Franklin from Pittsburgh regarding this issue. Here’s what Joe had written to us.
I am Joe working as Sr. Spec Product manager at BNY MELLON. Here we are using Verizon High Speed Internet for accessing Internet at our office. As usual the company is providing Internet without any other issues. But things had changed after we tried to add some new devices to the network. last day, our company had bought 5 Laptops which are running on Windows 8. While connecting the laptop to our WiFi network, it is showing dns_probe_finished_nxdomain error message. We are using Google Chrome as the default browser and Other browsers are showing No Internet error message. Our Network administrator is on a field work and arrive only after 1 week. Is there any simple way to resolve this issue. I can pay you if you could resolve this issue. Waiting for your reply.
How do we solve DNS_PROBE_FINISHED_NXDOMAIN in the above situation?
What is DNS?
Here is a small information for you. DNS means Domain Name Servers. The main job of DNS is to translate the domain name to its corresponding IP address. For example, we need to deal with hundreds of websites daily. Among them there will be Google, Facebook, YouTube etc. All these domain names have corresponding IP address where the files were stored. It is very had to remember the numeric IP address for a human being and here comes the importance of DNS. DNS converts the IP address into Domain Name which is easily memorable.
So the DNS Probe Finished nxdomain error is occurring due to DNS lookup failed. By default, your Computers use DNS which configured in your router or modem those are provided by your ISP Internet Provider. Changing the Private DNS settings to some public DNS may resolve this issue. So you can resolve this issue in most cases by doing some simple steps. Before proceeding this steps, kindly check whether other browsers are too showing the same or related issues.
Solution 1: Changing the DNS IP Address – 100% Working
Here is the 100% working solution for this issue. In 95% Situation the below steps work for you and this is personally tested by me. For “Joe Franklin”, the same solution worked without any other issues. Here are the steps.
Step 1:- Right Click on the Network icon on the right corner of the taskbar. If you have connected to WiFi, it will be a WiFi icon or if you are connected via LAN cable, it will be a PC icon.
Step 2:- Now a control panel window will open with lots of settings. Among them you need to choose Adapter Setting.
Step 3:- By clicking Change Adapter Settings, you could see all connections available to your Computer. Among them, there will be one Active connection in which you are getting the “dns_probe_finished_nxdomain” error message.
Step 4:- Right Click on that connection and choose Properties.
Step 5:- There you could see a list of properties and among them, choose Internet Protocol Version 4 (TCP/IPv4) and Click on Properties of Internet Protocol Version 4 (TCP/IPv4).
Step 6:- There you could see an option to assign custom DNS Settings. in that field fill the DNS as shown below.
Preferred DNS Server as 126.96.36.199
Alternative DNS Server as 188.8.131.52
Step 7:- Click OK and continue browsing.
Alternative Solution for dns_probe_finished_nxdomain by DNS Flusing
This is an alternative solution for the above issue. I am sure that you won’t need to follow the below solution as the above works in almost all situation. Please do the below only if you couldn’t solve the issue by the above solution.
Step 1:- Open Command Prompt by Pressing Win+R and by typing cmd.
Step 2:- Now type “netsh winsock reset catalog” and press enter.
Step 3:- After the command get executed, reboot your PC.
Now you won’t get the above mentioned error.
Hope one of the above solution worked for you. Whatever your finding, please feel free to comment below. If you have any other solutions, mention it. We appreciate your input.