Why Chrome’s DNS Cache Causes Connection Timeouts
Chrome maintains its own DNS cache separate from the Windows 11 system DNS resolver cache. This cache stores resolved IP addresses for frequently accessed domains for a duration determined by the DNS TTL value (often 300 seconds or higher). When a domain’s IP address changes (due to CDN failover, server migration, or DNS propagation after a change), Chrome’s stale cached IP can point the browser to a server that is no longer accepting connections on that IP. The TCP handshake never completes, and Chrome returns ERR_CONNECTION_TIMED_OUT.
The cached DNS entry is particularly problematic when using HTTP/2 connection pooling — Chrome reuses the same connection for multiple requests to the same domain, and if the underlying IP has changed, all requests on that pooled connection fail simultaneously.
How to Flush Browser DNS Cache in Chrome
Using Chrome’s Internal DNS Flush Tool
Open a new Chrome tab and navigate to chrome://net-internals/#dns. Click Clear host cache. This flushes Chrome’s internal DNS cache without affecting the Windows system cache. Navigate to chrome://net-internals/#sockets and click Flush socket pools. This closes all active HTTP/2 connections, forcing Chrome to establish fresh TCP connections with updated DNS-resolved IPs on the next request.
Clearing Both Windows DNS Cache and Chrome DNS Cache Simultaneously
For a comprehensive fix, open Command Prompt as Administrator and run:
ipconfig /flushdns && netsh winsock reset
Then open Chrome and navigate to chrome://net-internals/#dns → Clear host cache. This ensures that both the Windows 11 system DNS resolver and Chrome’s internal DNS cache are cleared simultaneously, preventing any cached entries from persisting across layers.
Using Web-Based DNS Flush Engine
The webs.ninja gateway provides a one-click DNS flush that clears both Windows DNS cache and Chrome DNS cache simultaneously from a web interface, without requiring Command Prompt access. This is particularly useful on corporate devices where the command line may be restricted.
Call to Action
Before troubleshooting further, run the webs.ninja gateway DNS flush tool to clear all cached DNS entries at both the Windows and Chrome layers. If the timeout resolves after the flush, the issue was DNS cache corruption. If the timeout persists, the issue is a TCP/IP stack problem requiring the WinSock reset procedure described earlier.