chrome net internals dns is the quickest way to clear Chrome’s own cached hostname result when a website still opens from an old server or shows a DNS error. Use the desktop or Android steps below, then check the operating system and public DNS layers if the old result remains.
What chrome://net-internals/#dns does
DNS turns a domain such as example.com into an IP address that browsers can connect to. Chrome keeps host-resolution information in its own network stack, so clearing Windows DNS or deleting browsing history does not necessarily clear the result Chrome is using.
The internal page is not a permanent DNS-history viewer. It gives you a DNS lookup area and a Clear host cache control. The current Chromium source also includes Flush socket pools on the Sockets page, while the older events viewer has moved to chrome://net-export and the NetLog viewer.
Clearing the host cache affects Chrome’s cached hostname-resolution state on that device. It does not change your domain’s nameservers, edit an A record, clear your router, or force every internet resolver to refresh. That distinction matters after you move a website or update nameservers.
What you need before clearing Chrome DNS
You need an up-to-date Chrome window, the affected domain, and a page you can reload after the reset. Close the affected tab if it has an open connection that you want to test from scratch, but keep one separate tab available for the internal Chrome page.
If you recently pointed a domain to HostKarle, first confirm that the nameservers or DNS records were saved at the correct registrar. HostKarle’s nameservers are explained in this nameserver update guide. A local cache reset cannot repair a typo in a record or a nameserver change that was never submitted.
For a quick external check after the reset, you can use the HostKarle Hosting Checker. It checks the hosting relationship separately from what one Chrome tab has cached.
Step 1: Clear Chrome’s host cache on desktop
Why this works: it removes Chrome’s cached hostname-resolution entries so the next request can perform a fresh lookup through the configured resolver.
- Open a new Chrome tab on Windows, macOS, Linux or ChromeOS.
- Enter this exact internal address in the address bar:
chrome://net-internals/#dns
- Press Enter. If Chrome opens the broader Net Internals page, select DNS.
- Under Host resolver cache, click Clear host cache.
- Return to the affected website and reload it. Use a private window for the test if you also want to avoid a normal page-cache result.
Success looks like a fresh page response, a changed server response, or a different DNS error that gives you a more useful clue. The button may not show a large confirmation message; the important action is the click followed by a new request.
The Chromium source labels this control Clear host cache, so look for that wording rather than a button labelled “Clear DNS cache”.
Step 2: Flush Chrome’s socket pools
Why this works: a browser can reuse an existing connection even after a hostname lookup has been cleared, so flushing the pools helps the next request establish a new connection.
- Open another Chrome tab and enter:
chrome://net-internals/#sockets
- Press Enter.
- Click Flush socket pools.
- Close the affected site tab, open a new tab, and visit the domain again.
The Chromium interface warns that flushing socket pools may affect pages with active connections. Save form entries or uploads before using it. This step is useful when the page is still connected to the previous address, but it does not replace the host-cache step.
Success looks like the next visit opening a new connection and reflecting the current DNS destination, provided the resolver and website are already updated.
If the page still looks unchanged, test it in an Incognito window after clearing both controls. That separates the DNS and connection test from an ordinary tab’s existing page state.
Step 3: Clear the Chrome host cache on Android
Why this works: Android Chrome may expose the same internal DNS page, but the exact page behaviour can vary by Chrome and device build.
- Open Chrome on your Android phone or tablet.
- Tap the address bar and enter:
chrome://net-internals/#dns
- Tap Go.
- If the DNS page opens, tap Clear host cache.
- Close the affected tab, open a new tab, and load the domain again.
If Android Chrome does not open the internal page or does not show the button, use the device-level fallback: open Settings, go to Apps or App management, choose Chrome, open Storage or Storage & cache, and choose Clear cache. The names of these menus vary by Android manufacturer. Do not choose Clear storage or Clear data unless you understand that it can remove local app data and sign you out.
Android does not provide a Chrome socket-pool button in every build. Restarting Chrome after clearing its app cache closes the browser’s active connections. If the website still resolves incorrectly on mobile data and Wi-Fi, continue with the public DNS checks below.
Success looks like the domain loading with the current result in a new Chrome tab, without needing to clear app data or sign out of Chrome.
Step 4: Flush the operating system’s DNS cache when needed
Why this works: Chrome’s host cache is only one layer. The operating system, router, VPN, Secure DNS provider, or ISP resolver may still return an older answer.
On Windows, open Command Prompt and run:
ipconfig /flushdns
You should see a message that the DNS Resolver Cache was successfully flushed. Microsoft documents /flushdns as a command that resets the DNS client resolver cache. Run the Chrome host-cache step again afterwards, then reload the site.
On macOS and Linux, the command depends on the OS release and the resolver service in use. Do not copy a command for a different release blindly. Restart the network connection or follow the resolver documentation for that operating system. A VPN, custom DNS application, or encrypted DNS setting may also sit outside the cache you just cleared.
Clearing an operating-system cache does not change the public DNS record. It only makes that device ask again sooner.
Success looks like Windows reporting that its DNS Resolver Cache was flushed, followed by a fresh Chrome lookup that no longer uses the local stale result.
Still seeing the old site? Check DNS propagation
Why this matters: a correct local reset cannot override a cached answer held by a recursive DNS resolver somewhere between your device and the authoritative nameserver.
After a nameserver or record change, different networks can temporarily return different answers because DNS responses are cached until their time-to-live, or TTL, expires. Google Public DNS explains that stale delegation or record data may remain after nameserver changes and recommends waiting for TTL expiry or using its cache-flush process for eligible domains.
Use this order:
- Check the domain from another network, such as mobile data instead of your home Wi-Fi.
- Query the domain with a DNS checker or command-line tool from more than one resolver.
- Compare the returned IP address or nameservers with the values you intended to publish.
- Check both the root domain and
wwwif they use separate records or a CNAME. - If different resolvers return different answers, wait for the relevant TTL and recheck instead of repeatedly clearing Chrome.
Do not treat “propagation” as a button you can press in Chrome. The browser reset helps one device; resolver caches across the internet expire on their own schedule. If the authoritative nameservers themselves return the wrong record, contact the DNS provider or correct the zone rather than waiting.
Verify which layer is still returning the old answer
Use the symptom to choose the next test:
| What you see | Most likely layer | Next check |
|---|---|---|
| Chrome alone opens the old site | Chrome host cache or an open connection | Clear host cache, then flush socket pools |
| Chrome and another browser on the same computer agree | Operating system, VPN or local network | Run ipconfig /flushdns, review VPN and DNS settings |
| Wi-Fi shows the old site but mobile data shows the new site | Router or ISP resolver cache | Restart the router if appropriate, or wait for TTL expiry |
| Several unrelated networks show the old site | Authoritative DNS or an incomplete change | Check nameservers, A/AAAA records and the DNS provider |
| The domain resolves but the page is wrong | Web hosting, HTTP cache or virtual-host setup | Check the hosting account and the requested hostname |
When you want to confirm that HostKarle can see the domain’s hosting relationship, run the Hosting Checker after the browser challenge, if one appears. The supplied capture shows that the checker may first display a browser security verification screen; that screen is not a DNS result and should not be mistaken for propagation failure.

