Skip to content
AdminKit

How do you read a DNS lookup result (A, AAAA, CNAME, MX, TXT, NS)?

AdminKit's DNS lookup tool returns one record type per query: A/AAAA give the IPv4 or IPv6 address a hostname points to, CNAME gives an alias, MX gives mail servers and priority, TXT gives arbitrary text such as SPF strings, and NS gives the authoritative name servers for the zone — a lookup only shows the type you asked for.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • A DNS lookup answers one question: which records of one type exist at one name. Ask for A and you get A records only, never the MX or TXT records at the same name.
  • Each row in a result has four parts: the name, the record type, the TTL in seconds and the data. The data column is what changes meaning from type to type.
  • “No records found” covers two different situations: the name doesn’t exist at all (NXDOMAIN), or it exists but has no record of that type (NODATA).
  • The TTL you see is usually the time left in the resolver’s cache, not the value set in the zone, so it drops between two lookups.
  • A CNAME in an A or AAAA result is normal: the resolver followed the alias and shows each step.

Why doesn’t one lookup show every record for a domain?

A common misconception is that a domain has one DNS “entry” that a lookup reveals all at once. It doesn’t. RFC 1035 defines DNS as a collection of independent resource record (RR) types, each with its own format and its own purpose, and a single name can publish several different types at once — an A record, an MX record and a TXT record can all exist at example.com. simultaneously, as entirely separate records that happen to share a name. A lookup always queries one specific type at a time; AdminKit’s DNS lookup tool queries Cloudflare’s public DNS-over-HTTPS resolver on your behalf and supports A, AAAA, MX, TXT, NS, CAA, PTR, SOA and CNAME, showing each as its own result rather than one combined record.

What does each column in a lookup result mean?

AdminKit’s DNS lookup shows every answer as a row with four columns. Cloudflare’s resolver returns these same fields in its DNS-over-HTTPS JSON format, and the tool passes them through without adding anything. Google Public DNS documents the same layout in its JSON API for DNS over HTTPS: each answer carries a name, a numeric type, a TTL in seconds and the data as text.

Example result (illustrative values, documentation addresses)
Lookup: www.example.com, type A

Name              Type    TTL     Data
www.example.com   CNAME   3600s   example.com.
example.com       A       1742s   192.0.2.10
example.com       A       1742s   192.0.2.11
ColumnWhat it tells youWhat it doesn’t
NameThe owner name of this record. With a CNAME chain, later rows can show a different name from the one you typed.Whether the name is the zone apex or a subdomain
TypeThe record type of this row. An A lookup can return a CNAME row as well as A rows.Any type you didn’t ask for
TTLHow many seconds the resolver may keep serving this answer from cacheThe value configured in the zone, if the answer came from cache
DataThe record content: an address, a hostname, a priority plus hostname, or textWhether the address or host behind it is reachable

A and AAAA: which address does a name point to?

A records (RFC 1035 §3.4.1) map a hostname to an IPv4 address — the most basic DNS record type, and the one that lets a browser turn example.com into a routable address. AAAA records (RFC 3596) do the identical job for IPv6, as a separate record type with a separate four-times-longer address format rather than an extension of A. A domain can publish both at once (a “dual-stack” setup), only one, or several of either type for load distribution or redundancy — a resolver returning multiple A records for one name is normal, not an error, and clients are free to try them in any order. A result can also come from a wildcard DNS record answering for every subdomain that lacks its own entry, rather than one created specifically for the name you queried.

CNAME: why does an alias show up in an address lookup?

A CNAME record (RFC 1035 §3.3.1) doesn’t hold an address at all — it holds another hostname, telling the resolver “look up whatever this other name resolves to instead.” It’s how a domain points www.example.com at example.com, or a custom domain at a hosting platform’s own infrastructure, without needing to track that platform’s IP addresses directly. One important restriction: RFC 1035 does not allow a CNAME to coexist with any other record type at the exact same name, which is why you cannot add, say, a TXT record directly on top of a name that already has a CNAME pointing elsewhere — it has to go on a different name, or the CNAME has to move. Cloudflare’s own explainer on CNAME records confirms this the same way working DNS providers implement it: a name with a CNAME can’t also answer for any other record type.

When you ask for A or AAAA at a name that has a CNAME, the resolver follows the alias for you. RFC 1034 §3.6.2 describes this: the resolver restarts the query at the target name and returns the CNAME together with what it found there. That is why the example above has a CNAME row followed by A rows for a different name. Each step in the chain has its own TTL, so the rows can show different TTL values.

MX: where does mail for the domain actually go?

MX records (RFC 1035 §3.3.9) list the hostnames authorized to receive mail for a domain, each with a priority (preference) number — lower numbers are tried first. A lookup against example.com for MX type shows these hostnames and priorities but not whether they’re actually reachable; that needs a follow-up A/AAAA lookup on each returned hostname, which AdminKit’s dedicated MX lookup tool does automatically. See what MX record priority actually does for how the priority ordering and ties between equal-priority records work in practice.

TXT: why does one name return several unrelated strings?

TXT records (RFC 1035 §3.3.14) hold arbitrary text, originally meant for human-readable notes but now used almost entirely for machine-readable policy strings: SPF (v=spf1 ...), domain-ownership verification tokens for services like search consoles or cloud platforms, and DKIM public keys published at a selector subdomain. A single name can carry multiple TXT records at once, which is why a DNS lookup on a busy domain’s root name often returns several unrelated-looking text strings — each one belongs to a different system that happens to use the same record type to publish its data.

