DNS Probe Finished NXDOMAIN: How to Fix in Chrome

This error means Chrome can’t find the website’s address (IP) through your DNS server, often due to a temporary glitch, incorrect DNS settings, or a corrupted cache. The fix usually involves flushing DNS, changing servers, or clearing Chrome’s internal cache. Below are step-by-step solutions that work for Windows, macOS, and Android.

What You’ll Need

Administrator or root access to your computer or router (for some steps).
Access to your router’s admin page (usually at 192.168.1.1 or 192.168.0.1).
A stable internet connection (even if the page fails, you need to reach other sites).

Step-by-Step

Try a different device or network. First, open the same URL on your phone (using mobile data) or another computer. If it works, the problem is local to your device or network. If it fails everywhere, the domain itself may be down (check with a site like downforeveryoneorjustme.com).
Restart your router and device. Power cycle your modem/router (unplug for 30 seconds, plug back in) and restart your computer or phone. This clears temporary network glitches and often resolves the error immediately.
Flush the DNS cache (Windows). Open Command Prompt as Administrator (right-click Start > Command Prompt (Admin)). Type ipconfig /flushdns and press Enter. Then type ipconfig /registerdns and press Enter. Restart Chrome.
Flush the DNS cache (macOS). Open Terminal (Finder > Applications > Utilities > Terminal). Run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (on older macOS, just sudo killall -HUP mDNSResponder). Enter your password if prompted.
Change your DNS server to a public one. Go to your network settings (Windows: Settings > Network & Internet > Change adapter options; macOS: System Preferences > Network > Advanced > DNS). Add 8.8.8.8 and 8.8.4.4 (Google) or 1.1.1.1 and 1.0.0.1 (Cloudflare). Remove any old DNS entries. Click OK/Apply and restart your browser.
Clear Chrome’s host cache. In Chrome, go to chrome://net-internals/#dns and click “Clear host cache.” Then go to chrome://net-internals/#sockets and click “Flush socket pools.” Restart Chrome.
Disable Chrome’s built-in DNS over HTTPS (DoH). Go to Chrome Settings > Privacy and security > Security. Scroll to “Use secure DNS” and turn it off. If it was off, turn it on and select a provider (e.g., Google Public DNS). This can fix conflicts with your router’s DNS.
Reset Chrome flags (if you’ve changed any). Go to chrome://flags and click “Reset all” at the top right. Restart Chrome.
Check your hosts file. On Windows, open Notepad as Admin and open C:\Windows\System32\drivers\etc\hosts. On macOS/Linux, open /etc/hosts. Look for any lines with the failing domain and delete them (unless you added them intentionally). Save and restart.
Update your router’s DNS settings. Log into your router (usually at 192.168.1.1 or 192.168.0.1), find the DNS settings under WAN or Internet, and change them to 8.8.8.8 and 8.8.4.4. Save and reboot the router.

Common Mistakes

Forgetting to restart Chrome after flushing DNS – the cached entries may still be in memory.
Typing the wrong IP address in DNS settings (e.g., 8.8.8.8 vs 8.8.8.9).
Editing the hosts file without admin rights – changes won’t save.
Changing DNS on the computer but not the router – if the router overrides, it won’t help.
Assuming the site is down when it’s actually a local issue – always test on another network first.

Tips

Use both IPv4 and IPv6 DNS addresses if your network supports IPv6 (e.g., 8.8.8.8 and 2001:4860:4860::8888).
If you use a VPN, try disconnecting it – VPNs often change DNS and cause this error.
Keep your router firmware updated – old firmware can have DNS bugs.
For persistent issues, consider using a free DNS benchmark tool to find the fastest server for your location.

Troubleshooting

If the error persists after trying all steps above:

Check if the domain is actually registered. Use a WHOIS lookup to see if the domain exists. If it doesn’t, no fix will work – you have a typo or the site was taken down.
Try a different browser. If Firefox or Edge loads the site, the problem is Chrome-specific. Reinstall Chrome (back up your bookmarks first) or try Chrome Beta/Canary.
Disable your antivirus/firewall temporarily. Some security software intercepts DNS and can block domains. If it works with them off, add an exception for the site.
Check for malware. Run a full system scan – some malware modifies DNS settings on your device.
Contact your ISP. If the error happens on multiple devices and after changing DNS to public servers, your ISP may have a routing issue. They can also confirm if the domain is blocked in your region.

Frequently Asked Questions

What does NXDOMAIN mean?

It stands for “Non-Existent Domain” – the DNS server responded that the domain name doesn’t exist. This can be a real typo or a temporary DNS failure.

Will changing DNS to 8.8.8.8 speed up my internet?

Not necessarily. It can improve DNS resolution times, but your overall speed depends on your ISP and connection. It helps mainly if your ISP’s DNS is slow or unreliable.

Is this error dangerous?

No, it’s usually a benign network issue. However, if it happens on every site, it could indicate malware or a compromised router – run a scan and check your router’s DNS settings.

Why does it happen only on my phone?

Phones often use the router’s DNS, but they also have their own DNS cache. Try toggling airplane mode or forgetting the Wi-Fi network and reconnecting.

Does clearing Chrome’s cache help?

Clearing the browser cache (history, cookies) doesn’t directly affect DNS, but clearing the host cache (step 6) does. It’s worth doing both if you have many cached pages.

How long does it take for DNS changes to take effect?

Usually a few seconds to a few minutes. If you’ve changed DNS on your router, it may take up to 24 hours for the world to update, but your local device should see it immediately.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →