How to Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome (2026)

By /

You type a URL, hit Enter, and Chrome shows you a blank page with the error: DNS_PROBE_FINISHED_NXDOMAIN. Below it, in smaller text: “This site can’t be reached.”

This is one of the most common browser errors on the internet. The good news: it’s almost always fixable in under two minutes, and in most cases the fix requires nothing more than flushing your DNS cache or changing your DNS server.

What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?

Breaking down the error code:

  • DNS: Domain Name System — the system that translates domain names (like google.com) into IP addresses
  • PROBE_FINISHED: Chrome ran a diagnostic probe and completed it
  • NXDOMAIN: “Non-Existent Domain” — the DNS server responded that the domain does not exist

In plain English: your browser asked a DNS server “what’s the IP address for [domain]?” and the server replied “no such domain exists.” This doesn’t necessarily mean the website is down — it means your browser couldn’t find it, which is a different problem.

To understand DNS better, read our guide: What is DNS and how does it work?

Most Likely Causes

  • Typo in the URL (most common)
  • Corrupted DNS cache on your device or router
  • Your ISP’s DNS server is down or slow
  • Your ISP is blocking the domain
  • The website’s DNS records are misconfigured or the domain has expired
  • A VPN or antivirus software intercepting DNS queries incorrectly

Fix 1: Check the URL First

Before anything else, look carefully at the URL. The most common cause of this error is a simple typo: a misspelling, a wrong TLD (.co instead of .com), or an extra character. Try typing the URL from scratch rather than copying it.

If you’re trying to reach a website you previously visited without issues, skip to Fix 2.

Fix 2: Flush Your DNS Cache (Works 80% of the Time)

Your computer stores recent DNS lookups in a local cache. If a cached entry has gone stale or corrupt, your browser will keep getting the wrong answer even if the DNS server has been fixed.

Windows:

  1. Press Win + R, type cmd, press Enter
  2. Type: ipconfig /flushdns and press Enter
  3. You should see: “Successfully flushed the DNS Resolver Cache”
  4. Restart Chrome and try again

Mac:

  1. Open Terminal (Applications → Utilities → Terminal)
  2. Type: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  3. Enter your password when prompted
  4. Restart Chrome

Chrome’s internal DNS cache:

  1. In Chrome, go to chrome://net-internals/#dns
  2. Click “Clear host cache”
  3. Then go to chrome://net-internals/#sockets and click “Flush socket pools”

Fix 3: Change Your DNS Server

If your ISP’s DNS server is slow, down, or blocking domains, switching to a public DNS server resolves the issue immediately.

Windows:

  1. Settings → Network & Internet → Change adapter options
  2. Right-click your connection → Properties
  3. Select Internet Protocol Version 4 → Properties
  4. Select “Use the following DNS server addresses”
  5. Preferred: 8.8.8.8 (Google)   Alternate: 8.8.4.4
  6. Click OK and restart Chrome

Alternative DNS servers to try: Cloudflare (1.1.1.1), Quad9 (9.9.9.9).

You can verify your DNS is working correctly with the ExamineIP DNS Checker — it queries Google DNS and Cloudflare simultaneously and shows you whether they agree.

Fix 4: Restart Your Router

Your router also maintains a DNS cache. A stuck router can cause DNS failures across every device on your network simultaneously.

  1. Unplug your router from power
  2. Wait 30 seconds
  3. Plug back in and wait for all lights to stabilize
  4. Reconnect and try again

Fix 5: Check Your Hosts File

The Windows hosts file can override DNS for specific domains. Malware sometimes modifies this file to redirect or block websites.

Windows:

  1. Open Notepad as Administrator
  2. File → Open → navigate to C:\Windows\System32\drivers\etc\hosts
  3. Look for any lines mentioning the domain you’re trying to reach
  4. Delete suspicious entries and save

Fix 6: Use a VPN to Bypass ISP Blocks

If the domain works on mobile data but not your home Wi-Fi, your ISP is likely blocking it. A VPN routes your DNS queries through a different network entirely, bypassing the block.

PureVPN and IPVanish both have their own DNS servers that are unaffected by ISP-level blocks.

See also: Does a VPN hide your IP address?

How to Check if the Site Itself Is Down

Before spending time troubleshooting your network, verify the site is actually reachable from elsewhere:

DNS_PROBE_FINISHED_NXDOMAIN vs DNS_PROBE_FINISHED_NO_INTERNET: NXDOMAIN means DNS found no record for the domain. NO_INTERNET means DNS couldn’t be reached at all. If you see NO_INTERNET, your device has no internet connection — start with your router.

Frequently Asked Questions

Does DNS_PROBE_FINISHED_NXDOMAIN only happen in Chrome?

The error code is Chrome-specific but the underlying problem is the same in all browsers. Firefox shows it as “Server Not Found” and Edge shows a slightly different message. The fixes are identical.

Why does this error happen on only some websites?

Site-specific NXDOMAIN usually means your DNS cache has a bad entry for that specific domain, or your ISP is blocking that domain. Flushing your DNS cache and testing with a VPN will tell you which one it is.

Can I fix this without admin access to my computer?

Yes — you can change Chrome’s DNS resolver without admin rights. Go to Chrome Settings → Privacy and security → Security → Use secure DNS → select Google or Cloudflare. This overrides the system DNS just for Chrome.

Scroll to Top