This is the reference guide for BIND 10 version 20110519. The most up-to-date version of this document, along with - other documents for BIND 10, can be found at http://bind10.isc.org/docs.
Table of Contents
Table of Contents
+ other documents for BIND 10, can be found at http://bind10.isc.org/docs.
Table of Contents
Table of Contents
BIND is the popular implementation of a DNS server, developer interfaces, and DNS tools. BIND 10 is a rewrite of BIND 9. BIND 10 is written in C++ and Python @@ -684,4 +684,48 @@ This may be a temporary setting until then. "stats.timestamp": 1295543046.823504 }
+
+ Each message written by BIND 10 to the configured logging destinations + comprises a number of components that identify the origin of the + message and, if the message indicates a problem, information about the + problem that may be useful in fixing it. +
+ Consider the message below logged to a file: +
2011-06-15 13:48:22.034 ERROR [b10-resolver.asiolink] + ASIODNS_OPENSOCK error 111 opening TCP socket to 127.0.0.1(53)
+
+ Note: the layout of messages written to the system logging + file (syslog) may be slightly different. This message has + been split across two lines here for display reasons; in the + logging file, it will appear on one line.) +
+ The log message comprises a number of components: + +
+ The date and time at which the message was generated. +
+ The severity of the message. +
+ The source of the message. This comprises two components: + the BIND 10 process generating the message (in this + case, b10-resolver) and the module + within the program from which the message originated + (which in the example is the asynchronous I/O link + module, asiolink). +
+ The message identification. Every message in BIND 10 + has a unique identification, which can be used as an + index into the BIND 10 Messages + Manual (http://bind10.isc.org/docs/bind10-messages.html) from which more information can be obtained. +
+ A brief description of the cause of the problem. Within this text, + information relating to the condition that caused the message to + be logged will be included. In this example, error number 111 + (an operating system-specific error number) was encountered when + trying to open a TCP connection to port 53 on the local system + (address 127.0.0.1). The next step would be to find out the reason + for the failure by consulting your system's documentation to + identify what error number 111 means. +
+