-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Unfortunately there are alot of servers that have AAAA records but are not listening on IPv6... I went through the hosts currently in your pool and all the following were not IPv6 capable....
[EMAIL PROTECTED]:~$ telnet 2001:41d0:1:e812:1c:c0ff:fe65:2cd4 11371 Trying 2001:41d0:1:e812:1c:c0ff:fe65:2cd4... telnet: Unable to connect to remote host: Connection refused [EMAIL PROTECTED]:~$ telnet 2a01:198:200:20a::2 11371 Trying 2a01:198:200:20a::2... telnet: Unable to connect to remote host: Connection refused [EMAIL PROTECTED]:~$ telnet 2001:610:1108:5011:230:48ff:fe12:2794 11371 Trying 2001:610:1108:5011:230:48ff:fe12:2794... telnet: Unable to connect to remote host: Connection refused [EMAIL PROTECTED]:~$ telnet 2001:748:100:1::32 11371 Trying 2001:748:100:1::32... telnet: Unable to connect to remote host: Connection refused - -Ryan Kristian Fiskerstrand wrote: > Ryan Hunt wrote, On 10/17/2008 07:50 AM: >> First, thanks to everyone who peered w/me, had no idea I'd get as many >> responses and so quickly. Neat community here. > >> Anyhow, I dug through all the SKS servers I could find and found a total >> of 5 (including myself) Syncing KeyServers that support IPv6. I put all >> those servers into a pool and setup my monitoring software to keep an >> eye on them encase a server disappears, allowing me to ensure the pool >> only contains active hosts. > >> the address for this IPv6 only pool is: x-hks://pool.ipv6.keys.nayr.net > >> pool.ipv6.keys.nayr.net has IPv6 address 2001:470:1f05:429:420:420:420:420 >> pool.ipv6.keys.nayr.net has IPv6 address 2001:5c0:8a8a:40::51 >> pool.ipv6.keys.nayr.net has IPv6 address 2001:638:204:10::2:1 >> pool.ipv6.keys.nayr.net has IPv6 address 2001:738:0:1:209:6bff:fe8c:845a >> pool.ipv6.keys.nayr.net has IPv6 address 2001:1418:1d7:1::1 > >> I'll check every few months to see if any new IPv6 supported keyservers >> pop up and add them to the list, feel free to use this pool if you find >> it useful. > >> If you want your server added or removed from this list shoot me an email. > > > This is actually not too bad an idea, so I implemented ipv6 to > sks-keyservers.net as well. > > the pool is available at x-hkp://ipv6.pool.sks-keyservers.net and uses > the same data as for the original synchronization test, just checks if > the same servers have AAAA records. > > in theory this could result in a situation where server responds to ipv4 > requests and not ipv6 requests, but for now that seems like an unlikely > issue, which I'll rather counter with blacklist if it happens. > > Status is currently BETA on ipv6, so please come with comments. IPv6 > support will be added to keys.kfwebs.net and possibly keys2.kfwebs.net > over the next couple of weeks as well. > _______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEARECAAYFAkkDR+MACgkQIcAiq3SnceGxXgCcCZssCQ99YcatrkH/9pLfR4J/ vkwAniQpU/Bs4bYmhNpXjsCl8YYzArX3 =jKno -----END PGP SIGNATURE----- _______________________________________________ Sks-devel mailing list Sks-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/sks-devel
