DNS is one of those “set it once, then forget it” parts of running a business website—until email stops arriving or your site doesn’t load. The good news: once you understand what A, CNAME, MX, and TXT records do in plain terms, you can make smarter changes, spot mistakes faster, and know when to ask for help.
When you’re looking at DNS settings, you usually have questions like:
“The trouble with the world is not that people know too little, but that they know so much that isn’t so.”
You can read this guide if you want clear answers to: what DNS records actually “do,” which ones affect website routing versus email delivery, and how to verify your setup in a control panel without guessing.
DNS record types are a shared convention that lets the internet route traffic to the right place. For email delivery specifically, the SMTP routing approach relies on DNS lookups (not “magic”). Understanding those basics makes it much easier to troubleshoot when something isn’t working.
By the end, you’ll know what A vs. CNAME means for websites, how MX records connect domains to mail servers, why TXT records matter for verification and email authentication, and what common errors to watch for.
What DNS does in simple terms
Think of DNS as a phone book for the internet. Humans remember domain names like resortwebmarketing.com; computers need answers like “where should I send requests for this domain?”
Most businesses don’t need to understand the full technical machinery. You mainly need two outcomes:
- Website routing: your domain resolves to the right web server (so visitors see your site).
- Email delivery: your domain tells the internet where to send messages (so your inbox receives mail).
Note: DNS also supports domain verification and security signals via TXT records and related mechanisms—details below.
A and CNAME records for websites
A record: maps a name to an IP address
An A record points a hostname (like www) to an IPv4 address. If your website is hosted at a specific server address, an A record helps visitors reach it.
| What you enter | Common example | Business outcome |
|---|---|---|
| Host | www | Routing for www.yourdomain.com |
| Value | 203.0.113.10 | Browser traffic reaches the correct web server |
| TTL | Default (often fine) | How quickly changes propagate |
Typical use: When your provider gives you a web server IPv4 address and you need your domain to land there.
CNAME: points an alias to another name
A CNAME record maps one hostname to another hostname (not directly to an IP address). You might use it when your website target is managed elsewhere and you’re instructed to “set a CNAME to X.”
Typical example: you want www to behave like another hostname (such as one provided for hosting, an application endpoint, or a CDN-like setup). Instead of maintaining IPs yourself, you point the alias.
Decision criteria:
- If your control panel says “set this to an IP address,” use an A record.
- If it says “set this to a hostname,” use a CNAME.
- If instructions mention propagation, expect changes to take time to appear everywhere.
If you’re managing multiple sites or relocating services, keep a simple change log (what you changed, when, and why). It turns DNS from a mystery into an audit trail.
MX records for email routing
MX: tells the internet where your mail should go
MX records (Mail Exchange) are the core DNS records for inbound email. They tell receiving mail servers which mail server(s) to contact when someone sends to your domain.
| What you enter | Common example | Business outcome |
|---|---|---|
| Priority | 10, 20 | Which server to try first |
| Mail server host | mail.yourdomain.com | Delivery destination for inbound messages |
What can go wrong: missing MX records, wrong mail server hostname, or outdated records after you move email hosting. The result is usually not subtle—messages bounce or land in the wrong place.
If you want a practical walkthrough of what you should set up for mailboxes and access, see Email Hosting and Control Panel.
TXT records for verification and email authentication
TXT: “text” signals for tools, security, and verification
TXT records store text-based data in DNS. For businesses, TXT records show up in two major places:
- Verification: proving you control a domain for services like website ownership checks or ownership confirmation in platforms.
- Email authentication: helping receivers verify that mail really comes from your domain (which improves deliverability and reduces spoofing risk).
Different systems use different TXT formats. You may see instructions to add TXT records for SPF, DKIM, or other authentication methods. These are designed to prevent forged messages and to improve the odds that legitimate mail reaches the inbox.
For general guidance on common DNS records and their relationships, the DNS record overview is a helpful reference. You can also compare the record types you’re seeing in your control panel to what they mean.
Important: TXT records aren’t “one-size-fits-all.” Copying random TXT values from the internet is a common way to accidentally break domain verification or email authentication.
How to spot mistakes (and when to ask support)
DNS problems tend to follow patterns. Here’s a simple checklist that helps non-technical owners identify the most common issues without falling into theory spirals.
Quick checks for website issues
- Your site won’t load: verify whether your records point to the right hostname/IP given by your hosting setup.
- Only “www” is broken (or only the root domain is broken): check that the record exists for the correct host (root vs www).
- Everything changed but nothing updates immediately: allow time for propagation based on TTL.
Quick checks for email issues
- No inbound email: confirm MX records are present and point to the correct mail server hostnames.
- Bounces or “recipient not found”: MX records may be wrong or outdated after a move.
- Delivery to spam: DNS authentication (TXT-based mechanisms) may be missing or mismatched.
- Some people get mail, others don’t: can happen when authentication is partially correct—verify your TXT values match your email service’s instructions.
When to ask for support
Ask support when you’ve identified a likely record mismatch but aren’t confident about the exact values. Provide:
- The domain name and which DNS host/record you changed
- The date/time of the change (and whether you changed multiple records)
- Any error message from your email system or a screenshot from your control panel record editor
- What you were trying to accomplish (new website, moved email hosting, verification request, etc.)
For the broader control-side capabilities that often help with troubleshooting, review Domains & DNS, then contact support if you need a second set of eyes.
Practical “record type to outcome” map
| Record type | Where you’ll see it | Business outcome | Most common mistake |
|---|---|---|---|
| A | Website routing | Domain points to the right server IP | Using an IP meant for a different service |
| CNAME | Hostname aliasing | One name redirects to another name | Pointing to the wrong target hostname |
| MX | Email routing | Inbound mail finds your mail server | Missing/old MX records after a move |
| TXT | Verification + authentication | Proves domain control; improves email legitimacy | Copying the wrong TXT values |
Conclusion: make DNS changes like a decision, not a gamble
DNS is just record-based routing and verification. When you match each record type to its real business outcome—website access for A/CNAME, inbox delivery for MX, and verification/authentication for TXT—DNS becomes manageable.
If you’d like help planning your setup, start with Domains & DNS and Email Hosting. When you’re ready, Contact Support and request a hosting plan review so your records are correct the first time.