DNS_PROBE_STARTED appears in Chrome when the DNS resolution process initiated but stalled or failed before completing. Chrome started querying the DNS server but never received a valid response. The most common causes are an unreachable or overloaded DNS server, a frozen DNS Client service on Windows, a firewall blocking outbound UDP queries on port 53, or an IPv6 DNS failure on a network that only partially supports IPv6.
Unlike DNS_PROBE_FINISHED_NO_INTERNET, which means DNS resolution completed but found nothing, DNS_PROBE_STARTED means the probe never finished at all. The process started and hung. This narrows your troubleshooting immediately: the problem is either the DNS server being unresponsive, the Windows DNS service being frozen, or something blocking the DNS query before it reaches the server.
What Causes DNS_PROBE_STARTED
The DNS Client service on Windows (also called dnscache) acts as the local DNS resolver and cache manager. When this service hangs or enters a deadlock state, Chrome initiates a DNS probe but never gets a callback. The probe starts, the service does not respond, and Chrome displays DNS_PROBE_STARTED indefinitely. This is a Windows-level issue, not a Chrome bug.
Network configuration problems are the second major cause. If your DNS server address is set to an IP that no longer routes correctly, or if your router’s DNS relay service crashes, every DNS query goes nowhere. Port 53 must be open for outbound UDP traffic for DNS to work. Security software and aggressive firewalls sometimes block port 53 either intentionally (to force DNS through a specific path) or by misconfiguration.
IPv6 adds complexity. Windows and Chrome will try IPv6 DNS (AAAA records) before falling back to IPv4 if IPv6 is enabled on your network adapter. If your network only partially supports IPv6 or your router does not properly relay IPv6 DNS queries, the probe starts over IPv6 and never completes. Disabling IPv6 on the adapter eliminates this variable entirely.
Flush the DNS Cache
The first step is clearing both Windows and Chrome’s DNS caches. Open Command Prompt as administrator and run ipconfig /flushdns. You should see a confirmation that the DNS Resolver Cache was successfully flushed. Then open Chrome and go to chrome://net-internals/#dns and click Clear host cache. Chrome maintains a separate DNS cache from Windows, and stale entries in either cache can cause DNS probes to start against cached but invalid server addresses.
After flushing, also visit chrome://net-internals/#sockets and click Flush socket pools. This closes all existing Chrome connections and forces fresh DNS lookups on the next page load. In many cases, this combination resolves DNS_PROBE_STARTED without any other changes.
Change Your DNS Servers
If your ISP’s DNS server is unreachable or slow, Chrome’s probe starts but receives no response. Switch to Cloudflare (1.1.1.1 and 1.0.0.1) or Google Public DNS (8.8.8.8 and 8.8.4.4). These resolvers have 99.99% uptime SLAs and respond in under 15ms from most locations globally.
On Windows 11, go to Settings, then Network and Internet, then click your active connection (Ethernet or Wi-Fi), scroll to DNS server assignment, and click Edit. Set it to Manual, enable IPv4, and enter the new DNS addresses. Click Save. Run ipconfig /flushdns again after changing the DNS addresses to clear any cached queries to the old server.
Enable DNS over HTTPS for Faster Resolution
DNS over HTTPS (DoH) encrypts DNS queries and routes them through verified servers. In Chrome, go to chrome://settings/security, find Use secure DNS, and enable it. Select Cloudflare or Google as the provider. DoH bypasses your system DNS settings entirely, so if your Windows DNS configuration is the problem, DoH in Chrome sidesteps it completely.
Restart the DNS Client Service
A frozen DNS Client service is one of the most common causes of DNS_PROBE_STARTED. Press Win+R, type services.msc, and press Enter. Scroll to DNS Client, right-click it, and select Restart. If the Restart option is grayed out, open Command Prompt as administrator and run net stop dnscache followed by net start dnscache.
If the service fails to restart, it may be in a crashed state. Run sfc /scannow from an elevated Command Prompt to check for corrupted system files that could prevent the DNS Client service from running. Windows 11 and Windows 10 both support this repair command, and it requires no additional software.
Reset Network Configuration
Corrupted Winsock or TCP/IP stack settings can block DNS queries on port 53. Open Command Prompt as administrator and run the following commands in sequence: netsh winsock reset, then netsh int ip reset, then netsh int ipv6 reset. Restart your computer after all three commands complete. These commands restore the Windows networking stack to its default factory state without affecting your IP addresses or adapter settings.
After the restart, run ipconfig /flushdns again and test the affected site. In cases where Winsock corruption was the cause, the DNS probe completes immediately after this reset.
Disable IPv6 on Your Network Adapter
IPv6 DNS resolution can stall on networks that do not fully support IPv6. To disable it, open Network Connections by pressing Win+R and typing ncpa.cpl. Right-click your active adapter, select Properties, uncheck Internet Protocol Version 6 (TCP/IPv6), and click OK. Test the site. If DNS_PROBE_STARTED resolves, your network has broken IPv6 DNS infrastructure.
Disabling IPv6 on the adapter does not affect your internet connectivity on IPv4 networks. Most residential ISPs and websites function normally over IPv4. You can re-enable IPv6 if your ISP or network administrator fixes IPv6 DNS support.
Advanced Fixes: Antivirus and Router
Security software with DNS filtering or network protection features can intercept DNS queries and fail silently, producing DNS_PROBE_STARTED. Kaspersky, Avast, and ESET all have this feature. Temporarily disable the network protection module in your antivirus and test. If the error clears, whitelist your primary browser in the antivirus settings or disable the DNS interception specifically.
Restart your router by unplugging it for 30 seconds and reconnecting. Router DNS relay services can crash after extended uptime, causing all DNS queries from connected devices to hang. If DNS_PROBE_STARTED appeared suddenly across multiple devices on the same network, a router restart almost certainly fixes it.
Frequently Asked Questions
What is the difference between DNS_PROBE_STARTED and DNS_PROBE_FINISHED_NO_INTERNET?
DNS_PROBE_STARTED means the DNS query was initiated but never received a response. DNS_PROBE_FINISHED_NO_INTERNET means the DNS query completed but returned no usable result, typically because the DNS server is reachable but has no record for the domain or because internet connectivity was lost. Probe Started is a service or connectivity failure; Probe Finished No Internet is a resolution failure.
Why does DNS_PROBE_STARTED only affect Chrome and not other browsers?
Chrome has its own built-in DNS resolver and cache that operates separately from the system DNS. If Chrome’s internal DNS state becomes corrupted or its cache contains invalid entries, it can fail at the probe stage while other browsers using the system DNS directly succeed. Clearing Chrome’s internal DNS cache at chrome://net-internals/#dns usually resolves Chrome-specific occurrences.
Does DNS_PROBE_STARTED mean my DNS server is down?
Not necessarily. The error means the probe did not complete, which can happen even when the DNS server is technically online if the query is blocked by a firewall, intercepted by security software, or the local DNS Client service is frozen. Check whether other devices on your network can resolve DNS before concluding the server is down.
How do I fix DNS_PROBE_STARTED on a corporate network?
On corporate networks, DNS queries are often routed through internal DNS servers and may be subject to firewall rules that block specific domains. Contact your IT administrator and report the specific domain that fails. Avoid changing DNS settings on corporate devices as this may bypass security policies. Disabling IPv6 on your adapter is typically safe and does not violate corporate security requirements.
If your browser is also showing slow page loads even when DNS resolves, see the guide to fixing slow DNS lookup speed. For connection failures after DNS resolves successfully, the ERR_CONNECTION_REFUSED article covers the next failure stage. Related redirect issues that follow DNS resolution are explained in the ERR_TOO_MANY_REDIRECTS guide.
