Your message dated Fri, 25 Nov 2022 21:29:57 +0100
with message-id <y4elxxog9umaz...@fliwatuet.svr02.mucip.net>
and subject line Re: Bug#606767: bind9: man pages and doc files wrongly use 
/etc/ instead of /etc/bind/
has caused the Debian Bug report #606767,
regarding bind9: man pages and doc files wrongly use /etc/ instead of /etc/bind/
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 ow...@bugs.debian.org
immediately.)


-- 
606767: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=606767
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bind9
Version: 1:9.7.2.dfsg.P3-1
Severity: normal
Tags: patch

Hi,

all man pages and documentation fiels referring to
named.conf, rndc.conf and rndc.key wrongly claim that
these files are to be found in /etc/ instead of /etc/bind/.

The attached pach fixes the issue.

Please note:
This bug is related although not identical to #260759
Closing this bug also closes #260759

Best regards
Peter



-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/4 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages bind9 depends on:
ii  adduser                3.112+nmu2        add and remove users and groups
ii  bind9utils             1:9.7.2.dfsg.P3-1 Utilities for BIND
ii  debconf [debconf-2.0]  1.5.36            Debian configuration management sy
ii  libbind9-60            1:9.7.2.dfsg.P3-1 BIND9 Shared Library used by BIND
ii  libc6                  2.11.2-7          Embedded GNU C Library: Shared lib
ii  libcap2                1:2.19-3          support for getting/setting POSIX.
ii  libdb4.8               4.8.30-2          Berkeley v4.8 Database Libraries [
ii  libdns69               1:9.7.2.dfsg.P3-1 DNS Shared Library used by BIND
ii  libgssapi-krb5-2       1.8.3+dfsg-3      MIT Kerberos runtime libraries - k
ii  libisc62               1:9.7.2.dfsg.P3-1 ISC Shared Library used by BIND
ii  libisccc60             1:9.7.2.dfsg.P3-1 Command Channel Library used by BI
ii  libisccfg62            1:9.7.2.dfsg.P3-1 Config File Handling Library used 
ii  libldap-2.4-2          2.4.23-7pm1       OpenLDAP libraries
ii  liblwres60             1:9.7.2.dfsg.P3-1 Lightweight Resolver Library used 
ii  libssl0.9.8            0.9.8o-3          SSL shared libraries
ii  libxml2                2.7.8.dfsg-1      GNOME XML library
ii  lsb-base               3.2-23.1          Linux Standard Base 3.2 init scrip
ii  net-tools              1.60-23           The NET-3 networking toolkit
ii  netbase                4.43              Basic TCP/IP networking system

bind9 recommends no packages.

Versions of packages bind9 suggests:
ii  bind9-doc              1:9.7.2.dfsg.P3-1 Documentation for BIND
ii  dnsutils               1:9.7.2.dfsg.P3-1 Clients provided with BIND
pn  resolvconf             <none>            (no description available)
pn  ufw                    <none>            (no description available)

-- Configuration Files:
/etc/bind/named.conf.local changed [not included]
/etc/bind/named.conf.options changed [not included]

-- debconf information:
  bind9/different-configuration-file:
  bind9/run-resolvconf: false
  bind9/start-as-user: bind

-- debsums errors found:
debsums: changed file /usr/share/bind9/bind9-default.md5sum (from bind9 package)
# bind9-correct-sysconfdir-in-doc+man.patch
#
# this patch was created using the following script:
#
#  #!/bin/sh
#  ALL_DOC_FILES=$(find bind9-9.7.2.dfsg.P3/ -name \*.docbook -o -name \*.html 
-o -name \*.[1-9])
#  AFFECTED_DOC_FILES=$(grep -l -e /etc/named.conf -e /etc/rndc.key -e 
/etc/rndc.conf ${ALL_DOC_FILES})
#  for file in $AFFECTED_DOC_FILES; do 
#       cp -a "$file" "${file}.orig"
#       sed -e 's:/etc/named.conf:/etc/bind/named.conf:g' \
#           -e 's:/etc/rndc.key:/etc/bind/rndc.key:g' \
#           -e 's:/etc/rndc.conf:/etc/bind/rndc.conf:g' < "${file}.orig" > 
"$file"
#       diff -ub "${file}.orig" "$file" >> 
bind9-correct-sysconfdir-in-doc+man.patch
#  done
#  exit


--- bind9-9.7.2.dfsg.P3/contrib/nslint-2.1a3/nslint.8   2001-12-21 
05:12:03.000000000 +0100
+++ bind9-9.7.2.dfsg.P3/contrib/nslint-2.1a3/nslint.8   2010-12-11 
16:26:03.421127563 +0100
@@ -108,7 +108,7 @@
 Specify an alternate
 .I named.conf
 file. The default is
-.IR /etc/named.conf .
+.IR /etc/bind/named.conf .
 .TP
 .B -B
 Specify an alternate
--- bind9-9.7.2.dfsg.P3/doc/arm/man.named.html  2010-08-20 04:40:26.000000000 
+0200
+++ bind9-9.7.2.dfsg.P3/doc/arm/man.named.html  2010-12-11 16:26:03.428490399 
+0100
@@ -60,7 +60,7 @@
       When invoked without arguments, <span><strong 
class="command">named</strong></span>
       will
       read the default configuration file
-      <code class="filename">/etc/named.conf</code>, read any initial
+      <code class="filename">/etc/bind/named.conf</code>, read any initial
       data, and listen for queries.
     </p>
 </div>
@@ -83,7 +83,7 @@
 <dd><p>
             Use <em class="replaceable"><code>config-file</code></em> as the
             configuration file instead of the default,
-            <code class="filename">/etc/named.conf</code>.  To
+            <code class="filename">/etc/bind/named.conf</code>.  To
             ensure that reloading the configuration file continues
             to work after the server has changed its working
             directory due to to a possible
@@ -286,7 +286,7 @@
 <div class="refsect1" lang="en">
 <a name="id2673580"></a><h2>FILES</h2>
 <div class="variablelist"><dl>
-<dt><span class="term"><code 
class="filename">/etc/named.conf</code></span></dt>
+<dt><span class="term"><code 
class="filename">/etc/bind/named.conf</code></span></dt>
 <dd><p>
             The default configuration file.
           </p></dd>
--- bind9-9.7.2.dfsg.P3/doc/arm/man.nsupdate.html       2010-08-20 
04:40:25.000000000 +0200
+++ bind9-9.7.2.dfsg.P3/doc/arm/man.nsupdate.html       2010-12-11 
16:26:03.438008039 +0100
@@ -104,14 +104,14 @@
       the appropriate algorithm as well as the key when authenticating
       each other.  For instance, suitable <span class="type">key</span> and
       <span class="type">server</span> statements would be added to
-      <code class="filename">/etc/named.conf</code> so that the name server
+      <code class="filename">/etc/bind/named.conf</code> so that the name 
server
       can associate the appropriate secret key and algorithm with
       the IP address of the client application that will be using
       TSIG authentication.  SIG(0) uses public key cryptography.
       To use a SIG(0) key, the public key must be stored in a KEY
       record in a zone served by the name server.
       <span><strong class="command">nsupdate</strong></span> does not read
-      <code class="filename">/etc/named.conf</code>.
+      <code class="filename">/etc/bind/named.conf</code>.
     </p>
 <p>
       GSS-TSIG uses Kerberos credentials.  Standard GSS-TSIG mode
--- bind9-9.7.2.dfsg.P3/doc/arm/Bv9ARM.ch03.html        2010-08-17 
02:08:26.000000000 +0200
+++ bind9-9.7.2.dfsg.P3/doc/arm/Bv9ARM.ch03.html        2010-12-11 
16:26:03.445984189 +0100
@@ -729,12 +729,12 @@
                   there is no way to provide that secret other than with a
                   configuration file.  The default location for the
                   <span><strong class="command">rndc</strong></span> 
configuration file is
-                  <code class="filename">/etc/rndc.conf</code>, but an
+                  <code class="filename">/etc/bind/rndc.conf</code>, but an
                   alternate
                   location can be specified with the <code 
class="option">-c</code>
                   option.  If the configuration file is not found,
                   <span><strong class="command">rndc</strong></span> will also 
look in
-                  <code class="filename">/etc/rndc.key</code> (or whatever
+                  <code class="filename">/etc/bind/rndc.key</code> (or whatever
                   <code class="varname">sysconfdir</code> was defined when
                   the <acronym class="acronym">BIND</acronym> build was
                   configured).
@@ -830,7 +830,7 @@
 };
 </pre>
 <p>
-                  This file, if installed as <code 
class="filename">/etc/rndc.conf</code>,
+                  This file, if installed as <code 
class="filename">/etc/bind/rndc.conf</code>,
                   would allow the command:
                 </p>
 <p>
