hostinglinks.
PRACTICAL TECH, EXPLAINED

DOMAIN ROUTING

DNS records explained without the alphabet soup

A website move should not accidentally become an email move. Read the record's name, type and target together before replacing anything.

Updated 17 October 2026. Examples use the reserved domain example.com and documentation addresses. They are illustrations, not settings to paste into a live DNS zone.

Read a small DNS zone

Illustrative records for a website and separate email service
NameTypeValuePurpose
@A192.0.2.10Root website address
wwwCNAMEexample.comAlias for the root hostname
@MXmail.example.com, priority 10Incoming email destination
mailA192.0.2.20Address of this example's mail server
@TXTProvider verification textProves domain control to a service

Many dashboards use @ for the root domain; others show the full domain or a blank name. A record named www applies to www.example.com, not every possible subdomain. Check how your provider displays names before adding a duplicate.

In this example, moving the website to 192.0.2.30 means changing the root A record. The www alias then follows that hostname. The MX, mail A and verification TXT records stay as they are because those services are staying put. Real hosting platforms may instead require a particular CNAME or several records: follow their exact instructions.

What each record does

A and AAAA: connect a hostname to IPv4 and IPv6 addresses respectively. If an old AAAA record remains after an IPv4-only move, visitors using IPv6 may still reach the previous server.

CNAME: aliases a hostname to another hostname. Its value is not a full web URL: do not add https:// or a page path. An alias does not redirect the browser to another website address. HTTP redirects are a separate hosting configuration.

MX: selects incoming mail servers. Lower priority numbers are preferred. Preserve every required destination and its priority when moving DNS.

TXT: holds text for verification and email authentication. SPF, DKIM and DMARC use specific names and formats supplied by your email service. A website host's DNS template is not a reason to discard them.

TTL: tells resolvers how long an answer can be cached. Reducing it immediately before a change does not remove answers already cached under the previous TTL. Prepare in advance and allow for that old value.

Check the answer your computer receives

On Windows, open Command Prompt. These read-only checks show different record types; replace example.com with your domain:

nslookup -type=A example.com
nslookup -type=AAAA example.com
nslookup -type=MX example.com
nslookup -type=TXT example.com

A successful DNS answer proves name resolution, not that a website, certificate or mailbox works. Open both the root and www website addresses, check HTTPS, and test incoming and outgoing email separately. Different resolvers may temporarily return different answers while caches expire.

Cloudflare proxying adds another layer

For supported web records, Cloudflare's proxy can return its own addresses instead of exposing the origin address. That is expected when proxying is enabled. An A record used for a mail server should be DNS only. MX and TXT records themselves are not proxied.

Ordinary CNAME restrictions at the root differ from provider features such as Cloudflare's CNAME flattening. Check the DNS provider's instructions rather than assuming every dashboard handles root aliases identically.

Keep a way back

  1. Export the zone and record the old values and proxy settings.
  2. Prepare and test the replacement hosting before changing traffic.
  3. Change only the records needed for the service being moved.
  4. Verify website and email behaviour. If necessary, restore the previous values, remembering that rollback also takes time to reach cached resolvers.

Changing nameservers replaces who serves the whole zone. Copy all required records to the new DNS provider first; changing just one web record is a much smaller operation.

Technical references

Cloudflare's record type reference and proxy status guidance explain provider behaviour. Microsoft's nslookup documentation covers the diagnostic command.