Configuring Hybrid DNS Conditional Forwarders for Azure and AD
Learn how to configure Azure DNS Private Resolver with Windows conditional forwarders to fix hybrid AD-to-Azure name resolution failures for good.

In this lesson
- Operational requirement
- Prerequisites and required permissions
- Step 1 — Deploy the Azure DNS Private Resolver and delegated subnets
- Step 2 — Create the inbound and outbound endpoints
- Step 3 — Build the outbound forwarding ruleset, Azure to on-premises AD
- Step 4 — Configure the on-premises conditional forwarder
Table of Contents
Table of contents
Before you begin
- Basic Windows Server DNS zone administration
- Azure networking fundamentals (VNets, subnets, NSGs)
- Familiarity with Azure CLI and PowerShell
Track this tutorial
Choose your current status and tick each safety check as you complete it. Sign in to sync progress between devices.
Current status
Tutorial stages
- Step 1 — Deploy the Azure DNS Private Resolver and delegated subnets
- Step 2 — Create the inbound and outbound endpoints
- Step 3 — Build the outbound forwarding ruleset, Azure to on-premises AD
- Step 4 — Configure the on-premises conditional forwarder
0 of 4 stages complete
Before you apply the change
Confirm these production-safety controls during the tutorial.
#Operational requirement
You are the engineer who inherits the hybrid DNS ticket queue the week workloads start moving into Azure. KBY Technologies runs Active DirectoryThe KBY LexiconActive DirectoryActive Directory is Microsoft's directory service for identity, access and policy management. This entry defines its LDAP/Kerberos architecture, security boundary role and key distinctions from Microsoft Entra ID.
on-premises and Azure Private Endpoints for App Service, SQL Managed Instance and Storage in parallel, and that split estate only works if name resolution crosses cleanly in both directions. Users on the corporate VPN or ExpressRoute circuit need to resolve corp.kbytech.local AD-integrated names. On-premises clients reaching Azure services through Private Endpoints need names such as mydb.database.windows.net to resolve, via Azure Private DNS zones such as privatelink.database.windows.net and privatelink.blob.core.windows.net, to private IP addresses, not public ones. If forwarding between the two estates is not explicitly configured, clients get intermittent SERVFAIL and NXDOMAIN responses depending on which resolver happens to answer first.
That failure does not present as a single clean error. It presents as a wave of tickets: Hybrid Azure AD Join failing on some machines, Group PolicyThe KBY LexiconGroup PolicyGroup Policy centrally manages Windows computer and user configuration through GPOs linked to Active Directory containers, with a defined processing order, refresh cycles, and rollback via unlinking rather than deletion. silently not applying on Azure-hosted VMs, Intune or SCCM co-management agents that stop phoning home, and SQL connection strings that resolve to public IPs instead of the private endpoint. None of these symptoms point directly at DNS. Treat any cluster of ‘works sometimes’ tickets from Azure-joined machines as a DNS forwarding suspect first, not last.
Your task is to build a production forwarding path using Azure DNS Private Resolver on the Azure side and Windows conditional forwarders on-premises. This is the current Microsoft-recommended pattern. It replaces the older approach of running IaaS DNS forwarder VMs in Azure — technical debt you will still find in older client tenants, and something you should flag for retirement whenever you encounter it.
#Prerequisites and required permissions
Confirm every item below before you open a change record. Missing permissions mid-change is how a thirty-minute task turns into a half-day escalation.
- Azure RBAC: Network Contributor on the target subscription or resource group.
- An existing hub VNet with ExpressRoute or Site-to-Site VPN already established, with routing confirmed to the on-premises DNS server subnet (10.0.1.0/24 in this walkthrough).
- Two unused /28 subnets in the hub VNet reserved for the resolver’s inbound and outbound endpoints. Each endpoint needs its own subnet, delegated to Microsoft.Network/dnsResolvers, and neither subnet can host any other resource.
- On-premises: membership of the DnsAdmins group, or Domain Admins, on the Windows ServerThe KBY LexiconWindows ServerWindows Server is Microsoft's server operating system family, providing directory, network and application services as installable roles. DNS role holders — typically the domain controllers themselves.
- Firewall and NSG rules reviewed in advance, allowing UDP and TCP port 53 across the VPN or ExpressRoute path for two flows: from the outbound endpoint subnet (10.10.4.16/28) to the on-premises DNS servers (10.0.1.0/24), because forwarded queries leave Azure from that subnet, and from the on-premises DNS servers (10.0.1.0/24) to the inbound endpoint subnet (10.10.4.0/28), where 10.10.4.4 listens.
- A change record raised and approved in your ITSM tool before touching production DNS. DNS changes with no rollback plan are how outages become incidents.
#Step 1 — Deploy the Azure DNS Private Resolver and delegated subnets
Create the two dedicated subnets first. The resolver service refuses to attach to a subnet that has not been delegated correctly, and it fails without a helpful message if you skip this.
1az network vnet subnet create \
2 --resource-group rg-network-hub \
3 --vnet-name vnet-hub \
4 --name snet-dns-inbound \
5 --address-prefixes 10.10.4.0/28 \
6 --delegations Microsoft.Network/dnsResolvers
7
8az network vnet subnet create \
9 --resource-group rg-network-hub \
10 --vnet-name vnet-hub \
11 --name snet-dns-outbound \
12 --address-prefixes 10.10.4.16/28 \
13 --delegations Microsoft.Network/dnsResolvers
14
15# --id is required: the resource ID of the VNet the resolver attaches to
16az dns-resolver create \
17 --name dnspr-hub \
18 --resource-group rg-network-hub \
19 --location uksouth \
20 --id "/subscriptions/<sub-id>/resourceGroups/rg-network-hub/providers/Microsoft.Network/virtualNetworks/vnet-hub"Keep the delegated subnets in place even after you roll back the resolver resource. Recreating delegated subnets under incident pressure is slower and riskier than leaving them provisioned but empty.
#Hands-on task
In a non-production subscription, deploy the resolver, create one forwarding rule for a test domain, and configure a conditional forwarder on a lab domain controller pointing at the inbound endpoint IP. Capture Resolve-DnsName output proving resolution succeeds in both directions, then execute the rollback sequence above and confirm the zones and rules are fully removed, with Get-DnsServerZone and az dns-resolver forwarding-rule list both returning empty results.
#Operational Summary
Hybrid DNS forwarding is not a one-off setup task. It is production infrastructure and needs the same change control, monitoring and rollback discipline you would apply to a firewall rule or a routing table change. Azure DNS Private Resolver replaces the older self-managed forwarder VM pattern and removes a whole category of patching and availability debt, but it still depends entirely on correct NSG rules, correct subnet delegation and correctly terminated domain names in the forwarding rule. Test resolution from both sides of the link before you close any change record, retain the Log Analytics query evidence, and never delete the resolver resource before removing the dependent rulesets and on-premises forwarder zones in the documented order. Get this wrong once during onboarding and you will remember the trailing dot for the rest of your career; get it right and hybrid name resolution stops being a source of unexplained tickets and becomes just another line item on the monitoring dashboard.
#Related reading
Preventing DNS Split-Brain in Hybrid Azure/AD
Resolving Hybrid DNS Failures for Entra ID Hybrid-Joined Devices
Azure Conditional Access Misses Service Principal Sign-Ins
DNS Resilience Defaults Silently Override Expected Safeguards
About this page
Credited to
Dates
Published
Sources
Read-only scripts
- Windows devices with no BitLocker recovery key in Entra IDMicrosoft Entra ID, Windows
- Intune devices that haven't synced in N daysMicrosoft Intune
- Mailboxes forwarding to external addressesExchange Online
- BitLocker status of every volume on this PCWindows
Upcoming deadlines
- Intune moves to macOS 15 and laterQ4 2026
- SAP SuccessFactors provisioning: move from basic auth to workload identityNovember 2026
- Intune November release: JIT registration reminder at APNs renewal and automatic JIT for eligible tenantsNovember 2026
Explore KBY
The KBY Brief
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.
SubscribeRelated articles
Enterprise IT Management
Microsoft 365 Conditional Access Blocking Legacy Auth: AADSTS53003
How to trace AADSTS53003 and legacy authentication blocks in Entra sign-in logs and remediate clients without weakening Conditional Access.
Enterprise IT Management
Part 1: Windows Autopilot Prerequisites in Intune: Licences, Automatic Enrolment and Branding
Get the tenant ready for Windows Autopilot: licences, automatic Intune enrolment for a pilot group, Entra join permissions, branding, and the choice between classic Autopilot and device preparation.
Discover more
Ops Playbook
Lexicon Definitions
Learn More About KBY
About KBY
Learn about our mission, how our content is produced, and how we handle corrections.
Why Trust KBY
How KBY content is produced, what is checked automatically, and how errors are corrected.
The KBY Brief
A short email about twice a week with new runbooks, configuration traps and fixes from KBY Technologies.
Was this useful?
Reports go to the site owner and are used to correct pages. Corrections are listed at /corrections.
Build practical engineering skills.
Receive new lessons, learning paths, practical exercises and early-career guidance.
Comments
Add a thoughtful note on Configuring Hybrid DNS Conditional Forwarders for Azure and AD. Comments are checked for spam and held for moderation before appearing.