Private endpoint integration with private DNS zones - no custom private zones show

Matt Rognlie 21 Reputation points
2020-06-25T15:07:54.187+00:00

I would like to associate a storage account to a private DNS zone that I have added. When creating the private endpoint, at the step where you integrate with a private DNS zone, any custom zones are not available to choose. The only private zone available is (in the case of file storage) privatelink.file.core.windows.net. I am wondering if this is by design, or if I missed an item setting up the custom private zone (which is properly configured with the virtual network link).

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
631 questions
0 comments No comments
{count} votes

Accepted answer
  1. msrini-MSFT 9,271 Reputation points Microsoft Employee
    2020-06-25T21:54:46.9+00:00

    Hi @MattRognlie-8234 ,

    It is by design. The way how this resolution work is as follows:

    Lets say your Storage Account file share URL is abc.file.core.windows.net.

    When you create Private DNS Zone, Azure Creates a CNAME for abc.file.core.windows.net to abc.privatelink.file.core.windows.net.

    When you access this URL (abc.file.core.windows.net. ) publicly, we map abc.privatelink.file.core.windows.net. to another CNAME which inturn returns Public IP of your Storage Account.

    If you try to access it via VM which is part of VNET linked to Private DNS Zone, the resolution of abc.privatelink.file.core.windows.net will return you PE Private IP.

    Hence you will not be able to customize the DNS name in this case.

    0 comments No comments

0 additional answers

Sort by: Most helpful