chrome://net-internals/dns: Flush Chrome’s DNS cache
If Chrome is the only place a site won’t load, `chrome://net-internals/dns` is the page to use to clear Chrome’s cached DNS entries. Open it in Chrome, click **Clear host cache**, and test the site again. If that does not fix it, the problem is probably outside Chrome’s DNS cache.
Symptom
The site loads in another browser, another device, or after a while, but not in Chrome on this computer.This usually shows up when a site worked earlier, then stops loading in Chrome without any obvious change on your side. Sometimes Chrome keeps trying to reach an old address for the site, which points to cached DNS data rather than a problem with the site itself.
Before you start
This applies to Chrome on desktop, including Windows, macOS, and Linux. You do not need administrator rights to use chrome://net-internals/dns because it is an internal Chrome page.
You do not need to restart the computer first, and clearing the Chrome host cache does not delete your bookmarks, passwords, cookies, or browsing history. Before you change anything else, try the site in another browser on the same device and, if you can, on another device on the same network. Those quick checks tell you whether the problem is limited to Chrome or is wider than that.
Why you’re probably here right now
This is the right place when a site suddenly stops loading in Chrome, especially if the same site opens in another browser or on another device. That pattern often means Chrome has cached an old DNS result and is still pointing at the wrong address.
If the problem only happens in Chrome, clearing Chrome’s DNS cache is a safe first step. If the site fails in every browser and on every device, the issue is probably not just Chrome’s cache.
What chrome://net-internals/dns actually does
chrome://net-internals/dns is an internal Chrome page for Chrome’s network diagnostics, including the host resolver cache. That cache stores domain-to-IP lookups so Chrome can load sites faster.
Clicking through this page clears Chrome’s stored DNS entries. It does not flush your router or your operating system’s DNS cache, so it is a browser-level fix, not a full network reset. That makes it useful when Chrome seems stuck on an old address, but it will not fix every loading problem.
How to clear Chrome’s DNS cache
- Open Chrome on the affected computer.
- Type the internal address exactly as written below into the address bar and press Enter.
chrome://net-internals/dns- On the page that opens, click Clear host cache.
- Try the site again in the same tab or open a fresh tab and load it there.
If Chrome had a stale DNS entry, the site should start resolving the current address instead. If the page does not look like a normal website and instead shows network controls, you are in the right place. If Chrome searches the text instead, the address was typed incorrectly.
How to check whether the fix worked
The quickest check is to reload the site right after you clear the host cache. If the page opens normally, or the error changes and then clears on the next try, DNS was probably part of the problem.
A better check is to compare results after the flush:
- Open the site in a new Chrome tab.
- Try it in another browser on the same device.
- If you can, try it on a phone or another computer on the same network.
If Chrome starts loading the site after the cache clear, but another browser also had trouble before, the problem may have been DNS outside Chrome as well. If Chrome still fails while another browser works, the issue is more likely in Chrome itself, such as an extension, a cached redirect, or browser settings.
If the page won’t open or nothing changes
If chrome://net-internals/dns does not open, first check that you typed the full chrome:// prefix. These are internal Chrome pages, and a small typo can turn the address into a search instead.
If the page still won’t open, restart Chrome and try again. A clean browser restart is usually enough to bring the internal page back if Chrome was temporarily stuck.
If the page opens and you clear the host cache but the site still won’t load, the DNS problem may be outside Chrome. At that point, you may need to clear the operating system’s DNS cache or renew the network connection. The exact steps depend on your device and operating system, so the reset method is different on Windows, macOS, and Linux.
When this is not a DNS problem
If the site times out, never finishes loading, or shows a connection refused message, DNS may not be the cause at all. The same is true if the problem only happens on one network, after connecting to a VPN, or only when a certain extension is enabled.
A few signs point away from DNS:
- The site still fails in Chrome after you clear the host cache, and disabling an ad blocker or privacy extension makes the site work.
- The site opens on mobile data but not on your Wi‑Fi.
- Disabling an ad blocker or privacy extension makes the site work.
- Other sites fail too, which suggests a broader network problem.
If you see one of those patterns, keep looking beyond Chrome’s DNS cache. Flushing it again usually won’t help.
What to do next if the site still fails
- Open the site on another network.
- Disable extensions one by one.
- Restart your router.
Those checks help separate a browser issue from a local network issue. If the site works elsewhere but not in Chrome on this device, test Chrome without extensions or with a fresh profile. If it fails everywhere, the site itself may be down or having DNS trouble on its end, and waiting is sometimes the only fix.
Conclusion
If Chrome is the only place the site fails, `chrome://net-internals/dns` is the right first place to clear stale host data. If the site still won’t load after that, move outward to extensions, browser settings, then your network and router.
Frequently Asked Questions
Is `chrome://net-internals/dns` the same as clearing my browser history?
No. It clears Chrome’s host resolver cache, not your browsing history, cookies, or saved passwords.
Will clearing Chrome’s DNS cache fix every site that won’t load?
No. It helps when Chrome has a stale or bad DNS entry, but it won’t fix a down site, a bad Wi‑Fi connection, or an extension blocking the page.
Do I need administrator rights to use `chrome://net-internals/dns`?
No. It is a Chrome page, so you only need normal access to Chrome itself.