Open the DNS zone and export a copy. Note the records for the root domain, www, other web subdomains and any AAAA addresses. Separately note MX records, the mail-server address, SPF, DKIM, DMARC, autodiscover and any provider verification records. If mail points to mail.example.com, check that hostname's A or AAAA record too.

1. Obtain the new website address or CNAME target from the hosting service. Confirm the new host has your domain configured and a suitable HTTPS certificate.
2. In DNS Manager, edit the website's A, AAAA or CNAME entries according to that host's instructions.
3. Review both the root domain and www. They may use different records.
4. Keep the existing mail records when email is staying with its current provider. Do not replace the whole zone with a hosting template unless you have checked its effect on mail.
5. Wait for the change to finish, then check the public answers and load the website over HTTPS.
6. Send a test message to the domain from an external mailbox and reply from the domain to confirm mail still works.

A nameserver change transfers authority for the entire DNS zone. Copy all required records to the new DNS service before changing the registrar delegation. The new website host's automatically created records may not include your external mail provider, custom subdomains or ownership checks. Keep the old DNS service running through the transition.

Check DNSSEC before switching. A parent DS record tied to the old DNS signing keys can cause validation failures after an uncoordinated move. Follow the DNSSEC migration guide rather than copying old DNSKEY or signing records into the new zone.

This illustrative zone serves a website on one address and email on another host. In your DNS Manager, use the actual hosting and mail-provider values. The sample addresses are reserved for documentation, and the record layout is not a provider configuration to paste unchanged.

example.com.       300   IN  A      192.0.2.10
www.example.com.   300   IN  CNAME  example.com.
example.com.       3600  IN  MX     10 mail.example.com.
mail.example.com.  3600  IN  A      192.0.2.25

Read the result: A website move can require changing the apex A record while leaving the MX and mail-host address intact. Because www follows the apex here, it follows that website move too. An existing AAAA record must also be reviewed so IPv6 visitors do not continue reaching the old website.

Preserve mail verification, SPF, DKIM, DMARC and service-discovery records from your actual inventory. Confirm the destination web server recognises both website names and has suitable certificates before making the reviewed change.

Compare public MX answers with the expected mail provider, then resolve the MX target itself. If the hosting control panel also handles mail routing, confirm it treats externally hosted mail as remote. DNS and local delivery settings must agree. Give support the failing recipient domain, the time of the test and the returned error text, with private message content removed.

• Add, edit and remove DNS records in the client area
• Import DNS records from another provider
• Enable DNSSEC and complete the DS-record setup
• Create and verify an email forwarder for your domain

• ISC BIND: dig and delv reference