How to Fix DNS_PROBE_FINISHED_NXDOMAIN (2026)

What DNS_PROBE_FINISHED_NXDOMAIN Actually Means

NXDOMAIN is a response code defined in the DNS specification. It means the queried name does not exist at all, which is stricter than "no record of the type you asked for." RFC 8020 tightened this further: an NXDOMAIN for a name implies nothing exists beneath it either.

The Chromium part matters more than most articles admit. When a navigation fails to resolve, Chromium does not simply print the failure. It launches a separate DNS probe that requests A records for a known-good hostname, and it runs that probe against your system DNS configuration and a public one. The error string you see reports the probe's verdict, not the original lookup.

That verdict is documented in Chromium's error page source. DNS_PROBE_FINISHED_NXDOMAIN is defined as the case where the DNS servers are working fine, so the domain must not exist. A broken resolver returns DNS_PROBE_FINISHED_BAD_CONFIG, and a dead connection returns DNS_PROBE_FINISHED_NO_INTERNET. Seeing the NXDOMAIN variant is therefore evidence that your DNS setup passed its own test.

One correction worth making: this error is not Chrome-only. It comes from Chromium, so Edge, Brave, Opera, and Vivaldi all produce it. Firefox and Safari show their own wording for the same underlying DNS failure.

Also Read: UDP Proxy Explained

How to Fix DNS_PROBE_FINISHED_NXDOMAIN

Work in the order the error implies. The domain is the prime suspect, not your network.

1. Retype the address carefully and confirm the domain is still registered and unexpired.
2. Query it directly with nslookup example.com or dig example.com +short. An NXDOMAIN reply from a public resolver confirms the record is missing at the source.
3. Open your hosts file and remove or comment out any line pointing that domain somewhere invalid. Local entries silently override DNS.
4. Flush the cache only if a record was recently created or repaired, since stale negative answers are cached too. Use ipconfig /flushdns on Windows, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS, and sudo resolvectl flush-caches on systemd Linux.
5. Reset the network stack if the problem is machine-wide. The correct command is netsh winsock reset, documented under netsh. Several popular guides misspell it as "winstock," which fails silently.

If You Own the Domain

A missing A or CNAME record produces a real NXDOMAIN, and so does a lapsed registration. Confirm the nameservers at your registrar match your DNS provider, then verify the zone actually contains the record. Broken DNSSEC usually surfaces as SERVFAIL rather than NXDOMAIN, so check the signing chain separately.

Why the Error Shows Up When a Proxy Is Configured

This is where the standard advice breaks down. When Chromium routes a request through an HTTP proxy, it sends the hostname inside the CONNECT request and the proxy resolves it. With SOCKS5 and remote DNS enabled, resolution also happens at the proxy. Your local resolver is not involved, so flushing it changes nothing.

If you see DNS_PROBE_FINISHED_NXDOMAIN while a proxy is active, the browser usually fell back to a direct connection, or the proxy rule never applied. Test the endpoint outside the browser before touching any network settings. Clean, correctly formatted credentials matter here, and the proxy formatter removes one common source of silent failures.

Resolver behavior also varies by proxy type. Residential proxies exit through consumer ISP resolvers, which sometimes return NXDOMAIN for domains that resolve fine elsewhere because of ISP-level filtering. Datacenter proxies and ISP proxies usually sit on stable upstream resolvers, so an NXDOMAIN from those is far more likely to be genuine.

Also Read: How to Use a Proxy Server on Any Device

FAQ Section

Does this error mean my internet is down?

No. The probe that produced this code required working DNS to complete. A dead connection returns DNS_PROBE_FINISHED_NO_INTERNET instead.

Will changing to a public DNS server fix it?

Rarely, for this specific code. The probe already tested a public resolver alongside yours. Switching resolvers helps with BAD_CONFIG, not NXDOMAIN.

Why do I sometimes see ERR_NAME_NOT_RESOLVED instead?

Because the probe did not run. Chromium skips it when the navigation error diagnostic setting is disabled, and reports the raw resolution failure instead.

Is it a virus?

No. It is a name resolution result, not malware. Check the hosts file if you suspect something modified your system, since that is the usual tampering point.

Final Thoughts

DNS_PROBE_FINISHED_NXDOMAIN is more specific than the guides suggest. Chromium has already ruled out your resolver by the time it prints this code, which is why cache flushing so often changes nothing. Start with the domain itself, then your hosts file, then the path your requests actually take. When a proxy sits in that path, resolution moves to the proxy and local fixes stop applying, so verify the endpoint independently before assuming your machine is at fault.