From 5f09ce124cad9712a9675f17f83ddc915e734909 Mon Sep 17 00:00:00 2001 From: Andreas Gustafsson Date: Fri, 3 Nov 2000 18:24:53 +0000 Subject: [PATCH] regenerated HTML --- doc/arm/Bv9ARM.ch01.html | 21 +- doc/arm/Bv9ARM.ch02.html | 20 +- doc/arm/Bv9ARM.ch03.html | 18 +- doc/arm/Bv9ARM.ch04.html | 60 +++--- doc/arm/Bv9ARM.ch05.html | 8 +- doc/arm/Bv9ARM.ch06.html | 436 +++++++++++++++++++++++---------------- doc/arm/Bv9ARM.ch07.html | 12 +- doc/arm/Bv9ARM.ch08.html | 14 +- doc/arm/Bv9ARM.ch09.html | 116 +++++------ doc/arm/Bv9ARM.html | 142 ++++++------- 10 files changed, 462 insertions(+), 385 deletions(-) diff --git a/doc/arm/Bv9ARM.ch01.html b/doc/arm/Bv9ARM.ch01.html index 5a1391480e..61850297d6 100644 --- a/doc/arm/Bv9ARM.ch01.html +++ b/doc/arm/Bv9ARM.ch01.html @@ -546,10 +546,7 @@ CLASS="acronym" > 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. @@ -564,7 +561,7 @@ CLASS="sect2" >

1.4.1. Nameservers

1.4.2. Types of Zones

1.4.3. Servers

1.4.3.1. Master Server

1.4.3.2. Slave Server

1.4.3.3. Caching Only Server

1.4.3.4. Forwarding Server

1.4.3.5. Stealth Server

2.1. Hardware requirements
2.2. CPU Requirements
2.3. Memory Requirements
2.4. Nameserver Intensive Environment Issues
2.5. Supported Operating Systems

2.1. Hardware requirements

2.2. CPU Requirements

2.3. Memory Requirements

2.4. Nameserver Intensive Environment Issues

2.5. Supported Operating Systems

3.2. Load Balancing
3.4. Nameserver Operations

3.1.1. A Caching-only Nameserver

3.1.2. An Authoritative-only Nameserver

3.2. Load Balancing

3.4. Nameserver Operations

3.4.1. Tools for Use With the Nameserver Daemon

3.4.1.1. Diagnostic Tools

3.4.2. Signals

4.3. Split DNS
4.5. TKEY
4.6. SIG(0)
4.8. IPv6 Support in BIND

4.3. Split DNS

4.4.1. Generate Shared Keys for Each Pair of Hosts

4.4.1.1. Automatic Generation

4.4.1.2. Manual Generation

4.4.2. Copying the Shared Secret to Both Machines

4.4.3. Informing the Servers of the Key's Existence

4.4.4. Instructing the Server to Use the Key

4.4.5. TSIG Key Based Access Control

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

4.4.6. Errors

4.5. TKEY

4.6. SIG(0)

4.7.1. Generating Keys

4.7.2. Creating a Keyset

4.7.3. Signing the Child's Keyset

4.7.4. Signing the Zone

4.7.5. Configuring Servers

4.8. IPv6 Support in BIND

4.8.1. Address Lookups Using AAAA Records

4.8.2. Address Lookups Using A6 Records

4.8.2.1. A6 Chains

4.8.2.2. A6 Records for DNS Servers

4.8.3. Address to Name Lookups Using Nibble Format

4.8.4. Address to Name Lookups Using Bitstring Format

4.8.5. Using DNAME for Delegation of IPv6 Reverse Addresses

5.1. The Lightweight Resolver Library
5.2. Running a Resolver Daemon

5.1. The Lightweight Resolver Library

5.2. Running a Resolver Daemon

6.3. Zone File
A list of one or more ip_addr, , ip_prefix, , key_id, or , or acl_name elements, see @@ -332,10 +323,7 @@ VALIGN="MIDDLE" >An ip4_addr or or ip6_addr.

k for +> for kilobytes, .

dialup_option

One of yes, +no, notify, +notify-passive, refresh or +passive. +When used in a zone, notify-passive, +refresh, and passive +are restricted to slave and stub zones.

6.1.1.1. Syntax

6.1.1.2. Definition and Usage
6.1.2. Comment Syntax
6.1.2.1. Syntax
6.1.2.2. Definition and Usage
6.2.1. acl
6.2.3. controls
6.2.4. controls
6.2.5. include
6.2.6. include
6.2.7. key
6.2.8. key
6.2.9. logging
6.2.10. logging
6.2.10.1. The channel
6.2.11. options dialup yes_or_nodialup_option; ]
@@ -3014,7 +3069,15 @@ CLASS="replaceable"
 >ip4_addr;  [port ip_port] ; ]
     [ip6_addr;  [port ip_port] ; ]
     [
6.2.12. optionsno.

+
The dialup option
 may also be specified in the zone statement,
-in which case it overrides the view and 
+options dialup statement.
zone statements,
+in which case it overrides the global dialup
+option.
If
-the zone is a master then the server will send out a NOTIFY request
+the zone is a master zone 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
 verify the zone while the connection is active.
If the
-zone is a slave or stub then the server will suppress the regular
-"zone up to date" queries and only perform them when the
+zone is a slave or stub zone, then the server will suppress the regular
+"zone up to date" (refresh) queries and only perform them when the
 heartbeat-interval expires.
 expires in addition to sending
+NOTIFY requests.
Finer control can be achieved by using
+Note: Not yet implemented
-in BIND 9.
notify which only sends NOTIFY messages,
+notify-passive which sends NOTIFY messages and
+suppresses the normal refresh queries, refresh
+which suppresses normal refresh processing and send refresh queries 
+when the heartbeat-interval expires and
+passive which just disables normal refresh
+processing.

+fetch-glue fetch-glue no can
+> can
 be used in conjunction with recursion recursion no to
+> to
 prevent the server's cache from growing or becoming corrupted (at
 the cost of requiring more work from the client).
has-old-clients has-old-clients yes, specify
 the two separate options auth-nxdomain auth-nxdomain yes and rfc2308-type1 rfc2308-type1 noprovide-ixfr provide-ixfr no
6.2.12.2. Forwarding
6.2.12.5. Interfaces
If no listen-on-v6 statement is specified,
+>listen-on-v6 statement is specified,
 the server will not listen on any IPv6 address.
6.2.12.6. Query Address
serial-queries option sets the maximum number
+>serial-queries option sets the maximum number
 of concurrent serial-number queries allowed to be outstanding at
 any given time. The default is 4.
transfer-source determines
 which local address will be bound to IPv4 TCP connections used to
-fetch zones transferred inbound by the server. If not set, it defaults
+fetch zones transferred inbound by the server.  It also determines
+the IPv4 address, and optionaly the UDP port, used for the refresh queries,
+notify messages and when updates are forwarded.  If not set, it defaults
 to a system controlled value which will usually be the address of
 the interface "closest to" the remote end. This address must appear
 in the remote end's 
6.2.12.8. Resource Limits
limit
-files to specify the limit explicitly.
 to specify the limit explicitly.
6.2.12.9. Periodic Task Intervals
The server will perform zone maintenance tasks
-for all zones marked  dialup yesdialup whenever this
 interval expires. The default is 60 minutes. Reasonable values are up
 to 1 day (1440 minutes). If set to 0, no zone maintenance for these zones will occur.
Note: Not yet
-implemented in BIND 9.
Round Robin order,
+> 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.
@@ -5933,8 +6009,8 @@ CLASS="command"
 > statement (see below) takes
 an address_match_list and interprets it even
+>address_match_list and interprets it even
 more specifically than the topology
