-
Notifications
You must be signed in to change notification settings - Fork 21.2k
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
Comments
Hello @wbplomp |
Hello @wbplomp, Thank you for reaching out.
We will now proceed to close this issue out, please tag me in your response if there are any additional concerns. Thank you! |
Hey @ChaitanyaNaykodi-MSFT |
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.
The text was updated successfully, but these errors were encountered: