[pkg-gnupg-maint] Bug#854359: Bug#854359: gnupg: always fails when --recv-keys

[NIIBE Yutaka]

Thanks a lot for your testing.  I think that I located the issue.

Roger Shimizu <rogershimizu at gmail.com> wrote:
> $ dirmngr --server --homedir=/run/user/1000/test
[...]
> dirmngr[25354.0]: resolve_dns_addr for 'hkps.pool.sks-keyservers.net':
> 'ip-209-135-211-141.ragingwire.net'
[...]
> dirmngr[25354.0]: resolving 'ip-209-135-211-141.ragingwire.net' failed: No name
> dirmngr[25354.0]: can't connect to
> 'ip-209-135-211-141.ragingwire.net': host not found
> dirmngr[25354.0]: error connecting to
> 'https://ip-209-135-211-141.ragingwire.net:443': No name
> dirmngr[25354.0]: command 'KS_GET' failed: No name
> ERR 167772380 No name <Dirmngr>

The keyservers have a problem and the current implementation of dirmngr
doesn't like this particular problem.

The keyservers of hkps.pool.sks-keyservers.net has A record of
209.135.211.141.  And 209.135.211.141 has a name of
ip-209-135-211-141.ragingwire.net.  But when it tries to resolve
ip-209-135-211-141.ragingwire.net, it results NODOMAIN.



Here is information in detail.

    $ host -d hkps.pool.sks-keyservers.net
    Trying "hkps.pool.sks-keyservers.net"
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 33307
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 10, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;hkps.pool.sks-keyservers.net.	IN	A

    ;; ANSWER SECTION:
    hkps.pool.sks-keyservers.net. 505 IN	A	216.66.15.2
    hkps.pool.sks-keyservers.net. 505 IN	A	163.172.29.20
    hkps.pool.sks-keyservers.net. 505 IN	A	92.43.111.21
    hkps.pool.sks-keyservers.net. 505 IN	A	51.15.53.138
    hkps.pool.sks-keyservers.net. 505 IN	A	18.9.60.141
    hkps.pool.sks-keyservers.net. 505 IN	A	94.142.242.225
    hkps.pool.sks-keyservers.net. 505 IN	A	193.224.163.43
    hkps.pool.sks-keyservers.net. 505 IN	A	209.135.211.141
    hkps.pool.sks-keyservers.net. 505 IN	A	192.94.109.73
    hkps.pool.sks-keyservers.net. 505 IN	A	130.206.1.8

    Received 206 bytes from 192.168.43.1#53 in 2 ms
    Trying "hkps.pool.sks-keyservers.net"
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 65108
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 9, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;hkps.pool.sks-keyservers.net.	IN	AAAA

    ;; ANSWER SECTION:
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2001:bc8:2515::1
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2a02:898:31:0:48:4558:73:6b73
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2001:720:418:caf1::8
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2606:9500:201:1::141
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2606:1c00:2802::b
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2001:470:1:116::6
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2a01:4a0:59:1000:223:9eff:fe00:100f
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2001:738:0:600:216:3eff:fe02:42
    hkps.pool.sks-keyservers.net. 499 IN	AAAA	2001:bc8:4700:2300::10:f15

    Received 298 bytes from 192.168.43.1#53 in 48 ms
    Trying "hkps.pool.sks-keyservers.net"
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18642
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

    ;; QUESTION SECTION:
    ;hkps.pool.sks-keyservers.net.	IN	MX

    ;; AUTHORITY SECTION:
    sks-keyservers.net.	300	IN	SOA	ns2.kfwebs.net. kf.kfwebs.net. 3170208123 600 14400 172800 600

    Received 96 bytes from 192.168.43.1#53 in 49 ms
    $ host 209.135.211.141
    141.211.135.209.in-addr.arpa domain name pointer ip-209-135-211-141.ragingwire.net.
    $ host ip-209-135-211-141.ragingwire.net
    Host ip-209-135-211-141.ragingwire.net not found: 3(NXDOMAIN)
    $ 
--