A registrar transfer changes who bills you and nothing else. The site and email keep working because the name servers stay pointed exactly where they were.

The fear is misplaced

Businesses put off consolidating registrars for years because they believe the transfer will take the site offline.

A registrar transfer moves the billing relationship and the administrative record, and that is all it moves.

The name server settings, which decide where the site and the email actually live, travel with the domain unchanged.

So the site keeps loading and the mail keeps arriving throughout, because nothing has been asked to point anywhere new.

What changes and what does not

The distinction people miss is between a registrar and a DNS host. The registrar is who you rent the name from and the DNS host is who answers questions about where things live, and they are frequently different companies.

The one case where it does break

Which is worth stating precisely.

If your current registrar is also providing the DNS, then moving away can end that service.

The records then stop being answered, and the site and email both stop, which is the outage everybody is afraid of.

The fix is to know which company answers your DNS before starting, and to recreate the records at the new place first if it is the registrar you are leaving.

Where DNS is at your host or a separate provider, none of this applies and the transfer is genuinely invisible.

That single question decides whether this is a five-minute job or one that needs preparation.

A worked example

A business had four domains at a registrar they wanted to leave and had delayed for three years.

Checking the name servers, three pointed at their hosting company and one pointed at the registrar itself.

The three transferred with no preparation and nothing changed for anybody.

For the fourth, they recorded every record, recreated them at the hosting company, changed the name servers, waited a week, and then transferred.

Nothing went down at any point.

The three years of delay had been about a risk that applied to one domain out of four.

Write the records down first

Which is the preparation for the case that needs it.

Before changing anything, take a copy of every DNS record: a screenshot and a typed list.

That includes the mail records, the sending and signing records, and any verification lines for services.

Those are the ones that get missed, since the site record is obvious and the others are not.

Rebuilding a set of mail records from memory afterwards is how a transfer turns into a week of email problems.

Keep that list even after the move, since it is the record of what your DNS should look like.

The sequence when DNS has to move

Separated so it does not get confused with the transfer itself.

Recreate every record at the new DNS provider while the old one is still live.

Lower the time to live on the name server settings if you can, then change them.

Wait a week and confirm the site, the mail, and any subdomain all still work.

Then, and only then, start the registrar transfer, which by that point touches nothing.

Two separate operations a week apart is considerably safer than one combined one.

Check the timing against the expiry

Which is the other thing that goes wrong.

A transfer takes five to seven days and adds a year to the existing expiry rather than resetting it.

Starting one in the fortnight before a domain expires is asking for it to lapse mid-transfer.

Renew first if the expiry is close, then transfer, and accept that the added year comes on top.

Also remember the sixty-day rules: no transfer within sixty days of registration, or of a change to the registrant.

Check both before scheduling anything, since either one will simply refuse the transfer with an unhelpful message.

Your registrar can tell you the relevant dates in a moment.

Watch for the approval email

Since a transfer stalls silently without it.

The confirmation goes to the registrant address on the domain, which may be an address nobody reads.

Update that address before starting, and watch for the message on the day.

An unapproved transfer simply expires after a period and has to be started again, which is where the week becomes three.

Check the spam folder too, since these messages are exactly the shape of the ones that get filtered automatically.

A transfer stalled by an unread approval is much the most common way a week becomes a month.

Nothing changes for your customers

Worth stating, since it is the reassurance that makes the decision easy.

Nobody outside the business can tell that a domain has changed registrar, because the address they type, the site they reach, and the addresses they email are all identical afterwards.

There is no announcement to make, no notice to publish, and no listing to update anywhere.

That is the difference between this and almost every other change discussed in the last month, most of which are visible to somebody.

A transfer done properly is invisible from every direction, including yours, apart from a different login and a different invoice.

The counter-case

Some transfers are genuinely awkward.

A registrar that makes leaving difficult, hides the authorisation code, or delays releasing it can turn a week into a month.

Country-specific domains occasionally have their own process that differs from the general one.

And a business with everything working, at a registrar it can access, has no particular reason to move at all.

Find out who answers your DNS first, write every record down, move DNS separately if it lives at the registrar, and transfer afterwards.

The sequence

  1. Check who answers your DNS.
  2. Write every record down.
  3. Move DNS first if it is at the registrar.
  4. Wait a week and confirm.
  5. Check the expiry is not close.
  6. Update the registrant address.
  7. Start the transfer and approve it.

Step one decides everything, since a transfer where DNS lives elsewhere is genuinely invisible and one where it lives at the registrar you are leaving is the only version that can take a site down.

Why you would consolidate at all is covered in two registrars and no reason.


Frequently asked questions

Will transferring take my site down?

No. A registrar transfer moves the billing relationship and the administrative record. The name server settings travel with the domain unchanged.

What is the difference between a registrar and a DNS host?

The registrar is who you rent the name from; the DNS host is who answers questions about where things live. They are frequently different companies.

When does it actually break?

When your current registrar is also providing the DNS, since moving away can end that service and the records stop being answered.

What should I do first?

Find out which company answers your DNS, and write down every record including mail, sending, signing, and verification lines.

How should I sequence it?

If DNS lives at the registrar, recreate the records elsewhere first, change the name servers, wait a week, then transfer. Two operations rather than one.

What about timing?

A transfer takes five to seven days, so do not start one close to expiry. Also check the sixty-day rules after registration or a registrant change.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Delayed a transfer because you feared downtime?

Check who answers your DNS. If it is not the registrar, the transfer is invisible.

Start a Conversation