DNS_PROBE_FINISHED_NO_INTERNET

What’s actually happening

Every site fails, not one, and Chrome's own DNS probe came back unable to reach any resolver at all. This is a connectivity-layer problem, not the target domain's records. The usual culprits are a dropped Wi-Fi/Ethernet link, a crashed local DNS client service, a VPN that injected a resolver and then died, or a router whose DNS cache got wedged. The site you were aiming at is almost never the issue.

Common causes

• The network link is actually down — Wi-Fi dropped, cable unplugged, captive portal not yet passed
• The local DNS client/stub resolver crashed or hung (Windows 'DNS Client', systemd-resolved, macOS mDNSResponder)
• A VPN injected a DNS server and then disconnected, leaving the system pointed at a resolver that's gone
• The router's DNS forwarder or cache is wedged and answering nothing
• Adapter set to a static DNS server that's now unreachable

How to fix it

1. Prove whether you have a network at allPing a raw IP that skips DNS: ping 1.1.1.1. If that fails too, it's pure connectivity — reconnect Wi-Fi, replug the cable, finish the captive-portal login. If the IP ping works but names don't, it's DNS specifically and you move to the next steps.
2. Restart the local DNS clientWindows: net stop dnscache && net start dnscache (or restart 'DNS Client' in services.msc). Linux: sudo systemctl restart systemd-resolved. macOS: sudo killall -HUP mDNSResponder. A hung stub resolver makes every lookup fail with the box otherwise online.
3. Flush DNS and renew the leaseipconfig /flushdns then ipconfig /release && ipconfig /renew on Windows; on macOS sudo dscacheutil -flushcache plus toggling the interface. This clears a poisoned cache and pulls fresh DHCP-provided DNS.
4. Point at a public resolverSet the adapter's DNS to 1.1.1.1 and 8.8.8.8. If a dead VPN-injected or stale static server was the problem, this gets you resolving again immediately.
5. Power-cycle the routerIf multiple devices on the LAN show it, the router's DNS forwarder is likely wedged. Reboot it (full 30-second power-off) to clear its cache and re-establish upstream DNS.