NS: who is authoritative for the whole zone?

NS records (RFC 1035 §3.3.11) list the nameservers authoritative for an entire zone, not just one name — they answer the question “who do I ask about anything under this domain” rather than describing one specific record. The NS records that actually get used are the ones delegated at the parent zone (set through your registrar), which should match what your DNS provider’s own zone reports about itself; a mismatch between the two is a common, often overlooked cause of DNS changes not taking effect anywhere, since resolvers follow the registrar-level delegation, not your provider’s internal records, to find the zone in the first place.

The other types the tool supports follow the same pattern. This table is a quick reference for what the data column holds for each:

TypeData column holdsExample data
A / AAAAAn IPv4 / IPv6 address192.0.2.10 / 2001:db8::10
CNAMEAnother hostnameexample.net.
MXPreference, then mail host10 mail.example.com.
TXTOne or more quoted strings"v=spf1 -all"
NSA nameserver hostnamens1.example.net.
CAAFlag, tag, CA domain0 issue "letsencrypt.org"
SOAPrimary server, contact, serial and timersns1.example.net. hostmaster.example.com. 2026111001 7200 3600 1209600 3600
PTRThe hostname for an address (reverse zone)host.example.com.

For CAA, see what CAA records are; for the SOA timers, see SOA records explained.

What does “no records found” actually mean?

When the tool reports that no records of a type were found, the resolver gave one of two different negative answers. RFC 2308 names them:

  • NXDOMAIN (name error): the name itself doesn’t exist. Nothing of any type is published there. A typo in the name is the usual cause.
  • NODATA: the name exists, but there is no record of the type you asked for. Asking for AAAA on a name that only has an A record gives this answer.

The tool shows both as an empty result, because both mean “nothing of this type here”. To tell them apart, query the same name with a command-line client and read the status field:

Example output (illustrative, abbreviated)

$ dig www.example.com AAAA
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4242
;; ANSWER SECTION:            <- empty: the name exists, no AAAA (NODATA)

$ dig wwww.example.com A
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 4243
                              <- the name does not exist at all

Both kinds of negative answer are cached too. RFC 2308 sets their cache time from the zone’s SOA record, which is why a record you just created can stay “missing” for a while on a resolver that recently looked for it.

Why is the TTL lower than the value I set?

The TTL in a zone is fixed, but a resolver’s cached copy counts down. RFC 1035 (§7) describes TTLs for cached data that “conceptually count down, while data in the zone stays with constant TTLs.” A resolver that answers from its cache reports the time it has left. If you set a TTL of 3600 and the tool shows 1742, the resolver fetched the record about half an hour ago and will keep using it for another 1742 seconds. Look up the same record again a minute later and the number will be about 60 lower.

That count-down is the reason a change you just made can take a while to show up — see DNS propagation and TTL explained for how long that realistically takes. Before assuming a result is wrong, confirm you’re querying the record type you intend, that you’ve waited out the previous value’s TTL, and that the registrar-level NS delegation actually points at the DNS provider you think it does.

Which records won’t this lookup show?

AdminKit’s DNS lookup covers the nine types listed above. Some record types need their own tool or a command-line client:

  • DNSSEC records (DNSKEY, DS, RRSIG). Use AdminKit’s DNSSEC check, which asks a validating resolver whether the domain is signed and whether the chain validates.
  • SVCB and HTTPS records. See how to read an SVCB/HTTPS DNS record for what they hold.
  • Answers from a specific nameserver. The tool always asks the same public resolver. To query your authoritative nameserver directly, or to compare resolvers, see DNS answers that differ between resolvers.

If you need a wider set of record types than AdminKit’s own tool supports, or the ability to query a specific nameserver directly, see how AdminKit’s DNS lookup compares to Dig Web Interface.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Why does looking up a domain's A record not show its MX or TXT records too?

Because DNS stores each record type separately, even at the same name. A query for the A type only returns A records; you need a separate query (or a separate panel in a tool like AdminKit's DNS lookup) for MX, TXT, NS or any other type published at that name. There is no single 'everything about this domain' record — RFC 1035 defines each resource record type with its own format and purpose.

A domain has both an A record and a CNAME at the same name — is that normal?

No, and it isn't valid DNS. RFC 1035 requires that if a CNAME record exists for a name, no other record type can coexist at that exact name (the one standard exception is DNSSEC-related records at the same name). A CNAME pointing to another host is instead expected to resolve further by following that alias to wherever its own A or AAAA record lives.

What does it mean if a lookup returns multiple A records for the same hostname?

It means the domain publishes more than one IPv4 address for that name, which a resolver is free to return in any order or rotate between — a simple, DNS-level way to spread traffic across multiple servers or provide basic redundancy if one address stops responding. This is normal and common for high-traffic sites; it does not mean the domain is misconfigured.

My NS lookup shows different nameservers than my DNS provider's dashboard — what's wrong?

Usually nothing is wrong with your DNS provider's records; the mismatch is almost always at the registrar. The NS records a resolver actually uses come from delegation records set at the registry/registrar level, not from what your DNS provider's own zone file says about itself — if those two disagree, the registrar-level delegation wins. Confirm the registrar's nameserver delegation matches what you intend to use.

Why does a DNS lookup sometimes return no result for a record type I know exists?

The most common reasons are querying the wrong record type for that name (for example, looking up A on a name that only has a CNAME), a very recent change that hasn't propagated to the resolver you're querying yet, or a genuinely empty record set at that name. A resolver only ever reports what the authoritative servers for that zone currently return for the exact type and name you asked about.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.