When the DNS has just been modified or a post keeps an old answer, emptying the local cache and comparing resolutions allows quickly to isolate the problem.
Steps.
- Show cache if necessary — Identify the relevant entries before deleting them if you need to understand what the post used.
- Clear cache — Run ipconfig /flushdns in a command prompt.
- Solve Name — Use nslookup or Resolve-DnsName on the relevant FQDN.
- Compare DNS servers — Check in ipconfig /all which solvers are actually used.
- Test Resource — Check the application after validation of the address obtained.
Commands
ipconfig /displaydnsipconfig /flushdnsnslookup server.domaine.localResolve-DnsName server.domaine.localKey takeaways
- A DNS flush does not correct an erroneous DNS area.
- The browser and some applications sometimes have their own cache.
- Take into account the server-side TTL and intermediate solvers.