What this check shows
A global DNS lookup compares how independent recursive resolvers answer the same DNS question. This helps separate a local cache problem from a wider DNS, delegation or provider issue.
DNSRadar queries global resolvers in parallel and reports the returned value, status and latency so you can confirm whether a record is consistent worldwide.
When to use it
- Checking any DNS record after a change
- Comparing local DNS with public resolvers
- Finding stale cached answers
- Collecting evidence for hosting or DNS support
How to read the result
- Matching answers across providers normally indicate the record is globally stable.
- Different answers can be valid for CDNs, but unexpected differences after a migration usually point to caching or authoritative inconsistency.
- Consistent NXDOMAIN, SERVFAIL or timeout states should be investigated at the authoritative DNS and delegation level.
Command examples
Use these dig commands when you need to compare DNSRadar with a terminal check or collect evidence for a DNS provider.
dig example.com A +short
dig @1.1.1.1 example.com A
dig @8.8.8.8 example.com A +noall +answerTroubleshooting focus
Use this page when you need one place to compare any DNS record type across independent resolvers. It is most useful when the symptom is unclear: a website may fail because of A, AAAA, CNAME, NS, DNSSEC or provider routing, while email problems often require MX and TXT checks together.
Practical examples
- Check A and AAAA records together when users report that only some networks can reach a website.
- Compare MX and TXT records during an email provider migration to confirm both routing and authentication.
- Look up NS and SOA records when a domain works in one resolver but returns NXDOMAIN or SERVFAIL in another.
- Use CAA before TLS renewal if a certificate authority reports that issuance is not allowed.
Common mistakes
Checking only the record that changed
A DNS migration can expose related problems in NS, SOA, CNAME, MX or TXT records.
Assuming every difference is wrong
CDNs and load balancers may return multiple valid addresses, so read differences together with provider context.
Ignoring resolver status codes
NXDOMAIN, SERVFAIL, timeout and no-answer mean different things and require different fixes.
Skipping authoritative checks
Recursive resolver data is useful, but persistent disagreement should be confirmed at the authoritative nameservers.
Questions
Which DNS record types can I check?
DNSRadar supports A, AAAA, CNAME, MX, TXT, NS, SOA, PTR, SRV and CAA lookups from the same global checker.
Why use a global DNS lookup instead of my computer?
Your computer usually queries one resolver. A global lookup shows whether other networks already see the same DNS answer.