Chrome is one of the most cohesive web browsing experiences you can have right now. However, for all the good that this browser packs, there can be annoying bugs and glitches here and there.
One such issue is the DNS_Probe_Finished_NXDomain error that can restrict internet access to your browser. In this article, we’re going over eight solutions you can use to resolve the error.
Restart your router
The first thing you should do is restart your router. This can help you find out any internet issues before you start fiddling with your browser. Restarting networking equipment can magically deal with several such issues.
Check your antivirus
Although a bit of a far shot, but you should check your antivirus to see if it’s restricting Chrome’s internet access. This can happen due to several reasons, but if something fishy shows up in your antivirus, there could be malware present on your machine that could be causing the error.
Clear Chrome’s data
Buggy files stored in the cache or any other form can cause all sorts of random internet connectivity issues. Here’s how to clear them out.
Step 1: Type chrome://settings/clearBrowserData in your browser’s address bar and hit Enter.
Step 2: Select the cache and cookies options and make sure the Time range is set to All time. Click on the Clear now button to clear out all the data.
Clear DNS settings.
As the error itself states, it has something to do with DNS settings. Misconfigured DNS settings can cause a lot of headaches. Here’s how you can reset them.
Step 1: Press Windows key + R and type in cmd and hit enter.
Step 2: Type in ipconfig /flushdns to reset DNS settings to default.
If the above command doesn’t help, try entering these commands in the Command Prompt one at a time.
netsh winsock reset netsh int ip reset
If you suspect an issue with your router’s DHCP assignment, use these commands to release your old IP and request a new one.
ipconfig /release ipconfig /renew
If this doesn’t work either, use the following commands to reset your network stack.
ipconfig/flushdns nbtstat -R nbtstat -RR netsh int ip reset C:\resetlog.txt netsh winsock reset
On a mac, head over to your terminal and type in sudo killall -HUP mDNSResponder. Type in your password when prompted for it and try re-accessing the internet.
Try Google’s DNS
Another thing that you can try out is switching to a public DNS. We’re using Google’s DNS for this example as it’s one of the fastest and most reliable public DNSs out there.
Step 1: Press Windows key + I to open the Windows settings and click on Network & Internet.
Step 2: Click on Change adaptor options.
Step 3: Right-click on your active network (WiFi or LAN) and click Properties.
Step 4: Find Internet Protocol Version 4 in the list, click on it and then click Properties.
Step 5: Check the Use the following DNS server addresses radio button and type in 18.104.22.168 and 22.214.171.124 in the preferred and alternative DNS addresses, respectively.
Reset Chrome flags to default
A misconfigured or buggy Chrome flag can cause this issue as well. Here’s how you can reset all Chrome flags to their default values.
Step 1: Head over to chrome://flags.
Step 2: Click on Reset all in the top right to reset all flags to their default values.
If nothing else works, you can try resetting Chrome to ensure there are no faulty settings in the browser that could be causing this issue.
Step 1: Head over to chrome://settings/reset. Click on Restore settings to their original defaults.
Step 2: Chrome will show you a warning prompt. Click on Reset Settings, and your browser will reset to default settings.
Restart the DNS client service
Restarting the DNS client service on your PC can help clear up any buggy files or paused processes that might be causing problems.
Step 1: Press Windows key + R to open the Run prompt, type in services.msc and hit enter.
Step 2: Locate the DNS Client service, right-click it and select Restart. If the restart option is greyed out, click Refresh instead.