Question

Your company has three spoke virtual networks (VNet-A, VNet-B, VNet-C) peered to a hub VNet. You deploy a private endpoint for an Azure Storage account (blob sub-resource) in VNet-A. Workloads in all three spoke VNets must resolve the storage account's FQDN to the private endpoint's private IP address. You want to minimize administrative overhead and avoid duplicating DNS records. What should you do?

Accepted Answer

Create one privatelink.blob.core.windows.net Private DNS zone and link it to VNet-A, VNet-B, and VNet-C using virtual network links.

Answer

Create a separate privatelink.blob.core.windows.net Private DNS zone in each VNet and manually add matching A records to all three.

Answer

Configure custom DNS servers in each spoke VNet with host file entries pointing to the private endpoint IP.

Answer

Enable auto-registration on a privatelink.blob.core.windows.net zone linked only to VNet-A so the other VNets inherit resolution through peering.