How to Flush DNS Cache on Any Device
Clear stale DNS records, fix connection errors, and force your system to fetch the latest IP addresses. Choose your platform below for instant 1-click copy terminal commands and step-by-step instructions.
Windows 11 & Windows 10
Press Win + R, type cmd or powershell, and press Enter. Run the command:
ipconfig /flushdnsExpected confirmation: "Successfully flushed the DNS Resolver Cache."
Apple macOS (Sonoma & Sequoia)
Press Cmd + Space, type Terminal, and press Enter. Paste and enter administrator password:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponderPurges both directory services cache and Bonjour multicast DNS responder daemon.
Google Chrome / Brave / Edge
Chromium browsers maintain their own socket pool and DNS cache independent of Windows/macOS. Paste into your URL bar:
chrome://net-internals/#dnsClick the "Clear host cache" button, then navigate to chrome://net-internals/#sockets and click "Flush socket pools".
Linux (Ubuntu, Debian, Fedora, Arch)
Most modern Linux distributions use systemd-resolved. Open your bash/zsh shell and run:
sudo resolvectl flush-cachesVerify cache clearance with: resolvectl statistics.
Flushed your DNS? Test your resolution speed now
Benchmark 28+ DNS servers to verify whether your resolver is delivering peak latency.
Flush DNS FAQs
What does flushing DNS actually do?↓
Flushing DNS erases your operating system and browser local cache of translated domain names and IP addresses. The next time you open a website, your computer requests a fresh, up-to-date DNS record from your configured DNS resolver instead of reading stale local cache.
When should I flush my DNS cache?↓
You should flush DNS when: (1) you have updated domain nameservers or hosting IPs and want to see changes immediately, (2) you encounter browser errors like ERR_NAME_NOT_RESOLVED or DNS_PROBE_FINISHED_NXDOMAIN, (3) you switch to a faster DNS resolver, or (4) you suspect DNS spoofing or cache poisoning.
Does flushing DNS delete my browsing history or cookies?↓
No. Flushing DNS only purges the temporary IP mapping cache stored by your operating system networking daemon. It has no effect on your browser history, saved passwords, sessions, or website cookies.
Why do I still see an old website after flushing DNS?↓
If you still see old records after running ipconfig /flushdns, your browser may have its own internal DNS cache (flush via chrome://net-internals/#dns), your home router may be caching records, or your ISP recursive resolver is honoring a remaining TTL countdown.