DNS Records Explained for People Who Own a Small Website
Your host emails you a setup guide that says "point your A record here and add a CNAME there," and your registrar's control panel shows a table of cryptic rows you are scared to touch.

Your host emails you a setup guide that says "point your A record here and add a CNAME there," and your registrar's control panel shows a table of cryptic rows you are scared to touch. One wrong entry and your site or your email could vanish for a day.
This is DNS records explained in plain language for people who run a small site and just want things to work. I look after hosting for a handful of small businesses and help friends move sites most months, and the same six record types cover nearly every job you will ever need to do.
What DNS records actually do
DNS, the Domain Name System, is the internet's address book. When someone types your domain name, their device asks a DNS server where to go. Your DNS records are the answers you publish. Each record says, in effect, "for this name, here is this piece of information."
If you want the bigger picture of how a name connects to a server, our guide on what a domain name is and how it works covers registrars, registries and nameservers.
Every record has the same basic parts:
- Name or host. Which part of the domain it applies to. "@" means the bare domain itself, and "www" means the www version.
- Type. A, CNAME, MX and so on.
- Value. The IP address, hostname or text the record points to.
- TTL. Time to live, in seconds. It tells other servers how long to cache the answer before asking again.
The six DNS records you will actually use
| Record | What it does | Typical value |
|---|---|---|
| A | Points a name to an IPv4 address | 203.0.113.25 |
| AAAA | Points a name to an IPv6 address | A long address with colons |
| CNAME | Makes one name an alias of another name | A hostname your host gives you |
| MX | Says which servers receive your email | Mail server hostname with a priority number |
| TXT | Holds text, used for verification and email security | SPF, DKIM or a verification code |
| NS | Names the servers that hold all your other records | Two to four nameserver hostnames |
A and AAAA records
The A record is the one that makes your website load. Your host gives you an IP address, and you create an A record for "@" with that address. If your host supports IPv6, they will also give you an AAAA record. Add both.
CNAME records
A CNAME points a name at another name rather than an address. The classic use is making "www" an alias of your bare domain, or pointing it at a hostname from a platform such as a site builder or a CDN. One rule trips people up: a name with a CNAME cannot have any other records. That is why you usually cannot put a CNAME on "@".
MX records
MX records route your email. Each has a priority number, and lower numbers are tried first. A typical setup from an email provider has two to five MX records with priorities such as 1, 5 and 10. Our walkthrough on setting up a professional email address on your domain shows the full process.
TXT records
TXT records carry text that other services read. The three you will meet most are an SPF record, which lists who may send email for your domain, a DKIM record, which publishes a key that signs your messages, and DMARC, which tells receiving servers what to do with mail that fails those checks. Search consoles and other tools also ask you to add a TXT code to prove you own the domain.
NS records
NS records decide who is in charge. If your NS records point to your registrar, you edit DNS at the registrar. If they point to your host or a service like a CDN, you edit DNS there instead. Editing records in the wrong panel is the most common reason "nothing changed."
How to change DNS records safely
- Find the active panel. Look up which nameservers your domain uses, then log in to that provider.
- Screenshot everything first. Take a full screenshot or export of the current records. If something breaks, you can put it back in two minutes.
- Lower the TTL a day ahead. If you are moving a site, set the TTL on the records you will change to 300 seconds, about 5 minutes, at least 24 hours before the move.
- Change one thing at a time. Update the A record, test the site, then move on to email records.
- Test from outside. Use a public DNS lookup tool or your phone on mobile data, not your home connection, which may be caching old answers.
- Raise the TTL again. Once everything works, set it back to 3600 seconds or more.
If you are changing records as part of a hosting switch, our guide to switching web hosts with zero downtime walks through the full sequence.
Why "wait 48 hours for propagation" is mostly outdated
Almost every host still tells customers that DNS changes take 24 to 48 hours to spread around the world. I think that advice causes more confusion than it prevents.
DNS does not "propagate" like a wave. Other servers simply hold your old answer until its TTL runs out, then ask again. If your record had a TTL of 3600 seconds, most of the world sees the change within about an hour. If you lowered it to 300 seconds the day before, it is often a matter of minutes.
The 48-hour figure comes from changes to NS records at the registry level, where parent servers commonly cache for up to two days. That is a real wait, but it only applies when you switch nameservers, not when you edit an A or MX record. So if you change an A record and nothing has happened after two hours, do not just wait. Check that you edited the right panel and typed the value correctly.
Common DNS mistakes to avoid
- Two SPF records. You can only have one SPF TXT record. Merge the values into a single line.
- Typing the domain twice. Many panels add your domain automatically, so entering the full name in the host field creates a doubled name.
- Deleting MX records during a website move. Your website and email are separate. Leave mail records alone unless you are moving email too.
- Forgetting www. Set up both the bare domain and www, or visitors typing one version will see an error.
Frequently asked questions
What is the difference between an A record and a CNAME?
An A record points a name directly to an IP address. A CNAME points a name to another name, which then resolves to an address. Use an A record for your main domain and a CNAME for aliases such as www when your host recommends it.
How long do DNS record changes take to work?
Most changes are visible within the record's old TTL, often between 5 minutes and an hour. Changing nameservers can take up to 48 hours because of caching higher up the system. Lowering the TTL a day before a change speeds things up.
Can changing DNS records break my email?
Yes, if you delete or alter MX, SPF or DKIM records by mistake. Changing only the A record for your website will not affect email. Always save a copy of your current records before editing anything.
More in Hosting and Domains
Hosting and Domains
Inode and Entry Process Limits on Shared Hosting
A reader wrote to me last March after his host suspended his site at nine on a Friday evening.
Hosting and Domains
How to Set Up a Staging Site on Cheap Shared Hosting
A plugin update at nine in the evening is how most small sites go down.
Hosting and Domains
What Is Managed WordPress Hosting and Is It Worth Paying For
Your WordPress site is slow, an update broke something last month, and a hosting company is offering to "take care of...