How to Fix dns_probe_finished_nxdomain

The dns_probe_finished_nxdomain error appears in Google Chrome when the browser cannot resolve a domain name to an IP address. NXDOMAIN stands for "Non-Existent Domain," meaning the DNS system responded that the domain does not exist. You see the error page with "This site can't be reached" and the technical code DNS_PROBE_FINISHED_NXDOMAIN.

This error can mean the domain genuinely does not exist, but more often it indicates a problem with your DNS configuration, your local DNS cache, or the DNS resolver you are using. Here is how to diagnose the cause and fix it. For a broader look at DNS errors, see Common DNS Errors.

What Causes the Error

The error occurs when a DNS query returns an NXDOMAIN response. Several things can trigger this:

The domain does not exist. If you mistyped the URL or the domain has expired, the DNS system correctly reports that it does not exist.

Your DNS cache has a stale negative entry. If the domain was briefly unavailable and your system cached the NXDOMAIN response, you continue getting the error even after the domain comes back.

Your DNS resolver is not working. If your configured DNS server is down or unreachable, the browser reports an NXDOMAIN error even for domains that exist.

Your local hosts file redirects the domain. The hosts file can override DNS resolution. If an entry maps the domain to an invalid address or 0.0.0.0, the domain appears to not exist.

VPN or proxy interference. VPNs and proxies can modify DNS resolution, sometimes blocking or misrouting queries.

Browser extensions blocking the domain. Ad blockers and security extensions can intercept DNS queries and block access to certain domains.

ISP DNS blocking. Some ISPs block access to certain domains at the DNS level, returning NXDOMAIN instead of the real address.

Step 1: Verify the Domain Exists

Before troubleshooting your system, confirm that the domain actually exists. Try accessing the same URL from a different device or network (your phone on cellular data, for example). If it works elsewhere, the problem is local to your machine or network.

You can also check if the domain resolves using an online DNS lookup tool or by querying a public DNS resolver:

nslookup example.com 8.8.8.8

If this returns an IP address, the domain exists and the problem is on your end. If it also returns NXDOMAIN, the domain may genuinely not exist or may not have DNS records configured.

Step 2: Clear Your DNS Cache

Your operating system and browser both cache DNS responses. A cached NXDOMAIN response will persist until the cache entry expires, even if the domain has been fixed on the server side.

Windows

Open Command Prompt as Administrator and run:

ipconfig /flushdns

You should see "Successfully flushed the DNS Resolver Cache."

macOS

Open Terminal and run:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux

The command depends on your distribution and DNS resolver:

# systemd-resolved (Ubuntu 18.04+, Fedora)
sudo systemd-resolve --flush-caches

# Or the newer syntax
sudo resolvectl flush-caches

# dnsmasq
sudo systemctl restart dnsmasq

Chrome Browser Cache

Chrome maintains its own DNS cache. Clear it by navigating to:

chrome://net-internals/#dns

Click "Clear host cache." Then also clear socket pools at:

chrome://net-internals/#sockets

Click "Flush socket pools."

For a comprehensive guide to flushing DNS, see Flush DNS Cache.

Step 3: Check Your DNS Settings

Verify that your device is using a working DNS resolver.

Windows

1. Open Settings > Network & Internet > Advanced network settings.
2. Click on your active network adapter.
3. Click View additional properties or Edit next to DNS server assignment.
4. Check the DNS server addresses.

If the DNS server is set to your router's IP (often 192.168.1.1), the router forwards queries to your ISP's DNS. If your ISP's DNS is having issues, this is where the problem originates.

macOS

1. Open System Settings > Network.
2. Select your active connection.
3. Click Details > DNS.
4. Check the DNS server list.

Switching to a Public DNS Resolver

If your current DNS resolver is causing problems, switch to a public one:

Google Public DNS: 8.8.8.8 and 8.8.4.4 Cloudflare DNS: 1.1.1.1 and 1.0.0.1 Quad9: 9.9.9.9 and 149.112.112.112

For a comparison of public resolvers, see Public DNS Providers.

On Windows, change DNS in network adapter settings. On macOS, add DNS servers in System Settings > Network > Details > DNS. On Linux, edit /etc/resolv.conf or configure your network manager.

After changing DNS servers, flush your DNS cache and try the domain again.

Step 4: Check Your Hosts File

