Background: NIST operates a DNS load balancer for NTP: time.nist.gov See http://tf.nist.gov/tf-cgi/servers.cgi
USNO operates a server load balancer for NTP. See for example: http://tycho.usno.navy.mil/ptti/2010papers/paper9.pdf On Sun, Mar 23, 2014 at 2:43 AM, Terje Mathisen <[email protected]>wrote: > Daniel Quick wrote: > >> While this should be obvious, I always have to ask how and why... >> While considering that the number of requests to our time servers >> will grow over time since the client decides which server to sync >> with. >> >> Do we want a Netspeed setting that assists with taking the load off >> some of the more heavily, higher-speed servers? or do we want to keep >> a setting where we serve fewer clients with the highest resolution of >> time given specific setup and let the client queries grow from there? >> I suppose this also takes into the smart dns load-balancing that goes >> on in the background. >> > > You really do NOT want load-balancing of ntp servers!!! > > Put them all in a pool and let the clients connect to all, distributing > the load automatically. > > Terje > > >> Any input would be appreciated. >> >> Thanks, >> >> Daniel >> >> > > -- > - <Terje.Mathisen at tmsw.no> > "almost all programming can be viewed as an exercise in caching" > > > _______________________________________________ > questions mailing list > [email protected] > http://lists.ntp.org/listinfo/questions > _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
