Anatomy of a DNS record
Every DNS name can hold several records of different types — addresses, aliases, mail servers, verification strings, service locations. DevOps engineers touch them constantly: pointing domains at load balancers, verifying ownership for ACM and SaaS tools, setting up email authentication so alerts and customer emails don't land in spam, delegating subdomains to other teams, and automating it all from Kubernetes. This topic covers each record type in depth, the rules that trip people up (no CNAME at the apex), Route 53 aliases, email records, and DNS response codes and security.
Fields
- Name — fully qualified; the trailing dot is the root. In zone files, names without a trailing dot are relative to the zone origin, and
@means the zone apex. - TTL — cache lifetime in seconds.
- Class — virtually always
IN(internet). - Type — A, AAAA, CNAME, MX, TXT...
- RDATA — the data, whose format depends on the type.
A record set (RRset) is all records with the same name, class and type — e.g. three A records for api.example.com returning three IPs. They share one TTL and are returned together (often in rotating order — basic DNS round robin).
The zone apex
The apex (or root, "naked domain") is the zone's own name: example.com in the example.com zone. It always holds the zone's SOA and NS records. That fact drives the CNAME rule below.