Chrome keeps a local DNS cache to speed up browsing. When that cache stores stale or broken records, websites stop loading correctly. The built-in tool at chrome://net-internals/#dns lets you clear it in seconds without touching your system settings. Here’s what the tool does, when to use it, and exactly how to run it on Chrome or Chromebook.
How to Clear DNS Cache Using chrome://net-internals/#dns
The process takes four steps. No extensions, no admin access, and no third-party tools required.
Step 1: Open the net-internals DNS Page
Open Google Chrome. Click the address bar, type chrome://net-internals/#dns, and press Enter.
Chrome loads its internal network diagnostics page and lands directly on the DNS tab. You’ll see the “Host resolver cache” section, which lists every domain Chrome has resolved recently along with its TTL (time-to-live) value.
Step 2: Clear the Host Cache
Click the “Clear host cache” button. Chrome removes all stored DNS entries immediately. No confirmation dialog appears, but the action takes effect instantly.
After this, Chrome will perform a fresh DNS lookup the next time you visit any website, pulling a current IP address rather than a cached one.
Step 3: Flush Socket Pools
Navigate to chrome://net-internals/#sockets in the address bar, or use the left-side menu if it appears. Click “Flush socket pools.”
Socket pools are groups of pre-established connections Chrome holds open to speed up repeat visits. If you clear DNS but leave old socket connections active, Chrome can continue routing traffic through outdated paths. Flushing socket pools closes all active connections so new ones get built against fresh DNS data.
If your Chromebook won’t connect to WiFi or consistently fails to reach specific sites, flushing socket pools alongside DNS often resolves it.
Step 4: Restart Chrome
Close Chrome completely and reopen it. This clears any remaining temporary data and ensures the new DNS lookups start from a clean state.
After restarting, load the problem site. If pages still won’t load, check your firewall or antivirus settings, which can block Chrome’s outbound connections independently of DNS.
Chrome DNS Cache vs System DNS Cache
Chrome runs its own DNS cache separate from the operating system. Clearing one does not affect the other. This matters when you’re deciding which layer to target during troubleshooting.
| Feature | Chrome DNS Cache | System DNS Cache |
|---|---|---|
| Where it’s stored | Inside Chrome’s browser memory | Operating system (Windows, macOS, Linux, ChromeOS) |
| How to clear it | chrome://net-internals/#dns |
OS-level commands (ipconfig /flushdns on Windows) |
| Affects other browsers? | No — Chrome only | Yes — all applications on the device |
| Affects other apps? | No | Yes — any app using internet connections |
| Best used when | Only Chrome shows DNS errors | All browsers and apps face the same issue |
Estimated resolution rates based on common troubleshooting patterns reported across Chrome support communities.
When Should You Use net-internals DNS on Your Chromebook?
Not every connectivity problem calls for a DNS cache flush. Use chrome://net-internals/#dns when you notice any of these specific conditions:
- A site you know is live won’t load in Chrome, but works on your phone
- You’re getting a
DNS_PROBE_FINISHED_NXDOMAINerror - A website you recently visited shows an outdated version even after refreshing
- You changed DNS servers or switched networks and specific domains stopped resolving
- You migrated a website to a new host and Chrome still routes to the old IP
Regular cache clearing isn’t necessary. Chrome manages TTL values automatically and expires stale records on its own. The net-internals DNS tool is a troubleshooting step, not routine maintenance.
If you’re dealing with a broader network problem, such as an Error Configuring Network message or a complete failure to reach the router, DNS cache isn’t likely the cause. Start with your router and network stack instead.
Other Tabs in chrome://net-internals Worth Knowing
The net-internals tool goes beyond DNS. The main sections you’ll actually use:
#sockets— shows active connections and lets you flush socket pools#events— real-time log of Chrome’s network activity, useful for diagnosing failed requests#proxy— displays current proxy settings and lets you re-apply configuration
For DNS-related security settings like DNS over HTTPS, those live in chrome://settings/security, not here. That’s covered in detail in the Chromebook security guide if you want to configure encrypted DNS lookups alongside cache management.
If you’re troubleshooting at the network level, knowing your router’s default gateway can help you identify whether the problem is in Chrome or upstream from it.
FAQs
What does chrome://net-internals/#dns do?
It opens Chrome’s internal DNS management page. You can view all cached domain-to-IP mappings and clear them. This forces Chrome to perform fresh DNS lookups on the next visit to any website.
Will clearing DNS cache delete my browsing history or passwords?
No. Clearing the DNS cache only removes stored domain name records. Browsing history, saved passwords, cookies, and all other browser data remain completely untouched.
Does net-internals DNS work on Chromebook?
Yes. The chrome://net-internals/#dns page works on any device running Chrome, including Chromebooks, Windows, macOS, and Linux. The interface and steps are identical across platforms.
Why does chrome://net-internals/#dns not fix my connection issue?
Chrome’s DNS cache is separate from your system’s. If the issue affects all browsers or apps, you need to flush the OS-level DNS cache using system commands, not Chrome’s internal tool.
How often should I clear DNS cache in Chrome?
Only when troubleshooting specific DNS errors or site loading issues. Chrome automatically expires old cache entries using TTL values. Regular manual clearing provides no benefit and slightly slows initial page loads.