--- bind9-9.7.2.dfsg.P3/doc/arm/man.rndc.html   2010-08-20 04:40:25.000000000 
+0200
+++ bind9-9.7.2.dfsg.P3/doc/arm/man.rndc.html   2010-12-11 16:26:03.449984175 
+0100
@@ -92,14 +92,14 @@
 <dd><p>
             Use <em class="replaceable"><code>config-file</code></em>
             as the configuration file instead of the default,
-            <code class="filename">/etc/rndc.conf</code>.
+            <code class="filename">/etc/bind/rndc.conf</code>.
           </p></dd>
 <dt><span class="term">-k <em 
class="replaceable"><code>key-file</code></em></span></dt>
 <dd><p>
             Use <em class="replaceable"><code>key-file</code></em>
             as the key file instead of the default,
-            <code class="filename">/etc/rndc.key</code>.  The key in
-            <code class="filename">/etc/rndc.key</code> will be used to
+            <code class="filename">/etc/bind/rndc.key</code>.  The key in
+            <code class="filename">/etc/bind/rndc.key</code> will be used to
             authenticate
             commands sent to the server if the <em 
class="replaceable"><code>config-file</code></em>
             does not exist.
--- bind9-9.7.2.dfsg.P3/doc/arm/man.named-checkconf.html        2010-08-20 
04:40:26.000000000 +0200
+++ bind9-9.7.2.dfsg.P3/doc/arm/man.named-checkconf.html        2010-12-11 
16:26:03.457983340 +0100
@@ -55,7 +55,7 @@
       checks the syntax, but not the semantics, of a
       <span><strong class="command">named</strong></span> configuration file.  
The file is parsed
       and checked for syntax errors, along with all files included by it.
-      If no file is specified, <code class="filename">/etc/named.conf</code> 
is read
+      If no file is specified, <code 
class="filename">/etc/bind/named.conf</code> is read
       by default.
     </p>
 <p>
@@ -104,7 +104,7 @@
 <dt><span class="term">filename</span></dt>
 <dd><p>
             The name of the configuration file to be checked.  If not
-            specified, it defaults to <code 
class="filename">/etc/named.conf</code>.
+            specified, it defaults to <code 
class="filename">/etc/bind/named.conf</code>.
           </p></dd>
 </dl></div>
 </div>
--- bind9-9.7.2.dfsg.P3/bin/rndc/rndc.docbook   2007-12-14 21:39:14.000000000 
+0100
+++ bind9-9.7.2.dfsg.P3/bin/rndc/rndc.docbook   2010-12-11 16:26:03.461985008 
+0100
@@ -115,7 +115,7 @@
           <para>
             Use <replaceable class="parameter">config-file</replaceable>
             as the configuration file instead of the default,
-            <filename>/etc/rndc.conf</filename>.
+            <filename>/etc/bind/rndc.conf</filename>.
           </para>
         </listitem>
       </varlistentry>
@@ -126,8 +126,8 @@
           <para>
             Use <replaceable class="parameter">key-file</replaceable>
             as the key file instead of the default,
-            <filename>/etc/rndc.key</filename>.  The key in
-            <filename>/etc/rndc.key</filename> will be used to
+            <filename>/etc/bind/rndc.key</filename>.  The key in
+            <filename>/etc/bind/rndc.key</filename> will be used to
             authenticate
             commands sent to the server if the <replaceable 
class="parameter">config-file</replaceable>
             does not exist.
--- bind9-9.7.2.dfsg.P3/bin/rndc/rndc.8 2009-07-11 03:12:46.000000000 +0200
+++ bind9-9.7.2.dfsg.P3/bin/rndc/rndc.8 2010-12-11 16:26:03.469984730 +0100
@@ -65,7 +65,7 @@
 Use
 \fIconfig\-file\fR
 as the configuration file instead of the default,
-\fI/etc/rndc.conf\fR.
+\fI/etc/bind/rndc.conf\fR.
 .RE
 .PP
 \-k \fIkey\-file\fR
@@ -73,8 +73,8 @@
 Use
 \fIkey\-file\fR
 as the key file instead of the default,
-\fI/etc/rndc.key\fR. The key in
-\fI/etc/rndc.key\fR
+\fI/etc/bind/rndc.key\fR. The key in
+\fI/etc/bind/rndc.key\fR
 will be used to authenticate commands sent to the server if the
 \fIconfig\-file\fR
 does not exist.
