That concerned me because cell phone clocks are always synced. The one that serves as the AD PDC Emulator is only 1 minute faster than my phone; that seems more reasonable. So I looked at my other DC, which has none of the master roles. Second, my workstations have the same time as the faster DC (are they syncing to it? I looked in the error logs of both DC's and filtered for the Time-Service.I looked at my computer's clock, and it was the same, about 8 minutes ahead of my phone. It is exactly the same as the workstations, about 8 minutes fast. The PDC Emulator DC has Warning Event ID 144: The time service has stopped advertising as a good time source.The other DC has Warning Event ID 142: The time service has stopped advertising as a time source because the local clock is not synchronized. On the primary DC: Event IDs 12, 36, 144 (mentioned above), 131.On the secondary DC: Event IDs 131, 24, 142 (mentioned above), 50, 129. From what I'm seeing, it looks like my PDCe is not pointing to an external source.So which method is the right one to use, and what address do I use? Event ID 12: Time Provider Ntp Client: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source.When a master nameserver is updated (irrespective of the mechanism through which this happens), the working contents of the zone held in memory that have changed need to be transferred to the other servers that are authoritative for that zone (the slave servers). There are two types of zone transfer - full (AXFR) and incremental (IXFR). An Incremental zone transfer is a list of changes that, when applied, bring the slave zone up to date.Zone transfers are always initiated by the slave server (that is, they are 'requested' or 'pulled').
Only way for me to get the IPs is to run a network IP scan to see what the machine IPs are actually and then either do a update on the DNS manually to set the IP or just use the IP i got from the network scan to remote into these machines when needed.
If I look at my secondary DC, it has an Ntp Server entry of time.windows.com,0x9.