Common mistakes
- Typing the address into Google Search:
chrome://pages must be entered directly in Chrome’s address bar. - Using the wrong punctuation: the working path is
chrome://net-internals/#dns, with two slashes afterchrome:and a hash beforedns. - Clearing only browsing history: cookies, cached images and browsing history are separate from Chrome’s host resolver cache.
- Flushing only Windows DNS: Chrome and the operating system can hold different state, so use the browser step as well.
- Expecting a local reset to change the domain: cache clearing does not edit nameservers or DNS records.
- Checking only one network: a single resolver may still have the previous answer even when another resolver has updated.
FAQ
What is chrome net internals dns used for?
It opens Chrome’s internal DNS page, where you can clear the browser’s host resolver cache. It is useful when Chrome is using an old hostname-to-IP result after a DNS change or when a cached failed lookup is blocking a site.
Does chrome://net-internals/#dns clear Windows DNS too?
No. It clears Chrome’s own host cache only. On Windows, run ipconfig /flushdns separately if the operating system may be holding the old result.
What is the difference between Clear host cache and Flush socket pools?
Clear host cache makes Chrome forget cached hostname-resolution results. Flush socket pools closes reusable network connections so Chrome is more likely to create a fresh connection; use both when a changed IP is not appearing.
Does chrome net internals dns work on Android?
Try chrome://net-internals/#dns directly in Android Chrome and tap Clear host cache if the page provides it. If your build does not expose that page, clear Chrome’s app cache from Android Settings and restart Chrome, then test on another network.
Why does Chrome still show the old website after I clear DNS?
The old answer may be cached by Windows, your router, VPN, ISP resolver or another public DNS resolver. Compare the domain on another network and wait for the DNS record’s TTL when different resolvers are still returning different answers.
Sources: Chromium Net Internals source, Microsoft ipconfig documentation, and Google Public DNS troubleshooting.
Want to partner with us, suggest a resource or advertise on this blog? Email partnerships@hostkarle.in



