TopicIT Networking →
⌚ About 2 min read
Check which DNS records are returned for a domain.
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.
Use Windows Terminal.
-
2
Test the main recording
Run ns Lookup domaine.fr.
-
3
Test a specific type
With Power Shell, use Resolve-DnsName -Type MX, TXT or A.
-
4
Compare with another solver
You can explicitly query a public DNS to compare the results.
Commands utiles
ns Outlookup informatique.fr
Resolve-Dns(1) boxatoolsinformatique.fr -Type A
Resolve-Dns(1) boxinformatique.fr -Type MX
À retenir
- DNS propagation depends on TTLs and caches.
- An NXDOMAIN response means that the name requested does not exist for the Solveur interrogated.
DNS resolution: separate answer, authority and resolution path
Technical checkpoints
- NXDOMAIN means the name does not exist in the queried view; SERVFAIL means the resolver could not produce a valid answer.
- A/AAAA records provide an address, while CNAME delegates to another name; follow the full chain rather than validating only the first alias.
- Querying an explicit DNS server helps distinguish propagation, caching and local resolver issues.
Compare two resolvers
Query the expected DNS server then another authorized resolver and compare record type, TTL and target.
Resolve-DnsName example.com -Server 192.168.1.10
nslookup example.com 192.168.1.10Topic-specific pitfalls
- Ping can use a different resolution path and does not replace an explicit DNS query.
- Negative caching can preserve an NXDOMAIN until its TTL expires.
How to validate
- Record type, target and TTL match expectations on the authoritative server.
- Client resolvers converge after the expected propagation delay.