<html><head><metahttp-equiv="Content-Type"content="text/html; charset=ISO-8859-1"><title>BIND 10 Messages Manual</title><linkrel="stylesheet"href="./bind10-guide.css"type="text/css"><metaname="generator"content="DocBook XSL Stylesheets V1.75.2"><metaname="description"content="BIND 10 is a Domain Name System (DNS) suite managed by Internet Systems Consortium (ISC). It includes DNS libraries and modular components for controlling authoritative and recursive DNS servers. This is the messages manual for BIND 10 version 20120405. The most up-to-date version of this document, along with other documents for BIND 10, can be found at ."></head><bodybgcolor="white"text="black"link="#0000FF"vlink="#840084"alink="#0000FF"><divclass="book"title="BIND 10 Messages Manual"><divclass="titlepage"><div><div><h1class="title"><aname="id1168229451102"></a>BIND 10 Messages Manual</h1></div><div><pclass="releaseinfo">This is the messages manual for BIND 10 version
<html><head><metahttp-equiv="Content-Type"content="text/html; charset=ISO-8859-1"><title>BIND 10 Messages Manual</title><linkrel="stylesheet"href="./bind10-guide.css"type="text/css"><metaname="generator"content="DocBook XSL Stylesheets V1.75.2"><metaname="description"content="BIND 10 is a Domain Name System (DNS) suite managed by Internet Systems Consortium (ISC). It includes DNS libraries and modular components for controlling authoritative and recursive DNS servers. This is the messages manual for BIND 10 version 20120712. The most up-to-date version of this document, along with other documents for BIND 10, can be found at ."></head><bodybgcolor="white"text="black"link="#0000FF"vlink="#840084"alink="#0000FF"><divclass="book"title="BIND 10 Messages Manual"><divclass="titlepage"><div><div><h1class="title"><aname="id1168229451102"></a>BIND 10 Messages Manual</h1></div><div><pclass="releaseinfo">This is the messages manual for BIND 10 version
This is a debug message issued when the authoritative server has received
a command on the command channel.
</p></dd><dt><aname="AUTH_RECEIVED_NOTIFY"></a><spanclass="term">AUTH_RECEIVED_NOTIFY received incoming NOTIFY for zone name %1, zone class %2</span></dt><dd><p>
This is a debug message reporting that an incoming NOTIFY was received.
This is a debug message, produced when a received DNS packet being
processed by the authoritative server has been found to contain an
...
...
@@ -1089,6 +1105,12 @@ not contain RRs the requested type. AN NXRRSET indication is returned.
</p></dd><dt><aname="DATASRC_DO_QUERY"></a><spanclass="term">DATASRC_DO_QUERY handling query for '%1/%2'</span></dt><dd><p>
A debug message indicating that a query for the given name and RR type is being
processed.
</p></dd><dt><aname="DATASRC_LIST_NOT_CACHED"></a><spanclass="term">DATASRC_LIST_NOT_CACHED zone %1/%2 not cached, cache disabled globally. Will not be available.</span></dt><dd><p>
The process disabled caching of RR data completely. However, the given zone
is provided as a master file and it can be served from memory cache only.
Therefore, the zone will not be available for this process. If this is
a problem, you should move the zone to some database backend (sqlite3, for
example) and use it from there.
</p></dd><dt><aname="DATASRC_MEM_ADD_RRSET"></a><spanclass="term">DATASRC_MEM_ADD_RRSET adding RRset '%1/%2' into zone '%3'</span></dt><dd><p>
Debug information. An RRset is being added to the in-memory data source.
</p></dd><dt><aname="DATASRC_MEM_ADD_WILDCARD"></a><spanclass="term">DATASRC_MEM_ADD_WILDCARD adding wildcards for '%1'</span></dt><dd><p>
...
...
@@ -1693,12 +1715,45 @@ be completed, after which the process will exit.
</p></dd><dt><aname="DDNS_STARTED"></a><spanclass="term">DDNS_STARTED ddns server is running and listening for updates</span></dt><dd><p>
The ddns process has successfully started and is now ready to receive commands
and updates.
</p></dd><dt><aname="DDNS_START_FORWARDER_ERROR"></a><spanclass="term">DDNS_START_FORWARDER_ERROR Error from b10-auth when requesting DDNS UPDATE forwarding: %1</span></dt><dd><p>
There was an error response from b10-auth to the command to start
forwarding DDNS UPDATE messages to b10-ddns.
It is almost certain that DDNS UPDATE messages are not handled now, and that
they will be responded to with a NOTIMP error code, even though b10-ddns is
running.
The error message is printed, and additional information may be found in
the b10-auth log output. Since this is an error that is sent by the
b10-auth module, it should have more information as to what the actual
problem was.
</p></dd><dt><aname="DDNS_START_FORWARDER_FAIL"></a><spanclass="term">DDNS_START_FORWARDER_FAIL Error sending request for DDNS UPDATE forwarding to b10-auth: %1</span></dt><dd><p>
There was an error when attempting to send b10-auth the request to forward
DDNS UPDATE messages to the b10-ddns module. This points to an internal
problem using the inter-module messaging system.
This needs to be inspected, as it is almost certain that DDNS UPDATE messages
are not handled now.
The specific error is printed in the log message.
</p></dd><dt><aname="DDNS_STOPPED"></a><spanclass="term">DDNS_STOPPED ddns server has stopped</span></dt><dd><p>
The ddns process has successfully stopped and is no longer listening for or
There was a keyboard interrupt signal to stop the ddns process. The
process will now shut down.
</p></dd><dt><aname="DDNS_STOP_FORWARDER_ERROR"></a><spanclass="term">DDNS_STOP_FORWARDER_ERROR Error from b10-auth when requesting to stop DDNS UPDATE forwarding: %1</span></dt><dd><p>
There was an error response from b10-auth to the command to stop
forwarding DDNS UPDATE messages to b10-ddns.
This specific error may not be fatal; instead of returning NOTIMP for future
DDNS UPDATE messages, it will return SERVFAIL. However, this does point to
an underlying problem in the messaging system, and should be inspected.
The error message is printed, and additional information may be found in
the b10-auth log output.
</p></dd><dt><aname="DDNS_STOP_FORWARDER_FAIL"></a><spanclass="term">DDNS_STOP_FORWARDER_FAIL Error sending request to stop DDNS UPDATE forwarding to b10-auth: %1</span></dt><dd><p>
There was an error when attempting to send b10-auth the request to stop
forwarding DDNS UPDATE messages to the b10-ddns module. This points to an
internal problem using the inter-module messaging system.
This specific error may not be fatal; instead of returning NOTIMP for future
DDNS UPDATE messages, it will return SERVFAIL. However, this does point to
an underlying problem in the messaging system, and should be inspected.
The specific error is printed in the log message.
</p></dd><dt><aname="DDNS_UNCAUGHT_EXCEPTION"></a><spanclass="term">DDNS_UNCAUGHT_EXCEPTION uncaught exception of type %1: %2</span></dt><dd><p>
The b10-ddns process encountered an uncaught exception and will now shut
down. This is indicative of a programming error and should not happen under
...
...
@@ -2169,10 +2224,6 @@ an answer with a different given type and class.
</p><p>
This message indicates an internal error in the NSAS. Please raise a
bug report.
</p></dd><dt><aname="PYSERVER_COMMON_AUTH_CONFIG_NAME_PARSER_ERROR"></a><spanclass="term">PYSERVER_COMMON_AUTH_CONFIG_NAME_PARSER_ERROR Invalid name when parsing Auth configuration: %1</span></dt><dd><p>
There was an invalid name when parsing Auth configuration.
</p></dd><dt><aname="PYSERVER_COMMON_AUTH_CONFIG_RRCLASS_ERROR"></a><spanclass="term">PYSERVER_COMMON_AUTH_CONFIG_RRCLASS_ERROR Invalid RRClass when parsing Auth configuration: %1</span></dt><dd><p>
There was an invalid RR class when parsing Auth configuration.
</p></dd><dt><aname="PYSERVER_COMMON_DNS_TCP_SEND_DONE"></a><spanclass="term">PYSERVER_COMMON_DNS_TCP_SEND_DONE completed sending TCP message to %1 (%2 bytes in total)</span></dt><dd><p>
Debug message. A complete DNS message has been successfully
transmitted over a TCP connection, possibly after multiple send
...
...
@@ -2760,10 +2811,9 @@ is unknown in the implementation. The most likely cause is an
installation problem, where the specification file stats.spec is
from a different version of BIND 10 than the stats module itself.
Please check your installation.
</p></dd><dt><aname="XFRIN_AUTH_LOADZONE"></a><spanclass="term">XFRIN_AUTH_LOADZONE sending Auth loadzone for origin=%1, class=%2, datasrc=%3</span></dt><dd><p>
There was a successful zone transfer, and the zone is served by b10-auth
in the in-memory data source using sqlite3 as a backend. We send the
"loadzone" command for the zone to b10-auth.
</p></dd><dt><aname="XFRIN_AUTH_LOADZONE"></a><spanclass="term">XFRIN_AUTH_LOADZONE sending Auth loadzone for origin=%1, class=%2</span></dt><dd><p>
There was a successful zone transfer. We send the "loadzone" command for the
zone to b10-auth.
</p></dd><dt><aname="XFRIN_AXFR_INCONSISTENT_SOA"></a><spanclass="term">XFRIN_AXFR_INCONSISTENT_SOA AXFR SOAs are inconsistent for %1: %2 expected, %3 received</span></dt><dd><p>
The serial fields of the first and last SOAs of AXFR (including AXFR-style
IXFR) are not the same. According to RFC 5936 these two SOAs must be the
