Private DNS zones question

[samabc]

You manage the Azure environment for a company in the Philippines that hosts its logistics, supply chain, and operations services in the cloud. The company’s Azure subscription includes the following virtual networks:

The subscription also contains the following private DNS zones:

You created virtual network links as follows:

For each of the following items, choose Yes if the statement is true or choose No if the statement is false. Take note that each correct item is worth one point.

Answer to the question says:

> The option that says: You can configure a virtual network link between VNET-Manila and operations.ph is incorrect because you can create only one link between a private DNS zone and a virtual network with autoregistration enabled.

Perplexity.ai disagrees and provides a very clear answer:

> That’s an excellent and subtle question — and it highlights the important distinction between registration and resolution virtual network links in Azure Private DNS zones.

You can indeed create a virtual network link between VNET-Manila and operations.ph because Azure allows a virtual network to be linked to multiple private DNS zones as long as they have different domain names. In that case, logistics.ph and operations.ph are different DNS zones, so VNET-Manila can link to both.

[Irene-TutorialsDojo]

Hello samabc,

Thank you for bringing this to our attention. You are correct in pointing out the distinction between registration and resolution-only virtual network links in Azure Private DNS zones. While it’s true that only one auto-registration link is allowed per DNS zone, a virtual network can indeed be linked to multiple DNS zones for name resolution purposes, as long as they have unique domain names. In this case, VNET-Manila can link to both logistics.ph and operations.ph without issue.

We appreciate your input and hope this clears up any confusion. Let us know if you need further assistance!

Best,

Irene @ Tutorials Dojo