How to Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome (The Fix That 90% of Guides Miss)

You click a link or type a URL and Chrome shows you: “This site can’t be reached. [website].com’s server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN.”

NXDOMAIN means “Non-Existent Domain.” Chrome asked the DNS server “where is this website?” and the DNS server said “never heard of it.”

Now, this might be accurate — the domain might genuinely not exist, or it expired. But if you KNOW the website is real (you were just on it yesterday), something on your end is breaking DNS resolution.

Here’s what most guides miss: they tell you to run ipconfig /flushdns and call it a day. But Chrome has its own DNS cache that’s completely separate from Windows. If you only flush the Windows cache, Chrome is still using its stale internal data. You have to clear both.

Step 0: Make Sure It’s Not a Typo

Seriously. Before you do anything:

1. Double-check the URL — is it .com or .co? youtube.com or youtubee.com?
2. Try it on your phone (using mobile data, not Wi-Fi) — if it loads on your phone, the problem is your PC or network
3. Check isitdownrightnow.com — if the site is down for everyone, just wait

If the site works on other devices but not your PC, the DNS issue is local. Let’s fix it.

Fix 1: Flush BOTH DNS Caches (Windows + Chrome)

This is the fix that 90% of guides get half-right. They tell you to flush the Windows DNS cache. But Chrome maintains its own DNS cache that Windows doesn’t control.

Step 1 — Flush Windows DNS:

Open Command Prompt as Administrator and run:

ipconfig /flushdns

You’ll see “Successfully flushed the DNS Resolver Cache.”

Step 2 — Flush Chrome’s internal DNS:

1. Open Chrome and type chrome://net-internals/#dns in the address bar
2. Click “Clear host cache”

Step 3 — Flush Chrome’s socket pool too (bonus):

While you’re in chrome://net-internals, click on “Sockets” in the left sidebar, then click “Flush socket pools.” Stale socket connections can also cause DNS-related failures.

Now restart Chrome and try the website again.

Fix 2: Switch DNS Servers

Your ISP’s default DNS servers might be slow, overloaded, or having issues. Switching to a public DNS provider often fixes NXDOMAIN errors instantly.

How to change DNS on Windows:

1. Press Win + R, type ncpa.cpl, press Enter
2. Right-click your active network adapter → Properties
3. Select Internet Protocol Version 4 (TCP/IPv4) → click Properties
4. Select “Use the following DNS server addresses”
5. Enter:
   • Google DNS: 8.8.8.8 and 8.8.4.4
   • Cloudflare DNS: 1.1.1.1 and 1.0.0.1
6. Click OK → Close

How to change DNS on Mac:

System Preferences → Network → select your connection → Advanced → DNS tab → click + → add 1.1.1.1 and 1.0.0.1

After changing DNS, flush both caches again (Fix 1) and try the website.

Fix 3: Check Your Hosts File

Your computer has a local file called hosts that can override DNS for specific domains. If a domain is listed in this file pointing to 127.0.0.1 or 0.0.0.0, your browser will never reach it — no matter what DNS server you use.

Malware, parental control software, ad-blocking tools, and even developers testing local sites can add entries to the hosts file.

How to check on Windows:

1. Open Notepad as Administrator (right-click → Run as administrator)
2. File → Open → navigate to C:\Windows\System32\drivers\etc\
3. Change the file type filter from “Text Documents” to “All Files”
4. Open the file named hosts

Look for lines like:

127.0.0.1   youtube.com

0.0.0.0     facebook.com

If the website you can’t reach is listed here, delete that line, save the file, and try again.

Legitimate entries in the hosts file are usually just 127.0.0.1 localhost and ::1 localhost. Everything else is suspicious unless you specifically added it.

How to check on Mac:

Open Terminal and run:

sudo nano /etc/hosts

Look for suspicious entries, delete them, press Ctrl + O to save, Ctrl + X to exit.

Fix 4: Release and Renew IP Address

Sometimes your network adapter gets stuck with stale network configuration data. Releasing and renewing your IP address can fix this.

Open Command Prompt as Administrator and run these commands one at a time:

ipconfig /release

ipconfig /renew

ipconfig /flushdns

netsh winsock reset

Restart your PC after running all four commands.

Fix 5: Restart the DNS Client Service

Windows runs a service called “DNS Client” that handles DNS resolution. If this service crashes or gets stuck, DNS stops working entirely.

1. Press Win + R, type services.msc, press Enter
2. Scroll down to find “DNS Client”
3. Check the Status column — it should say “Running”
4. Right-click → Restart

If “Restart” is grayed out, you can stop and start the service via Command Prompt:

net stop dnscache

net start dnscache

Fix 6: Reset Chrome Flags

Chrome’s experimental flags can interfere with DNS resolution if you’ve (intentionally or accidentally) changed them.

1. Type chrome://flags in the address bar
2. Click “Reset all to default” at the top
3. Click “Relaunch”

This resets all experimental features without affecting your bookmarks, passwords, or extensions.

Fix 7: Disable VPN and Check Antivirus

VPN software replaces your DNS settings with its own servers. If the VPN’s DNS server is down or misconfigured, you get NXDOMAIN errors on every website.

• Temporarily disconnect your VPN and try the website
• If it works without VPN, switch the VPN to use custom DNS (most VPN apps have this option)

Antivirus programs with “web protection” or “safe browsing” features can also intercept and block DNS queries. Try disabling the web protection module temporarily.

Quick Reference: DNS_PROBE_FINISHED_NXDOMAIN Causes

Frequently Asked Questions

I changed DNS to 8.8.8.8 but still get the error. What now?

Google’s DNS isn’t perfect 100% of the time. Try Cloudflare (1.1.1.1) instead. Also make sure you flushed Chrome’s internal DNS cache at chrome://net-internals/#dns — not just the Windows cache.

Does this error mean the website got hacked?

No. NXDOMAIN just means the DNS system can’t find the domain. The website could be down, the domain could have expired, or your DNS settings could be wrong. It has nothing to do with hacking.

My ISP blocks certain websites. Could that cause NXDOMAIN?

Yes. Some ISPs use DNS-level blocking to restrict access to certain websites. When they block a domain, their DNS server returns NXDOMAIN as if the domain doesn’t exist. Switching to a third-party DNS like Cloudflare or Google bypasses this.

Should I permanently switch to Google or Cloudflare DNS?

For most people, yes. Third-party DNS providers like Cloudflare (1.1.1.1) and Google (8.8.8.8) are generally faster and more reliable than ISP DNS servers. Cloudflare also has a privacy focus — they don’t sell your DNS query data.

Stop Getting NXDOMAIN Errors

Switch your DNS to Cloudflare or Google permanently, flush Chrome’s internal DNS cache (not just Windows), and check your hosts file. Those three steps fix 95% of DNS_PROBE_FINISHED_NXDOMAIN cases. The remaining 5% is usually a dead domain or an ISP block.

Last updated: February 2026 | Tested on Chrome 131, Edge 131 — Windows 10/11, macOS