If you have made DNS changes (like updating nameservers or A records) but your computer still loads the old version of your site, your local DNS cache may be holding onto the old records. Flushing your DNS cache forces your computer to look up the fresh records.
Flush DNS by operating system
- Windows:
ipconfig /flushdns - macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Linux:
sudo systemd-resolve --flush-caches
01. Windows
- Open Command Prompt - Search "cmd" in the Start menu, right-click, and select "Run as administrator"
- Run:
ipconfig /flushdns - You should see: "Successfully flushed the DNS Resolver Cache"
02. macOS
- Open Terminal (Applications > Utilities > Terminal)
- Run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Enter your Mac password when prompted
03. Linux
The command depends on your DNS resolver:
- systemd-resolved (Ubuntu 18+, Fedora):
sudo systemd-resolve --flush-caches - nscd:
sudo service nscd restart - dnsmasq:
sudo service dnsmasq restart
04. Browser DNS Cache
Browsers maintain their own DNS cache separate from the operating system. Even after flushing the OS cache, your browser may still use cached DNS entries.
- Chrome: Navigate to
chrome://net-internals/#dnsand click "Clear host cache" - Firefox: Navigate to
about:networking#dnsand click "Clear DNS Cache" - All browsers: Close and reopen the browser completely, or use an incognito/private window
05. Still Seeing the Old Site?
If flushing the cache does not help, the DNS change may not have fully propagated yet. DNS propagation can take up to 48 hours worldwide. Check the current propagation status with our DNS Lookup tool.
For a deeper explanation of DNS propagation, see DNS Changed But Site Not Showing.
DNS Not Resolving?
If your domain is not resolving at all after 48 hours, open a ticket and we will check your DNS configuration.
Open a Support TicketQuick Recap
- Windows:
ipconfig /flushdnsin admin Command Prompt - macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Linux:
sudo systemd-resolve --flush-caches - Clear browser DNS cache too - Chrome and Firefox have their own caches
- Allow 48 hours for full DNS propagation worldwide
DNS troubleshooting · Last updated March 2026 · Browse all DNS articles
