Practical guide
How to use the dns lookup
The DNS lookup returns common public records for a domain, including address, mail, nameserver, alias and text records. It helps you see what resolvers can discover now, after propagation and caching have been taken into account.
Good reasons to use it
- Verify A and AAAA records after a hosting or CDN migration.
- Check MX, TXT and CNAME records during email or service verification.
- Compare public DNS with the values configured at the authoritative provider.
A reliable workflow
- Enter the bare domain or hostname.
- Review each returned record type, value and priority where relevant.
- Confirm unexpected values at the authoritative DNS provider before editing them.
How to interpret the result
DNS answers can vary because of caching, geographic routing, split-horizon configuration and propagation. An empty result can mean the record does not exist, the resolver timed out, DNSSEC failed or the queried name is not public.
Frequently asked questions
How long does DNS propagation take?
It depends on the previous TTL, resolver cache and provider. Many changes appear quickly, but cached answers may remain until their TTL expires.
Why are there several A or AAAA records?
Multiple addresses can provide load distribution, redundancy or CDN routing. They are not automatically duplicates.