chrome://net-internals/#dns is Chrome’s built-in diagnostic interface for inspecting and clearing its internal DNS cache. It helps resolve stale DNS lookups and network errors without restarting the browser, providing real-time visibility into cached hostname-to-IP mappings.
chrome://net-internals/#dns
What is chrome://net-internals/#dns and when to use it?
Every Chromium-based browser maintains an internal DNS cache separate from the operating system. This cache stores resolved IP addresses for visited domains to speed up subsequent requests. When a DNS record changes (e.g., during a website migration, CDN failover, or local development), Chrome may continue using the stale entry, causing DNS_PROBE_FINISHED_NXDOMAIN errors or loading outdated content. The chrome://net-internals/#dns tool gives you a direct view of this cache and a one-click “Clear host cache” button to force fresh lookups.
Use it when:
- You see
DNS_PROBE_FINISHED_NXDOMAINin Chrome but the site is reachable from other browsers or tools likenslookup. - You changed DNS records (A, AAAA, CNAME) and Chrome refuses to see the update even after waiting.
- You are developing/testing a local web application and Chrome insists on resolving to a production IP.
- You need a quick, non-destructive purge without flushing the entire system DNS cache.
Tested on Chrome 120 on Windows 11 and macOS 14.3 with standard DNS over HTTPS settings.
chrome://net-internals/#dns Rapid Reference Cheat Sheet
| Action | Method | Key Parameter | Result |
|---|---|---|---|
| View DNS cache | chrome://net-internals/#dns |
N/A | Displays all cached hostnames, addresses, and TTLs |
| Clear DNS cache | Click “Clear host cache” button | N/A | Removes all entries; next lookup goes to OS |
| Flush socket pools | chrome://net-internals/#sockets → “Flush socket pools” |
N/A | Closes idle and active connections |
| Restart Chrome | chrome://restart |
N/A | Reloads browser and resets all internal state |
| Disable extensions | chrome://extensions |
Disable all | Eliminates extension interference with DNS |
| Reset Chrome settings | chrome://settings/reset |
Restore settings to default | Removes rogue proxy/settings affecting DNS |
Error Resolution & Troubleshooting
| Error Code / Signal | Root Cause | Remediation Command / Step |
|---|---|---|
DNS_PROBE_FINISHED_NXDOMAIN |
Chrome’s DNS query completed, but the domain does not exist (NXDOMAIN). Could be stale cache or real missing record. | Clear Chrome DNS cache via chrome://net-internals/#dns → “Clear host cache”. Also flush sockets. Verify domain with nslookup example.com from terminal. |
ERR_NAME_NOT_RESOLVED |
DNS resolution failed completely. OS-level DNS misconfiguration or network issue. | Flush OS DNS cache: ipconfig /flushdns (Windows) or sudo systemd-resolve --flush-caches (Linux). Check DNS server settings. |
ERR_CONNECTION_TIMED_OUT |
DNS resolved, but connection to IP timed out. Often caused by stale socket pools. | Flush socket pools via chrome://net-internals/#sockets → “Flush socket pools”. Clear host cache as well. |
| Chrome still shows old IP after clearing | Browser process holding a persistent connection (HTTP keep-alive or WebSocket). Socket pools haven’t been flushed. | Flush socket pools and restart Chrome completely: chrome://restart. Also disable any proxy extensions temporarily. |
Step-by-Step: Clearing Chrome’s Internal DNS Cache
- Open the Net Internals DNS page
In Chrome’s address bar, typechrome://net-internals/#dnsand press Enter. The page shows the current DNS cache table (hostname, family, address, expiry). - Clear the host cache
Click the “Clear host cache” button. All cached entries are instantly removed. The table empties. - Flush socket pools (recommended)
Navigate tochrome://net-internals/#socketsand click “Flush socket pools”. This closes all active connections that may still hold stale DNS resolutions. - Restart Chrome
Completely close and reopen Chrome to ensure the process picks up fresh DNS queries from the OS resolver.
Frequently Asked Questions
How do I clear DNS cache in Chrome?
Open chrome://net-internals/#dns and click “Clear host cache”.
Is clearing DNS cache safe?
Yes, it is safe and helps fix browsing issues.
What is chrome://net-internals/#dns?
It is a Chrome internal tool used to view and clear DNS cache.

Command Line Expert & Software Engineer
Welcome! I’m Thomas Heinrich, a software engineer and system administrator with a deep passion for the Command Line Interface (CLI). With years of experience navigating the terminal, building backend architectures, and automating server deployments, I created this space to share practical, real-world terminal knowledge.
Whether you are a beginner taking your first steps in a Linux environment or a seasoned DevOps engineer looking to optimize your deployment scripts, you will find actionable solutions here. My goal is to help you ditch the mouse, speed up your workflow, and harness the full power of the command line.