Azure Private Endpoint DNS often fails after deployment because clients still query a resolver that cannot see the private zone. A successful deployment creates the network interface, but private name resolution also depends on DNS records, virtual network links and the client’s effective DNS settings.
If the hostname returns a public address, identify the DNS query path before changing firewall rules. Start with the resolver used by the affected client, then follow the request towards the private zone.
Key takeaways
- A linked zone doesn’t automatically serve clients using custom DNS servers.
- Automatic endpoint records depend on DNS integration, not endpoint creation alone.
- A private DNS answer confirms name resolution, but not endpoint approval, network connectivity or application authorisation.
Trace the Azure Private Endpoint DNS query path
The resolver receiving the query determines which private zones and forwarding rules can affect the answer.

When custom DNS servers are configured
Clients use custom DNS servers instead of Azure-provided DNS. Network interface settings can override virtual network settings, so inspect the affected VM rather than relying solely on the VNet configuration.
Custom DNS servers do not automatically consult Azure private zones. Blob and File lookups therefore need conditional forwarding or another resolution path that reaches those zones.
Azure’s platform address, 168.63.129.16, provides Azure DNS within Azure and can be entered as a custom VNet DNS server. It is not an internet-accessible resolver.
Do not add it after a corporate DNS server and expect namespace-based failover. A reachable first server returning a public answer or NXDOMAIN does not necessarily trigger a lookup against another server.
When Azure-provided DNS is used
Azure checks matching private DNS zones linked to the querying VNet, then matching rules in a linked forwarding ruleset. If no rule matches, Azure DNS resolves the query.
For centralised resolution, Azure DNS Private Resolver accepts queries at an inbound endpoint. A linked forwarding ruleset sends matching queries to configured DNS servers.
Among matching forwarding rules, the longest domain suffix wins. A rule for a child namespace therefore takes precedence over a broader parent-domain rule.
Microsoft’s Private Resolver resolution sequence describes this path. It does not mean Azure automatically checks private zones after a custom server returns an unwanted answer.
Check the endpoint, private zone and record
Azure Private DNS supplies private answers for an Azure PaaS service when the relevant zone and record are configured. Creating the zone alone does not establish its resolution scope or populate every required record.
Confirm approval and DNS integration
Review the endpoint’s connection state. A connection awaiting manual approval can remain Pending until an authorised administrator approves it through Private Link Center or the target resource.
Then inspect its DNS configuration and private DNS zone group. With DNS integration configured, Azure creates and manages the endpoint’s A record in the associated private zone.
Without that integration, the record may require separate management. Linking an empty zone to a VNet does not create the missing endpoint record.
Match the zone to the service
Use the service-specific namespace. Azure Blob Storage uses privatelink.blob.core.windows.net; Azure Files uses privatelink.file.core.windows.net. A Blob endpoint does not provide private connectivity for File access.
Microsoft’s private DNS zone reference identifies the required names for each service and subresource.
The normal service hostname commonly follows a public CNAME chain to a private-link hostname. The private zone must then return the endpoint’s private IP.
Link the zone to the client VNet when using Azure-provided DNS, or to the resolver’s VNet in a centralised design. VNet peering does not automatically extend private-zone visibility.
Also check that endpoint recreation has not left an obsolete A record pointing to the previous private IP.
Configure hybrid DNS without a DNS VM
Azure DNS Private Resolver is a cloud-native, highly available and zone-redundant service. For hybrid networking, Azure DNS Private Resolver resolves queries between Azure and corporate networks without deploying DNS-server VMs.

