Website hosting and email can be moved separately. Changing nameservers without recreating the complete zone can interrupt services that had nothing to do with the website.
Prepare the cutover
- Inventory current DNS records, mail providers, verification records and subdomains.
- Back up the website and database, then prepare the destination with compatible PHP and configuration.
- Test the new site through a supported staging or preview method. Check certificates before relying on HTTPS.
- Decide whether to change only web records or move the authoritative DNS service. Preserve MX and authentication records when mail stays elsewhere.
- Plan a quiet cutover window, final data synchronisation and rollback criteria.
- Verify both website and mail after the change using independent connections.
Allow for mixed traffic
DNS caches can send visitors to old and new servers during transition. For transactional sites, avoid accepting conflicting writes in two places. Coordinate a maintenance window or a documented synchronisation strategy.
Keep the old service available for the agreed transition period. Do not cancel it immediately after your own browser reaches the new site. Track DNS provides useful checks, but a single local answer is not proof that every resolver has refreshed.
Official references
Reviewed 2026-10-22. Menus and availability depend on your hosting plan and server configuration.