Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Auto Registration for Private DNS Zone is not limited to single VNET. #80796

Closed
wbplomp opened this issue Sep 8, 2021 · 3 comments
Closed

Auto Registration for Private DNS Zone is not limited to single VNET. #80796

wbplomp opened this issue Sep 8, 2021 · 3 comments

Comments

@wbplomp
Copy link

wbplomp commented Sep 8, 2021

The page memtions the following limits:

- Auto Registration for Private DNS Zone is limited to single VNET.
But when you enable auto registration on multiple VNets (Virtual Network Links) they de DNS records are automatically registerd on all VNets. Is this limit still valid?

- DNS records are created automatically only if the primary virtual machine NIC is using DHCP. If you're using static IPs, such a configuration with multiple IP addresses in Azure), auto registration won't create records for that virtual machine.
Maybe this descriptions somewhat misleading. Azure VM's with a static IP Address on a vNIC are automatically registered in the Private DNS Zone. This descriptions should mention static IP configurations from within the Operating System or something like that.


Document Details

Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

@ChaitanyaNaykodi-MSFT
Copy link
Contributor

Hello @wbplomp
Thank you for your feedback! We will review and update as appropriate.

@ChaitanyaNaykodi-MSFT
Copy link
Contributor

Hello @wbplomp, Thank you for reaching out.

  1. The limitation mentioned in the document is still valid. You can find the limitation mentioned here as well. . The number of Private DNS zones a virtual network can get linked to with auto-registration enabled is One.
    image

  2. The private zone's records are populated by the Azure DHCP service. As mentioned in the limitation if the VM is assigned static IP addresses, auto registration won't create records for that virtual machine. Please have a look at the FAQ document for additional details.

We will now proceed to close this issue out, please tag me in your response if there are any additional concerns. Thank you!

@ThorgalAegirsson
Copy link

ThorgalAegirsson commented Sep 6, 2023

Hey @ChaitanyaNaykodi-MSFT
As for 1. it seems like auto-registration works for me for multiple vnets. And the limitation you cited doesn't seem to be regarding the question @wbplomp asked. A Vnet can be linked to only one private DNS zone with auto-registration but it looks like there can be a 100 vnets with this option enabled linked to the same private zone (as per limits listed by MS)
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants