diff --git a/doc/arm/Bv9ARM.ch01.html b/doc/arm/Bv9ARM.ch01.html index 89d8216b29..dcb3ac7377 100644 --- a/doc/arm/Bv9ARM.ch01.html +++ b/doc/arm/Bv9ARM.ch01.html @@ -4,15 +4,19 @@ >Introduction BIND 9 Administrator Reference Manual
1.1. Scope of Document
1.2. Organization of This Document
1.3. Conventions Used in This Document
1.4. The Domain Name System (DNS

1.1. Scope of Document

1.2. Organization of This Document

1.3. Conventions Used in This Document

BIND configuration file:

]

1.4. The Domain Name System (DNS

1.4.1. DNS Fundamentals

1.4.2. Domains and Domain Names

1.4.3. Zones

1.4.4. Authoritative Name Servers

1.4.4.1. The Primary Master

1.4.4.2. Slave Servers

1.4.4.3. Stealth Servers

1.4.5. Caching Name Servers

1.4.5.1. Forwarding

1.4.6. Name Servers in Multiple Roles

BIND 9 Administrator Reference ManualBIND Resource RequirementsBIND 9 Administrator Reference Manual

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

Nameserver ConfigurationBIND 9 Administrator Reference Manual

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

is one of the following:

3.4.2. Signals

command.

Causes the server to clean up and exit.

Advanced ConceptsBIND 9 Administrator Reference Manual
4.3. Split DNS
4.5. TKEY
4.6. SIG(0)
4.8. IPv6 Support in BINDProposed StandardsProposed Standards

When acting as a master,

4.3. Split DNS

Proposed StandardsProposed Standards. The nsupdate

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

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

The BIND 9 Lightweight ResolverBIND 9 Administrator Reference Manual

5.1. The Lightweight Resolver Library

5.1. The Lightweight Resolver Library

BIND 9 Configuration ReferenceBIND 9 Administrator Reference Manual

6.3. Zone File

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
The following statements are supported:
defines a zone.
6.2.1. aclThe following ACLs are built-in:
6.2.3. controls
6.2.4. controlsRemote Name Daemon Control applicationRemote Name Daemon Control application in
       
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 releases.
Queries.
6.2.11. lwres
6.2.12. lwres
6.2.13. optionsip_port] ; [] ; 
+        [ 
6.2.14. options
6.2.14.2. Forwarding
Forwarding can also be configured on a per-domain basis, allowing
 for the global forwarding options to be overridden in a variety
@@ -4615,6 +4646,8 @@ HREF="Bv9ARM.ch06.html#address_match_lists"
 details on how to specify IP address lists.
6.2.14.4. Interfaces
6.2.14.5. Query Address
6.2.14.7. Resource Limits
.
6.2.14.8. Periodic Task Intervals
 are:
The following statistics counters are maintained:
6.2.15. serverStatement Grammar Statement Grammar
6.2.17. trusted-keys
6.2.18. trusted-keys
6.2.19. view
6.2.20. view
6.2.22. zone
6.2.22.1. Zone Types
6.2.22.2. Class
6.2.22.3. Zone Options
6.3. Zone File
6.3.1.1. Resource Records
The components of a Resource Record are:
(x) representation of X.25 network addresses. Experimental.
.
several fields.
6.3.1.2. Textual expression of RRs
For example, we might show the RRs carried in a message as:
Similarly we might see:
6.3.2. Discussion of MX Records
6.3.4. Inverse Mapping in IPv4
] domain:
6.3.5. Other Zone File Directives
6.3.5.1. The $ORIGIN
6.3.5.2. The $INCLUDE
6.3.5.3. The $TTL
6.3.6. BIND
BIND 9 Security ConsiderationsBIND 9 Administrator Reference Manual
7.2. chroot
7.2. chroot
7.2.1. The chroot
7.2.2. Using the setuidTroubleshootingBIND 9 Administrator Reference Manual
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?
AppendicesBIND 9 Administrator Reference Manual
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)
The aggregatable global Unicast address format is as follows:
<------ Interface Identifier ------>
Where
 
Interface Identifier
NLA ID
Bibliography
Standards
[RFC974] C. Partridge, [RFC974] C. Partridge, Mail Routing and the Domain System, January 1986.
[RFC1034] P.V. Mockapetris, [RFC1034] P.V. Mockapetris, Domain Names — Concepts and Facilities, November 1987.
[RFC1035] P. V. Mockapetris, [RFC1035] P. V. Mockapetris, Domain Names — Implementation and
 Specification, November 1987.
