Cloud platformDNS hostingCapabilities verified
Azure Private DNS
Migrate DNS zones to or from Azure Private DNS: what's supported, what access you need, and what changes for each destination.
See how a domain's records would land at Azure Private DNS. Free and read-only.
Access we need
- Credentials
- Service principal (client ID + secret)
- Permissions
- Reader on the resource group for the preview; Private DNS Zone Contributor to apply or create zones.
What Azure Private DNS 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
- PTR
Good to know
- Private zones only resolve inside Azure virtual networks linked to the zone, so changes can't be checked with public DNS lookups.
- Link the zone to your virtual networks after migrating; records auto-registered by VMs are skipped.
- Only A, AAAA, CNAME, MX, PTR, SRV and TXT records are supported; NS and CAA aren't.