How to Move DNS Hosting Without Changing Your Registrar

You move DNS hosting without changing your registrar by changing the set of name servers the registrar publishes for your domain, after you have already built and verified the same zone at the new provider. The registrar keeps the registration and the billing relationship; only the delegation changes. The domain is the same, the owner is the same, and your existing records move across as data you copy yourself. Nothing about the registration record itself needs to change, which is why this is a delegation change and not a transfer.

People confuse the two because registrars and DNS hosts are often the same company. They are separate roles. The registrar holds the registration in the registry database and publishes the delegation, meaning the NS records for your zone in the parent. The DNS host runs the authoritative servers that answer queries for your zone. You can point the delegation at any authoritative servers you control or rent, and the registrar does not need to be the one answering queries.

Understand what actually changes when you move DNS hosting without changing registrar

The only record that matters at the parent is the delegation. The registry holds an NS RRset for your domain, and the registrar is the party allowed to submit changes to it. Everything else, the A, AAAA, CNAME, MX, TXT, SRV and CAA records, lives in the zone file on the authoritative servers. When you switch hosts, the parent delegation changes and the zone file is served by different machines. The records themselves should be identical on both sides during the overlap, which is what keeps the site online.

There is one subtlety that catches people: the NS records inside your zone file at the apex should match the delegation at the parent. If they disagree, some resolvers and some monitoring tools will complain, and zone transfers between secondary servers can behave inconsistently. Keep them in sync.

Export the existing zone before you touch anything

Start by getting the current zone as data. If your current host allows zone transfers, use dig with the AXFR type against the primary name server. You need the primary to permit the transfer from your source address, and many hosts restrict this, so expect it to fail and fall back to a manual export or a screenshot of the record list.

dig AXFR example.com @ns1.old-dns.example

; <<>> DiG 9.x <<>> AXFR example.com @ns1.old-dns.example
example.com.        3600  IN  SOA   ns1.old-dns.example. hostmaster.example.com. (
                              2024010101 7200 3600 1209600 3600 )
example.com.        3600  IN  NS    ns1.old-dns.example.
example.com.        3600  IN  NS    ns2.old-dns.example.
example.com.        3600  IN  A     192.0.2.10
www.example.com.    3600  IN  CNAME example.com.
example.com.        3600  IN  MX    10 mail.example.com.

If the transfer is refused, use dig +noall +answer per name you know about, and pull the rest from the control panel. Check the SOA serial, the refresh and retry values, and the negative caching TTL, because those affect how quickly changes propagate. Note the TTL on the NS records at the apex: a long TTL means a longer window where some resolvers still hold the old delegation, which is why you lower it well before the switch.

Build and verify the new zone while the old one still answers

Create the zone at the new provider and paste the records in. Do not change the delegation yet. Point a resolver at the new servers directly and query them, so you are testing the new zone in isolation rather than whatever the public resolvers currently believe.

dig @ns1.new-dns.example example.com SOA +short
dig @ns1.new-dns.example www.example.com A +short
dig @ns1.new-dns.example example.com MX +short

# compare against the live answer from the old host
dig example.com A +short

Compare the output field by field. The SOA should have the same names and sensible timers, the apex records should match, and any wildcard or CAA records should be present. If you use DNSSEC, this is the part that needs care: the DS record in the parent is tied to the key at the new host, so either you disable DNSSEC before the move and re-enable after, or you coordinate the DS change with the delegation change. Doing both at once is the usual source of a hard outage, so most people turn DNSSEC off, wait for the DS to be removed from the parent, move the delegation, then turn DNSSEC back on with the new keys.

Change the delegation at the registrar

In the registrar control panel, find the name server settings for the domain. Replace the old host names with the new ones. Some registrars accept host names that resolve to addresses; others require you to register the host objects first, meaning glue records with the IP addresses of the new name servers. If the new servers are inside your own zone, for example ns1.example.com, you need glue, because a resolver cannot look up the address of a server that is authoritative for the name it is trying to resolve.

After submitting, confirm the change at the registry by querying the parent directly. Query a root or TLD server for the delegation and look at the NS records in the authority section.

dig +norecurse +noall +authority example.com NS @a.gtld-servers.net

example.com.  172800  IN  NS  ns1.new-dns.example.
example.com.  172800  IN  NS  ns2.new-dns.example.

The TLD servers hold the delegation with their own TTL, typically a couple of days, so the change is not instant everywhere. During the overlap both old and new servers should answer identically. That is the whole reason you build the new zone first and leave the old one running: whichever delegation a resolver has cached, it gets the same answers.

Confirm propagation and retire the old host

Watch the delegation from several vantage points. Query a few public resolvers directly and check which set of name servers they return, then query those servers for a record you care about. If you have a monitoring service, point it at both name server sets and compare the answers. Keep the old zone up until the old delegation TTL has fully expired everywhere, which means at least the TTL value you saw at the parent, plus margin. Only then delete the zone at the old host, and only after you have confirmed the new servers answer for the apex, for a subdomain, and for the MX.

If something breaks, the rollback is the same operation in reverse: put the old name servers back at the registrar. That is why you keep the old zone intact rather than deleting it on day one, and why you lower the delegation TTL before you start.

Next, do a dry run on a domain you can afford to break, such as a staging name, and write down the exact steps you took in order. Then do the real move at a quiet hour, with the old host still answering, and keep the terminal open with the dig commands above ready to run against both name server sets. The mechanics are simple; the discipline of verifying before and after is what keeps the site online.

Related articles

Subscribe to our newsletter

Get the latest hosting tips, performance insights, and industry news.