Study guide

10.4 Hybrid Name Resolution with Azure DNS Private Resolver

Administering Windows Server Hybrid Core Infrastructure AZ-800

Track your progress as you read

Finished sections get a check mark.

1 Introduction & Exam Overview

About Exam AZ-800: Format, Scoring & the September 2026 Retirement

2 Chapter 1: Active Directory Domain Services Architecture & Deployment

1.1 Deploying & Managing Domain Controllers On-Premises 1.2 Domain Controllers in Azure IaaS & Virtualized DC Cloning 1.3 Read-Only Domain Controllers (RODCs) & Password Replication Policies 1.4 Flexible Single Master Operation (FSMO) Roles & Troubleshooting 1.5 Active Directory Sites, Subnets & Site Link Topology 1.6 AD DS Replication: Topology Generation, Convergence & Diagnostics 1.7 Forest and Domain Trust Relationships

3 Chapter 2: AD DS Security Principals, Service Accounts & Domain Join

2.1 Managing Users, Groups & Objects in Multi-Domain and Multi-Forest Environments 2.2 Service Account Types & Group Managed Service Accounts (gMSA) 2.3 Joining Windows Server to AD DS, Microsoft Entra Domain Services & Microsoft Entra ID 2.4 Creating & Managing Users, Groups and Organizational Units at Scale

4 Chapter 3: Hybrid Identity & Microsoft Entra Integration

3.1 Microsoft Entra Connect Sync Architecture, Installation & Filtering 3.2 SourceAnchor, Synchronization Rules & Microsoft Entra Connect Health 3.3 Microsoft Entra Cloud Sync & Disconnected Multi-Forest Topologies 3.4 Hybrid Authentication Methods & Staged Rollout 3.5 Microsoft Entra Domain Services 3.6 Integrating Microsoft Entra ID, AD DS & Entra Domain Services: Choosing an Architecture

5 Chapter 4: Group Policy in AD DS and Hybrid Environments

4.1 Group Policy Architecture & Processing Order (LSDOU) 4.2 Group Policy Filtering, Loopback Processing & Client-Side Extensions 4.3 Group Policy Preferences, Item-Level Targeting & Central Store 4.4 Group Policy in Microsoft Entra Domain Services & Fine-Grained Password Policies

6 Chapter 5: Remote Server Management in Hybrid Environments

5.1 Windows Admin Center (WAC) Deployment On-Premises and in Azure 5.2 PowerShell Remoting, WinRM & the Kerberos Double-Hop Problem 5.3 Just Enough Administration (JEA) for Constrained PowerShell Endpoints 5.4 OpenSSH on Windows Server & PowerShell Remoting over SSH 5.5 Secure RDP Access, Remote Desktop Gateway & Azure Bastion

7 Chapter 6: Hybrid Management with Azure Arc and Azure Services

6.1 Azure Arc-Enabled Servers Architecture & Onboarding 6.2 Azure Machine Configuration & VM Extensions on Arc Servers 6.3 Azure Update Manager: Assessment, Maintenance Configurations & Dynamic Scoping 6.4 Azure Automation for Hybrid Workloads: Runbooks & Hybrid Runbook Workers

8 Chapter 7: Hyper-V Virtualization & Virtual Machine Configuration

7.1 Hyper-V Type 1 Architecture, Installation & Hardware Prerequisites 7.2 VM Generations, Secure Boot, vTPM, Enhanced Session Mode & Direct VM Access 7.3 Compute, Dynamic Memory & Hardware Acceleration 7.4 VM Resource Controls, CPU Groups & Host Compute Partitioning 7.5 Hyper-V Virtual Hard Disks & Checkpoint Management 7.6 Hyper-V Virtual Switches, NIC Teaming & Switch Embedded Teaming (SET) 7.7 Integration Services, Guest Components & Time Synchronization

9 Chapter 8: Hyper-V High Availability, Security & Containers

8.1 Hyper-V Failover Clustering & Cluster Shared Volumes (CSV) 8.2 Hyper-V Replica & Azure Site Recovery (ASR) 8.3 Guarded Fabric & Shielded Virtual Machines 8.4 Windows Server Container Hosts, Isolation Models & Images 8.5 Managing Container Instances & Linux Containers with WSL 8.6 Windows Container Networking & AKS Enabled by Azure Arc 8.7 Managing Container Images, Tags & Azure Container Registry

