Skip to content
DNSmigrator

Openprovider Cloudflare DNS

Migrate DNS from Openprovider to Cloudflare.

9 record types move as they are. Nothing else needs special handling.

Free preview. Read-only. Nothing changes until you apply.

Openprovider to Cloudflare 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

A straightforward move.

Every record type Openprovider supports has a direct equivalent at Cloudflare.

A typical Openprovider zone at Cloudflare

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

Openprovider Cloudflare

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

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 Openprovider

    Connect Openprovider with read-only access (Contact person username and password with API access enabled).

  2. 2

    Connect Cloudflare

    Connect Cloudflare (Scoped API token). 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 Cloudflare

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

  5. 5

    Verify

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

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.

Questions

Will there be downtime moving from Openprovider to Cloudflare?

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

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