BIND 10 Messages Manual

This is the messages manual for BIND 10 version - 20120127.

Abstract

BIND 10 is a Domain Name System (DNS) suite managed by +BIND 10 Messages Manual

BIND 10 Messages Manual

This is the messages manual for BIND 10 version + 20120405.

Abstract

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 20120127. + This is the messages manual for BIND 10 version 20120405. The most up-to-date version of this document, along with other documents for BIND 10, can be found at http://bind10.isc.org/docs. @@ -183,6 +183,17 @@ This is a debug message issued when the authoritative server has received a command from the statistics module to send it data. The 'sendstats' command is handled differently to other commands, which is why the debug message associated with it has its own code. +

AUTH_RESPONSE_FAILURE exception while building response to query: %1

+This is a debug message, generated by the authoritative server when an +attempt to create a response to a received DNS packet has failed. The +reason for the failure is given in the log message. A SERVFAIL response +is sent back. The most likely cause of this is an error in the data +source implementation; it is either creating bad responses or raising +exceptions itself. +

AUTH_RESPONSE_FAILURE_UNKNOWN unknown exception while building response to query

+This debug message is similar to AUTH_RESPONSE_FAILURE, but further +details about the error are unknown, because it was signaled by something +which is not an exception. This is definitely a bug.

AUTH_RESPONSE_RECEIVED received response message, ignoring

This is a debug message, this is output if the authoritative server receives a DNS packet with the QR bit set, i.e. a DNS response. The @@ -275,7 +286,7 @@ NOTIFY request will not be honored. 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 needs a dedicated message bus. -

BIND10_COMPONENT_FAILED component %1 (pid %2) failed with %3 exit status

BIND10_COMPONENT_FAILED component %1 (pid %2) failed: %3

The process terminated, but the bind10 boss didn't expect it to, which means it must have failed.

BIND10_COMPONENT_RESTART component %1 is about to restart

@@ -585,7 +596,7 @@ same RRset, but from more trusted source, so the old one is kept and new one ignored.

CACHE_RRSET_UPDATE updating RRset %1/%2/%3 in the cache

Debug message. The RRset is updating its data with this given RRset. -

CC_ASYNC_READ_FAILED asynchronous read failed

CC_ASYNC_READ_FAILED asynchronous read failed (error code = %1)

This marks a low level error, we tried to read data from the message queue daemon asynchronously, but the ASIO library returned an error.

CC_CONN_ERROR error connecting to message queue (%1)

@@ -669,6 +680,9 @@ assumed to have failed, and will not be stored.

CFGMGR_CC_SESSION_ERROR Error connecting to command channel: %1

The configuration manager daemon was unable to connect to the messaging system. The most likely cause is that msgq is not running. +

CFGMGR_CONFIG_FILE Configuration manager starting with configuration file: %1

+The configuration manager is starting, reading and saving the configuration +settings to the shown file.

CFGMGR_DATA_READ_ERROR error reading configuration database from disk: %1

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 @@ -686,6 +700,10 @@ 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 configuration is not stored. +

CFGMGR_RENAMED_CONFIG_FILE renamed configuration file %1 to %2, will create new %1

+BIND 10 has been started with the command to clear the configuration file. +The existing file is backed up to the given file name, so that data is not +immediately lost if this was done by accident.

CFGMGR_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the cfgmgr daemon. The daemon will now shut down. @@ -870,6 +888,30 @@ means no limit. The datasource tried to provide an NSEC proof that the named domain does not exist, but the database backend doesn't support DNSSEC. No proof is included in the answer as a result. +

DATASRC_DATABASE_FINDNSEC3 Looking for NSEC3 for %1 in %2 mode

+Debug information. A search in an database data source for NSEC3 that +matches or covers the given name is being started. +

DATASRC_DATABASE_FINDNSEC3_COVER found a covering NSEC3 for %1: %2

+Debug information. An NSEC3 that covers the given name is found and +being returned. The found NSEC3 RRset is also displayed. +

DATASRC_DATABASE_FINDNSEC3_MATCH found a matching NSEC3 for %1 at label count %2: %3

+Debug information. An NSEC3 that matches (a possibly superdomain of) +the given name is found and being returned. When the shown label +count is smaller than that of the given name, the matching NSEC3 is +for a superdomain of the given name (see DATASRC_DATABSE_FINDNSEC3_TRYHASH). +The found NSEC3 RRset is also displayed. +

