|
@@ -16,6 +16,10 @@ $NAMESPACE isc::datasrc::memory
|
|
|
|
|
|
# \brief Messages for the data source memory library
|
|
|
|
|
|
+% DATASRC_MEMORY_ANY_SUCCESS ANY query for '%1' successful
|
|
|
+Debug information. The domain was found and an ANY type query is being answered
|
|
|
+by providing everything found inside the domain.
|
|
|
+
|
|
|
% DATASRC_MEMORY_BAD_NSEC3_NAME NSEC3 record has a bad owner name '%1'
|
|
|
The software refuses to load NSEC3 records into a wildcard domain or
|
|
|
the owner name has two or more labels below the zone origin.
|
|
@@ -23,6 +27,71 @@ It isn't explicitly forbidden, but no sane zone wouldn have such names
|
|
|
for NSEC3. BIND 9 also refuses NSEC3 at wildcard, so this behavior is
|
|
|
compatible with BIND 9.
|
|
|
|
|
|
+% DATASRC_MEMORY_CHECK_ERROR post-load check of zone %1/%2 failed: %3
|
|
|
+The zone was loaded into the data source successfully, but the content fails
|
|
|
+basic sanity checks. See the message if you want to know what exactly is wrong
|
|
|
+with the data. The data can not be used and previous version, if any, will be
|
|
|
+preserved.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_CHECK_WARNING %1/%2: %3
|
|
|
+The zone was loaded into the data source successfully, but there's some problem
|
|
|
+with the content. The problem does not stop the new version from being used
|
|
|
+(though there may be other problems that do, see DATASRC_MEMORY_CHECK_ERROR),
|
|
|
+but it should still be checked and fixed. See the message to know what exactly
|
|
|
+is wrong with the data.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_CNAME CNAME at the domain '%1'
|
|
|
+Debug information. The requested domain is an alias to a different domain,
|
|
|
+returning the CNAME instead.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_DELEG_FOUND delegation found at '%1'
|
|
|
+Debug information. A delegation point was found above the requested record.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_DNAME_ENCOUNTERED encountered a DNAME
|
|
|
+Debug information. While searching for the requested domain, a DNAME was
|
|
|
+encountered on the way. This may lead to redirection to a different domain and
|
|
|
+stop the search.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_DNAME_FOUND DNAME found at '%1'
|
|
|
+Debug information. A DNAME was found instead of the requested information.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_DOMAIN_EMPTY requested domain '%1' is empty
|
|
|
+Debug information. The requested domain exists in the tree of domains, but
|
|
|
+it is empty. Therefore it doesn't contain the requested resource type.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_EXACT_DELEGATION delegation at the exact domain '%1'
|
|
|
+Debug information. There's a NS record at the requested domain. This means
|
|
|
+this zone is not authoritative for the requested domain, but a delegation
|
|
|
+should be followed. The requested domain is an apex of some zone.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_FINDNSEC3 finding NSEC3 for %1, mode %2
|
|
|
+Debug information. A search in an in-memory data source for NSEC3 that
|
|
|
+matches or covers the given name is being started.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_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_MEMORY_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_MEMORY_FINDNSEC3_TRYHASH).
|
|
|
+The found NSEC3 RRset is also displayed.
|
|
|
+
|
|
|
+% DATASRC_MEMORY_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).
|
|
|
+
|
|
|
+% DATASRC_MEMORY_FIND_TYPE_AT_ORIGIN origin query for type %1 in in-memory zone %2/%3 successful
|
|
|
+Debug information. A specific type RRset is requested at a zone origin
|
|
|
+of an in-memory zone and it is found.
|
|
|
+
|
|
|
% DATASRC_MEMORY_MEM_ADD_RRSET adding RRset '%1/%2' into zone '%3'
|
|
|
Debug information. An RRset is being added to the in-memory data source.
|
|
|
|
|
@@ -89,33 +158,15 @@ explicitly forbidden, but the protocol is ambiguous about how this should
|
|
|
behave and BIND 9 refuses that as well. Please describe your intention using
|
|
|
different tools.
|
|
|
|
|
|
-% DATASRC_MEMORY_CHECK_ERROR post-load check of zone %1/%2 failed: %3
|
|
|
-The zone was loaded into the data source successfully, but the content fails
|
|
|
-basic sanity checks. See the message if you want to know what exactly is wrong
|
|
|
-with the data. The data can not be used and previous version, if any, will be
|
|
|
-preserved.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_CHECK_WARNING %1/%2: %3
|
|
|
-The zone was loaded into the data source successfully, but there's some problem
|
|
|
-with the content. The problem does not stop the new version from being used
|
|
|
-(though there may be other problems that do, see DATASRC_MEMORY_CHECK_ERROR),
|
|
|
-but it should still be checked and fixed. See the message to know what exactly
|
|
|
-is wrong with the data.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_DNAME_ENCOUNTERED encountered a DNAME
|
|
|
-Debug information. While searching for the requested domain, a DNAME was
|
|
|
-encountered on the way. This may lead to redirection to a different domain and
|
|
|
-stop the search.
|
|
|
+% DATASRC_MEMORY_NOT_FOUND requested domain '%1' not found
|
|
|
+Debug information. The requested domain does not exist.
|
|
|
|
|
|
% DATASRC_MEMORY_NS_ENCOUNTERED encountered a NS
|
|
|
Debug information. While searching for the requested domain, a NS was
|
|
|
encountered on the way (a delegation). This may lead to stop of the search.
|
|
|
|
|
|
-% DATASRC_MEMORY_DNAME_FOUND DNAME found at '%1'
|
|
|
-Debug information. A DNAME was found instead of the requested information.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_DELEG_FOUND delegation found at '%1'
|
|
|
-Debug information. A delegation point was found above the requested record.
|
|
|
+% DATASRC_MEMORY_SUCCESS query for '%1/%2' successful
|
|
|
+Debug information. The requested record was found.
|
|
|
|
|
|
% DATASRC_MEMORY_SUPER_STOP stopped as '%1' is superdomain of a zone node, meaning it's empty
|
|
|
Debug information. The search stopped because the requested domain was
|
|
@@ -128,54 +179,3 @@ doesn't have the requested record type).
|
|
|
Debug information. A domain above wildcard was reached, but there's something
|
|
|
below the requested domain. Therefore the wildcard doesn't apply here. This
|
|
|
behaviour is specified by RFC 1034, section 4.3.3.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_NOT_FOUND requested domain '%1' not found
|
|
|
-Debug information. The requested domain does not exist.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_FIND_TYPE_AT_ORIGIN origin query for type %1 in in-memory zone %2/%3 successful
|
|
|
-Debug information. A specific type RRset is requested at a zone origin
|
|
|
-of an in-memory zone and it is found.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_DOMAIN_EMPTY requested domain '%1' is empty
|
|
|
-Debug information. The requested domain exists in the tree of domains, but
|
|
|
-it is empty. Therefore it doesn't contain the requested resource type.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_EXACT_DELEGATION delegation at the exact domain '%1'
|
|
|
-Debug information. There's a NS record at the requested domain. This means
|
|
|
-this zone is not authoritative for the requested domain, but a delegation
|
|
|
-should be followed. The requested domain is an apex of some zone.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_ANY_SUCCESS ANY query for '%1' successful
|
|
|
-Debug information. The domain was found and an ANY type query is being answered
|
|
|
-by providing everything found inside the domain.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_SUCCESS query for '%1/%2' successful
|
|
|
-Debug information. The requested record was found.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_CNAME CNAME at the domain '%1'
|
|
|
-Debug information. The requested domain is an alias to a different domain,
|
|
|
-returning the CNAME instead.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_FINDNSEC3 finding NSEC3 for %1, mode %2
|
|
|
-Debug information. A search in an in-memory data source for NSEC3 that
|
|
|
-matches or covers the given name is being started.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_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_MEMORY_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_MEMORY_FINDNSEC3_TRYHASH).
|
|
|
-The found NSEC3 RRset is also displayed.
|
|
|
-
|
|
|
-% DATASRC_MEMORY_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).
|