Changing nameservers hands DNS control to another provider. If the new DNS zone is missing records, your website or email can stop working. To switch safely, copy all existing records first, lower TTL, confirm propagation, and validate web and mail resolution before removing the old setup.
What Happens During the Switch
Nameservers tell the internet where to find your DNS records. When you change nameservers, you transfer DNS control from one provider to another.
The old nameservers stop being authoritative. The new nameservers become the source of truth. Any records that existed only on the old nameservers, and weren't copied, effectively disappear.
This isn't a merge. It's a handoff. The new provider starts with a blank zone unless you populate it first.
Why Email Breaks Instantly
MX records direct email to your mail servers. If your new DNS zone lacks MX records, incoming mail has nowhere to go. Messages don't queue, they fail immediately.
SPF and DKIM records also live in DNS. Forgetting these causes deliverability problems even if MX records exist.
The rule: Copy records first, switch second.
The Migration Checklist
Step 1 — Export Current Records Document every record: A, AAAA, CNAME, MX, TXT (SPF, DKIM, DMARC), and others.
Step 2 — Recreate on New Provider Add all records to your new DNS zone before switching. Verify values match exactly.
Step 3 — Lower TTL Reduce TTL to 3600 seconds (NameSilo's minimum) on critical records 24-48 hours before switching. This speeds propagation if corrections are needed.
Step 4 — Switch Nameservers Update nameservers at your registrar.
Step 5 — Verify Resolution Use DNS lookup tools to confirm records resolve correctly. Test website and send test emails.
Step 6 — Monitor 48 Hours Watch for issues as global caches update. Keep old provider access until confident everything works.
Changing Nameservers in NameSilo
Go to Domain Manager, tick the checkbox next to your domain, select "Change Nameservers" from the action panel, enter new nameserver addresses, and click Submit.
Changes submit immediately, but global propagation takes time, most resolvers update within hours, some take 48 hours.
Common Mistakes: Orphaned Records
Orphaned records exist on old nameservers but weren't copied. Common orphans:
- Subdomain records for apps or staging sites
- TXT records for domain verification
- SRV records for specialized services
- CAA records restricting certificate issuance
Audit thoroughly. Check for records created months ago for third-party services you may have forgotten.
What This Means for You
NameSilo provides DNS templates to restore default configurations if something breaks. Templates let you quickly reset to known-good states. Our support documentation covers DNS management step by step. Before any nameserver change, export current records from DNS Manager, this gives you recovery reference if issues arise. Frequently Asked Questions
What changes when I switch nameservers? DNS authority transfers to the new provider. All lookups query the new nameservers instead.
Will email stop working if I change nameservers? Only if MX records are missing from the new zone. Copy all mail-related records before switching.
How long does DNS propagation take? Most resolvers update within hours. Full global propagation can take 48 hours.
What is TTL and why lower it first? TTL tells resolvers how long to cache records. Lower TTL (minimum 3600 at NameSilo) means faster updates if corrections are needed.
Do I need to copy A/CNAME/MX/TXT records? Yes, all of them. Any record not recreated stops working after propagation.
How do I verify DNS after the switch? Use DNS lookup tools to confirm records return expected values from new nameservers.
What can cause downtime during a switch? Missing records, typos, or propagation delays while caches update.
Can I switch back if something breaks? Yes. Change nameservers back to the original provider. Propagation time applies again.
.png&w=2048&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)
.png&w=3840&q=75)