DNS_PROBE_FINISHED_NXDOMAIN means your DNS server looked up the domain name and confirmed it does not exist (NXDOMAIN = Non-Existent Domain). Chrome cannot connect because the domain name cannot be translated into an IP address. This is one of the most common DNS errors, and it usually means a typo in the URL, a DNS cache problem, or a recently expired/changed domain.
Despite the intimidating name, this error is almost always fixable in under five minutes. The domain may actually exist but your DNS resolver has stale or incorrect data. Here are the proven fixes in order of effectiveness.
Fix 1: Check the Domain Name for Typos
The most common cause is simply a misspelled domain name. Double-check every character in the URL. Common mistakes include: missing letters (gogle.com instead of google.com), wrong TLD (.com instead of .net), extra characters, and confusing hyphens with dots. If you clicked a link, the link itself may contain a typo.
Fix 2: Flush Your DNS Cache
Your system caches DNS lookups. If the domain recently changed its IP or your cache is corrupted, the old data returns NXDOMAIN. On Windows, open Command Prompt as Admin and run “ipconfig /flushdns.” On macOS: “sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.” Also clear Chrome’s DNS cache: go to chrome://net-internals/#dns and click “Clear host cache.”
Fix 3: Change Your DNS Server
Your ISP’s DNS may have incorrect records or may be slower to update than public DNS providers. Switch to Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare (1.1.1.1, 1.0.0.1). On Windows: Network Settings, adapter properties, IPv4, manual DNS. This often resolves NXDOMAIN errors immediately because public DNS servers update faster than ISP DNS.
Fix 4: Check Your Hosts File
The hosts file overrides DNS for specific domains. If the domain is mapped to 0.0.0.0 or 127.0.0.1 in your hosts file, it will return an NXDOMAIN-like error. Check C:\Windows\System32\drivers\etc\hosts (Windows) or /etc/hosts (macOS/Linux). Remove any entries for the affected domain.
Fix 5: Restart Your Router
Your router caches DNS too. Power cycle your router: unplug for 30 seconds, plug back in, wait for full restart. This clears the router’s DNS cache and forces it to fetch fresh records from your ISP. If you have custom DNS set on your router, verify those addresses are still valid.
Fix 6: Reset Network Configuration
For persistent NXDOMAIN errors across multiple domains, reset your entire network stack. Open Command Prompt as Admin: “netsh winsock reset” then “netsh int ip reset” then “ipconfig /release” then “ipconfig /renew.” Restart your computer. This resolves issues caused by corrupted network adapter settings or VPN remnants.
Frequently Asked Questions
Does DNS_PROBE_FINISHED_NXDOMAIN mean the website is gone?
Not necessarily. NXDOMAIN means your DNS server reports the domain does not exist, but your DNS data may be stale. The domain may have recently migrated to new nameservers that have not propagated to your DNS resolver yet. Change to Google DNS (8.8.8.8) and try again. If it still fails, the domain may genuinely be expired or unregistered.
Why does this error only appear on one device?
Each device has its own DNS cache and DNS settings. If the error appears on one device but not another on the same network, the issue is the device’s DNS cache or hosts file, not the network or domain itself. Flush the DNS cache on the affected device to resolve it.
Can malware cause DNS_PROBE_FINISHED_NXDOMAIN?
Yes. DNS-hijacking malware modifies your DNS settings or hosts file to redirect or block domains. If you see NXDOMAIN for known-good domains (google.com, facebook.com), run a full antivirus scan immediately. After cleaning, reset your DNS to automatic or set it to Google/Cloudflare DNS manually.
