DNS_PROBE_POSSIBLE: What It Means and How to Fix It
Appears on: Chrome, Edge. DNS_PROBE_POSSIBLE means Chrome suspects a DNS problem but is not certain. It is a softer version of DNS_PROBE_FINISHED_NO_INTERNET and usually points to a slow or misconfigured DNS server.
What DNS_PROBE_POSSIBLE actually means
Chrome ran a DNS probe and got an ambiguous result — possibly a timeout or partial response — rather than a clean success or outright failure. The page may load on retry, or the DNS issue may be consistent. It is almost always a DNS resolver problem, not a site being down.
Most likely causes (ranked)
- Your ISP's DNS server is slow, overloaded, or returning inconsistent results
- DNS settings were recently changed and have not propagated
- A VPN or security software is intercepting DNS queries
- Your router's DNS cache is stale
- Chrome's internal DNS cache has a bad entry
How to fix DNS_PROBE_POSSIBLE
Step 1: Clear Chrome's DNS cache
Navigate to chrome://net-internals/#dns and click 'Clear host cache'. This forces Chrome to re-query your DNS server fresh.
Step 2: Flush the OS DNS cache
On Windows: 'ipconfig /flushdns' in Command Prompt. On macOS: 'sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder'.
Step 3: Switch to a public DNS server
Change your router or OS DNS to 1.1.1.1 (Cloudflare) or 8.8.8.8 (Google). ISP DNS servers are the most common cause of this intermittent error.
Step 4: Restart the router
A router restart clears its DNS cache and re-establishes the upstream DNS connection.
Step 5: Try the page in an incognito window
If the page loads in incognito, a browser extension (ad blocker, privacy tool) is interfering with DNS resolution. Disable extensions one by one to identify the culprit.
Still not fixed? Rule out your connection
If the steps above did not clear the error, the next step is verifying the underlying internet connection is healthy. Run a speed test — if download, upload, and ping come back normal, the error is specific to one site or browser state. If the speed test also fails or shows packet loss, the problem is at the network or ISP layer.
Frequently Asked Questions
What is the difference between DNS_PROBE_POSSIBLE and DNS_PROBE_FINISHED_NO_INTERNET?
DNS_PROBE_FINISHED_NO_INTERNET is a definitive failure — Chrome confirmed no internet. DNS_PROBE_POSSIBLE is tentative — Chrome suspects a DNS issue but could not confirm. Both point to DNS or network problems, but PROBE_POSSIBLE often resolves on retry.
Why does DNS_PROBE_POSSIBLE happen on only some websites?
Different domains are handled by different DNS servers (authoritative nameservers). A specific domain may have a slow nameserver that times out intermittently. Switching to a faster public DNS resolver like Cloudflare (1.1.1.1) usually eliminates the inconsistency.
Can a VPN cause DNS_PROBE_POSSIBLE?
Yes — VPNs redirect DNS queries through their own resolver. If the VPN's DNS server is slow or filtering the domain you are trying to reach, Chrome may see an ambiguous response and show this error.
Related Guides
Internet Keeps Dropping
Diagnose the physical and ISP-side causes of unstable connections.
Wi-Fi Connected But No Internet
The full playbook for the most common error of all.
Which DNS Should You Use?
1.1.1.1, 8.8.8.8, or your ISP — which one actually wins.
What Is Packet Loss?
How to detect and fix the invisible network problem that causes most mid-session errors.