Home / Blog / DNS Records Explained: A, CNAME, MX, TXT and TTL

DNS

# DNS Records Explained: A, CNAME, MX, TXT and TTL

Published 19 April 2026 · By the Bryzora team

Dns Explained · Bryzora field notes

Published 30 October 20266 min readBy the Bryzora team

DNS turns names people can remember into the addresses computers use. When it is configured well nobody notices it, and when it breaks nothing works. Here are the records you will meet most often.

## The common record types
RecordWhat it does
APoints a name to an IPv4 address
AAAAPoints a name to an IPv6 address
CNAMEMakes a name an alias of another name
MXSays which mail servers accept email for the domain
TXTHolds text, often used for email authentication and ownership checks
NSLists the authoritative name servers for the domain
CAARestricts which certificate authorities may issue certificates
SOAHolds zone details such as the serial number

## A and AAAA

These are the simplest records. www.example.com has an A record with an IPv4 address and, if you support IPv6, an AAAA record with an IPv6 address. Visitors reach whichever address their network prefers.

## CNAME

A CNAME does not hold an address. It says that one name is an alias of another, and resolvers then look up the target name. It is commonly used to point www or a subdomain at a hosting provider. A name that has a CNAME cannot also carry other records, which is why a CNAME is usually not allowed at the root of a domain.

## MX and TXT

MX records route email, with a priority number so that a backup server can take over. TXT records carry text, and are used for SPF, DKIM and DMARC email authentication, as well as for proving you own a domain to another service. A mistake here rarely takes your website down, but it can quietly send your email to spam.

## What TTL means

Every record has a time to live, or TTL, in seconds. It tells resolvers how long they may cache an answer. A long TTL reduces lookups, but changes take longer to reach everyone. Before a planned migration, many teams lower the TTL a day or two ahead so the switch propagates quickly, then raise it again afterwards.

## Which changes are worth monitoring
- A and AAAA records for your main hostnames, in case traffic is redirected
- MX and TXT records, in case email delivery breaks
- NS records, because a change there moves control of the whole zone
- CAA records, if you restrict certificate issuance

Tip. Keep a history. When something stops working, the first question is usually what changed, and a record of past values answers it quickly.

### Watch your website the way this guide describes.

Start with the free Explorer plan and add checks as your needs grow.Get Started with Bryzora ↗

ChecklistThe Website Monitoring Checklist

A practical checklist of twelve things to monitor on every website, from uptime and SSL…Read more →ReliabilityWhy Uptime Monitoring Matters

What uptime percentages mean in minutes, why customers notice before you do, and how to start…Read more →

All guidesNewer guideThe Website Monitoring Checklist: 12 Things Worth WatchingOlder guideWhy Uptime Monitoring Matters (and What 99.9% Really Allows)