Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome

DNS_PROBE_FINISHED_NXDOMAIN is one of the more informative Chrome error codes — if you know how to read it. NXDOMAIN is DNS terminology for “non-existent domain.” Chrome tried to look up the IP address for the website you’re visiting, got a definitive answer back from the DNS server, and that answer was: this domain doesn’t exist. So the question isn’t “what went wrong with DNS?” but rather “why does DNS think this domain doesn’t exist?” We go deeper on the whole subject in our Google Chrome Errors.

The answers range from the trivially obvious (you typed the URL wrong) to the genuinely technical (your ISP’s DNS servers have a propagation delay, or a local software is blocking the domain). This guide works through all of them, starting with the checks that take thirty seconds.

Start Here: The URL Check That Nobody Wants to Do

I’ll say it plainly: the first time I ever saw DNS_PROBE_FINISHED_NXDOMAIN, I spent twenty minutes troubleshooting DNS settings before realising I’d typed “gogle.com” instead of “google.com.” NXDOMAIN literally means the domain doesn’t exist in DNS — and if you’ve made a typo, it genuinely doesn’t.

Read the URL in the address bar carefully before anything else. Common typos that produce DNS_PROBE_FINISHED_NXDOMAIN: transposed letters, extra dots, missing letters, .net instead of .com, .co instead of .com. If you’re clicking a link rather than typing, right-click the link and “Copy link address” to inspect it in a text editor before visiting — some links contain invisible characters or encoding errors that Chrome can’t resolve.

Also worth checking: if this is a site you visit regularly that has been working fine until today, consider that the domain may have expired. Domain registrations lapse, and when they do, the DNS records disappear and every DNS server returns NXDOMAIN. A quick WHOIS lookup on the domain will show its registration status. If it expired recently and the site is legitimate, the owner may just need to renew — nothing you can fix on your end.

DNS_PROBE_FINISHED_NXDOMAIN Fix 1: Flush the DNS Cache

Even when a domain genuinely exists and the URL is correct, Chrome can show DNS_PROBE_FINISHED_NXDOMAIN because it — or Windows — has cached a failed lookup from a period when the domain didn’t resolve. This happens more often than you’d think. Domains briefly expire and get renewed. DNS records get changed. Sites migrate to new servers. Any of these can leave a stale “doesn’t exist” entry in the DNS cache that persists long after the actual problem has been fixed.

1. Open Command Prompt as administrator (search “cmd”, right-click, Run as administrator)
2. Run: ipconfig /flushdns
3. Wait for “Successfully flushed the DNS Resolver Cache”
4. In Chrome, open chrome://net-internals/#dns → click Clear host cache
5. Reload the page

New websites sometimes take 24–48 hours for DNS changes to propagate globally. If DNS_PROBE_FINISHED_NXDOMAIN appears on a domain that was very recently registered, or that recently moved to a new registrar, the fix may just be waiting. Some parts of the global DNS infrastructure cache “this domain doesn’t exist” results for the TTL period specified by the zone, and no amount of flushing on your end can override what remote caching servers are holding.

DNS_PROBE_FINISHED_NXDOMAIN Fix 2: Switch DNS Server

ISP DNS servers occasionally lag on propagating DNS updates, or they cache NXDOMAIN results longer than they should. Switching to a public DNS resolver — Cloudflare’s 1.1.1.1 is the fastest for most locations — bypasses whatever your ISP’s servers are doing and often resolves DNS_PROBE_FINISHED_NXDOMAIN on domains that actually exist but your ISP hasn’t caught up with yet.

This was the fix when my ISP had a DNS configuration issue — switching to Cloudflare brought every affected site back instantly while my ISP’s resolver was still returning NXDOMAIN incorrectly.

1. Settings → Network and internet → Wi-Fi or Ethernet → click your connection
2. DNS server assignment → Edit → Manual
3. Enable IPv4 — Preferred DNS: 1.1.1.1, Alternate DNS: 8.8.8.8
4. Save → reload the failing page

If switching DNS resolves the issue, you’ve confirmed your ISP’s DNS servers were the problem. Leaving the switch in place permanently is a reasonable choice — Cloudflare’s 1.1.1.1 is consistently faster and more reliable than most ISP-provided DNS resolvers and has a strong privacy policy around query logging.

