DNS Records Explained: A, AAAA, CNAME, MX and TXT
Learn what common DNS records do, how to verify changes and how to avoid breaking email when moving a website.

Quick answer
A maps a name to an IPv4 address, AAAA maps it to IPv6, CNAME aliases a name, MX points to mail exchangers, and TXT holds text used for purposes such as verification and email policies. Change records at the authoritative DNS provider and verify web and mail results independently.
The web address works but a verification token is missing
Query the record type and hostname named in the instructions. Check an authoritative answer before diagnosing caching. A TXT value at the apex is a different record from a token on a provider-specific subdomain.
A website cutover that preserves business email
Suppose a fictional shop uses managed email and is moving only its Node.js site. The owner exports the authoritative zone before the switch. The inventory includes records for the root and www names, an existing IPv6 address, mail exchangers and the mail provider's TXT records. The new host supplies a new root record and a target for www. The owner checks if an IPv6 address is still valid on the new host, keeps the appropriate mail entries, and updates only the necessary web records. After the change, the owner checks authoritative answers first, then tests HTTPS at both web addresses and sends and receives a sample message using an approved account on the real mail service.
If the registrar points to a different authoritative DNS provider, changes belong at the provider that currently answers for the zone. The records displayed at the registrar may be irrelevant until authority is switched. When delegation is the actual change, arrange the complete replacement zone before switching nameservers. After web and mail checks pass, note the correct paths and support contacts in one operational record. In future DNS changes, labels such as “website target” and “mail exchanger” make the intention legible. That helps prevent someone from assuming that the company that registered the domain also handles DNS, websites and every mailbox.
Find the zone owner
Move a website whose domain was purchased from a registrar and hosts elsewhere. Find the authoritative nameservers and compare them with the provider panel you intend to edit.
Common problem. A correct record is added in a registrar UI that does not control the live zone. Check authoritative answers first, then compare with a public resolver and your workstation.
Identify who can edit the live DNS zone before scheduling any hosting cutover.
Understand website addresses
Point a website and its www name at a hosting environment. Use the hosting provider's exact record type and target. Distinguish the bare domain from the www subdomain.
Common problem. An outdated AAAA record sends IPv6 users to the previous host while IPv4 tests work. Check each specified record and request the website over both supported address families where possible.
Test the final URL and HTTPS certificate as well as the DNS answer.
Use aliases correctly
Point a subdomain at a managed platform's hostname. Use a CNAME only where allowed and verify the target name. Follow the provider’s documented apex-domain handling if needed.
Common problem. An entry is added beside conflicting records or the provider interprets the target as relative to the zone. Query the intended fully qualified name and follow the response to its actual address.
Keep a map of who owns both the alias and its target so later moves are traceable.
Protect email routing
Move website hosting while retaining a separate business email service. Inventory existing MX, SPF, DKIM and DMARC records and preserve the mail provider's settings during the migration.
Common problem. The website loads on the new host, but replies stop arriving because nameservers were replaced without copying mail records. Confirm mail exchanger records and test sending and receiving with an approved account after the change.
Include all configured mail domains and selectors in a pre-migration record export.
Verify ownership records
Add a TXT value requested by a platform you are configuring. Check the required host name, value and zone and verify it is published verbatim according to the provider form.
Common problem. The domain name is entered twice because the DNS editor appends the zone automatically. Check the actual queried name and value before clicking platform verification again.
Keep verification records only as long as the platform requires them for your ownership procedure.
Handle caching during a change
Understand why two devices show different addresses immediately after a cutover. Check the authoritative response and compare it with cached resolver answers. Use TTL as a planning factor.
Common problem. The new record is changed repeatedly because cached clients have yet to refresh their old answers. Record the old and new addresses, timestamp and TTL and avoid unnecessary changes while answers converge.
Plan lower TTLs ahead of a migration if your DNS provider and timing make that useful.
Separate DNS and web redirects
Redirect visitors from www to the chosen canonical address. Set up DNS so requests reach a valid endpoint, then configure the HTTP redirect at a host or supported edge service.
Common problem. An alias is treated as if it changes the browser's visible URL or preserves a path automatically. Check the exact HTTP response, target path and HTTPS behavior using both entry names.
Compare the output with the site's canonical link and sitemap after testing.
Make a cutover checklist
Plan a low-risk update for a small business domain. Export records, identify dependencies, record who can revert changes and choose a test window. Include success conditions for web and mail.
Common problem. A rollback owner remembers the old host name but none of the previous record values. Test that the old and new host are both reachable as planned and store the previous values securely.
Check several client networks after the switch and document follow-up ownership of external dependencies.
Verify the individual records after a change
For a test domain you administer, query the relevant type explicitly. Commands such as dig example.com A, dig example.com AAAA and dig example.com MX inspect different information. Windows users can use Resolve-DnsName example.com -Type MX when their system supports the command. Replace the example with your zone and optionally query its authoritative server to distinguish zone data from resolver caches. Look for the exact owner name, target and TTL. Check relevant TXT values independently and understand which provider uses each one. Make the HTTP and mail checks separately. A DNS result tells you how a client might locate a service, but the service still has to present the right certificate, redirect destination or mailbox behavior.
