Private DNS Zone with custom Domain name auto-registration for private Endpoints

Artem Grebenkin 20 Reputation points
2024-05-23T05:18:38.0666667+00:00

Hi folks,

I have a VNet, a private DNS zone e.g. private.brezel.com, and a link with auto registration between them. If I add a new VM e.g. capp l to the VNet, an A record capp pointing at the VM will be automatically created in the private DNS zone, so the VPN is reachable at capp.private.brezel.com.

The same seams to don't work with private Endpoints, which becomes capp.privatelink.blob.core.windows.net. Why?

Thanks, speechkey

Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
620 questions
Azure Private Link
Azure Private Link
An Azure service that provides private connectivity from a virtual network to Azure platform as a service, customer-owned, or Microsoft partner services.
482 questions
0 comments No comments
{count} votes

Accepted answer
  1. KapilAnanth-MSFT 38,456 Reputation points Microsoft Employee
    2024-05-23T05:47:23.95+00:00

    @Artem Grebenkin ,

    Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.

    This is an expected behavior

    The Azure DNS private zones auto registration feature is expected to work with VMs only.

    For Private EndPoints, you can specify if or not you want to update the record in a Private DNS Zone by using the "Integrate with private DNS zone" field while creating the PE.

    • User's image

    If you click "Yes" and,

    • If the resource group already has a Private DNS Zone of the same name, the A record gets updated- User's image
    • If the resource group does not already has a Private DNS Zone, it creates a new zone and also adds the A record
      • User's image

    Thanks,

    Kapil


    Please Accept an answer if correct.

    Original posters help the community find answers faster by identifying the correct answer.


0 additional answers

Sort by: Most helpful