Windows Commands / IT Support Guides
Inspect a stale Windows DNS cache before flushing it
After a service address changes, one workstation may keep using an earlier answer. Preserve its resolver evidence before considering a cache refresh.
Environment and inputs: Windows 11 · Command Prompt unless PowerShell is specified
Try the diagnostic command
Use the stated shell and platform. Replace sample domains, addresses, services and paths with values from the system you are authorized to support.
ipconfig /displaydns
ipconfig /flushdnsHow to read the result
The first command lists locally cached resolver records; the second clears that client cache. A successful flush does not change the upstream DNS record or its TTL.
What to do next
Record the old answer, then run the flush only when appropriate. Resolve the affected name again and reopen the application to see whether its own connection or cache also needs refreshing.
Before you make a change
Flushing removes useful evidence and cannot repair a wrong authoritative record. Browser or application DNS handling may differ from the Windows client cache.