> On Fri, 2008-12-05 at 11:53 -0500, Kevin Bralten wrote: >> The number of already IPv6 capable servers in the pool was discussed >> some time ago. Through a quick search, there are _at_least_ 13 IPv6 >> capable machines listed in the pool DNS as of about 10 minutes ago. >> [...] > > Check your test logic. I don't see my server there for example, which > is IPv6 capable since it was born. It has steady 20 points score > for last 3 days, therefore i don't see any reason you could've had > not to check it. 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.
> Server in question is 217.153.128.243, listed in global, Europe and > Poland pools. Having run since earlier today, your machine now appears as one of the 75 logged IPv6 capable hosts: ntp.ipartners.pl has IPv6 address 2001:4190:8002:1::143 > 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. _______________________________________________ timekeepers mailing list [email protected] https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
