Azure DNS
An Azure service that enables hosting Domain Name System (DNS) domains in Azure.
690 questions
Private DNS zones is not visible even after vnet is linked to it.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(214.4, 76%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EVS%3C/text%3E%3C/svg%3E)
vinayak sakharkar
0
Reputation points
Hi Team,
We are trying to do cross tenant private DNS zones. Our private DNS zones are created one tenant and trying to share with subscription which is another tenant. Successfully linked vnet from that subscription to private DNS zone in another tenant by following Microsoft documentation. We are using terraform service principle to create resources. service principle in each account is created with access to other tenant and admin consent is also signed in both tenant. Also assigned network contributor and private DNS zone contributor to those service principle via iam. I can see vnet of that subscription is linked in private DNS zone in virtual link networks. What am I missing here?. Can you please guide.
{count} votes
-
Vlad Costa 1,480 Reputation points2024-08-05T00:05:02.2266667+00:00 Check for NSGs or firewall rules that might be blocking DNS traffic between the virtual networks. Ensure that the necessary DNS ports (port 53 for UDP and TCP) are open.
-
vinayak sakharkar 0 Reputation points
2024-08-06T14:14:31.28+00:00 Checking but We don't configure firewall on virtual network and NSG at subnet level. I am not sure NSG & Firewall coming into picture since vnet is successfully linked to private DNS zones
-
KapilAnanth-MSFT 46,876 Reputation points Microsoft Employee2024-08-13T08:59:44.87+00:00 Welcome to the Microsoft Q&A Platform. Thank you for reaching out & I hope you are doing well.
I am afraid I did not understand your query.
I see you have successfully linked a Private DNS Zone from one tenant to a VNET in another tenant already.
- Now, what do you mean by "Private DNS zones is not visible"
- Do you mean to say, from Portal, you are unable to see the Private DNS Zone (of other tenant) from the VNET's tenant?
- In that case, this is expected.
- For cross tenant operations, please consider using Azure CLI/Powershell/Terraform/Bicep
Cheers,
Kapil
Sign in to comment
Sign in to answer