DNS records explained in plain English
What DNS records do in plain English: A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, SRV and PTR records, the email security trio, and tips that prevent common DNS problems.
DNS records are the instructions that tell the internet where your domain's website, email and services live. You'll edit them in your registrar or a DNS service like Cloudflare. Here's what each common record does, in plain English.
How DNS works in one paragraph
When someone types your domain, their device asks a resolver where it lives. The resolver asks the root servers, then the servers for your ending (like .com), then your domain's own nameservers, which answer with your records. Answers are cached for a while, set by each record's TTL (time to live), which is why changes can take minutes to hours to show everywhere.
The common record types
| Record | What it does | Example use |
|---|---|---|
| A | Points a name to an IPv4 address | yourbusiness.com → your web server |
| AAAA | Points a name to an IPv6 address | The same, for newer IPv6 networks |
| CNAME | Makes one name an alias of another | www → yourbusiness.com, or shop → your store platform |
| MX | Says which servers receive your email | Google Workspace or Microsoft 365 mail |
| TXT | Holds text for verification and email security | SPF, DKIM, DMARC, Google Search Console verification |
| NS | Says which nameservers are in charge of the domain | Pointing your domain to Cloudflare |
| SOA | Basic administrative info about the zone | Created automatically by your DNS host |
| CAA | Limits which certificate authorities can issue SSL certificates | Allowing only Let's Encrypt |
| SRV | Points specific services to a server and port | Some calling, chat or game services |
| PTR | Reverse lookup: IP address to name | Set by mail server hosts for deliverability |
The email security trio
- SPF (a TXT record) lists which services may send email for your domain.
- DKIM (a TXT or CNAME record) adds a digital signature to your emails.
- DMARC (a TXT record at _dmarc) tells inboxes what to do with mail that fails SPF or DKIM.
See how to get a professional email address for the full setup.
Tips that prevent most problems
- Screenshot your records before making changes.
- Only one SPF record per domain. Combine senders into one.
- A CNAME can't sit on the root domain alongside other records at most hosts. Some DNS providers, like Cloudflare, handle this with "CNAME flattening".
- Mail records should be DNS only, not proxied, on Cloudflare.
- Lower the TTL a day before a big move so changes spread faster.
Want to see a domain's records? Our WHOIS lookup shows a domain's nameservers.
Questions
How long do DNS changes take?
Often minutes, but up to 24 to 48 hours depending on TTL settings and caching.
What's the difference between an A record and a CNAME?
An A record points to an IP address. A CNAME points to another domain name.