DNS_PROBE_FINISHED_NO_INTERNET: What It Means and How to Fix It
Appears on: Chrome, Edge, Brave. DNS_PROBE_FINISHED_NO_INTERNET means your browser could not reach a DNS server. The fix is usually to flush DNS, switch to a public resolver like 1.1.1.1, or restart your router.
What DNS_PROBE_FINISHED_NO_INTERNET actually means
The browser tried to look up a domain, asked the DNS server configured on your machine, and got nothing back — or the OS reports no working internet connection at all. It is almost always a DNS or local-network issue, not the website being down.
Most likely causes (ranked)
- Your router's DNS settings are stale or pointing to a dead resolver
- Your ISP's DNS server is temporarily unreachable
- A VPN or corporate proxy is blocking DNS queries
- Windows / macOS has a corrupt DNS cache from a recent network change
- Antivirus or firewall software is intercepting DNS
How to fix DNS_PROBE_FINISHED_NO_INTERNET
Step 1: Flush the DNS cache
On Windows run 'ipconfig /flushdns' in Command Prompt. On macOS run 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder'. This clears stale lookups.
Step 2: Switch to a public DNS
In your router or OS settings, set DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google). These are faster and more reliable than most ISP resolvers.
Step 3: Restart modem and router
Unplug both for 60 seconds, plug the modem in first, wait for it to fully boot, then plug in the router. Half of DNS issues clear on a cold boot.
Step 4: Disable VPN or proxy temporarily
If you are on a VPN or corporate network, disconnect and try again. DNS leaks and split-tunnel misconfiguration are a common cause.
Step 5: Reset the network stack
On Windows run 'netsh winsock reset' and 'netsh int ip reset' as admin, then reboot. This clears accumulated network-config corruption.
Still not fixed? Rule out your connection
If the steps above did not clear the error, the next step is verifying the underlying internet connection is healthy. Run a speed test — if download, upload, and ping come back normal, the error is specific to one site or browser state. If the speed test also fails or shows packet loss, the problem is at the network or ISP layer.
Frequently Asked Questions
Is DNS_PROBE_FINISHED_NO_INTERNET an ISP problem?
Usually no — it is almost always a local DNS or router issue. But if a speed test also fails and no device on your network can load anything, it may be an ISP outage. Run a speed test from a mobile device on cellular to confirm.
Why does DNS_PROBE_FINISHED_NO_INTERNET only happen in Chrome?
Chrome has its own DNS cache layered on top of the OS. Clearing it via chrome://net-internals/#dns often fixes the error while other browsers work.
Does changing DNS slow down my internet?
No — public DNS servers like 1.1.1.1 are typically faster than ISP defaults. DNS affects how quickly names resolve, not bandwidth. A speed test will confirm nothing has changed.
Related Guides
Internet Keeps Dropping
Diagnose the physical and ISP-side causes of unstable connections.
Wi-Fi Connected But No Internet
The full playbook for the most common error of all.
Which DNS Should You Use?
1.1.1.1, 8.8.8.8, or your ISP — which one actually wins.
What Is Packet Loss?
How to detect and fix the invisible network problem that causes most mid-session errors.