<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 20110809. 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="id1168229460045"></a>BIND 10 Messages Manual</h1></div><div><pclass="releaseinfo">This is the messages manual for BIND 10 version
20110809.</p></div><div><pclass="copyright">Copyright <20> 2011 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_FETCH_COMPLETED"></a><spanclass="term">ASIODNS_FETCH_COMPLETED upstream fetch to %1(%2) has now completed</span></dt><dd><p>
A debug message, this records that the upstream fetch (a query made by the
</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
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_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="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
While listening on the message bus channel for messages, it suddenly
disappeared. The msgq daemon may have died. This might lead to an
inconsistent state of the system, and BIND 10 will now shut down.
</p></dd><dt><aname="BIND10_PROCESS_ENDED_NO_EXIT_STATUS"></a><spanclass="term">BIND10_PROCESS_ENDED_NO_EXIT_STATUS process %1 (PID %2) died: exit status not available</span></dt><dd><p>
The given process ended unexpectedly, but no exit status is
available. See BIND10_PROCESS_ENDED_WITH_EXIT_STATUS for a longer
description.
</p></dd><dt><aname="BIND10_PROCESS_ENDED_WITH_EXIT_STATUS"></a><spanclass="term">BIND10_PROCESS_ENDED_WITH_EXIT_STATUS process %1 (PID %2) terminated, exit status = %3</span></dt><dd><p>
The given process ended unexpectedly with the given exit status.
Depending on which module it was, it may simply be restarted, or it
may be a problem that will cause the boss module to shut down too.
The latter happens if it was the message bus daemon, which, if it has
died suddenly, may leave the system in an inconsistent state. BIND10
will also shut down now if it has been run with --brittle.
</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>
The given process has been restarted successfully, and is now running
with the given process id.
</p></dd><dt><aname="BIND10_RESURRECTING_PROCESS"></a><spanclass="term">BIND10_RESURRECTING_PROCESS resurrecting dead %1 process...</span></dt><dd><p>
The given process has ended unexpectedly, and is now restarted.
</p></dd><dt><aname="BIND10_SELECT_ERROR"></a><spanclass="term">BIND10_SELECT_ERROR error in select() call: %1</span></dt><dd><p>
There was a fatal error in the call to select(), used to see if a child
process has ended or if there is a message on the message bus. This
should not happen under normal circumstances and is considered fatal,
so BIND 10 will now shut down. The specific error is printed.
</p></dd><dt><aname="BIND10_SEND_SIGKILL"></a><spanclass="term">BIND10_SEND_SIGKILL sending SIGKILL to %1 (PID %2)</span></dt><dd><p>
The boss module is sending a SIGKILL signal to the given process.
</p></dd><dt><aname="BIND10_SEND_SIGTERM"></a><spanclass="term">BIND10_SEND_SIGTERM sending SIGTERM to %1 (PID %2)</span></dt><dd><p>
The boss module is sending a SIGTERM signal to the given process.
</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_CRASHED"></a><spanclass="term">BIND10_SOCKCREATOR_CRASHED the socket creator crashed</span></dt><dd><p>
The socket creator terminated unexpectedly. It is not possible to restart it
(because the boss already gave up root privileges), so the system is going
to terminate.
</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_STARTED_PROCESS"></a><spanclass="term">BIND10_STARTED_PROCESS started %1</span></dt><dd><p>
The given process has successfully been started.
</p></dd><dt><aname="BIND10_STARTED_PROCESS_PID"></a><spanclass="term">BIND10_STARTED_PROCESS_PID started %1 (PID %2)</span></dt><dd><p>
The given process has successfully been started, and has the given PID.
Informational message on startup that shows the full version.
</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>).
All modules have been successfully started, and BIND 10 is now running.
</p></dd><dt><aname="BIND10_STARTUP_ERROR"></a><spanclass="term">BIND10_STARTUP_ERROR error during startup: %1</span></dt><dd><p>
There was a fatal error when BIND10 was trying to start. The error is
shown, and BIND10 will now shut down.
</p></dd><dt><aname="BIND10_START_AS_NON_ROOT"></a><spanclass="term">BIND10_START_AS_NON_ROOT starting %1 as a user, not root. This might fail.</span></dt><dd><p>
The given module 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_STOP_PROCESS"></a><spanclass="term">BIND10_STOP_PROCESS asking %1 to shut down</span></dt><dd><p>
The boss module is sending a shutdown command to the given module over
An unknown child process has exited. The PID is printed, but no further
action will be taken by the boss process.
</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.
</p></dd><dt><aname="CACHE_RRSET_NOT_FOUND"></a><spanclass="term">CACHE_RRSET_NOT_FOUND no RRset found for %1/%2/%3</span></dt><dd><p>
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_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_CC_SESSION_ERROR"></a><spanclass="term">CFGMGR_CC_SESSION_ERROR Error connecting to command channel: %1</span></dt><dd><p>
The configuration manager daemon was unable to connect to the messaging
system. The most likely cause is that msgq is not running.
</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_FIND_ERROR"></a><spanclass="term">DATASRC_DATABASE_FIND_ERROR error retrieving data from datasource %1: %2</span></dt><dd><p>
This was an internal error while reading data from a datasource. This can either
mean the specific data source implementation is not behaving correctly, or the
data it provides is invalid. The current search is aborted.
The error message contains specific information about the error.
</p></dd><dt><aname="DATASRC_DATABASE_FIND_RECORDS"></a><spanclass="term">DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3</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
different TTL values. The TTL of the RRSET is set to the lowest value, which
is printed in the log message.
</p></dd><dt><aname="DATASRC_DATABASE_FIND_UNCAUGHT_ERROR"></a><spanclass="term">DATASRC_DATABASE_FIND_UNCAUGHT_ERROR uncaught general error retrieving data from datasource %1: %2</span></dt><dd><p>
There was an uncaught general exception while reading data from a datasource.
This most likely points to a logic error in the code, and can be considered a
bug. The current search is aborted. Specific information about the exception is
printed in this error message.
</p></dd><dt><aname="DATASRC_DATABASE_FIND_UNCAUGHT_ISC_ERROR"></a><spanclass="term">DATASRC_DATABASE_FIND_UNCAUGHT_ISC_ERROR uncaught error retrieving data from datasource %1: %2</span></dt><dd><p>
There was an uncaught ISC exception while reading data from a datasource. This
most likely points to a logic error in the code, and can be considered a bug.
The current search is aborted. Specific information about the exception is
printed in this error message.
</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 Found delegation at %2 (exact match) in %1</span></dt><dd><p>
The program found the domain requested, but it is a delegation point to a
different zone, therefore it is not authoritative for this domain name.
It will return the NS record instead.
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_DNAME"></a><spanclass="term">DATASRC_DATABASE_FOUND_DNAME Found DNAME at %2 in %1</span></dt><dd><p>
When searching for a domain, the program met a DNAME redirection to a different
place in the domain space at the given domain name. It will return that one
instead.
</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
domain name, class and type.
</p></dd><dt><aname="DATASRC_DATABASE_FOUND_NXRRSET"></a><spanclass="term">DATASRC_DATABASE_FOUND_NXRRSET search in datasource %1 resulted in NXRRSET for %2/%3/%4</span></dt><dd><p>
The data returned by the database backend contained data for the given domain
name and class, but not for the given type.
</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>
The data returned by the database backend contained data for the given domain
name, and it either matches the type or has a relevant type. The RRset that is
</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.
Debug information. The requested domain does not exist.
</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 at superdomain '%1', domain '%2' is empty</span></dt><dd><p>
Debug information. The search stopped at a superdomain of the requested
domain. The domain is a empty nonterminal, therefore it is treated as NXRRSET
case (eg. the domain exists, but it doesn't have the requested record type).
</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>
Lookup of domain failed because the data have no zone that contain the
domain. Maybe someone sent a query to the wrong server for some reason.
</p></dd><dt><aname="DATASRC_QUERY_PROCESS"></a><spanclass="term">DATASRC_QUERY_PROCESS processing query '%1/%2' in the '%3' class</span></dt><dd><p>
Debug information. A sure query is being processed now.
</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 user wants DNSSEC and we discovered the entity doesn't exist (either
domain or the record). But there was an error getting NSEC/NSEC3 record
to prove the nonexistence.
</p></dd><dt><aname="DATASRC_QUERY_REF_FAIL"></a><spanclass="term">DATASRC_QUERY_REF_FAIL the underlying data source failed with %1</span></dt><dd><p>
The underlying data source failed to answer the query for referral information.
1 means some error, 2 is not implemented. The data source should have logged
the specific error already.
</p></dd><dt><aname="DATASRC_QUERY_RRSIG"></a><spanclass="term">DATASRC_QUERY_RRSIG unable to answer RRSIG query</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_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_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="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_INPUT_OPEN_FAIL"></a><spanclass="term">LOG_INPUT_OPEN_FAIL unable to open message file %1 for input: %2</span></dt><dd><p>
The program was not able to open the specified input message file for
the reason given.
</p></dd><dt><aname="LOG_INVALID_MESSAGE_ID"></a><spanclass="term">LOG_INVALID_MESSAGE_ID line %1: invalid message identification '%2'</span></dt><dd><p>
An invalid message identification (ID) has been found during the read of
a message file. Message IDs should comprise only alphanumeric characters
and the underscore, and should not start with a digit.
</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
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_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_INVALID_RESPONSE"></a><spanclass="term">NSAS_INVALID_RESPONSE queried for %1 but got invalid response</span></dt><dd><p>
The NSAS (nameserver address store - part of the resolver) made a query
for a RR for the specified nameserver but received an invalid response.
Either the success function was called without a DNS message or the
message was invalid on some way. (In the latter case, the error should
have been picked up elsewhere in the processing logic, hence the raising
of the error here.)
</p><p>
This message indicates an internal error in the NSAS. Please raise a
bug report.
</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
nameservers in the zone.
</p></dd><dt><aname="NSAS_SEARCH_ZONE_NS"></a><spanclass="term">NSAS_SEARCH_ZONE_NS searching NSAS for nameservers for zone %1</span></dt><dd><p>
A debug message output when a call is made to the NSAS (nameserver
address store - part of the resolver) to obtain the nameservers for
the specified zone.
</p></dd><dt><aname="NSAS_UPDATE_RTT"></a><spanclass="term">NSAS_UPDATE_RTT update RTT for %1: was %2 ms, is now %3 ms</span></dt><dd><p>
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="RESLIB_ANSWER"></a><spanclass="term">RESLIB_ANSWER answer received in response to query for <%1></span></dt><dd><p>
A debug message recording that an answer has been received to an upstream
query for the specified question. Previous debug messages will have indicated
the server to which the question was sent.
</p></dd><dt><aname="RESLIB_CNAME"></a><spanclass="term">RESLIB_CNAME CNAME received in response to query for <%1></span></dt><dd><p>
A debug message recording that CNAME response has been received to an upstream
query for the specified question. Previous debug messages will have indicated
the server to which the question was sent.
</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_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_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_RCODE_ERR"></a><spanclass="term">RESLIB_RCODE_ERR RCODE indicates error in response to query for <%1></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>
This is debug message output when the resolver received a message with an
unsupported opcode (it can only process QUERY opcodes). It will return
a message to the sender with the RCODE set to NOTIMP.
</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 (%2)</span></dt><dd><p>
The recovery of old addresses after SRVCOMM_ADDRESS_FAIL also failed for
the reason listed.
</p><p>
The condition indicates problems with the server and/or the system on
which it is running. The server will continue running to allow
reconfiguration, but will not be listening on any address or port until
an administrator does so.
</p></dd><dt><aname="SRVCOMM_ADDRESS_VALUE"></a><spanclass="term">SRVCOMM_ADDRESS_VALUE address to set: %1#%2</span></dt><dd><p>
Debug message. This lists one address and port value of the set of
addresses we are going to listen on (eg. there will be one log message
per pair). This appears only after SRVCOMM_SET_LISTEN, but might
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
be ignored.
</p></dd><dt><aname="STATHTTPD_SERVER_ERROR"></a><spanclass="term">STATHTTPD_SERVER_ERROR HTTP server error: %1</span></dt><dd><p>
An internal error occurred while handling an HTTP request. An HTTP 500
response will be sent back, and the specific error is printed. This
is an error condition that likely points to a module that is not
responding correctly to statistic requests.
</p></dd><dt><aname="STATHTTPD_SERVER_INIT_ERROR"></a><spanclass="term">STATHTTPD_SERVER_INIT_ERROR HTTP server initialization error: %1</span></dt><dd><p>
There was a problem initializing the HTTP server in the stats-httpd
module upon receiving its configuration data. The most likely cause
is a port binding problem or a bad configuration value. The specific
error is printed in the message. The new configuration is ignored,
The stats-httpd daemon received a configuration update from the
configuration manager. However, one of the items in the
configuration is unknown. The new configuration is ignored, and an
error is sent back. As possible cause is that there was an upgrade
problem, and the stats-httpd version is out of sync with the rest of
the system.
</p></dd><dt><aname="STATS_BAD_OPTION_VALUE"></a><spanclass="term">STATS_BAD_OPTION_VALUE bad command line argument: %1</span></dt><dd><p>
The stats module was called with a bad command-line argument and will
not start.
</p></dd><dt><aname="STATS_CC_SESSION_ERROR"></a><spanclass="term">STATS_CC_SESSION_ERROR error connecting to message bus: %1</span></dt><dd><p>
The stats module was unable to connect to the BIND 10 command and
control bus. A likely problem is that the message bus daemon
(b10-msgq) is not running. The stats module will now shut down.
</p></dd><dt><aname="STATS_RECEIVED_NEW_CONFIG"></a><spanclass="term">STATS_RECEIVED_NEW_CONFIG received new configuration: %1</span></dt><dd><p>
This debug message is printed when the stats module has received a
configuration update from the configuration manager.
</p></dd><dt><aname="STATS_RECEIVED_REMOVE_COMMAND"></a><spanclass="term">STATS_RECEIVED_REMOVE_COMMAND received command to remove %1</span></dt><dd><p>
A remove command for the given name was sent to the stats module, and
the given statistics value will now be removed. It will not appear in
statistics reports until it appears in a statistics update from a
module again.
</p></dd><dt><aname="STATS_RECEIVED_RESET_COMMAND"></a><spanclass="term">STATS_RECEIVED_RESET_COMMAND received command to reset all statistics</span></dt><dd><p>
The stats module received a command to clear all collected statistics.
The data is cleared until it receives an update from the modules again.
</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_DATABASE_FAILURE"></a><spanclass="term">XFRIN_AXFR_DATABASE_FAILURE AXFR transfer of zone %1 failed: %2</span></dt><dd><p>
The AXFR transfer for the given zone has failed due to a database problem.
The error is shown in the log message.
</p></dd><dt><aname="XFRIN_AXFR_INTERNAL_FAILURE"></a><spanclass="term">XFRIN_AXFR_INTERNAL_FAILURE AXFR transfer of zone %1 failed: %2</span></dt><dd><p>
The AXFR transfer for the given zone has failed due to an internal
problem in the bind10 python wrapper library.
The error is shown in the log message.
</p></dd><dt><aname="XFRIN_AXFR_TRANSFER_FAILURE"></a><spanclass="term">XFRIN_AXFR_TRANSFER_FAILURE AXFR transfer of zone %1 failed: %2</span></dt><dd><p>
The AXFR transfer for the given zone has failed due to a protocol error.
The error is shown in the log message.
</p></dd><dt><aname="XFRIN_AXFR_TRANSFER_STARTED"></a><spanclass="term">XFRIN_AXFR_TRANSFER_STARTED AXFR transfer of zone %1 started</span></dt><dd><p>
A connection to the master server has been made, the serial value in
the SOA record has been checked, and a zone transfer has been started.
</p></dd><dt><aname="XFRIN_AXFR_TRANSFER_SUCCESS"></a><spanclass="term">XFRIN_AXFR_TRANSFER_SUCCESS AXFR transfer of zone %1 succeeded</span></dt><dd><p>
The AXFR transfer of the given zone was successfully completed.
</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
shown in the log message.
</p></dd><dt><aname="XFRIN_IMPORT_DNS"></a><spanclass="term">XFRIN_IMPORT_DNS error importing python DNS module: %1</span></dt><dd><p>
There was an error importing the python DNS module pydnspp. The most
likely cause is a PYTHONPATH problem.
</p></dd><dt><aname="XFRIN_MSGQ_SEND_ERROR"></a><spanclass="term">XFRIN_MSGQ_SEND_ERROR error while contacting %1 and %2</span></dt><dd><p>
There was a problem sending a message to the xfrout module or the
zone manager. This most likely means that the msgq daemon has quit or
was killed.
</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_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
zone name in the configuration.
</p></dd><dt><aname="XFRIN_STARTING"></a><spanclass="term">XFRIN_STARTING starting resolver with command line '%1'</span></dt><dd><p>
An informational message, this is output when the resolver starts up.
An uncaught exception was raised while running the xfrin daemon. The
exception message is printed in the log message.
</p></dd><dt><aname="XFROUT_AXFR_TRANSFER_DONE"></a><spanclass="term">XFROUT_AXFR_TRANSFER_DONE transfer of %1/%2 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_AXFR_TRANSFER_ERROR"></a><spanclass="term">XFROUT_AXFR_TRANSFER_ERROR error transferring zone %1/%2: %3</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_AXFR_TRANSFER_FAILED"></a><spanclass="term">XFROUT_AXFR_TRANSFER_FAILED transfer of %1/%2 failed, rcode: %3</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_AXFR_TRANSFER_STARTED"></a><spanclass="term">XFROUT_AXFR_TRANSFER_STARTED transfer of zone %1/%2 has started</span></dt><dd><p>
A transfer out of the given zone has started.
</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>
command and control channel. The most likely cause is that the
configuration manager b10-cfgmgr is not running.
</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_QUERY_DROPPED"></a><spanclass="term">XFROUT_QUERY_DROPPED request to transfer %1/%2 to [%3]:%4 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 %1 and %2 represent the zone name and class,
the %3 and %4 the IP address and port of the peer requesting the transfer.
</p></dd><dt><aname="XFROUT_QUERY_REJECTED"></a><spanclass="term">XFROUT_QUERY_REJECTED request to transfer %1/%2 to [%3]:%4 rejected</span></dt><dd><p>
The xfrout process rejected (by REFUSED rcode) a request to transfer zone to
given host. This is because of ACLs. The %1 and %2 represent the zone name and
class, the %3 and %4 the IP address and port of the peer requesting the
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
request. Normally, the request is received by b10-auth, and passed on
to the xfrout daemon, so it can answer directly. However, there was a
problem receiving this file descriptor. The request will be ignored.
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
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
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_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).
