Why Chrome still uses the old IP after you edit your hosts file · Max's Marginalia

maxmart.github.io3 min read

Chrome maintains a five-minute idle connection pool keyed on hostname and port rather than IP, causing the browser to continue using an old IP address after a hosts file modification. To resolve this without manually flushing socket pools or restarting all browser tabs, the author built an automated tool called Hosts Tray. The utility kills stale OS-level TCP connections on Windows and uses packet resets via the pf firewall on macOS. Open article →

More on this topic