Private DNS resolver does not work across different VNets

Zhou Liu 25 Reputation points
2025-07-18T11:29:02.7633333+00:00

Hi,

I have followed the link: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/private-link-and-dns-integration-at-scale.

I want to convert private endpoint name to ip address, when VM and private endpoint are in different VNets, as shown in the figure. The figure has a private DNS resolver. But the samme problem without the implementation of the private DNS resolver.

private DNS problem

Thanks a lot before hand.

Best regards

Liu

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

Accepted answer
  1. Ganesh Patapati 8,760 Reputation points Microsoft External Staff Moderator
    2025-07-18T14:40:01.88+00:00

    Hello Zhou Liu

    • Please add the private DNS resolver inbound IP to the Source machine VNET DNS server, then check the result and share a screenshot.

    Also,

    Could you share the necessary details in a private message so we can continue troubleshooting?


    I hope this has been helpful!

    If the above is unclear or you are unsure about something, please add a comment below.

    0 comments No comments

2 additional answers

Sort by: Most helpful
  1. Zhou Liu 25 Reputation points
    2025-07-19T12:08:53.4866667+00:00

    Hello Ganesh,

    Thank you for your suggestion. But I am quite sure that applying DNS resolvers inbound ip on VM will not help. My drawing shows that all VNets have the private DNS resolver as DNS server. The figure shows also the output of VM1's nslookup, where you can see that VM1 is using the inbound ip as DNS server.

    By the way, VM2 behaves similar as VM1, i.e. nslookup works for webapp02 (in the same VNet), not webapp01.

    Best regards

    Liu

    1 person found this answer helpful.

  2. Zhou Liu 25 Reputation points
    2025-07-21T11:36:52.9+00:00

    Hi,

    I have updated my figure, so that both output of "nslookup" from vm1 and vm2 is shown. It seems that private endpoint in HUB works fine with DNS resolver, but not in spokes.

    private DNS problem.png

    Best regards

    Liu

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.