10 Chapter 9: Azure IaaS Virtual Machine Administration

9.1 Azure VM Sizing, Series Selection & Managed Disk Tiers 9.2 Azure VM Host Caching, Disk Bursting, Ephemeral OS Disks & Disk Operations 9.3 Azure VM High Availability: Availability Sets, Zones & Proximity Placement Groups 9.4 Virtual Machine Scale Sets, Autoscale & Azure Dedicated Hosts 9.5 Azure VM Networking, NSGs & Connectivity

11 Chapter 10: Hybrid DNS Infrastructure & Name Resolution

10.1 Active Directory-Integrated DNS Architecture, Dynamic Updates & Zone Types 10.2 DNS Records, Aging & Scavenging and the GlobalNames Zone 10.3 DNS Forwarding, Conditional Forwarding & Azure DNS Zone Integration 10.4 Hybrid Name Resolution with Azure DNS Private Resolver 10.5 Windows Server DNS Policies & DNSSEC

12 Chapter 11: IP Addressing, DHCP & IPAM Management

11.1 DHCP Server Role, the DORA Lifecycle & Active Directory Authorization 11.2 DHCP Scopes, Option Hierarchy, Reservations & Relay Agents 11.3 DHCP High Availability & Failover Configurations 11.4 IP Address Management (IPAM) Deployment & Auditing 11.5 Resolving IP Address Issues in Hybrid Environments

13 Chapter 12: Hybrid Network Connectivity, Remote Access & Private Access

12.1 Remote Access Role, VPN Protocols & Site-to-Site VPN to Azure 12.2 Network Policy and Access Services (NPAS), RADIUS & Policy Processing 12.3 Azure Network Adapter & Azure Extended Network 12.4 Web Application Proxy & Microsoft Entra Application Proxy 12.5 Microsoft Entra Private Access & Global Secure Access 12.6 Azure Relay & Hybrid Connections

14 Chapter 13: File Services, DFS, SMB & Azure File Sync

13.1 Windows Server File Share Access, NTFS Permissions & Access-Based Enumeration 13.2 File Server Resource Manager: Quotas, File Screens & Storage Reports 13.3 DFS Namespaces (DFS-N) & DFS Replication (DFS-R) 13.4 BranchCache: Distributed Cache and Hosted Cache Modes 13.5 Modern SMB Protocols, SMB Multichannel & SMB over QUIC 13.6 Azure File Shares, Tiers & Hybrid Permissions 13.7 Azure File Sync, Cloud Tiering & Monitoring 13.8 Migrating DFS Namespaces & DFS Replication to Azure File Sync

15 Chapter 14: Windows Server Storage Infrastructure & High Availability

14.1 Disk Partitioning, Volumes & Enterprise File Systems (NTFS vs ReFS) 14.2 Data Deduplication Architecture, Usage Types & Management 14.3 Storage Spaces & Storage Spaces Direct (S2D) 14.4 Storage Replica & Storage Quality of Service 14.5 iSCSI Target Server, IQNs, CHAP Authentication & Multipath I/O

10.4 Hybrid Name Resolution with Azure DNS Private Resolver

Key Takeaways Explain This Topic AI

Azure Private DNS zones depend on the link-local platform address 168.63.129.16, which cannot be reached from on-premises, so a bridge component is always required.

An Azure DNS Private Resolver inbound endpoint takes a private IP inside the virtual network and receives queries forwarded from on-premises Windows Server conditional forwarders.

An outbound endpoint plus a DNS forwarding ruleset sends queries from Azure virtual networks back to on-premises domain controllers for corporate zones such as corp.contoso.com.

Forwarding rulesets are linked to virtual networks and evaluated by rule priority, so the most specific domain suffix must carry the winning priority.

The Private Resolver is a managed PaaS service with built-in high availability, removing the need to build, patch, and cluster custom IaaS DNS forwarder VMs.

Last updated: August 2026

  • Hybrid Name Resolution with Azure DNS Private Resolver
  • 1. Hybrid DNS Resolution Challenges & The Special VIP (168.63.129.16)

