DNS_PROBE_FINISHED_NXDOMAIN in Chrome? Fix the DNS Lookup (Not the Website)

Chrome can’t open a site and shows DNS_PROBE_FINISHED_NXDOMAIN (sometimes “This site can’t be reached — server IP address could not be found”).

What it means: DNS — the system that turns example.com into an IP address — couldn’t resolve the name. It’s a lookup problem on your side or your DNS provider, not the website being down (usually). So fix the resolver.

Fix 1: Flush the DNS cache

Admin Command Prompt:

ipconfig /flushdns

A stale/poisoned cache entry is the most common cause. Reload the page after.

Fix 2: Restart the DNS Client service

Win + R → services.msc → DNS Client (Dnscache) → Restart (or set Automatic and Start). Then retry.

Fix 3: Switch to a public DNS resolver

If your ISP’s DNS is flaky:

1. Settings → Network & internet → your adapter → Edit DNS settings → Manual → IPv4 on.
2. Set DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 / 8.8.4.4 (Google). Save and reload.

Fix 4: Renew your IP and reset the stack

ipconfig /release
ipconfig /renew
ipconfig /flushdns

For a full reset (after VPN/AV removal), see reset TCP/IP & Winsock.

Fix 5: Rule out the browser/VPN

• Try Incognito and another browser — if all fail, it’s DNS (above), not Chrome.
• Disable any VPN/proxy; a dead VPN tunnel breaks DNS resolution.

FAQ

Only one site gives NXDOMAIN? That domain may not exist / be mistyped, or your DNS hasn’t picked up a recent change — flush DNS (Fix 1) and double-check the address.

Everything fails to resolve? Your resolver is the issue — switch DNS (Fix 3). If the PC has no connection at all, see Wi-Fi connected but no internet.

Sources: Google Chrome Help — Get help with common error messages in Chrome