DNS_PROBE_FINISHED_NXDOMAIN Fix 3: Check for VPN and Antivirus DNS Interference

Some VPN applications install their own DNS resolver and route all DNS queries through their servers. When this resolver has connectivity issues, or when it blocks specific domains, DNS_PROBE_FINISHED_NXDOMAIN appears for those domains regardless of what DNS server you’ve configured in Windows. The same applies to antivirus products with DNS protection features — they sometimes block domains that have been flagged (correctly or incorrectly) as malicious, returning NXDOMAIN as the block method.

The fastest test: disconnect any active VPN completely — don’t just toggle the tunnel, fully quit the application. Then test the site. If it loads, the VPN’s DNS resolver was causing the issue. You can usually fix this by going into the VPN’s settings and finding a “Use system DNS” or “Don’t manage DNS” option that lets Windows handle DNS while the VPN handles the tunnel.

For antivirus, look for Web Shield, Web Protection, DNS Protection, or Safe Browsing settings and temporarily disable them to test. If the site loads with those disabled, check whether the domain has been incorrectly flagged and submit a false-positive report to the antivirus vendor. Most have a web form for this, and legitimate sites get cleared from block lists within a day or two.

DNS_PROBE_FINISHED_NXDOMAIN Fix 4: Restart the DNS Client Service

The Windows DNS Client service manages DNS resolution for the entire system. When this service stops — after certain Windows updates, after system events, or occasionally after resource exhaustion — every DNS lookup fails with NXDOMAIN because the resolver isn’t processing requests. This is a less common cause but worth checking when DNS_PROBE_FINISHED_NXDOMAIN appears suddenly across all browsers, not just Chrome.

1. Press Windows + R, type services.msc, press Enter
2. Scroll to DNS Client
3. Right-click → Restart
4. If Restart is greyed out: right-click → Properties → confirm Startup type is Automatic → click Start
5. Test Chrome after the service restarts

If DNS Client is showing as Stopped, restarting it will almost certainly fix DNS_PROBE_FINISHED_NXDOMAIN across all browsers immediately. Note that on some versions of Windows 11, the DNS Client service cannot be manually restarted through services.msc because it’s set to run as a protected service — in those cases, a PC restart achieves the same result.

DNS_PROBE_FINISHED_NXDOMAIN Fix 5: Check the Windows Hosts File

The hosts file can block specific domains entirely by mapping them to 127.0.0.1 (localhost) or a non-existent IP. Chrome returns DNS_PROBE_FINISHED_NXDOMAIN for any domain blocked this way. Malware commonly uses this method to block security sites. Parental control software uses it to block categories of sites. Some network management tools also write to the hosts file without much notice to the user.

1. Open Notepad as administrator
2. File → Open → navigate to C:WindowsSystem32driversetc
3. Change the file type dropdown to All Files
4. Open the file named hosts
5. Look for any line containing the domain that’s showing DNS_PROBE_FINISHED_NXDOMAIN
6. Delete any entries that shouldn’t be there
7. File → Save, then reload in Chrome

A legitimate hosts file on a standard Windows installation should have very few entries — mainly a localhost mapping and a few other system entries. If you see dozens of entries with third-party domains mapped to 127.0.0.1, something has been actively managing that file and blocking domains. A quick web search for the software name listed in any comments at the top of the file usually identifies what’s responsible.

DNS_PROBE_FINISHED_NXDOMAIN Fix 6: Reset Chrome Network Settings

If DNS_PROBE_FINISHED_NXDOMAIN only appears in Chrome while other browsers can reach the same sites, Chrome’s own network configuration has likely diverged from the system settings. Chrome has its own DNS-over-HTTPS settings and a set of network flags that can interfere with standard DNS resolution.

1. In Chrome, go to chrome://flags
2. Click Reset all in the top right
3. Restart Chrome
4. Also check: Settings → Privacy and security → Security → scroll to “Use secure DNS” → try toggling it off if it’s enabled, or switch the provider

DNS-over-HTTPS (the “secure DNS” setting) routes DNS queries through an HTTPS connection to a specific provider. If that provider has issues resolving a specific domain, or if Chrome’s DoH configuration is conflicting with your network’s DNS setup, DNS_PROBE_FINISHED_NXDOMAIN appears only in Chrome. Disabling DoH returns Chrome to using the system DNS resolver and usually resolves the Chrome-specific NXDOMAIN issue immediately.

Our guide on This site can’t be reached covers the broader connection error that wraps DNS_PROBE_FINISHED_NXDOMAIN alongside other error codes and has additional steps for network-level issues. For DNS failures that affect all browsers at once, our DNS server not responding guide goes deeper into Windows-level DNS service troubleshooting. Additional documentation covering DNS-over-HTTPS and enterprise DNS policy settings is available on the Google Chrome support pages.

On corporate networks, DNS_PROBE_FINISHED_NXDOMAIN appearing on specific external sites is sometimes intentional. Corporate DNS servers are often configured to return NXDOMAIN for domains in blocked categories — social media, streaming sites, gambling, and others — as a network-level access control measure. If this is happening on a work machine or a machine connected to a company network (including through a corporate VPN), the DNS_PROBE_FINISHED_NXDOMAIN may be a legitimate access restriction rather than a technical problem. Check with IT before assuming it’s an error that needs fixing.

For home networks, DNS_PROBE_FINISHED_NXDOMAIN on sites that were previously accessible sometimes results from a router DNS setting that has been changed — either by the user, by a family member, or occasionally by a router firmware update that resets DNS to default or changes how the router forwards DNS queries. Check the DNS settings in your router’s administration panel (usually accessible at 192.168.1.1 or 192.168.0.1 in a browser) and verify whether a custom DNS override is configured. Some routers have parental control features built in that block domains at the router level, returning NXDOMAIN to all devices on the network. If DNS_PROBE_FINISHED_NXDOMAIN is appearing on multiple devices in your household simultaneously, the router is the most likely common cause.

Chrome’s DNS prefetching is another factor that can make NXDOMAIN errors appear more persistent than they actually are. Chrome preemptively looks up DNS for links on pages you’re currently viewing, caching those results to speed up navigation. If a prefetch cached an NXDOMAIN result, that cached failure persists until the cache is cleared — even after the underlying DNS issue has been resolved. If you’ve fixed the DNS problem but Chrome is still showing NXDOMAIN on a site, clear Chrome’s internal DNS cache at chrome://net-internals/#dns (Clear host cache) before concluding the fix didn’t work. The prefetch cache is separate from the Windows DNS cache cleared by ipconfig /flushdns, so both need to be cleared to fully flush the cached NXDOMAIN result from Chrome’s memory.

A less obvious cause of DNS_PROBE_FINISHED_NXDOMAIN that appears specifically after switching networks — moving from home Wi-Fi to a mobile hotspot, or from a home network to a public WiFi — is that the new network’s DNS server hasn’t received your request before Chrome times out and falls back to showing NXDOMAIN. Public WiFi networks sometimes have slow or overloaded DNS resolvers that take several seconds to respond, which Chrome interprets as a failed lookup and reports as NXDOMAIN rather than a timeout. If DNS_PROBE_FINISHED_NXDOMAIN appears immediately after switching to a new network and other sites also load slowly or fail, the issue is the network’s DNS performance rather than anything on your machine. Switching to Cloudflare’s 1.1.1.1 as described in Fix 2 bypasses the network’s DNS resolver entirely and should resolve this immediately, since Cloudflare’s servers respond in milliseconds from virtually every location.

Secondary DNS validation is a quick diagnostic step that often reveals the true cause without requiring any changes to your system. Once you have Command Prompt open, run: nslookup domain.com (replacing domain.com with the domain showing DNS_PROBE_FINISHED_NXDOMAIN). If nslookup returns an IP address, DNS resolution is working fine on your system but Chrome isn’t using it correctly — point to Fix 6 (Chrome’s own DNS settings). If nslookup also returns “NXDOMAIN” or “Non-existent domain,” the DNS failure is at the system level, not Chrome-specific — points to Fixes 1 through 5. And if nslookup returns a valid IP but you still can’t reach the site after fixing Chrome, the problem has moved on from DNS to something else — an IP block, a server issue, or an SSL error that was masked by the DNS failure. This diagnostic takes ten seconds and saves you from applying Chrome-specific fixes to a system-level problem, or vice versa. If this sounds familiar, DNS_PROBE_FINISHED_NXDOMAIN is worth a look.