Oracle Cloud DNS DNSimple
Migrate DNS from Oracle Cloud to DNSimple.
17 record types move as they are. 1 things work differently at DNSimple, 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
- PTR
- ALIAS
- NAPTR
- SSHFP
- TLSA
- HTTPS
- SVCB
- DS
- SPF
CERT, LOC, DNAME aren't available
A typical Oracle Cloud zone at DNSimple
Example records for example.com. Open any flagged row to read why it changed.
Oracle Cloud DNSimple
- 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 DNSimple | 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 Oracle Cloud
Connect Oracle Cloud with read-only access (API signing key (tenancy, user, fingerprint, key)).
- 2
Connect DNSimple
Connect DNSimple (Account API access 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 DNSimple
We snapshot the DNSimple zone, write in batches, and leave Oracle Cloud untouched.
- 5
Verify
We query DNSimple'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 Oracle Cloud
- Only public zones in the commercial realm (oraclecloud.com) are supported. Private resolver zones are skipped.
- Apex NS records are fixed by Oracle Cloud, and records marked as protected can't be changed.
- DNSSEC key-signing-key rollovers still need a manual promote step in Oracle Cloud after the DS record is updated at the registrar.
Access we need: An IAM policy with “read dns” for the preview; “manage dns” to apply.
Good to know about DNSimple
- Add the domain to your DNSimple account before migrating; zones can't be created through this connection.
- Apex NS and SOA records are managed by DNSimple and can't be changed.
- ALIAS, URL and some record types depend on your DNSimple plan.
Access we need: DNSimple tokens can't be limited to read-only. Use an account token (not a user token) so access is confined to one account.
Questions
Will there be downtime moving from Oracle Cloud to DNSimple?
Not if both providers serve the same answers during the switch. The records are copied to DNSimple 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 Oracle Cloud?
No. We never write to Oracle Cloud. 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 DNSimple and publish its new DS record. The cutover plan walks you through each step.
Ready to see your own zone?
Start a free preview