How to clear/flush the DNS cache in Google Chrome?
--
Music by Eric Matyas
https://www.soundimage.org
Track title: Dream Voyager Looping
--
Chapters
00:00 Question
00:25 Accepted answer (Score 1503)
00:42 Answer 2 (Score 246)
00:57 Answer 3 (Score 63)
01:52 Answer 4 (Score 55)
03:09 Thank you
--
Full question
https://superuser.com/questions/203674/h...
Answer 2 links:
[The Chromium Projects]: https://web.archive.org/web/201303080126...
[http://www.google.com/support/forum/p/Ch...]: http://www.google.com/support/forum/p/Ch...
Answer 3 links:
[dig]: http://en.wikipedia.org/wiki/Dig_%28comm...
--
Content licensed under CC BY-SA
https://meta.stackexchange.com/help/lice...
--
Tags
#googlechrome #dns #hosts
#avk47
ACCEPTED ANSWER
Score 1541
Navigate to chrome://net-internals/#dns and press the "Clear host cache" button.
ANSWER 2
Score 267
Sometimes you need to flush the socket pools after flushing the DNS:
chrome://net-internals/#sockets
ANSWER 3
Score 66
"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:
The Chromium Projects
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."
ANSWER 4
Score 59
Clicking "clear host cache" in chrome://net-internals/#dns should do it for Google Chrome, but there are other DNS caches to consider on your machine.
Windows:
ipconfig /flushdns
OS X pre-10.7 (before Lion):
sudo dscacheutil -flushcache
OS X 10.7–10.9 (Lion, Mountain Lion, Mavericks):
sudo killall -HUP mDNSResponder
OS X 10.10+ (Yosemite):
sudo discoveryutil mdnsflushcache
OS X 10.11, 10.12+ (El Capitan, Sierra):
sudo killall -HUP mDNSResponder
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:
dig superuser.com
To query right from the source, try something like:
dig superuser.com @ns1.serverfault.com