How to Troubleshoot 'DNS_PROBE_FINISHED_NXDOMAIN' Error in Chrome

The DNS_PROBE_FINISHED_NXDOMAIN error in Google Chrome occurs when your browser cannot resolve a domain name to an IP address because the domain simply does not exist or your local network cannot find the correct nameserver. Fixing this issue usually requires clearing your local DNS cache, resetting your network stack, or switching to a reliable public DNS provider. Whether you are trying to reach your own live domain or browsing the web, this error points directly to a name resolution failure in the Domain Name System.

To quickly check if a domain is globally resolving or if the problem is strictly on your local machine, use the DNS Lookup tool to query authoritative nameservers and inspect live A, AAAA, and MX records instantly.

Understanding the NXDOMAIN Error

NXDOMAIN stands for "Non-Existent Domain." When you type example.com into your address bar, your browser asks your operating system for the corresponding IP address. Your OS asks your configured recursive resolver (such as your ISP's DNS server), which queries the root servers, Top-Level Domain (TLD) servers, and finally the domain's authoritative nameservers.

If the authoritative server replies that the record does not exist, or if your computer fails to reach any nameserver at all, Chrome displays the DNS_PROBE_FINISHED_NXDOMAIN page.

Common Causes

• Expired or newly registered domains: The domain name has not fully propagated or has lapsed.
• Local DNS cache corruption: Your operating system or browser holds onto outdated or broken IP mappings.
• Incorrect network configuration: Your computer is pointing to a dead or misconfigured local DNS resolver.
• VPN or firewall interference: Security software is blocking DNS queries or virtual network adapters are overriding standard routing.

Step-by-Step Troubleshooting Guide

Follow these practical steps in order to diagnose and resolve the error on your machine.

Step 1: Release and Renew Your IP Address

Stale local network configurations often prevent proper DNS routing. Refreshing your IP configuration forces your operating system to request new lease parameters from your local DHCP server.

• Windows (PowerShell or Command Prompt): Open PowerShell as Administrator and run the following commands one by one:

  ipconfig /release
  ipconfig /renew
  

• macOS (Terminal): Open Terminal and restart your DHCP lease by running:

  sudo ipconfig set en0 DHCP
  

  (Note: Replace en0 with your active network interface name such as en1 or Wi-Fi if necessary).

Step 2: Flush the Local DNS Cache

Your operating system stores recent DNS lookups in a local cache to speed up web browsing. If an IP address changes or a lookup fails, that bad record can get stuck.

• Windows:

  ipconfig /flushdns
  

  Sample Output:

  Windows IP Configuration
  
  Successfully flushed the DNS Resolver Cache.
  

• macOS:

  sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  

• Google Chrome Internal Cache: Chrome maintains its own independent DNS cache. Open a new tab, navigate to chrome://net-internals/#dns, and click the Clear host cache button.

Step 3: Reset Your Network Stack

If clearing caches does not work, resetting the entire network stack clears corrupted Winsock entries and IP helper bindings.

1. Open PowerShell or Command Prompt as Administrator.
2. Run the Winsock reset command:

   netsh winsock reset
   

3. Run the IP reset command:

   netsh int ip reset
   

4. Restart your computer immediately to apply the changes.

Step 4: Change Your DNS Server Addresses

Your Internet Service Provider's default DNS servers are notorious for slow propagation, downtime, and resolution failures. Switching to a public, highly available DNS provider instantly bypasses local ISP routing bugs.

• Popular Public DNS Providers:

  • Cloudflare: 1.1.1.1 and 1.0.0.1 (IPv6: 2606:4700:4700::1111)
  • Google Public DNS: 8.8.8.8 and 8.8.4.4 (IPv6: 2001:4860:4860::8888)
  • Quad9: 9..9.9.9 and 149.112.112.112

• How to change on Windows: Go to your system network settings, open adapter properties, select Internet Protocol Version 4 (TCP/IPv4), click Properties, and input your chosen DNS server addresses.

• How to change on macOS: Go to System Settings, click Network, select your active connection (Wi-Fi or Ethernet), click Details, navigate to the DNS tab, and click the + button to add new DNS server IPs.

Step 5: Temporarily Disable VPNs and Security Software

Virtual Private Networks (VPNs), third-party antivirus suites, and local firewalls often alter your network adapters or intercept DNS queries using custom protocols (like Secure DNS or encrypted proxies). Temporarily pause your VPN or disable third-party firewall filtering to test if the error disappears.

Verifying DNS Resolution via Command Line

Before assuming a site is broken, test resolution directly from your terminal using standard diagnostic utilities.

Using nslookup:

nslookup example.com

Expected Sample Output:

Server:  1.1.1.1
Address: 1.1.1.1#53

Non-authoritative answer:
Name:    example.com
Address: 192.0.2.1

Using dig (Linux and macOS):

dig example.com +short

Expected Sample Output:

192.0.2.1

If these commands return server failure or connection timed out, the issue lies with your network connectivity or DNS provider rather than Chrome itself.

Troubleshooting Comparison Table

Common Mistakes to Avoid

• Confusing Browser History with DNS Cache: Deleting your browsing history and cookies in Chrome does not clear the internal DNS host cache. You must use chrome://net-internals/#dns.
• Forgetting to Restart: Many network stack and Winsock adjustments on Windows require a full system reboot to take full effect.
• Mixing IPv4 and IPv6 Settings: If you manually set static IPv4 DNS servers, ensure your IPv6 settings are either populated with matching public IPv6 DNS addresses or disabled entirely to prevent leaks.
• Testing with Typos: Double-check your spelling. Typing exampel.com will reliably trigger an NXDOMAIN error because the domain does not exist.

Quick Troubleshooting Checklist

• Verify spelling of the domain name in the Chrome address bar.
• Test the domain using an external lookup utility to ensure it resolves globally.
• Flush operating system DNS cache (ipconfig /flushdns or dscacheutil).
• Clear Chrome's internal host cache via chrome://net-internals/#dns.
• Switch network adapter settings to use public DNS servers (1.1.1.1 or 8.8.8.8).
• Disable VPN, proxy, or aggressive third-party antivirus firewall rules.
• Restart your computer and network router.