How to Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome
What DNS_PROBE_FINISHED_NXDOMAIN means
DNS_PROBE_FINISHED_NXDOMAIN is Chrome's way of saying its DNS probe finished with an NXDOMAIN result — "non-existent domain." Every time you visit a site, your computer asks a DNS server to translate the domain name (like example.com) into an IP address. When that lookup fails, Chrome cannot even start loading the page, so you get this error instead of the site.
The failure can sit in several places: a stale entry in your computer's DNS cache, a DNS server that is down or slow (often your ISP's default), a router holding bad DNS data, a VPN or proxy rerouting lookups, or simply a mistyped domain that genuinely does not exist. The fix is a ladder: clear the local caches first, then switch to a reliable public DNS service.
Common causes
- Stale local DNS cache: your computer remembers an old, wrong, or expired DNS answer and keeps reusing it.
- Unreliable ISP DNS servers: your provider's default DNS servers can be slow, down, or return bad answers.
- Router holding bad DNS data: the router caches DNS too, and a glitch there poisons every device on the network.
- VPN or proxy interference: VPNs reroute DNS lookups; a misconfigured or disconnected VPN breaks resolution entirely.
- Typo in the domain name: a misspelled domain genuinely does not exist, so DNS correctly returns NXDOMAIN.
How to fix DNS_PROBE_FINISHED_NXDOMAIN — step by step
Work through these fixes in order. Most cases are fixed by step 1 or 2.
- Flush your DNS cache. On Windows, right-click Start, choose Terminal (Admin) or Command Prompt (Admin), type ipconfig /flushdns, and press Enter — you should see "Successfully flushed the DNS Resolver Cache." On a Mac, open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, entering your password when asked. Then clear Chrome's own DNS cache: type chrome://net-internals/#dns in the address bar and click Clear host cache. Close Chrome completely and reopen it before testing.
- Switch to a public DNS server. Your ISP's DNS may be the problem. On Windows, open Settings, then Network & internet, then your connection (Wi-Fi or Ethernet), then Hardware properties, then Edit under DNS server assignment. Switch to Manual, turn on IPv4, and enter 8.8.8.8 as the preferred DNS and 8.8.4.4 as the alternate (Google's public DNS), or 1.1.1.1 and 1.0.0.1 (Cloudflare's). Save and test. On a Mac, go to System Settings, then Wi-Fi, then Details next to your network, then DNS, and add the same addresses with the plus button.
- Restart your router and modem. Unplug both the router and the modem from power, wait a full 60 seconds, then plug the modem back in first. Wait until its lights stabilize, then plug the router back in and wait again. This clears the router's DNS cache and forces a fresh connection to your ISP. If the error appears on every device in your home, the router was almost certainly the culprit — and this step fixes it.
- Clear Chrome's browsing data. A corrupted browser cache can keep serving the failed lookup. Press Ctrl + Shift + Delete (Cmd + Shift + Delete on a Mac), set the time range to All time, check Cached images and files and Cookies and other site data, and click Clear data. Restart Chrome and try the site again. If it loads now, stale cached DNS data in the browser was to blame.
- Disable your VPN and proxy, then check the URL. Temporarily disconnect your VPN and reload the page — if it works, the VPN's DNS handling is broken; try a different VPN server or enable the VPN's own DNS leak protection setting. Also check for a proxy: in Chrome go to Settings, then System, then Open your computer's proxy settings, and turn off any proxy you do not recognize. Finally, retype the domain carefully — a typo like gooogle.com or a missing letter produces a genuine NXDOMAIN that no fix can resolve.
Did this fix it? Quick checklist
- The site loads without the DNS error
- Other websites load normally
- The error is gone after a full browser restart
- It works with the VPN disconnected and reconnected
If the error affects only one specific site on all your devices, the site's own DNS may be broken or the domain may have expired — check the domain on a tool like dnschecker.org to see whether it resolves worldwide. If only your computer is affected while your phone on the same Wi-Fi works, the problem is local to that machine: double-check for third-party firewall or "internet security" software filtering DNS, and try the steps above once more after a reboot.
Frequently asked questions
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
It means Chrome's DNS lookup failed with an NXDOMAIN (non-existent domain) result — the domain name could not be translated into an IP address. The cause is usually a stale DNS cache, a bad DNS server, a router glitch, VPN interference, or a typo in the address.
Is DNS_PROBE_FINISHED_NXDOMAIN a virus?
No. It is a standard network error, not malware. It simply means the domain lookup failed. That said, malware that hijacks DNS settings can cause it, so if the error appears out of nowhere alongside other odd behavior, run a malware scan.
Why does the error happen on Wi-Fi but not mobile data?
Because the two networks use different DNS servers and routers. If mobile data works, your home router or your ISP's DNS is the problem — restart the router and switch to a public DNS service like 8.8.8.8 as described above.
Will changing my DNS server to 8.8.8.8 cause problems?
For most people, no — Google's 8.8.8.8 and Cloudflare's 1.1.1.1 are fast, reliable public DNS services used by millions. If you rely on ISP-specific features (like parental controls from your provider), those may stop working, in which case you can switch back at any time.