
Open the DNS settings for any domain and you’ll see a list of cryptic letters: A, AAAA, CNAME, MX, TXT. Edit the wrong one and your website or email can disappear. The good news is that common DNS record types have distinct purposes, and once you know them, DNS stops being scary.
This guide explains what each common record does, how they work together, and the mistakes to avoid.
A DNS zone is a set of instructions for your domain. Each record has a name (such as @ for the root domain or www), a type, a value, and a TTL that controls how long it can be cached.
When someone visits your site, their browser asks for the A or AAAA record. When someone emails you, their mail server asks for your MX records. Services like Google check TXT records to confirm you own the domain. Different questions, different records — all in the same zone.
@ → 203.0.113.10.2001:db8::1.These are the records you change when you move your website to a new host. Publish IPv6 only when the destination service and its configuration support it. Step-by-step instructions are in How to Point a Domain to Your Hosting.
A CNAME makes one name an alias of another name. For example, www → yourdomain.com or shop → shops.myplatform.com. When the target’s IP changes, the alias follows automatically.
Important limits:
@) at most providers. Some offer “CNAME flattening” or ALIAS records to work around this.MX records tell the world which servers accept email for your domain. Each has a priority number: lower numbers are tried first, and higher numbers have lower preference; use the complete configuration supplied by the provider rather than treating an unrelated server as an automatic backup.
Your email provider gives you the exact MX values. Follow the mail migration plan when replacing MX records; preserve the old configuration and test the intended destination. Not sure whether you need separate email hosting? Read Email Hosting vs Web Hosting: Do You Need Both?.
Email authentication is explained in Email Deliverability: SPF, DKIM and DMARC in Plain English.
For a reference to supported DNS record types and provider-specific behavior, review Cloudflare’s record documentation. Use the instructions for your active provider and the service you are connecting.
The name identifies the hostname to which the record applies. A panel may accept a short label, a full name or a symbol for the zone root. Read the field’s help before entering a value. Otherwise, you can accidentally create a name with the domain repeated twice or place a verification entry at the wrong location.
The value depends on the type. An address record expects an address, while an alias expects a hostname. A mail entry also has a preference field. DNS record types are not interchangeable, so copying the right characters into the wrong type does not produce an equivalent configuration.
The TTL describes caching behavior, not the location of your files or the lifetime of your domain registration. Record the previous value when planning a change. A lower value saved now does not retroactively shorten data that a resolver already cached under the old policy.
An A record associates a name with an IPv4 address. An AAAA record serves the corresponding IPv6 role. Obtain the correct addresses from the host or application provider. Do not assume that a server address shown in an old email is still the active destination.
When reviewing DNS record types during a move, check both address families where applicable. A visitor using IPv6 may reach a different destination from a visitor using IPv4 if one record was left unchanged. Test the relevant hostname and compare the answers with the intended network configuration.
A proxy or CDN can change what a public lookup returns. The public destination may intentionally differ from the origin server. Understand that setup before editing the record to match an origin address. DNS and the proxy’s routing configuration need to be reviewed together.
A CNAME creates a DNS alias. It is not an HTTP redirect that tells the browser to display another page address. The destination application must still serve the requested hostname correctly, including HTTPS. Confusing these two operations can produce a resolving name with a certificate or application error.
Use the target hostname supplied by the service. Do not enter a full web address with a path when the panel expects a DNS name. Review any existing data at the same name before adding the alias. Among DNS record types, CNAME has coexistence constraints that matter for the design.
Some providers offer flattening or other managed behavior at the zone root. Treat that as a provider feature rather than assuming every DNS panel supports the same configuration. Read the documented limitations and test the resulting public service.
MX records identify destinations for incoming mail to the domain. Their values should match the mail provider’s organization-specific instructions. The website host and the mail provider can be different companies. Changing a website address does not require rewriting mail routing unless the project includes a mail-service move.
Review all supplied preference values and destinations together. Do not add an unrelated server as a supposed backup. The server must be configured to handle the domain’s mail. DNS record types describe routing data, but they do not create mailboxes or transfer historical messages.
When switching mail services, use a migration plan that includes accounts, data and testing. Keep a record of the previous DNS configuration. Test new incoming and outgoing messages with accounts you control before cancelling a service that still supports the transition.
A verification service may ask for a TXT value at the root or at a specific prefixed name. Enter the full intended name according to your DNS panel’s conventions. An otherwise correct value at the wrong hostname will not satisfy the service’s check.
Keep the requesting service and purpose beside the record in your internal inventory. A zone can contain several unrelated TXT entries, and an unfamiliar value should not be deleted merely because the website loads without it. DNS record types can support services that are not visible in the home page.
After adding a verification entry, use the requesting platform’s own verification process and inspect the public record when needed. Avoid repeatedly generating or replacing values without recording which one the service currently expects.
SPF, DKIM and DMARC involve different mechanisms and record names. Follow the sending service’s exact instructions and coordinate the domain’s legitimate senders. A business can use separate systems for staff mail, website notifications and newsletters, so one setup wizard may not describe the entire environment.
Some DKIM configurations use a TXT public-key record, while others use CNAME delegation. Do not replace one with the other simply because a generic DNS record types guide shows a different example. The correct choice is the one supported by the service and the intended design.
Authentication records do not guarantee inbox placement. Test actual messages and inspect the relevant results through the provider’s supported tools. Keep changes documented so another administrator can understand why a sender was included or excluded.
SRV records contain service-specific fields such as a target and port. Copy the complete set of requested fields and record names. Do not try to approximate the configuration with an A record just because that interface looks simpler. Ask the application provider to clarify an unfamiliar field.
CAA expresses certificate-authority authorization policy. Review it with the certificate and hosting setup before changing it. An overly narrow or outdated configuration can interfere with the certificate process your services rely on. DNS record types used for security policy still require operational planning.
A domain does not need every available record type merely to look complete. Add data for a defined service or policy. An unnecessary entry can create confusion later, especially when nobody knows which application requested it or whether it can be removed.

