diff --git a/doc/guide/bind10-guide.xml b/doc/guide/bind10-guide.xml index b1861111fd..6cea253024 100644 --- a/doc/guide/bind10-guide.xml +++ b/doc/guide/bind10-guide.xml @@ -35,16 +35,16 @@ BIND 10 is a Domain Name System (DNS) suite managed by - Internet Systems Consortium (ISC). It includes DNS libraries - and modular components for controlling authoritative and - recursive DNS servers. + Internet Systems Consortium (ISC). It includes DNS libraries + and modular components for controlling authoritative and + recursive DNS servers. This is the reference guide for BIND 10 version &__VERSION__;. - The most up-to-date version of this document (in PDF, HTML, - and plain text formats), along with other documents for - BIND 10, can be found at . - + The most up-to-date version of this document (in PDF, HTML, + and plain text formats), along with other documents for + BIND 10, can be found at . + This is the reference guide for BIND 10 version &__VERSION__;. @@ -98,20 +98,20 @@ - BIND 10 uses the Botan crypto library for C++. It requires - at least Botan version 1.8. + BIND 10 uses the Botan crypto library for C++. It requires + at least Botan version 1.8. - BIND 10 uses the log4cplus C++ logging library. It requires - at least log4cplus version 1.0.3. + BIND 10 uses the log4cplus C++ logging library. It requires + at least log4cplus version 1.0.3. - The authoritative server requires SQLite 3.3.9 or newer. - The b10-xfrin, b10-xfrout, - and b10-zonemgr modules require the - libpython3 library and the Python _sqlite3.so module. + The authoritative server requires SQLite 3.3.9 or newer. + The b10-xfrin, b10-xfrout, + and b10-zonemgr modules require the + libpython3 library and the Python _sqlite3.so module. @@ -133,19 +133,19 @@ BIND 10 is modular. Part of this modularity is accomplished using multiple cooperating processes which, together, - provide the server functionality. This is a change from - the previous generation of BIND software, which used a - single process. + provide the server functionality. This is a change from + the previous generation of BIND software, which used a + single process. - At first, running many different processes may seem confusing. - However, these processes are started, stopped, and maintained - by a single command, bind10. - This command starts a master process which will start other - processes as needed. - The processes started by the bind10 - command have names starting with "b10-", including: + At first, running many different processes may seem confusing. + However, these processes are started, stopped, and maintained + by a single command, bind10. + This command starts a master process which will start other + processes as needed. + The processes started by the bind10 + command have names starting with "b10-", including: @@ -215,9 +215,9 @@ b10-xfrout — Outgoing zone transfer service. - This process is used to handle transfer requests to - send a local zone to a remote secondary server, - when acting as a master server. + This process is used to handle transfer requests to + send a local zone to a remote secondary server, + when acting as a master server. @@ -225,7 +225,7 @@ b10-zonemgr — Secondary manager. - This process keeps track of timers and other + This process keeps track of timers and other necessary information for BIND 10 to act as a slave server. @@ -234,8 +234,8 @@ - These are ran automatically by bind10 - and do not need to be run manually. + These are ran automatically by bind10 + and do not need to be run manually. @@ -244,8 +244,8 @@ Managing BIND 10 - Once BIND 10 is running, a few commands are used to interact - directly with the system: + Once BIND 10 is running, a few commands are used to interact + directly with the system: @@ -342,8 +342,8 @@ var/ - To build BIND 10, also install the Botan (at least version - 1.8) and the log4cplus (at least version 1.0.3) + To build BIND 10, also install the Botan (at least version + 1.8) and the log4cplus (at least version 1.0.3) development include headers. @@ -355,7 +355,7 @@ Debian and Ubuntu: - The Python Library and Python _sqlite3 module are required to + The Python Library and Python _sqlite3 module are required to enable the Xfrout and Xfrin support. @@ -818,20 +818,20 @@ Debian and Ubuntu: - The kind specifies how a failure of the component should - be handled. If it is set to dispensable - (the default unless you set something else), it will get - started again if it fails. If it is set to needed - and it fails at startup, the whole bind10 - shuts down and exits with error exit code. But if it fails - some time later, it is just started again. If you set it - to core, you indicate that the system is - not usable without the component and if such component - fails, the system shuts down no matter when the failure - happened. This is the behaviour of the core components - (the ones you can't turn off), but you can declare any - other components as core as well if you wish (but you can - turn these off, they just can't fail). + The kind specifies how a failure of the component should + be handled. If it is set to dispensable + (the default unless you set something else), it will get + started again if it fails. If it is set to needed + and it fails at startup, the whole bind10 + shuts down and exits with error exit code. But if it fails + some time later, it is just started again. If you set it + to core, you indicate that the system is + not usable without the component and if such component + fails, the system shuts down no matter when the failure + happened. This is the behaviour of the core components + (the ones you can't turn off), but you can declare any + other components as core as well if you wish (but you can + turn these off, they just can't fail). @@ -842,13 +842,13 @@ Debian and Ubuntu: There are other parameters we didn't use in our example. - One of them is address. It is the address - used by the component on the b10-msgq - message bus. The special components already know their - address, but the usual ones don't. The address is by - convention the thing after b10-, with - the first letter capital (eg. b10-stats - would have Stats as its address). + One of them is address. It is the address + used by the component on the b10-msgq + message bus. The special components already know their + address, but the usual ones don't. The address is by + convention the thing after b10-, with + the first letter capital (eg. b10-stats + would have Stats as its address). @@ -877,15 +877,15 @@ address, but the usual ones don't." mean? --> - The configuration is quite powerful, but that includes - a lot of space for mistakes. You could turn off the - b10-cmdctl, but then you couldn't - change it back the usual way, as it would require it to - be running (you would have to find and edit the configuration - directly). Also, some modules might have dependencies - -- b10-stats-httpd need - b10-stats, b10-xfrout - needs the b10-auth to be running, etc. + The configuration is quite powerful, but that includes + a lot of space for mistakes. You could turn off the + b10-cmdctl, but then you couldn't + change it back the usual way, as it would require it to + be running (you would have to find and edit the configuration + directly). Also, some modules might have dependencies + -- b10-stats-httpd need + b10-stats, b10-xfrout + needs the b10-auth to be running, etc. @@ -896,19 +896,19 @@ address, but the usual ones don't." mean? --> - Now, to the mysterious setuid virtual component. If you - use the -u option to start the - bind10 as root, but change the user - later, we need to start the b10-auth or - b10-resolver as root (until the socket - creator is finished). So we need to specify - the time when the switch from root do the given user happens - and that's what the setuid component is for. The switch is - done at the time the setuid component would be started, if - it was a process. The default configuration contains the - setuid component with priority 5, b10-auth - has 10 to be started before the switch and everything else - is without priority, so it is started after the switch. + Now, to the mysterious setuid virtual component. If you + use the -u option to start the + bind10 as root, but change the user + later, we need to start the b10-auth or + b10-resolver as root (until the socket + creator is finished). So we need to specify + the time when the switch from root do the given user happens + and that's what the setuid component is for. The switch is + done at the time the setuid component would be started, if + it was a process. The default configuration contains the + setuid component with priority 5, b10-auth + has 10 to be started before the switch and everything else + is without priority, so it is started after the switch. @@ -1441,16 +1441,16 @@ TODO
Configuration for Incoming Zone Transfers - In practice, you need to specify a list of secondary zones to - enable incoming zone transfers for these zones (you can still - trigger a zone transfer manually, without a prior configuration - (see below)). + In practice, you need to specify a list of secondary zones to + enable incoming zone transfers for these zones (you can still + trigger a zone transfer manually, without a prior configuration + (see below)). - For example, to enable zone transfers for a zone named "example.com" - (whose master address is assumed to be 2001:db8::53 here), - run the following at the bindctl prompt: + For example, to enable zone transfers for a zone named "example.com" + (whose master address is assumed to be 2001:db8::53 here), + run the following at the bindctl prompt: > config add Xfrin/zones > config set Xfrin/zones[0]/name "" @@ -1549,11 +1549,11 @@ what if a NOTIFY is sent? Trigger an Incoming Zone Transfer Manually - To manually trigger a zone transfer to retrieve a remote zone, - you may use the bindctl utility. - For example, at the bindctl prompt run: + To manually trigger a zone transfer to retrieve a remote zone, + you may use the bindctl utility. + For example, at the bindctl prompt run: - > Xfrin retransfer zone_name="" master= + > Xfrin retransfer zone_name="" master=
@@ -1603,9 +1603,9 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default) > config commit - In the above example the lines - for were divided for - readability. In the actual input it must be in a single line. + In the above example the lines + for were divided for + readability. In the actual input it must be in a single line. @@ -1630,10 +1630,10 @@ Xfrout/transfer_acl[0] {"action": "ACCEPT"} any (default) - In a future version, b10-xfrout will also - use the system wide TSIG configuration. - The way to specify zone specific configuration (ACLs, etc) is - likely to be changed, too. + In a future version, b10-xfrout will also + use the system wide TSIG configuration. + The way to specify zone specific configuration (ACLs, etc) is + likely to be changed, too. - For example to allow the 192.168.1.0/24 - network to use your recursive name server, at the - bindctl prompt run: + For example to allow the 192.168.1.0/24 + network to use your recursive name server, at the + bindctl prompt run: @@ -1806,6 +1806,164 @@ then change those defaults with config set Resolver/forward_addresses[0]/address + + DHCPv4 Server + Dynamic Host Configuration Protocol for IPv4 (DHCP or + DHCPv4) and Dynamic Host Configuration Protocol for IPv6 (DHCPv6) + are protocols that allow one node (server) to provision + configuration parameters to many hosts and devices (clients). To + ease deployment in larger networks, additional nodes (relays) may + be deployed that facilitate communication between servers and + clients. Even though principles of both DHCPv4 and DHCPv6 are + somewhat similar, these are two radically different + protocols. BIND10 offers server implementations for both DHCPv4 + and DHCPv6. + + + + As of December 2011, both DHCPv4 and DHCPv6 components are + skeleton servers. That means that while they are capable of + performing DHCP configuration, they are not fully functional + yet. In particular, both do not have functional lease + databases. This means that they will assign the same, fixed, + hardcoded addresses to any client that will ask. See and for + detailed description. + + + +
+ Server Usage + BIND10 provides experimental DHCPv4 server component since + December 2011. It is currently described as skeleton server and + can be described as an early prototype that is not yet fully + functional. It is mature enough to conduct first tests in lab + environment, but it has significant limitations. See for details. + + + + DHCPv4 server is implemented as b10-dhcp4 + daemon. As it is configurable yet, it is fully autonomous, + i.e. it does not interact with b10-cfgmgr. + To start DHCPv4 server, simply input: + + +#cd src/bin/dhcp4 +#./b10-dhcp4 + + + Depending on your installation, b10-dhcp4 + binary may reside in src/bin/dhcp4 in your source code + directory, in /usr/local/bin/b10-dhcp4 or other directory + you specified during compilation. + + Afre start, server will detect available network interfaces + and will attempt to open UDP sockets on all interfaces that + are up, running, are not loopback and have IPv4 address + assigned. + + Server will then listen to incoming traffic. Currently + supported client messages are DISCOVER and REQUEST. Server + will respond to them with OFFER and ACK, respectively. + + As DHCPv4 server opens privileged ports, it requires root + access. Make sure you run this daemon as root. + +
+ +
+ Server Configuration + + DHCPv4 server does not have lease database implemented yet + or any support for configuration, so every time the same set + of configuration options (including the same fixed address) + will be assigned every time. + + + At this stage of development, the only way to alter server + configuration is to tweak its source code. To do so, please edit + src/bin/dhcp4/dhcp4_srv.cc file and modify following parameters: + +const std::string HARDCODED_LEASE = "10.3.2.222"; // assigned lease +const std::string HARDCODED_NETMASK = "255.255.255.0"; +const uint32_t HARDCODED_LEASE_TIME = 60; // in seconds +const std::string HARDCODED_GATEWAY = "10.3.2.2"; +const std::string HARDCODED_DNS_SERVER = "8.8.8.8"; +const std::string HARDCODED_DOMAIN_NAME = "isc.example.org"; +const std::string HARDCODED_SERVER_ID = "10.3.1.1"; + + Lease database and configuration support is planned for 2012. + +
+ +
+ DHCPv4 Server Limitations + + During initial IPv4 node configuration, where server has to + send packet to a node that does not have IPv4 address + assigned yet, server requires certain tricks (or hacks) to + transmit such packets. This is not implemented yet, therefore + DHCPv4 server supports relayed traffic only. + +
+ + + + DHCPv6 Server +
+ DHCPv6 Server Limitations + + Relayed traffic is not supported. + +
+ + + + + + libdhcp++ library + libdhcp++ is a common library written in C++ that is + handles many DHCP-related tasks, like DHCPv4 and DHCPv6 packets + parsing, manipulation and assembly, option parsing, manipulation + and assembly, network interface detection and socket operations. + + + + While this library is currently used by + b10-dhcp6 and b10-dhcp4 + only, it is designed to be portable, universal library useful + for any kind of DHCP-related software. + + +
+ Interface detection + Both DHCPv4 and DHCPv6 components share network + interface detection routines (see for details). Interface detection is + currently only supported on Linux systems. + + For non-linux systems, there is currently stub + implementation provided. As DHCP servers need to know + available addresses, there was a simple mechanism implemented + to provide that information. User is expected to create + interfaces.txt file. Format of this file is simple. It + contains list of interfaces along with available address on + each interface. This mechanism is temporary and is going to be + removed as soon as interface detection becomes available on + non-linux systems. Example of interfaces.txt file looks as follows: + +# For DHCPv6, please specify link-local address (starts with fe80::) +# If in doubt, check output of 'ifconfig -a' command. +eth0 fe80::21e:8cff:fe9b:7349 + +# For DHCPv4, please use following format: +#eth0 192.0.2.5 + +
+ + + Statistics @@ -1857,10 +2015,10 @@ then change those defaults with config set Resolver/forward_addresses[0]/address - The logging system in BIND 10 is configured through the - Logging module. All BIND 10 modules will look at the - configuration in Logging to see what should be logged and - to where. + The logging system in BIND 10 is configured through the + Logging module. All BIND 10 modules will look at the + configuration in Logging to see what should be logged and + to where. @@ -1871,28 +2029,28 @@ then change those defaults with config set Resolver/forward_addresses[0]/address - Within BIND 10, a message is logged through a component - called a "logger". Different parts of BIND 10 log messages - through different loggers, and each logger can be configured - independently of one another. + Within BIND 10, a message is logged through a component + called a "logger". Different parts of BIND 10 log messages + through different loggers, and each logger can be configured + independently of one another. - In the Logging module, you can specify the configuration - for zero or more loggers; any that are not specified will - take appropriate default values.. + In the Logging module, you can specify the configuration + for zero or more loggers; any that are not specified will + take appropriate default values.. - The three most important elements of a logger configuration - are the (the component that is - generating the messages), the - (what to log), and the - (where to log). + The three most important elements of a logger configuration + are the (the component that is + generating the messages), the + (what to log), and the + (where to log). @@ -1900,12 +2058,12 @@ then change those defaults with config set Resolver/forward_addresses[0]/address name (string) - Each logger in the system has a name, the name being that - of the component using it to log messages. For instance, - if you want to configure logging for the resolver module, - you add an entry for a logger named Resolver. This - configuration will then be used by the loggers in the - Resolver module, and all the libraries used by it. + Each logger in the system has a name, the name being that + of the component using it to log messages. For instance, + if you want to configure logging for the resolver module, + you add an entry for a logger named Resolver. This + configuration will then be used by the loggers in the + Resolver module, and all the libraries used by it. - To illustrate this, suppose you want the cache library - to log messages of severity DEBUG, and the rest of the - resolver code to log messages of severity INFO. To achieve - this you specify two loggers, one with the name - Resolver and severity INFO, and one with - the name Resolver.cache with severity - DEBUG. As there are no entries for other libraries (e.g. - the nsas), they will use the configuration for the module - (Resolver), so giving the desired behavior. + To illustrate this, suppose you want the cache library + to log messages of severity DEBUG, and the rest of the + resolver code to log messages of severity INFO. To achieve + this you specify two loggers, one with the name + Resolver and severity INFO, and one with + the name Resolver.cache with severity + DEBUG. As there are no entries for other libraries (e.g. + the nsas), they will use the configuration for the module + (Resolver), so giving the desired behavior. - One special case is that of a module name of * - (asterisks), which is interpreted as any - module. You can set global logging options by using this, - including setting the logging configuration for a library - that is used by multiple modules (e.g. *.config - specifies the configuration library code in whatever - module is using it). + One special case is that of a module name of * + (asterisks), which is interpreted as any + module. You can set global logging options by using this, + including setting the logging configuration for a library + that is used by multiple modules (e.g. *.config + specifies the configuration library code in whatever + module is using it). - If there are multiple logger specifications in the - configuration that might match a particular logger, the - specification with the more specific logger name takes - precedence. For example, if there are entries for for - both * and Resolver, the - resolver module — and all libraries it uses — - will log messages according to the configuration in the - second entry (Resolver). All other modules - will use the configuration of the first entry - (*). If there was also a configuration - entry for Resolver.cache, the cache library - within the resolver would use that in preference to the - entry for Resolver. + If there are multiple logger specifications in the + configuration that might match a particular logger, the + specification with the more specific logger name takes + precedence. For example, if there are entries for for + both * and Resolver, the + resolver module — and all libraries it uses — + will log messages according to the configuration in the + second entry (Resolver). All other modules + will use the configuration of the first entry + (*). If there was also a configuration + entry for Resolver.cache, the cache library + within the resolver would use that in preference to the + entry for Resolver. - One final note about the naming. When specifying the - module name within a logger, use the name of the module - as specified in bindctl, e.g. - Resolver for the resolver module, - Xfrout for the xfrout module, etc. When - the message is logged, the message will include the name - of the logger generating the message, but with the module - name replaced by the name of the process implementing - the module (so for example, a message generated by the - Auth.cache logger will appear in the output - with a logger name of b10-auth.cache). + One final note about the naming. When specifying the + module name within a logger, use the name of the module + as specified in bindctl, e.g. + Resolver for the resolver module, + Xfrout for the xfrout module, etc. When + the message is logged, the message will include the name + of the logger generating the message, but with the module + name replaced by the name of the process implementing + the module (so for example, a message generated by the + Auth.cache logger will appear in the output + with a logger name of b10-auth.cache). @@ -2004,9 +2162,9 @@ specify module-wide logging and see what appears... This specifies the category of messages logged. - Each message is logged with an associated severity which - may be one of the following (in descending order of - severity): + Each message is logged with an associated severity which + may be one of the following (in descending order of + severity): @@ -2033,11 +2191,11 @@ specify module-wide logging and see what appears... - When the severity of a logger is set to one of these - values, it will only log messages of that severity, and - the severities above it. The severity may also be set to - NONE, in which case all messages from that logger are - inhibited. + When the severity of a logger is set to one of these + values, it will only log messages of that severity, and + the severities above it. The severity may also be set to + NONE, in which case all messages from that logger are + inhibited. @@ -2050,9 +2208,9 @@ specify module-wide logging and see what appears... - Each logger can have zero or more - . These specify where log - messages are sent to. These are explained in detail below. + Each logger can have zero or more + . These specify where log + messages are sent to. These are explained in detail below. @@ -2069,15 +2227,15 @@ specify module-wide logging and see what appears... - When a logger's severity is set to DEBUG, this value - specifies what debug messages should be printed. It ranges - from 0 (least verbose) to 99 (most verbose). + When a logger's severity is set to DEBUG, this value + specifies what debug messages should be printed. It ranges + from 0 (least verbose) to 99 (most verbose). @@ -2119,10 +2277,10 @@ TODO; there's a ticket to determine these levels, see #1074 - The main settings for an output option are the - and a value called - , the meaning of which depends on - the destination that is set. + The main settings for an output option are the + and a value called + , the meaning of which depends on + the destination that is set. @@ -2158,8 +2316,8 @@ TODO; there's a ticket to determine these levels, see #1074 - Depending on what is set as the output destination, this - value is interpreted as follows: + Depending on what is set as the output destination, this + value is interpreted as follows: @@ -2169,10 +2327,10 @@ TODO; there's a ticket to determine these levels, see #1074 is console - The value of output must be one of stdout - (messages printed to standard output) or - stderr (messages printed to standard - error). + The value of output must be one of stdout + (messages printed to standard output) or + stderr (messages printed to standard + error). @@ -2181,8 +2339,8 @@ TODO; there's a ticket to determine these levels, see #1074 is file - The value of output is interpreted as a file name; - log messages will be appended to this file. + The value of output is interpreted as a file name; + log messages will be appended to this file. @@ -2191,10 +2349,10 @@ TODO; there's a ticket to determine these levels, see #1074 is syslog - The value of output is interpreted as the - syslog facility (e.g. - local0) that should be used - for log messages. + The value of output is interpreted as the + syslog facility (e.g. + local0) that should be used + for log messages. @@ -2211,10 +2369,10 @@ TODO; there's a ticket to determine these levels, see #1074 flush (true of false) - Flush buffers after each log message. Doing this will - reduce performance but will ensure that if the program - terminates abnormally, all messages up to the point of - termination are output. + Flush buffers after each log message. Doing this will + reduce performance but will ensure that if the program + terminates abnormally, all messages up to the point of + termination are output. @@ -2223,11 +2381,11 @@ TODO; there's a ticket to determine these levels, see #1074 maxsize (integer) - Only relevant when destination is file, this is maximum - file size of output files in bytes. When the maximum - size is reached, the file is renamed and a new file opened. - (For example, a ".1" is appended to the name — - if a ".1" file exists, it is renamed ".2", + Only relevant when destination is file, this is maximum + file size of output files in bytes. When the maximum + size is reached, the file is renamed and a new file opened. + (For example, a ".1" is appended to the name — + if a ".1" file exists, it is renamed ".2", etc.) @@ -2241,9 +2399,9 @@ TODO; there's a ticket to determine these levels, see #1074 maxver (integer) - Maximum number of old log files to keep around when - rolling the output file. Only relevant when - is file. + Maximum number of old log files to keep around when + rolling the output file. Only relevant when + is file. @@ -2257,11 +2415,11 @@ TODO; there's a ticket to determine these levels, see #1074 - In this example we want to set the global logging to - write to the file /var/log/my_bind10.log, - at severity WARN. We want the authoritative server to - log at DEBUG with debuglevel 40, to a different file - (/tmp/debug_messages). + In this example we want to set the global logging to + write to the file /var/log/my_bind10.log, + at severity WARN. We want the authoritative server to + log at DEBUG with debuglevel 40, to a different file + (/tmp/debug_messages). @@ -2282,9 +2440,9 @@ Logging/loggers [] list - By default, no specific loggers are configured, in which - case the severity defaults to INFO and the output is - written to stderr. + By default, no specific loggers are configured, in which + case the severity defaults to INFO and the output is + written to stderr. @@ -2306,8 +2464,8 @@ Logging/loggers/ list (modified) - The loggers value line changed to indicate that it is no - longer an empty list: + The loggers value line changed to indicate that it is no + longer an empty list: @@ -2325,9 +2483,9 @@ Logging/loggers[0]/output_options [] list (default) - The name is mandatory, so we must set it. We will also - change the severity as well. Let's start with the global - logger. + The name is mandatory, so we must set it. We will also + change the severity as well. Let's start with the global + logger. @@ -2347,8 +2505,8 @@ Logging/loggers[0]/output_options [] list (default) - Of course, we need to specify where we want the log - messages to go, so we add an entry for an output option. + Of course, we need to specify where we want the log + messages to go, so we add an entry for an output option. @@ -2384,8 +2542,8 @@ Logging/loggers[0]/output_options[0]/maxver 0 integer (default) - Which would make the entire configuration for this logger - look like: + Which would make the entire configuration for this logger + look like: @@ -2407,8 +2565,8 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified) - That looks OK, so let's commit it before we add the - configuration for the authoritative server's logger. + That looks OK, so let's commit it before we add the + configuration for the authoritative server's logger. @@ -2420,8 +2578,8 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified) - Now that we have set it, and checked each value along - the way, adding a second entry is quite similar. + Now that we have set it, and checked each value along + the way, adding a second entry is quite similar. @@ -2441,10 +2599,10 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified) - And that's it. Once we have found whatever it was we - needed the debug messages for, we can simply remove the - second logger to let the authoritative server use the - same settings as the rest. + And that's it. Once we have found whatever it was we + needed the debug messages for, we can simply remove the + second logger to let the authoritative server use the + same settings as the rest. @@ -2458,8 +2616,8 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified) - And every module will now be using the values from the - logger named *. + And every module will now be using the values from the + logger named *. @@ -2471,11 +2629,11 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified) Logging Message Format - 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. + 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. @@ -2525,29 +2683,29 @@ Logging/loggers[0]/output_options[0]/maxver 8 integer (modified) ASIODNS_OPENSOCK - 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 () from which more information can be obtained. + 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 () from which more information can be obtained. error 111 opening TCP socket to 127.0.0.1(53) - 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. + 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.