Why does IPv6 interfere with Automatic Time Zone update

Question

We have run in to issues with the Automatic Time Zone update for our users that travel. Either the time zone does not update at all or it gets stuck in an incorrect time zone. Manual setting will allow you to change it, but as soon as you turn the automatic setting back on, it goes back to the wrong time zone. We have tried several posted fixes and found that the only way we can resolve is by disabling IPv6. We are running Win10x64 21H2. Can someone advise how IPv6 interfaces with time zone settings and settings to use or has anyone else seen this?

Answer 1

Hello,

The most likely cause for this, is that Time synchronization depends on the name resolution of the Time Server or NTP configured in the system. This name resolution may be only available for IPv4 records (known as "A" records in Active Directory DNS) while IPv6 interfaces will need to have a DNS record that resolves IPv6 records (known as "AAAA" records in AD DNS) for the Time Source. Be aware that some public NTP Servers will not provide IPv6 or AAAA record resolution.

--If the reply is helpful, please Upvote and Accept as answer--