Azure DNS Private Resolver is not returning private endpoint IP Address for Forms Recognizer

Anon4343 451 Reputation points
2023-06-12T21:43:51.1466667+00:00

We're using Azure DNS Private Resolver to look up the Private Endpoint for Azure Forms Recognizer. Despite having the Private Endpoint DNS registered in the Private DNS Zone and our on-premises DNS configured with a Conditional Forward to cognitiveservices.azure.com, we are still only receiving the public IP address. Networking properties have public access disabled. All resources are in the same region.

What configuration could be missing?

nslookup - <ip of Azure DNS Private DNS Resolver>

example-formrecognizer01-main.cognitiveservices.azure.com

Name:    vnetproxyv3-use2-prod.eastus2.cloudapp.azure.com
Address:  20.119.156.143
Aliases:  example-formrecognizer01-main.privatelink.cognitiveservices.azure.com
          eastus2.prod.vnet.cog.trafficmanager.net
Azure DNS
Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
607 questions
Azure AI Document Intelligence
Azure AI Document Intelligence
An Azure service that turns documents into usable data. Previously known as Azure Form Recognizer.
1,447 questions
{count} votes

Accepted answer
  1. KapilAnanth-MSFT 37,406 Reputation points Microsoft Employee
    2023-06-15T04:45:06.9+00:00

    @Anon4343

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

    I understand that Azure DNS Private Resolver is not returning private endpoint IP Address for Forms Recognizer

    I suggested that we deploy a dummyVM in the VNet as the Private DNS Resolver and use it to check the DNS response from Private resolver.

    • Also, from this VM, can you do
      nslookup <yourservicename>.cognitiveservices.azure.com 168.63.129.16
    • Also, if there are any peered VNets, you can use the VMs in these VNets as well
    • The intention of this is to make sure Private DNS Resolver is actually resolving the Private DNS Zones IP.

    After further troubleshooting,

    • It appears you have not linked to the VNet containing the Private DNS Resolver's Inbound IP address to the Private DNS Zone.
    • And you were able to resolve this issue

    Kindly let us know if this helps or you need further assistance on this issue.

    Thanks,

    Kapil


    Please don’t forget to close the thread by clicking "Accept the answer" wherever the information provided helps you, as this can be beneficial to other community members.

    0 comments No comments

0 additional answers

Sort by: Most helpful