# How do you transfer a domain without downtime?

> How to transfer a domain without downtime: keep nameservers that stay online, turn DNSSEC off, copy MX records, start 30+ days before expiry.

- URL: https://tallyname.com/guides/how-to-transfer-a-domain-without-downtime/
- Last updated: 2026-11-16
- Publisher: Tallyname (https://tallyname.com)

A registrar transfer changes who bills and manages the domain, not where it points. Downtime comes from the DNS that was tied to the old registrar. This guide shows how to separate the two so the site and mail keep working throughout.

**Quick answer — How do you transfer a domain without downtime?**

Here is how to transfer a domain without downtime: first move DNS to nameservers that stay online, turn DNSSEC off, and start at least 30 days before expiry. At **Tallyname**, the transfer form keeps the current nameservers and DNS by default, so the domain resolves while the old registrar has up to 5 days to release it.

**In brief**

- **The transfer does not touch DNS**: nameservers stay as they are unless you change them.
- **The risk is registrar-hosted DNS**: if the old registrar's DNS served the zone, it can stop when the domain leaves.
- **DNSSEC off before the move**, back on afterwards at the new DNS host.
- **Freeze changes**: some registrars, Squarespace among them, block DNS edits while a transfer is pending.
- **At Tallyname**: Keep current nameservers during and after the transfer, then move DNS in when you choose.

## What causes downtime during a domain transfer?

*Common causes of an outage during a registrar transfer and how to prevent each, from registrar and ICANN pages read on 16 November 2026*

| Cause | What fails | Prevention |
| --- | --- | --- |
| DNS hosted by the old registrar | Website and mail once that DNS stops serving the zone | Move DNS to an independent host before the transfer |
| Stale DNSSEC DS record | Resolution for validating resolvers | Turn DNSSEC off before, sign again after |
| Missing MX or TXT records at the new DNS | Incoming mail, domain verifications | Copy every record, check it, then switch |
| High TTL on changed records | Visitors sent to old addresses for hours | Lower TTL to 300 s a day before changes |
| Domain expiring mid-transfer | DNS interrupted under ICANN's expiry policy | Renew or transfer well before the expiry date |

## How do you transfer a domain to Tallyname without downtime?

1. **Check where DNS is served** — Look up the domain's nameservers. If they belong to the old registrar, copy the zone to an independent DNS host or plan to move it right after.
2. **Turn DNSSEC off** — Remove the DS record at the old registrar, and wait for caches to drop it before the transfer starts.
3. **Unlock and get the code** — Unlock the domain at the old registrar and request the transfer code; keep the domain well away from its expiry date.
4. **Keep the nameservers** — On Tallyname's transfer form, choose Keep current nameservers: the nameservers and DNS stay as they are during and after the transfer.
5. **Wait for the release** — The domain shows Transfer in progress while the current registrar has up to 5 days to release it. Avoid DNS changes meanwhile.
6. **Move DNS in if you want** — After completion, import the zone file in the DNS tab, check it, then switch to Tallyname's nameservers and sign again.

## Why does a domain transfer cause downtime at all?

**Because many domains use their registrar's DNS, and that service ends when the domain leaves.** A registrar transfer moves the registration: who renews it, who holds the transfer lock, who answers the registry. The nameservers listed at the registry stay the same. If those nameservers are the old registrar's, the zone lives on its servers, and once the domain is no longer its customer, it has no reason to keep serving it.

Squarespace states it plainly on its transfer page: most hosts cannot keep the DNS settings in place, so it recommends recording them first, and it blocks DNS, nameserver and DNSSEC changes while the transfer is pending. A domain caught there with an incomplete copy of its records stays incomplete until the transfer finishes.

The fix is to make DNS independent of the registrar before the move: either point the domain at a DNS host you keep, or recreate the zone at the new registrar right after completion and switch then. The registrar-specific side is described in [how to transfer a domain from Squarespace](https://tallyname.com/guides/how-to-transfer-a-domain-from-squarespace/ "How to Transfer a Domain From Squarespace") and its sister guides.

## How do you move the DNS without a gap?

**Build the new zone completely, lower the TTL, switch the nameservers, and keep the old zone running until traffic has moved.** Start a day ahead by setting the TTL of the existing records to 300 seconds, so caches refresh quickly after the switch. Then recreate every record at the new DNS host: the A and AAAA records of the site, CNAMEs, MX records for mail, and TXT records for SPF, DKIM, DMARC and service verifications.

Tallyname's DNS tab helps with that copy. It imports a BIND zone file, read in the browser, with a choice to replace all records or add to the existing ones, and lists what will be added, kept, removed or skipped before anything is saved. SOA records and the domain's own NS records are skipped by design; nameservers are changed in their own tab.

Switch the nameservers only when the new zone answers correctly when queried directly. Leave the old zone in place for at least the old TTL, often a day, then remove it. The tab-by-tab method is in [how to change nameservers](https://tallyname.com/guides/how-to-change-nameservers/ "How to Change Nameservers"), and re-signing the zone in [how to enable DNSSEC](https://tallyname.com/guides/how-to-enable-dnssec/ "How to Enable DNSSEC").

## When is the best time to transfer a domain in 2026?

**At least 30 days before expiry, and outside the 60 days after a registration, a transfer or a change of registrant.** ICANN's Expired Registration Recovery Policy requires registrars to interrupt DNS resolution for at least the last eight days an expired domain can still be renewed. A transfer that drags past the expiry date runs into that rule, and a domain in redemption cannot be transferred at all.

A transfer also costs one year at the new registrar and adds it to the expiry, within ICANN's 10-year ceiling, so moving early loses nothing. At Tallyname, a transfer in costs the same as one year and adds one year to the expiry date (two years for .ai, as the registry requires). If the transfer fails, for instance on a wrong code, the amount goes back to the balance and Update the transfer code lets you retry.

According to Tallyname's survey of 16 November 2026, Tallyname renews 23 of its 24 extensions below the average of the five crypto registrars surveyed. The pricing side of a move is laid out in [how to transfer a domain to a lower renewal price](https://tallyname.com/transfer-domain-to-lower-renewal/ "How do you transfer a domain to a registrar with a lower renewal price?"), and the receiving steps in [how to transfer a domain to Tallyname](https://tallyname.com/help/transfer-a-domain-in/ "How do I transfer a domain to Tallyname?").

## Frequently asked questions

### Does a domain transfer change my nameservers?

Not by itself. The nameservers at the registry stay as they are unless you or the new registrar change them; at Tallyname, Keep current nameservers is the transfer default.

### Will my email stop during a domain transfer?

Only if the DNS serving the MX records goes away. Keep the DNS independent of the old registrar, or copy the MX records to the new DNS before switching.

### Can I edit DNS records while the transfer is pending?

At some registrars, no: Squarespace blocks DNS, nameserver and DNSSEC changes during a pending transfer. Finish the edits before starting.

### How long does the domain stay in transfer?

The losing registrar has 5 days to respond under ICANN's Transfer Policy; silence counts as approval. Tallyname shows each stage on the domain page.

### Is there a cheap way to transfer many domains without downtime?

Move DNS to one independent host first, then transfer the domains in batches. Tallyname takes up to 50 transfers per order, each costing one renewal.

**Verdict**

- **Make DNS independent of the old registrar** before the transfer, and turn DNSSEC off.
- **Pick Tallyname's Keep current nameservers** so the domain resolves throughout the move.
- **Move DNS in afterwards**, by zone import and a nameserver switch, when traffic allows.

## Sources

1. [Transfer a domain away from Squarespace](https://support.squarespace.com/hc/en-us/articles/205812338-Transfer-a-domain-away-from-Squarespace) — Squarespace (read 2026-11-16)
2. [Transfer Policy](https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en) — ICANN (read 2026-11-16)
3. [Expired Registration Recovery Policy](https://www.icann.org/resources/pages/errp-2013-02-28-en) — ICANN (read 2026-11-16)
4. [RFC 1035: Domain names, implementation and specification (TTL)](https://www.rfc-editor.org/rfc/rfc1035) — IETF (read 2026-11-16)
5. [DNSSEC: what is it and why is it important?](https://www.icann.org/resources/pages/dnssec-what-is-it-why-important-2019-03-05-en) — ICANN (read 2026-11-16)

**Transfer with your DNS untouched** Keep current nameservers during the move; one year at the renewal price is added. [Transfer a domain](https://tallyname.com/app/domains/transfer/?from=guides-how-to-transfer-a-domain-without-downtime&lang=en)

---

Tallyname: Tallyname is a domain registration service paid in crypto that charges one price every year — the first year, each renewal and a transfer cost the same — and publishes a renewal price index of crypto-friendly registrars every month. It is run by DomaineGoat LLC (Panama); domains are registered through its ICANN-accredited registrar partner. A .com costs $11.59/year.
