Website
DNS Records Explained for Website Owners
A plain-language guide to A, AAAA, CNAME, MX, and TXT records with a safe change sequence.
A plain-language guide to A, AAAA, CNAME, MX, and TXT records with a safe change sequence.
Direct answer: DNS records map names to destinations or service instructions. For a website task, identify the exact hostname and record purpose before changing anything: A and AAAA route to addresses, CNAME aliases one name to another, MX routes mail, and TXT carries verification or policy data.
Read a record as a set of fields
Record type, name, value, TTL, and provider-specific proxy behavior all matter. An A record for the root hostname is not interchangeable with a CNAME for a subdomain. A proxy service can change what is publicly returned while the authoritative DNS record remains different.
Safe change sequence
- Inventory the current zone and identify mail, verification, and application dependencies.
- Confirm the exact hostname and destination with the service owner.
- Export or record the before state and choose a low-risk change window.
- Make one small change, then query authoritative and recursive resolvers.
- Verify HTTPS, redirects, mail, and application health before making a second change.
DNS propagation is a cache behavior, not a reason to make repeated blind edits. If a certificate mismatch or redirect loop appears, use the before record and the service’s documented rollback path. Never include project credentials or private incident details in a public example.
This guide separates documented platform behavior from interpretation and identifies the source behind material claims.