In Microsoft Azure, default DNS resolution inside Virtual Networks is handled by the Azure wire server virtual IP: 168.63.129.16 . +-----------------------------------------------------------------------------+

  • | THE HYBRID DNS RESOLUTION ROUTING DILEMMA |
  • | |
  • | [ON-PREMISES NETWORK] [AZURE CLOUD VNET] |
  • | +-----------------------+ +------------------------+ |
  • | | On-Premises DNS | | Azure Default Resolver | |
  • | | (10.0.1.10) | | 168.63.129.16 (VIP) | |
  • | +-----------------------+ +------------------------+ |
  • | | | |
  • | | =====[ ExpressRoute / S2S VPN Tunnel ]========= |
  • | | | |
  • | x (CANNOT ROUTE) x |
  • | +---> 168.63.129.16 is a non-routable link-local | |
  • | IP address unreachable from on-premises. | |
  • +-----------------------------------------------------------------------------+

The Two Hybrid DNS Dilemmas:

On-Premises to Azure Resolution: When on-premises servers attempt to resolve Azure Private Endpoints ( mysqldb.privatelink.database.windows.net ), they cannot forward queries to 168.63.129.16 because that IP address is a link-local virtual IP reachable only from within the local Azure VNet host hypervisor.

Azure to On-Premises Resolution: If an Azure VNet's DNS settings are changed from "Default (Azure-provided)" to "Custom" (pointing to on-premises DC IP 10.0.1.10 ), Azure VMs can resolve on-premises records, but they lose native resolution for Azure Private DNS zones , breaking Private Endpoint connectivity for Azure Storage, Azure SQL, and Azure Key Vault.

2. Azure DNS Private Resolver Architecture

The Azure DNS Private Resolver is a fully managed, cloud-native PaaS service that bridges Azure Virtual Networks with on-premises DNS infrastructure without requiring custom virtual machines. +-----------------------------------------------------------------------------+

  • | AZURE DNS PRIVATE RESOLVER FULL TOPOLOGY |
  • | |
  • | [ON-PREMISES DATACENTER] [AZURE CLOUD INFRASTRUCTURE]|
  • | +-----------------------+ +------------------------+ |
  • | | Windows DNS Server | | Azure DNS Resolver VNet| |
  • | | (10.0.1.10) | | | |
  • | | | | +--------------------+ | |
  • | | Conditional Forwarder | | | Inbound Endpoint | | |
  • | | for *.privatelink -> | ---(VPN/ExpressRoute)| | Subnet (/28) | | |
  • | | points to Inbound IP | ===================> | | IP: 10.100.1.4 | | |
  • | +-----------------------+ | +---------+----------+ | |
  • | ^ | | | |
  • | | | v | |
  • | | | [168.63.129.16 / Azure | |
  • | | | Private DNS Zones] | |
  • | | | | | |
  • | | | v | |
  • | | | +--------------------+ | |
  • | | | | Outbound Endpoint | | |
  • | | | | Subnet (/28) | | |
  • | | | +---------+----------+ | |
  • | | +-----------|------------+ |
  • | | | |
  • | +---(Queries corp.contoso.com forwarded via)----+ |
  • | Forwarding Ruleset linked to Spoke VNets |
  • +-----------------------------------------------------------------------------+

Core Components of Azure DNS Private Resolver:

Inbound Endpoints:

Provisioned in a dedicated subnet (minimum subnet size: /28 ; cannot contain any other resources).

Receives an allocated private IP address from the subnet (e.g., 10.100.1.4 ).

Function: Serves as the target IP address for on-premises Windows Server conditional forwarders. Queries received from on-premises are routed directly to Azure's internal resolver ( 168.63.129.16 ) to resolve Azure Private DNS zones and Private Endpoints.

Outbound Endpoints:

Provisioned in a separate dedicated subnet (minimum subnet size: /28 ).

Function: Originates DNS queries from Azure and transmits them to on-premises DNS servers or external public targets based on rules.

DNS Forwarding Rulesets & Rules:

A Ruleset contains one or more DNS forwarding rules and is linked to one or more Virtual Networks.

Each Rule specifies:

Domain Name: Suffix to match (e.g., corp.contoso.com. or 10.in-addr.arpa. ).

Target DNS Servers: List of on-premises DNS IP addresses and ports (e.g., 10.0.1.10:53 , 10.0.1.11:53 ).

Rule State: Enabled or Disabled .

Priority: Value between 100 and 1000 (lower number = higher precedence).

When an Azure VM in a linked VNet queries server01.corp.contoso.com , the Outbound Endpoint intercepts the query and forwards it directly to the on-premises domain controller.

