Study guide

7.3 Private Endpoint DNS Integration & Hybrid 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

7.3 Private Endpoint DNS Integration & Hybrid Resolution

Key Takeaways Explain This Topic AI

Azure PaaS services with Private Endpoints retain their public FQDNs to maintain TLS/SSL certificate validation and HTTP Host header integrity, relying on dynamic CNAME alias delegation (e.g., mydb.database.windows.net -> mydb.privatelink.database.windows.net).

Azure Private DNS Zones (e.g., privatelink.blob.core.windows.net) linked to virtual networks resolve privatelink CNAMEs to the Private Endpoint's private IP (10.x.x.x) for internal clients while public internet clients continue resolving to the PaaS public IP.

The Split-Brain DNS dilemma occurs when local or hybrid DNS servers override entire public zones, leading to NXDOMAIN errors for external resources; resolving this requires targeted conditional forwarding specifically to the privatelink sub-namespace.

Azure Private DNS Resolver Inbound Endpoints provide dedicated private IPs that accept forwarded DNS queries from on-premises DNS servers, enabling hybrid workloads to resolve Azure Private Endpoints seamlessly over VPN/ExpressRoute.

Azure Private DNS Resolver Outbound Endpoints with DNS Forwarding Rulesets allow Azure workloads to conditionally resolve on-premises enterprise domain namespaces without standing up custom IaaS VM DNS forwarders.

Last updated: August 2026

Private Endpoint DNS Integration & Hybrid Resolution

Deploying an Azure Private Endpoint assigns a private IP address to a PaaS service, but applications must be able to discover and resolve that private IP seamlessly. PaaS connection strings, SDKs, and TLS/SSL certificates are strictly bound to the service's Fully Qualified Domain Name (FQDN) (e.g., mystorageaccount.blob.core.windows.net or myserver.database.windows.net ).

