Control: severity -1 minor Control: tag -1 + wontfix upstream
On Tue, 02 Nov 2021 09:27:40 +0100 Bjørn Mork <bj...@mork.no> wrote:
Package: ldnsutils Version: 1.7.1-2+b1 Severity: normal File: /usr/bin/drill -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
...
This is the documented behaviour in debian. Quoting from resolv.conf(5)
...
However, drill seems to use all entries in a random(?) order. Or at least in an order which changes from one run to another, causing failures which come and go depending on whether the nameserver works on the primary link or not.
Hi Bjørn! Drill is a dns debugging tool using a special-purpose dns library. What do you read about resolv.conf is being said for the standard glibc resolver, the manpage describes how the glibc resolver works. Other tools may use the information in there in some other ways, there's no obligation an information is used only the way it was initially supposed to be used. Drill has another tidbit here: it does not use default nameserver of 127.0.0.1 if no nameserver line is specified in resolv.conf. While this might be unexpected to a new user of drill, I don't see it is a bug per se. It is the way how it works (but the lack of default nameserver is annoying). I'm lowering severity of this bug and tagging with wontfix. Rewriting the upstream-decided algorithm of nameserver query order in Debian is definitely not an option. If you think the behavior is incorrect, please file upstream bugreport about this issue. Thank you for the bug report! /mjt
