Exoscale DNS Bunny DNS

Migrate DNS from Exoscale to Bunny.

8 record types move as they are. 2 things work differently at Bunny, and the preview shows exactly which of your records they affect.

Free preview. Read-only. Nothing changes until you apply.

What works differently

Generated from the same provider capability data the migration engine uses.

Moves as-is

A
AAAA
CNAME
MX
TXT
NS
SRV
CAA

Alias records are converted

Exoscale alias records become CNAMEs at Bunny. At the apex, Bunny flattens them automatically.

SSHFP, NAPTR aren't available

Bunny can't store SSHFP, NAPTR records through its API. They're marked Unsupported with the reason, never dropped silently.

A typical Exoscale zone at Bunny

Example records for example.com. Open any flagged row to read why it changed.

Exoscale Bunny

ExactA@
192.0.2.70
ExactAAAA@
2001:db8::70
ExactMX@
10 mx1.mail.example.net. +1
ExactTXT@
"v=spf1 include:_spf.example.net -all"
ExactCAA@
0 issue "letsencrypt.org"
ExactTXT_dmarc
"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"
ExactSRV_sip._tls
100 1 443 sip.example.net.
ExactCNAMEwww
example.com.

How each record at Exoscale DNS translates to Bunny DNS
Status	Type	Name	At Bunny	TTL
Exact	A	@	192.0.2.70	5m
Exact	AAAA	@	2001:db8::70	5m
Exact	MX	@	10 mx1.mail.example.net. 20 mx2.mail.example.net.	1h
Exact	TXT	@	"v=spf1 include:_spf.example.net -all"	1h
Exact	CAA	@	0 issue "letsencrypt.org"	1h
Exact	TXT	_dmarc	"v=DMARC1; p=reject; rua=mailto:dmarc@example.com"	1h
Exact	SRV	_sip._tls	100 1 443 sip.example.net.	1h
Exact	CNAME	www	example.com.	1h

How the move works

1
Connect Exoscale
Connect Exoscale with read-only access (IAM API key + secret).
2
Connect Bunny
Connect Bunny (Account API key). Write access is only used when you apply.
3
Review the preview
Check every record marked Review or Unsupported. Each one explains what changes and why.
4
Apply to Bunny
We snapshot the Bunny zone, write in batches, and leave Exoscale untouched.
5
Verify
We query Bunny's own nameservers for every record and compare the answers before you switch.
6
Switch nameservers
Lower TTLs a day or two ahead, remove any DS record if DNSSEC is on, then point the domain at the new nameservers at your registrar.

Good to know about Exoscale

Exoscale DNS needs an active DNS subscription on the organization before zones can be created.
PTR and TLSA records aren't supported, and SRV records can't have an empty target.
Apex NS records are fixed by Exoscale and can't be changed.

Access we need: An IAM role limited to the dns service: read operations for the preview; all dns operations to apply.

Good to know about Bunny

Pull Zone, Script and Flatten records, and disabled records, aren't migrated. Redirect records are read as URL redirects to recreate by hand.
Records that use smart routing (latency or geolocation) or CDN acceleration are flagged and never changed by us.
An apex CNAME is flattened by Bunny, so it can point at any hostname.

Access we need: The account API key has full access. There is no read-only key, so rotate it after the migration.

Questions

Will there be downtime moving from Exoscale to Bunny?

Not if both providers serve the same answers during the switch. The records are copied to Bunny and verified before you change nameservers, so resolvers get the same answer from either side while caches expire.

Do I have to delete anything at Exoscale?

No. We never write to Exoscale. Keep the old zone for a week after cutover so you can switch back instantly if anything looks wrong.

What about DNSSEC?

If DNSSEC is on, remove the DS record at your registrar and wait for it to expire before switching nameservers. Then enable DNSSEC at Bunny and publish its new DS record. The cutover plan walks you through each step.

Ready to see your own zone?

Start a free preview