Crypto-only payments. Pay with USDT or USDC.
DNS Records for a Website and Business Mail: A Practical Map
The Hightide Hosting Editorial Team · 2026-10-02
A website loading correctly does not prove that business mail is configured. Map each DNS record to the service it supports before editing a zone or changing nameservers.
Find the authoritative place to edit
Start with the domain's nameserver delegation. It identifies the DNS service responsible for the zone. A registrar dashboard may display a record editor without being the authoritative provider currently answering queries. Editing the wrong copy can look successful in the interface while leaving public answers unchanged. Record where delegation is managed and where active records must be maintained.
Before making changes, export the zone if the provider supports it or save an inventory of record names, types, values, and TTLs. Include records for services you are not changing. A new website should not erase mail routing, domain verification, or other subdomains simply because their purpose is less obvious than the record pointing at the main site.
Map website records to destinations
An A record points a name to an IPv4 address; an AAAA record points to an IPv6 address; a CNAME aliases one name to another. Use the destination values supplied for your actual hosting service. An old AAAA record can keep some visitors reaching an old host even after you update the A record, so inspect both address families when troubleshooting.
Decide how the root domain and www should behave, and check each separately. Do not invent a destination from an example in an article. Also avoid placing a conventional CNAME alongside other records at the same name; providers that offer root-domain alias features may handle that differently. Follow the authoritative provider's supported configuration rather than assuming every editor implements aliases identically.
Treat mail routing and authentication separately
MX records direct incoming mail to a mail service. They do not create a mailbox or establish outgoing-mail authentication. TXT records can carry provider verification and authentication information. SPF, DKIM, and DMARC have different roles: authorized sending sources, message signatures, and domain policy or reporting. Use the exact records issued by the mail provider for your configuration.
If several services send mail for one domain, coordinate the SPF configuration instead of publishing conflicting independent policies. Keep DKIM selectors distinct as instructed by each sender. Approach DMARC changes with an understanding of legitimate mail sources and available reports; a copied policy can reject valid business messages. A working inbox alone does not demonstrate that every sending service is authenticated correctly.
Plan cache behavior and a rollback
TTL influences how long DNS answers can remain cached. Lowering it ahead of a planned change can help shorten future cache periods, but it does not instantly erase answers already cached under an earlier TTL. Avoid a universal propagation deadline. Check the authoritative answer first, then compare results from other resolvers to distinguish an editing problem from cached information.
When changing nameservers, populate the destination zone before updating delegation. Preserve mail and verification records, and coordinate DNSSEC with the provider if it is in use; mismatched delegation and signing settings can break resolution. Keep the old values available for rollback. Make a small, documented change and verify its effect before making another unrelated adjustment.
Diagnose with concrete evidence
For a support ticket, provide the affected hostname, record type, expected destination, observed result, and time of the check. Do not attach passwords or private mailbox messages. If DNS answers are correct but the website fails, investigate hosting or application behavior. If mail fails while the site works, examine mail-specific records and mailbox configuration rather than repeatedly changing the website record.
Hightide support is through dashboard tickets. Paid orders require manual review, so first confirm that the destination service is actually ready. Public DNS can reveal infrastructure relationships and is not an anonymity layer. Hightide also has analytics; neither DNS configuration nor no-ID platform signup supports a claim that the website or its operation has no observable footprint.
Will changing my website A record change incoming mail?
Not necessarily. Incoming mail uses MX records, but check for dependencies before making changes.
Can I copy another domain's mail authentication records?
No. Obtain the exact records for your domain and sending services from the relevant mail providers.