- When Should You Flush DNS Cache?
- Before You Flush: Quick Checks (Avoid Wasted Time)
- Flush DNS Cache on Windows
- Flush DNS Cache on macOS
- Flush DNS Cache on Linux
- Flush DNS Cache in Google Chrome
- Flush DNS Cache in Microsoft Edge
- Flush DNS Cache on Android
- Flush DNS Cache on iPhone / iPad (iOS)
- Don’t Forget Your Router / ISP Cache
- Verify the Fix (Quick Checklist)
- FAQ
- Need Help?
- Related Hosticko Pages
If you’ve recently updated nameservers, changed an A record, or moved your site to a new host, your device may still load the old server due to cached DNS results. That’s when you need to flush DNS cache (also called clearing DNS cache). It forces your device (and sometimes your browser/router) to request fresh DNS records so you can see the latest changes.
This Hosticko guide covers Windows, macOS, Linux, Android, iPhone/iPad, plus browser DNS and router cache. It also includes quick verification steps so you can confirm the DNS update is live.
When Should You Flush DNS Cache? #
- After changing nameservers or DNS records (A, CNAME, MX, TXT)
- You’re seeing the old website after a migration
- You get DNS_PROBE_FINISHED_NXDOMAIN or “site not found” unexpectedly
- Email routing changed (MX updated) but your device still behaves oddly
- You switched CDN/proxy settings and want your device to re-resolve the domain
Before You Flush: Quick Checks (Avoid Wasted Time) #
DNS changes can take time depending on TTL and cache layers. Before flushing, quickly verify if the DNS has actually updated globally:
- Check the record from a public resolver like Google DNS or Cloudflare DNS (instructions below).
- If you changed nameservers, allow time for registry-level propagation (can take longer than record changes).
Quick DNS Check (Command-Line) #
Try one of these to see what IP your system is currently resolving:
- Windows:
nslookup yourdomain.com - macOS/Linux:
dig yourdomain.com +short(installbind-toolsif needed)
Flush DNS Cache on Windows #
Works on Windows 10/11 (and generally older versions too).
Method 1: Command Prompt (Recommended) #
- Open Start → type cmd
- Right-click Command Prompt → Run as Administrator
- Run this command:
ipconfig /flushdns
You should see: “Successfully flushed the DNS Resolver Cache.”
Method 2: PowerShell #
Clear-DnsClientCache
Microsoft documentation: ipconfig
Flush DNS Cache on macOS #
macOS uses different commands depending on version, but this one works for most modern macOS releases.
- Open Terminal
- Run:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Enter your Mac password when prompted. There usually isn’t a confirmation message — that’s normal.
Apple support: If you can’t connect to the internet (DNS steps)
Flush DNS Cache on Linux #
Linux is different depending on your resolver service. Try the one that matches your system.
Option A: systemd-resolved (Most Common) #
sudo resolvectl flush-caches
Option B: nscd (If Installed) #
sudo systemctl restart nscd
Option C: dnsmasq (If Installed) #
sudo systemctl restart dnsmasq
Tip: If you’re unsure what’s running, try:
ps aux | egrep 'systemd-resolved|nscd|dnsmasq'
systemd-resolved documentation
Flush DNS Cache in Google Chrome #
Chrome maintains its own DNS cache. If your OS cache is flushed but Chrome still shows the old result, flush Chrome too.
- Open:
chrome://net-internals/#dns
- Click Clear host cache.
Also do this: if you’re behind a proxy/VPN, disable it temporarily and test again.
Flush DNS Cache in Microsoft Edge #
Edge (Chromium-based) uses similar internal DNS behavior.
- Open:
edge://net-internals/#dns
- Click Clear host cache.
Flush DNS Cache on Android #
Android doesn’t provide a universal “flush DNS cache” button, but these methods work.
Method 1: Toggle Airplane Mode (Fastest) #
- Enable Airplane Mode for 10 seconds
- Disable it
- Re-test the site
Method 2: Restart the Device #
A reboot clears many network caches and resets connections.
Method 3: Clear Chrome DNS Cache (If Using Chrome) #
Use the Chrome method above: chrome://net-internals/#dns
Flush DNS Cache on iPhone / iPad (iOS) #
iOS doesn’t expose a manual DNS flush button, but these work reliably.
Method 1: Toggle Airplane Mode #
- Enable Airplane Mode for 10–15 seconds
- Disable it
- Re-test the domain
Method 2: Restart iPhone/iPad #
Simple but effective.
Method 3: Reset Network Settings (Last Resort) #
Warning: This will remove saved Wi-Fi networks and VPN settings.
- Settings → General → Transfer or Reset iPhone
- Reset → Reset Network Settings
Apple support: Reset network settings
Don’t Forget Your Router / ISP Cache #
Sometimes the device cache is clean, but your router still holds old DNS results.
- Restart your router (power off 10 seconds, then back on)
- Try a different network (mobile hotspot) to compare results
- Switch DNS resolvers temporarily (example: Google DNS
8.8.8.8, Cloudflare1.1.1.1)
Verify the Fix (Quick Checklist) #
- Run
nslookup yourdomain.comand confirm the new IP appears - Open the site in an incognito window
- Test from another network (mobile data) to confirm it’s not just local cache
FAQ #
How long does DNS propagation take? #
It depends on TTL, your DNS provider, and cache layers. Many record changes update quickly, but some networks cache longer. Nameserver changes can take longer than single-record changes.
Flushing DNS didn’t work – why? #
Either the DNS change hasn’t fully propagated, your router/ISP is caching it, or you’re behind a VPN/proxy. Verify the DNS record using a public resolver, then re-test on a different network.
Will flushing DNS break anything? #
No. It just clears cached DNS lookups so your device fetches updated records.
Need Help? #
If you changed DNS for Hosticko migration and still can’t see the new server, send us the domain name and what you changed (nameservers or A record). We’ll verify the DNS and guide you quickly:
https://client.hosticko.com/submitticket.php