--- bind9-9.7.2.dfsg.P3/bin/rndc/rndc.html      2009-07-11 03:12:46.000000000 
+0200
+++ bind9-9.7.2.dfsg.P3/bin/rndc/rndc.html      2010-12-11 16:26:03.473983359 
+0100
@@ -74,14 +74,14 @@
 <dd><p>
             Use <em class="replaceable"><code>config-file</code></em>
             as the configuration file instead of the default,
-            <code class="filename">/etc/rndc.conf</code>.
+            <code class="filename">/etc/bind/rndc.conf</code>.
           </p></dd>
 <dt><span class="term">-k <em 
class="replaceable"><code>key-file</code></em></span></dt>
 <dd><p>
             Use <em class="replaceable"><code>key-file</code></em>
             as the key file instead of the default,
-            <code class="filename">/etc/rndc.key</code>.  The key in
-            <code class="filename">/etc/rndc.key</code> will be used to
+            <code class="filename">/etc/bind/rndc.key</code>.  The key in
+            <code class="filename">/etc/bind/rndc.key</code> will be used to
             authenticate
             commands sent to the server if the <em 
class="replaceable"><code>config-file</code></em>
             does not exist.
--- bind9-9.7.2.dfsg.P3/bin/named/named.html    2009-10-06 03:14:41.000000000 
+0200
+++ bind9-9.7.2.dfsg.P3/bin/named/named.html    2010-12-11 16:26:03.481984023 
+0100
@@ -42,7 +42,7 @@
       When invoked without arguments, <span><strong 
class="command">named</strong></span>
       will
       read the default configuration file
-      <code class="filename">/etc/named.conf</code>, read any initial
+      <code class="filename">/etc/bind/named.conf</code>, read any initial
       data, and listen for queries.
     </p>
 </div>
@@ -65,7 +65,7 @@
 <dd><p>
             Use <em class="replaceable"><code>config-file</code></em> as the
             configuration file instead of the default,
-            <code class="filename">/etc/named.conf</code>.  To
+            <code class="filename">/etc/bind/named.conf</code>.  To
             ensure that reloading the configuration file continues
             to work after the server has changed its working
             directory due to to a possible
@@ -268,7 +268,7 @@
 <div class="refsect1" lang="en">
 <a name="id2544046"></a><h2>FILES</h2>
 <div class="variablelist"><dl>
-<dt><span class="term"><code 
class="filename">/etc/named.conf</code></span></dt>
+<dt><span class="term"><code 
class="filename">/etc/bind/named.conf</code></span></dt>
 <dd><p>
             The default configuration file.
           </p></dd>
--- bind9-9.7.2.dfsg.P3/bin/named/named.docbook 2009-10-05 19:30:49.000000000 
+0200
+++ bind9-9.7.2.dfsg.P3/bin/named/named.docbook 2010-12-11 16:26:03.489983119 
+0100
@@ -87,7 +87,7 @@
       When invoked without arguments, <command>named</command>
       will
       read the default configuration file
-      <filename>/etc/named.conf</filename>, read any initial
+      <filename>/etc/bind/named.conf</filename>, read any initial
       data, and listen for queries.
     </para>
   </refsect1>
@@ -124,7 +124,7 @@
           <para>
             Use <replaceable class="parameter">config-file</replaceable> as the
             configuration file instead of the default,
-            <filename>/etc/named.conf</filename>.  To
+            <filename>/etc/bind/named.conf</filename>.  To
             ensure that reloading the configuration file continues
             to work after the server has changed its working
             directory due to to a possible
@@ -408,7 +408,7 @@
     <variablelist>
 
       <varlistentry>
-        <term><filename>/etc/named.conf</filename></term>
+        <term><filename>/etc/bind/named.conf</filename></term>
         <listitem>
           <para>
             The default configuration file.
--- bind9-9.7.2.dfsg.P3/bin/named/named.conf.html       2010-05-15 
04:41:59.000000000 +0200
+++ bind9-9.7.2.dfsg.P3/bin/named/named.conf.html       2010-12-11 
16:26:03.498037737 +0100
@@ -595,7 +595,7 @@
 </div>
 <div class="refsect1" lang="en">
 <a name="id2545521"></a><h2>FILES</h2>
-<p><code class="filename">/etc/named.conf</code>
+<p><code class="filename">/etc/bind/named.conf</code>
     </p>
 </div>
 <div class="refsect1" lang="en">
--- bind9-9.7.2.dfsg.P3/bin/named/named.8       2009-10-06 03:14:41.000000000 
+0200
+++ bind9-9.7.2.dfsg.P3/bin/named/named.8       2010-12-11 16:26:03.501986369 
+0100
@@ -42,7 +42,7 @@
 When invoked without arguments,
 \fBnamed\fR
 will read the default configuration file
