deSEC Infomaniak DNS
Migrate DNS from deSEC to Infomaniak.
13 record types move as they are. 1 things work differently at Infomaniak, 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
- DS
- TLSA
- SSHFP
- DNAME
- SMIMEA
PTR, HTTPS, SVCB, NAPTR, LOC, CERT, URI, DHCID, OPENPGPKEY, RP aren't available
A typical deSEC zone at Infomaniak
Example records for example.com. Open any flagged row to read why it changed.
deSEC Infomaniak
- 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.
| Status | Type | Name | At Infomaniak | TTL | Details |
|---|---|---|---|---|---|
| Exact | A | @ |
| 5m | |
| Exact | AAAA | @ |
| 5m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
How the move works
- 1
Connect deSEC
Connect deSEC with read-only access (API token).
- 2
Connect Infomaniak
Connect Infomaniak (API token (OAuth2 Bearer) with scopes). 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 Infomaniak
We snapshot the Infomaniak zone, write in batches, and leave deSEC untouched.
- 5
Verify
We query Infomaniak'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 deSEC
- The minimum TTL is 3600 seconds for most domains (deSEC sets it per domain) and the maximum is 86400.
- ALIAS/ANAME records and apex CNAMEs aren't supported; use A/AAAA or HTTPS records at the apex.
- Every zone is DNSSEC-signed automatically. Give the DS records to your registrar to complete the chain.
Access we need: Any token can read all RRsets. Applying needs write permission on the RRsets (token policies can restrict it); creating zones needs perm_create_domain.
Good to know about Infomaniak
- The API is limited to 60 requests per minute, so large zones apply slowly (one request per record value).
- TTLs must be between 60 and 86400 seconds.
- PTR records can be read but not created through the API.
Access we need: A token with domain:read and dns:read for the preview; dns:write to apply (domain:write only to toggle DNSSEC).
Questions
Will there be downtime moving from deSEC to Infomaniak?
Not if both providers serve the same answers during the switch. The records are copied to Infomaniak 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 deSEC?
No. We never write to deSEC. 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 Infomaniak and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview