Managed resolver inside a VNet that removes the need for DNS server VMs in hybrid setups. Its inbound and outbound endpoints each need their own subnet of at least /28 delegated to Microsoft.Network/dnsResolvers, and it can link only to a VNet in the same region.
Read more: Microsoft Learn
In the Ultra Transcenders books
Each book explains Azure DNS Private Resolver in context, with comparison tables and the common traps.
Terms in this definition
- 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.
- DNS
The system that turns names into addresses. In Azure, private endpoints depend on private DNS zones, which are queried through 168.63.129.16.
- 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.
- Subnet
A segment of a VNet's address space from which resources receive private IPs. Azure holds back five addresses per subnet (the first four and the last), leaving 251 usable in a /24 and three in a /29, the smallest IPv4 subnet.
- LEAST
Pass up to 254 expressions to this T-SQL function and it hands back whichever is smallest. Both Fabric Warehouse and SQL analytics endpoints support it.
- region
A provider-defined grouping in VCF Automation of Supervisors that all share one NSX Local Manager; tenants consume its compute, storage and memory via quotas set per region.
Related terms
- 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.