Attempting to open a website in Google Chrome only to be stopped by the status message: ‘This site can’t be reached. DNS_PROBE_STARTED’ indicates that the browser has initiated a Domain Name System lookup to convert the human-readable web address into a numerical IP address, but the query has stalled before receiving an answer. Because this is an intermediary state error, it often precedes more permanent DNS failures such as DNS_PROBE_FINISHED_NXDOMAIN or DNS_PROBE_FINISHED_NO_INTERNET. Resolving the bottleneck promptly restores your web navigation.
What Triggers DNS_PROBE_STARTED in Chrome?
When you input a URL, Chrome queries your local operating system DNS client cache, which in turn queries upstream resolvers configured by your Internet Service Provider (ISP) or router. Stalls occur due to:
- Corrupted Internal Chrome DNS Host Cache: Google Chrome maintains its own independent in-memory socket and DNS lookup cache that can desynchronise from operating system tables.
- Unresponsive ISP DNS Resolvers: High latency, packet loss, or server outages on your default provider’s recursive DNS servers.
- Corrupted Winsock or IP Routing Tables: Damaged network stack catalog entries in Windows requiring a complete socket reset.
- Conflicting VPN Extensions and Antivirus Web Shields: Security tools intercepting DNS requests to scan for malicious hostnames, causing request timeouts.
- Stale Local DNS Client Cache: Outdated hostname mappings stored in the Windows or macOS operating system resolver cache.
Step 1: Clear Google Chrome’s Internal Host and Socket Pools
Chrome contains specialized internal diagnostic dashboards that allow you to purge cached socket connections without clearing your personal browsing history.
- Open a new tab in Google Chrome, paste the following URI into the address bar, and press Enter:
chrome://net-internals/#dns - Click the Clear host cache button.
- Next, navigate to the sockets diagnostic page:
chrome://net-internals/#sockets - Click Close idle sockets and then click Flush socket pools.
- Restart Chrome and reload the target webpage.
Step 2: Flush Operating System DNS Cache
If the stale record resides within your operating system resolver, clearing it forces an immediate query to external authoritative nameservers.
- On Windows 11: Right-click the Start button and select Terminal (Admin) or Command Prompt (Admin). Execute:
Verify that Windows reports: ‘Successfully flushed the DNS Resolver Cache.’ipconfig /flushdns - On macOS: Open Terminal and execute:
Enter your administrator password and press Return.sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Step 3: Switch to Secure Public DNS Resolvers
ISP-provided DNS servers frequently experience congestion or aggressive caching policies. Switching to Cloudflare or Google Public DNS resolves names with low latency.
- Open Settings > Network & internet > Wi-Fi (or Ethernet) in Windows 11.
- Click on your active connection properties and click Edit next to DNS server assignment.
- Change the setting from Automatic (DHCP) to Manual and toggle IPv4 to On.
- Input the following addresses:
- Preferred DNS:
1.1.1.1(Cloudflare) or8.8.8.8(Google) - Alternate DNS:
1.0.0.1(Cloudflare) or8.8.4.4(Google)
- Preferred DNS:
- Click Save.
Step 4: Enable Secure DNS (DNS-over-HTTPS) in Chrome
Enabling encrypted DNS lookups directly within Chrome encrypts queries and circumvents local router interception.
- In Chrome, click the three-dot menu in the upper right corner and select Settings.
- Navigate to Privacy and security > Security.
- Scroll down to the Advanced section and locate Use secure DNS.
- Ensure the toggle is enabled, choose With Custom, and select Cloudflare (1.1.1.1) or Google (Public DNS) from the dropdown.
Step 5: Reset the Windows Network Stack and Winsock Catalog
If underlying transport sockets are corrupted, a complete protocol stack reset clears persistent socket hangs.
- Open Command Prompt as Administrator.
- Run the following commands sequentially, pressing Enter after each:
netsh winsock reset netsh int ip reset ipconfig /release ipconfig /renew - Restart your computer when prompted to reinitialise the network subsystem.
Clearing internal browser caches and configuring high-performance DNS resolvers ensures Chrome resolves domain names rapidly without triggering DNS probe errors.