DNS_PROBE_STARTED: What It Means and How to Fix It

You’re browsing normally, then a page refuses to load and Chrome shows a cryptic code at the bottom: DNS_PROBE_STARTED. It looks like something broke mid-process — and in a sense it did: your browser began a DNS check to translate the site’s name into an IP address, and that check couldn’t finish. The good news is that it’s almost always a local, quickly fixable problem — your DNS settings, network adapter, router, or security software — not the website.

This guide explains what the error means, why it happens, and every fix that works, in order — for Windows, macOS, and Android, from the 30-second quick wins to a full network reset.

What does DNS_PROBE_STARTED mean?

When you open a site, your browser runs a DNS probe — a lookup that translates the domain name (like copahost.com) into the IP address it needs to connect. DNS_PROBE_STARTED is Chrome’s way of saying that probe began but didn’t complete: the lookup started, then stalled or failed before returning an answer, so the page can’t load. (For the fundamentals of how this lookup works, see what DNS is and how it works.)

Because the probe is a local step — run by your device against your configured DNS server — the cause is almost always on your side: a misconfigured or unreachable DNS server, a network-adapter glitch, a router that needs a restart, or security software blocking the DNS request. The error shows up most in Google Chrome, but Edge, Brave, and Android browsers hit the same underlying issue.

What causes DNS_PROBE_STARTED?

The common triggers, all local:

• DNS server down or misconfigured. Your ISP’s resolver is unreachable, or your DNS settings point somewhere invalid.
• Stale or corrupted DNS cache. An old cached entry stops fresh lookups from completing.
• Network adapter or router glitch. A temporary fault in your adapter or router interrupts the probe.
• Firewall or antivirus blocking DNS. Security software intercepts the DNS request before it resolves.
• Outdated network driver. A buggy or old adapter driver disrupts name resolution.
• Chrome’s own DNS cache. A corrupted entry in Chrome’s separate cache causes the error even when the OS is fine.

How to fix DNS_PROBE_STARTED

Work through these in order — quickest and most common first. Re-test the page after each step.

1. Restart your router and reload

The fastest fix. Your router keeps its own DNS state, and a brief glitch can stall the probe. Power off the router (and modem) for 30 seconds, plug it back in, let it fully reconnect, and reload the page. This clears a large share of cases and costs nothing.

2. Flush your DNS cache

A stale or corrupted local cache is a leading cause. Clearing it forces a fresh lookup. Full per-platform guide: how to flush DNS. The essentials:

3. Clear Chrome’s own DNS cache

Chrome keeps a DNS cache separate from your operating system, so it can trigger the error even when the OS cache is clean. In the address bar, go to chrome://net-internals/#dns and click Clear host cache. Then reload the page. (The same page exists in Edge at edge://net-internals/#dns.)

4. Switch to a public DNS server

If your ISP’s resolver is down or misconfigured — a common cause — pointing your device at a public resolver often fixes the error immediately. Use Cloudflare (1.1.1.1 / 1.0.0.1) or Google (8.8.8.8 / 8.8.4.4). Full step-by-step for every platform is in our guide to the best DNS servers and how to change them. Quick version:

• Windows: Settings → Network & Internet → your connection → DNS server assignment → Edit → Manual → enter the addresses.
• macOS: System Settings → Network → your connection → Details → DNS → + → add the addresses.
• Android: Settings → Network & internet → Private DNS → enter a provider hostname like dns.google or 1dot1dot1dot1.cloudflare-dns.com.

5. Renew your IP address (Windows)

A stale IP lease can stall the probe. In Command Prompt (as administrator), run:

6. Temporarily disable firewall / antivirus

Security software can block the DNS request before it resolves. Turn off your firewall or antivirus briefly to test — if the page loads, re-enable it and adjust its settings (allow the DNS request) rather than leaving protection off.

7. Update your network adapter driver (Windows)

An outdated or corrupted network driver can disrupt name resolution. In Device Manager → Network adapters → right-click your adapter → Update driver. Restart and test. If updating doesn’t help, uninstalling and reinstalling the driver can clear a corrupted state.

8. Reset the network stack

If nothing above works, reset the network configuration to defaults. In Command Prompt (as administrator), run, then reboot:

On Windows you can also use Settings → Network & Internet → Advanced network settings → Network reset.

Is it ever the website’s fault?

Rarely. DNS_PROBE_STARTED is a local probe failure, so the fix is almost always on your device or network. If the site genuinely fails for everyone — which you can check with a “is it down” tool — the issue is more likely on the site’s side (its DNS records or nameservers), but that usually surfaces as a different error, not DNS_PROBE_STARTED. If you run the site and suspect its DNS, verify the records and allow for DNS propagation after any change.

Frequently asked questions

What does DNS_PROBE_STARTED mean?
It means your browser started a DNS lookup to translate a website’s name into an IP address, but the lookup couldn’t complete. The probe began and then stalled or failed before returning an answer, so the page can’t load. It’s almost always a local issue — your DNS settings, network adapter, router, or security software — not the website.

How do I fix DNS_PROBE_STARTED?
Start with the quick fixes: restart your router, flush your DNS cache (ipconfig /flushdns), clear Chrome’s host cache at chrome://net-internals/#dns, and switch to a public DNS like Cloudflare (1.1.1.1) or Google (8.8.8.8). If those don’t work, renew your IP, disable firewall/antivirus briefly, update your network driver, or reset the network stack.

Is DNS_PROBE_STARTED a virus?
No. It’s a standard network error, not malware. It simply means a DNS lookup couldn’t complete. In rare cases, aggressive antivirus or a VPN can block DNS requests and trigger it, which is why temporarily disabling security software is one of the troubleshooting steps.

What’s the difference between DNS_PROBE_STARTED and DNS_PROBE_FINISHED_NXDOMAIN?
DNS_PROBE_STARTED means the lookup began but couldn’t finish — usually a local DNS, adapter, or network problem. DNS_PROBE_FINISHED_NXDOMAIN means the lookup finished but found no such domain — often a typo or an expired/unregistered domain. They share some fixes (flush DNS, change resolver) but point to different root causes.

Why does DNS_PROBE_STARTED happen only in Chrome?
Chrome keeps its own DNS cache, separate from your operating system, so a corrupted entry there can cause the error in Chrome even when other browsers work. Clearing Chrome’s host cache at chrome://net-internals/#dns usually resolves that case.

Conclusion

DNS_PROBE_STARTED looks technical but is one of the easier browser errors to fix — and almost always on your side. Start with the quick wins: restart your router, flush your DNS cache, clear Chrome’s host cache, and switch to a public DNS like Cloudflare (1.1.1.1) or Google (8.8.8.8). If those don’t clear it, renew your IP, check your firewall, update the network driver, or reset the network stack. Work top to bottom and you’ll almost always be back online in a couple of minutes.