Self-hostedDNS hostingCapabilities verified
MikroTik RouterOS
Migrate DNS zones to or from MikroTik RouterOS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at MikroTik. Free and read-only.
Access we need
- Credentials
- RouterOS REST API URL + username + password (HTTP Basic, RouterOS v7.1+)
- Permissions
- A user group with the read and rest-api policies for the preview; add the write policy to apply changes.
Runs on your own infrastructure.
We connect to its API over the internet, so the API endpoint must be reachable on a public address over HTTPS. We never connect to private or internal addresses.
What MikroTik supports
The same data the translation engine uses when it plans a migration.
- Create zones through the API
- List zones through the API
- Turn on DNSSEC through the API
- Apex CNAME (flattening)
- Apex ALIAS record
- Aliases to cloud resources
- CDN proxy on records
- Routing policies
- Minimum TTL
- 0s
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- NS
- SRV
MikroTik-only records
- MIKROTIK_FORWARDER
- MIKROTIK_FWD
- MIKROTIK_NXDOMAIN
These have no equivalent elsewhere and are flagged in every preview.
Good to know
- 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.