DNS Records Explained for Non-Technical Owners
Imagine you have a friend's home address written on a slip of paper, but instead of a street and number it just says "the blue house near the big oak." That description works because someone, somewhere, can translate it into the exact place you need to go. The internet has a translator just like this, working silently behind every website, every email, and every app you use. It is called DNS, and the little instructions that power it are called DNS records.
Most business owners never look at their DNS records until something breaks: the website vanishes, email stops arriving, or a new tool refuses to connect. By then it feels intimidating, technical, and urgent all at once. This guide is here to change that. By the end you will understand what the main DNS records do, why they matter, and how to make changes without breaking anything. No jargon left unexplained, no assumptions about prior knowledge.
What DNS actually does
DNS stands for the Domain Name System. Think of it as the phone book of the internet. People remember names like yourcompany.com, but computers talk to each other using numbers called IP addresses, which look something like 192.0.2.45. When someone types your web address into a browser, DNS is the service that quietly looks up the matching number and connects them to the right server. It happens in a fraction of a second, millions of times a day, and you never see it.
Your domain name and your DNS are related but separate things. You register a domain through a registrar, and then a set of DNS records tells the world where that domain should point. If you want a deeper look at how registration and renewal fit together, our guide on domain renewal and DNS basics is a good companion piece. It also helps to understand the difference between a domain, hosting, and the website itself, which is covered well in this explainer on how those three pieces fit together.
Where your DNS records live
Your DNS records are stored in a place often called a DNS zone, managed through a control panel. That control panel might be at your domain registrar, your web host, or a dedicated DNS provider. The important thing to know is that only one set of these records is "in charge" at any time, decided by your nameservers. Nameservers are simply the addresses that tell the world which provider holds the authoritative version of your records. If your nameservers point somewhere, that is where you go to make changes. Editing records in the wrong place is one of the most common reasons changes seem to do nothing.
A quick word about patience
When you change a DNS record, the update does not reach the whole world instantly. Computers cache, or temporarily remember, the old answer for a set period called the TTL, short for Time To Live. A TTL might be a few minutes or a few hours. This is why a change you made this morning might still look broken on your phone this afternoon. It is almost never a mistake on your part, just the internet catching up. Lowering the TTL a day before a planned change can make updates take effect faster.
The DNS records you will actually meet
There are many record types, but in practice a small handful do almost all the work for a typical business. Let us walk through them in plain language, then summarise them in a table you can return to.
The A record: your front door
An A record connects your domain name to an IP address, the numeric location of your website's server. When someone visits your site, the A record is usually what points them to the right machine. The "AAAA" record does the same job for newer-style addresses called IPv6. If your site has moved hosts and is showing the old version, a stale A record is a prime suspect.
The CNAME record: a forwarding label
A CNAME, or canonical name record, points one name to another name rather than to a number. A common example is making www.yourcompany.com point to yourcompany.com, so both versions reach the same place. Many third-party tools, from email marketing platforms to booking systems, ask you to add a CNAME so a subdomain like shop.yourcompany.com resolves to their servers. It is essentially a friendly redirect that happens at the DNS level.
The MX record: where email goes
MX stands for mail exchange. These records decide which servers receive email sent to your domain. If you use a hosted email service for your business addresses, its MX records must be correct or messages will bounce or silently disappear. Email is one of the most fragile things to break with a careless DNS edit, so MX records deserve respect. Our deeper guide on email deliverability and SPF, DKIM and DMARC explains the related records that keep your messages out of spam folders.
The TXT record: notes for machines
TXT records hold plain text, but that text is usually meaningful to other systems rather than to humans. They are used to verify that you own a domain when setting up new services, and they hold email authentication settings like SPF and DKIM. You will add TXT records more often than you expect, because so many platforms use them to confirm ownership before they let you connect.
| Record | What it does | When you touch it |
|---|---|---|
| A / AAAA | Points your domain to a server's numeric address. | Moving hosts or launching a site. |
| CNAME | Points one name to another name. | Connecting subdomains and third-party tools. |
| MX | Routes incoming email to the right servers. | Setting up or changing business email. |
| TXT | Holds verification and email-security text. | Verifying ownership and protecting email. |
| NS | Names the servers in charge of your zone. | Switching DNS providers. |
Subdomains: rooms inside your house
If your domain is the house, subdomains are the rooms. blog.yourcompany.com, shop.yourcompany.com, and help.yourcompany.com are all subdomains. Each can point to a completely different service through its own record, which is why one part of your online presence can break while another stays perfectly fine. Understanding this saves a lot of panic, because a broken shop subdomain does not mean your main site is in trouble. It also means you can experiment with new tools on a subdomain without risking your main address.
How DNS connects to the rest of your website
DNS does not work alone. It is the first link in a chain that includes your hosting, your security certificate, and any performance services you use. For example, when you set up a content delivery network to speed up your site for global visitors, you often do it by changing DNS records so traffic flows through the network first. If that idea is new to you, our overview of what a CDN is and our practical CDN setup guide show exactly where DNS fits in.
Your secure padlock in the browser also depends on a healthy relationship with DNS, because certificate providers often verify domain ownership through DNS records before issuing or renewing a certificate. If you have ever wondered why a certificate renewal failed, an out-of-date DNS record is a frequent culprit. Our guides on what SSL certificates are and how to renew and manage them pair naturally with this topic.
Making changes safely
The single most useful habit is to write down what a record looks like before you change it. Take a screenshot or copy the existing values into a note. If something breaks, you can put it back exactly as it was. The second habit is to change one thing at a time and then wait, rather than editing several records at once and losing track of which change caused which result.
A simple pre-flight checklist
Before you touch anything, confirm you are editing records at the provider your nameservers actually point to. Confirm you understand what the current record does. Lower the TTL ahead of a planned change if you can. And keep a record of who else might be affected, especially for email, where a mistake can quietly stop messages from reaching you for hours. If your business depends on uninterrupted access, it is worth pairing DNS hygiene with uptime monitoring so you are alerted the moment something goes wrong rather than hearing it from a customer.
When to call for help
Some DNS changes are genuinely routine, like adding a TXT record to verify a new tool. Others, like migrating email or switching nameservers for a busy site, carry real risk if mistimed. There is no shame in asking a professional to handle the high-stakes changes while you confidently manage the everyday ones. If you would rather hand the whole area to someone who does it daily, you can always get in touch with a team that manages this for businesses. Knowing the basics, though, means you will never feel powerless when a record needs a quick look.
Frequently asked questions
Why did my DNS change not work immediately?+
What is the difference between an A record and a CNAME?+
Can a DNS mistake stop my email?+
Where do I actually edit my DNS records?+
References
- ICANN. "Beginner's Guide to Domain Names." icann.org.
- Internet Engineering Task Force. "Domain Names - Concepts and Facilities (RFC 1034)." ietf.org.
- Cloudflare. "What is DNS? Learning Center." cloudflare.com.