DNS_PROBE_STARTED
The DNS lookup failed and Chrome is still diagnosing it
Seen in Chrome, Edge
A DNS lookup failed and Chrome started its own test to find out why, but the result was not ready when the error page was shown.
Common causes
- The connection dropped or is unstable, so lookups time out.
- The configured DNS server is slow or not answering.
- A firewall, antivirus or VPN is interfering with DNS.
How to fix it
- Reload the page: the error often changes to a more specific DNS_PROBE_FINISHED_* code.
- Restart the router and flush the DNS cache with `ipconfig /flushdns`.
- Try a known-good resolver such as 1.1.1.1 and disable VPN or security software to test.
Got a different message? Paste it into the error explainer.
Related errors
- DNS_PROBE_FINISHED_NO_INTERNET · DNS failed because there is no internet connection
- DNS_PROBE_FINISHED_BAD_SECURE_CONFIG · Chrome's secure DNS provider is not working
- DNS request timed out. · The DNS server did not answer in time
- DNS_PROBE_FINISHED_NXDOMAIN · The domain name doesn't exist
- SERVFAIL · The DNS server failed to answer
- REFUSED · The DNS server refused the query
- ERR_NAME_NOT_RESOLVED · The browser couldn't resolve the hostname
- DNS_PROBE_FINISHED_BAD_CONFIG · The configured DNS server is not working
- ** server can't find example.com: NXDOMAIN · nslookup says the name doesn't exist
- *** UnKnown can't find · nslookup couldn't name the DNS server, then the lookup failed
- Non-authoritative answer: · The answer came from a resolver cache, which is normal
- ;; connection timed out; no servers could be reached · No DNS server answered the query