DNS Probe Started? Meaning & Fixes

If you see an error that says “DNS probe started” or “DNS_PROBE_STARTED” in your browser, it means your computer has begun a DNS lookup but the request is hanging or failing. This usually points to a problem with your DNS server, network connection, or browser cache, and it can typically be fixed by flushing your DNS cache, changing your DNS server, or restarting your router.

What Does DNS Probe Started Mean?

DNS stands for Domain Name System. When you type a website address like example.com, your computer doesn’t know its numeric IP address (like 93.184.216.34). It sends a query to a DNS server to translate the name into an IP address. The error “DNS probe started” is a message from Chrome (and sometimes other Chromium-based browsers) indicating that the browser has initiated this lookup but hasn’t received a response within a reasonable time.

This is different from other DNS errors like DNS_PROBE_FINISHED_NXDOMAIN, which means the domain doesn’t exist, or DNS_PROBE_FINISHED_NO_INTERNET, which means there’s no network connection at all. “Started” means the process began but stalled—the request was sent, but no reply came back.

Common Causes of DNS Probe Started

Several issues can cause this error, and understanding them helps you pick the right fix:

DNS server outage or unresponsiveness: Your ISP’s DNS server may be down, overloaded, or blocking certain domains.
Incorrect DNS settings: Your router or computer may be configured with an invalid or unreachable DNS server address.
Corrupted DNS cache: Your operating system stores recent DNS lookups; if that cache is corrupted, it can cause lookup failures.
Firewall or antivirus interference: Security software may block DNS queries, especially if it includes a “web shield” or “secure DNS” feature.
Router issues: A router that has been running for a long time may have a stale routing table or a failed DNS relay.
IPv6 problems: Sometimes your computer tries to use IPv6 DNS servers that aren’t reachable, while IPv4 works fine.

How to Fix DNS Probe Started (Step-by-Step)

Try these fixes in order—they go from simplest to most thorough. After each one, reload the page that gave the error.

Restart your router and modem. Unplug both for 30 seconds, plug the modem back in, wait for it to fully connect, then plug in the router. This clears temporary network glitches.
Flush your DNS cache. Open a command prompt (Windows) or terminal (macOS/Linux) and run the appropriate command:
- Windows: ipconfig /flushdns
- macOS: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
- Linux (systemd): sudo systemd-resolve --flush-caches or sudo resolvectl flush-caches
Change your DNS server. Use a public DNS like Google (8.8.8.8 and 8.8.4.4) or Cloudflare (1.1.1.1 and 1.0.0.1). You can change this in your router’s settings or on your computer’s network adapter settings.
Disable IPv6 temporarily. In your network adapter settings, uncheck the IPv6 option. If the error disappears, you can either leave it disabled or update your router’s IPv6 DNS settings.
Clear your browser’s DNS cache. Chrome has its own DNS cache. Go to chrome://net-internals/#dns and click “Clear host cache.” Also clear the socket pool at chrome://net-internals/#sockets.
Disable your firewall/antivirus temporarily. If the error goes away, adjust the software’s settings to allow DNS queries or whitelist your browser.
Run a network reset. On Windows, go to Settings > Network & Internet > Advanced network settings > Network reset. On macOS, you can delete the network configuration files (but that’s more advanced).

Why Does This Happen Only on Some Websites?

If the error occurs only on specific sites, it’s likely not a global network problem. Possibilities include:

The website’s DNS records are misconfigured or its server is down.
Your DNS server is returning a stale or incorrect IP for that domain.
Your firewall or parental controls are blocking that domain specifically.
Your ISP is throttling or blocking that site (e.g., torrent sites or streaming services).

Try loading the site on a different device (like your phone) using the same Wi-Fi. If it works there, the problem is on your computer. If it fails there too, the problem is likely your router or ISP.

DNS Probe Started vs. Other DNS Errors

It helps to know the difference between the common DNS error messages you might see:

DNS_PROBE_STARTED: The lookup began but hasn’t completed. Usually a timeout or network issue.
DNS_PROBE_FINISHED_NXDOMAIN: The domain doesn’t exist (or the DNS server says so). Check for typos.
DNS_PROBE_FINISHED_NO_INTERNET: Your device has no network connection at all.
DNS_PROBE_FINISHED_BAD_CONFIG: Your DNS settings are invalid—often a misconfigured VPN or proxy.
ERR_NAME_NOT_RESOLVED: The browser couldn’t find the IP address, similar to NXDOMAIN but may also indicate a local issue.

If you see any of these, the fixes above still apply, but the specific cause may differ. For example, BAD_CONFIG often points to a VPN or proxy that isn’t working.

Preventing DNS Probe Started in the Future

Once you’ve fixed the error, you can reduce the chances of it happening again:

Use reliable DNS servers like Google, Cloudflare, or OpenDNS instead of your ISP’s default.
Keep your router firmware updated—check your router’s admin page for updates.
Set your computer to use DHCP (automatic DNS) unless you have a specific reason not to.
Regularly clear your browser cache—this also clears DNS entries in some browsers.
If you use a VPN, make sure it’s working properly—a broken VPN can cause DNS errors.

Frequently Asked Questions

Is DNS probe started a virus?

No, it’s a browser error message, not a virus. However, some malware can change your DNS settings to redirect you, which might cause DNS errors. If you see this error frequently and other fixes don’t work, run a malware scan.

Why does DNS probe started happen on my phone but not my computer?

If it happens on your phone but not your computer, the issue is likely with your phone’s network settings or its DNS cache. Try restarting your phone, toggling airplane mode, or changing your phone’s DNS settings (in Wi-Fi settings).

Will changing my DNS server speed up my internet?

It can. A faster DNS server can reduce the time it takes to load a website’s IP address, which can make browsing feel snappier. However, it won’t increase your raw download speed. Public DNS servers like Cloudflare and Google are often faster than ISP defaults.

How do I flush DNS on Windows 11?

Open Command Prompt as administrator (right-click the Start button and select “Terminal (Admin)”), then type ipconfig /flushdns and press Enter. You’ll see a confirmation message that the DNS resolver cache was successfully flushed.

Can a VPN cause DNS probe started?

Yes. A VPN routes your traffic through its own DNS servers. If the VPN connection is unstable or its DNS servers are unreachable, you’ll get DNS errors. Try disconnecting the VPN and reloading the page. If it works, the VPN is the problem.

What does “DNS probe started” mean in Chrome on Android?

It means the same thing as on desktop: Chrome started a DNS lookup but it didn’t complete. On Android, you can try toggling Wi-Fi off and on, forgetting and reconnecting to the network, or changing your DNS settings in the Wi-Fi network’s advanced options.

Method: the standard formula for this calculation, rounded as each result states. See how the calculators work or report an error.

More cards in this drawer

The whole Numbers and Powers drawer →