Fast Web Builder Guide
What Is DNS and How Does It Work?
A friendly explanation of DNS as the internet’s address book, including records, nameservers, caching and safe website or email changes.
Key takeaways
- DNS records are separate directions for services such as websites, email and domain verification.
- Nameservers identify where the domain’s official set of DNS directions is kept.
- Cached answers can make a DNS change appear at different times for different people.
- Change only the records for the service you intend to move, especially when email must stay put.
DNS is the internet’s address book.
You type a friendly name like example.com. DNS helps your device figure out where that name is supposed to go.
You do not need to know how every page of the address book works to use it. You mainly need to know that DNS contains directions for different services—your website, your email, and other things connected to your domain.
Imagine calling somebody from your contacts
You probably don’t memorize everyone’s phone number anymore.
You tap:
Mom
Your phone quietly translates “Mom” into the correct number.
DNS does something similar.
You type:
example.com
The internet uses DNS to find the technical destination associated with that name.
Names for humans.
Technical destinations for computers.
Everybody gets what they want.
Why isn’t DNS just one giant list?
Because the internet is huge.
One enormous global spreadsheet would be… ambitious.
Instead, DNS is distributed across many systems.
When your device needs an answer, it may ask a DNS resolver. If that resolver doesn’t already know the answer, it can follow a chain of directions until it reaches the authoritative source for that domain.
Think of asking:
“Where does Jamie live?”
One person says:
“Ask the neighborhood office.”
The office says:
“That street is handled over there.”
Eventually you reach the place that has the actual address.
The computer version happens very quickly and with considerably less small talk.
What are DNS records?
DNS records are individual instructions.
Different records do different jobs.
You may see names like these:
A record
An A record can point a name toward an IPv4 address.
Think:
“For this website name, go to this address.”
AAAA record
Similar idea, but for IPv6 addresses.
The name has four A’s because apparently two would have been too easy.
CNAME
A CNAME says one hostname is an alias for another hostname.
Think:
“If someone asks for this name, follow the sign to that other name.”
MX
MX records handle incoming email routing.
Think:
“Mail for this domain goes to this post office.”
TXT
TXT records carry text used for many different purposes, including verification and email security.
Think of them as notes pinned to the domain’s information board.
NS
Nameserver records help identify where the authoritative DNS information lives.
This is more like:
“The official address book for this domain is kept over there.”
You don’t need to memorize these.
When you need one, we’ll tell you what it does.
What does “DNS propagation” mean?
You’ve probably heard somebody say:
“It can take time for DNS to propagate.”
That makes it sound like a wave slowly traveling across the planet.
The everyday explanation is easier.
DNS systems often cache answers.
Caching is like writing down a phone number so you don’t have to look it up again every single time.
Each cached answer has a timer called a TTL, or time to live.
When you change a DNS record, some systems may still have the old answer saved until their timer expires.
So one person may see the new website while another temporarily sees the old one.
Nobody is necessarily doing anything wrong.
Different address books are simply refreshing at different times.
Why DNS changes can accidentally break email
This is important.
Your website and email can both depend on DNS, but they use different instructions.
Imagine a building directory:
Suite 100: Website
Suite 200: Email
If you only want to move the website, change Suite 100.
Don’t throw away the whole directory.
When people move a website and accidentally replace every DNS record, they can delete the email directions too.
That is why a smart migration starts by taking a picture of the current “directory” before changing anything.
Nameservers vs DNS records
This sounds technical, but the distinction is straightforward.
DNS records are the individual directions.
Nameservers tell the internet where the official set of directions is kept.
Changing one DNS record is like updating one person’s phone number in a contact list.
Changing nameservers is closer to saying:
“We moved the entire contact list to a new office.”
If you do that, make sure the new office has all the entries—not just the website.
The part worth remembering
DNS is an address book.
It connects your easy-to-remember domain to the services behind it.
Website goes here.
Email goes there.
Other services get their own directions.
You do not need to memorize DNS record types to make good decisions.
You just need to know what you’re trying to move before you change the directions.
That’s already enough to avoid a surprising number of internet headaches.
Keep the domain directions under control.
Domain Manager gives you a domain-only place to manage names and their DNS without buying website hosting first.
Explore Domain Manager →