You have an Azure subscription that contains a virtual network named VNet1. VNet1 contains a subnet named Subnet1. You deploy an Azure Storage account named storageapp2026 and configure a private endpoint for the storage account in Subnet1. You create a private DNS zone named privatelink.blob.core.windows.net and add the host record for storageapp2026. You discover that virtual machines in Subnet1 continue to resolve the fully qualified domain name (FQDN) of storageapp2026 to its public IP address instead of the private endpoint IP address. What should you do to ensure that the virtual machines resolve the FQDN to the private IP address?
- Link the privatelink.blob.core.windows.net private DNS zone to VNet1.Cevap
- BEnable the Microsoft.Storage service endpoint on Subnet1.
- CAssign the Storage Blob Data Contributor role to the virtual machines.
- DChange the public network access setting of the storage account to Disabled.
Cevap
Link the privatelink.blob.core.windows.net private DNS zone to VNet1.
Linking the private DNS zone `privatelink.blob.core.windows.net` to `VNet1` is required because the Azure-provided DNS server (168.63.129.16) in the virtual network can only resolve records from the private DNS zone once the zone is linked to that virtual network. Without this link, name resolution queries from the virtual machines will fall back to public DNS servers and resolve to the public IP address of the storage account.
Adım Adım Çözüm
Anahtar Kavram
Azure Private Endpoints require the associated Private DNS Zone to be linked to the virtual network for proper name resolution.