dirmngr: dirmngr/dns.c issue with 127.0.0.1
Open, NormalPublic

Description

I think that this issue matters for dirmngr when it is used with local name server (127.0.0.1):
https://github.com/wahern/dns/issues/19

Originally, it was reported at #gnupg IRC channel for dnsmasq on localhost.

gniibe created this task.Jun 13 2018, 8:02 AM
gniibe renamed this task from dirmngr/dns.c issue with dnsmasq to dirmngr/dns.c issue with 127.0.0.1.Jun 13 2018, 8:08 AM
gniibe updated the task description. (Show Details)
gniibe updated the task description. (Show Details)
gniibe claimed this task.Jun 15 2018, 2:38 AM
gniibe added a project: dirmngr.
gniibe triaged this task as Normal priority.

I tested on Debian with local dnsmasq. For usual setting, no problem.
If /etc/resolv.conf has nameserver 127.0.0.1 and the service by dnsmasq somehow stops, and we have another nameserver nameserver somewhere-not-local the issues/19 matters.

gniibe renamed this task from dirmngr/dns.c issue with 127.0.0.1 to dirmngr: dirmngr/dns.c issue with 127.0.0.1.Jun 15 2018, 2:38 AM

For issues/19, it is also reported in T3374: gpg recv-keys fail if first dns server end up with "Connection refused".
This is fixed in master now.
I'm not sure if original reporter's problem is issues/19 or not.