Self-hostedDNS hostingCapabilities verified
UniFi Network
Migrate DNS zones to or from UniFi Network: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at UniFi. Free and read-only.
Access we need
- Credentials
- API key (X-API-Key) + controller URL or UniFi console ID (via api.ui.com)
- Permissions
- A UniFi API key acts with the role of the admin who created it; create it from an admin limited to network settings where possible. It can read and write static DNS entries.
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 UniFi 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
- auto
Record types
- A
- AAAA
- CNAME
- MX
- TXT
- SRV
Good to know
- Consoles usually sit on a private network; we refuse private addresses by design, so either use the console ID (reached through api.ui.com) or expose the console publicly over HTTPS.
- A publicly trusted TLS certificate is required when connecting directly: we never skip certificate verification, so the console's default self-signed certificate will not work.
- Records are one flat list per site (no zones); only A, AAAA and CNAME have a configurable TTL, and TXT values are limited to 255 characters without double quotes.