Transferring a Domain Name Without Breaking Your DNS: A 2026 Step-by-Step Guide

EXPERT GUIDE

Transferring a domain name is a five-minute form and a five-day waiting game, and most horror stories come from doing two jobs at once: moving the registration and moving the DNS. This guide separates them, explains the transfer locks and auth codes that ICANN’s rules actually impose, and gives you a cutover order that keeps your site and your email answering while the paperwork moves.

🔀 Three Different Things People Call Transferring a Domain

The word transfer covers three unrelated operations, and mixing them up is what creates downtime. The first is an inter-registrar transfer: the domain moves from one accredited registrar to another and the registry updates who is authoritative for the name. That is the only one of the three that triggers ICANN’s transfer machinery and its 60-day locks.

The second is a nameserver move, where the registration stays put and you edit the NS records so queries are answered by different servers: this is what most people actually want when they say they are changing hosts, and it is the operation that can take a site down. The third is a change of registrant — a new owner, company name or registrant email in the WHOIS record — handled by your current registrar, which drops a fresh 60-day lock that stops any transfer until it expires.

The practical consequence: if your goal is a new host, you probably do not need to transfer the domain at all. ICANN says you can switch hosting providers instead of registrars and avoid the lock altogether, simply by updating your nameservers or the hosting IP address.

✅ Pre-Flight Checks Before Transferring a Domain

Confirm who your registrar actually is. If billing has been handled by an agency or a reseller, look the name up in ICANN’s public lookup tool and read the registrar field: the request goes to the registrar of record, not to whoever sends you an invoice.

Make sure you can receive mail at the registrant address. The authorisation email goes to the transfer contact on file, and a dead mailbox stalls the move before it starts. Only update those details if you have more than 60 days to spare, since the update starts a lock.

Check the calendar and the expiry date. A registrar may deny a transfer inside 60 days of the initial registration, of a previous transfer, or of any change to the registrant name, organisation or email. An expired domain can still be transferred unless a previous period is unpaid, but a name in the Redemption Grace Period must be restored first.

🔑 Auth Codes, Locks and Forms: What the Transfer Rules Require

The mechanics of an inter-registrar transfer are standardised, which turns a support ticket into a checklist. You start at the gaining registrar — the one you want to move to, not the one you are leaving — and it normally asks for the auth code (also called an authorisation or EPP code), which proves the person asking is entitled to the name.

Your current registrar has five calendar days to supply it. Many generate it instantly in the control panel; five days is the outer limit when you must request it by ticket.

Both sides confirm intent. The gaining registrar sends a Form of Authorization to the transfer contact and the transfer is not processed if you do not respond; your existing registrar then verifies the request from its side. Expect two emails and answer both.

Denials are limited. A registrar may refuse for evidence of fraud, a dispute over who is authorising the transfer, an unpaid balance on a previous period, an express written objection from the holder, a lock status, or one of the 60-day windows, and must refuse if the name is subject to a UDRP proceeding, a court order, a URS suspension or a change-of-registrant lock.

📋 Export Your DNS Zone Before You Touch Anything

This step separates a calm move from a weekend of guesswork. Your live zone is not a single A record; it is a small database built up over years, and a new provider cannot invent what it cannot see.

Export or screenshot every record type in use: A and AAAA for the web server, CNAME for subdomains and hosted services, MX for mail routing, TXT for SPF, DKIM and DMARC, plus any SRV and CAA records. Domain-verification TXT records are the ones people forget, and losing one can take a paid service offline days later.

Treat anything you cannot explain as important, and export the zone to a text file stored off the server you are about to change, taken from the authoritative nameservers rather than a public cache.

⏱ Lower Your TTLs 24-48 Hours Before Transferring a Domain

A DNS record carries a time-to-live value — an unsigned number from zero to 2,147,483,647 seconds — telling resolvers how many seconds they may cache the answer, which is ample opportunity to configure something that outlives your patience.

The rule that matters for a move is arithmetic, not folklore: when you change a record, the old answer keeps being served from warm caches until its TTL expires. Change a record with an 86,400-second TTL and expect up to a day of split traffic, with some visitors reaching the new infrastructure and some the old one.

TTL	Worst-case caching after a change	When to use it
300 seconds	5 minutes	during a planned cutover window
3,600 seconds	1 hour	a sensible steady-state default
86,400 seconds	24 hours	records that genuinely never change

So: lower the TTL on the records you are about to edit, wait at least as long as the old value, and only then make the change. Leave the short TTL in place until the move is verified end to end.

📧 Keeping Email Alive Through the Move

