Home › Web & HTTP

DNS_PROBE_FINISHED_NO_INTERNET — how to fix

No internet
Try:
  Checking the network cables, modem, and router
  Reconnecting to Wi-Fi
  Running Windows Network Diagnostics
DNS_PROBE_FINISHED_NO_INTERNET

Quick fix: Check if you're online at all (ping 1.1.1.1). If IPs work but names don't, it's DNS: set DNS to 1.1.1.1 / 8.8.8.8, flush the cache (ipconfig /flushdns on Windows, sudo resolvectl flush-caches on Linux, sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on macOS) and clear Chrome's at chrome://net-internals/#dns. Disable VPN/proxy and restart the router.

What it means

Chrome's DNS_PROBE_* errors come from a lookup failure followed by a diagnostic probe. The NO_INTERNET variant means the probe couldn't reach a DNS server at all, so Chrome concludes there's no connectivity. Related variants:

Start by telling apart "offline" from "DNS broken".

Step 1: are you online?

ping 1.1.1.1          # an IP: no DNS involved
ping example.com      # a name: needs DNS
nslookup example.com 1.1.1.1

Step 2: switch to a public DNS server

ISP and router DNS servers are a frequent cause. Set 1.1.1.1 and 8.8.8.8 (or 9.9.9.9):

nmcli con mod "<connection>" ipv4.dns "1.1.1.1 8.8.8.8" ipv4.ignore-auto-dns yes
nmcli con up "<connection>"

Step 3: flush DNS caches and reset the network stack

Windows (admin Command Prompt):

ipconfig /flushdns
ipconfig /release
ipconfig /renew
netsh winsock reset
netsh int ip reset

Reboot after the netsh resets.

macOS:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Linux with systemd-resolved:

sudo resolvectl flush-caches
resolvectl status

Step 4: Chrome-specific checks

Step 5: VPN, firewall and security software

A disconnected or half-connected VPN often leaves DNS pointing to an unreachable server. Disconnect it fully or reinstall its network adapter. Antivirus "web shields" and firewalls can block DNS; temporarily disable them to test.

Step 6: hosts file and adapters

Check the hosts file for unexpected entries: C:\Windows\System32\drivers\etc\hosts or /etc/hosts. On Windows, outdated Wi-Fi drivers or a power-saving setting on the adapter can drop connectivity; update the driver, or in Device Manager uncheck "Allow the computer to turn off this device to save power".

For site owners

If only your domain fails for visitors with NXDOMAIN, the DNS records are the problem: check them with dig +trace yourdomain.com and confirm the nameservers at your registrar.

Last updated 2026-11-18.