DNS Management
The records that decide where your site and your mail go, and how to copy them before a move.
Read the DNS guideYou know what a transfer is. How to transfer a domain comes down to procedure: what to check before you start, how to get the authorisation code, what happens while you wait, and when the right move is to leave the domain alone.
A transfer changes who bills you and where you log in. It does not move your website and it does not move your email. If that distinction is still fuzzy, read the overview of how domains work first. Everything below assumes you have a domain somewhere, you can get into the account holding it, and you want it held somewhere else.
Nearly every failed transfer fails at the start, not in the middle. Ten minutes of checking saves a week of waiting.
Work through these in the account you are transferring away from. Each one can stop a transfer, and most fail quietly: the request is refused, or it never appears at all.
| Check | What it blocks | What to do |
|---|---|---|
| Registered less than 60 days ago | Everything. The transfer is refused outright. | Wait it out. You can still point the domain anywhere meanwhile. |
| Transferred in the last 60 days | Everything, for the same reason. | Check the transfer date, not the registration date. |
| Registrant name or email changed recently | Often triggers its own transfer lock. | Settle the contact details first, then start the clock. |
| Registrar lock is on | The code is accepted, then the transfer fails. | Unlock it immediately before you start. |
| Administrative contact email | The approval message, so the whole transfer. | Make sure it is a mailbox somebody reads today. |
| Domain privacy | At some registrars, the approval message and the code. | Turn it off for the move, then straight back on. |
| Expiry date | Nothing directly, but a lapse mid-move is expensive. | Renew first if it is close, then transfer. |
| Where the DNS records live | Nothing yet. It breaks the site later. | Copy every record down before anything changes. |
That last row catches people out. The transfer leaves your DNS alone, but if the records live in the old registrar's DNS and you later switch nameservers, they do not come with you. Read how DNS records work first.
Authorisation code, EPP code, auth code, transfer key: four names for one thing, a single-use password proving you control the domain. The new registrar cannot start without it.
It normally sits in the domain's settings, near the lock switch, behind a link called something like transfer out or get authorisation code. Some registrars show it on screen. Others send it to the administrative contact address, which is why that mailbox matters.
Three things to get right:
Some control panels hide the code behind a support ticket, a phone call or a retention offer. You are entitled to it. Ask support in writing for the authorisation code for a transfer out, decline the offer, repeat the request, and keep the ticket number.
If it is being refused rather than just being slow, ICANN runs a complaints process for blocked transfers. Knowing that exists tends to make the second ticket more productive.
Confirm the administrative contact is a mailbox you can open right now. Changing it later can restart a lock, and changing it mid-transfer is worse.
One switch in the domain settings. Leave it unlocked only while the transfer runs, then lock it again at the new registrar.
Copy it exactly, punctuation included. If it arrives by email, check the spam folder before deciding it was never sent.
You always begin at the gaining side, never the losing side. Enter the domain, paste the code and pay for the transfer term.
A confirmation goes to the administrative contact. Nothing moves until somebody clicks it, and an unapproved transfer eventually times out.
The old registrar gets several days to approve or object. If it does nothing, the transfer completes anyway. Do not start a second one while the first is pending.
Confirm the nameservers and DNS records are what you expect, put the registrar lock back on, turn privacy back on and set auto-renew.
The delay is deliberate. A domain is valuable and a transfer is hard to unpick, so the rules give the current registrar a fixed period to confirm the move is genuine. That window stops somebody who has briefly got into your account walking the name out the door.
You can sometimes shorten it. Many registrars offer an approve the transfer out button that releases the domain straight away instead of waiting for the clock. Where that button is not offered, there is no way to hurry the window, so plan on the better part of a week.
The site, the mail and the name itself are covered in the domains overview. The paperwork behind the name is not.
The order is fixed, and the reason is diagnostic. Both jobs take time to settle, so if you change both at once and the site or the mail stops, you cannot tell which one did it.
If mail runs on the domain, the mail records are the ones that punish a rushed job. See how a website migration works and how an email migration works before you move either.
A refused transfer nearly always has one of a handful of causes, and the error message rarely says which:
If it has simply stalled, check the order status at the new registrar before contacting anyone. More often than not, the window has simply not run out.
The honest answer is sometimes leave it alone:
Most transfers we are asked to run start the same way, with a business whose domain sits in an account nobody can log into. We work out what state the registration is in and say honestly whether it is worth moving.
If the name is somewhere you can no longer reach, start at the support centre or call 716-771-2536. Recovering access is a different job to transferring, and it comes first.
Ask their support in writing for the authorisation code for a transfer out. Registrars are required to release it to the registrant, and a retention offer is not a reason to withhold it. If it is still refused, ICANN runs a complaints process for blocked transfers.
Not by itself. Outages during a transfer come from somebody changing nameservers at the same time, or from DNS records that lived in the old registrar's panel and were never copied out.
No. The remaining term travels with the domain, and for common extensions such as .com and .net a transfer adds a further year on top. What a transfer cannot do is rescue a name that has already expired.
Check three things in order: whether the approval message is unread in the administrative contact mailbox, whether the domain is still locked at the old registrar, and whether the authorisation code was accepted. If all three are clear, the losing registrar's window has not run out yet.
Renew it first, then transfer once the new expiry date has settled. Starting a transfer close to expiry risks the registration lapsing part way through the move, and recovering an expired name costs far more than renewing one.
The records that decide where your site and your mail go, and how to copy them before a move.
Read the DNS guideWhat you turn off for the transfer, why it goes straight back on, and what it hides.
How domain privacy worksGrace, redemption and release, and why a name close to expiry is renewed first.
What happens at expiryBring the name over, keep the years you have already paid for, and have one place to log in.