<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="idp74800"></a>BIND 10 Messages Manual</h1></div><div><pclass="releaseinfo">This is the messages manual for BIND 10 version
20120712.</p></div><div><pclass="copyright">Copyright <20> 2011-2012 Internet Systems Consortium, Inc.</p></div><div><divclass="abstract"title="Abstract"><pclass="title"><b>Abstract</b></p><p>BIND 10 is a Domain Name System (DNS) suite managed by
</p><divclass="variablelist"><dl><dt><aname="ASIODNS_FD_ADD_TCP"></a><spanclass="term">ASIODNS_FD_ADD_TCP adding a new TCP server by opened fd %1</span></dt><dd><p>
A debug message informing about installing a file descriptor as a server.
The file descriptor number is noted.
</p></dd><dt><aname="ASIODNS_FD_ADD_UDP"></a><spanclass="term">ASIODNS_FD_ADD_UDP adding a new UDP server by opened fd %1</span></dt><dd><p>
A debug message informing about installing a file descriptor as a server.
The file descriptor number is noted.
</p></dd><dt><aname="ASIODNS_FETCH_COMPLETED"></a><spanclass="term">ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed</span></dt><dd><p>
</p></dd><dt><aname="ASIODNS_READ_TIMEOUT"></a><spanclass="term">ASIODNS_READ_TIMEOUT receive timeout while waiting for data from %1(%2)</span></dt><dd><p>
An internal consistency check on the origin of a message from the
asynchronous I/O module failed. This may indicate an internal error;
please submit a bug report.
</p></dd><dt><aname="ASIODNS_UNKNOWN_RESULT"></a><spanclass="term">ASIODNS_UNKNOWN_RESULT unknown result (%1) when IOFetch::stop() was executed for I/O to %2(%3)</span></dt><dd><p>
An internal error indicating that the termination method of the resolver's
upstream fetch class was called with an unknown result code (which is
given in the message). Please submit a bug report.
successfully created. It is issued during server startup is an indication
that the initialization is proceeding normally.
</p></dd><dt><aname="AUTH_HEADER_PARSE_FAIL"></a><spanclass="term">AUTH_HEADER_PARSE_FAIL unable to parse header in received DNS packet: %1</span></dt><dd><p>
This is a debug message, generated by the authoritative server when an
attempt to parse the header of a received DNS packet has failed. (The
reason for the failure is given in the message.) The server will drop the
</p></dd><dt><aname="AUTH_INVALID_STATISTICS_DATA"></a><spanclass="term">AUTH_INVALID_STATISTICS_DATA invalid specification of statistics data specified</span></dt><dd><p>
An error was encountered when the authoritiative server specified
statistics data which is invalid for the auth specification file.
has requested the keyring holding TSIG keys from the configuration
database. It is issued during server startup is an indication that the
initialization is proceeding normally.
</p></dd><dt><aname="AUTH_LOAD_ZONE"></a><spanclass="term">AUTH_LOAD_ZONE loaded zone %1/%2</span></dt><dd><p>
This debug message is issued during the processing of the 'loadzone' command
when the authoritative server has successfully loaded the named zone of the
named class.
</p></dd><dt><aname="AUTH_MEM_DATASRC_DISABLED"></a><spanclass="term">AUTH_MEM_DATASRC_DISABLED memory data source is disabled for class %1</span></dt><dd><p>
This is a debug message reporting that the authoritative server has
discovered that the memory data source is disabled for the given class.
</p></dd><dt><aname="AUTH_MEM_DATASRC_ENABLED"></a><spanclass="term">AUTH_MEM_DATASRC_ENABLED memory data source is enabled for class %1</span></dt><dd><p>
This is a debug message reporting that the authoritative server has
discovered that the memory data source is enabled for the given class.
</p></dd><dt><aname="AUTH_MESSAGE_FORWARD_ERROR"></a><spanclass="term">AUTH_MESSAGE_FORWARD_ERROR failed to forward %1 request from %2: %3</span></dt><dd><p>
The authoritative server tried to forward some type DNS request
message to a separate process (e.g., forwarding dynamic update
requests to b10-ddns) to handle it, but it failed. The authoritative
server returns SERVFAIL to the client on behalf of the separate
process. The error could be configuration mismatch between b10-auth
and the recipient component, or it may be because the requests are
coming too fast and the receipient process cannot keep up with the
rate, or some system level failure. In either case this means the
BIND 10 system is not working as expected, so the administrator should
look into the cause and address the issue. The log message includes
the client's address (and port), and the error message sent from the
</p></dd><dt><aname="AUTH_NOTIFY_QUESTIONS"></a><spanclass="term">AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY</span></dt><dd><p>
This debug message is logged by the authoritative server when it receives
a NOTIFY packet that contains zero or more than one question. (A valid
NOTIFY packet contains one question.) The server will return a FORMERR
error to the sender.
</p></dd><dt><aname="AUTH_NOTIFY_RRTYPE"></a><spanclass="term">AUTH_NOTIFY_RRTYPE invalid question RR type (%1) in incoming NOTIFY</span></dt><dd><p>
This debug message is logged by the authoritative server when it receives
a NOTIFY packet that an RR type of something other than SOA in the
question section. (The RR type received is included in the message.) The
server will return a FORMERR error to the sender.
</p></dd><dt><aname="AUTH_NO_STATS_SESSION"></a><spanclass="term">AUTH_NO_STATS_SESSION session interface for statistics is not available</span></dt><dd><p>
The authoritative server had no session with the statistics module at the
time it attempted to send it data: the attempt has been abandoned. This
could be an error in configuration.
</p></dd><dt><aname="AUTH_NO_XFRIN"></a><spanclass="term">AUTH_NO_XFRIN received NOTIFY but XFRIN session is not running</span></dt><dd><p>
This is a debug message produced by the authoritative server when it receives
a NOTIFY packet but the XFRIN process is not running. The packet will be
dropped and nothing returned to the sender.
</p></dd><dt><aname="AUTH_PACKET_PARSE_ERROR"></a><spanclass="term">AUTH_PACKET_PARSE_ERROR unable to parse received DNS packet: %1</span></dt><dd><p>
This is a debug message, generated by the authoritative server when an
attempt to parse a received DNS packet has failed due to something other
than a protocol error. The reason for the failure is given in the message;
the server will return a SERVFAIL error code to the sender.
</p></dd><dt><aname="AUTH_PACKET_PROTOCOL_ERROR"></a><spanclass="term">AUTH_PACKET_PROTOCOL_ERROR DNS packet protocol error: %1. Returning %2</span></dt><dd><p>
This is a debug message, generated by the authoritative server when an
attempt to parse a received DNS packet has failed due to a protocol error.
The reason for the failure is given in the message, as is the error code
</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.
</p></dd><dt><aname="AUTH_RESPONSE_FAILURE"></a><spanclass="term">AUTH_RESPONSE_FAILURE exception while building response to query: %1</span></dt><dd><p>
This is a debug message, generated by the authoritative server when an
attempt to create a response to a received DNS packet has failed. The
reason for the failure is given in the log message. A SERVFAIL response
is sent back. The most likely cause of this is an error in the data
source implementation; it is either creating bad responses or raising
exceptions itself.
</p></dd><dt><aname="AUTH_RESPONSE_FAILURE_UNKNOWN"></a><spanclass="term">AUTH_RESPONSE_FAILURE_UNKNOWN unknown exception while building response to query</span></dt><dd><p>
This debug message is similar to AUTH_RESPONSE_FAILURE, but further
details about the error are unknown, because it was signaled by something
which is not an exception. This is definitely a bug.
</p></dd><dt><aname="BIND10_CHECK_MSGQ_ALREADY_RUNNING"></a><spanclass="term">BIND10_CHECK_MSGQ_ALREADY_RUNNING checking if msgq is already running</span></dt><dd><p>
The boss process is starting up and will now check if the message bus
daemon is already running. If so, it will not be able to start, as it
The process terminated, but the bind10 boss didn't expect it to, which means
it must have failed.
</p></dd><dt><aname="BIND10_COMPONENT_RESTART"></a><spanclass="term">BIND10_COMPONENT_RESTART component %1 is about to restart</span></dt><dd><p>
The named component failed previously and we will try to restart it to provide
as flawless service as possible, but it should be investigated what happened,
as it could happen again.
</p></dd><dt><aname="BIND10_COMPONENT_START"></a><spanclass="term">BIND10_COMPONENT_START component %1 is starting</span></dt><dd><p>
The named component is about to be started by the boss process.
</p></dd><dt><aname="BIND10_COMPONENT_START_EXCEPTION"></a><spanclass="term">BIND10_COMPONENT_START_EXCEPTION component %1 failed to start: %2</span></dt><dd><p>
An exception (mentioned in the message) happened during the startup of the
named component. The componet is not considered started and further actions
will be taken about it.
</p></dd><dt><aname="BIND10_COMPONENT_STOP"></a><spanclass="term">BIND10_COMPONENT_STOP component %1 is being stopped</span></dt><dd><p>
A component is about to be asked to stop willingly by the boss.
</p></dd><dt><aname="BIND10_COMPONENT_UNSATISFIED"></a><spanclass="term">BIND10_COMPONENT_UNSATISFIED component %1 is required to run and failed</span></dt><dd><p>
A component failed for some reason (see previous messages). It is either a core
component or needed component that was just started. In any case, the system
can't continue without it and will terminate.
</p></dd><dt><aname="BIND10_CONFIGURATOR_BUILD"></a><spanclass="term">BIND10_CONFIGURATOR_BUILD building plan '%1' -> '%2'</span></dt><dd><p>
A debug message. This indicates that the configurator is building a plan
how to change configuration from the older one to newer one. This does no
real work yet, it just does the planning what needs to be done.
</p></dd><dt><aname="BIND10_CONFIGURATOR_PLAN_INTERRUPTED"></a><spanclass="term">BIND10_CONFIGURATOR_PLAN_INTERRUPTED configurator plan interrupted, only %1 of %2 done</span></dt><dd><p>
There was an exception during some planned task. The plan will not continue and
only some tasks of the plan were completed. The rest is aborted. The exception
A different configuration of which components should be running is being
installed. All components that are no longer needed will be stopped and
newly introduced ones started. This happens at startup, when the configuration
is read the first time, or when an operator changes configuration of the boss.
</p></dd><dt><aname="BIND10_CONFIGURATOR_RUN"></a><spanclass="term">BIND10_CONFIGURATOR_RUN running plan of %1 tasks</span></dt><dd><p>
A debug message. The configurator is about to execute a plan of actions it
computed previously.
</p></dd><dt><aname="BIND10_CONFIGURATOR_START"></a><spanclass="term">BIND10_CONFIGURATOR_START bind10 component configurator is starting up</span></dt><dd><p>
The part that cares about starting and stopping the right component from the
boss process is starting up. This happens only once at the startup of the
boss process. It will start the basic set of processes now (the ones boss
needs to read the configuration), the rest will be started after the
configuration is known.
</p></dd><dt><aname="BIND10_CONFIGURATOR_STOP"></a><spanclass="term">BIND10_CONFIGURATOR_STOP bind10 component configurator is shutting down</span></dt><dd><p>
The part that cares about starting and stopping processes in the boss is
shutting down. All started components will be shut down now (more precisely,
asked to terminate by their own, if they fail to comply, other parts of
the boss process will try to force them).
</p></dd><dt><aname="BIND10_CONFIGURATOR_TASK"></a><spanclass="term">BIND10_CONFIGURATOR_TASK performing task %1 on %2</span></dt><dd><p>
A debug message. The configurator is about to perform one task of the plan it
is currently executing on the named component.
</p></dd><dt><aname="BIND10_INVALID_STATISTICS_DATA"></a><spanclass="term">BIND10_INVALID_STATISTICS_DATA invalid specification of statistics data specified</span></dt><dd><p>
An error was encountered when the boss module specified
statistics data which is invalid for the boss specification file.
</p></dd><dt><aname="BIND10_LOST_SOCKET_CONSUMER"></a><spanclass="term">BIND10_LOST_SOCKET_CONSUMER consumer %1 of sockets disconnected, considering all its sockets closed</span></dt><dd><p>
A connection from one of the applications which requested a socket was
closed. This means the application has terminated, so all the sockets it was
using are now closed and bind10 process can release them as well, unless the
</p></dd><dt><aname="BIND10_NO_SOCKET"></a><spanclass="term">BIND10_NO_SOCKET couldn't send a socket for token %1 because of error: %2</span></dt><dd><p>
An error occurred when the bind10 process was asked to send a socket file
descriptor. The error is mentioned, most common reason is that the request
is invalid and may not come from bind10 process at all.
</p></dd><dt><aname="BIND10_READING_BOSS_CONFIGURATION"></a><spanclass="term">BIND10_READING_BOSS_CONFIGURATION reading boss configuration</span></dt><dd><p>
The boss process is starting up, and will now process the initial
configuration, as received from the configuration manager.
</p></dd><dt><aname="BIND10_RECEIVED_COMMAND"></a><spanclass="term">BIND10_RECEIVED_COMMAND received command: %1</span></dt><dd><p>
The boss module received a command and shall now process it. The command
is printed.
</p></dd><dt><aname="BIND10_RECEIVED_NEW_CONFIGURATION"></a><spanclass="term">BIND10_RECEIVED_NEW_CONFIGURATION received new configuration: %1</span></dt><dd><p>
The boss module received a configuration update and is going to apply
it now. The new configuration is printed.
</p></dd><dt><aname="BIND10_RECEIVED_SIGNAL"></a><spanclass="term">BIND10_RECEIVED_SIGNAL received signal %1</span></dt><dd><p>
</p></dd><dt><aname="BIND10_SHUTDOWN"></a><spanclass="term">BIND10_SHUTDOWN stopping the server</span></dt><dd><p>
The boss process received a command or signal telling it to shut down.
It will send a shutdown command to each process. The processes that do
not shut down will then receive a SIGTERM signal. If that doesn't work,
it shall send SIGKILL signals to the processes still alive.
</p></dd><dt><aname="BIND10_SHUTDOWN_COMPLETE"></a><spanclass="term">BIND10_SHUTDOWN_COMPLETE all processes ended, shutdown complete</span></dt><dd><p>
All child processes have been stopped, and the boss process will now
stop itself.
</p></dd><dt><aname="BIND10_SOCKCREATOR_BAD_CAUSE"></a><spanclass="term">BIND10_SOCKCREATOR_BAD_CAUSE unknown error cause from socket creator: %1</span></dt><dd><p>
The socket creator reported an error when creating a socket. But the function
which failed is unknown (not one of 'S' for socket or 'B' for bind).
</p></dd><dt><aname="BIND10_SOCKCREATOR_BAD_RESPONSE"></a><spanclass="term">BIND10_SOCKCREATOR_BAD_RESPONSE unknown response for socket request: %1</span></dt><dd><p>
The boss requested a socket from the creator, but the answer is unknown. This
looks like a programmer error.
</p></dd><dt><aname="BIND10_SOCKCREATOR_EOF"></a><spanclass="term">BIND10_SOCKCREATOR_EOF eof while expecting data from socket creator</span></dt><dd><p>
There should be more data from the socket creator, but it closed the socket.
The boss module sends a request to terminate to the socket creator.
</p></dd><dt><aname="BIND10_SOCKCREATOR_TRANSPORT_ERROR"></a><spanclass="term">BIND10_SOCKCREATOR_TRANSPORT_ERROR transport error when talking to the socket creator: %1</span></dt><dd><p>
Either sending or receiving data from the socket creator failed with the given
error. The creator probably crashed or some serious OS-level problem happened,
as the communication happens only on local host.
</p></dd><dt><aname="BIND10_SOCKET_CREATED"></a><spanclass="term">BIND10_SOCKET_CREATED successfully created socket %1</span></dt><dd><p>
The socket creator successfully created and sent a requested socket, it has
the given file number.
</p></dd><dt><aname="BIND10_SOCKET_ERROR"></a><spanclass="term">BIND10_SOCKET_ERROR error on %1 call in the creator: %2/%3</span></dt><dd><p>
The socket creator failed to create the requested socket. It failed on the
indicated OS API function with given error.
</p></dd><dt><aname="BIND10_SOCKET_GET"></a><spanclass="term">BIND10_SOCKET_GET requesting socket [%1]:%2 of type %3 from the creator</span></dt><dd><p>
The boss forwards a request for a socket to the socket creator.
</p></dd><dt><aname="BIND10_STARTING_PROCESS"></a><spanclass="term">BIND10_STARTING_PROCESS starting process %1</span></dt><dd><p>
The boss module is starting the given process.
</p></dd><dt><aname="BIND10_STARTING_PROCESS_PORT"></a><spanclass="term">BIND10_STARTING_PROCESS_PORT starting process %1 (to listen on port %2)</span></dt><dd><p>
The boss module is starting the given process, which will listen on the
given port number.
</p></dd><dt><aname="BIND10_STARTING_PROCESS_PORT_ADDRESS"></a><spanclass="term">BIND10_STARTING_PROCESS_PORT_ADDRESS starting process %1 (to listen on %2#%3)</span></dt><dd><p>
The boss module is starting the given process, which will listen on the
given address and port number (written as <address>#<port>).
During the startup process, a number of messages are exchanged between the
Boss process and the processes it starts. This error is output when a
message received by the Boss process is not recognised.
</p></dd><dt><aname="BIND10_START_AS_NON_ROOT_AUTH"></a><spanclass="term">BIND10_START_AS_NON_ROOT_AUTH starting b10-auth as a user, not root. This might fail.</span></dt><dd><p>
The authoritative server is being started or restarted without root privileges.
If the module needs these privileges, it may have problems starting.
Note that this issue should be resolved by the pending 'socket-creator'
process; once that has been implemented, modules should not need root
privileges anymore. See tickets #800 and #801 for more information.
</p></dd><dt><aname="BIND10_START_AS_NON_ROOT_RESOLVER"></a><spanclass="term">BIND10_START_AS_NON_ROOT_RESOLVER starting b10-resolver as a user, not root. This might fail.</span></dt><dd><p>
The resolver is being started or restarted without root privileges.
</p></dd><dt><aname="BIND10_WAIT_CFGMGR"></a><spanclass="term">BIND10_WAIT_CFGMGR waiting for configuration manager process to initialize</span></dt><dd><p>
The configuration manager process is so critical to operation of BIND 10
that after starting it, the Boss module will wait for it to initialize
itself before continuing. This debug message is produced during the
wait and may be output zero or more times depending on how long it takes
the configuration manager to start up. The total length of time Boss
will wait for the configuration manager before reporting an error is
set with the command line --wait switch, which has a default value of
</p></dd><dt><aname="CACHE_ENTRY_MISSING_RRSET"></a><spanclass="term">CACHE_ENTRY_MISSING_RRSET missing RRset to generate message for %1</span></dt><dd><p>
The cache tried to generate the complete answer message. It knows the structure
of the message, but some of the RRsets to be put there are not in cache (they
probably expired already). Therefore it pretends the message was not found.
</p></dd><dt><aname="CACHE_LOCALZONE_FOUND"></a><spanclass="term">CACHE_LOCALZONE_FOUND found entry with key %1 in local zone data</span></dt><dd><p>
Debug message, noting that the requested data was successfully found in the
local zone data of the cache.
</p></dd><dt><aname="CACHE_LOCALZONE_UNKNOWN"></a><spanclass="term">CACHE_LOCALZONE_UNKNOWN entry with key %1 not found in local zone data</span></dt><dd><p>
Debug message. The requested data was not found in the local zone data.
</p></dd><dt><aname="CACHE_LOCALZONE_UPDATE"></a><spanclass="term">CACHE_LOCALZONE_UPDATE updating local zone element at key %1</span></dt><dd><p>
Debug message issued when there's update to the local zone section of cache.
Debug message. It is issued when the server deinitializes the message cache.
</p></dd><dt><aname="CACHE_MESSAGES_EXPIRED"></a><spanclass="term">CACHE_MESSAGES_EXPIRED found an expired message entry for %1 in the message cache</span></dt><dd><p>
Debug message. The requested data was found in the message cache, but it
already expired. Therefore the cache removes the entry and pretends it found
nothing.
</p></dd><dt><aname="CACHE_MESSAGES_FOUND"></a><spanclass="term">CACHE_MESSAGES_FOUND found a message entry for %1 in the message cache</span></dt><dd><p>
Debug message. We found the whole message in the cache, so it can be returned
to user without any other lookups.
</p></dd><dt><aname="CACHE_MESSAGES_INIT"></a><spanclass="term">CACHE_MESSAGES_INIT initialized message cache for %1 messages of class %2</span></dt><dd><p>
Debug message issued when a new message cache is issued. It lists the class
of messages it can hold and the maximum size of the cache.
</p></dd><dt><aname="CACHE_MESSAGES_REMOVE"></a><spanclass="term">CACHE_MESSAGES_REMOVE removing old instance of %1/%2/%3 first</span></dt><dd><p>
Debug message. This may follow CACHE_MESSAGES_UPDATE and indicates that, while
updating, the old instance is being removed prior of inserting a new one.
</p></dd><dt><aname="CACHE_MESSAGES_UNCACHEABLE"></a><spanclass="term">CACHE_MESSAGES_UNCACHEABLE not inserting uncacheable message %1/%2/%3</span></dt><dd><p>
Debug message, noting that the given message can not be cached. This is because
there's no SOA record in the message. See RFC 2308 section 5 for more
information.
</p></dd><dt><aname="CACHE_MESSAGES_UNKNOWN"></a><spanclass="term">CACHE_MESSAGES_UNKNOWN no entry for %1 found in the message cache</span></dt><dd><p>
Debug message. The message cache didn't find any entry for the given key.
Debug message issued when the message cache is being updated with a new
message. Either the old instance is removed or, if none is found, new one
is created.
</p></dd><dt><aname="CACHE_RESOLVER_DEEPEST"></a><spanclass="term">CACHE_RESOLVER_DEEPEST looking up deepest NS for %1/%2</span></dt><dd><p>
Debug message. The resolver cache is looking up the deepest known nameserver,
so the resolution doesn't have to start from the root.
</p></dd><dt><aname="CACHE_RESOLVER_INIT"></a><spanclass="term">CACHE_RESOLVER_INIT initializing resolver cache for class %1</span></dt><dd><p>
Debug message. The resolver cache is being created for this given class.
</p></dd><dt><aname="CACHE_RESOLVER_INIT_INFO"></a><spanclass="term">CACHE_RESOLVER_INIT_INFO initializing resolver cache for class %1</span></dt><dd><p>
Debug message, the resolver cache is being created for this given class. The
difference from CACHE_RESOLVER_INIT is only in different format of passed
information, otherwise it does the same.
</p></dd><dt><aname="CACHE_RESOLVER_LOCAL_MSG"></a><spanclass="term">CACHE_RESOLVER_LOCAL_MSG message for %1/%2 found in local zone data</span></dt><dd><p>
Debug message. The resolver cache found a complete message for the user query
in the zone data.
</p></dd><dt><aname="CACHE_RESOLVER_LOCAL_RRSET"></a><spanclass="term">CACHE_RESOLVER_LOCAL_RRSET RRset for %1/%2 found in local zone data</span></dt><dd><p>
Debug message. The resolver cache found a requested RRset in the local zone
data.
</p></dd><dt><aname="CACHE_RESOLVER_LOOKUP_MSG"></a><spanclass="term">CACHE_RESOLVER_LOOKUP_MSG looking up message in resolver cache for %1/%2</span></dt><dd><p>
Debug message. The resolver cache is trying to find a message to answer the
user query.
</p></dd><dt><aname="CACHE_RESOLVER_LOOKUP_RRSET"></a><spanclass="term">CACHE_RESOLVER_LOOKUP_RRSET looking up RRset in resolver cache for %1/%2</span></dt><dd><p>
Debug message. The resolver cache is trying to find an RRset (which usually
originates as internally from resolver).
</p></dd><dt><aname="CACHE_RESOLVER_NO_QUESTION"></a><spanclass="term">CACHE_RESOLVER_NO_QUESTION answer message for %1/%2 has empty question section</span></dt><dd><p>
The cache tried to fill in found data into the response message. But it
discovered the message contains no question section, which is invalid.
This is likely a programmer error, please submit a bug report.
</p></dd><dt><aname="CACHE_RESOLVER_UNKNOWN_CLASS_MSG"></a><spanclass="term">CACHE_RESOLVER_UNKNOWN_CLASS_MSG no cache for class %1</span></dt><dd><p>
Debug message. While trying to lookup a message in the resolver cache, it was
discovered there's no cache for this class at all. Therefore no message is
found.
</p></dd><dt><aname="CACHE_RESOLVER_UNKNOWN_CLASS_RRSET"></a><spanclass="term">CACHE_RESOLVER_UNKNOWN_CLASS_RRSET no cache for class %1</span></dt><dd><p>
Debug message. While trying to lookup an RRset in the resolver cache, it was
discovered there's no cache for this class at all. Therefore no data is found.
</p></dd><dt><aname="CACHE_RESOLVER_UPDATE_MSG"></a><spanclass="term">CACHE_RESOLVER_UPDATE_MSG updating message for %1/%2/%3</span></dt><dd><p>
Debug message. The resolver is updating a message in the cache.
</p></dd><dt><aname="CACHE_RESOLVER_UPDATE_RRSET"></a><spanclass="term">CACHE_RESOLVER_UPDATE_RRSET updating RRset for %1/%2/%3</span></dt><dd><p>
Debug message. The resolver is updating an RRset in the cache.
</p></dd><dt><aname="CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_MSG"></a><spanclass="term">CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_MSG no cache for class %1</span></dt><dd><p>
Debug message. While trying to insert a message into the cache, it was
discovered that there's no cache for the class of message. Therefore
the message will not be cached.
</p></dd><dt><aname="CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_RRSET"></a><spanclass="term">CACHE_RESOLVER_UPDATE_UNKNOWN_CLASS_RRSET no cache for class %1</span></dt><dd><p>
Debug message. While trying to insert an RRset into the cache, it was
discovered that there's no cache for the class of the RRset. Therefore
the message will not be cached.
</p></dd><dt><aname="CACHE_RRSET_EXPIRED"></a><spanclass="term">CACHE_RRSET_EXPIRED found expired RRset %1/%2/%3</span></dt><dd><p>
Debug message. The requested data was found in the RRset cache. However, it is
expired, so the cache removed it and is going to pretend nothing was found.
</p></dd><dt><aname="CACHE_RRSET_INIT"></a><spanclass="term">CACHE_RRSET_INIT initializing RRset cache for %1 RRsets of class %2</span></dt><dd><p>
Debug message. The RRset cache to hold at most this many RRsets for the given
class is being created.
</p></dd><dt><aname="CACHE_RRSET_LOOKUP"></a><spanclass="term">CACHE_RRSET_LOOKUP looking up %1/%2/%3 in RRset cache</span></dt><dd><p>
Debug message. The resolver is trying to look up data in the RRset cache.
Debug message which can follow CACHE_RRSET_LOOKUP. This means the data is not
in the cache.
</p></dd><dt><aname="CACHE_RRSET_REMOVE_OLD"></a><spanclass="term">CACHE_RRSET_REMOVE_OLD removing old RRset for %1/%2/%3 to make space for new one</span></dt><dd><p>
Debug message which can follow CACHE_RRSET_UPDATE. During the update, the cache
removed an old instance of the RRset to replace it with the new one.
</p></dd><dt><aname="CACHE_RRSET_UNTRUSTED"></a><spanclass="term">CACHE_RRSET_UNTRUSTED not replacing old RRset for %1/%2/%3, it has higher trust level</span></dt><dd><p>
Debug message which can follow CACHE_RRSET_UPDATE. The cache already holds the
same RRset, but from more trusted source, so the old one is kept and new one
ignored.
</p></dd><dt><aname="CACHE_RRSET_UPDATE"></a><spanclass="term">CACHE_RRSET_UPDATE updating RRset %1/%2/%3 in the cache</span></dt><dd><p>
Debug message. The RRset is updating its data with this given RRset.
This marks a low level error, we tried to read data from the message queue
daemon asynchronously, but the ASIO library returned an error.
</p></dd><dt><aname="CC_CONN_ERROR"></a><spanclass="term">CC_CONN_ERROR error connecting to message queue (%1)</span></dt><dd><p>
It is impossible to reach the message queue daemon for the reason given. It
is unlikely there'll be reason for whatever program this currently is to
continue running, as the communication with the rest of BIND 10 is vital
for the components.
</p></dd><dt><aname="CC_DISCONNECT"></a><spanclass="term">CC_DISCONNECT disconnecting from message queue daemon</span></dt><dd><p>
The library is disconnecting from the message queue daemon. This debug message
indicates that the program is trying to shut down gracefully.
</p></dd><dt><aname="CC_ESTABLISH"></a><spanclass="term">CC_ESTABLISH trying to establish connection with message queue daemon at %1</span></dt><dd><p>
This debug message indicates that the command channel library is about to
connect to the message queue daemon, which should be listening on the UNIX-domain
socket listed in the output.
</p></dd><dt><aname="CC_ESTABLISHED"></a><spanclass="term">CC_ESTABLISHED successfully connected to message queue daemon</span></dt><dd><p>
This debug message indicates that the connection was successfully made, this
should follow CC_ESTABLISH.
</p></dd><dt><aname="CC_GROUP_RECEIVE"></a><spanclass="term">CC_GROUP_RECEIVE trying to receive a message</span></dt><dd><p>
Debug message, noting that a message is expected to come over the command
The library received a message length being zero, which makes no sense, since
all messages must contain at least the envelope.
</p></dd><dt><aname="CFGMGR_AUTOMATIC_CONFIG_DATABASE_UPDATE"></a><spanclass="term">CFGMGR_AUTOMATIC_CONFIG_DATABASE_UPDATE Updating configuration database from version %1 to %2</span></dt><dd><p>
An older version of the configuration database has been found, from which
there was an automatic upgrade path to the current version. These changes
are now applied, and no action from the administrator is necessary.
</p></dd><dt><aname="CFGMGR_BACKED_UP_CONFIG_FILE"></a><spanclass="term">CFGMGR_BACKED_UP_CONFIG_FILE Config file %1 was removed; a backup was made at %2</span></dt><dd><p>
BIND 10 has been started with the command to clear the configuration
file. The existing file has been backed up (moved) to the given file
name. A new configuration file will be created in the original location
</p></dd><dt><aname="CFGMGR_BAD_UPDATE_RESPONSE_FROM_MODULE"></a><spanclass="term">CFGMGR_BAD_UPDATE_RESPONSE_FROM_MODULE Unable to parse response from module %1: %2</span></dt><dd><p>
The configuration manager sent a configuration update to a module, but
the module responded with an answer that could not be parsed. The answer
message appears to be invalid JSON data, or not decodable to a string.
This is likely to be a problem in the module in question. The update is
</p></dd><dt><aname="CFGMGR_DATA_READ_ERROR"></a><spanclass="term">CFGMGR_DATA_READ_ERROR error reading configuration database from disk: %1</span></dt><dd><p>
There was a problem reading the persistent configuration data as stored
on disk. The file may be corrupted, or it is of a version from where
there is no automatic upgrade path. The file needs to be repaired or
removed. The configuration manager daemon will now shut down.
</p></dd><dt><aname="CFGMGR_IOERROR_WHILE_WRITING_CONFIGURATION"></a><spanclass="term">CFGMGR_IOERROR_WHILE_WRITING_CONFIGURATION Unable to write configuration file; configuration not stored: %1</span></dt><dd><p>
There was an IO error from the system while the configuration manager
was trying to write the configuration database to disk. The specific
error is given. The most likely cause is that the directory where
the file is stored does not exist, or is not writable. The updated
configuration is not stored.
</p></dd><dt><aname="CFGMGR_OSERROR_WHILE_WRITING_CONFIGURATION"></a><spanclass="term">CFGMGR_OSERROR_WHILE_WRITING_CONFIGURATION Unable to write configuration file; configuration not stored: %1</span></dt><dd><p>
There was an OS error from the system while the configuration manager
was trying to write the configuration database to disk. The specific
error is given. The most likely cause is that the system does not have
write access to the configuration database file. The updated
</p></dd><dt><aname="CMDCTL_BAD_CONFIG_DATA"></a><spanclass="term">CMDCTL_BAD_CONFIG_DATA error in config data: %1</span></dt><dd><p>
There was an error reading the updated configuration data. The specific
error is printed.
</p></dd><dt><aname="CMDCTL_BAD_PASSWORD"></a><spanclass="term">CMDCTL_BAD_PASSWORD bad password for user: %1</span></dt><dd><p>
A login attempt was made to b10-cmdctl, but the password was wrong.
Users can be managed with the tool b10-cmdctl-usermgr.
</p></dd><dt><aname="CMDCTL_CC_SESSION_ERROR"></a><spanclass="term">CMDCTL_CC_SESSION_ERROR error reading from cc channel: %1</span></dt><dd><p>
There was a problem reading from the command and control channel. The
most likely cause is that the message bus daemon is not running.
</p></dd><dt><aname="CMDCTL_CC_SESSION_TIMEOUT"></a><spanclass="term">CMDCTL_CC_SESSION_TIMEOUT timeout on cc channel</span></dt><dd><p>
A timeout occurred when waiting for essential data from the cc session.
This usually occurs when b10-cfgmgr is not running or not responding.
Since we are waiting for essential information, this is a fatal error,
and the cmdctl daemon will now shut down.
</p></dd><dt><aname="CMDCTL_COMMAND_ERROR"></a><spanclass="term">CMDCTL_COMMAND_ERROR error in command %1 to module %2: %3</span></dt><dd><p>
An error was encountered sending the given command to the given module.
Either there was a communication problem with the module, or the module
was not able to process the command, and sent back an error. The
specific error is printed in the message.
</p></dd><dt><aname="CMDCTL_COMMAND_SENT"></a><spanclass="term">CMDCTL_COMMAND_SENT command '%1' to module '%2' was sent</span></dt><dd><p>
This debug message indicates that the given command has been sent to
the given module.
</p></dd><dt><aname="CMDCTL_NO_SUCH_USER"></a><spanclass="term">CMDCTL_NO_SUCH_USER username not found in user database: %1</span></dt><dd><p>
A login attempt was made to b10-cmdctl, but the username was not known.
Users can be added with the tool b10-cmdctl-usermgr.
</p></dd><dt><aname="CMDCTL_NO_USER_ENTRIES_READ"></a><spanclass="term">CMDCTL_NO_USER_ENTRIES_READ failed to read user information, all users will be denied</span></dt><dd><p>
The b10-cmdctl daemon was unable to find any user data in the user
database file. Either it was unable to read the file (in which case
this message follows a message CMDCTL_USER_DATABASE_READ_ERROR
containing a specific error), or the file was empty. Users can be added
with the tool b10-cmdctl-usermgr.
</p></dd><dt><aname="CMDCTL_SEND_COMMAND"></a><spanclass="term">CMDCTL_SEND_COMMAND sending command %1 to module %2</span></dt><dd><p>
This debug message indicates that the given command is being sent to
the given module.
</p></dd><dt><aname="CMDCTL_SSL_SETUP_FAILURE_USER_DENIED"></a><spanclass="term">CMDCTL_SSL_SETUP_FAILURE_USER_DENIED failed to create an SSL connection (user denied): %1</span></dt><dd><p>
The user was denied because the SSL connection could not successfully
be set up. The specific error is given in the log message. Possible
causes may be that the ssl request itself was bad, or the local key or
The b10-cmdctl daemon encountered an uncaught exception and
will now shut down. This is indicative of a programming error and
should not happen under normal circumstances. The exception message
is printed.
</p></dd><dt><aname="CMDCTL_USER_DATABASE_READ_ERROR"></a><spanclass="term">CMDCTL_USER_DATABASE_READ_ERROR failed to read user database file %1: %2</span></dt><dd><p>
The b10-cmdctl daemon was unable to read the user database file. The
file may be unreadable for the daemon, or it may be corrupted. In the
latter case, it can be recreated with b10-cmdctl-usermgr. The specific
</p></dd><dt><aname="CONFIG_LOG_CONFIG_ERRORS"></a><spanclass="term">CONFIG_LOG_CONFIG_ERRORS error(s) in logging configuration: %1</span></dt><dd><p>
There was a logging configuration update, but the internal validator
for logging configuration found that it contained errors. The errors
are shown, and the update is ignored.
</p></dd><dt><aname="CONFIG_LOG_EXPLICIT"></a><spanclass="term">CONFIG_LOG_EXPLICIT will use logging configuration for explicitly-named logger %1</span></dt><dd><p>
This is a debug message. When processing the "loggers" part of the
configuration file, the configuration library found an entry for the named
logger that matches the logger specification for the program. The logging
configuration for the program will be updated with the information.
</p></dd><dt><aname="CONFIG_LOG_IGNORE_EXPLICIT"></a><spanclass="term">CONFIG_LOG_IGNORE_EXPLICIT ignoring logging configuration for explicitly-named logger %1</span></dt><dd><p>
This is a debug message. When processing the "loggers" part of the
configuration file, the configuration library found an entry for the
named logger. As this does not match the logger specification for the
program, it has been ignored.
</p></dd><dt><aname="CONFIG_LOG_IGNORE_WILD"></a><spanclass="term">CONFIG_LOG_IGNORE_WILD ignoring logging configuration for wildcard logger %1</span></dt><dd><p>
This is a debug message. When processing the "loggers" part of the
configuration file, the configuration library found the named wildcard
entry (one containing the "*" character) that matched a logger already
matched by an explicitly named entry. The configuration is ignored.
</p></dd><dt><aname="CONFIG_LOG_WILD_MATCH"></a><spanclass="term">CONFIG_LOG_WILD_MATCH will use logging configuration for wildcard logger %1</span></dt><dd><p>
This is a debug message. When processing the "loggers" part of
the configuration file, the configuration library found the named
wildcard entry (one containing the "*" character) that matches a logger
specification in the program. The logging configuration for the program
</p></dd><dt><aname="DATASRC_CACHE_NOT_FOUND"></a><spanclass="term">DATASRC_CACHE_NOT_FOUND the item '%1' was not found in the hotspot cache</span></dt><dd><p>
A debug message issued when hotspot cache was searched for the specified
item but it was not found.
</p></dd><dt><aname="DATASRC_CACHE_OLD_FOUND"></a><spanclass="term">DATASRC_CACHE_OLD_FOUND older instance of hotspot cache item '%1' found, replacing</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_DATABASE_COVER_NSEC_UNSUPPORTED"></a><spanclass="term">DATASRC_DATABASE_COVER_NSEC_UNSUPPORTED %1 doesn't support DNSSEC when asked for NSEC data covering %2</span></dt><dd><p>
The datasource tried to provide an NSEC proof that the named domain does not
exist, but the database backend doesn't support DNSSEC. No proof is included
</p></dd><dt><aname="DATASRC_DATABASE_FINDNSEC3"></a><spanclass="term">DATASRC_DATABASE_FINDNSEC3 Looking for NSEC3 for %1 in %2 mode</span></dt><dd><p>
Debug information. A search in an database data source for NSEC3 that
matches or covers the given name is being started.
</p></dd><dt><aname="DATASRC_DATABASE_FINDNSEC3_COVER"></a><spanclass="term">DATASRC_DATABASE_FINDNSEC3_COVER found a covering NSEC3 for %1 at label count %2: %3</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_DATABASE_FINDNSEC3_MATCH"></a><spanclass="term">DATASRC_DATABASE_FINDNSEC3_MATCH found a matching NSEC3 for %1 at label count %2: %3</span></dt><dd><p>
Debug information. An NSEC3 that matches (a possibly superdomain of)
the given name is found and being returned. When the shown label
count is smaller than that of the given name, the matching NSEC3 is
for a superdomain of the given name (see DATASRC_DATABSE_FINDNSEC3_TRYHASH).
The found NSEC3 RRset is also displayed.
</p></dd><dt><aname="DATASRC_DATABASE_FINDNSEC3_TRYHASH"></a><spanclass="term">DATASRC_DATABASE_FINDNSEC3_TRYHASH looking for NSEC3 for %1 at label count %2 (hash %3)</span></dt><dd><p>
Debug information. In an attempt of finding an NSEC3 for the give name,
(a possibly superdomain of) the name is hashed and searched for in the
NSEC3 name space. When the shown label count is smaller than that of the
shown name, the search tries the superdomain name that share the shown
(higher) label count of the shown name (e.g., for
www.example.com. with shown label count of 3, example.com. is being
tried, as "." is 1 label long).
</p></dd><dt><aname="DATASRC_DATABASE_FINDNSEC3_TRYHASH_PREV"></a><spanclass="term">DATASRC_DATABASE_FINDNSEC3_TRYHASH_PREV looking for previous NSEC3 for %1 at label count %2 (hash %3)</span></dt><dd><p>
Debug information. An exact match on hash (see
DATASRC_DATABASE_FINDNSEC3_TRYHASH) was unsuccessful. We get the previous hash
</p></dd><dt><aname="DATASRC_DATABASE_FIND_RECORDS"></a><spanclass="term">DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3/%4</span></dt><dd><p>
Debug information. The database data source is looking up records with the given
name and type in the database.
</p></dd><dt><aname="DATASRC_DATABASE_FIND_TTL_MISMATCH"></a><spanclass="term">DATASRC_DATABASE_FIND_TTL_MISMATCH TTL values differ in %1 for elements of %2/%3/%4, setting to %5</span></dt><dd><p>
The datasource backend provided resource records for the given RRset with
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_ANY"></a><spanclass="term">DATASRC_DATABASE_FOUND_ANY search in datasource %1 resulted in returning all records of %2</span></dt><dd><p>
The data returned by the database backend contained data for the given domain
name, so all the RRsets of the domain are returned.
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_CNAME"></a><spanclass="term">DATASRC_DATABASE_FOUND_CNAME search in datasource %1 for %2/%3/%4 found CNAME, resulting in %5</span></dt><dd><p>
When searching the domain for a name a CNAME was found at that name.
Even though it was not the RR type being sought, it is returned. (The
caller may want to continue the lookup by replacing the query name with
the canonical name and restarting the query with the original RR type.)
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_DELEGATION"></a><spanclass="term">DATASRC_DATABASE_FOUND_DELEGATION Found delegation at %2 in %1</span></dt><dd><p>
When searching for a domain, the program met a delegation to a different zone
at the given domain name. It will return that one instead.
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_DELEGATION_EXACT"></a><spanclass="term">DATASRC_DATABASE_FOUND_DELEGATION_EXACT search in datasource %1 for %2/%3/%4 found delegation at %5</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_NXDOMAIN"></a><spanclass="term">DATASRC_DATABASE_FOUND_NXDOMAIN search in datasource %1 resulted in NXDOMAIN for %2/%3/%4</span></dt><dd><p>
The data returned by the database backend did not contain any data for the given
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_NXRRSET"></a><spanclass="term">DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 for %2/%3/%4 resulted in NXRRSET</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_NXRRSET_NSEC"></a><spanclass="term">DATASRC_DATABASE_FOUND_NXRRSET_NSEC search in datasource %1 for %2/%3/%4 resulted in RRset %5</span></dt><dd><p>
A search in the database for RRs for the specified name, type and class has
located RRs that match the name and class but not the type. DNSSEC information
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_RRSET"></a><spanclass="term">DATASRC_DATABASE_FOUND_RRSET search in datasource %1 resulted in RRset %2</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_DATABASE_ITERATE"></a><spanclass="term">DATASRC_DATABASE_ITERATE iterating zone %1</span></dt><dd><p>
The program is reading the whole zone, eg. not searching for data, but going
through each of the RRsets there.
</p></dd><dt><aname="DATASRC_DATABASE_ITERATE_END"></a><spanclass="term">DATASRC_DATABASE_ITERATE_END iterating zone finished</span></dt><dd><p>
While iterating through the zone, the program reached end of the data.
</p></dd><dt><aname="DATASRC_DATABASE_ITERATE_NEXT"></a><spanclass="term">DATASRC_DATABASE_ITERATE_NEXT next RRset in zone is %1/%2</span></dt><dd><p>
While iterating through the zone, the program extracted next RRset from it.
The name and RRtype of the RRset is indicated in the message.
</p></dd><dt><aname="DATASRC_DATABASE_ITERATE_TTL_MISMATCH"></a><spanclass="term">DATASRC_DATABASE_ITERATE_TTL_MISMATCH TTL values differ for RRs of %1/%2/%3, setting to %4</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_DATABASE_JOURNALREADER_END"></a><spanclass="term">DATASRC_DATABASE_JOURNALREADER_END %1/%2 on %3 from %4 to %5</span></dt><dd><p>
This is a debug message indicating that the program (successfully)
reaches the end of sequences of a zone's differences. The zone's name
and class, database name, and the start and end serials are shown in
the message.
</p></dd><dt><aname="DATASRC_DATABASE_JOURNALREADER_NEXT"></a><spanclass="term">DATASRC_DATABASE_JOURNALREADER_NEXT %1/%2 in %3/%4 on %5</span></dt><dd><p>
This is a debug message indicating that the program retrieves one
difference in difference sequences of a zone and successfully converts
it to an RRset. The zone's name and class, database name, and the
name and RR type of the retrieved diff are shown in the message.
</p></dd><dt><aname="DATASRC_DATABASE_JOURNALREADER_START"></a><spanclass="term">DATASRC_DATABASE_JOURNALREADER_START %1/%2 on %3 from %4 to %5</span></dt><dd><p>
This is a debug message indicating that the program starts reading
a zone's difference sequences from a database-based data source. The
zone's name and class, database name, and the start and end serials
are shown in the message.
</p></dd><dt><aname="DATASRC_DATABASE_JOURNALREADR_BADDATA"></a><spanclass="term">DATASRC_DATABASE_JOURNALREADR_BADDATA failed to convert a diff to RRset in %1/%2 on %3 between %4 and %5: %6</span></dt><dd><p>
This is an error message indicating that a zone's diff is broken and
the data source library failed to convert it to a valid RRset. The
most likely cause of this is that someone has manually modified the
zone's diff in the database and inserted invalid data as a result.
The zone's name and class, database name, and the start and end
serials, and an additional detail of the error are shown in the
message. The administrator should examine the diff in the database
</p></dd><dt><aname="DATASRC_DATABASE_UPDATER_COMMIT"></a><spanclass="term">DATASRC_DATABASE_UPDATER_COMMIT updates committed for '%1/%2' on %3</span></dt><dd><p>
Debug information. A set of updates to a zone has been successfully
committed to the corresponding database backend. The zone name,
its class and the database name are printed.
</p></dd><dt><aname="DATASRC_DATABASE_UPDATER_CREATED"></a><spanclass="term">DATASRC_DATABASE_UPDATER_CREATED zone updater created for '%1/%2' on %3</span></dt><dd><p>
Debug information. A zone updater object is created to make updates to
the shown zone on the shown backend database.
</p></dd><dt><aname="DATASRC_DATABASE_UPDATER_DESTROYED"></a><spanclass="term">DATASRC_DATABASE_UPDATER_DESTROYED zone updater destroyed for '%1/%2' on %3</span></dt><dd><p>
Debug information. A zone updater object is destroyed, either successfully
or after failure of, making updates to the shown zone on the shown backend
database.
</p></dd><dt><aname="DATASRC_DATABASE_UPDATER_ROLLBACK"></a><spanclass="term">DATASRC_DATABASE_UPDATER_ROLLBACK zone updates roll-backed for '%1/%2' on %3</span></dt><dd><p>
A zone updater is being destroyed without committing the changes.
This would typically mean the update attempt was aborted due to some
error, but may also be a bug of the application that forgets committing
the changes. The intermediate changes made through the updater won't
be applied to the underlying database. The zone name, its class, and
the underlying database name are shown in the log message.
</p></dd><dt><aname="DATASRC_DATABASE_UPDATER_ROLLBACKFAIL"></a><spanclass="term">DATASRC_DATABASE_UPDATER_ROLLBACKFAIL failed to roll back zone updates for '%1/%2' on %3: %4</span></dt><dd><p>
A zone updater is being destroyed without committing the changes to
the database, and attempts to rollback incomplete updates, but it
unexpectedly fails. The higher level implementation does not expect
it to fail, so this means either a serious operational error in the
underlying data source (such as a system failure of a database) or
software bug in the underlying data source implementation. In either
case if this message is logged the administrator should carefully
examine the underlying data source to see what exactly happens and
whether the data is still valid. The zone name, its class, and the
underlying database name as well as the error message thrown from the
</p></dd><dt><aname="DATASRC_DATABASE_WILDCARD_ANY"></a><spanclass="term">DATASRC_DATABASE_WILDCARD_ANY search in datasource %1 resulted in wildcard match type ANY on %2</span></dt><dd><p>
The database doesn't contain directly matching name. When searching
for a wildcard match, a wildcard record matching the name of the query
containing some RRsets was found. All the RRsets of the node are returned.
</p></dd><dt><aname="DATASRC_DATABASE_WILDCARD_CANCEL_NS"></a><spanclass="term">DATASRC_DATABASE_WILDCARD_CANCEL_NS canceled wildcard match on %3 because %2 contains NS (data source %1)</span></dt><dd><p>
The database was queried to provide glue data and it didn't find direct match.
It could create it from given wildcard, but matching wildcards is forbidden
under a zone cut, which was found. Therefore the delegation will be returned
instead.
</p></dd><dt><aname="DATASRC_DATABASE_WILDCARD_CANCEL_SUB"></a><spanclass="term">DATASRC_DATABASE_WILDCARD_CANCEL_SUB wildcard %2 can't be used to construct %3 because %4 exists in %1</span></dt><dd><p>
The answer could be constructed using the wildcard, but the given subdomain
exists, therefore this name is something like empty non-terminal (actually,
from the protocol point of view, it is empty non-terminal, but the code
</p></dd><dt><aname="DATASRC_DATABASE_WILDCARD_CNAME"></a><spanclass="term">DATASRC_DATABASE_WILDCARD_CNAME search in datasource %1 for %2/%3/%4 found wildcard CNAME at %5, resulting in %6</span></dt><dd><p>
The database doesn't contain directly matching name. When searching
for a wildcard match, a CNAME RR was found at a wildcard record
matching the name. This is returned as the result of the search.
</p></dd><dt><aname="DATASRC_DATABASE_WILDCARD_EMPTY"></a><spanclass="term">DATASRC_DATABASE_WILDCARD_EMPTY found subdomains of %2 which is a wildcard match for %3 in %1</span></dt><dd><p>
The given wildcard matches the name being sough but it as an empty
nonterminal (e.g. there's nothing at *.example.com but something like
subdomain.*.example.org, do exist: so *.example.org exists in the
namespace but has no RRs assopciated with it). This will produce NXRRSET.
</p></dd><dt><aname="DATASRC_DATABASE_WILDCARD_MATCH"></a><spanclass="term">DATASRC_DATABASE_WILDCARD_MATCH search in datasource %1 resulted in wildcard match at %2 with RRset %3</span></dt><dd><p>
The database doesn't contain directly matching name. When searching
for a wildcard match, a wildcard record matching the name and type of
the query was found. The data at this point is returned.
</p></dd><dt><aname="DATASRC_DATABASE_WILDCARD_NS"></a><spanclass="term">DATASRC_DATABASE_WILDCARD_NS search in datasource %1 for %2/%3/%4 found wildcard delegation at %5, resulting in %6</span></dt><dd><p>
The database doesn't contain directly matching name. When searching
for a wildcard match, an NS RR was found at a wildcard record matching
the name. This is returned as the result of the search.
</p></dd><dt><aname="DATASRC_DATABASE_WILDCARD_NXRRSET"></a><spanclass="term">DATASRC_DATABASE_WILDCARD_NXRRSET search in datasource %1 for %2/%3/%4 resulted in wildcard NXRRSET at %5</span></dt><dd><p>
The database doesn't contain directly matching name. When searching
for a wildcard match, a matching wildcard entry was found but it did
not contain RRs the requested type. AN NXRRSET indication is returned.
</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
</p></dd><dt><aname="DATASRC_MEM_ADD_ZONE"></a><spanclass="term">DATASRC_MEM_ADD_ZONE adding zone '%1/%2'</span></dt><dd><p>
Debug information. A zone is being added into the in-memory data source.
</p></dd><dt><aname="DATASRC_MEM_ANY_SUCCESS"></a><spanclass="term">DATASRC_MEM_ANY_SUCCESS ANY query for '%1' successful</span></dt><dd><p>
Debug information. The domain was found and an ANY type query is being answered
by providing everything found inside the domain.
</p></dd><dt><aname="DATASRC_MEM_CNAME"></a><spanclass="term">DATASRC_MEM_CNAME CNAME at the domain '%1'</span></dt><dd><p>
Debug information. The requested domain is an alias to a different domain,
returning the CNAME instead.
</p></dd><dt><aname="DATASRC_MEM_CNAME_COEXIST"></a><spanclass="term">DATASRC_MEM_CNAME_COEXIST can't add data to CNAME in domain '%1'</span></dt><dd><p>
This is the same problem as in MEM_CNAME_TO_NONEMPTY, but it happened the
</p></dd><dt><aname="DATASRC_MEM_CNAME_TO_NONEMPTY"></a><spanclass="term">DATASRC_MEM_CNAME_TO_NONEMPTY can't add CNAME to domain with other data in '%1'</span></dt><dd><p>
Someone or something tried to add a CNAME into a domain that already contains
some other data. But the protocol forbids coexistence of CNAME with anything
(RFC 1034, section 3.6.2). This indicates a problem with provided data.
</p></dd><dt><aname="DATASRC_MEM_CREATE"></a><spanclass="term">DATASRC_MEM_CREATE creating zone '%1' in '%2' class</span></dt><dd><p>
Debug information. A representation of a zone for the in-memory data source is
being created.
</p></dd><dt><aname="DATASRC_MEM_DELEG_FOUND"></a><spanclass="term">DATASRC_MEM_DELEG_FOUND delegation found at '%1'</span></dt><dd><p>
Debug information. A delegation point was found above the requested record.
</p></dd><dt><aname="DATASRC_MEM_DESTROY"></a><spanclass="term">DATASRC_MEM_DESTROY destroying zone '%1' in '%2' class</span></dt><dd><p>
Debug information. A zone from in-memory data source is being destroyed.
</p></dd><dt><aname="DATASRC_MEM_DNAME_ENCOUNTERED"></a><spanclass="term">DATASRC_MEM_DNAME_ENCOUNTERED encountered a DNAME</span></dt><dd><p>
Debug information. While searching for the requested domain, a DNAME was
encountered on the way. This may lead to redirection to a different domain and
stop the search.
</p></dd><dt><aname="DATASRC_MEM_DNAME_FOUND"></a><spanclass="term">DATASRC_MEM_DNAME_FOUND DNAME found at '%1'</span></dt><dd><p>
Debug information. A DNAME was found instead of the requested information.
</p></dd><dt><aname="DATASRC_MEM_DNAME_NS"></a><spanclass="term">DATASRC_MEM_DNAME_NS DNAME and NS can't coexist in non-apex domain '%1'</span></dt><dd><p>
An RRset is being inserted into in-memory data source for a second time. The
original version must be removed first. Note that loading master files where an
RRset is split into multiple locations is not supported yet.
</p></dd><dt><aname="DATASRC_MEM_EXACT_DELEGATION"></a><spanclass="term">DATASRC_MEM_EXACT_DELEGATION delegation at the exact domain '%1'</span></dt><dd><p>
Debug information. There's a NS record at the requested domain. This means
this zone is not authoritative for the requested domain, but a delegation
should be followed. The requested domain is an apex of some zone.
</p></dd><dt><aname="DATASRC_MEM_FINDNSEC3"></a><spanclass="term">DATASRC_MEM_FINDNSEC3 finding NSEC3 for %1, mode %2</span></dt><dd><p>
Debug information. A search in an in-memory data source for NSEC3 that
matches or covers the given name is being started.
</p></dd><dt><aname="DATASRC_MEM_FINDNSEC3_COVER"></a><spanclass="term">DATASRC_MEM_FINDNSEC3_COVER found a covering NSEC3 for %1: %2</span></dt><dd><p>
Debug information. An NSEC3 that covers the given name is found and
being returned. The found NSEC3 RRset is also displayed.
</p></dd><dt><aname="DATASRC_MEM_FINDNSEC3_MATCH"></a><spanclass="term">DATASRC_MEM_FINDNSEC3_MATCH found a matching NSEC3 for %1 at label count %2: %3</span></dt><dd><p>
Debug information. An NSEC3 that matches (a possibly superdomain of)
the given name is found and being returned. When the shown label
count is smaller than that of the given name, the matching NSEC3 is
for a superdomain of the given name (see DATASRC_MEM_FINDNSEC3_TRYHASH).
The found NSEC3 RRset is also displayed.
</p></dd><dt><aname="DATASRC_MEM_FINDNSEC3_TRYHASH"></a><spanclass="term">DATASRC_MEM_FINDNSEC3_TRYHASH looking for NSEC3 for %1 at label count %2 (hash %3)</span></dt><dd><p>
Debug information. In an attempt of finding an NSEC3 for the give name,
(a possibly superdomain of) the name is hashed and searched for in the
NSEC3 name space. When the shown label count is smaller than that of the
shown name, the search tries the superdomain name that share the shown
(higher) label count of the shown name (e.g., for
www.example.com. with shown label count of 3, example.com. is being
</p></dd><dt><aname="DATASRC_MEM_NO_NSEC3PARAM"></a><spanclass="term">DATASRC_MEM_NO_NSEC3PARAM NSEC3PARAM is missing for NSEC3-signed zone %1/%2</span></dt><dd><p>
The in-memory data source has loaded a zone signed with NSEC3 RRs,
but it doesn't have a NSEC3PARAM RR at the zone origin. It's likely that
the zone is somehow broken, but this RR is not necessarily needed for
handling lookups with NSEC3 in this data source, so it accepts the given
content of the zone. Nevertheless the administrator should look into
</p></dd><dt><aname="DATASRC_MEM_NS_ENCOUNTERED"></a><spanclass="term">DATASRC_MEM_NS_ENCOUNTERED encountered a NS</span></dt><dd><p>
Debug information. While searching for the requested domain, a NS was
encountered on the way (a delegation). This may lead to stop of the search.
</p></dd><dt><aname="DATASRC_MEM_NXRRSET"></a><spanclass="term">DATASRC_MEM_NXRRSET no such type '%1' at '%2'</span></dt><dd><p>
Debug information. The domain exists, but it doesn't hold any record of the
requested type.
</p></dd><dt><aname="DATASRC_MEM_OUT_OF_ZONE"></a><spanclass="term">DATASRC_MEM_OUT_OF_ZONE domain '%1' doesn't belong to zone '%2'</span></dt><dd><p>
It was attempted to add the domain into a zone that shouldn't have it
(eg. the domain is not subdomain of the zone origin). This indicates a
problem with provided data.
</p></dd><dt><aname="DATASRC_MEM_RENAME"></a><spanclass="term">DATASRC_MEM_RENAME renaming RRset from '%1' to '%2'</span></dt><dd><p>
Debug information. A RRset is being generated from a different RRset (most
probably a wildcard). So it must be renamed to whatever the user asked for. In
fact, it's impossible to rename RRsets with our libraries, so a new one is
created and all resource records are copied over.
</p></dd><dt><aname="DATASRC_MEM_SINGLETON"></a><spanclass="term">DATASRC_MEM_SINGLETON trying to add multiple RRs for domain '%1' and type '%2'</span></dt><dd><p>
Some resource types are singletons -- only one is allowed in a domain
(for example CNAME or SOA). This indicates a problem with provided data.
</p></dd><dt><aname="DATASRC_MEM_SUCCESS"></a><spanclass="term">DATASRC_MEM_SUCCESS query for '%1/%2' successful</span></dt><dd><p>
Debug information. The requested record was found.
</p></dd><dt><aname="DATASRC_MEM_SUPER_STOP"></a><spanclass="term">DATASRC_MEM_SUPER_STOP stopped as '%1' is superdomain of a zone node, meaning it's empty</span></dt><dd><p>
Debug information. The search stopped because the requested domain was
detected to be a superdomain of some existing node of zone (while there
was no exact match). This means that the domain is an empty nonterminal,
therefore it is treated as NXRRSET case (eg. the domain exists, but it
</p></dd><dt><aname="DATASRC_MEM_SWAP"></a><spanclass="term">DATASRC_MEM_SWAP swapping contents of two zone representations ('%1' and '%2')</span></dt><dd><p>
Debug information. The contents of two in-memory zones are being exchanged.
This is usual practice to do some manipulation in exception-safe manner -- the
new data are prepared in a different zone object and when it works, they are
swapped. The old one contains the new data and the other one can be safely
destroyed.
</p></dd><dt><aname="DATASRC_MEM_WILDCARD_CANCEL"></a><spanclass="term">DATASRC_MEM_WILDCARD_CANCEL wildcard match canceled for '%1'</span></dt><dd><p>
Debug information. A domain above wildcard was reached, but there's something
below the requested domain. Therefore the wildcard doesn't apply here. This
</p></dd><dt><aname="DATASRC_MEM_WILDCARD_DNAME"></a><spanclass="term">DATASRC_MEM_WILDCARD_DNAME DNAME record in wildcard domain '%1'</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_META_ADD_CLASS_MISMATCH"></a><spanclass="term">DATASRC_META_ADD_CLASS_MISMATCH mismatch between classes '%1' and '%2'</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_META_REMOVE"></a><spanclass="term">DATASRC_META_REMOVE removing data source from meta data source</span></dt><dd><p>
Debug information. A data source is being removed from meta data source.
</p></dd><dt><aname="DATASRC_QUERY_ADD_NSEC"></a><spanclass="term">DATASRC_QUERY_ADD_NSEC adding NSEC record for '%1'</span></dt><dd><p>
Debug information. A NSEC record covering this zone is being added.
</p></dd><dt><aname="DATASRC_QUERY_ADD_NSEC3"></a><spanclass="term">DATASRC_QUERY_ADD_NSEC3 adding NSEC3 record of zone '%1'</span></dt><dd><p>
Debug information. A NSEC3 record for the given zone is being added to the
response message.
</p></dd><dt><aname="DATASRC_QUERY_ADD_RRSET"></a><spanclass="term">DATASRC_QUERY_ADD_RRSET adding RRset '%1/%2' to message</span></dt><dd><p>
Debug information. An RRset is being added to the response message.
</p></dd><dt><aname="DATASRC_QUERY_ADD_SOA"></a><spanclass="term">DATASRC_QUERY_ADD_SOA adding SOA of '%1'</span></dt><dd><p>
Debug information. A SOA record of the given zone is being added to the
authority section of the response message.
</p></dd><dt><aname="DATASRC_QUERY_AUTH_FAIL"></a><spanclass="term">DATASRC_QUERY_AUTH_FAIL the underlying data source failed with %1</span></dt><dd><p>
The underlying data source failed to answer the authoritative query. 1 means
some error, 2 is not implemented. The data source should have logged the
specific error already.
</p></dd><dt><aname="DATASRC_QUERY_BAD_REFERRAL"></a><spanclass="term">DATASRC_QUERY_BAD_REFERRAL bad referral to '%1'</span></dt><dd><p>
The domain lives in another zone. But it is not possible to generate referral
Debug information. While processing a query, lookup to the hotspot cache
is being made.
</p></dd><dt><aname="DATASRC_QUERY_COPY_AUTH"></a><spanclass="term">DATASRC_QUERY_COPY_AUTH copying authoritative section into message</span></dt><dd><p>
Debug information. The whole referral information is being copied into the
response message.
</p></dd><dt><aname="DATASRC_QUERY_DELEGATION"></a><spanclass="term">DATASRC_QUERY_DELEGATION looking for delegation on the path to '%1'</span></dt><dd><p>
Debug information. The software is trying to identify delegation points on the
</p></dd><dt><aname="DATASRC_QUERY_GET_MX_ADDITIONAL"></a><spanclass="term">DATASRC_QUERY_GET_MX_ADDITIONAL addition of A/AAAA for '%1' requested by MX '%2'</span></dt><dd><p>
Debug information. While processing a query, a MX record was met. It
references the mentioned address, so A/AAAA records for it are looked up
and put it into the additional section.
</p></dd><dt><aname="DATASRC_QUERY_GET_NS_ADDITIONAL"></a><spanclass="term">DATASRC_QUERY_GET_NS_ADDITIONAL addition of A/AAAA for '%1' requested by NS '%2'</span></dt><dd><p>
Debug information. While processing a query, a NS record was met. It
references the mentioned address, so A/AAAA records for it are looked up
and put it into the additional section.
</p></dd><dt><aname="DATASRC_QUERY_GLUE_FAIL"></a><spanclass="term">DATASRC_QUERY_GLUE_FAIL the underlying data source failed with %1</span></dt><dd><p>
The underlying data source failed to answer the glue query. 1 means some error,
2 is not implemented. The data source should have logged the specific error
Debug information. The last DO_QUERY is a simple query.
</p></dd><dt><aname="DATASRC_QUERY_MISPLACED_TASK"></a><spanclass="term">DATASRC_QUERY_MISPLACED_TASK task of this type should not be here</span></dt><dd><p>
This indicates a programming error. A task was found in the internal task
queue, but this kind of task wasn't designed to be inside the queue (it should
be handled right away, not queued).
</p></dd><dt><aname="DATASRC_QUERY_MISSING_NS"></a><spanclass="term">DATASRC_QUERY_MISSING_NS missing NS records for '%1'</span></dt><dd><p>
NS records should have been put into the authority section. However, this zone
has none. This indicates problem with provided data.
</p></dd><dt><aname="DATASRC_QUERY_MISSING_SOA"></a><spanclass="term">DATASRC_QUERY_MISSING_SOA the zone '%1' has no SOA</span></dt><dd><p>
The answer should have been a negative one (eg. of nonexistence of something).
To do so, a SOA record should be put into the authority section, but the zone
does not have one. This indicates problem with provided data.
</p></dd><dt><aname="DATASRC_QUERY_NOGLUE_FAIL"></a><spanclass="term">DATASRC_QUERY_NOGLUE_FAIL the underlying data source failed with %1</span></dt><dd><p>
The underlying data source failed to answer the no-glue query. 1 means some
error, 2 is not implemented. The data source should have logged the specific
</p></dd><dt><aname="DATASRC_QUERY_NO_CACHE_ANY_AUTH"></a><spanclass="term">DATASRC_QUERY_NO_CACHE_ANY_AUTH ignoring hotspot cache for ANY query (%1/%2 in %3 class)</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_QUERY_NO_CACHE_ANY_SIMPLE"></a><spanclass="term">DATASRC_QUERY_NO_CACHE_ANY_SIMPLE ignoring hotspot cache for ANY query (%1/%2 in %3 class)</span></dt><dd><p>
Debug information. The hotspot cache is ignored for ANY queries for consistency
reasons.
</p></dd><dt><aname="DATASRC_QUERY_NO_DS_NSEC"></a><spanclass="term">DATASRC_QUERY_NO_DS_NSEC there's no DS record in the '%1' zone</span></dt><dd><p>
An attempt to add a NSEC record into the message failed, because the zone does
not have any DS record. This indicates problem with the provided data.
</p></dd><dt><aname="DATASRC_QUERY_NO_DS_NSEC3"></a><spanclass="term">DATASRC_QUERY_NO_DS_NSEC3 there's no DS record in the '%1' zone</span></dt><dd><p>
An attempt to add a NSEC3 record into the message failed, because the zone does
not have any DS record. This indicates problem with the provided data.
</p></dd><dt><aname="DATASRC_QUERY_NO_ZONE"></a><spanclass="term">DATASRC_QUERY_NO_ZONE no zone containing '%1' in class '%2'</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_QUERY_PROVE_NX_FAIL"></a><spanclass="term">DATASRC_QUERY_PROVE_NX_FAIL unable to prove nonexistence of '%1'</span></dt><dd><p>
The server is unable to answer a direct query for RRSIG type, but was asked
to do so.
</p></dd><dt><aname="DATASRC_QUERY_SIMPLE_FAIL"></a><spanclass="term">DATASRC_QUERY_SIMPLE_FAIL the underlying data source failed with %1</span></dt><dd><p>
The underlying data source failed to answer the simple query. 1 means some
error, 2 is not implemented. The data source should have logged the specific
error already.
</p></dd><dt><aname="DATASRC_QUERY_SYNTH_CNAME"></a><spanclass="term">DATASRC_QUERY_SYNTH_CNAME synthesizing CNAME from DNAME on '%1'</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_QUERY_WILDCARD_PROVE_NX_FAIL"></a><spanclass="term">DATASRC_QUERY_WILDCARD_PROVE_NX_FAIL unable to prove nonexistence of '%1' (%2)</span></dt><dd><p>
While processing a wildcard, it wasn't possible to prove nonexistence of the
given domain or record. The code is 1 for error and 2 for not implemented.
</p></dd><dt><aname="DATASRC_QUERY_WILDCARD_REFERRAL"></a><spanclass="term">DATASRC_QUERY_WILDCARD_REFERRAL unable to find referral info for '%1' (%2)</span></dt><dd><p>
While processing a wildcard, a referral was met. But it wasn't possible to get
enough information for it. The code is 1 for error, 2 for not implemented.
</p></dd><dt><aname="DATASRC_SQLITE_COMPATIBLE_VERSION"></a><spanclass="term">DATASRC_SQLITE_COMPATIBLE_VERSION database schema V%1.%2 not up to date (expecting V%3.%4) but is compatible</span></dt><dd><p>
The version of the SQLite3 database schema used to hold the zone data
is not the latest one - the current version of BIND 10 was written
with a later schema version in mind. However, the database is
compatible with the current version of BIND 10, and BIND 10 will run
without any problems.
</p><p>
Consult the release notes for your version of BIND 10. Depending on
the changes made to the database schema, it is possible that improved
performance could result if the database were upgraded.
</p></dd><dt><aname="DATASRC_SQLITE_ENCLOSURE_NOT_FOUND"></a><spanclass="term">DATASRC_SQLITE_ENCLOSURE_NOT_FOUND no zone contains '%1'</span></dt><dd><p>
</p></dd><dt><aname="DATASRC_SQLITE_FIND"></a><spanclass="term">DATASRC_SQLITE_FIND looking for RRset '%1/%2'</span></dt><dd><p>
Debug information. The SQLite data source is looking up a resource record
set.
</p></dd><dt><aname="DATASRC_SQLITE_FINDADDRS"></a><spanclass="term">DATASRC_SQLITE_FINDADDRS looking for A/AAAA addresses for '%1'</span></dt><dd><p>
Debug information. The data source is looking up the addresses for given
domain name.
</p></dd><dt><aname="DATASRC_SQLITE_FINDADDRS_BAD_CLASS"></a><spanclass="term">DATASRC_SQLITE_FINDADDRS_BAD_CLASS class mismatch looking for addresses ('%1' and '%2')</span></dt><dd><p>
The SQLite data source was looking up A/AAAA addresses, but the data source
contains different class than the query was for.
</p></dd><dt><aname="DATASRC_SQLITE_FINDEXACT"></a><spanclass="term">DATASRC_SQLITE_FINDEXACT looking for exact RRset '%1/%2'</span></dt><dd><p>
Debug information. The SQLite data source is looking up an exact resource
record.
</p></dd><dt><aname="DATASRC_SQLITE_FINDEXACT_BAD_CLASS"></a><spanclass="term">DATASRC_SQLITE_FINDEXACT_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')</span></dt><dd><p>
The SQLite data source was looking up an exact RRset, but the data source
contains different class than the query was for.
</p></dd><dt><aname="DATASRC_SQLITE_FINDREC"></a><spanclass="term">DATASRC_SQLITE_FINDREC looking for record '%1/%2'</span></dt><dd><p>
Debug information. The SQLite data source is looking up records of given name
and type in the database.
</p></dd><dt><aname="DATASRC_SQLITE_FINDREF"></a><spanclass="term">DATASRC_SQLITE_FINDREF looking for referral at '%1'</span></dt><dd><p>
Debug information. The SQLite data source is identifying if this domain is
a referral and where it goes.
</p></dd><dt><aname="DATASRC_SQLITE_FINDREF_BAD_CLASS"></a><spanclass="term">DATASRC_SQLITE_FINDREF_BAD_CLASS class mismatch looking for referral ('%1' and '%2')</span></dt><dd><p>
it contains different class than the query was for.
</p></dd><dt><aname="DATASRC_SQLITE_FIND_BAD_CLASS"></a><spanclass="term">DATASRC_SQLITE_FIND_BAD_CLASS class mismatch looking for an RRset ('%1' and '%2')</span></dt><dd><p>
The SQLite data source was looking up an RRset, but the data source contains
different class than the query was for.
</p></dd><dt><aname="DATASRC_SQLITE_FIND_NSEC3"></a><spanclass="term">DATASRC_SQLITE_FIND_NSEC3 looking for NSEC3 in zone '%1' for hash '%2'</span></dt><dd><p>
Debug information. We're trying to look up a NSEC3 record in the SQLite data
source.
</p></dd><dt><aname="DATASRC_SQLITE_FIND_NSEC3_NO_ZONE"></a><spanclass="term">DATASRC_SQLITE_FIND_NSEC3_NO_ZONE no such zone '%1'</span></dt><dd><p>
The SQLite data source was asked to provide a NSEC3 record for given zone.
</p></dd><dt><aname="DATASRC_SQLITE_INCOMPATIBLE_VERSION"></a><spanclass="term">DATASRC_SQLITE_INCOMPATIBLE_VERSION database schema V%1.%2 incompatible with version (V%3.%4) expected</span></dt><dd><p>
The version of the SQLite3 database schema used to hold the zone data
is incompatible with the version expected by BIND 10. As a result,
BIND 10 is unable to run using the database file as the data source.
</p><p>
The database should be updated using the means described in the BIND
</p></dd><dt><aname="DATASRC_STATIC_CLASS_NOT_CH"></a><spanclass="term">DATASRC_STATIC_CLASS_NOT_CH static data source can handle CH class only</span></dt><dd><p>
An error message indicating that a query requesting a RR for a class other
that CH was sent to the static data source (which only handles CH queries).
</p></dd><dt><aname="DBUTIL_BACKUP"></a><spanclass="term">DBUTIL_BACKUP created backup of %1 in %2</span></dt><dd><p>
A backup for the given database file was created. Same of original file and
backup are given in the output message.
</p></dd><dt><aname="DBUTIL_CHECK_ERROR"></a><spanclass="term">DBUTIL_CHECK_ERROR unable to check database version: %1</span></dt><dd><p>
There was an error while trying to check the current version of the database
schema. The error is shown in the message.
</p></dd><dt><aname="DBUTIL_CHECK_NOCONFIRM"></a><spanclass="term">DBUTIL_CHECK_NOCONFIRM --noconfirm is not compatible with --check</span></dt><dd><p>
b10-dbutil was called with --check and --noconfirm. --noconfirm only has
meaning with --upgrade, so this is considered an error.
</p></dd><dt><aname="DBUTIL_CHECK_OK"></a><spanclass="term">DBUTIL_CHECK_OK this is the latest version of the database schema. No upgrade is required</span></dt><dd><p>
The database schema version has been checked, and is up to date.
No action is required.
</p></dd><dt><aname="DBUTIL_CHECK_UPGRADE_NEEDED"></a><spanclass="term">DBUTIL_CHECK_UPGRADE_NEEDED re-run this program with the --upgrade switch to upgrade</span></dt><dd><p>
The database schema version is not up to date, and an update is required.
Please run the dbutil tool again, with the --upgrade argument.
</p></dd><dt><aname="DBUTIL_COMMAND_NONE"></a><spanclass="term">DBUTIL_COMMAND_NONE must select one of --check or --upgrade</span></dt><dd><p>
b10-dbutil was called with neither --check nor --upgrade. One action must be
provided.
</p></dd><dt><aname="DBUTIL_COMMAND_UPGRADE_CHECK"></a><spanclass="term">DBUTIL_COMMAND_UPGRADE_CHECK --upgrade is not compatible with --check</span></dt><dd><p>
b10-dbutil was called with both the commands --upgrade and --check. Only one
action can be performed at a time.
</p></dd><dt><aname="DBUTIL_DATABASE_MAY_BE_CORRUPT"></a><spanclass="term">DBUTIL_DATABASE_MAY_BE_CORRUPT database file %1 may be corrupt, restore it from backup (%2)</span></dt><dd><p>
The upgrade failed while it was in progress; the database may now be in an
inconsistent state, and it is advised to restore it from the backup that was
</p></dd><dt><aname="DBUTIL_NO_FILE"></a><spanclass="term">DBUTIL_NO_FILE must supply name of the database file to upgrade</span></dt><dd><p>
b10-dbutil was called without a database file. Currently, it cannot find this
file on its own, and it must be provided.
</p></dd><dt><aname="DBUTIL_STATEMENT_ERROR"></a><spanclass="term">DBUTIL_STATEMENT_ERROR failed to execute %1: %2</span></dt><dd><p>
The given database statement failed to execute. The error is shown in the
message.
</p></dd><dt><aname="DBUTIL_TOO_MANY_ARGUMENTS"></a><spanclass="term">DBUTIL_TOO_MANY_ARGUMENTS too many arguments to the command, maximum of one expected</span></dt><dd><p>
There were too many command-line arguments to b10-dbutil
</p></dd><dt><aname="DBUTIL_UPGRADE_CANCELED"></a><spanclass="term">DBUTIL_UPGRADE_CANCELED upgrade canceled; database has not been changed</span></dt><dd><p>
The user aborted the upgrade, and b10-dbutil will now exit.
</p></dd><dt><aname="DBUTIL_UPGRADE_DBUTIL"></a><spanclass="term">DBUTIL_UPGRADE_DBUTIL please get the latest version of b10-dbutil and re-run</span></dt><dd><p>
A database schema was found that was newer than this version of dbutil, which
is apparently out of date and should be upgraded itself.
While the upgrade was in progress, an unexpected error occurred. The error
is shown in the message.
</p></dd><dt><aname="DBUTIL_UPGRADE_NOT_ATTEMPTED"></a><spanclass="term">DBUTIL_UPGRADE_NOT_ATTEMPTED database upgrade was not attempted</span></dt><dd><p>
Due to the earlier failure, the database schema upgrade was not attempted,
and b10-dbutil will now exit.
</p></dd><dt><aname="DBUTIL_UPGRADE_NOT_NEEDED"></a><spanclass="term">DBUTIL_UPGRADE_NOT_NEEDED database already at latest version, no upgrade necessary</span></dt><dd><p>
b10-dbutil was told to upgrade the database schema, but it is already at the
latest version.
</p></dd><dt><aname="DBUTIL_UPGRADE_NOT_POSSIBLE"></a><spanclass="term">DBUTIL_UPGRADE_NOT_POSSIBLE database at a later version than this utility can support</span></dt><dd><p>
b10-dbutil was told to upgrade the database schema, but it is at a higher
version than this tool currently supports. Please update b10-dbutil and try
The database schema update was completed successfully.
</p></dd><dt><aname="DBUTIL_UPGRADING"></a><spanclass="term">DBUTIL_UPGRADING upgrading database from %1 to %2</span></dt><dd><p>
An upgrade is in progress, the versions of the current upgrade action are shown.
</p></dd><dt><aname="DBUTIL_VERSION_CURRENT"></a><spanclass="term">DBUTIL_VERSION_CURRENT database version %1</span></dt><dd><p>
The current version of the database schema.
</p></dd><dt><aname="DBUTIL_VERSION_HIGH"></a><spanclass="term">DBUTIL_VERSION_HIGH database is at a later version (%1) than this program can cope with (%2)</span></dt><dd><p>
The database schema is at a higher version than b10-dbutil knows about.
</p></dd><dt><aname="DBUTIL_VERSION_LOW"></a><spanclass="term">DBUTIL_VERSION_LOW database version %1, latest version is %2.</span></dt><dd><p>
The database schema is not up to date, the current version and the latest
</p></dd><dt><aname="DDNS_CC_SESSION_ERROR"></a><spanclass="term">DDNS_CC_SESSION_ERROR error reading from cc channel: %1</span></dt><dd><p>
There was a problem reading from the command and control channel. The
most likely cause is that the msgq process is not running.
</p></dd><dt><aname="DDNS_CC_SESSION_TIMEOUT_ERROR"></a><spanclass="term">DDNS_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response</span></dt><dd><p>
There was a problem reading a response from another module over the
command and control channel. The most likely cause is that the
configuration manager b10-cfgmgr is not running.
</p></dd><dt><aname="DDNS_CONFIG_ERROR"></a><spanclass="term">DDNS_CONFIG_ERROR error found in configuration data: %1</span></dt><dd><p>
The ddns process encountered an error when installing the configuration at
startup time. Details of the error are included in the log message.
</p></dd><dt><aname="DDNS_DROP_CONN"></a><spanclass="term">DDNS_DROP_CONN dropping connection on file descriptor %1 because of error %2</span></dt><dd><p>
There was an error on a connection with the b10-auth server (or whatever
connects to the ddns daemon). This might be OK, for example when the
authoritative server shuts down, the connection would get closed. It also
can mean the system is busy and can't keep up or that the other side got
</p></dd><dt><aname="DDNS_GET_REMOTE_CONFIG_FAIL"></a><spanclass="term">DDNS_GET_REMOTE_CONFIG_FAIL failed to get %1 module configuration %2 times: %3</span></dt><dd><p>
b10-ddns tried to get configuration of some remote modules for its
operation, but it failed. The most likely cause of this is that the
remote module has not fully started up and b10-ddns couldn't get the
configuration in a timely fashion. b10-ddns attempts to retry it a
few times, imposing a short delay, hoping it eventually succeeds if
it's just a timing issue. The number of total failed attempts is also
logged. If it reaches an internal threshold b10-ddns considers it a
fatal error and terminates. Even in that case, if b10-ddns is
configured as a "dispensable" component (which is the default), the
parent bind10 process will restart it, and there will be another
chance of getting the remote configuration successfully. These are
not the optimal behavior, but it's believed to be sufficient in
practice (there would normally be no failure in the first place). If
it really causes an operational trouble other than having a few of
these log messages, please submit a bug report; there can be several
ways to make it more sophisticated. Another, less likely reason for
having this error is because the remote modules are not actually
configured to run. If that's the case fixing the configuration should
solve the problem - either by making sure the remote module will run
or by not running b10-ddns (without these remote modules b10-ddns is
not functional, so there's no point in running it in this case).
</p></dd><dt><aname="DDNS_RECEIVED_AUTH_UPDATE"></a><spanclass="term">DDNS_RECEIVED_AUTH_UPDATE received configuration updates from auth server</span></dt><dd><p>
b10-ddns is notified of updates to b10-auth configuration
(including a report of the initial configuration) that b10-ddns might
</p></dd><dt><aname="DDNS_RECEIVED_ZONEMGR_UPDATE"></a><spanclass="term">DDNS_RECEIVED_ZONEMGR_UPDATE received configuration updates from zonemgr</span></dt><dd><p>
b10-ddns is notified of updates to b10-zonemgr's configuration
(including a report of the initial configuration). It may possibly
contain changes to the secondary zones, in which case b10-ddns will
update its internal copy of that configuration.
</p></dd><dt><aname="DDNS_REQUEST_PARSE_FAIL"></a><spanclass="term">DDNS_REQUEST_PARSE_FAIL failed to parse update request: %1</span></dt><dd><p>
b10-ddns received an update request via b10-auth, but the received
data failed to pass minimum validation: it was either broken wire
format data for a valid DNS message (e.g. it's shorter than the
fixed-length header), or the opcode is not update, or TSIG is included
in the request but it fails to validate. Since b10-auth should have
performed this level of checks, such an error shouldn't be detected at
this stage and should rather be considered an internal bug. This
event is therefore logged at the error level, and the request is
simply dropped. Additional information of the error is also logged.
b10-ddns received a new update request from a client over TCP, but
the number of TCP clients being handled by the server already reached
the configured quota, so the latest client was rejected by closing
the connection. The administrator may want to check the status of
b10-ddns, and if this happens even if the server is not very busy,
the quota may have to be increased. Or, if it's more likely to be
malicious or simply bogus clients that somehow keep the TCP connection
open for a long period, maybe they should be rejected with an
appropriate ACL configuration or some lower layer filtering. The
number of existing TCP clients are shown in the log, which should be
identical to the current quota.
</p></dd><dt><aname="DDNS_RESPONSE_SOCKET_ERROR"></a><spanclass="term">DDNS_RESPONSE_SOCKET_ERROR failed to send update response to %1: %2</span></dt><dd><p>
Network I/O error happens in sending an update response. The
client's address that caused the error and error details are also
logged.
</p></dd><dt><aname="DDNS_RESPONSE_TCP_SOCKET_ERROR"></a><spanclass="term">DDNS_RESPONSE_TCP_SOCKET_ERROR failed to complete sending update response to %1 over TCP</span></dt><dd><p>
b10-ddns had tried to send an update response over TCP, and it hadn't
been completed at that time, and a followup attempt to complete the
send operation failed due to some network I/O error. While a network
error can happen any time, this event is quite unexpected for two
reasons. First, since the size of a response to an update request
should be generally small, it's unlikely that the initial attempt
didn't fail but wasn't completed. Second, since the first attempt
succeeded and the TCP connection had been established in the first
place, it's more likely for the subsequent attempt to succeed. In any
case, there may not be able to do anything to fix it at the server
side, but the administrator may want to check the general reachability
with the client address.
</p></dd><dt><aname="DDNS_SECONDARY_ZONES_UPDATE"></a><spanclass="term">DDNS_SECONDARY_ZONES_UPDATE updated secondary zone list (%1 zones are listed)</span></dt><dd><p>
b10-ddns has successfully updated the internal copy of secondary zones
obtained from b10-zonemgr, based on a latest update to zonemgr's
configuration. The number of newly configured (unique) secondary
zones is logged.
</p></dd><dt><aname="DDNS_SECONDARY_ZONES_UPDATE_FAIL"></a><spanclass="term">DDNS_SECONDARY_ZONES_UPDATE_FAIL failed to update secondary zone list: %1</span></dt><dd><p>
An error message. b10-ddns was notified of updates to a list of
secondary zones from b10-zonemgr and tried to update its own internal
copy of the list, but it failed. This can happen if the configuration
contains an error, and b10-zonemgr should also reject that update.
Unfortunately, in the current implementation there is no way to ensure
that both zonemgr and ddns have consistent information when an update
contains an error; further, as of this writing zonemgr has a bug that
it could partially update the list of secondary zones if part of the
list has an error (see Trac ticket #2038). b10-ddns still keeps
running with the previous configuration, but it's strongly advisable
to check log messages from zonemgr, and if it indicates there can be
inconsistent state, it's better to restart the entire BIND 10 system
(just restarting b10-ddns wouldn't be enough, because zonemgr can have
partially updated configuration due to bug #2038). The log message
contains an error description, but it's intentionally kept simple as
it's primarily a matter of zonemgr. To know the details of the error,
</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
</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.
</p></dd><dt><aname="DDNS_UPDATE_NOTIFY"></a><spanclass="term">DDNS_UPDATE_NOTIFY notified %1 of updates to %2</span></dt><dd><p>
Debug message. b10-ddns has made updates to a zone based on an update
request and has successfully notified an external module of the updates.
The notified module will use that information for updating its own
state or any necessary protocol action such as zone reloading or sending
notify messages to secondary servers.
</p></dd><dt><aname="DDNS_UPDATE_NOTIFY_FAIL"></a><spanclass="term">DDNS_UPDATE_NOTIFY_FAIL failed to notify %1 of updates to %2: %3</span></dt><dd><p>
b10-ddns has made updates to a zone based on an update request and
tried to notify an external component of the updates, but the
notification fails. One possible cause of this is that the external
component is not really running and it times out in waiting for the
response, although it will be less likely to happen in practice
because these components will normally be configured to run when the
server provides the authoritative DNS service; ddns is rather optional
among them. If this happens, however, it will suspend b10-ddns for a
few seconds during which it cannot handle new requests (some may be
delayed, some may be dropped, depending on the volume of the incoming
requests). This is obviously bad, and if this error happens due to
this reason, the administrator should make sure the component in
question should be configured to run. For a longer term, b10-ddns
should be more robust about this case such as by making this
notification asynchronously and/or detecting the existence of the
external components to avoid hopeless notification in the first place.
Severity of this error for the receiving components depends on the
type of the component. If it's b10-xfrout, this means DNS notify
messages won't be sent to secondary servers of the zone. It's
suboptimal, but not necessarily critical as the secondary servers will
try to check the zone's status periodically. If it's b10-auth and the
notification was needed to have it reload the corresponding zone, it's
more serious because b10-auth won't be able to serve the new version
of the zone unless some explicit recovery action is taken. So the
administrator needs to examine this message and takes an appropriate
action. In either case, this notification is generally expected to
succeed; so the fact it fails itself means there's something wrong in
the BIND 10 system, and it would be advisable to check other log
messages.
</p></dd><dt><aname="LIBDDNS_DATASRC_ERROR"></a><spanclass="term">LIBDDNS_DATASRC_ERROR update client %1 failed due to data source error: %2</span></dt><dd><p>
An update attempt failed due to some error in the corresponding data
source. This is generally an unexpected event, but can still happen
for various reasons such as DB lock contention or a failure of the
backend DB server. The cause of the error is also logged. It's
advisable to check the message, and, if necessary, take an appropriate
action (e.g., restarting the DB server if it dies). If this message
is logged the data source isn't modified due to the
corresponding update request. When used by the b10-ddns, the server
will return a response with an RCODE of SERVFAIL.
</p></dd><dt><aname="LIBDDNS_PREREQ_FORMERR"></a><spanclass="term">LIBDDNS_PREREQ_FORMERR update client %1 for zone %2: Format error in prerequisite (%3). Non-zero TTL.</span></dt><dd><p>
The prerequisite with the given name, class and type is not well-formed.
The specific prerequisite is shown. In this case, it has a non-zero TTL value.
A FORMERR error response is sent to the client.
</p></dd><dt><aname="LIBDDNS_PREREQ_FORMERR_ANY"></a><spanclass="term">LIBDDNS_PREREQ_FORMERR_ANY update client %1 for zone %2: Format error in prerequisite (%3). Non-zero TTL or rdata found.</span></dt><dd><p>
The prerequisite with the given name, class and type is not well-formed.
The specific prerequisite is shown. In this case, it either has a non-zero
TTL value, or has rdata fields. A FORMERR error response is sent to the client.
</p></dd><dt><aname="LIBDDNS_PREREQ_FORMERR_CLASS"></a><spanclass="term">LIBDDNS_PREREQ_FORMERR_CLASS update client %1 for zone %2: Format error in prerequisite (%3). Bad class.</span></dt><dd><p>
The prerequisite with the given name, class and type is not well-formed.
The specific prerequisite is shown. In this case, the class of the
prerequisite should either match the class of the zone in the Zone Section,
or it should be ANY or NONE, and it is not. A FORMERR error response is sent
to the client.
</p></dd><dt><aname="LIBDDNS_PREREQ_FORMERR_NONE"></a><spanclass="term">LIBDDNS_PREREQ_FORMERR_NONE update client %1 for zone %2: Format error in prerequisite (%3). Non-zero TTL or rdata found.</span></dt><dd><p>
The prerequisite with the given name, class and type is not well-formed.
The specific prerequisite is shown. In this case, it either has a non-zero
TTL value, or has rdata fields. A FORMERR error response is sent to the client.
</p></dd><dt><aname="LIBDDNS_PREREQ_NAME_IN_USE_FAILED"></a><spanclass="term">LIBDDNS_PREREQ_NAME_IN_USE_FAILED update client %1 for zone %2: 'Name is in use' prerequisite not satisfied (%3), rcode: %4</span></dt><dd><p>
A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that
was not satisfied is shown. The client is sent an error response with the
given rcode.
In this case, the specific prerequisite is 'Name is in use'. From RFC2136:
Name is in use. At least one RR with a specified NAME (in
the zone and class specified by the Zone Section) must exist.
Note that this prerequisite is NOT satisfied by empty
nonterminals.
</p></dd><dt><aname="LIBDDNS_PREREQ_NAME_NOT_IN_USE_FAILED"></a><spanclass="term">LIBDDNS_PREREQ_NAME_NOT_IN_USE_FAILED update client %1 for zone %2: 'Name is not in use' (%3) prerequisite not satisfied, rcode: %4</span></dt><dd><p>
A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that
was not satisfied is shown. The client is sent an error response with the
given rcode.
In this case, the specific prerequisite is 'Name is not in use'.
From RFC2136:
Name is not in use. No RR of any type is owned by a
specified NAME. Note that this prerequisite IS satisfied by
empty nonterminals.
</p></dd><dt><aname="LIBDDNS_PREREQ_NOTZONE"></a><spanclass="term">LIBDDNS_PREREQ_NOTZONE update client %1 for zone %2: prerequisite not in zone (%3)</span></dt><dd><p>
A DDNS UPDATE prerequisite has a name that does not appear to be inside
the zone specified in the Zone section of the UPDATE message.
The specific prerequisite is shown. A NOTZONE error response is sent to
the client.
</p></dd><dt><aname="LIBDDNS_PREREQ_RRSET_DOES_NOT_EXIST_FAILED"></a><spanclass="term">LIBDDNS_PREREQ_RRSET_DOES_NOT_EXIST_FAILED update client %1 for zone %2: 'RRset does not exist' (%3) prerequisite not satisfied, rcode: %4</span></dt><dd><p>
A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that
was not satisfied is shown. The client is sent an error response with the
given rcode.
In this case, the specific prerequisite is 'RRset does not exist'.
From RFC2136:
RRset does not exist. No RRs with a specified NAME and TYPE
(in the zone and class denoted by the Zone Section) can exist.
</p></dd><dt><aname="LIBDDNS_PREREQ_RRSET_EXISTS_FAILED"></a><spanclass="term">LIBDDNS_PREREQ_RRSET_EXISTS_FAILED update client %1 for zone %2: 'RRset exists (value independent)' (%3) prerequisite not satisfied, rcode: %4</span></dt><dd><p>
A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that
was not satisfied is shown. The client is sent an error response with the
given rcode.
In this case, the specific prerequisite is 'RRset exists (value independent)'.
From RFC2136:
RRset exists (value dependent). A set of RRs with a
specified NAME and TYPE exists and has the same members
with the same RDATAs as the RRset specified here in this
Section.
</p></dd><dt><aname="LIBDDNS_PREREQ_RRSET_EXISTS_VAL_FAILED"></a><spanclass="term">LIBDDNS_PREREQ_RRSET_EXISTS_VAL_FAILED update client %1 for zone %2: 'RRset exists (value dependent)' (%3) prerequisite not satisfied, rcode: %4</span></dt><dd><p>
A DNS UPDATE prerequisite was not satisfied. The specific prerequisite that
was not satisfied is shown. The client is sent an error response with the
given rcode.
In this case, the specific prerequisite is 'RRset exists (value dependent)'.
From RFC2136:
RRset exists (value independent). At least one RR with a
specified NAME and TYPE (in the zone and class specified by
the Zone Section) must exist.
</p></dd><dt><aname="LIBDDNS_UPDATE_ADD_BAD_TYPE"></a><spanclass="term">LIBDDNS_UPDATE_ADD_BAD_TYPE update client %1 for zone %2: update addition RR bad type: %3</span></dt><dd><p>
The Update section of a DDNS update message contains a statement
that tries to add a record of an invalid type. Most likely the
record has an RRType that is considered a 'meta' type, which
cannot be zone content data. The specific record is shown.
A FORMERR response is sent back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_APPROVED"></a><spanclass="term">LIBDDNS_UPDATE_APPROVED update client %1 for zone %2 approved</span></dt><dd><p>
Debug message. An update request was approved in terms of the zone's
update ACL.
</p></dd><dt><aname="LIBDDNS_UPDATE_BAD_CLASS"></a><spanclass="term">LIBDDNS_UPDATE_BAD_CLASS update client %1 for zone %2: bad class in update RR: %3</span></dt><dd><p>
The Update section of a DDNS update message contains an RRset with
a bad class. The class of the update RRset must be either the same
as the class in the Zone Section, ANY, or NONE.
A FORMERR response is sent back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_DATASRC_ERROR"></a><spanclass="term">LIBDDNS_UPDATE_DATASRC_ERROR error in datasource during DDNS update: %1</span></dt><dd><p>
An error occured while committing the DDNS update changes to the
datasource. The specific error is printed. A SERVFAIL response is sent
back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_DELETE_BAD_TYPE"></a><spanclass="term">LIBDDNS_UPDATE_DELETE_BAD_TYPE update client %1 for zone %2: update deletion RR bad type: %3</span></dt><dd><p>
The Update section of a DDNS update message contains a statement
that tries to delete an rrset of an invalid type. Most likely the
record has an RRType that is considered a 'meta' type, which
cannot be zone content data. The specific record is shown.
A FORMERR response is sent back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_DELETE_NONZERO_TTL"></a><spanclass="term">LIBDDNS_UPDATE_DELETE_NONZERO_TTL update client %1 for zone %2: update deletion RR has non-zero TTL: %3</span></dt><dd><p>
The Update section of a DDNS update message contains a 'delete rrset'
statement with a non-zero TTL. This is not allowed by the protocol.
A FORMERR response is sent back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_DELETE_RRSET_NOT_EMPTY"></a><spanclass="term">LIBDDNS_UPDATE_DELETE_RRSET_NOT_EMPTY update client %1 for zone %2: update deletion RR contains data %3</span></dt><dd><p>
The Update section of a DDNS update message contains a 'delete rrset'
statement with a non-empty RRset. This is not allowed by the protocol.
A FORMERR response is sent back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_DELETE_RR_BAD_TYPE"></a><spanclass="term">LIBDDNS_UPDATE_DELETE_RR_BAD_TYPE update client %1 for zone %2: update deletion RR bad type: %3</span></dt><dd><p>
The Update section of a DDNS update message contains a statement
that tries to delete one or more rrs of an invalid type. Most
likely the records have an RRType that is considered a 'meta'
type, which cannot be zone content data. The specific record is
shown. A FORMERR response is sent back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_DELETE_RR_NONZERO_TTL"></a><spanclass="term">LIBDDNS_UPDATE_DELETE_RR_NONZERO_TTL update client %1 for zone %2: update deletion RR has non-zero TTL: %3</span></dt><dd><p>
The Update section of a DDNS update message contains a 'delete rrs'
statement with a non-zero TTL. This is not allowed by the protocol.
A FORMERR response is sent back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_DENIED"></a><spanclass="term">LIBDDNS_UPDATE_DENIED update client %1 for zone %2 denied</span></dt><dd><p>
Informational message. An update request was denied because it was
rejected by the zone's update ACL. When this library is used by
b10-ddns, the server will respond to the request with an RCODE of
REFUSED as described in Section 3.3 of RFC2136.
</p></dd><dt><aname="LIBDDNS_UPDATE_DROPPED"></a><spanclass="term">LIBDDNS_UPDATE_DROPPED update client %1 for zone %2 dropped</span></dt><dd><p>
Informational message. An update request was denied because it was
rejected by the zone's update ACL. When this library is used by
b10-ddns, the server will then completely ignore the request; no
response will be sent.
</p></dd><dt><aname="LIBDDNS_UPDATE_ERROR"></a><spanclass="term">LIBDDNS_UPDATE_ERROR update client %1 for zone %2: %3</span></dt><dd><p>
Debug message. An error is found in processing a dynamic update
request. This log message is used for general errors that are not
normally expected to happen. So, in general, it would mean some
problem in the client implementation or an interoperability issue
with this implementation. The client's address, the zone name and
class, and description of the error are logged.
</p></dd><dt><aname="LIBDDNS_UPDATE_FORWARD_FAIL"></a><spanclass="term">LIBDDNS_UPDATE_FORWARD_FAIL update client %1 for zone %2: update forwarding not supported</span></dt><dd><p>
Debug message. An update request is sent to a secondary server. This
is not necessarily invalid, but this implementation does not yet
support update forwarding as specified in Section 6 of RFC2136 and it
will simply return a response with an RCODE of NOTIMP to the client.
The client's address and the zone name/class are logged.
</p></dd><dt><aname="LIBDDNS_UPDATE_NOTAUTH"></a><spanclass="term">LIBDDNS_UPDATE_NOTAUTH update client %1 for zone %2: not authoritative for update zone</span></dt><dd><p>
Debug message. An update request was received for a zone for which
the receiving server doesn't have authority. In theory this is an
unexpected event, but there are client implementations that could send
update requests carelessly, so it may not necessarily be so uncommon
in practice. If possible, you may want to check the implementation or
configuration of those clients to suppress the requests. As specified
in Section 3.1 of RFC2136, the receiving server will return a response
with an RCODE of NOTAUTH.
</p></dd><dt><aname="LIBDDNS_UPDATE_NOTZONE"></a><spanclass="term">LIBDDNS_UPDATE_NOTZONE update client %1 for zone %2: update RR out of zone %3</span></dt><dd><p>
A DDNS UPDATE record has a name that does not appear to be inside
the zone specified in the Zone section of the UPDATE message.
The specific update record is shown. A NOTZONE error response is
sent to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_PREREQUISITE_FAILED"></a><spanclass="term">LIBDDNS_UPDATE_PREREQUISITE_FAILED prerequisite failed in update client %1 for zone %2: result code %3</span></dt><dd><p>
The handling of the prerequisite section (RFC2136 Section 3.2) found
that one of the prerequisites was not satisfied. The result code
should give more information on what prerequisite type failed.
If the result code is FORMERR, the prerequisite section was not well-formed.
An error response with the given result code is sent back to the client.
</p></dd><dt><aname="LIBDDNS_UPDATE_UNCAUGHT_EXCEPTION"></a><spanclass="term">LIBDDNS_UPDATE_UNCAUGHT_EXCEPTION update client %1 for zone %2: uncaught exception while processing update section: %3</span></dt><dd><p>
An uncaught exception was encountered while processing the Update
section of a DDNS message. The specific exception is shown in the log message.
To make sure DDNS service is not interrupted, this problem is caught instead
of reraised; The update is aborted, and a SERVFAIL is sent back to the client.
This is most probably a bug in the DDNS code, but *could* be caused by
</p></dd><dt><aname="LIBXFRIN_DIFFERENT_TTL"></a><spanclass="term">LIBXFRIN_DIFFERENT_TTL multiple data with different TTLs (%1, %2) on %3/%4/%5. Adjusting %2 -> %1.</span></dt><dd><p>
</p></dd><dt><aname="LOGIMPL_ABOVE_MAX_DEBUG"></a><spanclass="term">LOGIMPL_ABOVE_MAX_DEBUG debug level of %1 is too high and will be set to the maximum of %2</span></dt><dd><p>
A message from the interface to the underlying logger implementation reporting
that the debug level (as set by an internally-created string DEBUGn, where n
is an integer, e.g. DEBUG22) is above the maximum allowed value and has
been reduced to that value. The appearance of this message may indicate
a programming error - please submit a bug report.
</p></dd><dt><aname="LOGIMPL_BAD_DEBUG_STRING"></a><spanclass="term">LOGIMPL_BAD_DEBUG_STRING debug string '%1' has invalid format</span></dt><dd><p>
A message from the interface to the underlying logger implementation
reporting that an internally-created string used to set the debug level
is not of the correct format (it should be of the form DEBUGn, where n
is an integer, e.g. DEBUG22). The appearance of this message indicates
a programming error - please submit a bug report.
</p></dd><dt><aname="LOGIMPL_BELOW_MIN_DEBUG"></a><spanclass="term">LOGIMPL_BELOW_MIN_DEBUG debug level of %1 is too low and will be set to the minimum of %2</span></dt><dd><p>
A message from the interface to the underlying logger implementation reporting
that the debug level (as set by an internally-created string DEBUGn, where n
is an integer, e.g. DEBUG22) is below the minimum allowed value and has
been increased to that value. The appearance of this message may indicate
</p></dd><dt><aname="LOG_DUPLICATE_MESSAGE_ID"></a><spanclass="term">LOG_DUPLICATE_MESSAGE_ID duplicate message ID (%1) in compiled code</span></dt><dd><p>
</p></dd><dt><aname="LOG_NAMESPACE_EXTRA_ARGS"></a><spanclass="term">LOG_NAMESPACE_EXTRA_ARGS line %1: $NAMESPACE directive has too many arguments</span></dt><dd><p>
The $NAMESPACE directive in a message file takes a single argument, a
namespace in which all the generated symbol names are placed. This error
is generated when the compiler finds a $NAMESPACE directive with more
than one argument.
</p></dd><dt><aname="LOG_NAMESPACE_INVALID_ARG"></a><spanclass="term">LOG_NAMESPACE_INVALID_ARG line %1: $NAMESPACE directive has an invalid argument ('%2')</span></dt><dd><p>
The $NAMESPACE argument in a message file should be a valid C++ namespace.
This message is output if the simple check on the syntax of the string
carried out by the reader fails.
</p></dd><dt><aname="LOG_NAMESPACE_NO_ARGS"></a><spanclass="term">LOG_NAMESPACE_NO_ARGS line %1: no arguments were given to the $NAMESPACE directive</span></dt><dd><p>
The $NAMESPACE directive in a message file takes a single argument,
a C++ namespace in which all the generated symbol names are placed.
This error is generated when the compiler finds a $NAMESPACE directive
with no arguments.
</p></dd><dt><aname="LOG_NO_MESSAGE_ID"></a><spanclass="term">LOG_NO_MESSAGE_ID line %1: message definition line found without a message ID</span></dt><dd><p>
Within a message file, message are defined by lines starting with a "%".
The rest of the line should comprise the message ID and text describing
the message. This error indicates the message compiler found a line in
the message file comprising just the "%" and nothing else.
</p></dd><dt><aname="LOG_NO_MESSAGE_TEXT"></a><spanclass="term">LOG_NO_MESSAGE_TEXT line %1: line found containing a message ID ('%2') and no text</span></dt><dd><p>
Within a message file, message are defined by lines starting with a "%".
The rest of the line should comprise the message ID and text describing
the message. This error indicates the message compiler found a line
in the message file comprising just the "%" and message identification,
but no text.
</p></dd><dt><aname="LOG_NO_SUCH_MESSAGE"></a><spanclass="term">LOG_NO_SUCH_MESSAGE could not replace message text for '%1': no such message</span></dt><dd><p>
</p></dd><dt><aname="LOG_OPEN_OUTPUT_FAIL"></a><spanclass="term">LOG_OPEN_OUTPUT_FAIL unable to open %1 for output: %2</span></dt><dd><p>
Originating within the logging code, the program was not able to open
the specified output file for the reason given.
</p></dd><dt><aname="LOG_PREFIX_EXTRA_ARGS"></a><spanclass="term">LOG_PREFIX_EXTRA_ARGS line %1: $PREFIX directive has too many arguments</span></dt><dd><p>
Within a message file, the $PREFIX directive takes a single argument,
a prefix to be added to the symbol names when a C++ file is created.
This error is generated when the compiler finds a $PREFIX directive with
more than one argument.
</p><p>
Note: the $PREFIX directive is deprecated and will be removed in a future
</p></dd><dt><aname="LOG_PREFIX_INVALID_ARG"></a><spanclass="term">LOG_PREFIX_INVALID_ARG line %1: $PREFIX directive has an invalid argument ('%2')</span></dt><dd><p>
Within a message file, the $PREFIX directive takes a single argument,
a prefix to be added to the symbol names when a C++ file is created.
As such, it must adhere to restrictions on C++ symbol names (e.g. may
only contain alphanumeric characters or underscores, and may nor start
with a digit). A $PREFIX directive was found with an argument (given
</p></dd><dt><aname="NOTIFY_OUT_DATASRC_ACCESS_FAILURE"></a><spanclass="term">NOTIFY_OUT_DATASRC_ACCESS_FAILURE failed to get access to data source: %1</span></dt><dd><p>
notify_out failed to get access to one of configured data sources.
Detailed error is shown in the log message. This can be either a
configuration error or installation setup failure.
</p></dd><dt><aname="NOTIFY_OUT_DATASRC_ZONE_NOT_FOUND"></a><spanclass="term">NOTIFY_OUT_DATASRC_ZONE_NOT_FOUND Zone %1 is not found</span></dt><dd><p>
notify_out attempted to get slave information of a zone but the zone
isn't found in the expected data source. This shouldn't happen,
because notify_out first identifies a list of available zones before
this process. So this means some critical inconsistency in the data
The notify_out library tried to send a notify message to the given
address, but it appears to be an invalid address. The configuration
for secondary nameservers might contain a typographic error, or a
different BIND 10 module has forgotten to validate its data before
sending this module a notify command. As such, this should normally
not happen, and points to an oversight in a different module.
</p></dd><dt><aname="NOTIFY_OUT_REPLY_BAD_OPCODE"></a><spanclass="term">NOTIFY_OUT_REPLY_BAD_OPCODE bad opcode in notify reply from %1#%2: %3</span></dt><dd><p>
The notify_out library sent a notify message to the nameserver at
the given address, but the response did not have the opcode set to
NOTIFY. The opcode in the response is printed. Since there was a
response, no more notifies will be sent to this server for this
notification event.
</p></dd><dt><aname="NOTIFY_OUT_REPLY_BAD_QID"></a><spanclass="term">NOTIFY_OUT_REPLY_BAD_QID bad QID in notify reply from %1#%2: got %3, should be %4</span></dt><dd><p>
The notify_out library sent a notify message to the nameserver at
the given address, but the query id in the response does not match
the one we sent. Since there was a response, no more notifies will
be sent to this server for this notification event.
</p></dd><dt><aname="NOTIFY_OUT_REPLY_BAD_QUERY_NAME"></a><spanclass="term">NOTIFY_OUT_REPLY_BAD_QUERY_NAME bad query name in notify reply from %1#%2: got %3, should be %4</span></dt><dd><p>
The notify_out library sent a notify message to the nameserver at
the given address, but the query name in the response does not match
the one we sent. Since there was a response, no more notifies will
be sent to this server for this notification event.
</p></dd><dt><aname="NOTIFY_OUT_REPLY_QR_NOT_SET"></a><spanclass="term">NOTIFY_OUT_REPLY_QR_NOT_SET QR flags set to 0 in reply to notify from %1#%2</span></dt><dd><p>
The notify_out library sent a notify message to the namesever at the
given address, but the reply did not have the QR bit set to one.
Since there was a response, no more notifies will be sent to this
There was an uncaught exception in the handling of a notify reply
message, either in the message parser, or while trying to extract data
from the parsed message. The error is printed, and notify_out will
treat the response as a bad message, but this does point to a
programming error, since all exceptions should have been caught
explicitly. Please file a bug report. Since there was a response,
no more notifies will be sent to this server for this notification
event.
</p></dd><dt><aname="NOTIFY_OUT_RETRY_EXCEEDED"></a><spanclass="term">NOTIFY_OUT_RETRY_EXCEEDED notify to %1#%2: number of retries (%3) exceeded</span></dt><dd><p>
The maximum number of retries for the notify target has been exceeded.
Either the address of the secondary nameserver is wrong, or it is not
responding.
</p></dd><dt><aname="NOTIFY_OUT_SENDING_NOTIFY"></a><spanclass="term">NOTIFY_OUT_SENDING_NOTIFY sending notify to %1#%2</span></dt><dd><p>
A notify message is sent to the secondary nameserver at the given
address.
</p></dd><dt><aname="NOTIFY_OUT_SOCKET_ERROR"></a><spanclass="term">NOTIFY_OUT_SOCKET_ERROR socket error sending notify to %1#%2: %3</span></dt><dd><p>
There was a network error while trying to send a notify message to
the given address. The address might be unreachable. The socket
error is printed and should provide more information.
</p></dd><dt><aname="NOTIFY_OUT_SOCKET_RECV_ERROR"></a><spanclass="term">NOTIFY_OUT_SOCKET_RECV_ERROR socket error reading notify reply from %1#%2: %3</span></dt><dd><p>
There was a network error while trying to read a notify reply
message from the given address. The socket error is printed and should
provide more information.
</p></dd><dt><aname="NOTIFY_OUT_TIMEOUT"></a><spanclass="term">NOTIFY_OUT_TIMEOUT retry notify to %1#%2</span></dt><dd><p>
The notify message to the given address (noted as address#port) has
timed out, and the message will be resent until the max retry limit
</p></dd><dt><aname="NSAS_EMPTY_RESPONSE"></a><spanclass="term">NSAS_EMPTY_RESPONSE response to query for %1 returned an empty answer section</span></dt><dd><p>
The NSAS (nameserver address store - part of the resolver) made a query
for information it needed. The query completed successfully but the
answer section in the response was empty.
</p></dd><dt><aname="NSAS_ERROR_RESPONSE"></a><spanclass="term">NSAS_ERROR_RESPONSE error response of %1 returned in query for %2</span></dt><dd><p>
The NSAS (nameserver address store - part of the resolver) made a query
for information it needed. The query completed successfully but the
RCODE in the response was something other than NOERROR.
</p></dd><dt><aname="NSAS_FIND_NS_ADDRESS"></a><spanclass="term">NSAS_FIND_NS_ADDRESS asking resolver to obtain A and AAAA records for %1</span></dt><dd><p>
A debug message issued when the NSAS (nameserver address store - part
of the resolver) is making a callback into the resolver to retrieve the
address records for the specified nameserver.
</p></dd><dt><aname="NSAS_FOUND_ADDRESS"></a><spanclass="term">NSAS_FOUND_ADDRESS found address %1 for %2</span></dt><dd><p>
A debug message issued when the NSAS (nameserver address store - part
of the resolver) has retrieved the given address for the specified
nameserver through an external query.
</p></dd><dt><aname="NSAS_LOOKUP_CANCEL"></a><spanclass="term">NSAS_LOOKUP_CANCEL lookup for zone %1 has been canceled</span></dt><dd><p>
A debug message issued when an NSAS (nameserver address store - part of
the resolver) lookup for a zone has been canceled.
</p></dd><dt><aname="NSAS_NS_LOOKUP_FAIL"></a><spanclass="term">NSAS_NS_LOOKUP_FAIL failed to lookup any %1 for %2</span></dt><dd><p>
A debug message issued when the NSAS (nameserver address store - part of
the resolver) has been unable to retrieve the specified resource record
for the specified nameserver. This is not necessarily a problem - the
nameserver may be unreachable, in which case the NSAS will try other
</p></dd><dt><aname="NSAS_NULL_RESPONSE"></a><spanclass="term">NSAS_NULL_RESPONSE got null message in success callback for query for %1</span></dt><dd><p>
The NSAS (nameserver address store - part of the resolver) made a query
for information it needed. The query completed successfully, but the
message passed to the callback was null.
</p><p>
This message indicates an internal error in the NSAS. Please raise a
reporting the update of a round-trip time (RTT) for a query made to the
specified nameserver. The RTT has been updated using the value given
and the new RTT is displayed. (The RTT is subject to a calculation that
damps out sudden changes. As a result, the new RTT used by the NSAS in
future decisions of which nameserver to use is not necessarily equal to
the RTT reported.)
</p></dd><dt><aname="NSAS_WRONG_ANSWER"></a><spanclass="term">NSAS_WRONG_ANSWER queried for %1 RR of type/class %2/%3, received response %4/%5</span></dt><dd><p>
A NSAS (nameserver address store - part of the resolver) made a query for
a resource record of a particular type and class, but instead received
an answer with a different given type and class.
</p><p>
This message indicates an internal error in the NSAS. Please raise a
</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
operations. The destination address and the total size of the message
(including the 2-byte length field) are shown in the log message.
</p></dd><dt><aname="PYSERVER_COMMON_DNS_TCP_SEND_ERROR"></a><spanclass="term">PYSERVER_COMMON_DNS_TCP_SEND_ERROR failed to send TCP message to %1 (%2/%3 bytes sent): %4</span></dt><dd><p>
A DNS message has been attempted to be sent out over a TCP connection,
but it failed due to some network error. Although it's not expected
to happen too often, it can still happen for various reasons. The
administrator may want to examine the cause of the failure, which is
included in the log message, to see if it requires some action to
be taken at the server side. When this message is logged, the
corresponding TCP connection was closed immediately after the error
was detected.
</p></dd><dt><aname="PYSERVER_COMMON_DNS_TCP_SEND_PENDING"></a><spanclass="term">PYSERVER_COMMON_DNS_TCP_SEND_PENDING sent part TCP message to %1 (up to %2/%3 bytes)</span></dt><dd><p>
Debug message. A part of DNS message has been transmitted over a TCP
connection, and it's suspended because further attempt would block.
The destination address and the total size of the message that has
been transmitted so far (including the 2-byte length field) are shown
</p></dd><dt><aname="PYSERVER_COMMON_TSIG_KEYRING_DEINIT"></a><spanclass="term">PYSERVER_COMMON_TSIG_KEYRING_DEINIT Deinitializing global TSIG keyring</span></dt><dd><p>
A debug message noting that the global TSIG keyring is being removed from
memory. Most programs don't do that, they just exit, which is OK.
</p></dd><dt><aname="PYSERVER_COMMON_TSIG_KEYRING_INIT"></a><spanclass="term">PYSERVER_COMMON_TSIG_KEYRING_INIT Initializing global TSIG keyring</span></dt><dd><p>
A debug message noting the TSIG keyring storage is being prepared. It should
appear at most once in the lifetime of a program. The keyring still needs
to be loaded from configuration.
</p></dd><dt><aname="PYSERVER_COMMON_TSIG_KEYRING_UPDATE"></a><spanclass="term">PYSERVER_COMMON_TSIG_KEYRING_UPDATE Updating global TSIG keyring</span></dt><dd><p>
A debug message. The TSIG keyring is being (re)loaded from configuration.
This happens at startup or when the configuration changes. The old keyring
</p></dd><dt><aname="RESLIB_DEEPEST"></a><spanclass="term">RESLIB_DEEPEST did not find <%1> in cache, deepest delegation found is %2</span></dt><dd><p>
A debug message, a cache lookup did not find the specified <name,
class, type> tuple in the cache; instead, the deepest delegation found
is indicated.
</p></dd><dt><aname="RESLIB_EMPTY_RESPONSE"></a><spanclass="term">RESLIB_EMPTY_RESPONSE empty response received to query for <%1></span></dt><dd><p>
A debug message, the response to the specified query from an upstream
nameserver did not contain anything in the answer or authority sections,
although in all other respects it was a valid response. A SERVFAIL will
be returned to the system making the original query.
</p></dd><dt><aname="RESLIB_ERROR_RESPONSE"></a><spanclass="term">RESLIB_ERROR_RESPONSE unspecified error received in response to query for <%1></span></dt><dd><p>
A debug message, the response to the specified query to an upstream
nameserver indicated that the response was classified as an erroneous
response, but that the nature of the error cannot be identified.
A SERVFAIL will be returned to the system making the original query.
</p></dd><dt><aname="RESLIB_EXTRADATA_RESPONSE"></a><spanclass="term">RESLIB_EXTRADATA_RESPONSE extra data in response to query for <%1></span></dt><dd><p>
A debug message indicating that the response to the specified query
from an upstream nameserver contained too much data. This can happen if
an ANY query was sent and the answer section in the response contained
multiple RRs with different names. A SERVFAIL will be returned to the
A debug message, a CNAME response was received and another query is
being issued for the <name, class, type> tuple.
</p></dd><dt><aname="RESLIB_INVALID_NAMECLASS_RESPONSE"></a><spanclass="term">RESLIB_INVALID_NAMECLASS_RESPONSE invalid name or class in response to query for <%1></span></dt><dd><p>
A debug message, the response to the specified query from an upstream
nameserver (as identified by the ID of the response) contained either
an answer not matching the query name or an answer having a different
class to that queried for. A SERVFAIL will be returned to the system
making the original query.
</p></dd><dt><aname="RESLIB_INVALID_QNAME_RESPONSE"></a><spanclass="term">RESLIB_INVALID_QNAME_RESPONSE invalid name or class in response to query for <%1></span></dt><dd><p>
A debug message, the response to the specified query from an upstream
nameserver (as identified by the ID of the response) contained a name
in the question section that did not match that of the query. A SERVFAIL
will be returned to the system making the original query.
</p></dd><dt><aname="RESLIB_INVALID_TYPE_RESPONSE"></a><spanclass="term">RESLIB_INVALID_TYPE_RESPONSE invalid name or class in response to query for <%1></span></dt><dd><p>
A debug message, the response to the specified query from an upstream
nameserver (as identified by the ID of the response) contained an
invalid type field. A SERVFAIL will be returned to the system making
</p></dd><dt><aname="RESLIB_LONG_CHAIN"></a><spanclass="term">RESLIB_LONG_CHAIN CNAME received in response to query for <%1>: CNAME chain length exceeded</span></dt><dd><p>
</p></dd><dt><aname="RESLIB_MULTIPLE_CLASS_RESPONSE"></a><spanclass="term">RESLIB_MULTIPLE_CLASS_RESPONSE response to query for <%1> contained multiple RRsets with different classes</span></dt><dd><p>
A debug message reporting that the response to an upstream query for
the specified name contained multiple RRsets in the answer and not all
were of the same class. This is a violation of the standard and so a
SERVFAIL will be returned.
</p></dd><dt><aname="RESLIB_NOTSINGLE_RESPONSE"></a><spanclass="term">RESLIB_NOTSINGLE_RESPONSE response to query for <%1> was not a response</span></dt><dd><p>
A debug message, the response to the specified query from an upstream
nameserver was a CNAME that had mutiple RRs in the RRset. This is
an invalid response according to the standards so a SERVFAIL will be
returned to the system making the original query.
</p></dd><dt><aname="RESLIB_NOT_ONE_QNAME_RESPONSE"></a><spanclass="term">RESLIB_NOT_ONE_QNAME_RESPONSE not one question in response to query for <%1></span></dt><dd><p>
A debug message, the response to the specified query from an upstream
nameserver (as identified by the ID of the response) did not contain
one name in the question section as required by the standard. A SERVFAIL
will be returned to the system making the original query.
</p></dd><dt><aname="RESLIB_NOT_RESPONSE"></a><spanclass="term">RESLIB_NOT_RESPONSE response to query for <%1> was not a response</span></dt><dd><p>
A debug message, the response to the specified query from an upstream
nameserver (as identified by the ID of the response) did not have the QR
bit set (thus indicating that the packet was a query, not a response).
A SERVFAIL will be returned to the system making the original query.
</p></dd><dt><aname="RESLIB_NO_NS_RRSET"></a><spanclass="term">RESLIB_NO_NS_RRSET no NS RRSet in referral response received to query for <%1></span></dt><dd><p>
</p></dd><dt><aname="RESLIB_NXDOM_NXRR"></a><spanclass="term">RESLIB_NXDOM_NXRR NXDOMAIN/NXRRSET received in response to query for <%1></span></dt><dd><p>
</p></dd><dt><aname="RESLIB_OPCODE_RESPONSE"></a><spanclass="term">RESLIB_OPCODE_RESPONSE response to query for <%1> did not have query opcode</span></dt><dd><p>
A debug message, the response to the specified query from an upstream
nameserver was a response that did not have the opcode set to that of
a query. According to the standards, this is an invalid response to
the query that was made, so a SERVFAIL will be returned to the system
</p></dd><dt><aname="RESLIB_RCODE_ERROR"></a><spanclass="term">RESLIB_RCODE_ERROR response to query for <%1> returns RCODE of %2</span></dt><dd><p>
</p></dd><dt><aname="RESLIB_RECQ_CACHE_FIND"></a><spanclass="term">RESLIB_RECQ_CACHE_FIND found <%1> in the cache (resolve() instance %2)</span></dt><dd><p>
</p></dd><dt><aname="RESLIB_RECQ_CACHE_NO_FIND"></a><spanclass="term">RESLIB_RECQ_CACHE_NO_FIND did not find <%1> in the cache, starting RunningQuery (resolve() instance %2)</span></dt><dd><p>
</p></dd><dt><aname="RESLIB_RRSET_FOUND"></a><spanclass="term">RESLIB_RRSET_FOUND found single RRset in the cache when querying for <%1> (resolve() instance %2)</span></dt><dd><p>
</p></dd><dt><aname="RESLIB_TEST_UPSTREAM"></a><spanclass="term">RESLIB_TEST_UPSTREAM sending upstream query for <%1> to test server at %2</span></dt><dd><p>
A debug message indicating that the specified query has timed out and that
the resolver is repeating the query to the same nameserver. After this
repeated query, there will be the indicated number of retries left.
</p></dd><dt><aname="RESLIB_TRUNCATED"></a><spanclass="term">RESLIB_TRUNCATED response to query for <%1> was truncated, re-querying over TCP</span></dt><dd><p>
A debug message, this indicates that the response to the specified query was
truncated and that the resolver will be re-querying over TCP. There are
various reasons why responses may be truncated, so this message is normal and
gives no cause for concern.
</p></dd><dt><aname="RESLIB_UPSTREAM"></a><spanclass="term">RESLIB_UPSTREAM sending upstream query for <%1> to %2</span></dt><dd><p>
A debug message indicating that a query for the specified <name, class, type>
tuple is being sent to a nameserver whose address is given in the message.
</p></dd><dt><aname="RESOLVER_NEGATIVE_RETRIES"></a><spanclass="term">RESOLVER_NEGATIVE_RETRIES negative number of retries (%1) specified in the configuration</span></dt><dd><p>
</p></dd><dt><aname="RESOLVER_NOTIFY_RECEIVED"></a><spanclass="term">RESOLVER_NOTIFY_RECEIVED NOTIFY arrived but server is not authoritative</span></dt><dd><p>
</p></dd><dt><aname="RESOLVER_NOT_ONE_QUESTION"></a><spanclass="term">RESOLVER_NOT_ONE_QUESTION query contained %1 questions, exactly one question was expected</span></dt><dd><p>
</p></dd><dt><aname="RESOLVER_UNEXPECTED_RESPONSE"></a><spanclass="term">RESOLVER_UNEXPECTED_RESPONSE received unexpected response, ignoring</span></dt><dd><p>
</p></dd><dt><aname="RESOLVER_UNSUPPORTED_OPCODE"></a><spanclass="term">RESOLVER_UNSUPPORTED_OPCODE opcode %1 not supported by the resolver</span></dt><dd><p>
</p></dd><dt><aname="SOCKETREQUESTOR_CREATED"></a><spanclass="term">SOCKETREQUESTOR_CREATED Socket requestor created for application %1</span></dt><dd><p>
Debug message. The socket requestor created at SOCKETREQUESTOR_CREATED
has been destroyed. This event is generally unexpected other than in
test cases.
</p></dd><dt><aname="SOCKETREQUESTOR_GETSOCKET"></a><spanclass="term">SOCKETREQUESTOR_GETSOCKET Received a %1 socket for [%2]:%3, FD=%4, token=%5, path=%6</span></dt><dd><p>
Debug message. The socket requestor for the corresponding application
has requested a socket for a set of address, port and protocol (shown
in the log message) and successfully got it from the creator. The
corresponding file descriptor and the associated "token" (an internal
ID used between the creator and requestor) are shown in the log
message.
</p></dd><dt><aname="SOCKETREQUESTOR_RELEASESOCKET"></a><spanclass="term">SOCKETREQUESTOR_RELEASESOCKET Released a socket of token %1</span></dt><dd><p>
Debug message. The socket requestor has released a socket passed by
the creator. The associated token of the socket is shown in the
log message. If the corresponding SOCKETREQUESTOR_GETSOCKET was logged
more detailed information of the socket can be identified by matching
</p></dd><dt><aname="SRVCOMM_ADDRESSES_NOT_LIST"></a><spanclass="term">SRVCOMM_ADDRESSES_NOT_LIST the address and port specification is not a list in %1</span></dt><dd><p>
This points to an error in configuration. What was supposed to be a list of
IP address - port pairs isn't a list at all but something else.
</p></dd><dt><aname="SRVCOMM_ADDRESS_FAIL"></a><spanclass="term">SRVCOMM_ADDRESS_FAIL failed to listen on addresses (%1)</span></dt><dd><p>
The server failed to bind to one of the address/port pair it should according
to configuration, for reason listed in the message (usually because that pair
is already used by other service or missing privileges). The server will try
to recover and bind the address/port pairs it was listening to before (if any).
</p></dd><dt><aname="SRVCOMM_ADDRESS_MISSING"></a><spanclass="term">SRVCOMM_ADDRESS_MISSING address specification is missing "address" or "port" element in %1</span></dt><dd><p>
This points to an error in configuration. An address specification in the
configuration is missing either an address or port and so cannot be used. The
specification causing the error is given in the message.
</p></dd><dt><aname="SRVCOMM_ADDRESS_TYPE"></a><spanclass="term">SRVCOMM_ADDRESS_TYPE address specification type is invalid in %1</span></dt><dd><p>
This points to an error in configuration. An address specification in the
configuration malformed. The specification causing the error is given in the
message. A valid specification contains an address part (which must be a string
and must represent a valid IPv4 or IPv6 address) and port (which must be an
integer in the range valid for TCP/UDP ports on your system).
</p></dd><dt><aname="SRVCOMM_ADDRESS_UNRECOVERABLE"></a><spanclass="term">SRVCOMM_ADDRESS_UNRECOVERABLE failed to recover original addresses also (%1)</span></dt><dd><p>
</p></dd><dt><aname="SRVCOMM_UNKNOWN_EXCEPTION_ALLOC"></a><spanclass="term">SRVCOMM_UNKNOWN_EXCEPTION_ALLOC unknown exception when allocating a socket</span></dt><dd><p>
The situation is the same as in the SRVCOMM_EXCEPTION_ALLOC case, but further
details about the error are unknown, because it was signaled by throwing
something not being an exception. This is definitely a bug.
A shutdown command was sent to the stats-httpd module, and it will
now shut down.
</p></dd><dt><aname="STATHTTPD_RECEIVED_STATUS_COMMAND"></a><spanclass="term">STATHTTPD_RECEIVED_STATUS_COMMAND received command to return status</span></dt><dd><p>
A status command was sent to the stats-httpd module, and it will
respond with 'Stats Httpd is up.' and its PID.
</p></dd><dt><aname="STATHTTPD_RECEIVED_UNKNOWN_COMMAND"></a><spanclass="term">STATHTTPD_RECEIVED_UNKNOWN_COMMAND received unknown command: %1</span></dt><dd><p>
An unknown command has been sent to the stats-httpd module. The
stats-httpd module will respond with an error, and the command will
</p></dd><dt><aname="STATS_RECEIVED_SHOWSCHEMA_ALL_COMMAND"></a><spanclass="term">STATS_RECEIVED_SHOWSCHEMA_ALL_COMMAND received command to show all statistics schema</span></dt><dd><p>
The stats module received a command to show all statistics schemas of all modules.
</p></dd><dt><aname="STATS_RECEIVED_SHOWSCHEMA_NAME_COMMAND"></a><spanclass="term">STATS_RECEIVED_SHOWSCHEMA_NAME_COMMAND received command to show statistics schema for %1</span></dt><dd><p>
The stats module received a command to show the specified statistics schema of the specified module.
</p></dd><dt><aname="STATS_RECEIVED_SHOW_ALL_COMMAND"></a><spanclass="term">STATS_RECEIVED_SHOW_ALL_COMMAND received command to show all statistics</span></dt><dd><p>
The stats module received a command to show all statistics that it has
collected.
</p></dd><dt><aname="STATS_RECEIVED_SHOW_NAME_COMMAND"></a><spanclass="term">STATS_RECEIVED_SHOW_NAME_COMMAND received command to show statistics for %1</span></dt><dd><p>
The stats module received a command to show the statistics that it has
A shutdown command was sent to the stats module and it will now shut down.
</p></dd><dt><aname="STATS_RECEIVED_STATUS_COMMAND"></a><spanclass="term">STATS_RECEIVED_STATUS_COMMAND received command to return status</span></dt><dd><p>
A status command was sent to the stats module. It will return a
response indicating that it is running normally.
</p></dd><dt><aname="STATS_RECEIVED_UNKNOWN_COMMAND"></a><spanclass="term">STATS_RECEIVED_UNKNOWN_COMMAND received unknown command: %1</span></dt><dd><p>
An unknown command has been sent to the stats module. The stats module
will respond with an error and the command will be ignored.
</p></dd><dt><aname="STATS_SEND_REQUEST_BOSS"></a><spanclass="term">STATS_SEND_REQUEST_BOSS requesting boss to send statistics</span></dt><dd><p>
This debug message is printed when a request is sent to the boss module
</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
"same" (not only for the serial), but it is still not clear what the
receiver should do if this condition does not hold. There was a discussion
</p></dd><dt><aname="XFRIN_BAD_MASTER_ADDR_FORMAT"></a><spanclass="term">XFRIN_BAD_MASTER_ADDR_FORMAT bad format for master address: %1</span></dt><dd><p>
The given master address is not a valid IP address.
</p></dd><dt><aname="XFRIN_BAD_MASTER_PORT_FORMAT"></a><spanclass="term">XFRIN_BAD_MASTER_PORT_FORMAT bad format for master port: %1</span></dt><dd><p>
The master port as read from the configuration is not a valid port number.
</p></dd><dt><aname="XFRIN_BAD_TSIG_KEY_STRING"></a><spanclass="term">XFRIN_BAD_TSIG_KEY_STRING bad TSIG key string: %1</span></dt><dd><p>
The TSIG key string as read from the configuration does not represent
a valid TSIG key.
</p></dd><dt><aname="XFRIN_BAD_ZONE_CLASS"></a><spanclass="term">XFRIN_BAD_ZONE_CLASS Invalid zone class: %1</span></dt><dd><p>
The zone class as read from the configuration is not a valid DNS class.
</p></dd><dt><aname="XFRIN_CC_SESSION_ERROR"></a><spanclass="term">XFRIN_CC_SESSION_ERROR error reading from cc channel: %1</span></dt><dd><p>
There was a problem reading from the command and control channel. The
most likely cause is that xfrin the msgq daemon is not running.
</p></dd><dt><aname="XFRIN_COMMAND_ERROR"></a><spanclass="term">XFRIN_COMMAND_ERROR error while executing command '%1': %2</span></dt><dd><p>
There was an error while the given command was being processed. The
error is given in the log message.
</p></dd><dt><aname="XFRIN_CONNECT_MASTER"></a><spanclass="term">XFRIN_CONNECT_MASTER error connecting to master at %1: %2</span></dt><dd><p>
There was an error opening a connection to the master. The error is
</p></dd><dt><aname="XFRIN_IXFR_UPTODATE"></a><spanclass="term">XFRIN_IXFR_UPTODATE IXFR requested serial for %1 is %2, master has %3, not updating</span></dt><dd><p>
The first SOA record in an IXFR response indicates the zone's serial
at the primary server is not newer than the client's. This is
basically unexpected event because normally the client first checks
the SOA serial by an SOA query, but can still happen if the transfer
is manually invoked or (although unlikely) there is a rapid change at
the primary server between the SOA and IXFR queries. The client
implementation confirms the whole response is this single SOA, and
</p></dd><dt><aname="XFRIN_MSGQ_SEND_ERROR_ZONE_MANAGER"></a><spanclass="term">XFRIN_MSGQ_SEND_ERROR_ZONE_MANAGER error while contacting %1</span></dt><dd><p>
There was a problem sending a message to the zone manager. This most
likely means that the msgq daemon has quit or was killed.
</p></dd><dt><aname="XFRIN_NOTIFY_UNKNOWN_MASTER"></a><spanclass="term">XFRIN_NOTIFY_UNKNOWN_MASTER got notification to retransfer zone %1 from %2, expected %3</span></dt><dd><p>
The system received a notify for the given zone, but the address it came
from does not match the master address in the Xfrin configuration. The notify
is ignored. This may indicate that the configuration for the master is wrong,
that a wrong machine is sending notifies, or that fake notifies are being sent.
</p></dd><dt><aname="XFRIN_RETRANSFER_UNKNOWN_ZONE"></a><spanclass="term">XFRIN_RETRANSFER_UNKNOWN_ZONE got notification to retransfer unknown zone %1</span></dt><dd><p>
There was an internal command to retransfer the given zone, but the
zone is not known to the system. This may indicate that the configuration
for xfrin is incomplete, or there was a typographical error in the
</p></dd><dt><aname="XFRIN_TRANSFER_SUCCESS"></a><spanclass="term">XFRIN_TRANSFER_SUCCESS full %1 transfer of zone %2 succeeded (messages: %3, records: %4, bytes: %5, run time: %6 seconds, %7 bytes/second)</span></dt><dd><p>
The AXFR transfer of the given zone was successful.
The provided information contains the following values:
</p><p>
messages: Number of overhead DNS messages in the transfer
</p><p>
records: Number of Resource Records in the full transfer, excluding the
final SOA record that marks the end of the AXFR.
</p><p>
bytes: Full size of the transfer data on the wire.
</p><p>
run time: Time (in seconds) the complete axfr took
</p></dd><dt><aname="XFRIN_XFR_OTHER_FAILURE"></a><spanclass="term">XFRIN_XFR_OTHER_FAILURE %1 transfer of zone %2 failed: %3</span></dt><dd><p>
The XFR transfer for the given zone has failed due to a problem outside
of the xfrin module. Possible reasons are a broken DNS message or failure
in database connection. The error is shown in the log message.
</p></dd><dt><aname="XFRIN_XFR_PROCESS_FAILURE"></a><spanclass="term">XFRIN_XFR_PROCESS_FAILURE %1 transfer of zone %2/%3 failed: %4</span></dt><dd><p>
An XFR session failed outside the main protocol handling. This
includes an error at the data source level at the initialization
phase, unexpected failure in the network connection setup to the
master server, or even more unexpected failure due to unlikely events
such as memory allocation failure. Details of the error are shown in
the log message. In general, these errors are not really expected
ones, and indicate an installation error or a program bug. The
session handler thread tries to clean up all intermediate resources
even on these errors, but it may be incomplete. So, if this log
message continuously appears, system resource consumption should be
checked, and you may even want to disable the corresponding transfers.
You may also want to file a bug report if this message appears so
</p></dd><dt><aname="XFRIN_XFR_TRANSFER_FAILURE"></a><spanclass="term">XFRIN_XFR_TRANSFER_FAILURE %1 transfer of zone %2 with %3 failed: %4</span></dt><dd><p>
The XFR transfer for the given zone has failed due to an internal error.
</p></dd><dt><aname="XFRIN_XFR_TRANSFER_FALLBACK"></a><spanclass="term">XFRIN_XFR_TRANSFER_FALLBACK falling back from IXFR to AXFR for %1</span></dt><dd><p>
The IXFR transfer of the given zone failed. This might happen in many cases,
such that the remote server doesn't support IXFR, we don't have the SOA record
(or the zone at all), we are out of sync, etc. In many of these situations,
AXFR could still work. Therefore we try that one in case it helps.
</p></dd><dt><aname="XFRIN_XFR_TRANSFER_PROTOCOL_ERROR"></a><spanclass="term">XFRIN_XFR_TRANSFER_PROTOCOL_ERROR %1 transfer of zone %2 with %3 failed: %4</span></dt><dd><p>
The XFR transfer for the given zone has failed due to a protocol
error, such as an unexpected response from the primary server. The
error is shown in the log message. It may be because the primary
server implementation is broken or (although less likely) there was
some attack attempt, but it can also happen due to configuration
mismatch such as the remote server does not have authority for the
zone any more but the local configuration hasn't been updated. So it
is recommended to check the primary server configuration.
</p></dd><dt><aname="XFRIN_ZONE_CREATED"></a><spanclass="term">XFRIN_ZONE_CREATED Zone %1 not found in the given data source, newly created</span></dt><dd><p>
On starting an xfrin session, it is identified that the zone to be
transferred is not found in the data source. This can happen if a
secondary DNS server first tries to perform AXFR from a primary server
without creating the zone image beforehand (e.g. by b10-loadzone). As
of this writing the xfrin process provides backward compatible
behavior to previous versions: creating a new one in the data source
not to surprise existing users too much. This is probably not a good
idea, however, in terms of who should be responsible for managing
zones at a higher level. In future it is more likely that a separate
zone management framework is provided, and the situation where the
given zone isn't found in xfrout will be treated as an error.
</p></dd><dt><aname="XFRIN_ZONE_MULTIPLE_SOA"></a><spanclass="term">XFRIN_ZONE_MULTIPLE_SOA Zone %1 has %2 SOA RRs</span></dt><dd><p>
On starting an xfrin session, it is identified that the zone to be
transferred has multiple SOA RRs. Such a zone is broken, but could be
accidentally configured especially in a data source using "non
captive" backend database. The implementation ignores entire SOA RRs
and tries to continue processing as if the zone were empty. This
means subsequent AXFR can succeed and possibly replace the zone with
valid content, but an IXFR attempt will fail.
</p></dd><dt><aname="XFRIN_ZONE_NO_SOA"></a><spanclass="term">XFRIN_ZONE_NO_SOA Zone %1 does not have SOA</span></dt><dd><p>
On starting an xfrin session, it is identified that the zone to be
transferred does not have an SOA RR in the data source. This is not
necessarily an error; if a secondary DNS server first tries to perform
transfer from a primary server, the zone can be empty, and therefore
doesn't have an SOA. Subsequent AXFR will fill in the zone; if the
attempt is IXFR it will fail in query creation.
</p></dd><dt><aname="XFRIN_ZONE_SERIAL_AHEAD"></a><spanclass="term">XFRIN_ZONE_SERIAL_AHEAD Serial number (%1) for %2 received from master %3 < ours (%4)</span></dt><dd><p>
The response to an SOA query prior to xfr indicated that the zone's
SOA serial at the primary server is smaller than that of the xfrin
client. This is not necessarily an error especially if that
particular primary server is another secondary server which hasn't got
the latest version of the zone. But if the primary server is known to
be the real source of the zone, some unexpected inconsistency may have
happened, and you may want to take a closer look. In this case xfrin
</p></dd><dt><aname="XFROUT_BAD_TSIG_KEY_STRING"></a><spanclass="term">XFROUT_BAD_TSIG_KEY_STRING bad TSIG key string: %1</span></dt><dd><p>
The TSIG key string as read from the configuration does not represent
a valid TSIG key.
</p></dd><dt><aname="XFROUT_CC_SESSION_ERROR"></a><spanclass="term">XFROUT_CC_SESSION_ERROR error reading from cc channel: %1</span></dt><dd><p>
There was a problem reading from the command and control channel. The
most likely cause is that the msgq daemon is not running.
</p></dd><dt><aname="XFROUT_CC_SESSION_TIMEOUT_ERROR"></a><spanclass="term">XFROUT_CC_SESSION_TIMEOUT_ERROR timeout waiting for cc response</span></dt><dd><p>
</p></dd><dt><aname="XFROUT_FETCH_REQUEST_ERROR"></a><spanclass="term">XFROUT_FETCH_REQUEST_ERROR socket error while fetching a request from the auth daemon</span></dt><dd><p>
There was a socket error while contacting the b10-auth daemon to
fetch a transfer request. The auth daemon may have shutdown.
</p></dd><dt><aname="XFROUT_HANDLE_QUERY_ERROR"></a><spanclass="term">XFROUT_HANDLE_QUERY_ERROR error while handling query: %1</span></dt><dd><p>
There was a general error handling an xfrout query. The error is shown
in the message. In principle this error should not appear, and points
to an oversight catching exceptions in the right place. However, to
ensure the daemon keeps running, this error is caught and reported.
</p></dd><dt><aname="XFROUT_IXFR_MULTIPLE_SOA"></a><spanclass="term">XFROUT_IXFR_MULTIPLE_SOA IXFR client %1: authority section has multiple SOAs</span></dt><dd><p>
An IXFR request was received with more than one SOA RRs in the authority
section. The xfrout daemon rejects the request with an RCODE of
FORMERR.
</p></dd><dt><aname="XFROUT_IXFR_NO_JOURNAL_SUPPORT"></a><spanclass="term">XFROUT_IXFR_NO_JOURNAL_SUPPORT IXFR client %1, %2: journaling not supported in the data source, falling back to AXFR</span></dt><dd><p>
An IXFR request was received but the underlying data source did
not support journaling. The xfrout daemon fell back to AXFR-style
An IXFR request was received with no SOA RR in the authority section.
The xfrout daemon rejects the request with an RCODE of FORMERR.
</p></dd><dt><aname="XFROUT_IXFR_NO_VERSION"></a><spanclass="term">XFROUT_IXFR_NO_VERSION IXFR client %1, %2: version (%3 to %4) not in journal, falling back to AXFR</span></dt><dd><p>
An IXFR request was received, but the requested range of differences
were not found in the data source. The xfrout daemon fell back to
AXFR-style IXFR.
</p></dd><dt><aname="XFROUT_IXFR_NO_ZONE"></a><spanclass="term">XFROUT_IXFR_NO_ZONE IXFR client %1, %2: zone not found with journal</span></dt><dd><p>
The requested zone in IXFR was not found in the data source
even though the xfrout daemon sucessfully found the SOA RR of the zone
in the data source. This can happen if the administrator removed the
zone from the data source within the small duration between these
operations, but it's more likely to be a bug or broken data source.
Unless you know why this message was logged, and especially if it
happens often, it's advisable to check whether the data source is
valid for this zone. The xfrout daemon considers it a possible,
though unlikely, event, and returns a response with an RCODE of
NOTAUTH.
</p></dd><dt><aname="XFROUT_IXFR_UPTODATE"></a><spanclass="term">XFROUT_IXFR_UPTODATE IXFR client %1, %2: client version is new enough (theirs=%3, ours=%4)</span></dt><dd><p>
An IXFR request was received, but the client's SOA version is the same as
or newer than that of the server. The xfrout server responds to the
request with the answer section being just one SOA of that version.
Note: as of this wrting the 'newer version' cannot be identified due to
the lack of support for the serial number arithmetic. This will soon
be implemented.
</p></dd><dt><aname="XFROUT_MODULECC_SESSION_ERROR"></a><spanclass="term">XFROUT_MODULECC_SESSION_ERROR error encountered by configuration/command module: %1</span></dt><dd><p>
There was a problem in the lower level module handling configuration and
control commands. This could happen for various reasons, but the most likely
cause is that the configuration database contains a syntax error and xfrout
failed to start at initialization. A detailed error message from the module
</p></dd><dt><aname="XFROUT_QUERY_DROPPED"></a><spanclass="term">XFROUT_QUERY_DROPPED %1 client %2: request to transfer %3 dropped</span></dt><dd><p>
The xfrout process silently dropped a request to transfer zone to
given host. This is required by the ACLs. The %2 represents the IP
address and port of the peer requesting the transfer, and the %3
represents the zone name and class.
</p></dd><dt><aname="XFROUT_QUERY_QUOTA_EXCCEEDED"></a><spanclass="term">XFROUT_QUERY_QUOTA_EXCCEEDED %1 client %2: request denied due to quota (%3)</span></dt><dd><p>
The xfr request was rejected because the server was already handling
the maximum number of allowable transfers as specified in the transfers_out
configuration parameter, which is also shown in the log message. The
request was immediately responded and terminated with an RCODE of REFUSED.
This can happen for a busy xfrout server, and you may want to increase
this parameter; if the server is being too busy due to requests from
unexpected clients you may want to restrict the legitimate clients
with ACL.
</p></dd><dt><aname="XFROUT_QUERY_REJECTED"></a><spanclass="term">XFROUT_QUERY_REJECTED %1 client %2: request to transfer %3 rejected</span></dt><dd><p>
The xfrout daemon received a shutdown command from the command channel
and will now shut down.
</p></dd><dt><aname="XFROUT_RECEIVE_FILE_DESCRIPTOR_ERROR"></a><spanclass="term">XFROUT_RECEIVE_FILE_DESCRIPTOR_ERROR error receiving the file descriptor for an XFR connection</span></dt><dd><p>
There was an error receiving the file descriptor for the transfer
When shutting down, the xfrout daemon tried to clear the unix socket
file used for communication with the auth daemon. It failed to remove
the file. The reason for the failure is given in the error message.
</p></dd><dt><aname="XFROUT_SOCKET_SELECT_ERROR"></a><spanclass="term">XFROUT_SOCKET_SELECT_ERROR error while calling select() on request socket: %1</span></dt><dd><p>
There was an error while calling select() on the socket that informs
the xfrout daemon that a new xfrout request has arrived. This should
be a result of rare local error such as memory allocation failure and
shouldn't happen under normal conditions. The error is included in the
There was a keyboard interrupt signal to stop the xfrout daemon. The
daemon will now shut down.
</p></dd><dt><aname="XFROUT_STOPPING"></a><spanclass="term">XFROUT_STOPPING the xfrout daemon is shutting down</span></dt><dd><p>
The current transfer is aborted, as the xfrout daemon is shutting down.
</p></dd><dt><aname="XFROUT_UNIX_SOCKET_FILE_IN_USE"></a><spanclass="term">XFROUT_UNIX_SOCKET_FILE_IN_USE another xfrout process seems to be using the unix socket file %1</span></dt><dd><p>
While starting up, the xfrout daemon tried to clear the unix domain
socket needed for contacting the b10-auth daemon to pass requests
on, but the file is in use. The most likely cause is that another
xfrout daemon process is still running. This xfrout daemon (the one
</p></dd><dt><aname="XFROUT_XFR_TRANSFER_CHECK_ERROR"></a><spanclass="term">XFROUT_XFR_TRANSFER_CHECK_ERROR %1 client %2: check for transfer of %3 failed: %4</span></dt><dd><p>
Pre-response check for an incomding XFR request failed unexpectedly.
The most likely cause of this is that some low level error in the data
source, but it may also be other general (more unlikely) errors such
as memory shortage. Some detail of the error is also included in the
message. The xfrout server tries to return a SERVFAIL response in this case.
</p></dd><dt><aname="XFROUT_XFR_TRANSFER_DONE"></a><spanclass="term">XFROUT_XFR_TRANSFER_DONE %1 client %2: transfer of %3 complete</span></dt><dd><p>
The transfer of the given zone has been completed successfully, or was
aborted due to a shutdown event.
</p></dd><dt><aname="XFROUT_XFR_TRANSFER_ERROR"></a><spanclass="term">XFROUT_XFR_TRANSFER_ERROR %1 client %2: error transferring zone %3: %4</span></dt><dd><p>
An uncaught exception was encountered while sending the response to
an AXFR query. The error message of the exception is included in the
log message, but this error most likely points to incomplete exception
handling in the code.
</p></dd><dt><aname="XFROUT_XFR_TRANSFER_FAILED"></a><spanclass="term">XFROUT_XFR_TRANSFER_FAILED %1 client %2: transfer of %3 failed, rcode: %4</span></dt><dd><p>
A transfer out for the given zone failed. An error response is sent
to the client. The given rcode is the rcode that is set in the error
response. This is either NOTAUTH (we are not authoritative for the
zone), SERVFAIL (our internal database is missing the SOA record for
the zone), or REFUSED (the limit of simultaneous outgoing AXFR
transfers, as specified by the configuration value
Xfrout/max_transfers_out, has been reached).
</p></dd><dt><aname="XFROUT_XFR_TRANSFER_STARTED"></a><spanclass="term">XFROUT_XFR_TRANSFER_STARTED %1 client %2: transfer of zone %3 has started</span></dt><dd><p>
An error was encountered on the command channel. The message indicates
the nature of the error.
</p></dd><dt><aname="ZONEMGR_JITTER_TOO_BIG"></a><spanclass="term">ZONEMGR_JITTER_TOO_BIG refresh_jitter is too big, setting to 0.5</span></dt><dd><p>
The value specified in the configuration for the refresh jitter is too large
so its value has been set to the maximum of 0.5.
</p></dd><dt><aname="ZONEMGR_KEYBOARD_INTERRUPT"></a><spanclass="term">ZONEMGR_KEYBOARD_INTERRUPT exiting zonemgr process as result of keyboard interrupt</span></dt><dd><p>
An informational message output when the zone manager was being run at a
terminal and it was terminated via a keyboard interrupt signal.
</p></dd><dt><aname="ZONEMGR_LOAD_ZONE"></a><spanclass="term">ZONEMGR_LOAD_ZONE loading zone %1 (class %2)</span></dt><dd><p>
This is a debug message indicating that the zone of the specified class
is being loaded.
</p></dd><dt><aname="ZONEMGR_NO_MASTER_ADDRESS"></a><spanclass="term">ZONEMGR_NO_MASTER_ADDRESS internal BIND 10 command did not contain address of master</span></dt><dd><p>
A command received by the zone manager from the Auth module did not
contain the address of the master server from which a NOTIFY message
was received. This may be due to an internal programming error; please
submit a bug report.
</p></dd><dt><aname="ZONEMGR_NO_SOA"></a><spanclass="term">ZONEMGR_NO_SOA zone %1 (class %2) does not have an SOA record</span></dt><dd><p>
When loading the named zone of the specified class the zone manager
discovered that the data did not contain an SOA record. The load has
been abandoned.
</p></dd><dt><aname="ZONEMGR_NO_TIMER_THREAD"></a><spanclass="term">ZONEMGR_NO_TIMER_THREAD trying to stop zone timer thread but it is not running</span></dt><dd><p>
An attempt was made to stop the timer thread (used to track when zones
should be refreshed) but it was not running. This may indicate an
internal program error. Please submit a bug report.
</p></dd><dt><aname="ZONEMGR_NO_ZONE_CLASS"></a><spanclass="term">ZONEMGR_NO_ZONE_CLASS internal BIND 10 command did not contain class of zone</span></dt><dd><p>
A command received by the zone manager from another BIND 10 module did
not contain the class of the zone on which the zone manager should act.
This may be due to an internal programming error; please submit a
bug report.
</p></dd><dt><aname="ZONEMGR_NO_ZONE_NAME"></a><spanclass="term">ZONEMGR_NO_ZONE_NAME internal BIND 10 command did not contain name of zone</span></dt><dd><p>
A command received by the zone manager from another BIND 10 module did
not contain the name of the zone on which the zone manager should act.
This may be due to an internal programming error; please submit a
bug report.
</p></dd><dt><aname="ZONEMGR_RECEIVE_NOTIFY"></a><spanclass="term">ZONEMGR_RECEIVE_NOTIFY received NOTIFY command for zone %1 (class %2)</span></dt><dd><p>
This is a debug message indicating that the zone manager has received a
NOTIFY command over the command channel. The command is sent by the Auth
process when it is acting as a slave server for the zone and causes the
zone manager to record the master server for the zone and start a timer;
when the timer expires, the master will be polled to see if it contains
new data.
</p></dd><dt><aname="ZONEMGR_RECEIVE_SHUTDOWN"></a><spanclass="term">ZONEMGR_RECEIVE_SHUTDOWN received SHUTDOWN command</span></dt><dd><p>
This is a debug message indicating that the zone manager has received
a SHUTDOWN command over the command channel from the Boss process.
It will act on this command and shut down.
</p></dd><dt><aname="ZONEMGR_RECEIVE_UNKNOWN"></a><spanclass="term">ZONEMGR_RECEIVE_UNKNOWN received unknown command '%1'</span></dt><dd><p>
This is a warning message indicating that the zone manager has received
the stated command over the command channel. The command is not known
to the zone manager and although the command is ignored, its receipt
may indicate an internal error. Please submit a bug report.
</p></dd><dt><aname="ZONEMGR_RECEIVE_XFRIN_FAILED"></a><spanclass="term">ZONEMGR_RECEIVE_XFRIN_FAILED received XFRIN FAILED command for zone %1 (class %2)</span></dt><dd><p>
This is a debug message indicating that the zone manager has received
an XFRIN FAILED command over the command channel. The command is sent
by the Xfrin process when a transfer of zone data into the system has
failed, and causes the zone manager to schedule another transfer attempt.
</p></dd><dt><aname="ZONEMGR_RECEIVE_XFRIN_SUCCESS"></a><spanclass="term">ZONEMGR_RECEIVE_XFRIN_SUCCESS received XFRIN SUCCESS command for zone %1 (class %2)</span></dt><dd><p>
This is a debug message indicating that the zone manager has received
an XFRIN SUCCESS command over the command channel. The command is sent
by the Xfrin process when the transfer of zone data into the system has
succeeded, and causes the data to be loaded and served by BIND 10.
</p></dd><dt><aname="ZONEMGR_REFRESH_ZONE"></a><spanclass="term">ZONEMGR_REFRESH_ZONE refreshing zone %1 (class %2)</span></dt><dd><p>
The zone manager is refreshing the named zone of the specified class
with updated information.
</p></dd><dt><aname="ZONEMGR_SELECT_ERROR"></a><spanclass="term">ZONEMGR_SELECT_ERROR error with select(): %1</span></dt><dd><p>
An attempt to wait for input from a socket failed. The failing operation
is a call to the operating system's select() function, which failed for
the given reason.
</p></dd><dt><aname="ZONEMGR_SEND_FAIL"></a><spanclass="term">ZONEMGR_SEND_FAIL failed to send command to %1, session has been closed</span></dt><dd><p>
The zone manager attempted to send a command to the named BIND 10 module,
but the send failed. The session between the modules has been closed.
</p></dd><dt><aname="ZONEMGR_SESSION_ERROR"></a><spanclass="term">ZONEMGR_SESSION_ERROR unable to establish session to command channel daemon</span></dt><dd><p>
The zonemgr process was not able to be started because it could not
connect to the command channel daemon. The most usual cause of this
problem is that the daemon is not running.
</p></dd><dt><aname="ZONEMGR_SESSION_TIMEOUT"></a><spanclass="term">ZONEMGR_SESSION_TIMEOUT timeout on session to command channel daemon</span></dt><dd><p>
The zonemgr process was not able to be started because it timed out when
connecting to the command channel daemon. The most usual cause of this
problem is that the daemon is not running.
</p></dd><dt><aname="ZONEMGR_SHUTDOWN"></a><spanclass="term">ZONEMGR_SHUTDOWN zone manager has shut down</span></dt><dd><p>
A debug message, output when the zone manager has shut down completely.
</p></dd><dt><aname="ZONEMGR_STARTING"></a><spanclass="term">ZONEMGR_STARTING zone manager starting</span></dt><dd><p>
A debug message output when the zone manager starts up.
</p></dd><dt><aname="ZONEMGR_TIMER_THREAD_RUNNING"></a><spanclass="term">ZONEMGR_TIMER_THREAD_RUNNING trying to start timer thread but one is already running</span></dt><dd><p>
This message is issued when an attempt is made to start the timer
thread (which keeps track of when zones need a refresh) but one is
already running. It indicates either an error in the program logic or
a problem with stopping a previous instance of the timer. Please submit
a bug report.
</p></dd><dt><aname="ZONEMGR_UNKNOWN_ZONE_FAIL"></a><spanclass="term">ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager</span></dt><dd><p>
An XFRIN operation has failed but the zone that was the subject of the
</p></dd><dt><aname="ZONEMGR_UNKNOWN_ZONE_NOTIFIED"></a><spanclass="term">ZONEMGR_UNKNOWN_ZONE_NOTIFIED notified zone %1 (class %2) is not known to the zone manager</span></dt><dd><p>
A NOTIFY was received but the zone that was the subject of the operation
is not being managed by the zone manager. This may indicate an error
in the program (as the operation should not have been initiated if this
were the case). Please submit a bug report.
</p></dd><dt><aname="ZONEMGR_UNKNOWN_ZONE_SUCCESS"></a><spanclass="term">ZONEMGR_UNKNOWN_ZONE_SUCCESS zone %1 (class %2) is not known to the zone manager</span></dt><dd><p>
An XFRIN operation has succeeded but the zone received is not being
managed by the zone manager. This may indicate an error in the program
(as the operation should not have been initiated if this were the case).