The hosts file on your system can override DNS resolution for specific domains. If a domain is mapped to 127.0.0.1, 0.0.0.0, or a non-existent IP, the browser may show NXDOMAIN or a connection error.

Windows

Open C:\Windows\System32\drivers\etc\hosts in a text editor (run as Administrator):

notepad C:\Windows\System32\drivers\etc\hosts

Look for lines containing the domain you are trying to access. If the domain is listed with 0.0.0.0 or 127.0.0.1, remove or comment out (prefix with #) that line.

macOS / Linux

sudo nano /etc/hosts

Check for entries mapping the target domain to a local or invalid address.

Malware sometimes modifies the hosts file to block access to security sites or redirect traffic. If you find unexpected entries, remove them and scan your system for malware.

Step 5: Disable VPN and Proxy

If you use a VPN, disconnect it temporarily and try accessing the domain again. VPNs route your traffic through their own DNS resolvers, which may handle certain domains differently.

Similarly, check for proxy configurations:

Windows

Settings > Network & Internet > Proxy. Make sure "Use a proxy server" is off (unless you intentionally use a proxy).

macOS

System Settings > Network > select your connection > Details > Proxies. Ensure no proxies are enabled unless intended.

Chrome

Check Chrome's proxy settings at chrome://settings/?search=proxy. Chrome uses your system's proxy settings by default.

Step 6: Disable Browser Extensions

Ad blockers, privacy extensions, and security tools can intercept DNS queries and block domains. Disable extensions temporarily to test:

1. Open Chrome's extension manager: chrome://extensions/
2. Disable all extensions.
3. Try accessing the domain.
4. If it works, re-enable extensions one at a time to find the culprit.

Step 7: Reset Chrome Flags

Experimental Chrome flags can sometimes interfere with DNS resolution:

1. Navigate to chrome://flags/
2. Click "Reset all" at the top of the page.
3. Restart Chrome.

Step 8: Renew Your IP Address

Network configuration issues can sometimes cause DNS problems. Renewing your IP address resets your network connection:

Windows

ipconfig /release
ipconfig /renew

macOS

Go to System Settings > Network > select your connection > Details > TCP/IP > Renew DHCP Lease.

Linux

sudo dhclient -r
sudo dhclient

Step 9: Check the Domain's DNS Configuration

If the domain is yours and other people are also seeing the error, the problem may be with the domain's DNS configuration:

• Verify nameserver settings. Check that the correct nameservers are assigned at your registrar.
• Check for missing A/AAAA records. The domain needs A or AAAA records (or a CNAME pointing to a hostname with A/AAAA records) to resolve.
• Check for expired domain. If the domain registration expired, the registrar may have removed the DNS records or changed the nameservers.
• Check DNS propagation. If you recently changed DNS records, the changes may not have propagated to all resolvers yet. See Check DNS Propagation.

Use dig or nslookup to check from your authoritative nameservers directly:

dig example.com @ns1.yourdnsprovider.com

If the authoritative nameservers return NXDOMAIN, the zone is not configured correctly. If they return a valid response but public resolvers return NXDOMAIN, the issue is propagation or caching.

The Error in Other Browsers

Other browsers display the same underlying error differently:

• Firefox: "Hmm. We're having trouble finding that site."
• Safari: "Safari Can't Find the Server"
• Edge: Same as Chrome (Chromium-based)

The causes and fixes are identical regardless of the browser. The DNS resolution issue is at the operating system level, not the browser level (except for browser-specific caching and extensions).

Preventing the Error for Your Domain

If you manage a domain and want to prevent your users from seeing this error:

1. Monitor your DNS records. Use DNS monitoring to detect when records are removed or changed unexpectedly.
2. Keep your domain registration current. Set up auto-renewal and ensure your registrar contact information is up to date.
3. Use multiple nameservers on different networks. This provides redundancy if one nameserver goes down.
4. Set appropriate TTL values. Low TTLs mean cached records expire quickly, but they also mean more frequent queries to your nameservers. Find a balance.

References

1. RFC 8499, "DNS Terminology," January 2019. https://datatracker.ietf.org/doc/html/rfc8499
2. RFC 2308, "Negative Caching of DNS Queries (DNS NCACHE)," March 1998. https://datatracker.ietf.org/doc/html/rfc2308
3. Google, "Fix 'This site can't be reached' error," Chrome Help. https://support.google.com/chrome/answer/6098869