How to change domain nameservers

Set at least two nameserver hostnames on the domain overview, wait for registry propagation, and rebuild website or mail records at the new DNS host.

What nameservers control

Nameservers are the authoritative DNS hosts for your domain. Changing them moves where the internet looks up your A, MX, TXT, and other records. On NextShopper you edit nameservers on the domain overview: enter at least two hostnames, save, and wait for the registrar adapter to update the registry. Help text notes: Two hostnames minimum. Glue records are not edited here.

This guide covers viewing, copying, and changing nameservers safely—and what to recreate at the new DNS host so websites and email keep working.

Who this guide is for

Customers pointing a domain to NextShopper DNS or to Cloudflare/another DNS provider
Anyone migrating away from parking nameservers toward hosting nameservers
Users troubleshooting “I saved DNS records but the public internet ignores them”

Before you start

Collect the exact NS hostnames from your DNS or hosting provider (for example ns1.example.net and ns2.example.net).
Understand that after NS change, records at the old host stop mattering for public resolution.
If email already works, export current MX/TXT before you switch so you can rebuild them.
Lower TTLs ahead of time when possible to shorten cutover pain.
Sign in and open the domain under Domains.

Step-by-step: change nameservers

Go to My products → Domains → open the FQDN.
Find Nameservers on the overview.
Replace the listed hosts with at least two valid nameserver hostnames.
Save and confirm Nameservers updated at the registrar adapter.
Optionally use Copy nameservers when you need to paste values elsewhere (Copied confirms).
Wait for registry and resolver propagation (minutes to 48 hours depending on caches).

After you switch away from NextShopper DNS

Log into the new DNS host immediately.
Recreate A/AAAA/CNAME for the website.
Recreate MX and authentication TXT for email.
Complete any SSL DCV records at the new host if a certificate is pending.
Only then delete obsolete records at the old provider.

If you switch to NextShopper DNS, manage records under the DNS tab instead.

What happens next / how to verify success

Portal shows your new NS list after refresh.
Public RDAP/WHOIS nameserver fields eventually match.
dig NS yourdomain against a public resolver returns the new hosts.
Website and mail work again once records exist at the authoritative host.

Common problems

Problem	What to try
Save requires two NS	Add a second hostname
Site down after change	Rebuild records at the new DNS host or temporarily revert NS
Email broke	Restore MX/TXT at the authoritative DNS
Still seeing old NS publicly	Wait for propagation; confirm registrar accepted the update
Custom NS needs glue	Contact support—glue is not edited in this console
Portal DNS edits ignored	Your NS are elsewhere—edit that host, or point NS back here

Frequently asked questions

Is changing nameservers the same as adding an A record?
No. NS chooses which company answers DNS; A records live inside that company’s zone.

Can I use only one nameserver?
The portal requires at least two.

Will EPP lock block NS changes?
Lock targets transfers. Ordinary NS updates usually still work while locked.

Should I enable DNSSEC before changing NS?
Coordinate carefully. DNSSEC/DS at an old host can break resolution after you move—see the DNSSEC guide.

Do portal DNS rows delete automatically when I leave?
They may remain stored, but they are not public until NS point here again.

Related guides

Still need help?

If nameserver updates fail at the adapter, open a support ticket or Contact with the FQDN and the NS hostnames you tried.