Realtime Register deSEC
Migrate DNS from Realtime Register to deSEC.
15 record types move as they are. 3 things work differently at deSEC, 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
- LOC
- NAPTR
- SSHFP
- TLSA
- URI
- CERT
Alias records are converted
URL isn't available
TTLs below 3600s are raised
A typical Realtime Register zone at deSEC
Example records for example.com. Open any flagged row to read why it changed.
Realtime Register deSEC
- TranslatedA@
192.0.2.70
TTL 300s is outside the allowed range. Set to 3600s.
- TranslatedAAAA@
2001:db8::70
TTL 300s is outside the allowed range. Set to 3600s.
- 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 deSEC | TTL | Details |
|---|---|---|---|---|---|
| Translated | A | @ |
| 1h | |
| Translated | AAAA | @ |
| 1h | |
| 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 Realtime Register
Connect Realtime Register with read-only access (API key (Authorization: ApiKey)).
- 2
Connect deSEC
Connect deSEC (API token). 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 deSEC
We snapshot the deSEC zone, write in batches, and leave Realtime Register untouched.
- 5
Verify
We query deSEC'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 Realtime Register
- Every change rewrites the zone's full custom record list in one request; records we don't manage (such as MBOXFW and HINFO) are sent back unchanged.
- Basic and Premium DNS are separate services with separate zones; the connection works with one of them at a time.
- Zones linked to a DNS template also receive the template's records, which are managed on the template, not per zone.
Access we need: An API user with VIEW_DNS_ZONE for the preview; CREATE_DNS_ZONE and UPDATE_DNS_ZONE to apply.
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.
Questions
Will there be downtime moving from Realtime Register to deSEC?
Not if both providers serve the same answers during the switch. The records are copied to deSEC 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 Realtime Register?
No. We never write to Realtime Register. 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 deSEC and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview