Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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.

share|improve this question

2 Answers 2

up vote 10 down vote accepted

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.

share|improve this answer
Yep, this is the right answer, so you don't clobber the whole windows.com domain. –  Ivan May 15 '09 at 16:54
Yup. That's what I did, but nice to know I didn't do something whack! –  WaldenL May 27 '09 at 18:10

Another option would be to alias time.windows.com to an appropriate subdomain of pool.ntp.org (e.g. us.pool.ntp.org)...particularly useful for folks who don't have a local time server on their network. (Check out the information at www.pool.ntp.org.)

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.