How to flush a DNS cache
A stale answer can be cached in several places at once: public resolvers, your ISP, your computer and your browser. Here is how to clear each one, and which ones can’t be cleared.
Public resolvers
| Resolver | How |
|---|---|
| Google Public DNS (8.8.8.8) | Flush cache page: enter the name and record type. |
| Cloudflare (1.1.1.1) | Purge cache page: takes a few seconds to reach every data center. |
| OpenDNS (208.67.222.222) | CacheCheck: shows what OpenDNS serves and lets you refresh it. |
| Quad9, ISPs, most others | No public purge. You wait out the TTL. |
Purges work one name and one record type at a time. If you changed several subdomains, purge each one.
Your computer
macOS
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Windows
ipconfig /flushdns
Linux with systemd-resolved
resolvectl flush-caches
Your browser
Chrome and Edge keep their own cache. Open chrome://net-internals/#dns (or edge://net-internals/#dns) and choose “Clear host cache”. Firefox: about:networking#dns, then “Clear DNS Cache”.
Servers and clusters
- Kubernetes: CoreDNS caches answers (30 seconds by default on many clusters). Restarting the CoreDNS pods clears it.
- AWS VPC resolver: there is no way to flush it. Instances get its cached answers until they expire.
- Applications: long-running processes often resolve once and hold the address in connection pools. Restarting them can matter more than any DNS flush.
Check a domain now.
See what Google, Cloudflare, OpenDNS, Quad9 and major ISPs are serving, how long each will cache it, and the registry status.
Open the checkerMore guides: How long DNS propagation takes · clientHold and serverHold