I've been tasked to implement ntp on my SCO Unix servers. I have over 600 servers spread across the US in different time zones. Each remote server has network connectivity to a main server here, through their local ISP. (That's how we currently deliver mail to them).
My question is, how can I implement ntp to keep accurate time across different time zones? I was wanting to send out one ntp.conf file to each server, but I believe that will make the time on a server in California the same as the time on a server in New York. Is this correct? Does the server not compensate for the time based upon the time zone it is configured for?
I appreciate your responses and your effort in helping me understand this.
Most machines store their internal clock in Universal time (UTC) a.k.a GMT. The local time is then configured via a timezone setting, commonly with an environmental variable named TZ. In other words, it should not matter which ntp source your machines use, if their timezone information is correct they will all keep the correct time.
If you have 600 machines to synchronize, you may wish to setup one master time server which is under your control, have them sync to that one and then have it in turn sync to a stratum-1 server. (i.e. distribute the load)
That is exactly what I had planned on doing with regards to having my 600 servers look at one server here, and that server looking at the stratum 1 server. My concern was the timezone differences.
Yesterday I posted a thread about ntp configuration and the effects of servers located in different timezones. After configuring ntp on my server, today I came in to discover that my the time on my server is now one and a half hours off. What is causing this problem?