Skip to content
DNSmigrator

Cloudflare DNS Openprovider

Migrate DNS from Cloudflare to Openprovider.

9 record types move as they are. 6 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.

Cloudflare 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

Proxied records lose the CDN

Openprovider has no equivalent of Cloudflare's proxy. Proxied records move as plain records pointing at your origin, which exposes the origin IP. Put a CDN in front before cutting over if that matters.

Apex CNAMEs need a different shape

Openprovider doesn't allow a CNAME at the apex and has no alias record for external hostnames. These become static A/AAAA records, which don't follow the target if its IPs change.

TTLs below 900s are raised

Openprovider's minimum TTL is 900 seconds. Shorter TTLs are raised to 900s and shown as translated.

"Auto" TTLs get a real value

Cloudflare's automatic TTL has no equivalent, so those records get Openprovider's default of 3600s.

Domains registered at Cloudflare must transfer out

Cloudflare Registrar only allows Cloudflare's nameservers. If the domain is registered there, transfer it to another registrar before switching.

A typical Cloudflare zone at Openprovider

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

Cloudflare Openprovider

  • UnsupportedCNAME@

    Not migrated

    @ is a CNAME at the zone apex. Openprovider doesn't allow that, and app.example-host.net isn't a target it can alias.

  • 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.

  • TranslatedAmail

    203.0.113.25

    TTL 300s is outside the allowed range. Set to 900s.

  • ReviewAshop

    203.0.113.10

    TTL was "auto". Set to 3600s.

  • ExactCNAMEwww

    example.com.

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. 1

    Connect Cloudflare

    Connect Cloudflare with read-only access (Scoped API token).

  2. 2

    Connect Openprovider

    Connect Openprovider (Contact person username and password with API access enabled). 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 Openprovider

    We snapshot the Openprovider zone, write in batches, and leave Cloudflare untouched.

  5. 5

    Verify

    We query Openprovider'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 Cloudflare

  • Proxied (orange-cloud) records hide the origin IP. Moving them to another provider sends traffic straight to the origin.
  • Apex CNAMEs are flattened by Cloudflare. Other providers need an ALIAS record or static A/AAAA records instead.
  • Cloudflare Registrar only allows Cloudflare nameservers, so domains registered there must be transferred out first.

Access we need: Zone → DNS → Read for the preview, Zone → DNS → Edit to apply. Redirect and Worker route records also need Zone → Single Redirect → Edit and Zone → Workers Routes → Edit.

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 Cloudflare 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 Cloudflare?

No. We never write to Cloudflare. 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.

What happens to Cloudflare proxied records?

They move as ordinary records pointing at your origin server, because Openprovider can't proxy traffic. The preview lists every proxied record and the IP it would expose.

Related migrations

Ready to see your own zone?

Start a free preview