You type a web address, press Enter and a page appears. Between those two moments, your browser has to answer a deceptively simple question: which server actually hosts this site? The answer comes from the Domain Name System and Chrome keeps a private window into how it handles that process at an address most people never visit: chrome.//net-internals/dns.
This guide explains what that page is, what it does, when it helps and how it fits with the other network tools built into Chrome.
A Quick Refresher on DNS
Computers locate each other using numeric IP addresses, but humans prefer names like example.com. DNS is the phonebook that translates one into the other. When Chrome needs to load a site, it asks a resolver, usually run by your internet provider, your router or a public service such as Google or Cloudflare. The resolver replies with one or more IP addresses and Chrome connects to one of them.
Because doing this lookup for every single request would be slow and wasteful, the answers are cached at several layers. Your router may cache them, your operating system keeps its own cache and Chrome maintains an internal one too. Each cached answer carries a time-to-live (TTL), a timer set by the domain owner that says how long the answer can be reused before it must be refreshed.
Caching is wonderful when it works. It makes pages load faster and reduces network traffic. But when a cached answer goes stale, you get strange symptoms: a site that loads for your friend but not for you, a migrated website that still shows the old server, or an error that vanishes when you switch to a different browser.
What is chrome://net-internals?
chrome://net-internals is a diagnostic page built into Chromium-based browsers. It exposes the inner workings of Chrome’s network stack, the code responsible for everything from DNS lookups and proxy settings to open sockets and security policies. Developers and network engineers have used it for years to figure out why a connection is slow, blocked or behaving oddly.
The page is organized into sections, each reachable through a hash fragment in the address. The #dns section focuses on the host resolver, the part of Chrome that turns hostnames into IP addresses and remembers the results.
A word of caution: net-internals is an internal tool, and Google has trimmed it over time. Older versions of Chrome offered a rich set of tabs, including a live event log, but much of that functionality moved to separate pages such as chrome://net-export. Depending on your version, the DNS page may look simpler than screenshots in older tutorials. The core feature, clearing Chrome’s host cache, has remained the most dependable part.
What You Will Do on the DNS Page
Open a new tab, paste chrome://net-internals/#dns into the address bar and press Enter. Chrome blocks links to chrome.//pages from ordinary websites, so you must type or paste the address yourself.
The page centers on the host resolver cache. Depending on your Chrome version, you may see:
A ‘clear host cache’ button. This is the main attraction. Pressing it wipes Chrome’s stored hostname-to-IP mappings so that the next visit to any site triggers a fresh lookup.
Cache details. Some versions show the cache capacity, the number of active entries and a table of cached hostnames, the addresses they resolved to, and when each entry expires.
Resolver information. Newer builds may show whether Chrome is using its built-in asynchronous DNS client or handing lookups to the operating system, along with settings related to secure DNS.
If you see a table, it can be quite revealing. Each row corresponds to a hostname Chrome has resolved recently and you will often spot domains you never types: advertising networks, analytics services, content delivery networks and fonts. Modern web pages pull resources from dozens of domains and everyone needs its own lookup.
How to Clear Chrome’s DNS Cache?
Clearing the cache takes seconds:
Open a new tab and go to chrome.//net-internals/dns
Click Clear host cache
Reload the problem website.
There is usually no confirmation message, so do not be alarmed if nothing visibly changes. The cache is emptied silently and Chrome will repopulate it as you browse.
Here is the part many people miss: this only clears Chrome’s cache. Your operating system keeps its own DNS cache and your router may keep another. If the stale answer lives there, clearing Chrome’s cache will not fix the problem. To flush the system cache, you can use:
Windows: run ipconfig/flushdns in Command Prompt
macOS: run sudo dscacheutil-flushcache; sudo killaii- HUP mDNSResponder in Terminal.
Linux: the command depends on your setup; on systems using systemd-resolved, try resolvectl flush-caches.
For stubborn cases, restarting your router clears its cache too.
When Should You Use It?
Most people will never need this page, which is a good sign. Chrome’s cache is generally well-behaved. But there are several situations where it earns its keep.
After a website migration. If you have just moved a site to a new host or changed its DNS records, your own browser may keep sending you to the old server until the cached entry expires. Clearing the host cache lets you see the new destination immediately, which is invaluable when you are verifying a launch.
When a site loads for others but not for you. If a colleague can reach a site and you cannot, a stable or corrupted DNS entry is a prime suspect. Clearing the cache is a cheap first test before you dive into firewalls and VPN settings.
After changing DNS providers. Switched from your provider’s default resolver to a public one? Chrome may still hold answers obtained from the old resolver. A clear ensures every new lookup uses the new path.
Troubleshooting errors like ERR_NAME_NOT_RESOLVED. This error means Chrome could not find an address for the hostname. Sometimes it is a genuine outage and sometimes it is a temporary failure that Chrome has remembered. Clearing the cache removes cached failures and lets you retry cleanly.
Testing local development setups. If you edit your hosts file to point a domain at a local server, Chrome may not notice right away. Clearing the host cache, and sometimes the socket pools, helps your change take effect.
Related Tools in Net-internals
The DNS page rarely works alone. A few neighbors are worth knowing.
Sockets (#sockets). Chrome keeps connections open for reuse. If a server’s address changed but Chrome keeps talking to an existing connection, the old socket may linger. Flushing socket pools forces new connections and pairing this with a DNS clear is a classic one-two punch.
Domain Security Policy (#hsts). Here you can query or delete HSTS entries, which tell Chrome to always use HTTPS for a domain. If you are testing a site and Chrome refuses to load it over plain HTTP, this is where you look.
Proxy (#proxy). This shows which proxy configuration Chrome is using and lets you re-apply it. Handy when corporate network settings seem to be misfiring.
Net-export (chrome://net-export). For deep investigations, this tool records network activity into a log file you can analyze or share with support teams. If you are chasing an intermittent failure, a captured log often reveals what happened step by step.
Common Pitfalls
Expecting a global fix. Clearing Chrome's cache affects only Chrome on your device. It will not change what other people see, and it will not fix a record that is genuinely wrong at the DNS provider.
Forgetting about the TTL. If you update a DNS record, remote resolvers may still hand out the old answer until the TTL expires. Clearing your own cache cannot speed that up.
Ignoring other browsers and apps. Firefox and Safari keep their own caches, and many desktop apps use the system resolver instead. A site can work in one program and fail in another for exactly this reason.
Relying on old tutorials. Because net-internals has changed across versions, buttons and tables described in older articles may be missing. If something is absent, check chrome://version to see which build you are running.
Pasting commands from strangers. Only type internal addresses yourself, and be wary of anyone who asks you to change DNS settings to unfamiliar servers. DNS controls where your traffic goes, so a malicious resolver can redirect you to fake sites.
A Simple Troubleshooting Routine
When a website misbehaves and you suspect DNS, try this order of operations:
1. Reload the page with a hard refresh to rule out an ordinary page cache problem.
2. Visit chrome://net-internals/#dns and clear the host cache.
3. Flush the sockets from the sockets section if the problem persists.
4. Flush your operating system's DNS cache.
5. Try the site in another browser or on another network, such as a phone hotspot, to determine whether the issue is local.
6. If it still fails, restart your router, or test with a different DNS provider.
This sequence moves from the narrowest, least disruptive fix to the broadest, and it helps you learn where the problem lives, which is often more useful than the fix itself.
Final thoughts
The page at chrome://net-internals/#dns is not glamorous. It is a plain utility with a button and, depending on your version, a small table. Yet it offers a rare glimpse into a part of the internet that normally stays invisible, and it gives you a precise tool for one of the most common causes of baffling browser behavior: stale DNS answers.
Next time a website refuses to cooperate, resist the urge to reinstall your browser or reboot everything in sight. Open the tab, clear the host cache, and see whether the phonebook was simply out of date. Sometimes the smallest tool in the toolbox is the one that solves the problem.