Can't resolve DNS since 2.1.17
Gabriel Souza Franco
gabrielfrancosouza at gmail.com
Wed Mar 1 15:30:50 CET 2017
On Mon, Feb 13, 2017 at 11:01 PM, Gabriel Souza Franco
<gabrielfrancosouza at gmail.com> wrote:
> On Mon, Feb 13, 2017 at 10:19 PM, Daniel Kahn Gillmor
> <dkg at fifthhorseman.net> wrote:
>> I believe the PTR requests themselves are a bug, so not making them
>> seems just fine to me:
>> So it looks to me like the stock behavior is the correct behavior for
>> dirmngr to me, given a broken DNS resolver that cannot handle SRV
>> Can you explain what you would expect to be done differently?
> Not bailing out on a FORMERR from a SRV query. Note that my problem
> isn't that my resolver can't handle SRV, but that it gives the wrong
> answer instead of a NXDOMAIN. This marks the keyserver as dead even
> with successful A and AAAA replies.
> $ gpg --refresh-keys
> gpg: refreshing […] keys from hkps://hkps.pool.sks-keyservers.net
> gpg: keyserver refresh failed: No keyserver available
Ping. I would really like to see a solution for this.
More information about the Gnupg-devel