Use the correct endpoint direction
On-premises DNS servers send queries to the resolver’s inbound endpoint. The resolver can answer from private zones linked to its VNet.
This requires VPN or Azure ExpressRoute connectivity, working routes and permitted UDP and TCP port 53 traffic. Microsoft’s hybrid DNS architecture guidance describes that inbound path.
An outbound endpoint serves the opposite requirement: forwarding Azure-originated queries to on-premises or remote DNS servers through rulesets. It isn’t required merely to receive on-premises queries.
Each inbound and outbound endpoint needs its own dedicated subnet, delegated to Microsoft.Network/dnsResolvers. These subnets can’t host other services or share resolver endpoints.
Forward the namespace that clients actually query
For private-zone conditional forwarders, use the deployed resolver address, for example 10.255.1.68, rather than 168.63.129.16.
However, forwarding only privatelink.* names can fail when an upstream recursive resolver has already completed the public CNAME chain. Microsoft’s private endpoint DNS integration guidance also uses service-specific public namespaces, such as blob.core.windows.net, where the original query must reach Azure.
Conditional forwarding is different from hosting a replacement public zone. Don’t create private zones that override broad public namespaces such as windows.net or powerbi.com, or blanket-forward those parent domains without a service-specific design.
Validate resolution from Azure and on-premises
Test DNS resolution from the affected networks, not only from an administrator’s laptop. An Azure VM and a remote client can receive different answers because they use different resolvers.
Record the service hostname, private-link hostname, expected endpoint IP and actual responding resolver before testing.
- On the Azure VM, inspect
ipconfig /all, then runnslookupfollowed by the normal service hostname. Record the resolver and final address. The answer should match the intended endpoint’s private IP. - Repeat
nslookupagainst the full private-link hostname shown in the endpoint’s DNS configuration. A private answer here but a public answer for the normal hostname points towards forwarding or CNAME-chain handling. - Repeat both lookups from a client on the corporate network. Then run interactive
nslookup, enterserverfollowed by the inbound endpoint IP, and query both names again.
If direct queries to the resolver IP succeed but normal client queries fail, investigate the client’s configured DNS path.
After correcting records or forwarding, clear relevant caches. Windows clients support ipconfig /flushdns; upstream resolvers can retain cached answers too.
Finally, test the application using its normal hostname. A private IP answer does not establish that routing, TLS or authentication works.
Match the symptom to the failing layer
Use the observed response to narrow the investigation before changing unrelated settings.
| Symptom | Likely cause | Next action |
|---|---|---|
| Public IP returned | Custom DNS bypasses the private zone | Trace forwarding and the responding resolver |
| NXDOMAIN returned | Missing record or private zone masking the namespace | Inspect the matching zone and A record |
| Azure works, on-premises fails | Missing forwarding or hybrid connectivity | Test the inbound endpoint directly |
| One VM fails | NIC override, stale DNS settings or cache | Inspect effective settings and refresh them |
| DNS query times out | Unreachable resolver or blocked DNS traffic | Review routes and UDP/TCP 53 |
| Private IP returned, application fails | Approval, routing, service policy or permissions | Investigate beyond DNS |
A private address is not sufficient evidence that the correct endpoint was selected. Compare it with the endpoint’s current network interface address.
Keep DNS repair separate from access controls
An Azure Private Link endpoint assigns a service subresource a private IP address in a VNet. A service endpoint instead extends subnet identity to a service’s public endpoint, without assigning that resource a private IP.
Keep these endpoints in a dedicated subnet, separate from resolver endpoint subnets. This simplifies address management and network policy review.
Creating one doesn’t disable the service’s public endpoint. Public network access must be restricted separately, as our Azure Storage security guidance explains.
Avoid overriding broad public DNS zones such as blob.core.windows.net or database.windows.net with private records. Use the relevant privatelink zone and conditional forwarding instead of blanket forwarding.
Don’t reopen broad public access to compensate for broken DNS. After repair, test both expected success and expected rejection: approved applications should connect, whilst disallowed network paths should remain blocked.
Frequently asked questions
Do the original Private Resolver preview limits still apply?
The old maximum of 25 rules per ruleset is outdated. Microsoft’s endpoint and ruleset documentation for Azure DNS Private Resolver allows up to 1,000 rules and supports cross-subscription VNet linking within documented configurations.
Cross-tenant ruleset linking remains unsupported. Resolver endpoints also cannot use IPv6-enabled subnets. These restrictions are separate from private endpoint DNS record configuration.
Can Fabric tenant provisioning look like a DNS problem?
Fabric tenant-level Private Link must be enabled and provisioned before dependent deployment. An InvalidRequest reporting that private link support is not enabled or provisioned points to that prerequisite, rather than a missing DNS record. Check Fabric’s documented DNS configuration before assuming privatelink.powerbi.com is required.
Microsoft’s Fabric Private Link setup guidance describes approximately 15 minutes for disabling public internet access after the relevant setting changes. That is not a universal DNS provisioning timer.
Should applications connect using the private-link hostname?
Applications should normally retain the service’s documented hostname. DNS directs that name towards the private endpoint where the service supports this pattern.
Replacing connection strings with private-link names or raw private IP addresses can introduce TLS hostname-validation or service-routing problems. Use private-link names for diagnosis, not as an automatic application fix.
Restore private resolution without widening access
A successful deployment does not prove that clients use the intended resolver. Establish the query path, correct the zone and forwarding configuration, then test application access separately.
Document the working resolver, zone links and expected answers so later network changes can be tested against them.
If Azure connectivity remains inconsistent, our Azure cloud services and support can help review DNS, private connectivity and access controls together.




