Self-hostedDNS hostingCapabilities verified
NetBird
Migrate DNS zones to or from NetBird: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at NetBird. Free and read-only.
Access we need
- Credentials
- Personal access token (Authorization: Token) + optional self-hosted management URL
- Permissions
- A service user whose role has DNS read permission for the preview and DNS create/update/delete to apply (Admin or Owner).
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 NetBird 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
Good to know
- NetBird custom zones are private DNS served only to peers in the zone's distribution groups; creating a zone needs at least one distribution group ID.
- Only A, AAAA and CNAME records are supported.
- Self-hosted management servers are often on private networks: we only connect if the API is exposed publicly over HTTPS, because private and internal addresses are refused by design.