deSEC Openprovider
Migrate DNS from deSEC to Openprovider.
9 record types move as they are. 1 things work differently at Openprovider, and the preview shows exactly which of your records they affect.
Free preview. Read-only. Nothing changes until you apply.
deSEC to Openprovider DNS migration differences
Generated from the same provider capability data the migration engine uses.
Moves as-is
- A
- AAAA
- CNAME
- MX
- TXT
- SRV
- CAA
- TLSA
- SSHFP
NS, PTR, DS, HTTPS, SVCB, NAPTR, LOC, CERT, URI, DHCID, DNAME, OPENPGPKEY, RP, SMIMEA aren't available
A typical deSEC zone at Openprovider
Example records for example.com. Open any flagged row to read why it changed.
deSEC Openprovider
- TranslatedA@
192.0.2.70
TTL 300s is outside the allowed range. Set to 900s.
- TranslatedAAAA@
2001:db8::70
TTL 300s is outside the allowed range. Set to 900s.
- 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 Openprovider | TTL | Details |
|---|---|---|---|---|---|
| Translated | A | @ |
| 15m | |
| Translated | AAAA | @ |
| 15m | |
| Exact | MX | @ |
| 1h | |
| Exact | TXT | @ |
| 1h | |
| Exact | CAA | @ |
| 1h | |
| Exact | TXT | _dmarc |
| 1h | |
| Exact | SRV | _sip._tls |
| 1h | |
| Exact | CNAME | www |
| 1h |
Set up the connections
Use the provider-specific credential guides before you preview, then keep the migration checklist beside the cutover plan.
How the move works
- 1
Connect deSEC
Connect deSEC with read-only access (API token).
- 2
Connect Openprovider
Connect Openprovider (Contact person username and password with API access enabled). 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 Openprovider
We snapshot the Openprovider zone, write in batches, and leave deSEC untouched.
- 5
Verify
We query Openprovider'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 Openprovider
- Openprovider only accepts TTLs of 900, 3600, 10800, 21600, 43200 and 86400 seconds; other TTLs are rounded up to the next accepted value.
- Apex NS and SOA records are managed by Openprovider. NS records can't be added for subdomains and a CNAME can't sit at the zone apex (no ALIAS/ANAME).
- Null MX records (target ".") aren't supported. Legacy SPF-type records can be read and removed but not created; use TXT.
- Sectigo Premium DNS zones aren't listed or changed through this connection.
- Zones on Openprovider nameservers are signed automatically. For domains on other nameservers, Openprovider registers DNSSEC from the DNSKEY public key, not the DS digest.
- Identical API calls are limited to 300 per 5 minutes and failed logins to 100 per hour; going over can block the contact's API access until it's unblocked in the control panel.
Access we need: Openprovider API access is switched on per contact person and uses that contact's login; it can't be limited to read-only or to DNS only. Create a dedicated contact person for DNSMigrator and turn its API access off when you're done.
Questions
Will there be downtime moving from deSEC to Openprovider?
Not if both providers serve the same answers during the switch. The records are copied to Openprovider 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 Openprovider and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?