Your message dated Sun, 9 Aug 2026 10:38:39 +0300
with message-id <[email protected]>
and subject line Re: Bug#1101980: unbound-host: Name is confusing; how about
unbound-lookup?
has caused the Debian Bug report #1101980,
regarding unbound-host: Name is confusing; how about unbound-lookup?
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1101980: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1101980
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: unbound-host
Version: 1.22.0-1
Severity: normal
X-Debbugs-Cc: [email protected]
Owner: [email protected]
Tags: trixie
Hi Michael, Robert,
I've just had an instance of user confusion regarding unbound-hosts'
function happen in front of me. Mirroring the confusion in #508053.
Contemporary DNS debugging is confusing enough already I think we should
rename the package and binary. I propose unbound-lookup -- just to get the
bikeshedding going ;-). Something implying that it does a lookup at the
root may be better.
I don't see any packages in Debian using unbound-host direcly:
https://codesearch.debian.net/search?q=unbound-host&page=1&perpkg=1
Happy to forward this upstream too but I think we should move on this first
and before trixie still.
--Daniel
signature.asc
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Tue, 5 May 2026 15:55:10 +0300 Michael Tokarev <[email protected]> wrote:
[..]
For the suggestion, it is definitely an upstream decision, and
definitely not something we should do before upstream.
I see no reason to keep this bug report in the debian BTS, as it
unnecessary draws attention to something which should be decided
elsewhere.
Closing it now.
Thanks,
/mjt
--- End Message ---
