DNS_PROBE_FINISHED_NXDOMAIN: What It Means and How to Fix It

DNS_PROBE_FINISHED_NXDOMAIN is shown by Chrome, Edge and other Chromium browsers when a DNS lookup came back with NXDOMAIN, meaning "this domain name does not exist." The page says "This site can't be reached" and "server IP address could not be found." Firefox shows its "Hmm. We're having trouble finding that site" page instead, and Safari says it cannot find the server.

NXDOMAIN is an authoritative answer, not a timeout. Some resolver somewhere asked the DNS tree and was told that no such name exists. That narrows the problem to three things: you typed the wrong name, the domain's DNS genuinely lacks the record, or a cache is serving a stale "does not exist."

Check what the DNS says

dig www.example.com A

Look for the status line in the header:

• status: NXDOMAIN confirms the resolver you asked claims the name does not exist.
• status: NOERROR with an ANSWER: 0 section means the name exists but has no record of that type; the error will be different.
• status: SERVFAIL is a server failure, not NXDOMAIN, and points to DNSSEC or nameserver trouble.

Then ask a different resolver:

dig www.example.com A @8.8.8.8
dig www.example.com A @1.1.1.1

NXDOMAIN everywhere means the problem is in the domain's DNS. NXDOMAIN only on your default resolver means a cache or filtering rule on your side.

If you are a visitor

1. Look for a typo. Check the spelling and TLD. Remove stray characters from copy-pasted links.
2. Try the bare domain. If example.com works but www.example.com does not, the site has no www record. Use the address that works and tell the owner.
3. Flush caches. On Windows, ipconfig /flushdns. On macOS, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. In Chrome, clear the host cache at chrome://net-internals/#dns.
4. Change resolver. Use another public DNS for a test; a family-filter or malware-blocking resolver may return NXDOMAIN on purpose for blocked names.
5. Review the hosts file and security software. Some blockers return NXDOMAIN for listed domains.
6. Wait if the domain is brand new. A domain registered or changed within the last hours may not have propagated, and a resolver that already asked may cache the negative answer for a while.

If you own the site

1. The record was never created or was deleted

The most common cause on a fresh site: the A or CNAME record for www or a subdomain does not exist at the DNS host. Create it and verify at the authoritative server:

dig +short NS example.com
dig www.example.com A @ns1.example-dns.com

Check the DNS zone, not only the website builder's "connected" status.

2. You edited DNS at the wrong provider

If you changed nameservers, the zone you edit must be the one the registrar delegates to. Editing the old provider's zone has no effect. Compare registry delegation with the Nameserver Lookup and use the DNS Checker to see what the world resolves.

3. The domain expired or was suspended

When registration lapses, the registry or registrar may remove the delegation, and every name under it returns NXDOMAIN. Check expiry and status codes in the WHOIS Lookup and Domain Age Checker. Look for hold statuses. Renew immediately, then read expiry grace and redemption if you are past the date. Prevent a repeat with domain expiry alerts.

4. Nameserver delegation is wrong

If the registrar lists nameservers that are not authoritative for the zone, resolvers get a lame delegation and may produce NXDOMAIN or failure. Make sure each listed nameserver actually has the zone loaded.

5. Wildcard and subdomain confusion

A missing record under a zone with no wildcard returns NXDOMAIN for that exact name. If a subdomain used to work, compare past records with DNS History to see what was removed. Also check for typos in CNAME targets: a CNAME to a nonexistent hostname causes a failure when the target name is looked up.

6. Negative caching delays recovery

After you add a missing record, resolvers that already saw NXDOMAIN may keep that result for the duration of the zone's negative TTL, taken from the SOA record's minimum field:

dig example.com SOA +short

The last number is commonly several minutes to several hours. During that period some users still see the error. Details are in how long DNS propagation takes.

Confirm the fix

1. Run the DNS Checker on the exact hostname that failed. Every resolver should return the intended IP or CNAME.
2. Re-run dig against your authoritative nameserver directly to verify it serves the record.
3. Add an uptime monitor with DNS-change alerts; it alerts you if a record goes missing again.

Next steps

• Understand the pieces in DNS explained for website owners.
• Compare the broader message in ERR_NAME_NOT_RESOLVED.
• If the whole internet seems down, see DNS_PROBE_FINISHED_NO_INTERNET.
• Use the DNS records cheat sheet to create the right record type.

FAQ

Does NXDOMAIN mean the domain is not registered?

Not necessarily. It means the resolver found no such name in DNS. The domain may be registered but lack that record, or its delegation may be broken.

Why does it work on my phone but not on my laptop?

They are using different resolvers or caches. Flush the laptop's DNS cache and change its resolver to test.

How long until a newly added record works everywhere?

Positive caches follow the record's TTL. A cached negative answer follows the SOA negative TTL. Most users see changes within minutes to a few hours.

Can my ISP cause NXDOMAIN?

Some ISPs redirect or block names at their resolver. Switching to a different resolver usually reveals whether that is the cause.

This page is general information written by our editorial team and updated when documentation changes. Servers and providers differ, so test changes safely first. See our editorial policy and disclaimer.