[RFC2181] R., R. Bush Elz, [RFC2181] R., R. Bush Elz, Clarifications to the DNS
[RFC2308] M. Andrews, [RFC2308] M. Andrews, Negative Caching of DNS
[RFC1995] M. Ohta, [RFC1995] M. Ohta, Incremental Zone Transfer in DNS
[RFC1996] P. Vixie, [RFC1996] P. Vixie, A Mechanism for Prompt Notification of Zone Changes, August 1996.
[RFC2136] P. Vixie, S. Thomson, Y. Rekhter, and J. Bound, [RFC2136] P. Vixie, S. Thomson, Y. Rekhter, and J. Bound, Dynamic Updates in the Domain Name System, April 1997.
[RFC2845] P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington, [RFC2845] P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington, Secret Key Transaction Authentication for DNS
Proposed Standards Still Under Development
[RFC1886] S. Thomson and C. Huitema, [RFC1886] S. Thomson and C. Huitema, DNS
[RFC2065] D. Eastlake, 3rd and C. Kaufman, [RFC2065] D. Eastlake, 3rd and C. Kaufman, Domain Name System Security Extensions, January 1997.
[RFC2137] D. Eastlake, 3rd, [RFC2137] D. Eastlake, 3rd, Secure Domain Name System Dynamic Update, April 1997.
Other Important RFCs About DNS
[RFC1535] E. Gavron, [RFC1535] E. Gavron, A Security Problem and Proposed Correction With Widely Deployed DNS
[RFC1536] A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller, [RFC1536] A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller, Common DNS
[RFC1982] R. Elz and R. Bush, [RFC1982] R. Elz and R. Bush, Serial Number Arithmetic, August 1996.
Resource Record Types
[RFC1183] C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris, [RFC1183] C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris, New DNS
[RFC1706] B. Manning and R. Colella, [RFC1706] B. Manning and R. Colella, DNS
[RFC2168] R. Daniel and M. Mealling, [RFC2168] R. Daniel and M. Mealling, Resolution of Uniform Resource Identifiers using
 the Domain Name System, June 1997.
[RFC1876] C. Davis, P. Vixie, T., and I. Dickinson, [RFC1876] C. Davis, P. Vixie, T., and I. Dickinson, A Means for Expressing Location Information in the Domain
 Name System, January 1996.
[RFC2052] A. Gulbrandsen and P. Vixie, [RFC2052] A. Gulbrandsen and P. Vixie, A DNS
[RFC2163] A. Allocchio, [RFC2163] A. Allocchio, Using the Internet DNS
[RFC2230] R. Atkinson, [RFC2230] R. Atkinson, Key Exchange Delegation Record for the DNS
DNS
[RFC1101] P. V. Mockapetris, [RFC1101] P. V. Mockapetris, DNS
[RFC1123] Braden, [RFC1123] Braden, Requirements for Internet Hosts - Application and Support, October 1989.
[RFC1591] J. Postel, [RFC1591] J. Postel, Domain Name System Structure and Delegation, March 1994.
[RFC2317] H. Eidnes, G. de Groot, and P. Vixie, [RFC2317] H. Eidnes, G. de Groot, and P. Vixie, Classless IN-ADDR.ARPA Delegation, March 1998.
DNS
[RFC1537] P. Beertema, [RFC1537] P. Beertema, Common DNS
[RFC1912] D. Barr, [RFC1912] D. Barr, Common DNS
[RFC1912] D. Barr, [RFC1912] D. Barr, Common DNS
[RFC2010] B. Manning and P. Vixie, [RFC2010] B. Manning and P. Vixie, Operational Criteria for Root Name Servers., October 1996.
[RFC2219] M. Hamilton and R. Wright, [RFC2219] M. Hamilton and R. Wright, Use of DNS
Other DNS
[RFC1464] R. Rosenbaum, [RFC1464] R. Rosenbaum, Using the Domain Name System To Store Arbitrary String Attributes, May 1993.
[RFC1713] A. Romao, [RFC1713] A. Romao, Tools for DNS
[RFC1794] T. Brisco, [RFC1794] T. Brisco, DNS
[RFC2240] O. Vaughan, [RFC2240] O. Vaughan, A Legal Basis for Domain Name Allocation, November 1997.
[RFC2345] J. Klensin, T. Wolf, and G. Oglesby, [RFC2345] J. Klensin, T. Wolf, and G. Oglesby, Domain Names and Company Name Retrieval, May 1998.
[RFC2352] O. Vaughan, [RFC2352] O. Vaughan, A Convention For Using Legal Names as Domain Names, May 1998.
Obsolete and Unimplemented Experimental RRs
[RFC1712] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni, [RFC1712] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni, DNS
A.4.3. Other Documents About BIND
Bibliography
Paul Albitz and Cricket Liu, Paul Albitz and Cricket Liu, DNSBIND 9 Administrator Reference Manual
BIND 9 Administrator Reference Manual
Copyright © 2000, 2001 by Internet Software Consortium
1.1. Scope of Document
1.2. Organization of This Document
1.3. Conventions Used in This Document
1.4. The Domain Name System (DNS
1.4.1. DNS Fundamentals
1.4.2. Domains and Domain Names
1.4.3. Zones
1.4.4. Authoritative Name Servers
1.4.5. Caching Name Servers
1.4.6. Name Servers in Multiple Roles
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
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. lwres
6.2.12. lwres
6.2.13. options
6.2.14. optionsserverStatement Grammar Statement Grammar
6.2.16. 
6.2.17. trusted-keys
6.2.18. trusted-keys
6.2.19. view
6.2.20. view
6.2.22. 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
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