|
@@ -0,0 +1,155 @@
|
|
|
+# Copyright (C) 2011 Internet Systems Consortium, Inc. ("ISC")
|
|
|
+#
|
|
|
+# Permission to use, copy, modify, and/or distribute this software for any
|
|
|
+# purpose with or without fee is hereby granted, provided that the above
|
|
|
+# copyright notice and this permission notice appear in all copies.
|
|
|
+#
|
|
|
+# THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
|
|
|
+# REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
|
|
|
+# AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
|
|
|
+# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
|
|
|
+# LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
|
|
|
+# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
|
|
+# PERFORMANCE OF THIS SOFTWARE.
|
|
|
+
|
|
|
+$PREFIX RESLIB_
|
|
|
+$NAMESPACE isc::resolve
|
|
|
+
|
|
|
+% ANSWER answer received in response to query for <%1>
|
|
|
+A debug message recording that an answer has been received to an upstream
|
|
|
+query for the specified question. Previous debug messages will have indicated
|
|
|
+the server to which the question was sent.
|
|
|
+
|
|
|
+% CNAME CNAME received in response to query for <%1>
|
|
|
+A debug message recording that CNAME response has been received to an upstream
|
|
|
+query for the specified question. Previous debug messages will have indicated
|
|
|
+the server to which the question was sent."
|
|
|
+
|
|
|
+% DEEPEST did not find <%1> in cache, deepest delegation found is %2
|
|
|
+A debug message, a cache lookup did not find the specified <name, class,
|
|
|
+type> tuple in the cache; instead, the deepest delegation found is indicated.
|
|
|
+
|
|
|
+% FOLLOWCNAME following CNAME chain to <%1>
|
|
|
+A debug message, a CNAME response was received and another query is being issued
|
|
|
+for the <name, class, type> tuple.
|
|
|
+
|
|
|
+% LONGCHAIN CNAME received in response to query for <%1>: CNAME chain length exceeded
|
|
|
+A debug message recording that CNAME response has been received to an upstream
|
|
|
+query for the specified question. (Previous debug messages will have indicated
|
|
|
+the server to which the question was sent.") However, receipt of this CNAME
|
|
|
+has meant that the resolver has exceeded the CNAME chain limit (a CNAME chain
|
|
|
+is where on CNAME points to another) and so an error is being returned.
|
|
|
+
|
|
|
+% NONSRRSET no NS RRSet in referral response received to query for <%1>
|
|
|
+A debug message, this indicates that a response was received for the specified
|
|
|
+query and was categorised as a referral. However, the received message did
|
|
|
+not contain any NS RRsets. This may indicate a programming error in the
|
|
|
+response classification code.
|
|
|
+
|
|
|
+% NSASLOOK looking up nameserver for zone %1 in the NSAS
|
|
|
+A debug message, the RunningQuery object is querying the NSAS for the
|
|
|
+nameservers for the specified zone.
|
|
|
+
|
|
|
+% NXDOMRR NXDOMAIN/NXRRSET received in response to query for <%1>
|
|
|
+A debug message recording that either a NXDOMAIN or an NXRRSET response has
|
|
|
+been received to an upstream query for the specified question. Previous debug
|
|
|
+messages will have indicated the server to which the question was sent.
|
|
|
+
|
|
|
+% PROTOCOL protocol error in answer for %1: %3
|
|
|
+A debug message indicating that a protocol error was received. As there
|
|
|
+are no retries left, an error will be reported.
|
|
|
+
|
|
|
+% PROTOCOLRTRY protocol error in answer for %1: %2 (retries left: %3)
|
|
|
+A debug message indicating that a protocol error was received and that
|
|
|
+the resolver is repeating the query to the same nameserver. After this
|
|
|
+repeated query, there will be the indicated number of retries left.
|
|
|
+
|
|
|
+% RCODERR RCODE indicates error in response to query for <%1>
|
|
|
+A debug message, the response to the specified query indicated an error
|
|
|
+that is not covered by a specific code path. A SERVFAIL will be returned.
|
|
|
+
|
|
|
+% REFERRAL referral received in response to query for <%1>
|
|
|
+A debug message recording that a referral response has been received to an
|
|
|
+upstream query for the specified question. Previous debug messages will
|
|
|
+have indicated the server to which the question was sent.
|
|
|
+
|
|
|
+% REFERZONE referred to zone %1
|
|
|
+A debug message indicating that the last referral message was to the specified
|
|
|
+zone.
|
|
|
+
|
|
|
+% RESCAFND found <%1> in the cache (resolve() instance %2)
|
|
|
+This is a debug message and indicates that a RecursiveQuery object found the
|
|
|
+the specified <name, class, type> tuple in the cache. The instance number
|
|
|
+at the end of the message indicates which of the two resolve() methods has
|
|
|
+been called.
|
|
|
+
|
|
|
+% RESCANOTFND did not find <%1> in the cache, starting RunningQuery (resolve() instance %2)
|
|
|
+This is a debug message and indicates that the look in the cache made by the
|
|
|
+RecursiveQuery::resolve() method did not find an answer, so a new RunningQuery
|
|
|
+object has been created to resolve the question. The instance number at
|
|
|
+the end of the message indicates which of the two resolve() methods has
|
|
|
+been called.
|
|
|
+
|
|
|
+% RESOLVE asked to resolve <%1> (resolve() instance %2)
|
|
|
+A debug message, the RecursiveQuery::resolve method has been called to resolve
|
|
|
+the specified <name, class, type> tuple. The first action will be to lookup
|
|
|
+the specified tuple in the cache. The instance number at the end of the
|
|
|
+message indicates which of the two resolve() methods has been called.
|
|
|
+
|
|
|
+% RRSETFND found single RRset in the cache when querying for <%1> (resolve() instance %2)
|
|
|
+A debug message, indicating that when RecursiveQuery::resolve queried the
|
|
|
+cache, a single RRset was found which was put in the answer. The instance
|
|
|
+number at the end of the message indicates which of the two resolve()
|
|
|
+methods has been called.
|
|
|
+
|
|
|
+% RTT round-trip time of last query calculated as %1
|
|
|
+A debug imessage giving the RTT of the last query and response.
|
|
|
+
|
|
|
+% RUNCAFND found <%1> in the cache
|
|
|
+This is a debug message and indicates that a RunningQuery object found the
|
|
|
+the specified <name, class, type> tuple in the cache.
|
|
|
+
|
|
|
+% RUNCALOOK looking up up <%1> in the cache
|
|
|
+This is a debug message and indicates that a RunningQuery object has made
|
|
|
+a call to its doLookup() method to look up the specified <name, class, type>
|
|
|
+tuple, the first action of which will be to examine the cache.
|
|
|
+
|
|
|
+% RUNQUFAIL failure callback - nameservers are unreachable
|
|
|
+A debug message indicating that a RunningQuery's failure callback has been
|
|
|
+called because all nameservers for the zone in question are unreachable.
|
|
|
+
|
|
|
+% RUNQUSUCC success callback - sending query to %1
|
|
|
+A debug message indicating that a RunningQuery's success callback has been
|
|
|
+called because a nameserver has been found, and that a query is being sent
|
|
|
+to the specified nameserver.
|
|
|
+
|
|
|
+% TESTSERV setting test server to %1(%2)
|
|
|
+This is an internal debugging message and is only generated in unit tests.
|
|
|
+It indicates that all upstream queries from the resolver are being routed to
|
|
|
+the specified server, regardless of the address of the nameserver to which
|
|
|
+the query would normall be routed. As it should never be seen in normal
|
|
|
+operation, it is a warning message instead of a debug message.
|
|
|
+
|
|
|
+% TESTUPSTR sending upstream query for <%1> to test server at %2
|
|
|
+This is a debug message and should only be seen in unit tests. A query for
|
|
|
+the specified <name, class, type> tuple is being sent to a test nameserver
|
|
|
+whose address is given in the message.
|
|
|
+
|
|
|
+% TIMEOUT query <%1> to %2 timed out
|
|
|
+A debug message indicating that the specified query has timed out and as
|
|
|
+there are no retries left, an error will be reported.
|
|
|
+
|
|
|
+% TIMEOUTRTRY query <%1> to %2 timed out, re-trying (retries left: %3)
|
|
|
+A debug message indicating that the specified query has timed out and that
|
|
|
+the resolver is repeating the query to the same nameserver. After this
|
|
|
+repeated query, there will be the indicated number of retries left.
|
|
|
+
|
|
|
+% TRUNCATED response to query for <%1> was truncated, re-querying over TCP
|
|
|
+A debug message, this indicates that the response to the specified query was
|
|
|
+truncated and that the resolver will be re-querying over TCP. There are
|
|
|
+various reasons why responses may be truncated, so this message is normal and
|
|
|
+gives no cause for concern.
|
|
|
+
|
|
|
+% UPSTREAM sending upstream query for <%1> to %2
|
|
|
+A debug message indicating that a query for the specified <name, class, type>
|
|
|
+tuple is being sent to a nameserver whose address is given in the message.
|