Use the nameservers vs DNS records guide when deciding whether a task needs a delegation change or only an edit inside the existing authoritative zone.
NS records identify authoritative servers for a zone or delegated part of the namespace. Changing the domain’s authoritative provider is a different operation from updating a website address. Confirm where the registrar controls delegation and where the active DNS service manages zone data.
If a subdomain is delegated to another DNS service, its records may be managed there rather than in the parent zone’s ordinary entries. DNS record types should be interpreted in the context of that delegation. A record added at the wrong authority may not affect the public result.
Before any delegation change, inventory the services and review DNSSEC if it is enabled. Use the documented migration process for the providers involved. A short TTL on one website record is not a complete plan for switching authoritative DNS.
Create a small table with the full name, type, value, TTL, purpose and responsible service. Add priority or other fields where relevant. Keep a date and an owner for recent changes. This turns a list of cryptic entries into an operational record the team can understand.
Review the inventory before a hosting, email or DNS-provider move. Check DNS record types by purpose rather than copying only the entries that look familiar. Include verification and security records as well as website addresses. Confirm unknown entries with the responsible service.
Do not store passwords or private API credentials in the general inventory. Keep those in the organization’s approved credential system. Public record data and account access information have different handling needs, even when both are used during setup.

Use our dig and nslookup walkthrough to collect lookup evidence, and review DNS propagation and cached answers before assuming that different observations require another record edit.
Use a DNS lookup for the exact name and type to inspect the public answer. Record the resolver or authoritative server queried and the time. Different caches can reflect different stages of a recent change. Preserve the observation before drawing a conclusion about the provider.
Then test the actual service. A website should serve the intended pages over HTTPS. Mail routing should support controlled sending and receiving checks. A verification service should confirm its own record. DNS record types define data, but service health depends on more than the presence of that data.
If the answer is correct and the application still fails, investigate the destination configuration. A missing certificate, incorrect virtual host or unconfigured mailbox will not be repaired by repeatedly replacing a correct record. Keep the diagnosis focused on the layer that failed.

One common error is entering a record in an inactive zone. Another is including the parent domain twice because the panel automatically appends it. A third is copying a URL where a hostname or address is expected. Read the field guidance and compare the saved result with the intended full name.
Conflicting data can also cause trouble. Review existing entries before adding a new one, particularly when the service asks for a CNAME. DNS record types have different constraints, and a panel accepting an entry is not proof that the complete service design is correct.
Finally, avoid making several speculative edits at once. Save the previous values, change the relevant item and repeat the same test. A clear sequence makes it possible to identify the correction that helped and to reverse a mistaken change.
Imagine that a business buys a domain, launches a website and chooses a separate mail provider. It first identifies the active DNS service. It obtains the website destination from the host and the mail records from the mail provider, then documents the purpose of each requested entry.
The team enters each record using the correct name and type, preserving any existing services. It verifies the website and mail separately. DNS record types for verification and authentication are checked against the requesting platform rather than guessed from another company’s example.
Later, only the website moves. The team updates the records involved in that move and keeps the mail setup intact. Because the inventory explains each entry, the project does not turn into an unnecessary replacement of the whole zone.
Promotional recommendation: Consider KAWEDMA if you need to compare domain services, website hosting or business email. For a mailbox on your own domain, review KAWEDMA’s professional email plans and confirm the migration requirements before moving mail. Ask which DNS record types and values the selected service requires, and who will maintain the active zone. Confirm the setup and support scope before changing an existing domain.
No. A DNS alias and an HTTP redirect are different mechanisms. The application must still handle the requested hostname correctly.
No. Add records for a defined service or policy and keep their purpose documented. More entries are not automatically a better configuration.
No. The destination mail service must also be configured for the domain and accounts. Routing data does not create or migrate mailbox contents.
Yes. Different DNS record types and application settings support each service. Test them independently after changes.
Keep the final configuration and test results with the domain documentation so another administrator can review future changes without guessing.
We may earn a commission on purchases made through these links, at no extra cost to you.
Don’t miss the chance to participate in the biggest giveaway of this year.