LightAtom

DNS_PROBE_STARTED: How to Fix It

A DNS lookup failed and Chrome began diagnosing it, but the check couldn't finish, typically because the connection or DNS is unstable.

DNS_PROBE_STARTED

Chrome couldn't resolve the site's name and started testing why, but the test itself didn't complete. Your connection or DNS is failing.

Quick checks

  • Reload after a few seconds.
  • Check your Wi-Fi connection and other sites.
  • Disconnect the VPN.

Fixes on Mac

  1. Flush caches and renew

    1. Run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.
    2. Clear chrome://net-internals/#dns.
    3. Renew the DHCP lease in System Settings › Network › Details › TCP/IP.

  2. Use reliable DNS servers

    1. Add 1.1.1.1 and 8.8.8.8 in System Settings › Network › Details › DNS.

Fixes on Windows

  1. Reset network settings

    1. ipconfig /flushdns and netsh winsock reset, then restart.

Other devices

  1. Router

    1. Restart the router and modem.

Still not working?

If the message keeps appearing, your Wi-Fi may be dropping briefly. Try Ethernet, move closer to the router, and run the packet loss test.

See what’s happening

LightAtom's connections view shows domain names on connections as lookups start succeeding.

Frequently asked questions

What is DNS_PROBE_STARTED?

Chrome's status while it investigates a failed DNS lookup. Seeing it as the final error means the investigation couldn't finish, usually because the connection is unstable.

Is DNS_PROBE_STARTED dangerous?

No. It's a connectivity problem, not a security warning.

Why does it only happen on Wi-Fi?

Unstable Wi-Fi drops packets, and DNS over UDP is sensitive to that. Improve the signal or test over Ethernet.

Related errors and tools

Related

LightAtom team

The people who build LightAtom, a network monitor for macOS.