How to Fix DNS_PROBE_FINISHED_NXDOMAIN

DNS_PROBE_FINISHED_NXDOMAIN is the error Chrome shows when it asks the Domain Name System for a website's address and gets back "no such name." NXDOMAIN is short for "non-existent domain," and it means the resolver looked for the hostname you typed and found no matching record. Other browsers phrase it differently, such as Firefox's "We can't connect to the server" or a plain "server not found," but the underlying answer is the same: the name did not resolve to an IP address. The first thing to determine is whether the domain genuinely has no DNS record, or whether something between you and the real answer is broken. A quick DNS Lookup lookup against the hostname tells you immediately which case you are in.

Every time you visit a site, your device asks a DNS resolver to translate a human-friendly name like example.com into the numeric IP address a computer can connect to. The resolver walks the DNS hierarchy, from the root servers to the domain's authoritative nameservers, looking for an A record (IPv4) or AAAA record (IPv6). When the authoritative server replies that the name does not exist, that authoritative "this name has no records" answer is NXDOMAIN. Your browser cannot connect to an address it was never given, so it stops and shows the error.

This is different from a server being down or refusing the connection. With NXDOMAIN there is no address to even attempt; the lookup itself failed. That distinction matters because it points you toward DNS, registration, and caching as the likely culprits rather than the web server or your firewall.

The single most common cause is a simple typo, such as exmaple.com or a .cm instead of .com. Beyond that, the usual suspects fall into two groups. On the visitor side: a stale local DNS cache holding an old "does not exist" answer, a misconfigured or unreachable resolver, a VPN or proxy intercepting DNS, or a stray entry in your hosts file pointing the name nowhere. A flaky home router that has cached bad data is also surprisingly common.

On the domain side: the domain has expired or was never registered, the DNS zone has no A or AAAA record for the hostname (for example, the apex works but www does not, or a subdomain was never created), the nameservers are misconfigured or not responding, or a recent DNS change simply has not propagated yet. A WHOIS check with the WHOIS Lookup tool quickly rules expiry in or out, and a Domain Info / WHOIS lookup shows the nameservers and records in one place.

Before changing anything, find out how widespread the failure is, because that single fact tells you whether to fix your device or fix the domain. The fastest test is to run the DNS Lookup lookup on the hostname from this site: it queries public resolvers rather than your local machine, so it shows what the rest of the internet sees.

If the DNS Lookup tool returns valid A or AAAA records but your browser still fails, the problem is local to you, meaning your cache, resolver, VPN, hosts file, or router. If the lookup also returns NXDOMAIN, the domain really has no working record right now, and the fix belongs to whoever owns the domain. Confirming you are online at all (any other site loads, your What Is My IP result is normal) rules out a dead connection masquerading as a DNS error.

Start by clearing the cached bad answer. On Windows, open Command Prompt and run ipconfig /flushdns. On macOS, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder in Terminal. Chrome keeps its own internal DNS cache too, which you can clear by visiting chrome://net-internals/#dns and clicking "Clear host cache," then restarting the browser. A great deal of "it works everywhere but here" NXDOMAIN cases disappear after a flush.

If flushing does not help, change your DNS resolver. Your ISP's resolver can hold stale or filtered data, so switch your device or router to a reliable public resolver such as Cloudflare's 1.1.1.1 or Google's 8.8.8.8 and 8.8.4.4, then retry. While you are at it, power-cycle your router for thirty seconds to clear any bad data it cached, and temporarily disconnect any VPN or proxy, since these reroute DNS and can return NXDOMAIN for names they cannot resolve.

Finally, check your hosts file for a bad manual entry. It lives at C:\Windows\System32\drivers\etc\hosts on Windows and /etc/hosts on macOS and Linux. Remove or correct any line referencing the failing domain, save, and flush the cache again. After each change, re-test in a fresh browser tab; if the DNS Lookup tool already shows good records, one of these local fixes will resolve it.

If the DNS Lookup lookup returns NXDOMAIN for everyone, work through the chain in order. First, confirm the domain is registered and not expired, since an expired domain stops resolving entirely; the WHOIS Lookup tool shows the registration and expiry dates, and renewing immediately is the fix if it has lapsed. Then confirm the domain's nameservers are correct at the registrar and that they actually answer, which the Domain Info / WHOIS tool surfaces alongside the zone's records.

Next, verify the specific record exists. NXDOMAIN often hits one hostname and not another, for example the apex example.com resolves but the www subdomain has no record, or a newly added subdomain was never given an A, AAAA, or CNAME entry. Add the missing record in your DNS provider's dashboard, pointing it at the correct IP or target, and save.

If you just made a change, the cause may simply be propagation: DNS edits take time to reach resolvers worldwide, bounded by the record's TTL. Use the DNS Propagation checker to watch the new record appear across global locations; once most nodes show the correct answer, the NXDOMAIN errors will clear on their own as old cached "does not exist" answers expire.

Most recurring NXDOMAIN incidents trace back to two avoidable things: a forgotten domain renewal and an incomplete DNS change. Enable auto-renew at your registrar and keep the contact email current so expiry notices actually reach you, then verify periodically with the WHOIS Lookup tool that the expiry date is comfortably in the future. When you migrate hosts or restructure your zone, change records during low-traffic windows and lower the TTL a day in advance so updates propagate faster.

After any DNS change, make verification a habit: confirm the record resolves with the DNS Lookup tool and watch it roll out globally with the DNS Propagation checker before you announce the change or assume it is live. A two-minute check at the source prevents the kind of half-finished edit that leaves some visitors staring at DNS_PROBE_FINISHED_NXDOMAIN.

Does NXDOMAIN mean the website is down? No. It means the name did not resolve to an address at all, so the browser never reached a server. A site that is down but has valid DNS produces a connection or timeout error instead, not NXDOMAIN.

I can open the site on my phone but not my laptop. Why? That is the classic "just me" pattern, where one device has a stale cache, a bad resolver, a VPN, or a hosts-file entry. Flush the DNS cache, switch resolvers, and check the hosts file on the failing device.

I added a DNS record but still get the error. What now? It is almost certainly propagation or a cached negative answer. Confirm the record is correct with the DNS Lookup tool, watch it spread with the DNS Propagation checker, and flush your local cache before retesting.

How long until a DNS fix takes effect? It depends on the record's TTL and any cached negative responses, ranging from a few minutes to a day. Lowering the TTL ahead of a planned change shortens the wait considerably.