TL;DR
If you're moving domains and email from 1&1 or 1Blu to Hetzner, a few things can make life unpleasant:
- Nameserver changes sometimes take longer than expected
- A missing or inactive DNS zone can lead to NXDOMAIN errors
- Gmail may reject outgoing mail when SPF or DKIM isn't configured correctly
- Catch-all mailboxes across several domains may work differently at the new provider
Here's what happened to me, without the marketing fluff.
A note on accuracy: This is my migration experience from March 2026. Provider interfaces, product limitations, mail server names and transfer times can change. Check the actual values in your Hetzner account before modifying DNS.
Why move at all?
Before: Domains, DNS, email and webspace at 1&1/1Blu.
After: Domain management, DNS, email and hosting at Hetzner.
The attraction was better performance, a lower bill and a simpler setup. The downside was the migration itself.
Phase 1: Move the mail before touching DNS
imapsync is your friend
I used imapsync to copy mailboxes directly between the two IMAP servers.
An example of the command structure:
imapsync \
--host1 imap.1blu.de --user1 user@example.com \
--host2 mail.hetzner.de --user2 user@example.com \
--ssl1 --ssl2 \
--delete2duplicates \
--syncinternaldates
I've deliberately left passwords out of this example. Use a secure credential input method supported by your imapsync version instead of exposing passwords in a process command line or shell history.
Do at least two passes:
- A full initial copy, which can take hours.
- A final synchronisation shortly before or after the MX cutover.
A last pass covering only recent mail can save time, but be careful: limiting by message age can miss older messages moved or changed during the migration. Verify the actual mailbox contents.
Otherwise, mail delivered to the old provider during the transition can be missed.
Phase 2: Transfer the domain
At 1Blu I had to disable the transfer lock and request the authorisation code.
Then, in the Hetzner Console, I started the domain transfer and entered the code.
After that came the confirmation email and the wait.
My transfer took several days. That's an experience, not a guaranteed duration.
Phase 3: Prepare the DNS zone first
Before making nameserver changes, the destination DNS zone must exist and contain the records the domain needs.
Typical records include:
A @ WEB_SERVER_IP
A www WEB_SERVER_IP
MX @ YOUR_ACTUAL_MAIL_EXCHANGER
TXT @ "v=spf1 mx ~all"
Those are placeholders. Don't use the example MX or SPF records as a substitute for the provider's actual instructions. SPF must cover every authorised outbound mail service, and DKIM/DMARC should also be planned.
The Hetzner webhosting nameservers I recorded were:
ns1.your-server.de
ns2.second-ns.com
ns3.second-ns.de
Yes, “your-server.de” really was the hostname. It looks odd but isn't a typo. Still, use the authoritative nameservers shown for your particular service.
The nerve-racking bit: switching nameservers
Scenario A: The domain transfer is still running
If you can still change nameservers at the old registrar, it's tempting to point them at Hetzner early.
Don't do that until you've confirmed the destination DNS zone is active and correctly delegated.
Otherwise, you may end up with NXDOMAIN and a website and email address that appear to have vanished.
Scenario B: You changed them too early
A lookup might report:
nslookup -type=mx example.com
** server can't find example.com: NXDOMAIN
No website, no email. Excellent way to ruin a Friday evening.
Depending on the state of the transfer, the fix is to restore working delegation at the current registrar or get the destination zone activated. DNS caching means recovery might not be instant.
Phase 4: Gmail rejects outgoing mail
One error I encountered was:
550-5.7.26 Gmail requires all senders to authenticate with either SPF or DKIM.
550-5.7.26 DKIM = did not pass
550-5.7.26 SPF = did not pass
In my case the mail client was still sending through the old SMTP server, but the SPF configuration had already moved to the new service.
Fix 1: Update the SMTP server
Change the outgoing server in the iPhone Mail settings or in Thunderbird/Outlook, including the correct authentication and TLS settings.
Fix 2: Make SPF match reality
If you're still sending through the old service during the transition, SPF may need to authorise it temporarily.
Don't copy a random SPF include from a blog. Obtain the correct mechanisms from both providers, and make sure you have one valid SPF record, not several competing ones.
Fix 3: Enable DKIM
Generate or activate the DKIM selector in your mail hosting account and publish the corresponding DNS record.
Then check it with a DNS lookup and send test messages to an external mailbox.
SPF, DKIM and DMARC are related but different checks. One successful DNS lookup alone doesn't prove deliverability.
Bonus complication: catch-all for several domains
At 1Blu I had catch-all mail from several domains going into one mailbox.
My Hetzner package didn't offer the same arrangement in the way I wanted.
Possible workarounds:
- Forward catch-all mail from one domain to a mailbox on another.
- Create separate mailboxes and combine them in your mail client.
- Use a mail provider whose multi-domain setup matches your requirements.
Forwarding solves inbound delivery, but doesn't necessarily let you send as addresses from the forwarded domain. That's a separate configuration decision.
Migration checklist
- Run a full imapsync pass and keep an independent backup
- Request the authorisation code
- Prepare and verify the destination DNS zone
- Start the domain transfer
- Run a final IMAP delta synchronisation
- Publish the correct SPF, DKIM and DMARC records
- Update outgoing SMTP settings on every device
- Test receiving mail and sending to Gmail
- Only cancel the old hosting after a safe overlap period
Lessons learnt
- Nameserver changes are the dangerous part. Verify the destination zone first.
- DNS propagation and caching take time.
- Mail authentication matters. Gmail certainly notices.
- Check catch-all behaviour before choosing a hosting plan.
- Run imapsync more than once and compare mailbox contents.
The tools that helped were imapsync, nslookup, MXToolbox and the provider documentation.
Moving everything was annoying, but manageable. My biggest mistake was touching nameservers before I was certain the destination DNS zone was working.
After a few hours of debugging and several coffees, it all made sense. Mostly.