DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It

DNS_PROBE_FINISHED_NXDOMAIN is a Chrome error that means the domain you tried to reach returned an NXDOMAIN (Non-Existent Domain) response, the DNS system couldn't find any records for it. Other browsers display the same underlying problem as "Server Not Found" (Firefox) or "Hmm, can't reach this page" (Edge). The problem is always DNS, but the cause could be on your machine, your network, or the domain itself.

What NXDOMAIN Actually Means

NXDOMAIN is a DNS response code meaning "this domain does not exist." It's a definitive response from the DNS system, the query reached an authoritative nameserver and the answer was "we have no records for this domain." This is distinct from a timeout (no response at all) or SERVFAIL (the server failed to look it up).

The error can come from: the domain genuinely not existing, your local cache holding an NXDOMAIN response from a failed previous lookup, a resolver returning NXDOMAIN due to filtering or a misconfiguration, or a DNS record that hasn't propagated yet.

Cause 1: Typo in the Domain Name

Check the URL carefully. Extra characters, missing hyphens, wrong TLD (.net instead of .com), or an incorrectly copied link will all return NXDOMAIN because the mistyped domain genuinely doesn't exist in DNS. Double-check the exact URL before troubleshooting further.

Cause 2: The Domain Has Expired or Doesn't Exist

If the domain registration has lapsed, it will be removed from DNS and return NXDOMAIN until it's renewed. You can verify the registration status by doing a WHOIS lookup at ICANN Lookup. If the domain shows as expired or not found, it needs to be renewed by the owner.

To quickly test whether the domain is registered at all:

nslookup -type=NS yourdomain.com 8.8.8.8

If this returns nameservers, the domain is registered and delegated. If it returns NXDOMAIN, the domain doesn't exist in the DNS system.

Cause 3: DNS Propagation In Progress

If you've recently set up a new domain, changed nameservers, or added DNS records, the change may not have propagated to your resolver yet. Different resolvers around the world update at different times based on cached TTL values.

To check whether the issue is propagation or something else, query Google's resolver directly:

nslookup yourdomain.com 8.8.8.8

If Google's resolver finds the domain, the DNS configuration is correct and your local resolver just hasn't caught up yet. Also use our DNS Propagation Checker to see the global propagation status from dozens of locations at once.

Cause 4: Your Local DNS Cache Has a Stale NXDOMAIN Response

DNS resolvers also cache negative responses (NXDOMAIN). If a lookup failed in the past, perhaps during a brief period when DNS records weren't configured, your system may have cached that failure and will keep returning NXDOMAIN until the negative cache entry expires.

Flush your local DNS cache:

• Windows: ipconfig /flushdns (run Command Prompt as Administrator)
• macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
• Linux (systemd): sudo systemd-resolve --flush-caches

Also clear Chrome's internal cache: navigate to chrome://net-internals/#dns and click Clear host cache.

Cause 5: Your DNS Resolver Is Having Problems

Your configured DNS server (usually your ISP's) may be experiencing issues, blocking certain domains, or returning incorrect responses. Switch to a public resolver temporarily to test:

• Google: 8.8.8.8 and 8.8.4.4
• Cloudflare: 1.1.1.1 and 1.0.0.1

On Windows, change DNS in Settings > Network & Internet > Change adapter options > right-click your connection > Properties > Internet Protocol Version 4 > Use the following DNS server addresses. On Mac: System Settings > Network > select connection > Details > DNS.

Cause 6: Missing DNS Records on the Hosting Side

If you're seeing this error for your own domain after a migration, the domain may not be fully configured at the hosting level. Common scenarios:

• The domain was added to HostBible but the DNS zone hasn't been created yet.
• The nameservers were changed to HostBible's but no A record was created for the domain.
• The domain isn't assigned to your hosting package.

Log in to your HostBible control panel and confirm the domain is assigned to your hosting package and that an A record exists pointing to your server's IP. You can also verify by querying the authoritative nameserver directly:

dig @ns1.hosted-server.net yourdomain.com A +short

If this returns an IP address, the record is there and propagation is simply in progress. If it returns NXDOMAIN, the record needs to be added.

Quick Diagnostic Checklist

1. Check the URL for typos.
2. Try loading the site in a different browser.
3. Try from a different network (mobile data instead of your home Wi-Fi).
4. Run nslookup yourdomain.com 8.8.8.8: if Google's resolver finds it, the problem is local.
5. Flush your system DNS cache and Chrome's internal DNS cache.
6. Switch your DNS server to 8.8.8.8 or 1.1.1.1 temporarily.
7. If it's your own domain: verify DNS records in your hosting control panel.
8. Check global propagation status with our DNS Propagation Checker.