DNS_PROBE_FINISHED_NXDOMAIN: 9 Ways to Fix It

Chrome shows "This site can't be reached" with the code DNS_PROBE_FINISHED_NXDOMAIN underneath. Edge shows "Hmm... can't reach this page" with the same code. The error looks technical, but it has a simple meaning, and the fixes take minutes. This guide explains the error, helps you tell whether the problem is the site or your PC, and walks through nine fixes in order.

What DNS_PROBE_FINISHED_NXDOMAIN Means

Before the browser can open a site, it asks a DNS server for the site's IP address. NXDOMAIN stands for "non-existent domain": the DNS server answered, but said the name does not exist. That happens when:

• The address has a typo, or the domain really has expired or never existed.
• Your PC or browser has cached a wrong answer.
• Your DNS server is failing and returning bad answers.
• A VPN, proxy, parental-control or security tool is blocking the name.
• A line in the Windows hosts file points the site somewhere wrong.

It is different from DNS server not responding, where no answer comes back at all. With NXDOMAIN an answer arrives, it is just "no such site".

Is It the Website or Your PC?

Open the same address on your phone using mobile data, not Wi-Fi:

• It fails on mobile data too: the site itself is down or the domain has expired. Nothing on your PC will fix it; wait or contact the site owner.
• It works on mobile data but not your PC: the problem is on your PC or network. Use the fixes below.
• Only one site fails: start with Fix 1–4. Every site fails: start with Fix 5 and 6.

9 Ways to Fix DNS_PROBE_FINISHED_NXDOMAIN

1. Check the address

   Look for typos, missing letters and the wrong ending (.com vs .co). Type the address again instead of using an old bookmark or autocomplete suggestion, which may point to an outdated address.

2. Flush the Windows DNS cache

   Command

   ipconfig /flushdns

   Run it in Terminal (Admin). Windows forgets every cached lookup and asks again. Full guide: flush DNS on Windows 11.

3. Clear the browser's host cache

   Chrome and Edge keep their own DNS cache. Open chrome://net-internals/#dns (or edge://net-internals/#dns) and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools. Restart the browser.

4. Check Secure DNS in the browser

   Chrome: Settings > Privacy and security > Security > Use secure DNS. Edge: Settings > Privacy, search, and services > Security. If a custom provider is chosen, switch to "With your current service provider" or pick Cloudflare, and test again. A broken custom DNS-over-HTTPS provider produces exactly this error.

5. Switch to a public DNS server

   If many sites fail, your ISP's DNS may be returning bad answers. In Settings > Network & internet > your connection > DNS server assignment > Edit, choose Manual and set 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google). Screens: change DNS server on Windows 11.

6. Renew the IP address and reset Winsock

   Commands

   ipconfig /release
   ipconfig /renew
   netsh winsock reset

   Restart the PC after the last command.

7. Turn off VPN, proxy and filters

   Disconnect any VPN, turn off the proxy in Settings > Network & internet > Proxy, and pause ad blockers, parental controls and antivirus web shields. Some block whole domains by returning NXDOMAIN on purpose.

8. Check the hosts file

   Open Notepad as administrator, then open C:\Windows\System32\drivers\etc\hosts (choose "All files"). Lines that start with # are comments. If a line without # mentions the failing site, delete it, save and flush DNS again.

9. Restart the router

   Many routers cache DNS for every device. Unplug it for 30 seconds. If every device on the network shows the error for one site, this is often the fix.

Test the Lookup Yourself

To see what your DNS server answers, run nslookup with the site name, then ask a public server directly:

nslookup example.com
nslookup example.com 1.1.1.1

If the first command says "Non-existent domain" but the second returns an address, your current DNS server is the problem: switch DNS (Fix 5). If both fail, the domain really does not resolve right now. IP Address App does the same check with a click: its DNS Lookup tool queries any domain and shows the answer, next to your current DNS servers.

Similar Browser Errors

FAQ

Conclusion

DNS_PROBE_FINISHED_NXDOMAIN means "this name does not exist" according to your DNS server. Check the address, flush Windows and browser DNS caches, and switch to a public DNS server if the error keeps appearing. The hosts file and blocking tools cover the rare remaining cases. Find more network apps for Windows to keep an eye on your connection.

Get it freeIP Address App