I had some issues with my master ntp server not getting in sync to well and all other equipment sync to it, get very often deny updates because of source out of sync. This master sync about 2 thousands other time devices, witch is not a big load by any mean what so ever.

Then looking at it more, I saw some source getting out of sync, etc.

Then looking at the reference at ntp.org, I came across this:

http://www.pool.ntp.org/vendors.html

Quote "You 'must absolutely not use the default pool.ntp.org zone names' as the default configuration in your application or appliance."

So, I changed my pool to us.pool.ntp.org and it is now getting back in sync and operate better. There is even sub zone in that us zone itself too.

So, it goes from the top, to like

north-america.pool.ntp.org

then sub to
0.north-america.pool.ntp.org
1.north-america.pool.ntp.org
2.north-america.pool.ntp.org
3.north-america.pool.ntp.org

And sub to
us.pool.ntp.org

then sub to
0.us.pool.ntp.org
1.us.pool.ntp.org
2.us.pool.ntp.org
3.us.pool.ntp.org

So, shouldn't the default configuration change to address their requirements and to make it more user friendly?

I just came across this when looking as to why my master wasn't holding time as well as it used to do.

Reply via email to