DNS_PROBE_STARTED: Chrome's DNS probe is still running

A transient state Chrome shows while it retries a failed lookup with its own probe. If it sticks, the resolver is not answering at all — this usually resolves into NXDOMAIN or a resolver-unreachable failure.

Short answer

A transient state Chrome shows while it retries a failed lookup with its own probe. If it sticks, the resolver is not answering at all — this usually resolves into NXDOMAIN or a resolver-unreachable failure.

What DNS_PROBE_STARTED means

When the first lookup fails, Chrome runs a secondary DNS probe to work out whether the problem is the name or the network. This message is that probe in progress. A page stuck here means the probe itself is not completing.

Causes and fixes, most likely first

1. The configured resolver is not responding. Switch to a public resolver and retry. A non-responding resolver is far more common than a broken domain.
2. The network connection dropped mid-lookup. Confirm general connectivity, then reload. Wi-Fi handoffs commonly cause this.
3. A DNS-filtering extension or security tool is delaying lookups. Disable filtering extensions and retry in a private window.

How to stop it happening again

• Monitor DNS response time as well as record content — a resolver that answers slowly degrades every page load.

Check your own domain

An external lookup completes independently of your resolver, so it confirms whether the hostname resolves at all while your own probe is stuck.

Frequently asked questions

Why is DNS_PROBE_STARTED stuck?

Because the probe cannot reach a working resolver. Switch to a public DNS server and the state usually resolves immediately.