DNS comparison
DNS propagation checker vs DNS lookup
A DNS lookup tells you what a resolver answers now. A DNS propagation checker compares whether many resolvers agree after a change. The DNS query may be similar, but the diagnostic question is different.
Main difference
DNS propagation check
Best after a DNS change. It looks for agreement, stale values, partial propagation, NXDOMAIN, SERVFAIL and resolver-specific timeouts across public resolvers.
DNS lookup
Best when you need to inspect a record type directly. It answers questions like: what is the current A record, MX target, TXT policy or CNAME alias?
Use cases
Changing hosting
Run a propagation check for A and AAAA, then inspect CNAME if the hostname points to a CDN or managed platform.
Changing email provider
Check MX propagation first, then inspect TXT records for SPF, DKIM and DMARC.
Changing nameservers
Check NS and SOA globally, then query authoritative nameservers directly if serials or delegations differ.
Seeing SERVFAIL
Do not treat this as normal propagation. Check DNSSEC, DS records and authoritative nameserver reachability.
How to interpret results
- All resolvers return the intended value: the public recursive layer is broadly consistent.
- Some resolvers return the old value: usually cached data that has not expired yet.
- Authoritative nameservers disagree: this is a zone consistency problem, not normal propagation.
- Many validating resolvers show SERVFAIL: investigate DNSSEC before making more record changes.
Useful checks
Questions
Are DNS propagation checks and DNS lookups the same?
They use similar DNS queries, but the intent is different. A propagation check compares resolver agreement after a change, while a lookup inspects the current answer for a record.
Which one should I use after a migration?
Use a propagation checker first, then inspect specific record types such as A, AAAA, CNAME, MX, TXT, NS or SOA when you see a mismatch.
Can a global DNS lookup detect propagation issues?
Yes, if it compares multiple resolvers. The difference is in how you interpret the result: consistency and stale values matter more than a single answer.
What if every resolver returns NXDOMAIN?
That usually means the name is missing or delegation is broken. Check NS and SOA records, then query authoritative nameservers directly.