Skip to content
dnsmigrator

DigitalOcean DNS Oracle Cloud DNS

Migrate DNS from DigitalOcean to Oracle Cloud.

8 record types move as they are. 1 things work differently at Oracle Cloud, 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

TTLs below 60s are raised

Oracle Cloud's minimum TTL is 60 seconds. Shorter TTLs are raised to 60s and shown as translated.

A typical DigitalOcean zone at Oracle Cloud

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

DigitalOcean Oracle Cloud

  • 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 the move works

  1. 1

    Connect DigitalOcean

    Connect DigitalOcean with read-only access (Personal access token (custom scopes)).

  2. 2

    Connect Oracle Cloud

    Connect Oracle Cloud (API signing key (tenancy, user, fingerprint, key)). Write access is only used when you apply.

  3. 3

    Review the preview

    Check every record marked Review or Unsupported. Each one explains what changes and why.

  4. 4

    Apply to Oracle Cloud

    We snapshot the Oracle Cloud zone, write in batches, and leave DigitalOcean untouched.

  5. 5

    Verify

    We query Oracle Cloud's own nameservers for every record and compare the answers before you switch.

  6. 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 DigitalOcean

  • DigitalOcean nameservers don't support DNSSEC, so turn DNSSEC off at the registrar before switching to them.
  • TXT records are limited to roughly 500 characters in total and can't contain backslashes.
  • CAA records can't use a bare ";" value or CA parameters such as "letsencrypt.org; accounturi=…".

Access we need: domain:read for the preview; domain:read, domain:create, domain:update and domain:delete to apply.

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.

Questions

Will there be downtime moving from DigitalOcean to Oracle Cloud?

Not if both providers serve the same answers during the switch. The records are copied to Oracle Cloud 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 DigitalOcean?

No. We never write to DigitalOcean. 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 Oracle Cloud and publish its new DS record. The cutover plan walks you through each step.

Related migrations

Ready to see your own zone?

Start a free preview