BIND 10 trac2759, updated. 213d905ed8661b9d1f5ce214c6f391e702d518d7 [2759] Update log messages to better reflect the DDNS case

BIND 10 source code commits bind10-changes at lists.isc.org
Thu Jun 27 00:56:40 UTC 2013


The branch, trac2759 has been updated
       via  213d905ed8661b9d1f5ce214c6f391e702d518d7 (commit)
      from  fac95b174e553ac8eba5805c47541530e9fbb2e1 (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 213d905ed8661b9d1f5ce214c6f391e702d518d7
Author: Mukund Sivaraman <muks at isc.org>
Date:   Thu Jun 27 06:26:15 2013 +0530

    [2759] Update log messages to better reflect the DDNS case

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

Summary of changes:
 src/lib/python/isc/ddns/libddns_messages.mes |   16 +++++++++-------
 1 file changed, 9 insertions(+), 7 deletions(-)

-----------------------------------------------------------------------
diff --git a/src/lib/python/isc/ddns/libddns_messages.mes b/src/lib/python/isc/ddns/libddns_messages.mes
index d9bfbc9..86af4c3 100644
--- a/src/lib/python/isc/ddns/libddns_messages.mes
+++ b/src/lib/python/isc/ddns/libddns_messages.mes
@@ -213,10 +213,12 @@ of reraised; The update is aborted, and a SERVFAIL is sent back to the client.
 This is most probably a bug in the DDNS code, but *could* be caused by
 the data source.
 
-% LIBDDNS_ZONE_INVALID_ERROR Newly received zone %1/%2 fails validation: %3
-The zone was received successfully, but it failed validation.
-
-% LIBDDNS_ZONE_INVALID_WARN Newly received zone %1/%2 has a problem: %3
-The zone was received successfully, but when checking it, it was discovered
-there's some issue with it. It might be correct, but it should be checked
-and possibly fixed. The problem does not stop the zone from being used.
+% LIBDDNS_ZONE_INVALID_ERROR Newly received zone data %1/%2 fails validation: %3
+The zone data was received successfully, but the zone when updated with
+this zone data fails validation.
+
+% LIBDDNS_ZONE_INVALID_WARN Newly received zone data %1/%2 has a problem: %3
+The zone data was received successfully, but when checking the zone when
+updated with this zone data, it was discovered there's some issue with
+it. It might be correct, but it should be checked and possibly
+fixed. The problem does not stop the zone from being used.



More information about the bind10-changes mailing list