DNS_PROBE_FINISHED_NXDOMAIN Fix

Short answer. DNS_PROBE_FINISHED_NXDOMAIN in Chrome means the DNS resolver could not find an IP address for the domain (NXDOMAIN = "non-existent domain"). The usual causes are a typo in the URL, a missing A record, a stale DNS cache, or a failing ISP resolver. Start by checking the spelling, then flush your DNS cache and temporarily switch your resolver to 1.1.1.1 or 8.8.8.8.

What NXDOMAIN means

NXDOMAIN (Non-Existent Domain) is a DNS response code that says: "no such domain exists in this zone." Your browser tried to turn the hostname into an IP, but the authoritative DNS server returned an empty answer. This is not a connection failure with the site — the request never even reached the server.

NXDOMAIN is a name-resolution problem, not a server-availability one. The site can be perfectly healthy, but if DNS returns no IP, the browser has nowhere to connect.

60-second triage

1. Check the address for typos: exmaple.com instead of example.com is the single most common cause.
2. Open the site on your phone over mobile data. Works? The problem is your network/resolver, not the domain's DNS records.
3. Run dig example.com in a terminal and see whether you get an IP back.
4. Try another browser and an incognito window to rule out extensions.

Check DNS with dig and nslookup

The dig command shows exactly what the resolver returns:

dig example.com

;; ANSWER SECTION:
example.com.    300    IN    A    93.184.216.34

# If you see "status: NXDOMAIN" the record is missing:
dig example.com +short        # empty = domain does not resolve

# Query a specific resolver (Cloudflare):
dig @1.1.1.1 example.com +short

# Windows / alternative:
nslookup example.com
nslookup example.com 8.8.8.8

If dig @1.1.1.1 returns an IP but your system resolver does not, the problem is your local cache or your ISP's DNS.

Flush the DNS cache

System	Command	Effect
Windows	ipconfig /flushdns	Clears the Windows resolver cache
macOS	sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder	Resets mDNSResponder
Linux (systemd)	sudo systemd-resolve --flush-caches	Clears systemd-resolved
Chrome	chrome://net-internals/#dns → Clear host cache	Resets the browser's internal DNS cache

Switch your DNS resolver

If your ISP resolver is failing, switch to a public one:

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

On Windows: Network settings → Adapter properties → IPv4 → set DNS manually. On macOS: System Settings → Network → DNS.

If you own the domain

NXDOMAIN from the owner's side usually means the A record is not configured, or the domain is expired or delegated incorrectly. Check:

• An A record exists for the apex and for www (check your DNS records).
• The NS servers match between registrar and zone.
• The domain registration has not lapsed.
• DNS propagation benchmark has completed after a record change (up to 48 hours).

After changing DNS records, the old NXDOMAIN may stay cached at some resolvers until the TTL expires. Verify from several locations, not just your own machine.

How enterno.io helps

The enterno.io DNS checker shows every record (A, AAAA, MX, NS, TXT, CNAME запись, SOA) and resolves the domain server-side, which removes your local cache from the equation. Uptime monitoring with a DNS check type every minute catches a record disappearing before visitors notice and alerts you via Telegram, Slack, email, or webhook. enterno.io diagnoses and warns — the DNS record itself is fixed by the owner at the registrar.

FAQ

Is this my computer or the website?

Open the site over mobile data. If it works there, the issue is local (cache, resolver). If NXDOMAIN appears everywhere, the domain's DNS records are the problem.

Does a VPN help?

Sometimes: a VPN uses its own resolver. If the site loads through a VPN, your ISP DNS is returning NXDOMAIN — switch to 1.1.1.1.

How long after changing an A record?

Until the previous record's TTL expires plus propagation time — typically minutes to 48 hours. Lower the TTL in advance to speed it up.

Why does dig return an IP but the browser still errors?

The browser keeps its own DNS cache. Clear it at chrome://net-internals/#dns and restart the browser.

Next step: Check your domain's DNS records server-side to confirm whether the A record is being served. See also Domain not resolving: what to do and set up DNS monitoring.