On 10 August 2018 at 18:50, Simon McVittie <s...@debian.org> wrote: > Which nss-mdns version are you using?
0.14.1-1 > What's in the hosts: line in your /etc/nsswitch.conf? I currently have: hosts: files mymachines mdns_minimal resolve [!UNAVAIL=return] dns myhostname but I also tried some variations. The delay simply occurs once it hits the mdns_minimal module. > I suspect that you and Eduard might be experiencing different issues > that have the same high-level symptom (delays in name resolution). Oops, I think you're right. While quickly scanning through the bug report it seemed to match, but I somehow managed to overlook that it was resolved for the original poster, I thought the issue was still open for him. My sincere apologies! > This effectively disables the code that tries to avoid interfering with > a .local domain if one exists in normal (non-multicast) DNS, so it's > likely to solve problems for some people but cause problems for others. Yes I didn't mean to imply this is a valid solution, it simply confirms that this particular code is indeed responsible for the delay for me (and provides a workaround for me, since I personally don't care about this feature). > time host -t SOA debian.org. > time host -t SOA local. The first works, the second hangs for 10 seconds until ;; connection timed out; no servers could be reached However, I'm using systemd-resolved and /etc/resolv.conf points to its stub resolver. If I ask the upstream dns server instead, I do get a prompt answer. So, it would seem that the bug actually lies in systemd-resolved. Matthijs