How to Flush DNS Cache on Windows 11 to Fix Slow Browsing 2026 👋
Quick intro: Flushing the DNS cache often fixes slow page loads, wrong-site errors, and “site not found” issues. Do this first before reinstalling browsers or changing network gear — it’s fast and low-risk.
---
1] Why flush DNS cache? 🧠
- DNS cache stores domain-to-IP mappings.
- Corrupt or stale entries cause slow browsing or wrong site loads.
- Flushing forces Windows to fetch fresh DNS records — often fixes problems immediately.
Personal note: I do this whenever a site looks “off” after an ISP hiccup — usually it’s enough.
---
2] Quick method — Command Prompt (admin)
1. Press Start, type cmd.
2. Right-click Command Prompt → Run as administrator.
3. Type:
ipconfig /flushdns
4. Press Enter.
5. You should see: “Successfully flushed the DNS Resolver Cache.”
6. Close CMD and reload the problem site.
Simple. Works 8 times out of 10.
---
3] PowerShell (admin) alternative
1. Press Start, type powershell.
2. Right-click Windows PowerShell → Run as administrator.
3. Enter:
Clear-DnsClientCache
4. Press Enter.
5. Close PowerShell and test browsing.
Note: PowerShell uses the same system call — choice is personal preference.
---
4] If you use a DNS service (Cloudflare, Google, OpenDNS)
- After flushing your PC cache, also flush your router DNS:
1. Reboot router — unplug 10 seconds, plug back in.
2. Or sign into router admin and restart DNS resolver service if available.
- If ISP caches aggressively, switch temporarily to public DNS:
- 1.1.1.1 (Cloudflare) or 8.8.8.8 / 8.8.4.4 (Google).
- Steps to change DNS on Windows 11:
1. Settings → Network & internet → Wi‑Fi (or Ethernet) → Hardware properties.
2. Edit under DNS server assignment → Manual → IPv4 → set Preferred DNS and Alternate DNS.
3. Save. Test.
Real talk — changing to Cloudflare sometimes speeds things up noticeably.
---
5] Flush DNS for Microsoft Edge and Chrome (hard refresh)
- After OS flush, clear browser DNS and cache:
- Chrome: go to chrome://net-internals/#dns → Clear host cache.
- Edge: edge://net-internals/#dns → Clear host cache.
- Then do a hard refresh on pages: Ctrl+F5 (Windows).
Tip: Chrome’s internal cache is separate from OS DNS — clear both.
---
6] Flush DNS on macOS (short)
- Open Terminal.
- macOS 12+ command:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
- Enter your password, press Enter.
- No success message usually — just test the site.
---
7] Flush DNS on Linux (systemd-resolved)
- For systems using systemd-resolved:
sudo systemd-resolve --flush-caches
- Or restart resolver:
sudo systemctl restart systemd-resolved.service
Paths vary by distro — Google your distro + “flush DNS” if unsure.
---
8] Mobile quick fixes (Android / iOS)
- Android: Settings → Apps → Chrome → Storage → Clear cache. Toggle Airplane mode on/off.
- iOS: Settings → Safari → Clear History and Website Data. Or toggle Airplane mode.
- For both: reboot device if problem persists.
---
9] When flush doesn’t help — next steps
- Ping domain: open CMD → ping example.com — check IP and latency.
- nslookup example.com — see what DNS server responds.
- Try another DNS server (1.1.1.1 or 8.8.8.8).
- Check hosts file (C:\Windows\System32\drivers\etc\hosts) for erroneous entries.
- Disable VPN or proxy temporarily; they can cache DNS.
I once blamed a corporate VPN for a dozen “site down” tickets — turned out VPN DNS routing was the culprit.
---
10] Automated batch script for Windows (save and run)
- Create a file named flush_dns.bat with this content:
@echo off
ipconfig /flushdns
net stop dnscache
net start dnscache
echo DNS cache flushed.
- Right-click → Run as administrator.
- Keeps things repeatable if you do this often.
---
11] Comparison — flush vs reboot vs router restart (no table)
- Flushing DNS is fastest, least disruptive; good first step.
- Router restart clears both router and ISP transient caches; do this if multiple devices affected.
- Full system reboot helps when services misbehave; use if flush alone fails.
---
12] Common messages and fixes
- “Could not flush the DNS Resolver Cache” → run CMD as admin.
- Still slow after flush → try a different DNS server and check router firmware.
- Sites resolve to wrong IP → inspect hosts file and VPN/proxy settings.
---
13] Safety and notes
- Don’t add random entries to hosts file unless you know what they do.
- Keep router firmware updated — outdated firmware can have DNS bugs.
- If your ISP uses DNS hijacking, consider DNS-over-HTTPS (DoH) in browser settings.
Note: If you enable DoH in browser, the browser bypasses some OS DNS behaviors — handy and private but can complicate troubleshooting.
---
14] FAQ — quick hits
Q: How often should I flush DNS?
A: Only when needed — after ISP/DNS changes, site move, or errors.
Q: Will flushing delete saved passwords or bookmarks?
A: No. Only DNS mappings are cleared.
Q: Does flushing improve speed permanently?
A: Not permanently — it fixes stale entries. Use faster DNS providers for lasting gains.
Q: Can flushing harm my system?
A: No — safe and reversible.
---
What you can take away 📝
- Start with ipconfig /flushdns (admin).
- Then clear browser host cache and do a hard refresh.
- If issues persist, restart router, switch DNS providers, check hosts file, and consider VPN/proxy impacts.
- Keep a small batch script handy — saves time.
Final tip — when you run into weird browsing errors, follow these steps in order. It’s fast. It works. And yes — sometimes it’s just the ISP being dumb.
---
Related: Guide ideas — “enable DNS over HTTPS in Chrome 2026”, “best public DNS for gaming 2026”, “how to check DNS propagation after site move 2026”.
إرسال تعليق