DNS record lookup
Read the A, AAAA, MX, NS, TXT, and CNAME records currently published for a hostname.
Quick answer
A DNS record lookup asks a resolver for the records a hostname currently publishes. A and AAAA records provide addresses, MX records identify mail exchangers, NS records identify authoritative nameservers, TXT records carry policy or verification text, and CNAME records point one name to another. Empty record types can be normal.
Use DNS records to separate naming from hosting
This page fits incidents where the published name data itself is in question: a new address is not appearing, mail is choosing the wrong exchanger, verification text is missing, or nameservers do not match the intended provider. Query the precise hostname and record type instead of assuming every label beneath a domain shares one answer.
Review a website change
Compare A, AAAA, and CNAME answers with the intended destination and retain the former TTL before calling a rollout complete.
Inspect mail routing
Read MX priority and target names, then resolve those targets separately; an MX record alone cannot confirm that mail is accepted.
Check domain verification
Find the expected TXT value at the exact owner name and avoid exposing unrelated verification strings in a public support report.
Follow the result into the next relevant page
Read how DNS resolution works because it connects caches, resolvers, and authoritative servers; Read hostname-to-IP lookup because it narrows the result to A and AAAA destinations; Read TLS certificate checker because it tests the named encrypted endpoint after resolution.
How to interpret the output
The returned answer is shaped by caching and delegation. A resolver may continue serving an older value until its time to live expires, while the authoritative server already holds a new value. Split-horizon DNS, geographic answers, and provider routing can also make correct responses differ between networks.
A reliable checking workflow
Check the exact hostname rather than assuming the bare domain and its www name are interchangeable. Read A and AAAA separately, follow CNAME chains, and confirm MX priorities and NS delegation. After a planned change, compare the authoritative answer with at least one recursive resolver and allow the former TTL to expire before declaring propagation broken.
Key ideas behind dns record lookup
DNS is a set of record types, not one address book entry. Choose the record that answers your question, then account for cache time before deciding a change failed.
Web destinations
A and AAAA records publish IPv4 and IPv6 addresses; CNAME records point one name to another.
Mail delivery
MX records name mail exchangers, while TXT records often carry SPF or verification policy.
Authority
NS records identify the nameservers responsible for a DNS zone, but caches may still hold older answers.
Example: a DNS change looks correct in one place only
You change an A record from 192.0.2.10 to 192.0.2.20. The authoritative server returns the new value, but a recursive resolver still returns the old one. If the old time to live has not expired, both observations can be normal. Record the resolver and TTL instead of repeatedly editing the zone.
The boundary that matters
A DNS response does not prove that the destination accepts connections or that every user receives the same answer. TXT text is not automatically trustworthy, and an MX record does not certify mail delivery. DNSSEC can authenticate signed data but does not encrypt ordinary queries or validate the service reached after resolution.
How the main entities relate
| Subject | Relationship | Object |
|---|---|---|
| A record | maps a name to | an IPv4 address |
| MX record | directs mail toward | a mail exchanger |
| TTL | limits | how long a cached answer may remain |