How to Fix DNS Probe Finished No Internet in Chrome

If Google Chrome suddenly shows “DNS_PROBE_FINISHED_NO_INTERNET� while other apps still work, your browser can’t resolve website names into IP addresses. This guide walks through the most common fixes, from clearing the DNS cache to changing your DNS server, so you can get back online quickly.

What You’ll Need

Administrator access to your computer (to run command prompt or terminal commands)
Your router’s login details (usually printed on a sticker on the device)
About 10–15 minutes of time

Step-by-Step

Check if the internet is actually down. Open another browser (Edge, Firefox, Safari) or try a different device on the same Wi-Fi. If nothing loads, the problem is your network, not Chrome. Restart your router by unplugging it for 30 seconds and plugging it back in.
Restart Chrome completely. Close all Chrome windows, then open Task Manager (Ctrl+Shift+Esc on Windows, Cmd+Option+Esc on Mac) and end any remaining Chrome processes. Reopen Chrome and try the site again.
Clear Chrome’s DNS cache. In Chrome’s address bar, type chrome://net-internals/#dns and press Enter. Click the “Clear host cache� button. Then go to chrome://net-internals/#sockets and click “Flush socket pools.� Restart Chrome.
Flush your operating system’s DNS cache.
- Windows: Open Command Prompt as Administrator (search “cmd,� right-click, “Run as administrator�), type ipconfig /flushdns, and press Enter.
- Mac: Open Terminal and type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then press Enter and enter your password.
- Linux: Depending on your distro, try sudo systemd-resolve --flush-caches or sudo resolvectl flush-caches.
Renew your IP address. In the same Command Prompt (Windows), type ipconfig /release, press Enter, then ipconfig /renew, and press Enter. On Mac, go to System Settings → Network → Wi-Fi → Details → TCP/IP → “Renew DHCP Lease.�
Disable Chrome’s built-in DNS resolver. Go to Chrome Settings → Privacy and security → Security. Scroll to “Use secure DNS� and toggle it off. If it’s already off, turn it on and choose a provider like Cloudflare (1.1.1.1) or Google (8.8.8.8).
Change your DNS server to a public one.
- Windows: Control Panel → Network and Sharing Center → Change adapter settings → right-click your connection → Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties → “Use the following DNS server addresses.� Enter 8.8.8.8 and 8.8.4.4, click OK.
- Mac: System Settings → Network → Wi-Fi → Details → DNS → click “+� and add 8.8.8.8 and 8.8.4.4.
- Router: Log into your router’s admin page (usually 192.168.1.1 or 192.168.0.1), find the DNS settings under WAN or Internet, and set the same addresses.
Reset Chrome’s network settings. In Chrome, go to Settings → Advanced → “Reset and clean up� → “Restore settings to their original defaults.� This disables extensions and clears temporary data, which often fixes DNS conflicts.
Disable proxy or VPN. If you use a VPN, turn it off and test. In Windows, go to Settings → Network & Internet → Proxy and ensure “Use a proxy server� is off. On Mac, System Settings → Network → Proxies and uncheck any active proxies.
Run Windows network diagnostics. Type “Network troubleshooter� in the Start menu and run it. It may automatically detect and repair a misconfigured network adapter.

Common Mistakes

Only clearing Chrome’s cache, not the system cache. Chrome’s internal cache and your OS’s DNS cache are separate; you need to flush both.
Typing commands without admin rights. The ipconfig /flushdns command fails silently if you don’t run Command Prompt as Administrator.
Changing DNS on the wrong adapter. If you have both Wi-Fi and Ethernet, make sure you edit the one you’re actually using.
Forgetting to restart after changing DNS. Some changes only take effect after a reboot or at least a browser restart.
Skipping the router restart. A stale router cache can cause this error even when your computer’s settings are fine.

Tips

Try a different network. Connect your computer to your phone’s mobile hotspot. If Chrome works there, the problem is your home network or router, not your device.
Keep your router firmware updated. Outdated router software can cause intermittent DNS failures.
Use a reliable DNS provider. Google (8.8.8.8 / 8.8.4.4) and Cloudflare (1.1.1.1 / 1.0.0.1) are free and generally faster than ISP defaults.
Check for interference from antivirus. Some security suites filter DNS traffic. Temporarily disable your antivirus firewall to see if it’s blocking Chrome.
Use Chrome’s incognito mode as a test. If the error disappears in incognito, an extension is likely the culprit.

Troubleshooting

If the error persists after all the steps above, try these additional checks:

Check the date and time. Wrong system time breaks HTTPS connections and DNS verification. Go to your OS date/time settings and enable automatic time sync.
Disable IPv6 temporarily. In Windows, go to Network adapter properties and uncheck “Internet Protocol Version 6 (TCP/IPv6).� Some routers mishandle IPv6 DNS queries. Re-enable it after testing.
Check Windows hosts file. Open Notepad as Administrator, then open C:\Windows\System32\drivers\etc\hosts. Look for any lines that aren’t commented out (don’t start with #). If you see entries for sites you’re trying to visit, delete them and save.
Run a DNS lookup test. In Command Prompt, type nslookup google.com. If it returns an IP address, your DNS is working; if it times out, your DNS server is unreachable.
Reset the network stack. In an elevated Command Prompt, run these commands one by one: netsh winsock reset, netsh int ip reset, then restart your computer.
Update your network drivers. Go to Device Manager → Network adapters → right-click your adapter → “Update driver.�
Try a different Chrome profile. Create a new user profile (click your avatar → “Add� → “Add profile�). If the error goes away, your main profile’s settings are corrupted.

Frequently Asked Questions

Q: What does “DNS_PROBE_FINISHED_NO_INTERNET� actually mean?
A: Chrome sent a DNS query to translate a domain name into an IP address, but the DNS server never responded. Chrome interprets this as “no internet,� even if other network functions work.

Q: Why does this happen on one device but not others?
A: The device’s local DNS cache is corrupted, its DNS settings point to a dead server, or its network adapter has a problem. Other devices may use different DNS settings or have a fresh cache.

Q: Will changing my DNS server affect my internet speed?
A: Usually yes, in a positive way. Public DNS servers like Google and Cloudflare are often faster than ISP defaults, especially for the first lookup of a site. The actual download speed is unaffected.

Q: Is it safe to use public DNS like 8.8.8.8?
A: Yes. Google and Cloudflare run public DNS services that are widely used and trusted. Your ISP can still see your traffic, but DNS queries go to the public server instead.

Q: How often should I flush my DNS cache?
A: Only when you have connection issues or after changing DNS servers. Flushing daily is unnecessary and can slightly slow down browsing since your device has to re-resolve every domain.

Q: Can this error be caused by malware?
A: Rarely, but some malware modifies DNS settings to redirect traffic. If the error persists after a full reset, run a malware scan with Windows Defender or a reputable third-party tool.

General steps for current mainstream versions; menus can differ by device and version. See the disclaimer or report an error.

More in this bed

The whole Tech How-To bed →