DATASRC_DATABASE_FINDNSEC3_TRYHASH looking for NSEC3 for %1 at label count %2 (hash %3)

+Debug information. In an attempt of finding an NSEC3 for the give name, +(a possibly superdomain of) the name is hashed and searched for in the +NSEC3 name space. When the shown label count is smaller than that of the +shown name, the search tries the superdomain name that share the shown +(higher) label count of the shown name (e.g., for +www.example.com. with shown label count of 3, example.com. is being +tried, as "." is 1 label long). +

DATASRC_DATABASE_FINDNSEC3_TRYHASH_PREV looking for previous NSEC3 for %1 at label count %2 (hash %3)

+Debug information. An exact match on hash (see +DATASRC_DATABASE_FINDNSEC3_TRYHASH) was unsuccessful. We get the previous hash +to that one instead.

DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3/%4

Debug information. The database data source is looking up records with the given name and type in the database. @@ -925,10 +967,12 @@ While iterating through the zone, the program reached end of the data. While iterating through the zone, the program extracted next RRset from it. The name and RRtype of the RRset is indicated in the message.

DATASRC_DATABASE_ITERATE_TTL_MISMATCH TTL values differ for RRs of %1/%2/%3, setting to %4

-While iterating through the zone, the time to live for RRs of the given RRset -were found to be different. This isn't allowed on the wire and is considered -an error, so we set it to the lowest value we found (but we don't modify the -database). The data in database should be checked and fixed. +While iterating through the zone, the time to live for RRs of the +given RRset were found to be different. Since an RRset cannot have +multiple TTLs, we set it to the lowest value we found (but we don't +modify the database). This is what the client would do when such RRs +were given in a DNS response according to RFC2181. The data in +database should be checked and fixed.

DATASRC_DATABASE_JOURNALREADER_END %1/%2 on %3 from %4 to %5

This is a debug message indicating that the program (successfully) reaches the end of sequences of a zone's differences. The zone's name @@ -1259,8 +1303,10 @@ not have any DS record. This indicates problem with the provided data. 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.

DATASRC_QUERY_NO_ZONE no zone containing '%1' in class '%2'

-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. +Debug information. Lookup of domain failed because the datasource +has no zone that contains the domain. Maybe someone sent a query +to the wrong server for some reason. This may also happen when +looking in the datasource for addresses for NS records.

DATASRC_QUERY_PROCESS processing query '%1/%2' in the '%3' class

Debug information. A sure query is being processed now.

DATASRC_QUERY_PROVE_NX_FAIL unable to prove nonexistence of '%1'

@@ -1307,6 +1353,16 @@ 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.

DATASRC_SQLITE_CLOSE closing SQLite database

Debug information. The SQLite data source is closing the database file. +

DATASRC_SQLITE_COMPATIBLE_VERSION database schema V%1.%2 not up to date (expecting V%3.%4) but is compatible

+The version of the SQLite3 database schema used to hold the zone data +is not the latest one - the current version of BIND 10 was written +with a later schema version in mind. However, the database is +compatible with the current version of BIND 10, and BIND 10 will run +without any problems. +

+Consult the release notes for your version of BIND 10. Depending on +the changes made to the database schema, it is possible that improved +performance could result if the database were upgraded.

DATASRC_SQLITE_CONNCLOSE Closing sqlite database

The database file is no longer needed and is being closed.

DATASRC_SQLITE_CONNOPEN Opening sqlite database file '%1'

@@ -1356,6 +1412,13 @@ source.

DATASRC_SQLITE_FIND_NSEC3_NO_ZONE no such zone '%1'

The SQLite data source was asked to provide a NSEC3 record for given zone. But it doesn't contain that zone. +

DATASRC_SQLITE_INCOMPATIBLE_VERSION database schema V%1.%2 incompatible with version (V%3.%4) expected

+The version of the SQLite3 database schema used to hold the zone data +is incompatible with the version expected by BIND 10. As a result, +BIND 10 is unable to run using the database file as the data source. +

+The database should be updated using the means described in the BIND +10 documentation.

DATASRC_SQLITE_NEWCONN SQLite3Database is being initialized

A wrapper object to hold database connection is being initialized.

DATASRC_SQLITE_OPEN opening SQLite database '%1'

@@ -1389,6 +1452,75 @@ data source.

DATASRC_UNEXPECTED_QUERY_STATE unexpected query state

This indicates a programming error. An internal task of unknown type was generated. +

DBUTIL_BACKUP created backup of %1 in %2

+A backup for the given database file was created. Same of original file and +backup are given in the output message. +

DBUTIL_CHECK_ERROR unable to check database version: %1

+There was an error while trying to check the current version of the database +schema. The error is shown in the message. +

DBUTIL_CHECK_NOCONFIRM --noconfirm is not compatible with --check

+b10-dbutil was called with --check and --noconfirm. --noconfirm only has +meaning with --upgrade, so this is considered an error. +

DBUTIL_CHECK_OK this is the latest version of the database schema. No upgrade is required

+The database schema version has been checked, and is up to date. +No action is required. +

DBUTIL_CHECK_UPGRADE_NEEDED re-run this program with the --upgrade switch to upgrade

+The database schema version is not up to date, and an update is required. +Please run the dbutil tool again, with the --upgrade argument. +

DBUTIL_COMMAND_NONE must select one of --check or --upgrade

+b10-dbutil was called with neither --check nor --upgrade. One action must be +provided. +

DBUTIL_COMMAND_UPGRADE_CHECK --upgrade is not compatible with --check

+b10-dbutil was called with both the commands --upgrade and --check. Only one +action can be performed at a time. +

DBUTIL_DATABASE_MAY_BE_CORRUPT database file %1 may be corrupt, restore it from backup (%2)

+The upgrade failed while it was in progress; the database may now be in an +inconsistent state, and it is advised to restore it from the backup that was +created when b10-dbutil started. +

DBUTIL_EXECUTE Executing SQL statement: %1

+Debug message; the given SQL statement is executed +

DBUTIL_FILE Database file: %1

+The database file that is being checked. +

DBUTIL_NO_FILE must supply name of the database file to upgrade

+b10-dbutil was called without a database file. Currently, it cannot find this +file on its own, and it must be provided. +

DBUTIL_STATEMENT_ERROR failed to execute %1: %2

+The given database statement failed to execute. The error is shown in the +message. +

DBUTIL_TOO_MANY_ARGUMENTS too many arguments to the command, maximum of one expected

+There were too many command-line arguments to b10-dbutil +

DBUTIL_UPGRADE_CANCELED upgrade canceled; database has not been changed

+The user aborted the upgrade, and b10-dbutil will now exit. +

DBUTIL_UPGRADE_DBUTIL please get the latest version of b10-dbutil and re-run

+A database schema was found that was newer than this version of dbutil, which +is apparently out of date and should be upgraded itself. +

DBUTIL_UPGRADE_FAILED upgrade failed: %1

+While the upgrade was in progress, an unexpected error occurred. The error +is shown in the message. +

DBUTIL_UPGRADE_NOT_ATTEMPTED database upgrade was not attempted

+Due to the earlier failure, the database schema upgrade was not attempted, +and b10-dbutil will now exit. +

DBUTIL_UPGRADE_NOT_NEEDED database already at latest version, no upgrade necessary

+b10-dbutil was told to upgrade the database schema, but it is already at the +latest version. +

DBUTIL_UPGRADE_NOT_POSSIBLE database at a later version than this utility can support

+b10-dbutil was told to upgrade the database schema, but it is at a higher +version than this tool currently supports. Please update b10-dbutil and try +again. +

DBUTIL_UPGRADE_PREPARATION_FAILED upgrade preparation failed: %1

+An unexpected error occurred while b10-dbutil was preparing to upgrade the +database schema. The error is shown in the message +

DBUTIL_UPGRADE_SUCCESFUL database upgrade successfully completed

+The database schema update was completed successfully. +

DBUTIL_UPGRADING upgrading database from %1 to %2

+An upgrade is in progress, the versions of the current upgrade action are shown. +

DBUTIL_VERSION_CURRENT database version %1

+The current version of the database schema. +

DBUTIL_VERSION_HIGH database is at a later version (%1) than this program can cope with (%2)

+The database schema is at a higher version than b10-dbutil knows about. +

DBUTIL_VERSION_LOW database version %1, latest version is %2.

+The database schema is not up to date, the current version and the latest +version are in the message.

DDNS_ACCEPT_FAILURE error accepting a connection: %1

There was a low-level error when we tried to accept an incoming connection (probably coming from b10-auth). We continue serving on whatever other @@ -2064,7 +2196,7 @@ resolver. It is output during startup and may appear multiple times, once for each root server address.

RESOLVER_SHUTDOWN resolver shutdown complete

This informational message is output when the resolver has shut down. -

RESOLVER_SHUTDOWN (1) asked to shut down, doing so

RESOLVER_SHUTDOWN_RECEIVED received command to shut down

A debug message noting that the server was asked to terminate and is complying to the request.

RESOLVER_STARTED resolver started

@@ -2270,6 +2402,14 @@ is unknown in the implementation. The most likely cause is an installation problem, where the specification file stats.spec is from a different version of BIND 10 than the stats module itself. Please check your installation. +

XFRIN_AUTH_CONFIG_NAME_PARSER_ERROR Invalid name when parsing Auth configuration: %1

+There was an invalid name when parsing Auth configuration. +

XFRIN_AUTH_CONFIG_RRCLASS_ERROR Invalid RRClass when parsing Auth configuration: %1

+There was an invalid RR class when parsing Auth configuration. +

XFRIN_AUTH_LOADZONE sending Auth loadzone for origin=%1, class=%2, datasrc=%3

+There was a successful zone transfer, and the zone is served by b10-auth +in the in-memory data source using sqlite3 as a backend. We send the +"loadzone" command for the zone to b10-auth.

XFRIN_AXFR_INCONSISTENT_SOA AXFR SOAs are inconsistent for %1: %2 expected, %3 received

The serial fields of the first and last SOAs of AXFR (including AXFR-style IXFR) are not the same. According to RFC 5936 these two SOAs must be the @@ -2317,6 +2457,30 @@ is not equal to the requested SOA serial.

XFRIN_IMPORT_DNS error importing python DNS module: %1

There was an error importing the python DNS module pydnspp. The most likely cause is a PYTHONPATH problem. +

XFRIN_IXFR_TRANSFER_SUCCESS incremental IXFR transfer of zone %1 succeeded (messages: %2, changesets: %3, deletions: %4, additions: %5, bytes: %6, run time: %7 seconds, %8 bytes/second)

+The IXFR transfer for the given zone was successful. +The provided information contains the following values: +

+messages: Number of overhead DNS messages in the transfer. +

+changesets: Number of difference sequences. +

+deletions: Number of Resource Records deleted by all the changesets combined, +including the SOA records. +

+additions: Number of Resource Records added by all the changesets combined, +including the SOA records. +

+bytes: Full size of the transfer data on the wire. +

+run time: Time (in seconds) the complete ixfr took. +

+bytes/second: Transfer speed. +

+Note that there is no cross-checking of additions and deletions; if the same +RR gets added and deleted in multiple changesets, it is counted each time; +therefore, for each changeset, there should at least be 1 deletion and 1 +addition (the updated SOA record).

XFRIN_IXFR_UPTODATE IXFR requested serial for %1 is %2, master has %3, not updating

The first SOA record in an IXFR response indicates the zone's serial at the primary server is not newer than the client's. This is @@ -2330,6 +2494,9 @@ aborts the transfer just like a successful case. 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. +

XFRIN_MSGQ_SEND_ERROR_AUTH error while contacting %1

+There was a problem sending a message to b10-auth. This most likely +means that the msgq daemon has quit or was killed.

XFRIN_MSGQ_SEND_ERROR_ZONE_MANAGER error while contacting %1

There was a problem sending a message to the zone manager. This most likely means that the msgq daemon has quit or was killed. @@ -2343,11 +2510,26 @@ 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. -

XFRIN_STARTING starting resolver with command line '%1'

-An informational message, this is output when the resolver starts up. +

XFRIN_STARTED xfrin started

+This informational message is output by xfrin when all initialization +has been completed and it is entering its main loop.

XFRIN_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the xfrin daemon. The daemon will now shut down. +

XFRIN_TRANSFER_SUCCESS full %1 transfer of zone %2 succeeded (messages: %3, records: %4, bytes: %5, run time: %6 seconds, %7 bytes/second)

+The AXFR transfer of the given zone was successful. +The provided information contains the following values: +

+messages: Number of overhead DNS messages in the transfer +

+records: Number of Resource Records in the full transfer, excluding the +final SOA record that marks the end of the AXFR. +

+bytes: Full size of the transfer data on the wire. +

+run time: Time (in seconds) the complete axfr took +

+bytes/second: Transfer speed

XFRIN_UNKNOWN_ERROR unknown error: %1

An uncaught exception was raised while running the xfrin daemon. The exception message is printed in the log message. @@ -2389,8 +2571,6 @@ is recommended to check the primary server configuration.

XFRIN_XFR_TRANSFER_STARTED %1 transfer of zone %2 started

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. -

XFRIN_XFR_TRANSFER_SUCCESS %1 transfer of zone %2 succeeded

-The XFR transfer of the given zone was successfully completed.

XFRIN_ZONE_CREATED Zone %1 not found in the given data source, newly created

On starting an xfrin session, it is identified that the zone to be transferred is not found in the data source. This can happen if a @@ -2557,6 +2737,9 @@ 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 log message. +

XFROUT_STARTED xfrout started

+This informational message is output by xfrout when all initialization +has been completed and it is entering its main loop.

XFROUT_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down

There was a keyboard interrupt signal to stop the xfrout daemon. The daemon will now shut down. @@ -2673,6 +2856,9 @@ connecting to the command channel daemon. The most usual cause of this problem is that the daemon is not running.

ZONEMGR_SHUTDOWN zone manager has shut down

A debug message, output when the zone manager has shut down completely. +

ZONEMGR_STARTED zonemgr started

+This informational message is output by zonemgr when all initialization +has been completed and it is entering its main loop.

ZONEMGR_STARTING zone manager starting

A debug message output when the zone manager starts up.

ZONEMGR_TIMER_THREAD_RUNNING trying to start timer thread but one is already running

@@ -2683,9 +2869,11 @@ a problem with stopping a previous instance of the timer. Please submit a bug report.

ZONEMGR_UNKNOWN_ZONE_FAIL zone %1 (class %2) is not known to the zone manager

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. +operation is not being managed by the zone manager. This can be either the +result of a bindctl command to transfer in a currently unknown (or mistyped) +zone, or, if this error appears without the administrator giving transfer +commands, it can indicate an error in the program, as it should not have +initiated transfers of unknown zones on its own.

ZONEMGR_UNKNOWN_ZONE_NOTIFIED notified zone %1 (class %2) is not known to the zone manager

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 diff --git a/doc/guide/bind10-messages.xml b/doc/guide/bind10-messages.xml index 60f9665eb5..3edf11b179 100644 --- a/doc/guide/bind10-messages.xml +++ b/doc/guide/bind10-messages.xml @@ -1399,7 +1399,7 @@ Debug message. The RRset is updating its data with this given RRset. -CC_ASYNC_READ_FAILED asynchronous read failed +CC_ASYNC_READ_FAILED asynchronous read failed (error code = %1) This marks a low level error, we tried to read data from the message queue daemon asynchronously, but the ASIO library returned an error. @@ -1607,6 +1607,14 @@ system. The most likely cause is that msgq is not running. + +CFGMGR_CONFIG_FILE Configuration manager starting with configuration file: %1 + +The configuration manager is starting, reading and saving the configuration +settings to the shown file. + + + CFGMGR_DATA_READ_ERROR error reading configuration database from disk: %1 @@ -2057,6 +2065,55 @@ in the answer as a result. + +DATASRC_DATABASE_FINDNSEC3 Looking for NSEC3 for %1 in %2 mode + +Debug information. A search in an database data source for NSEC3 that +matches or covers the given name is being started. + + + + +DATASRC_DATABASE_FINDNSEC3_COVER found a covering NSEC3 for %1: %2 + +Debug information. An NSEC3 that covers the given name is found and +being returned. The found NSEC3 RRset is also displayed. + + + + +DATASRC_DATABASE_FINDNSEC3_MATCH found a matching NSEC3 for %1 at label count %2: %3 + +Debug information. An NSEC3 that matches (a possibly superdomain of) +the given name is found and being returned. When the shown label +count is smaller than that of the given name, the matching NSEC3 is +for a superdomain of the given name (see DATASRC_DATABSE_FINDNSEC3_TRYHASH). +The found NSEC3 RRset is also displayed. + + + + +DATASRC_DATABASE_FINDNSEC3_TRYHASH looking for NSEC3 for %1 at label count %2 (hash %3) + +Debug information. In an attempt of finding an NSEC3 for the give name, +(a possibly superdomain of) the name is hashed and searched for in the +NSEC3 name space. When the shown label count is smaller than that of the +shown name, the search tries the superdomain name that share the shown +(higher) label count of the shown name (e.g., for +www.example.com. with shown label count of 3, example.com. is being +tried, as "." is 1 label long). + + + + +DATASRC_DATABASE_FINDNSEC3_TRYHASH_PREV looking for previous NSEC3 for %1 at label count %2 (hash %3) + +Debug information. An exact match on hash (see +DATASRC_DATABASE_FINDNSEC3_TRYHASH) was unsuccessful. We get the previous hash +to that one instead. + + + DATASRC_DATABASE_FIND_RECORDS looking in datasource %1 for record %2/%3/%4 @@ -2189,10 +2246,12 @@ The name and RRtype of the RRset is indicated in the message. DATASRC_DATABASE_ITERATE_TTL_MISMATCH TTL values differ for RRs of %1/%2/%3, setting to %4 -While iterating through the zone, the time to live for RRs of the given RRset -were found to be different. This isn't allowed on the wire and is considered -an error, so we set it to the lowest value we found (but we don't modify the -database). The data in database should be checked and fixed. +While iterating through the zone, the time to live for RRs of the +given RRset were found to be different. Since an RRset cannot have +multiple TTLs, we set it to the lowest value we found (but we don't +modify the database). This is what the client would do when such RRs +were given in a DNS response according to RFC2181. The data in +database should be checked and fixed. @@ -3096,6 +3155,21 @@ Debug information. The SQLite data source is closing the database file. + +DATASRC_SQLITE_COMPATIBLE_VERSION database schema V%1.%2 not up to date (expecting V%3.%4) but is compatible + +The version of the SQLite3 database schema used to hold the zone data +is not the latest one - the current version of BIND 10 was written +with a later schema version in mind. However, the database is +compatible with the current version of BIND 10, and BIND 10 will run +without any problems. + +Consult the release notes for your version of BIND 10. Depending on +the changes made to the database schema, it is possible that improved +performance could result if the database were upgraded. + + + DATASRC_SQLITE_CONNCLOSE Closing sqlite database @@ -3235,6 +3309,18 @@ But it doesn't contain that zone. + +DATASRC_SQLITE_INCOMPATIBLE_VERSION database schema V%1.%2 incompatible with version (V%3.%4) expected + +The version of the SQLite3 database schema used to hold the zone data +is incompatible with the version expected by BIND 10. As a result, +BIND 10 is unable to run using the database file as the data source. + +The database should be updated using the means described in the BIND +10 documentation. + + + DATASRC_SQLITE_NEWCONN SQLite3Database is being initialized @@ -5388,6 +5474,29 @@ Please check your installation. + +XFRIN_AUTH_CONFIG_NAME_PARSER_ERROR Invalid name when parsing Auth configuration: %1 + +There was an invalid name when parsing Auth configuration. + + + + +XFRIN_AUTH_CONFIG_RRCLASS_ERROR Invalid RRClass when parsing Auth configuration: %1 + +There was an invalid RR class when parsing Auth configuration. + + + + +XFRIN_AUTH_LOADZONE sending Auth loadzone for origin=%1, class=%2, datasrc=%3 + +There was a successful zone transfer, and the zone is served by b10-auth +in the in-memory data source using sqlite3 as a backend. We send the +"loadzone" command for the zone to b10-auth. + + + XFRIN_AXFR_INCONSISTENT_SOA AXFR SOAs are inconsistent for %1: %2 expected, %3 received @@ -5542,6 +5651,14 @@ was killed. + +XFRIN_MSGQ_SEND_ERROR_AUTH error while contacting %1 + +There was a problem sending a message to b10-auth. This most likely +means that the msgq daemon has quit or was killed. + + + XFRIN_MSGQ_SEND_ERROR_ZONE_MANAGER error while contacting %1 @@ -5570,10 +5687,11 @@ zone name in the configuration. - -XFRIN_STARTING starting resolver with command line '%1' + +XFRIN_STARTED xfrin started -An informational message, this is output when the resolver starts up. +This informational message is output by xfrin when all initialization +has been completed and it is entering its main loop. @@ -6001,6 +6119,14 @@ log message. + +XFROUT_STARTED xfrout started + +This informational message is output by xfrout when all initialization +has been completed and it is entering its main loop. + + + XFROUT_STOPPED_BY_KEYBOARD keyboard interrupt, shutting down @@ -6257,6 +6383,14 @@ A debug message, output when the zone manager has shut down completely. + +ZONEMGR_STARTED zonemgr started + +This informational message is output by zonemgr when all initialization +has been completed and it is entering its main loop. + + + ZONEMGR_STARTING zone manager starting