6.2.12.14. Deprecated Features
provide-ixfr option in the global options block
+>provide-ixfr option in the global options block
 is used as a default.
The  4.9.5. You can specify which method
 to use for a server with the transfer-format option.
+>transfer-format option.
 If transfer-format is not specified, the transfer-format is not specified, the transfer-format specified
@@ -6709,8 +6785,8 @@ CLASS="command"
 >keys clause is used to identify a key_id defined
+>key_id defined
 by the key
6.2.15. trusted-keys
6.2.16. trusted-keys
6.2.17. view
6.2.18. viewview whose match-clients list
+>match-clients list
 matches the client's IP address.
Zones defined within a  dialup true_or_falsedialup_option ; ]
@@ -7239,7 +7315,7 @@ CLASS="optional"
 > maintain-ixfr-base true_or_falseyes_or_no ; ]
@@ -7329,7 +7405,7 @@ CLASS="optional"
 > notify true_or_falseyes_or_no ; ]
@@ -7367,7 +7443,15 @@ CLASS="replaceable"
 > | *) ; ) [port ip_port] ; ]
     [ | *) ; ) [port ip_port] ; ]
     [
6.2.20. zone
6.2.20.1. Zone Types
ex/example.com where ex/ is
+>ex/ is
 just the first two letters of the zone name. (Most operating systems
 behave very slowly if you put 100K files into a single directory.)
6.2.20.2. Class
6.2.20.3. Zone Options
 under Section 6.2.12.1.
-
Note: Not yet implemented in BIND 9.
.
Determines which local address will be bound
-to the IPv4 TCP connection used to fetch this zone. If not set,
+to the IPv4 TCP connection used to fetch this zone.  It also determines
+the IPv4 address, and optionaly the UDP port, used for the refresh queries,
+notify messages and when updates are forwarded.  If not set,
 it defaults to a system controlled value which will usually be the
 address of the interface "closest to" the remote end. If the remote
 end user is an 
6.3. Zone File
6.3.1.1. Resource Records
6.3.1.2. Textual expression of RRs
6.3.2. Discussion of MX Records
6.3.4. Inverse Mapping in IPv4
6.3.5. Other Zone File Directives
6.3.5.1. The $ORIGIN
$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 <$ORIGIN <zone-name>
6.3.5.2. The $INCLUDE
6.3.5.3. The $TTL
6.3.6. BIND is used to create a series of
 resource records that only differ from each other by an iterator. $GENERATE can
+>$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.
 is not
 absolute, the current $ORIGIN is appended to
+>$ORIGIN is appended to
 the name.
7.2. chroot
7.3. Dynamic Updates
7.2. chroot
7.2.1. The chroot
7.2.2. Using the setuid
7.3. Dynamic Updates
8.1. Common Problems
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
8.1. Common Problems
8.1.1. It's not working; how can I figure out what's wrong?
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
A.1. Acknowledgements
A.3. General DNS
A.1. Acknowledgements
A.1.1. A Brief History of the DNS
A.2.1.1. HS = hesiod
A.2.1.2. CH = chaos
A.3. General DNS
A.3.1. IPv6 addresses (A6)
.
Bibliography
Standards
[RFC974] C. Partridge, 
[RFC1034] P.V. Mockapetris, 
[RFC1035] P. V. Mockapetris, 
[RFC2181] R., R. Bush Elz, 
[RFC2308] M. Andrews, 
[RFC1995] M. Ohta, 
[RFC1996] P. Vixie, 
[RFC2136] P. Vixie, S. Thomson, Y. Rekhter, and J. Bound, 
[RFC2845] P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington, 
Proposed Standards Still Under Development
[RFC1886] S. Thomson and C. Huitema, 
[RFC2065] D. Eastlake, 3rd and C. Kaufman, 
[RFC2137] D. Eastlake, 3rd, 
Other Important RFCs About DNS
[RFC1535] E. Gavron, 
[RFC1536] A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller, 
[RFC1982] R. Elz and R. Bush, 
Resource Record Types
[RFC1183] C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris, 
[RFC1706] B. Manning and R. Colella, 
[RFC2168] R. Daniel and M. Mealling, 
[RFC1876] C. Davis, P. Vixie, T., and I. Dickinson, 
[RFC2052] A. Gulbrandsen and P. Vixie, 
[RFC2163] A. Allocchio, 
[RFC2230] R. Atkinson, 
DNS
[RFC1101] P. V. Mockapetris, 
[RFC1123] Braden, 
[RFC1591] J. Postel, 
[RFC2317] H. Eidnes, G. de Groot, and P. Vixie, 
DNS
[RFC1537] P. Beertema, 
[RFC1912] D. Barr, 
[RFC1912] D. Barr, 
[RFC2010] B. Manning and P. Vixie, 
[RFC2219] M. Hamilton and R. Wright, 
Other DNS
[RFC1464] R. Rosenbaum, 
[RFC1713] A. Romao, 
[RFC1794] T. Brisco, 
[RFC2240] O. Vaughan, 
[RFC2345] J. Klensin, T. Wolf, and G. Oglesby, 
[RFC2352] O. Vaughan, 
Obsolete and Unimplemented Experimental RRs
[RFC1712] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni, 
A.4.3. Other Documents About BIND
Bibliography
Paul Albitz and Cricket Liu, 
1.4.1. Nameservers
1.4.2. Types of Zones
1.4.3. Servers
2.1. Hardware requirements
2.2. CPU Requirements
2.3. Memory Requirements
2.4. Nameserver Intensive Environment Issues
2.5. Supported Operating Systems
3.1.1. A Caching-only Nameserver
3.1.2. An Authoritative-only Nameserver
3.2. Load Balancing
3.4. Nameserver Operations
3.4.1. Tools for Use With the Nameserver Daemon
3.4.2. Signals
4.3. Split DNS
4.4.1. Generate Shared Keys for Each Pair of Hosts
4.4.2. Copying the Shared Secret to Both Machines
4.4.3. Informing the Servers of the Key's Existence
4.4.4. Instructing the Server to Use the Key
4.4.5. TSIG Key Based Access Control
4.4.6. Errors
4.5. TKEY
4.6. SIG(0)
4.7.1. Generating Keys
4.7.2. Creating a Keyset
4.7.3. Signing the Child's Keyset
4.7.4. Signing the Zone
4.7.5. Configuring Servers
4.8. IPv6 Support in BIND
4.8.1. Address Lookups Using AAAA Records
4.8.2. Address Lookups Using A6 Records
4.8.3. Address to Name Lookups Using Nibble Format
4.8.4. Address to Name Lookups Using Bitstring Format
4.8.5. Using DNAME for Delegation of IPv6 Reverse Addresses
5.1. The Lightweight Resolver Library
5.2. Running a Resolver Daemon
6.1.2. Comment Syntax
6.2.1. acl
6.2.3. controls
6.2.4. controls
6.2.5. include
6.2.6. include
6.2.7. key
6.2.8. key
6.2.9. logging
6.2.10. logging
6.2.11. options
6.2.12. options
6.2.15. trusted-keys
6.2.16. trusted-keys
6.2.17. view
6.2.18. view
6.2.20. zone
6.3. Zone File
6.3.2. Discussion of MX Records
6.3.4. Inverse Mapping in IPv4
6.3.5. Other Zone File Directives
6.3.6. BIND
7.2. chroot
7.2.1. The chroot
7.2.2. Using the setuid
7.3. Dynamic Updates
8.1. Common Problems
8.1.1. It's not working; how can I figure out what's wrong?
8.2. Incrementing and Changing the Serial Number
8.3. Where Can I Get Help?
A.1. Acknowledgements
A.1.1. A Brief History of the DNS
A.3. General DNS
A.3.1. IPv6 addresses (A6)
A.4.3. Other Documents About BIND