DNS & Resolution
6 min read
How to Fix DNS_PROBE_FINISHED_NXDOMAIN Error (7 Proven Methods)
DNS_PROBE_FINISHED_NXDOMAIN indicates that the Domain Name System failed to resolve the website's IP address because the domain does not exist or local DNS resolvers timed out.
Actionable Resolution Steps
1. Flush Local DNS Resolver Cache
Corrupted or outdated DNS entries cause Chrome to report NXDOMAIN even if the site is online. Open Command Prompt as Administrator and run:
On macOS Terminal, run:
ipconfig /flushdnsOn macOS Terminal, run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
2. Switch to Public DNS Resolvers (Google or Cloudflare)
ISP DNS servers often suffer routing outages. Change your IPv4 DNS settings to:
- **Primary DNS:**
1.1.1.1 (Cloudflare) or 8.8.8.8 (Google)
- **Secondary DNS:** 1.0.0.1 or 8.8.4.4
3. Clear Google Chrome Internal Host Cache
Chrome maintains its own independent DNS cache. In Chrome's address bar, type
chrome://net-internals/#dns and click **Clear host cache**.
4. Release and Renew Your Local IP Address
Reset your local DHCP lease by running:
ipconfig /release
ipconfig /renew
5. Verify Domain Health with Our DNS Lookup Tool
Use our [DNS Lookup Tool](/dns-lookup) to query the domain's live A, AAAA, and CNAME records directly from public nameservers. If no records appear, the domain registration has expired or DNS records were deleted by the owner.
6. Reset Winsock & TCP/IP Stack
Reset the Windows socket network catalog:
netsh winsock reset
netsh int ip reset
Restart your computer afterwards.
7. Check the Windows Hosts File for Hijacked Entries
Check
C:\Windows\System32\drivers\etc\hosts using Notepad. If the domain is mapped to 127.0.0.1 or 0.0.0.0, remove the line and save.
Still experiencing connection drops?
Run a diagnostic trace on your active network adapter using our suite of real-time diagnostic tools: