|

DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It

You type in a web address, hit Enter, and Chrome throws back DNS_PROBE_FINISHED_NXDOMAIN with a little “This site can’t be reached” message. It looks scary. It usually isn’t.

Here’s the plain-English version: your browser asked the internet’s phone book (DNS) for the website’s address, and the phone book said that name doesn’t exist. NXDOMAIN literally means “non-existent domain.” Sometimes that’s true. More often, something between you and the phone book is confused.

What causes it

  • A typo in the address. Embarrassingly common. One wrong letter and the domain really doesn’t exist.
  • The website is gone or its domain expired. If nobody renewed it, DNS stops answering.
  • A stale DNS cache. Your computer remembers old answers, and sometimes it remembers wrong.
  • Your internet provider’s DNS servers are having a bad day.
  • A VPN, proxy or security app intercepting lookups and getting them wrong.
  • A messed-up router that’s handing out bad DNS settings.

Quick test: is it you or the website?

Before you change anything, try the same site on your phone using mobile data (Wi-Fi off). If it loads there, the problem is on your network or computer. If it fails everywhere, the site itself is probably down or gone, and there’s nothing to fix on your end.

Fix 1: Check the address

Read the URL slowly. Look for doubled letters, a missing dot, or .con instead of .com. If you clicked a link, try typing the site’s main address yourself instead.

Fix 2: Restart your router and computer

Unplug the router, wait 30 seconds, plug it back in, and give it two minutes to come back up. Restart your computer while you wait. Boring advice, but it clears a surprising number of DNS problems.

Fix 3: Flush your DNS cache

This wipes out the old answers your computer has stored so it asks fresh.

  • Windows: open Command Prompt as administrator and run ipconfig /flushdns.
  • Mac: open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then enter your Mac password.
  • Chrome only: type chrome://net-internals/#dns in the address bar and click Clear host cache.
  • Phone: turn airplane mode on for ten seconds, then off.

Fix 4: Switch to a public DNS server

Your internet provider’s DNS is the default, and it’s not always the most reliable. Switching to a well-known public DNS is free and takes two minutes.

ProviderPrimarySecondary
Cloudflare1.1.1.11.0.0.1
Google8.8.8.88.8.4.4
Quad99.9.9.9149.112.112.112
  • Windows: Settings > Network & internet > your connection > Hardware properties > DNS server assignment > Edit, then choose Manual and enter the addresses.
  • Mac: System Settings > Network > your connection > Details > DNS, then add the addresses with the + button.
  • Whole house: change the DNS settings in your router’s admin page so every device gets the fix.

Fix 5: Turn off your VPN or proxy

VPNs and some antivirus “web protection” features route your DNS lookups through their own servers. If those servers hiccup, you get NXDOMAIN. Pause the VPN or the web shield for a minute and reload the page.

Fix 6: Reset your network settings

On Windows, open Command Prompt as administrator and run these one at a time, then restart:

  • netsh winsock reset
  • netsh int ip reset
  • ipconfig /release then ipconfig /renew

On a Mac, you can remove your Wi-Fi network from System Settings and join it again, which forces fresh settings.

Fix 7: Check your hosts file

Your computer has a small text file called hosts that can override DNS. Some software, and occasionally malware, adds lines to it. On Windows it lives at C:\Windows\System32\drivers\etc\hosts, and on a Mac it’s /etc/hosts. If you see the website you’re trying to reach listed in there and you didn’t add it, remove that line.

If you run the website

Seeing this on your own site? Check that the domain hasn’t expired, that your nameservers point to the right host, and that there’s an A record for the domain. Changes can take a few hours to spread, so a site that just moved may show NXDOMAIN for some visitors and not others.

Our take

Nine times out of ten, a router restart plus a DNS flush clears it. If it keeps coming back, switch to Cloudflare or Google DNS and you’ll likely never see it again. And if the site fails on your phone’s mobile data too? It’s not you. Walk away and try later.

FAQ

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

Your browser couldn’t find an address for the website you typed. NXDOMAIN means the domain name didn’t resolve, either because it doesn’t exist or because a DNS lookup failed.

Is DNS_PROBE_FINISHED_NXDOMAIN a virus?

Almost never. It’s a lookup problem. Malware can edit your hosts file to cause it, so check that file if the error only hits certain sites.

Does changing DNS slow down my internet?

No. Public DNS like Cloudflare or Google is often as fast or faster than your provider’s.

Why does the error only happen on one device?

That device likely has a stale DNS cache, a VPN, or custom network settings. Flush its DNS and check its settings.

Can a website owner cause this error?

Yes. An expired domain or broken DNS records will show this error to every visitor.

Related fixes

Similar Posts

Leave a Reply

Your email address will not be published. Required fields are marked *