NetDig›Learn›DNS
DNS5 min read

DNS_PROBE_FINISHED_NXDOMAIN — Causes and Fixes

NXDOMAIN means 'Non-Existent Domain' — the DNS system returned no result for the hostname. Here's how to tell whether it's a site issue or your local DNS config.

What NXDOMAIN Means

NXDOMAIN is a DNS response code meaning the queried domain does not exist in DNS. When Chrome can't resolve a domain, it shows DNS_PROBE_FINISHED_NXDOMAIN. This can mean the site is down, the domain expired, or it's a local DNS issue on your machine.

Step 1: Is It Your Problem or the Site's?

Before troubleshooting your setup, check if anyone else can reach the site. Use the DNS Lookup tool to check if the domain resolves. If it resolves fine here, the problem is local to your machine or network.

If It's Your Machine

Flush your DNS cache:

  • Windows: ipconfig /flushdns in Command Prompt
  • macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
  • Linux: sudo systemctl restart systemd-resolved
  • Chrome: visit chrome://net-internals/#dns → Clear host cache

Try a different DNS resolver: Change your DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google) and retest. If the problem disappears, your ISP's resolver has a stale or missing record.

If the DNS Lookup Also Fails

The domain may have expired, the DNS records may have been deleted, or the nameservers may be misconfigured. Check with a WHOIS lookup to see the domain's expiry date and nameservers. Then do an NS lookup to verify the nameservers are responding.

Common Causes

  • Domain expired — registrar suspended it and removed DNS
  • DNS records accidentally deleted at the registrar or DNS provider
  • Nameservers changed but old records cached by your resolver
  • Hosts file on your machine blocking the domain
  • VPN or proxy intercepting DNS queries
  • Corporate firewall blocking DNS for certain domains

NXDOMAIN (Non-Existent Domain) is a DNS response code meaning no DNS records were found for the queried domain. It's returned by authoritative nameservers when a domain or record doesn't exist.

First check if others can access the site using a DNS lookup tool. If yes, flush your local DNS cache and try a public DNS resolver like 1.1.1.1. If no, the domain's DNS is misconfigured or expired.

Yes. VPNs route DNS queries through their own resolvers, which may not have the same records as your normal resolver. Try disabling the VPN to see if the error resolves.