what is DNS in simple words? the internet phone book, and why changes take a day
web · Oct 7, 2026 · 5 min read
dns is the internet's phone book. you type mybusiness.com, your browser asks the phone book "what number is that?", the phone book answers "it lives at 93.184.216.34", and only then does your browser go knock on that door. that is the whole job: translate names people remember into numbers machines need.
nobody looks up numbers anymore, but servers still do — and the translation layer between the two is dns, the domain name system.
the records, in plain words
the phone book is not one line per name, it is a small card per name with different kinds of entries — the "records". four of them cover everything a small business ever needs:
| record | what it answers | example use |
|---|---|---|
| A | "at which address does the site live?" | points mybusiness.com at your host's server |
| CNAME | "which other name is this one an alias of?" | points www.mybusiness.com at mybusiness.com |
| MX | "who delivers the email for this name?" | tells the world your mail is handled by google or your host |
| TXT | "a note for machines that check" | spam protection and verification entries, more below |
that is it. every "connect your domain" instruction from every host or email provider is ultimately asking you to add or edit one of these four lines on the card.
propagation is not what you think
here is the part that makes people lose a day: when you change a record, the change does not travel around the world slowly. the old answer was cached. every internet provider keeps the phone book's answers for a while — minutes to hours — so they do not have to ask again for every visitor. the "24-48 hours" you read everywhere is the worst case leftover from ancient settings; most changes today are visible in under an hour for most people, while a few unlucky visitors with long-cached answers see the old site for the rest of the day.
so when a change "is not working", the honest sequence is: check the record was actually saved, then wait out the cache, then check again in a private window, which skips your own cached answers. that is also why a site "works on your phone but not your laptop" or vice versa right after a change — the two devices cached different answers.
why you should care even if you never touch it
because dns is also where some of the scariest-sounding outages and some of the simplest wins live. a site that is "down for everyone" is often just a dns mistake made in one panel. and the email deliverability story in why do my business emails go to spam is almost entirely a dns story: the records that prove your mail is legitimate are typed into the same phone book.
if you are on a builder, the platform set its records when you signed up and you will never meet dns. if you have your own domain and your own hosting — the setup what is hosting argues for — the day you change hosts or add professional email, you will edit four lines in a panel and then wait out a cache. now you know why, and knowing why is the difference between "the internet is broken" and "the cache needs an hour".
FAQ: the questions i actually get
how long do dns changes really take?
most under an hour, the worst cases a day or two. the range is caching, not bureaucracy — the ttl setting on the record decides how long old answers are trusted.
what is an A record vs a CNAME?
A points a name at a number (the server's address). CNAME points a name at another name. www is almost always a CNAME pointing at the bare domain.
do i need to touch dns to connect my domain to a website?
yes, once — the host gives you one or two values and you add them as records. after that, dns becomes invisible until you move something.