resolver_messages.mes 12.4 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
# 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.

# No namespace declaration - these constants go in the global namespace
# along with the resolver methods.

18
% RESOLVER_AXFR_TCP AXFR request received over TCP
19 20 21 22
This is a debug message output when the resolver received a request for
an AXFR (full transfer of a zone) over TCP.  Only authoritative servers
are able to handle AXFR requests, so the resolver will return an error
message to the sender with the RCODE set to NOTIMP.
23

24
% RESOLVER_AXFR_UDP AXFR request received over UDP
25
This is a debug message output when the resolver received a request for
26
an AXFR (full transfer of a zone) over UDP.  Only authoritative servers
27 28 29
are able to handle AXFR requests (and in any case, an AXFR request should
be sent over TCP), so the resolver will return an error message to the
sender with the RCODE set to NOTIMP.
30

31
% RESOLVER_CLIENT_TIME_SMALL client timeout of %1 is too small
32 33 34
During the update of the resolver's configuration parameters, the value
of the client timeout was found to be too small.  The configuration
update was abandoned and the parameters were not changed.
35 36

% RESOLVER_CONFIG_CHANNEL configuration channel created
37 38
This is a debug message output when the resolver has successfully
established a connection to the configuration channel.
39

40
% RESOLVER_CONFIG_ERROR error in configuration: %1
41 42 43 44 45 46
An error was detected in a configuration update received by the
resolver. This may be in the format of the configuration message (in
which case this is a programming error) or it may be in the data supplied
(in which case it is a user error).  The reason for the error, included
in the message, will give more details.  The configuration update is
not applied and the resolver parameters were not changed.
47

48
% RESOLVER_CONFIG_LOADED configuration loaded
49 50
This is a debug message output when the resolver configuration has been
successfully loaded.
51

52
% RESOLVER_CONFIG_UPDATED configuration updated: %1
53 54
This is a debug message output when the resolver configuration is being
updated with the specified information.
55

56
% RESOLVER_CREATED main resolver object created
57 58
This is a debug message indicating that the main resolver object has
been created.
59

60
% RESOLVER_DNS_MESSAGE_RECEIVED DNS message received: %1
61 62
This is a debug message from the resolver listing the contents of a
received DNS message.
63

64
% RESOLVER_DNS_MESSAGE_SENT DNS message of %1 bytes sent: %2
65 66
This is a debug message containing details of the response returned by
the resolver to the querying system.
67

68
% RESOLVER_FAILED resolver failed, reason: %1
69 70 71
This is an error message output when an unhandled exception is caught
by the resolver.  After this, the resolver will shut itself down.
Please submit a bug report.
72

73
% RESOLVER_FORWARD_ADDRESS setting forward address %1(%2)
74 75 76
If the resolver is running in forward mode, this message will appear
during startup to list the forward address.  If multiple addresses are
specified, it will appear once for each address.
77

78
% RESOLVER_FORWARD_QUERY processing forward query
79 80
This is a debug message indicating that a query received by the resolver
has passed a set of checks (message is well-formed, it is allowed by the
81
ACL, it is a supported opcode, etc.) and is being forwarded to upstream
82 83
servers.

84
% RESOLVER_HEADER_ERROR message received, exception when processing header: %1
85 86 87
This is a debug message from the resolver noting that an exception
occurred during the processing of a received packet.  The packet has
been dropped.
88

89
% RESOLVER_IXFR IXFR request received
90 91 92 93
This is a debug message indicating that the resolver received a request
for an IXFR (incremental transfer of a zone).  Only authoritative servers
are able to handle IXFR requests, so the resolver will return an error
message to the sender with the RCODE set to NOTIMP.
94

95
% RESOLVER_LOOKUP_TIME_SMALL lookup timeout of %1 is too small
96 97 98
During the update of the resolver's configuration parameters, the value
of the lookup timeout was found to be too small.  The configuration
update will not be applied.
99

100
% RESOLVER_MESSAGE_ERROR error parsing received message: %1 - returning %2
101 102 103 104
This is a debug message noting that parsing of the body of a received
message by the resolver failed due to some error (although the parsing of
the header succeeded).  The message parameters give a textual description
of the problem and the RCODE returned.
105 106

% RESOLVER_NEGATIVE_RETRIES negative number of retries (%1) specified in the configuration
107 108 109
This error is issued when a resolver configuration update has specified
a negative retry count: only zero or positive values are valid.  The
configuration update was abandoned and the parameters were not changed.
110

111
% RESOLVER_NON_IN_PACKET non-IN class request received, returning REFUSED message
112 113 114
This debug message is issued when resolver has received a DNS packet that
was not IN (Internet) class.  The resolver cannot handle such packets,
so is returning a REFUSED response to the sender.
115

116
% RESOLVER_NORMAL_QUERY processing normal query
117 118
This is a debug message indicating that the query received by the resolver
has passed a set of checks (message is well-formed, it is allowed by the
119
ACL, it is a supported opcode, etc.) and is being processed by the resolver.
120

121
% RESOLVER_NOTIFY_RECEIVED NOTIFY arrived but server is not authoritative
122 123 124
The resolver has received a NOTIFY message.  As the server is not
authoritative it cannot process it, so it returns an error message to
the sender with the RCODE set to NOTAUTH.
125

126
% RESOLVER_NOT_ONE_QUESTION query contained %1 questions, exactly one question was expected
127 128 129 130 131
This debug message indicates that the resolver received a query that
contained the number of entries in the question section detailed in
the message.  This is a malformed message, as a DNS query must contain
only one question.  The resolver will return a message to the sender
with the RCODE set to FORMERR.
132

