Redirecting time.windows.com to internal server
Shouldn't be a problem. Just create a zone on your DNS server called 'time.windows.com'. We do it all the time for various things we want to override.
You can also try handing out the NTP server parameter (option ntp-servers) on your DHCP server. Windows may not pick it up, but it couldn't hurt.
Related videos on Youtube
Kyle
Owner of several companies including a IT consulting one and a SaaS one. Despite spending lots of time doing "management" stuff, I'm still lying to myself that I can stay technical too. :-)
Updated on September 18, 2022Comments
-
Kyle almost 2 years
In a corporate environment most machines will be domain joined and therefore get their time from the DCs. However, sometimes you get a machine that isn't in the domain. By default these machines will use time.windows.com as their time source.
Does anyone see a down side to adding a DNS entry for time.windows.com that points to the internal time source? This would result in all non-domain-joined machines still syncing their time to the domain time source.
-
Ivan about 15 yearsYep, this is the right answer, so you don't clobber the whole windows.com domain.
-
Kyle about 15 yearsYup. That's what I did, but nice to know I didn't do something whack!