Resolving "DNS_PROBE_FINISHED_NXDOMAIN" When Connecting to Remote Servers
What Does DNS_PROBE_FINISHED_NXDOMAIN Mean?
DNS_PROBE_FINISHED_NXDOMAIN means "Non-Existent Domain" — your DNS resolver returned an NXDOMAIN response, indicating it cannot find any DNS record for the domain or hostname you're trying to reach. This is almost always a client-side DNS issue (stale cache, wrong resolver, corrupted hosts file) rather than the remote server actually being down — though genuine DNS propagation delays or misconfigured server DNS records can also cause it.
Quick Diagnostic Table
| Scenario | Likely Cause | Fix |
|---|---|---|
| Only on your device | Stale DNS cache | Flush DNS cache |
| Only on your network | ISP DNS resolver issue | Switch to 1.1.1.1 or 8.8.8.8 |
| After domain migration | DNS propagation (up to 48h) | Wait or use dig to check TTL |
| After hosts file edit | Incorrect hosts file entry | Clean up /etc/hosts |
| Only in browser | Browser DNS-over-HTTPS conflict | Disable DoH or change DoH provider |
How to Fix DNS_PROBE_FINISHED_NXDOMAIN
Fix 1 — Flush Your DNS Cache
- Windows: Open Command Prompt as Admin and run
ipconfig /flushdns - macOS: Run
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Linux: Run
sudo systemd-resolve --flush-caches
Retest the connection immediately after flushing before applying other fixes.
Fix 2 — Switch to a Public DNS Resolver
Open Network Adapter Settings → IPv4 Properties and set:
- Preferred DNS:
1.1.1.1(Cloudflare) or8.8.8.8(Google) - Alternate DNS:
1.0.0.1or8.8.4.4
Save, then run ipconfig /flushdns again to force use of the new resolver.
Fix 3 — Inspect the Hosts File
Open the hosts file:
- Windows:
C:\Windows\System32\drivers\etc\hosts - macOS/Linux:
/etc/hosts
Look for any entries pointing your target domain to 0.0.0.0 or an incorrect IP — these override DNS and cause NXDOMAIN. Delete incorrect lines and save.
Fix 4 — Release and Renew IP Address
Open Command Prompt as Administrator and run:
ipconfig /release then ipconfig /renew. This forces your NIC to request a fresh DHCP lease and new DNS server assignment from your router.
Fix 5 — Verify DNS with nslookup
Run nslookup yourdomain.com 8.8.8.8 — this queries Google DNS directly. If it resolves correctly, your default resolver is the problem (Fix 2). If it also returns NXDOMAIN, the domain's DNS records may be misconfigured at the registrar or the domain has expired.
Verification
✓ How to Confirm the Fix Worked
Run nslookup yourdomain.com and confirm it returns a valid IP address without an NXDOMAIN response. Open the URL in your browser — it should load normally. For server-side DNS issues, verify your DNS records propagated using dnschecker.org by checking A, CNAME, and MX records across global resolvers.