I understand that for production use, if you have a Hyper-V Domain Controller VM, and the host is on the domain as well, you should have the DC VM reach out to an external source for date/time, and then in turn other machines will sync up to that DC VM.
However, I and a colleague are trying to create a lab exercise, involving 3 Hyper-V VMs which are using an Internal-only VM network switch, so there's no communication with the outside world. There is one domain controller VM, and two other windows server VMs connected to the domain. The host itself is NOT on the domain that the VMs are on, and I don't want it to be. All the VMs and the host machine are using Server 2012 R2.
We intend to use the VMs for a clustering exercise, and for that, all VMs need to have synchronized times.
My colleague, who should be knowledgeable about VMs, claims that in order for time synchronization between all 3 VMs to work properly, the Host machine must be part of the domain used by the VM. I think my colleague is worried about the domain controller VM having one time, and the other two VMs pulling time from the hardware.
My question is, for our VMs to all have synchronized times to each other, should we:
A) enable time synchronization on all 3 virtual machines (in the Integration Services screen of the Hyper-V Manager)
B) enable time synchronization on only 1 or 2 virtual machines - if so which ones
C) disable time synchronization on all 3 virtual machines
If there's not a way to avoid time drift with my described scenario, some time drift is acceptable as long as all 3 VMs have the same amount of drift and are still all in sync for time with each other.
If I were to guess what I should do, based on browsing similar questions, I would say that I should disable the time synchronization on the DC VM, but enable it on the other two VMs. But in that case, are the other two VMs going to have their time synced to the host hardware time, or the DC VM time? I want the latter outcome, and definitely not the former.
Thanks for your help!