HOTSPOT -
You have an Azure private DNS zone named contoso.com that is linked to the virtual networks shown in the following table.
The links have auto registration enabled.
You create the virtual machines shown in the following table.
You manually add the following entry to the contoso.com zone:
✑ Name: VM1
IP address: 10.1.10.9 -
For each of the following statements, select Yes if the statement is true. Otherwise, select No.
NOTE: Each correct selection is worth one point.
Hot Area:
Box 1: No -
The manual DNS record will overwrite the auto-registered DNS record so VM1 will resolve to 10.1.10.9.
Box 2: No -
The DNS record for VM1 is now a manually created record rather than an auto-registered record. Only auto-registered DNS records are deleted when a VM is deleted.
Box 3: No -
This answer depends on how the IP address is changed. To change the IP address of a VM manually, you would need to select 'Static' as the IP address assignment. In this case, the DNS record will not be updated because only DHCP assigned IP addresses are auto-registered.
Reference:
https://docs.microsoft.com/en-us/azure/dns/dns-faq-private
NNN 1. VM2 can't resolve v1.contoso.com to 10.1.10.10 because, there is a manual dns entry for vm1 points to 10.1.10.9 which over writes the automatic entry. So the answer is "NO" 2. Deleting a VM will delete only the automatic dns entry. Since we have a manual entry for vm1, that wouldn't be deleted when deleting the vm1. So the answer is "NO" 3. Manually changing the IP address of VM will not update the dns record. Auto DNS will only work if the VM gets ip via DHCP. So the answer is "NO:
Answer is correct, N,N,N, lab tested. For box3, when IP of VM3 is changed, VM3 will reboot, DNS record will disappear. Then VM3 is back, and registers to the new IP in the DNS zone.
So are you saying answer 3 should be Yes as it registers itself after a reboot?
if it comes back and registers, then the answer is YES right?
walkwolf3 - your described results should mean that the answer is N,N,Y
Agree that answer should be N,N,N as this link: https://learn.microsoft.com/en-us/azure/dns/private-dns-autoregistration#restrictions States: 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. Assuming that "changing of the IP address of VM3" means that the NIC is configured with a static IP.
You say for question 3 answer should be YES! Private DNS zone will remove and re-add the new static IP address. But question asks for UPDATE the entry. Remove and Re-add after is not an Update, right?
There is no possibility to change ip address without rebooting vm so DNS will be updated automatically.
By testing in my lab I get No, No and Yes. When you change the IP address of the VM, the VM will automatically reboot, in private DNS the A record disappears and reappears with the new IP address.
I would definitely answer N,N,Y As per the MS site: https://learn.microsoft.com/en-us/azure/dns/private-dns-overview It clearly states: To resolve the records of a private DNS zone from your virtual network, you must link the virtual network with the zone. Linked virtual networks have full access and can resolve all DNS records published in the private zone. You can also enable autoregistration on a virtual network link. When you enable autoregistration on a virtual network link, the DNS records for the virtual machines in that virtual network are registered in the private zone. When autoregistration gets enabled, Azure DNS will update the zone record whenever a virtual machine gets created, changes its' IP address, or gets deleted. The only way to change the IP address is to set it to static within the portal as changing it on the VM itself is a BIG no no. So as per the documentation this proves that the answer is Y for Box 3.
A few people also tested this in their LAB. The scenario provided in the FAQ page shown in the answer page I'm confident is an example of when a person sets a static IP at the OS level rather than from within the portal ipconfig. As tkcltoh mentioned, if you update in the portal and set an IP it should also then update the DNS record.
Answer is No, NO and YES
hi so i the correct answer is N N Y 1- N : in the manual configuration you will remove the auto-registration because u are overriding the DNS record 2- N : VM1 has manual configuration so the entry in the record will be static unless the whole DNS private zone is removed 3- Y : i changed the VM ip address from dynamic to static in the VNIC section , after the VM restarted , when the VM boot up the DNS record update the IP address to the new one you can do the lab is easy just create resource group , 1 vnet , 2 subnet and 3 VM
Lab tested - NNY You can‘t add 2 entries with the same name in the zone. So this record would be set to auto registered NO. Due to this it would not be deleted by deleting the vm. The according DNS record would be deleted, yes but only if auto registered is yes.
I think q3 is Yes because for VM, azure manage the DNS record automatically
Appeared on Exam 26 Aug 2023
In Exam Feb 2024 but vm3 changes its own IP
NNY I see there a lot of misconception on the 3rd question. Configuring a 'static' IP Address to VM3; this still applied Azure DHCP. Essentially it only creates a DHCP scope reservation in the Azure DHCP. Hence the DNS record is update automatically. Now if you question how the IP Address is changed, read the sentence closely; it says, 'of VM3' and not 'on VM3'. Just my two cents.
NYY. I've tested this in a lab. 1. Adding a manual entry overrides the auto-registered entry VM1 had previously, so answer is NO because it will resolve to the new entry that was manually added. 2. Deleting the VM auto-deleted the entry (it appears it checks the status of the VMs NIC), so answer is YES. 3. Changing the IP address of the [NIC] VM deleted the entry and then it re-added a new entry with the updated IP. (I've just tested this on 02/06/2024) Thank you all for your contributions
The answer given is correct
changing the IP address of a VM in a VNet with auto registration to a private DNS zone will update the record if the following conditions are met: - The VM is using DHCP for its primary NIC. - The VM is in a registration virtual network that is linked to the private DNS zone with auto registration enabled. - The VM is not using multiple IP addresses or multiple NICs. If any of these conditions are not met, you will have to manually create or update the DNS records for the VM in the private DNS zone.
appears on exam, 19 Sept 2023
Answer is correct, N,N,N, lab tested too.
1.NO-overwrite the automatically registered DNS records with a manually created DNS record in the zone 2.NO-due VM1 record Created manually here -The private zone's records are populated by the Azure DHCP service, if deallocated, the autoregistered DNS records are removed. 3.NO-Manually changing the IP address of VM will not update the dns record. The private zone's records are populated by the Azure DHCP service.
3 is yes if you change the IP address of the VM the machine will automatically restart , and the DNS will grab the new IP