skip to Main Content

So here is my scenario that I am trying to implement and need some help.

I have two VENT one for Virtual machine and another for Storage account. Both VNET have been peared successfully. Storage account have been disable public access and has Private Link enabled with Private DNS zone.

Now when I do nslookup on storage account from VM(in different network then storage account) it returns the public ip address and my understanding is I should be getting the private IP address which have been assigned in the Private DNS zone.

Am I incorrect with my understanding or am I supposed to do something extra which I haven’t done.

2

Answers


  1. You should be getting private IP addresses. Have you verified that both VNets are linked to the private DNS Zone? Go to the Private DNS Zone in the Azure portal and verify the proper VNets are linked in "Virtual network links"

    Login or Signup to reply.
  2. I have created two virtual network same one for Virtual machine and another for Storage account and peered like below:

    enter image description here

    When I check nslookup on storage account from VM I got the same public Ip address like below:

    enter image description here

    To resolve this issue, check the below steps:

    In Private DNS Zone under setting virtual network link add virtual machine vnet like below:

    enter image description here

    Now when I check nslookup I got storage account private IP address:

    nslookup strimr8xxx.blob.core.windows.net
    Server:  UnKnown
    Address:  168.63.129.16
    
    Non-authoritative answer:
    Name:    strimr88xxx.privatelink.blob.core.windows.net
    Address:  172.0.0.x
    Aliases:  strimr8xxx.blob.core.windows.net
    

    enter image description here

    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search