Self-hostedDNS hostingCapabilities verified
OpenWrt
Migrate DNS zones to or from OpenWrt: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at OpenWrt. Free and read-only.
Access we need
- Credentials
- LuCI URL + username + password (LuCI JSON-RPC, luci-mod-rpc)
- Permissions
- LuCI logins are not scoped: the account can read and change the whole router configuration. We only touch dnsmasq host, CNAME, MX and SRV entries in /etc/config/dhcp.
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 OpenWrt 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
- 300s
Record types
- A
- AAAA
- CNAME
- MX
- SRV
Good to know
- Routers usually sit on a private network; we refuse private and internal addresses by design, so LuCI must be exposed publicly over HTTPS with a trusted certificate (ideally allow-listed to our egress IPs).
- dnsmasq local records have no per-record TTL, so every record is reported and written with a fixed TTL of 300 seconds.
- Records live in one flat list on the router, so a zone is simply the set of names under that domain; wildcard CNAMEs, null MX and null-target SRV records are not supported.