DNS_PROBE_POSSIBLE in Chrome

What’s actually happening

This one is flaky by nature. A reload often works, then it fails again ten minutes later. Chrome ran its background probe against the configured DNS server and got neither a solid answer nor a hard error — the lookup stalled. You may notice pages loading slowly across the board right before the error appears, which points at a struggling resolver rather than a dead one.

Common causes

• DNS server overloaded or rate-limiting, so queries time out intermittently
• VPN, antivirus, or firewall inspecting and delaying DNS packets
• Weak Wi-Fi or packet loss dropping UDP/53 responses
• ISP resolver flapping under load (common on consumer routers using ISP DNS)
• Chrome's Secure DNS (DoH) pointed at a provider that's slow or partly blocked

How to fix it

1. Retry, then clear Chrome's host cacheReload once. If it sticks, go to chrome://net-internals/#dns, Clear host cache, then reload. A single corrupt or half-cached entry can cause repeat ambiguous probes.
2. Switch to a fast public resolverSet the OS or router DNS to 1.1.1.1 / 8.8.8.8. These respond in single-digit milliseconds and won't rate-limit a household, which removes the timeout source.
3. Toggle or disable Chrome Secure DNSchrome://settings/security — under Use secure DNS, switch the provider or turn it off. A flaky DoH endpoint produces exactly this ambiguous-probe behavior even when plain DNS works.
4. Take VPN/antivirus out of the pathDisconnect the VPN and pause AV web/HTTPS scanning, then retest. If it stabilizes, the tool was adding latency to every lookup — adjust its DNS handling or exclude port 53.
5. Fix the link itselfOn weak Wi-Fi, move closer or switch to 5 GHz/ethernet. Dropped UDP packets to the resolver show up as intermittent DNS_PROBE_POSSIBLE rather than a steady failure.