DNS records are database entries used to map a domain name to a resource, such as an IP address (A/AAAA), a mail server (MX), or another name (CNAME). Each record contains specific fields, including a name, type, TTL (Time to Live), and data relevant to the record type. These records are stored in zone files on authoritative nameservers.
Correct record configuration is necessary for the proper functioning of internet services. Misconfigured records can cause email delivery failures, website downtime, or security vulnerabilities like subdomain takeover. TTL values affect how quickly changes propagate across the internet.
Manage DNS records via code. Using Infrastructure as Code (IaC) for DNS management provides an audit trail, enables peer reviews, and reduces the risk of manual error. We favor short TTLs during migrations to allow for rapid rollback, reverting to standard values once the state is stable. Avoid using CNAME records for root domains when an ALIAS or ANAME record can maintain better performance.