Updated 2 hours ago
Your browser asked the Internet "where is this website?" and the answer came back: "That place doesn't exist."
That's what DNS_PROBE_FINISHED_NXDOMAIN means. The NXDOMAIN part stands for "Non-Existent Domain"—a definitive answer from a DNS server that searched its records and found nothing. This isn't a timeout. It's not a connection failure. The DNS system is working perfectly; it's telling you the domain genuinely cannot be found.
Why This Happens
You typed it wrong. This is the most common cause, and there's no shame in it. "gooogle.com" returns NXDOMAIN because that domain doesn't exist. Check the address bar before diving into troubleshooting.
The domain expired. Domain registrations require periodic renewal. When owners forget to pay, their domain gets removed from DNS records. The website existed yesterday; today, DNS correctly reports it's gone.
The domain is brand new. DNS changes take time to propagate across the Internet—anywhere from minutes to 48 hours. A newly registered domain might not have reached your DNS server yet. Some servers know about it; yours doesn't.
Your DNS cache is lying to you. Your computer remembers previous DNS lookups to speed up browsing. If that cache contains stale data—maybe an old NXDOMAIN response for a domain that now exists—you'll get the wrong answer even though the domain is fine.
Your DNS server has problems. The DNS server you're using (usually your ISP's) might have outdated records, configuration errors, or be experiencing issues. The domain exists, but your DNS server doesn't know it.
How to Fix It
Work through these in order. Test after each step.
Check the URL
Look carefully at the address bar. Extra letters, missing letters, wrong top-level domain (.com vs .org). Try visiting google.com to confirm your Internet is working at all.
Flush Your DNS Cache
This forces your computer to ask for fresh DNS information instead of relying on stored answers.
Windows: Open Command Prompt and run:
macOS: Open Terminal and run:
Linux: The command varies by distribution:
Restart Your Router
Unplug it, wait 30 seconds, plug it back in. Routers cache DNS responses too, and sometimes they need a fresh start.
Switch DNS Servers
If your ISP's DNS servers are the problem, bypass them entirely. Configure your network to use:
- Google Public DNS: 8.8.8.8 and 8.8.4.4
- Cloudflare DNS: 1.1.1.1 and 1.0.0.1
On Windows: Network and Sharing Center → Change adapter settings → Right-click your connection → Properties → Internet Protocol Version 4 → Enter DNS addresses.
On macOS: System Preferences → Network → Select connection → Advanced → DNS tab → Add servers.
Clear Browser Cache
In Chrome: Settings → Privacy and Security → Clear Browsing Data → Select "All time" → Check "Cached images and files" → Clear.
Disable VPN or Proxy
If you're using either, turn it off temporarily. Some VPN configurations route DNS queries in ways that cause resolution failures.
Try Another Device or Network
Access the site from your phone on mobile data. If it works there, the problem is your device or network. If it fails everywhere, the domain itself is the issue.
For Server Administrators
If users report NXDOMAIN errors for your domain, the troubleshooting is different.
Check domain registration. Log into your registrar. Is the domain active? Is payment current? Expired domains disappear from DNS immediately.
Verify nameservers. Your domain's nameserver configuration at the registrar must point to DNS servers that actually have your zone file. A mismatch here means DNS queries have nowhere to go.
Inspect DNS records. Use dig yourdomain.com or online DNS checkers to see what DNS servers are actually returning. Missing A records, typos in the zone file, or propagation delays all cause NXDOMAIN.
Monitor propagation. After DNS changes, use propagation checking tools to watch your updates spread globally. Some regions might take longer than others.
NXDOMAIN vs. Other DNS Errors
These errors look similar but mean different things:
DNS_PROBE_FINISHED_NXDOMAIN: The DNS server worked correctly and confirmed the domain doesn't exist.
DNS_PROBE_FINISHED_NO_INTERNET: Your device has no Internet connection. This is a connectivity problem, not DNS.
DNS_PROBE_FINISHED_BAD_CONFIG: Your network settings are misconfigured—wrong DNS servers, adapter problems.
ERR_NAME_NOT_RESOLVED: A broader category that includes DNS failures but also other resolution problems.
The key distinction: NXDOMAIN is a successful DNS query that returned a negative result. The system worked. The answer is just "no."
Frequently Asked Questions About DNS_PROBE_FINISHED_NXDOMAIN
Was this page helpful?