From: Andreas Gustafsson Date: Wed, 18 Oct 2000 18:31:51 +0000 (+0000) Subject: regenerated X-Git-Tag: v9.0.1^4 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=027e89d47af308db4b41761ca9f847c026b63ec8;p=thirdparty%2Fbind9.git regenerated --- diff --git a/doc/arm/Bv9ARM.ch01.html b/doc/arm/Bv9ARM.ch01.html index 3f47b4869b8..5a1391480ef 100644 --- a/doc/arm/Bv9ARM.ch01.html +++ b/doc/arm/Bv9ARM.ch01.html @@ -4,7 +4,7 @@ >Introduction

BIND configuration file:

]

BIND Resource RequirementsNameserver Configuration

:

stats[a]

trace[a]

notrace[a]

querylog[a]

stop[a]

restart[a]

Restart the server.

dumpdb[a]
Notes:
a. anot yet implemented

command.

Causes the server to clean up and exit.

Advanced ConceptsProposed StandardsProposed Standards

When acting as a master, Proposed StandardsProposed Standards. The nsupdate-h" option prints a - full list of parameters.

There must also be communication with the administrators of the parent and/or child zone to transmit keys and signatures. A diff --git a/doc/arm/Bv9ARM.ch05.html b/doc/arm/Bv9ARM.ch05.html index 18b653c3ef3..bb6f5272466 100644 --- a/doc/arm/Bv9ARM.ch05.html +++ b/doc/arm/Bv9ARM.ch05.html @@ -4,7 +4,7 @@ >The BIND 9 Lightweight ResolverBIND 9 Configuration Reference

6.3. Zone File

.

The following statements are supported:

defines a zone.

The following ACLs are built-in:

Remote Name Daemon Control applicationRemote Name Daemon Control application in Section 3.4.1.2 releases.

Dynamic updates.

ip_addr; [ [port ip_port] ; [ ip_addr; ... [port ip_port] ; ... ] }; ] [

6.2.12. options statement, an options block with each option set to its default will be used.

+

It was used in This option is obsolete. +It was used in BIND 8 to specify the pathname to the named-xfer program is needed; its functionality is built into the name server.

Note: This option is obsolete.

+

Note: These options are not yet implemented in BIND 9.0.

+

This option is obsoleteThis option is obsolete. It was used in , and a DNS query requests recursion, then the server will attempt to do -all the work required to answer the query. If recursion is not on, -the server will return a referral to the client if it doesn't know -the answer. The default is yes. See also . +Note that setting recursion no; does not prevent +clients from getting data from the server's cache; it only +prevents new data from being cached as an effect of client queries. +Caching may still occur as an effect the server's internal +operation, such as NOTIFY address lookups. +See also fetch-glue above.

This option is obsoleteThis option is obsolete.

6.2.12.2. Forwarding

Specifies which hosts are allowed to make recursive queries through this server. If not specified, the -default is to allow recursive queries from all hosts.

6.2.12.5. Interfaces

listen-on-v6 statement is specified, -the server will listen on port 53 on the IPv6 wildcard address.

6.2.12.6. Query Address

6.2.12.8. Resource Limits

.

.

6.2.12.9. Periodic Task Intervals

are:

6.2.12.14. Deprecated Features

6.2.15. trusted-keys

6.2.16. trusted-keys

6.2.17. viewview_name { +> [class] { match-clients {

6.2.18. viewview statement, and then -apply only when resolving queries with that view. When no a view-specific +apply only when resolving queries with that view. When no view-specific value is given, the value in the options statement.

Views are class specific. If no class is given, class IN -is assumed.

If there are no ] [ also-notify { [ also-notify { ip_addr ; [ [port ip_port] ; [ ip_addr ; [ [...]]] } ; port ip_port] ; ... ] }; ] [port numberip_port] { ip_addr ; [ [port ip_port] ; [...]

6.2.20. zone

6.2.20.1. Zone Types

A slave zone is a replica of a master -zone. The masters list specifies one or more IP addresses that the -slave contacts to update its copy of the zone. If a port is specified, -the slave then checks to see if the zone is current and zone transfers -will be done to the port given. If a file is specified, then the +zone. The masters list specifies one or more IP addresses +of master servers that the slave contacts to update its copy of the zone. +By default, transfers are made from port 53 on the servers; this can +be changed for all servers by specifying a port number before the +list of IP addresses, or on a per-server basis after the IP address. +If a file is specified, then the replica will be written to this file whenever the zone is changed, and reloaded from this file on a server restart. Use of a file is recommended, since it often speeds server start-up and eliminates @@ -7641,7 +7638,6 @@ IN, the server users a compiled-in default set of root servers hints. Classes other than IN have no built-in defaults hints.

6.2.20.2. Class

6.2.20.3. Zone Options

also-notify. +>. A port may be specified +with each also-notify address to send the notify +messages to a port other than the default of 53. also-notify is not meaningful for stub zones. -The default is the empty list.

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 Considerations
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

Troubleshooting

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?

Appendices

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, DNS

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