Web traffic is forgiving — a visitor who lands on the old server for ten minutes still sees your site. Mail is not. If the MX records point at servers that no longer answer, messages bounce, and a bounced enquiry is a lost customer who rarely tells you why.

Mail transport does give you a margin: standards-track SMTP guidance puts the point at which a sender gives up at generally at least four to five days, so a short gap during a cutover usually clears itself once the records settle.

Three rules make the difference. Recreate MX and the SPF, DKIM and DMARC records at the new provider before the nameserver change. Test with real mail from an outside account, because your own outbound test can pass by luck of caching. And never assume a hosting plan includes mailboxes — many modern hosts deliberately do not, so keep mail with a dedicated provider and point MX at it permanently.

🛡 DNSSEC: The Silent Killer of Domain Moves

DNSSEC strengthens DNS authentication with digital signatures: the DNS data itself is signed by the zone owner, so a resolver can prove the answer it received is the one that was published. When it is switched on, a chain of key and delegation records links your zone up to the root, and that chain is also the failure mode. The parent zone holds a delegation record containing a hash of the key published by the child; if the two stop matching, validating resolvers cannot build the chain of trust and the name stops resolving for a growing share of the internet — while working perfectly for you.

The rule: if your provider signs your zone and the destination does not, remove the delegation record at the registry before or as part of the nameserver change; if both support it, re-publish the keys and update the delegation together.

🚦 The Cutover Order That Avoids Downtime

Order matters more than speed. This sequence keeps the site answering with one variable changing at a time.

1. Prepare the destination. Create the new zone with every record you exported, or stand up the new hosting and confirm it serves the site on a temporary address.

2. Lower the TTLs and wait. Drop the records you are about to change to 300 seconds, then wait out the previous TTL before touching anything.

3. Move the DNS, not the registration. Change the nameservers, or switch the A record to the new host. Verify against the authoritative servers, then against public resolvers.

4. Keep the old setup warm. Do not cancel the old hosting, and do not change MX in the same hour as the A record — anything still resolving to the old address should land on a working page.

5. Transfer the registration afterwards, on a different day. Once DNS is stable, start the inter-registrar transfer with the auth code, keeping the records identical. A registrar change should be invisible, so never combine it with a nameserver change.

And never let the registration lapse while you are busy with DNS: renew first, transfer second.

🔍 What to Verify in the 48 Hours After the Move

Verification is a checklist, not a feeling — and run it from outside your own network, because your laptop is the least representative resolver on the internet.

Check both layers of DNS. Query the authoritative nameservers to confirm they publish what you intended, then public resolvers to confirm propagation. A recursive trace shows the delegation path and exposes an unexpected stop.

Check the web response and the certificate. Confirm HTTPS answers with a valid certificate, and remember that certificates validated by DNS records need those records in the new zone or renewal fails silently weeks later.

Check mail in both directions. Send from an outside account to a mailbox on the domain and reply, then send from the domain to a third-party provider and read the headers: landing in spam proves the record changed without proving deliverability survived.

Watch for two full days before you relax, keeping the short TTLs until that window passes and raising them one change at a time.

💵 What a Transfer Costs, and When to Let the Registrar Handle It

A registrar-to-registrar transfer normally costs about a year’s renewal, and that year is added to your registration term — a renewal paid in advance rather than a surcharge. Registrars may set their own price; they may not refuse the transfer because you declined to pay it.

There is also a case for a registrar that will hold your hand: when the losing registrar stalls or keeps a lock in place, a support line that answers the phone turns a week of email into an afternoon. Network Solutions is one of the oldest names in the industry — founded in 1979, the first commercial .com registrar in 1993 — and now sits in the Newfold Digital group alongside Web.com, Bluehost, HostGator and Domain.com, with domains, hosting, email and SSL in one account centre. Cloud hosting is advertised from around $5.69 per month and WordPress hosting from about $7.99, with free migration and 24/7 phone and chat support. Two caveats: those are promotional prices with higher renewals on auto-renew, and a registrant contact change still starts a fresh 60-day lock.

❓ Frequently Asked Questions

🎯 The Short Version

Transferring a domain safely is mostly a matter of refusing to do two things at once: move the DNS when you change hosts, move the registration when you change registrars, and never in the same window.

Before you start: know your registrar of record, be able to receive mail at the registrant address, confirm you are outside every 60-day lock, and export the zone. During the move: lower the TTLs, recreate mail and validation records at the destination, and clear the DNSSEC delegation record if the destination does not sign. Afterwards: verify from authoritative servers and public resolvers, and test mail in both directions.

⭐ READ OUR FULL REVIEWFeatures, pricing and our honest verdict →