How to fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome (Windows, Mac, Android, iPhone)

You type an address, hit Enter, and Chrome shows: "This site can't be reached. example.com's server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN."

The good news: this error is specific. It always means the same thing, and the fixes are short.

What DNS_PROBE_FINISHED_NXDOMAIN means

Before your browser can load a page, it has to turn the domain name into an IP address. That lookup is DNS. NXDOMAIN stands for "non-existent domain": the DNS resolver your device asked replied that the name does not exist.

That reply can be true or false:

• True: the domain is mistyped, expired, or was never set up (no DNS records).
• False: the domain exists, but your device got a wrong or stale answer. Common causes are a cached old answer, a broken resolver at your ISP, a VPN or ad-blocking DNS that filters the domain, or a hosts file entry.

Edge shows the same problem as "Hmm... can't reach this page", Firefox as "Hmm. We're having trouble finding that site", and Safari as "Safari can't find the server".

Step 1: Rule out a typo or a dead domain

Check the spelling first, including the ending (.com vs .co, .net vs .org). Then test whether the domain resolves anywhere at all by asking a public resolver directly.

Windows:

nslookup example.com 8.8.8.8

macOS / Linux:

dig example.com @8.8.8.8

• If the public resolver also returns NXDOMAIN (*** can't find example.com: Non-existent domain on Windows, status: NXDOMAIN in dig), the domain really doesn't resolve. If it's your domain, check the registration and DNS records at your registrar. If it isn't, there's nothing to fix locally.
• If the public resolver returns an IP address, the domain is fine and your local DNS is the problem. Continue below.

It also helps to check whether the site loads from outside your network; a free website checker such as upordown.online shows in a few seconds whether the site is up for everyone.

Step 2: Restart the simple things

Unexciting, but it fixes a large share of cases:

1. Turn Wi-Fi off and on, or unplug the router for 30 seconds.
2. Disconnect your VPN, or turn it on if you normally use it.
3. Temporarily disable ad-blocking or "secure DNS" apps and extensions.
4. Reload the page.

Step 3: Clear the cached DNS answers

Your OS and Chrome both keep recent DNS answers. If a site recently moved or briefly failed, you might be stuck on a bad cached answer.

• Chrome's cache: open chrome://net-internals/#dns and click Clear host cache. Then open chrome://net-internals/#sockets and click Flush socket pools.
• Windows: in an admin Command Prompt, run ipconfig /flushdns.
• macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
• Linux with systemd-resolved: sudo resolvectl flush-caches.

(If you want the full version of this step for every OS and browser, flushing DNS deserves its own guide; the commands above cover most cases.)

Step 4: Switch to a reliable public DNS resolver

If your ISP's resolver is broken or filtering, change resolvers. Common choices are 1.1.1.1 / 1.0.0.1 (Cloudflare) and 8.8.8.8 / 8.8.4.4 (Google).

Windows 10/11: Settings → Network & internet → Wi-Fi (or Ethernet) → your connection → DNS server assignment → Edit → Manual → IPv4 on → enter 1.1.1.1 and 8.8.8.8 → Save.

macOS: System Settings → Network → Wi-Fi → Details → DNS → click + and add 1.1.1.1 and 8.8.8.8 → OK.

Android 9+: Settings → Network & internet → Private DNS → Private DNS provider hostname → one.one.one.one or dns.google.

iPhone / iPad: Settings → Wi-Fi → tap the (i) next to your network → Configure DNS → Manual → add 1.1.1.1 and 8.8.8.8 → Save.

Linux (NetworkManager):

nmcli con mod "YourConnection" ipv4.dns "1.1.1.1 8.8.8.8" ipv4.ignore-auto-dns yes
nmcli con up "YourConnection"

You can also set it in Chrome only: Settings → Privacy and security → Security → Use secure DNS → choose a provider.

Step 5: Check the hosts file

The hosts file overrides DNS. An old entry from a dev project or a "blocker" tool can break a domain.

• Windows: open Notepad as administrator and open C:\Windows\System32\drivers\etc\hosts.
• macOS / Linux: sudo nano /etc/hosts.

Remove or comment out (with #) any line containing the domain, save, and flush DNS again.

Step 6: Renew your IP and reset the network stack (Windows)

If several sites fail, reset networking in an admin Command Prompt:

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

Restart the computer afterwards.

Step 7: Phones only — reset network settings

As a last resort on mobile:

• Android: Settings → System → Reset options → Reset Wi-Fi, mobile & Bluetooth.
• iPhone: Settings → General → Transfer or Reset iPhone → Reset → Reset Network Settings.

You'll need to re-enter Wi-Fi passwords afterwards.

If it's your own website

If visitors report DNS_PROBE_FINISHED_NXDOMAIN for your domain:

1. Confirm the domain hasn't expired at your registrar.
2. Check that the nameservers at the registrar match your DNS host.
3. Confirm an A (and/or AAAA or CNAME) record exists for the exact hostname, including www.
4. After a change, allow for the record's TTL before every resolver sees it.

dig NS example.com +short
dig www.example.com +short

FAQ

Is DNS_PROBE_FINISHED_NXDOMAIN a virus?

No. It's a DNS lookup failure. Malware can change DNS settings or the hosts file, so if the error appears on many sites suddenly, run a security scan and check both.

Why does the error happen on one site only?

Usually a stale cached answer, a hosts file entry, or the domain itself being misconfigured or expired. Test the domain against 8.8.8.8 to tell which.

Why does it work on mobile data but not Wi-Fi?

Your Wi-Fi network uses a different resolver, usually your router or ISP. Changing the DNS server on the device or router normally fixes it.

How long does a DNS change take to work?

Between a few minutes and the record's TTL, which is often one hour. The old claim of "up to 48 hours" mostly applies to nameserver changes.

Does clearing browser history fix it?

Rarely. Clearing Chrome's host cache at chrome://net-internals/#dns targets the actual problem far better.