ESDomain editorial team · Reviewed 2 November 2026
Identify what is changing
Changing nameservers selects which servers publish your domain’s DNS answers. It does not automatically copy mailboxes, stored messages or website files. Identify the current provider and the destination before starting. Confirm whether the work concerns DNS alone or whether another team is also moving hosting or email as part of the same project.
Choose a time when you can check results and reach the people responsible for the services. Keep the previous nameservers and a copy of the existing zone. If several people manage the domain, agree who makes the change and who validates each service. Avoid two teams publishing different configurations during the same maintenance window.
Prepare the complete zone first
Collect the records for the website, email, verification services and active subdomains. Include A, AAAA, CNAME, MX and TXT where present, preserving names, values and priorities. Ask each service administrator about additional entries. An automatic scan or a visible list from one panel may still require review before you can treat the inventory as complete.
Create and review the destination zone before changing delegation. If DNSSEC is enabled, coordinate signing and DS changes according to both providers’ procedures. Do not delete security settings or unrelated records at random to fix a failure. Prepare that part with support if you cannot confirm how the existing signed domain should transition.
Save the exact nameservers
Enter each nameserver in its own field and review the spelling. ESDomain provides additional fields when more servers are needed and lets you review the saved result. Use the full set assigned by the destination provider. Do not mix two providers’ servers on the assumption that this will make both zones operate together.
If you choose ESDomain’s nameservers, prepare the records in its editor. If you choose external servers, manage their records with that external provider. Save the time of the change and check delegation and the new zone’s responses. Some lookups may continue using earlier information while their cached answers remain valid, so keep both configurations available.
Test mail in both directions
Visit the main website and important subdomains. Send a message from an external mailbox to the domain, then reply from it. Check forms, receipts and other applications that send email as well. A working homepage does not establish that MX records and outbound authentication settings were copied correctly or that every sending application still works.
Keep the previous service available during transition and record specific failures. If reverting becomes necessary, remember that restoring nameservers is also affected by caches and cannot guarantee instant recovery. Once checks pass, document where future DNS changes belong. That final handover helps prevent someone from editing the former provider’s zone after it has stopped being authoritative.