On Fri, 2008-12-05 at 17:20 -0500, Kevin Bralten wrote: > Your machine will only show up when it's returned under one of the > *.pool.ntp.org zones. Only 5 servers are returned per query (this is how > the pool's load balancing works), giving only 240 someodd IPv4 results > after querying every zone. Eventually, it will (in theory) query every > host in the pool.
I admit i haven't read thoroughly your logic; i've naturally presumed that noone will share results just after a single iteration ;) > > Actually it may be much worse - i've noticed the problem on freshly > > installed IPv6 capable freebsd without configured ipv6 link. Trying > > to ntpdate my ntp server i've noticed ntpdate was satisfied with > > AAAA record, but it couldn't connect. No fall back for ipv4 (!) > See > http://unix.derkeiler.com/Mailing-Lists/FreeBSD/current/2004-02/0486.html > for the required changes to prefer A records. That is still strange though. Well, mine problem was not a problem at all :) The problem is - how many modern user desktops will behave the same way? Isn't IPv6 turned on in Vista by default? I believe it is. Isn't it asking for AAAA (before A)? How will it behave when there will be AAAA response and IPv6 connectivity won't be functioning? Will it effectively be unable to use the service? Shouldn't the system architects be awared of such behaviour and foresee impact of publishing AAAA records for service names already used in production? Of course. -- Miroslaw "Psyborg" Jaworski GCS/IT d- s+:+ a C++$ UBI++++$ P+++$ L- E--- W++(+++)$ N++ o+ K- w-- O- M- V- PS+ PE++ Y+ PGP t 5? X+ R++ !tv b++(+++) DI++ D+ G e* h++ r+++ y? _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
