Flush the DNS resolver cache on Windows
Purge cached DNS lookups so Windows re-resolves hostnames from scratch — the fix for 'the new server is live but my browser still hits the old one'.
01Command
$ ipconfig /flushdns02What it does
Windows caches every DNS answer locally (using whatever TTL the record carries), so an updated record can keep pointing you at the old IP for hours. Run `ipconfig /displaydns` first if you want to see exactly which names and addresses are cached. Flushing is instantaneous and safe — it only forces future lookups to query DNS servers again; browser-internal caches (Chrome has its own) may also need a restart.
03Risk
04Undo
✓No undo needed — this command does not change persistent state.
05Sources
- ipconfig | Microsoft LearnEvidence: Microsoft documents that 'ipconfig /flushdns' flushes and resets the contents of the DNS client resolver cache, and that /displaydns displays its contents.
- IPCONFIG - Windows CMDEvidence: SS64 lists /displaydns to view cached DNS entries and /flushdns to purge the DNS resolver cache.
Last verified: 2026-09-17 · Category: Network
06Related solutions
A built-in PowerShell one-liner that answers 'is port 5432/3389/443 actually open through this network?' — no telnet client needed.
Display the IP-to-MAC address cache Windows built by talking to neighbors — a quick way to spot which devices are on your subnet.
The modern, scriptable replacement for nslookup: ask for exact record types, hit specific DNS servers, and see TTLs as objects.