Article in English.
DNS records connect a domain to services such as website hosting, email and verification. A safe change starts with identifying the record's purpose and the provider's instructions.
Prepare a record-by-record change plan
Export the existing records, mark which service depends on each one and record the intended new value. Preserve mail-related records when changing only web hosting. After the change, test both website access and email delivery. Use the hosting guide to plan account ownership and support.
Key takeaways:
- DNS translates human-readable domain names into the addresses computers actually use to connect
- A records point your domain to a website's server address
- CNAME records point a subdomain to another domain name
- MX records control where email for your domain gets delivered
- Getting these wrong can take down your website or email — changes should be made carefully
What DNS Actually Does
Every website lives on a server with a numeric address (an IP address). DNS (Domain Name System) is essentially the internet's phone book — it translates a domain name like "yourbusiness.com" into the numeric address browsers and email systems actually need to connect to the right destination.
The Core DNS Record Types
| Record Type | What It Does | Common Use Case |
|---|---|---|
| A Record | Points a domain to an IPv4 address | Connecting your domain to your website's hosting server |
| AAAA Record | Points a domain to an IPv6 address | Same purpose as an A record, using the newer IP address format |
| CNAME Record | Points a subdomain to another domain name instead of an IP address | Connecting "www" to your main domain, or linking third-party tools |
| MX Record | Specifies which mail servers handle email for your domain | Directing email to Google Workspace, Outlook, or another provider |
| TXT Record | Stores text-based verification and configuration data | Domain verification, SPF/DKIM email authentication |
| NS Record | Specifies which nameservers manage your domain's DNS | Set when moving DNS management to a new provider like Cloudflare |
A Records: Connecting Your Domain to Your Website
An A record is the most fundamental DNS record — it points your domain directly to the numeric IP address of your hosting server. When you set up a new website, one of the first steps is usually pointing your domain's A record to your host's provided IP address.
CNAME Records: Pointing to Another Domain
Rather than pointing to a numeric address, a CNAME record points to another domain name. This is commonly used to connect "www.yourbusiness.com" to "yourbusiness.com," or to point a subdomain toward a third-party service, like a landing page builder or help desk tool.
MX Records: Making Sure Email Actually Arrives
MX records tell the internet where to deliver email sent to your domain. If you use Google Workspace, Microsoft 365, or another email provider, your domain's MX records need to point to that provider's mail servers — incorrect MX records are one of the most common causes of "my business email isn't receiving anything" issues.
TXT Records: Verification and Email Security
TXT records often go unnoticed until they're needed — for verifying domain ownership with a new tool, or setting up SPF and DKIM records that help prevent your business emails from being marked as spam.
Common Mistakes to Avoid
- Deleting records without understanding their purpose: Removing an MX or TXT record without checking what it controls can silently break email delivery or domain verification.
- Changing A records during a migration without a plan: Switching hosting requires careful A record updates — doing this without preparation can cause downtime.
- Ignoring TTL (Time to Live) settings: A high TTL value means changes take longer to propagate, which is worth lowering temporarily before a planned migration.
Frequently Asked Questions
How long do DNS changes take to take effect?
It depends on the record's TTL setting, but most changes propagate within a few minutes to a few hours, with full global propagation sometimes taking up to 24-48 hours.
Can I manage DNS myself, or do I need a developer?
Basic changes, like updating an A record when switching hosts, are usually manageable directly through your domain registrar or DNS provider's dashboard, though more complex setups (like email authentication) benefit from technical guidance.
What happens if I get a DNS record wrong?
Depending on the record, this can cause anything from your website becoming unreachable to email delivery failing — which is why it's worth double-checking values before saving changes, especially for A and MX records.
Next Steps for Your Business
Understanding your DNS setup, even at a basic level, makes future changes — like switching hosts or setting up new tools — far less stressful.
Our team can review or reconfigure your DNS settings, making sure your website and email are set up correctly and reliably.