133
% RESOLVER_NO_ROOT_ADDRESS no root addresses available
134 135 136
A warning message issued during resolver startup, this indicates that
no root addresses have been set.  This may be because the resolver will
get them from a priming query.
137

138
% RESOLVER_PARSE_ERROR error parsing received message: %1 - returning %2
139 140 141 142 143
This is a debug message noting that the resolver received a message and
the parsing of the body of the message failed due to some non-protocol
related reason (although the parsing of the header succeeded).
The message parameters give a textual description of the problem and
the RCODE returned.
144

145
% RESOLVER_PRINT_COMMAND print message command, arguments are: %1
146 147
This debug message is logged when a "print_message" command is received
by the resolver over the command channel.
148

149
% RESOLVER_PROTOCOL_ERROR protocol error parsing received message: %1 - returning %2
150 151 152 153
This is a debug message noting that the resolver received a message and
the parsing of the body of the message failed due to some protocol error
(although the parsing of the header succeeded).  The message parameters
give a textual description of the problem and the RCODE returned.
154

155
% RESOLVER_QUERY_SETUP query setup
156 157
This is a debug message noting that the resolver is creating a
RecursiveQuery object.
158 159

% RESOLVER_QUERY_SHUTDOWN query shutdown
160 161
This is a debug message noting that the resolver is destroying a
RecursiveQuery object.
162 163

% RESOLVER_QUERY_TIME_SMALL query timeout of %1 is too small
164 165 166
During the update of the resolver's configuration parameters, the value
of the query timeout was found to be too small.  The configuration
parameters were not changed.
167

168
% RESOLVER_RECEIVED_MESSAGE resolver has received a DNS message
169 170 171
This is a debug message indicating that the resolver has received a
DNS message.  Depending on the debug settings, subsequent log output
will indicate the nature of the message.
172

173
% RESOLVER_RECURSIVE running in recursive mode
174 175
This is an informational message that appears at startup noting that
the resolver is running in recursive mode.
176 177

% RESOLVER_SERVICE_CREATED service object created
178 179
This debug message is output when resolver creates the main service object
(which handles the received queries).
180

181
% RESOLVER_SET_PARAMS query timeout: %1, client timeout: %2, lookup timeout: %3, retry count: %4
182
This debug message lists the parameters being set for the resolver.  These are:
183
query timeout: the timeout (in ms) used for queries originated by the resolver
184
to upstream servers.  Client timeout: the interval to resolve a query by
185
a client: after this time, the resolver sends back a SERVFAIL to the client
186
whilst continuing to resolve the query. Lookup timeout: the time at which the
187 188 189 190
resolver gives up trying to resolve a query.  Retry count: the number of times
the resolver will retry a query to an upstream server if it gets a timeout.

The client and lookup timeouts require a bit more explanation. The
191
resolution of the client query might require a large number of queries to
192 193 194
upstream nameservers.  Even if none of these queries timeout, the total time
taken to perform all the queries may exceed the client timeout.  When this
happens, a SERVFAIL is returned to the client, but the resolver continues
195
with the resolution process; data received is added to the cache.  However,
196
there comes a time - the lookup timeout - when even the resolver gives up.
197 198 199
At this point it will wait for pending upstream queries to complete or
timeout and drop the query.

200
% RESOLVER_SET_ROOT_ADDRESS setting root address %1(%2)
201 202
This message gives the address of one of the root servers used by the
resolver.  It is output during startup and may appear multiple times,
203
once for each root server address.
204 205

% RESOLVER_SHUTDOWN resolver shutdown complete
206
This informational message is output when the resolver has shut down.
207

208
% RESOLVER_STARTED resolver started
209 210 211
This informational message is output by the resolver when all initialization
has been completed and it is entering its main loop.

212
% RESOLVER_STARTING starting resolver with command line '%1'
213 214
An informational message, this is output when the resolver starts up.

215
% RESOLVER_UNEXPECTED_RESPONSE received unexpected response, ignoring
216 217 218
This is a debug message noting that the resolver received a DNS response
packet on the port on which is it listening for queries.  The packet
has been ignored.
219 220

% RESOLVER_UNSUPPORTED_OPCODE opcode %1 not supported by the resolver
221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248
This is debug message output when the resolver received a message with an
unsupported opcode (it can only process QUERY opcodes).  It will return
a message to the sender with the RCODE set to NOTIMP.

% RESOLVER_SET_QUERY_ACL query ACL is configured
This debug message is generated when a new query ACL is configured for
the resolver.

% RESOLVER_QUERY_ACCEPTED query accepted: '%1/%2/%3' from %4
This debug message is produced by the resolver when an incoming query
is accepted in terms of the query ACL.  The log message shows the query
in the form of <query name>/<query type>/<query class>, and the client
that sends the query in the form of <Source IP address>#<source port>.

% RESOLVER_QUERY_REJECTED query rejected: '%1/%2/%3' from %4
This is an informational message that indicates an incoming query has
been rejected by the resolver because of the query ACL.  This results
in a response with an RCODE of REFUSED. The log message shows the query
in the form of <query name>/<query type>/<query class>, and the client
that sends the query in the form of <Source IP address>#<source port>.

% RESOLVER_QUERY_DROPPED query dropped: '%1/%2/%3' from %4
This is an informational message that indicates an incoming query has
been dropped by the resolver because of the query ACL.  Unlike the
RESOLVER_QUERY_REJECTED case, the server does not return any response.
The log message shows the query in the form of <query name>/<query
type>/<query class>, and the client that sends the query in the form of
<Source IP address>#<source port>.
249

250
% RESOLVER_SHUTDOWN_RECEIVED received command to shut down
251 252
A debug message noting that the server was asked to terminate and is
complying to the request.