Techi CAD

Upgrade Techi in You

DNS_PROBE_FINISHED_NO_INTERNET: 8 Chrome Fixes

Curtis Ogden015 mins
DNS_PROBE_FINISHED_NO_INTERNET: 8 Chrome Fixes

Chrome greets you with DNS_PROBE_FINISHED_NO_INTERNET — no page loads, every site fails, and your browser insists there is no internet even though your Wi-Fi icon looks fine. This error means Chrome tried to translate website names into IP addresses (the DNS lookup step) and the whole process failed. The fix depends on which layer broke: your router, your DNS servers, or your computer’s network stack. These eight fixes walk the layers in order. If Chrome loads some pages but drops connections mid-load, our ERR_CONNECTION_RESET guide covers that instead.

What Causes the DNS_PROBE_FINISHED_NO_INTERNET Error?

Every website visit starts with a DNS lookup: turning “example.com” into a numeric IP address. When that lookup cannot complete at all, Chrome reports DNS_PROBE_FINISHED_NO_INTERNET. The most common cause is also the most mundane — your router has lost its upstream connection or its DNS relay has wedged, so no lookup can get through even though your PC still shows “connected” to Wi-Fi.

The next layer is the DNS servers themselves. By default you use your ISP’s DNS servers, and when they go down or start returning garbage, every lookup fails at once. Corrupted DNS cache entries on your own PC cause a similar total failure: Windows stores recent lookups, and if that cache corrupts, Chrome cannot resolve anything. VPNs and proxy servers insert themselves into the lookup path too, and a misconfigured one breaks DNS for the whole system.

Finally, the network adapter or its drivers can be at fault — a driver crash or a corrupted TCP/IP stack means lookups never even leave your computer. The fixes below test each layer from the outside in, so you find the broken one fast.

How to Fix the DNS_PROBE_FINISHED_NO_INTERNET Error

Quick triage first: check whether other devices on the same network can browse. If they can, the problem is your computer (start at fix 3). If nothing can browse, start at fix 1.

1. Restart Your Router and Modem

A router whose DNS relay has crashed produces exactly this error on every connected device. A full power cycle is the fastest cure.

  1. Unplug your router and modem from power and wait a full 60 seconds.
  2. Plug the modem back in first and wait for its lights to stabilize.
  3. Plug the router back in, wait for your devices to reconnect, and retry Chrome.
  4. If browsing works now, the router’s DNS relay was the problem — consider a firmware update (fix 8) so it does not recur.

2. Switch to a Public DNS Server

If your ISP’s DNS servers are down or misbehaving, bypassing them entirely fixes the error immediately. Google’s and Cloudflare’s public DNS servers are free, fast, and reliable.

  1. Open Settings > Network & Internet, click your connection, and open its properties.
  2. Under DNS settings, change from Automatic to Manual and enable IPv4.
  3. Enter 8.8.8.8 as preferred DNS and 8.8.4.4 as alternate (Google), or 1.1.1.1 and 1.0.0.1 (Cloudflare).
  4. Save, then retry Chrome. If pages load, your ISP’s DNS was the culprit.

3. Flush the DNS Cache

A corrupted local DNS cache poisons every lookup Chrome attempts. Flushing it forces Windows to re-resolve everything from scratch.

  1. Click Start, type cmd, right-click Command Prompt, and choose Run as administrator.
  2. Type ipconfig /flushdns and press Enter. Confirm you see “Successfully flushed the DNS Resolver Cache.”
  3. Also clear Chrome’s internal DNS cache: type chrome://net-internals/#dns in the address bar and click Clear host cache.
  4. Restart Chrome and test.

4. Disable VPN and Proxy

VPNs and proxies intercept DNS lookups by design. When they malfunction, DNS breaks system-wide — which is exactly what this error reports.

  1. Fully exit your VPN application (not just disconnect — quit the app) and retry Chrome.
  2. Open Settings > Network & Internet > Proxy and disable any proxy server that your network does not require.
  3. In Chrome, check Settings > System > Open your computer’s proxy settings for anything unexpected.
  4. If the VPN was responsible, reconnect using a different server or enable split tunneling so DNS goes direct.

5. Reset the Network Adapter and TCP/IP Stack

