All VMs in a VNet are not listed in the private DNS Zone record set

Question

All VMs in a VNet are not listed in the private DNS Zone record set after the VNet is linked to it. I have 2 VMs but only one VM is showing. Not sure what is the issue.

Answer 1

@Subakarini Viswanathan

Thank you for reaching out.

I understand you have linked your Virtual Network to a Private DNS zone and enabled auto registration but record for one of VM is not showing up on the DNS zone.

The following may be the reason why the record might not show up.

• When you start a virtual machine within a linked virtual network with autoregistration enabled, DNS records are automatically created for that virtual machine. When you stop a virtual machine and it is deallocated, the autoregistered DNS records are removed. You can also try to stop and start the VM and see if that helps in autoregistration
• DNS records are created automatically only if the primary virtual machine NIC is using DHCP. If you're using static IPs, such as a configuration with multiple IP addresses in Azure, auto registration doesn't create records for that virtual machine.
• If above fails, just to validate there is no connectivity issue, can you try creating the DNS record manually for the VM in the private DNS zone and validate if you are able to reach the VM using the domain name?

Thank you!