-\fI/etc/named.conf\fR, read any initial data, and listen for queries.
+\fI/etc/bind/named.conf\fR, read any initial data, and listen for queries.
 .SH "OPTIONS"
 .PP
 \-4
@@ -68,7 +68,7 @@
 Use
 \fIconfig\-file\fR
 as the configuration file instead of the default,
-\fI/etc/named.conf\fR. To ensure that reloading the configuration file 
continues to work after the server has changed its working directory due to to 
a possible
+\fI/etc/bind/named.conf\fR. To ensure that reloading the configuration file 
continues to work after the server has changed its working directory due to to 
a possible
 \fBdirectory\fR
 option in the configuration file,
 \fIconfig\-file\fR
@@ -243,7 +243,7 @@
 process.
 .SH "FILES"
 .PP
-\fI/etc/named.conf\fR
+\fI/etc/bind/named.conf\fR
 .RS 4
 The default configuration file.
 .RE
--- bind9-9.7.2.dfsg.P3/bin/named/named.conf.5  2010-05-15 04:41:59.000000000 
+0200
+++ bind9-9.7.2.dfsg.P3/bin/named/named.conf.5  2010-12-11 16:26:03.509989382 
+0100
@@ -562,7 +562,7 @@
 .RE
 .SH "FILES"
 .PP
-\fI/etc/named.conf\fR
+\fI/etc/bind/named.conf\fR
 .SH "SEE ALSO"
 .PP
 \fBnamed\fR(8),
--- bind9-9.7.2.dfsg.P3/bin/named/named.conf.docbook    2010-05-15 
01:49:18.000000000 +0200
+++ bind9-9.7.2.dfsg.P3/bin/named/named.conf.docbook    2010-12-11 
16:26:03.517984341 +0100
@@ -631,7 +631,7 @@
 
   <refsect1>
     <title>FILES</title>
-    <para><filename>/etc/named.conf</filename>
+    <para><filename>/etc/bind/named.conf</filename>
     </para>
   </refsect1>
 
--- bind9-9.7.2.dfsg.P3/bin/check/named-checkconf.html  2009-12-29 
03:09:33.000000000 +0100
+++ bind9-9.7.2.dfsg.P3/bin/check/named-checkconf.html  2010-12-11 
16:26:03.525983955 +0100
@@ -37,7 +37,7 @@
       checks the syntax, but not the semantics, of a
       <span><strong class="command">named</strong></span> configuration file.  
The file is parsed
       and checked for syntax errors, along with all files included by it.
-      If no file is specified, <code class="filename">/etc/named.conf</code> 
is read
+      If no file is specified, <code 
class="filename">/etc/bind/named.conf</code> is read
       by default.
     </p>
 <p>
@@ -86,7 +86,7 @@
 <dt><span class="term">filename</span></dt>
 <dd><p>
             The name of the configuration file to be checked.  If not
-            specified, it defaults to <code 
class="filename">/etc/named.conf</code>.
+            specified, it defaults to <code 
class="filename">/etc/bind/named.conf</code>.
           </p></dd>
 </dl></div>
 </div>
--- bind9-9.7.2.dfsg.P3/bin/check/named-checkconf.8     2009-12-29 
03:09:32.000000000 +0100
+++ bind9-9.7.2.dfsg.P3/bin/check/named-checkconf.8     2010-12-11 
16:26:03.529985363 +0100
@@ -40,7 +40,7 @@
 checks the syntax, but not the semantics, of a
 \fBnamed\fR
 configuration file. The file is parsed and checked for syntax errors, along 
with all files included by it. If no file is specified,
-\fI/etc/named.conf\fR
+\fI/etc/bind/named.conf\fR
 is read by default.
 .PP
 Note: files that
@@ -98,7 +98,7 @@
 filename
 .RS 4
 The name of the configuration file to be checked. If not specified, it 
defaults to
-\fI/etc/named.conf\fR.
+\fI/etc/bind/named.conf\fR.
 .RE
 .SH "RETURN VALUES"
 .PP
--- bind9-9.7.2.dfsg.P3/bin/check/named-checkconf.docbook       2009-12-29 
00:21:44.000000000 +0100
+++ bind9-9.7.2.dfsg.P3/bin/check/named-checkconf.docbook       2010-12-11 
16:26:03.537983215 +0100
@@ -70,7 +70,7 @@
       checks the syntax, but not the semantics, of a
       <command>named</command> configuration file.  The file is parsed
       and checked for syntax errors, along with all files included by it.
