Chrome: No internet — DNS_PROBE_FINISHED_NO_INTERNET (DNS probe finished, no internet)
Chrome’s built-in DNS probe could not reach any DNS server, so the device effectively has no working internet or DNS.
DNS probe finished no internet Meaning
Like ERR_INTERNET_DISCONNECTED, but specifically after a DNS lookup failed and the probe confirmed nothing answers. Common with a router that lost its uplink, a VPN or firewall blocking DNS (port 53), or wrong DNS server settings.
Common causes
- Router/ISP outage or cable unplugged
- DNS server addresses wrong or unreachable
- Firewall/VPN blocking DNS traffic
- Corrupted network stack
- IPv6-only DNS configured on an IPv4 network
⚡ Quick fix
- Check the connection and restart the router
- Set DNS to 1.1.1.1 and 8.8.8.8
- Flush DNS and reset the network stack
Detailed fix by platform
Windows
ipconfig /flushdns,netsh winsock reset, then set DNS in Adapter properties → IPv4 → Use the following DNS server addresses
macOS
- System Settings → Network → Details → DNS: add 1.1.1.1 and 8.8.8.8
Linux
resolvectl statusandping -c1 1.1.1.1(connectivity) vsping -c1 example.com(DNS)
How to diagnose
- Connectivity — Does ping 1.1.1.1 work?
- DNS — Does nslookup work with 8.8.8.8?
- Network — Other devices online?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
Most viewed in Browser
Other ways to find it
Where this error sits
Origin: On your device. Errors that are often confused with or caused by this one (click to open):
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
💬 What worked for others
No tips yet — did something else fix this for you?
Share what worked for you
Tips are checked by an editor before they appear. Links are removed.
Report a correction or suggest an improvement
Last updated 15 Oct 2026