Practical hosting guide
Connect a Domain Without Breaking Email
Point the website to its new host while preserving the records your email and other services need.
Record the current DNS before changing it
Identify the authoritative DNS provider and export or record the current zone. Include A, AAAA, CNAME, MX, TXT, verification records and any delegated subdomains. Record which systems provide the website, email and other services.
Nameservers select the DNS provider for the whole domain. Changing only a website A or CNAME record is often sufficient when the registrar and email provider remain unchanged.
Prepare the destination
- Add the domain to the destination hosting package.
- Copy the website and database and test the destination before changing public DNS.
- Obtain the exact website DNS values from the new host.
- If moving nameservers, recreate the required mail and verification records at the new DNS provider first.
- Review DNSSEC with the DNS and registrar providers when changing authoritative DNS; an incorrect DS record can break resolution.
Switch and test
Change the relevant website records in the authoritative zone, then check the apex domain, www and HTTPS. DNS caches can retain earlier values until their TTL expires. Keep the old host available during verification.
Send and receive test email and confirm the intended MX, SPF, DKIM and DMARC records. Run DNS lookup and DNS propagation checks to sample public records.
The platform’s custom DNS migration guidance explains why existing mail records should be copied before changing nameservers.
Separate domain registration from hosting
You can connect a website without transferring its registration. If you want to change registrar as well, use the domain transfer process as a separate planned step.
