On 10/26/07, Evandro Menezes <[EMAIL PROTECTED]> wrote: > Let's face it, http://www.pool.ntp.org/scores/63.240.161.99 > is a lousy server, often being discarded as a false-ticker. > But because of its high declared bandwidth, it often makes > to the first server in a DNS query.
I am only 3 ms away from that server RTT (it is also in Chicago on AT&T's network), and it still seems bad (offset >120ms, jtter >7). So I do not think this is just a networking issue, that server is just crazy. I do think that we should weight DNS rotation frequency by the square or cube root of the bandwidth, just to be sure that one server doesn't soak up the majortiy of local pool traffic. -- RPM _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
