FernTool

How to fix DNS_PROBE_FINISHED_NXDOMAIN

DNS_PROBE_FINISHED_NXDOMAIN means your browser asked for the website’s address and was told “that name doesn’t exist” (NXDOMAIN = non-existent domain). Either the address is wrong or the domain really is gone, or something on your side (your device, router, DNS server, VPN or ISP) gave a wrong answer. The first step tells you which: put the address into the is it down for everyone or just me checker.

Step 1: is it you or the website? (1 minute)

  1. Check the spelling in the address bar. One wrong letter (gooogle.com, .co.za vs .com) gives exactly this error.
  2. Paste the address into the down checker. If it says the domain doesn’t exist, it’s not you: the domain has expired, been deleted or was never set up. Look at its WHOIS record for the expiry date.
  3. If the checker says the site is up, the problem is on your side. Work through the fixes below, in order; most people are sorted by fix 3.

Fix 1: restart the router and your device

Unplug the router for 30 seconds, plug it back in, wait for the lights to settle, and restart your computer or phone. Routers keep their own list of addresses, and a restart clears it. Also try the site on mobile data: if it works there, the problem is your home network or ISP, so skip to fix 4.

Fix 2: flush your DNS cache

Your computer and Chrome both remember addresses, including bad answers. On Windows open Command Prompt and run ipconfig /flushdns. On a Mac run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. Then open chrome://net-internals/#dns and click Clear host cache. Step-by-step for every device: how to flush your DNS cache.

Fix 3: switch to a public DNS server

If your ISP’s DNS server is having problems it can wrongly say a site doesn’t exist. Switch to Cloudflare (1.1.1.1 and 1.0.0.1) or Google (8.8.8.8 and 8.8.4.4). Doing it on the router fixes every device at home: change DNS on your router, or on Windows only. Not sure which to pick? See the best public DNS servers.

Fix 4: turn off VPN, proxy, ad blocker and “secure DNS” filters

VPN apps, family-safety filters (like CleanBrowsing or router parental controls), antivirus web shields and ad blockers can block a domain by answering “doesn’t exist”. Turn them off one at a time and reload. In Chrome, also check Settings → Privacy and security → Security → Use secure DNS: if it’s set to a custom provider, switch it to your current provider or turn it off to test.

Fix 5: renew your connection (Windows)

Open Command Prompt as administrator and run these one by one, then restart the PC:

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

This resets Windows’ network settings to clean defaults. It doesn’t delete files or saved Wi-Fi passwords.

Fix 6: check the hosts file

The hosts file can force a name to a dead address. On Windows open Notepad as administrator and open C:\Windows\System32\drivers\etc\hosts; on a Mac run sudo nano /etc/hosts. Any line with the website’s name in it (that you didn’t add on purpose) should be deleted or commented out with #.

Fix 7: Android and iPhone

Fix 8: reset Chrome’s network settings

Go to chrome://flags and click Reset all if you’ve changed experimental settings, then restart Chrome. If only Chrome fails but Edge or Firefox work, a Chrome extension is the likely cause: test in an Incognito window with extensions off.

Fix 9: it’s your own website

If you own the domain and visitors see this error:

  1. Check the domain hasn’t expired in its WHOIS record; renew it at your registrar if it has.
  2. Run a DNS lookup. There must be an A (or AAAA/CNAME) record for both example.com and www.example.com; a missing www record is a classic cause.
  3. Changed name servers or hosts recently? The DNS propagation checker shows which big DNS services still have the old answer and how long until they update.

Related errors and what they mean

DNS_PROBE_FINISHED_NO_INTERNET
Your device isn’t connected at all. Check Wi-Fi or cables, then run the ping test once you’re back online.
DNS_PROBE_FINISHED_BAD_CONFIG / DNS_PROBE_POSSIBLE
Your DNS settings are broken or unreachable. Fixes 1, 3 and 5 usually solve it.
ERR_NAME_NOT_RESOLVED
Same problem as NXDOMAIN, different wording (also on Android Chrome). Same fixes.
Safari: “Safari can’t find the server”
Apple’s wording for the same DNS failure.
Firefox: “Hmm. We’re having trouble finding that site.”
Firefox’s wording. Clear its DNS cache at about:networking#dns.
Edge: “Hmm… can’t reach this page”
Edge (Chrome-based) shows the same DNS_PROBE codes underneath.

Frequently asked questions

What does DNS_PROBE_FINISHED_NXDOMAIN mean?

It means the DNS server your device uses said the website’s name does not exist. Either the name is wrong or expired, or your device, router, VPN or DNS server gave a wrong answer.

Is DNS_PROBE_FINISHED_NXDOMAIN a virus?

Almost never. It is usually a typo, a stale DNS cache, a VPN or ad blocker, or a temporary ISP DNS problem. Malware that edits the hosts file can cause it, which is why fix 6 checks that file.

Why does a site work on my phone but not my computer?

Each device has its own DNS cache and settings. Flush the computer’s DNS and Chrome’s host cache, and check it isn’t using a VPN, proxy or a different DNS server.

How long does NXDOMAIN last?

A “does not exist” answer is cached for minutes up to a few hours, depending on the domain. Flushing your DNS cache and switching to a public DNS server skips the wait on your side.

More guides