DNS Probe Finished NXDOMAIN: What It Means & Fixes

“DNS probe finished NXDOMAIN” is a Chrome error that means the domain name you tried to visit does not exist, according to the DNS server you are using. It can happen for a genuine typo, a recently deleted website, or a temporary DNS hiccup on your device or router. This article explains what the error means, why it appears, and the exact steps to fix it on Windows, macOS, Android, and iOS.

What Is DNS and What Does NXDOMAIN Mean?

DNS (Domain Name System) is the internet’s phone book. When you type a website address, your device asks a DNS server to translate that name (like example.com) into an IP address (like 93.184.216.34). The DNS server responds with one of several answers:

• An IP address – the site exists, and your browser connects.
• NXDOMAIN – the domain name does not exist. The “NX” stands for “non-existent.”
• SERVFAIL – the DNS server had a problem, but the domain might exist.
• Timeout – no answer was received.

When Chrome shows “DNS probe finished NXDOMAIN,” it means the DNS lookup returned NXDOMAIN. That is different from a timeout or a server failure. It is the DNS equivalent of a phone company saying “that number is not in service.”

Why Does the Error Appear?

The most common reasons are:

• Typo in the address – a misspelled domain name often points to a non-existent domain.
• The site was taken down or never existed – expired domains or removed pages return NXDOMAIN.
• Your DNS cache is stale – your device may have saved an old “does not exist” answer, even after the site becomes available.
• Your router or ISP’s DNS server is having issues – they may temporarily return NXDOMAIN for valid sites.
• Malware or browser extensions – some malicious software can alter DNS settings or block certain domains.

How to Fix It on Windows

1. Clear the DNS cache. Open Command Prompt as administrator and run: ipconfig /flushdns
2. Change your DNS server. Go to Settings > Network & Internet > Change adapter options. Right-click your connection, select Properties, select Internet Protocol Version 4 (TCP/IPv4), and use a public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1).
3. Reset the network stack. In the same Command Prompt, run: netsh winsock reset and netsh int ip reset, then restart your computer.
4. Check for malware. Run a full scan with Windows Defender or another trusted antivirus.
5. Disable browser extensions. Chrome extensions that block ads or modify DNS can cause this error. Try incognito mode (which disables extensions) to test.

How to Fix It on macOS

1. Flush the DNS cache. Open Terminal and run: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
2. Change DNS servers. Go to System Settings > Network, select your connection, click Details, then DNS. Add 8.8.8.8 and 1.1.1.1.
3. Renew DHCP lease. In the same Network settings, click Renew DHCP Lease.
4. Restart in Safe Mode – this can help if a third-party extension or daemon is interfering.

How to Fix It on Android and iOS

On Android:

1. Go to Settings > Network & Internet > Wi-Fi, tap your network, and select “Modify network.”
2. Change IP settings to “Static” and set DNS 1 to 8.8.8.8 and DNS 2 to 1.1.1.1.
3. Alternatively, use Private DNS (Settings > Network & Internet > Private DNS) and enter dns.google or one.one.one.one.

On iPhone/iPad:

1. Go to Settings > Wi-Fi, tap the “i” next to your network.
2. Tap “Configure DNS” and set it to Manual. Add 8.8.8.8 and 1.1.1.1.
3. You can also install a DNS profile from a provider like Cloudflare or NextDNS.

Router-Level Fixes

If the error appears on all devices, the problem may be your router’s DNS. Try:

• Restarting the router (unplug for 30 seconds and plug back in).
• Logging into the router’s admin panel (usually at 192.168.1.1 or 192.168.0.1) and changing the DNS server to a public one.
• Updating the router firmware if an update is available.

When the Error Is Actually Correct

Sometimes the error is accurate: the domain truly does not exist. This can happen if you typed a wrong extension (like .com instead of .org) or if the site was recently deleted. Before trying elaborate fixes, verify the address:

• Use a search engine to find the correct URL.
• Check if the site is down for everyone using a service like downforeveryoneorjustme.com.
• Try a different browser or device – if it works there, the problem is local.

Frequently Asked Questions

What does “DNS probe finished NXDOMAIN” mean exactly?

It means the DNS server you queried responded with “non-existent domain.” The name you requested does not have a DNS record, so the browser cannot connect. It is not a network timeout or a server error.

Can this error be caused by a virus?

Yes, some malware can modify your DNS settings or redirect traffic to non-existent domains. If the error persists after changing DNS servers and flushing cache, run a full antivirus scan.

Why does the error only happen on one device?

That usually points to a device-specific issue – a stale DNS cache, a misconfigured network setting, or a browser extension. Try clearing the cache and using a different browser first.

Will changing my DNS server affect my internet speed?

It might improve speed slightly if your ISP’s DNS is slow, but the effect is usually minimal. Public DNS servers like Google and Cloudflare are reliable and free.

How do I clear the DNS cache on Chrome?

Chrome itself does not have a dedicated DNS cache, but it uses the system’s cache. Clearing the system cache (as described above) is sufficient. You can also type chrome://net-internals/#dns in Chrome and click “Clear host cache.”

Is there a way to prevent this error in the future?

Use a reliable DNS server, keep your browser and operating system updated, and be careful when typing URLs. If you frequently visit a site that goes down, check its status on social media or a status page before assuming it’s gone.

Related

• Web Page Hijacking: Types & How It Happens
• Why I Use Virtual Machines for Work
• Early Space Colonization Ideas That Failed