DNS Probe Finished NXDOMAIN: 7 Fixes for Chrome

If you see “DNS_PROBE_FINISHED_NXDOMAIN� in Google Chrome, it means the browser couldn’t find the website’s address in the Domain Name System (DNS), so it can’t load the page. The fix usually involves clearing your DNS cache, changing your DNS server, or disabling a faulty Chrome extension. Below are proven steps to resolve this error, followed by background on why it happens and how to prevent it.

What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?

DNS (Domain Name System) is the internet’s phonebook—it translates human-friendly names like example.com into numeric IP addresses like 93.184.216.34. When Chrome shows this error, it means the DNS lookup for the domain returned “NXDOMAIN� (non-existent domain). In simple terms, the DNS server you’re using couldn’t find a record for that address.

This can happen for several reasons:

• The domain genuinely doesn’t exist (typo, expired domain).
• Your local DNS cache is corrupted or outdated.
• Your router’s DNS settings are misconfigured.
• A VPN or proxy is interfering with DNS queries.
• A Chrome extension is blocking or redirecting DNS lookups.
• Your ISP’s DNS server is temporarily down or slow.

It’s important to note that the error is not always a problem with your computer—sometimes the website itself is down or has removed its DNS records. But the following fixes address the most common local causes.

Before You Start: Quick Checks

Spend 30 seconds ruling out the simplest causes before diving into technical fixes:

• Try a different browser (Firefox, Edge). If the site loads there, the problem is Chrome-specific.
• Try another device on the same network. If it also fails, the issue is likely your router or the site itself.
• Check the URL for typos. A single misspelled letter will produce NXDOMAIN.
• Look up the domain on a service like whois.com to see if it’s actually registered and active.

If none of these help, proceed with the fixes below in order.

Fix 1: Clear Chrome’s DNS Cache and Host Cache

Chrome maintains its own internal DNS cache and a host resolver cache that can become corrupt. To clear them:

1. Close all Chrome windows.
2. Open a new Chrome window and type chrome://net-internals/#dns in the address bar.
3. Click the “Clear host cache� button.
4. Go to chrome://net-internals/#sockets and click “Flush socket pools.�
5. Restart Chrome and try the site again.

This clears Chrome’s own records without affecting other programs. If the error persists, move on to clearing the system-level DNS cache.

Fix 2: Flush Your Operating System’s DNS Cache

Your OS also stores DNS lookups. Flushing it forces a fresh query to the DNS server.

• Windows: Open Command Prompt as Administrator and run ipconfig /flushdns.
• macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder (on modern versions).
• Linux: The command varies by distribution; common ones are sudo systemd-resolve --flush-caches or sudo service nscd restart.

After flushing, reload the page. If it still fails, the problem is likely with your DNS server itself.

Fix 3: Change Your DNS Server to a Public One

Your ISP’s DNS server might be slow, overloaded, or incorrectly returning NXDOMAIN for valid sites. Switching to a public DNS provider often resolves this. Two widely used options:

• Google Public DNS: Primary 8.8.8.8, Secondary 8.8.4.4
• Cloudflare DNS: Primary 1.1.1.1, Secondary 1.0.0.1

To change DNS on Windows:

1. Go to Control Panel > Network and Sharing Center > Change adapter settings.
2. Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
3. Select “Internet Protocol Version 4 (TCP/IPv4)� and click Properties.
4. Choose “Use the following DNS server addresses� and enter the public DNS addresses.
5. Click OK and restart your connection.

On macOS, go to System Settings > Network > your connection > Details > DNS, and add the public DNS servers. On a router, change the DNS settings in the admin panel (usually at 192.168.1.1 or 192.168.0.1).

Fix 4: Disable VPN and Proxy Extensions

VPNs and proxy extensions can interfere with DNS resolution. Some VPNs route DNS queries through their own servers, which may have outdated or incomplete records. To test:

1. Turn off your VPN (both the app and any browser extension).
2. In Chrome, go to Settings > Extensions and disable any VPN, proxy, or security extensions.
3. Try the site again.

If the site loads, re-enable extensions one by one to find the culprit. Also check that your system proxy settings aren’t misconfigured: in Windows, go to Settings > Network & Internet > Proxy and ensure “Use a proxy server� is off unless you actually use one. On macOS, check System Settings > Network > Proxies.

Fix 5: Reset Chrome Flags and Disable Hardware Acceleration

Sometimes Chrome’s experimental flags or hardware acceleration can cause DNS issues, especially after updates. To reset flags:

1. Type chrome://flags in the address bar.
2. Click “Reset all to default� at the top right.
3. Restart Chrome.

To disable hardware acceleration:

1. Go to Settings > System.
2. Turn off “Use hardware acceleration when available.�
3. Restart Chrome.

These changes can resolve conflicts that cause DNS errors, though they’re less common than the earlier fixes.

Fix 6: Renew Your IP Address and Reset Winsock (Windows)

If you’re on Windows, a corrupted Winsock catalog or a stale IP lease can cause DNS failures. Run these commands in an elevated Command Prompt:

1. ipconfig /release
2. ipconfig /renew
3. netsh winsock reset
4. netsh int ip reset
5. Restart your computer.

This resets the network stack to a clean state. On macOS or Linux, you can simply restart your router or toggle your Wi-Fi off and on.

Fix 7: Check Hosts File and Malware

A malicious or misconfigured hosts file can override DNS and cause NXDOMAIN errors. On Windows, the file is at C:\Windows\System32\drivers\etc\hosts; on macOS/Linux, it’s /etc/hosts. Open it with a text editor and look for any lines that aren’t commented out (starting with #) or that don’t match known entries. If you see strange redirects, remove them (but back up the file first).

Also run a reputable malware scan—some adware modifies DNS settings or hosts files to block or redirect sites. If you don’t have a scanner, Windows Defender (built into Windows 10/11) can perform a full scan.

Frequently Asked Questions

Why does the error only happen in Chrome and not other browsers?

Chrome has its own DNS cache and may use different network settings than other browsers. If other browsers work, the issue is likely Chrome’s internal cache or an extension. Clearing Chrome’s cache (Fix 1) or resetting flags (Fix 5) usually resolves it.

Can this error be caused by the website itself?

Yes. If the domain’s DNS records are removed, expired, or misconfigured, any device will get NXDOMAIN. Use a DNS lookup tool (like dns.google) to see if the domain resolves globally. If it doesn’t, the site is down and there’s nothing you can do locally.

Will changing DNS servers affect my internet speed?

It can. A faster DNS server can speed up the initial connection to websites, but it won’t increase your download or upload bandwidth. In most cases, public DNS servers like Google or Cloudflare are faster than ISP defaults, but results vary by location.

Is it safe to use public DNS servers?

Yes. Google and Cloudflare DNS are widely used and have strict privacy policies. They don’t sell your browsing history, but they do log some data for security. If privacy is a concern, you can use encrypted DNS (DoH) in Chrome by enabling it in Settings > Security and Privacy > Security.

How do I clear DNS cache on a router?

Most routers don’t have a manual cache flush; you simply reboot the router by unplugging it for 30 seconds and plugging it back in. This clears the router’s DNS cache and renews its connection to the ISP.

What if none of these fixes work?

If the error persists, try a different device on the same network. If that also fails, contact your ISP—there may be a broader DNS outage. If only your device fails, consider resetting your network settings to factory defaults (on Windows: Settings > Network & Internet > Advanced network settings > Network reset).

Related

• Using Attendant in Zoom: A Step-by-Step Guide
• Buy Me a Coffee vs PayPal: Key Differences
• Keep OBS Yoga Nidra Stream Running After Windows Restart