|
@@ -15,7 +15,7 @@
|
|
|
# No namespace declaration - these constants go in the global namespace
|
|
|
# of the notify_out_messages python module.
|
|
|
|
|
|
-% NOTIFY_OUT_IMPORT error importing python module: %1
|
|
|
+% NOTIFY_OUT_IMPORT_ERROR error importing python module: %1
|
|
|
There was an error importing a python module. One of the modules
|
|
|
needed by notify_out could not be found. This suggests that either
|
|
|
some libraries are missing on the system, or the PYTHONPATH variable
|
|
@@ -25,28 +25,35 @@ depends on your system and your specific installation.
|
|
|
% NOTIFY_OUT_INVALID_ADDRESS invalid address %1#%2: %3
|
|
|
The notify_out library tried to send a notify packet to the given
|
|
|
address, but it appears to be an invalid address. The configuration
|
|
|
-for secondary nameservers might contain a typographic error.
|
|
|
+for secondary nameservers might contain a typographic error, or a
|
|
|
+different BIND 10 module has forgotten to validate its data before
|
|
|
+sending this module a notify command. As such, this should normally
|
|
|
+not happen, and points to an oversight in a different module.
|
|
|
|
|
|
% NOTIFY_OUT_REPLY_BAD_OPCODE bad opcode in notify reply from %1#%2: %3
|
|
|
-The notify_out library sent a notify packet to the nameserver at the
|
|
|
-given address, but the response did not have the opcode set to NOTIFY.
|
|
|
-The opcode in the response is printed.
|
|
|
+The notify_out library sent a notify message to the nameserver at
|
|
|
+the given address, but the response did not have the opcode set to
|
|
|
+NOTIFY. The opcode in the response is printed. Since there was a
|
|
|
+response, no more notifies will be sent to this server for this
|
|
|
+notification event.
|
|
|
|
|
|
% NOTIFY_OUT_REPLY_BAD_QID bad QID in notify reply from %1#%2: got %3, should be %4
|
|
|
-The notify_out library sent a notify packet to the nameserver at the
|
|
|
-given address, but the query id in the response does not match the one
|
|
|
-we sent.
|
|
|
+The notify_out library sent a notify message to the nameserver at
|
|
|
+the given address, but the query id in the response does not match
|
|
|
+the one we sent. Since there was a response, no more notifies will
|
|
|
+be sent to this server for this notification event.
|
|
|
|
|
|
% NOTIFY_OUT_REPLY_BAD_QUERY_NAME bad query name in notify reply from %1#%2: got %3, should be %4
|
|
|
-The notify_out library sent a notify packet to the nameserver at the
|
|
|
-given address, but the query name in the response does not match the one
|
|
|
-we sent.
|
|
|
+The notify_out library sent a notify message to the nameserver at
|
|
|
+the given address, but the query name in the response does not match
|
|
|
+the one we sent. Since there was a response, no more notifies will
|
|
|
+be sent to this server for this notification event.
|
|
|
|
|
|
% NOTIFY_OUT_REPLY_QR_NOT_SET QR flags set to 0 in reply to notify from %1#%2
|
|
|
The notify_out library sent a notify packet to the namesever at the
|
|
|
given address, but the reply did not have the QR bit set to one.
|
|
|
|
|
|
-% NOTIFY_OUT_RETRY_EXCEEDED notify to %1#%2: number of retries exceeded
|
|
|
+% NOTIFY_OUT_RETRY_EXCEEDED notify to %1#%2: number of retries (%3) exceeded
|
|
|
The maximum number of retries for the notify target has been exceeded.
|
|
|
Either the address of the secondary nameserver is wrong, or it is not
|
|
|
responding.
|
|
@@ -56,22 +63,24 @@ A notify message is sent to the secondary nameserver at the given
|
|
|
address.
|
|
|
|
|
|
% NOTIFY_OUT_SOCKET_ERROR socket error sending notify to %1#%2: %3
|
|
|
-There was a network connection error while trying to send a notify
|
|
|
-packet to the given address. The socket error is printed and should
|
|
|
-provide more information.
|
|
|
+There was a network error while trying to send a notify packet to
|
|
|
+the given address. The address might be unreachable. The socket
|
|
|
+error is printed and should provide more information.
|
|
|
|
|
|
% NOTIFY_OUT_SOCKET_RECV_ERROR socket error reading notify reply from %1#%2: %3
|
|
|
-There was a network connection error while trying to read a notify reply
|
|
|
+There was a network error while trying to read a notify reply
|
|
|
packet from the given address. The socket error is printed and should
|
|
|
provide more information.
|
|
|
|
|
|
-% NOTIFY_OUT_TIMEOUT_RETRY retry notify to %1#%2
|
|
|
+% NOTIFY_OUT_TIMEOUT retry notify to %1#%2
|
|
|
The notify message to the given address (noted as address#port) has
|
|
|
-timed out, and the message is sent again.
|
|
|
+timed out, and the message will be resent until the max retry limit
|
|
|
+is reached.
|
|
|
|
|
|
% NOTIFY_OUT_REPLY_UNCAUGHT_EXCEPTION uncaught exception: %1
|
|
|
There was an uncaught exception in the handling of a notify reply
|
|
|
-packet. The error is printed, and notify_out will treat the response
|
|
|
-as a bad packet, but this does point to a programming error, since
|
|
|
-all exceptions should have been caught explicitely. Please file
|
|
|
-a bug report.
|
|
|
+packet, either in the packet parser, or while trying to extract data
|
|
|
+from the parsed packet. The error is printed, and notify_out will
|
|
|
+treat the response as a bad packet, but this does point to a
|
|
|
+programming error, since all exceptions should have been caught
|
|
|
+explicitely. Please file a bug report.
|