|
@@ -73,6 +73,10 @@ 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
|
|
|
packet.
|
|
|
|
|
|
+% AUTH_INVALID_STATISTICS_DATA invalid specification of statistics data specified
|
|
|
+An error was encountered when the authoritiative server specified
|
|
|
+statistics data which is invalid for the auth specification file.
|
|
|
+
|
|
|
% AUTH_LOAD_TSIG loading TSIG keys
|
|
|
This is a debug message indicating that the authoritative server
|
|
|
has requested the keyring holding TSIG keys from the configuration
|
|
@@ -92,6 +96,18 @@ discovered that the memory data source is disabled for the given class.
|
|
|
This is a debug message reporting that the authoritative server has
|
|
|
discovered that the memory data source is enabled for the given class.
|
|
|
|
|
|
+% AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY
|
|
|
+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.
|
|
|
+
|
|
|
+% AUTH_NOTIFY_RRTYPE invalid question RR type (%1) in incoming NOTIFY
|
|
|
+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.
|
|
|
+
|
|
|
% AUTH_NO_STATS_SESSION session interface for statistics is not available
|
|
|
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
|
|
@@ -102,18 +118,6 @@ 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.
|
|
|
|
|
|
-% AUTH_NOTIFY_RRTYPE invalid question RR type (%1) in incoming NOTIFY
|
|
|
-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.
|
|
|
-
|
|
|
-% AUTH_NOTIFY_QUESTIONS invalid number of questions (%1) in incoming NOTIFY
|
|
|
-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.
|
|
|
-
|
|
|
% AUTH_PACKET_PARSE_ERROR unable to parse received DNS packet: %1
|
|
|
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
|
|
@@ -154,6 +158,19 @@ 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
|
|
@@ -260,20 +277,3 @@ This is a debug message output during the processing of a NOTIFY
|
|
|
request. The zone manager component has been informed of the request,
|
|
|
but has returned an error response (which is included in the message). The
|
|
|
NOTIFY request will not be honored.
|
|
|
-
|
|
|
-% AUTH_INVALID_STATISTICS_DATA invalid specification of statistics data specified
|
|
|
-An error was encountered when the authoritiative server specified
|
|
|
-statistics data which is invalid for the auth specification file.
|
|
|
-
|
|
|
-% 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.
|