On Sun, 25 Nov 2018 22:22, csm...@debian.org said: > It seems it needs the SRV record and fails wrong without it. > Checking on the same system looking up that SRV record I get the > expected NXDOMAIN error.
That seems to be a Debian specific problem; with a dirmngr started by the gpg command, I get this with master (and pretty sure also with 2.2.11): DBG: chan_7 <- KEYSERVER --clear hkp://keyring.debian.org DBG: chan_7 -> OK DBG: chan_7 <- KS_GET -- 0xDF50FEA5 DBG: dns: libdns initialized DBG: dns: getsrv(_pgpkey-http._tcp.keyring.debian.org) -> 0 records DBG: dns: resolve_dns_name(keyring.debian.org): Success resolve_dns_addr for 'keyring.debian.org': 'keyring.debian.org' [already known] resolve_dns_addr for 'keyring.debian.org': 'keyring.debian.org' [already known] DBG: dns: resolve_dns_name(keyring.debian.org): Success DBG: chan_7 -> S SOURCE http://keyring.debian.org:11371 DBG: (20847 bytes sent via D lines not shown) Can you please test with standard-resolver no-use-tor in dirmngr.conf ? -- Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
pgpQo0mPcGr38.pgp
Description: PGP signature
