NetworkEdge resolution

DNS Lookup

Query A, AAAA, MX, TXT, and NS records for any domain in one lookup.

Quick presets
🌐

Authoritative DNS Multi-Record Resolver

Enter a domain above to query A, AAAA, MX, TXT, NS, and CNAME records in one lookup.

Technical specification & engineering details

What this tool does

Queries a domain's DNS records — A, AAAA, MX, TXT, NS, and CNAME — and returns everything currently published, all in one lookup instead of running separate queries for each record type.

When you'd use this

Confirming a DNS change has actually taken effect, verifying a new server's IP is correctly published before cutting over traffic, checking that a domain's mail routing (MX) and verification (TXT) records are set up as expected, or simply auditing what's publicly published for a domain you manage.

Why results can lag a recent change

DNS records are cached for the duration of their TTL (time-to-live) by resolvers between you and the authoritative nameservers. A record with a 3600-second TTL can take up to an hour to be consistently visible everywhere after a change, even though the authoritative server itself already has the new value — this is normal DNS propagation, not a sign the change failed.

Frequently asked questions

Why does this show different results than my local `nslookup`?

Your local resolver may have a cached (stale) answer from before a recent change. This tool queries fresh each time, so it reflects the current published records rather than a locally cached copy.

Why do I see multiple IP addresses for one A record?

That's round-robin DNS — the domain is intentionally pointed at several servers for load balancing or redundancy, and different queries may return them in a different order.

Why is the TTL not what I expected?

TTL controls how long resolvers are allowed to cache a record before re-checking it. If it was recently lowered (common right before a migration) or raised, what you see now reflects that change, not an error in the lookup.