TopicIT Networking →
⌚ About 2 min read
Clear locally stored DNS entries when a site or server points to a wrong address.
Avant de commencer : adaptez toujours les commandes et manipulations à votre environnement. Sur un système de production, prévoyez une backup ou un retour arrière lorsque l’action peut modifier la configuration.
Étapes à suivre
-
1
Open a terminal.
Open Windows Terminal or l, prompt commands.
-
2
Empty DNS cache
Run ipconfig /flushdns.
-
3
Check Result
Windows must confirm that the DNS resolution cache has been emptied.
-
4
Retester the name
Then try nslookup namedomain.fr or restart the affected application.
Commands utiles
ipconfig /flushdns
ns Outlook example.fr
À retenir
- Emptying the local cache does not alter public DNS records.
- A DNS cache may also exist in the browser, router or intermediate solver.
Windows DNS cache: what is actually cleared
Technical checkpoints
- ipconfig /flushdns clears the local DNS Client cache; it does not clear a DNS server cache or an application/browser cache.
- Get-DnsClientCache shows cached entries and their TTL.
- Restarting Dnscache is more intrusive than a flush and is normally unnecessary just to invalidate an entry.
Before / after
Inspect the entry, clear the cache, then resolve the same name again using the same DNS server.
Get-DnsClientCache
ipconfig /flushdns
Resolve-DnsName example.comTopic-specific pitfalls
How to validate
- The name resolves to the expected address and the response source is identified.
- TTL and cache behavior are consistent with the expected DNS change.