APIM Private Endpoint missing DNS CNAME alias

SvenGlöckner 436 Reputation points

We created an APIM stv2 instance, let's say test-apim.azure-api.net. We also created a private endpoint in our spoke vnet and a private DNS zone in the hub vnet. Both Vnets are peered. When doing a nslookup there is no test-apim.privatelink.azure-api.net entry. We already reprovisioned and created a new private endpoint serveral times but still no luck. What can be wrong?

Azure API Management
Azure API Management
An Azure service that provides a hybrid, multi-cloud management platform for APIs.
1,541 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.
416 questions
{count} votes

Accepted answer
  1. ChaitanyaNaykodi-MSFT 17,976 Reputation points Microsoft Employee


    Thank you for reaching out to us via email, I have just replied to your email.

    Another update from on this issue is :
    We've rolled out a fix for this issue and the fix is already in the prod and all newly created private endpoint for Azure API Management will no longer have the issue.

    At the same time, we are working on fixing the existing broken private point cnames.

    It will be helpful if you test this out and let us know if you are still facing this issue. Thank you!

    ​​Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.
    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. RevelinoB 1,960 Reputation points

    Hi Sven, If you're not seeing the test-apim.privatelink.azure-api.net entry in your nslookup results, there could be a few things causing the issue. First, make sure that your APIM instance is set up correctly to use private endpoints. Then, check that your private DNS zone is configured to resolve the private endpoint for your APIM instance. You should also verify that your VNet peering is set up correctly between your hub and spoke VNets. What you also could double check is if your DNS resolution settings to ensure that your VMs are using the right DNS server(s) to resolve private DNS names. I hope this could help with your issue?

  2. SvenGlöckner 436 Reputation points


    Hi again,

    we again have issues with private endpoint of our APIM instance.

    It seems that the Azure DNS does sometimes not resolve the private IP address from your private endpoint for APIM correctly. Then, the public IP address from our APIM instance is returned.

    This happens several days for about 5-10 minutes.

    Can you please help?

    We'll contact Azure support in parallel.



    0 comments No comments