Hello ,
Thank you for posting in Microsoft Community forum.
After you clone a Linux virtual machine and update its IP address and MAC address, the DNS records of the original virtual machine change, which can be related to several factors:
- If your network uses DHCP servers to assign IP addresses, it can cause DNS records to be updated. When you configure a new IP address for a cloned virtual machine, the DHCP server may associate that IP address with the new MAC address and update the DNS records.
If the IP address of the original virtual machine is also within DHCP range, the DHCP server may treat it as an available address and update it to the new IP address in the DNS. - DNS servers in Windows Server 2019 may be configured to update dynamically. That is, when a DHCP server assigns an IP address, it automatically updates the DNS records.
If the cloned virtual machine obtains an IP address via DHCP, the DNS server may update the A record of the original virtual machine to reflect the new IP address. - Check your network configuration to make sure that no other service is automatically updating DNS records in the background.
- If the cloned VM conflicts with the DNS records of the original VM, the DNS server may prioritize updating to the latest record.
- If a DNS update is triggered manually or through a script while updating the IP address of a cloned VM, it may result in the original VM's DNS records being overwritten.
We recommend that you make sure that the settings of the DHCP server do not affect the DNS records of the original virtual machine.
Check the DNS server's logs to see when and why the DNS records were updated.
If possible, consider configuring the original virtual machine with a static IP address to avoid conflicts caused by DHCP.
I hope the information above is helpful.
If you have any questions or concerns, please feel free to let us know.
Regards,
Jill Zhou