Hi
On Wednesday 1 June 2016 at 5:31:30 PM, in <mid:59e4f8b7-28b9-dddd-f0cf-a2a7ba4b4...@sumptuouscapital.com>, Kristian Fiskerstrand wrote: > what is the dig +trace output and any firewall > blocking port 11371 anywhere? Thanks for replying. Port 11371 is not blocked:- I can reach a keyserver's web interface in my browser at <http://pool.sks-keyservers.net:11371>. I can connect to <http://portquiz.net:11371>. The gpg --recv-key command works if I use GnuPG version 1.4.18, and one of the lines of output is "gpgkeys: HTTP URL is`http:/ /pool.sks-keyservers.net:11371/pks/lookup?op=get&options=mr& search=0x251BCCEB547B7194'". As for dig +trace, I am using Windows and don't have it. The dig web interface at <http://www.digwebinterface.com/?hostnames=pool.sks-keyservers.net&type=A&showcommand=on&colorize=on&trace=on&compare=on&ns=resolver&useresolver=8.8.4.4&nameservers=> gives me:- pool.sks-keyservers.net@8.8.4.4 (Default): dig A +noadditional +noquestion +nocomments +nocmd +nostats +trace pool.sks-keyservers.net. @8.8.4.4 . 4154 IN NS a.root-servers.net. . 4154 IN NS b.root-servers.net. . 4154 IN NS c.root-servers.net. . 4154 IN NS d.root-servers.net. . 4154 IN NS e.root-servers.net. . 4154 IN NS f.root-servers.net. . 4154 IN NS g.root-servers.net. . 4154 IN NS h.root-servers.net. . 4154 IN NS i.root-servers.net. . 4154 IN NS j.root-servers.net. . 4154 IN NS k.root-servers.net. . 4154 IN NS l.root-servers.net. . 4154 IN NS m.root-servers.net. ;; Received 228 bytes from 8.8.4.4#53(8.8.4.4) in 37 ms net. 172800 IN NS a.gtld-servers.net. net. 172800 IN NS b.gtld-servers.net. net. 172800 IN NS c.gtld-servers.net. net. 172800 IN NS d.gtld-servers.net. net. 172800 IN NS e.gtld-servers.net. net. 172800 IN NS f.gtld-servers.net. net. 172800 IN NS g.gtld-servers.net. net. 172800 IN NS h.gtld-servers.net. net. 172800 IN NS i.gtld-servers.net. net. 172800 IN NS j.gtld-servers.net. net. 172800 IN NS k.gtld-servers.net. net. 172800 IN NS l.gtld-servers.net. net. 172800 IN NS m.gtld-servers.net. ;; Received 510 bytes from 199.7.83.42#53(199.7.83.42) in 25 ms sks-keyservers.net. 172800 IN NS ns2.kfwebs.net. sks-keyservers.net. 172800 IN NS ns2.sks-keyservers.net. sks-keyservers.net. 172800 IN NS ns6.sks-keyservers.net. sks-keyservers.net. 172800 IN NS ns9.sks-keyservers.net. sks-keyservers.net. 172800 IN NS ns13.sks-keyservers.net. ;; Received 359 bytes from 192.42.93.30#53(192.42.93.30) in 450 ms pool.sks-keyservers.net. 60 IN A 46.4.212.178 pool.sks-keyservers.net. 60 IN A 78.47.176.74 pool.sks-keyservers.net. 60 IN A 84.200.66.125 pool.sks-keyservers.net. 60 IN A 95.89.12.215 pool.sks-keyservers.net. 60 IN A 104.131.30.118 pool.sks-keyservers.net. 60 IN A 188.40.206.8 pool.sks-keyservers.net. 60 IN A 206.176.170.195 pool.sks-keyservers.net. 60 IN A 5.135.158.148 pool.sks-keyservers.net. 60 IN A 37.59.213.225 pool.sks-keyservers.net. 60 IN A 37.97.129.189 sks-keyservers.net. 60 IN NS ns13.sks-keyservers.net. sks-keyservers.net. 60 IN NS ns7.sks-keyservers.net. sks-keyservers.net. 60 IN NS ns2.sks-keyservers.net. sks-keyservers.net. 60 IN NS ns9.sks-keyservers.net. sks-keyservers.net. 60 IN NS ns6.sks-keyservers.net. sks-keyservers.net. 60 IN NS ns12.sks-keyservers.net. sks-keyservers.net. 60 IN NS ns1.kfwebs.net. sks-keyservers.net. 60 IN NS ns2.kfwebs.net. sks-keyservers.net. 60 IN NS ns10.sks-keyservers.net. ;; Received 493 bytes from 199.74.220.4#53(199.74.220.4) in 22 ms "nslookup pool.sks-keyservers.net" gives me:- Non-authoritative answer: Name: pool.sks-keyservers.net Addresses: 2a01:4f8:150:7142::2 87.106.9.235 2001:980:53c0:1:46a:efff:fecf:701b 2001:41d0:2:3979:4f56:862a:d056:11c9 2001:41d0:2:a8b4::10 2001:41d0:8:d894::1 2604:a880:800:10::163:b001 2a01:4a0:59:1000:223:9eff:fe00:100f 2a01:7a0:1::6 2a03:b0c0:1:d0::fc:e001 104.131.30.118 5.9.50.141 37.191.220.247 83.160.105.236 85.119.82.209 85.143.112.59 92.43.111.21 144.76.9.122 176.9.146.20 208.89.139.251 "tracert -4 pool.sks-keyservers.net" gives, for example:- Tracing route to pool.sks-keyservers.net [176.241.243.15] over a maximum of 30 hops: 1 1 ms <1 ms <1 ms dsldevice.lan [IP ADDRESS REDACTED] 2 9 ms 9 ms 8 ms a.gormless.thn.aa.net.uk [90.155.53.51] 3 9 ms 9 ms 9 ms a.needless.tch.aa.net.uk [90.155.53.11] 4 10 ms 10 ms 11 ms 82.112.115.177 5 10 ms 10 ms 10 ms ae-13.r02.londen03.uk.bb.gin.ntt.net [129.250.2.118] 6 16 ms 17 ms 16 ms be3028.ccr21.lon02.atlas.cogentco.com [130.117.14.101] 7 17 ms 16 ms 18 ms be2791.ccr41.lon13.atlas.cogentco.com [154.54.56.77] 8 23 ms 23 ms 22 ms be12194.ccr41.ams03.atlas.cogentco.com [154.54.56.94] 9 31 ms 32 ms 31 ms be2815.ccr41.ham01.atlas.cogentco.com [154.54.38.206] 10 45 ms 44 ms 46 ms be2252.ccr21.waw01.atlas.cogentco.com [154.54.60.254] 11 44 ms 44 ms 44 ms be2882.rcr21.b016833-0.waw01.atlas.cogentco.com [154.54.59.38] 12 78 ms 245 ms 207 ms 149.11.6.230 13 45 ms 44 ms 44 ms host-80-238-113-202.jmdi.pl [80.238.113.202] 14 45 ms 44 ms 44 ms hell.kolosowscy.pl [176.241.243.15] Trace complete. Tracing route to pool.sks-keyservers.net [37.59.213.225] over a maximum of 30 hops: 1 1 ms <1 ms 1 ms dsldevice.lan [IP ADDRESS REDACTED] 2 9 ms 8 ms 8 ms a.gormless.thn.aa.net.uk [90.155.53.51] 3 9 ms 9 ms 9 ms a.aimless.thn.aa.net.uk [90.155.53.41] 4 * * * Request timed out. 5 13 ms 13 ms 13 ms be11-1188.rbx-g2-a9.fr.eu [91.121.128.88] 6 103 ms 57 ms 14 ms po3.vss-2-6k.routers.ovh.net [91.121.131.89] 7 13 ms 13 ms 13 ms x1.f2tec.de [94.23.210.194] 8 13 ms 13 ms 13 ms web.okoyono.de [37.59.213.225] Trace complete. "tracert -6 pool.sks-keyservers.net" gives, for example:- Tracing route to pool.sks-keyservers.net [2001:6f8:1c3c:babe::62:1] over a maximum of 30 hops: 1 1 ms 1 ms 1 ms dsldevice.lan [IP ADDRESS REDACTED] 2 9 ms 9 ms 9 ms a.gormless.thn.aa.net.uk [2001:8b0:0:53::51] 3 9 ms 9 ms 9 ms 2001:7f8:4::50e8:1 4 15 ms 15 ms 12 ms pc3.gr10.telon.uk.easynet.net [2001:7f8:4::11ed:1] 5 29 ms 28 ms 29 ms 2001:6f8:1:1:87:86:76:34 6 26 ms 26 ms 26 ms tengige0-0-0-2-112.er0.kgham.nexinto.net [2001:6f8:801:1:0:1a03:c240:812] 7 25 ms 25 ms 25 ms 2001:6f8:891:1::c2e9:c721 8 26 ms 25 ms 25 ms 2001:6f8:891:1::c2e9:c721 9 26 ms 25 ms 25 ms gw-112.ham-02.de.sixxs.net [2001:6f8:1c00:6f::1] 10 35 ms 34 ms 34 ms gpg.spline.inf.fu-berlin.de [2001:6f8:1c3c:babe::62:1] Trace complete. Tracing route to pool.sks-keyservers.net [2001:41d0:2:a8b4::10] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms dsldevice.lan [IP ADDRESS REDACTED] 2 9 ms 9 ms 9 ms a.gormless.thn.aa.net.uk [2001:8b0:0:53::51] 3 9 ms 9 ms 9 ms 2001:7f8:4::50e8:1 4 * * * Request timed out. 5 13 ms 12 ms 12 ms be10-1194.gra-g2-a9.fr.eu [2001:41d0::292] 6 * * * Request timed out. 7 * * * Request timed out. 8 20 ms 20 ms 20 ms po6.vss-4-6k.routers.ovh.net [2001:41d0::522] 9 20 ms 20 ms 20 ms 2001:41d0:2:a8b4::10 Trace complete. -- Best regards MFPA <mailto:2014-667rhzu3dc-lists-gro...@riseup.net> My mind works like lightning... one brilliant flash and it's gone _______________________________________________ Gnupg-users mailing list Gnupg-users@gnupg.org http://lists.gnupg.org/mailman/listinfo/gnupg-users