devopscodepro
Language
server-assisted

DNS lookup

Query any record type for a domain — A, AAAA, MX, TXT, NS, CAA, SRV, PTR and more, with TTLs.

one query against a public recursive resolver — nothing is stored
Enter a domain and pick a record type.

How the lookup works

One question goes to a public recursive resolver and the answer comes back as the resolver returned it — records, TTLs, the response code, and the authority section when there is nothing to answer with. It is the equivalent of a single dig, without the terminal.

The record type you choose is the question that gets asked. A domain that resolves fine for A can return nothing for MX, and that difference is usually what you are looking for.

Why does NXDOMAIN differ from an empty answer?

NXDOMAIN means the name does not exist at all. An empty NOERROR means the name exists but has no record of the type you asked for — the domain is fine, it simply has no MX, or no AAAA. Confusing the two sends people debugging the wrong thing.

Why do I still see the old value after changing a record?

You are seeing the resolver's cache, and it will hold the answer for as long as the previous TTL said. The TTL shown next to each record is how long a resolver may keep it. Nothing you do at the registrar shortens a value that was already handed out.

Can I look up an IP address?

Yes, with the PTR type — that is the reverse lookup. The tool converts the address to its .arpa name for you. Other record types are meaningless for an IP and are rejected rather than silently returning nothing.

Which resolver answers my query?

A public recursive resolver, shown with the result. That means you see what the internet sees, not what your office resolver or split-horizon DNS would return — which is usually the comparison you want when something works internally and fails outside.

Related tools: DNS health, WHOIS lookup and GeoIP lookup.