How to change domain nameservers without losing needed DNS records

Nameservers decide which DNS provider answers for your domain. Changing them can affect the website, email, and connected services together. Saving nameservers does not copy the old DNS records to the new provider.

1. Get the exact nameserver set from the service you intend to use. To move DNS here, open My Account > Hosting services (or Services), expand Get your hosting ready, and select Use Lucid nameservers. Copy the nameservers displayed under Change your nameservers; do not substitute example values.
2. Inventory the current DNS records, including website addresses, mail records, verification records, subdomains, and any DNSSEC configuration. Save a copy.
3. Prepare the destination before changing delegation. Hosting is created after payment and domain confirmation, even while DNS points elsewhere. Preserve existing website, external email, and verification records in the destination zone; contact support if you need help preparing them. They are not imported automatically.
4. For a domain managed here, open My Account > Domains > your domain > Nameservers. Enter the exact replacement nameservers, one per line, and choose Save nameservers. For an external domain, make the change at its current registrar.
5. Replace the old set as instructed; do not leave unrelated old and new providers mixed together.
6. Return to hosting setup and choose Check nameservers. After delegation is confirmed, use Recheck hosting records if shown. The setup flow checks the local zone and adds missing hosting address records; conflicting addresses need review.

Confirm the result: Check delegation and query records at the intended DNS provider, then test the main website, www, and email. Cloudflare's DNS migration guidance also stresses reviewing records before changing nameservers; this principle applies regardless of provider.

If you prefer to keep your DNS provider: Choose Keep my DNS provider and follow its address-record instructions instead. Changing nameservers is optional. See Choose a DNS setup method.

If only some visitors see the change: Cached DNS answers may still be in use. Follow the propagation guide before making another change.

If the site or email breaks: Compare the new zone with your saved inventory. Missing mail or verification records are not fixed merely by waiting. If DNSSEC was enabled, ask support to check that its chain of trust matches the new DNS service.

Related: Where to edit DNS, DNS propagation, DNSSEC.