DNS records are the instructions that tell the internet where to find things for your domain. The ones most domain owners deal with are: A and AAAA (point a name to an IPv4 or IPv6 address), CNAME (point a name to another name), MX (where email is delivered), TXT (text used for email security and verification), NS (which servers hold the domain's DNS), SOA (administrative details for the zone), CAA (which certificate authorities may issue SSL certificates) and SRV (where specific services live). Changing A, MX, NS or TXT records carelessly is what usually breaks websites and email.
This reference explains each type in plain terms, with examples, and what to watch for when you change them.
The quick reference
| Type | What it does | Example value | Breaks if wrong |
|---|---|---|---|
| A | Points a name to an IPv4 address | 203.0.113.10 | Website |
| AAAA | Points a name to an IPv6 address | 2001:db8::10 | Website for IPv6 visitors |
| CNAME | Makes a name an alias of another name | shops.example-host.com | Subdomains, hosted services |
| MX | Says which servers accept email, with a priority | 10 mail.example.com | Incoming email |
| TXT | Holds text: SPF, DKIM, DMARC, verification codes | v=spf1 include:_spf.example.net ~all | Email delivery, service verification |
| NS | Lists the authoritative nameservers | ns1.dnsprovider.example | Everything |
| SOA | Zone administration: primary server, serial, timers | Set by your DNS provider | Rarely edited by hand |
| CAA | Restricts which authorities can issue certificates | 0 issue "letsencrypt.org" | SSL certificate renewals |
| SRV | Locates a service by protocol and port | 10 5 5061 sip.example.com | Specific apps such as calling or chat |
| PTR | Maps an IP address back to a name (reverse DNS) | mail.example.com | Email reputation for mail servers |
Every record also has a TTL, the number of seconds resolvers may cache it. That is covered in our guide to which TTL to use.
A and AAAA records: where your website lives
An A record says "this name is at this IPv4 address". Your root domain (often shown as @ in DNS editors) and www usually have one each, or www is a CNAME. AAAA records do the same for IPv6.
When you change web hosts, the A record is normally what you change. If you add an AAAA record, make sure it points to the same host; a stale AAAA record can send some visitors to an old server while others reach the new one.
CNAME records: aliases
A CNAME says "this name is the same as that name, go and look that one up instead". They are common for www, and for services such as hosted shops, help desks and email marketing tools that ask you to point a subdomain at them.
Two rules catch people out:
- A name with a CNAME cannot have any other records. You cannot have a CNAME and an MX record on the same name.
- The root domain cannot use a standard CNAME, because it must hold NS and SOA records. Many DNS providers offer an ALIAS, ANAME or "CNAME flattening" feature to achieve the same effect.
MX records: where email goes
MX records tell sending servers where to deliver mail for your domain. Each has a priority number: lower numbers are tried first, and higher numbers are backups. The value must be a host name, not an IP address, and that host name must have its own A or AAAA record.
If MX records are wrong or missing, incoming mail bounces or is lost. When you change email provider, you replace the MX records; when you change web host, you should not touch them unless your email is moving too.
TXT records: email security and verification
TXT records hold free-form text, but in practice they are used for a few specific things:
- SPF: one record starting
v=spf1that lists which servers may send mail for your domain. You must have only one SPF record per name; merge them if a new service asks you to add another. - DKIM: public keys, usually at a name like
selector._domainkey.yourdomain.com, that let receivers check your mail's signature. - DMARC: a record at
_dmarc.yourdomain.comstartingv=DMARC1that tells receivers what to do with mail failing SPF and DKIM. - Verification: codes that prove to a service (search consoles, email providers, certificate authorities) that you control the domain.
Deleting an old-looking TXT record can quietly break email delivery or a service login, so find out what a record is for before removing it.
NS and SOA records: who is in charge
NS records list the nameservers that hold your domain's DNS. There are two copies: the delegation held by the registry (set through your registrar) and the NS records inside your zone. They should match. The registry's copy is the one that matters for where the world looks.
Changing nameservers moves your whole DNS zone to another provider, so every record must exist there first. If a change is not taking effect, see nameserver change not working.
The SOA record holds the zone's primary nameserver, an administrative contact, a serial number and timing values. Your DNS provider normally manages it.
CAA, SRV and PTR records
CAA
CAA records list the certificate authorities allowed to issue SSL certificates for your domain. If you have one and later switch to a host that uses a different authority, renewals will fail until you add it. If you have none, any authority may issue.
SRV
SRV records point clients to a service, including its protocol, port, priority and weight. They are used by some calling, chat and directory services, usually with values the provider gives you.
PTR
PTR records are reverse DNS: they map an IP address to a name. They live in a zone controlled by whoever owns the IP address, usually your hosting or internet provider, not in your domain's DNS. They mainly matter if you run your own mail server.
Which records to keep a copy of
Before any change of host, DNS provider or registrar, keep a copy of at least these:
- Nameservers (from the registry).
- A and AAAA records for the root and
www. - All CNAME records for subdomains.
- MX records with priorities.
- All TXT records, especially SPF, DKIM and DMARC.
- Any CAA and SRV records.
Names Organizer, a domain manager for Windows, records nameservers and DNS records for every domain in your portfolio and can print or export them as a DNS and nameservers report, which is handy for audits or before moving hosts. Names Organizer can also warn you when nameservers or DNS records change unexpectedly. For a manual way to look records up, see checking DNS records on Windows.
Frequently asked questions
What is the difference between an A record and a CNAME?
An A record points a name directly to an IPv4 address. A CNAME points a name to another name, which is then looked up in turn.
Can I have a CNAME on my root domain?
Not as a standard CNAME, because the root must also hold NS and SOA records. Many DNS providers offer a flattening or ALIAS record to get the same effect.
Which DNS records control email?
MX records say where mail is delivered, and TXT records hold SPF, DKIM and DMARC, which help receiving servers trust your mail.
