An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
Configure the conditional forwarder for servicebus.windows.net; clients continue using event1.servicebus.windows.net, and Azure DNS follows its CNAME to event1.privatelink.servicebus.windows.net, where the private DNS zone returns the private endpoint’s A record.
Why forward servicebus.windows.net?
For Azure Event Hubs, Microsoft defines:
- Client/public FQDN suffix:
servicebus.windows.net - Private DNS zone:
privatelink.servicebus.windows.net - Recommended conditional-forwarding zone:
servicebus.windows.net^1^
Applications and connection strings query the normal namespace name:
event1.servicebus.windows.net
The resolution sequence is:
event1.servicebus.windows.net
CNAME → event1.privatelink.servicebus.windows.net
A → <private-endpoint-private-IP>
Forwarding the public service zone ensures the initial query enters the Azure-aware resolution path. Azure’s Private Link guidance explicitly requires forwarding the recommended public DNS zone—for example, servicebus.windows.net for Event Hubs—rather than only its privatelink zone ^2^.
If only privatelink.servicebus.windows.net were forwarded, the first lookup for event1.servicebus.windows.net could be answered elsewhere. That resolver might return the public resolution path or fail to send the complete lookup through the resolver that can access the Azure private DNS zone.
For an on-premises DNS server, the forwarder should point to either:
- An Azure DNS Private Resolver inbound endpoint, or
- A DNS forwarder hosted in the Azure VNet linked to the private DNS zone.
That Azure-side resolver can then query Azure-provided DNS. Do not point an on-premises server directly to [IP Address]; that address is reachable only from within an Azure VNet ^3^.
Why ping displays the privatelink name
This is expected CNAME behavior, not a hostname replacement.
Azure publishes a CNAME that redirects the ordinary Event Hubs namespace name to its Private Link name. Your private DNS zone then supplies the A record containing the private endpoint IP. Existing applications therefore continue using event1.servicebus.windows.net; they should not be changed to use the privatelink hostname directly ^1^.
Windows ping displays the canonical name obtained after following the CNAME:
Pinging event1.privatelink.servicebus.windows.net [10.x.x.x]
The important result is the address in brackets:
- Private IP: DNS resolution is working as intended.
- Public IP: the private zone, VNet link, A record, or forwarding path is not being applied.
- NXDOMAIN: the private zone was reached but lacks the required record, or forwarding is incomplete.
Microsoft’s Service Bus private-endpoint validation likewise expects nslookup event1.servicebus.windows.net to return the privatelink alias and a private IP ^4^.
Use nslookup or PowerShell to inspect DNS more clearly:
Resolve-DnsName event1.servicebus.windows.net |
Select-Object Name, Type, NameHost, IPAddress
Expected output includes:
- A CNAME targeting
event1.privatelink.servicebus.windows.net. - An A record containing the private endpoint IP.
The ICMP timeouts in the screenshot do not invalidate the DNS result. ping combines a DNS lookup with an ICMP connectivity test; successful name resolution does not require the destination service to answer ICMP. Validate Event Hubs connectivity using the applicable application protocol rather than ICMP. For Service Bus/Event Hubs private connectivity, relevant network checks include AMQP ports 5671/5672, or port 443 when using WebSockets ^4^.
References