DNS is one of those topics that sounds far more technical than it is. People reach for it nervously, like there's a wrong wire to cut. But the whole system is built around one very ordinary idea — looking up an address — and once that clicks, the acronyms stop being scary and start being useful.
So here's DNS without the network-engineer vocabulary. What it is, the handful of record types you'll actually run into, and what "propagation" really means when someone tells you to wait for it.
What DNS actually is
DNS — the Domain Name System — is the address book of the internet. Or a phonebook, if you remember those: a way of looking up a friendly name and getting back the number you actually need to place the call.
Computers don't find each other by names like yoursite.com. They find each other by numeric addresses — IP addresses, strings of digits that no human wants to memorize. DNS is the lookup that sits between the two. You type a name; DNS quietly hands your browser the matching address; your browser connects. It happens in a fraction of a second, billions of times a day, and you never see it.
When you "set up DNS" for a domain, all you're really doing is writing entries in that address book — saying this name points to this thing. The entries are called records, and there are only a few you'll ever meet.
The records you'll actually use
You don't need all of these on day one, but it helps to recognize them when they appear in a settings screen.
| Record | Plain-English job |
|---|---|
| A | Points a name straight at an IP address — the web server itself |
| CNAME | Points a name at another name (an alias, "same as that one over there") |
| MX | Says where email for the domain should be delivered |
| TXT | Holds small notes — usually for verification or email security |
A record
An A record is the most direct one: it maps a name to an IP address. When yoursite.com resolves to a numeric address and your site appears, an A record did that. It's the "here is the actual building" entry.
CNAME
A CNAME points one name at another name instead of an address. Think of it as an alias — "www.yoursite.com is the same as yoursite.com, go ask about that one." It's handy because if the underlying address ever changes, the alias keeps working automatically; it was always just forwarding the question along.
MX
An MX record is purely about email. It tells the rest of the internet which mail server should receive messages for your domain. This is why web and email are independent: your A record can point your website one place while your MX record sends email somewhere else entirely. Move your site without touching MX, and your inboxes never notice.
TXT
A TXT record is a little notepad attached to your domain. Most of the time it holds verification strings — proving to a service that you own the domain — or email-security settings that help your messages avoid the spam folder. Small, plain text, quietly important.
Nameservers: who's holding the address book
There's one more piece. The records have to live somewhere, and the servers that hold them are called nameservers.
When someone looks up your domain, the very first question is "who keeps the records for this name?" The answer is your nameservers. They're the authoritative copy of your domain's address book — the source everyone else trusts. Point your domain at a set of nameservers and you've said "this is where my records are kept; ask here."
This is the cleanest way to manage a domain, because once the nameservers are set, every record lives in one place. When your domain is registered with CloudPerch, this is handled for you automatically — your records live on Cloudflare under the hood, and you never have to wire up a nameserver by hand. For the full breakdown of each record in your dashboard, see DNS records explained.
TTL and what propagation really means
Here's the part that confuses people most, so let's be plain about it.
Every record carries a TTL — "time to live," a number measured in seconds. The TTL is a hint to the rest of the internet: you can remember this answer for this long before checking again. Networks all over the world cache DNS answers so they don't have to ask from scratch every time, and the TTL tells them how stale they're allowed to let that memory get.
Propagation isn't your change traveling across the world. Your change is already done. Propagation is everyone else's cached copy of the old answer slowly expiring.
That's the whole reason a DNS change isn't instant. The moment you update a record, it's live at the source. But anyone whose network recently looked up your domain is holding the previous answer until its TTL runs out. As those cached copies expire — minutes for some, longer for others — everyone catches up to the new record. There's no switch that flips for the entire planet at once; there's just a tidy little wave of caches refreshing.
The practical upshot: changes usually take effect quickly, but give it a little time before you decide something's wrong. If you've just pointed a domain and a friend still sees the old site, they're almost certainly looking at a cached answer that hasn't aged out yet. You can read more about how that plays out during a move in our guide to connecting an existing domain.
You don't have to become an expert
The reassuring news is that for most people, the right amount of DNS knowledge is exactly this much: enough to read a settings screen without flinching. The actual plumbing — nameservers, records, TTLs settling — is the kind of boring, careful work that's better handled for you. When your domain lives with us, it is.
If you'd rather skip the address-book chores entirely, you can register a domain through us and let the records sort themselves out, or see the plans to find your perch. And when you're ready to point a name at your site, connect an existing domain walks you through it one record at a time.