Your message dated Sun, 22 Oct 2017 13:19:11 +0200
with message-id
<1508671151.815349.1146906880.773a8...@webmail.messagingengine.com>
and subject line Closing bugs in old-old-stable bind9 versions
has caused the Debian Bug report #168659,
regarding lwresd binds to 127.0.0.1:953 by default
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.)
--
168659: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=168659
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: lwresd
Version: 1:9.2.1-5
Severity: normal
lwresd binds to 127.0.0.1:953 (the control channel for rndc) by default
which is a little annoying if you're running a (non-recursive, hence the
reason for wanting lwresd in the first place) nameserver on the same
host. Perhaps the package ought to ship with /etc/bind/lwresd.conf,
defaulting to
controls { };
which causes it not to open the control channel?
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux dream.in.wossname.org.uk 2.4.19-acpi #4 Sat Aug 17 21:59:56 BST
2002 i686
Locale: LANG=C, LC_CTYPE=C (ignored: LC_ALL set)
Versions of packages lwresd depends on:
ii libc6 2.3.1-3 GNU C Library: Shared libraries an
ii libdns5 1:9.2.1-5 DNS Shared Library used by BIND
ii libisc4 1:9.2.1-5 ISC Shared Library used by BIND
ii libisccc0 1:9.2.1-5 Command Channel Library used by BI
ii libisccfg0 1:9.2.1-5 Config File Handling Library used
ii liblwres1 1:9.2.1-5 Lightweight Resolver Library used
ii libssl0.9.6 0.9.6g-10 SSL shared libraries
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1:9.10.3.dfsg.P4-12.3
Hi,
the bind9 bug list grew too much and the Debian BIND team cannot
simply test all the reported bugs against versions not in stable, so
this is mass bug close, as either the version is no longer relevant
(because of old-old-stable 9.8.x or old-stable 9.9.5 or even older
version of bind9) or the bug was already fixed.
However, if you can reproduce the bug with a current version in stable,
please use Debian BTS 'found <bug> <version_you_reproduced_the_issue>'
command to retag the bug and reopen it.
Cheers,
Ondrej
signature.asc
Description: PGP signature
--- End Message ---