-      If no file is specified, <filename>/etc/named.conf</filename> is read
+      If no file is specified, <filename>/etc/bind/named.conf</filename> is 
read
       by default.
     </para>
     <para>
@@ -153,7 +153,7 @@
         <listitem>
           <para>
             The name of the configuration file to be checked.  If not
-            specified, it defaults to <filename>/etc/named.conf</filename>.
+            specified, it defaults to 
<filename>/etc/bind/named.conf</filename>.
           </para>
         </listitem>
       </varlistentry>
--- bind9-9.7.2.dfsg.P3/bin/nsupdate/nsupdate.docbook   2010-07-10 
01:46:27.000000000 +0200
+++ bind9-9.7.2.dfsg.P3/bin/nsupdate/nsupdate.docbook   2010-12-11 
16:26:03.541986749 +0100
@@ -129,14 +129,14 @@
       the appropriate algorithm as well as the key when authenticating
       each other.  For instance, suitable <type>key</type> and
       <type>server</type> statements would be added to
-      <filename>/etc/named.conf</filename> so that the name server
+      <filename>/etc/bind/named.conf</filename> so that the name server
       can associate the appropriate secret key and algorithm with
       the IP address of the client application that will be using
       TSIG authentication.  SIG(0) uses public key cryptography.
       To use a SIG(0) key, the public key must be stored in a KEY
       record in a zone served by the name server.
       <command>nsupdate</command> does not read
-      <filename>/etc/named.conf</filename>.
+      <filename>/etc/bind/named.conf</filename>.
     </para>
     <para>
       GSS-TSIG uses Kerberos credentials.  Standard GSS-TSIG mode
--- bind9-9.7.2.dfsg.P3/bin/nsupdate/nsupdate.1 2010-07-10 04:41:30.000000000 
+0200
+++ bind9-9.7.2.dfsg.P3/bin/nsupdate/nsupdate.1 2010-12-11 16:26:03.545983408 
+0100
@@ -71,11 +71,11 @@
 and
 \fBserver\fR
 statements would be added to
-\fI/etc/named.conf\fR
+\fI/etc/bind/named.conf\fR
 so that the name server can associate the appropriate secret key and algorithm 
with the IP address of the client application that will be using TSIG 
authentication. SIG(0) uses public key cryptography. To use a SIG(0) key, the 
public key must be stored in a KEY record in a zone served by the name server.
 \fBnsupdate\fR
 does not read
-\fI/etc/named.conf\fR.
+\fI/etc/bind/named.conf\fR.
 .PP
 GSS\-TSIG uses Kerberos credentials. Standard GSS\-TSIG mode is switched on 
with the
 \fB\-g\fR
--- bind9-9.7.2.dfsg.P3/bin/nsupdate/nsupdate.html      2010-07-10 
04:41:30.000000000 +0200
+++ bind9-9.7.2.dfsg.P3/bin/nsupdate/nsupdate.html      2010-12-11 
16:26:03.549981915 +0100
@@ -86,14 +86,14 @@
       the appropriate algorithm as well as the key when authenticating
       each other.  For instance, suitable <span class="type">key</span> and
       <span class="type">server</span> statements would be added to
-      <code class="filename">/etc/named.conf</code> so that the name server
+      <code class="filename">/etc/bind/named.conf</code> so that the name 
server
       can associate the appropriate secret key and algorithm with
       the IP address of the client application that will be using
       TSIG authentication.  SIG(0) uses public key cryptography.
       To use a SIG(0) key, the public key must be stored in a KEY
       record in a zone served by the name server.
       <span><strong class="command">nsupdate</strong></span> does not read
-      <code class="filename">/etc/named.conf</code>.
+      <code class="filename">/etc/bind/named.conf</code>.
     </p>
 <p>
       GSS-TSIG uses Kerberos credentials.  Standard GSS-TSIG mode

--- End Message ---
--- Begin Message ---
Version: bind9/1:9.18.1-1

On 21/05/21 05:27 PM, Athos Ribeiro wrote:

> This bug is still valid in unstable. However, the patch provided
> previously no longer applies for the issue.
> 
> I filed a MR in salsa [1] and forwarded the patch upstream [2].
> 
> [1] https://salsa.debian.org/dns-team/bind9/-/merge_requests/16
> [2] https://gitlab.isc.org/isc-projects/bind9/-/issues/2717

This has been fixed upstream in 9.18.1, thanks.

Bernhard

--- End Message ---

Reply via email to