DNS records are the instructions that tell the internet where your website, email, verification services, and other domain-based tools should connect. This practical checklist explains which record to use, what each field means, how to connect a domain to hosting, and what to verify before changing live DNS.
Overview
When you register a domain, the domain name itself does not automatically know where your website or email service is hosted. DNS management connects that name to the correct services through records stored in a DNS zone.
Most DNS providers use similar concepts, although field names and interface layouts vary. Before making a change, identify the exact hostname, destination value, and record type supplied by your hosting or service provider. Keep a written copy of the existing records so you can restore them if necessary.
| Record | Typical purpose | Common fields | Example value |
|---|---|---|---|
| A | Points a hostname to an IPv4 address | Name, IPv4 address, TTL | 192.0.2.10 |
| AAAA | Points a hostname to an IPv6 address | Name, IPv6 address, TTL | 2001:db8::10 |
| CNAME | Points a hostname to another hostname | Name, target hostname, TTL | app.example-host.com |
| MX | Specifies where domain email should be delivered | Name, mail server, priority, TTL | mail.example.com |
| TXT | Stores text used for verification and email authentication | Name, text value, TTL | v=spf1 include:provider.example ~all |
| NS | Identifies the authoritative DNS servers for a zone | Name, nameserver hostname | ns1.dns-provider.example |
| SRV | Defines the host and port for a particular service | Service, protocol, priority, weight, port, target | 0 5 443 service.example.com |
| CAA | States which certificate authorities may issue certificates | Name, flag, tag, value | 0 issue "ca.example" |
TTL, or time to live, tells DNS resolvers how long a record may be cached. A shorter TTL can make planned changes easier to adjust, while a longer TTL can reduce repeated lookups. Use the value recommended by your DNS provider or service documentation, and avoid changing TTL repeatedly without a specific reason.
Checklist by scenario
To connect a domain to web hosting
- Confirm whether the host requires an A record, AAAA record, CNAME record, or a change to nameservers.
- Find the hosting destination in the hosting control panel or setup instructions. Use the exact IPv4 address, IPv6 address, or target hostname provided.
- Set the record name for the root domain, commonly represented by
@or left blank. Forwww, create the requested record separately unless your provider tells you otherwise. - Remove only conflicting records for the same hostname. Do not delete unrelated MX, TXT, verification, or subdomain records.
- Save the change, allow time for cached answers to expire, then test both the root domain and
wwwversion. - Confirm that the hosting account recognizes the domain and that HTTPS is configured separately. DNS pointing alone does not guarantee that an SSL certificate is installed or active.
If you are changing providers, map the old and new records before editing. A migration checklist should include the website, email, subdomains, verification records, and any developer tools that use the domain. For broader planning, see this domain portfolio management checklist.
To configure email with an MX record
- Use the mail servers and priority values supplied by your email provider.
- Set the MX record name to the root domain unless the provider specifies a different subdomain.
- Enter each mail server as its own MX record when multiple servers are supplied.
- Use the provider's priority values exactly. Lower numerical values generally indicate higher delivery preference, but follow the provider's instructions.
- Review TXT records required for SPF, DKIM, and DMARC. These are separate from MX records and should not be substituted for them.
- Send and receive a test message after the records are visible, while monitoring for configuration or authentication errors.
To verify ownership of a domain or service
Many SaaS, search, analytics, and certificate services ask for a TXT record. Copy the complete host or name and value exactly as provided. Some interfaces automatically append your domain, so entering the full domain can accidentally create a duplicated name. Do not remove an existing TXT record unless you have confirmed that it is obsolete; a domain can need several TXT records for different services.
To point a subdomain to an application
Use an A or AAAA record when the service gives you an IP address. Use a CNAME when it gives you a hostname such as project.provider.example. A CNAME is usually appropriate for a subdomain such as app, docs, or status. Check whether the target provider requires a trailing dot, a particular hostname, or an additional verification record.
What to double-check
- Nameserver location: Edit records wherever the authoritative nameservers are managed. Changing records at your registrar will have no effect if another DNS provider is authoritative.
- Root versus subdomain:
@, a blank name field,www, andmailrefer to different hostnames in most DNS panels. - Record conflicts: A hostname should not have an incompatible combination of records. In particular, review existing A, AAAA, and CNAME records before adding another value.
- Trailing dots and formatting: Some panels display fully qualified names with a trailing dot and others add the domain automatically. Follow the panel's format rather than guessing.
- Email authentication: SPF is normally represented by one SPF policy in a TXT record. DKIM values are often published under a selector subdomain, and DMARC is commonly placed under
_dmarc. Use the exact values generated by your email provider. - Verification: Query the record from more than one network or use a DNS lookup tool. A local cached answer may not reflect the current authoritative value.
- HTTPS: After connecting hosting, verify the certificate, redirect behavior, and both preferred and non-preferred hostname versions. The SSL certificate setup guide covers the next stage.
Common mistakes
Changing nameservers when only an A record was needed. Nameserver changes can move control of the entire DNS zone. Use them only when you intend to delegate DNS management to another provider and have recreated all required records there.
Using a CNAME at the root without checking provider support. Standard DNS rules treat a CNAME differently from ordinary address records, and some DNS providers offer special root-domain behavior while others do not. Follow the provider's documented method for the root domain.
Deleting records to make the panel look tidy. Old-looking TXT, MX, or verification records may still support email, certificates, or an external service. Confirm ownership and purpose before removal.
Expecting instant propagation. DNS caches update at different times based on prior TTL values, resolver behavior, and the provider's systems. Test from multiple locations and keep the previous service available during a planned migration when practical.
Combining email policies incorrectly. Adding multiple SPF policies or copying DKIM and DMARC values into the wrong hostname can cause authentication failures. Treat each provider's generated configuration as a set and validate it after publishing.
Testing only one hostname. A working example.com does not prove that www.example.com, mail.example.com, or application subdomains are configured correctly. Test every hostname used by visitors, staff, integrations, and deployment workflows.
When to revisit
Return to this checklist before moving web hosting, changing email providers, launching a new subdomain, adding a SaaS product, renewing a certificate workflow, or transferring a domain. It is also worth reviewing DNS during seasonal planning cycles and whenever your team changes its deployment or security tools.
For an operational review, confirm that the registrar account, DNS provider, hosting account, and email administrator are documented; check that renewal and access details are current; remove records for services that have been retired; and export or record the intended zone configuration. Provider interfaces, validation requirements, and recommended email-authentication settings can change, so review their current instructions before a high-impact update.
Make one controlled change at a time, record the previous value, and define a rollback plan. After each change, verify authoritative DNS answers, website access, email delivery, certificates, and important subdomains. This simple habit turns DNS management from trial and error into a repeatable website setup and troubleshooting workflow.