Michał Kępień
dfdd3a8a2f
Every DocBook source document can be namespaced (DocBook 5) or
non-namespaced (DocBook 4). The set of XSL stylesheets used for
producing an output document can also be namespaced or non-namespaced.
Namespaced source documents should be used with namespaced stylesheets
and non-namespaced source documents should be used with non-namespaced
stylesheets. However, both stylesheet flavors contain processing rules
which allow them to be used interchangeably for any type of source
document.
Unfortunately, these processing rules became broken in version 1.79.1 of
the stylesheets, which means that non-namespaced source documents can no
longer be correctly transformed into man pages using namespaced
stylesheets and vice versa. This problem was fixed upstream [1], but no
released version of the XSL stylesheets contains that fix yet.
Back in 2016, this problem was reported as RT #43831 and allegedly fixed
in commit 1b8ce3b330. However, that fix
only helped for the non-namespaced version of the stylesheets - while
also breaking man page generation for the namespaced flavor.
Since using namespaced DocBook sources is the current best practice
(DocBook 5), make BIND DocBook sources namespaced again. When using
version 1.79.1 or 1.79.2 of the XSL stylesheets, care must be taken to
ensure namespaced stylesheets are used for generating BIND
documentation.
[1] https://github.com/docbook/xslt10-stylesheets/issues/109
394 lines
10 KiB
XML
394 lines
10 KiB
XML
<!--
|
|
- Copyright (C) Internet Systems Consortium, Inc. ("ISC")
|
|
-
|
|
- This Source Code Form is subject to the terms of the Mozilla Public
|
|
- License, v. 2.0. If a copy of the MPL was not distributed with this
|
|
- file, you can obtain one at https://mozilla.org/MPL/2.0/.
|
|
-
|
|
- See the COPYRIGHT file distributed with this work for additional
|
|
- information regarding copyright ownership.
|
|
-->
|
|
|
|
<!-- Converted by db4-upgrade version 1.0 -->
|
|
<informaltable xmlns="http://docbook.org/ns/docbook" version="5.0" colsep="0" rowsep="0">
|
|
<tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
|
|
<colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
|
|
<colspec colname="2" colnum="2" colsep="0" colwidth="3.350in"/>
|
|
<tbody>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>client</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Processing of client requests.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>cname</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Name servers that are skipped for being
|
|
a CNAME rather than A/AAAA records.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>config</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Configuration file parsing and processing.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>database</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Messages relating to the databases used
|
|
internally by the name server to store zone and cache
|
|
data.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>default</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Logging
|
|
options for those categories where no specific
|
|
configuration has been
|
|
defined.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>delegation-only</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Queries that have been
|
|
forced to NXDOMAIN as the result of a
|
|
delegation-only zone or a
|
|
<command>delegation-only</command> in a
|
|
forward, hint, or stub zone declaration.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>dispatch</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Dispatching of incoming packets to the
|
|
server modules where they are to be processed.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>dnssec</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
DNSSEC and TSIG protocol processing.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>dnstap</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
The "dnstap" DNS traffic capture system.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>edns-disabled</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Log queries that have been forced to use plain
|
|
DNS due to timeouts. This is often due to
|
|
the remote servers not being RFC 1034-compliant
|
|
(not always returning FORMERR or similar to
|
|
EDNS queries and other extensions to the DNS
|
|
when they are not understood). In other words, this is
|
|
targeted at servers that fail to respond to
|
|
DNS queries that they don't understand.
|
|
</para>
|
|
<para>
|
|
Note: the log message can also be due to
|
|
packet loss. Before reporting servers for
|
|
non-RFC 1034 compliance they should be re-tested
|
|
to determine the nature of the non-compliance.
|
|
This testing should prevent or reduce the
|
|
number of false-positive reports.
|
|
</para>
|
|
<para>
|
|
Note: eventually <command>named</command> will have to stop
|
|
treating such timeouts as due to RFC 1034
|
|
non-compliance and start treating it as plain
|
|
packet loss. Falsely classifying packet
|
|
loss as due to RFC 1034 non-compliance impacts
|
|
DNSSEC validation, which requires EDNS for
|
|
the DNSSEC records to be returned.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>general</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Catch-all for many things that still are not
|
|
classified into categories.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>lame-servers</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Misconfigurations
|
|
in remote servers, discovered by <acronym>BIND</acronym> 9 when trying to
|
|
query those servers during resolution.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>network</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Network operations.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>notify</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
The NOTIFY protocol.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>queries</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Location where queries should be logged.
|
|
</para>
|
|
<para>
|
|
At startup, specifying the category <command>queries</command> also
|
|
enables query logging unless <command>querylog</command> option has been
|
|
specified.
|
|
</para>
|
|
|
|
<para>
|
|
The query log entry first reports a client object
|
|
identifier in @0x<hexadecimal-number>
|
|
format. Next, it reports the client's IP
|
|
address and port number, and the query name,
|
|
class, and type. Next, it reports whether the
|
|
Recursion Desired flag was set (+ if set, -
|
|
if not set), whether the query was signed (S),
|
|
whether EDNS was in use along with the EDNS version
|
|
number (E(#)), whether TCP was used (T), whether DO
|
|
(DNSSEC Ok) was set (D), whether CD (Checking
|
|
Disabled) was set (C), whether a valid DNS Server
|
|
COOKIE was received (V), and whether a DNS COOKIE
|
|
option without a valid Server COOKIE was
|
|
present (K). After this, the destination
|
|
address the query was sent to is reported.
|
|
</para>
|
|
|
|
<para>
|
|
<computeroutput>client 127.0.0.1#62536 (www.example.com): query: www.example.com IN AAAA +SE</computeroutput>
|
|
</para>
|
|
<para>
|
|
<computeroutput>client ::1#62537 (www.example.net): query: www.example.net IN AAAA -SE</computeroutput>
|
|
</para>
|
|
<para>
|
|
The first part of this log message, showing the
|
|
client address/port number and query name, is
|
|
repeated in all subsequent log messages related
|
|
to the same query.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>query-errors</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Information about queries that resulted in some
|
|
failure.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>rate-limit</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
The start, periodic, and final notices of the
|
|
rate limiting of a stream of responses are logged at
|
|
<command>info</command> severity in this category.
|
|
These messages include a hash value of the domain name
|
|
of the response and the name itself,
|
|
except when there is insufficient memory to record
|
|
the name for the final notice.
|
|
The final notice is normally delayed until about one
|
|
minute after rate limiting stops.
|
|
A lack of memory can hurry the final notice,
|
|
which is indicated by an initial asterisk (*).
|
|
Various internal events are logged at debug level 1
|
|
and higher.
|
|
</para>
|
|
<para>
|
|
Rate limiting of individual requests
|
|
is logged in the <command>query-errors</command> category.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>resolver</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
DNS resolution, such as the recursive
|
|
lookups performed on behalf of clients by a caching name
|
|
server.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>rpz</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Information about errors in response policy zone files,
|
|
rewritten responses, and, at the highest
|
|
<command>debug</command> levels, mere rewriting
|
|
attempts.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>security</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Approval and denial of requests.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>spill</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Queries that have been terminated, either by dropping
|
|
or responding with SERVFAIL, as a result of a fetchlimit
|
|
quota being exceeded.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>trust-anchor-telemetry</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Trust-anchor-telemetry requests received by <command>named</command>.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>unmatched</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Messages that <command>named</command> was unable to determine the
|
|
class of, or for which there was no matching <command>view</command>.
|
|
A one-line summary is also logged to the <command>client</command> category.
|
|
This category is best sent to a file or stderr; by
|
|
default it is sent to
|
|
the <command>null</command> channel.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>update</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Dynamic updates.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>update-security</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Approval and denial of update requests.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>xfer-in</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Zone transfers the server is receiving.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
<row rowsep="0">
|
|
<entry colname="1">
|
|
<para><command>xfer-out</command></para>
|
|
</entry>
|
|
<entry colname="2">
|
|
<para>
|
|
Zone transfers the server is sending.
|
|
</para>
|
|
</entry>
|
|
</row>
|
|
</tbody>
|
|
</tgroup>
|
|
</informaltable>
|