Change nameservers without losing email and verification records Print

Quick answer

To change nameservers without losing email, prepare the complete DNS zone at the new provider before updating the delegation at the domain's registrar. Preserve MX and mail-host records, verification records and required authentication records. Coordinate DNSSEC, then verify the website and mail independently. A website-only move can often keep the existing nameservers.

Applies to

Use this guide when moving DNS for a domain connected to Interactive Online hosting. You need authorized access to the domain registration and both DNS providers. The registrar, website host and email provider can be different companies. cPanel's Zone Editor changes a zone; it does not replace the registrar's nameserver delegation.

Prepare the zone before the change

1. Find the current authoritative DNS provider and record the current nameservers. Confirm whether you need a whole-zone move or only new website A/AAAA/CNAME records. Review the domain connection options if you are keeping DNS at your registrar or Cloudflare.
2. Export or record the existing zone and its TTL values. Include website A/AAAA/CNAME records, MX and mail destinations, SPF, DKIM, DMARC, service-verification TXT records and other records used by the business. Treat private verification values as account information.
3. Create the required zone at the new provider and compare it with your inventory. Automatic DNS scans may miss records. Confirm the destination website and intended mail service are ready. A mailbox must still exist at its actual provider.
4. Check whether DNSSEC is enabled and whether the registrar publishes a DS record. Follow the old/new providers' migration procedure before changing delegation. A previous provider's DS record can break validation at the new provider. Plan how and when to enable and verify DNSSEC for the new zone.
5. Record the proposed change time, rollback details and the people authorized to make changes. Plan caching and TTL changes and keep the old service available until the replacement is verified.

Change nameservers at the registrar

1. Sign in where the domain is registered. If it is registered through Interactive Online, open the Client Area, choose Domains > My Domains, select the exact domain and look for its Nameservers or Manage Nameservers option. Available controls depend on the registrar integration and your permissions.
2. Enter the exact nameservers assigned by the new DNS provider. Replace the previous set as instructed; do not combine unrelated providers' nameservers. Use hostnames rather than IP addresses unless the registrar explicitly asks for something different.
3. Save and check the registrar's readback. A saved form does not prove that public delegation or cached answers have changed. Some registrars restrict changing to external nameservers; follow their supported procedure or ask support before transferring a domain.

Email stopped working after changing nameservers

Compare the new zone's MX records and their mail-host A/CNAME records with the intended email provider's instructions. For cPanel-hosted mail, check local or remote routing separately. For messages missing from the provider's mailbox, use the delivery troubleshooting guide. Review SPF, DKIM and DMARC when investigating sender authentication too; a website homepage working does not verify mail delivery.

DNSSEC SERVFAIL or a domain that stopped resolving

Record the exact resolver error and compare the registrar's delegation and DS information with the new provider's DNSSEC instructions. An old or cached DS record can cause validating resolvers to return SERVFAIL. Avoid changing unrelated website IPs to fix a validation failure. Ask support or the DNS provider to verify the migration state before making another change.

Verify website, email and service records

Check the public nameserver delegation and authoritative answers for the domain. Open both the root and www HTTPS addresses, send a controlled message between addresses you own, confirm receipt and reply, and verify important third-party services. Check from another network or resolver when cached answers differ. Record the result and time. Keep the old zone and service until the transition is confirmed; a rollback also encounters DNS caches.

When to ask for help

Contact support before changing nameservers if the provider, zone contents, DNSSEC state or permitted control is unclear. Give the domain, registrar/DNS provider, old and proposed nameservers, change time/time zone, affected service and exact redacted error. Keep account passwords, API tokens and unrelated verification values private.

Moving DNS to Cloudflare? Use the cPanel-hosted website migration guide or the Shopify DNS and optional O2O guide for the platform-specific records, verification and rollback steps.

Related help

• Connect Your Domain: DNS, Nameservers & Cloudflare
• Find where your domain's DNS is managed before changing records
• Prepare a domain transfer while keeping the website and email running
• Check website and email behavior after a migration
• Plan DNS TTL changes before a website cutover
• Collect useful evidence when an email message is missing
• Send a website support request with useful troubleshooting details

Official references

• WHMCS domain management
• Cloudflare nameserver updates
• Cloudflare DNSSEC migration considerations
• cPanel Zone Editor

Content and source review: November 1, 2026. Registrar options and DNSSEC procedures vary by provider.