Modern web browsers maintain their own internal DNS cache, separate from your computer's operating system. If a website loads the old version after a DNS change, you must clear the browser's DNS cache. In Chrome or Edge, type chrome://net-internals/#dns into the address bar and click 'Clear host cache' to force the browser to fetch the new IP address.
OS DNS Cache vs Browser DNS Cache
Your computer has two separate DNS caches:
The problem: You flushed your OS cache with ipconfig /flushdns (Windows) or sudo dscacheutil -flushcache (Mac), but your browser still loads the old site.
Why: Browsers maintain their own DNS cache for faster lookups. This cache persists even after clearing the system cache.
The fix: Clear the browser's internal DNS cache using browser-specific methods.
Why It Matters: Bypass Stubborn Redirects
- Changed your site's IP address but still see the old version
- Migrated to a new host but browser loads the previous server
- DNS propagation complete globally, but your browser disagrees
- Clearing browsing history
The browser's DNS cache operates independently. You need the specific DNS flush command.
Decision Framework: Clear History vs Clear DNS
Standard cache clearing deletes files, images, CSS, cookies.
DNS cache clearing deletes routing information, the IP address your browser associated with the domain.
Different problems require different solutions.
Implementation Steps: Clear DNS by Browser
Google Chrome
chrome://net-internals/#dns
- Paste URL above into address bar
- Also visit
chrome://net-internals/#sockets and click "Flush socket pools"
Microsoft Edge
edge://net-internals/#dns
Mozilla Firefox
Safari (macOS)
- Go to Safari → Settings → Advanced
- Check "Show features for web developers"
- Click Develop menu → Empty Caches
Note: Safari doesn't have a dedicated DNS-only flush. Empty Caches clears all cached data including DNS.
Common Mistakes
Clearing cookies expecting DNS fix: Cookies store login data and preferences, not IP addresses. They won't affect routing.
Only clearing OS cache: System DNS flush doesn't touch browser DNS. Do both.
Not restarting the browser: Some browsers require full restart for DNS changes to take effect.
Skipping socket pools (Chrome): For stubborn issues, also flush socket pools at chrome://net-internals/#sockets.
What This Means for You
Before troubleshooting browser caches, verify your DNS records are correct. Use NameSilo's DNS Manager to confirm your A records point to the right IP. If records are correct but your browser disagrees, clear the browser DNS cache using the methods above.
Frequently Asked Questions
What is a browser DNS cache?
Internal storage mapping domain names to IP addresses.
How do I clear DNS cache in Chrome?
Visit chrome://net-internals/#dns → Clear host cache.
Does clearing cookies clear DNS cache?
No. Cookies and DNS are separate systems.
How do I clear DNS cache in Safari?
Enable Develop menu → Develop → Empty Caches.
Why is my browser showing an old version of a website?
Browser DNS cache holds outdated IP addresses.
What does net-internals/#dns do?
Opens Chrome's internal DNS management page.
How do I clear DNS cache on a Mac?
Terminal: sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
How long does a browser cache DNS?
Varies by browser, typically minutes to hours.
.png&w=3840&q=75)
.png&w=2048&q=75)
.png&w=3840&q=75)
