| ] |
| Causes the server to clean up and exit. |
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 18b653c3ef..bb6f527246 100644 --- a/doc/arm/Bv9ARM.ch05.html +++ b/doc/arm/Bv9ARM.ch05.html @@ -4,7 +4,7 @@ >The BIND 9 Lightweight Resolver
BIND 9 Configuration Reference| . |
| defines a zone. |
| Dynamic updates. |
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.
|
+
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. |
+
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. |
listen-on-v6 statement is specified, -the server will listen on port 53 on the IPv6 wildcard address.
.
| . |
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_addrip_port
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. |
| 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. |
The components of a Resource Record are:
| (x) representation of X.25 network addresses. Experimental. |
| . |
| several fields. |
For example, we might show the RRs carried in a message as:
] domain:
Troubleshooting
Appendices
The aggregatable global Unicast address format is as follows:
| <------ Interface Identifier ------> |
| Interface Identifier |
| NLA ID |
[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 [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. [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. [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 [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. [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 [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. [RFC2352] O. Vaughan, [RFC2345] J. Klensin, T. Wolf, and G. Oglesby, Domain Names and Company Name Retrieval, May 1998. [RFC2352] O. Vaughan, A Convention For Using Legal Names as Domain Names, May 1998. [RFC1712] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni, [RFC1712] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni, DNS Paul Albitz and Cricket Liu, Paul Albitz and Cricket Liu, DNSProposed Standards Still Under Development
Other Important RFCs About DNS
Resource Record Types
DNS
DNS
Other DNS
Obsolete and Unimplemented Experimental RRs
A.4.3. Other Documents About BIND
Bibliography