Study guide
2.2 Azure Private DNS Resolver & Hybrid Name Resolution
Designing and Implementing Microsoft Azure Networking Solutions AZ-700
Track your progress as you read
Finished sections get a check mark.
1 Introduction & AZ-700 Exam Overview
0.1 About the AZ-700 Exam: Format, Scoring & Skills Measured
2 Chapter 1: Azure Virtual Networks, Addressing & Subnet Architecture
1.1 VNet Planning, IP Addressing & Subnet Design 1.2 Virtual Network Peering & Global Peering 1.3 Azure NAT Gateway & Outbound Connectivity 1.4 Azure Virtual Network Manager (AVNM) & Network Groups 1.5 Public IP Addresses, Public IP Prefixes & Custom IP Prefixes (BYOIP)
3 Chapter 2: Azure Name Resolution & Core Routing
2.1 Azure DNS & Private DNS Zones 2.2 Azure Private DNS Resolver & Hybrid Name Resolution 2.3 System Routes & User-Defined Routes (UDR) 2.4 BGP & Custom Route Propagation 2.5 Azure Route Server & Dynamic NVA Route Exchange
4 Chapter 3: Hybrid Connectivity with Azure VPN Gateway
3.1 Azure VPN Gateway Architecture & SKUs 3.2 Site-to-Site (S2S) VPN & High Availability 3.3 Point-to-Site (P2S) VPN & Client Authentication 3.4 Azure Extended Network, Always On VPN & Azure Network Adapter
5 Chapter 4: Azure ExpressRoute & Virtual WAN
4.1 Azure ExpressRoute Architecture & Peering Models 4.2 ExpressRoute Routing, Resiliency & Global Reach 4.3 Azure Virtual WAN Architecture & Hub Routing 4.4 ExpressRoute BFD, Monitoring & Connection Troubleshooting
6 Chapter 5: Regional Load Balancing & Application Gateway
5.1 Azure Load Balancer Architecture & Rules 5.2 Azure Application Gateway Architecture & Routing 5.3 Web Application Firewall (WAF) on Application Gateway 5.4 Inbound NAT Rules, Port Forwarding & Health Probe Design
7 Chapter 6: Global Traffic Management & Azure Front Door
6.1 Azure Front Door Architecture & Routing 6.2 Azure Traffic Manager & DNS Load Balancing 6.3 Load Balancing Decision Matrix & Multi-Tier Design 6.4 Web Application Firewall on Azure Front Door
8 Chapter 7: Azure Private Link & Service Endpoints
7.1 Virtual Network Service Endpoints & Policies 7.2 Azure Private Endpoints & Private Link Architecture 7.3 Private Endpoint DNS Integration & Hybrid Resolution 7.4 Azure Private Link Service for Multi-Tenant Solutions
9 Chapter 8: Network Security Groups & Azure Bastion
8.1 Network Security Groups (NSGs) & Application Security Groups (ASGs) 8.2 Azure Bastion Architecture & Secure Remote Access 8.3 Azure Virtual Network Manager Security Admin Rules
10 Chapter 9: Azure Firewall & Security Policies
9.1 Azure Firewall Architecture & Rule Processing 9.2 Azure Firewall Manager & DDoS Protection
11 Chapter 10: Azure Network Observability & Troubleshooting
10.1 Network Watcher Diagnostic Tools 10.2 NSG Flow Logs, VNet Flow Logs & Traffic Analytics 10.3 Network Troubleshooting Scenarios & End-to-End Connectivity 10.4 Azure Monitor Network Insights & Defender for Cloud Network Posture
2.2 Azure Private DNS Resolver & Hybrid Name Resolution
Key Takeaways Explain This Topic AI
Azure Private DNS Resolver is a fully managed, cloud-native PaaS service that delivers bidirectional hybrid DNS resolution with 10,000 QPS per endpoint without requiring custom IaaS DNS VM forwarders.
Inbound Endpoints listen on a private IP within a dedicated delegated subnet, allowing on-premises DNS servers to forward queries into Azure Private DNS Zones.
Outbound Endpoints utilize DNS Forwarding Rulesets linked to VNets to conditionally forward queries originating in Azure out to on-premises or custom DNS servers.
Both Inbound and Outbound Endpoints require dedicated, non-overlapping subnets delegated to Microsoft.Network/dnsResolvers with a recommended minimum prefix size of /28.
Last updated: August 2026
Azure Private DNS Resolver & Hybrid Name Resolution
In hybrid cloud architectures connecting on-premises corporate datacenters to Azure via Site-to-Site VPN or ExpressRoute, bidirectional Domain Name System (DNS) resolution is an absolute operational requirement. On-premises workloads must seamlessly resolve Azure Private Endpoints and private services, while Azure workloads must resolve internal Active Directory domains and on-premises servers.
Historically, this required deploying, patching, and maintaining highly available pairs of IaaS virtual machine DNS forwarders (such as Windows Server DNS or BIND Linux VMs). Azure Private DNS Resolver replaces this operational burden with a fully managed, highly available, scalable PaaS offering.
The Hybrid DNS Dilemma & The PaaS Evolution
To understand why Azure Private DNS Resolver is transformative, consider the limitations of the traditional IaaS VM approach: +-----------------------------------------------------------------------------------------+
- | Legacy IaaS DNS Forwarder Architecture |
- | |
- | On-Premises DNS <=== S2S VPN / ExpressRoute ===> Hub VNet DNS VMs (IaaS) |
- | (Forwarder: *.azure) (Forwarder: 168.63.129.16) |
- | |
- | Pain Points: OS patching, clustering, single points of failure, custom VNet DNS IPs |
- +-----------------------------------------------------------------------------------------+
vs.
- +-----------------------------------------------------------------------------------------+
- | Modern Azure Private DNS Resolver (PaaS) |
- | |
- | On-Premises DNS <=== S2S VPN / ExpressRoute ===> Inbound Endpoint (Private IP) |
- | Outbound Endpoint + Rulesets |
- | |
- | Benefits: Zero VM maintenance, native AZ resiliency, 10,000 QPS/endpoint, PaaS SLA |
- +-----------------------------------------------------------------------------------------+
- Advantages of Azure Private DNS Resolver
Zero Infrastructure Management : No virtual machine patching, OS licensing, or availability set/zone configuration.
High Availability & High Throughput : Native multi-zone availability supporting up to 10,000 queries per second (QPS) per endpoint.
Native VNet DNS Preservation : VNets retain default Azure-provided DNS ( 168.63.129.16 ), avoiding manual custom DNS IP maintenance across hundreds of spoke VNets.
Architecture & Subnet Delegation Prerequisites
An Azure Private DNS Resolver is deployed within a Virtual Network (typically the Central Hub VNet in a Hub-and-Spoke topology). It requires dedicated subnets delegated to the Microsoft DNS resolver resource provider.
Subnet Requirements
Inbound Endpoint Subnet :
Must be delegated to Microsoft.Network/dnsResolvers .
Contains the static private IP address that listens for incoming DNS queries.
Minimum recommended subnet size: /28 (provides 16 IP addresses; minimum supported is /28 ).
Outbound Endpoint Subnet :
Must be delegated to Microsoft.Network/dnsResolvers .
Acts as the egress interface for queries sent from Azure to external/on-premises DNS servers.
Minimum recommended subnet size: /28 .
Subnet Isolation Rules :
Inbound and Outbound endpoints cannot share the same subnet .
The subnets cannot host any other workloads, VMs, or private endpoints.
Network Security Groups (NSGs) and User-Defined Routes (UDRs) attached to delegated resolver subnets must allow UDP/TCP port 53 traffic. // Azure Bicep: Dedicated Subnet Delegation for Private DNS Resolver
- resource inboundDnsSubnet 'Microsoft.Network/virtualNetworks/subnets@2023-05-01' = {
- name: 'snet-dns-inbound'
- parent: hubVnet
- properties: {
- addressPrefix: '10.0.10.0/28'
- delegations: [
- {
- name: 'dnsResolverDelegation'
- properties: {
- serviceName: 'Microsoft.Network/dnsResolvers'
- }
- }
- ]
- }
- }
- Inbound Endpoints: On-Premises to Azure Resolution
An Inbound Endpoint allows name resolution queries originating from outside Azure (on-premises datacenters, remote branches, or other cloud providers) to query Azure Private DNS Zones.
How Inbound Endpoints Work
The Inbound Endpoint allocates a private IP address within its delegated subnet (e.g., 10.0.10.4 ).
The endpoint listens on UDP and TCP port 53 for standard DNS requests.
When a query arrives over ExpressRoute or S2S VPN, the Inbound Endpoint forwards the query to the Azure platform resolver ( 168.63.129.16 ).
The Azure platform resolver queries all Azure Private DNS Zones linked to the resolver's VNet (such as privatelink.blob.core.windows.net or corp.internal ).
The resolved private IP address is returned back to the on-premises client.
On-Premises DNS Configuration
On the on-premises DNS servers (Windows Active Directory DNS or BIND), the administrator configures Conditional Forwarders :
- Forwarding Domain: privatelink.blob.core.windows.net (or *.azure.contoso.com )
- Master / Target IP: 10.0.10.4 (Inbound Endpoint IP)
- Outbound Endpoints & DNS Forwarding Rulesets: Azure to On-Premises Resolution
An Outbound Endpoint enables Azure VMs and workloads to conditionally resolve on-premises or third-party DNS domains without changing the VNet's default DNS server settings.
Core Components
Outbound Endpoint : The egress network interface in the resolver VNet that transmits forwarded queries to external IP destinations.
DNS Forwarding Ruleset : A management resource that groups one or more forwarding rules. The ruleset is attached to one or more Outbound Endpoints and then linked to target Virtual Networks.
Forwarding Rules : Individual conditional rules defined inside a Ruleset, consisting of:
Domain Name : The target domain suffix (e.g., onprem.contoso.com. or root . for catch-all).
Target DNS Servers : List of external IPv4/IPv6 addresses and ports (default: port 53).
Rule Priority : An integer between 100 and 1000 (lower numbers indicate higher priority).
Rule State : Enabled or Disabled .
Longest Domain Match Rule Evaluation
When a VM in a linked VNet issues a query, the DNS Forwarding Ruleset evaluates the domain matching using Longest Suffix Match :
If a VM queries server01.emea.corp.contoso.com :
- Rule 1: contoso.com (Priority 500) -> Target: 192.168.1.10
- Rule 2: corp.contoso.com (Priority 200) -> Target: 192.168.2.10
Result : Rule 2 matches because corp.contoso.com is a longer, more specific match than contoso.com , regardless of priority number. Priority numbers resolve ties when duplicate domain names exist.
Legacy IaaS Forwarders vs. Azure Private DNS Resolver
- Feature / Metric Legacy IaaS DNS Forwarder VMs Azure Private DNS Resolver (PaaS)
- Infrastructure Management OS patching, backup, AV, VM maintenance Fully managed PaaS by Microsoft
- High Availability Manual Availability Sets / Zones + Load Balancers Native Multi-Availability Zone redundancy
- Throughput / Scalability Limited by VM SKU compute and NIC limits Up to 10,000 QPS per endpoint
- VNet DNS Settings Spoke VNets must be set to custom VM IPs Spoke VNets remain on default 168.63.129.16
Private Link Integration Forwarders must relay to 168.63.129.16 Direct native integration with Private DNS Zones
- Subnet Delegation Standard VM subnets Requires Microsoft.Network/dnsResolvers
- Cost Model VM compute, OS disks, Load Balancer costs Endpoint hours + QPS query processing fees