On Mon 2018-11-26 08:42:20 +0100, Werner Koch wrote:
> 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 spe
The standard-resolver option makes it work, how strange. I can see the
system trys to resolve the SRV record and then after that an A/ record.
- Craig
On Mon, 26 Nov 2018 at 18:45, Werner Koch wrote:
> On Sun, 25 Nov 2018 22:22, csm...@debian.org said:
> > It seems it needs the SRV rec
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 g
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.
$ host -t srv _pgpkey-http._tcp.keyring.debian.org
Host _pgpkey-http._tcp.keyring.debian.org not found: 3(NXDOMAIN)
dirmngr log file:
2018-11-2
4 matches
Mail list logo
