DNS records connect your domain to a website, email service, verification tool, or other internet service. This practical checklist explains what each common record does, which records different setups usually need, and how to make and verify changes without losing access to your site or business email.
Overview
The Domain Name System (DNS) translates human-readable names such as example.com into the destinations used by browsers, mail servers, and online services. Your domain registrar, hosting provider, and DNS provider may be the same company, but they do not have to be. Before editing anything, identify where the domain’s authoritative nameservers are managed. Changes made in the wrong dashboard will not affect the live domain.
DNS records have four important parts: the name or host, the record type, the value or destination, and the TTL (time to live). A record’s name may appear as @ for the root domain, www for a subdomain, or a service-specific label such as mail or _acme-challenge. Interfaces vary, so follow the provider’s instructions for whether to enter the full domain name or only the host label.
DNS records explained
| Record | Plain-language purpose | Typical use | Important detail |
|---|---|---|---|
| A | Points a hostname to an IPv4 address. | Connecting a domain to a web server. | Enter an IPv4 address, not a URL or hostname. |
| AAAA | Points a hostname to an IPv6 address. | Supporting an IPv6-enabled website or service. | Enter an IPv6 address. Do not use an IPv4 address here. |
| CNAME | Aliases one hostname to another hostname. | Connecting www, a subdomain, or a hosted service. | It points to a hostname, not an IP address, and is usually not used at the root domain unless the DNS provider supports an equivalent feature. |
| MX | Identifies the servers that receive email for a domain. | Business email setup. | Priority matters: lower numbers generally indicate higher priority. |
| TXT | Stores text used for instructions, verification, or email policy. | SPF, DKIM, DMARC, and third-party domain verification. | Copy the value exactly, including punctuation and quotation handling required by the provider. |
| NS | Identifies the nameservers authoritative for a domain or subdomain. | Delegating DNS management to a provider. | Changing nameservers can replace the active DNS zone, so record migration must be planned first. |
| CAA | States which certificate authorities may issue TLS certificates for a domain. | Adding an extra control to certificate issuance. | Use only when you understand which certificate authorities your site and automation require. |
DNS is not the same as a web redirect. An A or CNAME record helps a hostname resolve to a service; it does not normally redirect visitors from one URL to another. For a permanent redirect, configure the web server, hosting platform, or redirect service. This distinction matters when moving from an old domain, consolidating HTTP and HTTPS URLs, or forwarding one domain to another.
Checklist by scenario
1. Connecting a website
Obtain the exact DNS instructions from the hosting provider before editing the zone. A common website setup looks like this:
| Name | Type | Example value | Purpose |
|---|---|---|---|
@ | A | 203.0.113.10 | Connects the root domain to an IPv4 server address. |
www | CNAME | example.com | Makes the www version follow the main hostname. |
The IP address above is an example placeholder, not a destination to use. Your host may instead require several A records, an AAAA record, a CNAME to a platform hostname, or a provider-specific root-domain record. Do not guess. Copy the values supplied by the hosting platform and remove conflicting records only when the provider’s instructions call for it.
2. Setting up business email
Email providers normally supply multiple MX records, often with different priorities. A simplified example is:
| Name | Type | Example value | Purpose |
|---|---|---|---|
@ | MX | mx1.mail-provider.example | Primary inbound mail server. |
@ | MX | mx2.mail-provider.example | Additional inbound mail server, subject to provider instructions. |
@ | TXT | v=spf1 include:provider.example ~all | Helps identify authorized senders when supplied by the email provider. |
selector1._domainkey | TXT or CNAME | provider-specific-value | Publishes DKIM information, using the provider’s specified record type. |
_dmarc | TXT | v=DMARC1; p=none; rua=mailto:[email protected] | Publishes a DMARC policy; use a carefully reviewed value. |
These are illustrative formats, not universal values. Email providers change hostnames, selectors, and required policies. Use the current setup values from your provider, and avoid publishing multiple competing SPF records. For a fuller email security workflow, see the SPF, DKIM, and DMARC Setup Guide.
3. Verifying a third-party service
Website analytics, advertising platforms, webmaster tools, certificate systems, and other services commonly ask for a TXT record. Add the requested host and value exactly. Some providers use an A record, CNAME, or a file upload instead, so do not substitute a different record type. After verification succeeds, check whether the provider wants the record retained. Some verification records are also useful for future account recovery or re-verification.
4. Adding a subdomain
For a subdomain such as shop.example.com, use the host label shop unless your DNS interface requests the full name. An A record can point it to an IP address; a CNAME can point it to a platform hostname. Keep subdomain records separate from the root and www records so a change to one service does not unintentionally move another.
5. Moving hosting or DNS management
When moving a site, first lower the relevant TTL if your providers recommend doing so, record the existing zone, and prepare the new records. If you are changing nameservers, recreate all required records at the new DNS provider before switching delegation. This includes website, email, verification, security, and any less obvious records used by subdomains. A domain transfer and a DNS change are related but separate operations; the registrar controls registration, while the authoritative DNS provider controls the active zone. The registrar versus hosting provider decision matrix explains that separation in practical terms.
What to double-check before and after a change
- Confirm the authoritative provider. Check the domain’s nameservers and open the DNS dashboard associated with them.
- Save the current configuration. Export the zone if the provider supports it, or record each existing record, value, and TTL.
- Write down the intended outcome. For example: “Make
www.example.comload the new host without changing email.” - Check for conflicts. A hostname should not have an A record and a CNAME at the same time. Review duplicate MX, SPF, or verification records as well.
- Copy values precisely. Check dots, hyphens, underscores, capitalization where relevant, and trailing periods accepted by the interface.
- Review TTL and propagation expectations. DNS resolvers may continue using cached data until the previous TTL expires. A change may appear in one location before another.
- Test from more than one perspective. Use the provider’s verification tool, a DNS lookup utility, or a DNS propagation checker, then test the actual website or email flow.
- Check HTTPS separately. DNS resolution does not install or renew an SSL certificate. Use the SSL certificate checklist when changing hosting or hostnames.
For a website change, test both the root domain and www, plus any important subdomains. For email, test inbound delivery, outbound delivery, and authentication results where your mail provider makes those available. If only one network or device shows the old destination, cached DNS may be the explanation; if authoritative lookup returns the wrong value, revisit the record itself.
Common mistakes
- Editing the registrar when DNS is hosted elsewhere. The registrar’s DNS page may not control the live zone after custom nameservers are enabled.
- Entering a URL in an A record. A records require an IP address. A hostname belongs in a CNAME or the record type specified by the provider.
- Deleting MX records while changing the website. Website hosting and email hosting can be separate. Preserve mail records unless email is intentionally moving.
- Publishing more than one SPF record. SPF is normally combined into one TXT policy according to the sending providers’ instructions.
- Assuming a CNAME creates a redirect. It aliases DNS; it does not automatically send a visitor to a different URL.
- Changing nameservers without copying the zone. A new provider may begin with an empty zone, causing website, email, and verification failures.
- Repeatedly editing during propagation. Record each change and allow enough time to determine whether the previous change worked.
- Ignoring renewal and account security. DNS depends on access to the registrar and DNS provider. Review domain lock, administrator accounts, recovery methods, and renewal settings using the domain renewal checklist.
When to revisit
Keep this checklist with your domain records and revisit it before a hosting migration, domain transfer, email-provider change, new subdomain launch, major seasonal campaign, or third-party verification request. It is also useful after a security incident, unexplained email failure, certificate problem, or website outage.
Review the zone at least during planned technical reviews and whenever a provider changes its setup instructions. Provider-specific hostnames, authentication records, certificate requirements, and dashboard labels can change even when the underlying DNS concepts remain the same. At each review, remove obsolete verification records, confirm that email authentication still reflects current senders, check that website records point to the intended host, and verify that only authorized people can edit DNS.
Action plan: identify the authoritative DNS provider, export or document the current zone, write down the single change you intend to make, apply the provider’s exact record values, and verify the result using both a DNS lookup and the affected website or email service. If the change involves a nameserver switch or a critical business domain, schedule it with a rollback plan and keep the previous records available until every important service has been tested.