When enabled on a private DNS zone's virtual network link, VMs in that VNet get A records created automatically, kept in step as their IPs change and removed when they are deleted. A VNet may autoregister into only one private zone.
Also called auto registration.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Autoregistration in context, with comparison tables and the common traps.
Terms in this definition
- Private DNS zone
A zone in Azure DNS for private records (A records, for example), linked to VNets. Because only 168.63.129.16 resolves it, clients on-premises must go through a DNS forwarder or Azure DNS Private Resolver.
- Virtual network link
Connects a private DNS zone to a VNet so the VNet can resolve names (a resolution-only link) or register records (with autoregistration on). Peering on its own provides neither.
- Virtual machines
Infrastructure-as-a-service compute giving complete control of the operating system, making it a fit for lift-and-shift moves and for software relying on OS-level pieces like COM.
- VNet
A private network belonging to a single subscription and region and covering all of that region's availability zones. A VM can only use a VNet located in the same region.
- Get
Key Vault permission on secrets that allows a single secret to be read; App Service Key Vault references need nothing beyond it.
Related terms
- Azure Private DNS
The part of Azure DNS that hosts private zones, giving name resolution within linked virtual networks without running your own DNS servers. It can also add records for VMs automatically through autoregistration.
- PTR record
DNS record used for reverse lookups, resolving an IP address back to a name. Private DNS zone autoregistration does not create these.
- Public DNS zone
Hosts a domain's internet-facing records in Azure DNS. It answers authoritatively only after the registrar delegates to the zone's four Azure name servers via NS records; autoregistration of VMs is not supported.
- Registration virtual network
VNet whose link to a private DNS zone has autoregistration turned on. A single zone may have many such VNets, yet each VNet registers in just one zone, with any further links limited to resolution.