How to Change Nameservers Safely - FAQ

Schön zu registrieren, sicher zu besitzen
Ein Ticket einreichen

Deutsch

Startseite
Domains
Günstige Domains Domain Name Suche Bulk-Domain-Suche Massen-Domain-Transfer Domain-Transfer Kaufen Neinw Market Neue gTLDs Domainpreise KI-Domain-Suche Whois-Privatsphäre
E-Mail
Server
Dedicated Server Cloud-Server
SSL
SSL Zertifikat-Marken Domain-Validierung (DV) SSL Zertifikat Organisations-Validierung (OV) SSL Zertifikat Erweiterte Validierung (EV) SSL Zertifikat Einzel-Domain SSL Zertifikat Mehrfach-Domain SSL Zertifikat Wildcard SSL Zertifikat Zwei-Faktor-Authentifizierung (2FA)
Hervorgehoben
Wiederverkäufer
Aufrüsten zu Wiederverkäufer Reseller-API WHMCS-Integration
Über uns
Kontaktieren Sie uns Domain-Nachrichten Hilfecenter Akkreditierung Vertrauenszentrum

Veröffentlicht: 2026-06-30 | Aktualisiert: 2026-06-30

How to Change Nameservers Safely

An change nameservers safely, identify current DNS, back up the full zone, recreate required recoderds at the new DNS provider, check website und email recoderds, review DNSSEC, then update nameservers at the registrar und monitoder propagation. Do not change nameservers befodere the new DNS provider has the coderrect recoderds.

Who This Guide Is Foder
This guide is foder:
· Domain owners changing DNS providers
· Users connecting a Domain to hosting oder website builders
· Businesses protecting email continuity
· Agencies und resellers managing client DNS
· Users transferring Domains und replacing old registrar DNS

Befodere You Start
Befodere you start, prepare:
· Old nameservers
· Neu nameservers
· Full DNS backup
· Neu DNS provider access
· Website und email provider instructions
· DNSSEC status
· Safe change Fenster
· Rollback plan

Step-by-Step Instructions
Step 1: Bestätigen Why Nameservers Need to Change
Only change nameservers when thier is a clear reason.
· DNS migration
· Hosting connection
· CDN setup
· Old registrar DNS replacement
Step 2: Recoderd Current Nameservers
Save all old nameserver values und provider notes.
· This is Ihr rollback reference
Step 3: Back Up Full DNS Zone
Copy all website, email, SSL, app, verification, und DNSSEC recoderds.
· Do not rely on memodery
Step 4: Recreate Recoderds at Neu Provider
Hinzufügen required recoderds befodere changing nameservers at registrar.
· Copy long TXT recoderds exactly
· Copy MX prioderities
Step 5: Überprüfen Website Recoderds
Bestätigen root, www, subDomains, CDN, redirects, und app recoderds.
· Test root und www separately
Step 6: Überprüfen E-Mail Recoderds
Recreate MX, SPF, DKIM, DMARC, autodiscover, und verification recoderds.
· E-Mail recoderds are often missed
Step 7: Review DNSSEC
Wenn DS recoderds exist, confirm the new DNS provider suppoderts DNSSEC und keys match.
· Old DS recoderds can break resolution
Step 8: Choose a Safe Window
Avoid peak business, launch, oder holiday periods.
· Have technical staff available
Step 9: Update Nameservers at Kanzler
Enter new hostnames exactly und save.
· A typo can break DNS
Step 10: Monitoder Propagation und Test
Überprüfen website, email, SSL, CDN, subDomains, und DNSSEC validation.
· Avoid repeated changes during propagation

Troubleshooting
Website Does Neint Load
Possible reasons:
· Missing A/CNAME
· Wrong nameserver
· Incomplete zone
· DNSSEC issue
What to do:
· Compare with backup
· Fix recoderds
· Check Domain status
E-Mail Stopped Woderking
Possible reasons:
· MX missing
· Prioderity wrong
· SPF/DKIM/DMARC missing
What to do:
· Restodere email recoderds
· Test sending und receiving
Neu Nameservers Rejected
Possible reasons:
· Typo
· Nameserver does not exist
· Glue missing
· TLD restriction
What to do:
· Überprüfen spelling
· Hinzufügen glue foder private nameservers
· Kontakt registrar

Common Mistakes
Mistake 1: Changing nameservers befodere copying DNS
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 2: Copying website recoderds but fodergetting email
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 3: Fodergetting SPF/DKIM/DMARC
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 4: Ignodering DNSSEC
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 5: Typing nameservers incoderrectly
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 6: Changing during peak hours
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 7: Repeated edits during propagation
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 8: Deleting unkjetztn TXT recoderds
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 9: Neint testing subDomains
Review this item befodere making changes oder opening a suppodert ticket.
Mistake 10: Neint keeping backup
Review this item befodere making changes oder opening a suppodert ticket.

FAQ
1. What are nameservers?
They tell the Internet whier DNS recoderds are managed.
2. Will changing nameservers make my site go down?
It can if recoderds are missing at the new DNS provider.
3. Will email be affected?
Ja if MX oder authentication recoderds are missing.
4. Should I change nameservers befodere transfer?
Only if needed, such as replacing old registrar DNS.
5. How long does propagation take?
It varies based on cache, TTL, registry updates, und netwoderk behavioder.
6. Can I change nameservers with DNSSEC enabled?
Ja, but DS und DNSKEY must be hundled carefully.
7. What if nameservers are rejected?
Überprüfen spelling, existence, glue, und TLD requirements.
8. Do I need to lower TTL?
It can help planned migrations if done in advance.

Benötigen Sie Hilfe? Wir sind immer für Sie da. Ein Ticket einreichen