DNS records connect your domain to a website, email provider, verification service, and security controls. This practical reference explains what A, AAAA, CNAME, MX, TXT, NS, and CAA records do, shows which records most sites need, and gives you a repeatable process for making and checking DNS changes safely.
Overview
When someone visits your domain or sends email to it, DNS helps their device find the correct service. Your domain registrar may provide DNS management, or your nameservers may point to a separate DNS provider. The important distinction is that the company where you bought the domain is not always the company hosting your DNS zone or website.
A typical website and email setup might include an A record for the website, an MX record for incoming email, several TXT records for verification and email authentication, and possibly a CAA record to control which certificate authorities may issue SSL/TLS certificates. A modern site may also use an AAAA record for IPv6 and CNAME records for subdomains or hosted services.
Before editing anything, identify where the authoritative nameservers are managed. You can usually find them in the domain registrar account or by using a DNS lookup tool. Changes made in the wrong dashboard will not affect the live domain.
A quick record reference
| Record | Primary purpose | Common example |
|---|---|---|
| A | Maps a hostname to an IPv4 address | example.com → 203.0.113.10 |
| AAAA | Maps a hostname to an IPv6 address | example.com → an IPv6 address |
| CNAME | Aliases one hostname to another hostname | www.example.com → sites.provider.example |
| MX | Specifies servers that receive email | example.com → mail provider hostnames |
| TXT | Stores text for verification and email policies | SPF, DKIM, DMARC, or ownership tokens |
| NS | Delegates DNS authority to nameservers | example.com → ns1.dns-provider.example |
| CAA | Indicates which certificate authorities may issue certificates | example.com → an approved certificate authority |
The IP addresses and provider hostnames above are illustrative. Always use the exact values supplied by your hosting, email, or verification provider.
What to track
Website records
Use an A record when your hosting provider gives you an IPv4 address. If the provider gives you an IPv6 address, use an AAAA record as well. A domain can have more than one address, but do not add extra values unless your provider specifically instructs you to do so.
Use a CNAME when a service gives you a destination hostname rather than an IP address. This is common for a www subdomain, landing page, documentation site, or other hosted service. Whether a CNAME can be used at the root domain depends on the DNS provider and its supported flattening or alias features. Follow the provider’s setup instructions rather than assuming the record type.
Keep a clear distinction between the root domain, often shown as @, and a subdomain such as www, blog, or shop. A website can work at one hostname while the other remains misconfigured.
Email records
MX records control incoming email. Each MX record has a mail server hostname and a priority value. Lower numerical priority generally indicates preference when multiple servers are listed, but the exact behavior and failover design should come from the email provider. Remove old MX records only after confirming that no active mailbox or forwarding service still depends on them.
TXT records support email authentication and service verification. An SPF policy identifies services authorized to send mail for your domain. DKIM normally uses a TXT record at a selector-based subdomain supplied by the email provider. DMARC is also published as TXT, usually at _dmarc, and describes how receiving systems should handle messages that fail authentication checks.
Do not create multiple independent SPF records for the same hostname. If more than one service sends email, their authorized sources generally need to be combined into one policy according to the providers’ instructions. DKIM selectors and DMARC settings vary, so copy the exact values and review them before publishing.
Delegation, verification, and certificate controls
NS records identify the authoritative nameservers for a domain. They are normally changed at the registrar or parent DNS service, not casually edited inside the zone. Changing nameservers can replace the entire DNS configuration, so export or document existing records first.
TXT records are also used to verify domain ownership for search tools, newsletters, analytics platforms, and other services. A verification record is usually safe to add, but deleting one may disconnect a service later. CAA records can add a layer of certificate-issuance control, but an incorrect CAA policy may prevent a legitimate certificate from being issued or renewed. Add CAA only when you understand which certificate authorities your site uses.
Provider-verification checklist
- Confirm the exact hostname, record type, value, and TTL provided by the service.
- Check whether the dashboard expects
@, a blank field, or the full domain name. - Remove quotation marks or trailing punctuation unless the provider explicitly includes them.
- Check for an existing conflicting record at the same hostname.
- Complete the provider’s verification step after the record is published.
- Record why the entry exists, who requested it, and when it should be reviewed.
Cadence and checkpoints
DNS is not a set-and-forget system when a domain supports a working website, email, and third-party services. A lightweight review each quarter is appropriate for many small sites. Review sooner after a hosting migration, domain transfer, email-provider change, security incident, or unexplained delivery problem.
Before a change
- Export the current zone if your provider supports it, or capture a written record list.
- Identify the authoritative nameservers and confirm you are editing the correct zone.
- Lower the TTL in advance only when you expect a planned migration and your provider recommends it. A lower TTL can help caches refresh sooner, but it does not eliminate all delay.
- Write down the intended result, such as moving the website while keeping email unchanged.
After a change
Check the record from more than one DNS lookup location when possible. Test the exact hostnames people use, including both the root domain and www. For email, send a test message in both directions and confirm that existing mailboxes, forwarding, and aliases still work. For a website, test HTTPS, redirects, forms, images, and any important subdomains.
Propagation is not a single global event. Resolver caches refresh according to TTL, providers may apply their own processing time, and some systems can continue using older answers temporarily. Treat the published TTL as a planning guide, not a guaranteed completion time.
Change-log template
Date and time:
Domain or hostname:
Record type:
Previous value:
New value:
Reason for change:
Requested by:
Expected impact:
Validation performed:
Rollback value:
Next review date:
How to interpret changes
When a website stops resolving after a DNS edit, start with the hostname and record type rather than changing several entries at once. Confirm that the authoritative zone contains the intended value, then check whether a conflicting A, AAAA, or CNAME record remains. If the record is correct, allow for caching before concluding that the change failed.
Simple troubleshooting flow
Website unavailable? → Confirm nameservers → Check the root and www records → Compare the value with the hosting provider’s instructions → Check for conflicting records → Test HTTPS and redirects.
Email not arriving? → Confirm MX records → Check that old and new mail systems are not unintentionally mixed → Review mailbox and routing settings with the email provider → Check SPF, DKIM, and DMARC results → Send controlled test messages.
Verification still pending? → Confirm the exact hostname and TXT value → Check for copied spaces or truncated text → Verify that the record is publicly visible → Use the service’s retry or recheck control.
A DNS lookup that shows the new value does not prove that the application is configured correctly. DNS only directs traffic. Hosting settings, SSL certificates, web-server rules, mailbox settings, and application configuration must also agree with the DNS records.
When to revisit
Revisit this DNS reference at least quarterly, and immediately after any event that changes how your domain is hosted or used. The most important triggers are a domain transfer, nameserver change, website migration, email-provider change, new marketing or transactional email tool, new subdomain, certificate change, or security incident.
At each review, compare the live zone with your change log. Remove records for services you no longer use, confirm that email authentication still reflects current senders, and check that certificate controls match your actual certificate workflow. Avoid deleting unfamiliar entries without identifying them first; a record may support a quiet but important service.
For a practical final check, maintain a small DNS inventory containing the hostname, type, purpose, provider, current value, TTL, owner, and review date. Back it up with your website and domain records. If you are preparing to move a domain, use a dedicated domain transfer checklist so DNS and email are reviewed before the transfer begins. For broader continuity planning, pair this process with a website backup and recovery plan.
DNS management is safest when every change has a purpose, a rollback value, and a verification step. Keep the record set documented, make one controlled change at a time, and schedule the next review before you close the dashboard.