When DNS fails on your PC but other devices are fine, Windows’ networking components are the suspect. These commands reset them to a clean default state.

  1. Open an elevated Command Prompt (Start > type cmd > right-click > Run as administrator).
  2. Run these commands one at a time, pressing Enter after each:
    netsh winsock reset,
    netsh int ip reset,
    ipconfig /release,
    ipconfig /renew,
    ipconfig /flushdns.
  3. Restart your computer.
  4. Alternatively, use Settings > Network & Internet > Advanced network settings > Network reset for the same effect through the GUI.

6. Check Firewall and Antivirus DNS Filtering

Some security suites filter DNS traffic and can block all lookups when their filtering engine glitches — producing this exact error.

  1. Temporarily disable your third-party antivirus (keep Windows Defender on) and retry Chrome.
  2. If browsing returns, look in the antivirus settings for DNS protection, web shield, or secure DNS features and reconfigure or disable the problematic one.
  3. Re-enable your antivirus afterward — do not browse unprotected as a permanent workaround.

7. Update or Reinstall the Network Adapter Driver

A crashed or outdated network driver can break DNS resolution while leaving the “connected” icon untouched — one of the more confusing presentations of this error.

  1. Open Device Manager and expand Network adapters.
  2. Right-click your Wi-Fi or Ethernet adapter and choose Update driver > Search automatically for drivers.
  3. If that finds nothing, visit your computer or motherboard manufacturer’s site and install their latest network driver manually.
  4. As a stronger step, choose Uninstall device (do not delete the driver software), restart, and let Windows reinstall the adapter fresh.

8. Update Router Firmware and Test Another Device

If the error affects every device on your network, the router itself is the common factor — outdated firmware with a buggy DNS relay is a known cause.

  1. Log into your router’s admin page (usually 192.168.1.1 or 192.168.0.1) and check for a firmware update.
  2. Install the update and let the router reboot fully.
  3. Test browsing on a second device (phone on Wi-Fi, another laptop). If all devices failed before and work now, the firmware was the cause.
  4. If every device still fails after all eight fixes, call your ISP — describe it as a total DNS failure, which helps their support skip the basic script.

How to Prevent DNS_PROBE_FINISHED_NO_INTERNET

  • Use a reliable public DNS permanently (1.1.1.1 or 8.8.8.8) instead of your ISP’s default — it removes the most common single point of failure.
  • Keep router firmware updated and reboot the router every month or two.
  • Keep network drivers current through your PC manufacturer’s update utility.
  • Configure VPN split tunneling so DNS does not depend on the VPN tunnel staying healthy.
  • Do not stack DNS-filtering tools — one antivirus web shield plus one “secure DNS” app is a conflict waiting to happen.

FAQs

What does DNS_PROBE_FINISHED_NO_INTERNET actually mean?

Chrome attempted its DNS “probe” — the lookup that turns a domain name into an IP address — and the network reported no usable internet for it. It means name resolution failed completely, which is why every site fails rather than just one.

Why does my Wi-Fi show connected if there is “no internet”?

The Wi-Fi icon only shows your connection to the router, not the router’s connection to the internet or the health of DNS. Your PC can be perfectly connected to a router that cannot resolve a single domain name.

Is switching to Google DNS safe?

Yes. Public DNS servers from Google (8.8.8.8) and Cloudflare (1.1.1.1) are widely used, free, and generally faster and more reliable than ISP defaults. Your DNS queries go to them instead of your ISP — a standard, documented configuration also recommended in Google’s Chrome help resources.

Will flushing DNS delete anything important?

No. The DNS cache is temporary by design — flushing it only forces fresh lookups. Browsing may feel marginally slower for a minute while the cache rebuilds, then returns to normal.

How is this different from DNS_PROBE_FINISHED_NXDOMAIN?

NXDOMAIN means DNS worked but the specific domain does not exist (usually a typo). NO_INTERNET means DNS itself failed entirely — a much broader problem affecting all sites, which is why the fixes target your connection and DNS configuration rather than the address you typed.

Conclusion

DNS_PROBE_FINISHED_NO_INTERNET is Chrome telling you that name resolution — the first step of every page load — is completely broken. Restart the router, switch to a public DNS server, flush your caches, and check VPN, proxy, and firewall interference; those steps resolve the large majority of cases. Driver and firmware updates cover the stubborn remainder. Set a reliable public DNS once, and this error becomes one you rarely see again.

Related Fixes

Related News