>> - When I add a hostname, it only uses the IPv4 Adresse. > > Patches welcome: https://github.com/abh/ntppool/issues/17
What behavior would you expect, anyway? It needs to chose whether it takes the IPv4 address or the IPv6 address. So under what conditions should it chose the IPv6 address when a name is entered? It's a design choice of the NTP pool that a server in the pool can't have both an IPv4 and an IPv6 address, so you have to add it twice. > I don't know of any IPv6 -> geo databases. Maxmind's (which we use > for IPv4) has IPv6 support I believe; but not enough data to be > useful. The database is actually complete and current (today's database is up-to-date until at least 2011-05-27). The country database is easy to keep up to date, since it can directly be generated from RIR data. Since addresses that are allocated typically aren't used right away, the Maxmind database should typically be ahead of actual deployment. It seems you need Geo::IP 1.39 to use the IPv6 database (haven't tried myself, though). > > Until the DNS servers can do a similar lookup, there's not too much > point to the servers having this data anyway. It wouldn't be useful for the DNS lookups, but it would be useful for registration. They are unrelated: even if we found the region during registration, and even if the pool client is going to use IPv6 for NTP, the DNS lookup will most certainly remain IPv4 for a foreseeable future (as the DNS is the last infrastructure that will migrate to IPv6). Regards, Martin _______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
