Skip to content
dnsmigrator

MikroTik RouterOS Cloudflare DNS

Migrate DNS from MikroTik to Cloudflare.

7 record types move as they are. 2 things work differently at Cloudflare, 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

TTLs below 60s are raised

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

A typical MikroTik zone at Cloudflare

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

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

How the move works

  1. 1

    Connect MikroTik

    Connect MikroTik with read-only access (RouterOS REST API URL + username + password (HTTP Basic, RouterOS v7.1+)).

  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 MikroTik 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 MikroTik

  • Routers usually sit on a private network; we refuse private addresses by design, so the REST API (www-ssl) is only reachable if you expose it publicly over HTTPS.
  • RouterOS has no zones: we group static entries by the domains you list (or the last two labels of each name). Regexp entries, dynamic entries and disabled entries are not imported, and match-subdomain / address-list settings are kept on existing entries but not migrated elsewhere.
  • MIKROTIK_FORWARDER records live in the virtual zone _forwarders.mikrotik and need RouterOS 7.17 or newer.

Access we need: A user group with the read and rest-api policies for the preview; add the write policy to apply changes.

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.

Questions

Will there be downtime moving from MikroTik 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 MikroTik?

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