The main records you will encounter
DNS is not just a domain-to-IP lookup. A DNS zone can publish several record types that support websites, email routing, validation and service discovery. Reading the correct type is essential when diagnosing a failure.
| Type | Typical purpose |
|---|---|
| A | Maps a name to an IPv4 address |
| AAAA | Maps a name to an IPv6 address |
| CNAME | Aliases a name to another canonical name |
| MX | Identifies mail exchangers and priorities |
| NS | Identifies nameservers for a zone or delegation |
| TXT | Stores text used for verification and policy |
| SOA | Identifies administrative zone metadata |
| CAA | Specifies allowed certificate authorities |
| SRV | Defines service host and port information |
| PTR | Supports reverse address-to-name mapping |
| DS / DNSKEY | Participate in DNSSEC validation chains |
Practical examples
If a website fails but email works, look first at A, AAAA and CNAME records and the server itself. If mail delivery fails, inspect MX, SPF, DKIM and DMARC. If an SSL certificate cannot be issued, CAA and DNS ownership verification may matter.
What TTL tells you
Each DNS answer generally includes a time-to-live value. It helps explain why a resolver may continue serving an older record after a change. TTL is a cache lifetime hint, not a guarantee that every device will update at the same exact moment.
How to explore a zone
Use our DNS Record Lookup to query each type. A public recursive lookup does not expose every possible record in a zone: querying an unknown name or record type can return no answer even though the zone contains other data.
Reference: RFC 1035: Domain Names — Implementation and Specification.
Editorial note: This is general educational information, not a live audit. DNS behavior and provider policies can change, and results should be verified against authoritative sources.