What the cache does, and how little of it matters
When you open a site, Windows asks a DNS resolver to turn the domain name into an IP address, and it keeps the answer in a small cache so the next visit skips the question. Entries expire on a timer set by the domain — often between one minute and a day — and a fresh lookup takes tens of milliseconds. A page load involves a few lookups, so even in the worst case you are looking at a rounding error next to the actual download of scripts, images and fonts. The browser keeps its own small DNS cache on top of the system one, and if it uses DNS-over-HTTPS, the Windows cache is bypassed entirely.
The cases where flushing genuinely fixes something
The command earns its keep in specific situations, and all of them are about stale or wrong entries rather than speed:
- You edited the hosts file, and Windows keeps serving the old answers until their TTL expires
- A site changed its IP addresses, and your machine keeps dialing the dead one — pages fail or load from the wrong edge server
- You switched between a VPN and the regular network, and the resolver cache holds answers from the wrong side
- A corporate or campus network rotated its internal DNS records, and your PC still remembers the previous ones
- You are debugging DNS itself — testing a new resolver or a filtering setup and needing a clean slate between tries
Why it cannot speed up a healthy connection
When you flush the cache, the next lookup goes upstream — to your router, your ISP's resolver, or a public one like 1.1.1.1 — and those usually still hold the answer, so it comes back nearly as fast. You are re-warming a cache that was already warm, and even a genuinely cold lookup costs milliseconds against page loads measured in seconds. The things that actually make browsing feel slow — a bloated browser profile, twenty extensions, a weak Wi-Fi link, a saturated line — have nothing to do with DNS. If a flush ever "fixed the internet" for you, the real problem was a stale entry, which is a correctness fix, not a performance one.
Questions and Answers
Does flushing the DNS cache make browsing faster?
No. On a healthy connection the cache saves a lookup measured in milliseconds, and upstream resolvers answer almost instantly anyway. Flushing fixes stale-entry errors, not speed.
When should you run ipconfig /flushdns?
After editing the hosts file, when a site's DNS records changed but your machine still reaches the old address, and when lookups misbehave after switching between a VPN and the local network.
Know what is included before you buy.
The one-time 30-minute trial covers core tools. PRO-labelled features stay locked until a paid license is activated.
Read next
Write to us: [email protected]