Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome

Symptoms

When attempting to visit a website in Google Chrome, you see the error message: DNS_PROBE_FINISHED_NXDOMAIN. The page fails to load, and other browsers may also have trouble accessing the same site. This error indicates that the DNS lookup for the domain name returned a non-existent domain (NXDOMAIN) response, meaning the domain could not be resolved to an IP address.

Root Causes

• Corrupted DNS cache: Your computer or router has outdated or corrupt DNS records.
• Incorrect DNS server settings: The DNS servers configured on your device or router are not responding properly or are misconfigured.
• Network connectivity issues: Temporary network glitches or ISP problems can cause DNS failures.
• Firewall or security software: Overly aggressive security settings may block DNS queries.
• Domain actually does not exist: The website may be down or the URL is mistyped.

Step-by-Step Fix

1. Check if the domain is correct: Ensure you typed the URL correctly. Try accessing a different website to see if the issue is isolated.
2. Restart your router and computer: Power cycle your modem/router and restart your computer to clear temporary network states.
3. Clear Chrome's DNS cache: Type chrome://net-internals/#dns in the address bar, then click Clear host cache.
4. Flush system DNS cache:
   • Windows: Open Command Prompt as Administrator and run ipconfig /flushdns.
   • macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
   • Linux: Run sudo systemd-resolve --flush-caches or sudo resolvectl flush-caches.
5. Change DNS server to Google Public DNS:
   • Go to your network adapter settings (Control Panel > Network and Sharing Center > Change adapter settings).
   • Right-click your active connection, select Properties, then select Internet Protocol Version 4 (TCP/IPv4).
   • Choose Use the following DNS server addresses and set:
     Preferred: 8.8.8.8
     Alternate: 8.8.4.4
   • Click OK and restart your browser.
6. Reset Chrome flags: Type chrome://flags in the address bar, click Reset all to default.
7. Disable IPv6 temporarily: In network adapter properties, uncheck Internet Protocol Version 6 (TCP/IPv6) and test.
8. Check hosts file: Ensure no incorrect entries for the domain. On Windows, the hosts file is at C:\Windows\System32\drivers\etc\hosts. On macOS/Linux, it's /etc/hosts.

Alternative Fixes

• Use a different browser: Test in Firefox or Edge to rule out Chrome-specific issues.
• Reset Winsock: On Windows, run netsh winsock reset in Command Prompt as Administrator, then restart.
• Disable security software temporarily: Turn off antivirus or firewall to see if they interfere.
• Use a VPN: Connecting to a VPN can bypass ISP DNS issues.
• Contact your ISP: If the problem persists for many sites, your ISP's DNS may be down.

Prevention

• Use reliable DNS servers: Configure Google DNS (8.8.8.8, 8.8.4.4) or Cloudflare DNS (1.1.1.1) for better stability.
• Regularly clear DNS cache: Schedule periodic flushing to avoid corruption.
• Keep network drivers updated: Outdated drivers can cause connectivity issues.
• Monitor network health: Use tools like ping and nslookup to diagnose DNS problems early.
• Avoid modifying hosts file unnecessarily: Incorrect entries can cause NXDOMAIN errors.