Comprehensive User Guide & Practical Applications
1. Start with the exact hostname
Enter the domain or subdomain you want to inspect, such as example.com or www.example.com. DNS records belong to names, so checking the apex does not automatically show records configured only for www or mail.
2. Choose a focused record type
Select A or AAAA to investigate web-address mapping, MX for mail routing, NS for delegation, TXT for published text, or CAA for certificate-authority policy. Use All common records for a broad first pass.
3. Read A and AAAA answers
An A record maps a name to an IPv4 address; AAAA maps it to IPv6. Example: if www.example.com returns 203.0.113.10, that is the IPv4 address reported by this resolver at query time, not proof that the server is healthy.
4. Check aliases carefully
A CNAME answer points one DNS name to another, for example www.example.com → example.hosting.net. Follow the target to understand the chain; the final address can change independently. A CNAME generally cannot coexist with other data at the same owner name.
5. Diagnose mail delivery
Inspect MX records and their preference values. Lower preference numbers are tried first, but the target host must also resolve and accept mail. Compare the MX targets with the email provider’s setup instructions before changing records.
6. Review TXT, SPF and verification values
TXT records may publish SPF, DKIM, DMARC or service-verification data. A DNS lookup only displays published values; it does not validate policy syntax or prove that a mail service is configured securely. Avoid sharing sensitive tokens publicly.
7. Use TTL to reason about caching
TTL is the time a resolver may cache an answer, in seconds. After changing a record, a resolver can continue serving an older cached value until its remaining TTL expires. Example: a 3600-second TTL can mean up to about an hour of cache life, not a guaranteed global propagation deadline.
8. Compare results before editing DNS
Record the queried name, type, answer, resolver context and time. If the result differs from your authoritative DNS dashboard, compare nameservers and query another independent resolver; make one controlled change and verify again after the relevant TTL.
Technical Foundations
DNS resolution path
A stub resolver asks a recursive resolver to find an answer. The recursive resolver may consult root, top-level-domain and authoritative nameservers, then cache the result. This tool queries from the site’s server environment, so geography, resolver policy and cache state can differ from a laptop or public resolver.
RFC 1034: Domain Names — Concepts and Facilities
A, AAAA, CNAME and address mapping
A stores an IPv4 address and AAAA an IPv6 address. A CNAME aliases one owner name to another canonical name; resolvers continue lookup at the target. Example: shop.example.com CNAME store.vendor.example can eventually resolve to an A or AAAA record. DNS providers may offer flattened aliases at a zone apex, but that behavior is provider-specific.
RFC 2181: Clarifications to the DNS Specification
MX, NS and SOA records
MX records identify mail exchangers and preference order; NS records identify delegated nameservers; SOA carries zone metadata including a serial and timing fields. For email, check that each MX target resolves and that its priority matches the provider’s published configuration. A mismatch in NS delegation can make correct-looking records at the wrong provider irrelevant.
RFC 1035: Domain Names — Implementation and Specification
TXT, SPF, DKIM and DMARC
TXT is a general text-record mechanism often used by email authentication and ownership checks. SPF policy is published in TXT, DKIM publishes a public key under a selector, and DMARC policy is commonly at _dmarc.example.com. A lookup displays data but does not evaluate alignment, message headers, key rotation or policy correctness; use the relevant provider’s validator.
RFC 7208: Sender Policy Framework (SPF)
CAA and certificate issuance
CAA records let a domain owner specify which certificate authorities may issue certificates for the name. An absent CAA record does not itself mean HTTPS is broken; issuance rules and inherited policy should be checked with the certificate authority and DNS standards. Example: inspect example.com and the exact subdomain before changing an issuance policy.
RFC 8659: DNS Certification Authority Authorization (CAA)
TTL, caches and change windows
A resolver caches positive answers for the record TTL and may cache negative answers under separate rules. Lowering TTL shortly before a migration does not erase copies already cached under the previous TTL. Plan changes ahead, keep old endpoints available during the transition when practical, and verify from multiple resolvers after cache lifetimes expire.
RFC 2308: Negative Caching of DNS Queries
NXDOMAIN, NODATA and failures
NXDOMAIN means the queried name does not exist according to the responding DNS path; NODATA means the name exists but has no record of the requested type. Timeouts or SERVFAIL indicate a different failure path and may involve delegation, DNSSEC validation or resolver trouble. Confirm the exact hostname and query type before concluding that the whole domain is missing.
RFC 2308: Negative Caching of DNS Queries
DNSSEC and the limits of this lookup
DNSSEC adds signatures that allow validating resolvers to check DNS data integrity. A displayed answer alone does not prove that the DNSSEC chain validates. Check DS records at the parent, DNSKEY and signatures in the zone, and a validating resolver; coordinate DS changes carefully to avoid making the zone bogus.
RFC 4033: DNS Security Introduction and Requirements