As you probably know Google Chrome has its own internal DNS cache. Is there a way to clear it without having to wait for the time out or close the browser?
Tell me more
×
Super User is a question and answer site for
computer enthusiasts and power users. It's 100% free, no registration required.
|
|
||||
|
|
Navigate to chrome://net-internals/#dns and press the "Clear host cache" button. Here you can find the documentation of Chrome's net-internals page |
|||||||||||||||||
|
|
"Navigate to chrome://net-internals/#dns" doesn't work in the Google Chrome browser, at least on my system. Looks like this solution maybe works for the Google Chrome OS, but not the Google Chrome browser more generally speaking. For me the link redirects here - http://www.chromium.org/developers/design-documents/network-stack/view-net-internals (very clever those Googlers) It appears "Empty the Cache" is the better solution. Also note my browser says "Preferences" rather than "Options" Via http://www.google.com/support/forum/p/Chrome/thread?tid=026b6a1d9151a6e3&hl=en "Go to tools -> options -> Under the hood -> Clear Browsing data and check 'empty the cache' and click on clear browsing data. Yes yes, I know, it is not the DNS cache I would expect it to clear, but hey it seems to. And now it works for me." |
||||
|
This worked for me: Empty and Clear the Disk Cache In Chrome, click on Wrench icon, and then Options. Go to Under the Hood tab. Click on Clear browsing data button under Privacy section. Select just "Empty the cache" check box, and then click on Clear browsing data button. This worked immediately - I didn't even have to close the browser. |
|||||
|
|
I tried to flush the DNS cache in so many ways, but nothing worked for me. At last, I planned to change my DNS entry. This trick will work for all people who access Internet through high speed LAN connection. On a LAN connection, a user is generally provided two DNS addresses. One is primary and another is secondary or alternative DNS address. What I did was that I just changed the secondary address to the primary address and vice-versa. It worked for me instantly. I kept the alternative DNS address as primary address for two days. The problem solved itself and later, I reinstated the old DNS entry. |
||||
|
|
|
Clicking "clear host cache" in Windows:
OS X pre-10.7:
OS X 10.7+:
Your router may be caching the DNS as well (restart it or read the manual). The ultimate test is to use dig, but this uses your network's DNS host, not the authoritative server by default:
To query right from the source, try something like:
|
|||
|
|
|
As far as I can find, in recent versions of Chrome (I'm on 26.0.1410.43), there's no (reliable) way to do it, at least not on a Mac. None of the suggestions on this page have worked for me. My situation is that I've added a hosts file entry, but Chrome is still going to the IP returned by DNS. Firefox works correctly. In fact, the chrome://net-internals/#dns page is simply lying about the IP address for me. It shows the IP from the hosts entry, but that is clearly not where it's actually getting the site from. |
|||
|
|
try DNS Flusher for Chrome
Note that to use it, it requires command line flag |
||||
|
|