3. Architecture Comparison: PaaS Resolver vs. Custom IaaS Forwarder VMs

  • Feature / Metric Azure DNS Private Resolver (PaaS) Custom IaaS DNS Forwarders (VMs)
  • Deployment Model Fully managed cloud-native PaaS IaaS Windows Server / BIND Linux VMs
  • High Availability Built-in Multi-AZ redundancy (99.99%) Requires Availability Sets / Zones + Load Balancers
  • Maintenance & Patching Zero OS patching, zero maintenance Monthly OS updates, reboot management

Throughput & Scaling Auto-scales up to 10,000 queries/sec per endpoint Constrained by VM SKU, vCPU, and network limits

  • Cost Model Hourly endpoint + query transaction fee VM compute, managed disks, OS licensing, Load Balancer
  • VNet Architecture Requires dedicated /28 subnets Shares standard workload or management subnets

4. Hybrid DNS Deployment Workflow via PowerShell # PowerShell: End-to-End Hybrid DNS Resolution with Azure DNS Private Resolver

  • # 1. Register the Microsoft.Network provider
  • Register-AzResourceProvider -ProviderNamespace 'Microsoft.Network'
  • # 2. Deploy the Azure DNS Private Resolver
  • $Resolver = New-AzDnsResolver `
  • Name 'Resolver-EastUS' `
  • ResourceGroupName 'RG-HybridDNS' `
  • Location 'eastus' `
  • VirtualNetworkId '/subscriptions/.../subnets/default'
  • # 3. Create the Inbound Endpoint (for queries originating from on-premises)
  • $InboundSubnet = '/subscriptions/.../subnets/snet-resolver-inbound'
  • New-AzDnsResolverInboundEndpoint `
  • DnsResolverName 'Resolver-EastUS' `
  • Name 'Inbound-Endpoint' `
  • ResourceGroupName 'RG-HybridDNS' `
  • Location 'eastus' `
  • IpConfiguration @{ SubnetId = $InboundSubnet; PrivateIpAllocationMethod = 'Dynamic' }
  • # 4. Create the Outbound Endpoint and DNS Forwarding Ruleset
  • $OutboundSubnet = '/subscriptions/.../subnets/snet-resolver-outbound'
  • $OutboundEndpoint = New-AzDnsResolverOutboundEndpoint `
  • DnsResolverName 'Resolver-EastUS' `
  • Name 'Outbound-Endpoint' `
  • ResourceGroupName 'RG-HybridDNS' `
  • Location 'eastus' `
  • SubnetId $OutboundSubnet
  • $Ruleset = New-AzDnsForwardingRuleset `
  • Name 'Ruleset-OnPrem' `
  • ResourceGroupName 'RG-HybridDNS' `
  • Location 'eastus' `
  • DnsResolverOutboundEndpoint $OutboundEndpoint
  • # 5. Add a Forwarding Rule for the On-Premises Active Directory Domain
  • $TargetDNS = New-AzDnsForwardingRulesetTargetDnsServerObject -IpAddress '10.0.1.10' -Port 53
  • New-AzDnsForwardingRule `
  • DnsForwardingRulesetName 'Ruleset-OnPrem' `
  • Name 'Rule-CorpContoso' `
  • ResourceGroupName 'RG-HybridDNS' `
  • DomainName 'corp.contoso.com.' `
  • TargetDnsServer $TargetDNS `
  • ForwardingRuleState 'Enabled'
  • # 6. Link the Ruleset to Spoke Virtual Networks
  • New-AzDnsForwardingRulesetVirtualNetworkLink `
  • DnsForwardingRulesetName 'Ruleset-OnPrem' `
  • Name 'Link-VNet-Spoke01' `
  • ResourceGroupName 'RG-HybridDNS' `
  • VirtualNetworkId '/subscriptions/.../virtualNetworks/VNet-Spoke01'
  • # 7. On-Premises Windows Server DNS: Add Conditional Forwarder for Private Link
  • # Points to the Azure Private Resolver Inbound Endpoint IP (10.100.1.4)
  • Add-DnsServerConditionalForwarderZone `
  • Name 'privatelink.database.windows.net' `
  • MasterServers '10.100.1.4' `
  • ReplicationScope 'Forest'

Loading diagram... Bi-Directional Hybrid DNS Resolution Flow with Azure DNS Private Resolver