Articles

Fix DNS_PROBE_FINISHED_NXDOMAIN in Chrome (2026)

April 16, 2026 4 min read

The DNS resolution system gave up on fetching the domain name because it couldn’t find any IP address associated with it.

Common Causes and Fixes for DNS_PROBE_FINISHED_NXDOMAIN:

  1. Incorrect DNS Server Configuration: Your system might be pointing to a DNS server that is down, misconfigured, or simply not authoritative for the domain you’re trying to reach.

    • Diagnosis: On Windows, run ipconfig /all. On macOS/Linux, run scutil --dns. Look for the DNS servers listed under your active network interface.
    • Fix: Manually set your DNS servers to a reliable public provider like Google DNS (8.8.8.8 and 8.8.4.4) or Cloudflare DNS (1.1.1.1 and 1.0.0.1).
      • Windows: Go to Network Connections, right-click your adapter, select Properties, then Internet Protocol Version 4 (TCP/IPv4) Properties. Select "Use the following DNS server addresses."
      • macOS: Go to System Preferences > Network, select your active connection, click Advanced, then DNS. Click the '+' button to add new DNS servers.
      • Linux: This varies by distribution. For systemd-resolved, edit /etc/systemd/resolved.conf and set DNS=8.8.8.8 8.8.4.4. For older systems, edit /etc/resolv.conf.
    • Why it works: This bypasses any potentially faulty local or ISP-provided DNS servers and directs your requests to robust, well-maintained servers that are highly likely to have the correct records.

  2. Local DNS Cache Corruption: Your operating system and browser maintain a local cache of DNS lookups to speed up subsequent requests. If this cache contains stale or incorrect information, it can lead to NXDOMAIN errors.

    • Diagnosis: Try accessing the website from a different device on the same network or from a different network entirely. If it works elsewhere, your local cache is a prime suspect.
    • Fix: Flush your 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: This depends on the DNS caching service. For systemd-resolved, run sudo systemd-resolve --flush-caches. For dnsmasq, run sudo /etc/init.d/dnsmasq restart or sudo service dnsmasq restart.
    • Why it works: This clears out any potentially bad entries, forcing your system to perform a fresh DNS lookup for the domain.

  3. Firewall or Antivirus Interference: Aggressive firewall or antivirus software can sometimes incorrectly flag legitimate DNS requests as malicious, blocking them before they can be resolved.

    • Diagnosis: Temporarily disable your firewall and antivirus software one at a time and try accessing the website. If it works, you’ve found the culprit.
    • Fix: Reconfigure your firewall or antivirus to allow DNS traffic (UDP/TCP port 53) or to whitelist the specific domain or IP address. Consult your software’s documentation for specific instructions.
    • Why it works: This removes the artificial barrier that was preventing DNS resolution from completing.

  4. Router DNS Issues: Your home or office router acts as a DNS forwarder for devices on your network. If the router’s DNS settings are incorrect or its DNS cache is corrupted, it can affect all devices connected to it.

    • Diagnosis: Try accessing the website using a mobile device connected via cellular data (bypassing your home network). If it works there, your router is suspect.
    • Fix: Log into your router’s administration interface (usually via an IP address like 192.168.1.1 or 192.168.0.1) and check its DNS settings. You can either set the router to use public DNS servers (like 8.8.8.8) or configure individual devices to use public DNS servers directly, bypassing the router’s forwarding. Rebooting the router can also sometimes clear its cache.
    • Why it works: This ensures that the DNS requests originating from your local network are being handled by a reliable server.

  5. Hosts File Misconfiguration: The hosts file on your operating system allows you to manually map domain names to IP addresses. An incorrect or outdated entry in this file can override normal DNS resolution.

    • Diagnosis: Check your hosts file for any entries related to the domain you’re trying to access.
    • Fix:
      • Windows: C:\Windows\System32\drivers\etc\hosts
      • macOS/Linux: /etc/hosts Open the file with a text editor (as administrator/root) and remove any lines that map the problematic domain to an IP address. Ensure there are no typos or accidental entries.
    • Why it works: By removing the manual override, you allow your system to query DNS servers for the correct IP address.

  6. Domain Expired or Incorrectly Registered: The NXDOMAIN error literally means "Non-Existent Domain." This could be because the domain name you’re trying to reach has genuinely expired, has been deleted, or was never registered in the first place.

    • Diagnosis: Perform a WHOIS lookup for the domain. Websites like whois.com or lookup.icann.org can provide this information. Check the registration status and expiry date.
    • Fix: If the domain is yours and expired, renew it through your domain registrar. If it’s a website you’re trying to access and it’s showing as expired or deleted, there’s nothing you can do except wait to see if it’s re-registered or contact the owner if possible.
    • Why it works: This addresses the root cause if the domain itself is no longer valid or resolvable on the internet.

After fixing these, you might encounter ERR_CONNECTION_REFUSED if the server is online but not listening on the expected port.

Want structured learning?

Take the full Dns course →