<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 20110705. 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="id1168230298906"></a>BIND 10 Messages Manual</h1></div><div><pclass="releaseinfo">This is the messages manual for BIND 10 version
20110705.</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.
This is a debug message, issued when the authoritative server has
posted a request to be notified when new configuration information is
available. It is issued during server startup is an indication that
the initialization is proceeding normally.
</p></dd><dt><aname="AUTH_CONFIG_LOAD_FAIL"></a><spanclass="term">AUTH_CONFIG_LOAD_FAIL load of configuration failed: %1</span></dt><dd><p>
An attempt to configure the server with information from the configuration
database during the startup sequence has failed. (The reason for
the failure is given in the message.) The server will continue its
initialization although it may not be configured in the desired way.
</p></dd><dt><aname="AUTH_CONFIG_UPDATE_FAIL"></a><spanclass="term">AUTH_CONFIG_UPDATE_FAIL update of configuration failed: %1</span></dt><dd><p>
At attempt to update the configuration the server with information
from the configuration database has failed, the reason being given in
the message.
</p></dd><dt><aname="AUTH_DATA_SOURCE"></a><spanclass="term">AUTH_DATA_SOURCE data source database file: %1</span></dt><dd><p>
This is a debug message produced by the authoritative server when it accesses a
datebase data source, listing the file that is being accessed.
</p></dd><dt><aname="AUTH_DNS_SERVICES_CREATED"></a><spanclass="term">AUTH_DNS_SERVICES_CREATED DNS services created</span></dt><dd><p>
This is a debug message indicating that the component that will handling
incoming queries for the authoritiative server (DNSServices) has been
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
This is a debug message indicating that the authoritiative server
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
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_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="DATASRC_CACHE_CREATE"></a><spanclass="term">DATASRC_CACHE_CREATE creating the hotspot cache</span></dt><dd><p>
Debug information that the hotspot cache was created at startup.
</p></dd><dt><aname="DATASRC_CACHE_DESTROY"></a><spanclass="term">DATASRC_CACHE_DESTROY destroying the hotspot cache</span></dt><dd><p>
Debug information. The hotspot cache is being destroyed.
</p></dd><dt><aname="DATASRC_CACHE_DISABLE"></a><spanclass="term">DATASRC_CACHE_DISABLE disabling the cache</span></dt><dd><p>
The hotspot cache is disabled from now on. It is not going to store
information or return anything.
</p></dd><dt><aname="DATASRC_CACHE_ENABLE"></a><spanclass="term">DATASRC_CACHE_ENABLE enabling the cache</span></dt><dd><p>
The hotspot cache is enabled from now on.
</p></dd><dt><aname="DATASRC_CACHE_EXPIRED"></a><spanclass="term">DATASRC_CACHE_EXPIRED the item '%1' is expired</span></dt><dd><p>
Debug information. There was an attempt to look up an item in the hotspot
cache. And the item was actually there, but it was too old, so it was removed
instead and nothing is reported (the external behaviour is the same as with
CACHE_NOT_FOUND).
</p></dd><dt><aname="DATASRC_CACHE_FOUND"></a><spanclass="term">DATASRC_CACHE_FOUND the item '%1' was found</span></dt><dd><p>
Debug information. An item was successfully looked up in the hotspot cache.
</p></dd><dt><aname="DATASRC_CACHE_FULL"></a><spanclass="term">DATASRC_CACHE_FULL cache is full, dropping oldest</span></dt><dd><p>
Debug information. After inserting an item into the hotspot cache, the
maximum number of items was exceeded, so the least recently used item will
be dropped. This should be directly followed by CACHE_REMOVE.
</p></dd><dt><aname="DATASRC_CACHE_INSERT"></a><spanclass="term">DATASRC_CACHE_INSERT inserting item '%1' into the cache</span></dt><dd><p>
Debug information. It means a new item is being inserted into the hotspot
cache.
</p></dd><dt><aname="DATASRC_CACHE_NOT_FOUND"></a><spanclass="term">DATASRC_CACHE_NOT_FOUND the item '%1' was not found</span></dt><dd><p>
Debug information. It was attempted to look up an item in the hotspot cache,
but it is not there.
</p></dd><dt><aname="DATASRC_CACHE_OLD_FOUND"></a><spanclass="term">DATASRC_CACHE_OLD_FOUND older instance of cache item found, replacing</span></dt><dd><p>
Debug information. While inserting an item into the hotspot cache, an older
instance of an item with the same name was found. The old instance will be
removed. This should be directly followed by CACHE_REMOVE.
</p></dd><dt><aname="DATASRC_CACHE_REMOVE"></a><spanclass="term">DATASRC_CACHE_REMOVE removing '%1' from the cache</span></dt><dd><p>
Debug information. An item is being removed from the hotspot cache.
</p></dd><dt><aname="DATASRC_CACHE_SLOTS"></a><spanclass="term">DATASRC_CACHE_SLOTS setting the cache size to '%1', dropping '%2' items</span></dt><dd><p>
The maximum allowed number of items of the hotspot cache is set to the given
number. If there are too many, some of them will be dropped. The size of 0
means no limit.
</p></dd><dt><aname="DATASRC_DO_QUERY"></a><spanclass="term">DATASRC_DO_QUERY handling query for '%1/%2'</span></dt><dd><p>
Debug information. We're processing some internal query for given name and
type.
</p></dd><dt><aname="DATASRC_MEM_ADD_RRSET"></a><spanclass="term">DATASRC_MEM_ADD_RRSET adding RRset '%1/%2' into zone '%3'</span></dt><dd><p>
Debug information. An RRset is being added to the in-memory data source.
</p></dd><dt><aname="DATASRC_MEM_ADD_WILDCARD"></a><spanclass="term">DATASRC_MEM_ADD_WILDCARD adding wildcards for '%1'</span></dt><dd><p>
Debug information. Some special marks above each * in wildcard name are needed.
They are being added now for this name.
</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. A search for the requested RRset is being started.
</p></dd><dt><aname="DATASRC_MEM_FIND_ZONE"></a><spanclass="term">DATASRC_MEM_FIND_ZONE looking for zone '%1'</span></dt><dd><p>
Debug information. A zone object for this zone is being searched for in the
in-memory data source.
</p></dd><dt><aname="DATASRC_MEM_LOAD"></a><spanclass="term">DATASRC_MEM_LOAD loading zone '%1' from file '%2'</span></dt><dd><p>
Debug information. The content of master file is being loaded into the memory.
</p></dd><dt><aname="DATASRC_MEM_NOTFOUND"></a><spanclass="term">DATASRC_MEM_NOTFOUND requested domain '%1' not found</span></dt><dd><p>
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>
The software refuses to load NS records into a wildcard domain. It isn't
explicitly forbidden, but the protocol is ambiguous about how this should
behave and BIND 9 refuses that as well. Please describe your intention using
different tools.
</p></dd><dt><aname="DATASRC_META_ADD"></a><spanclass="term">DATASRC_META_ADD adding a data source into meta data source</span></dt><dd><p>
Debug information. Yet another data source is being added into the meta data
source. (probably at startup or reconfiguration)
</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>
It was attempted to add a data source into a meta data source. But their
classes do not match.
</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
information for it.
</p></dd><dt><aname="DATASRC_QUERY_CACHED"></a><spanclass="term">DATASRC_QUERY_CACHED data for %1/%2 found in cache</span></dt><dd><p>
Debug information. The requested data were found in the hotspot cache, so
no query is sent to the real data source.
</p></dd><dt><aname="DATASRC_QUERY_CHECK_CACHE"></a><spanclass="term">DATASRC_QUERY_CHECK_CACHE checking cache for '%1/%2'</span></dt><dd><p>
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
Some subtask of query processing failed. The reason should have been reported
already. We are returning SERVFAIL.
</p></dd><dt><aname="DATASRC_QUERY_FOLLOW_CNAME"></a><spanclass="term">DATASRC_QUERY_FOLLOW_CNAME following CNAME at '%1'</span></dt><dd><p>
Debug information. The domain is a CNAME (or a DNAME and we created a CNAME
for it already), so it's being followed.
</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
error already.
</p></dd><dt><aname="DATASRC_QUERY_NO_CACHE_ANY_AUTH"></a><spanclass="term">DATASRC_QUERY_NO_CACHE_ANY_AUTH ignoring cache for ANY query (%1/%2 in %3 class)</span></dt><dd><p>
Debug information. The hotspot cache is ignored for authoritative ANY queries
for consistency reasons.
</p></dd><dt><aname="DATASRC_QUERY_NO_CACHE_ANY_SIMPLE"></a><spanclass="term">DATASRC_QUERY_NO_CACHE_ANY_SIMPLE ignoring 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_PROVENX_FAIL"></a><spanclass="term">DATASRC_QUERY_PROVENX_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>
Debug information. While answering a query, a DNAME was met. The DNAME itself
will be returned, but along with it a CNAME for clients which don't understand
DNAMEs will be synthesized.
</p></dd><dt><aname="DATASRC_QUERY_TASK_FAIL"></a><spanclass="term">DATASRC_QUERY_TASK_FAIL task failed with %1</span></dt><dd><p>
The query subtask failed. The reason should have been reported by the subtask
already. The code is 1 for error, 2 for not implemented.
A CNAME led to another CNAME and it led to another, and so on. After 16
CNAMEs, the software gave up. Long CNAME chains are discouraged, and this
might possibly be a loop as well. Note that some of the CNAMEs might have
been synthesized from DNAMEs. This indicates problem with supplied data.
</p></dd><dt><aname="DATASRC_QUERY_UNKNOWN_RESULT"></a><spanclass="term">DATASRC_QUERY_UNKNOWN_RESULT unknown result of subtask</span></dt><dd><p>
This indicates a programmer error. The answer of subtask doesn't look like
anything known.
</p></dd><dt><aname="DATASRC_QUERY_WILDCARD"></a><spanclass="term">DATASRC_QUERY_WILDCARD looking for a wildcard covering '%1'</span></dt><dd><p>
Debug information. A direct match wasn't found, so a wildcard covering the
domain is being looked for now.
</p></dd><dt><aname="DATASRC_QUERY_WILDCARD_FAIL"></a><spanclass="term">DATASRC_QUERY_WILDCARD_FAIL error processing wildcard for '%1'</span></dt><dd><p>
During an attempt to cover the domain by a wildcard an error happened. The
exact kind was hopefully already reported.
</p></dd><dt><aname="DATASRC_QUERY_WILDCARD_PROVENX_FAIL"></a><spanclass="term">DATASRC_QUERY_WILDCARD_PROVENX_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_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="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_BAD_STREAM"></a><spanclass="term">LOG_BAD_STREAM bad log console output stream: %1</span></dt><dd><p>
A log console output stream was given that was not recognized. The output
stream should be one of "stdout", or "stderr"
</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>
During start-up, BIND10 detected that the given message identification had
been defined multiple times in the BIND10 code.
</p><p>
This has no ill-effects other than the possibility that an erronous
message may be logged. However, as it is indicative of a programming
error, please log a bug report.
</p></dd><dt><aname="LOG_DUPLICATE_NAMESPACE"></a><spanclass="term">LOG_DUPLICATE_NAMESPACE line %1: duplicate $NAMESPACE directive found</span></dt><dd><p>
When reading a message file, more than one $NAMESPACE directive was found.
Such a condition is regarded as an error and the read will be abandoned.
</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>
- The local file was written for an earlier version of the BIND10 software
and the later version no longer generates that message.
</p><p>
Whatever the reason, there is no impact on the operation of BIND10.
</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
version of BIND10.
</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
in the message) that violates those restictions.
</p><p>
Note: the $PREFIX directive is deprecated and will be removed in a future
version of BIND10.
</p></dd><dt><aname="LOG_READING_LOCAL_FILE"></a><spanclass="term">LOG_READING_LOCAL_FILE reading local message file %1</span></dt><dd><p>
This is an informational message output by BIND10 when it starts to read
a local message file. (A local message file may replace the text of
one of more messages; the ID of the message will not be changed though.)
</p></dd><dt><aname="LOG_READ_ERROR"></a><spanclass="term">LOG_READ_ERROR error reading from message file %1: %2</span></dt><dd><p>
</p></dd><dt><aname="LOG_UNRECOGNISED_DIRECTIVE"></a><spanclass="term">LOG_UNRECOGNISED_DIRECTIVE line %1: unrecognised directive '%2'</span></dt><dd><p>
Within a message file, a line starting with a dollar symbol was found
(indicating the presence of a directive) but the first word on the line
(shown in the message) was not recognised.
</p></dd><dt><aname="LOG_WRITE_ERROR"></a><spanclass="term">LOG_WRITE_ERROR error writing to %1: %2</span></dt><dd><p>
The specified error was encountered by the message compiler when writing
to the named output file.
</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_MESSAGE_ERROR"></a><spanclass="term">RESOLVER_MESSAGE_ERROR error parsing received message: %1 - returning %2</span></dt><dd><p>
A debug message noting that the resolver received a message and the
parsing of the body of the message failed due to some error (although
the parsing of the header succeeded). The message parameters give a
textual description of the problem and the RCODE returned.
</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>
An error message indicating that the resolver configuration has specified a
negative retry count. Only zero or positive values are valid.
</p></dd><dt><aname="RESOLVER_NON_IN_PACKET"></a><spanclass="term">RESOLVER_NON_IN_PACKET non-IN class request received, returning REFUSED message</span></dt><dd><p>
</p></dd><dt><aname="RESOLVER_NORMAL_QUERY"></a><spanclass="term">RESOLVER_NORMAL_QUERY processing normal query</span></dt><dd><p>
The received query has passed all checks and is being processed by the resolver.
</p></dd><dt><aname="RESOLVER_NOTIFY_RECEIVED"></a><spanclass="term">RESOLVER_NOTIFY_RECEIVED NOTIFY arrived but server is not authoritative</span></dt><dd><p>
The resolver received a NOTIFY message. As the server is not authoritative it
cannot process it, so it returns an error message to the sender with the RCODE
set to NOTAUTH.
</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>
A debug message, 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="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>
There was a problem reading a response from antoher module over the
command and control channel. The most likely cause is that the
configuration manager b10-cfgmgr is not running.
</p></dd><dt><aname="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.
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
