Chrome DNS_PROBE_FINISHED_NXDOMAIN – What It Means and How to Fix It

DNS_PROBE_FINISHED_NXDOMAIN in Chrome means the domain name doesn't exist or can't be found by DNS. Here's what causes it and how to fix it quickly.

Does this happen on one site or all?

One specific domain

The domain doesn't exist, has expired, or your DNS hasn't updated after a recent change.

Next step: In Command Prompt, run: nslookup thatdomain.com — if it fails there too, the domain itself is the problem. Try Google's DNS as a test: nslookup thatdomain.com 8.8.8.8

Most or all websites

Your DNS server has failed or is unreachable.

Next step: Switch to Google Public DNS: Control Panel → Network → Adapter Settings → Properties → IPv4 → set Preferred DNS to 8.8.8.8 and Alternate to 8.8.4.4.

A site I visited recently that now fails

The site's DNS record changed and your cache has the old (now invalid) record.

Next step: Open Command Prompt as administrator and run: ipconfig /flushdns — then try the site again. This forces Chrome to look up the current DNS record.

Frequently asked questions

Is DNS_PROBE_FINISHED_NXDOMAIN a Chrome problem or a website problem?
It can be either. 'NXDOMAIN' means Chrome got a firm 'this domain does not exist' reply from your DNS server. If only one site shows it, that domain is likely expired or mistyped. If many sites show it, your DNS server itself has a problem.
Can I fix DNS_PROBE_FINISHED_NXDOMAIN without contacting my ISP?
Usually yes. The fastest fix is switching to a free public DNS: open your network adapter settings, change the DNS to 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare), and retry. Also try running ipconfig /flushdns in Command Prompt first.
Will clearing my DNS cache delete anything important?
No. The DNS cache is just a temporary lookup table that maps domain names to IP addresses. Flushing it forces your PC to do a fresh lookup — it does not delete files, passwords, or browsing history.
Upload your screenshot for a specific explanation →