BIND 10 trac1539-2, updated. fd12fc9298c6015c90321c8b9144ec2565b24dd0 [1539] some wording updates to log description for AUTH_MESSAGE_FORWARD_ERROR.

BIND 10 source code commits bind10-changes at lists.isc.org
Tue May 22 17:58:58 UTC 2012


The branch, trac1539-2 has been updated
       via  fd12fc9298c6015c90321c8b9144ec2565b24dd0 (commit)
      from  3aa296cf17e158576175ca0c349a6dee19a97af1 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit fd12fc9298c6015c90321c8b9144ec2565b24dd0
Author: JINMEI Tatuya <jinmei at isc.org>
Date:   Tue May 22 10:56:42 2012 -0700

    [1539] some wording updates to log description for AUTH_MESSAGE_FORWARD_ERROR.
    
    - use recipient instead of forwarded as it seemed more intuitive
    - descirbe how the request is responded
    - use 'component' instead of 'program' where it's more appropriate
    - use 'process' instead of 'program' where it's more appropriate

-----------------------------------------------------------------------

Summary of changes:
 src/bin/auth/auth_messages.mes |   19 ++++++++++---------
 1 files changed, 10 insertions(+), 9 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/bin/auth/auth_messages.mes b/src/bin/auth/auth_messages.mes
index 3d1a6d6..aeeb94f 100644
--- a/src/bin/auth/auth_messages.mes
+++ b/src/bin/auth/auth_messages.mes
@@ -258,15 +258,16 @@ will return an error code of NOTIMPL to the sender.
 % AUTH_MESSAGE_FORWARD_ERROR failed to forward %1 request from %2: %3
 The authoritative server tried to forward some type DNS request
 message to a separate process (e.g., forwarding dynamic update
-requests to b10-ddns) to handle it, but it failed.  It could be
-configuration mismatch between b10-auth and the forwarded program, or
-it may because the requests are coming too fast and the forwarded
-program cannot keep up with the rate, or some system level failure.
-In either case this means the BIND 10 system is not working as
-expected, so the administrator should look into the cause and address
-the issue.  The log message includes the client's address (and port),
-and the error message sent from the lower layer that detects the
-failure.
+requests to b10-ddns) to handle it, but it failed.  The authoritative
+server returns SERVFAIL to the client on behalf of the separate
+process.  The error could be configuration mismatch between b10-auth
+and the recipient component, or it may be because the requests are
+coming too fast and the receipient process cannot keep up with the
+rate, or some system level failure.  In either case this means the
+BIND 10 system is not working as expected, so the administrator should
+look into the cause and address the issue.  The log message includes
+the client's address (and port), and the error message sent from the
+lower layer that detects the failure.
 
 % AUTH_XFRIN_CHANNEL_CREATED XFRIN session channel created
 This is a debug message indicating that the authoritative server has



More information about the bind10-changes mailing list