If an application attempts to connect directly to the private IP (e.g., https://10.1.2.5/ ), the connection fails because the TLS handshake rejects the mismatch between the IP address and the server's public certificate Common Name (CN) / Subject Alternative Name (SAN). Therefore, a robust, highly available DNS Resolution Architecture is mandatory when implementing Azure Private Link.

1. Canonical CNAME Delegation & Resolution Lifecycle

Microsoft implements an automated DNS CNAME delegation mechanism for all PaaS services enabled with Private Link. +-----------------------------------------------------------------------------+

  • | PRIVATE LINK DNS CNAME RESOLUTION FLOW |
  • | |
  • | 1. Client queries DNS for: mystorage.blob.core.windows.net |
  • | 2. Azure Public DNS returns CNAME alias: |
  • | mystorage.blob.core.windows.net -> mystorage.privatelink.blob.core... |
  • | |
  • | +---------------------------------------------------------------------+ |
  • | | SCENARIO A: Public Internet Client (No Private DNS Zone) | |
  • | | - Queries Public DNS for mystorage.privatelink.blob.core... | |
  • | | - Public DNS resolves CNAME to Public IP: 20.150.45.12 | |
  • | | - Result: Connects to PaaS Public IP (Blocked if FW disabled) | |
  • | +---------------------------------------------------------------------+ |
  • | |
  • | +---------------------------------------------------------------------+ |
  • | | SCENARIO B: Azure VNet Client (Linked to Private DNS Zone) | |
  • | | - Queries Azure Provided DNS (168.63.129.16) | |
  • | | - Private DNS Zone 'privatelink.blob.core.windows.net' intercepts | |
  • | | - Resolves 'mystorage' A-Record to Private IP: 10.1.2.5 | |
  • | | - Result: Connects to Private Endpoint over Private VNet IP! | |
  • | +---------------------------------------------------------------------+ |
  • +-----------------------------------------------------------------------------+

Step-by-Step DNS Resolution Breakdown:

Application Request: The client initiates a connection to mystorage.blob.core.windows.net .

Public CNAME Lookup: Public DNS resolves mystorage.blob.core.windows.net to a canonical alias: mystorage.privatelink.blob.core.windows.net .

Conditional Resolution:

From Internet: The public recursive resolver queries Microsoft's public DNS servers for mystorage.privatelink.blob.core.windows.net and receives the public VIP .

From Azure VNet: The VNet's resolver queries Azure-provided DNS ( 168.63.129.16 ) , which detects a linked Azure Private DNS Zone ( privatelink.blob.core.windows.net ) containing an A record for mystorage pointing to 10.1.2.5 .

Seamless Handshake: The client establishes a TCP/TLS session with 10.1.2.5 while presenting the SNI header mystorage.blob.core.windows.net . The TLS certificate validates perfectly!

Loading diagram... Private Endpoint DNS Resolution and Connection Sequence

2. Azure Private DNS Zone Standard Names & Virtual Network Links

Microsoft defines standardized zone names for each Azure PaaS service that supports Private Endpoints. Maintaining exact zone naming is critical for automated DNS CNAME resolution.

Standard Private DNS Zone Naming Reference

  • Azure PaaS Resource Sub-Resource Type Required Azure Private DNS Zone Name
  • Azure Blob Storage blob privatelink.blob.core.windows.net
  • Azure Data Lake Gen2 dfs privatelink.dfs.core.windows.net
  • Azure Files file privatelink.file.core.windows.net
  • Azure SQL Database sqlServer privatelink.database.windows.net
  • Azure Key Vault vault privatelink.vaultcore.azure.net
  • Azure Cosmos DB (SQL API) Sql privatelink.documents.azure.com
  • Azure App Service (Web Apps) sites privatelink.azurewebsites.net
  • Azure Container Registry registry privatelink.azurecr.io
  • Azure Event Hubs namespace privatelink.servicebus.windows.net
  • Virtual Network Links & Hub-and-Spoke Topology

To enable virtual networks to resolve records in an Azure Private DNS Zone, you must create a Virtual Network Link between the Private DNS Zone and each target VNet. +-----------------------------------------------------------------------------+

  • | CENTRALIZED HUB-AND-SPOKE DNS ARCHITECTURE |
  • | |
  • | HUB VIRTUAL NETWORK (10.0.0.0/16) |
  • | +---------------------------------------------------------------------+ |
  • | | Central Private DNS Zone: privatelink.blob.core.windows.net | |
  • | | - A-Record: mystorage -> 10.0.2.5 | |
  • | | | |
  • | | Azure Private DNS Resolver (Inbound Endpoint: 10.0.1.4) | |
  • | +---------------------------------------------------------------------+ |
  • | | (Virtual Network Link) | (Virtual Network Link) |
  • | v v |
  • | SPOKE VNET 1 (10.1.0.0/16) SPOKE VNET 2 (10.2.0.0/16) |
  • | [App VM: 10.1.1.4] [App VM: 10.2.1.8] |
  • | - Resolves 'mystorage...' - Resolves 'mystorage...' |
  • | to 10.0.2.5 via Hub Link to 10.0.2.5 via Hub Link |
  • +-----------------------------------------------------------------------------+

Tip

Enterprise Best Practice: Centralize Private DNS Zones: In an enterprise hub-and-spoke topology, do not create separate Private DNS Zones in every spoke VNet. Maintain a single, centralized set of Private DNS Zones in the Hub Virtual Network (or dedicated Shared Services subscription) and link all spoke VNets to these central zones.

3. The Split-Brain DNS Dilemma & Mitigation

A frequent challenge in enterprise network engineering is managing Split-Brain (Split-Horizon) DNS when integrating private cloud resources with corporate naming infrastructure.

The Problem: Authoritative Zone Shadowing

If an administrator attempts to configure their internal DNS servers (Active Directory DNS or BIND) by creating an authoritative zone for the entire public domain blob.core.windows.net :

The internal DNS server responds authoritatively for all queries ending in blob.core.windows.net .

When an internal application queries companydata.blob.core.windows.net , the local DNS server returns the static private IP.

However, when an employee queries a public, third-party storage account (e.g., vendorupdates.blob.core.windows.net ), the internal DNS server cannot find the record and returns NXDOMAIN (Non-Existent Domain) , completely breaking access to all public Azure storage accounts worldwide! +-----------------------------------------------------------------------------+

  • | THE SPLIT-BRAIN DNS SHADOWING TRAP |
  • | |
  • | INCORRECT CONFIGURATION: |
  • | Internal DNS creates zone: 'blob.core.windows.net' |
  • | - Query: corp.blob.core.windows.net --> 10.1.2.5 (WORKS) |
  • | - Query: public.blob.core.windows.net--> NXDOMAIN (BROKEN FOR ALL PUBLIC!)|
  • | |
  • | CORRECT ARCHITECTURAL SOLUTION: |
  • | Internal DNS creates conditional forwarder ONLY for: |
  • | 'privatelink.blob.core.windows.net' -> Forward to Azure DNS Resolver |
  • | - Public queries resolve normally via public root hints |
  • | - Private queries follow CNAME to privatelink zone and resolve privately! |
  • +-----------------------------------------------------------------------------+

Mitigation Rule:

Never make on-premises or internal enterprise DNS servers authoritative for public Azure top-level zones (e.g., blob.core.windows.net ). Instead, configure conditional forwarders specifically for the privatelink.* sub-namespace.

4. Hybrid DNS Resolution with Azure Private DNS Resolver

Connecting on-premises datacenters to Azure via ExpressRoute or Site-to-Site VPN requires a bidirectional hybrid DNS mechanism. Azure-provided DNS ( 168.63.129.16 ) is a non-routable link-local VIP accessible only from within an Azure VNet—on-premises servers cannot send DNS packets directly to 168.63.129.16 .

Azure Private DNS Resolver is a fully managed, cloud-native PaaS service that bridges on-premises DNS infrastructure with Azure Private DNS Zones without deploying, patching, or scaling custom IaaS DNS virtual machines. +-----------------------------------------------------------------------------+

  • | HYBRID DNS RESOLUTION VIA PRIVATE DNS RESOLVER |
  • | |
  • | ON-PREMISES DATACENTER |
  • | [On-Prem Server: 192.168.1.50] |
  • | | |
  • | v (Queries: mystorage.blob.core.windows.net) |
  • | [On-Prem DNS Server: 192.168.1.10] |
  • | | |
  • | | (Conditional Forwarder: *.privatelink.blob.core.windows.net) |
  • | | (Target IP: 10.0.1.4 over ExpressRoute / VPN) |
  • | v |
  • | AZURE HUB VNET (10.0.0.0/16) |
  • | +---------------------------------------------------------------------+ |
  • | | Private DNS Resolver - Inbound Subnet (10.0.1.0/28) | |
  • | | [Inbound Endpoint: 10.0.1.4] <------------------------------------+ | |
  • | | | | |
  • | | v (Internal Bridge) | |
  • | | Azure Provided DNS (168.63.129.16) | |
  • | | | | |
  • | | v (Linked Zone) | |
  • | | Central Private DNS Zone: privatelink.blob.core.windows.net | |
  • | | - Record: mystorage -> 10.0.2.5 (Private Endpoint IP) | |
  • | +---------------------------------------------------------------------+ |
  • | | |
  • | +--- Returns 10.0.2.5 to On-Prem DNS ---> On-Prem Server |
  • +-----------------------------------------------------------------------------+

Components of Azure Private DNS Resolver:

Inbound Endpoints:

Allocated a static private IP from a dedicated subnet inside your VNet (subnet size minimum /28 ).

Receives standard DNS queries (UDP/TCP port 53) from on-premises DNS forwarders over ExpressRoute or VPN.

Proxies incoming queries directly to Azure-provided DNS ( 168.63.129.16 ) to resolve Azure Private DNS Zones.

Outbound Endpoints & DNS Forwarding Rulesets:

Allocated a private IP in a separate dedicated subnet (minimum /28 ).

Linked to DNS Forwarding Rulesets that evaluate outbound queries from Azure VNets.

If an Azure VM queries an on-premises domain (e.g., corp.contoso.internal ), the Outbound Endpoint forwards the query to the designated on-premises DNS server IP over the hybrid network.