Can't resolve DNS since 2.1.17
Gabriel Souza Franco
gabrielfrancosouza at gmail.com
Mon Feb 13 19:09:57 CET 2017
On Tue, Jan 31, 2017 at 1:22 AM, Gabriel Souza Franco
<gabrielfrancosouza at gmail.com> wrote:
> With the new backend introduced in 2.1.17 I can no longer resolve
> keyserver urls, and I've traced it back to a failing SRV lookup.
> For some unfathomable reason, my ISP provided router responds with
> FORMERR instead of NXDOMAIN (but not for .localdomain queries,
> interestingly). The failed SRV query then bubbles up, resulting in
> Server indicated failure/No keyserver available errors. The old
> backend seems to treat any failures as no response instead.
On Mon, Feb 13, 2017 at 3:53 PM, Kristian Fiskerstrand
<kristian.fiskerstrand at sumptuouscapital.com> wrote:
> On 02/13/2017 06:46 PM, Gabriel Souza Franco wrote:
>> Ping. Is just ignoring FORMERR the correct approach?
> The correct approach is likely to fix the network configuration causing
> FORMERR to begin with?
I don't think my ISP will care much (see above). Besides, the old
behavior worked with this configuration just fine.
More information about the Gnupg-devel