Domain Basics
What Is DNS? A Plain-English Breakdown of How Domains Resolve
DNS runs quietly behind every website visit and email you send — understanding the basics turns confusing zone files into something you can actually read.
4
Common record types: A, CNAME, MX, TXT
ms
Typical lookup time once a record is cached
24-48h
Worldwide propagation window after a change
24/7
Support for reading a confusing DNS zone
In short
DNS (Domain Name System) is the internet's directory service — it translates human-readable domain names like yoursite.com into the numeric IP addresses servers actually use to find each other. When you type a domain into a browser, your device asks a DNS resolver, which checks a chain of servers until it finds the right IP address, all within a fraction of a second.
Different record types inside that system handle different jobs: A records point to an IP, CNAME records alias one hostname to another, and MX records route email.
DNS is often described as the internet's phone book, and that's a fair starting point: it's the system that lets you type a name instead of a string of numbers. What the analogy misses is that it's not one book but a hierarchy of servers — root servers, then servers for each top-level domain like .com, then the specific authoritative nameservers for your domain — each handing the query one step closer to the right answer.
Hosting Cheap sets up sensible A and MX record defaults the moment an account is created, so most people never need to touch a DNS zone at all. But when you do — adding a subdomain, connecting a third-party mail filter, or verifying a domain with an external service — the cPanel-style panel lays every record's type, name, value and TTL out in plain columns rather than burying them in jargon.
How a DNS Lookup Actually Happens
Type a domain into a browser and the first stop is your own device's cache, then your operating system's, then a resolver — usually run by your ISP or a public one you've configured. If none of those already have the answer cached, the resolver asks a root server, which doesn't know the answer either but points it to the server responsible for the domain's extension, such as .com.
That TLD server points the resolver to the domain's actual authoritative nameservers — the ones set at your registrar — which finally return the real record. The resolver caches that answer for next time and hands it back to your browser, all of which typically happens in milliseconds once anything along the chain is warm.
The Record Types You'll Actually Use
An A record points a hostname to an IPv4 address and is the record that makes a website load at all. A CNAME record aliases one hostname to another instead of an address directly — commonly used to point "www" at the root domain — but a name with a CNAME can't have other records sitting alongside it.
An MX record tells the internet which server should handle incoming email for the domain, complete with a priority value if more than one mail server is listed. A TXT record just holds arbitrary text, most often used for SPF and DKIM values that help receiving servers verify your mail isn't being spoofed, plus one-off verification codes services sometimes require.
TTL: Why Some Changes Take a Day to Show Up
Every DNS record carries a TTL (time to live), measured in seconds, that tells resolvers how long they're allowed to cache it before checking the source again. A record with an hour-long TTL will show a change within an hour almost everywhere; one left at a day-long default can take noticeably longer.
Because every resolver worldwide caches independently on its own schedule, it's completely normal for a change to appear for one visitor immediately and take up to 24-48 hours to reach everyone else. Lowering the TTL a day or two ahead of a planned change is the one practical way to speed that window up in advance.
Where DNS Fits Into Your Hosting Setup
Nameservers are the setting that decides which DNS zone is authoritative for a domain — point them at your host and its zone, full of A, MX, TXT and CNAME records, becomes the one that actually answers for the site and its email. Everything else, from adding a subdomain to setting up email routing, happens inside that zone.
A cPanel-style panel puts editing that zone directly in your hands rather than requiring a support ticket for every small change, which matters most the first time you need to add a TXT record for a third-party service or a CNAME for a marketing tool.
Reading Your Own DNS Zone With Confidence
Once you know the four core record types, a DNS zone stops looking cryptic — decode any entry by asking what type it is first, then what it's pointing at or delivering.
Hosting Cheap's control panel lists records in plain columns rather than raw zone-file syntax, so adding an MX record for a third-party email filter or a TXT record for domain verification doesn't require opening a support ticket to attempt.
- A records point a hostname to an IPv4 address
- CNAME records alias one hostname to another
- MX records tell the internet where to deliver email
- TXT records hold verification and anti-spoofing text like SPF and DKIM
Why Hosting Cheap
What you get
Full DNS zone control
Add or edit A, CNAME, MX and TXT records yourself from the control panel.
Sensible defaults out of the box
New accounts get working A and MX records automatically, not a blank zone to configure.
Free SSL tied to your records
Once your A record resolves here, a certificate issues automatically.
24/7 human support
Get a real answer when a record you added doesn't behave as expected.
Free migration
Existing DNS records get recreated on your new zone as part of the move.
cPanel-style zone editor
See every record's type, name, value and TTL laid out clearly, not buried in jargon.
How It Works
Get set up in a few steps
Identify the record type you need
Decide whether you're pointing a hostname (A/CNAME), routing mail (MX), or adding verification text (TXT).
Add or edit it in your DNS zone
Use the control panel's zone editor to enter the exact value your provider requires.
Give it time to propagate
Allow up to 24-48 hours for resolvers everywhere to pick up the change.
Included
Everything you need, on every plan
- Know the four core record types: A, CNAME, MX and TXT
- Check a record's TTL before expecting an instant change
- Never point a CNAME at a name that also has other records
- Set MX priority correctly if using more than one mail server
- Add TXT records for SPF and DKIM if sending mail from your domain
- Use a DNS lookup tool to confirm a record before assuming it's broken
- Lower TTL a day ahead of a planned migration to speed propagation
- Remember nameservers decide which DNS zone is authoritative
FAQ
Frequently asked questions
What is DNS in simple terms?
DNS is the system that translates the domain name you type into a browser into the numeric IP address a server actually uses to find your site. Without it, you'd have to remember a string of numbers instead of a name for every website you visit.
What's the difference between an A record and a CNAME?
An A record points a hostname directly to an IPv4 address, while a CNAME points a hostname to another hostname instead of an address. CNAMEs are useful for aliasing, like pointing "www" at your root domain, but a name with a CNAME can't have other records alongside it.
Why do DNS changes take time to show up everywhere?
Every DNS record has a TTL telling resolvers how long to cache it before checking again, and resolvers around the world cache independently. That's why a change can appear instantly on one network and take up to a day or two to show everywhere else.
What does an MX record do?
An MX record tells the internet which server should receive email for your domain, and its priority value decides the order servers are tried if more than one is listed. Get it wrong and mail either bounces or goes to the wrong inbox entirely.
What is a TXT record used for?
TXT records hold arbitrary text tied to a domain, most commonly SPF and DKIM values that help receiving mail servers verify your email isn't spoofed, plus verification codes for other services. They don't route traffic themselves, they just carry information other systems check.
Do I need to understand DNS to run a website?
Not in depth — most hosting accounts work with sensible default records out of the box. But knowing the basics helps a lot when troubleshooting email delivery, adding a subdomain, or pointing a domain to hosting for the first time.
Get a DNS Zone That Just Works
Sensible A, MX and SSL defaults from the moment you sign up, with plans from $2.09/mo.
Get Started