DNS_PROBE_FINISHED_NO_INTERNET means Chrome could not reach a DNS resolver at all: its diagnostic probe went out and nothing came back. The fault is almost always your network or device settings, not the website. The usual fixes are flushing the DNS cache with ipconfig /flushdns, rebooting the router, and switching to a public DNS server such as 8.8.8.8 or 1.1.1.1.
This guide explains what Chrome actually checks before showing the error, how it differs from the similar-looking DNS_PROBE_FINISHED_NXDOMAIN, which causes are most common, and how to fix it step by step on Windows, macOS, and Android. It is written for both everyday users and admins troubleshooting client networks.
What DNS_PROBE_FINISHED_NO_INTERNET Means
When a page fails to load, Chrome runs a built-in diagnostic called a DNS probe. The browser sends a test DNS query to the configured resolver — typically your router or your ISP's DNS server — to work out which link in the chain is broken. The suffix in the error name is the verdict of that probe.
The NO_INTERNET verdict means the resolver never answered. From Chrome's point of view, DNS service is unreachable: either there is no working network path, or the DNS server configured on your system is down or blocked. Crucially, the site you were trying to open is irrelevant here — the browser never even got to the stage of asking about a specific domain.
DNS (Domain Name System) is the service that turns a name like example.com into an IP address. Without a reachable resolver the browser has no idea where to connect, so every site fails, not just one. That "everything is down" pattern is the key diagnostic signature of NO_INTERNET.
How It Differs from DNS_PROBE_FINISHED_NXDOMAIN
These two errors are often confused, but they need different fixes. NXDOMAIN is a received answer from a DNS server: "this domain does not exist." NO_INTERNET is the absence of any answer: the server is silent or unreachable. In the first case the network works and the problem lies with the domain name or its DNS records; in the second, the path to the resolver itself is broken. We cover the first error in detail in Fix DNS_PROBE_FINISHED_NXDOMAIN.
| Criterion | DNS_PROBE_FINISHED_NO_INTERNET | DNS_PROBE_FINISHED_NXDOMAIN |
|---|---|---|
| What is broken | The path to the DNS resolver (network, router, OS settings) | The domain itself: the record is missing or wrong |
| DNS server response | No response at all | A definitive answer: "domain does not exist" (NXDOMAIN) |
| Do other sites fail? | Yes, usually all of them | No, only the specific domain |
| Who fixes it | The user, network admin, or ISP | The domain owner (records) or the user (typo, stale cache) |
| Typical remedy | Router reboot, flushdns, switching DNS servers | Checking A/CNAME запись records, waiting for DNS propagation benchmark |
Common Causes of the Error
- Router or ISP resolver is down. The most frequent scenario: the router has hung, or the ISP's DNS resolver is temporarily failing while the internet link itself still works.
- Broken network settings in the OS. A wrong static DNS address, orphaned settings left after switching networks, or a corrupted TCP/IP stack or Winsock catalog on Windows.
- VPN or proxy software. A VPN client replaces your DNS with its own; after the tunnel drops, the system keeps sending queries to an address that is no longer reachable.
- Corrupted DNS cache. Stale or damaged entries in the local cache block new lookups — flushing it helps, see our DNS cache flush guide.
- Firewall or antivirus. Overly strict rules block outgoing UDP/TCP traffic on port 53, so DNS queries never leave the machine.
How to Fix It on Windows, Step by Step
Start with the obvious: power-cycle the router (unplug it for 30 seconds) and check whether the error reproduces on another device on the same network. If everything is down, the router or the ISP is at fault. If only one computer is affected, work through the steps below in an elevated Command Prompt (run as administrator).
Step 1. Flush the DNS Cache
This clears the Windows resolver cache and removes corrupted entries:
ipconfig /flushdnsStep 2. Renew the IP Address and DHCP Settings
The computer re-requests its address and DNS server list from the router, which repairs orphaned settings left over from a previous network:
ipconfig /release ipconfig /renewStep 3. Reset Winsock and the TCP/IP Stack
If the cache and DHCP renewal did not help, reset the network stack — this undoes damage left by VPN clients and "network optimizer" tools. Reboot the computer afterwards:
netsh winsock reset netsh int ip resetStep 4. Disable VPN, Proxy, and Check the Firewall
Turn off any VPN client and remove the proxy under Settings → Network & Internet → Proxy. Then temporarily disable a third-party firewall or antivirus and retry. If the site loads, add DNS traffic (port 53) to the exceptions instead of leaving protection off.
Changing Your DNS Server to a Public Resolver
If your ISP's resolver is unstable, set a public DNS manually: Settings → Network & Internet → Ethernet/Wi-Fi → DNS server assignment → Edit → Manual. Reliable options:
- Google Public DNS: 8.8.8.8 and 8.8.4.4 — the best-known resolver, with DoH/DoT support;
- Cloudflare: 1.1.1.1 and 1.0.0.1 — focused on speed and privacy;
- Yandex DNS: 77.88.8.8 (basic) and 77.88.8.1 — fast servers hosted in Russia, with optional filtering modes.
After switching, run ipconfig /flushdns again so the system stops using stale cached answers.
macOS and Android: Quick Instructions
macOS. Flush the resolver cache in Terminal: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. If needed, change DNS under System Settings → Network → Wi-Fi → Details → DNS and add 8.8.8.8 or 1.1.1.1. Forgetting the Wi-Fi network and rejoining it also helps.
Android. Open Settings → Network & internet → Private DNS and enter dns.google — this enables encrypted DNS on any network. Alternatively, forget the problematic Wi-Fi network and reconnect, or test on mobile data: if the error disappears there, your router is the culprit.
When Your ISP Is to Blame — and How to Prove It
Compare the answers from your ISP's resolver and a public one using nslookup:
nslookup example.com nslookup example.com 8.8.8.8If the first query times out ("DNS request timed out") while the second returns an IP address, the ISP's resolver is down. Switch to a public DNS temporarily and report the outage to your ISP. If both queries stay silent, the problem is closer to home: the router, the cable, or a block on the computer itself. Cases where only some domains fail to resolve are covered in DNS not resolving: causes and fixes.
How to Verify DNS After the Fix
Confirm that resolution has recovered from an independent vantage point: the online DNS records checker shows a domain's A, AAAA, MX, NS, and TXT records as external servers see them — if the records are fine but the site still fails for you, the problem is local. Then test host reachability with the ping and port checker: a stable response confirms the path to the server works.
Useful Sources
- Chromium Network Stack — how Chrome's networking layer and DNS diagnostics work;
- Google Public DNS: Get Started — the official setup guide for 8.8.8.8;
- Yandex DNS — addresses and modes of Yandex's public DNS servers;
- MDN: DNS — a concise explanation of how the Domain Name System works.
Frequently Asked Questions
Why does the error appear only in Chrome while other browsers work?
Chrome runs its own asynchronous DNS resolver with a separate cache, so it can stay stuck on broken entries after the system resolver has already recovered. Open chrome://net-internals/#dns, click "Clear host cache," and restart the browser. If that does not help, the fault really is at the system or network level.
Will reinstalling the browser help?
Almost never. The error describes the state of your network, not damage to Chrome itself: the browser is only reporting that the DNS resolver is unreachable. Reinstalling resets the cache and settings, but you can achieve the same by clearing the browser and system DNS caches in a minute, without losing extensions and saved data.
How is NO_INTERNET different from ERR_NAME_NOT_RESOLVED?
ERR_NAME_NOT_RESOLVED is the generic "name could not be resolved" failure: it appears both when the resolver is unreachable and when a record is missing. NO_INTERNET is the more precise post-probe diagnosis: the resolver is silent. The practical differences in troubleshooting are covered in Fix ERR_NAME_NOT_RESOLVED.
Is it safe to switch DNS to 8.8.8.8 or 1.1.1.1?
Yes. Public resolvers from Google, Cloudflare, and Yandex are a standard replacement for ISP DNS; they handle billions of queries daily and often respond faster. Just note that your queries will pass through the chosen provider, and internal corporate domains (intranet) may stop resolving — on an office network, check the policy with your admin first.
The error comes and goes on its own. What causes that?
Intermittent failures usually point to an overloaded router, unstable Wi-Fi, or a flaky ISP resolver. Set a public DNS, update the router firmware, and observe. If the error hits every device at the same time, log the timestamps and send them to your ISP — that pattern indicates degradation of its DNS infrastructure.
What if nothing helps?
Check the cable and the router's indicator lights, connect directly without the router, and boot into Safe Mode with Networking to rule out third-party software. Create a fresh user profile or scan the system for malware: malicious software sometimes hijacks DNS settings. The last resort is a full Windows network reset.