Moving a domain to a new registrar is routine - until something goes wrong. Then your website shows an error page, emails bounce, and clients wonder if you're still in business.
Most domain transfer problems are avoidable. Here's what actually matters.
Why Domain Transfers Go Wrong
DNS Gets Lost in Translation
Your domain has DNS records that point to your website, email provider, and various services. During a transfer, these records need to move too - but they don't copy automatically.
If you forget to recreate them at the new registrar, or get a value wrong, services stop working.
Email Is Especially Fragile
Email configuration is complex: MX records, SPF, DKIM, DMARC. Miss one record and emails fail. Unlike a broken website (which visitors notice immediately), broken email fails silently. You don't know what you're not receiving.
Timing Matters
DNS changes don't propagate instantly. Old values are cached for hours or days based on TTL settings. Change nameservers at the wrong time and some clients see your old configuration while others see the new one.
Domain transfers are high-stakes. A mistake can take your site offline and break email for days. If your business depends on being reachable, I can handle the transfer for you.
The Steps That Matter
Document Everything First
Before touching anything, record all your current DNS records. Every A record, CNAME, MX record, TXT record. Screenshot or export the entire zone. You'll need this to recreate the configuration exactly.
Set Up the Destination Before Moving
Create your DNS zone at the new registrar with all records in place before you start the transfer. Don't point to it yet - just have it ready.
Lower TTL Values in Advance
Two to three days before the transfer, lower TTL on critical records to 5 minutes. This means DNS changes propagate quickly when you eventually switch.
Doing this on the day of the transfer doesn't help - old values are already cached.
Respond to Confirmation Emails
Both registrars send confirmation emails during transfer. Ignoring them delays the transfer by 5+ days. Respond promptly.
Test Everything After
Once complete: test your website, test email (both sending and receiving), check subdomains, verify SSL certificates. Don't assume it worked - verify.
Common Problems
Website Shows Error Page
A records or CNAME records weren't copied correctly, or nameservers changed before DNS was set up at the new registrar.
Email Stopped Working
MX records missing or incorrect. SPF record not updated. This is the most common issue with transfers.
Transfer Rejected
Domain is locked (unlock it first). Domain was registered or transferred within the last 60 days (wait). Auth code expired (request a new one).
Partial Outage
Some users see the site, others don't. This is DNS propagation in progress. With proper TTL lowering it resolves in minutes; without it, can take 24-48 hours.
Had a transfer go wrong? I can audit your DNS configuration and fix whatever's broken. Get emergency support.
.uk Domains Are Different
.uk domains (including .co.uk) don't use the standard auth code transfer process. Instead, they use IPS tags managed by Nominet. The process is faster (usually completes in hours) but works differently.
If you're transferring a .uk domain and your current registrar is being unhelpful, you can contact Nominet directly - though it's easier with professional help.
When to Handle It Yourself vs Get Help
DIY Is Reasonable If:
- You understand DNS and have done transfers before
- Your configuration is simple (website and basic email)
- You have time to troubleshoot if something goes wrong
- Brief downtime wouldn't significantly impact your business
Get Help If:
- You're not confident with DNS
- You use multiple services that send email from your domain
- You can't afford downtime
- The domain is business-critical
I handle domain transfers regularly. I know the registrar quirks, the common pitfalls, and how to test properly before going live.