Google Chrome ERR_DNS_PROBE_FINISHED_NO_INTERNET: How to Fix It

Q: Why does ERR_DNS_PROBE_FINISHED_NO_INTERNET only happen in Chrome and not other browsers?

Chrome has its own internal DNS cache and connection management system that operates independently from your OS and other browsers. If you see this error only in Chrome but Edge or Firefox works fine, the issue is almost certainly Chrome-specific. Try clearing Chrome's internal DNS cache at chrome://net-internals/#dns, flushing socket pools, resetting Chrome settings, or disabling extensions. An extension that intercepts network requests — such as a VPN, proxy, or ad blocker — is a very common cause.

Q: Does ERR_DNS_PROBE_FINISHED_NO_INTERNET mean my internet is completely down?

Not necessarily. It means Chrome specifically could not complete a DNS lookup and concluded there was no internet. Your physical internet connection could be fine but DNS resolution might be broken. A good way to check: try pinging a well-known IP address directly using Command Prompt — type 'ping 8.8.8.8'. If the ping succeeds, your internet connection is alive but DNS is broken, which means changing your DNS servers (Step 4) should fix it. If the ping fails, the internet connection itself is the problem.

Q: Can a VPN cause ERR_DNS_PROBE_FINISHED_NO_INTERNET in Chrome?

Yes, absolutely. VPNs reroute your DNS traffic through their own servers, and if the VPN connection drops, becomes misconfigured, or has DNS leak protection enabled, Chrome may lose the ability to resolve any domain names, triggering this error. Try disconnecting your VPN completely and then testing the connection. If the error disappears without the VPN, the issue is with your VPN's DNS settings. Check your VPN app's settings for a 'DNS leak protection' or 'kill switch' option and try toggling it. Reinstalling the VPN client or switching to a different VPN server can also help.

Q: Why does this error appear on my phone's Chrome app but my Wi-Fi seems fine?

On mobile devices, this error can appear when your phone is connected to Wi-Fi but the Wi-Fi network itself has no internet access — for example, a coffee shop network that requires you to accept terms on a login page first. It can also happen if your phone switches between Wi-Fi and mobile data creating a brief connection drop. Try turning Wi-Fi off and on again, forgetting the network and reconnecting, or switching to mobile data to see if the issue is isolated to that specific Wi-Fi network. Also clear Chrome's cache on your mobile device under Settings > Apps > Chrome > Storage > Clear Cache.

Q: Will resetting my router fix ERR_DNS_PROBE_FINISHED_NO_INTERNET?

Simply restarting (power cycling) your router — unplugging it for 60 seconds — often fixes this error and is always worth trying first. However, performing a full factory reset by pressing the reset button on the router is rarely necessary and should be avoided unless all other steps fail, because it erases your Wi-Fi name, password, and all custom settings, requiring you to reconfigure everything from scratch. A simple restart is almost always sufficient to clear temporary DNS and routing issues in the router.

Abstract

The ERR_DNS_PROBE_FINISHED_NO_INTERNET error in Google Chrome means the browser ran a DNS probe and determined that your device has no active internet connection, or that DNS resolution has completely failed. This is different from a single site being down — it typically means Chrome cannot reach any website at all. The root cause is usually a broken network connection, misconfigured DNS settings, a faulty network adapter driver, or interference from security software.