From 9349d49b7f41b2441931fe3f4ea3136ac338e3a2 Mon Sep 17 00:00:00 2001 From: Andreas Gustafsson Date: Thu, 19 Oct 2000 17:22:53 +0000 Subject: [PATCH] minor spacing and font fixes --- doc/arm/Bv9ARM-book.xml | 52 ++++++++++++++++++++--------------------- 1 file changed, 26 insertions(+), 26 deletions(-) diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index f63f38bf11..3c9df373ca 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + @@ -140,7 +140,7 @@ called named and a resolver library. The BIND server runs in the background, servicing queries on a well known network port. The standard port for the User Datagram Protocol (UDP) and Transmission Control Protocol (TCP), usually port 53, -is specified in /etc/services. +is specified in /etc/services. The resolver is a set of routines residing in a system library that provides the interface that programs can use to access the domain name services. @@ -1131,7 +1131,7 @@ sign non-response messages to host1. TSIG Key Based Access Control BIND allows IP addresses and ranges to be specified in ACL definitions and -allow-{ query | transfer | update } directives. +allow-{ query | transfer | update } directives. This has been extended to allow TSIG keys also. The above key would be denoted key host1-host2. An example of an allow-update directive would be: @@ -1644,7 +1644,7 @@ defined by the acl statement. address_match_list -A list of one or more ip_addr, ip_prefix, key_id, or acl_name elements, see +A list of one or more ip_addr, ip_prefix, key_id, or acl_name elements, see . @@ -1668,7 +1668,7 @@ in dotted_decimal notation. ip_addr -An ip4_addr or ip6_addr. +An ip4_addr or ip6_addr. ip_port @@ -1717,7 +1717,7 @@ value of size_spec is that of unsigned long integers on the machine. An unlimited size_spec requests unlimited use, or the maximum available amount. A default size_spec uses the limit that was in force when the server was started.A number can -optionally be followed by a scaling factor: K or k for +optionally be followed by a scaling factor: K or k for kilobytes, M or m for megabytes, and G or g for gigabytes, which scale by 1024, 1024*1024, and 1024*1024*1024 respectively.Integer @@ -2542,7 +2542,7 @@ happens in a short interval, once every heartbeat-interval an hopefully during the one call. It also suppresses some of the normal zone maintenance traffic. The default is no.The dialup option may also be specified in the zone statement, -in which case it overrides the options dialup statement.If +in which case it overrides the options dialup statement.If the zone is a master then the server will send out a NOTIFY request to all the slaves. This will trigger the zone serial number check in the slave (providing it supports NOTIFY) allowing the slave to @@ -2564,8 +2564,8 @@ the obsolete DNS query type IQUERY. BIND 9 never does IQUERY nodes in the zone is called glue information). If yes (the default), the server will fetch glue resource records it doesn't have when constructing the additional -data section of a response. fetch-glue no can -be used in conjunction with recursion no to +data section of a response. fetch-glue no can +be used in conjunction with recursion no to prevent the server's cache from growing or becoming corrupted (at the cost of requiring more work from the client). Not yet @@ -2576,8 +2576,8 @@ implemented in BIND 9. This option was incorrectly implemented in BIND 8, and is ignored by BIND 9. To achieve the intended effect of -has-old-clients yes, specify -the two separate options auth-nxdomain yes and rfc2308-type1 no instead. +has-old-clients yes, specify +the two separate options auth-nxdomain yes and rfc2308-type1 no instead. host-statistics @@ -2594,7 +2594,7 @@ huge amounts of memory. It was used in BIND 8 to determine whether a transaction log was kept for Incremental Zone Transfer. BIND 9 maintains a transaction log whenever possible. If you need to disable outgoing incremental zone -transfers, use provide-ixfr no. +transfers, use provide-ixfr no. multiple-cnames @@ -2839,7 +2839,7 @@ listen-on-v6 port 1234 { any; }; To make the server not listen on any IPv6 address, use listen-on-v6 { none; }; -If no listen-on-v6 statement is specified, +If no listen-on-v6 statement is specified, the server will not listen on any IPv6 address. Query Address If the server doesn't know the answer to a question, it will @@ -2910,7 +2910,7 @@ servers to find out if zone serial numbers have changed. Each such query uses a minute amount of the slave server's network bandwidth, but more importantly each query uses a small amount of memory in the slave server while waiting for the master server to respond. -The serial-queries option sets the maximum number +The serial-queries option sets the maximum number of concurrent serial-number queries allowed to be outstanding at any given time. The default is 4. @@ -3034,7 +3034,7 @@ kernel can support. On such systems, choosing cause the server to use the larger of the rlim_max for RLIMIT_NOFILE and the value returned by sysconf(_SC_OPEN_MAX). If the actual kernel limit is larger than this value, use limit -files to specify the limit explicitly.Not yet +files to specify the limit explicitly.Not yet implemented in BIND 9. @@ -3147,7 +3147,7 @@ records, or RRset, you must use the sortlist. Specifications for RRs are documented in RFC 1035. When returning multiple RRs the nameserver will normally return -them in Round Robin order, +them in Round Robin order, that is, after each request the first RR is put at the end of the list. The client resolver code should rearrange the RRs as appropriate, that is, using any addresses on the local net in preference to other addresses. @@ -3156,7 +3156,7 @@ When a client is using a local server the sorting can be performed in the server, based on the client's address. This only requires configuring the nameservers, not all the clients. The sortlist statement (see below) takes -an address_match_list and interprets it even +an address_match_list and interprets it even more specifically than the topology statement does (). Each top level statement in the sortlist must itself be an explicit address_match_list with @@ -3369,7 +3369,7 @@ zone transfer when the given remote server, a slave, requests it. If set to yes, incremental transfer will be provided whenever possible. If set to no, all transfers to the remote server will be nonincremental. If not set, the value -of the provide-ixfr option in the global options block +of the provide-ixfr option in the global options block is used as a default. The request-ixfr clause determines whether the local server, acting as a slave, will request incremental zone @@ -3388,14 +3388,14 @@ uses one DNS message per resource record transferred. many-answersmany-answers is more efficient, but is only known to be understood by BIND 9, BIND 8.x, and patched versions of BIND 4.9.5. You can specify which method -to use for a server with the transfer-format option. -If transfer-format is not specified, the transfer-format specified +to use for a server with the transfer-format option. +If transfer-format is not specified, the transfer-format specified by the options statement will be used. transfers is used to limit the number of concurrent inbound zone transfers from the specified server. If no transfers clause is specified, the limit is set according to the transfers-per-ns option. -The keys clause is used to identify a key_id defined +The keys clause is used to identify a key_id defined by the key statement, to be used for transaction security when talking to the remote server. The key statement must come before the server statement that references @@ -3442,7 +3442,7 @@ split DNS setups without having to run multiple servers. DNS namespace that will be seen by those clients whose IP addresses match the address_match_list of the view's match-clients clause. The order of the view statements is significant-a -client query will be resolved in the context of the first view whose match-clients list +client query will be resolved in the context of the first view whose match-clients list matches the client's IP address. Zones defined within a view statement will be only be accessible to clients that match the view. @@ -4312,9 +4312,9 @@ and $TTL. The <command>$ORIGIN</command> Directive Syntax: $ORIGIN domain-name comment -$ORIGIN sets the domain name that will +$ORIGIN sets the domain name that will be appended to any unqualified records. When a zone is first read -in there is an implicit $ORIGIN <zone-name>. The +in there is an implicit $ORIGIN <zone-name>. The current $ORIGIN is appended to the domain specified in the $ORIGIN argument if it is not absolute. $ORIGIN example.com @@ -4345,7 +4345,7 @@ with undefined TTLs. Valid TTLs are of the range 0-2147483647 seconds. <acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive Syntax: $GENERATE range hs type rhs comment $GENERATE is used to create a series of -resource records that only differ from each other by an iterator. $GENERATE can +resource records that only differ from each other by an iterator. $GENERATE can be used to easily generate the sets of records required to support sub /24 reverse delegations described in RFC 2317: Classless IN-ADDR.ARPA delegation. @@ -4378,7 +4378,7 @@ owner name of the resource records to be created. Any single $lhs side are replaced by the iterator value. To get a $ in the output use a double $, e.g. $$. If the lhs is not -absolute, the current $ORIGIN is appended to +absolute, the current $ORIGIN is appended to the name.