From b414eb4312cd9d40f40399539ccaa2a9e48e40a3 Mon Sep 17 00:00:00 2001
From: Andreas Gustafsson The version the server should report
-via a query of the name version.bind
-with type TXT, class CHAOS.
-The default is the real version number of this server.
-Specifying version none
-disables processing of the queries. The hostname the server should report via a query of
-the name hostname.bind
-with type TXT, class CHAOS.
-This defaults to the hostname of the machine hosting the name server as
-found by gethostname(). The primary purpose of such queries is to
-identify which of a group of anycast servers is actually
-answering your queries. Specifying hostname none
-disables processing of the queries.
The server provides some helpful diagnostic information +through a number of built-in zones under the +pseudo-top-level-domain bind in the +CHAOS class. These zones are part of a +built-in view (see Section 6.2.19) of class +CHAOS which is separate from the default view of +class IN; therefore, any global server options +such as allow-query do not apply the these zones. +If you feel the need to disable these zones, use the options +below, or hide the built-in CHAOS view by +defining an explicit view of class CHAOS +that matches all clients.
The version the server should report +via a query of the name version.bind +with type TXT, class CHAOS. +The default is the real version number of this server. +Specifying version none +disables processing of the queries.
The hostname the server should report via a query of +the name hostname.bind +with type TXT, class CHAOS. +This defaults to the hostname of the machine hosting the name server as +found by gethostname(). The primary purpose of such queries is to +identify which of a group of anycast servers is actually +answering your queries. Specifying hostname none +disables processing of the queries.
The statistics file generated by [RFC974] [RFC1034] [RFC1035] [RFC2181] [RFC2308] [RFC1995] [RFC1996] [RFC2136] [RFC2845] [RFC1886] [RFC2065] [RFC2137] [RFC1535] [RFC1536] [RFC1982] [RFC1183] [RFC1706] [RFC2168] [RFC1876] [RFC2052] [RFC2163] [RFC2230] [RFC1101] [RFC1123] [RFC1591] [RFC2317] [RFC1537] [RFC1912] [RFC1912] [RFC2010] [RFC2219] [RFC1464] [RFC1713] [RFC1794] [RFC2240] [RFC2345] [RFC2352] [RFC1712] 6.2.17. trusted-keys
6.2.18. trusted-keys
6.2.19. view
6.2.20. viewview statements in the config
file, a default view that matches any client is automatically created
-in class IN, and any zone statements specified on
the top level of the configuration file are considered to be part of
-this default view. If any explicit options statement will
+apply to the default view. If any explicit view statements
-are present, all
+statements are present, all zone statements must occur inside
- statements must
+occur inside view statements.
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
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
6.3.5.2. The $INCLUDE
6.3.5.3. The $TTL
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
Bibliography
Standards
Proposed Standards Still Under Development
Other Important RFCs About DNS
Resource Record Types
DNS
DNS
Other DNS
Obsolete and Unimplemented Experimental RRs
A.3.3. Other Documents About BIND
Bibliography