What to know
- Identify whether hosting, mail or authoritative DNS is changing.
- Preserve the full zone, including email and verification records.
- Plan TTL and DNSSEC transitions and verify real customer tasks.
Separate the changes you are making
Moving a website to another server does not automatically require moving its email or authoritative DNS. Start with a written scope: which hostname changes address, which provider will answer DNS queries and which service keeps the mailboxes. Our suggested migration worksheet assigns an owner and a rollback decision to each change.
Copy the complete record inventory
According to the DNS record reference, A and AAAA records map addresses, MX identifies mail delivery destinations and TXT records carry information used by services such as email authentication. Export the existing zone and compare it with the destination. Include verification records, subdomains and mail-related entries. A successful homepage request does not confirm that outgoing invoices are authenticated.
Plan cache and DNSSEC behavior
TTL controls how long DNS records may be cached. If you lower a TTL for a planned change, allow the previous TTL to expire first; lowering it cannot instantly erase old cached answers. DNSSEC also needs a deliberate transition. Follow the provider’s DNSSEC migration instructions so the registrar’s DS record matches the new signing arrangement. Do not leave an obsolete chain of trust in place.
Rehearse the customer journey
Before the switch, test the new server using an appropriate hostname override and a valid certificate. Our acceptance list includes both address families when published, the main domain, www, sign-in, contact forms and a test order. Send mail from each legitimate sending system to an external inbox and send a reply back. Record expected results so another team member can repeat the checks.
Close the migration with evidence
Keep the old service available for the agreed transition period and monitor failures before cancelling it. Record the final zone, test results and any remaining redirects. Retain a protected backup and restore plan for application data. If you are planning a hosting move or reviewing domain settings, provide the existing service list with the request so website and email requirements can be assessed together.
Sources & further reading
Primary sources supporting this article. The practical recommendations are Kiava’s general guidance and should be adapted to your project.