November 2026 renewal index is out · .com $11.59/year, the same every year · Paid in BTC, USDT, USDC, ETH, SOL, LTC
Language: English
Search a domain

Guide · checked 16 November 2026

How do you change nameservers without breaking your domain?

Nameservers decide which DNS host answers for your domain. Changing them is a single form at the registrar, but the records, DNSSEC and any glue have to be ready first, or the domain goes dark. This guide gives the safe order.

Last updated: · 6 min read

Quick answer

How do you change nameservers?

Here is how to change nameservers: recreate every DNS record at the new DNS host, turn DNSSEC off or publish the new DS record, then enter the new nameservers at your registrar. At Tallyname the Nameservers tab takes 2 to 13 hosts, or Cloudflare's 2 names; the change can take up to 48 hours to reach every network.

In brief
  • Nameservers delegate the domain: the registry points resolvers to them, and they serve every record.
  • Copy before you switch: records at the old host stop being served the moment the change applies.
  • DNSSEC first: a DS record that does not match the new host's keys makes validating resolvers reject the domain.
  • Glue for in-domain nameservers: ns1.yourdomain needs personal nameserver records with IP addresses.
  • At Tallyname: three modes in one tab, and Nameservers… in the bulk bar for many domains at once.

Which nameserver options does Tallyname offer?

Nameserver modes in the Tallyname client area and what each one means for DNS, forwarding and DNSSEC, read on 16 November 2026
ModeWhat you enterDNS records and forwardingDNSSEC
Tallyname nameservers (Recommended)Nothing: assigned at registrationManaged in the DNS and Forwarding tabsManaged signing available
CloudflareThe 2 names Cloudflare gives youManaged at CloudflareDS record from Cloudflare, published in the DNSSEC tab
Custom nameservers2 to 13 host namesManaged at your DNS providerDS records from your provider
Personal nameserversHosts under the domain, with 1 to 4 IPv4 and up to 4 IPv6 eachYour own DNS serversYour own signing

How do you change nameservers at Tallyname?

  1. Prepare the new DNS host

    Add the domain at the new provider and recreate every record: A, AAAA, CNAME, MX, TXT. An export of the zone in BIND format helps.

  2. Handle DNSSEC

    In the DNSSEC tab, turn DNSSEC off, or replace the DS records with the ones the new provider gives you.

  3. Open the Nameservers tab

    In My domains, click Manage, then Nameservers, and pick Cloudflare or Custom nameservers.

  4. Enter the hosts

    Type each nameserver, such as ns1.example.net; Add a nameserver allows up to 13.

  5. Save and confirm

    Click Save nameservers, then confirm Use other nameservers when warned that DNS, forwarding and managed DNSSEC here stop working.

  6. Wait and verify

    Allow up to 48 hours. Query the new nameservers directly to check they answer before removing anything at the old host.

What happens when you change nameservers?

The registry starts sending resolvers to the new servers, and every record now comes from there. RFC 1034 describes NS records at a zone cut as the markers of a delegation: the parent zone, here the registry, lists the servers authoritative for the child. Changing nameservers at your registrar updates that list.

The old DNS host does not hand its records over. Anything not recreated at the new host, a forgotten MX or a verification TXT, simply stops existing from the resolvers' point of view once caches expire. Tallyname's DNS tab can export the zone as a BIND file, the format most DNS hosts can import, so the copy can be checked line by line.

The change also moves the features tied to the old host. At Tallyname, web forwarding, email forwarding and managed DNSSEC work only with Tallyname's own nameservers; the client area shows a confirmation before you leave them, and the Forwarding tab says so once the domain points elsewhere. How each record type works is explained in how to point a domain to a server.

Why must DNSSEC be handled before a nameserver change?

Because the DS record at the registry vouches for one set of keys, and a new DNS host signs with different ones. ICANN's explainer describes DNSSEC as a chain of trust: each zone's key is signed by its parent, and a resolver that finds a signature that does not validate discards the answer and returns an error. RFC 4034 places the DS record in the parent zone, referring to the child's key by key tag, algorithm and digest.

Leave the old DS in place while a new host serves unsigned or differently signed answers, and validating resolvers treat the domain as under attack: it stops resolving for their users. Tallyname's Nameservers tab checks this and warns, when DNSSEC is on, to turn it off or update the DS records first.

The safe sequence is: turn DNSSEC off, wait for the old DS to expire from caches, switch nameservers, then enable signing at the new host and publish its DS. Tallyname accepts up to 6 DS records with SHA-256 or SHA-384 digests in its DNSSEC tab. Signing is covered step by step in how to enable DNSSEC.

When do you need glue records for nameservers?

When the nameservers are named under the domain they serve, such as ns1.example.com for example.com. A resolver cannot look up ns1.example.com without already knowing where example.com is served, so the registry stores the nameservers' IP addresses alongside the delegation. Those are glue records.

At Tallyname they are set under Personal nameservers in the Nameservers tab: add a host such as ns1, give it 1 to 4 public IPv4 addresses and up to 4 IPv6 addresses, save, then click Use as nameservers. The form refuses private, loopback and documentation addresses, allows 10 personal nameservers per domain, and blocks removing a host while the domain still uses it.

For many domains at once, select them in My domains and choose Nameservers… in the bulk bar: the same nameservers apply to every selected domain, up to 100 per action, and any domain with DNSSEC on is flagged first. According to Tallyname's survey of 16 November 2026, Tallyname renews 23 of 24 extensions below the crypto registrar average, with DNS hosting included. Moving a whole domain between registrars without a DNS gap is covered in how to transfer a domain without downtime.

Frequently asked questions

How long does it take to change nameservers?

The registry update is quick, but resolvers keep cached delegation data for a while. Tallyname's client area warns it can take up to 48 hours to reach every network.

Will my email stop working when I change nameservers?

Only if the MX and related records are missing at the new DNS host. Copy them before switching, and forwarding set up at the old host will not follow.

How many nameservers do I need?

At least 2, for redundancy. Tallyname accepts 2 to 13 custom nameservers, and exactly the 2 names Cloudflare assigns in Cloudflare mode.

Which is the best DNS host to switch nameservers to in 2026?

The one where you will manage the records you need. Keeping the registrar's DNS avoids the switch entirely; at Tallyname it is free and includes forwarding and managed DNSSEC.

Can I go back to Tallyname's nameservers later?

Yes, from the same tab or with the switch-back button shown wherever a feature needs them. Recreate the records in the DNS tab first.

Verdict
  • Copy records, clear DNSSEC, then switch: in that order the domain keeps resolving.
  • Keep Tallyname's nameservers if you want DNS, forwarding and DNSSEC in the client area.
  • Use custom nameservers when your host or DNS provider must manage the zone.
Sources (3)
  1. RFC 1034: Domain names, concepts and facilities — IETF (read 2026-11-16)
  2. RFC 4034: Resource records for the DNS security extensions — IETF (read 2026-11-16)
  3. DNSSEC: what is it and why is it important? — ICANN (read 2026-11-16)

Nameservers your way

Tallyname's own, Cloudflare's or yours: switch from one tab, for one domain or a hundred.

.com $11.59/year · same price at renewal · crypto

Search a domain