DNS_PROBE_FINISHED_NXDOMAIN Fix on Windows

First ask: is the domain really missing, or is only this PC failing to resolve it?

Test	What it tells you
Only one website fails; other sites load	The domain, its DNS records, local hosts/filtering or a resolver cache is more likely than general internet failure.
Many unrelated sites fail with DNS errors	Check the configured DNS resolver, VPN/proxy/filtering and network connection.
The same domain fails on another network/device	The problem may be the domain's DNS rather than this Windows PC.
`nslookup example.com` returns “Non-existent domain”	The DNS server is returning NXDOMAIN for that name; verify the spelling/domain before resetting Windows.

What DNS_PROBE_FINISHED_NXDOMAIN actually means

Chrome shows this error when DNS name resolution finishes with a result that says the requested hostname does not exist. That can be a genuine domain problem, a misspelled hostname, a stale negative cache entry, a DNS resolver issue, or local filtering. It does not automatically mean your Wi-Fi hardware is broken.

Diagnose before resetting the network

1Check the exact address and a second site

Retype the domain manually. If only one site fails, try the same domain from another device or mobile data. If the domain is genuinely unavailable everywhere, changing your Windows network stack will not repair the website's DNS.

2Ask DNS directly

nslookup example.com

Replace example.com with the failing hostname. If a public site such as bing.com resolves but the failing name returns NXDOMAIN, keep the investigation focused on that name, cache, resolver or filtering.

3Flush the Windows DNS client cache

ipconfig /flushdns

Microsoft documents this as a way to discard cached DNS entries, including negative responses, during DNS troubleshooting. Then close and reopen the browser and test the exact hostname again.

If many sites fail

Check whether a VPN, proxy, security product, parental-control filter or corporate DNS policy is intercepting name resolution.
Open your adapter's DNS settings and confirm you are using the intended automatic or manual DNS servers. Do not randomly replace a managed corporate DNS configuration.
Run ipconfig /all to see which DNS servers the active adapter is using.
Test nslookup bing.com. If that also fails, note the DNS server shown by nslookup.
If the router supplies DNS automatically, restarting the router can refresh an upstream resolver problem. If other devices on the same network work, keep the focus on this PC instead.

Check the hosts file only when the symptom fits

If one specific domain resolves incorrectly only on this PC, inspect C:\Windows\System32\drivers\etc\hosts for an entry that intentionally overrides that hostname. Do not delete unrelated lines or replace the file with a download from the internet.

Do not stack “network reset” commands just because Chrome says NXDOMAIN

ipconfig /release, ipconfig /renew, Winsock resets and full Network reset change different layers. Use them only when the evidence shows a broader DHCP/socket/network problem. For a single NXDOMAIN result, spelling, domain status, resolver response and DNS cache are higher-value checks.

Verify the repair

nslookup returns an address or valid DNS answer for the hostname.
The same exact URL loads after reopening the browser.
Other unrelated sites still resolve normally.
The problem does not immediately return after a restart or reconnect.

Frequently asked questions

Does DNS_PROBE_FINISHED_NXDOMAIN mean the website is down?

Not always. DNS may genuinely say the hostname does not exist, but a stale local cache, wrong resolver, VPN/filter or hosts-file override can produce the same symptom on one device.

Is ipconfig /flushdns safe?

It clears the Windows DNS client resolver cache so names are queried again. Microsoft documents it specifically for DNS troubleshooting.

Should I change my DNS server immediately?

No. First compare one site versus many sites, test nslookup, and check whether another device/network resolves the same hostname. Change DNS only when the evidence points to the resolver.

Sources and review notes

Troubleshooting order was reviewed against Microsoft Learn: ipconfig /flushdns · Microsoft Learn: Troubleshooting DNS clients. Hardware, driver and menu names can vary by PC, accessory and Windows build.