diff options
Diffstat (limited to 'usr.sbin/bind/doc/arm')
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM-book.xml | 17491 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch03.html | 828 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch04.html | 1238 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch05.html | 110 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch06.html | 8201 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch07.html | 243 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch08.html | 107 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch09.html | 679 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.html | 212 |
9 files changed, 19258 insertions, 9851 deletions
diff --git a/usr.sbin/bind/doc/arm/Bv9ARM-book.xml b/usr.sbin/bind/doc/arm/Bv9ARM-book.xml index 09b12a96d89..f033cd9ca8c 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM-book.xml +++ b/usr.sbin/bind/doc/arm/Bv9ARM-book.xml @@ -1,11 +1,11 @@ -<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN" - "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd" +<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" + "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [<!ENTITY mdash "—">]> <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - - Permission to use, copy, modify, and distribute this software for any + - Permission to use, copy, modify, and/or distribute this software for any - purpose with or without fee is hereby granted, provided that the above - copyright notice and this permission notice appear in all copies. - @@ -18,16 +18,16 @@ - PERFORMANCE OF THIS SOFTWARE. --> -<!-- File: $ISC: Bv9ARM-book.xml,v 1.155.2.27.2.74 2006/11/14 22:38:53 sra Exp $ --> - -<book> -<title>BIND 9 Administrator Reference Manual</title> +<!-- File: $ISC: Bv9ARM-book.xml,v 1.241.18.82 2007/09/26 03:28:27 marka Exp $ --> +<book xmlns:xi="http://www.w3.org/2001/XInclude"> + <title>BIND 9 Administrator Reference Manual</title> <bookinfo> <copyright> <year>2004</year> <year>2005</year> <year>2006</year> + <year>2007</year> <holder>Internet Systems Consortium, Inc. ("ISC")</holder> </copyright> <copyright> @@ -40,421 +40,636 @@ </bookinfo> <chapter id="Bv9ARM.ch01"> - <title>Introduction </title> - <para>The Internet Domain Name System (<acronym>DNS</acronym>) consists of the syntax - to specify the names of entities in the Internet in a hierarchical - manner, the rules used for delegating authority over names, and the - system implementation that actually maps names to Internet - addresses. <acronym>DNS</acronym> data is maintained in a group of distributed - hierarchical databases.</para> - - <sect1> - <title>Scope of Document</title> - - <para>The Berkeley Internet Name Domain (<acronym>BIND</acronym>) implements a - domain name server for a number of operating systems. This - document provides basic information about the installation and - care of the Internet Software Consortium (<acronym>ISC</acronym>) - <acronym>BIND</acronym> version 9 software package for system - administrators.</para> - - <para>This version of the manual corresponds to BIND version 9.3.</para> - - </sect1> - <sect1><title>Organization of This Document</title> - <para>In this document, <emphasis>Section 1</emphasis> introduces - the basic <acronym>DNS</acronym> and <acronym>BIND</acronym> concepts. <emphasis>Section 2</emphasis> - describes resource requirements for running <acronym>BIND</acronym> in various - environments. Information in <emphasis>Section 3</emphasis> is - <emphasis>task-oriented</emphasis> in its presentation and is - organized functionally, to aid in the process of installing the - <acronym>BIND</acronym> 9 software. The task-oriented section is followed by - <emphasis>Section 4</emphasis>, which contains more advanced - concepts that the system administrator may need for implementing - certain options. <emphasis>Section 5</emphasis> - describes the <acronym>BIND</acronym> 9 lightweight - resolver. The contents of <emphasis>Section 6</emphasis> are - organized as in a reference manual to aid in the ongoing - maintenance of the software. <emphasis>Section 7 - </emphasis>addresses security considerations, and - <emphasis>Section 8</emphasis> contains troubleshooting help. The - main body of the document is followed by several - <emphasis>Appendices</emphasis> which contain useful reference - information, such as a <emphasis>Bibliography</emphasis> and - historic information related to <acronym>BIND</acronym> and the Domain Name - System.</para> - </sect1> - <sect1><title>Conventions Used in This Document</title> - - <para>In this document, we use the following general typographic - conventions:</para> - -<informaltable> - <tgroup cols = "2"> - <colspec colname = "1" colnum = "1" colwidth = "3.000in"/> - <colspec colname = "2" colnum = "2" colwidth = "2.625in"/> + <title>Introduction</title> + <para> + The Internet Domain Name System (<acronym>DNS</acronym>) + consists of the syntax + to specify the names of entities in the Internet in a hierarchical + manner, the rules used for delegating authority over names, and the + system implementation that actually maps names to Internet + addresses. <acronym>DNS</acronym> data is maintained in a + group of distributed + hierarchical databases. + </para> + + <sect1> + <title>Scope of Document</title> + + <para> + The Berkeley Internet Name Domain + (<acronym>BIND</acronym>) implements a + domain name server for a number of operating systems. This + document provides basic information about the installation and + care of the Internet Systems Consortium (<acronym>ISC</acronym>) + <acronym>BIND</acronym> version 9 software package for + system administrators. + </para> + + <para> + This version of the manual corresponds to BIND version 9.4. + </para> + + </sect1> + <sect1> + <title>Organization of This Document</title> + <para> + In this document, <emphasis>Section 1</emphasis> introduces + the basic <acronym>DNS</acronym> and <acronym>BIND</acronym> concepts. <emphasis>Section 2</emphasis> + describes resource requirements for running <acronym>BIND</acronym> in various + environments. Information in <emphasis>Section 3</emphasis> is + <emphasis>task-oriented</emphasis> in its presentation and is + organized functionally, to aid in the process of installing the + <acronym>BIND</acronym> 9 software. The task-oriented + section is followed by + <emphasis>Section 4</emphasis>, which contains more advanced + concepts that the system administrator may need for implementing + certain options. <emphasis>Section 5</emphasis> + describes the <acronym>BIND</acronym> 9 lightweight + resolver. The contents of <emphasis>Section 6</emphasis> are + organized as in a reference manual to aid in the ongoing + maintenance of the software. <emphasis>Section 7</emphasis> addresses + security considerations, and + <emphasis>Section 8</emphasis> contains troubleshooting help. The + main body of the document is followed by several + <emphasis>appendices</emphasis> which contain useful reference + information, such as a <emphasis>bibliography</emphasis> and + historic information related to <acronym>BIND</acronym> + and the Domain Name + System. + </para> + </sect1> + <sect1> + <title>Conventions Used in This Document</title> + + <para> + In this document, we use the following general typographic + conventions: + </para> + + <informaltable> + <tgroup cols="2"> + <colspec colname="1" colnum="1" colwidth="3.000in"/> + <colspec colname="2" colnum="2" colwidth="2.625in"/> <tbody> <row> - <entry colname = "1"> -<para><emphasis>To -describe:</emphasis></para></entry> - <entry colname = "2"> -<para><emphasis>We use the style:</emphasis></para></entry> + <entry colname="1"> + <para> + <emphasis>To describe:</emphasis> + </para> + </entry> + <entry colname="2"> + <para> + <emphasis>We use the style:</emphasis> + </para> + </entry> </row> <row> - <entry colname = "1"> -<para>a pathname, filename, URL, hostname, -mailing list name, or new term or concept</para></entry> - <entry colname = "2"><para><filename>Fixed width</filename></para></entry> + <entry colname="1"> + <para> + a pathname, filename, URL, hostname, + mailing list name, or new term or concept + </para> + </entry> + <entry colname="2"> + <para> + <filename>Fixed width</filename> + </para> + </entry> </row> <row> - <entry colname = "1"><para>literal user -input</para></entry> - <entry colname = "2"><para><userinput>Fixed Width Bold</userinput></para></entry> + <entry colname="1"> + <para> + literal user + input + </para> + </entry> + <entry colname="2"> + <para> + <userinput>Fixed Width Bold</userinput> + </para> + </entry> </row> <row> - <entry colname = "1"><para>program output</para></entry> - <entry colname = "2"><para><computeroutput>Fixed Width</computeroutput></para></entry> + <entry colname="1"> + <para> + program output + </para> + </entry> + <entry colname="2"> + <para> + <computeroutput>Fixed Width</computeroutput> + </para> + </entry> </row> </tbody> </tgroup> -</informaltable> - - <para>The following conventions are used in descriptions of the -<acronym>BIND</acronym> configuration file:<informaltable colsep = "0" frame = "all" rowsep = "0"> - <tgroup cols = "2" colsep = "0" rowsep = "0" - tgroupstyle = "2Level-table"> - <colspec colname = "1" colnum = "1" colsep = "0" colwidth = "3.000in"/> - <colspec colname = "2" colnum = "2" colsep = "0" colwidth = "2.625in"/> - <tbody> - <row rowsep = "0"> - <entry colname = "1" colsep = "1" rowsep = "1"><para><emphasis>To -describe:</emphasis></para></entry> - <entry colname = "2" rowsep = "1"><para><emphasis>We use the style:</emphasis></para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1" colsep = "1" rowsep = "1"><para>keywords</para></entry> - <entry colname = "2" rowsep = "1"><para><literal>Fixed Width</literal></para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1" colsep = "1" rowsep = "1"><para>variables</para></entry> - <entry colname = "2" rowsep = "1"><para><varname>Fixed Width</varname></para></entry> - </row> -<row rowsep = "0"> -<entry colname = "1" colsep = "1"><para>Optional input</para></entry> - <entry colname = "2"><para><optional>Text is enclosed in square brackets</optional></para></entry> -</row> -</tbody> -</tgroup></informaltable></para></sect1> -<sect1><title>The Domain Name System (<acronym>DNS</acronym>)</title> -<para>The purpose of this document is to explain the installation -and upkeep of the <acronym>BIND</acronym> software package, and we -begin by reviewing the fundamentals of the Domain Name System -(<acronym>DNS</acronym>) as they relate to <acronym>BIND</acronym>. -</para> - -<sect2> -<title>DNS Fundamentals</title> - -<para>The Domain Name System (DNS) is the hierarchical, distributed -database. It stores information for mapping Internet host names to IP -addresses and vice versa, mail routing information, and other data -used by Internet applications.</para> - -<para>Clients look up information in the DNS by calling a -<emphasis>resolver</emphasis> library, which sends queries to one or -more <emphasis>name servers</emphasis> and interprets the responses. -The <acronym>BIND</acronym> 9 software distribution contains a -name server, <command>named</command>, and two resolver -libraries, <command>liblwres</command> and <command>libbind</command>. -</para> - -</sect2><sect2> -<title>Domains and Domain Names</title> - -<para>The data stored in the DNS is identified by <emphasis>domain -names</emphasis> that are organized as a tree according to -organizational or administrative boundaries. Each node of the tree, -called a <emphasis>domain</emphasis>, is given a label. The domain name of the -node is the concatenation of all the labels on the path from the -node to the <emphasis>root</emphasis> node. This is represented -in written form as a string of labels listed from right to left and -separated by dots. A label need only be unique within its parent -domain.</para> - -<para>For example, a domain name for a host at the -company <emphasis>Example, Inc.</emphasis> could be -<literal>mail.example.com</literal>, -where <literal>com</literal> is the -top level domain to which -<literal>ourhost.example.com</literal> belongs, -<literal>example</literal> is -a subdomain of <literal>com</literal>, and -<literal>ourhost</literal> is the -name of the host.</para> - -<para>For administrative purposes, the name space is partitioned into -areas called <emphasis>zones</emphasis>, each starting at a node and -extending down to the leaf nodes or to nodes where other zones start. -The data for each zone is stored in a <emphasis>name -server</emphasis>, which answers queries about the zone using the -<emphasis>DNS protocol</emphasis>. -</para> - -<para>The data associated with each domain name is stored in the -form of <emphasis>resource records</emphasis> (<acronym>RR</acronym>s). -Some of the supported resource record types are described in -<xref linkend="types_of_resource_records_and_when_to_use_them"/>.</para> - -<para>For more detailed information about the design of the DNS and -the DNS protocol, please refer to the standards documents listed in -<xref linkend="rfcs"/>.</para> -</sect2> - -<sect2><title>Zones</title> -<para>To properly operate a name server, it is important to understand -the difference between a <emphasis>zone</emphasis> -and a <emphasis>domain</emphasis>.</para> - -<para>As we stated previously, a zone is a point of delegation in -the <acronym>DNS</acronym> tree. A zone consists of -those contiguous parts of the domain -tree for which a name server has complete information and over which -it has authority. It contains all domain names from a certain point -downward in the domain tree except those which are delegated to -other zones. A delegation point is marked by one or more -<emphasis>NS records</emphasis> in the -parent zone, which should be matched by equivalent NS records at -the root of the delegated zone.</para> - -<para>For instance, consider the <literal>example.com</literal> -domain which includes names -such as <literal>host.aaa.example.com</literal> and -<literal>host.bbb.example.com</literal> even though -the <literal>example.com</literal> zone includes -only delegations for the <literal>aaa.example.com</literal> and -<literal>bbb.example.com</literal> zones. A zone can map -exactly to a single domain, but could also include only part of a -domain, the rest of which could be delegated to other -name servers. Every name in the <acronym>DNS</acronym> tree is a -<emphasis>domain</emphasis>, even if it is -<emphasis>terminal</emphasis>, that is, has no -<emphasis>subdomains</emphasis>. Every subdomain is a domain and -every domain except the root is also a subdomain. The terminology is -not intuitive and we suggest that you read RFCs 1033, 1034 and 1035 to -gain a complete understanding of this difficult and subtle -topic.</para> - -<para>Though <acronym>BIND</acronym> is called a "domain name server", -it deals primarily in terms of zones. The master and slave -declarations in the <filename>named.conf</filename> file specify -zones, not domains. When you ask some other site if it is willing to -be a slave server for your <emphasis>domain</emphasis>, you are -actually asking for slave service for some collection of zones.</para> -</sect2> - -<sect2><title>Authoritative Name Servers</title> - -<para>Each zone is served by at least -one <emphasis>authoritative name server</emphasis>, -which contains the complete data for the zone. -To make the DNS tolerant of server and network failures, -most zones have two or more authoritative servers. -</para> - -<para>Responses from authoritative servers have the "authoritative -answer" (AA) bit set in the response packets. This makes them -easy to identify when debugging DNS configurations using tools like -<command>dig</command> (<xref linkend="diagnostic_tools"/>).</para> - -<sect3><title>The Primary Master</title> - -<para> -The authoritative server where the master copy of the zone data is maintained is -called the <emphasis>primary master</emphasis> server, or simply the -<emphasis>primary</emphasis>. It loads the zone contents from some -local file edited by humans or perhaps generated mechanically from -some other local file which is edited by humans. This file is called -the <emphasis>zone file</emphasis> or <emphasis>master file</emphasis>.</para> -</sect3> - -<sect3><title>Slave Servers</title> -<para>The other authoritative servers, the <emphasis>slave</emphasis> -servers (also known as <emphasis>secondary</emphasis> servers) load -the zone contents from another server using a replication process -known as a <emphasis>zone transfer</emphasis>. Typically the data are -transferred directly from the primary master, but it is also possible -to transfer it from another slave. In other words, a slave server -may itself act as a master to a subordinate slave server.</para> -</sect3> - -<sect3><title>Stealth Servers</title> - -<para>Usually all of the zone's authoritative servers are listed in -NS records in the parent zone. These NS records constitute -a <emphasis>delegation</emphasis> of the zone from the parent. -The authoritative servers are also listed in the zone file itself, -at the <emphasis>top level</emphasis> or <emphasis>apex</emphasis> -of the zone. You can list servers in the zone's top-level NS -records that are not in the parent's NS delegation, but you cannot -list servers in the parent's delegation that are not present at -the zone's top level.</para> - -<para>A <emphasis>stealth server</emphasis> is a server that is -authoritative for a zone but is not listed in that zone's NS -records. Stealth servers can be used for keeping a local copy of a -zone to speed up access to the zone's records or to make sure that the -zone is available even if all the "official" servers for the zone are -inaccessible.</para> - -<para>A configuration where the primary master server itself is a -stealth server is often referred to as a "hidden primary" -configuration. One use for this configuration is when the primary master -is behind a firewall and therefore unable to communicate directly -with the outside world.</para> - -</sect3> - -</sect2> -<sect2> - -<title>Caching Name Servers</title> - -<para>The resolver libraries provided by most operating systems are -<emphasis>stub resolvers</emphasis>, meaning that they are not capable of -performing the full DNS resolution process by themselves by talking -directly to the authoritative servers. Instead, they rely on a local -name server to perform the resolution on their behalf. Such a server -is called a <emphasis>recursive</emphasis> name server; it performs -<emphasis>recursive lookups</emphasis> for local clients.</para> - -<para>To improve performance, recursive servers cache the results of -the lookups they perform. Since the processes of recursion and -caching are intimately connected, the terms -<emphasis>recursive server</emphasis> and -<emphasis>caching server</emphasis> are often used synonymously.</para> - -<para>The length of time for which a record may be retained in -the cache of a caching name server is controlled by the -Time To Live (TTL) field associated with each resource record. -</para> - -<sect3><title>Forwarding</title> - -<para>Even a caching name server does not necessarily perform -the complete recursive lookup itself. Instead, it can -<emphasis>forward</emphasis> some or all of the queries -that it cannot satisfy from its cache to another caching name server, -commonly referred to as a <emphasis>forwarder</emphasis>. -</para> - -<para>There may be one or more forwarders, -and they are queried in turn until the list is exhausted or an answer -is found. Forwarders are typically used when you do not -wish all the servers at a given site to interact directly with the rest of -the Internet servers. A typical scenario would involve a number -of internal <acronym>DNS</acronym> servers and an Internet firewall. Servers unable -to pass packets through the firewall would forward to the server -that can do it, and that server would query the Internet <acronym>DNS</acronym> servers -on the internal server's behalf. An added benefit of using the forwarding -feature is that the central machine develops a much more complete -cache of information that all the clients can take advantage -of.</para> -</sect3> - -</sect2> - -<sect2><title>Name Servers in Multiple Roles</title> - -<para>The <acronym>BIND</acronym> name server can simultaneously act as -a master for some zones, a slave for other zones, and as a caching -(recursive) server for a set of local clients.</para> - -<para>However, since the functions of authoritative name service -and caching/recursive name service are logically separate, it is -often advantageous to run them on separate server machines. - -A server that only provides authoritative name service -(an <emphasis>authoritative-only</emphasis> server) can run with -recursion disabled, improving reliability and security. - -A server that is not authoritative for any zones and only provides -recursive service to local -clients (a <emphasis>caching-only</emphasis> server) -does not need to be reachable from the Internet at large and can -be placed inside a firewall.</para> - - </sect2> - </sect1> - -</chapter> - -<chapter id="Bv9ARM.ch02"><title><acronym>BIND</acronym> Resource Requirements</title> - -<sect1> -<title>Hardware requirements</title> - -<para><acronym>DNS</acronym> hardware requirements have traditionally been quite modest. -For many installations, servers that have been pensioned off from -active duty have performed admirably as <acronym>DNS</acronym> servers.</para> -<para>The DNSSEC and IPv6 features of <acronym>BIND</acronym> 9 may prove to be quite -CPU intensive however, so organizations that make heavy use of these -features may wish to consider larger systems for these applications. -<acronym>BIND</acronym> 9 is fully multithreaded, allowing full utilization of -multiprocessor systems for installations that need it.</para></sect1> -<sect1><title>CPU Requirements</title> -<para>CPU requirements for <acronym>BIND</acronym> 9 range from i486-class machines -for serving of static zones without caching, to enterprise-class -machines if you intend to process many dynamic updates and DNSSEC -signed zones, serving many thousands of queries per second.</para></sect1> - -<sect1><title>Memory Requirements</title> -<para>The memory of the server has to be large enough to fit the -cache and zones loaded off disk. The <command>max-cache-size</command> -option can be used to limit the amount of memory used by the cache, -at the expense of reducing cache hit rates and causing more <acronym>DNS</acronym> -traffic. It is still good practice to have enough memory to load -all zone and cache data into memory — unfortunately, the best way -to determine this for a given installation is to watch the name server -in operation. After a few weeks the server process should reach -a relatively stable size where entries are expiring from the cache as -fast as they are being inserted.</para></sect1> - -<sect1><title>Name Server Intensive Environment Issues</title> -<para>For name server intensive environments, there are two alternative -configurations that may be used. The first is where clients and -any second-level internal name servers query a main name server, which -has enough memory to build a large cache. This approach minimizes -the bandwidth used by external name lookups. The second alternative -is to set up second-level internal name servers to make queries independently. -In this configuration, none of the individual machines needs to -have as much memory or CPU power as in the first alternative, but -this has the disadvantage of making many more external queries, -as none of the name servers share their cached data.</para></sect1> - -<sect1><title>Supported Operating Systems</title> -<para>ISC <acronym>BIND</acronym> 9 compiles and runs on a large number -of Unix-like operating system and on Windows NT / 2000. For an up-to-date -list of supported systems, see the README file in the top level directory -of the BIND 9 source distribution.</para> -</sect1> -</chapter> - -<chapter id="Bv9ARM.ch03"> -<title>Name Server Configuration</title> -<para>In this section we provide some suggested configurations along -with guidelines for their use. We also address the topic of reasonable -option setting.</para> - -<sect1 id="sample_configuration"> -<title>Sample Configurations</title> -<sect2> -<title>A Caching-only Name Server</title> -<para>The following sample configuration is appropriate for a caching-only -name server for use by clients internal to a corporation. All queries -from outside clients are refused using the <command>allow-query</command> -option. Alternatively, the same effect could be achieved using suitable -firewall rules.</para> + </informaltable> + + <para> + The following conventions are used in descriptions of the + <acronym>BIND</acronym> configuration file:<informaltable colsep="0" frame="all" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="2Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="3.000in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="2.625in"/> + <tbody> + <row rowsep="0"> + <entry colname="1" colsep="1" rowsep="1"> + <para> + <emphasis>To describe:</emphasis> + </para> + </entry> + <entry colname="2" rowsep="1"> + <para> + <emphasis>We use the style:</emphasis> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1" colsep="1" rowsep="1"> + <para> + keywords + </para> + </entry> + <entry colname="2" rowsep="1"> + <para> + <literal>Fixed Width</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1" colsep="1" rowsep="1"> + <para> + variables + </para> + </entry> + <entry colname="2" rowsep="1"> + <para> + <varname>Fixed Width</varname> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1" colsep="1"> + <para> + Optional input + </para> + </entry> + <entry colname="2"> + <para> + <optional>Text is enclosed in square brackets</optional> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + </para> + </sect1> + <sect1> + <title>The Domain Name System (<acronym>DNS</acronym>)</title> + <para> + The purpose of this document is to explain the installation + and upkeep of the <acronym>BIND</acronym> (Berkeley Internet + Name Domain) software package, and we + begin by reviewing the fundamentals of the Domain Name System + (<acronym>DNS</acronym>) as they relate to <acronym>BIND</acronym>. + </para> + + <sect2> + <title>DNS Fundamentals</title> + + <para> + The Domain Name System (DNS) is a hierarchical, distributed + database. It stores information for mapping Internet host names to + IP + addresses and vice versa, mail routing information, and other data + used by Internet applications. + </para> + + <para> + Clients look up information in the DNS by calling a + <emphasis>resolver</emphasis> library, which sends queries to one or + more <emphasis>name servers</emphasis> and interprets the responses. + The <acronym>BIND</acronym> 9 software distribution + contains a + name server, <command>named</command>, and two resolver + libraries, <command>liblwres</command> and <command>libbind</command>. + </para> + + </sect2><sect2> + <title>Domains and Domain Names</title> + + <para> + The data stored in the DNS is identified by <emphasis>domain names</emphasis> that are organized as a tree according to + organizational or administrative boundaries. Each node of the tree, + called a <emphasis>domain</emphasis>, is given a label. The domain + name of the + node is the concatenation of all the labels on the path from the + node to the <emphasis>root</emphasis> node. This is represented + in written form as a string of labels listed from right to left and + separated by dots. A label need only be unique within its parent + domain. + </para> + + <para> + For example, a domain name for a host at the + company <emphasis>Example, Inc.</emphasis> could be + <literal>ourhost.example.com</literal>, + where <literal>com</literal> is the + top level domain to which + <literal>ourhost.example.com</literal> belongs, + <literal>example</literal> is + a subdomain of <literal>com</literal>, and + <literal>ourhost</literal> is the + name of the host. + </para> + + <para> + For administrative purposes, the name space is partitioned into + areas called <emphasis>zones</emphasis>, each starting at a node and + extending down to the leaf nodes or to nodes where other zones + start. + The data for each zone is stored in a <emphasis>name server</emphasis>, which answers queries about the zone using the + <emphasis>DNS protocol</emphasis>. + </para> + + <para> + The data associated with each domain name is stored in the + form of <emphasis>resource records</emphasis> (<acronym>RR</acronym>s). + Some of the supported resource record types are described in + <xref linkend="types_of_resource_records_and_when_to_use_them"/>. + </para> + + <para> + For more detailed information about the design of the DNS and + the DNS protocol, please refer to the standards documents listed in + <xref linkend="rfcs"/>. + </para> + </sect2> + + <sect2> + <title>Zones</title> + <para> + To properly operate a name server, it is important to understand + the difference between a <emphasis>zone</emphasis> + and a <emphasis>domain</emphasis>. + </para> + + <para> + As stated previously, a zone is a point of delegation in + the <acronym>DNS</acronym> tree. A zone consists of + those contiguous parts of the domain + tree for which a name server has complete information and over which + it has authority. It contains all domain names from a certain point + downward in the domain tree except those which are delegated to + other zones. A delegation point is marked by one or more + <emphasis>NS records</emphasis> in the + parent zone, which should be matched by equivalent NS records at + the root of the delegated zone. + </para> + + <para> + For instance, consider the <literal>example.com</literal> + domain which includes names + such as <literal>host.aaa.example.com</literal> and + <literal>host.bbb.example.com</literal> even though + the <literal>example.com</literal> zone includes + only delegations for the <literal>aaa.example.com</literal> and + <literal>bbb.example.com</literal> zones. A zone can + map + exactly to a single domain, but could also include only part of a + domain, the rest of which could be delegated to other + name servers. Every name in the <acronym>DNS</acronym> + tree is a + <emphasis>domain</emphasis>, even if it is + <emphasis>terminal</emphasis>, that is, has no + <emphasis>subdomains</emphasis>. Every subdomain is a domain and + every domain except the root is also a subdomain. The terminology is + not intuitive and we suggest that you read RFCs 1033, 1034 and 1035 + to + gain a complete understanding of this difficult and subtle + topic. + </para> + + <para> + Though <acronym>BIND</acronym> is called a "domain name + server", + it deals primarily in terms of zones. The master and slave + declarations in the <filename>named.conf</filename> file + specify + zones, not domains. When you ask some other site if it is willing to + be a slave server for your <emphasis>domain</emphasis>, you are + actually asking for slave service for some collection of zones. + </para> + </sect2> + + <sect2> + <title>Authoritative Name Servers</title> + + <para> + Each zone is served by at least + one <emphasis>authoritative name server</emphasis>, + which contains the complete data for the zone. + To make the DNS tolerant of server and network failures, + most zones have two or more authoritative servers, on + different networks. + </para> + + <para> + Responses from authoritative servers have the "authoritative + answer" (AA) bit set in the response packets. This makes them + easy to identify when debugging DNS configurations using tools like + <command>dig</command> (<xref linkend="diagnostic_tools"/>). + </para> + + <sect3> + <title>The Primary Master</title> + + <para> + The authoritative server where the master copy of the zone + data is maintained is called the + <emphasis>primary master</emphasis> server, or simply the + <emphasis>primary</emphasis>. Typically it loads the zone + contents from some local file edited by humans or perhaps + generated mechanically from some other local file which is + edited by humans. This file is called the + <emphasis>zone file</emphasis> or + <emphasis>master file</emphasis>. + </para> + + <para> + In some cases, however, the master file may not be edited + by humans at all, but may instead be the result of + <emphasis>dynamic update</emphasis> operations. + </para> + </sect3> + + <sect3> + <title>Slave Servers</title> + <para> + The other authoritative servers, the <emphasis>slave</emphasis> + servers (also known as <emphasis>secondary</emphasis> servers) + load + the zone contents from another server using a replication process + known as a <emphasis>zone transfer</emphasis>. Typically the data + are + transferred directly from the primary master, but it is also + possible + to transfer it from another slave. In other words, a slave server + may itself act as a master to a subordinate slave server. + </para> + </sect3> + + <sect3> + <title>Stealth Servers</title> + + <para> + Usually all of the zone's authoritative servers are listed in + NS records in the parent zone. These NS records constitute + a <emphasis>delegation</emphasis> of the zone from the parent. + The authoritative servers are also listed in the zone file itself, + at the <emphasis>top level</emphasis> or <emphasis>apex</emphasis> + of the zone. You can list servers in the zone's top-level NS + records that are not in the parent's NS delegation, but you cannot + list servers in the parent's delegation that are not present at + the zone's top level. + </para> + + <para> + A <emphasis>stealth server</emphasis> is a server that is + authoritative for a zone but is not listed in that zone's NS + records. Stealth servers can be used for keeping a local copy of + a + zone to speed up access to the zone's records or to make sure that + the + zone is available even if all the "official" servers for the zone + are + inaccessible. + </para> + + <para> + A configuration where the primary master server itself is a + stealth server is often referred to as a "hidden primary" + configuration. One use for this configuration is when the primary + master + is behind a firewall and therefore unable to communicate directly + with the outside world. + </para> + + </sect3> + + </sect2> + <sect2> + + <title>Caching Name Servers</title> + + <!-- + - Terminology here is inconsistent. Probably ought to + - convert to using "recursive name server" everywhere + - with just a note about "caching" terminology. + --> + + <para> + The resolver libraries provided by most operating systems are + <emphasis>stub resolvers</emphasis>, meaning that they are not + capable of + performing the full DNS resolution process by themselves by talking + directly to the authoritative servers. Instead, they rely on a + local + name server to perform the resolution on their behalf. Such a + server + is called a <emphasis>recursive</emphasis> name server; it performs + <emphasis>recursive lookups</emphasis> for local clients. + </para> + + <para> + To improve performance, recursive servers cache the results of + the lookups they perform. Since the processes of recursion and + caching are intimately connected, the terms + <emphasis>recursive server</emphasis> and + <emphasis>caching server</emphasis> are often used synonymously. + </para> + + <para> + The length of time for which a record may be retained in + the cache of a caching name server is controlled by the + Time To Live (TTL) field associated with each resource record. + </para> + + <sect3> + <title>Forwarding</title> + + <para> + Even a caching name server does not necessarily perform + the complete recursive lookup itself. Instead, it can + <emphasis>forward</emphasis> some or all of the queries + that it cannot satisfy from its cache to another caching name + server, + commonly referred to as a <emphasis>forwarder</emphasis>. + </para> + + <para> + There may be one or more forwarders, + and they are queried in turn until the list is exhausted or an + answer + is found. Forwarders are typically used when you do not + wish all the servers at a given site to interact directly with the + rest of + the Internet servers. A typical scenario would involve a number + of internal <acronym>DNS</acronym> servers and an + Internet firewall. Servers unable + to pass packets through the firewall would forward to the server + that can do it, and that server would query the Internet <acronym>DNS</acronym> servers + on the internal server's behalf. + </para> + </sect3> + + </sect2> + + <sect2> + <title>Name Servers in Multiple Roles</title> + + <para> + The <acronym>BIND</acronym> name server can + simultaneously act as + a master for some zones, a slave for other zones, and as a caching + (recursive) server for a set of local clients. + </para> + + <para> + However, since the functions of authoritative name service + and caching/recursive name service are logically separate, it is + often advantageous to run them on separate server machines. + + A server that only provides authoritative name service + (an <emphasis>authoritative-only</emphasis> server) can run with + recursion disabled, improving reliability and security. + + A server that is not authoritative for any zones and only provides + recursive service to local + clients (a <emphasis>caching-only</emphasis> server) + does not need to be reachable from the Internet at large and can + be placed inside a firewall. + </para> + + </sect2> + </sect1> + + </chapter> + + <chapter id="Bv9ARM.ch02"> + <title><acronym>BIND</acronym> Resource Requirements</title> + + <sect1> + <title>Hardware requirements</title> + + <para> + <acronym>DNS</acronym> hardware requirements have + traditionally been quite modest. + For many installations, servers that have been pensioned off from + active duty have performed admirably as <acronym>DNS</acronym> servers. + </para> + <para> + The DNSSEC features of <acronym>BIND</acronym> 9 + may prove to be quite + CPU intensive however, so organizations that make heavy use of these + features may wish to consider larger systems for these applications. + <acronym>BIND</acronym> 9 is fully multithreaded, allowing + full utilization of + multiprocessor systems for installations that need it. + </para> + </sect1> + <sect1> + <title>CPU Requirements</title> + <para> + CPU requirements for <acronym>BIND</acronym> 9 range from + i486-class machines + for serving of static zones without caching, to enterprise-class + machines if you intend to process many dynamic updates and DNSSEC + signed zones, serving many thousands of queries per second. + </para> + </sect1> + + <sect1> + <title>Memory Requirements</title> + <para> + The memory of the server has to be large enough to fit the + cache and zones loaded off disk. The <command>max-cache-size</command> + option can be used to limit the amount of memory used by the cache, + at the expense of reducing cache hit rates and causing more <acronym>DNS</acronym> + traffic. + Additionally, if additional section caching + (<xref linkend="acache"/>) is enabled, + the <command>max-acache-size</command> option can be used to + limit the amount + of memory used by the mechanism. + It is still good practice to have enough memory to load + all zone and cache data into memory — unfortunately, the best + way + to determine this for a given installation is to watch the name server + in operation. After a few weeks the server process should reach + a relatively stable size where entries are expiring from the cache as + fast as they are being inserted. + </para> + <!-- + - Add something here about leaving overhead for attacks? + - How much overhead? Percentage? + --> + </sect1> + + <sect1> + <title>Name Server Intensive Environment Issues</title> + <para> + For name server intensive environments, there are two alternative + configurations that may be used. The first is where clients and + any second-level internal name servers query a main name server, which + has enough memory to build a large cache. This approach minimizes + the bandwidth used by external name lookups. The second alternative + is to set up second-level internal name servers to make queries + independently. + In this configuration, none of the individual machines needs to + have as much memory or CPU power as in the first alternative, but + this has the disadvantage of making many more external queries, + as none of the name servers share their cached data. + </para> + </sect1> + + <sect1> + <title>Supported Operating Systems</title> + <para> + ISC <acronym>BIND</acronym> 9 compiles and runs on a large + number + of Unix-like operating system and on NT-derived versions of + Microsoft Windows such as Windows 2000 and Windows XP. For an + up-to-date + list of supported systems, see the README file in the top level + directory + of the BIND 9 source distribution. + </para> + </sect1> + </chapter> + + <chapter id="Bv9ARM.ch03"> + <title>Name Server Configuration</title> + <para> + In this section we provide some suggested configurations along + with guidelines for their use. We suggest reasonable values for + certain option settings. + </para> + + <sect1 id="sample_configuration"> + <title>Sample Configurations</title> + <sect2> + <title>A Caching-only Name Server</title> + <para> + The following sample configuration is appropriate for a caching-only + name server for use by clients internal to a corporation. All + queries + from outside clients are refused using the <command>allow-query</command> + option. Alternatively, the same effect could be achieved using + suitable + firewall rules. + </para> <programlisting> // Two corporate subnets we wish to allow queries from. @@ -470,17 +685,21 @@ zone "0.0.127.in-addr.arpa" { notify no; }; </programlisting> -</sect2> -<sect2> -<title>An Authoritative-only Name Server</title> -<para>This sample configuration is for an authoritative-only server -that is the master server for "<filename>example.com</filename>" -and a slave for the subdomain "<filename>eng.example.com</filename>".</para> + </sect2> + + <sect2> + <title>An Authoritative-only Name Server</title> + <para> + This sample configuration is for an authoritative-only server + that is the master server for "<filename>example.com</filename>" + and a slave for the subdomain "<filename>eng.example.com</filename>". + </para> <programlisting> options { directory "/etc/namedb"; // Working directory + allow-query-cache { none; }; // Do not allow access to cache allow-query { any; }; // This is the default recursion no; // Do not provide recursive service }; @@ -509,415 +728,743 @@ zone "eng.example.com" { masters { 192.168.4.12; }; }; </programlisting> -</sect2> -</sect1> - -<sect1> -<title>Load Balancing</title> - -<para>A primitive form of load balancing can be achieved in -the <acronym>DNS</acronym> by using multiple A records for one name.</para> - -<para>For example, if you have three WWW servers with network addresses -of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the -following means that clients will connect to each machine one third -of the time:</para> - -<informaltable colsep = "0" rowsep = "0"> -<tgroup cols = "5" colsep = "0" rowsep = "0" tgroupstyle = "2Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.875in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "0.500in"/> -<colspec colname = "3" colnum = "3" colsep = "0" colwidth = "0.750in"/> -<colspec colname = "4" colnum = "4" colsep = "0" colwidth = "0.750in"/> -<colspec colname = "5" colnum = "5" colsep = "0" colwidth = "2.028in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para>Name</para></entry> -<entry colname = "2"><para>TTL</para></entry> -<entry colname = "3"><para>CLASS</para></entry> -<entry colname = "4"><para>TYPE</para></entry> -<entry colname = "5"><para>Resource Record (RR) Data</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><literal>www</literal></para></entry> -<entry colname = "2"><para><literal>600</literal></para></entry> -<entry colname = "3"><para><literal>IN</literal></para></entry> -<entry colname = "4"><para><literal>A</literal></para></entry> -<entry colname = "5"><para><literal>10.0.0.1</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para><literal>600</literal></para></entry> -<entry colname = "3"><para><literal>IN</literal></para></entry> -<entry colname = "4"><para><literal>A</literal></para></entry> -<entry colname = "5"><para><literal>10.0.0.2</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para><literal>600</literal></para></entry> -<entry colname = "3"><para><literal>IN</literal></para></entry> -<entry colname = "4"><para><literal>A</literal></para></entry> -<entry colname = "5"><para><literal>10.0.0.3</literal></para></entry> - </row> - </tbody> - </tgroup> - </informaltable> - <para>When a resolver queries for these records, <acronym>BIND</acronym> will rotate - them and respond to the query with the records in a different - order. In the example above, clients will randomly receive - records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients - will use the first record returned and discard the rest.</para> - <para>For more detail on ordering responses, check the - <command>rrset-order</command> substatement in the - <command>options</command> statement, see - <xref endterm="rrset_ordering_title" linkend="rrset_ordering"/>. - This substatement is not supported in - <acronym>BIND</acronym> 9, and only the ordering scheme described above is - available.</para> - -</sect1> - -<sect1> -<title>Name Server Operations</title> - -<sect2> -<title>Tools for Use With the Name Server Daemon</title> -<para>There are several indispensable diagnostic, administrative -and monitoring tools available to the system administrator for controlling -and debugging the name server daemon. We describe several in this -section </para> -<sect3 id="diagnostic_tools"> -<title>Diagnostic Tools</title> -<para>The <command>dig</command>, <command>host</command>, and -<command>nslookup</command> programs are all command line tools -for manually querying name servers. They differ in style and -output format. -</para> - -<variablelist> -<varlistentry> -<term id="dig"><command>dig</command></term> -<listitem> -<para>The domain information groper (<command>dig</command>) -is the most versatile and complete of these lookup tools. -It has two modes: simple interactive -mode for a single query, and batch mode which executes a query for -each in a list of several query lines. All query options are accessible -from the command line.</para> -<cmdsynopsis label="Usage"> - <command>dig</command> - <arg>@<replaceable>server</replaceable></arg> - <arg choice="plain"><replaceable>domain</replaceable></arg> - <arg><replaceable>query-type</replaceable></arg> - <arg><replaceable>query-class</replaceable></arg> - <arg>+<replaceable>query-option</replaceable></arg> - <arg>-<replaceable>dig-option</replaceable></arg> - <arg>%<replaceable>comment</replaceable></arg> -</cmdsynopsis> -<para>The usual simple use of dig will take the form</para> -<simpara><command>dig @server domain query-type query-class</command></simpara> -<para>For more information and a list of available commands and -options, see the <command>dig</command> man page.</para> -</listitem> -</varlistentry> - -<varlistentry> -<term><command>host</command></term> -<listitem> -<para>The <command>host</command> utility emphasizes simplicity -and ease of use. By default, it converts -between host names and Internet addresses, but its functionality -can be extended with the use of options.</para> -<cmdsynopsis label="Usage"> - <command>host</command> - <arg>-aCdlrTwv</arg> - <arg>-c <replaceable>class</replaceable></arg> - <arg>-N <replaceable>ndots</replaceable></arg> - <arg>-t <replaceable>type</replaceable></arg> - <arg>-W <replaceable>timeout</replaceable></arg> - <arg>-R <replaceable>retries</replaceable></arg> - <arg choice="plain"><replaceable>hostname</replaceable></arg> - <arg><replaceable>server</replaceable></arg> -</cmdsynopsis> -<para>For more information and a list of available commands and -options, see the <command>host</command> man page.</para> -</listitem> -</varlistentry> - -<varlistentry> -<term><command>nslookup</command></term> -<listitem> -<para><command>nslookup</command> has two modes: interactive -and non-interactive. Interactive mode allows the user to query name servers -for information about various hosts and domains or to print a list -of hosts in a domain. Non-interactive mode is used to print just -the name and requested information for a host or domain.</para> -<cmdsynopsis label="Usage"> - <command>nslookup</command> - <arg rep="repeat">-option</arg> - <group> - <arg><replaceable>host-to-find</replaceable></arg> - <arg>- <arg>server</arg></arg> - </group> -</cmdsynopsis> -<para>Interactive mode is entered when no arguments are given (the -default name server will be used) or when the first argument is a -hyphen (`-') and the second argument is the host name or Internet address -of a name server.</para> -<para>Non-interactive mode is used when the name or Internet address -of the host to be looked up is given as the first argument. The -optional second argument specifies the host name or address of a name server.</para> -<para>Due to its arcane user interface and frequently inconsistent -behavior, we do not recommend the use of <command>nslookup</command>. -Use <command>dig</command> instead.</para> -</listitem> - -</varlistentry> -</variablelist> -</sect3> - -<sect3 id="admin_tools"> - <title>Administrative Tools</title> - <para>Administrative tools play an integral part in the management -of a server.</para> - <variablelist> - <varlistentry id="named-checkconf" xreflabel="Named Configuration Checking application"> - <term><command>named-checkconf</command></term> - <listitem> - <para>The <command>named-checkconf</command> program - checks the syntax of a <filename>named.conf</filename> file.</para> - <cmdsynopsis label="Usage"> - <command>named-checkconf</command> - <arg>-jvz</arg> - <arg>-t <replaceable>directory</replaceable></arg> - <arg><replaceable>filename</replaceable></arg> - </cmdsynopsis> - </listitem> - </varlistentry> - <varlistentry id="named-checkzone" xreflabel="Zone Checking application"> - <term><command>named-checkzone</command></term> - <listitem> - <para>The <command>named-checkzone</command> program checks a master file for - syntax and consistency.</para> - <cmdsynopsis label="Usage"> - <command>named-checkzone</command> - <arg>-djqvD</arg> - <arg>-c <replaceable>class</replaceable></arg> - <arg>-o <replaceable>output</replaceable></arg> - <arg>-t <replaceable>directory</replaceable></arg> - <arg>-w <replaceable>directory</replaceable></arg> - <arg>-k <replaceable>(ignore|warn|fail)</replaceable></arg> - <arg>-n <replaceable>(ignore|warn|fail)</replaceable></arg> - <arg choice="plain"><replaceable>zone</replaceable></arg> - <arg><replaceable>filename</replaceable></arg> - </cmdsynopsis> - </listitem> - </varlistentry> - <varlistentry id="rndc" xreflabel="Remote Name Daemon Control application"> - <term><command>rndc</command></term> - <listitem> - <para>The remote name daemon control - (<command>rndc</command>) program allows the system - administrator to control the operation of a name server. - If you run <command>rndc</command> without any options - it will display a usage message as follows:</para> - <cmdsynopsis label="Usage"> - <command>rndc</command> - <arg>-c <replaceable>config</replaceable></arg> - <arg>-s <replaceable>server</replaceable></arg> - <arg>-p <replaceable>port</replaceable></arg> - <arg>-y <replaceable>key</replaceable></arg> - <arg choice="plain"><replaceable>command</replaceable></arg> - <arg rep="repeat"><replaceable>command</replaceable></arg> - </cmdsynopsis> - <para>The <command>command</command> is one of the following:</para> - -<variablelist> - - <varlistentry><term><userinput>reload</userinput></term> - <listitem><para>Reload configuration file and zones.</para></listitem> - </varlistentry> - - <varlistentry><term><userinput>reload <replaceable>zone</replaceable> - <optional><replaceable>class</replaceable> - <optional><replaceable>view</replaceable></optional></optional></userinput></term> - <listitem><para>Reload the given zone.</para></listitem> - </varlistentry> - <varlistentry><term><userinput>refresh <replaceable>zone</replaceable> - <optional><replaceable>class</replaceable> + </sect2> + </sect1> + + <sect1> + <title>Load Balancing</title> + <!-- + - Add explanation of why load balancing is fragile at best + - and completely pointless in the general case. + --> + + <para> + A primitive form of load balancing can be achieved in + the <acronym>DNS</acronym> by using multiple records + (such as multiple A records) for one name. + </para> + + <para> + For example, if you have three WWW servers with network addresses + of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the + following means that clients will connect to each machine one third + of the time: + </para> + + <informaltable colsep="0" rowsep="0"> + <tgroup cols="5" colsep="0" rowsep="0" tgroupstyle="2Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="0.875in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="0.500in"/> + <colspec colname="3" colnum="3" colsep="0" colwidth="0.750in"/> + <colspec colname="4" colnum="4" colsep="0" colwidth="0.750in"/> + <colspec colname="5" colnum="5" colsep="0" colwidth="2.028in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + Name + </para> + </entry> + <entry colname="2"> + <para> + TTL + </para> + </entry> + <entry colname="3"> + <para> + CLASS + </para> + </entry> + <entry colname="4"> + <para> + TYPE + </para> + </entry> + <entry colname="5"> + <para> + Resource Record (RR) Data + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>www</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>600</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>IN</literal> + </para> + </entry> + <entry colname="4"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="5"> + <para> + <literal>10.0.0.1</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para/> + </entry> + <entry colname="2"> + <para> + <literal>600</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>IN</literal> + </para> + </entry> + <entry colname="4"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="5"> + <para> + <literal>10.0.0.2</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para/> + </entry> + <entry colname="2"> + <para> + <literal>600</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>IN</literal> + </para> + </entry> + <entry colname="4"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="5"> + <para> + <literal>10.0.0.3</literal> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + When a resolver queries for these records, <acronym>BIND</acronym> will rotate + them and respond to the query with the records in a different + order. In the example above, clients will randomly receive + records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients + will use the first record returned and discard the rest. + </para> + <para> + For more detail on ordering responses, check the + <command>rrset-order</command> substatement in the + <command>options</command> statement, see + <xref endterm="rrset_ordering_title" linkend="rrset_ordering"/>. + </para> + + </sect1> + + <sect1> + <title>Name Server Operations</title> + + <sect2> + <title>Tools for Use With the Name Server Daemon</title> + <para> + This section describes several indispensable diagnostic, + administrative and monitoring tools available to the system + administrator for controlling and debugging the name server + daemon. + </para> + <sect3 id="diagnostic_tools"> + <title>Diagnostic Tools</title> + <para> + The <command>dig</command>, <command>host</command>, and + <command>nslookup</command> programs are all command + line tools + for manually querying name servers. They differ in style and + output format. + </para> + + <variablelist> + <varlistentry> + <term id="dig"><command>dig</command></term> + <listitem> + <para> + The domain information groper (<command>dig</command>) + is the most versatile and complete of these lookup tools. + It has two modes: simple interactive + mode for a single query, and batch mode which executes a + query for + each in a list of several query lines. All query options are + accessible + from the command line. + </para> + <cmdsynopsis label="Usage"> + <command>dig</command> + <arg>@<replaceable>server</replaceable></arg> + <arg choice="plain"><replaceable>domain</replaceable></arg> + <arg><replaceable>query-type</replaceable></arg> + <arg><replaceable>query-class</replaceable></arg> + <arg>+<replaceable>query-option</replaceable></arg> + <arg>-<replaceable>dig-option</replaceable></arg> + <arg>%<replaceable>comment</replaceable></arg> + </cmdsynopsis> + <para> + The usual simple use of dig will take the form + </para> + <simpara> + <command>dig @server domain query-type query-class</command> + </simpara> + <para> + For more information and a list of available commands and + options, see the <command>dig</command> man + page. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>host</command></term> + <listitem> + <para> + The <command>host</command> utility emphasizes + simplicity + and ease of use. By default, it converts + between host names and Internet addresses, but its + functionality + can be extended with the use of options. + </para> + <cmdsynopsis label="Usage"> + <command>host</command> + <arg>-aCdlnrsTwv</arg> + <arg>-c <replaceable>class</replaceable></arg> + <arg>-N <replaceable>ndots</replaceable></arg> + <arg>-t <replaceable>type</replaceable></arg> + <arg>-W <replaceable>timeout</replaceable></arg> + <arg>-R <replaceable>retries</replaceable></arg> + <arg>-m <replaceable>flag</replaceable></arg> + <arg>-4</arg> + <arg>-6</arg> + <arg choice="plain"><replaceable>hostname</replaceable></arg> + <arg><replaceable>server</replaceable></arg> + </cmdsynopsis> + <para> + For more information and a list of available commands and + options, see the <command>host</command> man + page. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>nslookup</command></term> + <listitem> + <para><command>nslookup</command> + has two modes: interactive and + non-interactive. Interactive mode allows the user to + query name servers for information about various + hosts and domains or to print a list of hosts in a + domain. Non-interactive mode is used to print just + the name and requested information for a host or + domain. + </para> + <cmdsynopsis label="Usage"> + <command>nslookup</command> + <arg rep="repeat">-option</arg> + <group> + <arg><replaceable>host-to-find</replaceable></arg> + <arg>- <arg>server</arg></arg> + </group> + </cmdsynopsis> + <para> + Interactive mode is entered when no arguments are given (the + default name server will be used) or when the first argument + is a + hyphen (`-') and the second argument is the host name or + Internet address + of a name server. + </para> + <para> + Non-interactive mode is used when the name or Internet + address + of the host to be looked up is given as the first argument. + The + optional second argument specifies the host name or address + of a name server. + </para> + <para> + Due to its arcane user interface and frequently inconsistent + behavior, we do not recommend the use of <command>nslookup</command>. + Use <command>dig</command> instead. + </para> + </listitem> + + </varlistentry> + </variablelist> + </sect3> + + <sect3 id="admin_tools"> + <title>Administrative Tools</title> + <para> + Administrative tools play an integral part in the management + of a server. + </para> + <variablelist> + <varlistentry id="named-checkconf" xreflabel="Named Configuration Checking application"> + + <term><command>named-checkconf</command></term> + <listitem> + <para> + The <command>named-checkconf</command> program + checks the syntax of a <filename>named.conf</filename> file. + </para> + <cmdsynopsis label="Usage"> + <command>named-checkconf</command> + <arg>-jvz</arg> + <arg>-t <replaceable>directory</replaceable></arg> + <arg><replaceable>filename</replaceable></arg> + </cmdsynopsis> + </listitem> + </varlistentry> + <varlistentry id="named-checkzone" xreflabel="Zone Checking application"> + + <term><command>named-checkzone</command></term> + <listitem> + <para> + The <command>named-checkzone</command> program + checks a master file for + syntax and consistency. + </para> + <cmdsynopsis label="Usage"> + <command>named-checkzone</command> + <arg>-djqvD</arg> + <arg>-c <replaceable>class</replaceable></arg> + <arg>-o <replaceable>output</replaceable></arg> + <arg>-t <replaceable>directory</replaceable></arg> + <arg>-w <replaceable>directory</replaceable></arg> + <arg>-k <replaceable>(ignore|warn|fail)</replaceable></arg> + <arg>-n <replaceable>(ignore|warn|fail)</replaceable></arg> + <arg>-W <replaceable>(ignore|warn)</replaceable></arg> + <arg choice="plain"><replaceable>zone</replaceable></arg> + <arg><replaceable>filename</replaceable></arg> + </cmdsynopsis> + </listitem> + </varlistentry> + <varlistentry id="named-compilezone" xreflabel="Zone Compilation aplication"> + <term><command>named-compilezone</command></term> + <listitem> + <para> + Similar to <command>named-checkzone,</command> but + it always dumps the zone content to a specified file + (typically in a different format). + </para> + </listitem> + </varlistentry> + <varlistentry id="rndc" xreflabel="Remote Name Daemon Control application"> + + <term><command>rndc</command></term> + <listitem> + <para> + The remote name daemon control + (<command>rndc</command>) program allows the + system + administrator to control the operation of a name server. + Since <acronym>BIND</acronym> 9.2, <command>rndc</command> + supports all the commands of the BIND 8 <command>ndc</command> + utility except <command>ndc start</command> and + <command>ndc restart</command>, which were also + not supported in <command>ndc</command>'s + channel mode. + If you run <command>rndc</command> without any + options + it will display a usage message as follows: + </para> + <cmdsynopsis label="Usage"> + <command>rndc</command> + <arg>-c <replaceable>config</replaceable></arg> + <arg>-s <replaceable>server</replaceable></arg> + <arg>-p <replaceable>port</replaceable></arg> + <arg>-y <replaceable>key</replaceable></arg> + <arg choice="plain"><replaceable>command</replaceable></arg> + <arg rep="repeat"><replaceable>command</replaceable></arg> + </cmdsynopsis> + <para>The <command>command</command> + is one of the following: + </para> + + <variablelist> + + <varlistentry> + <term><userinput>reload</userinput></term> + <listitem> + <para> + Reload configuration file and zones. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>reload <replaceable>zone</replaceable> + <optional><replaceable>class</replaceable> + <optional><replaceable>view</replaceable></optional></optional></userinput></term> + <listitem> + <para> + Reload the given zone. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>refresh <replaceable>zone</replaceable> + <optional><replaceable>class</replaceable> <optional><replaceable>view</replaceable></optional></optional></userinput></term> - <listitem><para>Schedule zone maintenance for the given zone.</para></listitem> - </varlistentry> + <listitem> + <para> + Schedule zone maintenance for the given zone. + </para> + </listitem> + </varlistentry> - <varlistentry><term><userinput>retransfer <replaceable>zone</replaceable> - <optional><replaceable>class</replaceable> + <varlistentry> + <term><userinput>retransfer <replaceable>zone</replaceable> + + <optional><replaceable>class</replaceable> <optional><replaceable>view</replaceable></optional></optional></userinput></term> - <listitem><para>Retransfer the given zone from the master.</para></listitem> - </varlistentry> + <listitem> + <para> + Retransfer the given zone from the master. + </para> + </listitem> + </varlistentry> - <varlistentry> <term><userinput>freeze <optional><replaceable>zone</replaceable> + <varlistentry> + + <term><userinput>freeze + <optional><replaceable>zone</replaceable> <optional><replaceable>class</replaceable> <optional><replaceable>view</replaceable></optional></optional></optional></userinput></term> - <listitem><para>Suspend updates to a dynamic zone. If no zone is specified, - then all zones are suspended. This allows manual - edits to be made to a zone normally updated by dynamic update. It - also causes changes in the journal file to be synced into the master - and the journal file to be removed. All dynamic update attempts will - be refused while the zone is frozen.</para></listitem> - </varlistentry> - - <varlistentry><term><userinput>thaw <optional><replaceable>zone</replaceable> + <listitem> + <para> + Suspend updates to a dynamic zone. If no zone is + specified, + then all zones are suspended. This allows manual + edits to be made to a zone normally updated by dynamic + update. It + also causes changes in the journal file to be synced + into the master + and the journal file to be removed. All dynamic + update attempts will + be refused while the zone is frozen. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>thaw + <optional><replaceable>zone</replaceable> <optional><replaceable>class</replaceable> <optional><replaceable>view</replaceable></optional></optional></optional></userinput></term> - <listitem><para>Enable updates to a frozen dynamic zone. If no zone is - specified, then all frozen zones are enabled. This causes - the server to reload the zone from disk, and re-enables dynamic updates - after the load has completed. After a zone is thawed, dynamic updates - will no longer be refused.</para></listitem> - </varlistentry> - - <varlistentry><term><userinput>reconfig</userinput></term> - <listitem><para>Reload the configuration file and load new zones, - but do not reload existing zone files even if they have changed. - This is faster than a full <command>reload</command> when there - is a large number of zones because it avoids the need to examine the - modification times of the zones files. - </para></listitem> - </varlistentry> - - <varlistentry><term><userinput>stats</userinput></term> - <listitem><para>Write server statistics to the statistics file.</para></listitem> - </varlistentry> - - <varlistentry><term><userinput>querylog</userinput></term> - <listitem><para>Toggle query logging. Query logging can also be enabled - by explicitly directing the <command>queries</command> - <command>category</command> to a <command>channel</command> in the - <command>logging</command> section of - <filename>named.conf</filename>.</para></listitem></varlistentry> - - <varlistentry><term><userinput>dumpdb <optional>-all|-cache|-zone</optional> <optional><replaceable>view ...</replaceable></optional></userinput></term> - <listitem><para>Dump the server's caches (default) and / or zones to the - dump file for the specified views. If no view is specified, all - views are dumped.</para></listitem></varlistentry> - - <varlistentry><term><userinput>stop <optional>-p</optional></userinput></term> - <listitem><para>Stop the server, making sure any recent changes - made through dynamic update or IXFR are first saved to the master files - of the updated zones. If -p is specified named's process id is returned. - This allows an external process to determine when named had completed stopping.</para></listitem></varlistentry> - - <varlistentry><term><userinput>halt <optional>-p</optional></userinput></term> - <listitem><para>Stop the server immediately. Recent changes - made through dynamic update or IXFR are not saved to the master files, - but will be rolled forward from the journal files when the server - is restarted. If -p is specified named's process id is returned. - This allows an external process to determine when named had completed - stopping.</para></listitem></varlistentry> - - <varlistentry><term><userinput>trace</userinput></term> - <listitem><para>Increment the servers debugging level by one. </para></listitem></varlistentry> - - <varlistentry><term><userinput>trace <replaceable>level</replaceable></userinput></term> - <listitem><para>Sets the server's debugging level to an explicit - value.</para></listitem></varlistentry> - - <varlistentry><term><userinput>notrace</userinput></term> - <listitem><para>Sets the server's debugging level to 0.</para></listitem></varlistentry> - - <varlistentry><term><userinput>flush</userinput></term> - <listitem><para>Flushes the server's cache.</para></listitem></varlistentry> - - <varlistentry><term><userinput>flushname</userinput> <replaceable>name</replaceable></term> - <listitem><para>Flushes the given name from the server's cache.</para></listitem></varlistentry> - - <varlistentry><term><userinput>status</userinput></term> - <listitem><para>Display status of the server. -Note that the number of zones includes the internal <command>bind/CH</command> zone -and the default <command>./IN</command> hint zone if there is not an -explicit root zone configured.</para></listitem></varlistentry> - - <varlistentry><term><userinput>recursing</userinput></term> - <listitem><para>Dump the list of queries named is currently recursing - on. - </para></listitem></varlistentry> - -</variablelist> - -<para>In <acronym>BIND</acronym> 9.2, <command>rndc</command> -supports all the commands of the BIND 8 <command>ndc</command> -utility except <command>ndc start</command> and -<command>ndc restart</command>, which were also -not supported in <command>ndc</command>'s channel mode.</para> - -<para>A configuration file is required, since all -communication with the server is authenticated with -digital signatures that rely on a shared secret, and -there is no way to provide that secret other than with a -configuration file. The default location for the -<command>rndc</command> configuration file is -<filename>/etc/rndc.conf</filename>, but an alternate -location can be specified with the <option>-c</option> -option. If the configuration file is not found, -<command>rndc</command> will also look in -<filename>/etc/rndc.key</filename> (or whatever -<varname>sysconfdir</varname> was defined when -the <acronym>BIND</acronym> build was configured). -The <filename>rndc.key</filename> file is generated by -running <command>rndc-confgen -a</command> as described in -<xref linkend="controls_statement_definition_and_usage"/>.</para> - -<para>The format of the configuration file is similar to -that of <filename>named.conf</filename>, but limited to -only four statements, the <command>options</command>, -<command>key</command>, <command>server</command> and -<command>include</command> -statements. These statements are what associate the -secret keys to the servers with which they are meant to -be shared. The order of statements is not -significant.</para> - -<para>The <command>options</command> statement has three clauses: -<command>default-server</command>, <command>default-key</command>, -and <command>default-port</command>. -<command>default-server</command> takes a -host name or address argument and represents the server that will -be contacted if no <option>-s</option> -option is provided on the command line. -<command>default-key</command> takes -the name of a key as its argument, as defined by a <command>key</command> statement. -<command>default-port</command> specifies the port to which -<command>rndc</command> should connect if no -port is given on the command line or in a -<command>server</command> statement.</para> - -<para>The <command>key</command> statement defines a key to be used -by <command>rndc</command> when authenticating with -<command>named</command>. Its syntax is identical to the -<command>key</command> statement in named.conf. -The keyword <userinput>key</userinput> is -followed by a key name, which must be a valid -domain name, though it need not actually be hierarchical; thus, -a string like "<userinput>rndc_key</userinput>" is a valid name. -The <command>key</command> statement has two clauses: -<command>algorithm</command> and <command>secret</command>. -While the configuration parser will accept any string as the argument -to algorithm, currently only the string "<userinput>hmac-md5</userinput>" -has any meaning. The secret is a base-64 encoded string.</para> - -<para>The <command>server</command> statement associates a key -defined using the <command>key</command> statement with a server. -The keyword <userinput>server</userinput> is followed by a -host name or address. The <command>server</command> statement -has two clauses: <command>key</command> and <command>port</command>. -The <command>key</command> clause specifies the name of the key -to be used when communicating with this server, and the -<command>port</command> clause can be used to -specify the port <command>rndc</command> should connect -to on the server.</para> - -<para>A sample minimal configuration file is as follows:</para> + <listitem> + <para> + Enable updates to a frozen dynamic zone. If no zone + is + specified, then all frozen zones are enabled. This + causes + the server to reload the zone from disk, and + re-enables dynamic updates + after the load has completed. After a zone is thawed, + dynamic updates + will no longer be refused. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>notify <replaceable>zone</replaceable> + <optional><replaceable>class</replaceable> + <optional><replaceable>view</replaceable></optional></optional></userinput></term> + <listitem> + <para> + Resend NOTIFY messages for the zone. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>reconfig</userinput></term> + <listitem> + <para> + Reload the configuration file and load new zones, + but do not reload existing zone files even if they + have changed. + This is faster than a full <command>reload</command> when there + is a large number of zones because it avoids the need + to examine the + modification times of the zones files. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>stats</userinput></term> + <listitem> + <para> + Write server statistics to the statistics file. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>querylog</userinput></term> + <listitem> + <para> + Toggle query logging. Query logging can also be enabled + by explicitly directing the <command>queries</command> + <command>category</command> to a + <command>channel</command> in the + <command>logging</command> section of + <filename>named.conf</filename> or by specifying + <command>querylog yes;</command> in the + <command>options</command> section of + <filename>named.conf</filename>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>dumpdb + <optional>-all|-cache|-zone</optional> + <optional><replaceable>view ...</replaceable></optional></userinput></term> + <listitem> + <para> + Dump the server's caches (default) and/or zones to + the + dump file for the specified views. If no view is + specified, all + views are dumped. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>stop <optional>-p</optional></userinput></term> + <listitem> + <para> + Stop the server, making sure any recent changes + made through dynamic update or IXFR are first saved to + the master files of the updated zones. + If -p is specified named's process id is returned. + This allows an external process to determine when named + had completed stopping. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>halt <optional>-p</optional></userinput></term> + <listitem> + <para> + Stop the server immediately. Recent changes + made through dynamic update or IXFR are not saved to + the master files, but will be rolled forward from the + journal files when the server is restarted. + If -p is specified named's process id is returned. + This allows an external process to determine when named + had completed halting. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>trace</userinput></term> + <listitem> + <para> + Increment the servers debugging level by one. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>trace <replaceable>level</replaceable></userinput></term> + <listitem> + <para> + Sets the server's debugging level to an explicit + value. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>notrace</userinput></term> + <listitem> + <para> + Sets the server's debugging level to 0. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>flush</userinput></term> + <listitem> + <para> + Flushes the server's cache. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>flushname</userinput> <replaceable>name</replaceable></term> + <listitem> + <para> + Flushes the given name from the server's cache. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>status</userinput></term> + <listitem> + <para> + Display status of the server. + Note that the number of zones includes the internal <command>bind/CH</command> zone + and the default <command>./IN</command> + hint zone if there is not an + explicit root zone configured. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><userinput>recursing</userinput></term> + <listitem> + <para> + Dump the list of queries named is currently recursing + on. + </para> + </listitem> + </varlistentry> + + </variablelist> + + <para> + A configuration file is required, since all + communication with the server is authenticated with + digital signatures that rely on a shared secret, and + there is no way to provide that secret other than with a + configuration file. The default location for the + <command>rndc</command> configuration file is + <filename>/etc/rndc.conf</filename>, but an + alternate + location can be specified with the <option>-c</option> + option. If the configuration file is not found, + <command>rndc</command> will also look in + <filename>/etc/rndc.key</filename> (or whatever + <varname>sysconfdir</varname> was defined when + the <acronym>BIND</acronym> build was + configured). + The <filename>rndc.key</filename> file is + generated by + running <command>rndc-confgen -a</command> as + described in + <xref linkend="controls_statement_definition_and_usage"/>. + </para> + + <para> + The format of the configuration file is similar to + that of <filename>named.conf</filename>, but + limited to + only four statements, the <command>options</command>, + <command>key</command>, <command>server</command> and + <command>include</command> + statements. These statements are what associate the + secret keys to the servers with which they are meant to + be shared. The order of statements is not + significant. + </para> + + <para> + The <command>options</command> statement has + three clauses: + <command>default-server</command>, <command>default-key</command>, + and <command>default-port</command>. + <command>default-server</command> takes a + host name or address argument and represents the server + that will + be contacted if no <option>-s</option> + option is provided on the command line. + <command>default-key</command> takes + the name of a key as its argument, as defined by a <command>key</command> statement. + <command>default-port</command> specifies the + port to which + <command>rndc</command> should connect if no + port is given on the command line or in a + <command>server</command> statement. + </para> + + <para> + The <command>key</command> statement defines a + key to be used + by <command>rndc</command> when authenticating + with + <command>named</command>. Its syntax is + identical to the + <command>key</command> statement in named.conf. + The keyword <userinput>key</userinput> is + followed by a key name, which must be a valid + domain name, though it need not actually be hierarchical; + thus, + a string like "<userinput>rndc_key</userinput>" is a valid + name. + The <command>key</command> statement has two + clauses: + <command>algorithm</command> and <command>secret</command>. + While the configuration parser will accept any string as the + argument + to algorithm, currently only the string "<userinput>hmac-md5</userinput>" + has any meaning. The secret is a base-64 encoded string + as specified in RFC 3548. + </para> + + <para> + The <command>server</command> statement + associates a key + defined using the <command>key</command> + statement with a server. + The keyword <userinput>server</userinput> is followed by a + host name or address. The <command>server</command> statement + has two clauses: <command>key</command> and <command>port</command>. + The <command>key</command> clause specifies the + name of the key + to be used when communicating with this server, and the + <command>port</command> clause can be used to + specify the port <command>rndc</command> should + connect + to on the server. + </para> + + <para> + A sample minimal configuration file is as follows: + </para> + <programlisting> key rndc_key { algorithm "hmac-md5"; @@ -929,275 +1476,417 @@ options { }; </programlisting> -<para>This file, if installed as <filename>/etc/rndc.conf</filename>, -would allow the command:</para> + <para> + This file, if installed as <filename>/etc/rndc.conf</filename>, + would allow the command: + </para> + + <para> + <prompt>$ </prompt><userinput>rndc reload</userinput> + </para> -<para><prompt>$ </prompt><userinput>rndc reload</userinput></para> + <para> + to connect to 127.0.0.1 port 953 and cause the name server + to reload, if a name server on the local machine were + running with + following controls statements: + </para> -<para>to connect to 127.0.0.1 port 953 and cause the name server -to reload, if a name server on the local machine were running with -following controls statements:</para> <programlisting> controls { inet 127.0.0.1 allow { localhost; } keys { rndc_key; }; }; </programlisting> -<para>and it had an identical key statement for -<literal>rndc_key</literal>.</para> - -<para>Running the <command>rndc-confgen</command> program will -conveniently create a <filename>rndc.conf</filename> -file for you, and also display the -corresponding <command>controls</command> statement that you need to -add to <filename>named.conf</filename>. Alternatively, -you can run <command>rndc-confgen -a</command> to set up -a <filename>rndc.key</filename> file and not modify -<filename>named.conf</filename> at all. -</para> - </listitem> - </varlistentry> - </variablelist> + <para> + and it had an identical key statement for + <literal>rndc_key</literal>. + </para> + + <para> + Running the <command>rndc-confgen</command> + program will + conveniently create a <filename>rndc.conf</filename> + file for you, and also display the + corresponding <command>controls</command> + statement that you need to + add to <filename>named.conf</filename>. + Alternatively, + you can run <command>rndc-confgen -a</command> + to set up + a <filename>rndc.key</filename> file and not + modify + <filename>named.conf</filename> at all. + </para> - </sect3> - </sect2> -<sect2> - -<title>Signals</title> -<para>Certain UNIX signals cause the name server to take specific -actions, as described in the following table. These signals can -be sent using the <command>kill</command> command.</para> -<informaltable frame = "all" ><tgroup cols = "2"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.125in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "4.000in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><command>SIGHUP</command></para></entry> -<entry colname = "2"><para>Causes the server to read <filename>named.conf</filename> and -reload the database. </para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>SIGTERM</command></para></entry> -<entry colname = "2"><para>Causes the server to clean up and exit.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"> -<para><command>SIGINT</command></para> -</entry> - <entry colname = "2"><para>Causes the server to clean up and exit.</para></entry> - </row> - </tbody> - </tgroup> - </informaltable> - </sect2> - </sect1> + </listitem> + </varlistentry> + </variablelist> + + </sect3> + </sect2> + <sect2> + + <title>Signals</title> + <para> + Certain UNIX signals cause the name server to take specific + actions, as described in the following table. These signals can + be sent using the <command>kill</command> command. + </para> + <informaltable frame="all"> + <tgroup cols="2"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.125in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="4.000in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para><command>SIGHUP</command></para> + </entry> + <entry colname="2"> + <para> + Causes the server to read <filename>named.conf</filename> and + reload the database. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>SIGTERM</command></para> + </entry> + <entry colname="2"> + <para> + Causes the server to clean up and exit. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>SIGINT</command></para> + </entry> + <entry colname="2"> + <para> + Causes the server to clean up and exit. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + </sect2> + </sect1> </chapter> -<chapter id="Bv9ARM.ch04"> -<title>Advanced DNS Features</title> - -<sect1 id="notify"> - -<title>Notify</title> -<para><acronym>DNS</acronym> NOTIFY is a mechanism that allows master -servers to notify their slave servers of changes to a zone's data. In -response to a <command>NOTIFY</command> from a master server, the -slave will check to see that its version of the zone is the -current version and, if not, initiate a zone transfer.</para> - -<para><acronym>DNS</acronym> -For more information about -<command>NOTIFY</command>, see the description of the -<command>notify</command> option in <xref linkend="boolean_options"/> and -the description of the zone option <command>also-notify</command> in -<xref linkend="zone_transfers"/>. The <command>NOTIFY</command> -protocol is specified in RFC 1996. -</para> - -</sect1> - -<sect1 id="dynamic_update"> -<title>Dynamic Update</title> - - <para>Dynamic Update is a method for adding, replacing or deleting - records in a master server by sending it a special form of DNS - messages. The format and meaning of these messages is specified - in RFC 2136.</para> - - <para>Dynamic update is enabled on a zone-by-zone basis, by - including an <command>allow-update</command> or - <command>update-policy</command> clause in the - <command>zone</command> statement.</para> - - <para>Updating of secure zones (zones using DNSSEC) follows - RFC 3007: RRSIG and NSEC records affected by updates are automatically - regenerated by the server using an online zone key. - Update authorization is based - on transaction signatures and an explicit server policy.</para> - - <sect2 id="journal"> - <title>The journal file</title> - - <para>All changes made to a zone using dynamic update are stored in the - zone's journal file. This file is automatically created by the - server when the first dynamic update takes place. The name of - the journal file is formed by appending the - extension <filename>.jnl</filename> to the - name of the corresponding zone file. The journal file is in a - binary format and should not be edited manually.</para> - - <para>The server will also occasionally write ("dump") - the complete contents of the updated zone to its zone file. - This is not done immediately after - each dynamic update, because that would be too slow when a large - zone is updated frequently. Instead, the dump is delayed by - up to 15 minutes, allowing additional updates to take place.</para> - - <para>When a server is restarted after a shutdown or crash, it will replay - the journal file to incorporate into the zone any updates that took - place after the last zone dump.</para> - - <para>Changes that result from incoming incremental zone transfers are also - journalled in a similar way.</para> - - <para>The zone files of dynamic zones cannot normally be edited by - hand because they are not guaranteed to contain the most recent - dynamic changes — those are only in the journal file. - The only way to ensure that the zone file of a dynamic zone - is up to date is to run <command>rndc stop</command>.</para> - - <para>If you have to make changes to a dynamic zone - manually, the following procedure will work: Disable dynamic updates - to the zone using - <command>rndc freeze <replaceable>zone</replaceable></command>. - This will also remove the zone's <filename>.jnl</filename> file - and update the master file. Edit the zone file. Run - <command>rndc thaw <replaceable>zone</replaceable></command> - to reload the changed zone and re-enable dynamic updates.</para> - - </sect2> - -</sect1> - -<sect1 id="incremental_zone_transfers"> -<title>Incremental Zone Transfers (IXFR)</title> - -<para>The incremental zone transfer (IXFR) protocol is a way for -slave servers to transfer only changed data, instead of having to -transfer the entire zone. The IXFR protocol is specified in RFC -1995. See <xref linkend="proposed_standards"/>.</para> - -<para>When acting as a master, <acronym>BIND</acronym> 9 -supports IXFR for those zones -where the necessary change history information is available. These -include master zones maintained by dynamic update and slave zones -whose data was obtained by IXFR. For manually maintained master -zones, and for slave zones obtained by performing a full zone -transfer (AXFR), IXFR is supported only if the option -<command>ixfr-from-differences</command> is set -to <userinput>yes</userinput>. -</para> - -<para>When acting as a slave, <acronym>BIND</acronym> 9 will -attempt to use IXFR unless -it is explicitly disabled. For more information about disabling -IXFR, see the description of the <command>request-ixfr</command> clause -of the <command>server</command> statement.</para> -</sect1> - -<sect1><title>Split DNS</title> -<para>Setting up different views, or visibility, of the DNS space to -internal and external resolvers is usually referred to as a <emphasis>Split -DNS</emphasis> setup. There are several reasons an organization -would want to set up its DNS this way.</para> -<para>One common reason for setting up a DNS system this way is -to hide "internal" DNS information from "external" clients on the -Internet. There is some debate as to whether or not this is actually useful. -Internal DNS information leaks out in many ways (via email headers, -for example) and most savvy "attackers" can find the information -they need using other means.</para> -<para>Another common reason for setting up a Split DNS system is -to allow internal networks that are behind filters or in RFC 1918 -space (reserved IP space, as documented in RFC 1918) to resolve DNS -on the Internet. Split DNS can also be used to allow mail from outside -back in to the internal network.</para> -<para>Here is an example of a split DNS setup:</para> -<para>Let's say a company named <emphasis>Example, Inc.</emphasis> -(<literal>example.com</literal>) -has several corporate sites that have an internal network with reserved -Internet Protocol (IP) space and an external demilitarized zone (DMZ), -or "outside" section of a network, that is available to the public.</para> -<para><emphasis>Example, Inc.</emphasis> wants its internal clients -to be able to resolve external hostnames and to exchange mail with -people on the outside. The company also wants its internal resolvers -to have access to certain internal-only zones that are not available -at all outside of the internal network.</para> -<para>In order to accomplish this, the company will set up two sets -of name servers. One set will be on the inside network (in the reserved -IP space) and the other set will be on bastion hosts, which are "proxy" -hosts that can talk to both sides of its network, in the DMZ.</para> -<para>The internal servers will be configured to forward all queries, -except queries for <filename>site1.internal</filename>, <filename>site2.internal</filename>, <filename>site1.example.com</filename>, -and <filename>site2.example.com</filename>, to the servers in the -DMZ. These internal servers will have complete sets of information -for <filename>site1.example.com</filename>, <filename>site2.example.com</filename>,<emphasis> </emphasis><filename>site1.internal</filename>, -and <filename>site2.internal</filename>.</para> -<para>To protect the <filename>site1.internal</filename> and <filename>site2.internal</filename> domains, -the internal name servers must be configured to disallow all queries -to these domains from any external hosts, including the bastion -hosts.</para> -<para>The external servers, which are on the bastion hosts, will -be configured to serve the "public" version of the <filename>site1</filename> and <filename>site2.example.com</filename> zones. -This could include things such as the host records for public servers -(<filename>www.example.com</filename> and <filename>ftp.example.com</filename>), -and mail exchange (MX) records (<filename>a.mx.example.com</filename> and <filename>b.mx.example.com</filename>).</para> -<para>In addition, the public <filename>site1</filename> and <filename>site2.example.com</filename> zones -should have special MX records that contain wildcard (`*') records -pointing to the bastion hosts. This is needed because external mail -servers do not have any other way of looking up how to deliver mail -to those internal hosts. With the wildcard records, the mail will -be delivered to the bastion host, which can then forward it on to -internal hosts.</para> -<para>Here's an example of a wildcard MX record:</para> -<programlisting>* IN MX 10 external1.example.com.</programlisting> -<para>Now that they accept mail on behalf of anything in the internal -network, the bastion hosts will need to know how to deliver mail -to internal hosts. In order for this to work properly, the resolvers on -the bastion hosts will need to be configured to point to the internal -name servers for DNS resolution.</para> -<para>Queries for internal hostnames will be answered by the internal -servers, and queries for external hostnames will be forwarded back -out to the DNS servers on the bastion hosts.</para> -<para>In order for all this to work properly, internal clients will -need to be configured to query <emphasis>only</emphasis> the internal -name servers for DNS queries. This could also be enforced via selective -filtering on the network.</para> -<para>If everything has been set properly, <emphasis>Example, Inc.</emphasis>'s -internal clients will now be able to:</para> -<itemizedlist><listitem> - <simpara>Look up any hostnames in the <literal>site1</literal> and -<literal>site2.example.com</literal> zones.</simpara></listitem> -<listitem> - <simpara>Look up any hostnames in the <literal>site1.internal</literal> and -<literal>site2.internal</literal> domains.</simpara></listitem> -<listitem> - <simpara>Look up any hostnames on the Internet.</simpara></listitem> -<listitem> - <simpara>Exchange mail with both internal AND external people.</simpara></listitem></itemizedlist> -<para>Hosts on the Internet will be able to:</para> -<itemizedlist><listitem> - <simpara>Look up any hostnames in the <literal>site1</literal> and -<literal>site2.example.com</literal> zones.</simpara></listitem> -<listitem> - <simpara>Exchange mail with anyone in the <literal>site1</literal> and -<literal>site2.example.com</literal> zones.</simpara></listitem></itemizedlist> - - <para>Here is an example configuration for the setup we just - described above. Note that this is only configuration information; - for information on how to configure your zone files, see <xref - linkend="sample_configuration"/>.</para> - -<para>Internal DNS server config:</para> + <chapter id="Bv9ARM.ch04"> + <title>Advanced DNS Features</title> + + <sect1 id="notify"> + + <title>Notify</title> + <para> + <acronym>DNS</acronym> NOTIFY is a mechanism that allows master + servers to notify their slave servers of changes to a zone's data. In + response to a <command>NOTIFY</command> from a master server, the + slave will check to see that its version of the zone is the + current version and, if not, initiate a zone transfer. + </para> + + <para> + For more information about <acronym>DNS</acronym> + <command>NOTIFY</command>, see the description of the + <command>notify</command> option in <xref linkend="boolean_options"/> and + the description of the zone option <command>also-notify</command> in + <xref linkend="zone_transfers"/>. The <command>NOTIFY</command> + protocol is specified in RFC 1996. + </para> + + <note> + As a slave zone can also be a master to other slaves, named, + by default, sends <command>NOTIFY</command> messages for every zone + it loads. Specifying <command>notify master-only;</command> will + cause named to only send <command>NOTIFY</command> for master + zones that it loads. + </note> + + </sect1> + + <sect1 id="dynamic_update"> + <title>Dynamic Update</title> + + <para> + Dynamic Update is a method for adding, replacing or deleting + records in a master server by sending it a special form of DNS + messages. The format and meaning of these messages is specified + in RFC 2136. + </para> + + <para> + Dynamic update is enabled by + including an <command>allow-update</command> or + <command>update-policy</command> clause in the + <command>zone</command> statement. + </para> + + <para> + Updating of secure zones (zones using DNSSEC) follows + RFC 3007: RRSIG and NSEC records affected by updates are automatically + regenerated by the server using an online zone key. + Update authorization is based + on transaction signatures and an explicit server policy. + </para> + + <sect2 id="journal"> + <title>The journal file</title> + + <para> + All changes made to a zone using dynamic update are stored + in the zone's journal file. This file is automatically created + by the server when the first dynamic update takes place. + The name of the journal file is formed by appending the extension + <filename>.jnl</filename> to the name of the + corresponding zone + file unless specifically overridden. The journal file is in a + binary format and should not be edited manually. + </para> + + <para> + The server will also occasionally write ("dump") + the complete contents of the updated zone to its zone file. + This is not done immediately after + each dynamic update, because that would be too slow when a large + zone is updated frequently. Instead, the dump is delayed by + up to 15 minutes, allowing additional updates to take place. + </para> + + <para> + When a server is restarted after a shutdown or crash, it will replay + the journal file to incorporate into the zone any updates that + took + place after the last zone dump. + </para> + + <para> + Changes that result from incoming incremental zone transfers are + also + journalled in a similar way. + </para> + + <para> + The zone files of dynamic zones cannot normally be edited by + hand because they are not guaranteed to contain the most recent + dynamic changes — those are only in the journal file. + The only way to ensure that the zone file of a dynamic zone + is up to date is to run <command>rndc stop</command>. + </para> + + <para> + If you have to make changes to a dynamic zone + manually, the following procedure will work: Disable dynamic updates + to the zone using + <command>rndc freeze <replaceable>zone</replaceable></command>. + This will also remove the zone's <filename>.jnl</filename> file + and update the master file. Edit the zone file. Run + <command>rndc thaw <replaceable>zone</replaceable></command> + to reload the changed zone and re-enable dynamic updates. + </para> + + </sect2> + + </sect1> + + <sect1 id="incremental_zone_transfers"> + <title>Incremental Zone Transfers (IXFR)</title> + + <para> + The incremental zone transfer (IXFR) protocol is a way for + slave servers to transfer only changed data, instead of having to + transfer the entire zone. The IXFR protocol is specified in RFC + 1995. See <xref linkend="proposed_standards"/>. + </para> + + <para> + When acting as a master, <acronym>BIND</acronym> 9 + supports IXFR for those zones + where the necessary change history information is available. These + include master zones maintained by dynamic update and slave zones + whose data was obtained by IXFR. For manually maintained master + zones, and for slave zones obtained by performing a full zone + transfer (AXFR), IXFR is supported only if the option + <command>ixfr-from-differences</command> is set + to <userinput>yes</userinput>. + </para> + + <para> + When acting as a slave, <acronym>BIND</acronym> 9 will + attempt to use IXFR unless + it is explicitly disabled. For more information about disabling + IXFR, see the description of the <command>request-ixfr</command> clause + of the <command>server</command> statement. + </para> + </sect1> + + <sect1> + <title>Split DNS</title> + <para> + Setting up different views, or visibility, of the DNS space to + internal and external resolvers is usually referred to as a + <emphasis>Split DNS</emphasis> setup. There are several + reasons an organization would want to set up its DNS this way. + </para> + <para> + One common reason for setting up a DNS system this way is + to hide "internal" DNS information from "external" clients on the + Internet. There is some debate as to whether or not this is actually + useful. + Internal DNS information leaks out in many ways (via email headers, + for example) and most savvy "attackers" can find the information + they need using other means. + However, since listing addresses of internal servers that + external clients cannot possibly reach can result in + connection delays and other annoyances, an organization may + choose to use a Split DNS to present a consistent view of itself + to the outside world. + </para> + <para> + Another common reason for setting up a Split DNS system is + to allow internal networks that are behind filters or in RFC 1918 + space (reserved IP space, as documented in RFC 1918) to resolve DNS + on the Internet. Split DNS can also be used to allow mail from outside + back in to the internal network. + </para> + <sect2> + <title>Example split DNS setup</title> + <para> + Let's say a company named <emphasis>Example, Inc.</emphasis> + (<literal>example.com</literal>) + has several corporate sites that have an internal network with + reserved + Internet Protocol (IP) space and an external demilitarized zone (DMZ), + or "outside" section of a network, that is available to the public. + </para> + <para> + <emphasis>Example, Inc.</emphasis> wants its internal clients + to be able to resolve external hostnames and to exchange mail with + people on the outside. The company also wants its internal resolvers + to have access to certain internal-only zones that are not available + at all outside of the internal network. + </para> + <para> + In order to accomplish this, the company will set up two sets + of name servers. One set will be on the inside network (in the + reserved + IP space) and the other set will be on bastion hosts, which are + "proxy" + hosts that can talk to both sides of its network, in the DMZ. + </para> + <para> + The internal servers will be configured to forward all queries, + except queries for <filename>site1.internal</filename>, <filename>site2.internal</filename>, <filename>site1.example.com</filename>, + and <filename>site2.example.com</filename>, to the servers + in the + DMZ. These internal servers will have complete sets of information + for <filename>site1.example.com</filename>, <filename>site2.example.com</filename>,<emphasis/> <filename>site1.internal</filename>, + and <filename>site2.internal</filename>. + </para> + <para> + To protect the <filename>site1.internal</filename> and <filename>site2.internal</filename> domains, + the internal name servers must be configured to disallow all queries + to these domains from any external hosts, including the bastion + hosts. + </para> + <para> + The external servers, which are on the bastion hosts, will + be configured to serve the "public" version of the <filename>site1</filename> and <filename>site2.example.com</filename> zones. + This could include things such as the host records for public servers + (<filename>www.example.com</filename> and <filename>ftp.example.com</filename>), + and mail exchange (MX) records (<filename>a.mx.example.com</filename> and <filename>b.mx.example.com</filename>). + </para> + <para> + In addition, the public <filename>site1</filename> and <filename>site2.example.com</filename> zones + should have special MX records that contain wildcard (`*') records + pointing to the bastion hosts. This is needed because external mail + servers do not have any other way of looking up how to deliver mail + to those internal hosts. With the wildcard records, the mail will + be delivered to the bastion host, which can then forward it on to + internal hosts. + </para> + <para> + Here's an example of a wildcard MX record: + </para> + <programlisting>* IN MX 10 external1.example.com.</programlisting> + <para> + Now that they accept mail on behalf of anything in the internal + network, the bastion hosts will need to know how to deliver mail + to internal hosts. In order for this to work properly, the resolvers + on + the bastion hosts will need to be configured to point to the internal + name servers for DNS resolution. + </para> + <para> + Queries for internal hostnames will be answered by the internal + servers, and queries for external hostnames will be forwarded back + out to the DNS servers on the bastion hosts. + </para> + <para> + In order for all this to work properly, internal clients will + need to be configured to query <emphasis>only</emphasis> the internal + name servers for DNS queries. This could also be enforced via + selective + filtering on the network. + </para> + <para> + If everything has been set properly, <emphasis>Example, Inc.</emphasis>'s + internal clients will now be able to: + </para> + <itemizedlist> + <listitem> + <simpara> + Look up any hostnames in the <literal>site1</literal> + and + <literal>site2.example.com</literal> zones. + </simpara> + </listitem> + <listitem> + <simpara> + Look up any hostnames in the <literal>site1.internal</literal> and + <literal>site2.internal</literal> domains. + </simpara> + </listitem> + <listitem> + <simpara>Look up any hostnames on the Internet.</simpara> + </listitem> + <listitem> + <simpara>Exchange mail with both internal and external people.</simpara> + </listitem> + </itemizedlist> + <para> + Hosts on the Internet will be able to: + </para> + <itemizedlist> + <listitem> + <simpara> + Look up any hostnames in the <literal>site1</literal> + and + <literal>site2.example.com</literal> zones. + </simpara> + </listitem> + <listitem> + <simpara> + Exchange mail with anyone in the <literal>site1</literal> and + <literal>site2.example.com</literal> zones. + </simpara> + </listitem> + </itemizedlist> + + <para> + Here is an example configuration for the setup we just + described above. Note that this is only configuration information; + for information on how to configure your zone files, see <xref linkend="sample_configuration"/>. + </para> + + <para> + Internal DNS server config: + </para> + <programlisting> acl internals { 172.16.72.0/24; 192.168.1.0/24; }; @@ -1209,7 +1898,7 @@ options { ... forward only; forwarders { // forward to external servers - <varname>bastion-ips-go-here</varname>; + <varname>bastion-ips-go-here</varname>; }; allow-transfer { none; }; // sample allow-transfer (no one) allow-query { internals; externals; }; // restrict query access @@ -1253,7 +1942,11 @@ zone "site2.internal" { allow-transfer { internals; } }; </programlisting> - <para>External (bastion host) DNS server config:</para> + + <para> + External (bastion host) DNS server config: + </para> + <programlisting> acl internals { 172.16.72.0/24; 192.168.1.0/24; }; @@ -1263,7 +1956,8 @@ options { ... ... allow-transfer { none; }; // sample allow-transfer (no one) - allow-query { internals; externals; }; // restrict query access + allow-query { any; }; // default query access + allow-query-cache { internals; externals; }; // restrict cache access allow-recursion { internals; externals; }; // restrict recursion ... ... @@ -1272,7 +1966,6 @@ options { zone "site1.example.com" { // sample slave zone type master; file "m/site1.foo.com"; - allow-query { any; }; allow-transfer { internals; externals; }; }; @@ -1280,317 +1973,459 @@ zone "site2.example.com" { type slave; file "s/site2.foo.com"; masters { another_bastion_host_maybe; }; - allow-query { any; }; allow-transfer { internals; externals; } }; </programlisting> -<para>In the <filename>resolv.conf</filename> (or equivalent) on -the bastion host(s):</para> + + <para> + In the <filename>resolv.conf</filename> (or equivalent) on + the bastion host(s): + </para> + <programlisting> search ... nameserver 172.16.72.2 nameserver 172.16.72.3 nameserver 172.16.72.4 </programlisting> -</sect1> -<sect1 id="tsig"><title>TSIG</title> -<para>This is a short guide to setting up Transaction SIGnatures -(TSIG) based transaction security in <acronym>BIND</acronym>. It describes changes -to the configuration file as well as what changes are required for -different features, including the process of creating transaction -keys and using transaction signatures with <acronym>BIND</acronym>.</para> -<para><acronym>BIND</acronym> primarily supports TSIG for server to server communication. -This includes zone transfer, notify, and recursive query messages. -Resolvers based on newer versions of <acronym>BIND</acronym> 8 have limited support -for TSIG.</para> - - <para>TSIG might be most useful for dynamic update. A primary - server for a dynamic zone should use access control to control - updates, but IP-based access control is insufficient. - The cryptographic access control provided by TSIG - is far superior. The <command>nsupdate</command> - program supports TSIG via the <option>-k</option> and - <option>-y</option> command line options.</para> - -<sect2><title>Generate Shared Keys for Each Pair of Hosts</title> -<para>A shared secret is generated to be shared between <emphasis>host1</emphasis> and <emphasis>host2</emphasis>. -An arbitrary key name is chosen: "host1-host2.". The key name must -be the same on both hosts.</para> -<sect3><title>Automatic Generation</title> -<para>The following command will generate a 128-bit (16 byte) HMAC-MD5 -key as described above. Longer keys are better, but shorter keys -are easier to read. Note that the maximum key length is 512 bits; -keys longer than that will be digested with MD5 to produce a -128-bit key.</para> - <para><userinput>dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.</userinput></para> -<para>The key is in the file <filename>Khost1-host2.+157+00000.private</filename>. -Nothing directly uses this file, but the base-64 encoded string -following "<literal>Key:</literal>" -can be extracted from the file and used as a shared secret:</para> -<programlisting>Key: La/E5CjG9O+os1jq0a2jdA==</programlisting> -<para>The string "<literal>La/E5CjG9O+os1jq0a2jdA==</literal>" can -be used as the shared secret.</para></sect3> -<sect3><title>Manual Generation</title> -<para>The shared secret is simply a random sequence of bits, encoded -in base-64. Most ASCII strings are valid base-64 strings (assuming -the length is a multiple of 4 and only valid characters are used), -so the shared secret can be manually generated.</para> -<para>Also, a known string can be run through <command>mmencode</command> or -a similar program to generate base-64 encoded data.</para></sect3></sect2> -<sect2><title>Copying the Shared Secret to Both Machines</title> -<para>This is beyond the scope of DNS. A secure transport mechanism -should be used. This could be secure FTP, ssh, telephone, etc.</para></sect2> -<sect2><title>Informing the Servers of the Key's Existence</title> -<para>Imagine <emphasis>host1</emphasis> and <emphasis>host 2</emphasis> are -both servers. The following is added to each server's <filename>named.conf</filename> file:</para> + + </sect2> + </sect1> + <sect1 id="tsig"> + <title>TSIG</title> + <para> + This is a short guide to setting up Transaction SIGnatures + (TSIG) based transaction security in <acronym>BIND</acronym>. It describes changes + to the configuration file as well as what changes are required for + different features, including the process of creating transaction + keys and using transaction signatures with <acronym>BIND</acronym>. + </para> + <para> + <acronym>BIND</acronym> primarily supports TSIG for server + to server communication. + This includes zone transfer, notify, and recursive query messages. + Resolvers based on newer versions of <acronym>BIND</acronym> 8 have limited support + for TSIG. + </para> + + <para> + TSIG can also be useful for dynamic update. A primary + server for a dynamic zone should control access to the dynamic + update service, but IP-based access control is insufficient. + The cryptographic access control provided by TSIG + is far superior. The <command>nsupdate</command> + program supports TSIG via the <option>-k</option> and + <option>-y</option> command line options or inline by use + of the <command>key</command>. + </para> + + <sect2> + <title>Generate Shared Keys for Each Pair of Hosts</title> + <para> + A shared secret is generated to be shared between <emphasis>host1</emphasis> and <emphasis>host2</emphasis>. + An arbitrary key name is chosen: "host1-host2.". The key name must + be the same on both hosts. + </para> + <sect3> + <title>Automatic Generation</title> + <para> + The following command will generate a 128-bit (16 byte) HMAC-MD5 + key as described above. Longer keys are better, but shorter keys + are easier to read. Note that the maximum key length is 512 bits; + keys longer than that will be digested with MD5 to produce a + 128-bit key. + </para> + <para> + <userinput>dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.</userinput> + </para> + <para> + The key is in the file <filename>Khost1-host2.+157+00000.private</filename>. + Nothing directly uses this file, but the base-64 encoded string + following "<literal>Key:</literal>" + can be extracted from the file and used as a shared secret: + </para> + <programlisting>Key: La/E5CjG9O+os1jq0a2jdA==</programlisting> + <para> + The string "<literal>La/E5CjG9O+os1jq0a2jdA==</literal>" can + be used as the shared secret. + </para> + </sect3> + <sect3> + <title>Manual Generation</title> + <para> + The shared secret is simply a random sequence of bits, encoded + in base-64. Most ASCII strings are valid base-64 strings (assuming + the length is a multiple of 4 and only valid characters are used), + so the shared secret can be manually generated. + </para> + <para> + Also, a known string can be run through <command>mmencode</command> or + a similar program to generate base-64 encoded data. + </para> + </sect3> + </sect2> + <sect2> + <title>Copying the Shared Secret to Both Machines</title> + <para> + This is beyond the scope of DNS. A secure transport mechanism + should be used. This could be secure FTP, ssh, telephone, etc. + </para> + </sect2> + <sect2> + <title>Informing the Servers of the Key's Existence</title> + <para> + Imagine <emphasis>host1</emphasis> and <emphasis>host 2</emphasis> + are + both servers. The following is added to each server's <filename>named.conf</filename> file: + </para> + <programlisting> key host1-host2. { algorithm hmac-md5; secret "La/E5CjG9O+os1jq0a2jdA=="; }; </programlisting> -<para>The algorithm, hmac-md5, is the only one supported by <acronym>BIND</acronym>. -The secret is the one generated above. Since this is a secret, it -is recommended that either <filename>named.conf</filename> be non-world -readable, or the key directive be added to a non-world readable -file that is included by <filename>named.conf</filename>.</para> -<para>At this point, the key is recognized. This means that if the -server receives a message signed by this key, it can verify the -signature. If the signature is successfully verified, the -response is signed by the same key.</para></sect2> - -<sect2><title>Instructing the Server to Use the Key</title> -<para>Since keys are shared between two hosts only, the server must -be told when keys are to be used. The following is added to the <filename>named.conf</filename> file -for <emphasis>host1</emphasis>, if the IP address of <emphasis>host2</emphasis> is -10.1.2.3:</para> + + <para> + The algorithm, hmac-md5, is the only one supported by <acronym>BIND</acronym>. + The secret is the one generated above. Since this is a secret, it + is recommended that either <filename>named.conf</filename> be non-world + readable, or the key directive be added to a non-world readable + file that is included by + <filename>named.conf</filename>. + </para> + <para> + At this point, the key is recognized. This means that if the + server receives a message signed by this key, it can verify the + signature. If the signature is successfully verified, the + response is signed by the same key. + </para> + </sect2> + + <sect2> + <title>Instructing the Server to Use the Key</title> + <para> + Since keys are shared between two hosts only, the server must + be told when keys are to be used. The following is added to the <filename>named.conf</filename> file + for <emphasis>host1</emphasis>, if the IP address of <emphasis>host2</emphasis> is + 10.1.2.3: + </para> + <programlisting> server 10.1.2.3 { keys { host1-host2. ;}; }; </programlisting> -<para>Multiple keys may be present, but only the first is used. -This directive does not contain any secrets, so it may be in a world-readable -file.</para> -<para>If <emphasis>host1</emphasis> sends a message that is a request -to that address, the message will be signed with the specified key. <emphasis>host1</emphasis> will -expect any responses to signed messages to be signed with the same -key.</para> -<para>A similar statement must be present in <emphasis>host2</emphasis>'s -configuration file (with <emphasis>host1</emphasis>'s address) for <emphasis>host2</emphasis> to -sign request messages to <emphasis>host1</emphasis>.</para></sect2> -<sect2><title>TSIG Key Based Access Control</title> -<para><acronym>BIND</acronym> allows IP addresses and ranges to be specified in ACL -definitions and -<command>allow-{ query | transfer | update }</command> directives. -This has been extended to allow TSIG keys also. The above key would -be denoted <command>key host1-host2.</command></para> -<para>An example of an allow-update directive would be:</para> + + <para> + Multiple keys may be present, but only the first is used. + This directive does not contain any secrets, so it may be in a + world-readable + file. + </para> + <para> + If <emphasis>host1</emphasis> sends a message that is a request + to that address, the message will be signed with the specified key. <emphasis>host1</emphasis> will + expect any responses to signed messages to be signed with the same + key. + </para> + <para> + A similar statement must be present in <emphasis>host2</emphasis>'s + configuration file (with <emphasis>host1</emphasis>'s address) for <emphasis>host2</emphasis> to + sign request messages to <emphasis>host1</emphasis>. + </para> + </sect2> + <sect2> + <title>TSIG Key Based Access Control</title> + <para> + <acronym>BIND</acronym> allows IP addresses and ranges + to be specified in ACL + definitions and + <command>allow-{ query | transfer | update }</command> + directives. + This has been extended to allow TSIG keys also. The above key would + be denoted <command>key host1-host2.</command> + </para> + <para> + An example of an allow-update directive would be: + </para> + <programlisting> allow-update { key host1-host2. ;}; </programlisting> - <para>This allows dynamic updates to succeed only if the request - was signed by a key named - "<command>host1-host2.</command>".</para> <para>You may want to read about the more - powerful <command>update-policy</command> statement in <xref - linkend="dynamic_update_policies"/>.</para> - - </sect2> - <sect2> - <title>Errors</title> - - <para>The processing of TSIG signed messages can result in - several errors. If a signed message is sent to a non-TSIG - aware server, a FORMERR (format error) will be returned, since - the server will not understand the record. This is a result - of misconfiguration, since the server must be explicitly - configured to send a TSIG signed message to a specific - server.</para> - - <para>If a TSIG aware server receives a message signed by an - unknown key, the response will be unsigned with the TSIG - extended error code set to BADKEY. If a TSIG aware server - receives a message with a signature that does not validate, the - response will be unsigned with the TSIG extended error code set - to BADSIG. If a TSIG aware server receives a message with a time - outside of the allowed range, the response will be signed with - the TSIG extended error code set to BADTIME, and the time values - will be adjusted so that the response can be successfully - verified. In any of these cases, the message's rcode is set to - NOTAUTH (not authenticated).</para> - - </sect2> - </sect1> - <sect1> - <title>TKEY</title> - - <para><command>TKEY</command> is a mechanism for automatically - generating a shared secret between two hosts. There are several - "modes" of <command>TKEY</command> that specify how the key is - generated or assigned. <acronym>BIND</acronym> 9 - implements only one of these modes, - the Diffie-Hellman key exchange. Both hosts are required to have - a Diffie-Hellman KEY record (although this record is not required - to be present in a zone). The <command>TKEY</command> process - must use signed messages, signed either by TSIG or SIG(0). The - result of <command>TKEY</command> is a shared secret that can be - used to sign messages with TSIG. <command>TKEY</command> can also - be used to delete shared secrets that it had previously - generated.</para> - - <para>The <command>TKEY</command> process is initiated by a client - or server by sending a signed <command>TKEY</command> query - (including any appropriate KEYs) to a TKEY-aware server. The - server response, if it indicates success, will contain a - <command>TKEY</command> record and any appropriate keys. After - this exchange, both participants have enough information to - determine the shared secret; the exact process depends on the - <command>TKEY</command> mode. When using the Diffie-Hellman - <command>TKEY</command> mode, Diffie-Hellman keys are exchanged, - and the shared secret is derived by both participants.</para> - - </sect1> - <sect1> - <title>SIG(0)</title> - - <para><acronym>BIND</acronym> 9 partially supports DNSSEC SIG(0) - transaction signatures as specified in RFC 2535 and RFC2931. SIG(0) - uses public/private keys to authenticate messages. Access control - is performed in the same manner as TSIG keys; privileges can be - granted or denied based on the key name.</para> - - <para>When a SIG(0) signed message is received, it will only be - verified if the key is known and trusted by the server; the server - will not attempt to locate and / or validate the key.</para> - - <para>SIG(0) signing of multiple-message TCP streams is not - supported.</para> - - <para>The only tool shipped with <acronym>BIND</acronym> 9 that - generates SIG(0) signed messages is <command>nsupdate</command>.</para> - - </sect1> - <sect1 id="DNSSEC"> - <title>DNSSEC</title> - - <para>Cryptographic authentication of DNS information is possible - through the DNS Security (<emphasis>DNSSEC-bis</emphasis>) - extensions, defined in RFC 4033, RFC4034 and RFC4035. This - section describes the creation and use of DNSSEC signed - zones.</para> - - <para>In order to set up a DNSSEC secure zone, there are a series - of steps which must be followed. <acronym>BIND</acronym> 9 ships - with several tools - that are used in this process, which are explained in more detail - below. In all cases, the <option>-h</option> option prints a - full list of parameters. Note that the DNSSEC tools require the - keyset files to be in the working directory or the - directory specified by the <option>-h</option> option, and - that the tools shipped with BIND 9.2.x and earlier are not compatible - with the current ones.</para> - - <para>There must also be communication with the administrators of - the parent and/or child zone to transmit keys. A zone's security - status must be indicated by the parent zone for a DNSSEC capable - resolver to trust its data. This is done through the presence - or absence of a <literal>DS</literal> record at the delegation - point.</para> - - <para>For other servers to trust data in this zone, they must - either be statically configured with this zone's zone key or the - zone key of another zone above this one in the DNS tree.</para> - - <sect2> - <title>Generating Keys</title> - - <para>The <command>dnssec-keygen</command> program is used to - generate keys.</para> - - <para>A secure zone must contain one or more zone keys. The - zone keys will sign all other records in the zone, as well as - the zone keys of any secure delegated zones. Zone keys must - have the same name as the zone, a name type of - <command>ZONE</command>, and must be usable for authentication. - It is recommended that zone keys use a cryptographic algorithm - designated as "mandatory to implement" by the IETF; currently - the only one is RSASHA1.</para> - - <para>The following command will generate a 768-bit RSASHA1 key for - the <filename>child.example</filename> zone:</para> - - <para><userinput>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</userinput></para> - - <para>Two output files will be produced: - <filename>Kchild.example.+005+12345.key</filename> and - <filename>Kchild.example.+005+12345.private</filename> (where - 12345 is an example of a key tag). The key file names contain - the key name (<filename>child.example.</filename>), algorithm (3 - is DSA, 1 is RSAMD5, 5 is RSASHA1, etc.), and the key tag (12345 in this case). - The private key (in the <filename>.private</filename> file) is - used to generate signatures, and the public key (in the - <filename>.key</filename> file) is used for signature - verification.</para> - - <para>To generate another key with the same properties (but with - a different key tag), repeat the above command.</para> - - <para>The public keys should be inserted into the zone file by - including the <filename>.key</filename> files using - <command>$INCLUDE</command> statements. + <para> + This allows dynamic updates to succeed only if the request + was signed by a key named + "<command>host1-host2.</command>". + </para> + <para> + You may want to read about the more + powerful <command>update-policy</command> statement in <xref linkend="dynamic_update_policies"/>. + </para> + + </sect2> + <sect2> + <title>Errors</title> + + <para> + The processing of TSIG signed messages can result in + several errors. If a signed message is sent to a non-TSIG aware + server, a FORMERR (format error) will be returned, since the server will not + understand the record. This is a result of misconfiguration, + since the server must be explicitly configured to send a TSIG + signed message to a specific server. + </para> + + <para> + If a TSIG aware server receives a message signed by an + unknown key, the response will be unsigned with the TSIG + extended error code set to BADKEY. If a TSIG aware server + receives a message with a signature that does not validate, the + response will be unsigned with the TSIG extended error code set + to BADSIG. If a TSIG aware server receives a message with a time + outside of the allowed range, the response will be signed with + the TSIG extended error code set to BADTIME, and the time values + will be adjusted so that the response can be successfully + verified. In any of these cases, the message's rcode (response code) is set to + NOTAUTH (not authenticated). + </para> + + </sect2> + </sect1> + <sect1> + <title>TKEY</title> + + <para><command>TKEY</command> + is a mechanism for automatically generating a shared secret + between two hosts. There are several "modes" of + <command>TKEY</command> that specify how the key is generated + or assigned. <acronym>BIND</acronym> 9 implements only one of + these modes, the Diffie-Hellman key exchange. Both hosts are + required to have a Diffie-Hellman KEY record (although this + record is not required to be present in a zone). The + <command>TKEY</command> process must use signed messages, + signed either by TSIG or SIG(0). The result of + <command>TKEY</command> is a shared secret that can be used to + sign messages with TSIG. <command>TKEY</command> can also be + used to delete shared secrets that it had previously + generated. + </para> + + <para> + The <command>TKEY</command> process is initiated by a + client + or server by sending a signed <command>TKEY</command> + query + (including any appropriate KEYs) to a TKEY-aware server. The + server response, if it indicates success, will contain a + <command>TKEY</command> record and any appropriate keys. + After + this exchange, both participants have enough information to + determine the shared secret; the exact process depends on the + <command>TKEY</command> mode. When using the + Diffie-Hellman + <command>TKEY</command> mode, Diffie-Hellman keys are + exchanged, + and the shared secret is derived by both participants. + </para> + + </sect1> + <sect1> + <title>SIG(0)</title> + + <para> + <acronym>BIND</acronym> 9 partially supports DNSSEC SIG(0) + transaction signatures as specified in RFC 2535 and RFC2931. + SIG(0) + uses public/private keys to authenticate messages. Access control + is performed in the same manner as TSIG keys; privileges can be + granted or denied based on the key name. </para> - </sect2> - <sect2> - <title>Signing the Zone</title> + <para> + When a SIG(0) signed message is received, it will only be + verified if the key is known and trusted by the server; the server + will not attempt to locate and/or validate the key. + </para> - <para>The <command>dnssec-signzone</command> program is used to - sign a zone.</para> + <para> + SIG(0) signing of multiple-message TCP streams is not + supported. + </para> - <para>Any <filename>keyset</filename> files corresponding - to secure subzones should be present. The zone signer will - generate <literal>NSEC</literal> and <literal>RRSIG</literal> - records for the zone, as well as <literal>DS</literal> for - the child zones if <literal>'-d'</literal> is specified. - If <literal>'-d'</literal> is not specified, then DS RRsets for - the secure child zones need to be added manually.</para> + <para> + The only tool shipped with <acronym>BIND</acronym> 9 that + generates SIG(0) signed messages is <command>nsupdate</command>. + </para> - <para>The following command signs the zone, assuming it is in a - file called <filename>zone.child.example</filename>. By - default, all zone keys which have an available private key are - used to generate signatures.</para> + </sect1> + <sect1 id="DNSSEC"> + <title>DNSSEC</title> -<para><userinput>dnssec-signzone -o child.example zone.child.example</userinput></para> + <para> + Cryptographic authentication of DNS information is possible + through the DNS Security (<emphasis>DNSSEC-bis</emphasis>) extensions, + defined in RFC 4033, RFC 4034, and RFC 4035. + This section describes the creation and use of DNSSEC signed zones. + </para> - <para>One output file is produced: - <filename>zone.child.example.signed</filename>. This file - should be referenced by <filename>named.conf</filename> as the - input file for the zone.</para> + <para> + In order to set up a DNSSEC secure zone, there are a series + of steps which must be followed. <acronym>BIND</acronym> + 9 ships + with several tools + that are used in this process, which are explained in more detail + below. In all cases, the <option>-h</option> option prints a + full list of parameters. Note that the DNSSEC tools require the + keyset files to be in the working directory or the + directory specified by the <option>-d</option> option, and + that the tools shipped with BIND 9.2.x and earlier are not compatible + with the current ones. + </para> - <para><command>dnssec-signzone</command> will also produce a - keyset and dsset files and optionally a dlvset file. These - are used to provide the parent zone administators with the - <literal>DNSKEYs</literal> (or their corresponding <literal>DS</literal> - records) that are the secure entry point to the zone.</para> + <para> + There must also be communication with the administrators of + the parent and/or child zone to transmit keys. A zone's security + status must be indicated by the parent zone for a DNSSEC capable + resolver to trust its data. This is done through the presence + or absence of a <literal>DS</literal> record at the + delegation + point. + </para> - </sect2> + <para> + For other servers to trust data in this zone, they must + either be statically configured with this zone's zone key or the + zone key of another zone above this one in the DNS tree. + </para> -<sect2><title>Configuring Servers</title> + <sect2> + <title>Generating Keys</title> + + <para> + The <command>dnssec-keygen</command> program is used to + generate keys. + </para> + + <para> + A secure zone must contain one or more zone keys. The + zone keys will sign all other records in the zone, as well as + the zone keys of any secure delegated zones. Zone keys must + have the same name as the zone, a name type of + <command>ZONE</command>, and must be usable for + authentication. + It is recommended that zone keys use a cryptographic algorithm + designated as "mandatory to implement" by the IETF; currently + the only one is RSASHA1. + </para> + + <para> + The following command will generate a 768-bit RSASHA1 key for + the <filename>child.example</filename> zone: + </para> + + <para> + <userinput>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</userinput> + </para> + + <para> + Two output files will be produced: + <filename>Kchild.example.+005+12345.key</filename> and + <filename>Kchild.example.+005+12345.private</filename> + (where + 12345 is an example of a key tag). The key filenames contain + the key name (<filename>child.example.</filename>), + algorithm (3 + is DSA, 1 is RSAMD5, 5 is RSASHA1, etc.), and the key tag (12345 in + this case). + The private key (in the <filename>.private</filename> + file) is + used to generate signatures, and the public key (in the + <filename>.key</filename> file) is used for signature + verification. + </para> + + <para> + To generate another key with the same properties (but with + a different key tag), repeat the above command. + </para> + + <para> + The public keys should be inserted into the zone file by + including the <filename>.key</filename> files using + <command>$INCLUDE</command> statements. + </para> + + </sect2> + <sect2> + <title>Signing the Zone</title> + + <para> + The <command>dnssec-signzone</command> program is used + to + sign a zone. + </para> + + <para> + Any <filename>keyset</filename> files corresponding + to secure subzones should be present. The zone signer will + generate <literal>NSEC</literal> and <literal>RRSIG</literal> + records for the zone, as well as <literal>DS</literal> + for + the child zones if <literal>'-d'</literal> is specified. + If <literal>'-d'</literal> is not specified, then + DS RRsets for + the secure child zones need to be added manually. + </para> + + <para> + The following command signs the zone, assuming it is in a + file called <filename>zone.child.example</filename>. By + default, all zone keys which have an available private key are + used to generate signatures. + </para> + + <para> + <userinput>dnssec-signzone -o child.example zone.child.example</userinput> + </para> + + <para> + One output file is produced: + <filename>zone.child.example.signed</filename>. This + file + should be referenced by <filename>named.conf</filename> + as the + input file for the zone. + </para> + + <para><command>dnssec-signzone</command> + will also produce a keyset and dsset files and optionally a + dlvset file. These are used to provide the parent zone + administrators with the <literal>DNSKEYs</literal> (or their + corresponding <literal>DS</literal> records) that are the + secure entry point to the zone. + </para> + + </sect2> + + <sect2> + <title>Configuring Servers</title> <para> To enable <command>named</command> to respond appropriately to DNS requests from DNSSEC aware clients, <command>dnssec-enable</command> must be set to yes. - </para> - + </para> + <para> To enable <command>named</command> to validate answers from - other servers <command>dnssec-enable</command> and - some <command>trusted-keys</command> must be configured + other servers both <command>dnssec-enable</command> and + <command>dnssec-validation</command> must be set and some + <command>trusted-keys</command> must be configured into <filename>named.conf</filename>. - </para> - + </para> + <para> <command>trusted-keys</command> are copies of DNSKEY RRs for zones that are used to form the first link in the @@ -1658,6 +2493,7 @@ example.com. 257 3 5 "AwEAAaxPMcR2x0HbQV4WeZB6oEDX+r0QM65KbhTjrW1ZaARmPhEZZe options { ... dnssec-enable yes; + dnssec-validation yes; }; </programlisting> @@ -1666,710 +2502,1168 @@ options { the root key is not valid. </note> -</sect2> - -</sect1> - <sect1> - <title>IPv6 Support in <acronym>BIND</acronym> 9</title> - - <para><acronym>BIND</acronym> 9 fully supports all currently defined forms of IPv6 - name to address and address to name lookups. It will also use - IPv6 addresses to make queries when running on an IPv6 capable - system.</para> - - <para>For forward lookups, <acronym>BIND</acronym> 9 supports only AAAA - records. The use of A6 records is deprecated by RFC 3363, and the - support for forward lookups in <acronym>BIND</acronym> 9 is - removed accordingly. - However, authoritative <acronym>BIND</acronym> 9 name servers still - load zone files containing A6 records correctly, answer queries - for A6 records, and accept zone transfer for a zone containing A6 - records.</para> - - <para>For IPv6 reverse lookups, <acronym>BIND</acronym> 9 supports - the traditional "nibble" format used in the - <emphasis>ip6.arpa</emphasis> domain, as well as the older, deprecated - <emphasis>ip6.int</emphasis> domain. - <acronym>BIND</acronym> 9 formerly - supported the "binary label" (also known as "bitstring") format. - The support of binary labels, however, is now completely removed - according to the changes in RFC 3363. - Any applications in <acronym>BIND</acronym> 9 do not understand - the format any more, and will return an error if given. - In particular, an authoritative <acronym>BIND</acronym> 9 name - server rejects to load a zone file containing binary labels.</para> - - <para>For an overview of the format and structure of IPv6 addresses, - see <xref linkend="ipv6addresses"/>.</para> - - <sect2> - <title>Address Lookups Using AAAA Records</title> - - <para>The AAAA record is a parallel to the IPv4 A record. It - specifies the entire address in a single record. For - example,</para> + </sect2> + + </sect1> + <sect1> + <title>IPv6 Support in <acronym>BIND</acronym> 9</title> + + <para> + <acronym>BIND</acronym> 9 fully supports all currently + defined forms of IPv6 + name to address and address to name lookups. It will also use + IPv6 addresses to make queries when running on an IPv6 capable + system. + </para> + + <para> + For forward lookups, <acronym>BIND</acronym> 9 supports + only AAAA records. RFC 3363 deprecated the use of A6 records, + and client-side support for A6 records was accordingly removed + from <acronym>BIND</acronym> 9. + However, authoritative <acronym>BIND</acronym> 9 name servers still + load zone files containing A6 records correctly, answer queries + for A6 records, and accept zone transfer for a zone containing A6 + records. + </para> + + <para> + For IPv6 reverse lookups, <acronym>BIND</acronym> 9 supports + the traditional "nibble" format used in the + <emphasis>ip6.arpa</emphasis> domain, as well as the older, deprecated + <emphasis>ip6.int</emphasis> domain. + Older versions of <acronym>BIND</acronym> 9 + supported the "binary label" (also known as "bitstring") format, + but support of binary labels has been completely removed per + RFC 3363. + Many applications in <acronym>BIND</acronym> 9 do not understand + the binary label format at all any more, and will return an + error if given. + In particular, an authoritative <acronym>BIND</acronym> 9 + name server will not load a zone file containing binary labels. + </para> + + <para> + For an overview of the format and structure of IPv6 addresses, + see <xref linkend="ipv6addresses"/>. + </para> + + <sect2> + <title>Address Lookups Using AAAA Records</title> + + <para> + The IPv6 AAAA record is a parallel to the IPv4 A record, + and, unlike the deprecated A6 record, specifies the entire + IPv6 address in a single record. For example, + </para> <programlisting> $ORIGIN example.com. host 3600 IN AAAA 2001:db8::1 </programlisting> - <para>It is recommended that IPv4-in-IPv6 mapped addresses not - be used. If a host has an IPv4 address, use an A record, not - a AAAA, with <literal>::ffff:192.168.42.1</literal> as the - address.</para> - </sect2> - <sect2> - <title>Address to Name Lookups Using Nibble Format</title> - - <para>When looking up an address in nibble format, the address - components are simply reversed, just as in IPv4, and - <literal>ip6.arpa.</literal> is appended to the resulting name. - For example, the following would provide reverse name lookup for - a host with address - <literal>2001:db8::1</literal>.</para> + <para> + Use of IPv4-in-IPv6 mapped addresses is not recommended. + If a host has an IPv4 address, use an A record, not + a AAAA, with <literal>::ffff:192.168.42.1</literal> as + the address. + </para> + </sect2> + <sect2> + <title>Address to Name Lookups Using Nibble Format</title> + + <para> + When looking up an address in nibble format, the address + components are simply reversed, just as in IPv4, and + <literal>ip6.arpa.</literal> is appended to the + resulting name. + For example, the following would provide reverse name lookup for + a host with address + <literal>2001:db8::1</literal>. + </para> <programlisting> $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 14400 IN PTR host.example.com. </programlisting> - </sect2> - </sect1> + + </sect2> + </sect1> + </chapter> + + <chapter id="Bv9ARM.ch05"> + <title>The <acronym>BIND</acronym> 9 Lightweight Resolver</title> + <sect1> + <title>The Lightweight Resolver Library</title> + <para> + Traditionally applications have been linked with a stub resolver + library that sends recursive DNS queries to a local caching name + server. + </para> + <para> + IPv6 once introduced new complexity into the resolution process, + such as following A6 chains and DNAME records, and simultaneous + lookup of IPv4 and IPv6 addresses. Though most of the complexity was + then removed, these are hard or impossible + to implement in a traditional stub resolver. + </para> + <para> + <acronym>BIND</acronym> 9 therefore can also provide resolution + services to local clients + using a combination of a lightweight resolver library and a resolver + daemon process running on the local host. These communicate using + a simple UDP-based protocol, the "lightweight resolver protocol" + that is distinct from and simpler than the full DNS protocol. + </para> + </sect1> + <sect1 id="lwresd"> + <title>Running a Resolver Daemon</title> + + <para> + To use the lightweight resolver interface, the system must + run the resolver daemon <command>lwresd</command> or a + local + name server configured with a <command>lwres</command> + statement. + </para> + + <para> + By default, applications using the lightweight resolver library will + make + UDP requests to the IPv4 loopback address (127.0.0.1) on port 921. + The + address can be overridden by <command>lwserver</command> + lines in + <filename>/etc/resolv.conf</filename>. + </para> + + <para> + The daemon currently only looks in the DNS, but in the future + it may use other sources such as <filename>/etc/hosts</filename>, + NIS, etc. + </para> + + <para> + The <command>lwresd</command> daemon is essentially a + caching-only name server that responds to requests using the + lightweight + resolver protocol rather than the DNS protocol. Because it needs + to run on each host, it is designed to require no or minimal + configuration. + Unless configured otherwise, it uses the name servers listed on + <command>nameserver</command> lines in <filename>/etc/resolv.conf</filename> + as forwarders, but is also capable of doing the resolution + autonomously if + none are specified. + </para> + <para> + The <command>lwresd</command> daemon may also be + configured with a + <filename>named.conf</filename> style configuration file, + in + <filename>/etc/lwresd.conf</filename> by default. A name + server may also + be configured to act as a lightweight resolver daemon using the + <command>lwres</command> statement in <filename>named.conf</filename>. + </para> + + </sect1> </chapter> - <chapter id="Bv9ARM.ch05"><title>The <acronym>BIND</acronym> 9 Lightweight Resolver</title> -<sect1><title>The Lightweight Resolver Library</title> -<para>Traditionally applications have been linked with a stub resolver -library that sends recursive DNS queries to a local caching name -server.</para> -<para>IPv6 once introduced new complexity into the resolution process, -such as following A6 chains and DNAME records, and simultaneous -lookup of IPv4 and IPv6 addresses. Though most of the complexity was -then removed, these are hard or impossible -to implement in a traditional stub resolver.</para> -<para>Instead, <acronym>BIND</acronym> 9 provides resolution services to local clients -using a combination of a lightweight resolver library and a resolver -daemon process running on the local host. These communicate using -a simple UDP-based protocol, the "lightweight resolver protocol" -that is distinct from and simpler than the full DNS protocol.</para></sect1> -<sect1 id="lwresd"><title>Running a Resolver Daemon</title> - -<para>To use the lightweight resolver interface, the system must -run the resolver daemon <command>lwresd</command> or a local -name server configured with a <command>lwres</command> statement.</para> - -<para>By default, applications using the lightweight resolver library will make -UDP requests to the IPv4 loopback address (127.0.0.1) on port 921. The -address can be overridden by <command>lwserver</command> lines in -<filename>/etc/resolv.conf</filename>.</para> - -<para>The daemon currently only looks in the DNS, but in the future -it may use other sources such as <filename>/etc/hosts</filename>, -NIS, etc.</para> - -<para>The <command>lwresd</command> daemon is essentially a -caching-only name server that responds to requests using the lightweight -resolver protocol rather than the DNS protocol. Because it needs -to run on each host, it is designed to require no or minimal configuration. -Unless configured otherwise, it uses the name servers listed on -<command>nameserver</command> lines in <filename>/etc/resolv.conf</filename> -as forwarders, but is also capable of doing the resolution autonomously if -none are specified.</para> -<para>The <command>lwresd</command> daemon may also be configured with a -<filename>named.conf</filename> style configuration file, in -<filename>/etc/lwresd.conf</filename> by default. A name server may also -be configured to act as a lightweight resolver daemon using the -<command>lwres</command> statement in <filename>named.conf</filename>.</para> - -</sect1></chapter> - -<chapter id="Bv9ARM.ch06"><title><acronym>BIND</acronym> 9 Configuration Reference</title> - -<para><acronym>BIND</acronym> 9 configuration is broadly similar -to <acronym>BIND</acronym> 8; however, there are a few new areas -of configuration, such as views. <acronym>BIND</acronym> -8 configuration files should work with few alterations in <acronym>BIND</acronym> -9, although more complex configurations should be reviewed to check -if they can be more efficiently implemented using the new features -found in <acronym>BIND</acronym> 9.</para> - -<para><acronym>BIND</acronym> 4 configuration files can be converted to the new format -using the shell script -<filename>contrib/named-bootconf/named-bootconf.sh</filename>.</para> -<sect1 id="configuration_file_elements"><title>Configuration File Elements</title> -<para>Following is a list of elements used throughout the <acronym>BIND</acronym> configuration -file documentation:</para> -<informaltable colsep = "0" rowsep = "0"><tgroup cols = "2" - colsep = "0" rowsep = "0" tgroupstyle = "2Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.855in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.770in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><varname>acl_name</varname></para></entry> -<entry colname = "2"><para>The name of an <varname>address_match_list</varname> as -defined by the <command>acl</command> statement.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>address_match_list</varname></para></entry> -<entry colname = "2"><para>A list of one or more <varname>ip_addr</varname>, -<varname>ip_prefix</varname>, <varname>key_id</varname>, -or <varname>acl_name</varname> elements, see -<xref linkend="address_match_lists"/>.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>domain_name</varname></para></entry> -<entry colname = "2"><para>A quoted string which will be used as -a DNS name, for example "<literal>my.test.domain</literal>".</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>dotted_decimal</varname></para></entry> -<entry colname = "2"><para>One to four integers valued 0 through -255 separated by dots (`.'), such as <command>123</command>, -<command>45.67</command> or <command>89.123.45.67</command>.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>ip4_addr</varname></para></entry> -<entry colname = "2"><para>An IPv4 address with exactly four elements -in <varname>dotted_decimal</varname> notation.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>ip6_addr</varname></para></entry> -<entry colname = "2"><para>An IPv6 address, such as <command>2001:db8::1234</command>. -IPv6 scoped addresses that have ambiguity on their scope zones must be -disambiguated by an appropriate zone ID with the percent character -(`%') as delimiter. -It is strongly recommended to use string zone names rather than -numeric identifiers, in order to be robust against system -configuration changes. -However, since there is no standard mapping for such names and -identifier values, currently only interface names as link identifiers -are supported, assuming one-to-one mapping between interfaces and links. -For example, a link-local address <command>fe80::1</command> on the -link attached to the interface <command>ne0</command> -can be specified as <command>fe80::1%ne0</command>. -Note that on most systems link-local addresses always have the -ambiguity, and need to be disambiguated.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>ip_addr</varname></para></entry> -<entry colname = "2"><para>An <varname>ip4_addr</varname> or <varname>ip6_addr</varname>.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>ip_port</varname></para></entry> -<entry colname = "2"><para>An IP port <varname>number</varname>. -<varname>number</varname> is limited to 0 through 65535, with values -below 1024 typically restricted to use by processes running as root. -In some cases, an asterisk (`*') character can be used as a placeholder to -select a random high-numbered port.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>ip_prefix</varname></para></entry> -<entry colname = "2"><para>An IP network specified as an <varname>ip_addr</varname>, -followed by a slash (`/') and then the number of bits in the netmask. -Trailing zeros in a <varname>ip_addr</varname> may omitted. -For example, <command>127/8</command> is the network <command>127.0.0.0</command> with -netmask <command>255.0.0.0</command> and <command>1.2.3.0/28</command> is -network <command>1.2.3.0</command> with netmask <command>255.255.255.240</command>.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>key_id</varname></para></entry> -<entry colname = "2"><para>A <varname>domain_name</varname> representing -the name of a shared key, to be used for transaction security.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>key_list</varname></para></entry> -<entry colname = "2"><para>A list of one or more <varname>key_id</varname>s, -separated by semicolons and ending with a semicolon.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>number</varname></para></entry> -<entry colname = "2"><para>A non-negative 32-bit integer -(i.e., a number between 0 and 4294967295, inclusive). -Its acceptable value might further -be limited by the context in which it is used.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>path_name</varname></para></entry> -<entry colname = "2"><para>A quoted string which will be used as -a pathname, such as <filename>zones/master/my.test.domain</filename>.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>size_spec</varname></para></entry> -<entry colname = "2"><para>A number, the word <userinput>unlimited</userinput>, -or the word <userinput>default</userinput>.</para><para> -An <varname>unlimited</varname> <varname>size_spec</varname> requests unlimited -use, or the maximum available amount. A <varname>default size_spec</varname> uses -the limit that was in force when the server was started.</para><para>A <varname>number</varname> can -optionally be followed by a scaling factor: <userinput>K</userinput> or <userinput>k</userinput> for -kilobytes, <userinput>M</userinput> or <userinput>m</userinput> for -megabytes, and <userinput>G</userinput> or <userinput>g</userinput> for gigabytes, -which scale by 1024, 1024*1024, and 1024*1024*1024 respectively.</para> -<para>The value must be representable as a 64-bit unsigned integer -(0 to 18446744073709551615, inclusive). -Using <varname>unlimited</varname> is the best way -to safely set a really large number.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>yes_or_no</varname></para></entry> -<entry colname = "2"><para>Either <userinput>yes</userinput> or <userinput>no</userinput>. -The words <userinput>true</userinput> and <userinput>false</userinput> are -also accepted, as are the numbers <userinput>1</userinput> and <userinput>0</userinput>.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>dialup_option</varname></para></entry> -<entry colname = "2"><para>One of <userinput>yes</userinput>, -<userinput>no</userinput>, <userinput>notify</userinput>, -<userinput>notify-passive</userinput>, <userinput>refresh</userinput> or -<userinput>passive</userinput>. -When used in a zone, <userinput>notify-passive</userinput>, -<userinput>refresh</userinput>, and <userinput>passive</userinput> -are restricted to slave and stub zones.</para></entry> -</row> -</tbody> -</tgroup></informaltable> -<sect2 id="address_match_lists"><title>Address Match Lists</title> -<sect3><title>Syntax</title> - <programlisting><varname>address_match_list</varname> = address_match_list_element ; + <chapter id="Bv9ARM.ch06"> + <title><acronym>BIND</acronym> 9 Configuration Reference</title> + + <para> + <acronym>BIND</acronym> 9 configuration is broadly similar + to <acronym>BIND</acronym> 8; however, there are a few new + areas + of configuration, such as views. <acronym>BIND</acronym> + 8 configuration files should work with few alterations in <acronym>BIND</acronym> + 9, although more complex configurations should be reviewed to check + if they can be more efficiently implemented using the new features + found in <acronym>BIND</acronym> 9. + </para> + + <para> + <acronym>BIND</acronym> 4 configuration files can be + converted to the new format + using the shell script + <filename>contrib/named-bootconf/named-bootconf.sh</filename>. + </para> + <sect1 id="configuration_file_elements"> + <title>Configuration File Elements</title> + <para> + Following is a list of elements used throughout the <acronym>BIND</acronym> configuration + file documentation: + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="2Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.855in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.770in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>acl_name</varname> + </para> + </entry> + <entry colname="2"> + <para> + The name of an <varname>address_match_list</varname> as + defined by the <command>acl</command> statement. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>address_match_list</varname> + </para> + </entry> + <entry colname="2"> + <para> + A list of one or more + <varname>ip_addr</varname>, + <varname>ip_prefix</varname>, <varname>key_id</varname>, + or <varname>acl_name</varname> elements, see + <xref linkend="address_match_lists"/>. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>masters_list</varname> + </para> + </entry> + <entry colname="2"> + <para> + A named list of one or more <varname>ip_addr</varname> + with optional <varname>key_id</varname> and/or + <varname>ip_port</varname>. + A <varname>masters_list</varname> may include other + <varname>masters_lists</varname>. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>domain_name</varname> + </para> + </entry> + <entry colname="2"> + <para> + A quoted string which will be used as + a DNS name, for example "<literal>my.test.domain</literal>". + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>dotted_decimal</varname> + </para> + </entry> + <entry colname="2"> + <para> + One to four integers valued 0 through + 255 separated by dots (`.'), such as <command>123</command>, + <command>45.67</command> or <command>89.123.45.67</command>. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>ip4_addr</varname> + </para> + </entry> + <entry colname="2"> + <para> + An IPv4 address with exactly four elements + in <varname>dotted_decimal</varname> notation. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>ip6_addr</varname> + </para> + </entry> + <entry colname="2"> + <para> + An IPv6 address, such as <command>2001:db8::1234</command>. + IPv6 scoped addresses that have ambiguity on their scope + zones must be + disambiguated by an appropriate zone ID with the percent + character + (`%') as delimiter. + It is strongly recommended to use string zone names rather + than + numeric identifiers, in order to be robust against system + configuration changes. + However, since there is no standard mapping for such names + and + identifier values, currently only interface names as link + identifiers + are supported, assuming one-to-one mapping between + interfaces and links. + For example, a link-local address <command>fe80::1</command> on the + link attached to the interface <command>ne0</command> + can be specified as <command>fe80::1%ne0</command>. + Note that on most systems link-local addresses always have + the + ambiguity, and need to be disambiguated. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>ip_addr</varname> + </para> + </entry> + <entry colname="2"> + <para> + An <varname>ip4_addr</varname> or <varname>ip6_addr</varname>. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>ip_port</varname> + </para> + </entry> + <entry colname="2"> + <para> + An IP port <varname>number</varname>. + The <varname>number</varname> is limited to 0 + through 65535, with values + below 1024 typically restricted to use by processes running + as root. + In some cases, an asterisk (`*') character can be used as a + placeholder to + select a random high-numbered port. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>ip_prefix</varname> + </para> + </entry> + <entry colname="2"> + <para> + An IP network specified as an <varname>ip_addr</varname>, + followed by a slash (`/') and then the number of bits in the + netmask. + Trailing zeros in a <varname>ip_addr</varname> + may omitted. + For example, <command>127/8</command> is the + network <command>127.0.0.0</command> with + netmask <command>255.0.0.0</command> and <command>1.2.3.0/28</command> is + network <command>1.2.3.0</command> with netmask <command>255.255.255.240</command>. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>key_id</varname> + </para> + </entry> + <entry colname="2"> + <para> + A <varname>domain_name</varname> representing + the name of a shared key, to be used for transaction + security. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>key_list</varname> + </para> + </entry> + <entry colname="2"> + <para> + A list of one or more + <varname>key_id</varname>s, + separated by semicolons and ending with a semicolon. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>number</varname> + </para> + </entry> + <entry colname="2"> + <para> + A non-negative 32-bit integer + (i.e., a number between 0 and 4294967295, inclusive). + Its acceptable value might further + be limited by the context in which it is used. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>path_name</varname> + </para> + </entry> + <entry colname="2"> + <para> + A quoted string which will be used as + a pathname, such as <filename>zones/master/my.test.domain</filename>. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>size_spec</varname> + </para> + </entry> + <entry colname="2"> + <para> + A number, the word <userinput>unlimited</userinput>, + or the word <userinput>default</userinput>. + </para> + <para> + An <varname>unlimited</varname> <varname>size_spec</varname> requests unlimited + use, or the maximum available amount. A <varname>default size_spec</varname> uses + the limit that was in force when the server was started. + </para> + <para> + A <varname>number</varname> can optionally be + followed by a scaling factor: + <userinput>K</userinput> or <userinput>k</userinput> + for kilobytes, + <userinput>M</userinput> or <userinput>m</userinput> + for megabytes, and + <userinput>G</userinput> or <userinput>g</userinput> for gigabytes, + which scale by 1024, 1024*1024, and 1024*1024*1024 + respectively. + </para> + <para> + The value must be representable as a 64-bit unsigned integer + (0 to 18446744073709551615, inclusive). + Using <varname>unlimited</varname> is the best + way + to safely set a really large number. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>yes_or_no</varname> + </para> + </entry> + <entry colname="2"> + <para> + Either <userinput>yes</userinput> or <userinput>no</userinput>. + The words <userinput>true</userinput> and <userinput>false</userinput> are + also accepted, as are the numbers <userinput>1</userinput> + and <userinput>0</userinput>. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>dialup_option</varname> + </para> + </entry> + <entry colname="2"> + <para> + One of <userinput>yes</userinput>, + <userinput>no</userinput>, <userinput>notify</userinput>, + <userinput>notify-passive</userinput>, <userinput>refresh</userinput> or + <userinput>passive</userinput>. + When used in a zone, <userinput>notify-passive</userinput>, + <userinput>refresh</userinput>, and <userinput>passive</userinput> + are restricted to slave and stub zones. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <sect2 id="address_match_lists"> + <title>Address Match Lists</title> + <sect3> + <title>Syntax</title> + +<programlisting><varname>address_match_list</varname> = address_match_list_element ; <optional> address_match_list_element; ... </optional> <varname>address_match_list_element</varname> = <optional> ! </optional> (ip_address <optional>/length</optional> | key key_id | acl_name | { address_match_list } ) </programlisting> -</sect3> -<sect3><title>Definition and Usage</title> -<para>Address match lists are primarily used to determine access -control for various server operations. They are also used in -the <command>listen-on</command> and <command>sortlist</command> -statements. The elements -which constitute an address match list can be any of the following:</para> -<itemizedlist><listitem> - <simpara>an IP address (IPv4 or IPv6)</simpara></listitem> -<listitem> - <simpara>an IP prefix (in `/' notation)</simpara></listitem> -<listitem> - <simpara>a key ID, as defined by the <command>key</command> statement</simpara></listitem> -<listitem> - <simpara>the name of an address match list defined with -the <command>acl</command> statement</simpara></listitem> -<listitem> - <simpara>a nested address match list enclosed in braces</simpara></listitem></itemizedlist> - -<para>Elements can be negated with a leading exclamation mark (`!'), -and the match list names "any", "none", "localhost", and "localnets" -are predefined. More information on those names can be found in -the description of the acl statement.</para> - -<para>The addition of the key clause made the name of this syntactic -element something of a misnomer, since security keys can be used -to validate access without regard to a host or network address. Nonetheless, -the term "address match list" is still used throughout the documentation.</para> - -<para>When a given IP address or prefix is compared to an address -match list, the list is traversed in order until an element matches. -The interpretation of a match depends on whether the list is being used -for access control, defining listen-on ports, or in a sortlist, -and whether the element was negated.</para> - -<para>When used as an access control list, a non-negated match allows -access and a negated match denies access. If there is no match, -access is denied. The clauses <command>allow-notify</command>, -<command>allow-query</command>, <command>allow-transfer</command>, -<command>allow-update</command>, <command>allow-update-forwarding</command>, -and <command>blackhole</command> all -use address match lists this. Similarly, the listen-on option will cause -the server to not accept queries on any of the machine's addresses -which do not match the list.</para> - -<para>Because of the first-match aspect of the algorithm, an element -that defines a subset of another element in the list should come -before the broader element, regardless of whether either is negated. For -example, in -<command>1.2.3/24; ! 1.2.3.13;</command> the 1.2.3.13 element is -completely useless because the algorithm will match any lookup for -1.2.3.13 to the 1.2.3/24 element. -Using <command>! 1.2.3.13; 1.2.3/24</command> fixes -that problem by having 1.2.3.13 blocked by the negation but all -other 1.2.3.* hosts fall through.</para> -</sect3> -</sect2> - -<sect2> -<title>Comment Syntax</title> - -<para>The <acronym>BIND</acronym> 9 comment syntax allows for comments to appear -anywhere that white space may appear in a <acronym>BIND</acronym> configuration -file. To appeal to programmers of all kinds, they can be written -in the C, C++, or shell/perl style.</para> - -<sect3> -<title>Syntax</title> - -<para><programlisting>/* This is a <acronym>BIND</acronym> comment as in C */</programlisting> -<programlisting>// This is a <acronym>BIND</acronym> comment as in C++</programlisting> -<programlisting># This is a <acronym>BIND</acronym> comment as in common UNIX shells and perl</programlisting> - </para> - </sect3> - <sect3> - <title>Definition and Usage</title> -<para>Comments may appear anywhere that white space may appear in -a <acronym>BIND</acronym> configuration file.</para> -<para>C-style comments start with the two characters /* (slash, -star) and end with */ (star, slash). Because they are completely -delimited with these characters, they can be used to comment only -a portion of a line or to span multiple lines.</para> -<para>C-style comments cannot be nested. For example, the following -is not valid because the entire comment ends with the first */:</para> - <para><programlisting>/* This is the start of a comment. + + </sect3> + <sect3> + <title>Definition and Usage</title> + <para> + Address match lists are primarily used to determine access + control for various server operations. They are also used in + the <command>listen-on</command> and <command>sortlist</command> + statements. The elements + which constitute an address match list can be any of the + following: + </para> + <itemizedlist> + <listitem> + <simpara>an IP address (IPv4 or IPv6)</simpara> + </listitem> + <listitem> + <simpara>an IP prefix (in `/' notation)</simpara> + </listitem> + <listitem> + <simpara> + a key ID, as defined by the <command>key</command> + statement + </simpara> + </listitem> + <listitem> + <simpara>the name of an address match list defined with + the <command>acl</command> statement + </simpara> + </listitem> + <listitem> + <simpara>a nested address match list enclosed in braces</simpara> + </listitem> + </itemizedlist> + + <para> + Elements can be negated with a leading exclamation mark (`!'), + and the match list names "any", "none", "localhost", and + "localnets" + are predefined. More information on those names can be found in + the description of the acl statement. + </para> + + <para> + The addition of the key clause made the name of this syntactic + element something of a misnomer, since security keys can be used + to validate access without regard to a host or network address. + Nonetheless, + the term "address match list" is still used throughout the + documentation. + </para> + + <para> + When a given IP address or prefix is compared to an address + match list, the list is traversed in order until an element + matches. + The interpretation of a match depends on whether the list is being + used + for access control, defining listen-on ports, or in a sortlist, + and whether the element was negated. + </para> + + <para> + When used as an access control list, a non-negated match + allows access and a negated match denies access. If + there is no match, access is denied. The clauses + <command>allow-notify</command>, + <command>allow-query</command>, + <command>allow-query-cache</command>, + <command>allow-transfer</command>, + <command>allow-update</command>, + <command>allow-update-forwarding</command>, and + <command>blackhole</command> all use address match + lists. Similarly, the listen-on option will cause the + server to not accept queries on any of the machine's + addresses which do not match the list. + </para> + + <para> + Because of the first-match aspect of the algorithm, an element + that defines a subset of another element in the list should come + before the broader element, regardless of whether either is + negated. For + example, in + <command>1.2.3/24; ! 1.2.3.13;</command> the 1.2.3.13 + element is + completely useless because the algorithm will match any lookup for + 1.2.3.13 to the 1.2.3/24 element. + Using <command>! 1.2.3.13; 1.2.3/24</command> fixes + that problem by having 1.2.3.13 blocked by the negation but all + other 1.2.3.* hosts fall through. + </para> + </sect3> + </sect2> + + <sect2> + <title>Comment Syntax</title> + + <para> + The <acronym>BIND</acronym> 9 comment syntax allows for + comments to appear + anywhere that whitespace may appear in a <acronym>BIND</acronym> configuration + file. To appeal to programmers of all kinds, they can be written + in the C, C++, or shell/perl style. + </para> + + <sect3> + <title>Syntax</title> + + <para> + <programlisting>/* This is a <acronym>BIND</acronym> comment as in C */</programlisting> + <programlisting>// This is a <acronym>BIND</acronym> comment as in C++</programlisting> + <programlisting># This is a <acronym>BIND</acronym> comment as in common UNIX shells and perl</programlisting> + </para> + </sect3> + <sect3> + <title>Definition and Usage</title> + <para> + Comments may appear anywhere that whitespace may appear in + a <acronym>BIND</acronym> configuration file. + </para> + <para> + C-style comments start with the two characters /* (slash, + star) and end with */ (star, slash). Because they are completely + delimited with these characters, they can be used to comment only + a portion of a line or to span multiple lines. + </para> + <para> + C-style comments cannot be nested. For example, the following + is not valid because the entire comment ends with the first */: + </para> + <para> + +<programlisting>/* This is the start of a comment. This is still part of the comment. /* This is an incorrect attempt at nesting a comment. */ This is no longer in any comment. */ -</programlisting></para> - -<para>C++-style comments start with the two characters // (slash, -slash) and continue to the end of the physical line. They cannot -be continued across multiple physical lines; to have one logical -comment span multiple lines, each line must use the // pair.</para> -<para>For example:</para> - <para><programlisting>// This is the start of a comment. The next line +</programlisting> + + </para> + + <para> + C++-style comments start with the two characters // (slash, + slash) and continue to the end of the physical line. They cannot + be continued across multiple physical lines; to have one logical + comment span multiple lines, each line must use the // pair. + </para> + <para> + For example: + </para> + <para> + +<programlisting>// This is the start of a comment. The next line // is a new comment, even though it is logically // part of the previous comment. -</programlisting></para> -<para>Shell-style (or perl-style, if you prefer) comments start -with the character <literal>#</literal> (number sign) and continue to the end of the -physical line, as in C++ comments.</para> -<para>For example:</para> +</programlisting> + + </para> + <para> + Shell-style (or perl-style, if you prefer) comments start + with the character <literal>#</literal> (number sign) + and continue to the end of the + physical line, as in C++ comments. + </para> + <para> + For example: + </para> -<para><programlisting># This is the start of a comment. The next line + <para> + +<programlisting># This is the start of a comment. The next line # is a new comment, even though it is logically # part of the previous comment. </programlisting> -</para> - -<warning> - <para>You cannot use the semicolon (`;') character - to start a comment such as you would in a zone file. The - semicolon indicates the end of a configuration - statement.</para> -</warning> -</sect3> -</sect2> -</sect1> - -<sect1 id="Configuration_File_Grammar"> -<title>Configuration File Grammar</title> - - <para>A <acronym>BIND</acronym> 9 configuration consists of statements and comments. - Statements end with a semicolon. Statements and comments are the - only elements that can appear without enclosing braces. Many - statements contain a block of sub-statements, which are also - terminated with a semicolon.</para> - - <para>The following statements are supported:</para> - - <informaltable colsep = "0" rowsep = "0"> - <tgroup cols = "2" colsep = "0" rowsep = "0" tgroupstyle = - "2Level-table"> - <colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.336in"/> - <colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.778in"/> - <tbody> - <row rowsep = "0"> - <entry colname = "1"><para><command>acl</command></para></entry> - <entry colname = "2"><para>defines a named IP address -matching list, for access control and other uses.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>controls</command></para></entry> - <entry colname = "2"><para>declares control channels to be used -by the <command>rndc</command> utility.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>include</command></para></entry> - <entry colname = "2"><para>includes a file.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>key</command></para></entry> - <entry colname = "2"><para>specifies key information for use in -authentication and authorization using TSIG.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>logging</command></para></entry> - <entry colname = "2"><para>specifies what the server logs, and where -the log messages are sent.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>lwres</command></para></entry> - <entry colname = "2"><para>configures <command>named</command> to -also act as a light-weight resolver daemon (<command>lwresd</command>).</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>masters</command></para></entry> - <entry colname = "2"><para>defines a named masters list for -inclusion in stub and slave zone masters clauses.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>options</command></para></entry> - <entry colname = "2"><para>controls global server configuration -options and sets defaults for other statements.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>server</command></para></entry> - <entry colname = "2"><para>sets certain configuration options on -a per-server basis.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>trusted-keys</command></para></entry> - <entry colname = "2"><para>defines trusted DNSSEC keys.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>view</command></para></entry> - <entry colname = "2"><para>defines a view.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>zone</command></para></entry> - <entry colname = "2"><para>defines a zone.</para></entry> - </row> - </tbody> - </tgroup></informaltable> - - <para>The <command>logging</command> and - <command>options</command> statements may only occur once per - configuration.</para> - - <sect2> - <title><command>acl</command> Statement Grammar</title> - - <programlisting><command>acl</command> acl-name { - address_match_list + + </para> + + <warning> + <para> + You cannot use the semicolon (`;') character + to start a comment such as you would in a zone file. The + semicolon indicates the end of a configuration + statement. + </para> + </warning> + </sect3> + </sect2> + </sect1> + + <sect1 id="Configuration_File_Grammar"> + <title>Configuration File Grammar</title> + + <para> + A <acronym>BIND</acronym> 9 configuration consists of + statements and comments. + Statements end with a semicolon. Statements and comments are the + only elements that can appear without enclosing braces. Many + statements contain a block of sub-statements, which are also + terminated with a semicolon. + </para> + + <para> + The following statements are supported: + </para> + + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="2Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.336in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.778in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para><command>acl</command></para> + </entry> + <entry colname="2"> + <para> + defines a named IP address + matching list, for access control and other uses. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>controls</command></para> + </entry> + <entry colname="2"> + <para> + declares control channels to be used + by the <command>rndc</command> utility. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>include</command></para> + </entry> + <entry colname="2"> + <para> + includes a file. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>key</command></para> + </entry> + <entry colname="2"> + <para> + specifies key information for use in + authentication and authorization using TSIG. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>logging</command></para> + </entry> + <entry colname="2"> + <para> + specifies what the server logs, and where + the log messages are sent. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>lwres</command></para> + </entry> + <entry colname="2"> + <para> + configures <command>named</command> to + also act as a light-weight resolver daemon (<command>lwresd</command>). + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>masters</command></para> + </entry> + <entry colname="2"> + <para> + defines a named masters list for + inclusion in stub and slave zone masters clauses. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>options</command></para> + </entry> + <entry colname="2"> + <para> + controls global server configuration + options and sets defaults for other statements. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>server</command></para> + </entry> + <entry colname="2"> + <para> + sets certain configuration options on + a per-server basis. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>trusted-keys</command></para> + </entry> + <entry colname="2"> + <para> + defines trusted DNSSEC keys. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>view</command></para> + </entry> + <entry colname="2"> + <para> + defines a view. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>zone</command></para> + </entry> + <entry colname="2"> + <para> + defines a zone. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + + <para> + The <command>logging</command> and + <command>options</command> statements may only occur once + per + configuration. + </para> + + <sect2> + <title><command>acl</command> Statement Grammar</title> + +<programlisting><command>acl</command> acl-name { + address_match_list }; </programlisting> - </sect2> - <sect2 id="acl"> - <title><command>acl</command> Statement Definition and -Usage</title> - - <para>The <command>acl</command> statement assigns a symbolic - name to an address match list. It gets its name from a primary - use of address match lists: Access Control Lists (ACLs).</para> - - <para>Note that an address match list's name must be defined - with <command>acl</command> before it can be used elsewhere; no - forward references are allowed.</para> - - <para>The following ACLs are built-in:</para> - -<informaltable colsep = "0" rowsep = "0"><tgroup cols = "2" - colsep = "0" rowsep = "0" tgroupstyle = "3Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.130in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "4.000in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><command>any</command></para></entry> -<entry colname = "2"><para>Matches all hosts.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>none</command></para></entry> -<entry colname = "2"><para>Matches no hosts.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>localhost</command></para></entry> -<entry colname = "2"><para>Matches the IPv4 and IPv6 addresses of all network -interfaces on the system.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>localnets</command></para></entry> -<entry colname = "2"><para>Matches any host on an IPv4 or IPv6 network -for which the system has an interface. -Some systems do not provide a way to determine the prefix lengths of -local IPv6 addresses. -In such a case, <command>localnets</command> only matches the local -IPv6 addresses, just like <command>localhost</command>. -</para></entry> -</row> -</tbody> -</tgroup></informaltable> - -</sect2> -<sect2> - <title><command>controls</command> Statement Grammar</title> + + </sect2> + <sect2 id="acl"> + <title><command>acl</command> Statement Definition and + Usage</title> + + <para> + The <command>acl</command> statement assigns a symbolic + name to an address match list. It gets its name from a primary + use of address match lists: Access Control Lists (ACLs). + </para> + + <para> + Note that an address match list's name must be defined + with <command>acl</command> before it can be used + elsewhere; no + forward references are allowed. + </para> + + <para> + The following ACLs are built-in: + </para> + + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.130in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="4.000in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para><command>any</command></para> + </entry> + <entry colname="2"> + <para> + Matches all hosts. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>none</command></para> + </entry> + <entry colname="2"> + <para> + Matches no hosts. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>localhost</command></para> + </entry> + <entry colname="2"> + <para> + Matches the IPv4 and IPv6 addresses of all network + interfaces on the system. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>localnets</command></para> + </entry> + <entry colname="2"> + <para> + Matches any host on an IPv4 or IPv6 network + for which the system has an interface. + Some systems do not provide a way to determine the prefix + lengths of + local IPv6 addresses. + In such a case, <command>localnets</command> + only matches the local + IPv6 addresses, just like <command>localhost</command>. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + + </sect2> + <sect2> + <title><command>controls</command> Statement Grammar</title> + <programlisting><command>controls</command> { - inet ( ip_addr | * ) <optional> port ip_port </optional> allow { <replaceable> address_match_list </replaceable> } - keys { <replaceable> key_list </replaceable> }; - <optional> inet ...; </optional> + [ inet ( ip_addr | * ) [ port ip_port ] allow { <replaceable> address_match_list </replaceable> } + keys { <replaceable>key_list</replaceable> }; ] + [ inet ...; ] + [ unix <replaceable>path</replaceable> perm <replaceable>number</replaceable> owner <replaceable>number</replaceable> group <replaceable>number</replaceable> keys { <replaceable>key_list</replaceable> }; ] + [ unix ...; ] }; </programlisting> -</sect2> - -<sect2 id="controls_statement_definition_and_usage"> -<title><command>controls</command> Statement Definition and Usage</title> - - <para>The <command>controls</command> statement declares control - channels to be used by system administrators to control the - operation of the name server. These control channels are - used by the <command>rndc</command> utility to send commands to - and retrieve non-DNS results from a name server.</para> - - <para>An <command>inet</command> control channel is a TCP - socket listening at the specified - <command>ip_port</command> on the specified - <command>ip_addr</command>, which can be an IPv4 or IPv6 - address. An <command>ip_addr</command> - of <literal>*</literal> (asterisk) is interpreted as the IPv4 wildcard - address; connections will be accepted on any of the system's - IPv4 addresses. To listen on the IPv6 wildcard address, - use an <command>ip_addr</command> of <literal>::</literal>. - If you will only use <command>rndc</command> on the local host, - using the loopback address (<literal>127.0.0.1</literal> - or <literal>::1</literal>) is recommended for maximum - security. - </para> - <para> - If no port is specified, port 953 - is used. The asterisk "<literal>*</literal>" cannot be used for - <command>ip_port</command>.</para> - - <para>The ability to issue commands over the control channel is - restricted by the <command>allow</command> and - <command>keys</command> clauses. Connections to the control - channel are permitted based on the - <command>address_match_list</command>. This is for simple - IP address based filtering only; any <command>key_id</command> - elements of the <command>address_match_list</command> are - ignored. - </para> + </sect2> + + <sect2 id="controls_statement_definition_and_usage"> + <title><command>controls</command> Statement Definition and + Usage</title> + + <para> + The <command>controls</command> statement declares control + channels to be used by system administrators to control the + operation of the name server. These control channels are + used by the <command>rndc</command> utility to send + commands to and retrieve non-DNS results from a name server. + </para> + + <para> + An <command>inet</command> control channel is a TCP socket + listening at the specified <command>ip_port</command> on the + specified <command>ip_addr</command>, which can be an IPv4 or IPv6 + address. An <command>ip_addr</command> of <literal>*</literal> (asterisk) is + interpreted as the IPv4 wildcard address; connections will be + accepted on any of the system's IPv4 addresses. + To listen on the IPv6 wildcard address, + use an <command>ip_addr</command> of <literal>::</literal>. + If you will only use <command>rndc</command> on the local host, + using the loopback address (<literal>127.0.0.1</literal> + or <literal>::1</literal>) is recommended for maximum security. + </para> + + <para> + If no port is specified, port 953 is used. The asterisk + "<literal>*</literal>" cannot be used for <command>ip_port</command>. + </para> + + <para> + The ability to issue commands over the control channel is + restricted by the <command>allow</command> and + <command>keys</command> clauses. + Connections to the control channel are permitted based on the + <command>address_match_list</command>. This is for simple + IP address based filtering only; any <command>key_id</command> + elements of the <command>address_match_list</command> + are ignored. + </para> - <para>The primary authorization mechanism of the command - channel is the <command>key_list</command>, which contains - a list of <command>key_id</command>s. - Each <command>key_id</command> in - the <command>key_list</command> is authorized to execute - commands over the control channel. - See <xref linkend="rndc"/> in - <xref linkend="admin_tools"/>) for information about - configuring keys in <command>rndc</command>.</para> - -<para> -If no <command>controls</command> statement is present, -<command>named</command> will set up a default -control channel listening on the loopback address 127.0.0.1 -and its IPv6 counterpart ::1. -In this case, and also when the <command>controls</command> statement -is present but does not have a <command>keys</command> clause, -<command>named</command> will attempt to load the command channel key -from the file <filename>rndc.key</filename> in -<filename>/etc</filename> (or whatever <varname>sysconfdir</varname> -was specified as when <acronym>BIND</acronym> was built). -To create a <filename>rndc.key</filename> file, run -<userinput>rndc-confgen -a</userinput>. -</para> - - <para>The <filename>rndc.key</filename> feature was created to - ease the transition of systems from <acronym>BIND</acronym> 8, - which did not have digital signatures on its command channel messages - and thus did not have a <command>keys</command> clause. - -It makes it possible to use an existing <acronym>BIND</acronym> 8 -configuration file in <acronym>BIND</acronym> 9 unchanged, -and still have <command>rndc</command> work the same way -<command>ndc</command> worked in BIND 8, simply by executing the -command <userinput>rndc-confgen -a</userinput> after BIND 9 is -installed. -</para> + <para> + A <command>unix</command> control channel is a UNIX domain + socket listening at the specified path in the file system. + Access to the socket is specified by the <command>perm</command>, + <command>owner</command> and <command>group</command> clauses. + Note on some platforms (SunOS and Solaris) the permissions + (<command>perm</command>) are applied to the parent directory + as the permissions on the socket itself are ignored. + </para> + + <para> + The primary authorization mechanism of the command + channel is the <command>key_list</command>, which + contains a list of <command>key_id</command>s. + Each <command>key_id</command> in the <command>key_list</command> + is authorized to execute commands over the control channel. + See <xref linkend="rndc"/> in <xref linkend="admin_tools"/>) + for information about configuring keys in <command>rndc</command>. + </para> + + <para> + If no <command>controls</command> statement is present, + <command>named</command> will set up a default + control channel listening on the loopback address 127.0.0.1 + and its IPv6 counterpart ::1. + In this case, and also when the <command>controls</command> statement + is present but does not have a <command>keys</command> clause, + <command>named</command> will attempt to load the command channel key + from the file <filename>rndc.key</filename> in + <filename>/etc</filename> (or whatever <varname>sysconfdir</varname> + was specified as when <acronym>BIND</acronym> was built). + To create a <filename>rndc.key</filename> file, run + <userinput>rndc-confgen -a</userinput>. + </para> + + <para> + The <filename>rndc.key</filename> feature was created to + ease the transition of systems from <acronym>BIND</acronym> 8, + which did not have digital signatures on its command channel + messages and thus did not have a <command>keys</command> clause. + + It makes it possible to use an existing <acronym>BIND</acronym> 8 + configuration file in <acronym>BIND</acronym> 9 unchanged, + and still have <command>rndc</command> work the same way + <command>ndc</command> worked in BIND 8, simply by executing the + command <userinput>rndc-confgen -a</userinput> after BIND 9 is + installed. + </para> + + <para> + Since the <filename>rndc.key</filename> feature + is only intended to allow the backward-compatible usage of + <acronym>BIND</acronym> 8 configuration files, this + feature does not + have a high degree of configurability. You cannot easily change + the key name or the size of the secret, so you should make a + <filename>rndc.conf</filename> with your own key if you + wish to change + those things. The <filename>rndc.key</filename> file + also has its + permissions set such that only the owner of the file (the user that + <command>named</command> is running as) can access it. + If you + desire greater flexibility in allowing other users to access + <command>rndc</command> commands, then you need to create + a + <filename>rndc.conf</filename> file and make it group + readable by a group + that contains the users who should have access. + </para> + + <para> + To disable the command channel, use an empty + <command>controls</command> statement: + <command>controls { };</command>. + </para> + + </sect2> + <sect2> + <title><command>include</command> Statement Grammar</title> + <programlisting>include <replaceable>filename</replaceable>;</programlisting> + </sect2> + <sect2> + <title><command>include</command> Statement Definition and + Usage</title> + + <para> + The <command>include</command> statement inserts the + specified file at the point where the <command>include</command> + statement is encountered. The <command>include</command> + statement facilitates the administration of configuration + files + by permitting the reading or writing of some things but not + others. For example, the statement could include private keys + that are readable only by the name server. + </para> + + </sect2> + <sect2> + <title><command>key</command> Statement Grammar</title> - <para> - Since the <filename>rndc.key</filename> feature - is only intended to allow the backward-compatible usage of - <acronym>BIND</acronym> 8 configuration files, this feature does not - have a high degree of configurability. You cannot easily change - the key name or the size of the secret, so you should make a - <filename>rndc.conf</filename> with your own key if you wish to change - those things. The <filename>rndc.key</filename> file also has its - permissions set such that only the owner of the file (the user that - <command>named</command> is running as) can access it. If you - desire greater flexibility in allowing other users to access - <command>rndc</command> commands, then you need to create a - <filename>rndc.conf</filename> file and make it group readable by a group - that contains the users who should have access.</para> - - <para>The UNIX control channel type of <acronym>BIND</acronym> 8 is not supported - in <acronym>BIND</acronym> 9.0, <acronym>BIND</acronym> 9.1, - <acronym>BIND</acronym> 9.2 and <acronym>BIND</acronym> 9.3. - If it is present in the controls statement from a - <acronym>BIND</acronym> 8 configuration file, it is ignored - and a warning is logged.</para> - -<para> -To disable the command channel, use an empty <command>controls</command> -statement: <command>controls { };</command>. -</para> - - </sect2> - <sect2> - <title><command>include</command> Statement Grammar</title> - <programlisting>include <replaceable>filename</replaceable>;</programlisting> - </sect2> - <sect2> - <title><command>include</command> Statement Definition and Usage</title> - - <para>The <command>include</command> statement inserts the - specified file at the point where the <command>include</command> - statement is encountered. The <command>include</command> - statement facilitates the administration of configuration files - by permitting the reading or writing of some things but not - others. For example, the statement could include private keys - that are readable only by the name server.</para> - - </sect2> - <sect2> - <title><command>key</command> Statement Grammar</title> <programlisting>key <replaceable>key_id</replaceable> { algorithm <replaceable>string</replaceable>; secret <replaceable>string</replaceable>; }; </programlisting> - </sect2> - -<sect2> -<title><command>key</command> Statement Definition and Usage</title> - -<para>The <command>key</command> statement defines a shared -secret key for use with TSIG (see <xref linkend="tsig"/>) -or the command channel -(see <xref linkend="controls_statement_definition_and_usage"/>). -</para> - -<para> -The <command>key</command> statement can occur at the top level -of the configuration file or inside a <command>view</command> -statement. Keys defined in top-level <command>key</command> -statements can be used in all views. Keys intended for use in -a <command>controls</command> statement -(see <xref linkend="controls_statement_definition_and_usage"/>) -must be defined at the top level. -</para> - -<para>The <replaceable>key_id</replaceable>, also known as the -key name, is a domain name uniquely identifying the key. It can -be used in a <command>server</command> -statement to cause requests sent to that -server to be signed with this key, or in address match lists to -verify that incoming requests have been signed with a key -matching this name, algorithm, and secret.</para> - -<para>The <replaceable>algorithm_id</replaceable> is a string -that specifies a security/authentication algorithm. The only -algorithm currently supported with TSIG authentication is -<literal>hmac-md5</literal>. The -<replaceable>secret_string</replaceable> is the secret to be -used by the algorithm, and is treated as a base-64 encoded -string.</para> - -</sect2> - <sect2> - <title><command>logging</command> Statement Grammar</title> - <programlisting><command>logging</command> { + + </sect2> + + <sect2> + <title><command>key</command> Statement Definition and Usage</title> + + <para> + The <command>key</command> statement defines a shared + secret key for use with TSIG (see <xref linkend="tsig"/>) + or the command channel + (see <xref linkend="controls_statement_definition_and_usage"/>). + </para> + + <para> + The <command>key</command> statement can occur at the + top level + of the configuration file or inside a <command>view</command> + statement. Keys defined in top-level <command>key</command> + statements can be used in all views. Keys intended for use in + a <command>controls</command> statement + (see <xref linkend="controls_statement_definition_and_usage"/>) + must be defined at the top level. + </para> + + <para> + The <replaceable>key_id</replaceable>, also known as the + key name, is a domain name uniquely identifying the key. It can + be used in a <command>server</command> + statement to cause requests sent to that + server to be signed with this key, or in address match lists to + verify that incoming requests have been signed with a key + matching this name, algorithm, and secret. + </para> + + <para> + The <replaceable>algorithm_id</replaceable> is a string + that specifies a security/authentication algorithm. Named + supports <literal>hmac-md5</literal>, + <literal>hmac-sha1</literal>, <literal>hmac-sha224</literal>, + <literal>hmac-sha256</literal>, <literal>hmac-sha384</literal> + and <literal>hmac-sha512</literal> TSIG authentication. + Truncated hashes are supported by appending the minimum + number of required bits preceded by a dash, e.g. + <literal>hmac-sha1-80</literal>. The + <replaceable>secret_string</replaceable> is the secret + to be used by the algorithm, and is treated as a base-64 + encoded string. + </para> + + </sect2> + <sect2> + <title><command>logging</command> Statement Grammar</title> + +<programlisting><command>logging</command> { [ <command>channel</command> <replaceable>channel_name</replaceable> { ( <command>file</command> <replaceable>path name</replaceable> - [ <command>versions</command> ( <replaceable>number</replaceable> | <literal>unlimited</literal> ) ] + [ <command>versions</command> ( <replaceable>number</replaceable> | <command>unlimited</command> ) ] [ <command>size</command> <replaceable>size spec</replaceable> ] | <command>syslog</command> <replaceable>syslog_facility</replaceable> | <command>stderr</command> @@ -2381,24 +3675,32 @@ string.</para> [ <command>print-time</command> <option>yes</option> or <option>no</option>; ] }; ] [ <command>category</command> <replaceable>category_name</replaceable> { - <replaceable>channel_name</replaceable> ; [ <replaceable>channel_nam</replaceable>e ; ... ] + <replaceable>channel_name</replaceable> ; [ <replaceable>channel_name</replaceable> ; ... ] }; ] ... }; </programlisting> -</sect2> - -<sect2> -<title><command>logging</command> Statement Definition and Usage</title> -<para>The <command>logging</command> statement configures a wide -variety of logging options for the name server. Its <command>channel</command> phrase -associates output methods, format options and severity levels with -a name that can then be used with the <command>category</command> phrase -to select how various classes of messages are logged.</para> -<para>Only one <command>logging</command> statement is used to define -as many channels and categories as are wanted. If there is no <command>logging</command> statement, -the logging configuration will be:</para> + </sect2> + + <sect2> + <title><command>logging</command> Statement Definition and + Usage</title> + + <para> + The <command>logging</command> statement configures a + wide + variety of logging options for the name server. Its <command>channel</command> phrase + associates output methods, format options and severity levels with + a name that can then be used with the <command>category</command> phrase + to select how various classes of messages are logged. + </para> + <para> + Only one <command>logging</command> statement is used to + define + as many channels and categories as are wanted. If there is no <command>logging</command> statement, + the logging configuration will be: + </para> <programlisting>logging { category default { default_syslog; default_debug; }; @@ -2406,65 +3708,98 @@ the logging configuration will be:</para> }; </programlisting> -<para>In <acronym>BIND</acronym> 9, the logging configuration is only established when -the entire configuration file has been parsed. In <acronym>BIND</acronym> 8, it was -established as soon as the <command>logging</command> statement -was parsed. When the server is starting up, all logging messages -regarding syntax errors in the configuration file go to the default -channels, or to standard error if the "<option>-g</option>" option -was specified.</para> - -<sect3> -<title>The <command>channel</command> Phrase</title> - -<para>All log output goes to one or more <emphasis>channels</emphasis>; -you can make as many of them as you want.</para> - -<para>Every channel definition must include a destination clause that -says whether messages selected for the channel go to a file, to a -particular syslog facility, to the standard error stream, or are -discarded. It can optionally also limit the message severity level -that will be accepted by the channel (the default is -<command>info</command>), and whether to include a -<command>named</command>-generated time stamp, the category name -and/or severity level (the default is not to include any).</para> - -<para>The <command>null</command> destination clause -causes all messages sent to the channel to be discarded; -in that case, other options for the channel are meaningless.</para> - -<para>The <command>file</command> destination clause directs the channel -to a disk file. It can include limitations -both on how large the file is allowed to become, and how many versions -of the file will be saved each time the file is opened.</para> - -<para>If you use the <command>versions</command> log file option, then -<command>named</command> will retain that many backup versions of the file by -renaming them when opening. For example, if you choose to keep three old versions -of the file <filename>lamers.log</filename>, then just before it is opened -<filename>lamers.log.1</filename> is renamed to -<filename>lamers.log.2</filename>, <filename>lamers.log.0</filename> is renamed -to <filename>lamers.log.1</filename>, and <filename>lamers.log</filename> is -renamed to <filename>lamers.log.0</filename>. -You can say <command>versions unlimited</command> to not limit -the number of versions. -If a <command>size</command> option is associated with the log file, -then renaming is only done when the file being opened exceeds the -indicated size. No backup versions are kept by default; any existing -log file is simply appended.</para> - -<para>The <command>size</command> option for files is used to limit log -growth. If the file ever exceeds the size, then <command>named</command> will -stop writing to the file unless it has a <command>versions</command> option -associated with it. If backup versions are kept, the files are rolled as -described above and a new one begun. If there is no -<command>versions</command> option, no more data will be written to the log -until some out-of-band mechanism removes or truncates the log to less than the -maximum size. The default behavior is not to limit the size of the -file.</para> - -<para>Example usage of the <command>size</command> and -<command>versions</command> options:</para> + <para> + In <acronym>BIND</acronym> 9, the logging configuration + is only established when + the entire configuration file has been parsed. In <acronym>BIND</acronym> 8, it was + established as soon as the <command>logging</command> + statement + was parsed. When the server is starting up, all logging messages + regarding syntax errors in the configuration file go to the default + channels, or to standard error if the "<option>-g</option>" option + was specified. + </para> + + <sect3> + <title>The <command>channel</command> Phrase</title> + + <para> + All log output goes to one or more <emphasis>channels</emphasis>; + you can make as many of them as you want. + </para> + + <para> + Every channel definition must include a destination clause that + says whether messages selected for the channel go to a file, to a + particular syslog facility, to the standard error stream, or are + discarded. It can optionally also limit the message severity level + that will be accepted by the channel (the default is + <command>info</command>), and whether to include a + <command>named</command>-generated time stamp, the + category name + and/or severity level (the default is not to include any). + </para> + + <para> + The <command>null</command> destination clause + causes all messages sent to the channel to be discarded; + in that case, other options for the channel are meaningless. + </para> + + <para> + The <command>file</command> destination clause directs + the channel + to a disk file. It can include limitations + both on how large the file is allowed to become, and how many + versions + of the file will be saved each time the file is opened. + </para> + + <para> + If you use the <command>versions</command> log file + option, then + <command>named</command> will retain that many backup + versions of the file by + renaming them when opening. For example, if you choose to keep + three old versions + of the file <filename>lamers.log</filename>, then just + before it is opened + <filename>lamers.log.1</filename> is renamed to + <filename>lamers.log.2</filename>, <filename>lamers.log.0</filename> is renamed + to <filename>lamers.log.1</filename>, and <filename>lamers.log</filename> is + renamed to <filename>lamers.log.0</filename>. + You can say <command>versions unlimited</command> to + not limit + the number of versions. + If a <command>size</command> option is associated with + the log file, + then renaming is only done when the file being opened exceeds the + indicated size. No backup versions are kept by default; any + existing + log file is simply appended. + </para> + + <para> + The <command>size</command> option for files is used + to limit log + growth. If the file ever exceeds the size, then <command>named</command> will + stop writing to the file unless it has a <command>versions</command> option + associated with it. If backup versions are kept, the files are + rolled as + described above and a new one begun. If there is no + <command>versions</command> option, no more data will + be written to the log + until some out-of-band mechanism removes or truncates the log to + less than the + maximum size. The default behavior is not to limit the size of + the + file. + </para> + + <para> + Example usage of the <command>size</command> and + <command>versions</command> options: + </para> <programlisting>channel an_example_channel { file "example.log" versions 3 size 20m; @@ -2473,80 +3808,117 @@ file.</para> }; </programlisting> -<para>The <command>syslog</command> destination clause directs the -channel to the system log. Its argument is a -syslog facility as described in the <command>syslog</command> man -page. Known facilities are <command>kern</command>, <command>user</command>, -<command>mail</command>, <command>daemon</command>, <command>auth</command>, -<command>syslog</command>, <command>lpr</command>, <command>news</command>, -<command>uucp</command>, <command>cron</command>, <command>authpriv</command>, -<command>ftp</command>, <command>local0</command>, <command>local1</command>, -<command>local2</command>, <command>local3</command>, <command>local4</command>, -<command>local5</command>, <command>local6</command> and -<command>local7</command>, however not all facilities are supported on -all operating systems. -How <command>syslog</command> will handle messages sent to -this facility is described in the <command>syslog.conf</command> man -page. If you have a system which uses a very old version of <command>syslog</command> that -only uses two arguments to the <command>openlog()</command> function, -then this clause is silently ignored.</para> -<para>The <command>severity</command> clause works like <command>syslog</command>'s -"priorities", except that they can also be used if you are writing -straight to a file rather than using <command>syslog</command>. -Messages which are not at least of the severity level given will -not be selected for the channel; messages of higher severity levels -will be accepted.</para> -<para>If you are using <command>syslog</command>, then the <command>syslog.conf</command> priorities -will also determine what eventually passes through. For example, -defining a channel facility and severity as <command>daemon</command> and <command>debug</command> but -only logging <command>daemon.warning</command> via <command>syslog.conf</command> will -cause messages of severity <command>info</command> and <command>notice</command> to -be dropped. If the situation were reversed, with <command>named</command> writing -messages of only <command>warning</command> or higher, then <command>syslogd</command> would -print all messages it received from the channel.</para> - -<para>The <command>stderr</command> destination clause directs the -channel to the server's standard error stream. This is intended for -use when the server is running as a foreground process, for example -when debugging a configuration.</para> - -<para>The server can supply extensive debugging information when -it is in debugging mode. If the server's global debug level is greater -than zero, then debugging mode will be active. The global debug -level is set either by starting the <command>named</command> server -with the <option>-d</option> flag followed by a positive integer, -or by running <command>rndc trace</command>. -The global debug level -can be set to zero, and debugging mode turned off, by running <command>rndc + <para> + The <command>syslog</command> destination clause + directs the + channel to the system log. Its argument is a + syslog facility as described in the <command>syslog</command> man + page. Known facilities are <command>kern</command>, <command>user</command>, + <command>mail</command>, <command>daemon</command>, <command>auth</command>, + <command>syslog</command>, <command>lpr</command>, <command>news</command>, + <command>uucp</command>, <command>cron</command>, <command>authpriv</command>, + <command>ftp</command>, <command>local0</command>, <command>local1</command>, + <command>local2</command>, <command>local3</command>, <command>local4</command>, + <command>local5</command>, <command>local6</command> and + <command>local7</command>, however not all facilities + are supported on + all operating systems. + How <command>syslog</command> will handle messages + sent to + this facility is described in the <command>syslog.conf</command> man + page. If you have a system which uses a very old version of <command>syslog</command> that + only uses two arguments to the <command>openlog()</command> function, + then this clause is silently ignored. + </para> + <para> + The <command>severity</command> clause works like <command>syslog</command>'s + "priorities", except that they can also be used if you are writing + straight to a file rather than using <command>syslog</command>. + Messages which are not at least of the severity level given will + not be selected for the channel; messages of higher severity + levels + will be accepted. + </para> + <para> + If you are using <command>syslog</command>, then the <command>syslog.conf</command> priorities + will also determine what eventually passes through. For example, + defining a channel facility and severity as <command>daemon</command> and <command>debug</command> but + only logging <command>daemon.warning</command> via <command>syslog.conf</command> will + cause messages of severity <command>info</command> and + <command>notice</command> to + be dropped. If the situation were reversed, with <command>named</command> writing + messages of only <command>warning</command> or higher, + then <command>syslogd</command> would + print all messages it received from the channel. + </para> + + <para> + The <command>stderr</command> destination clause + directs the + channel to the server's standard error stream. This is intended + for + use when the server is running as a foreground process, for + example + when debugging a configuration. + </para> + + <para> + The server can supply extensive debugging information when + it is in debugging mode. If the server's global debug level is + greater + than zero, then debugging mode will be active. The global debug + level is set either by starting the <command>named</command> server + with the <option>-d</option> flag followed by a positive integer, + or by running <command>rndc trace</command>. + The global debug level + can be set to zero, and debugging mode turned off, by running <command>rndc notrace</command>. All debugging messages in the server have a debug -level, and higher debug levels give more detailed output. Channels -that specify a specific debug severity, for example:</para> + level, and higher debug levels give more detailed output. Channels + that specify a specific debug severity, for example: + </para> + <programlisting>channel specific_debug_level { file "foo"; severity debug 3; }; </programlisting> - <para>will get debugging output of level 3 or less any time the -server is in debugging mode, regardless of the global debugging -level. Channels with <command>dynamic</command> severity use the -server's global debug level to determine what messages to print.</para> - <para>If <command>print-time</command> has been turned on, then -the date and time will be logged. <command>print-time</command> may -be specified for a <command>syslog</command> channel, but is usually -pointless since <command>syslog</command> also prints the date and -time. If <command>print-category</command> is requested, then the -category of the message will be logged as well. Finally, if <command>print-severity</command> is -on, then the severity level of the message will be logged. The <command>print-</command> options may -be used in any combination, and will always be printed in the following -order: time, category, severity. Here is an example where all three <command>print-</command> options -are on:</para> - -<para><computeroutput>28-Feb-2000 15:05:32.863 general: notice: running</computeroutput></para> - -<para>There are four predefined channels that are used for -<command>named</command>'s default logging as follows. How they are -used is described in <xref linkend="the_category_phrase"/>. -</para> + + <para> + will get debugging output of level 3 or less any time the + server is in debugging mode, regardless of the global debugging + level. Channels with <command>dynamic</command> + severity use the + server's global debug level to determine what messages to print. + </para> + <para> + If <command>print-time</command> has been turned on, + then + the date and time will be logged. <command>print-time</command> may + be specified for a <command>syslog</command> channel, + but is usually + pointless since <command>syslog</command> also prints + the date and + time. If <command>print-category</command> is + requested, then the + category of the message will be logged as well. Finally, if <command>print-severity</command> is + on, then the severity level of the message will be logged. The <command>print-</command> options may + be used in any combination, and will always be printed in the + following + order: time, category, severity. Here is an example where all + three <command>print-</command> options + are on: + </para> + + <para> + <computeroutput>28-Feb-2000 15:05:32.863 general: notice: running</computeroutput> + </para> + + <para> + There are four predefined channels that are used for + <command>named</command>'s default logging as follows. + How they are + used is described in <xref linkend="the_category_phrase"/>. + </para> <programlisting>channel default_syslog { syslog daemon; // send to syslog's daemon @@ -2578,37 +3950,56 @@ channel null { }; </programlisting> -<para>The <command>default_debug</command> channel has the special -property that it only produces output when the server's debug level is -nonzero. It normally writes to a file called <filename>named.run</filename> -in the server's working directory.</para> - -<para>For security reasons, when the "<option>-u</option>" -command line option is used, the <filename>named.run</filename> file -is created only after <command>named</command> has changed to the -new UID, and any debug output generated while <command>named</command> is -starting up and still running as root is discarded. If you need -to capture this output, you must run the server with the "<option>-g</option>" -option and redirect standard error to a file.</para> - -<para>Once a channel is defined, it cannot be redefined. Thus you -cannot alter the built-in channels directly, but you can modify -the default logging by pointing categories at channels you have defined.</para> -</sect3> - -<sect3 id="the_category_phrase"><title>The <command>category</command> Phrase</title> - -<para>There are many categories, so you can send the logs you want -to see wherever you want, without seeing logs you don't want. If -you don't specify a list of channels for a category, then log messages -in that category will be sent to the <command>default</command> category -instead. If you don't specify a default category, the following -"default default" is used:</para> + <para> + The <command>default_debug</command> channel has the + special + property that it only produces output when the server's debug + level is + nonzero. It normally writes to a file called <filename>named.run</filename> + in the server's working directory. + </para> + + <para> + For security reasons, when the "<option>-u</option>" + command line option is used, the <filename>named.run</filename> file + is created only after <command>named</command> has + changed to the + new UID, and any debug output generated while <command>named</command> is + starting up and still running as root is discarded. If you need + to capture this output, you must run the server with the "<option>-g</option>" + option and redirect standard error to a file. + </para> + + <para> + Once a channel is defined, it cannot be redefined. Thus you + cannot alter the built-in channels directly, but you can modify + the default logging by pointing categories at channels you have + defined. + </para> + </sect3> + + <sect3 id="the_category_phrase"> + <title>The <command>category</command> Phrase</title> + + <para> + There are many categories, so you can send the logs you want + to see wherever you want, without seeing logs you don't want. If + you don't specify a list of channels for a category, then log + messages + in that category will be sent to the <command>default</command> category + instead. If you don't specify a default category, the following + "default default" is used: + </para> + <programlisting>category default { default_syslog; default_debug; }; </programlisting> -<para>As an example, let's say you want to log security events to -a file, but you also want keep the default logging behavior. You'd -specify the following:</para> + + <para> + As an example, let's say you want to log security events to + a file, but you also want keep the default logging behavior. You'd + specify the following: + </para> + <programlisting>channel my_security_channel { file "my_security_file"; severity info; @@ -2618,138 +4009,269 @@ category security { default_syslog; default_debug; };</programlisting> -<para>To discard all messages in a category, specify the <command>null</command> channel:</para> + + <para> + To discard all messages in a category, specify the <command>null</command> channel: + </para> + <programlisting>category xfer-out { null; }; category notify { null; }; </programlisting> -<para>Following are the available categories and brief descriptions -of the types of log information they contain. More -categories may be added in future <acronym>BIND</acronym> releases.</para> -<informaltable - colsep = "0" rowsep = "0"><tgroup cols = "2" - colsep = "0" rowsep = "0" tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.150in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.350in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><command>default</command></para></entry> -<entry colname = "2"><para>The default category defines the logging -options for those categories where no specific configuration has been -defined.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>general</command></para></entry> -<entry colname = "2"><para>The catch-all. Many things still aren't -classified into categories, and they all end up here.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>database</command></para></entry> -<entry colname = "2"><para>Messages relating to the databases used -internally by the name server to store zone and cache data.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>security</command></para></entry> -<entry colname = "2"><para>Approval and denial of requests.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>config</command></para></entry> -<entry colname = "2"><para>Configuration file parsing and processing.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>resolver</command></para></entry> -<entry colname = "2"><para>DNS resolution, such as the recursive -lookups performed on behalf of clients by a caching name server.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>xfer-in</command></para></entry> -<entry colname = "2"><para>Zone transfers the server is receiving.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>xfer-out</command></para></entry> -<entry colname = "2"><para>Zone transfers the server is sending.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>notify</command></para></entry> -<entry colname = "2"><para>The NOTIFY protocol.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>client</command></para></entry> -<entry colname = "2"><para>Processing of client requests.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>unmatched</command></para></entry> -<entry colname = "2"><para>Messages that named was unable to determine the -class of or for which there was no matching <command>view</command>. -A one line summary is also logged to the <command>client</command> category. -This category is best sent to a file or stderr, by default it is sent to -the <command>null</command> channel.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>network</command></para></entry> -<entry colname = "2"><para>Network operations.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>update</command></para></entry> -<entry colname = "2"><para>Dynamic updates.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>update-security</command></para></entry> -<entry colname = "2"><para>Approval and denial of update requests.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>queries</command></para></entry> -<entry colname = "2"><para>Specify where queries should be logged to.</para> -<para> -At startup, specifying the category <command>queries</command> will also -enable query logging unless <command>querylog</command> option has been -specified. -</para> -<para> -The query log entry reports the client's IP address and port number, and the -query name, class and type. It also reports whether the Recursion Desired -flag was set (+ if set, - if not set), EDNS was in use (E) or if the -query was signed (S).</para> -<para><computeroutput>client 127.0.0.1#62536: query: www.example.com IN AAAA +SE</computeroutput> -</para> -<para><computeroutput>client ::1#62537: query: www.example.net IN AAAA -SE</computeroutput> -</para> -</entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>dispatch</command></para></entry> -<entry colname = "2"><para>Dispatching of incoming packets to the -server modules where they are to be processed. -</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>dnssec</command></para></entry> -<entry colname = "2"><para>DNSSEC and TSIG protocol processing. -</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>lame-servers</command></para></entry> -<entry colname = "2"><para>Lame servers. These are misconfigurations -in remote servers, discovered by BIND 9 when trying to query -those servers during resolution. -</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>delegation-only</command></para></entry> -<entry colname = "2"><para>Delegation only. Logs queries that have have -been forced to NXDOMAIN as the result of a delegation-only zone or -a <command>delegation-only</command> in a hint or stub zone declaration. -</para></entry> -</row> -</tbody> -</tgroup></informaltable> -</sect3> -</sect2> - -<sect2> -<title><command>lwres</command> Statement Grammar</title> - -<para> This is the grammar of the <command>lwres</command> -statement in the <filename>named.conf</filename> file:</para> + + <para> + Following are the available categories and brief descriptions + of the types of log information they contain. More + categories may be added in future <acronym>BIND</acronym> releases. + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.350in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para><command>default</command></para> + </entry> + <entry colname="2"> + <para> + The default category defines the logging + options for those categories where no specific + configuration has been + defined. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>general</command></para> + </entry> + <entry colname="2"> + <para> + The catch-all. Many things still aren't + classified into categories, and they all end up here. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>database</command></para> + </entry> + <entry colname="2"> + <para> + Messages relating to the databases used + internally by the name server to store zone and cache + data. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>security</command></para> + </entry> + <entry colname="2"> + <para> + Approval and denial of requests. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>config</command></para> + </entry> + <entry colname="2"> + <para> + Configuration file parsing and processing. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>resolver</command></para> + </entry> + <entry colname="2"> + <para> + DNS resolution, such as the recursive + lookups performed on behalf of clients by a caching name + server. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>xfer-in</command></para> + </entry> + <entry colname="2"> + <para> + Zone transfers the server is receiving. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>xfer-out</command></para> + </entry> + <entry colname="2"> + <para> + Zone transfers the server is sending. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>notify</command></para> + </entry> + <entry colname="2"> + <para> + The NOTIFY protocol. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>client</command></para> + </entry> + <entry colname="2"> + <para> + Processing of client requests. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>unmatched</command></para> + </entry> + <entry colname="2"> + <para> + Messages that named was unable to determine the + class of or for which there was no matching <command>view</command>. + A one line summary is also logged to the <command>client</command> category. + This category is best sent to a file or stderr, by + default it is sent to + the <command>null</command> channel. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>network</command></para> + </entry> + <entry colname="2"> + <para> + Network operations. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>update</command></para> + </entry> + <entry colname="2"> + <para> + Dynamic updates. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>update-security</command></para> + </entry> + <entry colname="2"> + <para> + Approval and denial of update requests. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>queries</command></para> + </entry> + <entry colname="2"> + <para> + Specify where queries should be logged to. + </para> + <para> + At startup, specifying the category <command>queries</command> will also + enable query logging unless <command>querylog</command> option has been + specified. + </para> + <para> + The query log entry reports the client's IP address and + port number, and the + query name, class and type. It also reports whether the + Recursion Desired + flag was set (+ if set, - if not set), EDNS was in use + (E) or if the + query was signed (S). + </para> + <para> + <computeroutput>client 127.0.0.1#62536: query: www.example.com IN AAAA +SE</computeroutput> + </para> + <para> + <computeroutput>client ::1#62537: query: www.example.net IN AAAA -SE</computeroutput> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>dispatch</command></para> + </entry> + <entry colname="2"> + <para> + Dispatching of incoming packets to the + server modules where they are to be processed. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>dnssec</command></para> + </entry> + <entry colname="2"> + <para> + DNSSEC and TSIG protocol processing. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>lame-servers</command></para> + </entry> + <entry colname="2"> + <para> + Lame servers. These are misconfigurations + in remote servers, discovered by BIND 9 when trying to + query + those servers during resolution. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>delegation-only</command></para> + </entry> + <entry colname="2"> + <para> + Delegation only. Logs queries that have have + been forced to NXDOMAIN as the result of a + delegation-only zone or + a <command>delegation-only</command> in a + hint or stub zone declaration. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + </sect3> + </sect2> + + <sect2> + <title><command>lwres</command> Statement Grammar</title> + + <para> + This is the grammar of the <command>lwres</command> + statement in the <filename>named.conf</filename> file: + </para> <programlisting><command>lwres</command> { <optional> listen-on { <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> @@ -2759,55 +4281,87 @@ statement in the <filename>named.conf</filename> file:</para> }; </programlisting> -</sect2> -<sect2> -<title><command>lwres</command> Statement Definition and Usage</title> - -<para>The <command>lwres</command> statement configures the name -server to also act as a lightweight resolver server. (See -<xref linkend="lwresd"/>.) There may be be multiple -<command>lwres</command> statements configuring -lightweight resolver servers with different properties.</para> - -<para>The <command>listen-on</command> statement specifies a list of -addresses (and ports) that this instance of a lightweight resolver daemon -should accept requests on. If no port is specified, port 921 is used. -If this statement is omitted, requests will be accepted on 127.0.0.1, -port 921.</para> - -<para>The <command>view</command> statement binds this instance of a -lightweight resolver daemon to a view in the DNS namespace, so that the -response will be constructed in the same manner as a normal DNS query -matching this view. If this statement is omitted, the default view is -used, and if there is no default view, an error is triggered.</para> - -<para>The <command>search</command> statement is equivalent to the -<command>search</command> statement in -<filename>/etc/resolv.conf</filename>. It provides a list of domains -which are appended to relative names in queries.</para> - -<para>The <command>ndots</command> statement is equivalent to the -<command>ndots</command> statement in -<filename>/etc/resolv.conf</filename>. It indicates the minimum -number of dots in a relative domain name that should result in an -exact match lookup before search path elements are appended.</para> -</sect2> -<sect2> - <title><command>masters</command> Statement Grammar</title> + </sect2> + <sect2> + <title><command>lwres</command> Statement Definition and Usage</title> + + <para> + The <command>lwres</command> statement configures the + name + server to also act as a lightweight resolver server. (See + <xref linkend="lwresd"/>.) There may be multiple + <command>lwres</command> statements configuring + lightweight resolver servers with different properties. + </para> + + <para> + The <command>listen-on</command> statement specifies a + list of + addresses (and ports) that this instance of a lightweight resolver + daemon + should accept requests on. If no port is specified, port 921 is + used. + If this statement is omitted, requests will be accepted on + 127.0.0.1, + port 921. + </para> + + <para> + The <command>view</command> statement binds this + instance of a + lightweight resolver daemon to a view in the DNS namespace, so that + the + response will be constructed in the same manner as a normal DNS + query + matching this view. If this statement is omitted, the default view + is + used, and if there is no default view, an error is triggered. + </para> + + <para> + The <command>search</command> statement is equivalent to + the + <command>search</command> statement in + <filename>/etc/resolv.conf</filename>. It provides a + list of domains + which are appended to relative names in queries. + </para> + + <para> + The <command>ndots</command> statement is equivalent to + the + <command>ndots</command> statement in + <filename>/etc/resolv.conf</filename>. It indicates the + minimum + number of dots in a relative domain name that should result in an + exact match lookup before search path elements are appended. + </para> + </sect2> + <sect2> + <title><command>masters</command> Statement Grammar</title> + <programlisting> -<command>masters</command> <replaceable>name</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> | <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> } ; +<command>masters</command> <replaceable>name</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> | <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> }; </programlisting> -</sect2> -<sect2> - <title><command>masters</command> Statement Definition and Usage </title> -<para><command>masters</command> lists allow for a common set of masters -to be easily used by multiple stub and slave zones.</para> -</sect2> -<sect2> -<title><command>options</command> Statement Grammar</title> - -<para>This is the grammar of the <command>options</command> -statement in the <filename>named.conf</filename> file:</para> + + </sect2> + + <sect2> + <title><command>masters</command> Statement Definition and + Usage</title> + <para><command>masters</command> + lists allow for a common set of masters to be easily used by + multiple stub and slave zones. + </para> + </sect2> + + <sect2> + <title><command>options</command> Statement Grammar</title> + + <para> + This is the grammar of the <command>options</command> + statement in the <filename>named.conf</filename> file: + </para> <programlisting>options { <optional> version <replaceable>version_string</replaceable>; </optional> @@ -2822,6 +4376,7 @@ statement in the <filename>named.conf</filename> file:</para> <optional> dump-file <replaceable>path_name</replaceable>; </optional> <optional> memstatistics-file <replaceable>path_name</replaceable>; </optional> <optional> pid-file <replaceable>path_name</replaceable>; </optional> + <optional> recursing-file <replaceable>path_name</replaceable>; </optional> <optional> statistics-file <replaceable>path_name</replaceable>; </optional> <optional> zone-statistics <replaceable>yes_or_no</replaceable>; </optional> <optional> auth-nxdomain <replaceable>yes_or_no</replaceable>; </optional> @@ -2835,31 +4390,52 @@ statement in the <filename>named.conf</filename> file:</para> <optional> host-statistics-max <replaceable>number</replaceable>; </optional> <optional> minimal-responses <replaceable>yes_or_no</replaceable>; </optional> <optional> multiple-cnames <replaceable>yes_or_no</replaceable>; </optional> - <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable>; </optional> + <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable> | <replaceable>master-only</replaceable>; </optional> <optional> recursion <replaceable>yes_or_no</replaceable>; </optional> <optional> rfc2308-type1 <replaceable>yes_or_no</replaceable>; </optional> <optional> use-id-pool <replaceable>yes_or_no</replaceable>; </optional> <optional> maintain-ixfr-base <replaceable>yes_or_no</replaceable>; </optional> <optional> dnssec-enable <replaceable>yes_or_no</replaceable>; </optional> + <optional> dnssec-validation <replaceable>yes_or_no</replaceable>; </optional> <optional> dnssec-lookaside <replaceable>domain</replaceable> trust-anchor <replaceable>domain</replaceable>; </optional> <optional> dnssec-must-be-secure <replaceable>domain yes_or_no</replaceable>; </optional> + <optional> dnssec-accept-expired <replaceable>yes_or_no</replaceable>; </optional> <optional> forward ( <replaceable>only</replaceable> | <replaceable>first</replaceable> ); </optional> <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> - <optional> dual-stack-servers <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>domain_name</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> | <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ) ; ... }; </optional> - <optional> check-names ( <replaceable>master</replaceable> | <replaceable>slave</replaceable> | <replaceable>response</replaceable> )( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional> + <optional> dual-stack-servers <optional>port <replaceable>ip_port</replaceable></optional> { + ( <replaceable>domain_name</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> | + <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ) ; + ... }; </optional> + <optional> check-names ( <replaceable>master</replaceable> | <replaceable>slave</replaceable> | <replaceable>response</replaceable> ) + ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional> + <optional> check-mx ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional> + <optional> check-wildcard <replaceable>yes_or_no</replaceable>; </optional> + <optional> check-integrity <replaceable>yes_or_no</replaceable>; </optional> + <optional> check-mx-cname ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional> + <optional> check-srv-cname ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional> + <optional> check-sibling <replaceable>yes_or_no</replaceable>; </optional> <optional> allow-notify { <replaceable>address_match_list</replaceable> }; </optional> <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional> + <optional> allow-query-cache { <replaceable>address_match_list</replaceable> }; </optional> <optional> allow-transfer { <replaceable>address_match_list</replaceable> }; </optional> <optional> allow-recursion { <replaceable>address_match_list</replaceable> }; </optional> + <optional> allow-update { <replaceable>address_match_list</replaceable> }; </optional> <optional> allow-update-forwarding { <replaceable>address_match_list</replaceable> }; </optional> + <optional> update-check-ksk <replaceable>yes_or_no</replaceable>; </optional> <optional> allow-v6-synthesis { <replaceable>address_match_list</replaceable> }; </optional> <optional> blackhole { <replaceable>address_match_list</replaceable> }; </optional> <optional> avoid-v4-udp-ports { <replaceable>port_list</replaceable> }; </optional> <optional> avoid-v6-udp-ports { <replaceable>port_list</replaceable> }; </optional> <optional> listen-on <optional> port <replaceable>ip_port</replaceable> </optional> { <replaceable>address_match_list</replaceable> }; </optional> <optional> listen-on-v6 <optional> port <replaceable>ip_port</replaceable> </optional> { <replaceable>address_match_list</replaceable> }; </optional> - <optional> query-source <optional> address ( <replaceable>ip_addr</replaceable> | <replaceable>*</replaceable> ) </optional> <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional>; </optional> - <optional> query-source-v6 <optional> address ( <replaceable>ip_addr</replaceable> | <replaceable>*</replaceable> ) </optional> <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional>; </optional> + <optional> query-source ( ( <replaceable>ip4_addr</replaceable> | <replaceable>*</replaceable> ) + <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional> | + <optional> address ( <replaceable>ip4_addr</replaceable> | <replaceable>*</replaceable> ) </optional> + <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional> ) ; </optional> + <optional> query-source-v6 ( ( <replaceable>ip6_addr</replaceable> | <replaceable>*</replaceable> ) + <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional> | + <optional> address ( <replaceable>ip6_addr</replaceable> | <replaceable>*</replaceable> ) </optional> + <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional> ) ; </optional> <optional> max-transfer-time-in <replaceable>number</replaceable>; </optional> <optional> max-transfer-time-out <replaceable>number</replaceable>; </optional> <optional> max-transfer-idle-in <replaceable>number</replaceable>; </optional> @@ -2878,6 +4454,7 @@ statement in the <filename>named.conf</filename> file:</para> <optional> alt-transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> <optional> alt-transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> <optional> use-alt-transfer-source <replaceable>yes_or_no</replaceable>; </optional> + <optional> notify-delay <replaceable>seconds</replaceable> ; </optional> <optional> notify-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> <optional> notify-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> <optional> also-notify { <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> @@ -2915,69 +4492,128 @@ statement in the <filename>named.conf</filename> file:</para> <optional> match-mapped-addresses <replaceable>yes_or_no</replaceable>; </optional> <optional> preferred-glue ( <replaceable>A</replaceable> | <replaceable>AAAA</replaceable> | <replaceable>NONE</replaceable> ); </optional> <optional> edns-udp-size <replaceable>number</replaceable>; </optional> + <optional> max-udp-size <replaceable>number</replaceable>; </optional> <optional> root-delegation-only <optional> exclude { <replaceable>namelist</replaceable> } </optional> ; </optional> <optional> querylog <replaceable>yes_or_no</replaceable> ; </optional> <optional> disable-algorithms <replaceable>domain</replaceable> { <replaceable>algorithm</replaceable>; <optional> <replaceable>algorithm</replaceable>; </optional> }; </optional> + <optional> acache-enable <replaceable>yes_or_no</replaceable> ; </optional> + <optional> acache-cleaning-interval <replaceable>number</replaceable>; </optional> + <optional> max-acache-size <replaceable>size_spec</replaceable> ; </optional> + <optional> clients-per-query <replaceable>number</replaceable> ; </optional> + <optional> max-clients-per-query <replaceable>number</replaceable> ; </optional> + <optional> masterfile-format (<constant>text</constant>|<constant>raw</constant>) ; </optional> + <optional> empty-server <replaceable>name</replaceable> ; </optional> + <optional> empty-contact <replaceable>name</replaceable> ; </optional> + <optional> empty-zones-enable <replaceable>yes_or_no</replaceable> ; </optional> + <optional> disable-empty-zone <replaceable>zone_name</replaceable> ; </optional> + <optional> zero-no-soa-ttl <replaceable>yes_or_no</replaceable> ; </optional> + <optional> zero-no-soa-ttl-cache <replaceable>yes_or_no</replaceable> ; </optional> }; </programlisting> -</sect2> - -<sect2 id="options"><title><command>options</command> Statement Definition and Usage</title> - -<para>The <command>options</command> statement sets up global options -to be used by <acronym>BIND</acronym>. This statement may appear only -once in a configuration file. If there is no <command>options</command> -statement, an options block with each option set to its default will -be used.</para> - -<variablelist> - -<varlistentry><term><command>directory</command></term> -<listitem><para>The working directory of the server. -Any non-absolute pathnames in the configuration file will be taken -as relative to this directory. The default location for most server -output files (e.g. <filename>named.run</filename>) is this directory. -If a directory is not specified, the working directory defaults -to `<filename>.</filename>', the directory from which the server -was started. The directory specified should be an absolute path.</para> -</listitem></varlistentry> - -<varlistentry><term><command>key-directory</command></term> -<listitem><para>When performing dynamic update of secure zones, the -directory where the public and private key files should be found, -if different than the current working directory. The directory specified -must be an absolute path.</para> -</listitem></varlistentry> - -<varlistentry><term><command>named-xfer</command></term> -<listitem><para><emphasis>This option is obsolete.</emphasis> -It was used in <acronym>BIND</acronym> 8 to -specify the pathname to the <command>named-xfer</command> program. -In <acronym>BIND</acronym> 9, no separate <command>named-xfer</command> program is -needed; its functionality is built into the name server.</para> - -</listitem></varlistentry> - -<varlistentry><term><command>tkey-domain</command></term> -<listitem><para>The domain appended to the names of all -shared keys generated with <command>TKEY</command>. When a client -requests a <command>TKEY</command> exchange, it may or may not specify -the desired name for the key. If present, the name of the shared -key will be "<varname>client specified part</varname>" + -"<varname>tkey-domain</varname>". -Otherwise, the name of the shared key will be "<varname>random hex + + </sect2> + + <sect2 id="options"> + <title><command>options</command> Statement Definition and + Usage</title> + + <para> + The <command>options</command> statement sets up global + options + to be used by <acronym>BIND</acronym>. This statement + may appear only + once in a configuration file. If there is no <command>options</command> + statement, an options block with each option set to its default will + be used. + </para> + + <variablelist> + + <varlistentry> + <term><command>directory</command></term> + <listitem> + <para> + The working directory of the server. + Any non-absolute pathnames in the configuration file will be + taken + as relative to this directory. The default location for most + server + output files (e.g. <filename>named.run</filename>) + is this directory. + If a directory is not specified, the working directory + defaults to `<filename>.</filename>', the directory from + which the server + was started. The directory specified should be an absolute + path. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>key-directory</command></term> + <listitem> + <para> + When performing dynamic update of secure zones, the + directory where the public and private key files should be + found, + if different than the current working directory. The + directory specified + must be an absolute path. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>named-xfer</command></term> + <listitem> + <para> + <emphasis>This option is obsolete.</emphasis> + It was used in <acronym>BIND</acronym> 8 to + specify the pathname to the <command>named-xfer</command> program. + In <acronym>BIND</acronym> 9, no separate <command>named-xfer</command> program is + needed; its functionality is built into the name server. + </para> + + </listitem> + </varlistentry> + + <varlistentry> + <term><command>tkey-domain</command></term> + <listitem> + <para> + The domain appended to the names of all + shared keys generated with + <command>TKEY</command>. When a client + requests a <command>TKEY</command> exchange, it + may or may not specify + the desired name for the key. If present, the name of the + shared + key will be "<varname>client specified part</varname>" + + "<varname>tkey-domain</varname>". + Otherwise, the name of the shared key will be "<varname>random hex digits</varname>" + "<varname>tkey-domain</varname>". In most cases, -the <command>domainname</command> should be the server's domain -name.</para> -</listitem></varlistentry> - -<varlistentry><term><command>tkey-dhkey</command></term> -<listitem><para>The Diffie-Hellman key used by the server -to generate shared keys with clients using the Diffie-Hellman mode -of <command>TKEY</command>. The server must be able to load the -public and private keys from files in the working directory. In -most cases, the keyname should be the server's host name.</para> -</listitem></varlistentry> + the <command>domainname</command> should be the + server's domain + name. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>tkey-dhkey</command></term> + <listitem> + <para> + The Diffie-Hellman key used by the server + to generate shared keys with clients using the Diffie-Hellman + mode + of <command>TKEY</command>. The server must be + able to load the + public and private keys from files in the working directory. + In + most cases, the keyname should be the server's host name. + </para> + </listitem> + </varlistentry> <varlistentry> <term><command>cache-file</command></term> @@ -2988,877 +4624,1727 @@ most cases, the keyname should be the server's host name.</para> </listitem> </varlistentry> -<varlistentry><term><command>dump-file</command></term> -<listitem><para>The pathname of the file the server dumps -the database to when instructed to do so with -<command>rndc dumpdb</command>. -If not specified, the default is <filename>named_dump.db</filename>.</para> -</listitem></varlistentry> -<varlistentry><term><command>memstatistics-file</command></term> -<listitem><para>The pathname of the file the server writes memory -usage statistics to on exit. If not specified, -the default is <filename>named.memstats</filename>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>pid-file</command></term> -<listitem><para>The pathname of the file the server writes its process ID -in. If not specified, the default is <filename>/var/run/named.pid</filename>. -The pid-file is used by programs that want to send signals to the running -name server. Specifying <command>pid-file none</command> disables the -use of a PID file — no file will be written and any -existing one will be removed. Note that <command>none</command> -is a keyword, not a file name, and therefore is not enclosed in -double quotes.</para> -</listitem></varlistentry> - -<varlistentry><term><command>statistics-file</command></term> -<listitem><para>The pathname of the file the server appends statistics -to when instructed to do so using <command>rndc stats</command>. -If not specified, the default is <filename>named.stats</filename> in the -server's current directory. The format of the file is described -in <xref linkend="statsfile"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>port</command></term> -<listitem><para> -The UDP/TCP port number the server uses for -receiving and sending DNS protocol traffic. -The default is 53. This option is mainly intended for server testing; -a server using a port other than 53 will not be able to communicate with -the global DNS. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>random-device</command></term> -<listitem><para> -The source of entropy to be used by the server. Entropy is primarily needed -for DNSSEC operations, such as TKEY transactions and dynamic update of signed -zones. This option specifies the device (or file) from which to read -entropy. If this is a file, operations requiring entropy will fail when the -file has been exhausted. If not specified, the default value is -<filename>/dev/random</filename> -(or equivalent) when present, and none otherwise. The -<command>random-device</command> option takes effect during -the initial configuration load at server startup time and -is ignored on subsequent reloads.</para> -</listitem></varlistentry> - -<varlistentry><term><command>preferred-glue</command></term> -<listitem><para> -If specified, the listed type (A or AAAA) will be emitted before other glue -in the additional section of a query response. -The default is not to prefer any type (NONE). -</para> -</listitem></varlistentry> - -<varlistentry><term><command>root-delegation-only</command></term> -<listitem><para> -Turn on enforcement of delegation-only in TLDs (top level domains) -and root zones with an optional exclude list. -</para> -<para> -Note some TLDs are not delegation only (e.g. "DE", "LV", "US" and "MUSEUM"). -</para> + <varlistentry> + <term><command>dump-file</command></term> + <listitem> + <para> + The pathname of the file the server dumps + the database to when instructed to do so with + <command>rndc dumpdb</command>. + If not specified, the default is <filename>named_dump.db</filename>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>memstatistics-file</command></term> + <listitem> + <para> + The pathname of the file the server writes memory + usage statistics to on exit. If specified the + statistics will be written to the file on exit. + </para> + <para> + In <acronym>BIND</acronym> 9.5 and later this will + default to <filename>named.memstats</filename>. + <acronym>BIND</acronym> 9.5 will also introduce + <command>memstatistics</command> to control the + writing. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>pid-file</command></term> + <listitem> + <para> + The pathname of the file the server writes its process ID + in. If not specified, the default is <filename>/var/run/named.pid</filename>. + The pid-file is used by programs that want to send signals to + the running + name server. Specifying <command>pid-file none</command> disables the + use of a PID file — no file will be written and any + existing one will be removed. Note that <command>none</command> + is a keyword, not a filename, and therefore is not enclosed + in + double quotes. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>recursing-file</command></term> + <listitem> + <para> + The pathname of the file the server dumps + the queries that are currently recursing when instructed + to do so with <command>rndc recursing</command>. + If not specified, the default is <filename>named.recursing</filename>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>statistics-file</command></term> + <listitem> + <para> + The pathname of the file the server appends statistics + to when instructed to do so using <command>rndc stats</command>. + If not specified, the default is <filename>named.stats</filename> in the + server's current directory. The format of the file is + described + in <xref linkend="statsfile"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>port</command></term> + <listitem> + <para> + The UDP/TCP port number the server uses for + receiving and sending DNS protocol traffic. + The default is 53. This option is mainly intended for server + testing; + a server using a port other than 53 will not be able to + communicate with + the global DNS. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>random-device</command></term> + <listitem> + <para> + The source of entropy to be used by the server. Entropy is + primarily needed + for DNSSEC operations, such as TKEY transactions and dynamic + update of signed + zones. This options specifies the device (or file) from which + to read + entropy. If this is a file, operations requiring entropy will + fail when the + file has been exhausted. If not specified, the default value + is + <filename>/dev/random</filename> + (or equivalent) when present, and none otherwise. The + <command>random-device</command> option takes + effect during + the initial configuration load at server startup time and + is ignored on subsequent reloads. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>preferred-glue</command></term> + <listitem> + <para> + If specified, the listed type (A or AAAA) will be emitted + before other glue + in the additional section of a query response. + The default is not to prefer any type (NONE). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>root-delegation-only</command></term> + <listitem> + <para> + Turn on enforcement of delegation-only in TLDs (top level domains) and root zones + with an optional + exclude list. + </para> + <para> + Note some TLDs are not delegation only (e.g. "DE", "LV", "US" + and "MUSEUM"). + </para> + <programlisting> options { root-delegation-only exclude { "de"; "lv"; "us"; "museum"; }; }; </programlisting> -</listitem></varlistentry> - -<varlistentry><term><command>disable-algorithms</command></term> -<listitem><para> -Disable the specified DNSSEC algorithms at and below the specified name. -Multiple <command>disable-algorithms</command> statements are allowed. -Only the most specific will be applied. -</para></listitem></varlistentry> - -<varlistentry><term><command>dnssec-lookaside</command></term> -<listitem><para> -When set, <command>dnssec-lookaside</command> provides the -validator with an alternate method to validate DNSKEY records at the -top of a zone. When a DNSKEY is at or below a domain specified by the -deepest <command>dnssec-lookaside</command>, and the normal dnssec validation -has left the key untrusted, the trust-anchor will be append to the key -name and a DLV record will be looked up to see if it can validate the -key. If the DLV record validates a DNSKEY (similarly to the way a DS -record does) the DNSKEY RRset is deemed to be trusted. -</para></listitem></varlistentry> - -<varlistentry><term><command>dnssec-must-be-secure</command></term> -<listitem><para> -Specify heirarchies which must be or may not be secure (signed and validated). -If <userinput>yes</userinput>, then named will only accept answers if they -are secure. -If <userinput>no</userinput>, then normal dnssec validation applies -allowing for insecure answers to be accepted. -The specified domain must be under a <command>trusted-key</command> or -<command>dnssec-lookaside</command> must be active. -</para></listitem></varlistentry> - -</variablelist> - -<sect3 id="boolean_options"><title>Boolean Options</title> - -<variablelist> - -<varlistentry><term><command>auth-nxdomain</command></term> -<listitem><para>If <userinput>yes</userinput>, then the <command>AA</command> bit -is always set on NXDOMAIN responses, even if the server is not actually -authoritative. The default is <userinput>no</userinput>; this is -a change from <acronym>BIND</acronym> 8. If you are using very old DNS software, you -may need to set it to <userinput>yes</userinput>.</para></listitem></varlistentry> - -<varlistentry><term><command>deallocate-on-exit</command></term> -<listitem><para>This option was used in <acronym>BIND</acronym> 8 to enable checking -for memory leaks on exit. <acronym>BIND</acronym> 9 ignores the option and always performs -the checks.</para></listitem></varlistentry> - -<varlistentry><term><command>dialup</command></term> -<listitem><para>If <userinput>yes</userinput>, then the -server treats all zones as if they are doing zone transfers across -a dial-on-demand dialup link, which can be brought up by traffic -originating from this server. This has different effects according -to zone type and concentrates the zone maintenance so that it all -happens in a short interval, once every <command>heartbeat-interval</command> and -hopefully during the one call. It also suppresses some of the normal -zone maintenance traffic. The default is <userinput>no</userinput>.</para> -<para>The <command>dialup</command> option -may also be specified in the <command>view</command> and -<command>zone</command> statements, -in which case it overrides the global <command>dialup</command> -option.</para> -<para>If the zone is a master zone, then the server will send out a NOTIFY -request to all the slaves (default). This should 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. -The set of servers to which NOTIFY is sent can be controlled by -<command>notify</command> and <command>also-notify</command>.</para> -<para>If 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 -<command>heartbeat-interval</command> expires in addition to sending -NOTIFY requests.</para><para>Finer control can be achieved by using -<userinput>notify</userinput> which only sends NOTIFY messages, -<userinput>notify-passive</userinput> which sends NOTIFY messages and -suppresses the normal refresh queries, <userinput>refresh</userinput> -which suppresses normal refresh processing and sends refresh queries -when the <command>heartbeat-interval</command> expires, and -<userinput>passive</userinput> which just disables normal refresh -processing.</para> - -<informaltable colsep = "0" rowsep = "0"> -<tgroup cols = "4" colsep = "0" rowsep = "0" tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.150in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "1.150in"/> -<colspec colname = "3" colnum = "3" colsep = "0" colwidth = "1.150in"/> -<colspec colname = "4" colnum = "4" colsep = "0" colwidth = "1.150in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para>dialup mode</para></entry> -<entry colname = "2"><para>normal refresh</para></entry> -<entry colname = "3"><para>heart-beat refresh</para></entry> -<entry colname = "4"><para>heart-beat notify</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>no</command> (default)</para></entry> -<entry colname = "2"><para>yes</para></entry> -<entry colname = "3"><para>no</para></entry> -<entry colname = "4"><para>no</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>yes</command></para></entry> -<entry colname = "2"><para>no</para></entry> -<entry colname = "3"><para>yes</para></entry> -<entry colname = "4"><para>yes</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>notify</command></para></entry> -<entry colname = "2"><para>yes</para></entry> -<entry colname = "3"><para>no</para></entry> -<entry colname = "4"><para>yes</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>refresh</command></para></entry> -<entry colname = "2"><para>no</para></entry> -<entry colname = "3"><para>yes</para></entry> -<entry colname = "4"><para>no</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>passive</command></para></entry> -<entry colname = "2"><para>no</para></entry> -<entry colname = "3"><para>no</para></entry> -<entry colname = "4"><para>no</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>notify-passive</command></para></entry> -<entry colname = "2"><para>no</para></entry> -<entry colname = "3"><para>no</para></entry> -<entry colname = "4"><para>yes</para></entry> -</row> -</tbody> -</tgroup></informaltable> - -<para>Note that normal NOTIFY processing is not affected by -<command>dialup</command>.</para> - -</listitem></varlistentry> - -<varlistentry><term><command>fake-iquery</command></term> -<listitem><para>In <acronym>BIND</acronym> 8, this option -enabled simulating the obsolete DNS query type -IQUERY. <acronym>BIND</acronym> 9 never does IQUERY simulation. -</para></listitem></varlistentry> - -<varlistentry><term><command>fetch-glue</command></term> -<listitem><para>This option is obsolete. -In BIND 8, <userinput>fetch-glue yes</userinput> -caused the server to attempt to fetch glue resource records it -didn't have when constructing the additional -data section of a response. This is now considered a bad idea -and BIND 9 never does it.</para></listitem></varlistentry> - -<varlistentry><term><command>flush-zones-on-shutdown</command></term> -<listitem><para>When the nameserver exits due receiving SIGTERM, -flush or do not flush any pending zone writes. The default is -<command>flush-zones-on-shutdown</command> <userinput>no</userinput>. -</para></listitem></varlistentry> - -<varlistentry><term><command>has-old-clients</command></term> -<listitem><para>This option was incorrectly implemented -in <acronym>BIND</acronym> 8, and is ignored by <acronym>BIND</acronym> 9. -To achieve the intended effect -of -<command>has-old-clients</command> <userinput>yes</userinput>, specify -the two separate options <command>auth-nxdomain</command> <userinput>yes</userinput> -and <command>rfc2308-type1</command> <userinput>no</userinput> instead. -</para></listitem></varlistentry> - -<varlistentry><term><command>host-statistics</command></term> -<listitem><para>In BIND 8, this enables keeping of -statistics for every host that the name server interacts with. -Not implemented in BIND 9. -</para></listitem></varlistentry> - -<varlistentry><term><command>maintain-ixfr-base</command></term> -<listitem><para><emphasis>This option is obsolete</emphasis>. - It was used in <acronym>BIND</acronym> 8 to determine whether a transaction log was -kept for Incremental Zone Transfer. <acronym>BIND</acronym> 9 maintains a transaction -log whenever possible. If you need to disable outgoing incremental zone -transfers, use <command>provide-ixfr</command> <userinput>no</userinput>. -</para></listitem></varlistentry> - -<varlistentry><term><command>minimal-responses</command></term> -<listitem><para>If <userinput>yes</userinput>, then when generating -responses the server will only add records to the authority and -additional data sections when they are required (e.g. delegations, -negative responses). This may improve the performance of the server. -The default is <userinput>no</userinput>. -</para></listitem></varlistentry> - -<varlistentry><term><command>multiple-cnames</command></term> -<listitem><para>This option was used in <acronym>BIND</acronym> 8 to allow -a domain name to have multiple CNAME records in violation of the -DNS standards. <acronym>BIND</acronym> 9.2 always strictly -enforces the CNAME rules both in master files and dynamic updates. -</para></listitem></varlistentry> - -<varlistentry><term><command>notify</command></term> -<listitem><para>If <userinput>yes</userinput> (the default), -DNS NOTIFY messages are sent when a zone the server is authoritative for -changes, see <xref linkend="notify"/>. The messages are sent to the -servers listed in the zone's NS records (except the master server identified -in the SOA MNAME field), and to any servers listed in the -<command>also-notify</command> option. -</para><para> -If <userinput>explicit</userinput>, notifies are sent only to -servers explicitly listed using <command>also-notify</command>. -If <userinput>no</userinput>, no notifies are sent. -</para><para> -The <command>notify</command> option may also be -specified in the <command>zone</command> statement, -in which case it overrides the <command>options notify</command> statement. -It would only be necessary to turn off this option if it caused slaves -to crash.</para></listitem></varlistentry> - -<varlistentry><term><command>recursion</command></term> -<listitem><para>If <userinput>yes</userinput>, and a -DNS query requests recursion, then the server will attempt to do -all the work required to answer the query. If recursion is off -and the server does not already know the answer, it will return a -referral response. The default is <userinput>yes</userinput>. -Note that setting <command>recursion no</command> 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 <command>fetch-glue</command> above. -</para></listitem></varlistentry> - -<varlistentry><term><command>rfc2308-type1</command></term> -<listitem><para>Setting this to <userinput>yes</userinput> will -cause the server to send NS records along with the SOA record for negative -answers. The default is <userinput>no</userinput>.</para> -<note><simpara>Not yet implemented in <acronym>BIND</acronym> 9.</simpara></note> -</listitem></varlistentry> - -<varlistentry><term><command>use-id-pool</command></term> -<listitem><para><emphasis>This option is obsolete</emphasis>. -<acronym>BIND</acronym> 9 always allocates query IDs from a pool. -</para></listitem></varlistentry> - -<varlistentry><term><command>zone-statistics</command></term> -<listitem><para>If <userinput>yes</userinput>, the server will collect -statistical data on all zones (unless specifically turned off -on a per-zone basis by specifying <command>zone-statistics no</command> -in the <command>zone</command> statement). These statistics may be accessed -using <command>rndc stats</command>, which will dump them to the file listed -in the <command>statistics-file</command>. See also <xref linkend="statsfile"/>. -</para></listitem></varlistentry> - -<varlistentry><term><command>use-ixfr</command></term> -<listitem><para><emphasis>This option is obsolete</emphasis>. -If you need to disable IXFR to a particular server or servers see -the information on the <command>provide-ixfr</command> option -in <xref linkend="server_statement_definition_and_usage"/>. See also -<xref linkend="incremental_zone_transfers"/>. -</para></listitem></varlistentry> - -<varlistentry><term><command>provide-ixfr</command></term> -<listitem> -<para> -See the description of -<command>provide-ixfr</command> in -<xref linkend="server_statement_definition_and_usage"/>. -</para></listitem></varlistentry> - -<varlistentry><term><command>request-ixfr</command></term> -<listitem> -<para> -See the description of -<command>request-ixfr</command> in -<xref linkend="server_statement_definition_and_usage"/>. -</para></listitem></varlistentry> - -<varlistentry><term><command>treat-cr-as-space</command></term> -<listitem><para>This option was used in <acronym>BIND</acronym> 8 to make -the server treat carriage return ("<command>\r</command>") characters the same way -as a space or tab character, -to facilitate loading of zone files on a UNIX system that were generated -on an NT or DOS machine. In <acronym>BIND</acronym> 9, both UNIX "<command>\n</command>" -and NT/DOS "<command>\r\n</command>" newlines are always accepted, -and the option is ignored.</para></listitem></varlistentry> - -<varlistentry> -<term><command>additional-from-auth</command></term> -<term><command>additional-from-cache</command></term> -<listitem> - -<para> -These options control the behavior of an authoritative server when -answering queries which have additional data, or when following CNAME -and DNAME chains. -</para> - -<para> -When both of these options are set to <userinput>yes</userinput> -(the default) and a -query is being answered from authoritative data (a zone -configured into the server), the additional data section of the -reply will be filled in using data from other authoritative zones -and from the cache. In some situations this is undesirable, such -as when there is concern over the correctness of the cache, or -in servers where slave zones may be added and modified by -untrusted third parties. Also, avoiding -the search for this additional data will speed up server operations -at the possible expense of additional queries to resolve what would -otherwise be provided in the additional section. -</para> - -<para> -For example, if a query asks for an MX record for host <literal>foo.example.com</literal>, -and the record found is "<literal>MX 10 mail.example.net</literal>", normally the address -records (A and AAAA) for <literal>mail.example.net</literal> will be provided as well, -if known, even though they are not in the example.com zone. -Setting these options to <command>no</command> disables this behavior and makes -the server only search for additional data in the zone it answers from. -</para> - -<para> -These options are intended for use in authoritative-only -servers, or in authoritative-only views. Attempts to set -them to <command>no</command> without also specifying -<command>recursion no</command> will cause the server to -ignore the options and log a warning message. -</para> - -<para> -Specifying <command>additional-from-cache no</command> actually -disables the use of the cache not only for additional data lookups -but also when looking up the answer. This is usually the desired -behavior in an authoritative-only server where the correctness of -the cached data is an issue. -</para> - -<para> -When a name server is non-recursively queried for a name that is not -below the apex of any served zone, it normally answers with an -"upwards referral" to the root servers or the servers of some other -known parent of the query name. Since the data in an upwards referral -comes from the cache, the server will not be able to provide upwards -referrals when <command>additional-from-cache no</command> -has been specified. Instead, it will respond to such queries -with REFUSED. This should not cause any problems since -upwards referrals are not required for the resolution process. -</para> - -</listitem></varlistentry> - -<varlistentry><term><command>match-mapped-addresses</command></term> -<listitem><para>If <userinput>yes</userinput>, then an -IPv4-mapped IPv6 address will match any address match -list entries that match the corresponding IPv4 address. -Enabling this option is sometimes useful on IPv6-enabled Linux -systems, to work around a kernel quirk that causes IPv4 -TCP connections such as zone transfers to be accepted -on an IPv6 socket using mapped addresses, causing -address match lists designed for IPv4 to fail to match. -The use of this option for any other purpose is discouraged. -</para></listitem></varlistentry> - -<varlistentry><term><command>ixfr-from-differences</command></term> -<listitem> -<para> -When <userinput>yes</userinput> and the server loads a new version of a master -zone from its zone file or receives a new version of a slave -file by a non-incremental zone transfer, it will compare -the new version to the previous one and calculate a set -of differences. The differences are then logged in the -zone's journal file such that the changes can be transmitted -to downstream slaves as an incremental zone transfer. -</para><para> -By allowing incremental zone transfers to be used for -non-dynamic zones, this option saves bandwidth at the -expense of increased CPU and memory consumption at the master. -In particular, if the new version of a zone is completely -different from the previous one, the set of differences -will be of a size comparable to the combined size of the -old and new zone version, and the server will need to -temporarily allocate memory to hold this complete -difference set. -</para></listitem></varlistentry> - -<varlistentry><term><command>multi-master</command></term> -<listitem> -<para> -This should be set when you have multiple masters for a zone and the -addresses refer to different machines. If <userinput>yes</userinput>, named will not log -when the serial number on the master is less than what named currently -has. The default is <userinput>no</userinput>. -</para></listitem></varlistentry> - -<varlistentry><term><command>dnssec-enable</command></term> -<listitem> -<para> -Enable DNSSEC support in named. Unless set to <userinput>yes</userinput>, -named behaves as if it does not support DNSSEC. -The default is <userinput>no</userinput>. -</para></listitem></varlistentry> - -<varlistentry><term><command>querylog</command></term> -<listitem> -<para> -Specify whether query logging should be started when named starts. -If <command>querylog</command> is not specified, then the query logging -is determined by the presence of the logging category <command>queries</command>. -</para></listitem></varlistentry> - -<varlistentry><term><command>check-names</command></term> -<listitem> -<para> -This option is used to restrict the character set and syntax of -certain domain names in master files and/or DNS responses received -from the network. The default varies according to usage area. For -<command>master</command> zones the default is <command>fail</command>. -For <command>slave</command> zones the default is <command>warn</command>. -For answers received from the network (<command>response</command>) -the default is <command>ignore</command>. -</para> -<para>The rules for legal hostnames and mail domains are derived from RFC 952 -and RFC 821 as modified by RFC 1123. -</para> -<para><command>check-names</command> applies to the owner names of A, AAA and -MX records. It also applies to the domain names in the RDATA of NS, SOA and MX -records. It also applies to the RDATA of PTR records where the owner name -indicated that it is a reverse lookup of a hostname (the owner name ends in -IN-ADDR.ARPA, IP6.ARPA, IP6.INT). -</para> -</listitem></varlistentry> - -</variablelist> - -</sect3> - -<sect3><title>Forwarding</title> -<para>The forwarding facility can be used to create a large site-wide -cache on a few servers, reducing traffic over links to external -name servers. It can also be used to allow queries by servers that -do not have direct access to the Internet, but wish to look up exterior -names anyway. Forwarding occurs only on those queries for which -the server is not authoritative and does not have the answer in -its cache.</para> - -<variablelist> -<varlistentry><term><command>forward</command></term> -<listitem><para>This option is only meaningful if the -forwarders list is not empty. A value of <varname>first</varname>, -the default, causes the server to query the forwarders first — and -if that doesn't answer the question, the server will then look for -the answer itself. If <varname>only</varname> is specified, the -server will only query the forwarders. -</para></listitem></varlistentry> - -<varlistentry><term><command>forwarders</command></term> -<listitem><para>Specifies the IP addresses to be used -for forwarding. The default is the empty list (no forwarding). -</para></listitem></varlistentry> - -</variablelist> - -<para>Forwarding can also be configured on a per-domain basis, allowing -for the global forwarding options to be overridden in a variety -of ways. You can set particular domains to use different forwarders, -or have a different <command>forward only/first</command> behavior, -or not forward at all, see <xref linkend="zone_statement_grammar"/>.</para> -</sect3> - -<sect3><title>Dual-stack Servers</title> -<para>Dual-stack servers are used as servers of last resort to work around -problems in reachability due the lack of support for either IPv4 or IPv6 -on the host machine.</para> - -<variablelist> -<varlistentry><term><command>dual-stack-servers</command></term> -<listitem><para>Specifies host names or addresses of machines with access to -both IPv4 and IPv6 transports. If a hostname is used, the server must be able -to resolve the name using only the transport it has. If the machine is dual -stacked, then the <command>dual-stack-servers</command> have no effect unless -access to a transport has been disabled on the command line -(e.g. <command>named -4</command>).</para></listitem> -</varlistentry> -</variablelist> -</sect3> - -<sect3 id="access_control"><title>Access Control</title> - -<para>Access to the server can be restricted based on the IP address -of the requesting system. See <xref linkend="address_match_lists"/> for -details on how to specify IP address lists.</para> - -<variablelist> - -<varlistentry><term><command>allow-notify</command></term> -<listitem><para>Specifies which hosts are allowed to -notify this server, a slave, of zone changes in addition -to the zone masters. -<command>allow-notify</command> may also be specified in the -<command>zone</command> statement, in which case it overrides the -<command>options allow-notify</command> statement. It is only meaningful -for a slave zone. If not specified, the default is to process notify messages -only from a zone's master.</para> -</listitem></varlistentry> - -<varlistentry><term><command>allow-query</command></term> -<listitem><para>Specifies which hosts are allowed to -ask ordinary DNS questions. <command>allow-query</command> may also -be specified in the <command>zone</command> statement, in which -case it overrides the <command>options allow-query</command> statement. If -not specified, the default is to allow queries from all hosts.</para> -</listitem></varlistentry> - - -<varlistentry><term><command>allow-recursion</command></term> -<listitem><para>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. -Note that disallowing recursive queries for a host does not prevent the -host from retrieving data that is already in the server's cache. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>allow-update-forwarding</command></term> -<listitem><para>Specifies which hosts are allowed to -submit Dynamic DNS updates to slave zones to be forwarded to the -master. The default is <userinput>{ none; }</userinput>, which -means that no update forwarding will be performed. To enable -update forwarding, specify -<userinput>allow-update-forwarding { any; };</userinput>. -Specifying values other than <userinput>{ none; }</userinput> or -<userinput>{ any; }</userinput> is usually counterproductive, since -the responsibility for update access control should rest with the -master server, not the slaves.</para> -<para>Note that enabling the update forwarding feature on a slave server -may expose master servers relying on insecure IP address based -access control to attacks; see <xref linkend="dynamic_update_security"/> -for more details.</para> -</listitem></varlistentry> - -<varlistentry><term><command>allow-v6-synthesis</command></term> -<listitem><para>This option was introduced for the smooth transition from AAAA -to A6 and from "nibble labels" to binary labels. -However, since both A6 and binary labels were then deprecated, -this option was also deprecated. -It is now ignored with some warning messages. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>allow-transfer</command></term> -<listitem><para>Specifies which hosts are allowed to -receive zone transfers from the server. <command>allow-transfer</command> may -also be specified in the <command>zone</command> statement, in which -case it overrides the <command>options allow-transfer</command> statement. -If not specified, the default is to allow transfers to all hosts.</para> -</listitem></varlistentry> - -<varlistentry><term><command>blackhole</command></term> -<listitem><para>Specifies a list of addresses that the -server will not accept queries from or use to resolve a query. Queries -from these addresses will not be responded to. The default is <userinput>none</userinput>.</para> -</listitem></varlistentry> - -</variablelist> - -</sect3> - -<sect3><title>Interfaces</title> -<para>The interfaces and ports that the server will answer queries -from may be specified using the <command>listen-on</command> option. <command>listen-on</command> takes -an optional port, and an <varname>address_match_list</varname>. -The server will listen on all interfaces allowed by the address -match list. If a port is not specified, port 53 will be used.</para> -<para>Multiple <command>listen-on</command> statements are allowed. -For example,</para> + + </listitem> + </varlistentry> + + <varlistentry> + <term><command>disable-algorithms</command></term> + <listitem> + <para> + Disable the specified DNSSEC algorithms at and below the + specified name. + Multiple <command>disable-algorithms</command> + statements are allowed. + Only the most specific will be applied. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>dnssec-lookaside</command></term> + <listitem> + <para> + When set, <command>dnssec-lookaside</command> + provides the + validator with an alternate method to validate DNSKEY records + at the + top of a zone. When a DNSKEY is at or below a domain + specified by the + deepest <command>dnssec-lookaside</command>, and + the normal dnssec validation + has left the key untrusted, the trust-anchor will be append to + the key + name and a DLV record will be looked up to see if it can + validate the + key. If the DLV record validates a DNSKEY (similarly to the + way a DS + record does) the DNSKEY RRset is deemed to be trusted. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>dnssec-must-be-secure</command></term> + <listitem> + <para> + Specify hierarchies which must be or may not be secure (signed and + validated). + If <userinput>yes</userinput>, then named will only accept + answers if they + are secure. + If <userinput>no</userinput>, then normal dnssec validation + applies + allowing for insecure answers to be accepted. + The specified domain must be under a <command>trusted-key</command> or + <command>dnssec-lookaside</command> must be + active. + </para> + </listitem> + </varlistentry> + + </variablelist> + + <sect3 id="boolean_options"> + <title>Boolean Options</title> + + <variablelist> + + <varlistentry> + <term><command>auth-nxdomain</command></term> + <listitem> + <para> + If <userinput>yes</userinput>, then the <command>AA</command> bit + is always set on NXDOMAIN responses, even if the server is + not actually + authoritative. The default is <userinput>no</userinput>; + this is + a change from <acronym>BIND</acronym> 8. If you + are using very old DNS software, you + may need to set it to <userinput>yes</userinput>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>deallocate-on-exit</command></term> + <listitem> + <para> + This option was used in <acronym>BIND</acronym> + 8 to enable checking + for memory leaks on exit. <acronym>BIND</acronym> 9 ignores the option and always performs + the checks. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>dialup</command></term> + <listitem> + <para> + If <userinput>yes</userinput>, then the + server treats all zones as if they are doing zone transfers + across + a dial-on-demand dialup link, which can be brought up by + traffic + originating from this server. This has different effects + according + to zone type and concentrates the zone maintenance so that + it all + happens in a short interval, once every <command>heartbeat-interval</command> and + hopefully during the one call. It also suppresses some of + the normal + zone maintenance traffic. The default is <userinput>no</userinput>. + </para> + <para> + The <command>dialup</command> option + may also be specified in the <command>view</command> and + <command>zone</command> statements, + in which case it overrides the global <command>dialup</command> + option. + </para> + <para> + If the zone is a master zone, then the server will send out a + NOTIFY + request to all the slaves (default). This should 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. + The set of servers to which NOTIFY is sent can be controlled + by + <command>notify</command> and <command>also-notify</command>. + </para> + <para> + If 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 + <command>heartbeat-interval</command> expires in + addition to sending + NOTIFY requests. + </para> + <para> + Finer control can be achieved by using + <userinput>notify</userinput> which only sends NOTIFY + messages, + <userinput>notify-passive</userinput> which sends NOTIFY + messages and + suppresses the normal refresh queries, <userinput>refresh</userinput> + which suppresses normal refresh processing and sends refresh + queries + when the <command>heartbeat-interval</command> + expires, and + <userinput>passive</userinput> which just disables normal + refresh + processing. + </para> + + <informaltable colsep="0" rowsep="0"> + <tgroup cols="4" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="1.150in"/> + <colspec colname="3" colnum="3" colsep="0" colwidth="1.150in"/> + <colspec colname="4" colnum="4" colsep="0" colwidth="1.150in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + dialup mode + </para> + </entry> + <entry colname="2"> + <para> + normal refresh + </para> + </entry> + <entry colname="3"> + <para> + heart-beat refresh + </para> + </entry> + <entry colname="4"> + <para> + heart-beat notify + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>no</command> (default)</para> + </entry> + <entry colname="2"> + <para> + yes + </para> + </entry> + <entry colname="3"> + <para> + no + </para> + </entry> + <entry colname="4"> + <para> + no + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>yes</command></para> + </entry> + <entry colname="2"> + <para> + no + </para> + </entry> + <entry colname="3"> + <para> + yes + </para> + </entry> + <entry colname="4"> + <para> + yes + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>notify</command></para> + </entry> + <entry colname="2"> + <para> + yes + </para> + </entry> + <entry colname="3"> + <para> + no + </para> + </entry> + <entry colname="4"> + <para> + yes + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>refresh</command></para> + </entry> + <entry colname="2"> + <para> + no + </para> + </entry> + <entry colname="3"> + <para> + yes + </para> + </entry> + <entry colname="4"> + <para> + no + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>passive</command></para> + </entry> + <entry colname="2"> + <para> + no + </para> + </entry> + <entry colname="3"> + <para> + no + </para> + </entry> + <entry colname="4"> + <para> + no + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>notify-passive</command></para> + </entry> + <entry colname="2"> + <para> + no + </para> + </entry> + <entry colname="3"> + <para> + no + </para> + </entry> + <entry colname="4"> + <para> + yes + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + + <para> + Note that normal NOTIFY processing is not affected by + <command>dialup</command>. + </para> + + </listitem> + </varlistentry> + + <varlistentry> + <term><command>fake-iquery</command></term> + <listitem> + <para> + In <acronym>BIND</acronym> 8, this option + enabled simulating the obsolete DNS query type + IQUERY. <acronym>BIND</acronym> 9 never does + IQUERY simulation. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>fetch-glue</command></term> + <listitem> + <para> + This option is obsolete. + In BIND 8, <userinput>fetch-glue yes</userinput> + caused the server to attempt to fetch glue resource records + it + didn't have when constructing the additional + data section of a response. This is now considered a bad + idea + and BIND 9 never does it. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>flush-zones-on-shutdown</command></term> + <listitem> + <para> + When the nameserver exits due receiving SIGTERM, + flush or do not flush any pending zone writes. The default + is + <command>flush-zones-on-shutdown</command> <userinput>no</userinput>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>has-old-clients</command></term> + <listitem> + <para> + This option was incorrectly implemented + in <acronym>BIND</acronym> 8, and is ignored by <acronym>BIND</acronym> 9. + To achieve the intended effect + of + <command>has-old-clients</command> <userinput>yes</userinput>, specify + the two separate options <command>auth-nxdomain</command> <userinput>yes</userinput> + and <command>rfc2308-type1</command> <userinput>no</userinput> instead. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>host-statistics</command></term> + <listitem> + <para> + In BIND 8, this enables keeping of + statistics for every host that the name server interacts + with. + Not implemented in BIND 9. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>maintain-ixfr-base</command></term> + <listitem> + <para> + <emphasis>This option is obsolete</emphasis>. + It was used in <acronym>BIND</acronym> 8 to + determine whether a transaction log was + kept for Incremental Zone Transfer. <acronym>BIND</acronym> 9 maintains a transaction + log whenever possible. If you need to disable outgoing + incremental zone + transfers, use <command>provide-ixfr</command> <userinput>no</userinput>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>minimal-responses</command></term> + <listitem> + <para> + If <userinput>yes</userinput>, then when generating + responses the server will only add records to the authority + and additional data sections when they are required (e.g. + delegations, negative responses). This may improve the + performance of the server. + The default is <userinput>no</userinput>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>multiple-cnames</command></term> + <listitem> + <para> + This option was used in <acronym>BIND</acronym> 8 to allow + a domain name to have multiple CNAME records in violation of + the DNS standards. <acronym>BIND</acronym> 9.2 onwards + always strictly enforces the CNAME rules both in master + files and dynamic updates. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>notify</command></term> + <listitem> + <para> + If <userinput>yes</userinput> (the default), + DNS NOTIFY messages are sent when a zone the server is + authoritative for + changes, see <xref linkend="notify"/>. The messages are + sent to the + servers listed in the zone's NS records (except the master + server identified + in the SOA MNAME field), and to any servers listed in the + <command>also-notify</command> option. + </para> + <para> + If <userinput>master-only</userinput>, notifies are only + sent + for master zones. + If <userinput>explicit</userinput>, notifies are sent only + to + servers explicitly listed using <command>also-notify</command>. + If <userinput>no</userinput>, no notifies are sent. + </para> + <para> + The <command>notify</command> option may also be + specified in the <command>zone</command> + statement, + in which case it overrides the <command>options notify</command> statement. + It would only be necessary to turn off this option if it + caused slaves + to crash. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>recursion</command></term> + <listitem> + <para> + If <userinput>yes</userinput>, and a + DNS query requests recursion, then the server will attempt + to do + all the work required to answer the query. If recursion is + off + and the server does not already know the answer, it will + return a + referral response. The default is + <userinput>yes</userinput>. + Note that setting <command>recursion no</command> 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 <command>fetch-glue</command> above. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>rfc2308-type1</command></term> + <listitem> + <para> + Setting this to <userinput>yes</userinput> will + cause the server to send NS records along with the SOA + record for negative + answers. The default is <userinput>no</userinput>. + </para> + <note> + <simpara> + Not yet implemented in <acronym>BIND</acronym> + 9. + </simpara> + </note> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>use-id-pool</command></term> + <listitem> + <para> + <emphasis>This option is obsolete</emphasis>. + <acronym>BIND</acronym> 9 always allocates query + IDs from a pool. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>zone-statistics</command></term> + <listitem> + <para> + If <userinput>yes</userinput>, the server will collect + statistical data on all zones (unless specifically turned + off + on a per-zone basis by specifying <command>zone-statistics no</command> + in the <command>zone</command> statement). + These statistics may be accessed + using <command>rndc stats</command>, which will + dump them to the file listed + in the <command>statistics-file</command>. See + also <xref linkend="statsfile"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>use-ixfr</command></term> + <listitem> + <para> + <emphasis>This option is obsolete</emphasis>. + If you need to disable IXFR to a particular server or + servers, see + the information on the <command>provide-ixfr</command> option + in <xref linkend="server_statement_definition_and_usage"/>. + See also + <xref linkend="incremental_zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>provide-ixfr</command></term> + <listitem> + <para> + See the description of + <command>provide-ixfr</command> in + <xref linkend="server_statement_definition_and_usage"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>request-ixfr</command></term> + <listitem> + <para> + See the description of + <command>request-ixfr</command> in + <xref linkend="server_statement_definition_and_usage"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>treat-cr-as-space</command></term> + <listitem> + <para> + This option was used in <acronym>BIND</acronym> + 8 to make + the server treat carriage return ("<command>\r</command>") characters the same way + as a space or tab character, + to facilitate loading of zone files on a UNIX system that + were generated + on an NT or DOS machine. In <acronym>BIND</acronym> 9, both UNIX "<command>\n</command>" + and NT/DOS "<command>\r\n</command>" newlines + are always accepted, + and the option is ignored. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>additional-from-auth</command></term> + <term><command>additional-from-cache</command></term> + <listitem> + + <para> + These options control the behavior of an authoritative + server when + answering queries which have additional data, or when + following CNAME + and DNAME chains. + </para> + + <para> + When both of these options are set to <userinput>yes</userinput> + (the default) and a + query is being answered from authoritative data (a zone + configured into the server), the additional data section of + the + reply will be filled in using data from other authoritative + zones + and from the cache. In some situations this is undesirable, + such + as when there is concern over the correctness of the cache, + or + in servers where slave zones may be added and modified by + untrusted third parties. Also, avoiding + the search for this additional data will speed up server + operations + at the possible expense of additional queries to resolve + what would + otherwise be provided in the additional section. + </para> + + <para> + For example, if a query asks for an MX record for host <literal>foo.example.com</literal>, + and the record found is "<literal>MX 10 mail.example.net</literal>", normally the address + records (A and AAAA) for <literal>mail.example.net</literal> will be provided as well, + if known, even though they are not in the example.com zone. + Setting these options to <command>no</command> + disables this behavior and makes + the server only search for additional data in the zone it + answers from. + </para> + + <para> + These options are intended for use in authoritative-only + servers, or in authoritative-only views. Attempts to set + them to <command>no</command> without also + specifying + <command>recursion no</command> will cause the + server to + ignore the options and log a warning message. + </para> + + <para> + Specifying <command>additional-from-cache no</command> actually + disables the use of the cache not only for additional data + lookups + but also when looking up the answer. This is usually the + desired + behavior in an authoritative-only server where the + correctness of + the cached data is an issue. + </para> + + <para> + When a name server is non-recursively queried for a name + that is not + below the apex of any served zone, it normally answers with + an + "upwards referral" to the root servers or the servers of + some other + known parent of the query name. Since the data in an + upwards referral + comes from the cache, the server will not be able to provide + upwards + referrals when <command>additional-from-cache no</command> + has been specified. Instead, it will respond to such + queries + with REFUSED. This should not cause any problems since + upwards referrals are not required for the resolution + process. + </para> + + </listitem> + </varlistentry> + + <varlistentry> + <term><command>match-mapped-addresses</command></term> + <listitem> + <para> + If <userinput>yes</userinput>, then an + IPv4-mapped IPv6 address will match any address match + list entries that match the corresponding IPv4 address. + Enabling this option is sometimes useful on IPv6-enabled + Linux + systems, to work around a kernel quirk that causes IPv4 + TCP connections such as zone transfers to be accepted + on an IPv6 socket using mapped addresses, causing + address match lists designed for IPv4 to fail to match. + The use of this option for any other purpose is discouraged. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>ixfr-from-differences</command></term> + <listitem> + <para> + When <userinput>yes</userinput> and the server loads a new version of a master + zone from its zone file or receives a new version of a slave + file by a non-incremental zone transfer, it will compare + the new version to the previous one and calculate a set + of differences. The differences are then logged in the + zone's journal file such that the changes can be transmitted + to downstream slaves as an incremental zone transfer. + </para> + <para> + By allowing incremental zone transfers to be used for + non-dynamic zones, this option saves bandwidth at the + expense of increased CPU and memory consumption at the + master. + In particular, if the new version of a zone is completely + different from the previous one, the set of differences + will be of a size comparable to the combined size of the + old and new zone version, and the server will need to + temporarily allocate memory to hold this complete + difference set. + </para> + <para><command>ixfr-from-differences</command> + also accepts <command>master</command> and + <command>slave</command> at the view and options + levels which causes + <command>ixfr-from-differences</command> to apply to + all <command>master</command> or + <command>slave</command> zones respectively. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>multi-master</command></term> + <listitem> + <para> + This should be set when you have multiple masters for a zone + and the + addresses refer to different machines. If <userinput>yes</userinput>, named will + not log + when the serial number on the master is less than what named + currently + has. The default is <userinput>no</userinput>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>dnssec-enable</command></term> + <listitem> + <para> + Enable DNSSEC support in named. Unless set to <userinput>yes</userinput>, + named behaves as if it does not support DNSSEC. + The default is <userinput>yes</userinput>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>dnssec-validation</command></term> + <listitem> + <para> + Enable DNSSEC validation in named. + Note <command>dnssec-enable</command> also needs to be + set to <userinput>yes</userinput> to be effective. + The default is <userinput>no</userinput>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>dnssec-accept-expired</command></term> + <listitem> + <para> + Accept expired signatures when verifying DNSSEC signatures. + The default is <userinput>no</userinput>. + Setting this option to "yes" leaves named vulnerable to replay attacks. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>querylog</command></term> + <listitem> + <para> + Specify whether query logging should be started when named + starts. + If <command>querylog</command> is not specified, + then the query logging + is determined by the presence of the logging category <command>queries</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-names</command></term> + <listitem> + <para> + This option is used to restrict the character set and syntax + of + certain domain names in master files and/or DNS responses + received + from the network. The default varies according to usage + area. For + <command>master</command> zones the default is <command>fail</command>. + For <command>slave</command> zones the default + is <command>warn</command>. + For answers received from the network (<command>response</command>) + the default is <command>ignore</command>. + </para> + <para> + The rules for legal hostnames and mail domains are derived + from RFC 952 and RFC 821 as modified by RFC 1123. + </para> + <para><command>check-names</command> + applies to the owner names of A, AAA and MX records. + It also applies to the domain names in the RDATA of NS, SOA + and MX records. + It also applies to the RDATA of PTR records where the owner + name indicated that it is a reverse lookup of a hostname + (the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-mx</command></term> + <listitem> + <para> + Check whether the MX record appears to refer to a IP address. + The default is to <command>warn</command>. Other possible + values are <command>fail</command> and + <command>ignore</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-wildcard</command></term> + <listitem> + <para> + This option is used to check for non-terminal wildcards. + The use of non-terminal wildcards is almost always as a + result of a failure + to understand the wildcard matching algorithm (RFC 1034). + This option + affects master zones. The default (<command>yes</command>) is to check + for non-terminal wildcards and issue a warning. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-integrity</command></term> + <listitem> + <para> + Perform post load zone integrity checks on master + zones. This checks that MX and SRV records refer + to address (A or AAAA) records and that glue + address records exist for delegated zones. For + MX and SRV records only in-zone hostnames are + checked (for out-of-zone hostnames use named-checkzone). + For NS records only names below top of zone are + checked (for out-of-zone names and glue consistency + checks use named-checkzone). The default is + <command>yes</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-mx-cname</command></term> + <listitem> + <para> + If <command>check-integrity</command> is set then + fail, warn or ignore MX records that refer + to CNAMES. The default is to <command>warn</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-srv-cname</command></term> + <listitem> + <para> + If <command>check-integrity</command> is set then + fail, warn or ignore SRV records that refer + to CNAMES. The default is to <command>warn</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-sibling</command></term> + <listitem> + <para> + When performing integrity checks, also check that + sibling glue exists. The default is <command>yes</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>zero-no-soa-ttl</command></term> + <listitem> + <para> + When returning authoritative negative responses to + SOA queries set the TTL of the SOA recored returned in + the authority section to zero. + The default is <command>yes</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>zero-no-soa-ttl-cache</command></term> + <listitem> + <para> + When caching a negative response to a SOA query + set the TTL to zero. + The default is <command>no</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>update-check-ksk</command></term> + <listitem> + <para> + When regenerating the RRSIGs following a UPDATE + request to a secure zone, check the KSK flag on + the DNSKEY RR to determine if this key should be + used to generate the RRSIG. This flag is ignored + if there are not DNSKEY RRs both with and without + a KSK. + The default is <command>yes</command>. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3> + <title>Forwarding</title> + <para> + The forwarding facility can be used to create a large site-wide + cache on a few servers, reducing traffic over links to external + name servers. It can also be used to allow queries by servers that + do not have direct access to the Internet, but wish to look up + exterior + names anyway. Forwarding occurs only on those queries for which + the server is not authoritative and does not have the answer in + its cache. + </para> + + <variablelist> + <varlistentry> + <term><command>forward</command></term> + <listitem> + <para> + This option is only meaningful if the + forwarders list is not empty. A value of <varname>first</varname>, + the default, causes the server to query the forwarders + first — and + if that doesn't answer the question, the server will then + look for + the answer itself. If <varname>only</varname> is + specified, the + server will only query the forwarders. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>forwarders</command></term> + <listitem> + <para> + Specifies the IP addresses to be used + for forwarding. The default is the empty list (no + forwarding). + </para> + </listitem> + </varlistentry> + + </variablelist> + + <para> + Forwarding can also be configured on a per-domain basis, allowing + for the global forwarding options to be overridden in a variety + of ways. You can set particular domains to use different + forwarders, + or have a different <command>forward only/first</command> behavior, + or not forward at all, see <xref linkend="zone_statement_grammar"/>. + </para> + </sect3> + + <sect3> + <title>Dual-stack Servers</title> + <para> + Dual-stack servers are used as servers of last resort to work + around + problems in reachability due the lack of support for either IPv4 + or IPv6 + on the host machine. + </para> + + <variablelist> + <varlistentry> + <term><command>dual-stack-servers</command></term> + <listitem> + <para> + Specifies host names or addresses of machines with access to + both IPv4 and IPv6 transports. If a hostname is used, the + server must be able + to resolve the name using only the transport it has. If the + machine is dual + stacked, then the <command>dual-stack-servers</command> have no effect unless + access to a transport has been disabled on the command line + (e.g. <command>named -4</command>). + </para> + </listitem> + </varlistentry> + </variablelist> + </sect3> + + <sect3 id="access_control"> + <title>Access Control</title> + + <para> + Access to the server can be restricted based on the IP address + of the requesting system. See <xref linkend="address_match_lists"/> for + details on how to specify IP address lists. + </para> + + <variablelist> + + <varlistentry> + <term><command>allow-notify</command></term> + <listitem> + <para> + Specifies which hosts are allowed to + notify this server, a slave, of zone changes in addition + to the zone masters. + <command>allow-notify</command> may also be + specified in the + <command>zone</command> statement, in which case + it overrides the + <command>options allow-notify</command> + statement. It is only meaningful + for a slave zone. If not specified, the default is to + process notify messages + only from a zone's master. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-query</command></term> + <listitem> + <para> + Specifies which hosts are allowed to ask ordinary + DNS questions. <command>allow-query</command> may + also be specified in the <command>zone</command> + statement, in which case it overrides the + <command>options allow-query</command> statement. + If not specified, the default is to allow queries + from all hosts. + </para> + <note> + <para> + <command>allow-query-cache</command> is now + used to specify access to the cache. + </para> + </note> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-query-cache</command></term> + <listitem> + <para> + Specifies which hosts are allowed to get answers + from the cache. If <command>allow-query-cache</command> + is not set then <command>allow-recursion</command> + is used if set, otherwise <command>allow-query</command> + is used if set, otherwise the default + (<command>localnets;</command> + <command>localhost;</command>) is used. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-recursion</command></term> + <listitem> + <para> + Specifies which hosts are allowed to make recursive + queries through this server. If + <command>allow-recursion</command> is not set + then <command>allow-query-cache</command> is + used if set, otherwise <command>allow-query</command> + is used if set, otherwise the default + (<command>localnets;</command> + <command>localhost;</command>) is used. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-update</command></term> + <listitem> + <para> + Specifies which hosts are allowed to + submit Dynamic DNS updates for master zones. The default is + to deny + updates from all hosts. Note that allowing updates based + on the requestor's IP address is insecure; see + <xref linkend="dynamic_update_security"/> for details. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-update-forwarding</command></term> + <listitem> + <para> + Specifies which hosts are allowed to + submit Dynamic DNS updates to slave zones to be forwarded to + the + master. The default is <userinput>{ none; }</userinput>, + which + means that no update forwarding will be performed. To + enable + update forwarding, specify + <userinput>allow-update-forwarding { any; };</userinput>. + Specifying values other than <userinput>{ none; }</userinput> or + <userinput>{ any; }</userinput> is usually + counterproductive, since + the responsibility for update access control should rest + with the + master server, not the slaves. + </para> + <para> + Note that enabling the update forwarding feature on a slave + server + may expose master servers relying on insecure IP address + based + access control to attacks; see <xref linkend="dynamic_update_security"/> + for more details. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-v6-synthesis</command></term> + <listitem> + <para> + This option was introduced for the smooth transition from + AAAA + to A6 and from "nibble labels" to binary labels. + However, since both A6 and binary labels were then + deprecated, + this option was also deprecated. + It is now ignored with some warning messages. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-transfer</command></term> + <listitem> + <para> + Specifies which hosts are allowed to + receive zone transfers from the server. <command>allow-transfer</command> may + also be specified in the <command>zone</command> + statement, in which + case it overrides the <command>options allow-transfer</command> statement. + If not specified, the default is to allow transfers to all + hosts. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>blackhole</command></term> + <listitem> + <para> + Specifies a list of addresses that the + server will not accept queries from or use to resolve a + query. Queries + from these addresses will not be responded to. The default + is <userinput>none</userinput>. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3> + <title>Interfaces</title> + <para> + The interfaces and ports that the server will answer queries + from may be specified using the <command>listen-on</command> option. <command>listen-on</command> takes + an optional port, and an <varname>address_match_list</varname>. + The server will listen on all interfaces allowed by the address + match list. If a port is not specified, port 53 will be used. + </para> + <para> + Multiple <command>listen-on</command> statements are + allowed. + For example, + </para> <programlisting>listen-on { 5.6.7.8; }; listen-on port 1234 { !1.2.3.4; 1.2/16; }; </programlisting> -<para>will enable the name server on port 53 for the IP address -5.6.7.8, and on port 1234 of an address on the machine in net -1.2 that is not 1.2.3.4.</para> + <para> + will enable the name server on port 53 for the IP address + 5.6.7.8, and on port 1234 of an address on the machine in net + 1.2 that is not 1.2.3.4. + </para> -<para>If no <command>listen-on</command> is specified, the -server will listen on port 53 on all interfaces.</para> + <para> + If no <command>listen-on</command> is specified, the + server will listen on port 53 on all interfaces. + </para> -<para>The <command>listen-on-v6</command> option is used to -specify the interfaces and the ports on which the server will listen -for incoming queries sent using IPv6.</para> + <para> + The <command>listen-on-v6</command> option is used to + specify the interfaces and the ports on which the server will + listen + for incoming queries sent using IPv6. + </para> -<para>When <programlisting>{ any; }</programlisting> is specified -as the <varname>address_match_list</varname> for the -<command>listen-on-v6</command> option, -the server does not bind a separate socket to each IPv6 interface -address as it does for IPv4 if the operating system has enough API -support for IPv6 (specifically if it conforms to RFC 3493 and RFC 3542). -Instead, it listens on the IPv6 wildcard address. -If the system only has incomplete API support for IPv6, however, -the behavior is the same as that for IPv4.</para> + <para> + When <programlisting>{ any; }</programlisting> is + specified + as the <varname>address_match_list</varname> for the + <command>listen-on-v6</command> option, + the server does not bind a separate socket to each IPv6 interface + address as it does for IPv4 if the operating system has enough API + support for IPv6 (specifically if it conforms to RFC 3493 and RFC + 3542). + Instead, it listens on the IPv6 wildcard address. + If the system only has incomplete API support for IPv6, however, + the behavior is the same as that for IPv4. + </para> -<para>A list of particular IPv6 addresses can also be specified, in which case -the server listens on a separate socket for each specified address, -regardless of whether the desired API is supported by the system.</para> + <para> + A list of particular IPv6 addresses can also be specified, in + which case + the server listens on a separate socket for each specified + address, + regardless of whether the desired API is supported by the system. + </para> -<para>Multiple <command>listen-on-v6</command> options can be used. -For example,</para> + <para> + Multiple <command>listen-on-v6</command> options can + be used. + For example, + </para> <programlisting>listen-on-v6 { any; }; listen-on-v6 port 1234 { !2001:db8::/32; any; }; </programlisting> -<para>will enable the name server on port 53 for any IPv6 addresses -(with a single wildcard socket), -and on port 1234 of IPv6 addresses that is not in the prefix -2001:db8::/32 (with separate sockets for each matched address.)</para> + <para> + will enable the name server on port 53 for any IPv6 addresses + (with a single wildcard socket), + and on port 1234 of IPv6 addresses that is not in the prefix + 2001:db8::/32 (with separate sockets for each matched address.) + </para> + + <para> + To make the server not listen on any IPv6 address, use + </para> -<para>To make the server not listen on any IPv6 address, use</para> <programlisting>listen-on-v6 { none; }; </programlisting> -<para>If no <command>listen-on-v6</command> option is specified, -the server will not listen on any IPv6 address.</para></sect3> - -<sect3><title>Query Address</title> -<para>If the server doesn't know the answer to a question, it will -query other name servers. <command>query-source</command> specifies -the address and port used for such queries. For queries sent over -IPv6, there is a separate <command>query-source-v6</command> option. -If <command>address</command> is <command>*</command> (asterisk) or is omitted, -a wildcard IP address (<command>INADDR_ANY</command>) will be used. -If <command>port</command> is <command>*</command> or is omitted, -a random unprivileged port will be used. The <command>avoid-v4-udp-ports</command> -and <command>avoid-v6-udp-ports</command> options can be used to prevent named -from selecting certain ports. The defaults are:</para> + + <para> + If no <command>listen-on-v6</command> option is + specified, + the server will not listen on any IPv6 address. + </para> + </sect3> + + <sect3> + <title>Query Address</title> + <para> + If the server doesn't know the answer to a question, it will + query other name servers. <command>query-source</command> specifies + the address and port used for such queries. For queries sent over + IPv6, there is a separate <command>query-source-v6</command> option. + If <command>address</command> is <command>*</command> (asterisk) or is omitted, + a wildcard IP address (<command>INADDR_ANY</command>) + will be used. + If <command>port</command> is <command>*</command> or is omitted, + a random unprivileged port will be used. The <command>avoid-v4-udp-ports</command> + and <command>avoid-v6-udp-ports</command> options can be used + to prevent named + from selecting certain ports. The defaults are: + </para> + <programlisting>query-source address * port *; query-source-v6 address * port *; </programlisting> -<note> -<para>The address specified in the <command>query-source</command> option -is used for both UDP and TCP queries, but the port applies only to -UDP queries. TCP queries always use a random -unprivileged port.</para></note> -<note> -<para>See also <command>transfer-source</command> and -<command>notify-source</command>.</para></note> - <note> - <para> - Solaris 2.5.1 and earlier does not support setting the source - address for TCP sockets. - </para> - </note> -</sect3> - -<sect3 id="zone_transfers"><title>Zone Transfers</title> -<para><acronym>BIND</acronym> has mechanisms in place to facilitate zone transfers -and set limits on the amount of load that transfers place on the -system. The following options apply to zone transfers.</para> - -<variablelist> - -<varlistentry><term><command>also-notify</command></term> -<listitem><para>Defines a global list of IP addresses of name servers -that are also sent NOTIFY messages whenever a fresh copy of the -zone is loaded, in addition to the servers listed in the zone's NS records. -This helps to ensure that copies of the zones will -quickly converge on stealth servers. If an <command>also-notify</command> list -is given in a <command>zone</command> statement, it will override -the <command>options also-notify</command> statement. When a <command>zone notify</command> statement -is set to <command>no</command>, the IP addresses in the global <command>also-notify</command> list will -not be sent NOTIFY messages for that zone. The default is the empty -list (no global notification list).</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-transfer-time-in</command></term> -<listitem><para>Inbound zone transfers running longer than -this many minutes will be terminated. The default is 120 minutes -(2 hours). The maximum value is 28 days (40320 minutes).</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-transfer-idle-in</command></term> -<listitem><para>Inbound zone transfers making no progress -in this many minutes will be terminated. The default is 60 minutes -(1 hour). The maximum value is 28 days (40320 minutes).</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-transfer-time-out</command></term> -<listitem><para>Outbound zone transfers running longer than -this many minutes will be terminated. The default is 120 minutes -(2 hours). The maximum value is 28 days (40320 minutes).</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-transfer-idle-out</command></term> -<listitem><para>Outbound zone transfers making no progress -in this many minutes will be terminated. The default is 60 minutes (1 -hour). The maximum value is 28 days (40320 minutes).</para> -</listitem></varlistentry> - -<varlistentry><term><command>serial-query-rate</command></term> -<listitem><para>Slave servers will periodically query master servers -to find out if zone serial numbers have changed. Each such query uses -a minute amount of the slave server's network bandwidth. To limit the -amount of bandwidth used, BIND 9 limits the rate at which queries are -sent. The value of the <command>serial-query-rate</command> option, -an integer, is the maximum number of queries sent per second. -The default is 20. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>serial-queries</command></term> -<listitem><para>In BIND 8, the <command>serial-queries</command> option -set the maximum number of concurrent serial number queries -allowed to be outstanding at any given time. -BIND 9 does not limit the number of outstanding -serial queries and ignores the <command>serial-queries</command> option. -Instead, it limits the rate at which the queries are sent -as defined using the <command>serial-query-rate</command> option. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>transfer-format</command></term> -<listitem> - -<para> -Zone transfers can be sent using two different formats, -<command>one-answer</command> and <command>many-answers</command>. -The <command>transfer-format</command> option is used -on the master server to determine which format it sends. -<command>one-answer</command> uses one DNS message per -resource record transferred. -<command>many-answers</command> packs as many resource records as -possible into a message. <command>many-answers</command> is more -efficient, but is only supported by relatively new slave servers, -such as <acronym>BIND</acronym> 9, <acronym>BIND</acronym> 8.x and patched -versions of <acronym>BIND</acronym> 4.9.5. The <command>many-answers</command> -format is also supported by recent Microsoft Windows nameservers. The default is -<command>many-answers</command>. <command>transfer-format</command> -may be overridden on a per-server basis by using the -<command>server</command> statement. -</para> - -</listitem></varlistentry> - -<varlistentry><term><command>transfers-in</command></term> -<listitem><para>The maximum number of inbound zone transfers -that can be running concurrently. The default value is <literal>10</literal>. -Increasing <command>transfers-in</command> may speed up the convergence -of slave zones, but it also may increase the load on the local system.</para> -</listitem></varlistentry> - -<varlistentry><term><command>transfers-out</command></term> -<listitem><para>The maximum number of outbound zone transfers -that can be running concurrently. Zone transfer requests in excess -of the limit will be refused. The default value is <literal>10</literal>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>transfers-per-ns</command></term> -<listitem><para>The maximum number of inbound zone transfers -that can be concurrently transferring from a given remote name server. -The default value is <literal>2</literal>. Increasing <command>transfers-per-ns</command> may -speed up the convergence of slave zones, but it also may increase -the load on the remote name server. <command>transfers-per-ns</command> may -be overridden on a per-server basis by using the <command>transfers</command> phrase -of the <command>server</command> statement.</para> -</listitem></varlistentry> - -<varlistentry><term><command>transfer-source</command></term> -<listitem><para><command>transfer-source</command> determines -which local address will be bound to IPv4 TCP connections used to -fetch zones transferred inbound by the server. It also determines -the source IPv4 address, and optionally the UDP port, used for the -refresh queries and forwarded dynamic updates. 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 <command>allow-transfer</command> option for -the zone being transferred, if one is specified. This statement -sets the <command>transfer-source</command> for all zones, but can -be overridden on a per-view or per-zone basis by including a -<command>transfer-source</command> statement within the -<command>view</command> or <command>zone</command> block -in the configuration file.</para> -</listitem></varlistentry> - -<varlistentry><term><command>transfer-source-v6</command></term> -<listitem><para>The same as <command>transfer-source</command>, -except zone transfers are performed using IPv6.</para> - </listitem></varlistentry> - <varlistentry> - <term><command>alt-transfer-source</command></term> - <listitem> - <para> - An alternate transfer source if the one listed in - <command>transfer-source</command> fails and - <command>use-alt-transfer-source</command> is - set. - </para> + <note> + <para> + The address specified in the <command>query-source</command> option + is used for both UDP and TCP queries, but the port applies only + to + UDP queries. TCP queries always use a random + unprivileged port. + </para> + </note> + <note> + <para> + Solaris 2.5.1 and earlier does not support setting the source + address for TCP sockets. + </para> + </note> + <note> + <para> + See also <command>transfer-source</command> and + <command>notify-source</command>. + </para> + </note> + </sect3> + + <sect3 id="zone_transfers"> + <title>Zone Transfers</title> + <para> + <acronym>BIND</acronym> has mechanisms in place to + facilitate zone transfers + and set limits on the amount of load that transfers place on the + system. The following options apply to zone transfers. + </para> + + <variablelist> + + <varlistentry> + <term><command>also-notify</command></term> + <listitem> + <para> + Defines a global list of IP addresses of name servers + that are also sent NOTIFY messages whenever a fresh copy of + the + zone is loaded, in addition to the servers listed in the + zone's NS records. + This helps to ensure that copies of the zones will + quickly converge on stealth servers. If an <command>also-notify</command> list + is given in a <command>zone</command> statement, + it will override + the <command>options also-notify</command> + statement. When a <command>zone notify</command> + statement + is set to <command>no</command>, the IP + addresses in the global <command>also-notify</command> list will + not be sent NOTIFY messages for that zone. The default is + the empty + list (no global notification list). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-transfer-time-in</command></term> + <listitem> + <para> + Inbound zone transfers running longer than + this many minutes will be terminated. The default is 120 + minutes + (2 hours). The maximum value is 28 days (40320 minutes). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-transfer-idle-in</command></term> + <listitem> + <para> + Inbound zone transfers making no progress + in this many minutes will be terminated. The default is 60 + minutes + (1 hour). The maximum value is 28 days (40320 minutes). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-transfer-time-out</command></term> + <listitem> + <para> + Outbound zone transfers running longer than + this many minutes will be terminated. The default is 120 + minutes + (2 hours). The maximum value is 28 days (40320 minutes). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-transfer-idle-out</command></term> + <listitem> + <para> + Outbound zone transfers making no progress + in this many minutes will be terminated. The default is 60 + minutes (1 + hour). The maximum value is 28 days (40320 minutes). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>serial-query-rate</command></term> + <listitem> + <para> + Slave servers will periodically query master servers + to find out if zone serial numbers have changed. Each such + query uses + a minute amount of the slave server's network bandwidth. To + limit the + amount of bandwidth used, BIND 9 limits the rate at which + queries are + sent. The value of the <command>serial-query-rate</command> option, + an integer, is the maximum number of queries sent per + second. + The default is 20. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>serial-queries</command></term> + <listitem> + <para> + In BIND 8, the <command>serial-queries</command> + option + set the maximum number of concurrent serial number queries + allowed to be outstanding at any given time. + BIND 9 does not limit the number of outstanding + serial queries and ignores the <command>serial-queries</command> option. + Instead, it limits the rate at which the queries are sent + as defined using the <command>serial-query-rate</command> option. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>transfer-format</command></term> + <listitem> + + <para> + Zone transfers can be sent using two different formats, + <command>one-answer</command> and + <command>many-answers</command>. + The <command>transfer-format</command> option is used + on the master server to determine which format it sends. + <command>one-answer</command> uses one DNS message per + resource record transferred. + <command>many-answers</command> packs as many resource + records as possible into a message. + <command>many-answers</command> is more efficient, but is + only supported by relatively new slave servers, + such as <acronym>BIND</acronym> 9, <acronym>BIND</acronym> + 8.x and <acronym>BIND</acronym> 4.9.5 onwards. + The <command>many-answers</command> format is also supported by + recent Microsoft Windows nameservers. + The default is <command>many-answers</command>. + <command>transfer-format</command> may be overridden on a + per-server basis by using the <command>server</command> + statement. + </para> + + </listitem> + </varlistentry> + + <varlistentry> + <term><command>transfers-in</command></term> + <listitem> + <para> + The maximum number of inbound zone transfers + that can be running concurrently. The default value is <literal>10</literal>. + Increasing <command>transfers-in</command> may + speed up the convergence + of slave zones, but it also may increase the load on the + local system. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>transfers-out</command></term> + <listitem> + <para> + The maximum number of outbound zone transfers + that can be running concurrently. Zone transfer requests in + excess + of the limit will be refused. The default value is <literal>10</literal>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>transfers-per-ns</command></term> + <listitem> + <para> + The maximum number of inbound zone transfers + that can be concurrently transferring from a given remote + name server. + The default value is <literal>2</literal>. + Increasing <command>transfers-per-ns</command> + may + speed up the convergence of slave zones, but it also may + increase + the load on the remote name server. <command>transfers-per-ns</command> may + be overridden on a per-server basis by using the <command>transfers</command> phrase + of the <command>server</command> statement. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>transfer-source</command></term> + <listitem> + <para><command>transfer-source</command> + determines which local address will be bound to IPv4 + TCP connections used to fetch zones transferred + inbound by the server. It also determines the + source IPv4 address, and optionally the UDP port, + used for the refresh queries and forwarded dynamic + updates. 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 + <command>allow-transfer</command> option for the + zone being transferred, if one is specified. This + statement sets the + <command>transfer-source</command> for all zones, + but can be overridden on a per-view or per-zone + basis by including a + <command>transfer-source</command> statement within + the <command>view</command> or + <command>zone</command> block in the configuration + file. + </para> + <note> + <para> + Solaris 2.5.1 and earlier does not support setting the + source address for TCP sockets. + </para> + </note> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>transfer-source-v6</command></term> + <listitem> + <para> + The same as <command>transfer-source</command>, + except zone transfers are performed using IPv6. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>alt-transfer-source</command></term> + <listitem> + <para> + An alternate transfer source if the one listed in + <command>transfer-source</command> fails and + <command>use-alt-transfer-source</command> is + set. + </para> <note> If you do not wish the alternate transfer source to be used, you should set @@ -3868,310 +6354,482 @@ except zone transfers are performed using IPv6.</para> query. </note> </listitem> - </varlistentry> + </varlistentry> + + <varlistentry> + <term><command>alt-transfer-source-v6</command></term> + <listitem> + <para> + An alternate transfer source if the one listed in + <command>transfer-source-v6</command> fails and + <command>use-alt-transfer-source</command> is + set. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>use-alt-transfer-source</command></term> + <listitem> + <para> + Use the alternate transfer sources or not. If views are + specified this defaults to <command>no</command> + otherwise it defaults to + <command>yes</command> (for BIND 8 + compatibility). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>notify-source</command></term> + <listitem> + <para><command>notify-source</command> + determines which local source address, and + optionally UDP port, will be used to send NOTIFY + messages. This address must appear in the slave + server's <command>masters</command> zone clause or + in an <command>allow-notify</command> clause. This + statement sets the <command>notify-source</command> + for all zones, but can be overridden on a per-zone or + per-view basis by including a + <command>notify-source</command> statement within + the <command>zone</command> or + <command>view</command> block in the configuration + file. + </para> + <note> + <para> + Solaris 2.5.1 and earlier does not support setting the + source address for TCP sockets. + </para> + </note> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>notify-source-v6</command></term> + <listitem> + <para> + Like <command>notify-source</command>, + but applies to notify messages sent to IPv6 addresses. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3> + <title>Bad UDP Port Lists</title> + <para><command>avoid-v4-udp-ports</command> + and <command>avoid-v6-udp-ports</command> specify a list + of IPv4 and IPv6 UDP ports that will not be used as system + assigned source ports for UDP sockets. These lists + prevent named from choosing as its random source port a + port that is blocked by your firewall. If a query went + out with such a source port, the answer would not get by + the firewall and the name server would have to query + again. + </para> + </sect3> + + <sect3> + <title>Operating System Resource Limits</title> + + <para> + The server's usage of many system resources can be limited. + Scaled values are allowed when specifying resource limits. For + example, <command>1G</command> can be used instead of + <command>1073741824</command> to specify a limit of + one + gigabyte. <command>unlimited</command> requests + unlimited use, or the + maximum available amount. <command>default</command> + uses the limit + that was in force when the server was started. See the description + of <command>size_spec</command> in <xref linkend="configuration_file_elements"/>. + </para> + + <para> + The following options set operating system resource limits for + the name server process. Some operating systems don't support + some or + any of the limits. On such systems, a warning will be issued if + the + unsupported limit is used. + </para> + + <variablelist> + + <varlistentry> + <term><command>coresize</command></term> + <listitem> + <para> + The maximum size of a core dump. The default + is <literal>default</literal>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>datasize</command></term> + <listitem> + <para> + The maximum amount of data memory the server + may use. The default is <literal>default</literal>. + This is a hard limit on server memory usage. + If the server attempts to allocate memory in excess of this + limit, the allocation will fail, which may in turn leave + the server unable to perform DNS service. Therefore, + this option is rarely useful as a way of limiting the + amount of memory used by the server, but it can be used + to raise an operating system data size limit that is + too small by default. If you wish to limit the amount + of memory used by the server, use the + <command>max-cache-size</command> and + <command>recursive-clients</command> + options instead. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>files</command></term> + <listitem> + <para> + The maximum number of files the server + may have open concurrently. The default is <literal>unlimited</literal>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>stacksize</command></term> + <listitem> + <para> + The maximum amount of stack memory the server + may use. The default is <literal>default</literal>. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3> + <title>Server Resource Limits</title> + + <para> + The following options set limits on the server's + resource consumption that are enforced internally by the + server rather than the operating system. + </para> + + <variablelist> + + <varlistentry> + <term><command>max-ixfr-log-size</command></term> + <listitem> + <para> + This option is obsolete; it is accepted + and ignored for BIND 8 compatibility. The option + <command>max-journal-size</command> performs a + similar function in BIND 9. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-journal-size</command></term> + <listitem> + <para> + Sets a maximum size for each journal file + (see <xref linkend="journal"/>). When the journal file + approaches + the specified size, some of the oldest transactions in the + journal + will be automatically removed. The default is + <literal>unlimited</literal>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>host-statistics-max</command></term> + <listitem> + <para> + In BIND 8, specifies the maximum number of host statistics + entries to be kept. + Not implemented in BIND 9. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>recursive-clients</command></term> + <listitem> + <para> + The maximum number of simultaneous recursive lookups + the server will perform on behalf of clients. The default + is + <literal>1000</literal>. Because each recursing + client uses a fair + bit of memory, on the order of 20 kilobytes, the value of + the + <command>recursive-clients</command> option may + have to be decreased + on hosts with limited memory. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>tcp-clients</command></term> + <listitem> + <para> + The maximum number of simultaneous client TCP + connections that the server will accept. + The default is <literal>100</literal>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-cache-size</command></term> + <listitem> + <para> + The maximum amount of memory to use for the + server's cache, in bytes. When the amount of data in the + cache + reaches this limit, the server will cause records to expire + prematurely so that the limit is not exceeded. In a server + with + multiple views, the limit applies separately to the cache of + each + view. The default is <literal>unlimited</literal>, meaning that + records are purged from the cache only when their TTLs + expire. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>tcp-listen-queue</command></term> + <listitem> + <para> + The listen queue depth. The default and minimum is 3. + If the kernel supports the accept filter "dataready" this + also controls how + many TCP connections that will be queued in kernel space + waiting for + some data before being passed to accept. Values less than 3 + will be + silently raised. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3> + <title>Periodic Task Intervals</title> + + <variablelist> + + <varlistentry> + <term><command>cleaning-interval</command></term> + <listitem> + <para> + The server will remove expired resource records + from the cache every <command>cleaning-interval</command> minutes. + The default is 60 minutes. The maximum value is 28 days + (40320 minutes). + If set to 0, no periodic cleaning will occur. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>heartbeat-interval</command></term> + <listitem> + <para> + The server will perform zone maintenance tasks + for all zones marked as <command>dialup</command> whenever this + interval expires. The default is 60 minutes. Reasonable + values are up + to 1 day (1440 minutes). The maximum value is 28 days + (40320 minutes). + If set to 0, no zone maintenance for these zones will occur. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>interface-interval</command></term> + <listitem> + <para> + The server will scan the network interface list + every <command>interface-interval</command> + minutes. The default + is 60 minutes. The maximum value is 28 days (40320 minutes). + If set to 0, interface scanning will only occur when + the configuration file is loaded. After the scan, the + server will + begin listening for queries on any newly discovered + interfaces (provided they are allowed by the + <command>listen-on</command> configuration), and + will + stop listening on interfaces that have gone away. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>statistics-interval</command></term> + <listitem> + <para> + Name server statistics will be logged + every <command>statistics-interval</command> + minutes. The default is + 60. The maximum value is 28 days (40320 minutes). + If set to 0, no statistics will be logged. + </para><note> + <simpara> + Not yet implemented in + <acronym>BIND</acronym> 9. + </simpara> + </note> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3 id="topology"> + <title>Topology</title> + + <para> + All other things being equal, when the server chooses a name + server + to query from a list of name servers, it prefers the one that is + topologically closest to itself. The <command>topology</command> statement + takes an <command>address_match_list</command> and + interprets it + in a special way. Each top-level list element is assigned a + distance. + Non-negated elements get a distance based on their position in the + list, where the closer the match is to the start of the list, the + shorter the distance is between it and the server. A negated match + will be assigned the maximum distance from the server. If there + is no match, the address will get a distance which is further than + any non-negated list element, and closer than any negated element. + For example, + </para> -<varlistentry><term><command>alt-transfer-source-v6</command></term> -<listitem><para>An alternate transfer source if the one listed in -<command>transfer-source-v6</command> fails and -<command>use-alt-transfer-source</command> is set.</para> - </listitem></varlistentry> - -<varlistentry><term><command>use-alt-transfer-source</command></term> -<listitem><para>Use the alternate transfer sources or not. If views are -specified this defaults to <command>no</command> otherwise it defaults to -<command>yes</command> (for BIND 8 compatibility).</para> -</listitem></varlistentry> - -<varlistentry><term><command>notify-source</command></term> -<listitem><para><command>notify-source</command> determines -which local source address, and optionally UDP port, will be used to -send NOTIFY messages. -This address must appear in the slave server's <command>masters</command> -zone clause or in an <command>allow-notify</command> clause. -This statement sets the <command>notify-source</command> for all zones, -but can be overridden on a per-zone or per-view basis by including a -<command>notify-source</command> statement within the <command>zone</command> -or <command>view</command> block in the configuration file.</para> - <note> - <para> - Solaris 2.5.1 and earlier does not support setting the - source address for TCP sockets. - </para> - </note> -</listitem></varlistentry> - -<varlistentry><term><command>notify-source-v6</command></term> -<listitem><para>Like <command>notify-source</command>, -but applies to notify messages sent to IPv6 addresses.</para> -</listitem></varlistentry> - -</variablelist> - -</sect3> - -<sect3> -<title>Bad UDP Port Lists</title> -<para> -<command>avoid-v4-udp-ports</command> and <command>avoid-v6-udp-ports</command> -specify a list of IPv4 and IPv6 UDP ports that will not be used as system -assigned source ports for UDP sockets. These lists prevent named -from choosing as its random source port a port that is blocked by -your firewall. If a query went out with such a source port, the -answer would not get by the firewall and the name server would have -to query again. -</para> -</sect3> - -<sect3> -<title>Operating System Resource Limits</title> - -<para>The server's usage of many system resources can be limited. -Scaled values are allowed when specifying resource limits. For -example, <command>1G</command> can be used instead of -<command>1073741824</command> to specify a limit of one -gigabyte. <command>unlimited</command> requests unlimited use, or the -maximum available amount. <command>default</command> uses the limit -that was in force when the server was started. See the description -of <command>size_spec</command> in <xref -linkend="configuration_file_elements"/>.</para> - -<para>The following options set operating system resource limits for -the name server process. Some operating systems don't support some or -any of the limits. On such systems, a warning will be issued if the -unsupported limit is used.</para> - -<variablelist> - -<varlistentry><term><command>coresize</command></term> -<listitem><para>The maximum size of a core dump. The default -is <literal>default</literal>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>datasize</command></term> -<listitem><para>The maximum amount of data memory the server -may use. The default is <literal>default</literal>. -This is a hard limit on server memory usage. -If the server attempts to allocate memory in excess of this -limit, the allocation will fail, which may in turn leave -the server unable to perform DNS service. Therefore, -this option is rarely useful as a way of limiting the -amount of memory used by the server, but it can be used -to raise an operating system data size limit that is -too small by default. If you wish to limit the amount -of memory used by the server, use the -<command>max-cache-size</command> and -<command>recursive-clients</command> -options instead. -</para></listitem></varlistentry> - -<varlistentry><term><command>files</command></term> -<listitem><para>The maximum number of files the server -may have open concurrently. The default is <literal>unlimited</literal>. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>stacksize</command></term> -<listitem><para>The maximum amount of stack memory the server -may use. The default is <literal>default</literal>.</para> -</listitem></varlistentry> - -</variablelist> - -</sect3> - -<sect3> -<title>Server Resource Limits</title> - -<para>The following options set limits on the server's -resource consumption that are enforced internally by the -server rather than the operating system.</para> - -<variablelist> - -<varlistentry><term><command>max-ixfr-log-size</command></term> -<listitem><para>This option is obsolete; it is accepted -and ignored for BIND 8 compatibility. The option -<command>max-journal-size</command> performs a similar -function in BIND 8. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-journal-size</command></term> -<listitem><para>Sets a maximum size for each journal file -(see <xref linkend="journal"/>). When the journal file approaches -the specified size, some of the oldest transactions in the journal -will be automatically removed. The default is -<literal>unlimited</literal>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>host-statistics-max</command></term> -<listitem><para>In BIND 8, specifies the maximum number of host statistics -entries to be kept. -Not implemented in BIND 9. -</para></listitem></varlistentry> - -<varlistentry><term><command>recursive-clients</command></term> -<listitem><para>The maximum number of simultaneous recursive lookups -the server will perform on behalf of clients. The default is -<literal>1000</literal>. Because each recursing client uses a fair -bit of memory, on the order of 20 kilobytes, the value of the -<command>recursive-clients</command> option may have to be decreased -on hosts with limited memory. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>tcp-clients</command></term> -<listitem><para>The maximum number of simultaneous client TCP -connections that the server will accept. -The default is <literal>100</literal>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-cache-size</command></term> -<listitem><para>The maximum amount of memory to use for the -server's cache, in bytes. When the amount of data in the cache -reaches this limit, the server will cause records to expire -prematurely so that the limit is not exceeded. In a server with -multiple views, the limit applies separately to the cache of each -view. The default is <literal>unlimited</literal>, meaning that -records are purged from the cache only when their TTLs expire. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>tcp-listen-queue</command></term> -<listitem><para>The listen queue depth. The default and minimum is 3. -If the kernel supports the accept filter "dataready" this also controls how -many TCP connections that will be queued in kernel space waiting for -some data before being passed to accept. Values less than 3 will be -silently raised. -</para> -</listitem></varlistentry> - -</variablelist> - -</sect3> - -<sect3><title>Periodic Task Intervals</title> - -<variablelist> - -<varlistentry><term><command>cleaning-interval</command></term> -<listitem><para>The server will remove expired resource records -from the cache every <command>cleaning-interval</command> minutes. -The default is 60 minutes. The maximum value is 28 days (40320 minutes). -If set to 0, no periodic cleaning will occur.</para> -</listitem></varlistentry> - -<varlistentry><term><command>heartbeat-interval</command></term> -<listitem><para>The server will perform zone maintenance tasks -for all zones marked as <command>dialup</command> whenever this -interval expires. The default is 60 minutes. Reasonable values are up -to 1 day (1440 minutes). The maximum value is 28 days (40320 minutes). -If set to 0, no zone maintenance for these zones will occur.</para> -</listitem></varlistentry> - -<varlistentry><term><command>interface-interval</command></term> -<listitem><para>The server will scan the network interface list -every <command>interface-interval</command> minutes. The default -is 60 minutes. The maximum value is 28 days (40320 minutes). -If set to 0, interface scanning will only occur when -the configuration file is loaded. After the scan, the server will -begin listening for queries on any newly discovered -interfaces (provided they are allowed by the -<command>listen-on</command> configuration), and will -stop listening on interfaces that have gone away.</para> -</listitem></varlistentry> - -<varlistentry><term><command>statistics-interval</command></term> -<listitem><para>Name server statistics will be logged -every <command>statistics-interval</command> minutes. The default is -60. The maximum value is 28 days (40320 minutes). -If set to 0, no statistics will be logged.</para><note> -<simpara>Not yet implemented in <acronym>BIND</acronym>9.</simpara></note> -</listitem></varlistentry> - -</variablelist> - -</sect3> - -<sect3 id="topology"><title>Topology</title> - -<para>All other things being equal, when the server chooses a name server -to query from a list of name servers, it prefers the one that is -topologically closest to itself. The <command>topology</command> statement -takes an <command>address_match_list</command> and interprets it -in a special way. Each top-level list element is assigned a distance. -Non-negated elements get a distance based on their position in the -list, where the closer the match is to the start of the list, the -shorter the distance is between it and the server. A negated match -will be assigned the maximum distance from the server. If there -is no match, the address will get a distance which is further than -any non-negated list element, and closer than any negated element. -For example,</para> <programlisting>topology { 10/8; !1.2.3/24; { 1.2/16; 3/8; }; };</programlisting> -<para>will prefer servers on network 10 the most, followed by hosts -on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the -exception of hosts on network 1.2.3 (netmask 255.255.255.0), which -is preferred least of all.</para> -<para>The default topology is</para> + + <para> + will prefer servers on network 10 the most, followed by hosts + on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the + exception of hosts on network 1.2.3 (netmask 255.255.255.0), which + is preferred least of all. + </para> + <para> + The default topology is + </para> + <programlisting> topology { localhost; localnets; }; </programlisting> -<note><simpara>The <command>topology</command> option -is not implemented in <acronym>BIND</acronym> 9. -</simpara></note> -</sect3> - -<sect3 id="the_sortlist_statement"> - -<title>The <command>sortlist</command> Statement</title> - -<para>The response to a DNS query may consist of multiple resource -records (RRs) forming a resource records set (RRset). -The name server will normally return the -RRs within the RRset in an indeterminate order -(but see the <command>rrset-order</command> -statement in <xref linkend="rrset_ordering"/>). -The client resolver code should rearrange the RRs as appropriate, -that is, using any addresses on the local net in preference to other addresses. -However, not all resolvers can do this or are correctly configured. -When a client is using a local server, the sorting can be performed -in the server, based on the client's address. This only requires -configuring the name servers, not all the clients.</para> - -<para>The <command>sortlist</command> statement (see below) takes -an <command>address_match_list</command> and interprets it even -more specifically than the <command>topology</command> statement -does (<xref linkend="topology"/>). -Each top level statement in the <command>sortlist</command> must -itself be an explicit <command>address_match_list</command> with -one or two elements. The first element (which may be an IP address, -an IP prefix, an ACL name or a nested <command>address_match_list</command>) -of each top level list is checked against the source address of -the query until a match is found.</para> -<para>Once the source address of the query has been matched, if -the top level statement contains only one element, the actual primitive -element that matched the source address is used to select the address -in the response to move to the beginning of the response. If the -statement is a list of two elements, then the second element is -treated the same as the <command>address_match_list</command> in -a <command>topology</command> statement. Each top level element -is assigned a distance and the address in the response with the minimum -distance is moved to the beginning of the response.</para> -<para>In the following example, any queries received from any of -the addresses of the host itself will get responses preferring addresses -on any of the locally connected networks. Next most preferred are addresses -on the 192.168.1/24 network, and after that either the 192.168.2/24 -or -192.168.3/24 network with no preference shown between these two -networks. Queries received from a host on the 192.168.1/24 network -will prefer other addresses on that network to the 192.168.2/24 -and -192.168.3/24 networks. Queries received from a host on the 192.168.4/24 -or the 192.168.5/24 network will only prefer other addresses on -their directly connected networks.</para> + + <note> + <simpara> + The <command>topology</command> option + is not implemented in <acronym>BIND</acronym> 9. + </simpara> + </note> + </sect3> + + <sect3 id="the_sortlist_statement"> + + <title>The <command>sortlist</command> Statement</title> + + <para> + The response to a DNS query may consist of multiple resource + records (RRs) forming a resource records set (RRset). + The name server will normally return the + RRs within the RRset in an indeterminate order + (but see the <command>rrset-order</command> + statement in <xref linkend="rrset_ordering"/>). + The client resolver code should rearrange the RRs as appropriate, + that is, using any addresses on the local net in preference to + other addresses. + However, not all resolvers can do this or are correctly + configured. + When a client is using a local server, the sorting can be performed + in the server, based on the client's address. This only requires + configuring the name servers, not all the clients. + </para> + + <para> + The <command>sortlist</command> statement (see below) + takes + an <command>address_match_list</command> and + interprets it even + more specifically than the <command>topology</command> + statement + does (<xref linkend="topology"/>). + Each top level statement in the <command>sortlist</command> must + itself be an explicit <command>address_match_list</command> with + one or two elements. The first element (which may be an IP + address, + an IP prefix, an ACL name or a nested <command>address_match_list</command>) + of each top level list is checked against the source address of + the query until a match is found. + </para> + <para> + Once the source address of the query has been matched, if + the top level statement contains only one element, the actual + primitive + element that matched the source address is used to select the + address + in the response to move to the beginning of the response. If the + statement is a list of two elements, then the second element is + treated the same as the <command>address_match_list</command> in + a <command>topology</command> statement. Each top + level element + is assigned a distance and the address in the response with the + minimum + distance is moved to the beginning of the response. + </para> + <para> + In the following example, any queries received from any of + the addresses of the host itself will get responses preferring + addresses + on any of the locally connected networks. Next most preferred are + addresses + on the 192.168.1/24 network, and after that either the + 192.168.2/24 + or + 192.168.3/24 network with no preference shown between these two + networks. Queries received from a host on the 192.168.1/24 network + will prefer other addresses on that network to the 192.168.2/24 + and + 192.168.3/24 networks. Queries received from a host on the + 192.168.4/24 + or the 192.168.5/24 network will only prefer other addresses on + their directly connected networks. + </para> + <programlisting>sortlist { { localhost; // IF the local host { localnets; // THEN first fit on the @@ -4189,410 +6847,1047 @@ their directly connected networks.</para> { { 192.168.4/24; 192.168.5/24; }; // if .4 or .5, prefer that net }; };</programlisting> -<para>The following example will give reasonable behavior for the -local host and hosts on directly connected networks. It is similar -to the behavior of the address sort in <acronym>BIND</acronym> 4.9.x. Responses sent -to queries from the local host will favor any of the directly connected -networks. Responses sent to queries from any other hosts on a directly -connected network will prefer addresses on that same network. Responses -to other queries will not be sorted.</para> + + <para> + The following example will give reasonable behavior for the + local host and hosts on directly connected networks. It is similar + to the behavior of the address sort in <acronym>BIND</acronym> 4.9.x. Responses sent + to queries from the local host will favor any of the directly + connected + networks. Responses sent to queries from any other hosts on a + directly + connected network will prefer addresses on that same network. + Responses + to other queries will not be sorted. + </para> + <programlisting>sortlist { { localhost; localnets; }; { localnets; }; }; </programlisting> -</sect3> -<sect3 id="rrset_ordering"><title id="rrset_ordering_title">RRset Ordering</title> -<para>When multiple records are returned in an answer it may be -useful to configure the order of the records placed into the response. -The <command>rrset-order</command> statement permits configuration -of the ordering of the records in a multiple record response. -See also the <command>sortlist</command> statement, -<xref linkend="the_sortlist_statement"/>. -</para> - -<para>An <command>order_spec</command> is defined as follows:</para> -<programlisting><optional> class <replaceable>class_name</replaceable> </optional><optional> type <replaceable>type_name</replaceable> </optional><optional> name <replaceable>"domain_name"</replaceable></optional> - order <replaceable>ordering</replaceable> -</programlisting> -<para>If no class is specified, the default is <command>ANY</command>. -If no type is specified, the default is <command>ANY</command>. -If no name is specified, the default is "<command>*</command>" (asterisk).</para> -<para>The legal values for <command>ordering</command> are:</para> -<informaltable colsep = "0" rowsep = "0"><tgroup cols = "2" - colsep = "0" rowsep = "0" tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.750in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.750in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><command>fixed</command></para></entry> -<entry colname = "2"><para>Records are returned in the order they -are defined in the zone file.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>random</command></para></entry> -<entry colname = "2"><para>Records are returned in some random order.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>cyclic</command></para></entry> -<entry colname = "2"><para>Records are returned in a round-robin -order.</para></entry> -</row> -</tbody> -</tgroup></informaltable> -<para>For example:</para> + + </sect3> + <sect3 id="rrset_ordering"> + <title id="rrset_ordering_title">RRset Ordering</title> + <para> + When multiple records are returned in an answer it may be + useful to configure the order of the records placed into the + response. + The <command>rrset-order</command> statement permits + configuration + of the ordering of the records in a multiple record response. + See also the <command>sortlist</command> statement, + <xref linkend="the_sortlist_statement"/>. + </para> + + <para> + An <command>order_spec</command> is defined as + follows: + </para> + <para> + <optional>class <replaceable>class_name</replaceable></optional> + <optional>type <replaceable>type_name</replaceable></optional> + <optional>name <replaceable>"domain_name"</replaceable></optional> + order <replaceable>ordering</replaceable> + </para> + <para> + If no class is specified, the default is <command>ANY</command>. + If no type is specified, the default is <command>ANY</command>. + If no name is specified, the default is "<command>*</command>" (asterisk). + </para> + <para> + The legal values for <command>ordering</command> are: + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="0.750in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.750in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para><command>fixed</command></para> + </entry> + <entry colname="2"> + <para> + Records are returned in the order they + are defined in the zone file. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>random</command></para> + </entry> + <entry colname="2"> + <para> + Records are returned in some random order. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>cyclic</command></para> + </entry> + <entry colname="2"> + <para> + Records are returned in a round-robin + order. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + For example: + </para> + <programlisting>rrset-order { class IN type A name "host.example.com" order random; order cyclic; }; </programlisting> -<para>will cause any responses for type A records in class IN that -have "<literal>host.example.com</literal>" as a suffix, to always be returned -in random order. All other records are returned in cyclic order.</para> -<para>If multiple <command>rrset-order</command> statements appear, -they are not combined — the last one applies.</para> - -<note> -<simpara>The <command>rrset-order</command> statement -is not yet fully implemented in <acronym>BIND</acronym> 9. -BIND 9 currently does not support "fixed" ordering. -</simpara></note> -</sect3> - -<sect3 id="tuning"><title>Tuning</title> - -<variablelist> - -<varlistentry><term><command>lame-ttl</command></term> -<listitem><para>Sets the number of seconds to cache a -lame server indication. 0 disables caching. (This is -<emphasis role="bold">NOT</emphasis> recommended.) -The default is <literal>600</literal> (10 minutes) and the maximum value is -<literal>1800</literal> (30 minutes).</para> - -</listitem></varlistentry> - -<varlistentry><term><command>max-ncache-ttl</command></term> -<listitem><para>To reduce network traffic and increase performance, -the server stores negative answers. <command>max-ncache-ttl</command> is -used to set a maximum retention time for these answers in the server -in seconds. The default -<command>max-ncache-ttl</command> is <literal>10800</literal> seconds (3 hours). -<command>max-ncache-ttl</command> cannot exceed 7 days and will -be silently truncated to 7 days if set to a greater value.</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-cache-ttl</command></term> -<listitem><para>Sets -the maximum time for which the server will cache ordinary (positive) -answers. The default is one week (7 days).</para> -</listitem></varlistentry> - -<varlistentry><term><command>min-roots</command></term> -<listitem><para>The minimum number of root servers that -is required for a request for the root servers to be accepted. The default -is <userinput>2</userinput>.</para> -<note> -<simpara>Not implemented in <acronym>BIND</acronym> 9.</simpara></note> -</listitem></varlistentry> - -<varlistentry><term><command>sig-validity-interval</command></term> -<listitem><para>Specifies the number of days into the -future when DNSSEC signatures automatically generated as a result -of dynamic updates (<xref linkend="dynamic_update"/>) -will expire. The default is <literal>30</literal> days. -The maximum value is 10 years (3660 days). The signature -inception time is unconditionally set to one hour before the current time -to allow for a limited amount of clock skew.</para> -</listitem></varlistentry> - -<varlistentry> -<term><command>min-refresh-time</command></term> -<term><command>max-refresh-time</command></term> -<term><command>min-retry-time</command></term> -<term><command>max-retry-time</command></term> -<listitem><para> -These options control the server's behavior on refreshing a zone -(querying for SOA changes) or retrying failed transfers. -Usually the SOA values for the zone are used, but these values -are set by the master, giving slave server administrators little -control over their contents. -</para><para> -These options allow the administrator to set a minimum and maximum -refresh and retry time either per-zone, per-view, or globally. -These options are valid for slave and stub zones, -and clamp the SOA refresh and retry times to the specified values. -</para></listitem></varlistentry> - -<varlistentry> -<term><command>edns-udp-size</command></term> -<listitem><para> -<command>edns-udp-size</command> sets the advertised EDNS UDP buffer -size in bytes. Valid values are 512 to 4096 bytes (values outside this range will be -silently adjusted). The default value is 4096. The usual reason for -setting edns-udp-size to a non-default value it to get UDP answers to -pass through broken firewalls that block fragmented packets and/or -block UDP packets that are greater than 512 bytes. -</para></listitem></varlistentry> -</variablelist> - -</sect3> - -<sect3 id="builtin"> -<title>Built-in server information zones</title> - -<para>The server provides some helpful diagnostic information -through a number of built-in zones under the -pseudo-top-level-domain <literal>bind</literal> in the -<command>CHAOS</command> class. These zones are part of a -built-in view (see <xref linkend="view_statement_grammar"/>) of class -<command>CHAOS</command> which is separate from the default view of -class <command>IN</command>; therefore, any global server options -such as <command>allow-query</command> do not apply the these zones. -If you feel the need to disable these zones, use the options -below, or hide the built-in <command>CHAOS</command> view by -defining an explicit view of class <command>CHAOS</command> -that matches all clients.</para> - -<variablelist> - -<varlistentry><term><command>version</command></term> -<listitem><para>The version the server should report -via a query of the name <literal>version.bind</literal> -with type <command>TXT</command>, class <command>CHAOS</command>. -The default is the real version number of this server. -Specifying <command>version none</command> -disables processing of the queries.</para> -</listitem></varlistentry> - -<varlistentry><term><command>hostname</command></term> -<listitem><para>The hostname the server should report via a query of -the name <filename>hostname.bind</filename> -with type <command>TXT</command>, class <command>CHAOS</command>. -This defaults to the hostname of the machine hosting the name server as -found by the gethostname() function. The primary purpose of such queries is to -identify which of a group of anycast servers is actually -answering your queries. Specifying <command>hostname none;</command> -disables processing of the queries.</para> -</listitem></varlistentry> - -<varlistentry><term><command>server-id</command></term> -<listitem><para>The ID of the server should report via a query of -the name <filename>ID.SERVER</filename> -with type <command>TXT</command>, class <command>CHAOS</command>. -The primary purpose of such queries is to -identify which of a group of anycast servers is actually -answering your queries. Specifying <command>server-id none;</command> -disables processing of the queries. -Specifying <command>server-id hostname;</command> will cause named to -use the hostname as found by the gethostname() function. -The default <command>server-id</command> is <command>none</command>. -</para> -</listitem></varlistentry> - -</variablelist> - -</sect3> - -<sect3 id="statsfile"> -<title>The Statistics File</title> - -<para>The statistics file generated by <acronym>BIND</acronym> 9 -is similar, but not identical, to that -generated by <acronym>BIND</acronym> 8. -</para> -<para>The statistics dump begins with a line, like:</para> - <para> - <command>+++ Statistics Dump +++ (973798949)</command> - </para> - <para>The numberr in parentheses is a standard -Unix-style timestamp, measured as seconds since January 1, 1970. Following -that line are a series of lines containing a counter type, the value of the -counter, optionally a zone name, and optionally a view name. -The lines without view and zone listed are global statistics for the entire server. -Lines with a zone and view name for the given view and zone (the view name is -omitted for the default view). -</para> -<para> -The statistics dump ends with the line where the -number is identical to the number in the beginning line; for example: -</para> -<para> -<command>--- Statistics Dump --- (973798949)</command> -</para> -<para>The following statistics counters are maintained:</para> -<informaltable - colsep = "0" rowsep = "0"><tgroup cols = "2" - colsep = "0" rowsep = "0" tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.150in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.350in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><command>success</command></para></entry> -<entry colname = "2"><para>The number of -successful queries made to the server or zone. A successful query -is defined as query which returns a NOERROR response with at least -one answer RR.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>referral</command></para></entry> -<entry colname = "2"><para>The number of queries which resulted -in referral responses.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>nxrrset</command></para></entry> -<entry colname = "2"><para>The number of queries which resulted in -NOERROR responses with no data.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>nxdomain</command></para></entry> -<entry colname = "2"><para>The number -of queries which resulted in NXDOMAIN responses.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>failure</command></para></entry> -<entry colname = "2"><para>The number of queries which resulted in a -failure response other than those above.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><command>recursion</command></para></entry> -<entry colname = "2"><para>The number of queries which caused the server -to perform recursion in order to find the final answer.</para></entry> -</row> -</tbody> -</tgroup></informaltable> - -<para> -Each query received by the server will cause exactly one of -<command>success</command>, -<command>referral</command>, -<command>nxrrset</command>, -<command>nxdomain</command>, or -<command>failure</command> -to be incremented, and may additionally cause the -<command>recursion</command> counter to be incremented. -</para> - -</sect3> - -</sect2> - -<sect2 id="server_statement_grammar"> -<title><command>server</command> Statement Grammar</title> - -<programlisting>server <replaceable>ip_addr</replaceable> { + + <para> + will cause any responses for type A records in class IN that + have "<literal>host.example.com</literal>" as a + suffix, to always be returned + in random order. All other records are returned in cyclic order. + </para> + <para> + If multiple <command>rrset-order</command> statements + appear, + they are not combined — the last one applies. + </para> + + <note> + <simpara> + The <command>rrset-order</command> statement + is not yet fully implemented in <acronym>BIND</acronym> 9. + BIND 9 currently does not fully support "fixed" ordering. + </simpara> + </note> + </sect3> + + <sect3 id="tuning"> + <title>Tuning</title> + + <variablelist> + + <varlistentry> + <term><command>lame-ttl</command></term> + <listitem> + <para> + Sets the number of seconds to cache a + lame server indication. 0 disables caching. (This is + <emphasis role="bold">NOT</emphasis> recommended.) + The default is <literal>600</literal> (10 minutes) and the + maximum value is + <literal>1800</literal> (30 minutes). + </para> + + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-ncache-ttl</command></term> + <listitem> + <para> + To reduce network traffic and increase performance, + the server stores negative answers. <command>max-ncache-ttl</command> is + used to set a maximum retention time for these answers in + the server + in seconds. The default + <command>max-ncache-ttl</command> is <literal>10800</literal> seconds (3 hours). + <command>max-ncache-ttl</command> cannot exceed + 7 days and will + be silently truncated to 7 days if set to a greater value. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-cache-ttl</command></term> + <listitem> + <para> + Sets the maximum time for which the server will + cache ordinary (positive) answers. The default is + one week (7 days). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>min-roots</command></term> + <listitem> + <para> + The minimum number of root servers that + is required for a request for the root servers to be + accepted. The default + is <userinput>2</userinput>. + </para> + <note> + <simpara> + Not implemented in <acronym>BIND</acronym> 9. + </simpara> + </note> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>sig-validity-interval</command></term> + <listitem> + <para> + Specifies the number of days into the + future when DNSSEC signatures automatically generated as a + result + of dynamic updates (<xref linkend="dynamic_update"/>) + will expire. The default is <literal>30</literal> days. + The maximum value is 10 years (3660 days). The signature + inception time is unconditionally set to one hour before the + current time + to allow for a limited amount of clock skew. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>min-refresh-time</command></term> + <term><command>max-refresh-time</command></term> + <term><command>min-retry-time</command></term> + <term><command>max-retry-time</command></term> + <listitem> + <para> + These options control the server's behavior on refreshing a + zone + (querying for SOA changes) or retrying failed transfers. + Usually the SOA values for the zone are used, but these + values + are set by the master, giving slave server administrators + little + control over their contents. + </para> + <para> + These options allow the administrator to set a minimum and + maximum + refresh and retry time either per-zone, per-view, or + globally. + These options are valid for slave and stub zones, + and clamp the SOA refresh and retry times to the specified + values. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>edns-udp-size</command></term> + <listitem> + <para> + Sets the advertised EDNS UDP buffer size in bytes. Valid + values are 512 to 4096 (values outside this range + will be silently adjusted). The default value is + 4096. The usual reason for setting edns-udp-size to + a non-default value is to get UDP answers to pass + through broken firewalls that block fragmented + packets and/or block UDP packets that are greater + than 512 bytes. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-udp-size</command></term> + <listitem> + <para> + Sets the maximum EDNS UDP message size named will + send in bytes. Valid values are 512 to 4096 (values outside + this range will be silently adjusted). The default + value is 4096. The usual reason for setting + max-udp-size to a non-default value is to get UDP + answers to pass through broken firewalls that + block fragmented packets and/or block UDP packets + that are greater than 512 bytes. + This is independent of the advertised receive + buffer (<command>edns-udp-size</command>). + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>masterfile-format</command></term> + <listitem> + <para>Specifies + the file format of zone files (see + <xref linkend="zonefile_format"/>). + The default value is <constant>text</constant>, which is the + standard textual representation. Files in other formats + than <constant>text</constant> are typically expected + to be generated by the <command>named-compilezone</command> tool. + Note that when a zone file in a different format than + <constant>text</constant> is loaded, <command>named</command> + may omit some of the checks which would be performed for a + file in the <constant>text</constant> format. In particular, + <command>check-names</command> checks do not apply + for the <constant>raw</constant> format. This means + a zone file in the <constant>raw</constant> format + must be generated with the same check level as that + specified in the <command>named</command> configuration + file. This statement sets the + <command>masterfile-format</command> for all zones, + but can be overridden on a per-zone or per-view basis + by including a <command>masterfile-format</command> + statement within the <command>zone</command> or + <command>view</command> block in the configuration + file. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>clients-per-query</command></term> + <term><command>max-clients-per-query</command></term> + <listitem> + <para>These set the + initial value (minimum) and maximum number of recursive + simultanious clients for any given query + (<qname,qtype,qclass>) that the server will accept + before dropping additional clients. named will attempt to + self tune this value and changes will be logged. The + default values are 10 and 100. + </para> + <para> + This value should reflect how many queries come in for + a given name in the time it takes to resolve that name. + If the number of queries exceed this value, named will + assume that it is dealing with a non-responsive zone + and will drop additional queries. If it gets a response + after dropping queries, it will raise the estimate. The + estimate will then be lowered in 20 minutes if it has + remained unchanged. + </para> + <para> + If <command>clients-per-query</command> is set to zero, + then there is no limit on the number of clients per query + and no queries will be dropped. + </para> + <para> + If <command>max-clients-per-query</command> is set to zero, + then there is no upper bound other than imposed by + <command>recursive-clients</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>notify-delay</command></term> + <listitem> + <para> + The delay, in seconds, between sending sets of notify + messages for a zone. The default is zero. + </para> + </listitem> + </varlistentry> + </variablelist> + + </sect3> + + <sect3 id="builtin"> + <title>Built-in server information zones</title> + + <para> + The server provides some helpful diagnostic information + through a number of built-in zones under the + pseudo-top-level-domain <literal>bind</literal> in the + <command>CHAOS</command> class. These zones are part + of a + built-in view (see <xref linkend="view_statement_grammar"/>) of + class + <command>CHAOS</command> which is separate from the + default view of + class <command>IN</command>; therefore, any global + server options + such as <command>allow-query</command> do not apply + the these zones. + If you feel the need to disable these zones, use the options + below, or hide the built-in <command>CHAOS</command> + view by + defining an explicit view of class <command>CHAOS</command> + that matches all clients. + </para> + + <variablelist> + + <varlistentry> + <term><command>version</command></term> + <listitem> + <para> + The version the server should report + via a query of the name <literal>version.bind</literal> + with type <command>TXT</command>, class <command>CHAOS</command>. + The default is the real version number of this server. + Specifying <command>version none</command> + disables processing of the queries. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>hostname</command></term> + <listitem> + <para> + The hostname the server should report via a query of + the name <filename>hostname.bind</filename> + with type <command>TXT</command>, class <command>CHAOS</command>. + This defaults to the hostname of the machine hosting the + name server as + found by the gethostname() function. The primary purpose of such queries + is to + identify which of a group of anycast servers is actually + answering your queries. Specifying <command>hostname none;</command> + disables processing of the queries. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>server-id</command></term> + <listitem> + <para> + The ID of the server should report via a query of + the name <filename>ID.SERVER</filename> + with type <command>TXT</command>, class <command>CHAOS</command>. + The primary purpose of such queries is to + identify which of a group of anycast servers is actually + answering your queries. Specifying <command>server-id none;</command> + disables processing of the queries. + Specifying <command>server-id hostname;</command> will cause named to + use the hostname as found by the gethostname() function. + The default <command>server-id</command> is <command>none</command>. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + <sect3 id="empty"> + <title>Built-in Empty Zones</title> + <para> + Named has some built-in empty zones (SOA and NS records only). + These are for zones that should normally be answered locally + and which queries should not be sent to the Internet's root + servers. The official servers which cover these namespaces + return NXDOMAIN responses to these queries. In particular, + these cover the reverse namespace for addresses from RFC 1918 and + RFC 3330. They also include the reverse namespace for IPv6 local + address (locally assigned), IPv6 link local addresses, the IPv6 + loopback address and the IPv6 unknown addresss. + </para> + <para> + Named will attempt to determine if a built in zone already exists + or is active (covered by a forward-only forwarding declaration) + and will not not create a empty zone in that case. + </para> + <para> + The current list of empty zones is: + <itemizedlist> + <listitem>10.IN-ADDR.ARPA</listitem> + <listitem>127.IN-ADDR.ARPA</listitem> + <listitem>254.169.IN-ADDR.ARPA</listitem> + <listitem>16.172.IN-ADDR.ARPA</listitem> + <listitem>17.172.IN-ADDR.ARPA</listitem> + <listitem>18.172.IN-ADDR.ARPA</listitem> + <listitem>19.172.IN-ADDR.ARPA</listitem> + <listitem>20.172.IN-ADDR.ARPA</listitem> + <listitem>21.172.IN-ADDR.ARPA</listitem> + <listitem>22.172.IN-ADDR.ARPA</listitem> + <listitem>23.172.IN-ADDR.ARPA</listitem> + <listitem>24.172.IN-ADDR.ARPA</listitem> + <listitem>25.172.IN-ADDR.ARPA</listitem> + <listitem>26.172.IN-ADDR.ARPA</listitem> + <listitem>27.172.IN-ADDR.ARPA</listitem> + <listitem>28.172.IN-ADDR.ARPA</listitem> + <listitem>29.172.IN-ADDR.ARPA</listitem> + <listitem>30.172.IN-ADDR.ARPA</listitem> + <listitem>31.172.IN-ADDR.ARPA</listitem> + <listitem>168.192.IN-ADDR.ARPA</listitem> + <listitem>2.0.192.IN-ADDR.ARPA</listitem> + <listitem>0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</listitem> + <listitem>1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</listitem> + <listitem>D.F.IP6.ARPA</listitem> + <listitem>8.E.F.IP6.ARPA</listitem> + <listitem>9.E.F.IP6.ARPA</listitem> + <listitem>A.E.F.IP6.ARPA</listitem> + <listitem>B.E.F.IP6.ARPA</listitem> + </itemizedlist> + </para> + <para> + Empty zones are settable at the view level and only apply to + views of class IN. Disabled empty zones are only inherited + from options if there are no disabled empty zones specified + at the view level. To override the options list of disabled + zones, you can disable the root zone at the view level, for example: +<programlisting> + disable-empty-zone "."; +</programlisting> + </para> + <para> + If you are using the address ranges covered here, you should + already have reverse zones covering the addresses you use. + In practice this appears to not be the case with many queries + being made to the infrastructure servers for names in these + spaces. So many in fact that sacrificial servers were needed + to be deployed to channel the query load away from the + infrastructure servers. + </para> + <note> + The real parent servers for these zones should disable all + empty zone under the parent zone they serve. For the real + root servers, this is all built in empty zones. This will + enable them to return referrals to deeper in the tree. + </note> + <variablelist> + <varlistentry> + <term><command>empty-server</command></term> + <listitem> + <para> + Specify what server name will appear in the returned + SOA record for empty zones. If none is specified, then + the zone's name will be used. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>empty-contact</command></term> + <listitem> + <para> + Specify what contact name will appear in the returned + SOA record for empty zones. If none is specified, then + "." will be used. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>empty-zones-enable</command></term> + <listitem> + <para> + Enable or disable all empty zones. By default they + are enabled. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>disable-empty-zone</command></term> + <listitem> + <para> + Disable individual empty zones. By default none are + disabled. This option can be specified multiple times. + </para> + </listitem> + </varlistentry> + </variablelist> + </sect3> + + <sect3 id="statsfile"> + <title>The Statistics File</title> + + <para> + The statistics file generated by <acronym>BIND</acronym> 9 + is similar, but not identical, to that + generated by <acronym>BIND</acronym> 8. + </para> + <para> + The statistics dump begins with a line, like: + </para> + <para> + <command>+++ Statistics Dump +++ (973798949)</command> + </para> + <para> + The number in parentheses is a standard + Unix-style timestamp, measured as seconds since January 1, 1970. + Following + that line are a series of lines containing a counter type, the + value of the + counter, optionally a zone name, and optionally a view name. + The lines without view and zone listed are global statistics for + the entire server. + Lines with a zone and view name for the given view and zone (the + view name is + omitted for the default view). + </para> + <para> + The statistics dump ends with the line where the + number is identical to the number in the beginning line; for example: + </para> + <para> + <command>--- Statistics Dump --- (973798949)</command> + </para> + <para> + The following statistics counters are maintained: + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.350in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para><command>success</command></para> + </entry> + <entry colname="2"> + <para> + The number of + successful queries made to the server or zone. A + successful query + is defined as query which returns a NOERROR response + with at least + one answer RR. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>referral</command></para> + </entry> + <entry colname="2"> + <para> + The number of queries which resulted + in referral responses. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>nxrrset</command></para> + </entry> + <entry colname="2"> + <para> + The number of queries which resulted in + NOERROR responses with no data. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>nxdomain</command></para> + </entry> + <entry colname="2"> + <para> + The number + of queries which resulted in NXDOMAIN responses. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>failure</command></para> + </entry> + <entry colname="2"> + <para> + The number of queries which resulted in a + failure response other than those above. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>recursion</command></para> + </entry> + <entry colname="2"> + <para> + The number of queries which caused the server + to perform recursion in order to find the final answer. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>duplicate</command></para> + </entry> + <entry colname="2"> + <para> + The number of queries which the server attempted to + recurse but discover a existing query with the same + IP address, port, query id, name, type and class + already being processed. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>dropped</command></para> + </entry> + <entry colname="2"> + <para> + The number of queries for which the server + discovered a excessive number of existing + recursive queries for the same name, type and + class and were subsequently dropped. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + + <para> + Each query received by the server will cause exactly one of + <command>success</command>, + <command>referral</command>, + <command>nxrrset</command>, + <command>nxdomain</command>, or + <command>failure</command> + to be incremented, and may additionally cause the + <command>recursion</command> counter to be + incremented. + </para> + + </sect3> + + <sect3 id="acache"> + <title>Additional Section Caching</title> + + <para> + The additional section cache, also called <command>acache</command>, + is an internal cache to improve the response performance of BIND 9. + When additional section caching is enabled, BIND 9 will + cache an internal short-cut to the additional section content for + each answer RR. + Note that <command>acache</command> is an internal caching + mechanism of BIND 9, and is not related to the DNS caching + server function. + </para> + + <para> + Additional section caching does not change the + response content (except the RRsets ordering of the additional + section, see below), but can improve the response performance + significantly. + It is particularly effective when BIND 9 acts as an authoritative + server for a zone that has many delegations with many glue RRs. + </para> + + <para> + In order to obtain the maximum performance improvement + from additional section caching, setting + <command>additional-from-cache</command> + to <command>no</command> is recommended, since the current + implementation of <command>acache</command> + does not short-cut of additional section information from the + DNS cache data. + </para> + + <para> + One obvious disadvantage of <command>acache</command> is + that it requires much more + memory for the internal cached data. + Thus, if the response performance does not matter and memory + consumption is much more critical, the + <command>acache</command> mechanism can be + disabled by setting <command>acache-enable</command> to + <command>no</command>. + It is also possible to specify the upper limit of memory + consumption + for acache by using <command>max-acache-size</command>. + </para> + + <para> + Additional section caching also has a minor effect on the + RRset ordering in the additional section. + Without <command>acache</command>, + <command>cyclic</command> order is effective for the additional + section as well as the answer and authority sections. + However, additional section caching fixes the ordering when it + first caches an RRset for the additional section, and the same + ordering will be kept in succeeding responses, regardless of the + setting of <command>rrset-order</command>. + The effect of this should be minor, however, since an + RRset in the additional section + typically only contains a small number of RRs (and in many cases + it only contains a single RR), in which case the + ordering does not matter much. + </para> + + <para> + The following is a summary of options related to + <command>acache</command>. + </para> + + <variablelist> + + <varlistentry> + <term><command>acache-enable</command></term> + <listitem> + <para> + If <command>yes</command>, additional section caching is + enabled. The default value is <command>no</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>acache-cleaning-interval</command></term> + <listitem> + <para> + The server will remove stale cache entries, based on an LRU + based + algorithm, every <command>acache-cleaning-interval</command> minutes. + The default is 60 minutes. + If set to 0, no periodic cleaning will occur. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-acache-size</command></term> + <listitem> + <para> + The maximum amount of memory in bytes to use for the server's acache. + When the amount of data in the acache reaches this limit, + the server + will clean more aggressively so that the limit is not + exceeded. + In a server with multiple views, the limit applies + separately to the + acache of each view. + The default is <literal>unlimited</literal>, + meaning that + entries are purged from the acache only at the + periodic cleaning time. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + + </sect2> + + <sect2 id="server_statement_grammar"> + <title><command>server</command> Statement Grammar</title> + +<programlisting>server <replaceable>ip_addr[/prefixlen]</replaceable> { <optional> bogus <replaceable>yes_or_no</replaceable> ; </optional> <optional> provide-ixfr <replaceable>yes_or_no</replaceable> ; </optional> <optional> request-ixfr <replaceable>yes_or_no</replaceable> ; </optional> <optional> edns <replaceable>yes_or_no</replaceable> ; </optional> + <optional> edns-udp-size <replaceable>number</replaceable> ; </optional> + <optional> max-udp-size <replaceable>number</replaceable> ; </optional> <optional> transfers <replaceable>number</replaceable> ; </optional> <optional> transfer-format <replaceable>( one-answer | many-answers )</replaceable> ; ]</optional> <optional> keys <replaceable>{ string ; <optional> string ; <optional>...</optional></optional> }</replaceable> ; </optional> <optional> transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> <optional> transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> + <optional> notify-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> + <optional> notify-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> + <optional> query-source <optional> address ( <replaceable>ip_addr</replaceable> | <replaceable>*</replaceable> ) </optional> <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional>; </optional> + <optional> query-source-v6 <optional> address ( <replaceable>ip_addr</replaceable> | <replaceable>*</replaceable> ) </optional> <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional>; </optional> }; </programlisting> -</sect2> - -<sect2 id="server_statement_definition_and_usage"> -<title><command>server</command> Statement Definition and Usage</title> - -<para>The <command>server</command> statement defines characteristics -to be associated with a remote name server.</para> - -<para> -The <command>server</command> statement can occur at the top level of the -configuration file or inside a <command>view</command> statement. -If a <command>view</command> statement contains -one or more <command>server</command> statements, only those -apply to the view and any top-level ones are ignored. -If a view contains no <command>server</command> statements, -any top-level <command>server</command> statements are used as -defaults. -</para> - -<para>If you discover that a remote server is giving out bad data, -marking it as bogus will prevent further queries to it. The default -value of <command>bogus</command> is <command>no</command>.</para> -<para>The <command>provide-ixfr</command> clause determines whether -the local server, acting as master, will respond with an incremental -zone transfer when the given remote server, a slave, requests it. -If set to <command>yes</command>, incremental transfer will be provided -whenever possible. If set to <command>no</command>, all transfers -to the remote server will be non-incremental. If not set, the value -of the <command>provide-ixfr</command> option in the view or -global options block is used as a default.</para> - -<para>The <command>request-ixfr</command> clause determines whether -the local server, acting as a slave, will request incremental zone -transfers from the given remote server, a master. If not set, the -value of the <command>request-ixfr</command> option in the view or -global options block is used as a default.</para> - -<para>IXFR requests to servers that do not support IXFR will automatically -fall back to AXFR. Therefore, there is no need to manually list -which servers support IXFR and which ones do not; the global default -of <command>yes</command> should always work. -The purpose of the <command>provide-ixfr</command> and -<command>request-ixfr</command> clauses is -to make it possible to disable the use of IXFR even when both master -and slave claim to support it, for example if one of the servers -is buggy and crashes or corrupts data when IXFR is used.</para> - -<para>The <command>edns</command> clause determines whether the local server -will attempt to use EDNS when communicating with the remote server. The -default is <command>yes</command>.</para> - -<para>The server supports two zone transfer methods. The first, <command>one-answer</command>, -uses one DNS message per resource record transferred. <command>many-answers</command> packs -as many resource records as possible into a message. <command>many-answers</command> is -more efficient, but is only known to be understood by <acronym>BIND</acronym> 9, <acronym>BIND</acronym> -8.x, and patched versions of <acronym>BIND</acronym> 4.9.5. You can specify which method -to use for a server with the <command>transfer-format</command> option. -If <command>transfer-format</command> is not specified, the <command>transfer-format</command> specified -by the <command>options</command> statement will be used.</para> - -<para><command>transfers</command> is used to limit the number of -concurrent inbound zone transfers from the specified server. If -no <command>transfers</command> clause is specified, the limit is -set according to the <command>transfers-per-ns</command> option.</para> - -<para>The <command>keys</command> clause identifies a -<command>key_id</command> defined by the <command>key</command> statement, -to be used for transaction security (TSIG, <xref linkend="tsig"/>) -when talking to the remote server. -When a request is sent to the remote server, a request signature -will be generated using the key specified here and appended to the -message. A request originating from the remote server is not required -to be signed by this key.</para> - -<para>Although the grammar of the <command>keys</command> clause -allows for multiple keys, only a single key per server is currently -supported.</para> - -<para>The <command>transfer-source</command> and -<command>transfer-source-v6</command> clauses specify the IPv4 and IPv6 source -address to be used for zone transfer with the remote server, respectively. -For an IPv4 remote server, only <command>transfer-source</command> can -be specified. -Similarly, for an IPv6 remote server, only -<command>transfer-source-v6</command> can be specified. -For more details, see the description of -<command>transfer-source</command> and -<command>transfer-source-v6</command> in -<xref linkend="zone_transfers"/>.</para> - -</sect2> - -<sect2><title><command>trusted-keys</command> Statement Grammar</title> + </sect2> + + <sect2 id="server_statement_definition_and_usage"> + <title><command>server</command> Statement Definition and + Usage</title> + + <para> + The <command>server</command> statement defines + characteristics + to be associated with a remote name server. If a prefix length is + specified, then a range of servers is covered. Only the most + specific + server clause applies regardless of the order in + <filename>named.conf</filename>. + </para> + + <para> + The <command>server</command> statement can occur at + the top level of the + configuration file or inside a <command>view</command> + statement. + If a <command>view</command> statement contains + one or more <command>server</command> statements, only + those + apply to the view and any top-level ones are ignored. + If a view contains no <command>server</command> + statements, + any top-level <command>server</command> statements are + used as + defaults. + </para> + + <para> + If you discover that a remote server is giving out bad data, + marking it as bogus will prevent further queries to it. The + default + value of <command>bogus</command> is <command>no</command>. + </para> + <para> + The <command>provide-ixfr</command> clause determines + whether + the local server, acting as master, will respond with an + incremental + zone transfer when the given remote server, a slave, requests it. + If set to <command>yes</command>, incremental transfer + will be provided + whenever possible. If set to <command>no</command>, + all transfers + to the remote server will be non-incremental. If not set, the + value + of the <command>provide-ixfr</command> option in the + view or + global options block is used as a default. + </para> + + <para> + The <command>request-ixfr</command> clause determines + whether + the local server, acting as a slave, will request incremental zone + transfers from the given remote server, a master. If not set, the + value of the <command>request-ixfr</command> option in + the view or + global options block is used as a default. + </para> + + <para> + IXFR requests to servers that do not support IXFR will + automatically + fall back to AXFR. Therefore, there is no need to manually list + which servers support IXFR and which ones do not; the global + default + of <command>yes</command> should always work. + The purpose of the <command>provide-ixfr</command> and + <command>request-ixfr</command> clauses is + to make it possible to disable the use of IXFR even when both + master + and slave claim to support it, for example if one of the servers + is buggy and crashes or corrupts data when IXFR is used. + </para> + + <para> + The <command>edns</command> clause determines whether + the local server will attempt to use EDNS when communicating + with the remote server. The default is <command>yes</command>. + </para> + + <para> + The <command>edns-udp-size</command> option sets the EDNS UDP size + that is advertised by named when querying the remote server. + Valid values are 512 to 4096 bytes (values outside this range will be + silently adjusted). This option is useful when you wish to + advertises a different value to this server than the value you + advertise globally, for example, when there is a firewall at the + remote site that is blocking large replies. + </para> + + <para> + The <command>max-udp-size</command> option sets the + maximum EDNS UDP message size named will send. Valid + values are 512 to 4096 bytes (values outside this range will + be silently adjusted). This option is useful when you + know that there is a firewall that is blocking large + replies from named. + </para> + + <para> + The server supports two zone transfer methods. The first, <command>one-answer</command>, + uses one DNS message per resource record transferred. <command>many-answers</command> packs + as many resource records as possible into a message. <command>many-answers</command> is + more efficient, but is only known to be understood by <acronym>BIND</acronym> 9, <acronym>BIND</acronym> + 8.x, and patched versions of <acronym>BIND</acronym> + 4.9.5. You can specify which method + to use for a server with the <command>transfer-format</command> option. + If <command>transfer-format</command> is not + specified, the <command>transfer-format</command> + specified + by the <command>options</command> statement will be + used. + </para> + + <para><command>transfers</command> + is used to limit the number of concurrent inbound zone + transfers from the specified server. If no + <command>transfers</command> clause is specified, the + limit is set according to the + <command>transfers-per-ns</command> option. + </para> + + <para> + The <command>keys</command> clause identifies a + <command>key_id</command> defined by the <command>key</command> statement, + to be used for transaction security (TSIG, <xref linkend="tsig"/>) + when talking to the remote server. + When a request is sent to the remote server, a request signature + will be generated using the key specified here and appended to the + message. A request originating from the remote server is not + required + to be signed by this key. + </para> + + <para> + Although the grammar of the <command>keys</command> + clause + allows for multiple keys, only a single key per server is + currently + supported. + </para> + + <para> + The <command>transfer-source</command> and + <command>transfer-source-v6</command> clauses specify + the IPv4 and IPv6 source + address to be used for zone transfer with the remote server, + respectively. + For an IPv4 remote server, only <command>transfer-source</command> can + be specified. + Similarly, for an IPv6 remote server, only + <command>transfer-source-v6</command> can be + specified. + For more details, see the description of + <command>transfer-source</command> and + <command>transfer-source-v6</command> in + <xref linkend="zone_transfers"/>. + </para> + + <para> + The <command>notify-source</command> and + <command>notify-source-v6</command> clauses specify the + IPv4 and IPv6 source address to be used for notify + messages sent to remote servers, respectively. For an + IPv4 remote server, only <command>notify-source</command> + can be specified. Similarly, for an IPv6 remote server, + only <command>notify-source-v6</command> can be specified. + </para> + + <para> + The <command>query-source</command> and + <command>query-source-v6</command> clauses specify the + IPv4 and IPv6 source address to be used for queries + sent to remote servers, respectively. For an IPv4 + remote server, only <command>query-source</command> can + be specified. Similarly, for an IPv6 remote server, + only <command>query-source-v6</command> can be specified. + </para> + + </sect2> + + <sect2> + <title><command>trusted-keys</command> Statement Grammar</title> + <programlisting>trusted-keys { <replaceable>string</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; <optional> <replaceable>string</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; <optional>...</optional></optional> }; </programlisting> -</sect2> + </sect2> <sect2> <title><command>trusted-keys</command> Statement Definition and Usage</title> @@ -4607,15 +7902,15 @@ For more details, see the description of key, it is treated as if it had been validated and proven secure. The resolver attempts DNSSEC validation on all DNS data in subdomains of a security root. - </para> - <para> + </para> + <para> All keys (and corresponding zones) listed in <command>trusted-keys</command> are deemed to exist regardless of what parent zones say. Similarly for all keys listed in <command>trusted-keys</command> only those keys are used to validate the DNSKEY RRset. The parent's DS RRset will not be used. - </para> + </para> <para> The <command>trusted-keys</command> statement can contain multiple key entries, each consisting of the key's @@ -4624,71 +7919,114 @@ For more details, see the description of </para> </sect2> -<sect2 id="view_statement_grammar"> -<title><command>view</command> Statement Grammar</title> -<programlisting>view <replaceable>view_name</replaceable> + <sect2 id="view_statement_grammar"> + <title><command>view</command> Statement Grammar</title> + +<programlisting>view <replaceable>view_name</replaceable> <optional><replaceable>class</replaceable></optional> { - match-clients { <replaceable>address_match_list</replaceable> } ; - match-destinations { <replaceable>address_match_list</replaceable> } ; + match-clients { <replaceable>address_match_list</replaceable> }; + match-destinations { <replaceable>address_match_list</replaceable> }; match-recursive-only <replaceable>yes_or_no</replaceable> ; <optional> <replaceable>view_option</replaceable>; ...</optional> <optional> <replaceable>zone_statement</replaceable>; ...</optional> }; -</programlisting></sect2> -<sect2><title><command>view</command> Statement Definition and Usage</title> - -<para>The <command>view</command> statement is a powerful new feature -of <acronym>BIND</acronym> 9 that lets a name server answer a DNS query differently -depending on who is asking. It is particularly useful for implementing -split DNS setups without having to run multiple servers.</para> - -<para>Each <command>view</command> statement defines a view of the -DNS namespace that will be seen by a subset of clients. A client matches -a view if its source IP address matches the -<varname>address_match_list</varname> of the view's -<command>match-clients</command> clause and its destination IP address matches -the <varname>address_match_list</varname> of the view's -<command>match-destinations</command> clause. If not specified, both -<command>match-clients</command> and <command>match-destinations</command> -default to matching all addresses. In addition to checking IP addresses -<command>match-clients</command> and <command>match-destinations</command> -can also take <command>keys</command> which provide an mechanism for the -client to select the view. A view can also be specified -as <command>match-recursive-only</command>, which means that only recursive -requests from matching clients will match that view. -The order of the <command>view</command> statements is significant — -a client request will be resolved in the context of the first -<command>view</command> that it matches.</para> - -<para>Zones defined within a <command>view</command> statement will -be only be accessible to clients that match the <command>view</command>. - By defining a zone of the same name in multiple views, different -zone data can be given to different clients, for example, "internal" -and "external" clients in a split DNS setup.</para> - -<para>Many of the options given in the <command>options</command> statement -can also be used within a <command>view</command> statement, and then -apply only when resolving queries with that view. When no view-specific -value is given, the value in the <command>options</command> statement -is used as a default. Also, zone options can have default values specified -in the <command>view</command> statement; these view-specific defaults -take precedence over those in the <command>options</command> statement.</para> - -<para>Views are class specific. If no class is given, class IN -is assumed. Note that all non-IN views must contain a hint zone, -since only the IN class has compiled-in default hints.</para> - -<para>If there are no <command>view</command> statements in the config -file, a default view that matches any client is automatically created -in class IN. Any <command>zone</command> statements specified on -the top level of the configuration file are considered to be part of -this default view, and the <command>options</command> statement will -apply to the default view. If any explicit <command>view</command> -statements are present, all <command>zone</command> statements must -occur inside <command>view</command> statements.</para> - -<para>Here is an example of a typical split DNS setup implemented -using <command>view</command> statements:</para> +</programlisting> + + </sect2> + <sect2> + <title><command>view</command> Statement Definition and Usage</title> + + <para> + The <command>view</command> statement is a powerful + feature + of <acronym>BIND</acronym> 9 that lets a name server + answer a DNS query differently + depending on who is asking. It is particularly useful for + implementing + split DNS setups without having to run multiple servers. + </para> + + <para> + Each <command>view</command> statement defines a view + of the + DNS namespace that will be seen by a subset of clients. A client + matches + a view if its source IP address matches the + <varname>address_match_list</varname> of the view's + <command>match-clients</command> clause and its + destination IP address matches + the <varname>address_match_list</varname> of the + view's + <command>match-destinations</command> clause. If not + specified, both + <command>match-clients</command> and <command>match-destinations</command> + default to matching all addresses. In addition to checking IP + addresses + <command>match-clients</command> and <command>match-destinations</command> + can also take <command>keys</command> which provide an + mechanism for the + client to select the view. A view can also be specified + as <command>match-recursive-only</command>, which + means that only recursive + requests from matching clients will match that view. + The order of the <command>view</command> statements is + significant — + a client request will be resolved in the context of the first + <command>view</command> that it matches. + </para> + + <para> + Zones defined within a <command>view</command> + statement will + be only be accessible to clients that match the <command>view</command>. + By defining a zone of the same name in multiple views, different + zone data can be given to different clients, for example, + "internal" + and "external" clients in a split DNS setup. + </para> + + <para> + Many of the options given in the <command>options</command> statement + can also be used within a <command>view</command> + statement, and then + apply only when resolving queries with that view. When no + view-specific + value is given, the value in the <command>options</command> statement + is used as a default. Also, zone options can have default values + specified + in the <command>view</command> statement; these + view-specific defaults + take precedence over those in the <command>options</command> statement. + </para> + + <para> + Views are class specific. If no class is given, class IN + is assumed. Note that all non-IN views must contain a hint zone, + since only the IN class has compiled-in default hints. + </para> + + <para> + If there are no <command>view</command> statements in + the config + file, a default view that matches any client is automatically + created + in class IN. Any <command>zone</command> statements + specified on + the top level of the configuration file are considered to be part + of + this default view, and the <command>options</command> + statement will + apply to the default view. If any explicit <command>view</command> + statements are present, all <command>zone</command> + statements must + occur inside <command>view</command> statements. + </para> + + <para> + Here is an example of a typical split DNS setup implemented + using <command>view</command> statements: + </para> + <programlisting>view "internal" { // This should match our internal networks. match-clients { 10.0.0.0/8; }; @@ -4719,19 +8057,27 @@ view "external" { }; }; </programlisting> -</sect2> -<sect2 id="zone_statement_grammar"><title><command>zone</command> -Statement Grammar</title> -<programlisting>zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { + + </sect2> + <sect2 id="zone_statement_grammar"> + <title><command>zone</command> + Statement Grammar</title> + +<programlisting>zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { type master; - <optional> allow-query { <replaceable>address_match_list</replaceable> } ; </optional> - <optional> allow-transfer { <replaceable>address_match_list</replaceable> } ; </optional> - <optional> allow-update { <replaceable>address_match_list</replaceable> } ; </optional> - <optional> update-policy { <replaceable>update_policy_rule</replaceable> <optional>...</optional> } ; </optional> + <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional> + <optional> allow-transfer { <replaceable>address_match_list</replaceable> }; </optional> + <optional> allow-update { <replaceable>address_match_list</replaceable> }; </optional> + <optional> update-policy { <replaceable>update_policy_rule</replaceable> <optional>...</optional> }; </optional> <optional> also-notify { <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> <optional> check-names (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional> + <optional> check-mx (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional> + <optional> check-wildcard <replaceable>yes_or_no</replaceable>; </optional> + <optional> check-integrity <replaceable>yes_or_no</replaceable> ; </optional> <optional> dialup <replaceable>dialup_option</replaceable> ; </optional> <optional> file <replaceable>string</replaceable> ; </optional> + <optional> masterfile-format (<constant>text</constant>|<constant>raw</constant>) ; </optional> + <optional> journal <replaceable>string</replaceable> ; </optional> <optional> forward (<constant>only</constant>|<constant>first</constant>) ; </optional> <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> <optional> ixfr-base <replaceable>string</replaceable> ; </optional> @@ -4740,7 +8086,8 @@ Statement Grammar</title> <optional> max-ixfr-log-size <replaceable>number</replaceable> ; </optional> <optional> max-transfer-idle-out <replaceable>number</replaceable> ; </optional> <optional> max-transfer-time-out <replaceable>number</replaceable> ; </optional> - <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable> ; </optional> + <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable> | <replaceable>master-only</replaceable> ; </optional> + <optional> notify-delay <replaceable>seconds</replaceable> ; </optional> <optional> pubkey <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; </optional> <optional> notify-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> <optional> notify-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> @@ -4752,30 +8099,34 @@ Statement Grammar</title> <optional> min-retry-time <replaceable>number</replaceable> ; </optional> <optional> max-retry-time <replaceable>number</replaceable> ; </optional> <optional> key-directory <replaceable>path_name</replaceable>; </optional> + <optional> zero-no-soa-ttl <replaceable>yes_or_no</replaceable> ; </optional> }; -zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { +zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { type slave; - <optional> allow-notify { <replaceable>address_match_list</replaceable> } ; </optional> - <optional> allow-query { <replaceable>address_match_list</replaceable> } ; </optional> - <optional> allow-transfer { <replaceable>address_match_list</replaceable> } ; </optional> - <optional> allow-update-forwarding { <replaceable>address_match_list</replaceable> } ; </optional> + <optional> allow-notify { <replaceable>address_match_list</replaceable> }; </optional> + <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional> + <optional> allow-transfer { <replaceable>address_match_list</replaceable> }; </optional> + <optional> allow-update-forwarding { <replaceable>address_match_list</replaceable> }; </optional> + <optional> update-check-ksk <replaceable>yes_or_no</replaceable>; </optional> <optional> also-notify { <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> <optional> check-names (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional> <optional> dialup <replaceable>dialup_option</replaceable> ; </optional> <optional> file <replaceable>string</replaceable> ; </optional> + <optional> masterfile-format (<constant>text</constant>|<constant>raw</constant>) ; </optional> + <optional> journal <replaceable>string</replaceable> ; </optional> <optional> forward (<constant>only</constant>|<constant>first</constant>) ; </optional> <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> <optional> ixfr-base <replaceable>string</replaceable> ; </optional> <optional> ixfr-tmp-file <replaceable>string</replaceable> ; </optional> <optional> maintain-ixfr-base <replaceable>yes_or_no</replaceable> ; </optional> - <optional> masters <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> | <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> } ; </optional> + <optional> masters <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> | <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> }; </optional> <optional> max-ixfr-log-size <replaceable>number</replaceable> ; </optional> <optional> max-transfer-idle-in <replaceable>number</replaceable> ; </optional> <optional> max-transfer-idle-out <replaceable>number</replaceable> ; </optional> <optional> max-transfer-time-in <replaceable>number</replaceable> ; </optional> <optional> max-transfer-time-out <replaceable>number</replaceable> ; </optional> - <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable> ; </optional> + <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable> | <replaceable>master-only</replaceable> ; </optional> <optional> pubkey <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; </optional> <optional> transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> <optional> transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> @@ -4791,25 +8142,27 @@ zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replacea <optional> min-retry-time <replaceable>number</replaceable> ; </optional> <optional> max-retry-time <replaceable>number</replaceable> ; </optional> <optional> multi-master <replaceable>yes_or_no</replaceable> ; </optional> + <optional> zero-no-soa-ttl <replaceable>yes_or_no</replaceable> ; </optional> }; -zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { +zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { type hint; - <optional> file <replaceable>string</replaceable> ; </optional> + file <replaceable>string</replaceable> ; <optional> delegation-only <replaceable>yes_or_no</replaceable> ; </optional> <optional> check-names (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; // Not Implemented. </optional> }; -zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { +zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { type stub; - <optional> allow-query { <replaceable>address_match_list</replaceable> } ; </optional> + <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional> <optional> check-names (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional> <optional> dialup <replaceable>dialup_option</replaceable> ; </optional> <optional> delegation-only <replaceable>yes_or_no</replaceable> ; </optional> <optional> file <replaceable>string</replaceable> ; </optional> + <optional> masterfile-format (<constant>text</constant>|<constant>raw</constant>) ; </optional> <optional> forward (<constant>only</constant>|<constant>first</constant>) ; </optional> <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> - <optional> masters <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> | <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> } ; </optional> + <optional> masters <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> | <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> }; </optional> <optional> max-transfer-idle-in <replaceable>number</replaceable> ; </optional> <optional> max-transfer-time-in <replaceable>number</replaceable> ; </optional> <optional> pubkey <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; </optional> @@ -4819,7 +8172,6 @@ zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replacea <optional> alt-transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional> <optional> use-alt-transfer-source <replaceable>yes_or_no</replaceable>; </optional> <optional> zone-statistics <replaceable>yes_or_no</replaceable> ; </optional> - <optional> sig-validity-interval <replaceable>number</replaceable> ; </optional> <optional> database <replaceable>string</replaceable> ; </optional> <optional> min-refresh-time <replaceable>number</replaceable> ; </optional> <optional> max-refresh-time <replaceable>number</replaceable> ; </optional> @@ -4828,1013 +8180,2268 @@ zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replacea <optional> multi-master <replaceable>yes_or_no</replaceable> ; </optional> }; -zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { +zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { type forward; <optional> forward (<constant>only</constant>|<constant>first</constant>) ; </optional> <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional> <optional> delegation-only <replaceable>yes_or_no</replaceable> ; </optional> }; -zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { +zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> { type delegation-only; }; + </programlisting> -</sect2> -<sect2><title><command>zone</command> Statement Definition and Usage</title> -<sect3><title>Zone Types</title> -<informaltable colsep = "0" rowsep = "0"> -<tgroup cols = "2" colsep = "0" rowsep = "0" - tgroupstyle = "3Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.908in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "4.217in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><varname>master</varname></para></entry> -<entry colname = "2"><para>The server has a master copy of the data -for the zone and will be able to provide authoritative answers for -it.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>slave</varname></para></entry> -<entry colname = "2"><para>A slave zone is a replica of a master -zone. The <command>masters</command> list specifies one or more IP addresses -of master servers that the slave contacts to update its copy of the zone. -Masters list elements can also be names of other masters lists. -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. -Authentication to the master can also be done with per-server TSIG keys. -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 startup and eliminates -a needless waste of bandwidth. Note that for large numbers (in the -tens or hundreds of thousands) of zones per server, it is best to -use a two-level naming scheme for zone file names. For example, -a slave server for the zone <literal>example.com</literal> might place -the zone contents into a file called -<filename>ex/example.com</filename> where <filename>ex/</filename> is -just the first two letters of the zone name. (Most operating systems -behave very slowly if you put 100 000 files into -a single directory.)</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>stub</varname></para></entry> -<entry colname = "2"><para>A stub zone is similar to a slave zone, -except that it replicates only the NS records of a master zone instead -of the entire zone. Stub zones are not a standard part of the DNS; -they are a feature specific to the <acronym>BIND</acronym> implementation. -</para> - -<para>Stub zones can be used to eliminate the need for glue NS record -in a parent zone at the expense of maintaining a stub zone entry and -a set of name server addresses in <filename>named.conf</filename>. -This usage is not recommended for new configurations, and BIND 9 -supports it only in a limited way. -In <acronym>BIND</acronym> 4/8, zone transfers of a parent zone -included the NS records from stub children of that zone. This meant -that, in some cases, users could get away with configuring child stubs -only in the master server for the parent zone. <acronym>BIND</acronym> -9 never mixes together zone data from different zones in this -way. Therefore, if a <acronym>BIND</acronym> 9 master serving a parent -zone has child stub zones configured, all the slave servers for the -parent zone also need to have the same child stub zones -configured.</para> - -<para>Stub zones can also be used as a way of forcing the resolution -of a given domain to use a particular set of authoritative servers. -For example, the caching name servers on a private network using -RFC1918 addressing may be configured with stub zones for -<literal>10.in-addr.arpa</literal> -to use a set of internal name servers as the authoritative -servers for that domain.</para> -</entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>forward</varname></para></entry> -<entry colname = "2"><para>A "forward zone" is a way to configure -forwarding on a per-domain basis. A <command>zone</command> statement -of type <command>forward</command> can contain a <command>forward</command> and/or <command>forwarders</command> statement, -which will apply to queries within the domain given by the zone -name. If no <command>forwarders</command> statement is present or -an empty list for <command>forwarders</command> is given, then no -forwarding will be done for the domain, canceling the effects of -any forwarders in the <command>options</command> statement. Thus -if you want to use this type of zone to change the behavior of the -global <command>forward</command> option (that is, "forward first" -to, then "forward only", or vice versa, but want to use the same -servers as set globally) you need to re-specify the global forwarders.</para> -</entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>hint</varname></para></entry> -<entry colname = "2"><para>The initial set of root name servers is -specified using a "hint zone". When the server starts up, it uses -the root hints to find a root name server and get the most recent -list of root name servers. If no hint zone is specified for class -IN, the server uses a compiled-in default set of root servers hints. -Classes other than IN have no built-in defaults hints.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>delegation-only</varname></para></entry> -<entry colname = "2"><para>This is used to enforce the delegation-only -status of infrastructure zones (e.g. COM, NET, ORG). Any answer that -is received without an explicit or implicit delegation in the authority -section will be treated as NXDOMAIN. This does not apply to the zone -apex. This should not be applied to leaf zones.</para> -<para><varname>delegation-only</varname> has no effect on answers received -from forwarders.</para></entry> -</row> -</tbody> -</tgroup></informaltable></sect3> - -<sect3><title>Class</title> -<para>The zone's name may optionally be followed by a class. If -a class is not specified, class <literal>IN</literal> (for <varname>Internet</varname>), -is assumed. This is correct for the vast majority of cases.</para> -<para>The <literal>hesiod</literal> class is -named for an information service from MIT's Project Athena. It is -used to share information about various systems databases, such -as users, groups, printers and so on. The keyword -<literal>HS</literal> is -a synonym for hesiod.</para> -<para>Another MIT development is CHAOSnet, a LAN protocol created -in the mid-1970s. Zone data for it can be specified with the <literal>CHAOS</literal> class.</para></sect3> -<sect3> - -<title>Zone Options</title> - -<variablelist> - -<varlistentry><term><command>allow-notify</command></term> -<listitem><para>See the description of -<command>allow-notify</command> in <xref linkend="access_control"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>allow-query</command></term> -<listitem><para>See the description of -<command>allow-query</command> in <xref linkend="access_control"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>allow-transfer</command></term> -<listitem><para>See the description of <command>allow-transfer</command> -in <xref linkend="access_control"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>allow-update</command></term> -<listitem><para>Specifies which hosts are allowed to -submit Dynamic DNS updates for master zones. The default is to deny -updates from all hosts. Note that allowing updates based -on the requestor's IP address is insecure; see -<xref linkend="dynamic_update_security"/> for details. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>update-policy</command></term> -<listitem><para>Specifies a "Simple Secure Update" policy. See -<xref linkend="dynamic_update_policies"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>allow-update-forwarding</command></term> -<listitem><para>See the description of <command>allow-update-forwarding</command> -in <xref linkend="access_control"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>also-notify</command></term> -<listitem><para>Only meaningful if <command>notify</command> is -active for this zone. The set of machines that will receive a -<literal>DNS NOTIFY</literal> message -for this zone is made up of all the listed name servers (other than -the primary master) for the zone plus any IP addresses specified -with <command>also-notify</command>. A port may be specified -with each <command>also-notify</command> address to send the notify -messages to a port other than the default of 53. -<command>also-notify</command> is not meaningful for stub zones. -The default is the empty list.</para> -</listitem></varlistentry> - -<varlistentry><term><command>check-names</command></term> -<listitem><para> -This option is used to restrict the character set and syntax of -certain domain names in master files and/or DNS responses received from the -network. The default varies according to zone type. For <command>master</command> zones the default is <command>fail</command>. For <command>slave</command> -zones the default is <command>warn</command>. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>database</command></term> -<listitem><para>Specify the type of database to be used for storing the -zone data. The string following the <command>database</command> keyword -is interpreted as a list of whitespace-delimited words. The first word -identifies the database type, and any subsequent words are passed -as arguments to the database to be interpreted in a way specific -to the database type.</para> -<para>The default is <userinput>"rbt"</userinput>, BIND 9's native in-memory -red-black-tree database. This database does not take arguments.</para> -<para>Other values are possible if additional database drivers -have been linked into the server. Some sample drivers are included -with the distribution but none are linked in by default.</para> -</listitem></varlistentry> - -<varlistentry><term><command>dialup</command></term> -<listitem><para>See the description of -<command>dialup</command> in <xref linkend="boolean_options"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>delegation-only</command></term> -<listitem><para>The flag only applies to hint and stub zones. If set -to <userinput>yes</userinput>, then the zone will also be treated as if it -is also a delegation-only type zone. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>forward</command></term> -<listitem><para>Only meaningful if the zone has a forwarders -list. The <command>only</command> value causes the lookup to fail -after trying the forwarders and getting no answer, while <command>first</command> would -allow a normal lookup to be tried.</para> -</listitem></varlistentry> - -<varlistentry><term><command>forwarders</command></term> -<listitem><para>Used to override the list of global forwarders. -If it is not specified in a zone of type <command>forward</command>, -no forwarding is done for the zone and the global options are not used.</para> -</listitem></varlistentry> - -<varlistentry><term><command>ixfr-base</command></term> -<listitem><para>Was used in <acronym>BIND</acronym> 8 to specify the name -of the transaction log (journal) file for dynamic update and IXFR. -<acronym>BIND</acronym> 9 ignores the option and constructs the name of the journal -file by appending "<filename>.jnl</filename>" to the name of the -zone file.</para> -</listitem></varlistentry> - -<varlistentry><term><command>ixfr-tmp-file</command></term> -<listitem><para>Was an undocumented option in <acronym>BIND</acronym> 8. -Ignored in <acronym>BIND</acronym> 9.</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-transfer-time-in</command></term> -<listitem><para>See the description of -<command>max-transfer-time-in</command> in <xref linkend="zone_transfers"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-transfer-idle-in</command></term> -<listitem><para>See the description of -<command>max-transfer-idle-in</command> in <xref linkend="zone_transfers"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-transfer-time-out</command></term> -<listitem><para>See the description of -<command>max-transfer-time-out</command> in <xref linkend="zone_transfers"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>max-transfer-idle-out</command></term> -<listitem><para>See the description of -<command>max-transfer-idle-out</command> in <xref linkend="zone_transfers"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>notify</command></term> -<listitem><para>See the description of -<command>notify</command> in <xref linkend="boolean_options"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>pubkey</command></term> -<listitem><para>In <acronym>BIND</acronym> 8, this option was intended for specifying -a public zone key for verification of signatures in DNSSEC signed -zones when they are loaded from disk. <acronym>BIND</acronym> 9 does not verify signatures -on load and ignores the option.</para> -</listitem></varlistentry> - -<varlistentry><term><command>zone-statistics</command></term> -<listitem><para>If <userinput>yes</userinput>, the server will keep statistical -information for this zone, which can be dumped to the -<command>statistics-file</command> defined in the server options.</para> -</listitem></varlistentry> - -<varlistentry><term><command>sig-validity-interval</command></term> -<listitem><para>See the description of -<command>sig-validity-interval</command> in <xref linkend="tuning"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>transfer-source</command></term> -<listitem><para>See the description of -<command>transfer-source</command> in <xref linkend="zone_transfers"/>. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>transfer-source-v6</command></term> -<listitem><para>See the description of -<command>transfer-source-v6</command> in <xref linkend="zone_transfers"/>. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>alt-transfer-source</command></term> -<listitem><para>See the description of -<command>alt-transfer-source</command> in <xref linkend="zone_transfers"/>. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>alt-transfer-source-v6</command></term> -<listitem><para>See the description of -<command>alt-transfer-source-v6</command> in <xref linkend="zone_transfers"/>. -</para> -</listitem></varlistentry> - -<varlistentry><term><command>use-alt-transfer-source</command></term> -<listitem><para>See the description of -<command>use-alt-transfer-source</command> in <xref linkend="zone_transfers"/>. -</para> -</listitem></varlistentry> - - -<varlistentry><term><command>notify-source</command></term> -<listitem><para>See the description of -<command>notify-source</command> in <xref linkend="zone_transfers"/> -</para> -</listitem></varlistentry> - -<varlistentry><term><command>notify-source-v6</command></term> -<listitem><para>See the description of -<command>notify-source-v6</command> in <xref linkend="zone_transfers"/>. -</para> -</listitem></varlistentry> - -<varlistentry> -<term><command>min-refresh-time</command></term> -<term><command>max-refresh-time</command></term> -<term><command>min-retry-time</command></term> -<term><command>max-retry-time</command></term> -<listitem><para> -See the description in <xref linkend="tuning"/>. -</para></listitem></varlistentry> - -<varlistentry><term><command>ixfr-from-differences</command></term> -<listitem><para>See the description of -<command>ixfr-from-differences</command> in <xref linkend="boolean_options"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>key-directory</command></term> -<listitem><para>See the description of -<command>key-directory</command> in <xref linkend="options"/>.</para> -</listitem></varlistentry> - -<varlistentry><term><command>multi-master</command></term> -<listitem><para>See the description of -<command>multi-master</command> in <xref linkend="boolean_options"/>.</para> -</listitem></varlistentry> - -</variablelist> - -</sect3> -<sect3 id="dynamic_update_policies"><title>Dynamic Update Policies</title> -<para><acronym>BIND</acronym> 9 supports two alternative methods of granting clients -the right to perform dynamic updates to a zone, -configured by the <command>allow-update</command> and -<command>update-policy</command> option, respectively.</para> -<para>The <command>allow-update</command> clause works the same -way as in previous versions of <acronym>BIND</acronym>. It grants given clients the -permission to update any record of any name in the zone.</para> -<para>The <command>update-policy</command> clause is new in <acronym>BIND</acronym> -9 and allows more fine-grained control over what updates are allowed. -A set of rules is specified, where each rule either grants or denies -permissions for one or more names to be updated by one or more identities. - If the dynamic update request message is signed (that is, it includes -either a TSIG or SIG(0) record), the identity of the signer can -be determined.</para> -<para>Rules are specified in the <command>update-policy</command> zone -option, and are only meaningful for master zones. When the <command>update-policy</command> statement -is present, it is a configuration error for the <command>allow-update</command> statement -to be present. The <command>update-policy</command> statement only -examines the signer of a message; the source address is not relevant.</para> -<para>This is how a rule definition looks:</para> + + </sect2> + <sect2> + <title><command>zone</command> Statement Definition and Usage</title> + <sect3> + <title>Zone Types</title> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table"> + <!--colspec colname="1" colnum="1" colsep="0" colwidth="1.108in"/--> + <!--colspec colname="2" colnum="2" colsep="0" colwidth="4.017in"/--> + <colspec colname="1" colnum="1" colsep="0"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="4.017in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>master</varname> + </para> + </entry> + <entry colname="2"> + <para> + The server has a master copy of the data + for the zone and will be able to provide authoritative + answers for + it. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>slave</varname> + </para> + </entry> + <entry colname="2"> + <para> + A slave zone is a replica of a master + zone. The <command>masters</command> list + specifies one or more IP addresses + of master servers that the slave contacts to update + its copy of the zone. + Masters list elements can also be names of other + masters lists. + 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. + Authentication to the master can also be done with + per-server TSIG keys. + 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 startup and + eliminates + a needless waste of bandwidth. Note that for large + numbers (in the + tens or hundreds of thousands) of zones per server, it + is best to + use a two-level naming scheme for zone filenames. For + example, + a slave server for the zone <literal>example.com</literal> might place + the zone contents into a file called + <filename>ex/example.com</filename> where <filename>ex/</filename> is + just the first two letters of the zone name. (Most + operating systems + behave very slowly if you put 100 000 files into + a single directory.) + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>stub</varname> + </para> + </entry> + <entry colname="2"> + <para> + A stub zone is similar to a slave zone, + except that it replicates only the NS records of a + master zone instead + of the entire zone. Stub zones are not a standard part + of the DNS; + they are a feature specific to the <acronym>BIND</acronym> implementation. + </para> + + <para> + Stub zones can be used to eliminate the need for glue + NS record + in a parent zone at the expense of maintaining a stub + zone entry and + a set of name server addresses in <filename>named.conf</filename>. + This usage is not recommended for new configurations, + and BIND 9 + supports it only in a limited way. + In <acronym>BIND</acronym> 4/8, zone + transfers of a parent zone + included the NS records from stub children of that + zone. This meant + that, in some cases, users could get away with + configuring child stubs + only in the master server for the parent zone. <acronym>BIND</acronym> + 9 never mixes together zone data from different zones + in this + way. Therefore, if a <acronym>BIND</acronym> 9 master serving a parent + zone has child stub zones configured, all the slave + servers for the + parent zone also need to have the same child stub + zones + configured. + </para> + + <para> + Stub zones can also be used as a way of forcing the + resolution + of a given domain to use a particular set of + authoritative servers. + For example, the caching name servers on a private + network using + RFC1918 addressing may be configured with stub zones + for + <literal>10.in-addr.arpa</literal> + to use a set of internal name servers as the + authoritative + servers for that domain. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>forward</varname> + </para> + </entry> + <entry colname="2"> + <para> + A "forward zone" is a way to configure + forwarding on a per-domain basis. A <command>zone</command> statement + of type <command>forward</command> can + contain a <command>forward</command> + and/or <command>forwarders</command> + statement, + which will apply to queries within the domain given by + the zone + name. If no <command>forwarders</command> + statement is present or + an empty list for <command>forwarders</command> is given, then no + forwarding will be done for the domain, canceling the + effects of + any forwarders in the <command>options</command> statement. Thus + if you want to use this type of zone to change the + behavior of the + global <command>forward</command> option + (that is, "forward first" + to, then "forward only", or vice versa, but want to + use the same + servers as set globally) you need to re-specify the + global forwarders. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>hint</varname> + </para> + </entry> + <entry colname="2"> + <para> + The initial set of root name servers is + specified using a "hint zone". When the server starts + up, it uses + the root hints to find a root name server and get the + most recent + list of root name servers. If no hint zone is + specified for class + IN, the server uses a compiled-in default set of root + servers hints. + Classes other than IN have no built-in defaults hints. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>delegation-only</varname> + </para> + </entry> + <entry colname="2"> + <para> + This is used to enforce the delegation-only + status of infrastructure zones (e.g. COM, NET, ORG). + Any answer that + is received without an explicit or implicit delegation + in the authority + section will be treated as NXDOMAIN. This does not + apply to the zone + apex. This should not be applied to leaf zones. + </para> + <para> + <varname>delegation-only</varname> has no + effect on answers received + from forwarders. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + </sect3> + + <sect3> + <title>Class</title> + <para> + The zone's name may optionally be followed by a class. If + a class is not specified, class <literal>IN</literal> (for <varname>Internet</varname>), + is assumed. This is correct for the vast majority of cases. + </para> + <para> + The <literal>hesiod</literal> class is + named for an information service from MIT's Project Athena. It + is + used to share information about various systems databases, such + as users, groups, printers and so on. The keyword + <literal>HS</literal> is + a synonym for hesiod. + </para> + <para> + Another MIT development is Chaosnet, a LAN protocol created + in the mid-1970s. Zone data for it can be specified with the <literal>CHAOS</literal> class. + </para> + </sect3> + <sect3> + + <title>Zone Options</title> + + <variablelist> + + <varlistentry> + <term><command>allow-notify</command></term> + <listitem> + <para> + See the description of + <command>allow-notify</command> in <xref linkend="access_control"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-query</command></term> + <listitem> + <para> + See the description of + <command>allow-query</command> in <xref linkend="access_control"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-transfer</command></term> + <listitem> + <para> + See the description of <command>allow-transfer</command> + in <xref linkend="access_control"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-update</command></term> + <listitem> + <para> + See the description of <command>allow-update</command> + in <xref linkend="access_control"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>update-policy</command></term> + <listitem> + <para> + Specifies a "Simple Secure Update" policy. See + <xref linkend="dynamic_update_policies"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>allow-update-forwarding</command></term> + <listitem> + <para> + See the description of <command>allow-update-forwarding</command> + in <xref linkend="access_control"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>also-notify</command></term> + <listitem> + <para> + Only meaningful if <command>notify</command> + is + active for this zone. The set of machines that will + receive a + <literal>DNS NOTIFY</literal> message + for this zone is made up of all the listed name servers + (other than + the primary master) for the zone plus any IP addresses + specified + with <command>also-notify</command>. A port + may be specified + with each <command>also-notify</command> + address to send the notify + messages to a port other than the default of 53. + <command>also-notify</command> is not + meaningful for stub zones. + The default is the empty list. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-names</command></term> + <listitem> + <para> + This option is used to restrict the character set and + syntax of + certain domain names in master files and/or DNS responses + received from the + network. The default varies according to zone type. For <command>master</command> zones the default is <command>fail</command>. For <command>slave</command> + zones the default is <command>warn</command>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-mx</command></term> + <listitem> + <para> + See the description of + <command>check-mx</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-wildcard</command></term> + <listitem> + <para> + See the description of + <command>check-wildcard</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-integrity</command></term> + <listitem> + <para> + See the description of + <command>check-integrity</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>check-sibling</command></term> + <listitem> + <para> + See the description of + <command>check-sibling</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>zero-no-soa-ttl</command></term> + <listitem> + <para> + See the description of + <command>zero-no-soa-ttl</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>update-check-ksk</command></term> + <listitem> + <para> + See the description of + <command>update-check-ksk</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>database</command></term> + <listitem> + <para> + Specify the type of database to be used for storing the + zone data. The string following the <command>database</command> keyword + is interpreted as a list of whitespace-delimited words. + The first word + identifies the database type, and any subsequent words are + passed + as arguments to the database to be interpreted in a way + specific + to the database type. + </para> + <para> + The default is <userinput>"rbt"</userinput>, BIND 9's + native in-memory + red-black-tree database. This database does not take + arguments. + </para> + <para> + Other values are possible if additional database drivers + have been linked into the server. Some sample drivers are + included + with the distribution but none are linked in by default. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>dialup</command></term> + <listitem> + <para> + See the description of + <command>dialup</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>delegation-only</command></term> + <listitem> + <para> + The flag only applies to hint and stub zones. If set + to <userinput>yes</userinput>, then the zone will also be + treated as if it + is also a delegation-only type zone. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>forward</command></term> + <listitem> + <para> + Only meaningful if the zone has a forwarders + list. The <command>only</command> value causes + the lookup to fail + after trying the forwarders and getting no answer, while <command>first</command> would + allow a normal lookup to be tried. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>forwarders</command></term> + <listitem> + <para> + Used to override the list of global forwarders. + If it is not specified in a zone of type <command>forward</command>, + no forwarding is done for the zone and the global options are + not used. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>ixfr-base</command></term> + <listitem> + <para> + Was used in <acronym>BIND</acronym> 8 to + specify the name + of the transaction log (journal) file for dynamic update + and IXFR. + <acronym>BIND</acronym> 9 ignores the option + and constructs the name of the journal + file by appending "<filename>.jnl</filename>" + to the name of the + zone file. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>ixfr-tmp-file</command></term> + <listitem> + <para> + Was an undocumented option in <acronym>BIND</acronym> 8. + Ignored in <acronym>BIND</acronym> 9. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>journal</command></term> + <listitem> + <para> + Allow the default journal's filename to be overridden. + The default is the zone's filename with "<filename>.jnl</filename>" appended. + This is applicable to <command>master</command> and <command>slave</command> zones. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-transfer-time-in</command></term> + <listitem> + <para> + See the description of + <command>max-transfer-time-in</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-transfer-idle-in</command></term> + <listitem> + <para> + See the description of + <command>max-transfer-idle-in</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-transfer-time-out</command></term> + <listitem> + <para> + See the description of + <command>max-transfer-time-out</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>max-transfer-idle-out</command></term> + <listitem> + <para> + See the description of + <command>max-transfer-idle-out</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>notify</command></term> + <listitem> + <para> + See the description of + <command>notify</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>notify-delay</command></term> + <listitem> + <para> + See the description of + <command>notify-delay</command> in <xref linkend="tuning"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>pubkey</command></term> + <listitem> + <para> + In <acronym>BIND</acronym> 8, this option was + intended for specifying + a public zone key for verification of signatures in DNSSEC + signed + zones when they are loaded from disk. <acronym>BIND</acronym> 9 does not verify signatures + on load and ignores the option. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>zone-statistics</command></term> + <listitem> + <para> + If <userinput>yes</userinput>, the server will keep + statistical + information for this zone, which can be dumped to the + <command>statistics-file</command> defined in + the server options. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>sig-validity-interval</command></term> + <listitem> + <para> + See the description of + <command>sig-validity-interval</command> in <xref linkend="tuning"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>transfer-source</command></term> + <listitem> + <para> + See the description of + <command>transfer-source</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>transfer-source-v6</command></term> + <listitem> + <para> + See the description of + <command>transfer-source-v6</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>alt-transfer-source</command></term> + <listitem> + <para> + See the description of + <command>alt-transfer-source</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>alt-transfer-source-v6</command></term> + <listitem> + <para> + See the description of + <command>alt-transfer-source-v6</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>use-alt-transfer-source</command></term> + <listitem> + <para> + See the description of + <command>use-alt-transfer-source</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + + <varlistentry> + <term><command>notify-source</command></term> + <listitem> + <para> + See the description of + <command>notify-source</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>notify-source-v6</command></term> + <listitem> + <para> + See the description of + <command>notify-source-v6</command> in <xref linkend="zone_transfers"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>min-refresh-time</command></term> + <term><command>max-refresh-time</command></term> + <term><command>min-retry-time</command></term> + <term><command>max-retry-time</command></term> + <listitem> + <para> + See the description in <xref linkend="tuning"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>ixfr-from-differences</command></term> + <listitem> + <para> + See the description of + <command>ixfr-from-differences</command> in <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>key-directory</command></term> + <listitem> + <para> + See the description of + <command>key-directory</command> in <xref linkend="options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>multi-master</command></term> + <listitem> + <para> + See the description of <command>multi-master</command> in + <xref linkend="boolean_options"/>. + </para> + </listitem> + </varlistentry> + + <varlistentry> + <term><command>masterfile-format</command></term> + <listitem> + <para> + See the description of <command>masterfile-format</command> + in <xref linkend="tuning"/>. + </para> + </listitem> + </varlistentry> + + </variablelist> + + </sect3> + <sect3 id="dynamic_update_policies"> + <title>Dynamic Update Policies</title> + <para> + <acronym>BIND</acronym> 9 supports two alternative + methods of granting clients + the right to perform dynamic updates to a zone, + configured by the <command>allow-update</command> + and + <command>update-policy</command> option, + respectively. + </para> + <para> + The <command>allow-update</command> clause works the + same + way as in previous versions of <acronym>BIND</acronym>. It grants given clients the + permission to update any record of any name in the zone. + </para> + <para> + The <command>update-policy</command> clause is new + in <acronym>BIND</acronym> + 9 and allows more fine-grained control over what updates are + allowed. + A set of rules is specified, where each rule either grants or + denies + permissions for one or more names to be updated by one or more + identities. + If the dynamic update request message is signed (that is, it + includes + either a TSIG or SIG(0) record), the identity of the signer can + be determined. + </para> + <para> + Rules are specified in the <command>update-policy</command> zone + option, and are only meaningful for master zones. When the <command>update-policy</command> statement + is present, it is a configuration error for the <command>allow-update</command> statement + to be present. The <command>update-policy</command> + statement only + examines the signer of a message; the source address is not + relevant. + </para> + <para> + This is how a rule definition looks: + </para> + <programlisting> ( <command>grant</command> | <command>deny</command> ) <replaceable>identity</replaceable> <replaceable>nametype</replaceable> <replaceable>name</replaceable> <optional> <replaceable>types</replaceable> </optional> </programlisting> -<para>Each rule grants or denies privileges. Once a message has -successfully matched a rule, the operation is immediately granted -or denied and no further rules are examined. A rule is matched -when the signer matches the identity field, the name matches the -name field in accordance with the nametype field, and the type matches -the types specified in the type field.</para> - -<para>The identity field specifies a name or a wildcard name. Normally, this -is the name of the TSIG or SIG(0) key used to sign the update request. When a -TKEY exchange has been used to create a shared secret, the identity of the -shared secret is the same as the identity of the key used to authenticate the -TKEY exchange. When the <replaceable>identity</replaceable> field specifies a -wildcard name, it is subject to DNS wildcard expansion, so the rule will apply -to multiple identities. The <replaceable>identity</replaceable> field must -contain a fully qualified domain name.</para> - -<para>The <replaceable>nametype</replaceable> field has 4 values: -<varname>name</varname>, <varname>subdomain</varname>, -<varname>wildcard</varname>, and <varname>self</varname>. -</para> -<informaltable> - <tgroup cols = "2" colsep = "0" - rowsep = "0" tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.819in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.681in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><varname>name</varname></para></entry> -<entry colname = "2"><para>Exact-match semantics. This rule matches when the -name being updated is identical to the contents of the -<replaceable>name</replaceable> field.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>subdomain</varname></para></entry> -<entry colname = "2"><para>This rule matches when the name being updated -is a subdomain of, or identical to, the contents of the -<replaceable>name</replaceable> field.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>wildcard</varname></para></entry> -<entry colname = "2"><para>The <replaceable>name</replaceable> field is -subject to DNS wildcard expansion, and this rule matches when the name -being updated name is a valid expansion of the wildcard.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><varname>self</varname></para></entry> -<entry colname = "2"><para>This rule matches when the name being updated -matches the contents of the <replaceable>identity</replaceable> field. -The <replaceable>name</replaceable> field is ignored, but should be -the same as the <replaceable>identity</replaceable> field. The -<varname>self</varname> nametype is most useful when allowing using -one key per name to update, where the key has the same name as the name -to be updated. The <replaceable>identity</replaceable> would be -specified as <constant>*</constant> in this case.</para></entry> -</row> -</tbody> -</tgroup></informaltable> - -<para>In all cases, the <replaceable>name</replaceable> field must -specify a fully qualified domain name.</para> - -<para>If no types are explicitly specified, this rule matches all types except -SIG, NS, SOA, and NXT. Types may be specified by name, including -"ANY" (ANY matches all types except NXT, which can never be updated). -Note that when an attempt is made to delete all records associated with a -name, the rules are checked for each existing record type. -</para> - </sect3> - </sect2> - </sect1> - <sect1> - <title>Zone File</title> - <sect2 id="types_of_resource_records_and_when_to_use_them"> - <title>Types of Resource Records and When to Use Them</title> -<para>This section, largely borrowed from RFC 1034, describes the -concept of a Resource Record (RR) and explains when each is used. -Since the publication of RFC 1034, several new RRs have been identified -and implemented in the DNS. These are also included.</para> - <sect3> - <title>Resource Records</title> - - <para>A domain name identifies a node. Each node has a set of - resource information, which may be empty. The set of resource - information associated with a particular name is composed of - separate RRs. The order of RRs in a set is not significant and - need not be preserved by name servers, resolvers, or other - parts of the DNS. However, sorting of multiple RRs is - permitted for optimization purposes, for example, to specify - that a particular nearby server be tried first. See <xref - linkend="the_sortlist_statement"/> and <xref - linkend="rrset_ordering"/>.</para> - -<para>The components of a Resource Record are:</para> -<informaltable colsep = "0" - rowsep = "0"><tgroup cols = "2" colsep = "0" - rowsep = "0" tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.000in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.500in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para>owner name</para></entry> -<entry colname = "2"><para>the domain name where the RR is found.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>type</para></entry> -<entry colname = "2"><para>an encoded 16-bit value that specifies -the type of the resource record.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>TTL</para></entry> -<entry colname = "2"><para>the time-to-live of the RR. This field -is a 32-bit integer in units of seconds, and is primarily used by -resolvers when they cache RRs. The TTL describes how long a RR can -be cached before it should be discarded.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>class</para></entry> -<entry colname = "2"><para>an encoded 16-bit value that identifies -a protocol family or instance of a protocol.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>RDATA</para></entry> -<entry colname = "2"><para>the resource data. The format of the -data is type (and sometimes class) specific.</para></entry> -</row> -</tbody> -</tgroup></informaltable> -<para>The following are <emphasis>types</emphasis> of valid RRs:</para> -<informaltable colsep = "0" - rowsep = "0"><tgroup cols = "2" colsep = "0" - rowsep = "0" tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.875in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.625in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para>A</para></entry> -<entry colname = "2"><para>a host address. In the IN class, this is a -32-bit IP address. Described in RFC 1035.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>AAAA</para></entry> -<entry colname = "2"><para>IPv6 address. Described in RFC 1886.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>A6</para></entry> -<entry colname = "2"><para>IPv6 address. This can be a partial -address (a suffix) and an indirection to the name where the rest of the -address (the prefix) can be found. Experimental. Described in RFC 2874.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>AFSDB</para></entry> -<entry colname = "2"><para>location of AFS database servers. -Experimental. Described in RFC 1183.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>APL</para></entry> -<entry colname = "2"><para>address prefix list. Experimental. -Described in RFC 3123.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>CERT</para></entry> -<entry colname = "2"><para>holds a digital certificate. -Described in RFC 2538.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>CNAME</para></entry> -<entry colname = "2"><para>identifies the canonical name of an alias. -Described in RFC 1035.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>DNAME</para></entry> -<entry colname = "2"><para>Replaces the domain name specified with -another name to be looked up, effectively aliasing an entire -subtree of the domain name space rather than a single record -as in the case of the CNAME RR. -Described in RFC 2672.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>GPOS</para></entry> -<entry colname = "2"><para>Specifies the global position. Superseded by LOC.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>HINFO</para></entry> -<entry colname = "2"><para>identifies the CPU and OS used by a host. -Described in RFC 1035.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>ISDN</para></entry> -<entry colname = "2"><para>representation of ISDN addresses. -Experimental. Described in RFC 1183.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>KEY</para></entry> -<entry colname = "2"><para>stores a public key associated with a -DNS name. Described in RFC 2535.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>KX</para></entry> -<entry colname = "2"><para>identifies a key exchanger for this -DNS name. Described in RFC 2230.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>LOC</para></entry> -<entry colname = "2"><para>for storing GPS info. Described in RFC 1876. -Experimental.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>MX</para></entry> -<entry colname = "2"><para>identifies a mail exchange for the domain. -A 16-bit preference value (lower is better) -followed by the host name of the mail exchange. -Described in RFC 974, RFC 1035.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>NAPTR</para></entry> -<entry colname = "2"><para>name authority pointer. Described in RFC 2915.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>NSAP</para></entry> -<entry colname = "2"><para>a network service access point. -Described in RFC 1706.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>NS</para></entry> -<entry colname = "2"><para>the authoritative name server for the -domain. Described in RFC 1035.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>NXT</para></entry> -<entry colname = "2"><para>used in DNSSEC to securely indicate that -RRs with an owner name in a certain name interval do not exist in -a zone and indicate what RR types are present for an existing name. -Described in RFC 2535.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>PTR</para></entry> -<entry colname = "2"><para>a pointer to another part of the domain -name space. Described in RFC 1035.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>PX</para></entry> -<entry colname = "2"><para>provides mappings between RFC 822 and X.400 -addresses. Described in RFC 2163.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>RP</para></entry> -<entry colname = "2"><para>information on persons responsible -for the domain. Experimental. Described in RFC 1183.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>RT</para></entry> -<entry colname = "2"><para>route-through binding for hosts that -do not have their own direct wide area network addresses. -Experimental. Described in RFC 1183.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>SIG</para></entry> -<entry colname = "2"><para>("signature") contains data authenticated -in the secure DNS. Described in RFC 2535.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>SOA</para></entry> -<entry colname = "2"><para>identifies the start of a zone of authority. -Described in RFC 1035.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>SRV</para></entry> -<entry colname = "2"><para>information about well known network -services (replaces WKS). Described in RFC 2782.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>TXT</para></entry> -<entry colname = "2"><para>text records. Described in RFC 1035.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>WKS</para></entry> -<entry colname = "2"><para>information about which well known -network services, such as SMTP, that a domain supports. Historical. -</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>X25</para></entry> -<entry colname = "2"><para>representation of X.25 network addresses. -Experimental. Described in RFC 1183.</para></entry> -</row> -</tbody> -</tgroup></informaltable> -<para>The following <emphasis>classes</emphasis> of resource records -are currently valid in the DNS:</para><informaltable colsep = "0" - rowsep = "0"><tgroup cols = "2" colsep = "0" rowsep = "0" - tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.875in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "3.625in"/> -<tbody> - -<row rowsep = "0"> -<entry colname = "1"><para>IN</para></entry> -<entry colname = "2"><para>The Internet.</para></entry> -</row> - -<row rowsep = "0"> -<entry colname = "1"><para>CH</para></entry> -<entry colname = "2"><para> -CHAOSnet, a LAN protocol created at MIT in the mid-1970s. -Rarely used for its historical purpose, but reused for BIND's -built-in server information zones, e.g., -<literal>version.bind</literal>. -</para></entry> -</row> - -<row rowsep = "0"> -<entry colname = "1"><para>HS</para></entry> -<entry colname = "2"><para> -Hesiod, an information service -developed by MIT's Project Athena. It is used to share information -about various systems databases, such as users, groups, printers -and so on. -</para></entry> -</row> - -</tbody> -</tgroup></informaltable> - -<para>The owner name is often implicit, rather than forming an integral -part of the RR. For example, many name servers internally form tree -or hash structures for the name space, and chain RRs off nodes. - The remaining RR parts are the fixed header (type, class, TTL) -which is consistent for all RRs, and a variable part (RDATA) that -fits the needs of the resource being described.</para> -<para>The meaning of the TTL field is a time limit on how long an -RR can be kept in a cache. This limit does not apply to authoritative -data in zones; it is also timed out, but by the refreshing policies -for the zone. The TTL is assigned by the administrator for the -zone where the data originates. While short TTLs can be used to -minimize caching, and a zero TTL prohibits caching, the realities -of Internet performance suggest that these times should be on the -order of days for the typical host. If a change can be anticipated, -the TTL can be reduced prior to the change to minimize inconsistency -during the change, and then increased back to its former value following -the change.</para> -<para>The data in the RDATA section of RRs is carried as a combination -of binary strings and domain names. The domain names are frequently -used as "pointers" to other data in the DNS.</para></sect3> -<sect3><title>Textual expression of RRs</title> -<para>RRs are represented in binary form in the packets of the DNS -protocol, and are usually represented in highly encoded form when -stored in a name server or resolver. In the examples provided in -RFC 1034, a style similar to that used in master files was employed -in order to show the contents of RRs. In this format, most RRs -are shown on a single line, although continuation lines are possible -using parentheses.</para> -<para>The start of the line gives the owner of the RR. If a line -begins with a blank, then the owner is assumed to be the same as -that of the previous RR. Blank lines are often included for readability.</para> -<para>Following the owner, we list the TTL, type, and class of the -RR. Class and type use the mnemonics defined above, and TTL is -an integer before the type field. In order to avoid ambiguity in -parsing, type and class mnemonics are disjoint, TTLs are integers, -and the type mnemonic is always last. The IN class and TTL values -are often omitted from examples in the interests of clarity.</para> -<para>The resource data or RDATA section of the RR are given using -knowledge of the typical representation for the data.</para> -<para>For example, we might show the RRs carried in a message as:</para> <informaltable - colsep = "0" rowsep = "0"><tgroup cols = "3" - colsep = "0" rowsep = "0" tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.381in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "1.020in"/> -<colspec colname = "3" colnum = "3" colsep = "0" colwidth = "2.099in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><literal>ISI.EDU.</literal></para></entry> -<entry colname = "2"><para><literal>MX</literal></para></entry> -<entry colname = "3"><para><literal>10 VENERA.ISI.EDU.</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para><literal>MX</literal></para></entry> -<entry colname = "3"><para><literal>10 VAXA.ISI.EDU</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><literal>VENERA.ISI.EDU</literal></para></entry> -<entry colname = "2"><para><literal>A</literal></para></entry> -<entry colname = "3"><para><literal>128.9.0.32</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para><literal>A</literal></para></entry> -<entry colname = "3"><para><literal>10.1.0.52</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><literal>VAXA.ISI.EDU</literal></para></entry> -<entry colname = "2"><para><literal>A</literal></para></entry> -<entry colname = "3"><para><literal>10.2.0.27</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para><literal>A</literal></para></entry> -<entry colname = "3"><para><literal>128.9.0.33</literal></para></entry> -</row> -</tbody> -</tgroup></informaltable> -<para>The MX RRs have an RDATA section which consists of a 16-bit -number followed by a domain name. The address RRs use a standard -IP address format to contain a 32-bit internet address.</para> -<para>The above example shows six RRs, with two RRs at each of three -domain names.</para> -<para>Similarly we might see:</para><informaltable colsep = "0" - rowsep = "0"><tgroup cols = "3" colsep = "0" rowsep = "0" - tgroupstyle = "4Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.491in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "1.067in"/> -<colspec colname = "3" colnum = "3" colsep = "0" colwidth = "2.067in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><literal>XX.LCS.MIT.EDU. IN</literal></para></entry> -<entry colname = "2"><para><literal>A</literal></para></entry> -<entry colname = "3"><para><literal>10.0.0.44</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><literal>CH</literal></para></entry> -<entry colname = "2"><para><literal>A</literal></para></entry> -<entry colname = "3"><para><literal>MIT.EDU. 2420</literal></para></entry> -</row> -</tbody> -</tgroup></informaltable> -<para>This example shows two addresses for <literal>XX.LCS.MIT.EDU</literal>, -each of a different class.</para></sect3></sect2> - -<sect2><title>Discussion of MX Records</title> - -<para>As described above, domain servers store information as a -series of resource records, each of which contains a particular -piece of information about a given domain name (which is usually, -but not always, a host). The simplest way to think of a RR is as -a typed pair of data, a domain name matched with a relevant datum, -and stored with some additional type information to help systems -determine when the RR is relevant.</para> - -<para>MX records are used to control delivery of email. The data -specified in the record is a priority and a domain name. The priority -controls the order in which email delivery is attempted, with the -lowest number first. If two priorities are the same, a server is -chosen randomly. If no servers at a given priority are responding, -the mail transport agent will fall back to the next largest priority. -Priority numbers do not have any absolute meaning — they are relevant -only respective to other MX records for that domain name. The domain -name given is the machine to which the mail will be delivered. It <emphasis>must</emphasis> have -an associated A record — CNAME is not sufficient.</para> -<para>For a given domain, if there is both a CNAME record and an -MX record, the MX record is in error, and will be ignored. Instead, -the mail will be delivered to the server specified in the MX record -pointed to by the CNAME.</para> -<informaltable colsep = "0" rowsep = "0"><tgroup cols = "5" - colsep = "0" rowsep = "0" tgroupstyle = "3Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.708in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "0.444in"/> -<colspec colname = "3" colnum = "3" colsep = "0" colwidth = "0.444in"/> -<colspec colname = "4" colnum = "4" colsep = "0" colwidth = "0.976in"/> -<colspec colname = "5" colnum = "5" colsep = "0" colwidth = "1.553in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><literal>example.com.</literal></para></entry> -<entry colname = "2"><para><literal>IN</literal></para></entry> -<entry colname = "3"><para><literal>MX</literal></para></entry> -<entry colname = "4"><para><literal>10</literal></para></entry> -<entry colname = "5"><para><literal>mail.example.com.</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para><literal>IN</literal></para></entry> -<entry colname = "3"><para><literal>MX</literal></para></entry> -<entry colname = "4"><para><literal>10</literal></para></entry> -<entry colname = "5"><para><literal>mail2.example.com.</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para><literal>IN</literal></para></entry> -<entry colname = "3"><para><literal>MX</literal></para></entry> -<entry colname = "4"><para><literal>20</literal></para></entry> -<entry colname = "5"><para><literal>mail.backup.org.</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><literal>mail.example.com.</literal></para></entry> -<entry colname = "2"><para><literal>IN</literal></para></entry> -<entry colname = "3"><para><literal>A</literal></para></entry> -<entry colname = "4"><para><literal>10.0.0.1</literal></para></entry> -<entry colname = "5"><para></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><literal>mail2.example.com.</literal></para></entry> -<entry colname = "2"><para><literal>IN</literal></para></entry> -<entry colname = "3"><para><literal>A</literal></para></entry> -<entry colname = "4"><para><literal>10.0.0.2</literal></para></entry> -<entry colname = "5"><para></para></entry> -</row> -</tbody> -</tgroup></informaltable><para>For example:</para> -<para>Mail delivery will be attempted to <literal>mail.example.com</literal> and -<literal>mail2.example.com</literal> (in -any order), and if neither of those succeed, delivery to <literal>mail.backup.org</literal> will -be attempted.</para></sect2> -<sect2 id="Setting_TTLs"><title>Setting TTLs</title> -<para>The time-to-live of the RR field is a 32-bit integer represented -in units of seconds, and is primarily used by resolvers when they -cache RRs. The TTL describes how long a RR can be cached before it -should be discarded. The following three types of TTL are currently -used in a zone file.</para> -<informaltable colsep = "0" rowsep = "0"><tgroup cols = "2" - colsep = "0" rowsep = "0" tgroupstyle = "3Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.750in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "4.375in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para>SOA</para></entry> -<entry colname = "2"><para>The last field in the SOA is the negative -caching TTL. This controls how long other servers will cache no-such-domain -(NXDOMAIN) responses from you.</para><para>The maximum time for -negative caching is 3 hours (3h).</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>$TTL</para></entry> -<entry colname = "2"><para>The $TTL directive at the top of the -zone file (before the SOA) gives a default TTL for every RR without -a specific TTL set.</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>RR TTLs</para></entry> -<entry colname = "2"><para>Each RR can have a TTL as the second -field in the RR, which will control how long other servers can cache -the it.</para></entry> -</row> -</tbody> -</tgroup></informaltable> -<para>All of these TTLs default to units of seconds, though units -can be explicitly specified, for example, <literal>1h30m</literal>. </para></sect2> -<sect2><title>Inverse Mapping in IPv4</title> -<para>Reverse name resolution (that is, translation from IP address -to name) is achieved by means of the <emphasis>in-addr.arpa</emphasis> domain -and PTR records. Entries in the in-addr.arpa domain are made in -least-to-most significant order, read left to right. This is the -opposite order to the way IP addresses are usually written. Thus, -a machine with an IP address of 10.1.2.3 would have a corresponding -in-addr.arpa name of -3.2.1.10.in-addr.arpa. This name should have a PTR resource record -whose data field is the name of the machine or, optionally, multiple -PTR records if the machine has more than one name. For example, -in the <optional>example.com</optional> domain:</para> -<informaltable colsep = "0" rowsep = "0"> -<tgroup cols = "2" colsep = "0" rowsep = "0" - tgroupstyle = "3Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.125in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "4.000in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para><literal>$ORIGIN</literal></para></entry> -<entry colname = "2"><para><literal>2.1.10.in-addr.arpa</literal></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para><literal>3</literal></para></entry> -<entry colname = "2"><para><literal>IN PTR foo.example.com.</literal></para></entry> -</row> -</tbody> -</tgroup></informaltable> - <note> -<para>The <command>$ORIGIN</command> lines in the examples -are for providing context to the examples only-they do not necessarily -appear in the actual usage. They are only used here to indicate -that the example is relative to the listed origin.</para></note></sect2> -<sect2><title>Other Zone File Directives</title> -<para>The Master File Format was initially defined in RFC 1035 and -has subsequently been extended. While the Master File Format itself -is class independent all records in a Master File must be of the same -class.</para> -<para>Master File Directives include <command>$ORIGIN</command>, <command>$INCLUDE</command>, -and <command>$TTL.</command></para> -<sect3><title>The <command>$ORIGIN</command> Directive</title> -<para>Syntax: <command>$ORIGIN -</command><replaceable>domain-name</replaceable> <optional> <replaceable>comment</replaceable></optional></para> -<para><command>$ORIGIN</command> sets the domain name that will -be appended to any unqualified records. When a zone is first read -in there is an implicit <command>$ORIGIN</command> <<varname>zone-name</varname>><command>.</command> The -current <command>$ORIGIN</command> is appended to the domain specified -in the <command>$ORIGIN</command> argument if it is not absolute.</para> -<programlisting>$ORIGIN example.com. -WWW CNAME MAIN-SERVER</programlisting> -<para>is equivalent to</para> -<programlisting>WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.</programlisting></sect3> -<sect3><title>The <command>$INCLUDE</command> Directive</title> -<para>Syntax: <command>$INCLUDE</command> -<replaceable>filename</replaceable> <optional> -<replaceable>origin</replaceable> </optional> <optional> <replaceable>comment</replaceable> </optional></para> -<para>Read and process the file <filename>filename</filename> as -if it were included into the file at this point. If <command>origin</command> is -specified the file is processed with <command>$ORIGIN</command> set -to that value, otherwise the current <command>$ORIGIN</command> is -used.</para> -<para>The origin and the current domain name -revert to the values they had prior to the <command>$INCLUDE</command> once -the file has been read.</para> -<note><para> -RFC 1035 specifies that the current origin should be restored after -an <command>$INCLUDE</command>, but it is silent on whether the current -domain name should also be restored. BIND 9 restores both of them. -This could be construed as a deviation from RFC 1035, a feature, or both. -</para></note> -</sect3> -<sect3><title>The <command>$TTL</command> Directive</title> -<para>Syntax: <command>$TTL</command> -<replaceable>default-ttl</replaceable> <optional> -<replaceable>comment</replaceable> </optional></para> -<para>Set the default Time To Live (TTL) for subsequent records -with undefined TTLs. Valid TTLs are of the range 0-2147483647 seconds.</para> -<para><command>$TTL</command> is defined in RFC 2308.</para></sect3></sect2> -<sect2><title><acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive</title> - <para>Syntax: <command>$GENERATE</command> <replaceable>range</replaceable> <replaceable>lhs</replaceable> <optional><replaceable>ttl</replaceable></optional> <optional><replaceable>class</replaceable></optional> <replaceable>type</replaceable> <replaceable>rhs</replaceable> <optional> <replaceable>comment</replaceable> </optional></para> -<para><command>$GENERATE</command> is used to create a series of -resource records that only differ from each other by an iterator. <command>$GENERATE</command> 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.</para> + + <para> + Each rule grants or denies privileges. Once a message has + successfully matched a rule, the operation is immediately + granted + or denied and no further rules are examined. A rule is matched + when the signer matches the identity field, the name matches the + name field in accordance with the nametype field, and the type + matches + the types specified in the type field. + </para> + + <para> + The identity field specifies a name or a wildcard name. + Normally, this + is the name of the TSIG or SIG(0) key used to sign the update + request. When a + TKEY exchange has been used to create a shared secret, the + identity of the + shared secret is the same as the identity of the key used to + authenticate the + TKEY exchange. When the <replaceable>identity</replaceable> field specifies a + wildcard name, it is subject to DNS wildcard expansion, so the + rule will apply + to multiple identities. The <replaceable>identity</replaceable> field must + contain a fully-qualified domain name. + </para> + + <para> + The <replaceable>nametype</replaceable> field has 6 + values: + <varname>name</varname>, <varname>subdomain</varname>, + <varname>wildcard</varname>, <varname>self</varname>, + <varname>selfsub</varname>, and <varname>selfwild</varname>. + </para> + <informaltable> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="0.819in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.681in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>name</varname> + </para> + </entry> <entry colname="2"> + <para> + Exact-match semantics. This rule matches + when the name being updated is identical + to the contents of the + <replaceable>name</replaceable> field. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>subdomain</varname> + </para> + </entry> <entry colname="2"> + <para> + This rule matches when the name being updated + is a subdomain of, or identical to, the + contents of the <replaceable>name</replaceable> + field. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>wildcard</varname> + </para> + </entry> <entry colname="2"> + <para> + The <replaceable>name</replaceable> field + is subject to DNS wildcard expansion, and + this rule matches when the name being updated + name is a valid expansion of the wildcard. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>self</varname> + </para> + </entry> + <entry colname="2"> + <para> + This rule matches when the name being updated + matches the contents of the + <replaceable>identity</replaceable> field. + The <replaceable>name</replaceable> field + is ignored, but should be the same as the + <replaceable>identity</replaceable> field. + The <varname>self</varname> nametype is + most useful when allowing using one key per + name to update, where the key has the same + name as the name to be updated. The + <replaceable>identity</replaceable> would + be specified as <constant>*</constant> (an asterisk) in + this case. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>selfsub</varname> + </para> + </entry> <entry colname="2"> + <para> + This rule is similar to <varname>self</varname> + except that subdomains of <varname>self</varname> + can also be updated. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <varname>selfwild</varname> + </para> + </entry> <entry colname="2"> + <para> + This rule is similar to <varname>self</varname> + except that only subdomains of + <varname>self</varname> can be updated. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + + <para> + In all cases, the <replaceable>name</replaceable> + field must + specify a fully-qualified domain name. + </para> + + <para> + If no types are explicitly specified, this rule matches all + types except + RRSIG, NS, SOA, and NSEC. Types may be specified by name, including + "ANY" (ANY matches all types except NSEC, which can never be + updated). + Note that when an attempt is made to delete all records + associated with a + name, the rules are checked for each existing record type. + </para> + </sect3> + </sect2> + </sect1> + <sect1> + <title>Zone File</title> + <sect2 id="types_of_resource_records_and_when_to_use_them"> + <title>Types of Resource Records and When to Use Them</title> + <para> + This section, largely borrowed from RFC 1034, describes the + concept of a Resource Record (RR) and explains when each is used. + Since the publication of RFC 1034, several new RRs have been + identified + and implemented in the DNS. These are also included. + </para> + <sect3> + <title>Resource Records</title> + + <para> + A domain name identifies a node. Each node has a set of + resource information, which may be empty. The set of resource + information associated with a particular name is composed of + separate RRs. The order of RRs in a set is not significant and + need not be preserved by name servers, resolvers, or other + parts of the DNS. However, sorting of multiple RRs is + permitted for optimization purposes, for example, to specify + that a particular nearby server be tried first. See <xref linkend="the_sortlist_statement"/> and <xref linkend="rrset_ordering"/>. + </para> + + <para> + The components of a Resource Record are: + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.000in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.500in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + owner name + </para> + </entry> + <entry colname="2"> + <para> + The domain name where the RR is found. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + type + </para> + </entry> + <entry colname="2"> + <para> + An encoded 16-bit value that specifies + the type of the resource record. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + TTL + </para> + </entry> + <entry colname="2"> + <para> + The time-to-live of the RR. This field + is a 32-bit integer in units of seconds, and is + primarily used by + resolvers when they cache RRs. The TTL describes how + long a RR can + be cached before it should be discarded. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + class + </para> + </entry> + <entry colname="2"> + <para> + An encoded 16-bit value that identifies + a protocol family or instance of a protocol. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + RDATA + </para> + </entry> + <entry colname="2"> + <para> + The resource data. The format of the + data is type (and sometimes class) specific. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + The following are <emphasis>types</emphasis> of valid RRs: + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="0.875in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.625in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + A + </para> + </entry> + <entry colname="2"> + <para> + A host address. In the IN class, this is a + 32-bit IP address. Described in RFC 1035. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + AAAA + </para> + </entry> + <entry colname="2"> + <para> + IPv6 address. Described in RFC 1886. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + A6 + </para> + </entry> + <entry colname="2"> + <para> + IPv6 address. This can be a partial + address (a suffix) and an indirection to the name + where the rest of the + address (the prefix) can be found. Experimental. + Described in RFC 2874. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + AFSDB + </para> + </entry> + <entry colname="2"> + <para> + Location of AFS database servers. + Experimental. Described in RFC 1183. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + APL + </para> + </entry> + <entry colname="2"> + <para> + Address prefix list. Experimental. + Described in RFC 3123. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + CERT + </para> + </entry> + <entry colname="2"> + <para> + Holds a digital certificate. + Described in RFC 2538. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + CNAME + </para> + </entry> + <entry colname="2"> + <para> + Identifies the canonical name of an alias. + Described in RFC 1035. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + DNAME + </para> + </entry> + <entry colname="2"> + <para> + Replaces the domain name specified with + another name to be looked up, effectively aliasing an + entire + subtree of the domain name space rather than a single + record + as in the case of the CNAME RR. + Described in RFC 2672. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + DNSKEY + </para> + </entry> + <entry colname="2"> + <para> + Stores a public key associated with a signed + DNS zone. Described in RFC 4034. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + DS + </para> + </entry> + <entry colname="2"> + <para> + Stores the hash of a public key associated with a + signed DNS zone. Described in RFC 4034. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + GPOS + </para> + </entry> + <entry colname="2"> + <para> + Specifies the global position. Superseded by LOC. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + HINFO + </para> + </entry> + <entry colname="2"> + <para> + Identifies the CPU and OS used by a host. + Described in RFC 1035. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + ISDN + </para> + </entry> + <entry colname="2"> + <para> + Representation of ISDN addresses. + Experimental. Described in RFC 1183. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + KEY + </para> + </entry> + <entry colname="2"> + <para> + Stores a public key associated with a + DNS name. Used in original DNSSEC; replaced + by DNSKEY in DNSSECbis, but still used with + SIG(0). Described in RFCs 2535 and 2931. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + KX + </para> + </entry> + <entry colname="2"> + <para> + Identifies a key exchanger for this + DNS name. Described in RFC 2230. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + LOC + </para> + </entry> + <entry colname="2"> + <para> + For storing GPS info. Described in RFC 1876. + Experimental. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + MX + </para> + </entry> + <entry colname="2"> + <para> + Identifies a mail exchange for the domain with + a 16-bit preference value (lower is better) + followed by the host name of the mail exchange. + Described in RFC 974, RFC 1035. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + NAPTR + </para> + </entry> + <entry colname="2"> + <para> + Name authority pointer. Described in RFC 2915. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + NSAP + </para> + </entry> + <entry colname="2"> + <para> + A network service access point. + Described in RFC 1706. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + NS + </para> + </entry> + <entry colname="2"> + <para> + The authoritative name server for the + domain. Described in RFC 1035. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + NSEC + </para> + </entry> + <entry colname="2"> + <para> + Used in DNSSECbis to securely indicate that + RRs with an owner name in a certain name interval do + not exist in + a zone and indicate what RR types are present for an + existing name. + Described in RFC 4034. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + NXT + </para> + </entry> + <entry colname="2"> + <para> + Used in DNSSEC to securely indicate that + RRs with an owner name in a certain name interval do + not exist in + a zone and indicate what RR types are present for an + existing name. + Used in original DNSSEC; replaced by NSEC in + DNSSECbis. + Described in RFC 2535. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + PTR + </para> + </entry> + <entry colname="2"> + <para> + A pointer to another part of the domain + name space. Described in RFC 1035. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + PX + </para> + </entry> + <entry colname="2"> + <para> + Provides mappings between RFC 822 and X.400 + addresses. Described in RFC 2163. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + RP + </para> + </entry> + <entry colname="2"> + <para> + Information on persons responsible + for the domain. Experimental. Described in RFC 1183. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + RRSIG + </para> + </entry> + <entry colname="2"> + <para> + Contains DNSSECbis signature data. Described + in RFC 4034. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + RT + </para> + </entry> + <entry colname="2"> + <para> + Route-through binding for hosts that + do not have their own direct wide area network + addresses. + Experimental. Described in RFC 1183. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + SIG + </para> + </entry> + <entry colname="2"> + <para> + Contains DNSSEC signature data. Used in + original DNSSEC; replaced by RRSIG in + DNSSECbis, but still used for SIG(0). + Described in RFCs 2535 and 2931. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + SOA + </para> + </entry> + <entry colname="2"> + <para> + Identifies the start of a zone of authority. + Described in RFC 1035. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + SRV + </para> + </entry> + <entry colname="2"> + <para> + Information about well known network + services (replaces WKS). Described in RFC 2782. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + TXT + </para> + </entry> + <entry colname="2"> + <para> + Text records. Described in RFC 1035. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + WKS + </para> + </entry> + <entry colname="2"> + <para> + Information about which well known + network services, such as SMTP, that a domain + supports. Historical. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + X25 + </para> + </entry> + <entry colname="2"> + <para> + Representation of X.25 network addresses. + Experimental. Described in RFC 1183. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + The following <emphasis>classes</emphasis> of resource records + are currently valid in the DNS: + </para> + <informaltable colsep="0" rowsep="0"><tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="0.875in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="3.625in"/> + <tbody> + + <row rowsep="0"> + <entry colname="1"> + <para> + IN + </para> + </entry> + <entry colname="2"> + <para> + The Internet. + </para> + </entry> + </row> + + <row rowsep="0"> + <entry colname="1"> + <para> + CH + </para> + </entry> + <entry colname="2"> + <para> + Chaosnet, a LAN protocol created at MIT in the + mid-1970s. + Rarely used for its historical purpose, but reused for + BIND's + built-in server information zones, e.g., + <literal>version.bind</literal>. + </para> + </entry> + </row> + + <row rowsep="0"> + <entry colname="1"> + <para> + HS + </para> + </entry> + <entry colname="2"> + <para> + Hesiod, an information service + developed by MIT's Project Athena. It is used to share + information + about various systems databases, such as users, + groups, printers + and so on. + </para> + </entry> + </row> + + </tbody> + </tgroup> + </informaltable> + + <para> + The owner name is often implicit, rather than forming an + integral + part of the RR. For example, many name servers internally form + tree + or hash structures for the name space, and chain RRs off nodes. + The remaining RR parts are the fixed header (type, class, TTL) + which is consistent for all RRs, and a variable part (RDATA) + that + fits the needs of the resource being described. + </para> + <para> + The meaning of the TTL field is a time limit on how long an + RR can be kept in a cache. This limit does not apply to + authoritative + data in zones; it is also timed out, but by the refreshing + policies + for the zone. The TTL is assigned by the administrator for the + zone where the data originates. While short TTLs can be used to + minimize caching, and a zero TTL prohibits caching, the + realities + of Internet performance suggest that these times should be on + the + order of days for the typical host. If a change can be + anticipated, + the TTL can be reduced prior to the change to minimize + inconsistency + during the change, and then increased back to its former value + following + the change. + </para> + <para> + The data in the RDATA section of RRs is carried as a combination + of binary strings and domain names. The domain names are + frequently + used as "pointers" to other data in the DNS. + </para> + </sect3> + <sect3> + <title>Textual expression of RRs</title> + <para> + RRs are represented in binary form in the packets of the DNS + protocol, and are usually represented in highly encoded form + when + stored in a name server or resolver. In the examples provided + in + RFC 1034, a style similar to that used in master files was + employed + in order to show the contents of RRs. In this format, most RRs + are shown on a single line, although continuation lines are + possible + using parentheses. + </para> + <para> + The start of the line gives the owner of the RR. If a line + begins with a blank, then the owner is assumed to be the same as + that of the previous RR. Blank lines are often included for + readability. + </para> + <para> + Following the owner, we list the TTL, type, and class of the + RR. Class and type use the mnemonics defined above, and TTL is + an integer before the type field. In order to avoid ambiguity + in + parsing, type and class mnemonics are disjoint, TTLs are + integers, + and the type mnemonic is always last. The IN class and TTL + values + are often omitted from examples in the interests of clarity. + </para> + <para> + The resource data or RDATA section of the RR are given using + knowledge of the typical representation for the data. + </para> + <para> + For example, we might show the RRs carried in a message as: + </para> + <informaltable colsep="0" rowsep="0"><tgroup cols="3" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.381in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="1.020in"/> + <colspec colname="3" colnum="3" colsep="0" colwidth="2.099in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>ISI.EDU.</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>MX</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>10 VENERA.ISI.EDU.</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para/> + </entry> + <entry colname="2"> + <para> + <literal>MX</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>10 VAXA.ISI.EDU</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>VENERA.ISI.EDU</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>128.9.0.32</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para/> + </entry> + <entry colname="2"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>10.1.0.52</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>VAXA.ISI.EDU</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>10.2.0.27</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para/> + </entry> + <entry colname="2"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>128.9.0.33</literal> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + The MX RRs have an RDATA section which consists of a 16-bit + number followed by a domain name. The address RRs use a + standard + IP address format to contain a 32-bit internet address. + </para> + <para> + The above example shows six RRs, with two RRs at each of three + domain names. + </para> + <para> + Similarly we might see: + </para> + <informaltable colsep="0" rowsep="0"><tgroup cols="3" colsep="0" rowsep="0" tgroupstyle="4Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.491in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="1.067in"/> + <colspec colname="3" colnum="3" colsep="0" colwidth="2.067in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>XX.LCS.MIT.EDU.</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>IN A</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>10.0.0.44</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"/> + <entry colname="2"> + <para> + <literal>CH A</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>MIT.EDU. 2420</literal> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + This example shows two addresses for + <literal>XX.LCS.MIT.EDU</literal>, each of a different class. + </para> + </sect3> + </sect2> + + <sect2> + <title>Discussion of MX Records</title> + + <para> + As described above, domain servers store information as a + series of resource records, each of which contains a particular + piece of information about a given domain name (which is usually, + but not always, a host). The simplest way to think of a RR is as + a typed pair of data, a domain name matched with a relevant datum, + and stored with some additional type information to help systems + determine when the RR is relevant. + </para> + + <para> + MX records are used to control delivery of email. The data + specified in the record is a priority and a domain name. The + priority + controls the order in which email delivery is attempted, with the + lowest number first. If two priorities are the same, a server is + chosen randomly. If no servers at a given priority are responding, + the mail transport agent will fall back to the next largest + priority. + Priority numbers do not have any absolute meaning — they are + relevant + only respective to other MX records for that domain name. The + domain + name given is the machine to which the mail will be delivered. + It <emphasis>must</emphasis> have an associated address record + (A or AAAA) — CNAME is not sufficient. + </para> + <para> + For a given domain, if there is both a CNAME record and an + MX record, the MX record is in error, and will be ignored. + Instead, + the mail will be delivered to the server specified in the MX + record + pointed to by the CNAME. + </para> + <para> + For example: + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="5" colsep="0" rowsep="0" tgroupstyle="3Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.708in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="0.444in"/> + <colspec colname="3" colnum="3" colsep="0" colwidth="0.444in"/> + <colspec colname="4" colnum="4" colsep="0" colwidth="0.976in"/> + <colspec colname="5" colnum="5" colsep="0" colwidth="1.553in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>example.com.</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>IN</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>MX</literal> + </para> + </entry> + <entry colname="4"> + <para> + <literal>10</literal> + </para> + </entry> + <entry colname="5"> + <para> + <literal>mail.example.com.</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para/> + </entry> + <entry colname="2"> + <para> + <literal>IN</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>MX</literal> + </para> + </entry> + <entry colname="4"> + <para> + <literal>10</literal> + </para> + </entry> + <entry colname="5"> + <para> + <literal>mail2.example.com.</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para/> + </entry> + <entry colname="2"> + <para> + <literal>IN</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>MX</literal> + </para> + </entry> + <entry colname="4"> + <para> + <literal>20</literal> + </para> + </entry> + <entry colname="5"> + <para> + <literal>mail.backup.org.</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>mail.example.com.</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>IN</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="4"> + <para> + <literal>10.0.0.1</literal> + </para> + </entry> + <entry colname="5"> + <para/> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>mail2.example.com.</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>IN</literal> + </para> + </entry> + <entry colname="3"> + <para> + <literal>A</literal> + </para> + </entry> + <entry colname="4"> + <para> + <literal>10.0.0.2</literal> + </para> + </entry> + <entry colname="5"> + <para/> + </entry> + </row> + </tbody> + </tgroup> + </informaltable><para> + Mail delivery will be attempted to <literal>mail.example.com</literal> and + <literal>mail2.example.com</literal> (in + any order), and if neither of those succeed, delivery to <literal>mail.backup.org</literal> will + be attempted. + </para> + </sect2> + <sect2 id="Setting_TTLs"> + <title>Setting TTLs</title> + <para> + The time-to-live of the RR field is a 32-bit integer represented + in units of seconds, and is primarily used by resolvers when they + cache RRs. The TTL describes how long a RR can be cached before it + should be discarded. The following three types of TTL are + currently + used in a zone file. + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="0.750in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="4.375in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + SOA + </para> + </entry> + <entry colname="2"> + <para> + The last field in the SOA is the negative + caching TTL. This controls how long other servers will + cache no-such-domain + (NXDOMAIN) responses from you. + </para> + <para> + The maximum time for + negative caching is 3 hours (3h). + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + $TTL + </para> + </entry> + <entry colname="2"> + <para> + The $TTL directive at the top of the + zone file (before the SOA) gives a default TTL for every + RR without + a specific TTL set. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + RR TTLs + </para> + </entry> + <entry colname="2"> + <para> + Each RR can have a TTL as the second + field in the RR, which will control how long other + servers can cache + the it. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + All of these TTLs default to units of seconds, though units + can be explicitly specified, for example, <literal>1h30m</literal>. + </para> + </sect2> + <sect2> + <title>Inverse Mapping in IPv4</title> + <para> + Reverse name resolution (that is, translation from IP address + to name) is achieved by means of the <emphasis>in-addr.arpa</emphasis> domain + and PTR records. Entries in the in-addr.arpa domain are made in + least-to-most significant order, read left to right. This is the + opposite order to the way IP addresses are usually written. Thus, + a machine with an IP address of 10.1.2.3 would have a + corresponding + in-addr.arpa name of + 3.2.1.10.in-addr.arpa. This name should have a PTR resource record + whose data field is the name of the machine or, optionally, + multiple + PTR records if the machine has more than one name. For example, + in the <optional>example.com</optional> domain: + </para> + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="1.125in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="4.000in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>$ORIGIN</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>2.1.10.in-addr.arpa</literal> + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para> + <literal>3</literal> + </para> + </entry> + <entry colname="2"> + <para> + <literal>IN PTR foo.example.com.</literal> + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <note> + <para> + The <command>$ORIGIN</command> lines in the examples + are for providing context to the examples only — they do not + necessarily + appear in the actual usage. They are only used here to indicate + that the example is relative to the listed origin. + </para> + </note> + </sect2> + <sect2> + <title>Other Zone File Directives</title> + <para> + The Master File Format was initially defined in RFC 1035 and + has subsequently been extended. While the Master File Format + itself + is class independent all records in a Master File must be of the + same + class. + </para> + <para> + Master File Directives include <command>$ORIGIN</command>, <command>$INCLUDE</command>, + and <command>$TTL.</command> + </para> + <sect3> + <title>The <command>$ORIGIN</command> Directive</title> + <para> + Syntax: <command>$ORIGIN</command> + <replaceable>domain-name</replaceable> + <optional><replaceable>comment</replaceable></optional> + </para> + <para><command>$ORIGIN</command> + sets the domain name that will be appended to any + unqualified records. When a zone is first read in there + is an implicit <command>$ORIGIN</command> + <<varname>zone-name</varname>><command>.</command> + The current <command>$ORIGIN</command> is appended to + the domain specified in the <command>$ORIGIN</command> + argument if it is not absolute. + </para> + +<programlisting> +$ORIGIN example.com. +WWW CNAME MAIN-SERVER +</programlisting> + + <para> + is equivalent to + </para> + +<programlisting> +WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. +</programlisting> + + </sect3> + <sect3> + <title>The <command>$INCLUDE</command> Directive</title> + <para> + Syntax: <command>$INCLUDE</command> + <replaceable>filename</replaceable> + <optional> +<replaceable>origin</replaceable> </optional> + <optional> <replaceable>comment</replaceable> </optional> + </para> + <para> + Read and process the file <filename>filename</filename> as + if it were included into the file at this point. If <command>origin</command> is + specified the file is processed with <command>$ORIGIN</command> set + to that value, otherwise the current <command>$ORIGIN</command> is + used. + </para> + <para> + The origin and the current domain name + revert to the values they had prior to the <command>$INCLUDE</command> once + the file has been read. + </para> + <note> + <para> + RFC 1035 specifies that the current origin should be restored + after + an <command>$INCLUDE</command>, but it is silent + on whether the current + domain name should also be restored. BIND 9 restores both of + them. + This could be construed as a deviation from RFC 1035, a + feature, or both. + </para> + </note> + </sect3> + <sect3> + <title>The <command>$TTL</command> Directive</title> + <para> + Syntax: <command>$TTL</command> + <replaceable>default-ttl</replaceable> + <optional> +<replaceable>comment</replaceable> </optional> + </para> + <para> + Set the default Time To Live (TTL) for subsequent records + with undefined TTLs. Valid TTLs are of the range 0-2147483647 + seconds. + </para> + <para><command>$TTL</command> + is defined in RFC 2308. + </para> + </sect3> + </sect2> + <sect2> + <title><acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive</title> + <para> + Syntax: <command>$GENERATE</command> + <replaceable>range</replaceable> + <replaceable>lhs</replaceable> + <optional><replaceable>ttl</replaceable></optional> + <optional><replaceable>class</replaceable></optional> + <replaceable>type</replaceable> + <replaceable>rhs</replaceable> + <optional><replaceable>comment</replaceable></optional> + </para> + <para><command>$GENERATE</command> + is used to create a series of resource records that only + differ from each other by an + iterator. <command>$GENERATE</command> 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. + </para> + <programlisting>$ORIGIN 0.0.192.IN-ADDR.ARPA. $GENERATE 1-2 0 NS SERVER$.EXAMPLE. $GENERATE 1-127 $ CNAME $.0</programlisting> -<para>is equivalent to</para> + + <para> + is equivalent to + </para> + <programlisting>0.0.0.192.IN-ADDR.ARPA NS SERVER1.EXAMPLE. 0.0.0.192.IN-ADDR.ARPA. NS SERVER2.EXAMPLE. 1.0.0.192.IN-ADDR.ARPA. CNAME 1.0.0.0.192.IN-ADDR.ARPA. @@ -5842,97 +10449,215 @@ $GENERATE 1-127 $ CNAME $.0</programlisting> ... 127.0.0.192.IN-ADDR.ARPA. CNAME 127.0.0.0.192.IN-ADDR.ARPA. </programlisting> - <informaltable colsep = "0" rowsep = "0"> - <tgroup cols = "2" colsep = "0" rowsep = "0" tgroupstyle = "3Level-table"> - <colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.875in"/> - <colspec colname = "2" colnum = "2" colsep = "0" colwidth = "4.250in"/> - <tbody> - <row rowsep = "0"> - <entry colname = "1"><para><command>range</command></para></entry> - <entry colname = "2"><para>This can be one of two forms: start-stop -or start-stop/step. If the first form is used, then step is set to - 1. All of start, stop and step must be positive.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>lhs</command></para></entry> - <entry colname = "2"><para><command>lhs</command> describes the -owner name of the resource records to be created. Any single -<command>$</command> (dollar sign) symbols -within the <command>lhs</command> side are replaced by the iterator -value. -To get a $ in the output you need to escape the <command>$</command> -using a backslash <command>\</command>, -e.g. <command>\$</command>. The <command>$</command> may optionally be followed -by modifiers which change the offset from the iterator, field width and base. -Modifiers are introduced by a <command>{</command> immediately following the -<command>$</command> as <command>${offset[,width[,base]]}</command>. -For example, <command>${-20,3,d}</command> which subtracts 20 from the current value, -prints the result as a decimal in a zero-padded field of width 3. Available -output forms are decimal (<command>d</command>), octal (<command>o</command>) -and hexadecimal (<command>x</command> or <command>X</command> for uppercase). -The default modifier is <command>${0,0,d}</command>. -If the <command>lhs</command> is not -absolute, the current <command>$ORIGIN</command> is appended to -the name.</para> -<para>For compatibility with earlier versions, <command>$$</command> is still -recognized as indicating a literal $ in the output.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>ttl</command></para></entry> - <entry colname = "2"><para>Specifies the - ttl of the generated records. If not specified this will be - inherited using the normal ttl inheritance rules.</para> - <para><command>class</command> and <command>ttl</command> can be - entered in either order.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>class</command></para></entry> - <entry colname = "2"><para>Specifies the - class of the generated records. This must match the zone class if - it is specified.</para> - <para><command>class</command> and <command>ttl</command> can be - entered in either order.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>type</command></para></entry> - <entry colname = "2"><para>At present the only supported types are -PTR, CNAME, DNAME, A, AAAA and NS.</para></entry> - </row> - <row rowsep = "0"> - <entry colname = "1"><para><command>rhs</command></para></entry> - <entry colname = "2"><para>A domain name. It is processed -similarly to lhs.</para></entry> - </row> - </tbody> - </tgroup></informaltable> - <para>The <command>$GENERATE</command> directive is a <acronym>BIND</acronym> extension -and not part of the standard zone file format.</para> - <para>BIND 8 does not support the optional TTL and CLASS fields.</para> - </sect2> - </sect1> -</chapter> -<chapter id="Bv9ARM.ch07"><title><acronym>BIND</acronym> 9 Security Considerations</title> -<sect1 id="Access_Control_Lists"><title>Access Control Lists</title> -<para>Access Control Lists (ACLs), are address match lists that -you can set up and nickname for future use in <command>allow-notify</command>, -<command>allow-query</command>, <command>allow-recursion</command>, -<command>blackhole</command>, <command>allow-transfer</command>, -etc.</para> -<para>Using ACLs allows you to have finer control over who can access -your name server, without cluttering up your config files with huge -lists of IP addresses.</para> -<para>It is a <emphasis>good idea</emphasis> to use ACLs, and to -control access to your server. Limiting access to your server by -outside parties can help prevent spoofing and denial of service (DoS) -attacks against your server.</para> -<para>Here is an example of how to properly apply ACLs:</para> + + <informaltable colsep="0" rowsep="0"> + <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table"> + <colspec colname="1" colnum="1" colsep="0" colwidth="0.875in"/> + <colspec colname="2" colnum="2" colsep="0" colwidth="4.250in"/> + <tbody> + <row rowsep="0"> + <entry colname="1"> + <para><command>range</command></para> + </entry> + <entry colname="2"> + <para> + This can be one of two forms: start-stop + or start-stop/step. If the first form is used, then step + is set to + 1. All of start, stop and step must be positive. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>lhs</command></para> + </entry> + <entry colname="2"> + <para>This + describes the owner name of the resource records + to be created. Any single <command>$</command> + (dollar sign) + symbols within the <command>lhs</command> side + are replaced by the iterator value. + + To get a $ in the output, you need to escape the + <command>$</command> using a backslash + <command>\</command>, + e.g. <command>\$</command>. The + <command>$</command> may optionally be followed + by modifiers which change the offset from the + iterator, field width and base. + + Modifiers are introduced by a + <command>{</command> (left brace) immediately following the + <command>$</command> as + <command>${offset[,width[,base]]}</command>. + For example, <command>${-20,3,d}</command> + subtracts 20 from the current value, prints the + result as a decimal in a zero-padded field of + width 3. + + Available output forms are decimal + (<command>d</command>), octal + (<command>o</command>) and hexadecimal + (<command>x</command> or <command>X</command> + for uppercase). The default modifier is + <command>${0,0,d}</command>. If the + <command>lhs</command> is not absolute, the + current <command>$ORIGIN</command> is appended + to the name. + </para> + <para> + For compatibility with earlier versions, <command>$$</command> is still + recognized as indicating a literal $ in the output. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>ttl</command></para> + </entry> + <entry colname="2"> + <para> + Specifies the time-to-live of the generated records. If + not specified this will be inherited using the + normal ttl inheritance rules. + </para> + <para><command>class</command> + and <command>ttl</command> can be + entered in either order. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>class</command></para> + </entry> + <entry colname="2"> + <para> + Specifies the class of the generated records. + This must match the zone class if it is + specified. + </para> + <para><command>class</command> + and <command>ttl</command> can be + entered in either order. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>type</command></para> + </entry> + <entry colname="2"> + <para> + At present the only supported types are + PTR, CNAME, DNAME, A, AAAA and NS. + </para> + </entry> + </row> + <row rowsep="0"> + <entry colname="1"> + <para><command>rhs</command></para> + </entry> + <entry colname="2"> + <para> + <command>rhs</command> is a domain name. It is processed + similarly to lhs. + </para> + </entry> + </row> + </tbody> + </tgroup> + </informaltable> + <para> + The <command>$GENERATE</command> directive is a <acronym>BIND</acronym> extension + and not part of the standard zone file format. + </para> + <para> + BIND 8 does not support the optional TTL and CLASS fields. + </para> + </sect2> + + <sect2 id="zonefile_format"> + <title>Additional File Formats</title> + <para> + In addition to the standard textual format, BIND 9 + supports the ability to read or dump to zone files in + other formats. The <constant>raw</constant> format is + currently available as an additional format. It is a + binary format representing BIND 9's internal data + structure directly, thereby remarkably improving the + loading time. + </para> + <para> + For a primary server, a zone file in the + <constant>raw</constant> format is expected to be + generated from a textual zone file by the + <command>named-compilezone</command> command. For a + secondary server or for a dynamic zone, it is automatically + generated (if this format is specified by the + <command>masterfile-format</command> option) when + <command>named</command> dumps the zone contents after + zone transfer or when applying prior updates. + </para> + <para> + If a zone file in a binary format needs manual modification, + it first must be converted to a textual form by the + <command>named-compilezone</command> command. All + necessary modification should go to the text file, which + should then be converted to the binary form by the + <command>named-compilezone</command> command again. + </para> + <para> + Although the <constant>raw</constant> format uses the + network byte order and avoids architecture-dependent + data alignment so that it is as much portable as + possible, it is primarily expected to be used inside + the same single system. In order to export a zone + file in the <constant>raw</constant> format or make a + portable backup of the file, it is recommended to + convert the file to the standard textual representation. + </para> + </sect2> + </sect1> + </chapter> + <chapter id="Bv9ARM.ch07"> + <title><acronym>BIND</acronym> 9 Security Considerations</title> + <sect1 id="Access_Control_Lists"> + <title>Access Control Lists</title> + <para> + Access Control Lists (ACLs), are address match lists that + you can set up and nickname for future use in <command>allow-notify</command>, + <command>allow-query</command>, <command>allow-recursion</command>, + <command>blackhole</command>, <command>allow-transfer</command>, + etc. + </para> + <para> + Using ACLs allows you to have finer control over who can access + your name server, without cluttering up your config files with huge + lists of IP addresses. + </para> + <para> + It is a <emphasis>good idea</emphasis> to use ACLs, and to + control access to your server. Limiting access to your server by + outside parties can help prevent spoofing and denial of service (DoS) attacks against + your server. + </para> + <para> + Here is an example of how to properly apply ACLs: + </para> + <programlisting> -// Set up an ACL named "bogusnets" that will block RFC1918 space, -// which is commonly used in spoofing attacks. -acl bogusnets { 0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3; 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; }; +// Set up an ACL named "bogusnets" that will block RFC1918 space +// and some reserved space, which is commonly used in spoofing attacks. +acl bogusnets { + 0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3; + 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; +}; // Set up an ACL called our-nets. Replace this with the real IP numbers. -acl our-nets { x.x.x.x/24; x.x.x.x/21; }; +acl our-nets { x.x.x.x/24; x.x.x.x/21; }; options { ... ... @@ -5949,919 +10674,1653 @@ zone "example.com" { allow-query { any; }; }; </programlisting> -<para>This allows recursive queries of the server from the outside -unless recursion has been previously disabled.</para> -<para>For more information on how to use ACLs to protect your server, -see the <emphasis>AUSCERT</emphasis> advisory at -<ulink url="ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos">ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos</ulink></para></sect1> -<sect1><title><command>chroot</command> and <command>setuid</command> (for -UNIX servers)</title> -<para>On UNIX servers, it is possible to run <acronym>BIND</acronym> in a <emphasis>chrooted</emphasis> environment -(using the <command>chroot()</command> function) by specifying the "<option>-t</option>" -option. This can help improve system security by placing <acronym>BIND</acronym> in -a "sandbox", which will limit the damage done if a server is compromised.</para> -<para>Another useful feature in the UNIX version of <acronym>BIND</acronym> is the -ability to run the daemon as an unprivileged user ( <option>-u</option> <replaceable>user</replaceable> ). -We suggest running as an unprivileged user when using the <command>chroot</command> feature.</para> -<para>Here is an example command line to load <acronym>BIND</acronym> in a <command>chroot</command> sandbox, -<command>/var/named</command>, and to run <command>named</command> <command>setuid</command> to -user 202:</para> -<para><userinput>/usr/local/bin/named -u 202 -t /var/named</userinput></para> - -<sect2><title>The <command>chroot</command> Environment</title> - -<para>In order for a <command>chroot</command> environment to -work properly in a particular directory -(for example, <filename>/var/named</filename>), -you will need to set up an environment that includes everything -<acronym>BIND</acronym> needs to run. -From <acronym>BIND</acronym>'s point of view, <filename>/var/named</filename> is -the root of the filesystem. You will need to adjust the values of options like -like <command>directory</command> and <command>pid-file</command> to account -for this. -</para> -<para> -Unlike with earlier versions of BIND, you will typically -<emphasis>not</emphasis> need to compile <command>named</command> -statically nor install shared libraries under the new root. -However, depending on your operating system, you may need -to set up things like -<filename>/dev/zero</filename>, -<filename>/dev/random</filename>, -<filename>/dev/log</filename>, and -<filename>/etc/localtime</filename>. -</para> -</sect2> - -<sect2><title>Using the <command>setuid</command> Function</title> - -<para>Prior to running the <command>named</command> daemon, use -the <command>touch</command> utility (to change file access and -modification times) or the <command>chown</command> utility (to -set the user id and/or group id) on files -to which you want <acronym>BIND</acronym> -to write. Note that if the <command>named</command> daemon is running as an -unprivileged user, it will not be able to bind to new restricted ports if the -server is reloaded.</para> -</sect2> -</sect1> - -<sect1 id="dynamic_update_security"><title>Dynamic Update Security</title> - -<para>Access to the dynamic -update facility should be strictly limited. In earlier versions of -<acronym>BIND</acronym>, the only way to do this was based on the IP -address of the host requesting the update, by listing an IP address or -network prefix in the <command>allow-update</command> zone option. -This method is insecure since the source address of the update UDP packet -is easily forged. Also note that if the IP addresses allowed by the -<command>allow-update</command> option include the address of a slave -server which performs forwarding of dynamic updates, the master can be -trivially attacked by sending the update to the slave, which will -forward it to the master with its own source IP address causing the -master to approve it without question.</para> - -<para>For these reasons, we strongly recommend that updates be -cryptographically authenticated by means of transaction signatures -(TSIG). That is, the <command>allow-update</command> option should -list only TSIG key names, not IP addresses or network -prefixes. Alternatively, the new <command>update-policy</command> -option can be used.</para> - -<para>Some sites choose to keep all dynamically-updated DNS data -in a subdomain and delegate that subdomain to a separate zone. This -way, the top-level zone containing critical data such as the IP addresses -of public web and mail servers need not allow dynamic update at -all.</para> - -</sect1></chapter> - -<chapter id="Bv9ARM.ch08"> - <title>Troubleshooting</title> - <sect1> - <title>Common Problems</title> - <sect2> - <title>It's not working; how can I figure out what's wrong?</title> - - <para>The best solution to solving installation and - configuration issues is to take preventative measures by setting - up logging files beforehand. The log files provide a - source of hints and information that can be used to figure out - what went wrong and how to fix the problem.</para> - - </sect2> - </sect1> - <sect1> - <title>Incrementing and Changing the Serial Number</title> - - <para>Zone serial numbers are just numbers-they aren't date - related. A lot of people set them to a number that represents a - date, usually of the form YYYYMMDDRR. A number of people have been - testing these numbers for Y2K compliance and have set the number - to the year 2000 to see if it will work. They then try to restore - the old serial number. This will cause problems because serial - numbers are used to indicate that a zone has been updated. If the - serial number on the slave server is lower than the serial number - on the master, the slave server will attempt to update its copy of - the zone.</para> - - <para>Setting the serial number to a lower number on the master - server than the slave server means that the slave will not perform - updates to its copy of the zone.</para> - - <para>The solution to this is to add 2147483647 (2^31-1) to the - number, reload the zone and make sure all slaves have updated to - the new zone serial number, then reset the number to what you want - it to be, and reload the zone again.</para> - - </sect1> - <sect1> - <title>Where Can I Get Help?</title> - - <para>The Internet Software Consortium (<acronym>ISC</acronym>) offers a wide range - of support and service agreements for <acronym>BIND</acronym> and <acronym>DHCP</acronym> servers. Four - levels of premium support are available and each level includes - support for all <acronym>ISC</acronym> programs, significant discounts on products - and training, and a recognized priority on bug fixes and - non-funded feature requests. In addition, <acronym>ISC</acronym> offers a standard - support agreement package which includes services ranging from bug - fix announcements to remote support. It also includes training in - <acronym>BIND</acronym> and <acronym>DHCP</acronym>.</para> - - <para>To discuss arrangements for support, contact - <ulink url="mailto:info@isc.org">info@isc.org</ulink> or visit the - <acronym>ISC</acronym> web page at <ulink - url="http://www.isc.org/services/support/">http://www.isc.org/services/support/</ulink> - to read more.</para> - </sect1> -</chapter> -<appendix id="Bv9ARM.ch09"> - <title>Appendices</title> - <sect1> - <title>Acknowledgments</title> - <sect2> - <title>A Brief History of the <acronym>DNS</acronym> and <acronym>BIND</acronym></title> - - <para>Although the "official" beginning of the Domain Name - System occurred in 1984 with the publication of RFC 920, the - core of the new system was described in 1983 in RFCs 882 and - 883. From 1984 to 1987, the ARPAnet (the precursor to today's - Internet) became a testbed of experimentation for developing the - new naming/addressing scheme in a rapidly expanding, - operational network environment. New RFCs were written and - published in 1987 that modified the original documents to - incorporate improvements based on the working model. RFC 1034, - "Domain Names-Concepts and Facilities", and RFC 1035, "Domain - Names-Implementation and Specification" were published and - became the standards upon which all <acronym>DNS</acronym> implementations are - built. -</para> - - <para>The first working domain name server, called "Jeeves", was -written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20 -machines located at the University of Southern California's Information -Sciences Institute (USC-ISI) and SRI International's Network Information -Center (SRI-NIC). A <acronym>DNS</acronym> server for Unix machines, the Berkeley Internet -Name Domain (<acronym>BIND</acronym>) package, was written soon after by a group of -graduate students at the University of California at Berkeley under -a grant from the US Defense Advanced Research Projects Administration -(DARPA). -</para> -<para> -Versions of <acronym>BIND</acronym> through 4.8.3 were maintained by the Computer -Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark -Painter, David Riggle and Songnian Zhou made up the initial <acronym>BIND</acronym> -project team. After that, additional work on the software package -was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation -employee on loan to the CSRG, worked on <acronym>BIND</acronym> for 2 years, from 1985 -to 1987. Many other people also contributed to <acronym>BIND</acronym> development -during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell, -Mike Muuss, Jim Bloom and Mike Schwartz. <acronym>BIND</acronym> maintenance was subsequently -handled by Mike Karels and O. Kure.</para> - <para><acronym>BIND</acronym> versions 4.9 and 4.9.1 were released by Digital Equipment -Corporation (now Compaq Computer Corporation). Paul Vixie, then -a DEC employee, became <acronym>BIND</acronym>'s primary caretaker. He was assisted -by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew -Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat -Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe -Wolfhugel, and others.</para> - <para><acronym>BIND</acronym> version 4.9.2 was sponsored by Vixie Enterprises. Paul -Vixie became <acronym>BIND</acronym>'s principal architect/programmer.</para> - <para><acronym>BIND</acronym> versions from 4.9.3 onward have been developed and maintained -by the Internet Software Consortium with support being provided -by ISC's sponsors. As co-architects/programmers, Bob Halley and -Paul Vixie released the first production-ready version of <acronym>BIND</acronym> version -8 in May 1997.</para> - <para><acronym>BIND</acronym> development work is made possible today by the sponsorship -of several corporations, and by the tireless work efforts of numerous -individuals.</para> - </sect2> - </sect1> -<sect1 id="historical_dns_information"> - -<title>General <acronym>DNS</acronym> Reference Information</title> - <sect2 id="ipv6addresses"> - <title>IPv6 addresses (AAAA)</title> - <para>IPv6 addresses are 128-bit identifiers for interfaces and -sets of interfaces which were introduced in the <acronym>DNS</acronym> to facilitate -scalable Internet routing. There are three types of addresses: <emphasis>Unicast</emphasis>, -an identifier for a single interface; <emphasis>Anycast</emphasis>, -an identifier for a set of interfaces; and <emphasis>Multicast</emphasis>, -an identifier for a set of interfaces. Here we describe the global -Unicast address scheme. For more information, see RFC 2374.</para> -<para>The aggregatable global Unicast address format is as follows:</para> -<informaltable colsep = "0" rowsep = "0"><tgroup cols = "6" - colsep = "0" rowsep = "0" tgroupstyle = "1Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "0.477in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "0.501in"/> -<colspec colname = "3" colnum = "3" colsep = "0" colwidth = "0.523in"/> -<colspec colname = "4" colnum = "4" colsep = "0" colwidth = "0.731in"/> -<colspec colname = "5" colnum = "5" colsep = "0" colwidth = "1.339in"/> -<colspec colname = "6" colnum = "6" colsep = "0" colwidth = "2.529in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1" colsep = "1" rowsep = "1"><para>3</para></entry> -<entry colname = "2" colsep = "1" rowsep = "1"><para>13</para></entry> -<entry colname = "3" colsep = "1" rowsep = "1"><para>8</para></entry> -<entry colname = "4" colsep = "1" rowsep = "1"><para>24</para></entry> -<entry colname = "5" colsep = "1" rowsep = "1"><para>16</para></entry> -<entry colname = "6" rowsep = "1"><para>64 bits</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1" colsep = "1"><para>FP</para></entry> -<entry colname = "2" colsep = "1"><para>TLA ID</para></entry> -<entry colname = "3" colsep = "1"><para>RES</para></entry> -<entry colname = "4" colsep = "1"><para>NLA ID</para></entry> -<entry colname = "5" colsep = "1"><para>SLA ID</para></entry> -<entry colname = "6"><para>Interface ID</para></entry> -</row> -<row rowsep = "0"> -<entry nameend = "4" namest = "1"><para><------ Public Topology -------></para></entry> -<entry colname = "5"><para></para></entry> -<entry colname = "6"><para></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para></para></entry> -<entry colname = "3"><para></para></entry> -<entry colname = "4"><para></para></entry> -<entry colname = "5"><para><-Site Topology-></para></entry> -<entry colname = "6"><para></para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para></para></entry> -<entry colname = "2"><para></para></entry> -<entry colname = "3"><para></para></entry> -<entry colname = "4"><para></para></entry> -<entry colname = "5"><para></para></entry> -<entry colname = "6"><para><------ Interface Identifier ------></para></entry> -</row> -</tbody> -</tgroup></informaltable> - <para>Where -<informaltable colsep = "0" rowsep = "0"><tgroup - cols = "3" colsep = "0" rowsep = "0" tgroupstyle = "2Level-table"> -<colspec colname = "1" colnum = "1" colsep = "0" colwidth = "1.375in"/> -<colspec colname = "2" colnum = "2" colsep = "0" colwidth = "0.250in"/> -<colspec colname = "3" colnum = "3" colsep = "0" colwidth = "3.500in"/> -<tbody> -<row rowsep = "0"> -<entry colname = "1"><para>FP</para></entry> -<entry colname = "2"><para>=</para></entry> -<entry colname = "3"><para>Format Prefix (001)</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>TLA ID</para></entry> -<entry colname = "2"><para>=</para></entry> -<entry colname = "3"><para>Top-Level Aggregation Identifier</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>RES</para></entry> -<entry colname = "2"><para>=</para></entry> -<entry colname = "3"><para>Reserved for future use</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>NLA ID</para></entry> -<entry colname = "2"><para>=</para></entry> -<entry colname = "3"><para>Next-Level Aggregation Identifier</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>SLA ID</para></entry> -<entry colname = "2"><para>=</para></entry> -<entry colname = "3"><para>Site-Level Aggregation Identifier</para></entry> -</row> -<row rowsep = "0"> -<entry colname = "1"><para>INTERFACE ID</para></entry> -<entry colname = "2"><para>=</para></entry> -<entry colname = "3"><para>Interface Identifier</para></entry> -</row> -</tbody> -</tgroup></informaltable></para> - <para>The <emphasis>Public Topology</emphasis> is provided by the -upstream provider or ISP, and (roughly) corresponds to the IPv4 <emphasis>network</emphasis> section -of the address range. The <emphasis>Site Topology</emphasis> is -where you can subnet this space, much the same as subnetting an -IPv4 /16 network into /24 subnets. The <emphasis>Interface Identifier</emphasis> is -the address of an individual interface on a given network. (With -IPv6, addresses belong to interfaces rather than machines.)</para> - <para>The subnetting capability of IPv6 is much more flexible than -that of IPv4: subnetting can now be carried out on bit boundaries, -in much the same way as Classless InterDomain Routing (CIDR).</para> -<para>The Interface Identifier must be unique on that network. On -ethernet networks, one way to ensure this is to set the address -to the first three bytes of the hardware address, "FFFE", then the -last three bytes of the hardware address. The lowest significant -bit of the first byte should then be complemented. Addresses are -written as 32-bit blocks separated with a colon, and leading zeros -of a block may be omitted, for example:</para> -<para><command>2001:db8:201:9:a00:20ff:fe81:2b32</command></para> -<para>IPv6 address specifications are likely to contain long strings -of zeros, so the architects have included a shorthand for specifying -them. The double colon (`::') indicates the longest possible string -of zeros that can fit, and can be used only once in an address.</para> - </sect2> - </sect1> - <sect1 id="bibliography"> - <title>Bibliography (and Suggested Reading)</title> - <sect2 id="rfcs"> - <title>Request for Comments (RFCs)</title> - <para>Specification documents for the Internet protocol suite, including -the <acronym>DNS</acronym>, are published as part of the Request for Comments (RFCs) -series of technical notes. The standards themselves are defined -by the Internet Engineering Task Force (IETF) and the Internet Engineering -Steering Group (IESG). RFCs can be obtained online via FTP at -<ulink url="ftp://www.isi.edu/in-notes/">ftp://www.isi.edu/in-notes/RFC<replaceable>xxx</replaceable>.txt</ulink> (where <replaceable>xxx</replaceable> is -the number of the RFC). RFCs are also available via the Web at -<ulink url="http://www.ietf.org/rfc/">http://www.ietf.org/rfc/</ulink>. -</para> - <bibliography> - <bibliodiv> - <!-- one of (BIBLIOENTRY BIBLIOMIXED) --> - <title>Standards</title> - <biblioentry> - <abbrev>RFC974</abbrev> - <author> - <surname>Partridge</surname> - <firstname>C.</firstname> - </author> - <title>Mail Routing and the Domain System</title> - <pubdate>January 1986</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1034</abbrev> - <author> - <surname>Mockapetris</surname> - <firstname>P.V.</firstname> - </author> - <title>Domain Names — Concepts and Facilities</title> - <pubdate>November 1987</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1035</abbrev> - <author> - <surname>Mockapetris</surname> - <firstname>P. V.</firstname> - </author> <title>Domain Names — Implementation and -Specification</title> - <pubdate>November 1987</pubdate> - </biblioentry> - </bibliodiv> - <bibliodiv id="proposed_standards" xreflabel="Proposed Standards"> - - <title>Proposed Standards</title> - <!-- one of (BIBLIOENTRY BIBLIOMIXED) --> - <biblioentry> - <abbrev>RFC2181</abbrev> - <author> - <surname>Elz</surname> - <firstname>R., R. Bush</firstname> - </author> - <title>Clarifications to the <acronym>DNS</acronym> Specification</title> - <pubdate>July 1997</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2308</abbrev> - <author> - <surname>Andrews</surname> - <firstname>M.</firstname> - </author> - <title>Negative Caching of <acronym>DNS</acronym> Queries</title> - <pubdate>March 1998</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1995</abbrev> - <author> - <surname>Ohta</surname> - <firstname>M.</firstname> - </author> - <title>Incremental Zone Transfer in <acronym>DNS</acronym></title> - <pubdate>August 1996</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1996</abbrev> - <author> - <surname>Vixie</surname> - <firstname>P.</firstname> - </author> - <title>A Mechanism for Prompt Notification of Zone Changes</title> - <pubdate>August 1996</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2136</abbrev> - <authorgroup> - <author> - <surname>Vixie</surname> - <firstname>P.</firstname> - </author> - <author> - <firstname>S.</firstname> - <surname>Thomson</surname> - </author> - <author> - <firstname>Y.</firstname> - <surname>Rekhter</surname> - </author> - <author> - <firstname>J.</firstname> - <surname>Bound</surname> - </author> - </authorgroup> - <title>Dynamic Updates in the Domain Name System</title> - <pubdate>April 1997</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2845</abbrev> - <authorgroup> - <author> - <surname>Vixie</surname> - <firstname>P.</firstname> - </author> - <author> - <firstname>O.</firstname> - <surname>Gudmundsson</surname> - </author> - <author> - <firstname>D.</firstname> - <surname>Eastlake</surname> - <lineage>3rd</lineage></author> - <author> - <firstname>B.</firstname> - <surname>Wellington</surname> - </author></authorgroup> - <title>Secret Key Transaction Authentication for <acronym>DNS</acronym> (TSIG)</title> - <pubdate>May 2000</pubdate> - </biblioentry> - </bibliodiv> - <bibliodiv> - <title>Proposed Standards Still Under Development</title> - <note> - <para><emphasis>Note:</emphasis> the following list of -RFCs are undergoing major revision by the IETF.</para> - </note> - <biblioentry> - <abbrev>RFC1886</abbrev> - <authorgroup> - <author> - <surname>Thomson</surname> - <firstname>S.</firstname> - </author> - <author> - <firstname>C.</firstname> - <surname>Huitema</surname> - </author> - </authorgroup> - <title><acronym>DNS</acronym> Extensions to support IP version 6</title> - <pubdate>December 1995</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2065</abbrev> - <authorgroup> - <author> - <surname>Eastlake</surname> - <lineage>3rd</lineage> - <firstname>D.</firstname> - </author> - <author> - <firstname>C.</firstname> - <surname>Kaufman</surname> - </author> - </authorgroup> - <title>Domain Name System Security Extensions</title> - <pubdate>January 1997</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2137</abbrev> - <author> - <surname>Eastlake</surname> - <lineage>3rd</lineage> - <firstname>D.</firstname> - </author> - <title>Secure Domain Name System Dynamic Update</title> - <pubdate>April 1997</pubdate> - </biblioentry> - </bibliodiv> - <bibliodiv> - <title>Other Important RFCs About <acronym>DNS</acronym> Implementation</title> - <biblioentry> - <abbrev>RFC1535</abbrev> - <author> - <surname>Gavron</surname> - <firstname>E.</firstname> - </author> - <title>A Security Problem and Proposed Correction With Widely Deployed <acronym>DNS</acronym> Software.</title> - <pubdate>October 1993</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1536</abbrev> - <authorgroup> - <author> - <surname>Kumar</surname> - <firstname>A.</firstname> - </author> - <author> - <firstname>J.</firstname> - <surname>Postel</surname> - </author> - <author> - <firstname>C.</firstname> - <surname>Neuman</surname></author> - <author> - <firstname>P.</firstname> - <surname>Danzig</surname> - </author> - <author> - <firstname>S.</firstname> - <surname>Miller</surname> - </author> - </authorgroup> - <title>Common <acronym>DNS</acronym> Implementation Errors and Suggested Fixes</title> - <pubdate>October 1993</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1982</abbrev> - <authorgroup> - <author> - <surname>Elz</surname> - <firstname>R.</firstname> - </author> - <author> - <firstname>R.</firstname> - <surname>Bush</surname> - </author> - </authorgroup> - <title>Serial Number Arithmetic</title> - <pubdate>August 1996</pubdate> - </biblioentry> - </bibliodiv> - <bibliodiv> - <title>Resource Record Types</title> - <biblioentry> - <abbrev>RFC1183</abbrev> - <authorgroup> - <author> - <surname>Everhart</surname> - <firstname>C.F.</firstname> - </author> - <author> - <firstname>L. A.</firstname> - <surname>Mamakos</surname> - </author> - <author> - <firstname>R.</firstname> - <surname>Ullmann</surname> - </author> - <author> - <firstname>P.</firstname> - <surname>Mockapetris</surname> - </author> - </authorgroup> - <title>New <acronym>DNS</acronym> RR Definitions</title> - <pubdate>October 1990</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1706</abbrev> - <authorgroup> - <author> - <surname>Manning</surname> - <firstname>B.</firstname> - </author> - <author> - <firstname>R.</firstname> - <surname>Colella</surname> - </author> - </authorgroup> - <title><acronym>DNS</acronym> NSAP Resource Records</title> - <pubdate>October 1994</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2168</abbrev> - <authorgroup> - <author> - <surname>Daniel</surname> - <firstname>R.</firstname> - </author> - <author> - <firstname>M.</firstname> - <surname>Mealling</surname> - </author> - </authorgroup> - <title>Resolution of Uniform Resource Identifiers using -the Domain Name System</title> - <pubdate>June 1997</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1876</abbrev> - <authorgroup> - <author> - <surname>Davis</surname> - <firstname>C.</firstname> - </author> - <author> - <firstname>P.</firstname> - <surname>Vixie</surname> - </author> - <author> - <firstname>T.</firstname> - <firstname>Goodwin</firstname> - </author> - <author> - <firstname>I.</firstname> - <surname>Dickinson</surname> - </author> - </authorgroup> - <title>A Means for Expressing Location Information in the Domain -Name System</title> - <pubdate>January 1996</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2052</abbrev> - <authorgroup> - <author> - <surname>Gulbrandsen</surname> - <firstname>A.</firstname> - </author> - <author> - <firstname>P.</firstname> - <surname>Vixie</surname> - </author> - </authorgroup> - <title>A <acronym>DNS</acronym> RR for Specifying the Location of -Services.</title> - <pubdate>October 1996</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2163</abbrev> - <author> - <surname>Allocchio</surname> - <firstname>A.</firstname> - </author> - <title>Using the Internet <acronym>DNS</acronym> to Distribute MIXER -Conformant Global Address Mapping</title> - <pubdate>January 1998</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2230</abbrev> - <author> - <surname>Atkinson</surname> - <firstname>R.</firstname> - </author> - <title>Key Exchange Delegation Record for the <acronym>DNS</acronym></title> - <pubdate>October 1997</pubdate> - </biblioentry> - </bibliodiv> - <bibliodiv> - <title><acronym>DNS</acronym> and the Internet</title> - <biblioentry> - <abbrev>RFC1101</abbrev> - <author> - <surname>Mockapetris</surname> - <firstname>P. V.</firstname> - </author> - <title><acronym>DNS</acronym> Encoding of Network Names and Other Types</title> - <pubdate>April 1989</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1123</abbrev> - <author> - <surname>Braden</surname> - <surname>R.</surname> - </author> - <title>Requirements for Internet Hosts - Application and Support</title> - <pubdate>October 1989</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1591</abbrev> - <author> - <surname>Postel</surname> - <firstname>J.</firstname></author> - <title>Domain Name System Structure and Delegation</title> - <pubdate>March 1994</pubdate></biblioentry> - <biblioentry> - <abbrev>RFC2317</abbrev> - <authorgroup> - <author> - <surname>Eidnes</surname> - <firstname>H.</firstname> - </author> - <author> - <firstname>G.</firstname> - <surname>de Groot</surname> - </author> - <author> - <firstname>P.</firstname> - <surname>Vixie</surname> - </author> - </authorgroup> - <title>Classless IN-ADDR.ARPA Delegation</title> - <pubdate>March 1998</pubdate> - </biblioentry> - </bibliodiv> - <bibliodiv> - <title><acronym>DNS</acronym> Operations</title> - <biblioentry> - <abbrev>RFC1537</abbrev> - <author> - <surname>Beertema</surname> - <firstname>P.</firstname> - </author> - <title>Common <acronym>DNS</acronym> Data File Configuration Errors</title> - <pubdate>October 1993</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1912</abbrev> - <author> - <surname>Barr</surname> - <firstname>D.</firstname> - </author> - <title>Common <acronym>DNS</acronym> Operational and Configuration Errors</title> - <pubdate>February 1996</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2010</abbrev> - <authorgroup> - <author> - <surname>Manning</surname> - <firstname>B.</firstname> - </author> - <author> - <firstname>P.</firstname> - <surname>Vixie</surname> - </author> - </authorgroup> - <title>Operational Criteria for Root Name Servers.</title> - <pubdate>October 1996</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2219</abbrev> - <authorgroup> - <author> - <surname>Hamilton</surname> - <firstname>M.</firstname> - </author> - <author> - <firstname>R.</firstname> - <surname>Wright</surname> - </author> - </authorgroup> - <title>Use of <acronym>DNS</acronym> Aliases for Network Services.</title> - <pubdate>October 1997</pubdate> - </biblioentry> - </bibliodiv> - <bibliodiv> - <title>Other <acronym>DNS</acronym>-related RFCs</title> - <note> - <para>Note: the following list of RFCs, although -<acronym>DNS</acronym>-related, are not concerned with implementing software.</para> - </note> - <biblioentry> - <abbrev>RFC1464</abbrev> - <author> - <surname>Rosenbaum</surname> - <firstname>R.</firstname> - </author> - <title>Using the Domain Name System To Store Arbitrary String Attributes</title> - <pubdate>May 1993</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC1713</abbrev> - <author> - <surname>Romao</surname> - <firstname>A.</firstname> - </author> - <title>Tools for <acronym>DNS</acronym> Debugging</title> - <pubdate>November 1994</pubdate></biblioentry> - <biblioentry> - <abbrev>RFC1794</abbrev> - <author> - <surname>Brisco</surname> - <firstname>T.</firstname> - </author> - <title><acronym>DNS</acronym> Support for Load Balancing</title> - <pubdate>April 1995</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2240</abbrev> - <author> - <surname>Vaughan</surname> - <firstname>O.</firstname></author> - <title>A Legal Basis for Domain Name Allocation</title> - <pubdate>November 1997</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2345</abbrev> - <authorgroup> - <author> - <surname>Klensin</surname> - <firstname>J.</firstname> - </author> - <author> - <firstname>T.</firstname> - <surname>Wolf</surname> - </author> - <author> - <firstname>G.</firstname> - <surname>Oglesby</surname> - </author> - </authorgroup> - <title>Domain Names and Company Name Retrieval</title> - <pubdate>May 1998</pubdate> - </biblioentry> - <biblioentry> - <abbrev>RFC2352</abbrev> - <author> - <surname>Vaughan</surname> - <firstname>O.</firstname> - </author> - <title>A Convention For Using Legal Names as Domain Names</title> - <pubdate>May 1998</pubdate> - </biblioentry> - </bibliodiv> - <bibliodiv> - <title>Obsolete and Unimplemented Experimental RRs</title> - <biblioentry> - <abbrev>RFC1712</abbrev> - <authorgroup> - <author> - <surname>Farrell</surname> - <firstname>C.</firstname> - </author> - <author> - <firstname>M.</firstname> - <surname>Schulze</surname> - </author> - <author> - <firstname>S.</firstname> - <surname>Pleitner</surname> - </author> - <author> - <firstname>D.</firstname> - <surname>Baldoni</surname> - </author> - </authorgroup> - <title><acronym>DNS</acronym> Encoding of Geographical -Location</title> - <pubdate>November 1994</pubdate> - </biblioentry> - </bibliodiv> - </bibliography> - </sect2> - <sect2 id="internet_drafts"> - <title>Internet Drafts</title> - <para>Internet Drafts (IDs) are rough-draft working documents of -the Internet Engineering Task Force. They are, in essence, RFCs -in the preliminary stages of development. Implementors are cautioned not -to regard IDs as archival, and they should not be quoted or cited -in any formal documents unless accompanied by the disclaimer that -they are "works in progress." IDs have a lifespan of six months -after which they are deleted unless updated by their authors. -</para> - </sect2> - <sect2> - <title>Other Documents About <acronym>BIND</acronym></title> - <para></para> - <bibliography> - <biblioentry> - <authorgroup> - <author> - <surname>Albitz</surname> - <firstname>Paul</firstname> - </author> - <author> - <firstname>Cricket</firstname> - <surname>Liu</surname> - </author> - </authorgroup> - <title><acronym>DNS</acronym> and <acronym>BIND</acronym></title> - <copyright> - <year>1998</year> - <holder>Sebastopol, CA: O'Reilly and Associates</holder> - </copyright> - </biblioentry> - </bibliography> - </sect2> - </sect1> - -</appendix> - -</book> + + <para> + This allows recursive queries of the server from the outside + unless recursion has been previously disabled. + </para> + <para> + For more information on how to use ACLs to protect your server, + see the <emphasis>AUSCERT</emphasis> advisory at: + </para> + <para> + <ulink url="ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos" + >ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos</ulink> + </para> + </sect1> + <sect1> + <title><command>Chroot</command> and <command>Setuid</command></title> + <para> + On UNIX servers, it is possible to run <acronym>BIND</acronym> in a <emphasis>chrooted</emphasis> environment + (using the <command>chroot()</command> function) by specifying the "<option>-t</option>" + option. This can help improve system security by placing <acronym>BIND</acronym> in + a "sandbox", which will limit the damage done if a server is + compromised. + </para> + <para> + Another useful feature in the UNIX version of <acronym>BIND</acronym> is the + ability to run the daemon as an unprivileged user ( <option>-u</option> <replaceable>user</replaceable> ). + We suggest running as an unprivileged user when using the <command>chroot</command> feature. + </para> + <para> + Here is an example command line to load <acronym>BIND</acronym> in a <command>chroot</command> sandbox, + <command>/var/named</command>, and to run <command>named</command> <command>setuid</command> to + user 202: + </para> + <para> + <userinput>/usr/local/bin/named -u 202 -t /var/named</userinput> + </para> + + <sect2> + <title>The <command>chroot</command> Environment</title> + + <para> + In order for a <command>chroot</command> environment + to + work properly in a particular directory + (for example, <filename>/var/named</filename>), + you will need to set up an environment that includes everything + <acronym>BIND</acronym> needs to run. + From <acronym>BIND</acronym>'s point of view, <filename>/var/named</filename> is + the root of the filesystem. You will need to adjust the values of + options like + like <command>directory</command> and <command>pid-file</command> to account + for this. + </para> + <para> + Unlike with earlier versions of BIND, you typically will + <emphasis>not</emphasis> need to compile <command>named</command> + statically nor install shared libraries under the new root. + However, depending on your operating system, you may need + to set up things like + <filename>/dev/zero</filename>, + <filename>/dev/random</filename>, + <filename>/dev/log</filename>, and + <filename>/etc/localtime</filename>. + </para> + </sect2> + + <sect2> + <title>Using the <command>setuid</command> Function</title> + + <para> + Prior to running the <command>named</command> daemon, + use + the <command>touch</command> utility (to change file + access and + modification times) or the <command>chown</command> + utility (to + set the user id and/or group id) on files + to which you want <acronym>BIND</acronym> + to write. + </para> + <note> + Note that if the <command>named</command> daemon is running as an + unprivileged user, it will not be able to bind to new restricted + ports if the server is reloaded. + </note> + </sect2> + </sect1> + + <sect1 id="dynamic_update_security"> + <title>Dynamic Update Security</title> + + <para> + Access to the dynamic + update facility should be strictly limited. In earlier versions of + <acronym>BIND</acronym>, the only way to do this was + based on the IP + address of the host requesting the update, by listing an IP address + or + network prefix in the <command>allow-update</command> + zone option. + This method is insecure since the source address of the update UDP + packet + is easily forged. Also note that if the IP addresses allowed by the + <command>allow-update</command> option include the + address of a slave + server which performs forwarding of dynamic updates, the master can + be + trivially attacked by sending the update to the slave, which will + forward it to the master with its own source IP address causing the + master to approve it without question. + </para> + + <para> + For these reasons, we strongly recommend that updates be + cryptographically authenticated by means of transaction signatures + (TSIG). That is, the <command>allow-update</command> + option should + list only TSIG key names, not IP addresses or network + prefixes. Alternatively, the new <command>update-policy</command> + option can be used. + </para> + + <para> + Some sites choose to keep all dynamically-updated DNS data + in a subdomain and delegate that subdomain to a separate zone. This + way, the top-level zone containing critical data such as the IP + addresses + of public web and mail servers need not allow dynamic update at + all. + </para> + + </sect1> + </chapter> + + <chapter id="Bv9ARM.ch08"> + <title>Troubleshooting</title> + <sect1> + <title>Common Problems</title> + <sect2> + <title>It's not working; how can I figure out what's wrong?</title> + + <para> + The best solution to solving installation and + configuration issues is to take preventative measures by setting + up logging files beforehand. The log files provide a + source of hints and information that can be used to figure out + what went wrong and how to fix the problem. + </para> + + </sect2> + </sect1> + <sect1> + <title>Incrementing and Changing the Serial Number</title> + + <para> + Zone serial numbers are just numbers — they aren't + date related. A lot of people set them to a number that + represents a date, usually of the form YYYYMMDDRR. + Occasionally they will make a mistake and set them to a + "date in the future" then try to correct them by setting + them to the "current date". This causes problems because + serial numbers are used to indicate that a zone has been + updated. If the serial number on the slave server is + lower than the serial number on the master, the slave + server will attempt to update its copy of the zone. + </para> + + <para> + Setting the serial number to a lower number on the master + server than the slave server means that the slave will not perform + updates to its copy of the zone. + </para> + + <para> + The solution to this is to add 2147483647 (2^31-1) to the + number, reload the zone and make sure all slaves have updated to + the new zone serial number, then reset the number to what you want + it to be, and reload the zone again. + </para> + + </sect1> + <sect1> + <title>Where Can I Get Help?</title> + + <para> + The Internet Systems Consortium + (<acronym>ISC</acronym>) offers a wide range + of support and service agreements for <acronym>BIND</acronym> and <acronym>DHCP</acronym> servers. Four + levels of premium support are available and each level includes + support for all <acronym>ISC</acronym> programs, + significant discounts on products + and training, and a recognized priority on bug fixes and + non-funded feature requests. In addition, <acronym>ISC</acronym> offers a standard + support agreement package which includes services ranging from bug + fix announcements to remote support. It also includes training in + <acronym>BIND</acronym> and <acronym>DHCP</acronym>. + </para> + + <para> + To discuss arrangements for support, contact + <ulink url="mailto:info@isc.org">info@isc.org</ulink> or visit the + <acronym>ISC</acronym> web page at + <ulink url="http://www.isc.org/services/support/" + >http://www.isc.org/services/support/</ulink> + to read more. + </para> + </sect1> + </chapter> + <appendix id="Bv9ARM.ch09"> + <title>Appendices</title> + <sect1> + <title>Acknowledgments</title> + <sect2 id="historical_dns_information"> + <title>A Brief History of the <acronym>DNS</acronym> and <acronym>BIND</acronym></title> + + <para> + Although the "official" beginning of the Domain Name + System occurred in 1984 with the publication of RFC 920, the + core of the new system was described in 1983 in RFCs 882 and + 883. From 1984 to 1987, the ARPAnet (the precursor to today's + Internet) became a testbed of experimentation for developing the + new naming/addressing scheme in a rapidly expanding, + operational network environment. New RFCs were written and + published in 1987 that modified the original documents to + incorporate improvements based on the working model. RFC 1034, + "Domain Names-Concepts and Facilities", and RFC 1035, "Domain + Names-Implementation and Specification" were published and + became the standards upon which all <acronym>DNS</acronym> implementations are + built. + </para> + + <para> + The first working domain name server, called "Jeeves", was + written in 1983-84 by Paul Mockapetris for operation on DEC + Tops-20 + machines located at the University of Southern California's + Information + Sciences Institute (USC-ISI) and SRI International's Network + Information + Center (SRI-NIC). A <acronym>DNS</acronym> server for + Unix machines, the Berkeley Internet + Name Domain (<acronym>BIND</acronym>) package, was + written soon after by a group of + graduate students at the University of California at Berkeley + under + a grant from the US Defense Advanced Research Projects + Administration + (DARPA). + </para> + <para> + Versions of <acronym>BIND</acronym> through + 4.8.3 were maintained by the Computer + Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark + Painter, David Riggle and Songnian Zhou made up the initial <acronym>BIND</acronym> + project team. After that, additional work on the software package + was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment + Corporation + employee on loan to the CSRG, worked on <acronym>BIND</acronym> for 2 years, from 1985 + to 1987. Many other people also contributed to <acronym>BIND</acronym> development + during that time: Doug Kingston, Craig Partridge, Smoot + Carl-Mitchell, + Mike Muuss, Jim Bloom and Mike Schwartz. <acronym>BIND</acronym> maintenance was subsequently + handled by Mike Karels and Øivind Kure. + </para> + <para> + <acronym>BIND</acronym> versions 4.9 and 4.9.1 were + released by Digital Equipment + Corporation (now Compaq Computer Corporation). Paul Vixie, then + a DEC employee, became <acronym>BIND</acronym>'s + primary caretaker. He was assisted + by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan + Beecher, Andrew + Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat + Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe + Wolfhugel, and others. + </para> + <para> + In 1994, <acronym>BIND</acronym> version 4.9.2 was sponsored by + Vixie Enterprises. Paul + Vixie became <acronym>BIND</acronym>'s principal + architect/programmer. + </para> + <para> + <acronym>BIND</acronym> versions from 4.9.3 onward + have been developed and maintained + by the Internet Systems Consortium and its predecessor, + the Internet Software Consortium, with support being provided + by ISC's sponsors. + </para> + <para> + As co-architects/programmers, Bob Halley and + Paul Vixie released the first production-ready version of + <acronym>BIND</acronym> version 8 in May 1997. + </para> + <para> + BIND version 9 was released in September 2000 and is a + major rewrite of nearly all aspects of the underlying + BIND architecture. + </para> + <para> + BIND version 4 is officially deprecated and BIND version + 8 development is considered maintenance-only in favor + of BIND version 9. No additional development is done + on BIND version 4 or BIND version 8 other than for + security-related patches. + </para> + <para> + <acronym>BIND</acronym> development work is made + possible today by the sponsorship + of several corporations, and by the tireless work efforts of + numerous individuals. + </para> + </sect2> + </sect1> + <sect1> + <title>General <acronym>DNS</acronym> Reference Information</title> + <sect2 id="ipv6addresses"> + <title>IPv6 addresses (AAAA)</title> + <para> + IPv6 addresses are 128-bit identifiers for interfaces and + sets of interfaces which were introduced in the <acronym>DNS</acronym> to facilitate + scalable Internet routing. There are three types of addresses: <emphasis>Unicast</emphasis>, + an identifier for a single interface; + <emphasis>Anycast</emphasis>, + an identifier for a set of interfaces; and <emphasis>Multicast</emphasis>, + an identifier for a set of interfaces. Here we describe the global + Unicast address scheme. For more information, see RFC 3587, + "Global Unicast Address Format." + </para> + <para> + IPv6 unicast addresses consist of a + <emphasis>global routing prefix</emphasis>, a + <emphasis>subnet identifier</emphasis>, and an + <emphasis>interface identifier</emphasis>. + </para> + <para> + The global routing prefix is provided by the + upstream provider or ISP, and (roughly) corresponds to the + IPv4 <emphasis>network</emphasis> section + of the address range. + + The subnet identifier is for local subnetting, much the + same as subnetting an + IPv4 /16 network into /24 subnets. + + The interface identifier is the address of an individual + interface on a given network; in IPv6, addresses belong to + interfaces rather than to machines. + </para> + <para> + The subnetting capability of IPv6 is much more flexible than + that of IPv4: subnetting can be carried out on bit boundaries, + in much the same way as Classless InterDomain Routing + (CIDR), and the DNS PTR representation ("nibble" format) + makes setting up reverse zones easier. + </para> + <para> + The Interface Identifier must be unique on the local link, + and is usually generated automatically by the IPv6 + implementation, although it is usually possible to + override the default setting if necessary. A typical IPv6 + address might look like: + <command>2001:db8:201:9:a00:20ff:fe81:2b32</command> + </para> + <para> + IPv6 address specifications often contain long strings + of zeros, so the architects have included a shorthand for + specifying + them. The double colon (`::') indicates the longest possible + string + of zeros that can fit, and can be used only once in an address. + </para> + </sect2> + </sect1> + <sect1 id="bibliography"> + <title>Bibliography (and Suggested Reading)</title> + <sect2 id="rfcs"> + <title>Request for Comments (RFCs)</title> + <para> + Specification documents for the Internet protocol suite, including + the <acronym>DNS</acronym>, are published as part of + the Request for Comments (RFCs) + series of technical notes. The standards themselves are defined + by the Internet Engineering Task Force (IETF) and the Internet + Engineering Steering Group (IESG). RFCs can be obtained online via FTP at: + </para> + <para> + <ulink url="ftp://www.isi.edu/in-notes/"> + ftp://www.isi.edu/in-notes/RFC<replaceable>xxxx</replaceable>.txt + </ulink> + </para> + <para> + (where <replaceable>xxxx</replaceable> is + the number of the RFC). RFCs are also available via the Web at: + </para> + <para> + <ulink url="http://www.ietf.org/rfc/" + >http://www.ietf.org/rfc/</ulink>. + </para> + <bibliography> + <bibliodiv> + <!-- one of (BIBLIOENTRY BIBLIOMIXED) --> + <title>Standards</title> + <biblioentry> + <abbrev>RFC974</abbrev> + <author> + <surname>Partridge</surname> + <firstname>C.</firstname> + </author> + <title>Mail Routing and the Domain System</title> + <pubdate>January 1986</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1034</abbrev> + <author> + <surname>Mockapetris</surname> + <firstname>P.V.</firstname> + </author> + <title>Domain Names — Concepts and Facilities</title> + <pubdate>November 1987</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1035</abbrev> + <author> + <surname>Mockapetris</surname> + <firstname>P. V.</firstname> + </author> <title>Domain Names — Implementation and + Specification</title> + <pubdate>November 1987</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv id="proposed_standards" xreflabel="Proposed Standards"> + + <title>Proposed Standards</title> + <!-- one of (BIBLIOENTRY BIBLIOMIXED) --> + <biblioentry> + <abbrev>RFC2181</abbrev> + <author> + <surname>Elz</surname> + <firstname>R., R. Bush</firstname> + </author> + <title>Clarifications to the <acronym>DNS</acronym> + Specification</title> + <pubdate>July 1997</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2308</abbrev> + <author> + <surname>Andrews</surname> + <firstname>M.</firstname> + </author> + <title>Negative Caching of <acronym>DNS</acronym> + Queries</title> + <pubdate>March 1998</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1995</abbrev> + <author> + <surname>Ohta</surname> + <firstname>M.</firstname> + </author> + <title>Incremental Zone Transfer in <acronym>DNS</acronym></title> + <pubdate>August 1996</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1996</abbrev> + <author> + <surname>Vixie</surname> + <firstname>P.</firstname> + </author> + <title>A Mechanism for Prompt Notification of Zone Changes</title> + <pubdate>August 1996</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2136</abbrev> + <authorgroup> + <author> + <surname>Vixie</surname> + <firstname>P.</firstname> + </author> + <author> + <firstname>S.</firstname> + <surname>Thomson</surname> + </author> + <author> + <firstname>Y.</firstname> + <surname>Rekhter</surname> + </author> + <author> + <firstname>J.</firstname> + <surname>Bound</surname> + </author> + </authorgroup> + <title>Dynamic Updates in the Domain Name System</title> + <pubdate>April 1997</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2671</abbrev> + <authorgroup> + <author> + <firstname>P.</firstname> + <surname>Vixie</surname> + </author> + </authorgroup> + <title>Extension Mechanisms for DNS (EDNS0)</title> + <pubdate>August 1997</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2672</abbrev> + <authorgroup> + <author> + <firstname>M.</firstname> + <surname>Crawford</surname> + </author> + </authorgroup> + <title>Non-Terminal DNS Name Redirection</title> + <pubdate>August 1999</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2845</abbrev> + <authorgroup> + <author> + <surname>Vixie</surname> + <firstname>P.</firstname> + </author> + <author> + <firstname>O.</firstname> + <surname>Gudmundsson</surname> + </author> + <author> + <firstname>D.</firstname> + <surname>Eastlake</surname> + <lineage>3rd</lineage> + </author> + <author> + <firstname>B.</firstname> + <surname>Wellington</surname> + </author> + </authorgroup> + <title>Secret Key Transaction Authentication for <acronym>DNS</acronym> (TSIG)</title> + <pubdate>May 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2930</abbrev> + <authorgroup> + <author> + <firstname>D.</firstname> + <surname>Eastlake</surname> + <lineage>3rd</lineage> + </author> + </authorgroup> + <title>Secret Key Establishment for DNS (TKEY RR)</title> + <pubdate>September 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2931</abbrev> + <authorgroup> + <author> + <firstname>D.</firstname> + <surname>Eastlake</surname> + <lineage>3rd</lineage> + </author> + </authorgroup> + <title>DNS Request and Transaction Signatures (SIG(0)s)</title> + <pubdate>September 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3007</abbrev> + <authorgroup> + <author> + <firstname>B.</firstname> + <surname>Wellington</surname> + </author> + </authorgroup> + <title>Secure Domain Name System (DNS) Dynamic Update</title> + <pubdate>November 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3645</abbrev> + <authorgroup> + <author> + <firstname>S.</firstname> + <surname>Kwan</surname> + </author> + <author> + <firstname>P.</firstname> + <surname>Garg</surname> + </author> + <author> + <firstname>J.</firstname> + <surname>Gilroy</surname> + </author> + <author> + <firstname>L.</firstname> + <surname>Esibov</surname> + </author> + <author> + <firstname>J.</firstname> + <surname>Westhead</surname> + </author> + <author> + <firstname>R.</firstname> + <surname>Hall</surname> + </author> + </authorgroup> + <title>Generic Security Service Algorithm for Secret + Key Transaction Authentication for DNS + (GSS-TSIG)</title> + <pubdate>October 2003</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title><acronym>DNS</acronym> Security Proposed Standards</title> + <biblioentry> + <abbrev>RFC3225</abbrev> + <authorgroup> + <author> + <firstname>D.</firstname> + <surname>Conrad</surname> + </author> + </authorgroup> + <title>Indicating Resolver Support of DNSSEC</title> + <pubdate>December 2001</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3833</abbrev> + <authorgroup> + <author> + <firstname>D.</firstname> + <surname>Atkins</surname> + </author> + <author> + <firstname>R.</firstname> + <surname>Austein</surname> + </author> + </authorgroup> + <title>Threat Analysis of the Domain Name System (DNS)</title> + <pubdate>August 2004</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC4033</abbrev> + <authorgroup> + <author> + <firstname>R.</firstname> + <surname>Arends</surname> + </author> + <author> + <firstname>R.</firstname> + <surname>Austein</surname> + </author> + <author> + <firstname>M.</firstname> + <surname>Larson</surname> + </author> + <author> + <firstname>D.</firstname> + <surname>Massey</surname> + </author> + <author> + <firstname>S.</firstname> + <surname>Rose</surname> + </author> + </authorgroup> + <title>DNS Security Introduction and Requirements</title> + <pubdate>March 2005</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC4044</abbrev> + <authorgroup> + <author> + <firstname>R.</firstname> + <surname>Arends</surname> + </author> + <author> + <firstname>R.</firstname> + <surname>Austein</surname> + </author> + <author> + <firstname>M.</firstname> + <surname>Larson</surname> + </author> + <author> + <firstname>D.</firstname> + <surname>Massey</surname> + </author> + <author> + <firstname>S.</firstname> + <surname>Rose</surname> + </author> + </authorgroup> + <title>Resource Records for the DNS Security Extensions</title> + <pubdate>March 2005</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC4035</abbrev> + <authorgroup> + <author> + <firstname>R.</firstname> + <surname>Arends</surname> + </author> + <author> + <firstname>R.</firstname> + <surname>Austein</surname> + </author> + <author> + <firstname>M.</firstname> + <surname>Larson</surname> + </author> + <author> + <firstname>D.</firstname> + <surname>Massey</surname> + </author> + <author> + <firstname>S.</firstname> + <surname>Rose</surname> + </author> + </authorgroup> + <title>Protocol Modifications for the DNS + Security Extensions</title> + <pubdate>March 2005</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title>Other Important RFCs About <acronym>DNS</acronym> + Implementation</title> + <biblioentry> + <abbrev>RFC1535</abbrev> + <author> + <surname>Gavron</surname> + <firstname>E.</firstname> + </author> + <title>A Security Problem and Proposed Correction With Widely + Deployed <acronym>DNS</acronym> Software.</title> + <pubdate>October 1993</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1536</abbrev> + <authorgroup> + <author> + <surname>Kumar</surname> + <firstname>A.</firstname> + </author> + <author> + <firstname>J.</firstname> + <surname>Postel</surname> + </author> + <author> + <firstname>C.</firstname> + <surname>Neuman</surname> + </author> + <author> + <firstname>P.</firstname> + <surname>Danzig</surname> + </author> + <author> + <firstname>S.</firstname> + <surname>Miller</surname> + </author> + </authorgroup> + <title>Common <acronym>DNS</acronym> Implementation + Errors and Suggested Fixes</title> + <pubdate>October 1993</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1982</abbrev> + <authorgroup> + <author> + <surname>Elz</surname> + <firstname>R.</firstname> + </author> + <author> + <firstname>R.</firstname> + <surname>Bush</surname> + </author> + </authorgroup> + <title>Serial Number Arithmetic</title> + <pubdate>August 1996</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC4074</abbrev> + <authorgroup> + <author> + <surname>Morishita</surname> + <firstname>Y.</firstname> + </author> + <author> + <firstname>T.</firstname> + <surname>Jinmei</surname> + </author> + </authorgroup> + <title>Common Misbehaviour Against <acronym>DNS</acronym> + Queries for IPv6 Addresses</title> + <pubdate>May 2005</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title>Resource Record Types</title> + <biblioentry> + <abbrev>RFC1183</abbrev> + <authorgroup> + <author> + <surname>Everhart</surname> + <firstname>C.F.</firstname> + </author> + <author> + <firstname>L. A.</firstname> + <surname>Mamakos</surname> + </author> + <author> + <firstname>R.</firstname> + <surname>Ullmann</surname> + </author> + <author> + <firstname>P.</firstname> + <surname>Mockapetris</surname> + </author> + </authorgroup> + <title>New <acronym>DNS</acronym> RR Definitions</title> + <pubdate>October 1990</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1706</abbrev> + <authorgroup> + <author> + <surname>Manning</surname> + <firstname>B.</firstname> + </author> + <author> + <firstname>R.</firstname> + <surname>Colella</surname> + </author> + </authorgroup> + <title><acronym>DNS</acronym> NSAP Resource Records</title> + <pubdate>October 1994</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2168</abbrev> + <authorgroup> + <author> + <surname>Daniel</surname> + <firstname>R.</firstname> + </author> + <author> + <firstname>M.</firstname> + <surname>Mealling</surname> + </author> + </authorgroup> + <title>Resolution of Uniform Resource Identifiers using + the Domain Name System</title> + <pubdate>June 1997</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1876</abbrev> + <authorgroup> + <author> + <surname>Davis</surname> + <firstname>C.</firstname> + </author> + <author> + <firstname>P.</firstname> + <surname>Vixie</surname> + </author> + <author> + <firstname>T.</firstname> + <firstname>Goodwin</firstname> + </author> + <author> + <firstname>I.</firstname> + <surname>Dickinson</surname> + </author> + </authorgroup> + <title>A Means for Expressing Location Information in the + Domain + Name System</title> + <pubdate>January 1996</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2052</abbrev> + <authorgroup> + <author> + <surname>Gulbrandsen</surname> + <firstname>A.</firstname> + </author> + <author> + <firstname>P.</firstname> + <surname>Vixie</surname> + </author> + </authorgroup> + <title>A <acronym>DNS</acronym> RR for Specifying the + Location of + Services.</title> + <pubdate>October 1996</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2163</abbrev> + <author> + <surname>Allocchio</surname> + <firstname>A.</firstname> + </author> + <title>Using the Internet <acronym>DNS</acronym> to + Distribute MIXER + Conformant Global Address Mapping</title> + <pubdate>January 1998</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2230</abbrev> + <author> + <surname>Atkinson</surname> + <firstname>R.</firstname> + </author> + <title>Key Exchange Delegation Record for the <acronym>DNS</acronym></title> + <pubdate>October 1997</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2536</abbrev> + <author> + <surname>Eastlake</surname> + <firstname>D.</firstname> + <lineage>3rd</lineage> + </author> + <title>DSA KEYs and SIGs in the Domain Name System (DNS)</title> + <pubdate>March 1999</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2537</abbrev> + <author> + <surname>Eastlake</surname> + <firstname>D.</firstname> + <lineage>3rd</lineage> + </author> + <title>RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)</title> + <pubdate>March 1999</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2538</abbrev> + <authorgroup> + <author> + <surname>Eastlake</surname> + <firstname>D.</firstname> + <lineage>3rd</lineage> + </author> + <author> + <surname>Gudmundsson</surname> + <firstname>O.</firstname> + </author> + </authorgroup> + <title>Storing Certificates in the Domain Name System (DNS)</title> + <pubdate>March 1999</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2539</abbrev> + <authorgroup> + <author> + <surname>Eastlake</surname> + <firstname>D.</firstname> + <lineage>3rd</lineage> + </author> + </authorgroup> + <title>Storage of Diffie-Hellman Keys in the Domain Name System (DNS)</title> + <pubdate>March 1999</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2540</abbrev> + <authorgroup> + <author> + <surname>Eastlake</surname> + <firstname>D.</firstname> + <lineage>3rd</lineage> + </author> + </authorgroup> + <title>Detached Domain Name System (DNS) Information</title> + <pubdate>March 1999</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2782</abbrev> + <author> + <surname>Gulbrandsen</surname> + <firstname>A.</firstname> + </author> + <author> + <surname>Vixie</surname> + <firstname>P.</firstname> + </author> + <author> + <surname>Esibov</surname> + <firstname>L.</firstname> + </author> + <title>A DNS RR for specifying the location of services (DNS SRV)</title> + <pubdate>February 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2915</abbrev> + <author> + <surname>Mealling</surname> + <firstname>M.</firstname> + </author> + <author> + <surname>Daniel</surname> + <firstname>R.</firstname> + </author> + <title>The Naming Authority Pointer (NAPTR) DNS Resource Record</title> + <pubdate>September 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3110</abbrev> + <author> + <surname>Eastlake</surname> + <firstname>D.</firstname> + <lineage>3rd</lineage> + </author> + <title>RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</title> + <pubdate>May 2001</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3123</abbrev> + <author> + <surname>Koch</surname> + <firstname>P.</firstname> + </author> + <title>A DNS RR Type for Lists of Address Prefixes (APL RR)</title> + <pubdate>June 2001</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3596</abbrev> + <authorgroup> + <author> + <surname>Thomson</surname> + <firstname>S.</firstname> + </author> + <author> + <firstname>C.</firstname> + <surname>Huitema</surname> + </author> + <author> + <firstname>V.</firstname> + <surname>Ksinant</surname> + </author> + <author> + <firstname>M.</firstname> + <surname>Souissi</surname> + </author> + </authorgroup> + <title><acronym>DNS</acronym> Extensions to support IP + version 6</title> + <pubdate>October 2003</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3597</abbrev> + <author> + <surname>Gustafsson</surname> + <firstname>A.</firstname> + </author> + <title>Handling of Unknown DNS Resource Record (RR) Types</title> + <pubdate>September 2003</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title><acronym>DNS</acronym> and the Internet</title> + <biblioentry> + <abbrev>RFC1101</abbrev> + <author> + <surname>Mockapetris</surname> + <firstname>P. V.</firstname> + </author> + <title><acronym>DNS</acronym> Encoding of Network Names + and Other Types</title> + <pubdate>April 1989</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1123</abbrev> + <author> + <surname>Braden</surname> + <surname>R.</surname> + </author> + <title>Requirements for Internet Hosts - Application and + Support</title> + <pubdate>October 1989</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1591</abbrev> + <author> + <surname>Postel</surname> + <firstname>J.</firstname> + </author> + <title>Domain Name System Structure and Delegation</title> + <pubdate>March 1994</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2317</abbrev> + <authorgroup> + <author> + <surname>Eidnes</surname> + <firstname>H.</firstname> + </author> + <author> + <firstname>G.</firstname> + <surname>de Groot</surname> + </author> + <author> + <firstname>P.</firstname> + <surname>Vixie</surname> + </author> + </authorgroup> + <title>Classless IN-ADDR.ARPA Delegation</title> + <pubdate>March 1998</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2826</abbrev> + <authorgroup> + <author> + <surname>Internet Architecture Board</surname> + </author> + </authorgroup> + <title>IAB Technical Comment on the Unique DNS Root</title> + <pubdate>May 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2929</abbrev> + <authorgroup> + <author> + <surname>Eastlake</surname> + <firstname>D.</firstname> + <lineage>3rd</lineage> + </author> + <author> + <surname>Brunner-Williams</surname> + <firstname>E.</firstname> + </author> + <author> + <surname>Manning</surname> + <firstname>B.</firstname> + </author> + </authorgroup> + <title>Domain Name System (DNS) IANA Considerations</title> + <pubdate>September 2000</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title><acronym>DNS</acronym> Operations</title> + <biblioentry> + <abbrev>RFC1033</abbrev> + <author> + <surname>Lottor</surname> + <firstname>M.</firstname> + </author> + <title>Domain administrators operations guide.</title> + <pubdate>November 1987</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1537</abbrev> + <author> + <surname>Beertema</surname> + <firstname>P.</firstname> + </author> + <title>Common <acronym>DNS</acronym> Data File + Configuration Errors</title> + <pubdate>October 1993</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1912</abbrev> + <author> + <surname>Barr</surname> + <firstname>D.</firstname> + </author> + <title>Common <acronym>DNS</acronym> Operational and + Configuration Errors</title> + <pubdate>February 1996</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2010</abbrev> + <authorgroup> + <author> + <surname>Manning</surname> + <firstname>B.</firstname> + </author> + <author> + <firstname>P.</firstname> + <surname>Vixie</surname> + </author> + </authorgroup> + <title>Operational Criteria for Root Name Servers.</title> + <pubdate>October 1996</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2219</abbrev> + <authorgroup> + <author> + <surname>Hamilton</surname> + <firstname>M.</firstname> + </author> + <author> + <firstname>R.</firstname> + <surname>Wright</surname> + </author> + </authorgroup> + <title>Use of <acronym>DNS</acronym> Aliases for + Network Services.</title> + <pubdate>October 1997</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title>Internationalized Domain Names</title> + <biblioentry> + <abbrev>RFC2825</abbrev> + <authorgroup> + <author> + <surname>IAB</surname> + </author> + <author> + <surname>Daigle</surname> + <firstname>R.</firstname> + </author> + </authorgroup> + <title>A Tangled Web: Issues of I18N, Domain Names, + and the Other Internet protocols</title> + <pubdate>May 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3490</abbrev> + <authorgroup> + <author> + <surname>Faltstrom</surname> + <firstname>P.</firstname> + </author> + <author> + <surname>Hoffman</surname> + <firstname>P.</firstname> + </author> + <author> + <surname>Costello</surname> + <firstname>A.</firstname> + </author> + </authorgroup> + <title>Internationalizing Domain Names in Applications (IDNA)</title> + <pubdate>March 2003</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3491</abbrev> + <authorgroup> + <author> + <surname>Hoffman</surname> + <firstname>P.</firstname> + </author> + <author> + <surname>Blanchet</surname> + <firstname>M.</firstname> + </author> + </authorgroup> + <title>Nameprep: A Stringprep Profile for Internationalized Domain Names</title> + <pubdate>March 2003</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3492</abbrev> + <authorgroup> + <author> + <surname>Costello</surname> + <firstname>A.</firstname> + </author> + </authorgroup> + <title>Punycode: A Bootstring encoding of Unicode + for Internationalized Domain Names in + Applications (IDNA)</title> + <pubdate>March 2003</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title>Other <acronym>DNS</acronym>-related RFCs</title> + <note> + <para> + Note: the following list of RFCs, although + <acronym>DNS</acronym>-related, are not + concerned with implementing software. + </para> + </note> + <biblioentry> + <abbrev>RFC1464</abbrev> + <author> + <surname>Rosenbaum</surname> + <firstname>R.</firstname> + </author> + <title>Using the Domain Name System To Store Arbitrary String + Attributes</title> + <pubdate>May 1993</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1713</abbrev> + <author> + <surname>Romao</surname> + <firstname>A.</firstname> + </author> + <title>Tools for <acronym>DNS</acronym> Debugging</title> + <pubdate>November 1994</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC1794</abbrev> + <author> + <surname>Brisco</surname> + <firstname>T.</firstname> + </author> + <title><acronym>DNS</acronym> Support for Load + Balancing</title> + <pubdate>April 1995</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2240</abbrev> + <author> + <surname>Vaughan</surname> + <firstname>O.</firstname> + </author> + <title>A Legal Basis for Domain Name Allocation</title> + <pubdate>November 1997</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2345</abbrev> + <authorgroup> + <author> + <surname>Klensin</surname> + <firstname>J.</firstname> + </author> + <author> + <firstname>T.</firstname> + <surname>Wolf</surname> + </author> + <author> + <firstname>G.</firstname> + <surname>Oglesby</surname> + </author> + </authorgroup> + <title>Domain Names and Company Name Retrieval</title> + <pubdate>May 1998</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2352</abbrev> + <author> + <surname>Vaughan</surname> + <firstname>O.</firstname> + </author> + <title>A Convention For Using Legal Names as Domain Names</title> + <pubdate>May 1998</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3071</abbrev> + <authorgroup> + <author> + <surname>Klensin</surname> + <firstname>J.</firstname> + </author> + </authorgroup> + <title>Reflections on the DNS, RFC 1591, and Categories of Domains</title> + <pubdate>February 2001</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3258</abbrev> + <authorgroup> + <author> + <surname>Hardie</surname> + <firstname>T.</firstname> + </author> + </authorgroup> + <title>Distributing Authoritative Name Servers via + Shared Unicast Addresses</title> + <pubdate>April 2002</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3901</abbrev> + <authorgroup> + <author> + <surname>Durand</surname> + <firstname>A.</firstname> + </author> + <author> + <firstname>J.</firstname> + <surname>Ihren</surname> + </author> + </authorgroup> + <title>DNS IPv6 Transport Operational Guidelines</title> + <pubdate>September 2004</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title>Obsolete and Unimplemented Experimental RFC</title> + <biblioentry> + <abbrev>RFC1712</abbrev> + <authorgroup> + <author> + <surname>Farrell</surname> + <firstname>C.</firstname> + </author> + <author> + <firstname>M.</firstname> + <surname>Schulze</surname> + </author> + <author> + <firstname>S.</firstname> + <surname>Pleitner</surname> + </author> + <author> + <firstname>D.</firstname> + <surname>Baldoni</surname> + </author> + </authorgroup> + <title><acronym>DNS</acronym> Encoding of Geographical + Location</title> + <pubdate>November 1994</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2673</abbrev> + <authorgroup> + <author> + <surname>Crawford</surname> + <firstname>M.</firstname> + </author> + </authorgroup> + <title>Binary Labels in the Domain Name System</title> + <pubdate>August 1999</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2874</abbrev> + <authorgroup> + <author> + <surname>Crawford</surname> + <firstname>M.</firstname> + </author> + <author> + <surname>Huitema</surname> + <firstname>C.</firstname> + </author> + </authorgroup> + <title>DNS Extensions to Support IPv6 Address Aggregation + and Renumbering</title> + <pubdate>July 2000</pubdate> + </biblioentry> + </bibliodiv> + <bibliodiv> + <title>Obsoleted DNS Security RFCs</title> + <note> + <para> + Most of these have been consolidated into RFC4033, + RFC4034 and RFC4035 which collectively describe DNSSECbis. + </para> + </note> + <biblioentry> + <abbrev>RFC2065</abbrev> + <authorgroup> + <author> + <surname>Eastlake</surname> + <lineage>3rd</lineage> + <firstname>D.</firstname> + </author> + <author> + <firstname>C.</firstname> + <surname>Kaufman</surname> + </author> + </authorgroup> + <title>Domain Name System Security Extensions</title> + <pubdate>January 1997</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2137</abbrev> + <author> + <surname>Eastlake</surname> + <lineage>3rd</lineage> + <firstname>D.</firstname> + </author> + <title>Secure Domain Name System Dynamic Update</title> + <pubdate>April 1997</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC2535</abbrev> + <authorgroup> + <author> + <surname>Eastlake</surname> + <lineage>3rd</lineage> + <firstname>D.</firstname> + </author> + </authorgroup> + <title>Domain Name System Security Extensions</title> + <pubdate>March 1999</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3008</abbrev> + <authorgroup> + <author> + <surname>Wellington</surname> + <firstname>B.</firstname> + </author> + </authorgroup> + <title>Domain Name System Security (DNSSEC) + Signing Authority</title> + <pubdate>November 2000</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3090</abbrev> + <authorgroup> + <author> + <surname>Lewis</surname> + <firstname>E.</firstname> + </author> + </authorgroup> + <title>DNS Security Extension Clarification on Zone Status</title> + <pubdate>March 2001</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3445</abbrev> + <authorgroup> + <author> + <surname>Massey</surname> + <firstname>D.</firstname> + </author> + <author> + <surname>Rose</surname> + <firstname>S.</firstname> + </author> + </authorgroup> + <title>Limiting the Scope of the KEY Resource Record (RR)</title> + <pubdate>December 2002</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3655</abbrev> + <authorgroup> + <author> + <surname>Wellington</surname> + <firstname>B.</firstname> + </author> + <author> + <surname>Gudmundsson</surname> + <firstname>O.</firstname> + </author> + </authorgroup> + <title>Redefinition of DNS Authenticated Data (AD) bit</title> + <pubdate>November 2003</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3658</abbrev> + <authorgroup> + <author> + <surname>Gudmundsson</surname> + <firstname>O.</firstname> + </author> + </authorgroup> + <title>Delegation Signer (DS) Resource Record (RR)</title> + <pubdate>December 2003</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3755</abbrev> + <authorgroup> + <author> + <surname>Weiler</surname> + <firstname>S.</firstname> + </author> + </authorgroup> + <title>Legacy Resolver Compatibility for Delegation Signer (DS)</title> + <pubdate>May 2004</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3757</abbrev> + <authorgroup> + <author> + <surname>Kolkman</surname> + <firstname>O.</firstname> + </author> + <author> + <surname>Schlyter</surname> + <firstname>J.</firstname> + </author> + <author> + <surname>Lewis</surname> + <firstname>E.</firstname> + </author> + </authorgroup> + <title>Domain Name System KEY (DNSKEY) Resource Record + (RR) Secure Entry Point (SEP) Flag</title> + <pubdate>April 2004</pubdate> + </biblioentry> + <biblioentry> + <abbrev>RFC3845</abbrev> + <authorgroup> + <author> + <surname>Schlyter</surname> + <firstname>J.</firstname> + </author> + </authorgroup> + <title>DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format</title> + <pubdate>August 2004</pubdate> + </biblioentry> + </bibliodiv> + </bibliography> + </sect2> + <sect2 id="internet_drafts"> + <title>Internet Drafts</title> + <para> + Internet Drafts (IDs) are rough-draft working documents of + the Internet Engineering Task Force. They are, in essence, RFCs + in the preliminary stages of development. Implementors are + cautioned not + to regard IDs as archival, and they should not be quoted or cited + in any formal documents unless accompanied by the disclaimer that + they are "works in progress." IDs have a lifespan of six months + after which they are deleted unless updated by their authors. + </para> + </sect2> + <sect2> + <title>Other Documents About <acronym>BIND</acronym></title> + <para/> + <bibliography> + <biblioentry> + <authorgroup> + <author> + <surname>Albitz</surname> + <firstname>Paul</firstname> + </author> + <author> + <firstname>Cricket</firstname> + <surname>Liu</surname> + </author> + </authorgroup> + <title><acronym>DNS</acronym> and <acronym>BIND</acronym></title> + <copyright> + <year>1998</year> + <holder>Sebastopol, CA: O'Reilly and Associates</holder> + </copyright> + </biblioentry> + </bibliography> + </sect2> + </sect1> + </appendix> + + <reference id="Bv9ARM.ch10"> + <title>Manual pages</title> + <xi:include href="../../bin/dig/dig.docbook"/> + <xi:include href="../../bin/dig/host.docbook"/> + <xi:include href="../../bin/dnssec/dnssec-keygen.docbook"/> + <xi:include href="../../bin/dnssec/dnssec-signzone.docbook"/> + <xi:include href="../../bin/check/named-checkconf.docbook"/> + <xi:include href="../../bin/check/named-checkzone.docbook"/> + <xi:include href="../../bin/named/named.docbook"/> + <!-- named.conf.docbook and others? --> + <!-- nsupdate gives db2latex indigestion, markup problems? --> + <xi:include href="../../bin/rndc/rndc.docbook"/> + <xi:include href="../../bin/rndc/rndc.conf.docbook"/> + <xi:include href="../../bin/rndc/rndc-confgen.docbook"/> + </reference> + + </book> + +<!-- + - Local variables: + - mode: sgml + - End: + --> diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch03.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch03.html index af5ae435b45..c6ff6fe1d40 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch03.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch03.html @@ -1,5 +1,5 @@ <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - Permission to use, copy, modify, and distribute this software for any @@ -14,12 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $ISC: Bv9ARM.ch03.html,v 1.26.2.5.4.17 2006/06/29 13:02:31 marka Exp $ --> +<!-- $ISC: Bv9ARM.ch03.html,v 1.35.18.31 2007/10/31 01:35:57 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Chapter 3. Name Server Configuration</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="prev" href="Bv9ARM.ch02.html" title="Chapter 2. BIND Resource Requirements"> @@ -47,31 +47,37 @@ <dl> <dt><span class="sect1"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2571026">A Caching-only Name Server</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2571042">An Authoritative-only Name Server</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568004">A Caching-only Name Server</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568020">An Authoritative-only Name Server</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2571064">Load Balancing</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2571484">Name Server Operations</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568042">Load Balancing</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568465">Name Server Operations</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2571490">Tools for Use With the Name Server Daemon</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2572723">Signals</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568470">Tools for Use With the Name Server Daemon</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2570184">Signals</a></span></dt> </dl></dd> </dl> </div> -<p>In this section we provide some suggested configurations along -with guidelines for their use. We also address the topic of reasonable -option setting.</p> +<p> + In this section we provide some suggested configurations along + with guidelines for their use. We suggest reasonable values for + certain option settings. + </p> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="sample_configuration"></a>Sample Configurations</h2></div></div></div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2571026"></a>A Caching-only Name Server</h3></div></div></div> -<p>The following sample configuration is appropriate for a caching-only -name server for use by clients internal to a corporation. All queries -from outside clients are refused using the <span><strong class="command">allow-query</strong></span> -option. Alternatively, the same effect could be achieved using suitable -firewall rules.</p> +<a name="id2568004"></a>A Caching-only Name Server</h3></div></div></div> +<p> + The following sample configuration is appropriate for a caching-only + name server for use by clients internal to a corporation. All + queries + from outside clients are refused using the <span><strong class="command">allow-query</strong></span> + option. Alternatively, the same effect could be achieved using + suitable + firewall rules. + </p> <pre class="programlisting"> // Two corporate subnets we wish to allow queries from. acl corpnets { 192.168.4.0/24; 192.168.7.0/24; }; @@ -89,13 +95,16 @@ zone "0.0.127.in-addr.arpa" { </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2571042"></a>An Authoritative-only Name Server</h3></div></div></div> -<p>This sample configuration is for an authoritative-only server -that is the master server for "<code class="filename">example.com</code>" -and a slave for the subdomain "<code class="filename">eng.example.com</code>".</p> +<a name="id2568020"></a>An Authoritative-only Name Server</h3></div></div></div> +<p> + This sample configuration is for an authoritative-only server + that is the master server for "<code class="filename">example.com</code>" + and a slave for the subdomain "<code class="filename">eng.example.com</code>". + </p> <pre class="programlisting"> options { directory "/etc/namedb"; // Working directory + allow-query-cache { none; }; // Do not allow access to cache allow-query { any; }; // This is the default recursion no; // Do not provide recursive service }; @@ -128,13 +137,18 @@ zone "eng.example.com" { </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2571064"></a>Load Balancing</h2></div></div></div> -<p>A primitive form of load balancing can be achieved in -the <acronym class="acronym">DNS</acronym> by using multiple A records for one name.</p> -<p>For example, if you have three WWW servers with network addresses -of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the -following means that clients will connect to each machine one third -of the time:</p> +<a name="id2568042"></a>Load Balancing</h2></div></div></div> +<p> + A primitive form of load balancing can be achieved in + the <acronym class="acronym">DNS</acronym> by using multiple records + (such as multiple A records) for one name. + </p> +<p> + For example, if you have three WWW servers with network addresses + of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the + following means that clients will connect to each machine one third + of the time: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -145,296 +159,533 @@ of the time:</p> </colgroup> <tbody> <tr> -<td><p>Name</p></td> -<td><p>TTL</p></td> -<td><p>CLASS</p></td> -<td><p>TYPE</p></td> -<td><p>Resource Record (RR) Data</p></td> +<td> + <p> + Name + </p> + </td> +<td> + <p> + TTL + </p> + </td> +<td> + <p> + CLASS + </p> + </td> +<td> + <p> + TYPE + </p> + </td> +<td> + <p> + Resource Record (RR) Data + </p> + </td> </tr> <tr> -<td><p><code class="literal">www</code></p></td> -<td><p><code class="literal">600</code></p></td> -<td><p><code class="literal">IN</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">10.0.0.1</code></p></td> +<td> + <p> + <code class="literal">www</code> + </p> + </td> +<td> + <p> + <code class="literal">600</code> + </p> + </td> +<td> + <p> + <code class="literal">IN</code> + </p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">10.0.0.1</code> + </p> + </td> </tr> <tr> -<td><p></p></td> -<td><p><code class="literal">600</code></p></td> -<td><p><code class="literal">IN</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">10.0.0.2</code></p></td> +<td> + <p></p> + </td> +<td> + <p> + <code class="literal">600</code> + </p> + </td> +<td> + <p> + <code class="literal">IN</code> + </p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">10.0.0.2</code> + </p> + </td> </tr> <tr> -<td><p></p></td> -<td><p><code class="literal">600</code></p></td> -<td><p><code class="literal">IN</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">10.0.0.3</code></p></td> +<td> + <p></p> + </td> +<td> + <p> + <code class="literal">600</code> + </p> + </td> +<td> + <p> + <code class="literal">IN</code> + </p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">10.0.0.3</code> + </p> + </td> </tr> </tbody> </table></div> -<p>When a resolver queries for these records, <acronym class="acronym">BIND</acronym> will rotate - them and respond to the query with the records in a different - order. In the example above, clients will randomly receive - records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients - will use the first record returned and discard the rest.</p> -<p>For more detail on ordering responses, check the - <span><strong class="command">rrset-order</strong></span> substatement in the - <span><strong class="command">options</strong></span> statement, see - <a href="Bv9ARM.ch06.html#rrset_ordering">RRset Ordering</a>. - This substatement is not supported in - <acronym class="acronym">BIND</acronym> 9, and only the ordering scheme described above is - available.</p> +<p> + When a resolver queries for these records, <acronym class="acronym">BIND</acronym> will rotate + them and respond to the query with the records in a different + order. In the example above, clients will randomly receive + records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients + will use the first record returned and discard the rest. + </p> +<p> + For more detail on ordering responses, check the + <span><strong class="command">rrset-order</strong></span> substatement in the + <span><strong class="command">options</strong></span> statement, see + <a href="Bv9ARM.ch06.html#rrset_ordering">RRset Ordering</a>. + </p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2571484"></a>Name Server Operations</h2></div></div></div> +<a name="id2568465"></a>Name Server Operations</h2></div></div></div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2571490"></a>Tools for Use With the Name Server Daemon</h3></div></div></div> -<p>There are several indispensable diagnostic, administrative -and monitoring tools available to the system administrator for controlling -and debugging the name server daemon. We describe several in this -section </p> +<a name="id2568470"></a>Tools for Use With the Name Server Daemon</h3></div></div></div> +<p> + This section describes several indispensable diagnostic, + administrative and monitoring tools available to the system + administrator for controlling and debugging the name server + daemon. + </p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="diagnostic_tools"></a>Diagnostic Tools</h4></div></div></div> -<p>The <span><strong class="command">dig</strong></span>, <span><strong class="command">host</strong></span>, and -<span><strong class="command">nslookup</strong></span> programs are all command line tools -for manually querying name servers. They differ in style and -output format. -</p> +<p> + The <span><strong class="command">dig</strong></span>, <span><strong class="command">host</strong></span>, and + <span><strong class="command">nslookup</strong></span> programs are all command + line tools + for manually querying name servers. They differ in style and + output format. + </p> <div class="variablelist"><dl> <dt><span class="term"><a name="dig"></a><span><strong class="command">dig</strong></span></span></dt> <dd> -<p>The domain information groper (<span><strong class="command">dig</strong></span>) -is the most versatile and complete of these lookup tools. -It has two modes: simple interactive -mode for a single query, and batch mode which executes a query for -each in a list of several query lines. All query options are accessible -from the command line.</p> +<p> + The domain information groper (<span><strong class="command">dig</strong></span>) + is the most versatile and complete of these lookup tools. + It has two modes: simple interactive + mode for a single query, and batch mode which executes a + query for + each in a list of several query lines. All query options are + accessible + from the command line. + </p> <div class="cmdsynopsis"><p><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] <em class="replaceable"><code>domain</code></em> [<em class="replaceable"><code>query-type</code></em>] [<em class="replaceable"><code>query-class</code></em>] [+<em class="replaceable"><code>query-option</code></em>] [-<em class="replaceable"><code>dig-option</code></em>] [%<em class="replaceable"><code>comment</code></em>]</p></div> -<p>The usual simple use of dig will take the form</p> -<p><span><strong class="command">dig @server domain query-type query-class</strong></span></p> -<p>For more information and a list of available commands and -options, see the <span><strong class="command">dig</strong></span> man page.</p> +<p> + The usual simple use of dig will take the form + </p> +<p> + <span><strong class="command">dig @server domain query-type query-class</strong></span> + </p> +<p> + For more information and a list of available commands and + options, see the <span><strong class="command">dig</strong></span> man + page. + </p> </dd> <dt><span class="term"><span><strong class="command">host</strong></span></span></dt> <dd> -<p>The <span><strong class="command">host</strong></span> utility emphasizes simplicity -and ease of use. By default, it converts -between host names and Internet addresses, but its functionality -can be extended with the use of options.</p> -<div class="cmdsynopsis"><p><code class="command">host</code> [-aCdlrTwv] [-c <em class="replaceable"><code>class</code></em>] [-N <em class="replaceable"><code>ndots</code></em>] [-t <em class="replaceable"><code>type</code></em>] [-W <em class="replaceable"><code>timeout</code></em>] [-R <em class="replaceable"><code>retries</code></em>] <em class="replaceable"><code>hostname</code></em> [<em class="replaceable"><code>server</code></em>]</p></div> -<p>For more information and a list of available commands and -options, see the <span><strong class="command">host</strong></span> man page.</p> +<p> + The <span><strong class="command">host</strong></span> utility emphasizes + simplicity + and ease of use. By default, it converts + between host names and Internet addresses, but its + functionality + can be extended with the use of options. + </p> +<div class="cmdsynopsis"><p><code class="command">host</code> [-aCdlnrsTwv] [-c <em class="replaceable"><code>class</code></em>] [-N <em class="replaceable"><code>ndots</code></em>] [-t <em class="replaceable"><code>type</code></em>] [-W <em class="replaceable"><code>timeout</code></em>] [-R <em class="replaceable"><code>retries</code></em>] [-m <em class="replaceable"><code>flag</code></em>] [-4] [-6] <em class="replaceable"><code>hostname</code></em> [<em class="replaceable"><code>server</code></em>]</p></div> +<p> + For more information and a list of available commands and + options, see the <span><strong class="command">host</strong></span> man + page. + </p> </dd> <dt><span class="term"><span><strong class="command">nslookup</strong></span></span></dt> <dd> -<p><span><strong class="command">nslookup</strong></span> has two modes: interactive -and non-interactive. Interactive mode allows the user to query name servers -for information about various hosts and domains or to print a list -of hosts in a domain. Non-interactive mode is used to print just -the name and requested information for a host or domain.</p> +<p><span><strong class="command">nslookup</strong></span> + has two modes: interactive and + non-interactive. Interactive mode allows the user to + query name servers for information about various + hosts and domains or to print a list of hosts in a + domain. Non-interactive mode is used to print just + the name and requested information for a host or + domain. + </p> <div class="cmdsynopsis"><p><code class="command">nslookup</code> [-option...] [[<em class="replaceable"><code>host-to-find</code></em>] | [- [server]]]</p></div> -<p>Interactive mode is entered when no arguments are given (the -default name server will be used) or when the first argument is a -hyphen (`-') and the second argument is the host name or Internet address -of a name server.</p> -<p>Non-interactive mode is used when the name or Internet address -of the host to be looked up is given as the first argument. The -optional second argument specifies the host name or address of a name server.</p> -<p>Due to its arcane user interface and frequently inconsistent -behavior, we do not recommend the use of <span><strong class="command">nslookup</strong></span>. -Use <span><strong class="command">dig</strong></span> instead.</p> +<p> + Interactive mode is entered when no arguments are given (the + default name server will be used) or when the first argument + is a + hyphen (`-') and the second argument is the host name or + Internet address + of a name server. + </p> +<p> + Non-interactive mode is used when the name or Internet + address + of the host to be looked up is given as the first argument. + The + optional second argument specifies the host name or address + of a name server. + </p> +<p> + Due to its arcane user interface and frequently inconsistent + behavior, we do not recommend the use of <span><strong class="command">nslookup</strong></span>. + Use <span><strong class="command">dig</strong></span> instead. + </p> </dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="admin_tools"></a>Administrative Tools</h4></div></div></div> -<p>Administrative tools play an integral part in the management -of a server.</p> +<p> + Administrative tools play an integral part in the management + of a server. + </p> <div class="variablelist"><dl> <dt> <a name="named-checkconf"></a><span class="term"><span><strong class="command">named-checkconf</strong></span></span> </dt> <dd> -<p>The <span><strong class="command">named-checkconf</strong></span> program - checks the syntax of a <code class="filename">named.conf</code> file.</p> +<p> + The <span><strong class="command">named-checkconf</strong></span> program + checks the syntax of a <code class="filename">named.conf</code> file. + </p> <div class="cmdsynopsis"><p><code class="command">named-checkconf</code> [-jvz] [-t <em class="replaceable"><code>directory</code></em>] [<em class="replaceable"><code>filename</code></em>]</p></div> </dd> <dt> <a name="named-checkzone"></a><span class="term"><span><strong class="command">named-checkzone</strong></span></span> </dt> <dd> -<p>The <span><strong class="command">named-checkzone</strong></span> program checks a master file for - syntax and consistency.</p> -<div class="cmdsynopsis"><p><code class="command">named-checkzone</code> [-djqvD] [-c <em class="replaceable"><code>class</code></em>] [-o <em class="replaceable"><code>output</code></em>] [-t <em class="replaceable"><code>directory</code></em>] [-w <em class="replaceable"><code>directory</code></em>] [-k <em class="replaceable"><code>(ignore|warn|fail)</code></em>] [-n <em class="replaceable"><code>(ignore|warn|fail)</code></em>] <em class="replaceable"><code>zone</code></em> [<em class="replaceable"><code>filename</code></em>]</p></div> +<p> + The <span><strong class="command">named-checkzone</strong></span> program + checks a master file for + syntax and consistency. + </p> +<div class="cmdsynopsis"><p><code class="command">named-checkzone</code> [-djqvD] [-c <em class="replaceable"><code>class</code></em>] [-o <em class="replaceable"><code>output</code></em>] [-t <em class="replaceable"><code>directory</code></em>] [-w <em class="replaceable"><code>directory</code></em>] [-k <em class="replaceable"><code>(ignore|warn|fail)</code></em>] [-n <em class="replaceable"><code>(ignore|warn|fail)</code></em>] [-W <em class="replaceable"><code>(ignore|warn)</code></em>] <em class="replaceable"><code>zone</code></em> [<em class="replaceable"><code>filename</code></em>]</p></div> </dd> <dt> +<a name="named-compilezone"></a><span class="term"><span><strong class="command">named-compilezone</strong></span></span> +</dt> +<dd><p> + Similar to <span><strong class="command">named-checkzone,</strong></span> but + it always dumps the zone content to a specified file + (typically in a different format). + </p></dd> +<dt> <a name="rndc"></a><span class="term"><span><strong class="command">rndc</strong></span></span> </dt> <dd> -<p>The remote name daemon control - (<span><strong class="command">rndc</strong></span>) program allows the system - administrator to control the operation of a name server. - If you run <span><strong class="command">rndc</strong></span> without any options - it will display a usage message as follows:</p> +<p> + The remote name daemon control + (<span><strong class="command">rndc</strong></span>) program allows the + system + administrator to control the operation of a name server. + Since <acronym class="acronym">BIND</acronym> 9.2, <span><strong class="command">rndc</strong></span> + supports all the commands of the BIND 8 <span><strong class="command">ndc</strong></span> + utility except <span><strong class="command">ndc start</strong></span> and + <span><strong class="command">ndc restart</strong></span>, which were also + not supported in <span><strong class="command">ndc</strong></span>'s + channel mode. + If you run <span><strong class="command">rndc</strong></span> without any + options + it will display a usage message as follows: + </p> <div class="cmdsynopsis"><p><code class="command">rndc</code> [-c <em class="replaceable"><code>config</code></em>] [-s <em class="replaceable"><code>server</code></em>] [-p <em class="replaceable"><code>port</code></em>] [-y <em class="replaceable"><code>key</code></em>] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command</code></em>...]</p></div> -<p>The <span><strong class="command">command</strong></span> is one of the following:</p> +<p>The <span><strong class="command">command</strong></span> + is one of the following: + </p> <div class="variablelist"><dl> <dt><span class="term"><strong class="userinput"><code>reload</code></strong></span></dt> -<dd><p>Reload configuration file and zones.</p></dd> +<dd><p> + Reload configuration file and zones. + </p></dd> <dt><span class="term"><strong class="userinput"><code>reload <em class="replaceable"><code>zone</code></em> - [<span class="optional"><em class="replaceable"><code>class</code></em> + [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt> -<dd><p>Reload the given zone.</p></dd> +<dd><p> + Reload the given zone. + </p></dd> <dt><span class="term"><strong class="userinput"><code>refresh <em class="replaceable"><code>zone</code></em> - [<span class="optional"><em class="replaceable"><code>class</code></em> + [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt> -<dd><p>Schedule zone maintenance for the given zone.</p></dd> +<dd><p> + Schedule zone maintenance for the given zone. + </p></dd> <dt><span class="term"><strong class="userinput"><code>retransfer <em class="replaceable"><code>zone</code></em> - [<span class="optional"><em class="replaceable"><code>class</code></em> + + [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt> -<dd><p>Retransfer the given zone from the master.</p></dd> -<dt><span class="term"><strong class="userinput"><code>freeze [<span class="optional"><em class="replaceable"><code>zone</code></em> +<dd><p> + Retransfer the given zone from the master. + </p></dd> +<dt><span class="term"><strong class="userinput"><code>freeze + [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt> -<dd><p>Suspend updates to a dynamic zone. If no zone is specified, - then all zones are suspended. This allows manual - edits to be made to a zone normally updated by dynamic update. It - also causes changes in the journal file to be synced into the master - and the journal file to be removed. All dynamic update attempts will - be refused while the zone is frozen.</p></dd> -<dt><span class="term"><strong class="userinput"><code>thaw [<span class="optional"><em class="replaceable"><code>zone</code></em> +<dd><p> + Suspend updates to a dynamic zone. If no zone is + specified, + then all zones are suspended. This allows manual + edits to be made to a zone normally updated by dynamic + update. It + also causes changes in the journal file to be synced + into the master + and the journal file to be removed. All dynamic + update attempts will + be refused while the zone is frozen. + </p></dd> +<dt><span class="term"><strong class="userinput"><code>thaw + [<span class="optional"><em class="replaceable"><code>zone</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em> [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt> -<dd><p>Enable updates to a frozen dynamic zone. If no zone is - specified, then all frozen zones are enabled. This causes - the server to reload the zone from disk, and re-enables dynamic updates - after the load has completed. After a zone is thawed, dynamic updates - will no longer be refused.</p></dd> +<dd><p> + Enable updates to a frozen dynamic zone. If no zone + is + specified, then all frozen zones are enabled. This + causes + the server to reload the zone from disk, and + re-enables dynamic updates + after the load has completed. After a zone is thawed, + dynamic updates + will no longer be refused. + </p></dd> +<dt><span class="term"><strong class="userinput"><code>notify <em class="replaceable"><code>zone</code></em> + [<span class="optional"><em class="replaceable"><code>class</code></em> + [<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</code></strong></span></dt> +<dd><p> + Resend NOTIFY messages for the zone. + </p></dd> <dt><span class="term"><strong class="userinput"><code>reconfig</code></strong></span></dt> -<dd><p>Reload the configuration file and load new zones, - but do not reload existing zone files even if they have changed. - This is faster than a full <span><strong class="command">reload</strong></span> when there - is a large number of zones because it avoids the need to examine the - modification times of the zones files. - </p></dd> +<dd><p> + Reload the configuration file and load new zones, + but do not reload existing zone files even if they + have changed. + This is faster than a full <span><strong class="command">reload</strong></span> when there + is a large number of zones because it avoids the need + to examine the + modification times of the zones files. + </p></dd> <dt><span class="term"><strong class="userinput"><code>stats</code></strong></span></dt> -<dd><p>Write server statistics to the statistics file.</p></dd> +<dd><p> + Write server statistics to the statistics file. + </p></dd> <dt><span class="term"><strong class="userinput"><code>querylog</code></strong></span></dt> -<dd><p>Toggle query logging. Query logging can also be enabled - by explicitly directing the <span><strong class="command">queries</strong></span> - <span><strong class="command">category</strong></span> to a <span><strong class="command">channel</strong></span> in the - <span><strong class="command">logging</strong></span> section of - <code class="filename">named.conf</code>.</p></dd> -<dt><span class="term"><strong class="userinput"><code>dumpdb [<span class="optional">-all|-cache|-zone</span>] [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt> -<dd><p>Dump the server's caches (default) and / or zones to the - dump file for the specified views. If no view is specified, all - views are dumped.</p></dd> +<dd><p> + Toggle query logging. Query logging can also be enabled + by explicitly directing the <span><strong class="command">queries</strong></span> + <span><strong class="command">category</strong></span> to a + <span><strong class="command">channel</strong></span> in the + <span><strong class="command">logging</strong></span> section of + <code class="filename">named.conf</code> or by specifying + <span><strong class="command">querylog yes;</strong></span> in the + <span><strong class="command">options</strong></span> section of + <code class="filename">named.conf</code>. + </p></dd> +<dt><span class="term"><strong class="userinput"><code>dumpdb + [<span class="optional">-all|-cache|-zone</span>] + [<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt> +<dd><p> + Dump the server's caches (default) and/or zones to + the + dump file for the specified views. If no view is + specified, all + views are dumped. + </p></dd> <dt><span class="term"><strong class="userinput"><code>stop [<span class="optional">-p</span>]</code></strong></span></dt> -<dd><p>Stop the server, making sure any recent changes - made through dynamic update or IXFR are first saved to the master files - of the updated zones. If -p is specified named's process id is returned. - This allows an external process to determine when named had completed stopping.</p></dd> +<dd><p> + Stop the server, making sure any recent changes + made through dynamic update or IXFR are first saved to + the master files of the updated zones. + If -p is specified named's process id is returned. + This allows an external process to determine when named + had completed stopping. + </p></dd> <dt><span class="term"><strong class="userinput"><code>halt [<span class="optional">-p</span>]</code></strong></span></dt> -<dd><p>Stop the server immediately. Recent changes - made through dynamic update or IXFR are not saved to the master files, - but will be rolled forward from the journal files when the server - is restarted. If -p is specified named's process id is returned. - This allows an external process to determine when named had completed - stopping.</p></dd> +<dd><p> + Stop the server immediately. Recent changes + made through dynamic update or IXFR are not saved to + the master files, but will be rolled forward from the + journal files when the server is restarted. + If -p is specified named's process id is returned. + This allows an external process to determine when named + had completed halting. + </p></dd> <dt><span class="term"><strong class="userinput"><code>trace</code></strong></span></dt> -<dd><p>Increment the servers debugging level by one. </p></dd> +<dd><p> + Increment the servers debugging level by one. + </p></dd> <dt><span class="term"><strong class="userinput"><code>trace <em class="replaceable"><code>level</code></em></code></strong></span></dt> -<dd><p>Sets the server's debugging level to an explicit - value.</p></dd> +<dd><p> + Sets the server's debugging level to an explicit + value. + </p></dd> <dt><span class="term"><strong class="userinput"><code>notrace</code></strong></span></dt> -<dd><p>Sets the server's debugging level to 0.</p></dd> +<dd><p> + Sets the server's debugging level to 0. + </p></dd> <dt><span class="term"><strong class="userinput"><code>flush</code></strong></span></dt> -<dd><p>Flushes the server's cache.</p></dd> +<dd><p> + Flushes the server's cache. + </p></dd> <dt><span class="term"><strong class="userinput"><code>flushname</code></strong> <em class="replaceable"><code>name</code></em></span></dt> -<dd><p>Flushes the given name from the server's cache.</p></dd> +<dd><p> + Flushes the given name from the server's cache. + </p></dd> <dt><span class="term"><strong class="userinput"><code>status</code></strong></span></dt> -<dd><p>Display status of the server. -Note that the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone -and the default <span><strong class="command">./IN</strong></span> hint zone if there is not an -explicit root zone configured.</p></dd> +<dd><p> + Display status of the server. + Note that the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone + and the default <span><strong class="command">./IN</strong></span> + hint zone if there is not an + explicit root zone configured. + </p></dd> <dt><span class="term"><strong class="userinput"><code>recursing</code></strong></span></dt> -<dd><p>Dump the list of queries named is currently recursing - on. - </p></dd> +<dd><p> + Dump the list of queries named is currently recursing + on. + </p></dd> </dl></div> -<p>In <acronym class="acronym">BIND</acronym> 9.2, <span><strong class="command">rndc</strong></span> -supports all the commands of the BIND 8 <span><strong class="command">ndc</strong></span> -utility except <span><strong class="command">ndc start</strong></span> and -<span><strong class="command">ndc restart</strong></span>, which were also -not supported in <span><strong class="command">ndc</strong></span>'s channel mode.</p> -<p>A configuration file is required, since all -communication with the server is authenticated with -digital signatures that rely on a shared secret, and -there is no way to provide that secret other than with a -configuration file. The default location for the -<span><strong class="command">rndc</strong></span> configuration file is -<code class="filename">/etc/rndc.conf</code>, but an alternate -location can be specified with the <code class="option">-c</code> -option. If the configuration file is not found, -<span><strong class="command">rndc</strong></span> will also look in -<code class="filename">/etc/rndc.key</code> (or whatever -<code class="varname">sysconfdir</code> was defined when -the <acronym class="acronym">BIND</acronym> build was configured). -The <code class="filename">rndc.key</code> file is generated by -running <span><strong class="command">rndc-confgen -a</strong></span> as described in -<a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and Usage”</a>.</p> -<p>The format of the configuration file is similar to -that of <code class="filename">named.conf</code>, but limited to -only four statements, the <span><strong class="command">options</strong></span>, -<span><strong class="command">key</strong></span>, <span><strong class="command">server</strong></span> and -<span><strong class="command">include</strong></span> -statements. These statements are what associate the -secret keys to the servers with which they are meant to -be shared. The order of statements is not -significant.</p> -<p>The <span><strong class="command">options</strong></span> statement has three clauses: -<span><strong class="command">default-server</strong></span>, <span><strong class="command">default-key</strong></span>, -and <span><strong class="command">default-port</strong></span>. -<span><strong class="command">default-server</strong></span> takes a -host name or address argument and represents the server that will -be contacted if no <code class="option">-s</code> -option is provided on the command line. -<span><strong class="command">default-key</strong></span> takes -the name of a key as its argument, as defined by a <span><strong class="command">key</strong></span> statement. -<span><strong class="command">default-port</strong></span> specifies the port to which -<span><strong class="command">rndc</strong></span> should connect if no -port is given on the command line or in a -<span><strong class="command">server</strong></span> statement.</p> -<p>The <span><strong class="command">key</strong></span> statement defines a key to be used -by <span><strong class="command">rndc</strong></span> when authenticating with -<span><strong class="command">named</strong></span>. Its syntax is identical to the -<span><strong class="command">key</strong></span> statement in named.conf. -The keyword <strong class="userinput"><code>key</code></strong> is -followed by a key name, which must be a valid -domain name, though it need not actually be hierarchical; thus, -a string like "<strong class="userinput"><code>rndc_key</code></strong>" is a valid name. -The <span><strong class="command">key</strong></span> statement has two clauses: -<span><strong class="command">algorithm</strong></span> and <span><strong class="command">secret</strong></span>. -While the configuration parser will accept any string as the argument -to algorithm, currently only the string "<strong class="userinput"><code>hmac-md5</code></strong>" -has any meaning. The secret is a base-64 encoded string.</p> -<p>The <span><strong class="command">server</strong></span> statement associates a key -defined using the <span><strong class="command">key</strong></span> statement with a server. -The keyword <strong class="userinput"><code>server</code></strong> is followed by a -host name or address. The <span><strong class="command">server</strong></span> statement -has two clauses: <span><strong class="command">key</strong></span> and <span><strong class="command">port</strong></span>. -The <span><strong class="command">key</strong></span> clause specifies the name of the key -to be used when communicating with this server, and the -<span><strong class="command">port</strong></span> clause can be used to -specify the port <span><strong class="command">rndc</strong></span> should connect -to on the server.</p> -<p>A sample minimal configuration file is as follows:</p> +<p> + A configuration file is required, since all + communication with the server is authenticated with + digital signatures that rely on a shared secret, and + there is no way to provide that secret other than with a + configuration file. The default location for the + <span><strong class="command">rndc</strong></span> configuration file is + <code class="filename">/etc/rndc.conf</code>, but an + alternate + location can be specified with the <code class="option">-c</code> + option. If the configuration file is not found, + <span><strong class="command">rndc</strong></span> will also look in + <code class="filename">/etc/rndc.key</code> (or whatever + <code class="varname">sysconfdir</code> was defined when + the <acronym class="acronym">BIND</acronym> build was + configured). + The <code class="filename">rndc.key</code> file is + generated by + running <span><strong class="command">rndc-confgen -a</strong></span> as + described in + <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and + Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and + Usage”</a>. + </p> +<p> + The format of the configuration file is similar to + that of <code class="filename">named.conf</code>, but + limited to + only four statements, the <span><strong class="command">options</strong></span>, + <span><strong class="command">key</strong></span>, <span><strong class="command">server</strong></span> and + <span><strong class="command">include</strong></span> + statements. These statements are what associate the + secret keys to the servers with which they are meant to + be shared. The order of statements is not + significant. + </p> +<p> + The <span><strong class="command">options</strong></span> statement has + three clauses: + <span><strong class="command">default-server</strong></span>, <span><strong class="command">default-key</strong></span>, + and <span><strong class="command">default-port</strong></span>. + <span><strong class="command">default-server</strong></span> takes a + host name or address argument and represents the server + that will + be contacted if no <code class="option">-s</code> + option is provided on the command line. + <span><strong class="command">default-key</strong></span> takes + the name of a key as its argument, as defined by a <span><strong class="command">key</strong></span> statement. + <span><strong class="command">default-port</strong></span> specifies the + port to which + <span><strong class="command">rndc</strong></span> should connect if no + port is given on the command line or in a + <span><strong class="command">server</strong></span> statement. + </p> +<p> + The <span><strong class="command">key</strong></span> statement defines a + key to be used + by <span><strong class="command">rndc</strong></span> when authenticating + with + <span><strong class="command">named</strong></span>. Its syntax is + identical to the + <span><strong class="command">key</strong></span> statement in named.conf. + The keyword <strong class="userinput"><code>key</code></strong> is + followed by a key name, which must be a valid + domain name, though it need not actually be hierarchical; + thus, + a string like "<strong class="userinput"><code>rndc_key</code></strong>" is a valid + name. + The <span><strong class="command">key</strong></span> statement has two + clauses: + <span><strong class="command">algorithm</strong></span> and <span><strong class="command">secret</strong></span>. + While the configuration parser will accept any string as the + argument + to algorithm, currently only the string "<strong class="userinput"><code>hmac-md5</code></strong>" + has any meaning. The secret is a base-64 encoded string + as specified in RFC 3548. + </p> +<p> + The <span><strong class="command">server</strong></span> statement + associates a key + defined using the <span><strong class="command">key</strong></span> + statement with a server. + The keyword <strong class="userinput"><code>server</code></strong> is followed by a + host name or address. The <span><strong class="command">server</strong></span> statement + has two clauses: <span><strong class="command">key</strong></span> and <span><strong class="command">port</strong></span>. + The <span><strong class="command">key</strong></span> clause specifies the + name of the key + to be used when communicating with this server, and the + <span><strong class="command">port</strong></span> clause can be used to + specify the port <span><strong class="command">rndc</strong></span> should + connect + to on the server. + </p> +<p> + A sample minimal configuration file is as follows: + </p> <pre class="programlisting"> key rndc_key { algorithm "hmac-md5"; @@ -445,38 +696,55 @@ options { default-key rndc_key; }; </pre> -<p>This file, if installed as <code class="filename">/etc/rndc.conf</code>, -would allow the command:</p> -<p><code class="prompt">$ </code><strong class="userinput"><code>rndc reload</code></strong></p> -<p>to connect to 127.0.0.1 port 953 and cause the name server -to reload, if a name server on the local machine were running with -following controls statements:</p> +<p> + This file, if installed as <code class="filename">/etc/rndc.conf</code>, + would allow the command: + </p> +<p> + <code class="prompt">$ </code><strong class="userinput"><code>rndc reload</code></strong> + </p> +<p> + to connect to 127.0.0.1 port 953 and cause the name server + to reload, if a name server on the local machine were + running with + following controls statements: + </p> <pre class="programlisting"> controls { inet 127.0.0.1 allow { localhost; } keys { rndc_key; }; }; </pre> -<p>and it had an identical key statement for -<code class="literal">rndc_key</code>.</p> -<p>Running the <span><strong class="command">rndc-confgen</strong></span> program will -conveniently create a <code class="filename">rndc.conf</code> -file for you, and also display the -corresponding <span><strong class="command">controls</strong></span> statement that you need to -add to <code class="filename">named.conf</code>. Alternatively, -you can run <span><strong class="command">rndc-confgen -a</strong></span> to set up -a <code class="filename">rndc.key</code> file and not modify -<code class="filename">named.conf</code> at all. -</p> +<p> + and it had an identical key statement for + <code class="literal">rndc_key</code>. + </p> +<p> + Running the <span><strong class="command">rndc-confgen</strong></span> + program will + conveniently create a <code class="filename">rndc.conf</code> + file for you, and also display the + corresponding <span><strong class="command">controls</strong></span> + statement that you need to + add to <code class="filename">named.conf</code>. + Alternatively, + you can run <span><strong class="command">rndc-confgen -a</strong></span> + to set up + a <code class="filename">rndc.key</code> file and not + modify + <code class="filename">named.conf</code> at all. + </p> </dd> </dl></div> </div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2572723"></a>Signals</h3></div></div></div> -<p>Certain UNIX signals cause the name server to take specific -actions, as described in the following table. These signals can -be sent using the <span><strong class="command">kill</strong></span> command.</p> +<a name="id2570184"></a>Signals</h3></div></div></div> +<p> + Certain UNIX signals cause the name server to take specific + actions, as described in the following table. These signals can + be sent using the <span><strong class="command">kill</strong></span> command. + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -484,19 +752,35 @@ be sent using the <span><strong class="command">kill</strong></span> command.</p </colgroup> <tbody> <tr> -<td><p><span><strong class="command">SIGHUP</strong></span></p></td> -<td><p>Causes the server to read <code class="filename">named.conf</code> and -reload the database. </p></td> +<td> + <p><span><strong class="command">SIGHUP</strong></span></p> + </td> +<td> + <p> + Causes the server to read <code class="filename">named.conf</code> and + reload the database. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">SIGTERM</strong></span></p></td> -<td><p>Causes the server to clean up and exit.</p></td> +<td> + <p><span><strong class="command">SIGTERM</strong></span></p> + </td> +<td> + <p> + Causes the server to clean up and exit. + </p> + </td> </tr> <tr> <td> -<p><span><strong class="command">SIGINT</strong></span></p> -</td> -<td><p>Causes the server to clean up and exit.</p></td> + <p><span><strong class="command">SIGINT</strong></span></p> + </td> +<td> + <p> + Causes the server to clean up and exit. + </p> + </td> </tr> </tbody> </table></div> diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch04.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch04.html index 75b5fff942f..d938fca6a71 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch04.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch04.html @@ -1,5 +1,5 @@ <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - Permission to use, copy, modify, and distribute this software for any @@ -14,12 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $ISC: Bv9ARM.ch04.html,v 1.30.2.6.2.24 2006/11/15 04:33:41 marka Exp $ --> +<!-- $ISC: Bv9ARM.ch04.html,v 1.40.18.41 2007/10/31 01:35:57 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Chapter 4. Advanced DNS Features</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="prev" href="Bv9ARM.ch03.html" title="Chapter 3. Name Server Configuration"> @@ -49,213 +49,310 @@ <dt><span class="sect1"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt> <dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2573147">Split DNS</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2570642">Split DNS</a></span></dt> +<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570660">Example split DNS setup</a></span></dt></dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573709">Generate Shared Keys for Each Pair of Hosts</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573776">Copying the Shared Secret to Both Machines</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573784">Informing the Servers of the Key's Existence</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573824">Instructing the Server to Use the Key</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573876">TSIG Key Based Access Control</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573920">Errors</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571095">Generate Shared Keys for Each Pair of Hosts</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571169">Copying the Shared Secret to Both Machines</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571179">Informing the Servers of the Key's Existence</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571219">Instructing the Server to Use the Key</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571413">TSIG Key Based Access Control</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571458">Errors</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2573933">TKEY</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2573982">SIG(0)</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2571472">TKEY</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2571521">SIG(0)</a></span></dt> <dt><span class="sect1"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574049">Generating Keys</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574116">Signing the Zone</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574259">Configuring Servers</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571725">Generating Keys</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571795">Signing the Zone</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571874">Configuring Servers</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2574396">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2572153">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574455">Address Lookups Using AAAA Records</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574475">Address to Name Lookups Using Nibble Format</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572215">Address Lookups Using AAAA Records</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572236">Address to Name Lookups Using Nibble Format</a></span></dt> </dl></dd> </dl> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="notify"></a>Notify</h2></div></div></div> -<p><acronym class="acronym">DNS</acronym> NOTIFY is a mechanism that allows master -servers to notify their slave servers of changes to a zone's data. In -response to a <span><strong class="command">NOTIFY</strong></span> from a master server, the -slave will check to see that its version of the zone is the -current version and, if not, initiate a zone transfer.</p> -<p><acronym class="acronym">DNS</acronym> -For more information about -<span><strong class="command">NOTIFY</strong></span>, see the description of the -<span><strong class="command">notify</strong></span> option in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a> and -the description of the zone option <span><strong class="command">also-notify</strong></span> in -<a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. The <span><strong class="command">NOTIFY</strong></span> -protocol is specified in RFC 1996. -</p> +<p> + <acronym class="acronym">DNS</acronym> NOTIFY is a mechanism that allows master + servers to notify their slave servers of changes to a zone's data. In + response to a <span><strong class="command">NOTIFY</strong></span> from a master server, the + slave will check to see that its version of the zone is the + current version and, if not, initiate a zone transfer. + </p> +<p> + For more information about <acronym class="acronym">DNS</acronym> + <span><strong class="command">NOTIFY</strong></span>, see the description of the + <span><strong class="command">notify</strong></span> option in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a> and + the description of the zone option <span><strong class="command">also-notify</strong></span> in + <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. The <span><strong class="command">NOTIFY</strong></span> + protocol is specified in RFC 1996. + </p> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<h3 class="title">Note</h3> + As a slave zone can also be a master to other slaves, named, + by default, sends <span><strong class="command">NOTIFY</strong></span> messages for every zone + it loads. Specifying <span><strong class="command">notify master-only;</strong></span> will + cause named to only send <span><strong class="command">NOTIFY</strong></span> for master + zones that it loads. + </div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="dynamic_update"></a>Dynamic Update</h2></div></div></div> -<p>Dynamic Update is a method for adding, replacing or deleting - records in a master server by sending it a special form of DNS - messages. The format and meaning of these messages is specified - in RFC 2136.</p> -<p>Dynamic update is enabled on a zone-by-zone basis, by - including an <span><strong class="command">allow-update</strong></span> or - <span><strong class="command">update-policy</strong></span> clause in the - <span><strong class="command">zone</strong></span> statement.</p> -<p>Updating of secure zones (zones using DNSSEC) follows - RFC 3007: RRSIG and NSEC records affected by updates are automatically - regenerated by the server using an online zone key. - Update authorization is based - on transaction signatures and an explicit server policy.</p> +<p> + Dynamic Update is a method for adding, replacing or deleting + records in a master server by sending it a special form of DNS + messages. The format and meaning of these messages is specified + in RFC 2136. + </p> +<p> + Dynamic update is enabled by + including an <span><strong class="command">allow-update</strong></span> or + <span><strong class="command">update-policy</strong></span> clause in the + <span><strong class="command">zone</strong></span> statement. + </p> +<p> + Updating of secure zones (zones using DNSSEC) follows + RFC 3007: RRSIG and NSEC records affected by updates are automatically + regenerated by the server using an online zone key. + Update authorization is based + on transaction signatures and an explicit server policy. + </p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="journal"></a>The journal file</h3></div></div></div> -<p>All changes made to a zone using dynamic update are stored in the - zone's journal file. This file is automatically created by the - server when the first dynamic update takes place. The name of - the journal file is formed by appending the - extension <code class="filename">.jnl</code> to the - name of the corresponding zone file. The journal file is in a - binary format and should not be edited manually.</p> -<p>The server will also occasionally write ("dump") - the complete contents of the updated zone to its zone file. - This is not done immediately after - each dynamic update, because that would be too slow when a large - zone is updated frequently. Instead, the dump is delayed by - up to 15 minutes, allowing additional updates to take place.</p> -<p>When a server is restarted after a shutdown or crash, it will replay - the journal file to incorporate into the zone any updates that took - place after the last zone dump.</p> -<p>Changes that result from incoming incremental zone transfers are also - journalled in a similar way.</p> -<p>The zone files of dynamic zones cannot normally be edited by - hand because they are not guaranteed to contain the most recent - dynamic changes — those are only in the journal file. - The only way to ensure that the zone file of a dynamic zone - is up to date is to run <span><strong class="command">rndc stop</strong></span>.</p> -<p>If you have to make changes to a dynamic zone - manually, the following procedure will work: Disable dynamic updates - to the zone using - <span><strong class="command">rndc freeze <em class="replaceable"><code>zone</code></em></strong></span>. - This will also remove the zone's <code class="filename">.jnl</code> file - and update the master file. Edit the zone file. Run - <span><strong class="command">rndc thaw <em class="replaceable"><code>zone</code></em></strong></span> - to reload the changed zone and re-enable dynamic updates.</p> +<p> + All changes made to a zone using dynamic update are stored + in the zone's journal file. This file is automatically created + by the server when the first dynamic update takes place. + The name of the journal file is formed by appending the extension + <code class="filename">.jnl</code> to the name of the + corresponding zone + file unless specifically overridden. The journal file is in a + binary format and should not be edited manually. + </p> +<p> + The server will also occasionally write ("dump") + the complete contents of the updated zone to its zone file. + This is not done immediately after + each dynamic update, because that would be too slow when a large + zone is updated frequently. Instead, the dump is delayed by + up to 15 minutes, allowing additional updates to take place. + </p> +<p> + When a server is restarted after a shutdown or crash, it will replay + the journal file to incorporate into the zone any updates that + took + place after the last zone dump. + </p> +<p> + Changes that result from incoming incremental zone transfers are + also + journalled in a similar way. + </p> +<p> + The zone files of dynamic zones cannot normally be edited by + hand because they are not guaranteed to contain the most recent + dynamic changes — those are only in the journal file. + The only way to ensure that the zone file of a dynamic zone + is up to date is to run <span><strong class="command">rndc stop</strong></span>. + </p> +<p> + If you have to make changes to a dynamic zone + manually, the following procedure will work: Disable dynamic updates + to the zone using + <span><strong class="command">rndc freeze <em class="replaceable"><code>zone</code></em></strong></span>. + This will also remove the zone's <code class="filename">.jnl</code> file + and update the master file. Edit the zone file. Run + <span><strong class="command">rndc thaw <em class="replaceable"><code>zone</code></em></strong></span> + to reload the changed zone and re-enable dynamic updates. + </p> </div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="incremental_zone_transfers"></a>Incremental Zone Transfers (IXFR)</h2></div></div></div> -<p>The incremental zone transfer (IXFR) protocol is a way for -slave servers to transfer only changed data, instead of having to -transfer the entire zone. The IXFR protocol is specified in RFC -1995. See <a href="Bv9ARM.ch09.html#proposed_standards">Proposed Standards</a>.</p> -<p>When acting as a master, <acronym class="acronym">BIND</acronym> 9 -supports IXFR for those zones -where the necessary change history information is available. These -include master zones maintained by dynamic update and slave zones -whose data was obtained by IXFR. For manually maintained master -zones, and for slave zones obtained by performing a full zone -transfer (AXFR), IXFR is supported only if the option -<span><strong class="command">ixfr-from-differences</strong></span> is set -to <strong class="userinput"><code>yes</code></strong>. -</p> -<p>When acting as a slave, <acronym class="acronym">BIND</acronym> 9 will -attempt to use IXFR unless -it is explicitly disabled. For more information about disabling -IXFR, see the description of the <span><strong class="command">request-ixfr</strong></span> clause -of the <span><strong class="command">server</strong></span> statement.</p> +<p> + The incremental zone transfer (IXFR) protocol is a way for + slave servers to transfer only changed data, instead of having to + transfer the entire zone. The IXFR protocol is specified in RFC + 1995. See <a href="Bv9ARM.ch09.html#proposed_standards">Proposed Standards</a>. + </p> +<p> + When acting as a master, <acronym class="acronym">BIND</acronym> 9 + supports IXFR for those zones + where the necessary change history information is available. These + include master zones maintained by dynamic update and slave zones + whose data was obtained by IXFR. For manually maintained master + zones, and for slave zones obtained by performing a full zone + transfer (AXFR), IXFR is supported only if the option + <span><strong class="command">ixfr-from-differences</strong></span> is set + to <strong class="userinput"><code>yes</code></strong>. + </p> +<p> + When acting as a slave, <acronym class="acronym">BIND</acronym> 9 will + attempt to use IXFR unless + it is explicitly disabled. For more information about disabling + IXFR, see the description of the <span><strong class="command">request-ixfr</strong></span> clause + of the <span><strong class="command">server</strong></span> statement. + </p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2573147"></a>Split DNS</h2></div></div></div> -<p>Setting up different views, or visibility, of the DNS space to -internal and external resolvers is usually referred to as a <span class="emphasis"><em>Split -DNS</em></span> setup. There are several reasons an organization -would want to set up its DNS this way.</p> -<p>One common reason for setting up a DNS system this way is -to hide "internal" DNS information from "external" clients on the -Internet. There is some debate as to whether or not this is actually useful. -Internal DNS information leaks out in many ways (via email headers, -for example) and most savvy "attackers" can find the information -they need using other means.</p> -<p>Another common reason for setting up a Split DNS system is -to allow internal networks that are behind filters or in RFC 1918 -space (reserved IP space, as documented in RFC 1918) to resolve DNS -on the Internet. Split DNS can also be used to allow mail from outside -back in to the internal network.</p> -<p>Here is an example of a split DNS setup:</p> -<p>Let's say a company named <span class="emphasis"><em>Example, Inc.</em></span> -(<code class="literal">example.com</code>) -has several corporate sites that have an internal network with reserved -Internet Protocol (IP) space and an external demilitarized zone (DMZ), -or "outside" section of a network, that is available to the public.</p> -<p><span class="emphasis"><em>Example, Inc.</em></span> wants its internal clients -to be able to resolve external hostnames and to exchange mail with -people on the outside. The company also wants its internal resolvers -to have access to certain internal-only zones that are not available -at all outside of the internal network.</p> -<p>In order to accomplish this, the company will set up two sets -of name servers. One set will be on the inside network (in the reserved -IP space) and the other set will be on bastion hosts, which are "proxy" -hosts that can talk to both sides of its network, in the DMZ.</p> -<p>The internal servers will be configured to forward all queries, -except queries for <code class="filename">site1.internal</code>, <code class="filename">site2.internal</code>, <code class="filename">site1.example.com</code>, -and <code class="filename">site2.example.com</code>, to the servers in the -DMZ. These internal servers will have complete sets of information -for <code class="filename">site1.example.com</code>, <code class="filename">site2.example.com</code>,<span class="emphasis"><em> </em></span><code class="filename">site1.internal</code>, -and <code class="filename">site2.internal</code>.</p> -<p>To protect the <code class="filename">site1.internal</code> and <code class="filename">site2.internal</code> domains, -the internal name servers must be configured to disallow all queries -to these domains from any external hosts, including the bastion -hosts.</p> -<p>The external servers, which are on the bastion hosts, will -be configured to serve the "public" version of the <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones. -This could include things such as the host records for public servers -(<code class="filename">www.example.com</code> and <code class="filename">ftp.example.com</code>), -and mail exchange (MX) records (<code class="filename">a.mx.example.com</code> and <code class="filename">b.mx.example.com</code>).</p> -<p>In addition, the public <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones -should have special MX records that contain wildcard (`*') records -pointing to the bastion hosts. This is needed because external mail -servers do not have any other way of looking up how to deliver mail -to those internal hosts. With the wildcard records, the mail will -be delivered to the bastion host, which can then forward it on to -internal hosts.</p> -<p>Here's an example of a wildcard MX record:</p> +<a name="id2570642"></a>Split DNS</h2></div></div></div> +<p> + Setting up different views, or visibility, of the DNS space to + internal and external resolvers is usually referred to as a + <span class="emphasis"><em>Split DNS</em></span> setup. There are several + reasons an organization would want to set up its DNS this way. + </p> +<p> + One common reason for setting up a DNS system this way is + to hide "internal" DNS information from "external" clients on the + Internet. There is some debate as to whether or not this is actually + useful. + Internal DNS information leaks out in many ways (via email headers, + for example) and most savvy "attackers" can find the information + they need using other means. + However, since listing addresses of internal servers that + external clients cannot possibly reach can result in + connection delays and other annoyances, an organization may + choose to use a Split DNS to present a consistent view of itself + to the outside world. + </p> +<p> + Another common reason for setting up a Split DNS system is + to allow internal networks that are behind filters or in RFC 1918 + space (reserved IP space, as documented in RFC 1918) to resolve DNS + on the Internet. Split DNS can also be used to allow mail from outside + back in to the internal network. + </p> +<div class="sect2" lang="en"> +<div class="titlepage"><div><div><h3 class="title"> +<a name="id2570660"></a>Example split DNS setup</h3></div></div></div> +<p> + Let's say a company named <span class="emphasis"><em>Example, Inc.</em></span> + (<code class="literal">example.com</code>) + has several corporate sites that have an internal network with + reserved + Internet Protocol (IP) space and an external demilitarized zone (DMZ), + or "outside" section of a network, that is available to the public. + </p> +<p> + <span class="emphasis"><em>Example, Inc.</em></span> wants its internal clients + to be able to resolve external hostnames and to exchange mail with + people on the outside. The company also wants its internal resolvers + to have access to certain internal-only zones that are not available + at all outside of the internal network. + </p> +<p> + In order to accomplish this, the company will set up two sets + of name servers. One set will be on the inside network (in the + reserved + IP space) and the other set will be on bastion hosts, which are + "proxy" + hosts that can talk to both sides of its network, in the DMZ. + </p> +<p> + The internal servers will be configured to forward all queries, + except queries for <code class="filename">site1.internal</code>, <code class="filename">site2.internal</code>, <code class="filename">site1.example.com</code>, + and <code class="filename">site2.example.com</code>, to the servers + in the + DMZ. These internal servers will have complete sets of information + for <code class="filename">site1.example.com</code>, <code class="filename">site2.example.com</code>,<span class="emphasis"><em></em></span> <code class="filename">site1.internal</code>, + and <code class="filename">site2.internal</code>. + </p> +<p> + To protect the <code class="filename">site1.internal</code> and <code class="filename">site2.internal</code> domains, + the internal name servers must be configured to disallow all queries + to these domains from any external hosts, including the bastion + hosts. + </p> +<p> + The external servers, which are on the bastion hosts, will + be configured to serve the "public" version of the <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones. + This could include things such as the host records for public servers + (<code class="filename">www.example.com</code> and <code class="filename">ftp.example.com</code>), + and mail exchange (MX) records (<code class="filename">a.mx.example.com</code> and <code class="filename">b.mx.example.com</code>). + </p> +<p> + In addition, the public <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones + should have special MX records that contain wildcard (`*') records + pointing to the bastion hosts. This is needed because external mail + servers do not have any other way of looking up how to deliver mail + to those internal hosts. With the wildcard records, the mail will + be delivered to the bastion host, which can then forward it on to + internal hosts. + </p> +<p> + Here's an example of a wildcard MX record: + </p> <pre class="programlisting">* IN MX 10 external1.example.com.</pre> -<p>Now that they accept mail on behalf of anything in the internal -network, the bastion hosts will need to know how to deliver mail -to internal hosts. In order for this to work properly, the resolvers on -the bastion hosts will need to be configured to point to the internal -name servers for DNS resolution.</p> -<p>Queries for internal hostnames will be answered by the internal -servers, and queries for external hostnames will be forwarded back -out to the DNS servers on the bastion hosts.</p> -<p>In order for all this to work properly, internal clients will -need to be configured to query <span class="emphasis"><em>only</em></span> the internal -name servers for DNS queries. This could also be enforced via selective -filtering on the network.</p> -<p>If everything has been set properly, <span class="emphasis"><em>Example, Inc.</em></span>'s -internal clients will now be able to:</p> +<p> + Now that they accept mail on behalf of anything in the internal + network, the bastion hosts will need to know how to deliver mail + to internal hosts. In order for this to work properly, the resolvers + on + the bastion hosts will need to be configured to point to the internal + name servers for DNS resolution. + </p> +<p> + Queries for internal hostnames will be answered by the internal + servers, and queries for external hostnames will be forwarded back + out to the DNS servers on the bastion hosts. + </p> +<p> + In order for all this to work properly, internal clients will + need to be configured to query <span class="emphasis"><em>only</em></span> the internal + name servers for DNS queries. This could also be enforced via + selective + filtering on the network. + </p> +<p> + If everything has been set properly, <span class="emphasis"><em>Example, Inc.</em></span>'s + internal clients will now be able to: + </p> <div class="itemizedlist"><ul type="disc"> -<li>Look up any hostnames in the <code class="literal">site1</code> and -<code class="literal">site2.example.com</code> zones.</li> -<li>Look up any hostnames in the <code class="literal">site1.internal</code> and -<code class="literal">site2.internal</code> domains.</li> +<li> + Look up any hostnames in the <code class="literal">site1</code> + and + <code class="literal">site2.example.com</code> zones. + </li> +<li> + Look up any hostnames in the <code class="literal">site1.internal</code> and + <code class="literal">site2.internal</code> domains. + </li> <li>Look up any hostnames on the Internet.</li> -<li>Exchange mail with both internal AND external people.</li> +<li>Exchange mail with both internal and external people.</li> </ul></div> -<p>Hosts on the Internet will be able to:</p> +<p> + Hosts on the Internet will be able to: + </p> <div class="itemizedlist"><ul type="disc"> -<li>Look up any hostnames in the <code class="literal">site1</code> and -<code class="literal">site2.example.com</code> zones.</li> -<li>Exchange mail with anyone in the <code class="literal">site1</code> and -<code class="literal">site2.example.com</code> zones.</li> +<li> + Look up any hostnames in the <code class="literal">site1</code> + and + <code class="literal">site2.example.com</code> zones. + </li> +<li> + Exchange mail with anyone in the <code class="literal">site1</code> and + <code class="literal">site2.example.com</code> zones. + </li> </ul></div> -<p>Here is an example configuration for the setup we just - described above. Note that this is only configuration information; - for information on how to configure your zone files, see <a href="Bv9ARM.ch03.html#sample_configuration" title="Sample Configurations">the section called “Sample Configurations”</a>.</p> -<p>Internal DNS server config:</p> +<p> + Here is an example configuration for the setup we just + described above. Note that this is only configuration information; + for information on how to configure your zone files, see <a href="Bv9ARM.ch03.html#sample_configuration" title="Sample Configurations">the section called “Sample Configurations”</a>. + </p> +<p> + Internal DNS server config: + </p> <pre class="programlisting"> acl internals { 172.16.72.0/24; 192.168.1.0/24; }; @@ -267,7 +364,7 @@ options { ... forward only; forwarders { // forward to external servers - <code class="varname">bastion-ips-go-here</code>; + <code class="varname">bastion-ips-go-here</code>; }; allow-transfer { none; }; // sample allow-transfer (no one) allow-query { internals; externals; }; // restrict query access @@ -311,7 +408,9 @@ zone "site2.internal" { allow-transfer { internals; } }; </pre> -<p>External (bastion host) DNS server config:</p> +<p> + External (bastion host) DNS server config: + </p> <pre class="programlisting"> acl internals { 172.16.72.0/24; 192.168.1.0/24; }; @@ -321,7 +420,8 @@ options { ... ... allow-transfer { none; }; // sample allow-transfer (no one) - allow-query { internals; externals; }; // restrict query access + allow-query { any; }; // default query access + allow-query-cache { internals; externals; }; // restrict cache access allow-recursion { internals; externals; }; // restrict recursion ... ... @@ -330,7 +430,6 @@ options { zone "site1.example.com" { // sample slave zone type master; file "m/site1.foo.com"; - allow-query { any; }; allow-transfer { internals; externals; }; }; @@ -338,12 +437,13 @@ zone "site2.example.com" { type slave; file "s/site2.foo.com"; masters { another_bastion_host_maybe; }; - allow-query { any; }; allow-transfer { internals; externals; } }; </pre> -<p>In the <code class="filename">resolv.conf</code> (or equivalent) on -the bastion host(s):</p> +<p> + In the <code class="filename">resolv.conf</code> (or equivalent) on + the bastion host(s): + </p> <pre class="programlisting"> search ... nameserver 172.16.72.2 @@ -351,419 +451,555 @@ nameserver 172.16.72.3 nameserver 172.16.72.4 </pre> </div> +</div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="tsig"></a>TSIG</h2></div></div></div> -<p>This is a short guide to setting up Transaction SIGnatures -(TSIG) based transaction security in <acronym class="acronym">BIND</acronym>. It describes changes -to the configuration file as well as what changes are required for -different features, including the process of creating transaction -keys and using transaction signatures with <acronym class="acronym">BIND</acronym>.</p> -<p><acronym class="acronym">BIND</acronym> primarily supports TSIG for server to server communication. -This includes zone transfer, notify, and recursive query messages. -Resolvers based on newer versions of <acronym class="acronym">BIND</acronym> 8 have limited support -for TSIG.</p> -<p>TSIG might be most useful for dynamic update. A primary - server for a dynamic zone should use access control to control - updates, but IP-based access control is insufficient. - The cryptographic access control provided by TSIG - is far superior. The <span><strong class="command">nsupdate</strong></span> - program supports TSIG via the <code class="option">-k</code> and - <code class="option">-y</code> command line options.</p> +<p> + This is a short guide to setting up Transaction SIGnatures + (TSIG) based transaction security in <acronym class="acronym">BIND</acronym>. It describes changes + to the configuration file as well as what changes are required for + different features, including the process of creating transaction + keys and using transaction signatures with <acronym class="acronym">BIND</acronym>. + </p> +<p> + <acronym class="acronym">BIND</acronym> primarily supports TSIG for server + to server communication. + This includes zone transfer, notify, and recursive query messages. + Resolvers based on newer versions of <acronym class="acronym">BIND</acronym> 8 have limited support + for TSIG. + </p> +<p> + TSIG can also be useful for dynamic update. A primary + server for a dynamic zone should control access to the dynamic + update service, but IP-based access control is insufficient. + The cryptographic access control provided by TSIG + is far superior. The <span><strong class="command">nsupdate</strong></span> + program supports TSIG via the <code class="option">-k</code> and + <code class="option">-y</code> command line options or inline by use + of the <span><strong class="command">key</strong></span>. + </p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2573709"></a>Generate Shared Keys for Each Pair of Hosts</h3></div></div></div> -<p>A shared secret is generated to be shared between <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host2</em></span>. -An arbitrary key name is chosen: "host1-host2.". The key name must -be the same on both hosts.</p> +<a name="id2571095"></a>Generate Shared Keys for Each Pair of Hosts</h3></div></div></div> +<p> + A shared secret is generated to be shared between <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host2</em></span>. + An arbitrary key name is chosen: "host1-host2.". The key name must + be the same on both hosts. + </p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2573725"></a>Automatic Generation</h4></div></div></div> -<p>The following command will generate a 128-bit (16 byte) HMAC-MD5 -key as described above. Longer keys are better, but shorter keys -are easier to read. Note that the maximum key length is 512 bits; -keys longer than that will be digested with MD5 to produce a -128-bit key.</p> -<p><strong class="userinput"><code>dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.</code></strong></p> -<p>The key is in the file <code class="filename">Khost1-host2.+157+00000.private</code>. -Nothing directly uses this file, but the base-64 encoded string -following "<code class="literal">Key:</code>" -can be extracted from the file and used as a shared secret:</p> +<a name="id2571112"></a>Automatic Generation</h4></div></div></div> +<p> + The following command will generate a 128-bit (16 byte) HMAC-MD5 + key as described above. Longer keys are better, but shorter keys + are easier to read. Note that the maximum key length is 512 bits; + keys longer than that will be digested with MD5 to produce a + 128-bit key. + </p> +<p> + <strong class="userinput"><code>dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.</code></strong> + </p> +<p> + The key is in the file <code class="filename">Khost1-host2.+157+00000.private</code>. + Nothing directly uses this file, but the base-64 encoded string + following "<code class="literal">Key:</code>" + can be extracted from the file and used as a shared secret: + </p> <pre class="programlisting">Key: La/E5CjG9O+os1jq0a2jdA==</pre> -<p>The string "<code class="literal">La/E5CjG9O+os1jq0a2jdA==</code>" can -be used as the shared secret.</p> +<p> + The string "<code class="literal">La/E5CjG9O+os1jq0a2jdA==</code>" can + be used as the shared secret. + </p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2573760"></a>Manual Generation</h4></div></div></div> -<p>The shared secret is simply a random sequence of bits, encoded -in base-64. Most ASCII strings are valid base-64 strings (assuming -the length is a multiple of 4 and only valid characters are used), -so the shared secret can be manually generated.</p> -<p>Also, a known string can be run through <span><strong class="command">mmencode</strong></span> or -a similar program to generate base-64 encoded data.</p> +<a name="id2571150"></a>Manual Generation</h4></div></div></div> +<p> + The shared secret is simply a random sequence of bits, encoded + in base-64. Most ASCII strings are valid base-64 strings (assuming + the length is a multiple of 4 and only valid characters are used), + so the shared secret can be manually generated. + </p> +<p> + Also, a known string can be run through <span><strong class="command">mmencode</strong></span> or + a similar program to generate base-64 encoded data. + </p> </div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2573776"></a>Copying the Shared Secret to Both Machines</h3></div></div></div> -<p>This is beyond the scope of DNS. A secure transport mechanism -should be used. This could be secure FTP, ssh, telephone, etc.</p> +<a name="id2571169"></a>Copying the Shared Secret to Both Machines</h3></div></div></div> +<p> + This is beyond the scope of DNS. A secure transport mechanism + should be used. This could be secure FTP, ssh, telephone, etc. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2573784"></a>Informing the Servers of the Key's Existence</h3></div></div></div> -<p>Imagine <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host 2</em></span> are -both servers. The following is added to each server's <code class="filename">named.conf</code> file:</p> +<a name="id2571179"></a>Informing the Servers of the Key's Existence</h3></div></div></div> +<p> + Imagine <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host 2</em></span> + are + both servers. The following is added to each server's <code class="filename">named.conf</code> file: + </p> <pre class="programlisting"> key host1-host2. { algorithm hmac-md5; secret "La/E5CjG9O+os1jq0a2jdA=="; }; </pre> -<p>The algorithm, hmac-md5, is the only one supported by <acronym class="acronym">BIND</acronym>. -The secret is the one generated above. Since this is a secret, it -is recommended that either <code class="filename">named.conf</code> be non-world -readable, or the key directive be added to a non-world readable -file that is included by <code class="filename">named.conf</code>.</p> -<p>At this point, the key is recognized. This means that if the -server receives a message signed by this key, it can verify the -signature. If the signature is successfully verified, the -response is signed by the same key.</p> +<p> + The algorithm, hmac-md5, is the only one supported by <acronym class="acronym">BIND</acronym>. + The secret is the one generated above. Since this is a secret, it + is recommended that either <code class="filename">named.conf</code> be non-world + readable, or the key directive be added to a non-world readable + file that is included by + <code class="filename">named.conf</code>. + </p> +<p> + At this point, the key is recognized. This means that if the + server receives a message signed by this key, it can verify the + signature. If the signature is successfully verified, the + response is signed by the same key. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2573824"></a>Instructing the Server to Use the Key</h3></div></div></div> -<p>Since keys are shared between two hosts only, the server must -be told when keys are to be used. The following is added to the <code class="filename">named.conf</code> file -for <span class="emphasis"><em>host1</em></span>, if the IP address of <span class="emphasis"><em>host2</em></span> is -10.1.2.3:</p> +<a name="id2571219"></a>Instructing the Server to Use the Key</h3></div></div></div> +<p> + Since keys are shared between two hosts only, the server must + be told when keys are to be used. The following is added to the <code class="filename">named.conf</code> file + for <span class="emphasis"><em>host1</em></span>, if the IP address of <span class="emphasis"><em>host2</em></span> is + 10.1.2.3: + </p> <pre class="programlisting"> server 10.1.2.3 { keys { host1-host2. ;}; }; </pre> -<p>Multiple keys may be present, but only the first is used. -This directive does not contain any secrets, so it may be in a world-readable -file.</p> -<p>If <span class="emphasis"><em>host1</em></span> sends a message that is a request -to that address, the message will be signed with the specified key. <span class="emphasis"><em>host1</em></span> will -expect any responses to signed messages to be signed with the same -key.</p> -<p>A similar statement must be present in <span class="emphasis"><em>host2</em></span>'s -configuration file (with <span class="emphasis"><em>host1</em></span>'s address) for <span class="emphasis"><em>host2</em></span> to -sign request messages to <span class="emphasis"><em>host1</em></span>.</p> +<p> + Multiple keys may be present, but only the first is used. + This directive does not contain any secrets, so it may be in a + world-readable + file. + </p> +<p> + If <span class="emphasis"><em>host1</em></span> sends a message that is a request + to that address, the message will be signed with the specified key. <span class="emphasis"><em>host1</em></span> will + expect any responses to signed messages to be signed with the same + key. + </p> +<p> + A similar statement must be present in <span class="emphasis"><em>host2</em></span>'s + configuration file (with <span class="emphasis"><em>host1</em></span>'s address) for <span class="emphasis"><em>host2</em></span> to + sign request messages to <span class="emphasis"><em>host1</em></span>. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2573876"></a>TSIG Key Based Access Control</h3></div></div></div> -<p><acronym class="acronym">BIND</acronym> allows IP addresses and ranges to be specified in ACL -definitions and -<span><strong class="command">allow-{ query | transfer | update }</strong></span> directives. -This has been extended to allow TSIG keys also. The above key would -be denoted <span><strong class="command">key host1-host2.</strong></span></p> -<p>An example of an allow-update directive would be:</p> +<a name="id2571413"></a>TSIG Key Based Access Control</h3></div></div></div> +<p> + <acronym class="acronym">BIND</acronym> allows IP addresses and ranges + to be specified in ACL + definitions and + <span><strong class="command">allow-{ query | transfer | update }</strong></span> + directives. + This has been extended to allow TSIG keys also. The above key would + be denoted <span><strong class="command">key host1-host2.</strong></span> + </p> +<p> + An example of an allow-update directive would be: + </p> <pre class="programlisting"> allow-update { key host1-host2. ;}; </pre> -<p>This allows dynamic updates to succeed only if the request - was signed by a key named - "<span><strong class="command">host1-host2.</strong></span>".</p> -<p>You may want to read about the more - powerful <span><strong class="command">update-policy</strong></span> statement in <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>.</p> +<p> + This allows dynamic updates to succeed only if the request + was signed by a key named + "<span><strong class="command">host1-host2.</strong></span>". + </p> +<p> + You may want to read about the more + powerful <span><strong class="command">update-policy</strong></span> statement in <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2573920"></a>Errors</h3></div></div></div> -<p>The processing of TSIG signed messages can result in - several errors. If a signed message is sent to a non-TSIG - aware server, a FORMERR (format error) will be returned, since - the server will not understand the record. This is a result - of misconfiguration, since the server must be explicitly - configured to send a TSIG signed message to a specific - server.</p> -<p>If a TSIG aware server receives a message signed by an - unknown key, the response will be unsigned with the TSIG - extended error code set to BADKEY. If a TSIG aware server - receives a message with a signature that does not validate, the - response will be unsigned with the TSIG extended error code set - to BADSIG. If a TSIG aware server receives a message with a time - outside of the allowed range, the response will be signed with - the TSIG extended error code set to BADTIME, and the time values - will be adjusted so that the response can be successfully - verified. In any of these cases, the message's rcode is set to - NOTAUTH (not authenticated).</p> +<a name="id2571458"></a>Errors</h3></div></div></div> +<p> + The processing of TSIG signed messages can result in + several errors. If a signed message is sent to a non-TSIG aware + server, a FORMERR (format error) will be returned, since the server will not + understand the record. This is a result of misconfiguration, + since the server must be explicitly configured to send a TSIG + signed message to a specific server. + </p> +<p> + If a TSIG aware server receives a message signed by an + unknown key, the response will be unsigned with the TSIG + extended error code set to BADKEY. If a TSIG aware server + receives a message with a signature that does not validate, the + response will be unsigned with the TSIG extended error code set + to BADSIG. If a TSIG aware server receives a message with a time + outside of the allowed range, the response will be signed with + the TSIG extended error code set to BADTIME, and the time values + will be adjusted so that the response can be successfully + verified. In any of these cases, the message's rcode (response code) is set to + NOTAUTH (not authenticated). + </p> </div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2573933"></a>TKEY</h2></div></div></div> -<p><span><strong class="command">TKEY</strong></span> is a mechanism for automatically - generating a shared secret between two hosts. There are several - "modes" of <span><strong class="command">TKEY</strong></span> that specify how the key is - generated or assigned. <acronym class="acronym">BIND</acronym> 9 - implements only one of these modes, - the Diffie-Hellman key exchange. Both hosts are required to have - a Diffie-Hellman KEY record (although this record is not required - to be present in a zone). The <span><strong class="command">TKEY</strong></span> process - must use signed messages, signed either by TSIG or SIG(0). The - result of <span><strong class="command">TKEY</strong></span> is a shared secret that can be - used to sign messages with TSIG. <span><strong class="command">TKEY</strong></span> can also - be used to delete shared secrets that it had previously - generated.</p> -<p>The <span><strong class="command">TKEY</strong></span> process is initiated by a client - or server by sending a signed <span><strong class="command">TKEY</strong></span> query - (including any appropriate KEYs) to a TKEY-aware server. The - server response, if it indicates success, will contain a - <span><strong class="command">TKEY</strong></span> record and any appropriate keys. After - this exchange, both participants have enough information to - determine the shared secret; the exact process depends on the - <span><strong class="command">TKEY</strong></span> mode. When using the Diffie-Hellman - <span><strong class="command">TKEY</strong></span> mode, Diffie-Hellman keys are exchanged, - and the shared secret is derived by both participants.</p> +<a name="id2571472"></a>TKEY</h2></div></div></div> +<p><span><strong class="command">TKEY</strong></span> + is a mechanism for automatically generating a shared secret + between two hosts. There are several "modes" of + <span><strong class="command">TKEY</strong></span> that specify how the key is generated + or assigned. <acronym class="acronym">BIND</acronym> 9 implements only one of + these modes, the Diffie-Hellman key exchange. Both hosts are + required to have a Diffie-Hellman KEY record (although this + record is not required to be present in a zone). The + <span><strong class="command">TKEY</strong></span> process must use signed messages, + signed either by TSIG or SIG(0). The result of + <span><strong class="command">TKEY</strong></span> is a shared secret that can be used to + sign messages with TSIG. <span><strong class="command">TKEY</strong></span> can also be + used to delete shared secrets that it had previously + generated. + </p> +<p> + The <span><strong class="command">TKEY</strong></span> process is initiated by a + client + or server by sending a signed <span><strong class="command">TKEY</strong></span> + query + (including any appropriate KEYs) to a TKEY-aware server. The + server response, if it indicates success, will contain a + <span><strong class="command">TKEY</strong></span> record and any appropriate keys. + After + this exchange, both participants have enough information to + determine the shared secret; the exact process depends on the + <span><strong class="command">TKEY</strong></span> mode. When using the + Diffie-Hellman + <span><strong class="command">TKEY</strong></span> mode, Diffie-Hellman keys are + exchanged, + and the shared secret is derived by both participants. + </p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2573982"></a>SIG(0)</h2></div></div></div> -<p><acronym class="acronym">BIND</acronym> 9 partially supports DNSSEC SIG(0) - transaction signatures as specified in RFC 2535 and RFC2931. SIG(0) - uses public/private keys to authenticate messages. Access control - is performed in the same manner as TSIG keys; privileges can be - granted or denied based on the key name.</p> -<p>When a SIG(0) signed message is received, it will only be - verified if the key is known and trusted by the server; the server - will not attempt to locate and / or validate the key.</p> -<p>SIG(0) signing of multiple-message TCP streams is not - supported.</p> -<p>The only tool shipped with <acronym class="acronym">BIND</acronym> 9 that - generates SIG(0) signed messages is <span><strong class="command">nsupdate</strong></span>.</p> +<a name="id2571521"></a>SIG(0)</h2></div></div></div> +<p> + <acronym class="acronym">BIND</acronym> 9 partially supports DNSSEC SIG(0) + transaction signatures as specified in RFC 2535 and RFC2931. + SIG(0) + uses public/private keys to authenticate messages. Access control + is performed in the same manner as TSIG keys; privileges can be + granted or denied based on the key name. + </p> +<p> + When a SIG(0) signed message is received, it will only be + verified if the key is known and trusted by the server; the server + will not attempt to locate and/or validate the key. + </p> +<p> + SIG(0) signing of multiple-message TCP streams is not + supported. + </p> +<p> + The only tool shipped with <acronym class="acronym">BIND</acronym> 9 that + generates SIG(0) signed messages is <span><strong class="command">nsupdate</strong></span>. + </p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="DNSSEC"></a>DNSSEC</h2></div></div></div> -<p>Cryptographic authentication of DNS information is possible - through the DNS Security (<span class="emphasis"><em>DNSSEC-bis</em></span>) - extensions, defined in RFC 4033, RFC4034 and RFC4035. This - section describes the creation and use of DNSSEC signed - zones.</p> -<p>In order to set up a DNSSEC secure zone, there are a series - of steps which must be followed. <acronym class="acronym">BIND</acronym> 9 ships - with several tools - that are used in this process, which are explained in more detail - below. In all cases, the <code class="option">-h</code> option prints a - full list of parameters. Note that the DNSSEC tools require the - keyset files to be in the working directory or the - directory specified by the <code class="option">-h</code> option, and - that the tools shipped with BIND 9.2.x and earlier are not compatible - with the current ones.</p> -<p>There must also be communication with the administrators of - the parent and/or child zone to transmit keys. A zone's security - status must be indicated by the parent zone for a DNSSEC capable - resolver to trust its data. This is done through the presence - or absence of a <code class="literal">DS</code> record at the delegation - point.</p> -<p>For other servers to trust data in this zone, they must - either be statically configured with this zone's zone key or the - zone key of another zone above this one in the DNS tree.</p> +<p> + Cryptographic authentication of DNS information is possible + through the DNS Security (<span class="emphasis"><em>DNSSEC-bis</em></span>) extensions, + defined in RFC 4033, RFC 4034, and RFC 4035. + This section describes the creation and use of DNSSEC signed zones. + </p> +<p> + In order to set up a DNSSEC secure zone, there are a series + of steps which must be followed. <acronym class="acronym">BIND</acronym> + 9 ships + with several tools + that are used in this process, which are explained in more detail + below. In all cases, the <code class="option">-h</code> option prints a + full list of parameters. Note that the DNSSEC tools require the + keyset files to be in the working directory or the + directory specified by the <code class="option">-d</code> option, and + that the tools shipped with BIND 9.2.x and earlier are not compatible + with the current ones. + </p> +<p> + There must also be communication with the administrators of + the parent and/or child zone to transmit keys. A zone's security + status must be indicated by the parent zone for a DNSSEC capable + resolver to trust its data. This is done through the presence + or absence of a <code class="literal">DS</code> record at the + delegation + point. + </p> +<p> + For other servers to trust data in this zone, they must + either be statically configured with this zone's zone key or the + zone key of another zone above this one in the DNS tree. + </p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2574049"></a>Generating Keys</h3></div></div></div> -<p>The <span><strong class="command">dnssec-keygen</strong></span> program is used to - generate keys.</p> -<p>A secure zone must contain one or more zone keys. The - zone keys will sign all other records in the zone, as well as - the zone keys of any secure delegated zones. Zone keys must - have the same name as the zone, a name type of - <span><strong class="command">ZONE</strong></span>, and must be usable for authentication. - It is recommended that zone keys use a cryptographic algorithm - designated as "mandatory to implement" by the IETF; currently - the only one is RSASHA1.</p> -<p>The following command will generate a 768-bit RSASHA1 key for - the <code class="filename">child.example</code> zone:</p> -<p><strong class="userinput"><code>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</code></strong></p> -<p>Two output files will be produced: - <code class="filename">Kchild.example.+005+12345.key</code> and - <code class="filename">Kchild.example.+005+12345.private</code> (where - 12345 is an example of a key tag). The key file names contain - the key name (<code class="filename">child.example.</code>), algorithm (3 - is DSA, 1 is RSAMD5, 5 is RSASHA1, etc.), and the key tag (12345 in this case). - The private key (in the <code class="filename">.private</code> file) is - used to generate signatures, and the public key (in the - <code class="filename">.key</code> file) is used for signature - verification.</p> -<p>To generate another key with the same properties (but with - a different key tag), repeat the above command.</p> -<p>The public keys should be inserted into the zone file by - including the <code class="filename">.key</code> files using - <span><strong class="command">$INCLUDE</strong></span> statements. - </p> +<a name="id2571725"></a>Generating Keys</h3></div></div></div> +<p> + The <span><strong class="command">dnssec-keygen</strong></span> program is used to + generate keys. + </p> +<p> + A secure zone must contain one or more zone keys. The + zone keys will sign all other records in the zone, as well as + the zone keys of any secure delegated zones. Zone keys must + have the same name as the zone, a name type of + <span><strong class="command">ZONE</strong></span>, and must be usable for + authentication. + It is recommended that zone keys use a cryptographic algorithm + designated as "mandatory to implement" by the IETF; currently + the only one is RSASHA1. + </p> +<p> + The following command will generate a 768-bit RSASHA1 key for + the <code class="filename">child.example</code> zone: + </p> +<p> + <strong class="userinput"><code>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</code></strong> + </p> +<p> + Two output files will be produced: + <code class="filename">Kchild.example.+005+12345.key</code> and + <code class="filename">Kchild.example.+005+12345.private</code> + (where + 12345 is an example of a key tag). The key filenames contain + the key name (<code class="filename">child.example.</code>), + algorithm (3 + is DSA, 1 is RSAMD5, 5 is RSASHA1, etc.), and the key tag (12345 in + this case). + The private key (in the <code class="filename">.private</code> + file) is + used to generate signatures, and the public key (in the + <code class="filename">.key</code> file) is used for signature + verification. + </p> +<p> + To generate another key with the same properties (but with + a different key tag), repeat the above command. + </p> +<p> + The public keys should be inserted into the zone file by + including the <code class="filename">.key</code> files using + <span><strong class="command">$INCLUDE</strong></span> statements. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2574116"></a>Signing the Zone</h3></div></div></div> -<p>The <span><strong class="command">dnssec-signzone</strong></span> program is used to - sign a zone.</p> -<p>Any <code class="filename">keyset</code> files corresponding - to secure subzones should be present. The zone signer will - generate <code class="literal">NSEC</code> and <code class="literal">RRSIG</code> - records for the zone, as well as <code class="literal">DS</code> for - the child zones if <code class="literal">'-d'</code> is specified. - If <code class="literal">'-d'</code> is not specified, then DS RRsets for - the secure child zones need to be added manually.</p> -<p>The following command signs the zone, assuming it is in a - file called <code class="filename">zone.child.example</code>. By - default, all zone keys which have an available private key are - used to generate signatures.</p> -<p><strong class="userinput"><code>dnssec-signzone -o child.example zone.child.example</code></strong></p> -<p>One output file is produced: - <code class="filename">zone.child.example.signed</code>. This file - should be referenced by <code class="filename">named.conf</code> as the - input file for the zone.</p> -<p><span><strong class="command">dnssec-signzone</strong></span> will also produce a - keyset and dsset files and optionally a dlvset file. These - are used to provide the parent zone administators with the - <code class="literal">DNSKEYs</code> (or their corresponding <code class="literal">DS</code> - records) that are the secure entry point to the zone.</p> +<a name="id2571795"></a>Signing the Zone</h3></div></div></div> +<p> + The <span><strong class="command">dnssec-signzone</strong></span> program is used + to + sign a zone. + </p> +<p> + Any <code class="filename">keyset</code> files corresponding + to secure subzones should be present. The zone signer will + generate <code class="literal">NSEC</code> and <code class="literal">RRSIG</code> + records for the zone, as well as <code class="literal">DS</code> + for + the child zones if <code class="literal">'-d'</code> is specified. + If <code class="literal">'-d'</code> is not specified, then + DS RRsets for + the secure child zones need to be added manually. + </p> +<p> + The following command signs the zone, assuming it is in a + file called <code class="filename">zone.child.example</code>. By + default, all zone keys which have an available private key are + used to generate signatures. + </p> +<p> + <strong class="userinput"><code>dnssec-signzone -o child.example zone.child.example</code></strong> + </p> +<p> + One output file is produced: + <code class="filename">zone.child.example.signed</code>. This + file + should be referenced by <code class="filename">named.conf</code> + as the + input file for the zone. + </p> +<p><span><strong class="command">dnssec-signzone</strong></span> + will also produce a keyset and dsset files and optionally a + dlvset file. These are used to provide the parent zone + administrators with the <code class="literal">DNSKEYs</code> (or their + corresponding <code class="literal">DS</code> records) that are the + secure entry point to the zone. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2574259"></a>Configuring Servers</h3></div></div></div> +<a name="id2571874"></a>Configuring Servers</h3></div></div></div> <p> - To enable <span><strong class="command">named</strong></span> to respond appropriately - to DNS requests from DNSSEC aware clients, - <span><strong class="command">dnssec-enable</strong></span> must be set to yes. - </p> + To enable <span><strong class="command">named</strong></span> to respond appropriately + to DNS requests from DNSSEC aware clients, + <span><strong class="command">dnssec-enable</strong></span> must be set to yes. + </p> <p> - To enable <span><strong class="command">named</strong></span> to validate answers from - other servers <span><strong class="command">dnssec-enable</strong></span> and - some <span><strong class="command">trusted-keys</strong></span> must be configured - into <code class="filename">named.conf</code>. - </p> + To enable <span><strong class="command">named</strong></span> to validate answers from + other servers both <span><strong class="command">dnssec-enable</strong></span> and + <span><strong class="command">dnssec-validation</strong></span> must be set and some + <span><strong class="command">trusted-keys</strong></span> must be configured + into <code class="filename">named.conf</code>. + </p> +<p> + <span><strong class="command">trusted-keys</strong></span> are copies of DNSKEY RRs + for zones that are used to form the first link in the + cryptographic chain of trust. All keys listed in + <span><strong class="command">trusted-keys</strong></span> (and corresponding zones) + are deemed to exist and only the listed keys will be used + to validated the DNSKEY RRset that they are from. + </p> <p> - <span><strong class="command">trusted-keys</strong></span> are copies of DNSKEY RRs - for zones that are used to form the first link in the - cryptographic chain of trust. All keys listed in - <span><strong class="command">trusted-keys</strong></span> (and corresponding zones) - are deemed to exist and only the listed keys will be used - to validated the DNSKEY RRset that they are from. - </p> -<p> - <span><strong class="command">trusted-keys</strong></span> are described in more detail - later in this document. - </p> -<p> - Unlike <acronym class="acronym">BIND</acronym> 8, <acronym class="acronym">BIND</acronym> - 9 does not verify signatures on load, so zone keys for - authoritative zones do not need to be specified in the - configuration file. - </p> -<p> - After DNSSEC gets established, a typical DNSSEC configuration - will look something like the following. It has a one or - more public keys for the root. This allows answers from - outside the organization to be validated. It will also - have several keys for parts of the namespace the organization - controls. These are here to ensure that named is immune - to compromises in the DNSSEC components of the security - of parent zones. - </p> + <span><strong class="command">trusted-keys</strong></span> are described in more detail + later in this document. + </p> +<p> + Unlike <acronym class="acronym">BIND</acronym> 8, <acronym class="acronym">BIND</acronym> + 9 does not verify signatures on load, so zone keys for + authoritative zones do not need to be specified in the + configuration file. + </p> +<p> + After DNSSEC gets established, a typical DNSSEC configuration + will look something like the following. It has a one or + more public keys for the root. This allows answers from + outside the organization to be validated. It will also + have several keys for parts of the namespace the organization + controls. These are here to ensure that named is immune + to compromises in the DNSSEC components of the security + of parent zones. + </p> <pre class="programlisting"> trusted-keys { - /* Root Key */ + /* Root Key */ "." 257 3 3 "BNY4wrWM1nCfJ+CXd0rVXyYmobt7sEEfK3clRbGaTwSJxrGkxJWoZu6I7PzJu/ - E9gx4UC1zGAHlXKdE4zYIpRhaBKnvcC2U9mZhkdUpd1Vso/HAdjNe8LmMlnzY3 - zy2Xy4klWOADTPzSv9eamj8V18PHGjBLaVtYvk/ln5ZApjYghf+6fElrmLkdaz - MQ2OCnACR817DF4BBa7UR/beDHyp5iWTXWSi6XmoJLbG9Scqc7l70KDqlvXR3M - /lUUVRbkeg1IPJSidmK3ZyCllh4XSKbje/45SKucHgnwU5jefMtq66gKodQj+M - iA21AfUVe7u99WzTLzY3qlxDhxYQQ20FQ97S+LKUTpQcq27R7AT3/V5hRQxScI - Nqwcz4jYqZD2fQdgxbcDTClU0CRBdiieyLMNzXG3"; + E9gx4UC1zGAHlXKdE4zYIpRhaBKnvcC2U9mZhkdUpd1Vso/HAdjNe8LmMlnzY3 + zy2Xy4klWOADTPzSv9eamj8V18PHGjBLaVtYvk/ln5ZApjYghf+6fElrmLkdaz + MQ2OCnACR817DF4BBa7UR/beDHyp5iWTXWSi6XmoJLbG9Scqc7l70KDqlvXR3M + /lUUVRbkeg1IPJSidmK3ZyCllh4XSKbje/45SKucHgnwU5jefMtq66gKodQj+M + iA21AfUVe7u99WzTLzY3qlxDhxYQQ20FQ97S+LKUTpQcq27R7AT3/V5hRQxScI + Nqwcz4jYqZD2fQdgxbcDTClU0CRBdiieyLMNzXG3"; /* Key for our organization's forward zone */ example.com. 257 3 5 "AwEAAaxPMcR2x0HbQV4WeZB6oEDX+r0QM65KbhTjrW1ZaARmPhEZZe 3Y9ifgEuq7vZ/zGZUdEGNWy+JZzus0lUptwgjGwhUS1558Hb4JKUbb - OTcM8pwXlj0EiX3oDFVmjHO444gLkBO UKUf/mC7HvfwYH/Be22GnC - lrinKJp1Og4ywzO9WglMk7jbfW33gUKvirTHr25GL7STQUzBb5Usxt - 8lgnyTUHs1t3JwCY5hKZ6CqFxmAVZP20igTixin/1LcrgX/KMEGd/b - iuvF4qJCyduieHukuY3H4XMAcR+xia2 nIUPvm/oyWR8BW/hWdzOvn - SCThlHf3xiYleDbt/o1OTQ09A0="; + OTcM8pwXlj0EiX3oDFVmjHO444gLkBO UKUf/mC7HvfwYH/Be22GnC + lrinKJp1Og4ywzO9WglMk7jbfW33gUKvirTHr25GL7STQUzBb5Usxt + 8lgnyTUHs1t3JwCY5hKZ6CqFxmAVZP20igTixin/1LcrgX/KMEGd/b + iuvF4qJCyduieHukuY3H4XMAcR+xia2 nIUPvm/oyWR8BW/hWdzOvn + SCThlHf3xiYleDbt/o1OTQ09A0="; /* Key for our reverse zone. */ 2.0.192.IN-ADDRPA.NET. 257 3 5 "AQOnS4xn/IgOUpBPJ3bogzwcxOdNax071L18QqZnQQQA VVr+iLhGTnNGp3HoWQLUIzKrJVZ3zggy3WwNT6kZo6c0 - tszYqbtvchmgQC8CzKojM/W16i6MG/ea fGU3siaOdS0 - yOI6BgPsw+YZdzlYMaIJGf4M4dyoKIhzdZyQ2bYQrjyQ - 4LB0lC7aOnsMyYKHHYeRv PxjIQXmdqgOJGq+vsevG06 - zW+1xgYJh9rCIfnm1GX/KMgxLPG2vXTD/RnLX+D3T3UL - 7HJYHJhAZD5L59VvjSPsZJHeDCUyWYrvPZesZDIRvhDD - 52SKvbheeTJUm6EhkzytNN2SN96QRk8j/iI8ib"; + tszYqbtvchmgQC8CzKojM/W16i6MG/ea fGU3siaOdS0 + yOI6BgPsw+YZdzlYMaIJGf4M4dyoKIhzdZyQ2bYQrjyQ + 4LB0lC7aOnsMyYKHHYeRv PxjIQXmdqgOJGq+vsevG06 + zW+1xgYJh9rCIfnm1GX/KMgxLPG2vXTD/RnLX+D3T3UL + 7HJYHJhAZD5L59VvjSPsZJHeDCUyWYrvPZesZDIRvhDD + 52SKvbheeTJUm6EhkzytNN2SN96QRk8j/iI8ib"; }; options { - ... - dnssec-enable yes; + ... + dnssec-enable yes; + dnssec-validation yes; }; </pre> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> - None of the keys listed in this example are valid. In particular, - the root key is not valid. - </div> + None of the keys listed in this example are valid. In particular, + the root key is not valid. + </div> </div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2574396"></a>IPv6 Support in <acronym class="acronym">BIND</acronym> 9</h2></div></div></div> -<p><acronym class="acronym">BIND</acronym> 9 fully supports all currently defined forms of IPv6 - name to address and address to name lookups. It will also use - IPv6 addresses to make queries when running on an IPv6 capable - system.</p> -<p>For forward lookups, <acronym class="acronym">BIND</acronym> 9 supports only AAAA - records. The use of A6 records is deprecated by RFC 3363, and the - support for forward lookups in <acronym class="acronym">BIND</acronym> 9 is - removed accordingly. - However, authoritative <acronym class="acronym">BIND</acronym> 9 name servers still - load zone files containing A6 records correctly, answer queries - for A6 records, and accept zone transfer for a zone containing A6 - records.</p> -<p>For IPv6 reverse lookups, <acronym class="acronym">BIND</acronym> 9 supports - the traditional "nibble" format used in the - <span class="emphasis"><em>ip6.arpa</em></span> domain, as well as the older, deprecated - <span class="emphasis"><em>ip6.int</em></span> domain. - <acronym class="acronym">BIND</acronym> 9 formerly - supported the "binary label" (also known as "bitstring") format. - The support of binary labels, however, is now completely removed - according to the changes in RFC 3363. - Any applications in <acronym class="acronym">BIND</acronym> 9 do not understand - the format any more, and will return an error if given. - In particular, an authoritative <acronym class="acronym">BIND</acronym> 9 name - server rejects to load a zone file containing binary labels.</p> -<p>For an overview of the format and structure of IPv6 addresses, - see <a href="Bv9ARM.ch09.html#ipv6addresses" title="IPv6 addresses (AAAA)">the section called “IPv6 addresses (AAAA)”</a>.</p> +<a name="id2572153"></a>IPv6 Support in <acronym class="acronym">BIND</acronym> 9</h2></div></div></div> +<p> + <acronym class="acronym">BIND</acronym> 9 fully supports all currently + defined forms of IPv6 + name to address and address to name lookups. It will also use + IPv6 addresses to make queries when running on an IPv6 capable + system. + </p> +<p> + For forward lookups, <acronym class="acronym">BIND</acronym> 9 supports + only AAAA records. RFC 3363 deprecated the use of A6 records, + and client-side support for A6 records was accordingly removed + from <acronym class="acronym">BIND</acronym> 9. + However, authoritative <acronym class="acronym">BIND</acronym> 9 name servers still + load zone files containing A6 records correctly, answer queries + for A6 records, and accept zone transfer for a zone containing A6 + records. + </p> +<p> + For IPv6 reverse lookups, <acronym class="acronym">BIND</acronym> 9 supports + the traditional "nibble" format used in the + <span class="emphasis"><em>ip6.arpa</em></span> domain, as well as the older, deprecated + <span class="emphasis"><em>ip6.int</em></span> domain. + Older versions of <acronym class="acronym">BIND</acronym> 9 + supported the "binary label" (also known as "bitstring") format, + but support of binary labels has been completely removed per + RFC 3363. + Many applications in <acronym class="acronym">BIND</acronym> 9 do not understand + the binary label format at all any more, and will return an + error if given. + In particular, an authoritative <acronym class="acronym">BIND</acronym> 9 + name server will not load a zone file containing binary labels. + </p> +<p> + For an overview of the format and structure of IPv6 addresses, + see <a href="Bv9ARM.ch09.html#ipv6addresses" title="IPv6 addresses (AAAA)">the section called “IPv6 addresses (AAAA)”</a>. + </p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2574455"></a>Address Lookups Using AAAA Records</h3></div></div></div> -<p>The AAAA record is a parallel to the IPv4 A record. It - specifies the entire address in a single record. For - example,</p> +<a name="id2572215"></a>Address Lookups Using AAAA Records</h3></div></div></div> +<p> + The IPv6 AAAA record is a parallel to the IPv4 A record, + and, unlike the deprecated A6 record, specifies the entire + IPv6 address in a single record. For example, + </p> <pre class="programlisting"> $ORIGIN example.com. host 3600 IN AAAA 2001:db8::1 </pre> -<p>It is recommended that IPv4-in-IPv6 mapped addresses not - be used. If a host has an IPv4 address, use an A record, not - a AAAA, with <code class="literal">::ffff:192.168.42.1</code> as the - address.</p> +<p> + Use of IPv4-in-IPv6 mapped addresses is not recommended. + If a host has an IPv4 address, use an A record, not + a AAAA, with <code class="literal">::ffff:192.168.42.1</code> as + the address. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2574475"></a>Address to Name Lookups Using Nibble Format</h3></div></div></div> -<p>When looking up an address in nibble format, the address - components are simply reversed, just as in IPv4, and - <code class="literal">ip6.arpa.</code> is appended to the resulting name. - For example, the following would provide reverse name lookup for - a host with address - <code class="literal">2001:db8::1</code>.</p> +<a name="id2572236"></a>Address to Name Lookups Using Nibble Format</h3></div></div></div> +<p> + When looking up an address in nibble format, the address + components are simply reversed, just as in IPv4, and + <code class="literal">ip6.arpa.</code> is appended to the + resulting name. + For example, the following would provide reverse name lookup for + a host with address + <code class="literal">2001:db8::1</code>. + </p> <pre class="programlisting"> $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa. 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 14400 IN PTR host.example.com. diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch05.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch05.html index ec6c188edca..cecaaf5997d 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch05.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch05.html @@ -1,5 +1,5 @@ <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - Permission to use, copy, modify, and distribute this software for any @@ -14,12 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $ISC: Bv9ARM.ch05.html,v 1.24.2.5.2.17 2006/06/29 13:02:31 marka Exp $ --> +<!-- $ISC: Bv9ARM.ch05.html,v 1.33.18.33 2007/10/31 01:35:58 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Chapter 5. The BIND 9 Lightweight Resolver</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="prev" href="Bv9ARM.ch04.html" title="Chapter 4. Advanced DNS Features"> @@ -45,53 +45,81 @@ <div class="toc"> <p><b>Table of Contents</b></p> <dl> -<dt><span class="sect1"><a href="Bv9ARM.ch05.html#id2574507">The Lightweight Resolver Library</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch05.html#id2572269">The Lightweight Resolver Library</a></span></dt> <dt><span class="sect1"><a href="Bv9ARM.ch05.html#lwresd">Running a Resolver Daemon</a></span></dt> </dl> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2574507"></a>The Lightweight Resolver Library</h2></div></div></div> -<p>Traditionally applications have been linked with a stub resolver -library that sends recursive DNS queries to a local caching name -server.</p> -<p>IPv6 once introduced new complexity into the resolution process, -such as following A6 chains and DNAME records, and simultaneous -lookup of IPv4 and IPv6 addresses. Though most of the complexity was -then removed, these are hard or impossible -to implement in a traditional stub resolver.</p> -<p>Instead, <acronym class="acronym">BIND</acronym> 9 provides resolution services to local clients -using a combination of a lightweight resolver library and a resolver -daemon process running on the local host. These communicate using -a simple UDP-based protocol, the "lightweight resolver protocol" -that is distinct from and simpler than the full DNS protocol.</p> +<a name="id2572269"></a>The Lightweight Resolver Library</h2></div></div></div> +<p> + Traditionally applications have been linked with a stub resolver + library that sends recursive DNS queries to a local caching name + server. + </p> +<p> + IPv6 once introduced new complexity into the resolution process, + such as following A6 chains and DNAME records, and simultaneous + lookup of IPv4 and IPv6 addresses. Though most of the complexity was + then removed, these are hard or impossible + to implement in a traditional stub resolver. + </p> +<p> + <acronym class="acronym">BIND</acronym> 9 therefore can also provide resolution + services to local clients + using a combination of a lightweight resolver library and a resolver + daemon process running on the local host. These communicate using + a simple UDP-based protocol, the "lightweight resolver protocol" + that is distinct from and simpler than the full DNS protocol. + </p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="lwresd"></a>Running a Resolver Daemon</h2></div></div></div> -<p>To use the lightweight resolver interface, the system must -run the resolver daemon <span><strong class="command">lwresd</strong></span> or a local -name server configured with a <span><strong class="command">lwres</strong></span> statement.</p> -<p>By default, applications using the lightweight resolver library will make -UDP requests to the IPv4 loopback address (127.0.0.1) on port 921. The -address can be overridden by <span><strong class="command">lwserver</strong></span> lines in -<code class="filename">/etc/resolv.conf</code>.</p> -<p>The daemon currently only looks in the DNS, but in the future -it may use other sources such as <code class="filename">/etc/hosts</code>, -NIS, etc.</p> -<p>The <span><strong class="command">lwresd</strong></span> daemon is essentially a -caching-only name server that responds to requests using the lightweight -resolver protocol rather than the DNS protocol. Because it needs -to run on each host, it is designed to require no or minimal configuration. -Unless configured otherwise, it uses the name servers listed on -<span><strong class="command">nameserver</strong></span> lines in <code class="filename">/etc/resolv.conf</code> -as forwarders, but is also capable of doing the resolution autonomously if -none are specified.</p> -<p>The <span><strong class="command">lwresd</strong></span> daemon may also be configured with a -<code class="filename">named.conf</code> style configuration file, in -<code class="filename">/etc/lwresd.conf</code> by default. A name server may also -be configured to act as a lightweight resolver daemon using the -<span><strong class="command">lwres</strong></span> statement in <code class="filename">named.conf</code>.</p> +<p> + To use the lightweight resolver interface, the system must + run the resolver daemon <span><strong class="command">lwresd</strong></span> or a + local + name server configured with a <span><strong class="command">lwres</strong></span> + statement. + </p> +<p> + By default, applications using the lightweight resolver library will + make + UDP requests to the IPv4 loopback address (127.0.0.1) on port 921. + The + address can be overridden by <span><strong class="command">lwserver</strong></span> + lines in + <code class="filename">/etc/resolv.conf</code>. + </p> +<p> + The daemon currently only looks in the DNS, but in the future + it may use other sources such as <code class="filename">/etc/hosts</code>, + NIS, etc. + </p> +<p> + The <span><strong class="command">lwresd</strong></span> daemon is essentially a + caching-only name server that responds to requests using the + lightweight + resolver protocol rather than the DNS protocol. Because it needs + to run on each host, it is designed to require no or minimal + configuration. + Unless configured otherwise, it uses the name servers listed on + <span><strong class="command">nameserver</strong></span> lines in <code class="filename">/etc/resolv.conf</code> + as forwarders, but is also capable of doing the resolution + autonomously if + none are specified. + </p> +<p> + The <span><strong class="command">lwresd</strong></span> daemon may also be + configured with a + <code class="filename">named.conf</code> style configuration file, + in + <code class="filename">/etc/lwresd.conf</code> by default. A name + server may also + be configured to act as a lightweight resolver daemon using the + <span><strong class="command">lwres</strong></span> statement in <code class="filename">named.conf</code>. + </p> </div> </div> <div class="navfooter"> diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch06.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch06.html index 0d6ec9b1643..ef243d58d67 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch06.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch06.html @@ -1,5 +1,5 @@ <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - Permission to use, copy, modify, and distribute this software for any @@ -14,12 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $ISC: Bv9ARM.ch06.html,v 1.56.2.12.2.43 2006/11/15 04:33:41 marka Exp $ --> +<!-- $ISC: Bv9ARM.ch06.html,v 1.82.18.73 2007/10/31 01:35:58 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Chapter 6. BIND 9 Configuration Reference</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="prev" href="Bv9ARM.ch05.html" title="Chapter 5. The BIND 9 Lightweight Resolver"> @@ -48,64 +48,79 @@ <dt><span class="sect1"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575672">Comment Syntax</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2573480">Comment Syntax</a></span></dt> </dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576157"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574092"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#acl"><span><strong class="command">acl</strong></span> Statement Definition and -Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576326"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576672"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576686"><span><strong class="command">include</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576709"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576730"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576870"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577064"><span><strong class="command">logging</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578270"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578343"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578406"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578518"><span><strong class="command">masters</strong></span> Statement Definition and Usage </a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578533"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and Usage</a></span></dt> + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574282"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574711"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574726"><span><strong class="command">include</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574749"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574771"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574930"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575056"><span><strong class="command">logging</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576406"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576480"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576544"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576587"><span><strong class="command">masters</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576602"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and + Usage</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2586290"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2586338"><span><strong class="command">trusted-keys</strong></span> Statement Definition - and Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2585361"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2585410"><span><strong class="command">trusted-keys</strong></span> Statement Definition + and Usage</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span><strong class="command">view</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2586420"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2585490"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span> -Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2587635"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt> + Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2586798"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2589173">Zone File</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2589080">Zone File</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2590605">Discussion of MX Records</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591101">Discussion of MX Records</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591102">Inverse Mapping in IPv4</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591208">Other Zone File Directives</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591377"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591653">Inverse Mapping in IPv4</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591848">Other Zone File Directives</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2592173"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt> </dl></dd> </dl> </div> -<p><acronym class="acronym">BIND</acronym> 9 configuration is broadly similar -to <acronym class="acronym">BIND</acronym> 8; however, there are a few new areas -of configuration, such as views. <acronym class="acronym">BIND</acronym> -8 configuration files should work with few alterations in <acronym class="acronym">BIND</acronym> -9, although more complex configurations should be reviewed to check -if they can be more efficiently implemented using the new features -found in <acronym class="acronym">BIND</acronym> 9.</p> -<p><acronym class="acronym">BIND</acronym> 4 configuration files can be converted to the new format -using the shell script -<code class="filename">contrib/named-bootconf/named-bootconf.sh</code>.</p> +<p> + <acronym class="acronym">BIND</acronym> 9 configuration is broadly similar + to <acronym class="acronym">BIND</acronym> 8; however, there are a few new + areas + of configuration, such as views. <acronym class="acronym">BIND</acronym> + 8 configuration files should work with few alterations in <acronym class="acronym">BIND</acronym> + 9, although more complex configurations should be reviewed to check + if they can be more efficiently implemented using the new features + found in <acronym class="acronym">BIND</acronym> 9. + </p> +<p> + <acronym class="acronym">BIND</acronym> 4 configuration files can be + converted to the new format + using the shell script + <code class="filename">contrib/named-bootconf/named-bootconf.sh</code>. + </p> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="configuration_file_elements"></a>Configuration File Elements</h2></div></div></div> -<p>Following is a list of elements used throughout the <acronym class="acronym">BIND</acronym> configuration -file documentation:</p> +<p> + Following is a list of elements used throughout the <acronym class="acronym">BIND</acronym> configuration + file documentation: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -113,129 +128,298 @@ file documentation:</p> </colgroup> <tbody> <tr> -<td><p><code class="varname">acl_name</code></p></td> -<td><p>The name of an <code class="varname">address_match_list</code> as -defined by the <span><strong class="command">acl</strong></span> statement.</p></td> +<td> + <p> + <code class="varname">acl_name</code> + </p> + </td> +<td> + <p> + The name of an <code class="varname">address_match_list</code> as + defined by the <span><strong class="command">acl</strong></span> statement. + </p> + </td> </tr> <tr> -<td><p><code class="varname">address_match_list</code></p></td> -<td><p>A list of one or more <code class="varname">ip_addr</code>, -<code class="varname">ip_prefix</code>, <code class="varname">key_id</code>, -or <code class="varname">acl_name</code> elements, see -<a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called “Address Match Lists”</a>.</p></td> +<td> + <p> + <code class="varname">address_match_list</code> + </p> + </td> +<td> + <p> + A list of one or more + <code class="varname">ip_addr</code>, + <code class="varname">ip_prefix</code>, <code class="varname">key_id</code>, + or <code class="varname">acl_name</code> elements, see + <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called “Address Match Lists”</a>. + </p> + </td> </tr> <tr> -<td><p><code class="varname">domain_name</code></p></td> -<td><p>A quoted string which will be used as -a DNS name, for example "<code class="literal">my.test.domain</code>".</p></td> +<td> + <p> + <code class="varname">masters_list</code> + </p> + </td> +<td> + <p> + A named list of one or more <code class="varname">ip_addr</code> + with optional <code class="varname">key_id</code> and/or + <code class="varname">ip_port</code>. + A <code class="varname">masters_list</code> may include other + <code class="varname">masters_lists</code>. + </p> + </td> </tr> <tr> -<td><p><code class="varname">dotted_decimal</code></p></td> -<td><p>One to four integers valued 0 through -255 separated by dots (`.'), such as <span><strong class="command">123</strong></span>, -<span><strong class="command">45.67</strong></span> or <span><strong class="command">89.123.45.67</strong></span>.</p></td> +<td> + <p> + <code class="varname">domain_name</code> + </p> + </td> +<td> + <p> + A quoted string which will be used as + a DNS name, for example "<code class="literal">my.test.domain</code>". + </p> + </td> </tr> <tr> -<td><p><code class="varname">ip4_addr</code></p></td> -<td><p>An IPv4 address with exactly four elements -in <code class="varname">dotted_decimal</code> notation.</p></td> +<td> + <p> + <code class="varname">dotted_decimal</code> + </p> + </td> +<td> + <p> + One to four integers valued 0 through + 255 separated by dots (`.'), such as <span><strong class="command">123</strong></span>, + <span><strong class="command">45.67</strong></span> or <span><strong class="command">89.123.45.67</strong></span>. + </p> + </td> </tr> <tr> -<td><p><code class="varname">ip6_addr</code></p></td> -<td><p>An IPv6 address, such as <span><strong class="command">2001:db8::1234</strong></span>. -IPv6 scoped addresses that have ambiguity on their scope zones must be -disambiguated by an appropriate zone ID with the percent character -(`%') as delimiter. -It is strongly recommended to use string zone names rather than -numeric identifiers, in order to be robust against system -configuration changes. -However, since there is no standard mapping for such names and -identifier values, currently only interface names as link identifiers -are supported, assuming one-to-one mapping between interfaces and links. -For example, a link-local address <span><strong class="command">fe80::1</strong></span> on the -link attached to the interface <span><strong class="command">ne0</strong></span> -can be specified as <span><strong class="command">fe80::1%ne0</strong></span>. -Note that on most systems link-local addresses always have the -ambiguity, and need to be disambiguated.</p></td> +<td> + <p> + <code class="varname">ip4_addr</code> + </p> + </td> +<td> + <p> + An IPv4 address with exactly four elements + in <code class="varname">dotted_decimal</code> notation. + </p> + </td> </tr> <tr> -<td><p><code class="varname">ip_addr</code></p></td> -<td><p>An <code class="varname">ip4_addr</code> or <code class="varname">ip6_addr</code>.</p></td> +<td> + <p> + <code class="varname">ip6_addr</code> + </p> + </td> +<td> + <p> + An IPv6 address, such as <span><strong class="command">2001:db8::1234</strong></span>. + IPv6 scoped addresses that have ambiguity on their scope + zones must be + disambiguated by an appropriate zone ID with the percent + character + (`%') as delimiter. + It is strongly recommended to use string zone names rather + than + numeric identifiers, in order to be robust against system + configuration changes. + However, since there is no standard mapping for such names + and + identifier values, currently only interface names as link + identifiers + are supported, assuming one-to-one mapping between + interfaces and links. + For example, a link-local address <span><strong class="command">fe80::1</strong></span> on the + link attached to the interface <span><strong class="command">ne0</strong></span> + can be specified as <span><strong class="command">fe80::1%ne0</strong></span>. + Note that on most systems link-local addresses always have + the + ambiguity, and need to be disambiguated. + </p> + </td> </tr> <tr> -<td><p><code class="varname">ip_port</code></p></td> -<td><p>An IP port <code class="varname">number</code>. -<code class="varname">number</code> is limited to 0 through 65535, with values -below 1024 typically restricted to use by processes running as root. -In some cases, an asterisk (`*') character can be used as a placeholder to -select a random high-numbered port.</p></td> +<td> + <p> + <code class="varname">ip_addr</code> + </p> + </td> +<td> + <p> + An <code class="varname">ip4_addr</code> or <code class="varname">ip6_addr</code>. + </p> + </td> </tr> <tr> -<td><p><code class="varname">ip_prefix</code></p></td> -<td><p>An IP network specified as an <code class="varname">ip_addr</code>, -followed by a slash (`/') and then the number of bits in the netmask. -Trailing zeros in a <code class="varname">ip_addr</code> may omitted. -For example, <span><strong class="command">127/8</strong></span> is the network <span><strong class="command">127.0.0.0</strong></span> with -netmask <span><strong class="command">255.0.0.0</strong></span> and <span><strong class="command">1.2.3.0/28</strong></span> is -network <span><strong class="command">1.2.3.0</strong></span> with netmask <span><strong class="command">255.255.255.240</strong></span>.</p></td> +<td> + <p> + <code class="varname">ip_port</code> + </p> + </td> +<td> + <p> + An IP port <code class="varname">number</code>. + The <code class="varname">number</code> is limited to 0 + through 65535, with values + below 1024 typically restricted to use by processes running + as root. + In some cases, an asterisk (`*') character can be used as a + placeholder to + select a random high-numbered port. + </p> + </td> </tr> <tr> -<td><p><code class="varname">key_id</code></p></td> -<td><p>A <code class="varname">domain_name</code> representing -the name of a shared key, to be used for transaction security.</p></td> +<td> + <p> + <code class="varname">ip_prefix</code> + </p> + </td> +<td> + <p> + An IP network specified as an <code class="varname">ip_addr</code>, + followed by a slash (`/') and then the number of bits in the + netmask. + Trailing zeros in a <code class="varname">ip_addr</code> + may omitted. + For example, <span><strong class="command">127/8</strong></span> is the + network <span><strong class="command">127.0.0.0</strong></span> with + netmask <span><strong class="command">255.0.0.0</strong></span> and <span><strong class="command">1.2.3.0/28</strong></span> is + network <span><strong class="command">1.2.3.0</strong></span> with netmask <span><strong class="command">255.255.255.240</strong></span>. + </p> + </td> </tr> <tr> -<td><p><code class="varname">key_list</code></p></td> -<td><p>A list of one or more <code class="varname">key_id</code>s, -separated by semicolons and ending with a semicolon.</p></td> +<td> + <p> + <code class="varname">key_id</code> + </p> + </td> +<td> + <p> + A <code class="varname">domain_name</code> representing + the name of a shared key, to be used for transaction + security. + </p> + </td> </tr> <tr> -<td><p><code class="varname">number</code></p></td> -<td><p>A non-negative 32-bit integer -(i.e., a number between 0 and 4294967295, inclusive). -Its acceptable value might further -be limited by the context in which it is used.</p></td> +<td> + <p> + <code class="varname">key_list</code> + </p> + </td> +<td> + <p> + A list of one or more + <code class="varname">key_id</code>s, + separated by semicolons and ending with a semicolon. + </p> + </td> </tr> <tr> -<td><p><code class="varname">path_name</code></p></td> -<td><p>A quoted string which will be used as -a pathname, such as <code class="filename">zones/master/my.test.domain</code>.</p></td> +<td> + <p> + <code class="varname">number</code> + </p> + </td> +<td> + <p> + A non-negative 32-bit integer + (i.e., a number between 0 and 4294967295, inclusive). + Its acceptable value might further + be limited by the context in which it is used. + </p> + </td> </tr> <tr> -<td><p><code class="varname">size_spec</code></p></td> <td> -<p>A number, the word <strong class="userinput"><code>unlimited</code></strong>, -or the word <strong class="userinput"><code>default</code></strong>.</p> -<p> -An <code class="varname">unlimited</code> <code class="varname">size_spec</code> requests unlimited -use, or the maximum available amount. A <code class="varname">default size_spec</code> uses -the limit that was in force when the server was started.</p> -<p>A <code class="varname">number</code> can -optionally be followed by a scaling factor: <strong class="userinput"><code>K</code></strong> or <strong class="userinput"><code>k</code></strong> for -kilobytes, <strong class="userinput"><code>M</code></strong> or <strong class="userinput"><code>m</code></strong> for -megabytes, and <strong class="userinput"><code>G</code></strong> or <strong class="userinput"><code>g</code></strong> for gigabytes, -which scale by 1024, 1024*1024, and 1024*1024*1024 respectively.</p> -<p>The value must be representable as a 64-bit unsigned integer -(0 to 18446744073709551615, inclusive). -Using <code class="varname">unlimited</code> is the best way -to safely set a really large number.</p> -</td> + <p> + <code class="varname">path_name</code> + </p> + </td> +<td> + <p> + A quoted string which will be used as + a pathname, such as <code class="filename">zones/master/my.test.domain</code>. + </p> + </td> +</tr> +<tr> +<td> + <p> + <code class="varname">size_spec</code> + </p> + </td> +<td> + <p> + A number, the word <strong class="userinput"><code>unlimited</code></strong>, + or the word <strong class="userinput"><code>default</code></strong>. + </p> + <p> + An <code class="varname">unlimited</code> <code class="varname">size_spec</code> requests unlimited + use, or the maximum available amount. A <code class="varname">default size_spec</code> uses + the limit that was in force when the server was started. + </p> + <p> + A <code class="varname">number</code> can optionally be + followed by a scaling factor: + <strong class="userinput"><code>K</code></strong> or <strong class="userinput"><code>k</code></strong> + for kilobytes, + <strong class="userinput"><code>M</code></strong> or <strong class="userinput"><code>m</code></strong> + for megabytes, and + <strong class="userinput"><code>G</code></strong> or <strong class="userinput"><code>g</code></strong> for gigabytes, + which scale by 1024, 1024*1024, and 1024*1024*1024 + respectively. + </p> + <p> + The value must be representable as a 64-bit unsigned integer + (0 to 18446744073709551615, inclusive). + Using <code class="varname">unlimited</code> is the best + way + to safely set a really large number. + </p> + </td> </tr> <tr> -<td><p><code class="varname">yes_or_no</code></p></td> -<td><p>Either <strong class="userinput"><code>yes</code></strong> or <strong class="userinput"><code>no</code></strong>. -The words <strong class="userinput"><code>true</code></strong> and <strong class="userinput"><code>false</code></strong> are -also accepted, as are the numbers <strong class="userinput"><code>1</code></strong> and <strong class="userinput"><code>0</code></strong>.</p></td> +<td> + <p> + <code class="varname">yes_or_no</code> + </p> + </td> +<td> + <p> + Either <strong class="userinput"><code>yes</code></strong> or <strong class="userinput"><code>no</code></strong>. + The words <strong class="userinput"><code>true</code></strong> and <strong class="userinput"><code>false</code></strong> are + also accepted, as are the numbers <strong class="userinput"><code>1</code></strong> + and <strong class="userinput"><code>0</code></strong>. + </p> + </td> </tr> <tr> -<td><p><code class="varname">dialup_option</code></p></td> -<td><p>One of <strong class="userinput"><code>yes</code></strong>, -<strong class="userinput"><code>no</code></strong>, <strong class="userinput"><code>notify</code></strong>, -<strong class="userinput"><code>notify-passive</code></strong>, <strong class="userinput"><code>refresh</code></strong> or -<strong class="userinput"><code>passive</code></strong>. -When used in a zone, <strong class="userinput"><code>notify-passive</code></strong>, -<strong class="userinput"><code>refresh</code></strong>, and <strong class="userinput"><code>passive</code></strong> -are restricted to slave and stub zones.</p></td> +<td> + <p> + <code class="varname">dialup_option</code> + </p> + </td> +<td> + <p> + One of <strong class="userinput"><code>yes</code></strong>, + <strong class="userinput"><code>no</code></strong>, <strong class="userinput"><code>notify</code></strong>, + <strong class="userinput"><code>notify-passive</code></strong>, <strong class="userinput"><code>refresh</code></strong> or + <strong class="userinput"><code>passive</code></strong>. + When used in a zone, <strong class="userinput"><code>notify-passive</code></strong>, + <strong class="userinput"><code>refresh</code></strong>, and <strong class="userinput"><code>passive</code></strong> + are restricted to slave and stub zones. + </p> + </td> </tr> </tbody> </table></div> @@ -244,7 +428,7 @@ are restricted to slave and stub zones.</p></td> <a name="address_match_lists"></a>Address Match Lists</h3></div></div></div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2575552"></a>Syntax</h4></div></div></div> +<a name="id2573277"></a>Syntax</h4></div></div></div> <pre class="programlisting"><code class="varname">address_match_list</code> = address_match_list_element ; [<span class="optional"> address_match_list_element; ... </span>] <code class="varname">address_match_list_element</code> = [<span class="optional"> ! </span>] (ip_address [<span class="optional">/length</span>] | @@ -253,115 +437,181 @@ are restricted to slave and stub zones.</p></td> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2575578"></a>Definition and Usage</h4></div></div></div> -<p>Address match lists are primarily used to determine access -control for various server operations. They are also used in -the <span><strong class="command">listen-on</strong></span> and <span><strong class="command">sortlist</strong></span> -statements. The elements -which constitute an address match list can be any of the following:</p> +<a name="id2573305"></a>Definition and Usage</h4></div></div></div> +<p> + Address match lists are primarily used to determine access + control for various server operations. They are also used in + the <span><strong class="command">listen-on</strong></span> and <span><strong class="command">sortlist</strong></span> + statements. The elements + which constitute an address match list can be any of the + following: + </p> <div class="itemizedlist"><ul type="disc"> <li>an IP address (IPv4 or IPv6)</li> <li>an IP prefix (in `/' notation)</li> -<li>a key ID, as defined by the <span><strong class="command">key</strong></span> statement</li> +<li> + a key ID, as defined by the <span><strong class="command">key</strong></span> + statement + </li> <li>the name of an address match list defined with -the <span><strong class="command">acl</strong></span> statement</li> + the <span><strong class="command">acl</strong></span> statement + </li> <li>a nested address match list enclosed in braces</li> </ul></div> -<p>Elements can be negated with a leading exclamation mark (`!'), -and the match list names "any", "none", "localhost", and "localnets" -are predefined. More information on those names can be found in -the description of the acl statement.</p> -<p>The addition of the key clause made the name of this syntactic -element something of a misnomer, since security keys can be used -to validate access without regard to a host or network address. Nonetheless, -the term "address match list" is still used throughout the documentation.</p> -<p>When a given IP address or prefix is compared to an address -match list, the list is traversed in order until an element matches. -The interpretation of a match depends on whether the list is being used -for access control, defining listen-on ports, or in a sortlist, -and whether the element was negated.</p> -<p>When used as an access control list, a non-negated match allows -access and a negated match denies access. If there is no match, -access is denied. The clauses <span><strong class="command">allow-notify</strong></span>, -<span><strong class="command">allow-query</strong></span>, <span><strong class="command">allow-transfer</strong></span>, -<span><strong class="command">allow-update</strong></span>, <span><strong class="command">allow-update-forwarding</strong></span>, -and <span><strong class="command">blackhole</strong></span> all -use address match lists this. Similarly, the listen-on option will cause -the server to not accept queries on any of the machine's addresses -which do not match the list.</p> -<p>Because of the first-match aspect of the algorithm, an element -that defines a subset of another element in the list should come -before the broader element, regardless of whether either is negated. For -example, in -<span><strong class="command">1.2.3/24; ! 1.2.3.13;</strong></span> the 1.2.3.13 element is -completely useless because the algorithm will match any lookup for -1.2.3.13 to the 1.2.3/24 element. -Using <span><strong class="command">! 1.2.3.13; 1.2.3/24</strong></span> fixes -that problem by having 1.2.3.13 blocked by the negation but all -other 1.2.3.* hosts fall through.</p> +<p> + Elements can be negated with a leading exclamation mark (`!'), + and the match list names "any", "none", "localhost", and + "localnets" + are predefined. More information on those names can be found in + the description of the acl statement. + </p> +<p> + The addition of the key clause made the name of this syntactic + element something of a misnomer, since security keys can be used + to validate access without regard to a host or network address. + Nonetheless, + the term "address match list" is still used throughout the + documentation. + </p> +<p> + When a given IP address or prefix is compared to an address + match list, the list is traversed in order until an element + matches. + The interpretation of a match depends on whether the list is being + used + for access control, defining listen-on ports, or in a sortlist, + and whether the element was negated. + </p> +<p> + When used as an access control list, a non-negated match + allows access and a negated match denies access. If + there is no match, access is denied. The clauses + <span><strong class="command">allow-notify</strong></span>, + <span><strong class="command">allow-query</strong></span>, + <span><strong class="command">allow-query-cache</strong></span>, + <span><strong class="command">allow-transfer</strong></span>, + <span><strong class="command">allow-update</strong></span>, + <span><strong class="command">allow-update-forwarding</strong></span>, and + <span><strong class="command">blackhole</strong></span> all use address match + lists. Similarly, the listen-on option will cause the + server to not accept queries on any of the machine's + addresses which do not match the list. + </p> +<p> + Because of the first-match aspect of the algorithm, an element + that defines a subset of another element in the list should come + before the broader element, regardless of whether either is + negated. For + example, in + <span><strong class="command">1.2.3/24; ! 1.2.3.13;</strong></span> the 1.2.3.13 + element is + completely useless because the algorithm will match any lookup for + 1.2.3.13 to the 1.2.3/24 element. + Using <span><strong class="command">! 1.2.3.13; 1.2.3/24</strong></span> fixes + that problem by having 1.2.3.13 blocked by the negation but all + other 1.2.3.* hosts fall through. + </p> </div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2575672"></a>Comment Syntax</h3></div></div></div> -<p>The <acronym class="acronym">BIND</acronym> 9 comment syntax allows for comments to appear -anywhere that white space may appear in a <acronym class="acronym">BIND</acronym> configuration -file. To appeal to programmers of all kinds, they can be written -in the C, C++, or shell/perl style.</p> +<a name="id2573480"></a>Comment Syntax</h3></div></div></div> +<p> + The <acronym class="acronym">BIND</acronym> 9 comment syntax allows for + comments to appear + anywhere that whitespace may appear in a <acronym class="acronym">BIND</acronym> configuration + file. To appeal to programmers of all kinds, they can be written + in the C, C++, or shell/perl style. + </p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2575687"></a>Syntax</h4></div></div></div> +<a name="id2573495"></a>Syntax</h4></div></div></div> +<p> + </p> <pre class="programlisting">/* This is a <acronym class="acronym">BIND</acronym> comment as in C */</pre> <p> -</p> + </p> <pre class="programlisting">// This is a <acronym class="acronym">BIND</acronym> comment as in C++</pre> <p> -</p> + </p> <pre class="programlisting"># This is a <acronym class="acronym">BIND</acronym> comment as in common UNIX shells and perl</pre> <p> - </p> + </p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2575716"></a>Definition and Usage</h4></div></div></div> -<p>Comments may appear anywhere that white space may appear in -a <acronym class="acronym">BIND</acronym> configuration file.</p> -<p>C-style comments start with the two characters /* (slash, -star) and end with */ (star, slash). Because they are completely -delimited with these characters, they can be used to comment only -a portion of a line or to span multiple lines.</p> -<p>C-style comments cannot be nested. For example, the following -is not valid because the entire comment ends with the first */:</p> +<a name="id2573525"></a>Definition and Usage</h4></div></div></div> +<p> + Comments may appear anywhere that whitespace may appear in + a <acronym class="acronym">BIND</acronym> configuration file. + </p> +<p> + C-style comments start with the two characters /* (slash, + star) and end with */ (star, slash). Because they are completely + delimited with these characters, they can be used to comment only + a portion of a line or to span multiple lines. + </p> +<p> + C-style comments cannot be nested. For example, the following + is not valid because the entire comment ends with the first */: + </p> +<p> + +</p> <pre class="programlisting">/* This is the start of a comment. This is still part of the comment. /* This is an incorrect attempt at nesting a comment. */ This is no longer in any comment. */ </pre> -<p>C++-style comments start with the two characters // (slash, -slash) and continue to the end of the physical line. They cannot -be continued across multiple physical lines; to have one logical -comment span multiple lines, each line must use the // pair.</p> -<p>For example:</p> +<p> + + </p> +<p> + C++-style comments start with the two characters // (slash, + slash) and continue to the end of the physical line. They cannot + be continued across multiple physical lines; to have one logical + comment span multiple lines, each line must use the // pair. + </p> +<p> + For example: + </p> +<p> + +</p> <pre class="programlisting">// This is the start of a comment. The next line // is a new comment, even though it is logically // part of the previous comment. </pre> -<p>Shell-style (or perl-style, if you prefer) comments start -with the character <code class="literal">#</code> (number sign) and continue to the end of the -physical line, as in C++ comments.</p> -<p>For example:</p> +<p> + + </p> +<p> + Shell-style (or perl-style, if you prefer) comments start + with the character <code class="literal">#</code> (number sign) + and continue to the end of the + physical line, as in C++ comments. + </p> +<p> + For example: + </p> +<p> + +</p> <pre class="programlisting"># This is the start of a comment. The next line # is a new comment, even though it is logically # part of the previous comment. </pre> <p> -</p> + + </p> <div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Warning</h3> -<p>You cannot use the semicolon (`;') character - to start a comment such as you would in a zone file. The - semicolon indicates the end of a configuration - statement.</p> +<p> + You cannot use the semicolon (`;') character + to start a comment such as you would in a zone file. The + semicolon indicates the end of a configuration + statement. + </p> </div> </div> </div> @@ -369,12 +619,17 @@ physical line, as in C++ comments.</p> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="Configuration_File_Grammar"></a>Configuration File Grammar</h2></div></div></div> -<p>A <acronym class="acronym">BIND</acronym> 9 configuration consists of statements and comments. - Statements end with a semicolon. Statements and comments are the - only elements that can appear without enclosing braces. Many - statements contain a block of sub-statements, which are also - terminated with a semicolon.</p> -<p>The following statements are supported:</p> +<p> + A <acronym class="acronym">BIND</acronym> 9 configuration consists of + statements and comments. + Statements end with a semicolon. Statements and comments are the + only elements that can appear without enclosing braces. Many + statements contain a block of sub-statements, which are also + terminated with a semicolon. + </p> +<p> + The following statements are supported: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -382,85 +637,167 @@ physical line, as in C++ comments.</p> </colgroup> <tbody> <tr> -<td><p><span><strong class="command">acl</strong></span></p></td> -<td><p>defines a named IP address -matching list, for access control and other uses.</p></td> +<td> + <p><span><strong class="command">acl</strong></span></p> + </td> +<td> + <p> + defines a named IP address + matching list, for access control and other uses. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">controls</strong></span></p></td> -<td><p>declares control channels to be used -by the <span><strong class="command">rndc</strong></span> utility.</p></td> +<td> + <p><span><strong class="command">controls</strong></span></p> + </td> +<td> + <p> + declares control channels to be used + by the <span><strong class="command">rndc</strong></span> utility. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">include</strong></span></p></td> -<td><p>includes a file.</p></td> +<td> + <p><span><strong class="command">include</strong></span></p> + </td> +<td> + <p> + includes a file. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">key</strong></span></p></td> -<td><p>specifies key information for use in -authentication and authorization using TSIG.</p></td> +<td> + <p><span><strong class="command">key</strong></span></p> + </td> +<td> + <p> + specifies key information for use in + authentication and authorization using TSIG. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">logging</strong></span></p></td> -<td><p>specifies what the server logs, and where -the log messages are sent.</p></td> +<td> + <p><span><strong class="command">logging</strong></span></p> + </td> +<td> + <p> + specifies what the server logs, and where + the log messages are sent. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">lwres</strong></span></p></td> -<td><p>configures <span><strong class="command">named</strong></span> to -also act as a light-weight resolver daemon (<span><strong class="command">lwresd</strong></span>).</p></td> +<td> + <p><span><strong class="command">lwres</strong></span></p> + </td> +<td> + <p> + configures <span><strong class="command">named</strong></span> to + also act as a light-weight resolver daemon (<span><strong class="command">lwresd</strong></span>). + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">masters</strong></span></p></td> -<td><p>defines a named masters list for -inclusion in stub and slave zone masters clauses.</p></td> +<td> + <p><span><strong class="command">masters</strong></span></p> + </td> +<td> + <p> + defines a named masters list for + inclusion in stub and slave zone masters clauses. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">options</strong></span></p></td> -<td><p>controls global server configuration -options and sets defaults for other statements.</p></td> +<td> + <p><span><strong class="command">options</strong></span></p> + </td> +<td> + <p> + controls global server configuration + options and sets defaults for other statements. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">server</strong></span></p></td> -<td><p>sets certain configuration options on -a per-server basis.</p></td> +<td> + <p><span><strong class="command">server</strong></span></p> + </td> +<td> + <p> + sets certain configuration options on + a per-server basis. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">trusted-keys</strong></span></p></td> -<td><p>defines trusted DNSSEC keys.</p></td> +<td> + <p><span><strong class="command">trusted-keys</strong></span></p> + </td> +<td> + <p> + defines trusted DNSSEC keys. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">view</strong></span></p></td> -<td><p>defines a view.</p></td> +<td> + <p><span><strong class="command">view</strong></span></p> + </td> +<td> + <p> + defines a view. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">zone</strong></span></p></td> -<td><p>defines a zone.</p></td> +<td> + <p><span><strong class="command">zone</strong></span></p> + </td> +<td> + <p> + defines a zone. + </p> + </td> </tr> </tbody> </table></div> -<p>The <span><strong class="command">logging</strong></span> and - <span><strong class="command">options</strong></span> statements may only occur once per - configuration.</p> +<p> + The <span><strong class="command">logging</strong></span> and + <span><strong class="command">options</strong></span> statements may only occur once + per + configuration. + </p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2576157"></a><span><strong class="command">acl</strong></span> Statement Grammar</h3></div></div></div> -<pre class="programlisting"><span><strong class="command">acl</strong></span> acl-name { - address_match_list +<a name="id2574092"></a><span><strong class="command">acl</strong></span> Statement Grammar</h3></div></div></div> +<pre class="programlisting"><span><strong class="command">acl</strong></span> acl-name { + address_match_list }; </pre> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="acl"></a><span><strong class="command">acl</strong></span> Statement Definition and -Usage</h3></div></div></div> -<p>The <span><strong class="command">acl</strong></span> statement assigns a symbolic - name to an address match list. It gets its name from a primary - use of address match lists: Access Control Lists (ACLs).</p> -<p>Note that an address match list's name must be defined - with <span><strong class="command">acl</strong></span> before it can be used elsewhere; no - forward references are allowed.</p> -<p>The following ACLs are built-in:</p> + Usage</h3></div></div></div> +<p> + The <span><strong class="command">acl</strong></span> statement assigns a symbolic + name to an address match list. It gets its name from a primary + use of address match lists: Access Control Lists (ACLs). + </p> +<p> + Note that an address match list's name must be defined + with <span><strong class="command">acl</strong></span> before it can be used + elsewhere; no + forward references are allowed. + </p> +<p> + The following ACLs are built-in: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -468,155 +805,201 @@ Usage</h3></div></div></div> </colgroup> <tbody> <tr> -<td><p><span><strong class="command">any</strong></span></p></td> -<td><p>Matches all hosts.</p></td> +<td> + <p><span><strong class="command">any</strong></span></p> + </td> +<td> + <p> + Matches all hosts. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">none</strong></span></p></td> -<td><p>Matches no hosts.</p></td> +<td> + <p><span><strong class="command">none</strong></span></p> + </td> +<td> + <p> + Matches no hosts. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">localhost</strong></span></p></td> -<td><p>Matches the IPv4 and IPv6 addresses of all network -interfaces on the system.</p></td> +<td> + <p><span><strong class="command">localhost</strong></span></p> + </td> +<td> + <p> + Matches the IPv4 and IPv6 addresses of all network + interfaces on the system. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">localnets</strong></span></p></td> -<td><p>Matches any host on an IPv4 or IPv6 network -for which the system has an interface. -Some systems do not provide a way to determine the prefix lengths of -local IPv6 addresses. -In such a case, <span><strong class="command">localnets</strong></span> only matches the local -IPv6 addresses, just like <span><strong class="command">localhost</strong></span>. -</p></td> +<td> + <p><span><strong class="command">localnets</strong></span></p> + </td> +<td> + <p> + Matches any host on an IPv4 or IPv6 network + for which the system has an interface. + Some systems do not provide a way to determine the prefix + lengths of + local IPv6 addresses. + In such a case, <span><strong class="command">localnets</strong></span> + only matches the local + IPv6 addresses, just like <span><strong class="command">localhost</strong></span>. + </p> + </td> </tr> </tbody> </table></div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2576326"></a><span><strong class="command">controls</strong></span> Statement Grammar</h3></div></div></div> +<a name="id2574282"></a><span><strong class="command">controls</strong></span> Statement Grammar</h3></div></div></div> <pre class="programlisting"><span><strong class="command">controls</strong></span> { - inet ( ip_addr | * ) [<span class="optional"> port ip_port </span>] allow { <em class="replaceable"><code> address_match_list </code></em> } - keys { <em class="replaceable"><code> key_list </code></em> }; - [<span class="optional"> inet ...; </span>] + [ inet ( ip_addr | * ) [ port ip_port ] allow { <em class="replaceable"><code> address_match_list </code></em> } + keys { <em class="replaceable"><code>key_list</code></em> }; ] + [ inet ...; ] + [ unix <em class="replaceable"><code>path</code></em> perm <em class="replaceable"><code>number</code></em> owner <em class="replaceable"><code>number</code></em> group <em class="replaceable"><code>number</code></em> keys { <em class="replaceable"><code>key_list</code></em> }; ] + [ unix ...; ] }; </pre> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="controls_statement_definition_and_usage"></a><span><strong class="command">controls</strong></span> Statement Definition and Usage</h3></div></div></div> -<p>The <span><strong class="command">controls</strong></span> statement declares control - channels to be used by system administrators to control the - operation of the name server. These control channels are - used by the <span><strong class="command">rndc</strong></span> utility to send commands to - and retrieve non-DNS results from a name server.</p> -<p>An <span><strong class="command">inet</strong></span> control channel is a TCP - socket listening at the specified - <span><strong class="command">ip_port</strong></span> on the specified - <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6 - address. An <span><strong class="command">ip_addr</strong></span> - of <code class="literal">*</code> (asterisk) is interpreted as the IPv4 wildcard - address; connections will be accepted on any of the system's - IPv4 addresses. To listen on the IPv6 wildcard address, - use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>. - If you will only use <span><strong class="command">rndc</strong></span> on the local host, - using the loopback address (<code class="literal">127.0.0.1</code> - or <code class="literal">::1</code>) is recommended for maximum - security. - </p> +<a name="controls_statement_definition_and_usage"></a><span><strong class="command">controls</strong></span> Statement Definition and + Usage</h3></div></div></div> <p> - If no port is specified, port 953 - is used. The asterisk "<code class="literal">*</code>" cannot be used for - <span><strong class="command">ip_port</strong></span>.</p> -<p>The ability to issue commands over the control channel is - restricted by the <span><strong class="command">allow</strong></span> and - <span><strong class="command">keys</strong></span> clauses. Connections to the control - channel are permitted based on the - <span><strong class="command">address_match_list</strong></span>. This is for simple - IP address based filtering only; any <span><strong class="command">key_id</strong></span> - elements of the <span><strong class="command">address_match_list</strong></span> are - ignored. - </p> -<p>The primary authorization mechanism of the command - channel is the <span><strong class="command">key_list</strong></span>, which contains - a list of <span><strong class="command">key_id</strong></span>s. - Each <span><strong class="command">key_id</strong></span> in - the <span><strong class="command">key_list</strong></span> is authorized to execute - commands over the control channel. - See <a href="Bv9ARM.ch03.html#rndc">Remote Name Daemon Control application</a> in - <a href="Bv9ARM.ch03.html#admin_tools" title="Administrative Tools">the section called “Administrative Tools”</a>) for information about - configuring keys in <span><strong class="command">rndc</strong></span>.</p> -<p> -If no <span><strong class="command">controls</strong></span> statement is present, -<span><strong class="command">named</strong></span> will set up a default -control channel listening on the loopback address 127.0.0.1 -and its IPv6 counterpart ::1. -In this case, and also when the <span><strong class="command">controls</strong></span> statement -is present but does not have a <span><strong class="command">keys</strong></span> clause, -<span><strong class="command">named</strong></span> will attempt to load the command channel key -from the file <code class="filename">rndc.key</code> in -<code class="filename">/etc</code> (or whatever <code class="varname">sysconfdir</code> -was specified as when <acronym class="acronym">BIND</acronym> was built). -To create a <code class="filename">rndc.key</code> file, run -<strong class="userinput"><code>rndc-confgen -a</code></strong>. -</p> -<p>The <code class="filename">rndc.key</code> feature was created to - ease the transition of systems from <acronym class="acronym">BIND</acronym> 8, - which did not have digital signatures on its command channel messages - and thus did not have a <span><strong class="command">keys</strong></span> clause. + The <span><strong class="command">controls</strong></span> statement declares control + channels to be used by system administrators to control the + operation of the name server. These control channels are + used by the <span><strong class="command">rndc</strong></span> utility to send + commands to and retrieve non-DNS results from a name server. + </p> +<p> + An <span><strong class="command">inet</strong></span> control channel is a TCP socket + listening at the specified <span><strong class="command">ip_port</strong></span> on the + specified <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6 + address. An <span><strong class="command">ip_addr</strong></span> of <code class="literal">*</code> (asterisk) is + interpreted as the IPv4 wildcard address; connections will be + accepted on any of the system's IPv4 addresses. + To listen on the IPv6 wildcard address, + use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>. + If you will only use <span><strong class="command">rndc</strong></span> on the local host, + using the loopback address (<code class="literal">127.0.0.1</code> + or <code class="literal">::1</code>) is recommended for maximum security. + </p> +<p> + If no port is specified, port 953 is used. The asterisk + "<code class="literal">*</code>" cannot be used for <span><strong class="command">ip_port</strong></span>. + </p> +<p> + The ability to issue commands over the control channel is + restricted by the <span><strong class="command">allow</strong></span> and + <span><strong class="command">keys</strong></span> clauses. + Connections to the control channel are permitted based on the + <span><strong class="command">address_match_list</strong></span>. This is for simple + IP address based filtering only; any <span><strong class="command">key_id</strong></span> + elements of the <span><strong class="command">address_match_list</strong></span> + are ignored. + </p> +<p> + A <span><strong class="command">unix</strong></span> control channel is a UNIX domain + socket listening at the specified path in the file system. + Access to the socket is specified by the <span><strong class="command">perm</strong></span>, + <span><strong class="command">owner</strong></span> and <span><strong class="command">group</strong></span> clauses. + Note on some platforms (SunOS and Solaris) the permissions + (<span><strong class="command">perm</strong></span>) are applied to the parent directory + as the permissions on the socket itself are ignored. + </p> +<p> + The primary authorization mechanism of the command + channel is the <span><strong class="command">key_list</strong></span>, which + contains a list of <span><strong class="command">key_id</strong></span>s. + Each <span><strong class="command">key_id</strong></span> in the <span><strong class="command">key_list</strong></span> + is authorized to execute commands over the control channel. + See <a href="Bv9ARM.ch03.html#rndc">Remote Name Daemon Control application</a> in <a href="Bv9ARM.ch03.html#admin_tools" title="Administrative Tools">the section called “Administrative Tools”</a>) + for information about configuring keys in <span><strong class="command">rndc</strong></span>. + </p> +<p> + If no <span><strong class="command">controls</strong></span> statement is present, + <span><strong class="command">named</strong></span> will set up a default + control channel listening on the loopback address 127.0.0.1 + and its IPv6 counterpart ::1. + In this case, and also when the <span><strong class="command">controls</strong></span> statement + is present but does not have a <span><strong class="command">keys</strong></span> clause, + <span><strong class="command">named</strong></span> will attempt to load the command channel key + from the file <code class="filename">rndc.key</code> in + <code class="filename">/etc</code> (or whatever <code class="varname">sysconfdir</code> + was specified as when <acronym class="acronym">BIND</acronym> was built). + To create a <code class="filename">rndc.key</code> file, run + <strong class="userinput"><code>rndc-confgen -a</code></strong>. + </p> +<p> + The <code class="filename">rndc.key</code> feature was created to + ease the transition of systems from <acronym class="acronym">BIND</acronym> 8, + which did not have digital signatures on its command channel + messages and thus did not have a <span><strong class="command">keys</strong></span> clause. -It makes it possible to use an existing <acronym class="acronym">BIND</acronym> 8 -configuration file in <acronym class="acronym">BIND</acronym> 9 unchanged, -and still have <span><strong class="command">rndc</strong></span> work the same way -<span><strong class="command">ndc</strong></span> worked in BIND 8, simply by executing the -command <strong class="userinput"><code>rndc-confgen -a</code></strong> after BIND 9 is -installed. -</p> + It makes it possible to use an existing <acronym class="acronym">BIND</acronym> 8 + configuration file in <acronym class="acronym">BIND</acronym> 9 unchanged, + and still have <span><strong class="command">rndc</strong></span> work the same way + <span><strong class="command">ndc</strong></span> worked in BIND 8, simply by executing the + command <strong class="userinput"><code>rndc-confgen -a</code></strong> after BIND 9 is + installed. + </p> <p> - Since the <code class="filename">rndc.key</code> feature - is only intended to allow the backward-compatible usage of - <acronym class="acronym">BIND</acronym> 8 configuration files, this feature does not - have a high degree of configurability. You cannot easily change - the key name or the size of the secret, so you should make a - <code class="filename">rndc.conf</code> with your own key if you wish to change - those things. The <code class="filename">rndc.key</code> file also has its - permissions set such that only the owner of the file (the user that - <span><strong class="command">named</strong></span> is running as) can access it. If you - desire greater flexibility in allowing other users to access - <span><strong class="command">rndc</strong></span> commands, then you need to create a - <code class="filename">rndc.conf</code> file and make it group readable by a group - that contains the users who should have access.</p> -<p>The UNIX control channel type of <acronym class="acronym">BIND</acronym> 8 is not supported - in <acronym class="acronym">BIND</acronym> 9.0, <acronym class="acronym">BIND</acronym> 9.1, - <acronym class="acronym">BIND</acronym> 9.2 and <acronym class="acronym">BIND</acronym> 9.3. - If it is present in the controls statement from a - <acronym class="acronym">BIND</acronym> 8 configuration file, it is ignored - and a warning is logged.</p> -<p> -To disable the command channel, use an empty <span><strong class="command">controls</strong></span> -statement: <span><strong class="command">controls { };</strong></span>. -</p> + Since the <code class="filename">rndc.key</code> feature + is only intended to allow the backward-compatible usage of + <acronym class="acronym">BIND</acronym> 8 configuration files, this + feature does not + have a high degree of configurability. You cannot easily change + the key name or the size of the secret, so you should make a + <code class="filename">rndc.conf</code> with your own key if you + wish to change + those things. The <code class="filename">rndc.key</code> file + also has its + permissions set such that only the owner of the file (the user that + <span><strong class="command">named</strong></span> is running as) can access it. + If you + desire greater flexibility in allowing other users to access + <span><strong class="command">rndc</strong></span> commands, then you need to create + a + <code class="filename">rndc.conf</code> file and make it group + readable by a group + that contains the users who should have access. + </p> +<p> + To disable the command channel, use an empty + <span><strong class="command">controls</strong></span> statement: + <span><strong class="command">controls { };</strong></span>. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2576672"></a><span><strong class="command">include</strong></span> Statement Grammar</h3></div></div></div> +<a name="id2574711"></a><span><strong class="command">include</strong></span> Statement Grammar</h3></div></div></div> <pre class="programlisting">include <em class="replaceable"><code>filename</code></em>;</pre> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2576686"></a><span><strong class="command">include</strong></span> Statement Definition and Usage</h3></div></div></div> -<p>The <span><strong class="command">include</strong></span> statement inserts the - specified file at the point where the <span><strong class="command">include</strong></span> - statement is encountered. The <span><strong class="command">include</strong></span> - statement facilitates the administration of configuration files - by permitting the reading or writing of some things but not - others. For example, the statement could include private keys - that are readable only by the name server.</p> +<a name="id2574726"></a><span><strong class="command">include</strong></span> Statement Definition and + Usage</h3></div></div></div> +<p> + The <span><strong class="command">include</strong></span> statement inserts the + specified file at the point where the <span><strong class="command">include</strong></span> + statement is encountered. The <span><strong class="command">include</strong></span> + statement facilitates the administration of configuration + files + by permitting the reading or writing of some things but not + others. For example, the statement could include private keys + that are readable only by the name server. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2576709"></a><span><strong class="command">key</strong></span> Statement Grammar</h3></div></div></div> +<a name="id2574749"></a><span><strong class="command">key</strong></span> Statement Grammar</h3></div></div></div> <pre class="programlisting">key <em class="replaceable"><code>key_id</code></em> { algorithm <em class="replaceable"><code>string</code></em>; secret <em class="replaceable"><code>string</code></em>; @@ -625,43 +1008,58 @@ statement: <span><strong class="command">controls { };</strong></span>. </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2576730"></a><span><strong class="command">key</strong></span> Statement Definition and Usage</h3></div></div></div> -<p>The <span><strong class="command">key</strong></span> statement defines a shared -secret key for use with TSIG (see <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>) -or the command channel -(see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and Usage”</a>). -</p> +<a name="id2574771"></a><span><strong class="command">key</strong></span> Statement Definition and Usage</h3></div></div></div> <p> -The <span><strong class="command">key</strong></span> statement can occur at the top level -of the configuration file or inside a <span><strong class="command">view</strong></span> -statement. Keys defined in top-level <span><strong class="command">key</strong></span> -statements can be used in all views. Keys intended for use in -a <span><strong class="command">controls</strong></span> statement -(see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and Usage”</a>) -must be defined at the top level. -</p> -<p>The <em class="replaceable"><code>key_id</code></em>, also known as the -key name, is a domain name uniquely identifying the key. It can -be used in a <span><strong class="command">server</strong></span> -statement to cause requests sent to that -server to be signed with this key, or in address match lists to -verify that incoming requests have been signed with a key -matching this name, algorithm, and secret.</p> -<p>The <em class="replaceable"><code>algorithm_id</code></em> is a string -that specifies a security/authentication algorithm. The only -algorithm currently supported with TSIG authentication is -<code class="literal">hmac-md5</code>. The -<em class="replaceable"><code>secret_string</code></em> is the secret to be -used by the algorithm, and is treated as a base-64 encoded -string.</p> + The <span><strong class="command">key</strong></span> statement defines a shared + secret key for use with TSIG (see <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>) + or the command channel + (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and + Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and + Usage”</a>). + </p> +<p> + The <span><strong class="command">key</strong></span> statement can occur at the + top level + of the configuration file or inside a <span><strong class="command">view</strong></span> + statement. Keys defined in top-level <span><strong class="command">key</strong></span> + statements can be used in all views. Keys intended for use in + a <span><strong class="command">controls</strong></span> statement + (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and + Usage">the section called “<span><strong class="command">controls</strong></span> Statement Definition and + Usage”</a>) + must be defined at the top level. + </p> +<p> + The <em class="replaceable"><code>key_id</code></em>, also known as the + key name, is a domain name uniquely identifying the key. It can + be used in a <span><strong class="command">server</strong></span> + statement to cause requests sent to that + server to be signed with this key, or in address match lists to + verify that incoming requests have been signed with a key + matching this name, algorithm, and secret. + </p> +<p> + The <em class="replaceable"><code>algorithm_id</code></em> is a string + that specifies a security/authentication algorithm. Named + supports <code class="literal">hmac-md5</code>, + <code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>, + <code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code> + and <code class="literal">hmac-sha512</code> TSIG authentication. + Truncated hashes are supported by appending the minimum + number of required bits preceded by a dash, e.g. + <code class="literal">hmac-sha1-80</code>. The + <em class="replaceable"><code>secret_string</code></em> is the secret + to be used by the algorithm, and is treated as a base-64 + encoded string. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2576870"></a><span><strong class="command">logging</strong></span> Statement Grammar</h3></div></div></div> +<a name="id2574930"></a><span><strong class="command">logging</strong></span> Statement Grammar</h3></div></div></div> <pre class="programlisting"><span><strong class="command">logging</strong></span> { [ <span><strong class="command">channel</strong></span> <em class="replaceable"><code>channel_name</code></em> { ( <span><strong class="command">file</strong></span> <em class="replaceable"><code>path name</code></em> - [ <span><strong class="command">versions</strong></span> ( <em class="replaceable"><code>number</code></em> | <code class="literal">unlimited</code> ) ] + [ <span><strong class="command">versions</strong></span> ( <em class="replaceable"><code>number</code></em> | <span><strong class="command">unlimited</strong></span> ) ] [ <span><strong class="command">size</strong></span> <em class="replaceable"><code>size spec</code></em> ] | <span><strong class="command">syslog</strong></span> <em class="replaceable"><code>syslog_facility</code></em> | <span><strong class="command">stderr</strong></span> @@ -673,7 +1071,7 @@ string.</p> [ <span><strong class="command">print-time</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ] }; ] [ <span><strong class="command">category</strong></span> <em class="replaceable"><code>category_name</code></em> { - <em class="replaceable"><code>channel_name</code></em> ; [ <em class="replaceable"><code>channel_nam</code></em>e ; ... ] + <em class="replaceable"><code>channel_name</code></em> ; [ <em class="replaceable"><code>channel_name</code></em> ; ... ] }; ] ... }; @@ -681,148 +1079,223 @@ string.</p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2577064"></a><span><strong class="command">logging</strong></span> Statement Definition and Usage</h3></div></div></div> -<p>The <span><strong class="command">logging</strong></span> statement configures a wide -variety of logging options for the name server. Its <span><strong class="command">channel</strong></span> phrase -associates output methods, format options and severity levels with -a name that can then be used with the <span><strong class="command">category</strong></span> phrase -to select how various classes of messages are logged.</p> -<p>Only one <span><strong class="command">logging</strong></span> statement is used to define -as many channels and categories as are wanted. If there is no <span><strong class="command">logging</strong></span> statement, -the logging configuration will be:</p> +<a name="id2575056"></a><span><strong class="command">logging</strong></span> Statement Definition and + Usage</h3></div></div></div> +<p> + The <span><strong class="command">logging</strong></span> statement configures a + wide + variety of logging options for the name server. Its <span><strong class="command">channel</strong></span> phrase + associates output methods, format options and severity levels with + a name that can then be used with the <span><strong class="command">category</strong></span> phrase + to select how various classes of messages are logged. + </p> +<p> + Only one <span><strong class="command">logging</strong></span> statement is used to + define + as many channels and categories as are wanted. If there is no <span><strong class="command">logging</strong></span> statement, + the logging configuration will be: + </p> <pre class="programlisting">logging { category default { default_syslog; default_debug; }; category unmatched { null; }; }; </pre> -<p>In <acronym class="acronym">BIND</acronym> 9, the logging configuration is only established when -the entire configuration file has been parsed. In <acronym class="acronym">BIND</acronym> 8, it was -established as soon as the <span><strong class="command">logging</strong></span> statement -was parsed. When the server is starting up, all logging messages -regarding syntax errors in the configuration file go to the default -channels, or to standard error if the "<code class="option">-g</code>" option -was specified.</p> +<p> + In <acronym class="acronym">BIND</acronym> 9, the logging configuration + is only established when + the entire configuration file has been parsed. In <acronym class="acronym">BIND</acronym> 8, it was + established as soon as the <span><strong class="command">logging</strong></span> + statement + was parsed. When the server is starting up, all logging messages + regarding syntax errors in the configuration file go to the default + channels, or to standard error if the "<code class="option">-g</code>" option + was specified. + </p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2577116"></a>The <span><strong class="command">channel</strong></span> Phrase</h4></div></div></div> -<p>All log output goes to one or more <span class="emphasis"><em>channels</em></span>; -you can make as many of them as you want.</p> -<p>Every channel definition must include a destination clause that -says whether messages selected for the channel go to a file, to a -particular syslog facility, to the standard error stream, or are -discarded. It can optionally also limit the message severity level -that will be accepted by the channel (the default is -<span><strong class="command">info</strong></span>), and whether to include a -<span><strong class="command">named</strong></span>-generated time stamp, the category name -and/or severity level (the default is not to include any).</p> -<p>The <span><strong class="command">null</strong></span> destination clause -causes all messages sent to the channel to be discarded; -in that case, other options for the channel are meaningless.</p> -<p>The <span><strong class="command">file</strong></span> destination clause directs the channel -to a disk file. It can include limitations -both on how large the file is allowed to become, and how many versions -of the file will be saved each time the file is opened.</p> -<p>If you use the <span><strong class="command">versions</strong></span> log file option, then -<span><strong class="command">named</strong></span> will retain that many backup versions of the file by -renaming them when opening. For example, if you choose to keep three old versions -of the file <code class="filename">lamers.log</code>, then just before it is opened -<code class="filename">lamers.log.1</code> is renamed to -<code class="filename">lamers.log.2</code>, <code class="filename">lamers.log.0</code> is renamed -to <code class="filename">lamers.log.1</code>, and <code class="filename">lamers.log</code> is -renamed to <code class="filename">lamers.log.0</code>. -You can say <span><strong class="command">versions unlimited</strong></span> to not limit -the number of versions. -If a <span><strong class="command">size</strong></span> option is associated with the log file, -then renaming is only done when the file being opened exceeds the -indicated size. No backup versions are kept by default; any existing -log file is simply appended.</p> -<p>The <span><strong class="command">size</strong></span> option for files is used to limit log -growth. If the file ever exceeds the size, then <span><strong class="command">named</strong></span> will -stop writing to the file unless it has a <span><strong class="command">versions</strong></span> option -associated with it. If backup versions are kept, the files are rolled as -described above and a new one begun. If there is no -<span><strong class="command">versions</strong></span> option, no more data will be written to the log -until some out-of-band mechanism removes or truncates the log to less than the -maximum size. The default behavior is not to limit the size of the -file.</p> -<p>Example usage of the <span><strong class="command">size</strong></span> and -<span><strong class="command">versions</strong></span> options:</p> +<a name="id2575108"></a>The <span><strong class="command">channel</strong></span> Phrase</h4></div></div></div> +<p> + All log output goes to one or more <span class="emphasis"><em>channels</em></span>; + you can make as many of them as you want. + </p> +<p> + Every channel definition must include a destination clause that + says whether messages selected for the channel go to a file, to a + particular syslog facility, to the standard error stream, or are + discarded. It can optionally also limit the message severity level + that will be accepted by the channel (the default is + <span><strong class="command">info</strong></span>), and whether to include a + <span><strong class="command">named</strong></span>-generated time stamp, the + category name + and/or severity level (the default is not to include any). + </p> +<p> + The <span><strong class="command">null</strong></span> destination clause + causes all messages sent to the channel to be discarded; + in that case, other options for the channel are meaningless. + </p> +<p> + The <span><strong class="command">file</strong></span> destination clause directs + the channel + to a disk file. It can include limitations + both on how large the file is allowed to become, and how many + versions + of the file will be saved each time the file is opened. + </p> +<p> + If you use the <span><strong class="command">versions</strong></span> log file + option, then + <span><strong class="command">named</strong></span> will retain that many backup + versions of the file by + renaming them when opening. For example, if you choose to keep + three old versions + of the file <code class="filename">lamers.log</code>, then just + before it is opened + <code class="filename">lamers.log.1</code> is renamed to + <code class="filename">lamers.log.2</code>, <code class="filename">lamers.log.0</code> is renamed + to <code class="filename">lamers.log.1</code>, and <code class="filename">lamers.log</code> is + renamed to <code class="filename">lamers.log.0</code>. + You can say <span><strong class="command">versions unlimited</strong></span> to + not limit + the number of versions. + If a <span><strong class="command">size</strong></span> option is associated with + the log file, + then renaming is only done when the file being opened exceeds the + indicated size. No backup versions are kept by default; any + existing + log file is simply appended. + </p> +<p> + The <span><strong class="command">size</strong></span> option for files is used + to limit log + growth. If the file ever exceeds the size, then <span><strong class="command">named</strong></span> will + stop writing to the file unless it has a <span><strong class="command">versions</strong></span> option + associated with it. If backup versions are kept, the files are + rolled as + described above and a new one begun. If there is no + <span><strong class="command">versions</strong></span> option, no more data will + be written to the log + until some out-of-band mechanism removes or truncates the log to + less than the + maximum size. The default behavior is not to limit the size of + the + file. + </p> +<p> + Example usage of the <span><strong class="command">size</strong></span> and + <span><strong class="command">versions</strong></span> options: + </p> <pre class="programlisting">channel an_example_channel { file "example.log" versions 3 size 20m; print-time yes; print-category yes; }; </pre> -<p>The <span><strong class="command">syslog</strong></span> destination clause directs the -channel to the system log. Its argument is a -syslog facility as described in the <span><strong class="command">syslog</strong></span> man -page. Known facilities are <span><strong class="command">kern</strong></span>, <span><strong class="command">user</strong></span>, -<span><strong class="command">mail</strong></span>, <span><strong class="command">daemon</strong></span>, <span><strong class="command">auth</strong></span>, -<span><strong class="command">syslog</strong></span>, <span><strong class="command">lpr</strong></span>, <span><strong class="command">news</strong></span>, -<span><strong class="command">uucp</strong></span>, <span><strong class="command">cron</strong></span>, <span><strong class="command">authpriv</strong></span>, -<span><strong class="command">ftp</strong></span>, <span><strong class="command">local0</strong></span>, <span><strong class="command">local1</strong></span>, -<span><strong class="command">local2</strong></span>, <span><strong class="command">local3</strong></span>, <span><strong class="command">local4</strong></span>, -<span><strong class="command">local5</strong></span>, <span><strong class="command">local6</strong></span> and -<span><strong class="command">local7</strong></span>, however not all facilities are supported on -all operating systems. -How <span><strong class="command">syslog</strong></span> will handle messages sent to -this facility is described in the <span><strong class="command">syslog.conf</strong></span> man -page. If you have a system which uses a very old version of <span><strong class="command">syslog</strong></span> that -only uses two arguments to the <span><strong class="command">openlog()</strong></span> function, -then this clause is silently ignored.</p> -<p>The <span><strong class="command">severity</strong></span> clause works like <span><strong class="command">syslog</strong></span>'s -"priorities", except that they can also be used if you are writing -straight to a file rather than using <span><strong class="command">syslog</strong></span>. -Messages which are not at least of the severity level given will -not be selected for the channel; messages of higher severity levels -will be accepted.</p> -<p>If you are using <span><strong class="command">syslog</strong></span>, then the <span><strong class="command">syslog.conf</strong></span> priorities -will also determine what eventually passes through. For example, -defining a channel facility and severity as <span><strong class="command">daemon</strong></span> and <span><strong class="command">debug</strong></span> but -only logging <span><strong class="command">daemon.warning</strong></span> via <span><strong class="command">syslog.conf</strong></span> will -cause messages of severity <span><strong class="command">info</strong></span> and <span><strong class="command">notice</strong></span> to -be dropped. If the situation were reversed, with <span><strong class="command">named</strong></span> writing -messages of only <span><strong class="command">warning</strong></span> or higher, then <span><strong class="command">syslogd</strong></span> would -print all messages it received from the channel.</p> -<p>The <span><strong class="command">stderr</strong></span> destination clause directs the -channel to the server's standard error stream. This is intended for -use when the server is running as a foreground process, for example -when debugging a configuration.</p> -<p>The server can supply extensive debugging information when -it is in debugging mode. If the server's global debug level is greater -than zero, then debugging mode will be active. The global debug -level is set either by starting the <span><strong class="command">named</strong></span> server -with the <code class="option">-d</code> flag followed by a positive integer, -or by running <span><strong class="command">rndc trace</strong></span>. -The global debug level -can be set to zero, and debugging mode turned off, by running <span><strong class="command">rndc +<p> + The <span><strong class="command">syslog</strong></span> destination clause + directs the + channel to the system log. Its argument is a + syslog facility as described in the <span><strong class="command">syslog</strong></span> man + page. Known facilities are <span><strong class="command">kern</strong></span>, <span><strong class="command">user</strong></span>, + <span><strong class="command">mail</strong></span>, <span><strong class="command">daemon</strong></span>, <span><strong class="command">auth</strong></span>, + <span><strong class="command">syslog</strong></span>, <span><strong class="command">lpr</strong></span>, <span><strong class="command">news</strong></span>, + <span><strong class="command">uucp</strong></span>, <span><strong class="command">cron</strong></span>, <span><strong class="command">authpriv</strong></span>, + <span><strong class="command">ftp</strong></span>, <span><strong class="command">local0</strong></span>, <span><strong class="command">local1</strong></span>, + <span><strong class="command">local2</strong></span>, <span><strong class="command">local3</strong></span>, <span><strong class="command">local4</strong></span>, + <span><strong class="command">local5</strong></span>, <span><strong class="command">local6</strong></span> and + <span><strong class="command">local7</strong></span>, however not all facilities + are supported on + all operating systems. + How <span><strong class="command">syslog</strong></span> will handle messages + sent to + this facility is described in the <span><strong class="command">syslog.conf</strong></span> man + page. If you have a system which uses a very old version of <span><strong class="command">syslog</strong></span> that + only uses two arguments to the <span><strong class="command">openlog()</strong></span> function, + then this clause is silently ignored. + </p> +<p> + The <span><strong class="command">severity</strong></span> clause works like <span><strong class="command">syslog</strong></span>'s + "priorities", except that they can also be used if you are writing + straight to a file rather than using <span><strong class="command">syslog</strong></span>. + Messages which are not at least of the severity level given will + not be selected for the channel; messages of higher severity + levels + will be accepted. + </p> +<p> + If you are using <span><strong class="command">syslog</strong></span>, then the <span><strong class="command">syslog.conf</strong></span> priorities + will also determine what eventually passes through. For example, + defining a channel facility and severity as <span><strong class="command">daemon</strong></span> and <span><strong class="command">debug</strong></span> but + only logging <span><strong class="command">daemon.warning</strong></span> via <span><strong class="command">syslog.conf</strong></span> will + cause messages of severity <span><strong class="command">info</strong></span> and + <span><strong class="command">notice</strong></span> to + be dropped. If the situation were reversed, with <span><strong class="command">named</strong></span> writing + messages of only <span><strong class="command">warning</strong></span> or higher, + then <span><strong class="command">syslogd</strong></span> would + print all messages it received from the channel. + </p> +<p> + The <span><strong class="command">stderr</strong></span> destination clause + directs the + channel to the server's standard error stream. This is intended + for + use when the server is running as a foreground process, for + example + when debugging a configuration. + </p> +<p> + The server can supply extensive debugging information when + it is in debugging mode. If the server's global debug level is + greater + than zero, then debugging mode will be active. The global debug + level is set either by starting the <span><strong class="command">named</strong></span> server + with the <code class="option">-d</code> flag followed by a positive integer, + or by running <span><strong class="command">rndc trace</strong></span>. + The global debug level + can be set to zero, and debugging mode turned off, by running <span><strong class="command">rndc notrace</strong></span>. All debugging messages in the server have a debug -level, and higher debug levels give more detailed output. Channels -that specify a specific debug severity, for example:</p> + level, and higher debug levels give more detailed output. Channels + that specify a specific debug severity, for example: + </p> <pre class="programlisting">channel specific_debug_level { file "foo"; severity debug 3; }; </pre> -<p>will get debugging output of level 3 or less any time the -server is in debugging mode, regardless of the global debugging -level. Channels with <span><strong class="command">dynamic</strong></span> severity use the -server's global debug level to determine what messages to print.</p> -<p>If <span><strong class="command">print-time</strong></span> has been turned on, then -the date and time will be logged. <span><strong class="command">print-time</strong></span> may -be specified for a <span><strong class="command">syslog</strong></span> channel, but is usually -pointless since <span><strong class="command">syslog</strong></span> also prints the date and -time. If <span><strong class="command">print-category</strong></span> is requested, then the -category of the message will be logged as well. Finally, if <span><strong class="command">print-severity</strong></span> is -on, then the severity level of the message will be logged. The <span><strong class="command">print-</strong></span> options may -be used in any combination, and will always be printed in the following -order: time, category, severity. Here is an example where all three <span><strong class="command">print-</strong></span> options -are on:</p> -<p><code class="computeroutput">28-Feb-2000 15:05:32.863 general: notice: running</code></p> -<p>There are four predefined channels that are used for -<span><strong class="command">named</strong></span>'s default logging as follows. How they are -used is described in <a href="Bv9ARM.ch06.html#the_category_phrase" title="The category Phrase">the section called “The <span><strong class="command">category</strong></span> Phrase”</a>. -</p> +<p> + will get debugging output of level 3 or less any time the + server is in debugging mode, regardless of the global debugging + level. Channels with <span><strong class="command">dynamic</strong></span> + severity use the + server's global debug level to determine what messages to print. + </p> +<p> + If <span><strong class="command">print-time</strong></span> has been turned on, + then + the date and time will be logged. <span><strong class="command">print-time</strong></span> may + be specified for a <span><strong class="command">syslog</strong></span> channel, + but is usually + pointless since <span><strong class="command">syslog</strong></span> also prints + the date and + time. If <span><strong class="command">print-category</strong></span> is + requested, then the + category of the message will be logged as well. Finally, if <span><strong class="command">print-severity</strong></span> is + on, then the severity level of the message will be logged. The <span><strong class="command">print-</strong></span> options may + be used in any combination, and will always be printed in the + following + order: time, category, severity. Here is an example where all + three <span><strong class="command">print-</strong></span> options + are on: + </p> +<p> + <code class="computeroutput">28-Feb-2000 15:05:32.863 general: notice: running</code> + </p> +<p> + There are four predefined channels that are used for + <span><strong class="command">named</strong></span>'s default logging as follows. + How they are + used is described in <a href="Bv9ARM.ch06.html#the_category_phrase" title="The category Phrase">the section called “The <span><strong class="command">category</strong></span> Phrase”</a>. + </p> <pre class="programlisting">channel default_syslog { syslog daemon; // send to syslog's daemon // facility @@ -852,35 +1325,50 @@ channel null { // this channel }; </pre> -<p>The <span><strong class="command">default_debug</strong></span> channel has the special -property that it only produces output when the server's debug level is -nonzero. It normally writes to a file called <code class="filename">named.run</code> -in the server's working directory.</p> -<p>For security reasons, when the "<code class="option">-u</code>" -command line option is used, the <code class="filename">named.run</code> file -is created only after <span><strong class="command">named</strong></span> has changed to the -new UID, and any debug output generated while <span><strong class="command">named</strong></span> is -starting up and still running as root is discarded. If you need -to capture this output, you must run the server with the "<code class="option">-g</code>" -option and redirect standard error to a file.</p> -<p>Once a channel is defined, it cannot be redefined. Thus you -cannot alter the built-in channels directly, but you can modify -the default logging by pointing categories at channels you have defined.</p> +<p> + The <span><strong class="command">default_debug</strong></span> channel has the + special + property that it only produces output when the server's debug + level is + nonzero. It normally writes to a file called <code class="filename">named.run</code> + in the server's working directory. + </p> +<p> + For security reasons, when the "<code class="option">-u</code>" + command line option is used, the <code class="filename">named.run</code> file + is created only after <span><strong class="command">named</strong></span> has + changed to the + new UID, and any debug output generated while <span><strong class="command">named</strong></span> is + starting up and still running as root is discarded. If you need + to capture this output, you must run the server with the "<code class="option">-g</code>" + option and redirect standard error to a file. + </p> +<p> + Once a channel is defined, it cannot be redefined. Thus you + cannot alter the built-in channels directly, but you can modify + the default logging by pointing categories at channels you have + defined. + </p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="the_category_phrase"></a>The <span><strong class="command">category</strong></span> Phrase</h4></div></div></div> -<p>There are many categories, so you can send the logs you want -to see wherever you want, without seeing logs you don't want. If -you don't specify a list of channels for a category, then log messages -in that category will be sent to the <span><strong class="command">default</strong></span> category -instead. If you don't specify a default category, the following -"default default" is used:</p> +<p> + There are many categories, so you can send the logs you want + to see wherever you want, without seeing logs you don't want. If + you don't specify a list of channels for a category, then log + messages + in that category will be sent to the <span><strong class="command">default</strong></span> category + instead. If you don't specify a default category, the following + "default default" is used: + </p> <pre class="programlisting">category default { default_syslog; default_debug; }; </pre> -<p>As an example, let's say you want to log security events to -a file, but you also want keep the default logging behavior. You'd -specify the following:</p> +<p> + As an example, let's say you want to log security events to + a file, but you also want keep the default logging behavior. You'd + specify the following: + </p> <pre class="programlisting">channel my_security_channel { file "my_security_file"; severity info; @@ -890,13 +1378,17 @@ category security { default_syslog; default_debug; };</pre> -<p>To discard all messages in a category, specify the <span><strong class="command">null</strong></span> channel:</p> +<p> + To discard all messages in a category, specify the <span><strong class="command">null</strong></span> channel: + </p> <pre class="programlisting">category xfer-out { null; }; category notify { null; }; </pre> -<p>Following are the available categories and brief descriptions -of the types of log information they contain. More -categories may be added in future <acronym class="acronym">BIND</acronym> releases.</p> +<p> + Following are the available categories and brief descriptions + of the types of log information they contain. More + categories may be added in future <acronym class="acronym">BIND</acronym> releases. + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -904,114 +1396,235 @@ categories may be added in future <acronym class="acronym">BIND</acronym> releas </colgroup> <tbody> <tr> -<td><p><span><strong class="command">default</strong></span></p></td> -<td><p>The default category defines the logging -options for those categories where no specific configuration has been -defined.</p></td> +<td> + <p><span><strong class="command">default</strong></span></p> + </td> +<td> + <p> + The default category defines the logging + options for those categories where no specific + configuration has been + defined. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">general</strong></span></p></td> -<td><p>The catch-all. Many things still aren't -classified into categories, and they all end up here.</p></td> +<td> + <p><span><strong class="command">general</strong></span></p> + </td> +<td> + <p> + The catch-all. Many things still aren't + classified into categories, and they all end up here. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">database</strong></span></p></td> -<td><p>Messages relating to the databases used -internally by the name server to store zone and cache data.</p></td> +<td> + <p><span><strong class="command">database</strong></span></p> + </td> +<td> + <p> + Messages relating to the databases used + internally by the name server to store zone and cache + data. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">security</strong></span></p></td> -<td><p>Approval and denial of requests.</p></td> +<td> + <p><span><strong class="command">security</strong></span></p> + </td> +<td> + <p> + Approval and denial of requests. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">config</strong></span></p></td> -<td><p>Configuration file parsing and processing.</p></td> +<td> + <p><span><strong class="command">config</strong></span></p> + </td> +<td> + <p> + Configuration file parsing and processing. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">resolver</strong></span></p></td> -<td><p>DNS resolution, such as the recursive -lookups performed on behalf of clients by a caching name server.</p></td> +<td> + <p><span><strong class="command">resolver</strong></span></p> + </td> +<td> + <p> + DNS resolution, such as the recursive + lookups performed on behalf of clients by a caching name + server. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">xfer-in</strong></span></p></td> -<td><p>Zone transfers the server is receiving.</p></td> +<td> + <p><span><strong class="command">xfer-in</strong></span></p> + </td> +<td> + <p> + Zone transfers the server is receiving. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">xfer-out</strong></span></p></td> -<td><p>Zone transfers the server is sending.</p></td> +<td> + <p><span><strong class="command">xfer-out</strong></span></p> + </td> +<td> + <p> + Zone transfers the server is sending. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">notify</strong></span></p></td> -<td><p>The NOTIFY protocol.</p></td> +<td> + <p><span><strong class="command">notify</strong></span></p> + </td> +<td> + <p> + The NOTIFY protocol. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">client</strong></span></p></td> -<td><p>Processing of client requests.</p></td> +<td> + <p><span><strong class="command">client</strong></span></p> + </td> +<td> + <p> + Processing of client requests. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">unmatched</strong></span></p></td> -<td><p>Messages that named was unable to determine the -class of or for which there was no matching <span><strong class="command">view</strong></span>. -A one line summary is also logged to the <span><strong class="command">client</strong></span> category. -This category is best sent to a file or stderr, by default it is sent to -the <span><strong class="command">null</strong></span> channel.</p></td> +<td> + <p><span><strong class="command">unmatched</strong></span></p> + </td> +<td> + <p> + Messages that named was unable to determine the + class of or for which there was no matching <span><strong class="command">view</strong></span>. + A one line summary is also logged to the <span><strong class="command">client</strong></span> category. + This category is best sent to a file or stderr, by + default it is sent to + the <span><strong class="command">null</strong></span> channel. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">network</strong></span></p></td> -<td><p>Network operations.</p></td> +<td> + <p><span><strong class="command">network</strong></span></p> + </td> +<td> + <p> + Network operations. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">update</strong></span></p></td> -<td><p>Dynamic updates.</p></td> +<td> + <p><span><strong class="command">update</strong></span></p> + </td> +<td> + <p> + Dynamic updates. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">update-security</strong></span></p></td> -<td><p>Approval and denial of update requests.</p></td> +<td> + <p><span><strong class="command">update-security</strong></span></p> + </td> +<td> + <p> + Approval and denial of update requests. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">queries</strong></span></p></td> <td> -<p>Specify where queries should be logged to.</p> -<p> -At startup, specifying the category <span><strong class="command">queries</strong></span> will also -enable query logging unless <span><strong class="command">querylog</strong></span> option has been -specified. -</p> -<p> -The query log entry reports the client's IP address and port number, and the -query name, class and type. It also reports whether the Recursion Desired -flag was set (+ if set, - if not set), EDNS was in use (E) or if the -query was signed (S).</p> -<p><code class="computeroutput">client 127.0.0.1#62536: query: www.example.com IN AAAA +SE</code> -</p> -<p><code class="computeroutput">client ::1#62537: query: www.example.net IN AAAA -SE</code> -</p> -</td> + <p><span><strong class="command">queries</strong></span></p> + </td> +<td> + <p> + Specify where queries should be logged to. + </p> + <p> + At startup, specifying the category <span><strong class="command">queries</strong></span> will also + enable query logging unless <span><strong class="command">querylog</strong></span> option has been + specified. + </p> + <p> + The query log entry reports the client's IP address and + port number, and the + query name, class and type. It also reports whether the + Recursion Desired + flag was set (+ if set, - if not set), EDNS was in use + (E) or if the + query was signed (S). + </p> + <p> + <code class="computeroutput">client 127.0.0.1#62536: query: www.example.com IN AAAA +SE</code> + </p> + <p> + <code class="computeroutput">client ::1#62537: query: www.example.net IN AAAA -SE</code> + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">dispatch</strong></span></p></td> -<td><p>Dispatching of incoming packets to the -server modules where they are to be processed. -</p></td> +<td> + <p><span><strong class="command">dispatch</strong></span></p> + </td> +<td> + <p> + Dispatching of incoming packets to the + server modules where they are to be processed. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">dnssec</strong></span></p></td> -<td><p>DNSSEC and TSIG protocol processing. -</p></td> +<td> + <p><span><strong class="command">dnssec</strong></span></p> + </td> +<td> + <p> + DNSSEC and TSIG protocol processing. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">lame-servers</strong></span></p></td> -<td><p>Lame servers. These are misconfigurations -in remote servers, discovered by BIND 9 when trying to query -those servers during resolution. -</p></td> +<td> + <p><span><strong class="command">lame-servers</strong></span></p> + </td> +<td> + <p> + Lame servers. These are misconfigurations + in remote servers, discovered by BIND 9 when trying to + query + those servers during resolution. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">delegation-only</strong></span></p></td> -<td><p>Delegation only. Logs queries that have have -been forced to NXDOMAIN as the result of a delegation-only zone or -a <span><strong class="command">delegation-only</strong></span> in a hint or stub zone declaration. -</p></td> +<td> + <p><span><strong class="command">delegation-only</strong></span></p> + </td> +<td> + <p> + Delegation only. Logs queries that have have + been forced to NXDOMAIN as the result of a + delegation-only zone or + a <span><strong class="command">delegation-only</strong></span> in a + hint or stub zone declaration. + </p> + </td> </tr> </tbody> </table></div> @@ -1019,9 +1632,11 @@ a <span><strong class="command">delegation-only</strong></span> in a hint or stu </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2578270"></a><span><strong class="command">lwres</strong></span> Statement Grammar</h3></div></div></div> -<p> This is the grammar of the <span><strong class="command">lwres</strong></span> -statement in the <code class="filename">named.conf</code> file:</p> +<a name="id2576406"></a><span><strong class="command">lwres</strong></span> Statement Grammar</h3></div></div></div> +<p> + This is the grammar of the <span><strong class="command">lwres</strong></span> + statement in the <code class="filename">named.conf</code> file: + </p> <pre class="programlisting"><span><strong class="command">lwres</strong></span> { [<span class="optional"> listen-on { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] [<span class="optional"> view <em class="replaceable"><code>view_name</code></em>; </span>] @@ -1032,50 +1647,78 @@ statement in the <code class="filename">named.conf</code> file:</p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2578343"></a><span><strong class="command">lwres</strong></span> Statement Definition and Usage</h3></div></div></div> -<p>The <span><strong class="command">lwres</strong></span> statement configures the name -server to also act as a lightweight resolver server. (See -<a href="Bv9ARM.ch05.html#lwresd" title="Running a Resolver Daemon">the section called “Running a Resolver Daemon”</a>.) There may be be multiple -<span><strong class="command">lwres</strong></span> statements configuring -lightweight resolver servers with different properties.</p> -<p>The <span><strong class="command">listen-on</strong></span> statement specifies a list of -addresses (and ports) that this instance of a lightweight resolver daemon -should accept requests on. If no port is specified, port 921 is used. -If this statement is omitted, requests will be accepted on 127.0.0.1, -port 921.</p> -<p>The <span><strong class="command">view</strong></span> statement binds this instance of a -lightweight resolver daemon to a view in the DNS namespace, so that the -response will be constructed in the same manner as a normal DNS query -matching this view. If this statement is omitted, the default view is -used, and if there is no default view, an error is triggered.</p> -<p>The <span><strong class="command">search</strong></span> statement is equivalent to the -<span><strong class="command">search</strong></span> statement in -<code class="filename">/etc/resolv.conf</code>. It provides a list of domains -which are appended to relative names in queries.</p> -<p>The <span><strong class="command">ndots</strong></span> statement is equivalent to the -<span><strong class="command">ndots</strong></span> statement in -<code class="filename">/etc/resolv.conf</code>. It indicates the minimum -number of dots in a relative domain name that should result in an -exact match lookup before search path elements are appended.</p> +<a name="id2576480"></a><span><strong class="command">lwres</strong></span> Statement Definition and Usage</h3></div></div></div> +<p> + The <span><strong class="command">lwres</strong></span> statement configures the + name + server to also act as a lightweight resolver server. (See + <a href="Bv9ARM.ch05.html#lwresd" title="Running a Resolver Daemon">the section called “Running a Resolver Daemon”</a>.) There may be multiple + <span><strong class="command">lwres</strong></span> statements configuring + lightweight resolver servers with different properties. + </p> +<p> + The <span><strong class="command">listen-on</strong></span> statement specifies a + list of + addresses (and ports) that this instance of a lightweight resolver + daemon + should accept requests on. If no port is specified, port 921 is + used. + If this statement is omitted, requests will be accepted on + 127.0.0.1, + port 921. + </p> +<p> + The <span><strong class="command">view</strong></span> statement binds this + instance of a + lightweight resolver daemon to a view in the DNS namespace, so that + the + response will be constructed in the same manner as a normal DNS + query + matching this view. If this statement is omitted, the default view + is + used, and if there is no default view, an error is triggered. + </p> +<p> + The <span><strong class="command">search</strong></span> statement is equivalent to + the + <span><strong class="command">search</strong></span> statement in + <code class="filename">/etc/resolv.conf</code>. It provides a + list of domains + which are appended to relative names in queries. + </p> +<p> + The <span><strong class="command">ndots</strong></span> statement is equivalent to + the + <span><strong class="command">ndots</strong></span> statement in + <code class="filename">/etc/resolv.conf</code>. It indicates the + minimum + number of dots in a relative domain name that should result in an + exact match lookup before search path elements are appended. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2578406"></a><span><strong class="command">masters</strong></span> Statement Grammar</h3></div></div></div> +<a name="id2576544"></a><span><strong class="command">masters</strong></span> Statement Grammar</h3></div></div></div> <pre class="programlisting"> -<span><strong class="command">masters</strong></span> <em class="replaceable"><code>name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] } ; +<span><strong class="command">masters</strong></span> <em class="replaceable"><code>name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </pre> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2578518"></a><span><strong class="command">masters</strong></span> Statement Definition and Usage </h3></div></div></div> -<p><span><strong class="command">masters</strong></span> lists allow for a common set of masters -to be easily used by multiple stub and slave zones.</p> +<a name="id2576587"></a><span><strong class="command">masters</strong></span> Statement Definition and + Usage</h3></div></div></div> +<p><span><strong class="command">masters</strong></span> + lists allow for a common set of masters to be easily used by + multiple stub and slave zones. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2578533"></a><span><strong class="command">options</strong></span> Statement Grammar</h3></div></div></div> -<p>This is the grammar of the <span><strong class="command">options</strong></span> -statement in the <code class="filename">named.conf</code> file:</p> +<a name="id2576602"></a><span><strong class="command">options</strong></span> Statement Grammar</h3></div></div></div> +<p> + This is the grammar of the <span><strong class="command">options</strong></span> + statement in the <code class="filename">named.conf</code> file: + </p> <pre class="programlisting">options { [<span class="optional"> version <em class="replaceable"><code>version_string</code></em>; </span>] [<span class="optional"> hostname <em class="replaceable"><code>hostname_string</code></em>; </span>] @@ -1089,6 +1732,7 @@ statement in the <code class="filename">named.conf</code> file:</p> [<span class="optional"> dump-file <em class="replaceable"><code>path_name</code></em>; </span>] [<span class="optional"> memstatistics-file <em class="replaceable"><code>path_name</code></em>; </span>] [<span class="optional"> pid-file <em class="replaceable"><code>path_name</code></em>; </span>] + [<span class="optional"> recursing-file <em class="replaceable"><code>path_name</code></em>; </span>] [<span class="optional"> statistics-file <em class="replaceable"><code>path_name</code></em>; </span>] [<span class="optional"> zone-statistics <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> auth-nxdomain <em class="replaceable"><code>yes_or_no</code></em>; </span>] @@ -1102,31 +1746,52 @@ statement in the <code class="filename">named.conf</code> file:</p> [<span class="optional"> host-statistics-max <em class="replaceable"><code>number</code></em>; </span>] [<span class="optional"> minimal-responses <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> multiple-cnames <em class="replaceable"><code>yes_or_no</code></em>; </span>] - [<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em>; </span>] + [<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <em class="replaceable"><code>master-only</code></em>; </span>] [<span class="optional"> recursion <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> rfc2308-type1 <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> use-id-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> dnssec-enable <em class="replaceable"><code>yes_or_no</code></em>; </span>] + [<span class="optional"> dnssec-validation <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> dnssec-lookaside <em class="replaceable"><code>domain</code></em> trust-anchor <em class="replaceable"><code>domain</code></em>; </span>] [<span class="optional"> dnssec-must-be-secure <em class="replaceable"><code>domain yes_or_no</code></em>; </span>] + [<span class="optional"> dnssec-accept-expired <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> forward ( <em class="replaceable"><code>only</code></em> | <em class="replaceable"><code>first</code></em> ); </span>] [<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] - [<span class="optional"> dual-stack-servers [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>domain_name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] | <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ) ; ... }; </span>] - [<span class="optional"> check-names ( <em class="replaceable"><code>master</code></em> | <em class="replaceable"><code>slave</code></em> | <em class="replaceable"><code>response</code></em> )( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>] + [<span class="optional"> dual-stack-servers [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { + ( <em class="replaceable"><code>domain_name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] | + <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ) ; + ... }; </span>] + [<span class="optional"> check-names ( <em class="replaceable"><code>master</code></em> | <em class="replaceable"><code>slave</code></em> | <em class="replaceable"><code>response</code></em> ) + ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>] + [<span class="optional"> check-mx ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>] + [<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>] + [<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em>; </span>] + [<span class="optional"> check-mx-cname ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>] + [<span class="optional"> check-srv-cname ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>] + [<span class="optional"> check-sibling <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> }; </span>] [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> allow-query-cache { <em class="replaceable"><code>address_match_list</code></em> }; </span>] [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>] [<span class="optional"> allow-recursion { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> }; </span>] [<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> allow-v6-synthesis { <em class="replaceable"><code>address_match_list</code></em> }; </span>] [<span class="optional"> blackhole { <em class="replaceable"><code>address_match_list</code></em> }; </span>] [<span class="optional"> avoid-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>] [<span class="optional"> avoid-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>] [<span class="optional"> listen-on [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em> </span>] { <em class="replaceable"><code>address_match_list</code></em> }; </span>] [<span class="optional"> listen-on-v6 [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em> </span>] { <em class="replaceable"><code>address_match_list</code></em> }; </span>] - [<span class="optional"> query-source [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]; </span>] - [<span class="optional"> query-source-v6 [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]; </span>] + [<span class="optional"> query-source ( ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> ) + [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] | + [<span class="optional"> address ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] + [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] ) ; </span>] + [<span class="optional"> query-source-v6 ( ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> ) + [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] | + [<span class="optional"> address ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] + [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] ) ; </span>] [<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em>; </span>] [<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em>; </span>] [<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em>; </span>] @@ -1145,6 +1810,7 @@ statement in the <code class="filename">named.conf</code> file:</p> [<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] [<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] [<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>] + [<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>] [<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] [<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] [<span class="optional"> also-notify { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] @@ -1182,202 +1848,331 @@ statement in the <code class="filename">named.conf</code> file:</p> [<span class="optional"> match-mapped-addresses <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> preferred-glue ( <em class="replaceable"><code>A</code></em> | <em class="replaceable"><code>AAAA</code></em> | <em class="replaceable"><code>NONE</code></em> ); </span>] [<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em>; </span>] + [<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em>; </span>] [<span class="optional"> root-delegation-only [<span class="optional"> exclude { <em class="replaceable"><code>namelist</code></em> } </span>] ; </span>] [<span class="optional"> querylog <em class="replaceable"><code>yes_or_no</code></em> ; </span>] [<span class="optional"> disable-algorithms <em class="replaceable"><code>domain</code></em> { <em class="replaceable"><code>algorithm</code></em>; [<span class="optional"> <em class="replaceable"><code>algorithm</code></em>; </span>] }; </span>] + [<span class="optional"> acache-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>] + [<span class="optional"> acache-cleaning-interval <em class="replaceable"><code>number</code></em>; </span>] + [<span class="optional"> max-acache-size <em class="replaceable"><code>size_spec</code></em> ; </span>] + [<span class="optional"> clients-per-query <em class="replaceable"><code>number</code></em> ; </span>] + [<span class="optional"> max-clients-per-query <em class="replaceable"><code>number</code></em> ; </span>] + [<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>) ; </span>] + [<span class="optional"> empty-server <em class="replaceable"><code>name</code></em> ; </span>] + [<span class="optional"> empty-contact <em class="replaceable"><code>name</code></em> ; </span>] + [<span class="optional"> empty-zones-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>] + [<span class="optional"> disable-empty-zone <em class="replaceable"><code>zone_name</code></em> ; </span>] + [<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>] + [<span class="optional"> zero-no-soa-ttl-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>] }; </pre> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="options"></a><span><strong class="command">options</strong></span> Statement Definition and Usage</h3></div></div></div> -<p>The <span><strong class="command">options</strong></span> statement sets up global options -to be used by <acronym class="acronym">BIND</acronym>. This statement may appear only -once in a configuration file. If there is no <span><strong class="command">options</strong></span> -statement, an options block with each option set to its default will -be used.</p> +<a name="options"></a><span><strong class="command">options</strong></span> Statement Definition and + Usage</h3></div></div></div> +<p> + The <span><strong class="command">options</strong></span> statement sets up global + options + to be used by <acronym class="acronym">BIND</acronym>. This statement + may appear only + once in a configuration file. If there is no <span><strong class="command">options</strong></span> + statement, an options block with each option set to its default will + be used. + </p> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">directory</strong></span></span></dt> -<dd><p>The working directory of the server. -Any non-absolute pathnames in the configuration file will be taken -as relative to this directory. The default location for most server -output files (e.g. <code class="filename">named.run</code>) is this directory. -If a directory is not specified, the working directory defaults -to `<code class="filename">.</code>', the directory from which the server -was started. The directory specified should be an absolute path.</p></dd> +<dd><p> + The working directory of the server. + Any non-absolute pathnames in the configuration file will be + taken + as relative to this directory. The default location for most + server + output files (e.g. <code class="filename">named.run</code>) + is this directory. + If a directory is not specified, the working directory + defaults to `<code class="filename">.</code>', the directory from + which the server + was started. The directory specified should be an absolute + path. + </p></dd> <dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt> -<dd><p>When performing dynamic update of secure zones, the -directory where the public and private key files should be found, -if different than the current working directory. The directory specified -must be an absolute path.</p></dd> +<dd><p> + When performing dynamic update of secure zones, the + directory where the public and private key files should be + found, + if different than the current working directory. The + directory specified + must be an absolute path. + </p></dd> <dt><span class="term"><span><strong class="command">named-xfer</strong></span></span></dt> -<dd><p><span class="emphasis"><em>This option is obsolete.</em></span> -It was used in <acronym class="acronym">BIND</acronym> 8 to -specify the pathname to the <span><strong class="command">named-xfer</strong></span> program. -In <acronym class="acronym">BIND</acronym> 9, no separate <span><strong class="command">named-xfer</strong></span> program is -needed; its functionality is built into the name server.</p></dd> +<dd><p> + <span class="emphasis"><em>This option is obsolete.</em></span> + It was used in <acronym class="acronym">BIND</acronym> 8 to + specify the pathname to the <span><strong class="command">named-xfer</strong></span> program. + In <acronym class="acronym">BIND</acronym> 9, no separate <span><strong class="command">named-xfer</strong></span> program is + needed; its functionality is built into the name server. + </p></dd> <dt><span class="term"><span><strong class="command">tkey-domain</strong></span></span></dt> -<dd><p>The domain appended to the names of all -shared keys generated with <span><strong class="command">TKEY</strong></span>. When a client -requests a <span><strong class="command">TKEY</strong></span> exchange, it may or may not specify -the desired name for the key. If present, the name of the shared -key will be "<code class="varname">client specified part</code>" + -"<code class="varname">tkey-domain</code>". -Otherwise, the name of the shared key will be "<code class="varname">random hex +<dd><p> + The domain appended to the names of all + shared keys generated with + <span><strong class="command">TKEY</strong></span>. When a client + requests a <span><strong class="command">TKEY</strong></span> exchange, it + may or may not specify + the desired name for the key. If present, the name of the + shared + key will be "<code class="varname">client specified part</code>" + + "<code class="varname">tkey-domain</code>". + Otherwise, the name of the shared key will be "<code class="varname">random hex digits</code>" + "<code class="varname">tkey-domain</code>". In most cases, -the <span><strong class="command">domainname</strong></span> should be the server's domain -name.</p></dd> + the <span><strong class="command">domainname</strong></span> should be the + server's domain + name. + </p></dd> <dt><span class="term"><span><strong class="command">tkey-dhkey</strong></span></span></dt> -<dd><p>The Diffie-Hellman key used by the server -to generate shared keys with clients using the Diffie-Hellman mode -of <span><strong class="command">TKEY</strong></span>. The server must be able to load the -public and private keys from files in the working directory. In -most cases, the keyname should be the server's host name.</p></dd> +<dd><p> + The Diffie-Hellman key used by the server + to generate shared keys with clients using the Diffie-Hellman + mode + of <span><strong class="command">TKEY</strong></span>. The server must be + able to load the + public and private keys from files in the working directory. + In + most cases, the keyname should be the server's host name. + </p></dd> <dt><span class="term"><span><strong class="command">cache-file</strong></span></span></dt> <dd><p> - This is for testing only. Do not use. + This is for testing only. Do not use. </p></dd> <dt><span class="term"><span><strong class="command">dump-file</strong></span></span></dt> -<dd><p>The pathname of the file the server dumps -the database to when instructed to do so with -<span><strong class="command">rndc dumpdb</strong></span>. -If not specified, the default is <code class="filename">named_dump.db</code>.</p></dd> +<dd><p> + The pathname of the file the server dumps + the database to when instructed to do so with + <span><strong class="command">rndc dumpdb</strong></span>. + If not specified, the default is <code class="filename">named_dump.db</code>. + </p></dd> <dt><span class="term"><span><strong class="command">memstatistics-file</strong></span></span></dt> -<dd><p>The pathname of the file the server writes memory -usage statistics to on exit. If not specified, -the default is <code class="filename">named.memstats</code>.</p></dd> +<dd> +<p> + The pathname of the file the server writes memory + usage statistics to on exit. If specified the + statistics will be written to the file on exit. + </p> +<p> + In <acronym class="acronym">BIND</acronym> 9.5 and later this will + default to <code class="filename">named.memstats</code>. + <acronym class="acronym">BIND</acronym> 9.5 will also introduce + <span><strong class="command">memstatistics</strong></span> to control the + writing. + </p> +</dd> <dt><span class="term"><span><strong class="command">pid-file</strong></span></span></dt> -<dd><p>The pathname of the file the server writes its process ID -in. If not specified, the default is <code class="filename">/var/run/named.pid</code>. -The pid-file is used by programs that want to send signals to the running -name server. Specifying <span><strong class="command">pid-file none</strong></span> disables the -use of a PID file — no file will be written and any -existing one will be removed. Note that <span><strong class="command">none</strong></span> -is a keyword, not a file name, and therefore is not enclosed in -double quotes.</p></dd> +<dd><p> + The pathname of the file the server writes its process ID + in. If not specified, the default is <code class="filename">/var/run/named.pid</code>. + The pid-file is used by programs that want to send signals to + the running + name server. Specifying <span><strong class="command">pid-file none</strong></span> disables the + use of a PID file — no file will be written and any + existing one will be removed. Note that <span><strong class="command">none</strong></span> + is a keyword, not a filename, and therefore is not enclosed + in + double quotes. + </p></dd> +<dt><span class="term"><span><strong class="command">recursing-file</strong></span></span></dt> +<dd><p> + The pathname of the file the server dumps + the queries that are currently recursing when instructed + to do so with <span><strong class="command">rndc recursing</strong></span>. + If not specified, the default is <code class="filename">named.recursing</code>. + </p></dd> <dt><span class="term"><span><strong class="command">statistics-file</strong></span></span></dt> -<dd><p>The pathname of the file the server appends statistics -to when instructed to do so using <span><strong class="command">rndc stats</strong></span>. -If not specified, the default is <code class="filename">named.stats</code> in the -server's current directory. The format of the file is described -in <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called “The Statistics File”</a>.</p></dd> +<dd><p> + The pathname of the file the server appends statistics + to when instructed to do so using <span><strong class="command">rndc stats</strong></span>. + If not specified, the default is <code class="filename">named.stats</code> in the + server's current directory. The format of the file is + described + in <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called “The Statistics File”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">port</strong></span></span></dt> <dd><p> -The UDP/TCP port number the server uses for -receiving and sending DNS protocol traffic. -The default is 53. This option is mainly intended for server testing; -a server using a port other than 53 will not be able to communicate with -the global DNS. -</p></dd> + The UDP/TCP port number the server uses for + receiving and sending DNS protocol traffic. + The default is 53. This option is mainly intended for server + testing; + a server using a port other than 53 will not be able to + communicate with + the global DNS. + </p></dd> <dt><span class="term"><span><strong class="command">random-device</strong></span></span></dt> <dd><p> -The source of entropy to be used by the server. Entropy is primarily needed -for DNSSEC operations, such as TKEY transactions and dynamic update of signed -zones. This options specifies the device (or file) from which to read -entropy. If this is a file, operations requiring entropy will fail when the -file has been exhausted. If not specified, the default value is -<code class="filename">/dev/random</code> -(or equivalent) when present, and none otherwise. The -<span><strong class="command">random-device</strong></span> option takes effect during -the initial configuration load at server startup time and -is ignored on subsequent reloads.</p></dd> + The source of entropy to be used by the server. Entropy is + primarily needed + for DNSSEC operations, such as TKEY transactions and dynamic + update of signed + zones. This options specifies the device (or file) from which + to read + entropy. If this is a file, operations requiring entropy will + fail when the + file has been exhausted. If not specified, the default value + is + <code class="filename">/dev/random</code> + (or equivalent) when present, and none otherwise. The + <span><strong class="command">random-device</strong></span> option takes + effect during + the initial configuration load at server startup time and + is ignored on subsequent reloads. + </p></dd> <dt><span class="term"><span><strong class="command">preferred-glue</strong></span></span></dt> <dd><p> -If specified, the listed type (A or AAAA) will be emitted before other glue -in the additional section of a query response. -The default is not to prefer any type (NONE). -</p></dd> + If specified, the listed type (A or AAAA) will be emitted + before other glue + in the additional section of a query response. + The default is not to prefer any type (NONE). + </p></dd> <dt><span class="term"><span><strong class="command">root-delegation-only</strong></span></span></dt> <dd> <p> -Turn on enforcement of delegation-only in TLDs (top level domains) -and root zones with an optional exclude list. -</p> + Turn on enforcement of delegation-only in TLDs (top level domains) and root zones + with an optional + exclude list. + </p> <p> -Note some TLDs are not delegation only (e.g. "DE", "LV", "US" and "MUSEUM"). -</p> + Note some TLDs are not delegation only (e.g. "DE", "LV", "US" + and "MUSEUM"). + </p> <pre class="programlisting"> options { - root-delegation-only exclude { "de"; "lv"; "us"; "museum"; }; + root-delegation-only exclude { "de"; "lv"; "us"; "museum"; }; }; </pre> </dd> <dt><span class="term"><span><strong class="command">disable-algorithms</strong></span></span></dt> <dd><p> -Disable the specified DNSSEC algorithms at and below the specified name. -Multiple <span><strong class="command">disable-algorithms</strong></span> statements are allowed. -Only the most specific will be applied. -</p></dd> + Disable the specified DNSSEC algorithms at and below the + specified name. + Multiple <span><strong class="command">disable-algorithms</strong></span> + statements are allowed. + Only the most specific will be applied. + </p></dd> <dt><span class="term"><span><strong class="command">dnssec-lookaside</strong></span></span></dt> <dd><p> -When set, <span><strong class="command">dnssec-lookaside</strong></span> provides the -validator with an alternate method to validate DNSKEY records at the -top of a zone. When a DNSKEY is at or below a domain specified by the -deepest <span><strong class="command">dnssec-lookaside</strong></span>, and the normal dnssec validation -has left the key untrusted, the trust-anchor will be append to the key -name and a DLV record will be looked up to see if it can validate the -key. If the DLV record validates a DNSKEY (similarly to the way a DS -record does) the DNSKEY RRset is deemed to be trusted. -</p></dd> + When set, <span><strong class="command">dnssec-lookaside</strong></span> + provides the + validator with an alternate method to validate DNSKEY records + at the + top of a zone. When a DNSKEY is at or below a domain + specified by the + deepest <span><strong class="command">dnssec-lookaside</strong></span>, and + the normal dnssec validation + has left the key untrusted, the trust-anchor will be append to + the key + name and a DLV record will be looked up to see if it can + validate the + key. If the DLV record validates a DNSKEY (similarly to the + way a DS + record does) the DNSKEY RRset is deemed to be trusted. + </p></dd> <dt><span class="term"><span><strong class="command">dnssec-must-be-secure</strong></span></span></dt> <dd><p> -Specify heirarchies which must be or may not be secure (signed and validated). -If <strong class="userinput"><code>yes</code></strong>, then named will only accept answers if they -are secure. -If <strong class="userinput"><code>no</code></strong>, then normal dnssec validation applies -allowing for insecure answers to be accepted. -The specified domain must be under a <span><strong class="command">trusted-key</strong></span> or -<span><strong class="command">dnssec-lookaside</strong></span> must be active. -</p></dd> + Specify hierarchies which must be or may not be secure (signed and + validated). + If <strong class="userinput"><code>yes</code></strong>, then named will only accept + answers if they + are secure. + If <strong class="userinput"><code>no</code></strong>, then normal dnssec validation + applies + allowing for insecure answers to be accepted. + The specified domain must be under a <span><strong class="command">trusted-key</strong></span> or + <span><strong class="command">dnssec-lookaside</strong></span> must be + active. + </p></dd> </dl></div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="boolean_options"></a>Boolean Options</h4></div></div></div> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">auth-nxdomain</strong></span></span></dt> -<dd><p>If <strong class="userinput"><code>yes</code></strong>, then the <span><strong class="command">AA</strong></span> bit -is always set on NXDOMAIN responses, even if the server is not actually -authoritative. The default is <strong class="userinput"><code>no</code></strong>; this is -a change from <acronym class="acronym">BIND</acronym> 8. If you are using very old DNS software, you -may need to set it to <strong class="userinput"><code>yes</code></strong>.</p></dd> +<dd><p> + If <strong class="userinput"><code>yes</code></strong>, then the <span><strong class="command">AA</strong></span> bit + is always set on NXDOMAIN responses, even if the server is + not actually + authoritative. The default is <strong class="userinput"><code>no</code></strong>; + this is + a change from <acronym class="acronym">BIND</acronym> 8. If you + are using very old DNS software, you + may need to set it to <strong class="userinput"><code>yes</code></strong>. + </p></dd> <dt><span class="term"><span><strong class="command">deallocate-on-exit</strong></span></span></dt> -<dd><p>This option was used in <acronym class="acronym">BIND</acronym> 8 to enable checking -for memory leaks on exit. <acronym class="acronym">BIND</acronym> 9 ignores the option and always performs -the checks.</p></dd> +<dd><p> + This option was used in <acronym class="acronym">BIND</acronym> + 8 to enable checking + for memory leaks on exit. <acronym class="acronym">BIND</acronym> 9 ignores the option and always performs + the checks. + </p></dd> <dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt> <dd> -<p>If <strong class="userinput"><code>yes</code></strong>, then the -server treats all zones as if they are doing zone transfers across -a dial-on-demand dialup link, which can be brought up by traffic -originating from this server. This has different effects according -to zone type and concentrates the zone maintenance so that it all -happens in a short interval, once every <span><strong class="command">heartbeat-interval</strong></span> and -hopefully during the one call. It also suppresses some of the normal -zone maintenance traffic. The default is <strong class="userinput"><code>no</code></strong>.</p> -<p>The <span><strong class="command">dialup</strong></span> option -may also be specified in the <span><strong class="command">view</strong></span> and -<span><strong class="command">zone</strong></span> statements, -in which case it overrides the global <span><strong class="command">dialup</strong></span> -option.</p> -<p>If the zone is a master zone, then the server will send out a NOTIFY -request to all the slaves (default). This should 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. -The set of servers to which NOTIFY is sent can be controlled by -<span><strong class="command">notify</strong></span> and <span><strong class="command">also-notify</strong></span>.</p> -<p>If 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 -<span><strong class="command">heartbeat-interval</strong></span> expires in addition to sending -NOTIFY requests.</p> -<p>Finer control can be achieved by using -<strong class="userinput"><code>notify</code></strong> which only sends NOTIFY messages, -<strong class="userinput"><code>notify-passive</code></strong> which sends NOTIFY messages and -suppresses the normal refresh queries, <strong class="userinput"><code>refresh</code></strong> -which suppresses normal refresh processing and sends refresh queries -when the <span><strong class="command">heartbeat-interval</strong></span> expires, and -<strong class="userinput"><code>passive</code></strong> which just disables normal refresh -processing.</p> +<p> + If <strong class="userinput"><code>yes</code></strong>, then the + server treats all zones as if they are doing zone transfers + across + a dial-on-demand dialup link, which can be brought up by + traffic + originating from this server. This has different effects + according + to zone type and concentrates the zone maintenance so that + it all + happens in a short interval, once every <span><strong class="command">heartbeat-interval</strong></span> and + hopefully during the one call. It also suppresses some of + the normal + zone maintenance traffic. The default is <strong class="userinput"><code>no</code></strong>. + </p> +<p> + The <span><strong class="command">dialup</strong></span> option + may also be specified in the <span><strong class="command">view</strong></span> and + <span><strong class="command">zone</strong></span> statements, + in which case it overrides the global <span><strong class="command">dialup</strong></span> + option. + </p> +<p> + If the zone is a master zone, then the server will send out a + NOTIFY + request to all the slaves (default). This should 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. + The set of servers to which NOTIFY is sent can be controlled + by + <span><strong class="command">notify</strong></span> and <span><strong class="command">also-notify</strong></span>. + </p> +<p> + If 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 + <span><strong class="command">heartbeat-interval</strong></span> expires in + addition to sending + NOTIFY requests. + </p> +<p> + Finer control can be achieved by using + <strong class="userinput"><code>notify</code></strong> which only sends NOTIFY + messages, + <strong class="userinput"><code>notify-passive</code></strong> which sends NOTIFY + messages and + suppresses the normal refresh queries, <strong class="userinput"><code>refresh</code></strong> + which suppresses normal refresh processing and sends refresh + queries + when the <span><strong class="command">heartbeat-interval</strong></span> + expires, and + <strong class="userinput"><code>passive</code></strong> which just disables normal + refresh + processing. + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -1387,818 +2182,1373 @@ processing.</p> </colgroup> <tbody> <tr> -<td><p>dialup mode</p></td> -<td><p>normal refresh</p></td> -<td><p>heart-beat refresh</p></td> -<td><p>heart-beat notify</p></td> +<td> + <p> + dialup mode + </p> + </td> +<td> + <p> + normal refresh + </p> + </td> +<td> + <p> + heart-beat refresh + </p> + </td> +<td> + <p> + heart-beat notify + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">no</strong></span> (default)</p></td> -<td><p>yes</p></td> -<td><p>no</p></td> -<td><p>no</p></td> +<td> + <p><span><strong class="command">no</strong></span> (default)</p> + </td> +<td> + <p> + yes + </p> + </td> +<td> + <p> + no + </p> + </td> +<td> + <p> + no + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">yes</strong></span></p></td> -<td><p>no</p></td> -<td><p>yes</p></td> -<td><p>yes</p></td> +<td> + <p><span><strong class="command">yes</strong></span></p> + </td> +<td> + <p> + no + </p> + </td> +<td> + <p> + yes + </p> + </td> +<td> + <p> + yes + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">notify</strong></span></p></td> -<td><p>yes</p></td> -<td><p>no</p></td> -<td><p>yes</p></td> +<td> + <p><span><strong class="command">notify</strong></span></p> + </td> +<td> + <p> + yes + </p> + </td> +<td> + <p> + no + </p> + </td> +<td> + <p> + yes + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">refresh</strong></span></p></td> -<td><p>no</p></td> -<td><p>yes</p></td> -<td><p>no</p></td> +<td> + <p><span><strong class="command">refresh</strong></span></p> + </td> +<td> + <p> + no + </p> + </td> +<td> + <p> + yes + </p> + </td> +<td> + <p> + no + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">passive</strong></span></p></td> -<td><p>no</p></td> -<td><p>no</p></td> -<td><p>no</p></td> +<td> + <p><span><strong class="command">passive</strong></span></p> + </td> +<td> + <p> + no + </p> + </td> +<td> + <p> + no + </p> + </td> +<td> + <p> + no + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">notify-passive</strong></span></p></td> -<td><p>no</p></td> -<td><p>no</p></td> -<td><p>yes</p></td> +<td> + <p><span><strong class="command">notify-passive</strong></span></p> + </td> +<td> + <p> + no + </p> + </td> +<td> + <p> + no + </p> + </td> +<td> + <p> + yes + </p> + </td> </tr> </tbody> </table></div> -<p>Note that normal NOTIFY processing is not affected by -<span><strong class="command">dialup</strong></span>.</p> +<p> + Note that normal NOTIFY processing is not affected by + <span><strong class="command">dialup</strong></span>. + </p> </dd> <dt><span class="term"><span><strong class="command">fake-iquery</strong></span></span></dt> -<dd><p>In <acronym class="acronym">BIND</acronym> 8, this option -enabled simulating the obsolete DNS query type -IQUERY. <acronym class="acronym">BIND</acronym> 9 never does IQUERY simulation. -</p></dd> +<dd><p> + In <acronym class="acronym">BIND</acronym> 8, this option + enabled simulating the obsolete DNS query type + IQUERY. <acronym class="acronym">BIND</acronym> 9 never does + IQUERY simulation. + </p></dd> <dt><span class="term"><span><strong class="command">fetch-glue</strong></span></span></dt> -<dd><p>This option is obsolete. -In BIND 8, <strong class="userinput"><code>fetch-glue yes</code></strong> -caused the server to attempt to fetch glue resource records it -didn't have when constructing the additional -data section of a response. This is now considered a bad idea -and BIND 9 never does it.</p></dd> +<dd><p> + This option is obsolete. + In BIND 8, <strong class="userinput"><code>fetch-glue yes</code></strong> + caused the server to attempt to fetch glue resource records + it + didn't have when constructing the additional + data section of a response. This is now considered a bad + idea + and BIND 9 never does it. + </p></dd> <dt><span class="term"><span><strong class="command">flush-zones-on-shutdown</strong></span></span></dt> -<dd><p>When the nameserver exits due receiving SIGTERM, -flush or do not flush any pending zone writes. The default is -<span><strong class="command">flush-zones-on-shutdown</strong></span> <strong class="userinput"><code>no</code></strong>. -</p></dd> +<dd><p> + When the nameserver exits due receiving SIGTERM, + flush or do not flush any pending zone writes. The default + is + <span><strong class="command">flush-zones-on-shutdown</strong></span> <strong class="userinput"><code>no</code></strong>. + </p></dd> <dt><span class="term"><span><strong class="command">has-old-clients</strong></span></span></dt> -<dd><p>This option was incorrectly implemented -in <acronym class="acronym">BIND</acronym> 8, and is ignored by <acronym class="acronym">BIND</acronym> 9. -To achieve the intended effect -of -<span><strong class="command">has-old-clients</strong></span> <strong class="userinput"><code>yes</code></strong>, specify -the two separate options <span><strong class="command">auth-nxdomain</strong></span> <strong class="userinput"><code>yes</code></strong> -and <span><strong class="command">rfc2308-type1</strong></span> <strong class="userinput"><code>no</code></strong> instead. -</p></dd> +<dd><p> + This option was incorrectly implemented + in <acronym class="acronym">BIND</acronym> 8, and is ignored by <acronym class="acronym">BIND</acronym> 9. + To achieve the intended effect + of + <span><strong class="command">has-old-clients</strong></span> <strong class="userinput"><code>yes</code></strong>, specify + the two separate options <span><strong class="command">auth-nxdomain</strong></span> <strong class="userinput"><code>yes</code></strong> + and <span><strong class="command">rfc2308-type1</strong></span> <strong class="userinput"><code>no</code></strong> instead. + </p></dd> <dt><span class="term"><span><strong class="command">host-statistics</strong></span></span></dt> -<dd><p>In BIND 8, this enables keeping of -statistics for every host that the name server interacts with. -Not implemented in BIND 9. -</p></dd> +<dd><p> + In BIND 8, this enables keeping of + statistics for every host that the name server interacts + with. + Not implemented in BIND 9. + </p></dd> <dt><span class="term"><span><strong class="command">maintain-ixfr-base</strong></span></span></dt> -<dd><p><span class="emphasis"><em>This option is obsolete</em></span>. - It was used in <acronym class="acronym">BIND</acronym> 8 to determine whether a transaction log was -kept for Incremental Zone Transfer. <acronym class="acronym">BIND</acronym> 9 maintains a transaction -log whenever possible. If you need to disable outgoing incremental zone -transfers, use <span><strong class="command">provide-ixfr</strong></span> <strong class="userinput"><code>no</code></strong>. -</p></dd> +<dd><p> + <span class="emphasis"><em>This option is obsolete</em></span>. + It was used in <acronym class="acronym">BIND</acronym> 8 to + determine whether a transaction log was + kept for Incremental Zone Transfer. <acronym class="acronym">BIND</acronym> 9 maintains a transaction + log whenever possible. If you need to disable outgoing + incremental zone + transfers, use <span><strong class="command">provide-ixfr</strong></span> <strong class="userinput"><code>no</code></strong>. + </p></dd> <dt><span class="term"><span><strong class="command">minimal-responses</strong></span></span></dt> -<dd><p>If <strong class="userinput"><code>yes</code></strong>, then when generating -responses the server will only add records to the authority and -additional data sections when they are required (e.g. delegations, -negative responses). This may improve the performance of the server. -The default is <strong class="userinput"><code>no</code></strong>. -</p></dd> +<dd><p> + If <strong class="userinput"><code>yes</code></strong>, then when generating + responses the server will only add records to the authority + and additional data sections when they are required (e.g. + delegations, negative responses). This may improve the + performance of the server. + The default is <strong class="userinput"><code>no</code></strong>. + </p></dd> <dt><span class="term"><span><strong class="command">multiple-cnames</strong></span></span></dt> -<dd><p>This option was used in <acronym class="acronym">BIND</acronym> 8 to allow -a domain name to have multiple CNAME records in violation of the -DNS standards. <acronym class="acronym">BIND</acronym> 9.2 always strictly -enforces the CNAME rules both in master files and dynamic updates. -</p></dd> +<dd><p> + This option was used in <acronym class="acronym">BIND</acronym> 8 to allow + a domain name to have multiple CNAME records in violation of + the DNS standards. <acronym class="acronym">BIND</acronym> 9.2 onwards + always strictly enforces the CNAME rules both in master + files and dynamic updates. + </p></dd> <dt><span class="term"><span><strong class="command">notify</strong></span></span></dt> <dd> -<p>If <strong class="userinput"><code>yes</code></strong> (the default), -DNS NOTIFY messages are sent when a zone the server is authoritative for -changes, see <a href="Bv9ARM.ch04.html#notify" title="Notify">the section called “Notify”</a>. The messages are sent to the -servers listed in the zone's NS records (except the master server identified -in the SOA MNAME field), and to any servers listed in the -<span><strong class="command">also-notify</strong></span> option. -</p> <p> -If <strong class="userinput"><code>explicit</code></strong>, notifies are sent only to -servers explicitly listed using <span><strong class="command">also-notify</strong></span>. -If <strong class="userinput"><code>no</code></strong>, no notifies are sent. -</p> + If <strong class="userinput"><code>yes</code></strong> (the default), + DNS NOTIFY messages are sent when a zone the server is + authoritative for + changes, see <a href="Bv9ARM.ch04.html#notify" title="Notify">the section called “Notify”</a>. The messages are + sent to the + servers listed in the zone's NS records (except the master + server identified + in the SOA MNAME field), and to any servers listed in the + <span><strong class="command">also-notify</strong></span> option. + </p> +<p> + If <strong class="userinput"><code>master-only</code></strong>, notifies are only + sent + for master zones. + If <strong class="userinput"><code>explicit</code></strong>, notifies are sent only + to + servers explicitly listed using <span><strong class="command">also-notify</strong></span>. + If <strong class="userinput"><code>no</code></strong>, no notifies are sent. + </p> <p> -The <span><strong class="command">notify</strong></span> option may also be -specified in the <span><strong class="command">zone</strong></span> statement, -in which case it overrides the <span><strong class="command">options notify</strong></span> statement. -It would only be necessary to turn off this option if it caused slaves -to crash.</p> + The <span><strong class="command">notify</strong></span> option may also be + specified in the <span><strong class="command">zone</strong></span> + statement, + in which case it overrides the <span><strong class="command">options notify</strong></span> statement. + It would only be necessary to turn off this option if it + caused slaves + to crash. + </p> </dd> <dt><span class="term"><span><strong class="command">recursion</strong></span></span></dt> -<dd><p>If <strong class="userinput"><code>yes</code></strong>, and a -DNS query requests recursion, then the server will attempt to do -all the work required to answer the query. If recursion is off -and the server does not already know the answer, it will return a -referral response. The default is <strong class="userinput"><code>yes</code></strong>. -Note that setting <span><strong class="command">recursion no</strong></span> 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 <span><strong class="command">fetch-glue</strong></span> above. -</p></dd> +<dd><p> + If <strong class="userinput"><code>yes</code></strong>, and a + DNS query requests recursion, then the server will attempt + to do + all the work required to answer the query. If recursion is + off + and the server does not already know the answer, it will + return a + referral response. The default is + <strong class="userinput"><code>yes</code></strong>. + Note that setting <span><strong class="command">recursion no</strong></span> 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 <span><strong class="command">fetch-glue</strong></span> above. + </p></dd> <dt><span class="term"><span><strong class="command">rfc2308-type1</strong></span></span></dt> <dd> -<p>Setting this to <strong class="userinput"><code>yes</code></strong> will -cause the server to send NS records along with the SOA record for negative -answers. The default is <strong class="userinput"><code>no</code></strong>.</p> +<p> + Setting this to <strong class="userinput"><code>yes</code></strong> will + cause the server to send NS records along with the SOA + record for negative + answers. The default is <strong class="userinput"><code>no</code></strong>. + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>Not yet implemented in <acronym class="acronym">BIND</acronym> 9.</p> +<p> + Not yet implemented in <acronym class="acronym">BIND</acronym> + 9. + </p> </div> </dd> <dt><span class="term"><span><strong class="command">use-id-pool</strong></span></span></dt> -<dd><p><span class="emphasis"><em>This option is obsolete</em></span>. -<acronym class="acronym">BIND</acronym> 9 always allocates query IDs from a pool. -</p></dd> +<dd><p> + <span class="emphasis"><em>This option is obsolete</em></span>. + <acronym class="acronym">BIND</acronym> 9 always allocates query + IDs from a pool. + </p></dd> <dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt> -<dd><p>If <strong class="userinput"><code>yes</code></strong>, the server will collect -statistical data on all zones (unless specifically turned off -on a per-zone basis by specifying <span><strong class="command">zone-statistics no</strong></span> -in the <span><strong class="command">zone</strong></span> statement). These statistics may be accessed -using <span><strong class="command">rndc stats</strong></span>, which will dump them to the file listed -in the <span><strong class="command">statistics-file</strong></span>. See also <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called “The Statistics File”</a>. -</p></dd> +<dd><p> + If <strong class="userinput"><code>yes</code></strong>, the server will collect + statistical data on all zones (unless specifically turned + off + on a per-zone basis by specifying <span><strong class="command">zone-statistics no</strong></span> + in the <span><strong class="command">zone</strong></span> statement). + These statistics may be accessed + using <span><strong class="command">rndc stats</strong></span>, which will + dump them to the file listed + in the <span><strong class="command">statistics-file</strong></span>. See + also <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called “The Statistics File”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">use-ixfr</strong></span></span></dt> -<dd><p><span class="emphasis"><em>This option is obsolete</em></span>. -If you need to disable IXFR to a particular server or servers see -the information on the <span><strong class="command">provide-ixfr</strong></span> option -in <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and Usage”</a>. See also -<a href="Bv9ARM.ch04.html#incremental_zone_transfers" title="Incremental Zone Transfers (IXFR)">the section called “Incremental Zone Transfers (IXFR)”</a>. -</p></dd> +<dd><p> + <span class="emphasis"><em>This option is obsolete</em></span>. + If you need to disable IXFR to a particular server or + servers, see + the information on the <span><strong class="command">provide-ixfr</strong></span> option + in <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and + Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and + Usage”</a>. + See also + <a href="Bv9ARM.ch04.html#incremental_zone_transfers" title="Incremental Zone Transfers (IXFR)">the section called “Incremental Zone Transfers (IXFR)”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">provide-ixfr</strong></span></span></dt> <dd><p> -See the description of -<span><strong class="command">provide-ixfr</strong></span> in -<a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and Usage”</a>. -</p></dd> + See the description of + <span><strong class="command">provide-ixfr</strong></span> in + <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and + Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and + Usage”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">request-ixfr</strong></span></span></dt> <dd><p> -See the description of -<span><strong class="command">request-ixfr</strong></span> in -<a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and Usage”</a>. -</p></dd> + See the description of + <span><strong class="command">request-ixfr</strong></span> in + <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and + Usage">the section called “<span><strong class="command">server</strong></span> Statement Definition and + Usage”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">treat-cr-as-space</strong></span></span></dt> -<dd><p>This option was used in <acronym class="acronym">BIND</acronym> 8 to make -the server treat carriage return ("<span><strong class="command">\r</strong></span>") characters the same way -as a space or tab character, -to facilitate loading of zone files on a UNIX system that were generated -on an NT or DOS machine. In <acronym class="acronym">BIND</acronym> 9, both UNIX "<span><strong class="command">\n</strong></span>" -and NT/DOS "<span><strong class="command">\r\n</strong></span>" newlines are always accepted, -and the option is ignored.</p></dd> +<dd><p> + This option was used in <acronym class="acronym">BIND</acronym> + 8 to make + the server treat carriage return ("<span><strong class="command">\r</strong></span>") characters the same way + as a space or tab character, + to facilitate loading of zone files on a UNIX system that + were generated + on an NT or DOS machine. In <acronym class="acronym">BIND</acronym> 9, both UNIX "<span><strong class="command">\n</strong></span>" + and NT/DOS "<span><strong class="command">\r\n</strong></span>" newlines + are always accepted, + and the option is ignored. + </p></dd> <dt> <span class="term"><span><strong class="command">additional-from-auth</strong></span>, </span><span class="term"><span><strong class="command">additional-from-cache</strong></span></span> </dt> <dd> <p> -These options control the behavior of an authoritative server when -answering queries which have additional data, or when following CNAME -and DNAME chains. -</p> + These options control the behavior of an authoritative + server when + answering queries which have additional data, or when + following CNAME + and DNAME chains. + </p> <p> -When both of these options are set to <strong class="userinput"><code>yes</code></strong> -(the default) and a -query is being answered from authoritative data (a zone -configured into the server), the additional data section of the -reply will be filled in using data from other authoritative zones -and from the cache. In some situations this is undesirable, such -as when there is concern over the correctness of the cache, or -in servers where slave zones may be added and modified by -untrusted third parties. Also, avoiding -the search for this additional data will speed up server operations -at the possible expense of additional queries to resolve what would -otherwise be provided in the additional section. -</p> + When both of these options are set to <strong class="userinput"><code>yes</code></strong> + (the default) and a + query is being answered from authoritative data (a zone + configured into the server), the additional data section of + the + reply will be filled in using data from other authoritative + zones + and from the cache. In some situations this is undesirable, + such + as when there is concern over the correctness of the cache, + or + in servers where slave zones may be added and modified by + untrusted third parties. Also, avoiding + the search for this additional data will speed up server + operations + at the possible expense of additional queries to resolve + what would + otherwise be provided in the additional section. + </p> <p> -For example, if a query asks for an MX record for host <code class="literal">foo.example.com</code>, -and the record found is "<code class="literal">MX 10 mail.example.net</code>", normally the address -records (A and AAAA) for <code class="literal">mail.example.net</code> will be provided as well, -if known, even though they are not in the example.com zone. -Setting these options to <span><strong class="command">no</strong></span> disables this behavior and makes -the server only search for additional data in the zone it answers from. -</p> + For example, if a query asks for an MX record for host <code class="literal">foo.example.com</code>, + and the record found is "<code class="literal">MX 10 mail.example.net</code>", normally the address + records (A and AAAA) for <code class="literal">mail.example.net</code> will be provided as well, + if known, even though they are not in the example.com zone. + Setting these options to <span><strong class="command">no</strong></span> + disables this behavior and makes + the server only search for additional data in the zone it + answers from. + </p> <p> -These options are intended for use in authoritative-only -servers, or in authoritative-only views. Attempts to set -them to <span><strong class="command">no</strong></span> without also specifying -<span><strong class="command">recursion no</strong></span> will cause the server to -ignore the options and log a warning message. -</p> + These options are intended for use in authoritative-only + servers, or in authoritative-only views. Attempts to set + them to <span><strong class="command">no</strong></span> without also + specifying + <span><strong class="command">recursion no</strong></span> will cause the + server to + ignore the options and log a warning message. + </p> <p> -Specifying <span><strong class="command">additional-from-cache no</strong></span> actually -disables the use of the cache not only for additional data lookups -but also when looking up the answer. This is usually the desired -behavior in an authoritative-only server where the correctness of -the cached data is an issue. -</p> + Specifying <span><strong class="command">additional-from-cache no</strong></span> actually + disables the use of the cache not only for additional data + lookups + but also when looking up the answer. This is usually the + desired + behavior in an authoritative-only server where the + correctness of + the cached data is an issue. + </p> <p> -When a name server is non-recursively queried for a name that is not -below the apex of any served zone, it normally answers with an -"upwards referral" to the root servers or the servers of some other -known parent of the query name. Since the data in an upwards referral -comes from the cache, the server will not be able to provide upwards -referrals when <span><strong class="command">additional-from-cache no</strong></span> -has been specified. Instead, it will respond to such queries -with REFUSED. This should not cause any problems since -upwards referrals are not required for the resolution process. -</p> + When a name server is non-recursively queried for a name + that is not + below the apex of any served zone, it normally answers with + an + "upwards referral" to the root servers or the servers of + some other + known parent of the query name. Since the data in an + upwards referral + comes from the cache, the server will not be able to provide + upwards + referrals when <span><strong class="command">additional-from-cache no</strong></span> + has been specified. Instead, it will respond to such + queries + with REFUSED. This should not cause any problems since + upwards referrals are not required for the resolution + process. + </p> </dd> <dt><span class="term"><span><strong class="command">match-mapped-addresses</strong></span></span></dt> -<dd><p>If <strong class="userinput"><code>yes</code></strong>, then an -IPv4-mapped IPv6 address will match any address match -list entries that match the corresponding IPv4 address. -Enabling this option is sometimes useful on IPv6-enabled Linux -systems, to work around a kernel quirk that causes IPv4 -TCP connections such as zone transfers to be accepted -on an IPv6 socket using mapped addresses, causing -address match lists designed for IPv4 to fail to match. -The use of this option for any other purpose is discouraged. -</p></dd> +<dd><p> + If <strong class="userinput"><code>yes</code></strong>, then an + IPv4-mapped IPv6 address will match any address match + list entries that match the corresponding IPv4 address. + Enabling this option is sometimes useful on IPv6-enabled + Linux + systems, to work around a kernel quirk that causes IPv4 + TCP connections such as zone transfers to be accepted + on an IPv6 socket using mapped addresses, causing + address match lists designed for IPv4 to fail to match. + The use of this option for any other purpose is discouraged. + </p></dd> <dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt> <dd> <p> -When <strong class="userinput"><code>yes</code></strong> and the server loads a new version of a master -zone from its zone file or receives a new version of a slave -file by a non-incremental zone transfer, it will compare -the new version to the previous one and calculate a set -of differences. The differences are then logged in the -zone's journal file such that the changes can be transmitted -to downstream slaves as an incremental zone transfer. -</p> + When <strong class="userinput"><code>yes</code></strong> and the server loads a new version of a master + zone from its zone file or receives a new version of a slave + file by a non-incremental zone transfer, it will compare + the new version to the previous one and calculate a set + of differences. The differences are then logged in the + zone's journal file such that the changes can be transmitted + to downstream slaves as an incremental zone transfer. + </p> <p> -By allowing incremental zone transfers to be used for -non-dynamic zones, this option saves bandwidth at the -expense of increased CPU and memory consumption at the master. -In particular, if the new version of a zone is completely -different from the previous one, the set of differences -will be of a size comparable to the combined size of the -old and new zone version, and the server will need to -temporarily allocate memory to hold this complete -difference set. -</p> + By allowing incremental zone transfers to be used for + non-dynamic zones, this option saves bandwidth at the + expense of increased CPU and memory consumption at the + master. + In particular, if the new version of a zone is completely + different from the previous one, the set of differences + will be of a size comparable to the combined size of the + old and new zone version, and the server will need to + temporarily allocate memory to hold this complete + difference set. + </p> +<p><span><strong class="command">ixfr-from-differences</strong></span> + also accepts <span><strong class="command">master</strong></span> and + <span><strong class="command">slave</strong></span> at the view and options + levels which causes + <span><strong class="command">ixfr-from-differences</strong></span> to apply to + all <span><strong class="command">master</strong></span> or + <span><strong class="command">slave</strong></span> zones respectively. + </p> </dd> <dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt> <dd><p> -This should be set when you have multiple masters for a zone and the -addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, named will not log -when the serial number on the master is less than what named currently -has. The default is <strong class="userinput"><code>no</code></strong>. -</p></dd> + This should be set when you have multiple masters for a zone + and the + addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, named will + not log + when the serial number on the master is less than what named + currently + has. The default is <strong class="userinput"><code>no</code></strong>. + </p></dd> <dt><span class="term"><span><strong class="command">dnssec-enable</strong></span></span></dt> <dd><p> -Enable DNSSEC support in named. Unless set to <strong class="userinput"><code>yes</code></strong>, -named behaves as if it does not support DNSSEC. -The default is <strong class="userinput"><code>no</code></strong>. -</p></dd> + Enable DNSSEC support in named. Unless set to <strong class="userinput"><code>yes</code></strong>, + named behaves as if it does not support DNSSEC. + The default is <strong class="userinput"><code>yes</code></strong>. + </p></dd> +<dt><span class="term"><span><strong class="command">dnssec-validation</strong></span></span></dt> +<dd><p> + Enable DNSSEC validation in named. + Note <span><strong class="command">dnssec-enable</strong></span> also needs to be + set to <strong class="userinput"><code>yes</code></strong> to be effective. + The default is <strong class="userinput"><code>no</code></strong>. + </p></dd> +<dt><span class="term"><span><strong class="command">dnssec-accept-expired</strong></span></span></dt> +<dd><p> + Accept expired signatures when verifying DNSSEC signatures. + The default is <strong class="userinput"><code>no</code></strong>. + Setting this option to "yes" leaves named vulnerable to replay attacks. + </p></dd> <dt><span class="term"><span><strong class="command">querylog</strong></span></span></dt> <dd><p> -Specify whether query logging should be started when named starts. -If <span><strong class="command">querylog</strong></span> is not specified, then the query logging -is determined by the presence of the logging category <span><strong class="command">queries</strong></span>. -</p></dd> + Specify whether query logging should be started when named + starts. + If <span><strong class="command">querylog</strong></span> is not specified, + then the query logging + is determined by the presence of the logging category <span><strong class="command">queries</strong></span>. + </p></dd> <dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt> <dd> <p> -This option is used to restrict the character set and syntax of -certain domain names in master files and/or DNS responses received -from the network. The default varies according to usage area. For -<span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>. -For <span><strong class="command">slave</strong></span> zones the default is <span><strong class="command">warn</strong></span>. -For answers received from the network (<span><strong class="command">response</strong></span>) -the default is <span><strong class="command">ignore</strong></span>. -</p> -<p>The rules for legal hostnames and mail domains are derived from RFC 952 -and RFC 821 as modified by RFC 1123. -</p> -<p><span><strong class="command">check-names</strong></span> applies to the owner names of A, AAA and -MX records. It also applies to the domain names in the RDATA of NS, SOA and MX -records. It also applies to the RDATA of PTR records where the owner name -indicated that it is a reverse lookup of a hostname (the owner name ends in -IN-ADDR.ARPA, IP6.ARPA, IP6.INT). -</p> + This option is used to restrict the character set and syntax + of + certain domain names in master files and/or DNS responses + received + from the network. The default varies according to usage + area. For + <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>. + For <span><strong class="command">slave</strong></span> zones the default + is <span><strong class="command">warn</strong></span>. + For answers received from the network (<span><strong class="command">response</strong></span>) + the default is <span><strong class="command">ignore</strong></span>. + </p> +<p> + The rules for legal hostnames and mail domains are derived + from RFC 952 and RFC 821 as modified by RFC 1123. + </p> +<p><span><strong class="command">check-names</strong></span> + applies to the owner names of A, AAA and MX records. + It also applies to the domain names in the RDATA of NS, SOA + and MX records. + It also applies to the RDATA of PTR records where the owner + name indicated that it is a reverse lookup of a hostname + (the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT). + </p> </dd> +<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt> +<dd><p> + Check whether the MX record appears to refer to a IP address. + The default is to <span><strong class="command">warn</strong></span>. Other possible + values are <span><strong class="command">fail</strong></span> and + <span><strong class="command">ignore</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt> +<dd><p> + This option is used to check for non-terminal wildcards. + The use of non-terminal wildcards is almost always as a + result of a failure + to understand the wildcard matching algorithm (RFC 1034). + This option + affects master zones. The default (<span><strong class="command">yes</strong></span>) is to check + for non-terminal wildcards and issue a warning. + </p></dd> +<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt> +<dd><p> + Perform post load zone integrity checks on master + zones. This checks that MX and SRV records refer + to address (A or AAAA) records and that glue + address records exist for delegated zones. For + MX and SRV records only in-zone hostnames are + checked (for out-of-zone hostnames use named-checkzone). + For NS records only names below top of zone are + checked (for out-of-zone names and glue consistency + checks use named-checkzone). The default is + <span><strong class="command">yes</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">check-mx-cname</strong></span></span></dt> +<dd><p> + If <span><strong class="command">check-integrity</strong></span> is set then + fail, warn or ignore MX records that refer + to CNAMES. The default is to <span><strong class="command">warn</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">check-srv-cname</strong></span></span></dt> +<dd><p> + If <span><strong class="command">check-integrity</strong></span> is set then + fail, warn or ignore SRV records that refer + to CNAMES. The default is to <span><strong class="command">warn</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt> +<dd><p> + When performing integrity checks, also check that + sibling glue exists. The default is <span><strong class="command">yes</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt> +<dd><p> + When returning authoritative negative responses to + SOA queries set the TTL of the SOA recored returned in + the authority section to zero. + The default is <span><strong class="command">yes</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">zero-no-soa-ttl-cache</strong></span></span></dt> +<dd><p> + When caching a negative response to a SOA query + set the TTL to zero. + The default is <span><strong class="command">no</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt> +<dd><p> + When regenerating the RRSIGs following a UPDATE + request to a secure zone, check the KSK flag on + the DNSKEY RR to determine if this key should be + used to generate the RRSIG. This flag is ignored + if there are not DNSKEY RRs both with and without + a KSK. + The default is <span><strong class="command">yes</strong></span>. + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2581312"></a>Forwarding</h4></div></div></div> -<p>The forwarding facility can be used to create a large site-wide -cache on a few servers, reducing traffic over links to external -name servers. It can also be used to allow queries by servers that -do not have direct access to the Internet, but wish to look up exterior -names anyway. Forwarding occurs only on those queries for which -the server is not authoritative and does not have the answer in -its cache.</p> +<a name="id2580536"></a>Forwarding</h4></div></div></div> +<p> + The forwarding facility can be used to create a large site-wide + cache on a few servers, reducing traffic over links to external + name servers. It can also be used to allow queries by servers that + do not have direct access to the Internet, but wish to look up + exterior + names anyway. Forwarding occurs only on those queries for which + the server is not authoritative and does not have the answer in + its cache. + </p> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">forward</strong></span></span></dt> -<dd><p>This option is only meaningful if the -forwarders list is not empty. A value of <code class="varname">first</code>, -the default, causes the server to query the forwarders first — and -if that doesn't answer the question, the server will then look for -the answer itself. If <code class="varname">only</code> is specified, the -server will only query the forwarders. -</p></dd> +<dd><p> + This option is only meaningful if the + forwarders list is not empty. A value of <code class="varname">first</code>, + the default, causes the server to query the forwarders + first — and + if that doesn't answer the question, the server will then + look for + the answer itself. If <code class="varname">only</code> is + specified, the + server will only query the forwarders. + </p></dd> <dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt> -<dd><p>Specifies the IP addresses to be used -for forwarding. The default is the empty list (no forwarding). -</p></dd> +<dd><p> + Specifies the IP addresses to be used + for forwarding. The default is the empty list (no + forwarding). + </p></dd> </dl></div> -<p>Forwarding can also be configured on a per-domain basis, allowing -for the global forwarding options to be overridden in a variety -of ways. You can set particular domains to use different forwarders, -or have a different <span><strong class="command">forward only/first</strong></span> behavior, -or not forward at all, see <a href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone -Statement Grammar">the section called “<span><strong class="command">zone</strong></span> -Statement Grammar”</a>.</p> +<p> + Forwarding can also be configured on a per-domain basis, allowing + for the global forwarding options to be overridden in a variety + of ways. You can set particular domains to use different + forwarders, + or have a different <span><strong class="command">forward only/first</strong></span> behavior, + or not forward at all, see <a href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone + Statement Grammar">the section called “<span><strong class="command">zone</strong></span> + Statement Grammar”</a>. + </p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2581362"></a>Dual-stack Servers</h4></div></div></div> -<p>Dual-stack servers are used as servers of last resort to work around -problems in reachability due the lack of support for either IPv4 or IPv6 -on the host machine.</p> +<a name="id2580595"></a>Dual-stack Servers</h4></div></div></div> +<p> + Dual-stack servers are used as servers of last resort to work + around + problems in reachability due the lack of support for either IPv4 + or IPv6 + on the host machine. + </p> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">dual-stack-servers</strong></span></span></dt> -<dd><p>Specifies host names or addresses of machines with access to -both IPv4 and IPv6 transports. If a hostname is used, the server must be able -to resolve the name using only the transport it has. If the machine is dual -stacked, then the <span><strong class="command">dual-stack-servers</strong></span> have no effect unless -access to a transport has been disabled on the command line -(e.g. <span><strong class="command">named -4</strong></span>).</p></dd> +<dd><p> + Specifies host names or addresses of machines with access to + both IPv4 and IPv6 transports. If a hostname is used, the + server must be able + to resolve the name using only the transport it has. If the + machine is dual + stacked, then the <span><strong class="command">dual-stack-servers</strong></span> have no effect unless + access to a transport has been disabled on the command line + (e.g. <span><strong class="command">named -4</strong></span>). + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="access_control"></a>Access Control</h4></div></div></div> -<p>Access to the server can be restricted based on the IP address -of the requesting system. See <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called “Address Match Lists”</a> for -details on how to specify IP address lists.</p> +<p> + Access to the server can be restricted based on the IP address + of the requesting system. See <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called “Address Match Lists”</a> for + details on how to specify IP address lists. + </p> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt> -<dd><p>Specifies which hosts are allowed to -notify this server, a slave, of zone changes in addition -to the zone masters. -<span><strong class="command">allow-notify</strong></span> may also be specified in the -<span><strong class="command">zone</strong></span> statement, in which case it overrides the -<span><strong class="command">options allow-notify</strong></span> statement. It is only meaningful -for a slave zone. If not specified, the default is to process notify messages -only from a zone's master.</p></dd> +<dd><p> + Specifies which hosts are allowed to + notify this server, a slave, of zone changes in addition + to the zone masters. + <span><strong class="command">allow-notify</strong></span> may also be + specified in the + <span><strong class="command">zone</strong></span> statement, in which case + it overrides the + <span><strong class="command">options allow-notify</strong></span> + statement. It is only meaningful + for a slave zone. If not specified, the default is to + process notify messages + only from a zone's master. + </p></dd> <dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt> -<dd><p>Specifies which hosts are allowed to -ask ordinary DNS questions. <span><strong class="command">allow-query</strong></span> may also -be specified in the <span><strong class="command">zone</strong></span> statement, in which -case it overrides the <span><strong class="command">options allow-query</strong></span> statement. If -not specified, the default is to allow queries from all hosts.</p></dd> +<dd> +<p> + Specifies which hosts are allowed to ask ordinary + DNS questions. <span><strong class="command">allow-query</strong></span> may + also be specified in the <span><strong class="command">zone</strong></span> + statement, in which case it overrides the + <span><strong class="command">options allow-query</strong></span> statement. + If not specified, the default is to allow queries + from all hosts. + </p> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<h3 class="title">Note</h3> +<p> + <span><strong class="command">allow-query-cache</strong></span> is now + used to specify access to the cache. + </p> +</div> +</dd> +<dt><span class="term"><span><strong class="command">allow-query-cache</strong></span></span></dt> +<dd><p> + Specifies which hosts are allowed to get answers + from the cache. If <span><strong class="command">allow-query-cache</strong></span> + is not set then <span><strong class="command">allow-recursion</strong></span> + is used if set, otherwise <span><strong class="command">allow-query</strong></span> + is used if set, otherwise the default + (<span><strong class="command">localnets;</strong></span> + <span><strong class="command">localhost;</strong></span>) is used. + </p></dd> <dt><span class="term"><span><strong class="command">allow-recursion</strong></span></span></dt> -<dd><p>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. -Note that disallowing recursive queries for a host does not prevent the -host from retrieving data that is already in the server's cache. -</p></dd> +<dd><p> + Specifies which hosts are allowed to make recursive + queries through this server. If + <span><strong class="command">allow-recursion</strong></span> is not set + then <span><strong class="command">allow-query-cache</strong></span> is + used if set, otherwise <span><strong class="command">allow-query</strong></span> + is used if set, otherwise the default + (<span><strong class="command">localnets;</strong></span> + <span><strong class="command">localhost;</strong></span>) is used. + </p></dd> +<dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt> +<dd><p> + Specifies which hosts are allowed to + submit Dynamic DNS updates for master zones. The default is + to deny + updates from all hosts. Note that allowing updates based + on the requestor's IP address is insecure; see + <a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called “Dynamic Update Security”</a> for details. + </p></dd> <dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt> <dd> -<p>Specifies which hosts are allowed to -submit Dynamic DNS updates to slave zones to be forwarded to the -master. The default is <strong class="userinput"><code>{ none; }</code></strong>, which -means that no update forwarding will be performed. To enable -update forwarding, specify -<strong class="userinput"><code>allow-update-forwarding { any; };</code></strong>. -Specifying values other than <strong class="userinput"><code>{ none; }</code></strong> or -<strong class="userinput"><code>{ any; }</code></strong> is usually counterproductive, since -the responsibility for update access control should rest with the -master server, not the slaves.</p> -<p>Note that enabling the update forwarding feature on a slave server -may expose master servers relying on insecure IP address based -access control to attacks; see <a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called “Dynamic Update Security”</a> -for more details.</p> +<p> + Specifies which hosts are allowed to + submit Dynamic DNS updates to slave zones to be forwarded to + the + master. The default is <strong class="userinput"><code>{ none; }</code></strong>, + which + means that no update forwarding will be performed. To + enable + update forwarding, specify + <strong class="userinput"><code>allow-update-forwarding { any; };</code></strong>. + Specifying values other than <strong class="userinput"><code>{ none; }</code></strong> or + <strong class="userinput"><code>{ any; }</code></strong> is usually + counterproductive, since + the responsibility for update access control should rest + with the + master server, not the slaves. + </p> +<p> + Note that enabling the update forwarding feature on a slave + server + may expose master servers relying on insecure IP address + based + access control to attacks; see <a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called “Dynamic Update Security”</a> + for more details. + </p> </dd> <dt><span class="term"><span><strong class="command">allow-v6-synthesis</strong></span></span></dt> -<dd><p>This option was introduced for the smooth transition from AAAA -to A6 and from "nibble labels" to binary labels. -However, since both A6 and binary labels were then deprecated, -this option was also deprecated. -It is now ignored with some warning messages. -</p></dd> +<dd><p> + This option was introduced for the smooth transition from + AAAA + to A6 and from "nibble labels" to binary labels. + However, since both A6 and binary labels were then + deprecated, + this option was also deprecated. + It is now ignored with some warning messages. + </p></dd> <dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt> -<dd><p>Specifies which hosts are allowed to -receive zone transfers from the server. <span><strong class="command">allow-transfer</strong></span> may -also be specified in the <span><strong class="command">zone</strong></span> statement, in which -case it overrides the <span><strong class="command">options allow-transfer</strong></span> statement. -If not specified, the default is to allow transfers to all hosts.</p></dd> +<dd><p> + Specifies which hosts are allowed to + receive zone transfers from the server. <span><strong class="command">allow-transfer</strong></span> may + also be specified in the <span><strong class="command">zone</strong></span> + statement, in which + case it overrides the <span><strong class="command">options allow-transfer</strong></span> statement. + If not specified, the default is to allow transfers to all + hosts. + </p></dd> <dt><span class="term"><span><strong class="command">blackhole</strong></span></span></dt> -<dd><p>Specifies a list of addresses that the -server will not accept queries from or use to resolve a query. Queries -from these addresses will not be responded to. The default is <strong class="userinput"><code>none</code></strong>.</p></dd> +<dd><p> + Specifies a list of addresses that the + server will not accept queries from or use to resolve a + query. Queries + from these addresses will not be responded to. The default + is <strong class="userinput"><code>none</code></strong>. + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2581677"></a>Interfaces</h4></div></div></div> -<p>The interfaces and ports that the server will answer queries -from may be specified using the <span><strong class="command">listen-on</strong></span> option. <span><strong class="command">listen-on</strong></span> takes -an optional port, and an <code class="varname">address_match_list</code>. -The server will listen on all interfaces allowed by the address -match list. If a port is not specified, port 53 will be used.</p> -<p>Multiple <span><strong class="command">listen-on</strong></span> statements are allowed. -For example,</p> +<a name="id2581153"></a>Interfaces</h4></div></div></div> +<p> + The interfaces and ports that the server will answer queries + from may be specified using the <span><strong class="command">listen-on</strong></span> option. <span><strong class="command">listen-on</strong></span> takes + an optional port, and an <code class="varname">address_match_list</code>. + The server will listen on all interfaces allowed by the address + match list. If a port is not specified, port 53 will be used. + </p> +<p> + Multiple <span><strong class="command">listen-on</strong></span> statements are + allowed. + For example, + </p> <pre class="programlisting">listen-on { 5.6.7.8; }; listen-on port 1234 { !1.2.3.4; 1.2/16; }; </pre> -<p>will enable the name server on port 53 for the IP address -5.6.7.8, and on port 1234 of an address on the machine in net -1.2 that is not 1.2.3.4.</p> -<p>If no <span><strong class="command">listen-on</strong></span> is specified, the -server will listen on port 53 on all interfaces.</p> -<p>The <span><strong class="command">listen-on-v6</strong></span> option is used to -specify the interfaces and the ports on which the server will listen -for incoming queries sent using IPv6.</p> -<p>When </p> +<p> + will enable the name server on port 53 for the IP address + 5.6.7.8, and on port 1234 of an address on the machine in net + 1.2 that is not 1.2.3.4. + </p> +<p> + If no <span><strong class="command">listen-on</strong></span> is specified, the + server will listen on port 53 on all interfaces. + </p> +<p> + The <span><strong class="command">listen-on-v6</strong></span> option is used to + specify the interfaces and the ports on which the server will + listen + for incoming queries sent using IPv6. + </p> +<p> + When </p> <pre class="programlisting">{ any; }</pre> -<p> is specified -as the <code class="varname">address_match_list</code> for the -<span><strong class="command">listen-on-v6</strong></span> option, -the server does not bind a separate socket to each IPv6 interface -address as it does for IPv4 if the operating system has enough API -support for IPv6 (specifically if it conforms to RFC 3493 and RFC 3542). -Instead, it listens on the IPv6 wildcard address. -If the system only has incomplete API support for IPv6, however, -the behavior is the same as that for IPv4.</p> -<p>A list of particular IPv6 addresses can also be specified, in which case -the server listens on a separate socket for each specified address, -regardless of whether the desired API is supported by the system.</p> -<p>Multiple <span><strong class="command">listen-on-v6</strong></span> options can be used. -For example,</p> +<p> is + specified + as the <code class="varname">address_match_list</code> for the + <span><strong class="command">listen-on-v6</strong></span> option, + the server does not bind a separate socket to each IPv6 interface + address as it does for IPv4 if the operating system has enough API + support for IPv6 (specifically if it conforms to RFC 3493 and RFC + 3542). + Instead, it listens on the IPv6 wildcard address. + If the system only has incomplete API support for IPv6, however, + the behavior is the same as that for IPv4. + </p> +<p> + A list of particular IPv6 addresses can also be specified, in + which case + the server listens on a separate socket for each specified + address, + regardless of whether the desired API is supported by the system. + </p> +<p> + Multiple <span><strong class="command">listen-on-v6</strong></span> options can + be used. + For example, + </p> <pre class="programlisting">listen-on-v6 { any; }; listen-on-v6 port 1234 { !2001:db8::/32; any; }; </pre> -<p>will enable the name server on port 53 for any IPv6 addresses -(with a single wildcard socket), -and on port 1234 of IPv6 addresses that is not in the prefix -2001:db8::/32 (with separate sockets for each matched address.)</p> -<p>To make the server not listen on any IPv6 address, use</p> +<p> + will enable the name server on port 53 for any IPv6 addresses + (with a single wildcard socket), + and on port 1234 of IPv6 addresses that is not in the prefix + 2001:db8::/32 (with separate sockets for each matched address.) + </p> +<p> + To make the server not listen on any IPv6 address, use + </p> <pre class="programlisting">listen-on-v6 { none; }; </pre> -<p>If no <span><strong class="command">listen-on-v6</strong></span> option is specified, -the server will not listen on any IPv6 address.</p> +<p> + If no <span><strong class="command">listen-on-v6</strong></span> option is + specified, + the server will not listen on any IPv6 address. + </p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2581834"></a>Query Address</h4></div></div></div> -<p>If the server doesn't know the answer to a question, it will -query other name servers. <span><strong class="command">query-source</strong></span> specifies -the address and port used for such queries. For queries sent over -IPv6, there is a separate <span><strong class="command">query-source-v6</strong></span> option. -If <span><strong class="command">address</strong></span> is <span><strong class="command">*</strong></span> (asterisk) or is omitted, -a wildcard IP address (<span><strong class="command">INADDR_ANY</strong></span>) will be used. -If <span><strong class="command">port</strong></span> is <span><strong class="command">*</strong></span> or is omitted, -a random unprivileged port will be used. The <span><strong class="command">avoid-v4-udp-ports</strong></span> -and <span><strong class="command">avoid-v6-udp-ports</strong></span> options can be used to prevent named -from selecting certain ports. The defaults are:</p> +<a name="id2581241"></a>Query Address</h4></div></div></div> +<p> + If the server doesn't know the answer to a question, it will + query other name servers. <span><strong class="command">query-source</strong></span> specifies + the address and port used for such queries. For queries sent over + IPv6, there is a separate <span><strong class="command">query-source-v6</strong></span> option. + If <span><strong class="command">address</strong></span> is <span><strong class="command">*</strong></span> (asterisk) or is omitted, + a wildcard IP address (<span><strong class="command">INADDR_ANY</strong></span>) + will be used. + If <span><strong class="command">port</strong></span> is <span><strong class="command">*</strong></span> or is omitted, + a random unprivileged port will be used. The <span><strong class="command">avoid-v4-udp-ports</strong></span> + and <span><strong class="command">avoid-v6-udp-ports</strong></span> options can be used + to prevent named + from selecting certain ports. The defaults are: + </p> <pre class="programlisting">query-source address * port *; query-source-v6 address * port *; </pre> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>The address specified in the <span><strong class="command">query-source</strong></span> option -is used for both UDP and TCP queries, but the port applies only to -UDP queries. TCP queries always use a random -unprivileged port.</p> +<p> + The address specified in the <span><strong class="command">query-source</strong></span> option + is used for both UDP and TCP queries, but the port applies only + to + UDP queries. TCP queries always use a random + unprivileged port. + </p> </div> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>See also <span><strong class="command">transfer-source</strong></span> and -<span><strong class="command">notify-source</strong></span>.</p> +<p> + Solaris 2.5.1 and earlier does not support setting the source + address for TCP sockets. + </p> </div> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p> - Solaris 2.5.1 and earlier does not support setting the source - address for TCP sockets. - </p> + See also <span><strong class="command">transfer-source</strong></span> and + <span><strong class="command">notify-source</strong></span>. + </p> </div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="zone_transfers"></a>Zone Transfers</h4></div></div></div> -<p><acronym class="acronym">BIND</acronym> has mechanisms in place to facilitate zone transfers -and set limits on the amount of load that transfers place on the -system. The following options apply to zone transfers.</p> +<p> + <acronym class="acronym">BIND</acronym> has mechanisms in place to + facilitate zone transfers + and set limits on the amount of load that transfers place on the + system. The following options apply to zone transfers. + </p> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">also-notify</strong></span></span></dt> -<dd><p>Defines a global list of IP addresses of name servers -that are also sent NOTIFY messages whenever a fresh copy of the -zone is loaded, in addition to the servers listed in the zone's NS records. -This helps to ensure that copies of the zones will -quickly converge on stealth servers. If an <span><strong class="command">also-notify</strong></span> list -is given in a <span><strong class="command">zone</strong></span> statement, it will override -the <span><strong class="command">options also-notify</strong></span> statement. When a <span><strong class="command">zone notify</strong></span> statement -is set to <span><strong class="command">no</strong></span>, the IP addresses in the global <span><strong class="command">also-notify</strong></span> list will -not be sent NOTIFY messages for that zone. The default is the empty -list (no global notification list).</p></dd> +<dd><p> + Defines a global list of IP addresses of name servers + that are also sent NOTIFY messages whenever a fresh copy of + the + zone is loaded, in addition to the servers listed in the + zone's NS records. + This helps to ensure that copies of the zones will + quickly converge on stealth servers. If an <span><strong class="command">also-notify</strong></span> list + is given in a <span><strong class="command">zone</strong></span> statement, + it will override + the <span><strong class="command">options also-notify</strong></span> + statement. When a <span><strong class="command">zone notify</strong></span> + statement + is set to <span><strong class="command">no</strong></span>, the IP + addresses in the global <span><strong class="command">also-notify</strong></span> list will + not be sent NOTIFY messages for that zone. The default is + the empty + list (no global notification list). + </p></dd> <dt><span class="term"><span><strong class="command">max-transfer-time-in</strong></span></span></dt> -<dd><p>Inbound zone transfers running longer than -this many minutes will be terminated. The default is 120 minutes -(2 hours). The maximum value is 28 days (40320 minutes).</p></dd> +<dd><p> + Inbound zone transfers running longer than + this many minutes will be terminated. The default is 120 + minutes + (2 hours). The maximum value is 28 days (40320 minutes). + </p></dd> <dt><span class="term"><span><strong class="command">max-transfer-idle-in</strong></span></span></dt> -<dd><p>Inbound zone transfers making no progress -in this many minutes will be terminated. The default is 60 minutes -(1 hour). The maximum value is 28 days (40320 minutes).</p></dd> +<dd><p> + Inbound zone transfers making no progress + in this many minutes will be terminated. The default is 60 + minutes + (1 hour). The maximum value is 28 days (40320 minutes). + </p></dd> <dt><span class="term"><span><strong class="command">max-transfer-time-out</strong></span></span></dt> -<dd><p>Outbound zone transfers running longer than -this many minutes will be terminated. The default is 120 minutes -(2 hours). The maximum value is 28 days (40320 minutes).</p></dd> +<dd><p> + Outbound zone transfers running longer than + this many minutes will be terminated. The default is 120 + minutes + (2 hours). The maximum value is 28 days (40320 minutes). + </p></dd> <dt><span class="term"><span><strong class="command">max-transfer-idle-out</strong></span></span></dt> -<dd><p>Outbound zone transfers making no progress -in this many minutes will be terminated. The default is 60 minutes (1 -hour). The maximum value is 28 days (40320 minutes).</p></dd> +<dd><p> + Outbound zone transfers making no progress + in this many minutes will be terminated. The default is 60 + minutes (1 + hour). The maximum value is 28 days (40320 minutes). + </p></dd> <dt><span class="term"><span><strong class="command">serial-query-rate</strong></span></span></dt> -<dd><p>Slave servers will periodically query master servers -to find out if zone serial numbers have changed. Each such query uses -a minute amount of the slave server's network bandwidth. To limit the -amount of bandwidth used, BIND 9 limits the rate at which queries are -sent. The value of the <span><strong class="command">serial-query-rate</strong></span> option, -an integer, is the maximum number of queries sent per second. -The default is 20. -</p></dd> +<dd><p> + Slave servers will periodically query master servers + to find out if zone serial numbers have changed. Each such + query uses + a minute amount of the slave server's network bandwidth. To + limit the + amount of bandwidth used, BIND 9 limits the rate at which + queries are + sent. The value of the <span><strong class="command">serial-query-rate</strong></span> option, + an integer, is the maximum number of queries sent per + second. + The default is 20. + </p></dd> <dt><span class="term"><span><strong class="command">serial-queries</strong></span></span></dt> -<dd><p>In BIND 8, the <span><strong class="command">serial-queries</strong></span> option -set the maximum number of concurrent serial number queries -allowed to be outstanding at any given time. -BIND 9 does not limit the number of outstanding -serial queries and ignores the <span><strong class="command">serial-queries</strong></span> option. -Instead, it limits the rate at which the queries are sent -as defined using the <span><strong class="command">serial-query-rate</strong></span> option. -</p></dd> +<dd><p> + In BIND 8, the <span><strong class="command">serial-queries</strong></span> + option + set the maximum number of concurrent serial number queries + allowed to be outstanding at any given time. + BIND 9 does not limit the number of outstanding + serial queries and ignores the <span><strong class="command">serial-queries</strong></span> option. + Instead, it limits the rate at which the queries are sent + as defined using the <span><strong class="command">serial-query-rate</strong></span> option. + </p></dd> <dt><span class="term"><span><strong class="command">transfer-format</strong></span></span></dt> <dd><p> -Zone transfers can be sent using two different formats, -<span><strong class="command">one-answer</strong></span> and <span><strong class="command">many-answers</strong></span>. -The <span><strong class="command">transfer-format</strong></span> option is used -on the master server to determine which format it sends. -<span><strong class="command">one-answer</strong></span> uses one DNS message per -resource record transferred. -<span><strong class="command">many-answers</strong></span> packs as many resource records as -possible into a message. <span><strong class="command">many-answers</strong></span> is more -efficient, but is only supported by relatively new slave servers, -such as <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym> 8.x and patched -versions of <acronym class="acronym">BIND</acronym> 4.9.5. The <span><strong class="command">many-answers</strong></span> -format is also supported by recent Microsoft Windows nameservers. The default is -<span><strong class="command">many-answers</strong></span>. <span><strong class="command">transfer-format</strong></span> -may be overridden on a per-server basis by using the -<span><strong class="command">server</strong></span> statement. -</p></dd> + Zone transfers can be sent using two different formats, + <span><strong class="command">one-answer</strong></span> and + <span><strong class="command">many-answers</strong></span>. + The <span><strong class="command">transfer-format</strong></span> option is used + on the master server to determine which format it sends. + <span><strong class="command">one-answer</strong></span> uses one DNS message per + resource record transferred. + <span><strong class="command">many-answers</strong></span> packs as many resource + records as possible into a message. + <span><strong class="command">many-answers</strong></span> is more efficient, but is + only supported by relatively new slave servers, + such as <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym> + 8.x and <acronym class="acronym">BIND</acronym> 4.9.5 onwards. + The <span><strong class="command">many-answers</strong></span> format is also supported by + recent Microsoft Windows nameservers. + The default is <span><strong class="command">many-answers</strong></span>. + <span><strong class="command">transfer-format</strong></span> may be overridden on a + per-server basis by using the <span><strong class="command">server</strong></span> + statement. + </p></dd> <dt><span class="term"><span><strong class="command">transfers-in</strong></span></span></dt> -<dd><p>The maximum number of inbound zone transfers -that can be running concurrently. The default value is <code class="literal">10</code>. -Increasing <span><strong class="command">transfers-in</strong></span> may speed up the convergence -of slave zones, but it also may increase the load on the local system.</p></dd> +<dd><p> + The maximum number of inbound zone transfers + that can be running concurrently. The default value is <code class="literal">10</code>. + Increasing <span><strong class="command">transfers-in</strong></span> may + speed up the convergence + of slave zones, but it also may increase the load on the + local system. + </p></dd> <dt><span class="term"><span><strong class="command">transfers-out</strong></span></span></dt> -<dd><p>The maximum number of outbound zone transfers -that can be running concurrently. Zone transfer requests in excess -of the limit will be refused. The default value is <code class="literal">10</code>.</p></dd> +<dd><p> + The maximum number of outbound zone transfers + that can be running concurrently. Zone transfer requests in + excess + of the limit will be refused. The default value is <code class="literal">10</code>. + </p></dd> <dt><span class="term"><span><strong class="command">transfers-per-ns</strong></span></span></dt> -<dd><p>The maximum number of inbound zone transfers -that can be concurrently transferring from a given remote name server. -The default value is <code class="literal">2</code>. Increasing <span><strong class="command">transfers-per-ns</strong></span> may -speed up the convergence of slave zones, but it also may increase -the load on the remote name server. <span><strong class="command">transfers-per-ns</strong></span> may -be overridden on a per-server basis by using the <span><strong class="command">transfers</strong></span> phrase -of the <span><strong class="command">server</strong></span> statement.</p></dd> +<dd><p> + The maximum number of inbound zone transfers + that can be concurrently transferring from a given remote + name server. + The default value is <code class="literal">2</code>. + Increasing <span><strong class="command">transfers-per-ns</strong></span> + may + speed up the convergence of slave zones, but it also may + increase + the load on the remote name server. <span><strong class="command">transfers-per-ns</strong></span> may + be overridden on a per-server basis by using the <span><strong class="command">transfers</strong></span> phrase + of the <span><strong class="command">server</strong></span> statement. + </p></dd> <dt><span class="term"><span><strong class="command">transfer-source</strong></span></span></dt> -<dd><p><span><strong class="command">transfer-source</strong></span> determines -which local address will be bound to IPv4 TCP connections used to -fetch zones transferred inbound by the server. It also determines -the source IPv4 address, and optionally the UDP port, used for the -refresh queries and forwarded dynamic updates. 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 <span><strong class="command">allow-transfer</strong></span> option for -the zone being transferred, if one is specified. This statement -sets the <span><strong class="command">transfer-source</strong></span> for all zones, but can -be overridden on a per-view or per-zone basis by including a -<span><strong class="command">transfer-source</strong></span> statement within the -<span><strong class="command">view</strong></span> or <span><strong class="command">zone</strong></span> block -in the configuration file.</p></dd> +<dd> +<p><span><strong class="command">transfer-source</strong></span> + determines which local address will be bound to IPv4 + TCP connections used to fetch zones transferred + inbound by the server. It also determines the + source IPv4 address, and optionally the UDP port, + used for the refresh queries and forwarded dynamic + updates. 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 + <span><strong class="command">allow-transfer</strong></span> option for the + zone being transferred, if one is specified. This + statement sets the + <span><strong class="command">transfer-source</strong></span> for all zones, + but can be overridden on a per-view or per-zone + basis by including a + <span><strong class="command">transfer-source</strong></span> statement within + the <span><strong class="command">view</strong></span> or + <span><strong class="command">zone</strong></span> block in the configuration + file. + </p> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<h3 class="title">Note</h3> +<p> + Solaris 2.5.1 and earlier does not support setting the + source address for TCP sockets. + </p> +</div> +</dd> <dt><span class="term"><span><strong class="command">transfer-source-v6</strong></span></span></dt> -<dd><p>The same as <span><strong class="command">transfer-source</strong></span>, -except zone transfers are performed using IPv6.</p></dd> +<dd><p> + The same as <span><strong class="command">transfer-source</strong></span>, + except zone transfers are performed using IPv6. + </p></dd> <dt><span class="term"><span><strong class="command">alt-transfer-source</strong></span></span></dt> <dd> <p> - An alternate transfer source if the one listed in - <span><strong class="command">transfer-source</strong></span> fails and - <span><strong class="command">use-alt-transfer-source</strong></span> is - set. - </p> + An alternate transfer source if the one listed in + <span><strong class="command">transfer-source</strong></span> fails and + <span><strong class="command">use-alt-transfer-source</strong></span> is + set. + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> - If you do not wish the alternate transfer source - to be used, you should set - <span><strong class="command">use-alt-transfer-source</strong></span> - appropriately and you should not depend upon - getting a answer back to the first refresh - query. - </div> + If you do not wish the alternate transfer source + to be used, you should set + <span><strong class="command">use-alt-transfer-source</strong></span> + appropriately and you should not depend upon + getting a answer back to the first refresh + query. + </div> </dd> <dt><span class="term"><span><strong class="command">alt-transfer-source-v6</strong></span></span></dt> -<dd><p>An alternate transfer source if the one listed in -<span><strong class="command">transfer-source-v6</strong></span> fails and -<span><strong class="command">use-alt-transfer-source</strong></span> is set.</p></dd> +<dd><p> + An alternate transfer source if the one listed in + <span><strong class="command">transfer-source-v6</strong></span> fails and + <span><strong class="command">use-alt-transfer-source</strong></span> is + set. + </p></dd> <dt><span class="term"><span><strong class="command">use-alt-transfer-source</strong></span></span></dt> -<dd><p>Use the alternate transfer sources or not. If views are -specified this defaults to <span><strong class="command">no</strong></span> otherwise it defaults to -<span><strong class="command">yes</strong></span> (for BIND 8 compatibility).</p></dd> +<dd><p> + Use the alternate transfer sources or not. If views are + specified this defaults to <span><strong class="command">no</strong></span> + otherwise it defaults to + <span><strong class="command">yes</strong></span> (for BIND 8 + compatibility). + </p></dd> <dt><span class="term"><span><strong class="command">notify-source</strong></span></span></dt> <dd> -<p><span><strong class="command">notify-source</strong></span> determines -which local source address, and optionally UDP port, will be used to -send NOTIFY messages. -This address must appear in the slave server's <span><strong class="command">masters</strong></span> -zone clause or in an <span><strong class="command">allow-notify</strong></span> clause. -This statement sets the <span><strong class="command">notify-source</strong></span> for all zones, -but can be overridden on a per-zone or per-view basis by including a -<span><strong class="command">notify-source</strong></span> statement within the <span><strong class="command">zone</strong></span> -or <span><strong class="command">view</strong></span> block in the configuration file.</p> +<p><span><strong class="command">notify-source</strong></span> + determines which local source address, and + optionally UDP port, will be used to send NOTIFY + messages. This address must appear in the slave + server's <span><strong class="command">masters</strong></span> zone clause or + in an <span><strong class="command">allow-notify</strong></span> clause. This + statement sets the <span><strong class="command">notify-source</strong></span> + for all zones, but can be overridden on a per-zone or + per-view basis by including a + <span><strong class="command">notify-source</strong></span> statement within + the <span><strong class="command">zone</strong></span> or + <span><strong class="command">view</strong></span> block in the configuration + file. + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p> - Solaris 2.5.1 and earlier does not support setting the - source address for TCP sockets. - </p> + Solaris 2.5.1 and earlier does not support setting the + source address for TCP sockets. + </p> </div> </dd> <dt><span class="term"><span><strong class="command">notify-source-v6</strong></span></span></dt> -<dd><p>Like <span><strong class="command">notify-source</strong></span>, -but applies to notify messages sent to IPv6 addresses.</p></dd> +<dd><p> + Like <span><strong class="command">notify-source</strong></span>, + but applies to notify messages sent to IPv6 addresses. + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2582444"></a>Bad UDP Port Lists</h4></div></div></div> -<p> -<span><strong class="command">avoid-v4-udp-ports</strong></span> and <span><strong class="command">avoid-v6-udp-ports</strong></span> -specify a list of IPv4 and IPv6 UDP ports that will not be used as system -assigned source ports for UDP sockets. These lists prevent named -from choosing as its random source port a port that is blocked by -your firewall. If a query went out with such a source port, the -answer would not get by the firewall and the name server would have -to query again. -</p> +<a name="id2581988"></a>Bad UDP Port Lists</h4></div></div></div> +<p><span><strong class="command">avoid-v4-udp-ports</strong></span> + and <span><strong class="command">avoid-v6-udp-ports</strong></span> specify a list + of IPv4 and IPv6 UDP ports that will not be used as system + assigned source ports for UDP sockets. These lists + prevent named from choosing as its random source port a + port that is blocked by your firewall. If a query went + out with such a source port, the answer would not get by + the firewall and the name server would have to query + again. + </p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2570036"></a>Operating System Resource Limits</h4></div></div></div> -<p>The server's usage of many system resources can be limited. -Scaled values are allowed when specifying resource limits. For -example, <span><strong class="command">1G</strong></span> can be used instead of -<span><strong class="command">1073741824</strong></span> to specify a limit of one -gigabyte. <span><strong class="command">unlimited</strong></span> requests unlimited use, or the -maximum available amount. <span><strong class="command">default</strong></span> uses the limit -that was in force when the server was started. See the description -of <span><strong class="command">size_spec</strong></span> in <a href="Bv9ARM.ch06.html#configuration_file_elements" title="Configuration File Elements">the section called “Configuration File Elements”</a>.</p> -<p>The following options set operating system resource limits for -the name server process. Some operating systems don't support some or -any of the limits. On such systems, a warning will be issued if the -unsupported limit is used.</p> +<a name="id2582003"></a>Operating System Resource Limits</h4></div></div></div> +<p> + The server's usage of many system resources can be limited. + Scaled values are allowed when specifying resource limits. For + example, <span><strong class="command">1G</strong></span> can be used instead of + <span><strong class="command">1073741824</strong></span> to specify a limit of + one + gigabyte. <span><strong class="command">unlimited</strong></span> requests + unlimited use, or the + maximum available amount. <span><strong class="command">default</strong></span> + uses the limit + that was in force when the server was started. See the description + of <span><strong class="command">size_spec</strong></span> in <a href="Bv9ARM.ch06.html#configuration_file_elements" title="Configuration File Elements">the section called “Configuration File Elements”</a>. + </p> +<p> + The following options set operating system resource limits for + the name server process. Some operating systems don't support + some or + any of the limits. On such systems, a warning will be issued if + the + unsupported limit is used. + </p> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">coresize</strong></span></span></dt> -<dd><p>The maximum size of a core dump. The default -is <code class="literal">default</code>.</p></dd> +<dd><p> + The maximum size of a core dump. The default + is <code class="literal">default</code>. + </p></dd> <dt><span class="term"><span><strong class="command">datasize</strong></span></span></dt> -<dd><p>The maximum amount of data memory the server -may use. The default is <code class="literal">default</code>. -This is a hard limit on server memory usage. -If the server attempts to allocate memory in excess of this -limit, the allocation will fail, which may in turn leave -the server unable to perform DNS service. Therefore, -this option is rarely useful as a way of limiting the -amount of memory used by the server, but it can be used -to raise an operating system data size limit that is -too small by default. If you wish to limit the amount -of memory used by the server, use the -<span><strong class="command">max-cache-size</strong></span> and -<span><strong class="command">recursive-clients</strong></span> -options instead. -</p></dd> +<dd><p> + The maximum amount of data memory the server + may use. The default is <code class="literal">default</code>. + This is a hard limit on server memory usage. + If the server attempts to allocate memory in excess of this + limit, the allocation will fail, which may in turn leave + the server unable to perform DNS service. Therefore, + this option is rarely useful as a way of limiting the + amount of memory used by the server, but it can be used + to raise an operating system data size limit that is + too small by default. If you wish to limit the amount + of memory used by the server, use the + <span><strong class="command">max-cache-size</strong></span> and + <span><strong class="command">recursive-clients</strong></span> + options instead. + </p></dd> <dt><span class="term"><span><strong class="command">files</strong></span></span></dt> -<dd><p>The maximum number of files the server -may have open concurrently. The default is <code class="literal">unlimited</code>. -</p></dd> +<dd><p> + The maximum number of files the server + may have open concurrently. The default is <code class="literal">unlimited</code>. + </p></dd> <dt><span class="term"><span><strong class="command">stacksize</strong></span></span></dt> -<dd><p>The maximum amount of stack memory the server -may use. The default is <code class="literal">default</code>.</p></dd> +<dd><p> + The maximum amount of stack memory the server + may use. The default is <code class="literal">default</code>. + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2570205"></a>Server Resource Limits</h4></div></div></div> -<p>The following options set limits on the server's -resource consumption that are enforced internally by the -server rather than the operating system.</p> +<a name="id2582186"></a>Server Resource Limits</h4></div></div></div> +<p> + The following options set limits on the server's + resource consumption that are enforced internally by the + server rather than the operating system. + </p> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">max-ixfr-log-size</strong></span></span></dt> -<dd><p>This option is obsolete; it is accepted -and ignored for BIND 8 compatibility. The option -<span><strong class="command">max-journal-size</strong></span> performs a similar -function in BIND 8. -</p></dd> +<dd><p> + This option is obsolete; it is accepted + and ignored for BIND 8 compatibility. The option + <span><strong class="command">max-journal-size</strong></span> performs a + similar function in BIND 9. + </p></dd> <dt><span class="term"><span><strong class="command">max-journal-size</strong></span></span></dt> -<dd><p>Sets a maximum size for each journal file -(see <a href="Bv9ARM.ch04.html#journal" title="The journal file">the section called “The journal file”</a>). When the journal file approaches -the specified size, some of the oldest transactions in the journal -will be automatically removed. The default is -<code class="literal">unlimited</code>.</p></dd> +<dd><p> + Sets a maximum size for each journal file + (see <a href="Bv9ARM.ch04.html#journal" title="The journal file">the section called “The journal file”</a>). When the journal file + approaches + the specified size, some of the oldest transactions in the + journal + will be automatically removed. The default is + <code class="literal">unlimited</code>. + </p></dd> <dt><span class="term"><span><strong class="command">host-statistics-max</strong></span></span></dt> -<dd><p>In BIND 8, specifies the maximum number of host statistics -entries to be kept. -Not implemented in BIND 9. -</p></dd> +<dd><p> + In BIND 8, specifies the maximum number of host statistics + entries to be kept. + Not implemented in BIND 9. + </p></dd> <dt><span class="term"><span><strong class="command">recursive-clients</strong></span></span></dt> -<dd><p>The maximum number of simultaneous recursive lookups -the server will perform on behalf of clients. The default is -<code class="literal">1000</code>. Because each recursing client uses a fair -bit of memory, on the order of 20 kilobytes, the value of the -<span><strong class="command">recursive-clients</strong></span> option may have to be decreased -on hosts with limited memory. -</p></dd> +<dd><p> + The maximum number of simultaneous recursive lookups + the server will perform on behalf of clients. The default + is + <code class="literal">1000</code>. Because each recursing + client uses a fair + bit of memory, on the order of 20 kilobytes, the value of + the + <span><strong class="command">recursive-clients</strong></span> option may + have to be decreased + on hosts with limited memory. + </p></dd> <dt><span class="term"><span><strong class="command">tcp-clients</strong></span></span></dt> -<dd><p>The maximum number of simultaneous client TCP -connections that the server will accept. -The default is <code class="literal">100</code>.</p></dd> +<dd><p> + The maximum number of simultaneous client TCP + connections that the server will accept. + The default is <code class="literal">100</code>. + </p></dd> <dt><span class="term"><span><strong class="command">max-cache-size</strong></span></span></dt> -<dd><p>The maximum amount of memory to use for the -server's cache, in bytes. When the amount of data in the cache -reaches this limit, the server will cause records to expire -prematurely so that the limit is not exceeded. In a server with -multiple views, the limit applies separately to the cache of each -view. The default is <code class="literal">unlimited</code>, meaning that -records are purged from the cache only when their TTLs expire. -</p></dd> +<dd><p> + The maximum amount of memory to use for the + server's cache, in bytes. When the amount of data in the + cache + reaches this limit, the server will cause records to expire + prematurely so that the limit is not exceeded. In a server + with + multiple views, the limit applies separately to the cache of + each + view. The default is <code class="literal">unlimited</code>, meaning that + records are purged from the cache only when their TTLs + expire. + </p></dd> <dt><span class="term"><span><strong class="command">tcp-listen-queue</strong></span></span></dt> -<dd><p>The listen queue depth. The default and minimum is 3. -If the kernel supports the accept filter "dataready" this also controls how -many TCP connections that will be queued in kernel space waiting for -some data before being passed to accept. Values less than 3 will be -silently raised. -</p></dd> +<dd><p> + The listen queue depth. The default and minimum is 3. + If the kernel supports the accept filter "dataready" this + also controls how + many TCP connections that will be queued in kernel space + waiting for + some data before being passed to accept. Values less than 3 + will be + silently raised. + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2584723"></a>Periodic Task Intervals</h4></div></div></div> +<a name="id2582320"></a>Periodic Task Intervals</h4></div></div></div> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">cleaning-interval</strong></span></span></dt> -<dd><p>The server will remove expired resource records -from the cache every <span><strong class="command">cleaning-interval</strong></span> minutes. -The default is 60 minutes. The maximum value is 28 days (40320 minutes). -If set to 0, no periodic cleaning will occur.</p></dd> +<dd><p> + The server will remove expired resource records + from the cache every <span><strong class="command">cleaning-interval</strong></span> minutes. + The default is 60 minutes. The maximum value is 28 days + (40320 minutes). + If set to 0, no periodic cleaning will occur. + </p></dd> <dt><span class="term"><span><strong class="command">heartbeat-interval</strong></span></span></dt> -<dd><p>The server will perform zone maintenance tasks -for all zones marked as <span><strong class="command">dialup</strong></span> whenever this -interval expires. The default is 60 minutes. Reasonable values are up -to 1 day (1440 minutes). The maximum value is 28 days (40320 minutes). -If set to 0, no zone maintenance for these zones will occur.</p></dd> +<dd><p> + The server will perform zone maintenance tasks + for all zones marked as <span><strong class="command">dialup</strong></span> whenever this + interval expires. The default is 60 minutes. Reasonable + values are up + to 1 day (1440 minutes). The maximum value is 28 days + (40320 minutes). + If set to 0, no zone maintenance for these zones will occur. + </p></dd> <dt><span class="term"><span><strong class="command">interface-interval</strong></span></span></dt> -<dd><p>The server will scan the network interface list -every <span><strong class="command">interface-interval</strong></span> minutes. The default -is 60 minutes. The maximum value is 28 days (40320 minutes). -If set to 0, interface scanning will only occur when -the configuration file is loaded. After the scan, the server will -begin listening for queries on any newly discovered -interfaces (provided they are allowed by the -<span><strong class="command">listen-on</strong></span> configuration), and will -stop listening on interfaces that have gone away.</p></dd> +<dd><p> + The server will scan the network interface list + every <span><strong class="command">interface-interval</strong></span> + minutes. The default + is 60 minutes. The maximum value is 28 days (40320 minutes). + If set to 0, interface scanning will only occur when + the configuration file is loaded. After the scan, the + server will + begin listening for queries on any newly discovered + interfaces (provided they are allowed by the + <span><strong class="command">listen-on</strong></span> configuration), and + will + stop listening on interfaces that have gone away. + </p></dd> <dt><span class="term"><span><strong class="command">statistics-interval</strong></span></span></dt> <dd> -<p>Name server statistics will be logged -every <span><strong class="command">statistics-interval</strong></span> minutes. The default is -60. The maximum value is 28 days (40320 minutes). -If set to 0, no statistics will be logged.</p> +<p> + Name server statistics will be logged + every <span><strong class="command">statistics-interval</strong></span> + minutes. The default is + 60. The maximum value is 28 days (40320 minutes). + If set to 0, no statistics will be logged. + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>Not yet implemented in <acronym class="acronym">BIND</acronym>9.</p> +<p> + Not yet implemented in + <acronym class="acronym">BIND</acronym> 9. + </p> </div> </dd> </dl></div> @@ -2206,83 +3556,115 @@ If set to 0, no statistics will be logged.</p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="topology"></a>Topology</h4></div></div></div> -<p>All other things being equal, when the server chooses a name server -to query from a list of name servers, it prefers the one that is -topologically closest to itself. The <span><strong class="command">topology</strong></span> statement -takes an <span><strong class="command">address_match_list</strong></span> and interprets it -in a special way. Each top-level list element is assigned a distance. -Non-negated elements get a distance based on their position in the -list, where the closer the match is to the start of the list, the -shorter the distance is between it and the server. A negated match -will be assigned the maximum distance from the server. If there -is no match, the address will get a distance which is further than -any non-negated list element, and closer than any negated element. -For example,</p> +<p> + All other things being equal, when the server chooses a name + server + to query from a list of name servers, it prefers the one that is + topologically closest to itself. The <span><strong class="command">topology</strong></span> statement + takes an <span><strong class="command">address_match_list</strong></span> and + interprets it + in a special way. Each top-level list element is assigned a + distance. + Non-negated elements get a distance based on their position in the + list, where the closer the match is to the start of the list, the + shorter the distance is between it and the server. A negated match + will be assigned the maximum distance from the server. If there + is no match, the address will get a distance which is further than + any non-negated list element, and closer than any negated element. + For example, + </p> <pre class="programlisting">topology { 10/8; !1.2.3/24; { 1.2/16; 3/8; }; };</pre> -<p>will prefer servers on network 10 the most, followed by hosts -on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the -exception of hosts on network 1.2.3 (netmask 255.255.255.0), which -is preferred least of all.</p> -<p>The default topology is</p> +<p> + will prefer servers on network 10 the most, followed by hosts + on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the + exception of hosts on network 1.2.3 (netmask 255.255.255.0), which + is preferred least of all. + </p> +<p> + The default topology is + </p> <pre class="programlisting"> topology { localhost; localnets; }; </pre> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>The <span><strong class="command">topology</strong></span> option -is not implemented in <acronym class="acronym">BIND</acronym> 9. -</p> +<p> + The <span><strong class="command">topology</strong></span> option + is not implemented in <acronym class="acronym">BIND</acronym> 9. + </p> </div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="the_sortlist_statement"></a>The <span><strong class="command">sortlist</strong></span> Statement</h4></div></div></div> -<p>The response to a DNS query may consist of multiple resource -records (RRs) forming a resource records set (RRset). -The name server will normally return the -RRs within the RRset in an indeterminate order -(but see the <span><strong class="command">rrset-order</strong></span> -statement in <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called “RRset Ordering”</a>). -The client resolver code should rearrange the RRs as appropriate, -that is, using any addresses on the local net in preference to other addresses. -However, not all resolvers can do this or are correctly configured. -When a client is using a local server, the sorting can be performed -in the server, based on the client's address. This only requires -configuring the name servers, not all the clients.</p> -<p>The <span><strong class="command">sortlist</strong></span> statement (see below) takes -an <span><strong class="command">address_match_list</strong></span> and interprets it even -more specifically than the <span><strong class="command">topology</strong></span> statement -does (<a href="Bv9ARM.ch06.html#topology" title="Topology">the section called “Topology”</a>). -Each top level statement in the <span><strong class="command">sortlist</strong></span> must -itself be an explicit <span><strong class="command">address_match_list</strong></span> with -one or two elements. The first element (which may be an IP address, -an IP prefix, an ACL name or a nested <span><strong class="command">address_match_list</strong></span>) -of each top level list is checked against the source address of -the query until a match is found.</p> -<p>Once the source address of the query has been matched, if -the top level statement contains only one element, the actual primitive -element that matched the source address is used to select the address -in the response to move to the beginning of the response. If the -statement is a list of two elements, then the second element is -treated the same as the <span><strong class="command">address_match_list</strong></span> in -a <span><strong class="command">topology</strong></span> statement. Each top level element -is assigned a distance and the address in the response with the minimum -distance is moved to the beginning of the response.</p> -<p>In the following example, any queries received from any of -the addresses of the host itself will get responses preferring addresses -on any of the locally connected networks. Next most preferred are addresses -on the 192.168.1/24 network, and after that either the 192.168.2/24 -or -192.168.3/24 network with no preference shown between these two -networks. Queries received from a host on the 192.168.1/24 network -will prefer other addresses on that network to the 192.168.2/24 -and -192.168.3/24 networks. Queries received from a host on the 192.168.4/24 -or the 192.168.5/24 network will only prefer other addresses on -their directly connected networks.</p> +<p> + The response to a DNS query may consist of multiple resource + records (RRs) forming a resource records set (RRset). + The name server will normally return the + RRs within the RRset in an indeterminate order + (but see the <span><strong class="command">rrset-order</strong></span> + statement in <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called “RRset Ordering”</a>). + The client resolver code should rearrange the RRs as appropriate, + that is, using any addresses on the local net in preference to + other addresses. + However, not all resolvers can do this or are correctly + configured. + When a client is using a local server, the sorting can be performed + in the server, based on the client's address. This only requires + configuring the name servers, not all the clients. + </p> +<p> + The <span><strong class="command">sortlist</strong></span> statement (see below) + takes + an <span><strong class="command">address_match_list</strong></span> and + interprets it even + more specifically than the <span><strong class="command">topology</strong></span> + statement + does (<a href="Bv9ARM.ch06.html#topology" title="Topology">the section called “Topology”</a>). + Each top level statement in the <span><strong class="command">sortlist</strong></span> must + itself be an explicit <span><strong class="command">address_match_list</strong></span> with + one or two elements. The first element (which may be an IP + address, + an IP prefix, an ACL name or a nested <span><strong class="command">address_match_list</strong></span>) + of each top level list is checked against the source address of + the query until a match is found. + </p> +<p> + Once the source address of the query has been matched, if + the top level statement contains only one element, the actual + primitive + element that matched the source address is used to select the + address + in the response to move to the beginning of the response. If the + statement is a list of two elements, then the second element is + treated the same as the <span><strong class="command">address_match_list</strong></span> in + a <span><strong class="command">topology</strong></span> statement. Each top + level element + is assigned a distance and the address in the response with the + minimum + distance is moved to the beginning of the response. + </p> +<p> + In the following example, any queries received from any of + the addresses of the host itself will get responses preferring + addresses + on any of the locally connected networks. Next most preferred are + addresses + on the 192.168.1/24 network, and after that either the + 192.168.2/24 + or + 192.168.3/24 network with no preference shown between these two + networks. Queries received from a host on the 192.168.1/24 network + will prefer other addresses on that network to the 192.168.2/24 + and + 192.168.3/24 networks. Queries received from a host on the + 192.168.4/24 + or the 192.168.5/24 network will only prefer other addresses on + their directly connected networks. + </p> <pre class="programlisting">sortlist { { localhost; // IF the local host { localnets; // THEN first fit on the @@ -2300,13 +3682,18 @@ their directly connected networks.</p> { { 192.168.4/24; 192.168.5/24; }; // if .4 or .5, prefer that net }; };</pre> -<p>The following example will give reasonable behavior for the -local host and hosts on directly connected networks. It is similar -to the behavior of the address sort in <acronym class="acronym">BIND</acronym> 4.9.x. Responses sent -to queries from the local host will favor any of the directly connected -networks. Responses sent to queries from any other hosts on a directly -connected network will prefer addresses on that same network. Responses -to other queries will not be sorted.</p> +<p> + The following example will give reasonable behavior for the + local host and hosts on directly connected networks. It is similar + to the behavior of the address sort in <acronym class="acronym">BIND</acronym> 4.9.x. Responses sent + to queries from the local host will favor any of the directly + connected + networks. Responses sent to queries from any other hosts on a + directly + connected network will prefer addresses on that same network. + Responses + to other queries will not be sorted. + </p> <pre class="programlisting">sortlist { { localhost; localnets; }; { localnets; }; @@ -2316,21 +3703,34 @@ to other queries will not be sorted.</p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="rrset_ordering"></a>RRset Ordering</h4></div></div></div> -<p>When multiple records are returned in an answer it may be -useful to configure the order of the records placed into the response. -The <span><strong class="command">rrset-order</strong></span> statement permits configuration -of the ordering of the records in a multiple record response. -See also the <span><strong class="command">sortlist</strong></span> statement, -<a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called “The <span><strong class="command">sortlist</strong></span> Statement”</a>. -</p> -<p>An <span><strong class="command">order_spec</strong></span> is defined as follows:</p> -<pre class="programlisting">[<span class="optional"> class <em class="replaceable"><code>class_name</code></em> </span>][<span class="optional"> type <em class="replaceable"><code>type_name</code></em> </span>][<span class="optional"> name <em class="replaceable"><code>"domain_name"</code></em></span>] - order <em class="replaceable"><code>ordering</code></em> -</pre> -<p>If no class is specified, the default is <span><strong class="command">ANY</strong></span>. -If no type is specified, the default is <span><strong class="command">ANY</strong></span>. -If no name is specified, the default is "<span><strong class="command">*</strong></span>" (asterisk).</p> -<p>The legal values for <span><strong class="command">ordering</strong></span> are:</p> +<p> + When multiple records are returned in an answer it may be + useful to configure the order of the records placed into the + response. + The <span><strong class="command">rrset-order</strong></span> statement permits + configuration + of the ordering of the records in a multiple record response. + See also the <span><strong class="command">sortlist</strong></span> statement, + <a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called “The <span><strong class="command">sortlist</strong></span> Statement”</a>. + </p> +<p> + An <span><strong class="command">order_spec</strong></span> is defined as + follows: + </p> +<p> + [<span class="optional">class <em class="replaceable"><code>class_name</code></em></span>] + [<span class="optional">type <em class="replaceable"><code>type_name</code></em></span>] + [<span class="optional">name <em class="replaceable"><code>"domain_name"</code></em></span>] + order <em class="replaceable"><code>ordering</code></em> + </p> +<p> + If no class is specified, the default is <span><strong class="command">ANY</strong></span>. + If no type is specified, the default is <span><strong class="command">ANY</strong></span>. + If no name is specified, the default is "<span><strong class="command">*</strong></span>" (asterisk). + </p> +<p> + The legal values for <span><strong class="command">ordering</strong></span> are: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -2338,38 +3738,65 @@ If no name is specified, the default is "<span><strong class="command">*</strong </colgroup> <tbody> <tr> -<td><p><span><strong class="command">fixed</strong></span></p></td> -<td><p>Records are returned in the order they -are defined in the zone file.</p></td> +<td> + <p><span><strong class="command">fixed</strong></span></p> + </td> +<td> + <p> + Records are returned in the order they + are defined in the zone file. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">random</strong></span></p></td> -<td><p>Records are returned in some random order.</p></td> +<td> + <p><span><strong class="command">random</strong></span></p> + </td> +<td> + <p> + Records are returned in some random order. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">cyclic</strong></span></p></td> -<td><p>Records are returned in a round-robin -order.</p></td> +<td> + <p><span><strong class="command">cyclic</strong></span></p> + </td> +<td> + <p> + Records are returned in a round-robin + order. + </p> + </td> </tr> </tbody> </table></div> -<p>For example:</p> +<p> + For example: + </p> <pre class="programlisting">rrset-order { class IN type A name "host.example.com" order random; order cyclic; }; </pre> -<p>will cause any responses for type A records in class IN that -have "<code class="literal">host.example.com</code>" as a suffix, to always be returned -in random order. All other records are returned in cyclic order.</p> -<p>If multiple <span><strong class="command">rrset-order</strong></span> statements appear, -they are not combined — the last one applies.</p> +<p> + will cause any responses for type A records in class IN that + have "<code class="literal">host.example.com</code>" as a + suffix, to always be returned + in random order. All other records are returned in cyclic order. + </p> +<p> + If multiple <span><strong class="command">rrset-order</strong></span> statements + appear, + they are not combined — the last one applies. + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>The <span><strong class="command">rrset-order</strong></span> statement -is not yet fully implemented in <acronym class="acronym">BIND</acronym> 9. -BIND 9 currently does not support "fixed" ordering. -</p> +<p> + The <span><strong class="command">rrset-order</strong></span> statement + is not yet fully implemented in <acronym class="acronym">BIND</acronym> 9. + BIND 9 currently does not fully support "fixed" ordering. + </p> </div> </div> <div class="sect3" lang="en"> @@ -2377,143 +3804,377 @@ BIND 9 currently does not support "fixed" ordering. <a name="tuning"></a>Tuning</h4></div></div></div> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">lame-ttl</strong></span></span></dt> -<dd><p>Sets the number of seconds to cache a -lame server indication. 0 disables caching. (This is -<span class="bold"><strong>NOT</strong></span> recommended.) -The default is <code class="literal">600</code> (10 minutes) and the maximum value is -<code class="literal">1800</code> (30 minutes).</p></dd> +<dd><p> + Sets the number of seconds to cache a + lame server indication. 0 disables caching. (This is + <span class="bold"><strong>NOT</strong></span> recommended.) + The default is <code class="literal">600</code> (10 minutes) and the + maximum value is + <code class="literal">1800</code> (30 minutes). + </p></dd> <dt><span class="term"><span><strong class="command">max-ncache-ttl</strong></span></span></dt> -<dd><p>To reduce network traffic and increase performance, -the server stores negative answers. <span><strong class="command">max-ncache-ttl</strong></span> is -used to set a maximum retention time for these answers in the server -in seconds. The default -<span><strong class="command">max-ncache-ttl</strong></span> is <code class="literal">10800</code> seconds (3 hours). -<span><strong class="command">max-ncache-ttl</strong></span> cannot exceed 7 days and will -be silently truncated to 7 days if set to a greater value.</p></dd> +<dd><p> + To reduce network traffic and increase performance, + the server stores negative answers. <span><strong class="command">max-ncache-ttl</strong></span> is + used to set a maximum retention time for these answers in + the server + in seconds. The default + <span><strong class="command">max-ncache-ttl</strong></span> is <code class="literal">10800</code> seconds (3 hours). + <span><strong class="command">max-ncache-ttl</strong></span> cannot exceed + 7 days and will + be silently truncated to 7 days if set to a greater value. + </p></dd> <dt><span class="term"><span><strong class="command">max-cache-ttl</strong></span></span></dt> -<dd><p>Sets -the maximum time for which the server will cache ordinary (positive) -answers. The default is one week (7 days).</p></dd> +<dd><p> + Sets the maximum time for which the server will + cache ordinary (positive) answers. The default is + one week (7 days). + </p></dd> <dt><span class="term"><span><strong class="command">min-roots</strong></span></span></dt> <dd> -<p>The minimum number of root servers that -is required for a request for the root servers to be accepted. The default -is <strong class="userinput"><code>2</code></strong>.</p> +<p> + The minimum number of root servers that + is required for a request for the root servers to be + accepted. The default + is <strong class="userinput"><code>2</code></strong>. + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>Not implemented in <acronym class="acronym">BIND</acronym> 9.</p> +<p> + Not implemented in <acronym class="acronym">BIND</acronym> 9. + </p> </div> </dd> <dt><span class="term"><span><strong class="command">sig-validity-interval</strong></span></span></dt> -<dd><p>Specifies the number of days into the -future when DNSSEC signatures automatically generated as a result -of dynamic updates (<a href="Bv9ARM.ch04.html#dynamic_update" title="Dynamic Update">the section called “Dynamic Update”</a>) -will expire. The default is <code class="literal">30</code> days. -The maximum value is 10 years (3660 days). The signature -inception time is unconditionally set to one hour before the current time -to allow for a limited amount of clock skew.</p></dd> +<dd><p> + Specifies the number of days into the + future when DNSSEC signatures automatically generated as a + result + of dynamic updates (<a href="Bv9ARM.ch04.html#dynamic_update" title="Dynamic Update">the section called “Dynamic Update”</a>) + will expire. The default is <code class="literal">30</code> days. + The maximum value is 10 years (3660 days). The signature + inception time is unconditionally set to one hour before the + current time + to allow for a limited amount of clock skew. + </p></dd> <dt> <span class="term"><span><strong class="command">min-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">max-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">min-retry-time</strong></span>, </span><span class="term"><span><strong class="command">max-retry-time</strong></span></span> </dt> <dd> <p> -These options control the server's behavior on refreshing a zone -(querying for SOA changes) or retrying failed transfers. -Usually the SOA values for the zone are used, but these values -are set by the master, giving slave server administrators little -control over their contents. -</p> + These options control the server's behavior on refreshing a + zone + (querying for SOA changes) or retrying failed transfers. + Usually the SOA values for the zone are used, but these + values + are set by the master, giving slave server administrators + little + control over their contents. + </p> <p> -These options allow the administrator to set a minimum and maximum -refresh and retry time either per-zone, per-view, or globally. -These options are valid for slave and stub zones, -and clamp the SOA refresh and retry times to the specified values. -</p> + These options allow the administrator to set a minimum and + maximum + refresh and retry time either per-zone, per-view, or + globally. + These options are valid for slave and stub zones, + and clamp the SOA refresh and retry times to the specified + values. + </p> </dd> <dt><span class="term"><span><strong class="command">edns-udp-size</strong></span></span></dt> <dd><p> -<span><strong class="command">edns-udp-size</strong></span> sets the advertised EDNS UDP buffer -size in bytes. Valid values are 512 to 4096 bytes (values outside this range will be -silently adjusted). The default value is 4096. The usual reason for -setting edns-udp-size to a non-default value it to get UDP answers to -pass through broken firewalls that block fragmented packets and/or -block UDP packets that are greater than 512 bytes. -</p></dd> + Sets the advertised EDNS UDP buffer size in bytes. Valid + values are 512 to 4096 (values outside this range + will be silently adjusted). The default value is + 4096. The usual reason for setting edns-udp-size to + a non-default value is to get UDP answers to pass + through broken firewalls that block fragmented + packets and/or block UDP packets that are greater + than 512 bytes. + </p></dd> +<dt><span class="term"><span><strong class="command">max-udp-size</strong></span></span></dt> +<dd><p> + Sets the maximum EDNS UDP message size named will + send in bytes. Valid values are 512 to 4096 (values outside + this range will be silently adjusted). The default + value is 4096. The usual reason for setting + max-udp-size to a non-default value is to get UDP + answers to pass through broken firewalls that + block fragmented packets and/or block UDP packets + that are greater than 512 bytes. + This is independent of the advertised receive + buffer (<span><strong class="command">edns-udp-size</strong></span>). + </p></dd> +<dt><span class="term"><span><strong class="command">masterfile-format</strong></span></span></dt> +<dd><p>Specifies + the file format of zone files (see + <a href="Bv9ARM.ch06.html#zonefile_format" title="Additional File Formats">the section called “Additional File Formats”</a>). + The default value is <code class="constant">text</code>, which is the + standard textual representation. Files in other formats + than <code class="constant">text</code> are typically expected + to be generated by the <span><strong class="command">named-compilezone</strong></span> tool. + Note that when a zone file in a different format than + <code class="constant">text</code> is loaded, <span><strong class="command">named</strong></span> + may omit some of the checks which would be performed for a + file in the <code class="constant">text</code> format. In particular, + <span><strong class="command">check-names</strong></span> checks do not apply + for the <code class="constant">raw</code> format. This means + a zone file in the <code class="constant">raw</code> format + must be generated with the same check level as that + specified in the <span><strong class="command">named</strong></span> configuration + file. This statement sets the + <span><strong class="command">masterfile-format</strong></span> for all zones, + but can be overridden on a per-zone or per-view basis + by including a <span><strong class="command">masterfile-format</strong></span> + statement within the <span><strong class="command">zone</strong></span> or + <span><strong class="command">view</strong></span> block in the configuration + file. + </p></dd> +<dt> +<span class="term"><span><strong class="command">clients-per-query</strong></span>, </span><span class="term"><span><strong class="command">max-clients-per-query</strong></span></span> +</dt> +<dd> +<p>These set the + initial value (minimum) and maximum number of recursive + simultanious clients for any given query + (<qname,qtype,qclass>) that the server will accept + before dropping additional clients. named will attempt to + self tune this value and changes will be logged. The + default values are 10 and 100. + </p> +<p> + This value should reflect how many queries come in for + a given name in the time it takes to resolve that name. + If the number of queries exceed this value, named will + assume that it is dealing with a non-responsive zone + and will drop additional queries. If it gets a response + after dropping queries, it will raise the estimate. The + estimate will then be lowered in 20 minutes if it has + remained unchanged. + </p> +<p> + If <span><strong class="command">clients-per-query</strong></span> is set to zero, + then there is no limit on the number of clients per query + and no queries will be dropped. + </p> +<p> + If <span><strong class="command">max-clients-per-query</strong></span> is set to zero, + then there is no upper bound other than imposed by + <span><strong class="command">recursive-clients</strong></span>. + </p> +</dd> +<dt><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt> +<dd><p> + The delay, in seconds, between sending sets of notify + messages for a zone. The default is zero. + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="builtin"></a>Built-in server information zones</h4></div></div></div> -<p>The server provides some helpful diagnostic information -through a number of built-in zones under the -pseudo-top-level-domain <code class="literal">bind</code> in the -<span><strong class="command">CHAOS</strong></span> class. These zones are part of a -built-in view (see <a href="Bv9ARM.ch06.html#view_statement_grammar" title="view Statement Grammar">the section called “<span><strong class="command">view</strong></span> Statement Grammar”</a>) of class -<span><strong class="command">CHAOS</strong></span> which is separate from the default view of -class <span><strong class="command">IN</strong></span>; therefore, any global server options -such as <span><strong class="command">allow-query</strong></span> do not apply the these zones. -If you feel the need to disable these zones, use the options -below, or hide the built-in <span><strong class="command">CHAOS</strong></span> view by -defining an explicit view of class <span><strong class="command">CHAOS</strong></span> -that matches all clients.</p> +<p> + The server provides some helpful diagnostic information + through a number of built-in zones under the + pseudo-top-level-domain <code class="literal">bind</code> in the + <span><strong class="command">CHAOS</strong></span> class. These zones are part + of a + built-in view (see <a href="Bv9ARM.ch06.html#view_statement_grammar" title="view Statement Grammar">the section called “<span><strong class="command">view</strong></span> Statement Grammar”</a>) of + class + <span><strong class="command">CHAOS</strong></span> which is separate from the + default view of + class <span><strong class="command">IN</strong></span>; therefore, any global + server options + such as <span><strong class="command">allow-query</strong></span> do not apply + the these zones. + If you feel the need to disable these zones, use the options + below, or hide the built-in <span><strong class="command">CHAOS</strong></span> + view by + defining an explicit view of class <span><strong class="command">CHAOS</strong></span> + that matches all clients. + </p> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">version</strong></span></span></dt> -<dd><p>The version the server should report -via a query of the name <code class="literal">version.bind</code> -with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>. -The default is the real version number of this server. -Specifying <span><strong class="command">version none</strong></span> -disables processing of the queries.</p></dd> +<dd><p> + The version the server should report + via a query of the name <code class="literal">version.bind</code> + with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>. + The default is the real version number of this server. + Specifying <span><strong class="command">version none</strong></span> + disables processing of the queries. + </p></dd> <dt><span class="term"><span><strong class="command">hostname</strong></span></span></dt> -<dd><p>The hostname the server should report via a query of -the name <code class="filename">hostname.bind</code> -with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>. -This defaults to the hostname of the machine hosting the name server as -found by the gethostname() function. The primary purpose of such queries is to -identify which of a group of anycast servers is actually -answering your queries. Specifying <span><strong class="command">hostname none;</strong></span> -disables processing of the queries.</p></dd> +<dd><p> + The hostname the server should report via a query of + the name <code class="filename">hostname.bind</code> + with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>. + This defaults to the hostname of the machine hosting the + name server as + found by the gethostname() function. The primary purpose of such queries + is to + identify which of a group of anycast servers is actually + answering your queries. Specifying <span><strong class="command">hostname none;</strong></span> + disables processing of the queries. + </p></dd> <dt><span class="term"><span><strong class="command">server-id</strong></span></span></dt> -<dd><p>The ID of the server should report via a query of -the name <code class="filename">ID.SERVER</code> -with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>. -The primary purpose of such queries is to -identify which of a group of anycast servers is actually -answering your queries. Specifying <span><strong class="command">server-id none;</strong></span> -disables processing of the queries. -Specifying <span><strong class="command">server-id hostname;</strong></span> will cause named to -use the hostname as found by the gethostname() function. -The default <span><strong class="command">server-id</strong></span> is <span><strong class="command">none</strong></span>. -</p></dd> +<dd><p> + The ID of the server should report via a query of + the name <code class="filename">ID.SERVER</code> + with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>. + The primary purpose of such queries is to + identify which of a group of anycast servers is actually + answering your queries. Specifying <span><strong class="command">server-id none;</strong></span> + disables processing of the queries. + Specifying <span><strong class="command">server-id hostname;</strong></span> will cause named to + use the hostname as found by the gethostname() function. + The default <span><strong class="command">server-id</strong></span> is <span><strong class="command">none</strong></span>. + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="statsfile"></a>The Statistics File</h4></div></div></div> -<p>The statistics file generated by <acronym class="acronym">BIND</acronym> 9 -is similar, but not identical, to that -generated by <acronym class="acronym">BIND</acronym> 8. -</p> -<p>The statistics dump begins with a line, like:</p> -<p> - <span><strong class="command">+++ Statistics Dump +++ (973798949)</strong></span> - </p> -<p>The numberr in parentheses is a standard -Unix-style timestamp, measured as seconds since January 1, 1970. Following -that line are a series of lines containing a counter type, the value of the -counter, optionally a zone name, and optionally a view name. -The lines without view and zone listed are global statistics for the entire server. -Lines with a zone and view name for the given view and zone (the view name is -omitted for the default view). -</p> +<a name="empty"></a>Built-in Empty Zones</h4></div></div></div> <p> -The statistics dump ends with the line where the -number is identical to the number in the beginning line; for example: -</p> + Named has some built-in empty zones (SOA and NS records only). + These are for zones that should normally be answered locally + and which queries should not be sent to the Internet's root + servers. The official servers which cover these namespaces + return NXDOMAIN responses to these queries. In particular, + these cover the reverse namespace for addresses from RFC 1918 and + RFC 3330. They also include the reverse namespace for IPv6 local + address (locally assigned), IPv6 link local addresses, the IPv6 + loopback address and the IPv6 unknown addresss. + </p> <p> -<span><strong class="command">--- Statistics Dump --- (973798949)</strong></span> + Named will attempt to determine if a built in zone already exists + or is active (covered by a forward-only forwarding declaration) + and will not not create a empty zone in that case. + </p> +<p> + The current list of empty zones is: + </p> +<div class="itemizedlist"><ul type="disc"> +<li>10.IN-ADDR.ARPA</li> +<li>127.IN-ADDR.ARPA</li> +<li>254.169.IN-ADDR.ARPA</li> +<li>16.172.IN-ADDR.ARPA</li> +<li>17.172.IN-ADDR.ARPA</li> +<li>18.172.IN-ADDR.ARPA</li> +<li>19.172.IN-ADDR.ARPA</li> +<li>20.172.IN-ADDR.ARPA</li> +<li>21.172.IN-ADDR.ARPA</li> +<li>22.172.IN-ADDR.ARPA</li> +<li>23.172.IN-ADDR.ARPA</li> +<li>24.172.IN-ADDR.ARPA</li> +<li>25.172.IN-ADDR.ARPA</li> +<li>26.172.IN-ADDR.ARPA</li> +<li>27.172.IN-ADDR.ARPA</li> +<li>28.172.IN-ADDR.ARPA</li> +<li>29.172.IN-ADDR.ARPA</li> +<li>30.172.IN-ADDR.ARPA</li> +<li>31.172.IN-ADDR.ARPA</li> +<li>168.192.IN-ADDR.ARPA</li> +<li>2.0.192.IN-ADDR.ARPA</li> +<li>0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li> +<li>1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li> +<li>D.F.IP6.ARPA</li> +<li>8.E.F.IP6.ARPA</li> +<li>9.E.F.IP6.ARPA</li> +<li>A.E.F.IP6.ARPA</li> +<li>B.E.F.IP6.ARPA</li> +</ul></div> +<p> + </p> +<p> + Empty zones are settable at the view level and only apply to + views of class IN. Disabled empty zones are only inherited + from options if there are no disabled empty zones specified + at the view level. To override the options list of disabled + zones, you can disable the root zone at the view level, for example: </p> -<p>The following statistics counters are maintained:</p> +<pre class="programlisting"> + disable-empty-zone "."; +</pre> +<p> + </p> +<p> + If you are using the address ranges covered here, you should + already have reverse zones covering the addresses you use. + In practice this appears to not be the case with many queries + being made to the infrastructure servers for names in these + spaces. So many in fact that sacrificial servers were needed + to be deployed to channel the query load away from the + infrastructure servers. + </p> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<h3 class="title">Note</h3> + The real parent servers for these zones should disable all + empty zone under the parent zone they serve. For the real + root servers, this is all built in empty zones. This will + enable them to return referrals to deeper in the tree. + </div> +<div class="variablelist"><dl> +<dt><span class="term"><span><strong class="command">empty-server</strong></span></span></dt> +<dd><p> + Specify what server name will appear in the returned + SOA record for empty zones. If none is specified, then + the zone's name will be used. + </p></dd> +<dt><span class="term"><span><strong class="command">empty-contact</strong></span></span></dt> +<dd><p> + Specify what contact name will appear in the returned + SOA record for empty zones. If none is specified, then + "." will be used. + </p></dd> +<dt><span class="term"><span><strong class="command">empty-zones-enable</strong></span></span></dt> +<dd><p> + Enable or disable all empty zones. By default they + are enabled. + </p></dd> +<dt><span class="term"><span><strong class="command">disable-empty-zone</strong></span></span></dt> +<dd><p> + Disable individual empty zones. By default none are + disabled. This option can be specified multiple times. + </p></dd> +</dl></div> +</div> +<div class="sect3" lang="en"> +<div class="titlepage"><div><div><h4 class="title"> +<a name="statsfile"></a>The Statistics File</h4></div></div></div> +<p> + The statistics file generated by <acronym class="acronym">BIND</acronym> 9 + is similar, but not identical, to that + generated by <acronym class="acronym">BIND</acronym> 8. + </p> +<p> + The statistics dump begins with a line, like: + </p> +<p> + <span><strong class="command">+++ Statistics Dump +++ (973798949)</strong></span> + </p> +<p> + The number in parentheses is a standard + Unix-style timestamp, measured as seconds since January 1, 1970. + Following + that line are a series of lines containing a counter type, the + value of the + counter, optionally a zone name, and optionally a view name. + The lines without view and zone listed are global statistics for + the entire server. + Lines with a zone and view name for the given view and zone (the + view name is + omitted for the default view). + </p> +<p> + The statistics dump ends with the line where the + number is identical to the number in the beginning line; for example: + </p> +<p> + <span><strong class="command">--- Statistics Dump --- (973798949)</strong></span> + </p> +<p> + The following statistics counters are maintained: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -2521,148 +4182,404 @@ number is identical to the number in the beginning line; for example: </colgroup> <tbody> <tr> -<td><p><span><strong class="command">success</strong></span></p></td> -<td><p>The number of -successful queries made to the server or zone. A successful query -is defined as query which returns a NOERROR response with at least -one answer RR.</p></td> +<td> + <p><span><strong class="command">success</strong></span></p> + </td> +<td> + <p> + The number of + successful queries made to the server or zone. A + successful query + is defined as query which returns a NOERROR response + with at least + one answer RR. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">referral</strong></span></p></td> -<td><p>The number of queries which resulted -in referral responses.</p></td> +<td> + <p><span><strong class="command">referral</strong></span></p> + </td> +<td> + <p> + The number of queries which resulted + in referral responses. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">nxrrset</strong></span></p></td> -<td><p>The number of queries which resulted in -NOERROR responses with no data.</p></td> +<td> + <p><span><strong class="command">nxrrset</strong></span></p> + </td> +<td> + <p> + The number of queries which resulted in + NOERROR responses with no data. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">nxdomain</strong></span></p></td> -<td><p>The number -of queries which resulted in NXDOMAIN responses.</p></td> +<td> + <p><span><strong class="command">nxdomain</strong></span></p> + </td> +<td> + <p> + The number + of queries which resulted in NXDOMAIN responses. + </p> + </td> +</tr> +<tr> +<td> + <p><span><strong class="command">failure</strong></span></p> + </td> +<td> + <p> + The number of queries which resulted in a + failure response other than those above. + </p> + </td> +</tr> +<tr> +<td> + <p><span><strong class="command">recursion</strong></span></p> + </td> +<td> + <p> + The number of queries which caused the server + to perform recursion in order to find the final answer. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">failure</strong></span></p></td> -<td><p>The number of queries which resulted in a -failure response other than those above.</p></td> +<td> + <p><span><strong class="command">duplicate</strong></span></p> + </td> +<td> + <p> + The number of queries which the server attempted to + recurse but discover a existing query with the same + IP address, port, query id, name, type and class + already being processed. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">recursion</strong></span></p></td> -<td><p>The number of queries which caused the server -to perform recursion in order to find the final answer.</p></td> +<td> + <p><span><strong class="command">dropped</strong></span></p> + </td> +<td> + <p> + The number of queries for which the server + discovered a excessive number of existing + recursive queries for the same name, type and + class and were subsequently dropped. + </p> + </td> </tr> </tbody> </table></div> <p> -Each query received by the server will cause exactly one of -<span><strong class="command">success</strong></span>, -<span><strong class="command">referral</strong></span>, -<span><strong class="command">nxrrset</strong></span>, -<span><strong class="command">nxdomain</strong></span>, or -<span><strong class="command">failure</strong></span> -to be incremented, and may additionally cause the -<span><strong class="command">recursion</strong></span> counter to be incremented. -</p> + Each query received by the server will cause exactly one of + <span><strong class="command">success</strong></span>, + <span><strong class="command">referral</strong></span>, + <span><strong class="command">nxrrset</strong></span>, + <span><strong class="command">nxdomain</strong></span>, or + <span><strong class="command">failure</strong></span> + to be incremented, and may additionally cause the + <span><strong class="command">recursion</strong></span> counter to be + incremented. + </p> +</div> +<div class="sect3" lang="en"> +<div class="titlepage"><div><div><h4 class="title"> +<a name="acache"></a>Additional Section Caching</h4></div></div></div> +<p> + The additional section cache, also called <span><strong class="command">acache</strong></span>, + is an internal cache to improve the response performance of BIND 9. + When additional section caching is enabled, BIND 9 will + cache an internal short-cut to the additional section content for + each answer RR. + Note that <span><strong class="command">acache</strong></span> is an internal caching + mechanism of BIND 9, and is not related to the DNS caching + server function. + </p> +<p> + Additional section caching does not change the + response content (except the RRsets ordering of the additional + section, see below), but can improve the response performance + significantly. + It is particularly effective when BIND 9 acts as an authoritative + server for a zone that has many delegations with many glue RRs. + </p> +<p> + In order to obtain the maximum performance improvement + from additional section caching, setting + <span><strong class="command">additional-from-cache</strong></span> + to <span><strong class="command">no</strong></span> is recommended, since the current + implementation of <span><strong class="command">acache</strong></span> + does not short-cut of additional section information from the + DNS cache data. + </p> +<p> + One obvious disadvantage of <span><strong class="command">acache</strong></span> is + that it requires much more + memory for the internal cached data. + Thus, if the response performance does not matter and memory + consumption is much more critical, the + <span><strong class="command">acache</strong></span> mechanism can be + disabled by setting <span><strong class="command">acache-enable</strong></span> to + <span><strong class="command">no</strong></span>. + It is also possible to specify the upper limit of memory + consumption + for acache by using <span><strong class="command">max-acache-size</strong></span>. + </p> +<p> + Additional section caching also has a minor effect on the + RRset ordering in the additional section. + Without <span><strong class="command">acache</strong></span>, + <span><strong class="command">cyclic</strong></span> order is effective for the additional + section as well as the answer and authority sections. + However, additional section caching fixes the ordering when it + first caches an RRset for the additional section, and the same + ordering will be kept in succeeding responses, regardless of the + setting of <span><strong class="command">rrset-order</strong></span>. + The effect of this should be minor, however, since an + RRset in the additional section + typically only contains a small number of RRs (and in many cases + it only contains a single RR), in which case the + ordering does not matter much. + </p> +<p> + The following is a summary of options related to + <span><strong class="command">acache</strong></span>. + </p> +<div class="variablelist"><dl> +<dt><span class="term"><span><strong class="command">acache-enable</strong></span></span></dt> +<dd><p> + If <span><strong class="command">yes</strong></span>, additional section caching is + enabled. The default value is <span><strong class="command">no</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">acache-cleaning-interval</strong></span></span></dt> +<dd><p> + The server will remove stale cache entries, based on an LRU + based + algorithm, every <span><strong class="command">acache-cleaning-interval</strong></span> minutes. + The default is 60 minutes. + If set to 0, no periodic cleaning will occur. + </p></dd> +<dt><span class="term"><span><strong class="command">max-acache-size</strong></span></span></dt> +<dd><p> + The maximum amount of memory in bytes to use for the server's acache. + When the amount of data in the acache reaches this limit, + the server + will clean more aggressively so that the limit is not + exceeded. + In a server with multiple views, the limit applies + separately to the + acache of each view. + The default is <code class="literal">unlimited</code>, + meaning that + entries are purged from the acache only at the + periodic cleaning time. + </p></dd> +</dl></div> </div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="server_statement_grammar"></a><span><strong class="command">server</strong></span> Statement Grammar</h3></div></div></div> -<pre class="programlisting">server <em class="replaceable"><code>ip_addr</code></em> { +<pre class="programlisting">server <em class="replaceable"><code>ip_addr[/prefixlen]</code></em> { [<span class="optional"> bogus <em class="replaceable"><code>yes_or_no</code></em> ; </span>] [<span class="optional"> provide-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>] [<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>] [<span class="optional"> edns <em class="replaceable"><code>yes_or_no</code></em> ; </span>] + [<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em> ; </span>] + [<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> transfers <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> transfer-format <em class="replaceable"><code>( one-answer | many-answers )</code></em> ; ]</span>] [<span class="optional"> keys <em class="replaceable"><code>{ string ; [<span class="optional"> string ; [<span class="optional">...</span>]</span>] }</code></em> ; </span>] [<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] [<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] + [<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] + [<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] + [<span class="optional"> query-source [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]; </span>] + [<span class="optional"> query-source-v6 [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]; </span>] }; </pre> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="server_statement_definition_and_usage"></a><span><strong class="command">server</strong></span> Statement Definition and Usage</h3></div></div></div> -<p>The <span><strong class="command">server</strong></span> statement defines characteristics -to be associated with a remote name server.</p> -<p> -The <span><strong class="command">server</strong></span> statement can occur at the top level of the -configuration file or inside a <span><strong class="command">view</strong></span> statement. -If a <span><strong class="command">view</strong></span> statement contains -one or more <span><strong class="command">server</strong></span> statements, only those -apply to the view and any top-level ones are ignored. -If a view contains no <span><strong class="command">server</strong></span> statements, -any top-level <span><strong class="command">server</strong></span> statements are used as -defaults. -</p> -<p>If you discover that a remote server is giving out bad data, -marking it as bogus will prevent further queries to it. The default -value of <span><strong class="command">bogus</strong></span> is <span><strong class="command">no</strong></span>.</p> -<p>The <span><strong class="command">provide-ixfr</strong></span> clause determines whether -the local server, acting as master, will respond with an incremental -zone transfer when the given remote server, a slave, requests it. -If set to <span><strong class="command">yes</strong></span>, incremental transfer will be provided -whenever possible. If set to <span><strong class="command">no</strong></span>, all transfers -to the remote server will be non-incremental. If not set, the value -of the <span><strong class="command">provide-ixfr</strong></span> option in the view or -global options block is used as a default.</p> -<p>The <span><strong class="command">request-ixfr</strong></span> clause determines whether -the local server, acting as a slave, will request incremental zone -transfers from the given remote server, a master. If not set, the -value of the <span><strong class="command">request-ixfr</strong></span> option in the view or -global options block is used as a default.</p> -<p>IXFR requests to servers that do not support IXFR will automatically -fall back to AXFR. Therefore, there is no need to manually list -which servers support IXFR and which ones do not; the global default -of <span><strong class="command">yes</strong></span> should always work. -The purpose of the <span><strong class="command">provide-ixfr</strong></span> and -<span><strong class="command">request-ixfr</strong></span> clauses is -to make it possible to disable the use of IXFR even when both master -and slave claim to support it, for example if one of the servers -is buggy and crashes or corrupts data when IXFR is used.</p> -<p>The <span><strong class="command">edns</strong></span> clause determines whether the local server -will attempt to use EDNS when communicating with the remote server. The -default is <span><strong class="command">yes</strong></span>.</p> -<p>The server supports two zone transfer methods. The first, <span><strong class="command">one-answer</strong></span>, -uses one DNS message per resource record transferred. <span><strong class="command">many-answers</strong></span> packs -as many resource records as possible into a message. <span><strong class="command">many-answers</strong></span> is -more efficient, but is only known to be understood by <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym> -8.x, and patched versions of <acronym class="acronym">BIND</acronym> 4.9.5. You can specify which method -to use for a server with the <span><strong class="command">transfer-format</strong></span> option. -If <span><strong class="command">transfer-format</strong></span> is not specified, the <span><strong class="command">transfer-format</strong></span> specified -by the <span><strong class="command">options</strong></span> statement will be used.</p> -<p><span><strong class="command">transfers</strong></span> is used to limit the number of -concurrent inbound zone transfers from the specified server. If -no <span><strong class="command">transfers</strong></span> clause is specified, the limit is -set according to the <span><strong class="command">transfers-per-ns</strong></span> option.</p> -<p>The <span><strong class="command">keys</strong></span> clause identifies a -<span><strong class="command">key_id</strong></span> defined by the <span><strong class="command">key</strong></span> statement, -to be used for transaction security (TSIG, <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>) -when talking to the remote server. -When a request is sent to the remote server, a request signature -will be generated using the key specified here and appended to the -message. A request originating from the remote server is not required -to be signed by this key.</p> -<p>Although the grammar of the <span><strong class="command">keys</strong></span> clause -allows for multiple keys, only a single key per server is currently -supported.</p> -<p>The <span><strong class="command">transfer-source</strong></span> and -<span><strong class="command">transfer-source-v6</strong></span> clauses specify the IPv4 and IPv6 source -address to be used for zone transfer with the remote server, respectively. -For an IPv4 remote server, only <span><strong class="command">transfer-source</strong></span> can -be specified. -Similarly, for an IPv6 remote server, only -<span><strong class="command">transfer-source-v6</strong></span> can be specified. -For more details, see the description of -<span><strong class="command">transfer-source</strong></span> and -<span><strong class="command">transfer-source-v6</strong></span> in -<a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.</p> +<a name="server_statement_definition_and_usage"></a><span><strong class="command">server</strong></span> Statement Definition and + Usage</h3></div></div></div> +<p> + The <span><strong class="command">server</strong></span> statement defines + characteristics + to be associated with a remote name server. If a prefix length is + specified, then a range of servers is covered. Only the most + specific + server clause applies regardless of the order in + <code class="filename">named.conf</code>. + </p> +<p> + The <span><strong class="command">server</strong></span> statement can occur at + the top level of the + configuration file or inside a <span><strong class="command">view</strong></span> + statement. + If a <span><strong class="command">view</strong></span> statement contains + one or more <span><strong class="command">server</strong></span> statements, only + those + apply to the view and any top-level ones are ignored. + If a view contains no <span><strong class="command">server</strong></span> + statements, + any top-level <span><strong class="command">server</strong></span> statements are + used as + defaults. + </p> +<p> + If you discover that a remote server is giving out bad data, + marking it as bogus will prevent further queries to it. The + default + value of <span><strong class="command">bogus</strong></span> is <span><strong class="command">no</strong></span>. + </p> +<p> + The <span><strong class="command">provide-ixfr</strong></span> clause determines + whether + the local server, acting as master, will respond with an + incremental + zone transfer when the given remote server, a slave, requests it. + If set to <span><strong class="command">yes</strong></span>, incremental transfer + will be provided + whenever possible. If set to <span><strong class="command">no</strong></span>, + all transfers + to the remote server will be non-incremental. If not set, the + value + of the <span><strong class="command">provide-ixfr</strong></span> option in the + view or + global options block is used as a default. + </p> +<p> + The <span><strong class="command">request-ixfr</strong></span> clause determines + whether + the local server, acting as a slave, will request incremental zone + transfers from the given remote server, a master. If not set, the + value of the <span><strong class="command">request-ixfr</strong></span> option in + the view or + global options block is used as a default. + </p> +<p> + IXFR requests to servers that do not support IXFR will + automatically + fall back to AXFR. Therefore, there is no need to manually list + which servers support IXFR and which ones do not; the global + default + of <span><strong class="command">yes</strong></span> should always work. + The purpose of the <span><strong class="command">provide-ixfr</strong></span> and + <span><strong class="command">request-ixfr</strong></span> clauses is + to make it possible to disable the use of IXFR even when both + master + and slave claim to support it, for example if one of the servers + is buggy and crashes or corrupts data when IXFR is used. + </p> +<p> + The <span><strong class="command">edns</strong></span> clause determines whether + the local server will attempt to use EDNS when communicating + with the remote server. The default is <span><strong class="command">yes</strong></span>. + </p> +<p> + The <span><strong class="command">edns-udp-size</strong></span> option sets the EDNS UDP size + that is advertised by named when querying the remote server. + Valid values are 512 to 4096 bytes (values outside this range will be + silently adjusted). This option is useful when you wish to + advertises a different value to this server than the value you + advertise globally, for example, when there is a firewall at the + remote site that is blocking large replies. + </p> +<p> + The <span><strong class="command">max-udp-size</strong></span> option sets the + maximum EDNS UDP message size named will send. Valid + values are 512 to 4096 bytes (values outside this range will + be silently adjusted). This option is useful when you + know that there is a firewall that is blocking large + replies from named. + </p> +<p> + The server supports two zone transfer methods. The first, <span><strong class="command">one-answer</strong></span>, + uses one DNS message per resource record transferred. <span><strong class="command">many-answers</strong></span> packs + as many resource records as possible into a message. <span><strong class="command">many-answers</strong></span> is + more efficient, but is only known to be understood by <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym> + 8.x, and patched versions of <acronym class="acronym">BIND</acronym> + 4.9.5. You can specify which method + to use for a server with the <span><strong class="command">transfer-format</strong></span> option. + If <span><strong class="command">transfer-format</strong></span> is not + specified, the <span><strong class="command">transfer-format</strong></span> + specified + by the <span><strong class="command">options</strong></span> statement will be + used. + </p> +<p><span><strong class="command">transfers</strong></span> + is used to limit the number of concurrent inbound zone + transfers from the specified server. If no + <span><strong class="command">transfers</strong></span> clause is specified, the + limit is set according to the + <span><strong class="command">transfers-per-ns</strong></span> option. + </p> +<p> + The <span><strong class="command">keys</strong></span> clause identifies a + <span><strong class="command">key_id</strong></span> defined by the <span><strong class="command">key</strong></span> statement, + to be used for transaction security (TSIG, <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called “TSIG”</a>) + when talking to the remote server. + When a request is sent to the remote server, a request signature + will be generated using the key specified here and appended to the + message. A request originating from the remote server is not + required + to be signed by this key. + </p> +<p> + Although the grammar of the <span><strong class="command">keys</strong></span> + clause + allows for multiple keys, only a single key per server is + currently + supported. + </p> +<p> + The <span><strong class="command">transfer-source</strong></span> and + <span><strong class="command">transfer-source-v6</strong></span> clauses specify + the IPv4 and IPv6 source + address to be used for zone transfer with the remote server, + respectively. + For an IPv4 remote server, only <span><strong class="command">transfer-source</strong></span> can + be specified. + Similarly, for an IPv6 remote server, only + <span><strong class="command">transfer-source-v6</strong></span> can be + specified. + For more details, see the description of + <span><strong class="command">transfer-source</strong></span> and + <span><strong class="command">transfer-source-v6</strong></span> in + <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p> +<p> + The <span><strong class="command">notify-source</strong></span> and + <span><strong class="command">notify-source-v6</strong></span> clauses specify the + IPv4 and IPv6 source address to be used for notify + messages sent to remote servers, respectively. For an + IPv4 remote server, only <span><strong class="command">notify-source</strong></span> + can be specified. Similarly, for an IPv6 remote server, + only <span><strong class="command">notify-source-v6</strong></span> can be specified. + </p> +<p> + The <span><strong class="command">query-source</strong></span> and + <span><strong class="command">query-source-v6</strong></span> clauses specify the + IPv4 and IPv6 source address to be used for queries + sent to remote servers, respectively. For an IPv4 + remote server, only <span><strong class="command">query-source</strong></span> can + be specified. Similarly, for an IPv6 remote server, + only <span><strong class="command">query-source-v6</strong></span> can be specified. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2586290"></a><span><strong class="command">trusted-keys</strong></span> Statement Grammar</h3></div></div></div> +<a name="id2585361"></a><span><strong class="command">trusted-keys</strong></span> Statement Grammar</h3></div></div></div> <pre class="programlisting">trusted-keys { <em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; [<span class="optional"> <em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; [<span class="optional">...</span>]</span>] @@ -2671,41 +4588,41 @@ For more details, see the description of </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2586338"></a><span><strong class="command">trusted-keys</strong></span> Statement Definition - and Usage</h3></div></div></div> -<p> - The <span><strong class="command">trusted-keys</strong></span> statement defines - DNSSEC security roots. DNSSEC is described in <a href="Bv9ARM.ch04.html#DNSSEC" title="DNSSEC">the section called “DNSSEC”</a>. A security root is defined when the - public key for a non-authoritative zone is known, but - cannot be securely obtained through DNS, either because - it is the DNS root zone or because its parent zone is - unsigned. Once a key has been configured as a trusted - key, it is treated as if it had been validated and - proven secure. The resolver attempts DNSSEC validation - on all DNS data in subdomains of a security root. - </p> -<p> - All keys (and corresponding zones) listed in - <span><strong class="command">trusted-keys</strong></span> are deemed to exist regardless - of what parent zones say. Similarly for all keys listed in - <span><strong class="command">trusted-keys</strong></span> only those keys are - used to validate the DNSKEY RRset. The parent's DS RRset - will not be used. - </p> -<p> - The <span><strong class="command">trusted-keys</strong></span> statement can contain - multiple key entries, each consisting of the key's - domain name, flags, protocol, algorithm, and the Base-64 - representation of the key data. - </p> +<a name="id2585410"></a><span><strong class="command">trusted-keys</strong></span> Statement Definition + and Usage</h3></div></div></div> +<p> + The <span><strong class="command">trusted-keys</strong></span> statement defines + DNSSEC security roots. DNSSEC is described in <a href="Bv9ARM.ch04.html#DNSSEC" title="DNSSEC">the section called “DNSSEC”</a>. A security root is defined when the + public key for a non-authoritative zone is known, but + cannot be securely obtained through DNS, either because + it is the DNS root zone or because its parent zone is + unsigned. Once a key has been configured as a trusted + key, it is treated as if it had been validated and + proven secure. The resolver attempts DNSSEC validation + on all DNS data in subdomains of a security root. + </p> +<p> + All keys (and corresponding zones) listed in + <span><strong class="command">trusted-keys</strong></span> are deemed to exist regardless + of what parent zones say. Similarly for all keys listed in + <span><strong class="command">trusted-keys</strong></span> only those keys are + used to validate the DNSKEY RRset. The parent's DS RRset + will not be used. + </p> +<p> + The <span><strong class="command">trusted-keys</strong></span> statement can contain + multiple key entries, each consisting of the key's + domain name, flags, protocol, algorithm, and the Base-64 + representation of the key data. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="view_statement_grammar"></a><span><strong class="command">view</strong></span> Statement Grammar</h3></div></div></div> -<pre class="programlisting">view <em class="replaceable"><code>view_name</code></em> +<pre class="programlisting">view <em class="replaceable"><code>view_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { - match-clients { <em class="replaceable"><code>address_match_list</code></em> } ; - match-destinations { <em class="replaceable"><code>address_match_list</code></em> } ; + match-clients { <em class="replaceable"><code>address_match_list</code></em> }; + match-destinations { <em class="replaceable"><code>address_match_list</code></em> }; match-recursive-only <em class="replaceable"><code>yes_or_no</code></em> ; [<span class="optional"> <em class="replaceable"><code>view_option</code></em>; ...</span>] [<span class="optional"> <em class="replaceable"><code>zone_statement</code></em>; ...</span>] @@ -2714,53 +4631,91 @@ For more details, see the description of </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2586420"></a><span><strong class="command">view</strong></span> Statement Definition and Usage</h3></div></div></div> -<p>The <span><strong class="command">view</strong></span> statement is a powerful new feature -of <acronym class="acronym">BIND</acronym> 9 that lets a name server answer a DNS query differently -depending on who is asking. It is particularly useful for implementing -split DNS setups without having to run multiple servers.</p> -<p>Each <span><strong class="command">view</strong></span> statement defines a view of the -DNS namespace that will be seen by a subset of clients. A client matches -a view if its source IP address matches the -<code class="varname">address_match_list</code> of the view's -<span><strong class="command">match-clients</strong></span> clause and its destination IP address matches -the <code class="varname">address_match_list</code> of the view's -<span><strong class="command">match-destinations</strong></span> clause. If not specified, both -<span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span> -default to matching all addresses. In addition to checking IP addresses -<span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span> -can also take <span><strong class="command">keys</strong></span> which provide an mechanism for the -client to select the view. A view can also be specified -as <span><strong class="command">match-recursive-only</strong></span>, which means that only recursive -requests from matching clients will match that view. -The order of the <span><strong class="command">view</strong></span> statements is significant — -a client request will be resolved in the context of the first -<span><strong class="command">view</strong></span> that it matches.</p> -<p>Zones defined within a <span><strong class="command">view</strong></span> statement will -be only be accessible to clients that match the <span><strong class="command">view</strong></span>. - By defining a zone of the same name in multiple views, different -zone data can be given to different clients, for example, "internal" -and "external" clients in a split DNS setup.</p> -<p>Many of the options given in the <span><strong class="command">options</strong></span> statement -can also be used within a <span><strong class="command">view</strong></span> statement, and then -apply only when resolving queries with that view. When no view-specific -value is given, the value in the <span><strong class="command">options</strong></span> statement -is used as a default. Also, zone options can have default values specified -in the <span><strong class="command">view</strong></span> statement; these view-specific defaults -take precedence over those in the <span><strong class="command">options</strong></span> statement.</p> -<p>Views are class specific. If no class is given, class IN -is assumed. Note that all non-IN views must contain a hint zone, -since only the IN class has compiled-in default hints.</p> -<p>If there are no <span><strong class="command">view</strong></span> statements in the config -file, a default view that matches any client is automatically created -in class IN. Any <span><strong class="command">zone</strong></span> statements specified on -the top level of the configuration file are considered to be part of -this default view, and the <span><strong class="command">options</strong></span> statement will -apply to the default view. If any explicit <span><strong class="command">view</strong></span> -statements are present, all <span><strong class="command">zone</strong></span> statements must -occur inside <span><strong class="command">view</strong></span> statements.</p> -<p>Here is an example of a typical split DNS setup implemented -using <span><strong class="command">view</strong></span> statements:</p> +<a name="id2585490"></a><span><strong class="command">view</strong></span> Statement Definition and Usage</h3></div></div></div> +<p> + The <span><strong class="command">view</strong></span> statement is a powerful + feature + of <acronym class="acronym">BIND</acronym> 9 that lets a name server + answer a DNS query differently + depending on who is asking. It is particularly useful for + implementing + split DNS setups without having to run multiple servers. + </p> +<p> + Each <span><strong class="command">view</strong></span> statement defines a view + of the + DNS namespace that will be seen by a subset of clients. A client + matches + a view if its source IP address matches the + <code class="varname">address_match_list</code> of the view's + <span><strong class="command">match-clients</strong></span> clause and its + destination IP address matches + the <code class="varname">address_match_list</code> of the + view's + <span><strong class="command">match-destinations</strong></span> clause. If not + specified, both + <span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span> + default to matching all addresses. In addition to checking IP + addresses + <span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span> + can also take <span><strong class="command">keys</strong></span> which provide an + mechanism for the + client to select the view. A view can also be specified + as <span><strong class="command">match-recursive-only</strong></span>, which + means that only recursive + requests from matching clients will match that view. + The order of the <span><strong class="command">view</strong></span> statements is + significant — + a client request will be resolved in the context of the first + <span><strong class="command">view</strong></span> that it matches. + </p> +<p> + Zones defined within a <span><strong class="command">view</strong></span> + statement will + be only be accessible to clients that match the <span><strong class="command">view</strong></span>. + By defining a zone of the same name in multiple views, different + zone data can be given to different clients, for example, + "internal" + and "external" clients in a split DNS setup. + </p> +<p> + Many of the options given in the <span><strong class="command">options</strong></span> statement + can also be used within a <span><strong class="command">view</strong></span> + statement, and then + apply only when resolving queries with that view. When no + view-specific + value is given, the value in the <span><strong class="command">options</strong></span> statement + is used as a default. Also, zone options can have default values + specified + in the <span><strong class="command">view</strong></span> statement; these + view-specific defaults + take precedence over those in the <span><strong class="command">options</strong></span> statement. + </p> +<p> + Views are class specific. If no class is given, class IN + is assumed. Note that all non-IN views must contain a hint zone, + since only the IN class has compiled-in default hints. + </p> +<p> + If there are no <span><strong class="command">view</strong></span> statements in + the config + file, a default view that matches any client is automatically + created + in class IN. Any <span><strong class="command">zone</strong></span> statements + specified on + the top level of the configuration file are considered to be part + of + this default view, and the <span><strong class="command">options</strong></span> + statement will + apply to the default view. If any explicit <span><strong class="command">view</strong></span> + statements are present, all <span><strong class="command">zone</strong></span> + statements must + occur inside <span><strong class="command">view</strong></span> statements. + </p> +<p> + Here is an example of a typical split DNS setup implemented + using <span><strong class="command">view</strong></span> statements: + </p> <pre class="programlisting">view "internal" { // This should match our internal networks. match-clients { 10.0.0.0/8; }; @@ -2795,17 +4750,22 @@ view "external" { <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="zone_statement_grammar"></a><span><strong class="command">zone</strong></span> -Statement Grammar</h3></div></div></div> -<pre class="programlisting">zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { + Statement Grammar</h3></div></div></div> +<pre class="programlisting">zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { type master; - [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> } ; </span>] - [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> } ; </span>] - [<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> } ; </span>] - [<span class="optional"> update-policy { <em class="replaceable"><code>update_policy_rule</code></em> [<span class="optional">...</span>] } ; </span>] + [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> update-policy { <em class="replaceable"><code>update_policy_rule</code></em> [<span class="optional">...</span>] }; </span>] [<span class="optional"> also-notify { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] [<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>] + [<span class="optional"> check-mx (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>] + [<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>] + [<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em> ; </span>] [<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>] [<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>] + [<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>) ; </span>] + [<span class="optional"> journal <em class="replaceable"><code>string</code></em> ; </span>] [<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>] [<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] [<span class="optional"> ixfr-base <em class="replaceable"><code>string</code></em> ; </span>] @@ -2814,7 +4774,8 @@ Statement Grammar</h3></div></div></div> [<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em> ; </span>] - [<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> ; </span>] + [<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <em class="replaceable"><code>master-only</code></em> ; </span>] + [<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>] [<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>] [<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] [<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] @@ -2826,30 +4787,34 @@ Statement Grammar</h3></div></div></div> [<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> key-directory <em class="replaceable"><code>path_name</code></em>; </span>] + [<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>] }; -zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { +zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { type slave; - [<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> } ; </span>] - [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> } ; </span>] - [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> } ; </span>] - [<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> } ; </span>] + [<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> }; </span>] + [<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> also-notify { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] [<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>] [<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>] [<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>] + [<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>) ; </span>] + [<span class="optional"> journal <em class="replaceable"><code>string</code></em> ; </span>] [<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>] [<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] [<span class="optional"> ixfr-base <em class="replaceable"><code>string</code></em> ; </span>] [<span class="optional"> ixfr-tmp-file <em class="replaceable"><code>string</code></em> ; </span>] [<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em> ; </span>] - [<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] } ; </span>] + [<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>] [<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em> ; </span>] - [<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> ; </span>] + [<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <em class="replaceable"><code>master-only</code></em> ; </span>] [<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>] [<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] [<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] @@ -2865,25 +4830,27 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional" [<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> multi-master <em class="replaceable"><code>yes_or_no</code></em> ; </span>] + [<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>] }; -zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { +zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { type hint; - [<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>] + file <em class="replaceable"><code>string</code></em> ; [<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>] [<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; // Not Implemented. </span>] }; -zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { +zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { type stub; - [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> } ; </span>] + [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>] [<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>] [<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>] [<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>] [<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>] + [<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>) ; </span>] [<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>] [<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] - [<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] } ; </span>] + [<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>] [<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>] @@ -2893,7 +4860,6 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional" [<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>] [<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>] [<span class="optional"> zone-statistics <em class="replaceable"><code>yes_or_no</code></em> ; </span>] - [<span class="optional"> sig-validity-interval <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> database <em class="replaceable"><code>string</code></em> ; </span>] [<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>] [<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>] @@ -2902,24 +4868,25 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional" [<span class="optional"> multi-master <em class="replaceable"><code>yes_or_no</code></em> ; </span>] }; -zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { +zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { type forward; [<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>] [<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>] [<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>] }; -zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { +zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] { type delegation-only; }; + </pre> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2587635"></a><span><strong class="command">zone</strong></span> Statement Definition and Usage</h3></div></div></div> +<a name="id2586798"></a><span><strong class="command">zone</strong></span> Statement Definition and Usage</h3></div></div></div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2587641"></a>Zone Types</h4></div></div></div> +<a name="id2586806"></a>Zone Types</h4></div></div></div> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -2927,324 +4894,592 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional" </colgroup> <tbody> <tr> -<td><p><code class="varname">master</code></p></td> -<td><p>The server has a master copy of the data -for the zone and will be able to provide authoritative answers for -it.</p></td> -</tr> -<tr> -<td><p><code class="varname">slave</code></p></td> -<td><p>A slave zone is a replica of a master -zone. The <span><strong class="command">masters</strong></span> list specifies one or more IP addresses -of master servers that the slave contacts to update its copy of the zone. -Masters list elements can also be names of other masters lists. -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. -Authentication to the master can also be done with per-server TSIG keys. -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 startup and eliminates -a needless waste of bandwidth. Note that for large numbers (in the -tens or hundreds of thousands) of zones per server, it is best to -use a two-level naming scheme for zone file names. For example, -a slave server for the zone <code class="literal">example.com</code> might place -the zone contents into a file called -<code class="filename">ex/example.com</code> where <code class="filename">ex/</code> is -just the first two letters of the zone name. (Most operating systems -behave very slowly if you put 100 000 files into -a single directory.)</p></td> -</tr> -<tr> -<td><p><code class="varname">stub</code></p></td> -<td> -<p>A stub zone is similar to a slave zone, -except that it replicates only the NS records of a master zone instead -of the entire zone. Stub zones are not a standard part of the DNS; -they are a feature specific to the <acronym class="acronym">BIND</acronym> implementation. -</p> +<td> + <p> + <code class="varname">master</code> + </p> + </td> +<td> + <p> + The server has a master copy of the data + for the zone and will be able to provide authoritative + answers for + it. + </p> + </td> +</tr> +<tr> +<td> + <p> + <code class="varname">slave</code> + </p> + </td> +<td> + <p> + A slave zone is a replica of a master + zone. The <span><strong class="command">masters</strong></span> list + specifies one or more IP addresses + of master servers that the slave contacts to update + its copy of the zone. + Masters list elements can also be names of other + masters lists. + 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. + Authentication to the master can also be done with + per-server TSIG keys. + 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 startup and + eliminates + a needless waste of bandwidth. Note that for large + numbers (in the + tens or hundreds of thousands) of zones per server, it + is best to + use a two-level naming scheme for zone filenames. For + example, + a slave server for the zone <code class="literal">example.com</code> might place + the zone contents into a file called + <code class="filename">ex/example.com</code> where <code class="filename">ex/</code> is + just the first two letters of the zone name. (Most + operating systems + behave very slowly if you put 100 000 files into + a single directory.) + </p> + </td> +</tr> +<tr> +<td> + <p> + <code class="varname">stub</code> + </p> + </td> +<td> + <p> + A stub zone is similar to a slave zone, + except that it replicates only the NS records of a + master zone instead + of the entire zone. Stub zones are not a standard part + of the DNS; + they are a feature specific to the <acronym class="acronym">BIND</acronym> implementation. + </p> -<p>Stub zones can be used to eliminate the need for glue NS record -in a parent zone at the expense of maintaining a stub zone entry and -a set of name server addresses in <code class="filename">named.conf</code>. -This usage is not recommended for new configurations, and BIND 9 -supports it only in a limited way. -In <acronym class="acronym">BIND</acronym> 4/8, zone transfers of a parent zone -included the NS records from stub children of that zone. This meant -that, in some cases, users could get away with configuring child stubs -only in the master server for the parent zone. <acronym class="acronym">BIND</acronym> -9 never mixes together zone data from different zones in this -way. Therefore, if a <acronym class="acronym">BIND</acronym> 9 master serving a parent -zone has child stub zones configured, all the slave servers for the -parent zone also need to have the same child stub zones -configured.</p> + <p> + Stub zones can be used to eliminate the need for glue + NS record + in a parent zone at the expense of maintaining a stub + zone entry and + a set of name server addresses in <code class="filename">named.conf</code>. + This usage is not recommended for new configurations, + and BIND 9 + supports it only in a limited way. + In <acronym class="acronym">BIND</acronym> 4/8, zone + transfers of a parent zone + included the NS records from stub children of that + zone. This meant + that, in some cases, users could get away with + configuring child stubs + only in the master server for the parent zone. <acronym class="acronym">BIND</acronym> + 9 never mixes together zone data from different zones + in this + way. Therefore, if a <acronym class="acronym">BIND</acronym> 9 master serving a parent + zone has child stub zones configured, all the slave + servers for the + parent zone also need to have the same child stub + zones + configured. + </p> -<p>Stub zones can also be used as a way of forcing the resolution -of a given domain to use a particular set of authoritative servers. -For example, the caching name servers on a private network using -RFC1918 addressing may be configured with stub zones for -<code class="literal">10.in-addr.arpa</code> -to use a set of internal name servers as the authoritative -servers for that domain.</p> -</td> + <p> + Stub zones can also be used as a way of forcing the + resolution + of a given domain to use a particular set of + authoritative servers. + For example, the caching name servers on a private + network using + RFC1918 addressing may be configured with stub zones + for + <code class="literal">10.in-addr.arpa</code> + to use a set of internal name servers as the + authoritative + servers for that domain. + </p> + </td> </tr> <tr> -<td><p><code class="varname">forward</code></p></td> -<td> -<p>A "forward zone" is a way to configure -forwarding on a per-domain basis. A <span><strong class="command">zone</strong></span> statement -of type <span><strong class="command">forward</strong></span> can contain a <span><strong class="command">forward</strong></span> and/or <span><strong class="command">forwarders</strong></span> statement, -which will apply to queries within the domain given by the zone -name. If no <span><strong class="command">forwarders</strong></span> statement is present or -an empty list for <span><strong class="command">forwarders</strong></span> is given, then no -forwarding will be done for the domain, canceling the effects of -any forwarders in the <span><strong class="command">options</strong></span> statement. Thus -if you want to use this type of zone to change the behavior of the -global <span><strong class="command">forward</strong></span> option (that is, "forward first" -to, then "forward only", or vice versa, but want to use the same -servers as set globally) you need to re-specify the global forwarders.</p> -</td> +<td> + <p> + <code class="varname">forward</code> + </p> + </td> +<td> + <p> + A "forward zone" is a way to configure + forwarding on a per-domain basis. A <span><strong class="command">zone</strong></span> statement + of type <span><strong class="command">forward</strong></span> can + contain a <span><strong class="command">forward</strong></span> + and/or <span><strong class="command">forwarders</strong></span> + statement, + which will apply to queries within the domain given by + the zone + name. If no <span><strong class="command">forwarders</strong></span> + statement is present or + an empty list for <span><strong class="command">forwarders</strong></span> is given, then no + forwarding will be done for the domain, canceling the + effects of + any forwarders in the <span><strong class="command">options</strong></span> statement. Thus + if you want to use this type of zone to change the + behavior of the + global <span><strong class="command">forward</strong></span> option + (that is, "forward first" + to, then "forward only", or vice versa, but want to + use the same + servers as set globally) you need to re-specify the + global forwarders. + </p> + </td> </tr> <tr> -<td><p><code class="varname">hint</code></p></td> -<td><p>The initial set of root name servers is -specified using a "hint zone". When the server starts up, it uses -the root hints to find a root name server and get the most recent -list of root name servers. If no hint zone is specified for class -IN, the server uses a compiled-in default set of root servers hints. -Classes other than IN have no built-in defaults hints.</p></td> +<td> + <p> + <code class="varname">hint</code> + </p> + </td> +<td> + <p> + The initial set of root name servers is + specified using a "hint zone". When the server starts + up, it uses + the root hints to find a root name server and get the + most recent + list of root name servers. If no hint zone is + specified for class + IN, the server uses a compiled-in default set of root + servers hints. + Classes other than IN have no built-in defaults hints. + </p> + </td> </tr> <tr> -<td><p><code class="varname">delegation-only</code></p></td> <td> -<p>This is used to enforce the delegation-only -status of infrastructure zones (e.g. COM, NET, ORG). Any answer that -is received without an explicit or implicit delegation in the authority -section will be treated as NXDOMAIN. This does not apply to the zone -apex. This should not be applied to leaf zones.</p> -<p><code class="varname">delegation-only</code> has no effect on answers received -from forwarders.</p> -</td> + <p> + <code class="varname">delegation-only</code> + </p> + </td> +<td> + <p> + This is used to enforce the delegation-only + status of infrastructure zones (e.g. COM, NET, ORG). + Any answer that + is received without an explicit or implicit delegation + in the authority + section will be treated as NXDOMAIN. This does not + apply to the zone + apex. This should not be applied to leaf zones. + </p> + <p> + <code class="varname">delegation-only</code> has no + effect on answers received + from forwarders. + </p> + </td> </tr> </tbody> </table></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2588084"></a>Class</h4></div></div></div> -<p>The zone's name may optionally be followed by a class. If -a class is not specified, class <code class="literal">IN</code> (for <code class="varname">Internet</code>), -is assumed. This is correct for the vast majority of cases.</p> -<p>The <code class="literal">hesiod</code> class is -named for an information service from MIT's Project Athena. It is -used to share information about various systems databases, such -as users, groups, printers and so on. The keyword -<code class="literal">HS</code> is -a synonym for hesiod.</p> -<p>Another MIT development is CHAOSnet, a LAN protocol created -in the mid-1970s. Zone data for it can be specified with the <code class="literal">CHAOS</code> class.</p> +<a name="id2587362"></a>Class</h4></div></div></div> +<p> + The zone's name may optionally be followed by a class. If + a class is not specified, class <code class="literal">IN</code> (for <code class="varname">Internet</code>), + is assumed. This is correct for the vast majority of cases. + </p> +<p> + The <code class="literal">hesiod</code> class is + named for an information service from MIT's Project Athena. It + is + used to share information about various systems databases, such + as users, groups, printers and so on. The keyword + <code class="literal">HS</code> is + a synonym for hesiod. + </p> +<p> + Another MIT development is Chaosnet, a LAN protocol created + in the mid-1970s. Zone data for it can be specified with the <code class="literal">CHAOS</code> class. + </p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2588115"></a>Zone Options</h4></div></div></div> +<a name="id2587395"></a>Zone Options</h4></div></div></div> <div class="variablelist"><dl> <dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">allow-notify</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">allow-notify</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">allow-query</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">allow-query</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt> -<dd><p>See the description of <span><strong class="command">allow-transfer</strong></span> -in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.</p></dd> +<dd><p> + See the description of <span><strong class="command">allow-transfer</strong></span> + in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt> -<dd><p>Specifies which hosts are allowed to -submit Dynamic DNS updates for master zones. The default is to deny -updates from all hosts. Note that allowing updates based -on the requestor's IP address is insecure; see -<a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called “Dynamic Update Security”</a> for details. -</p></dd> +<dd><p> + See the description of <span><strong class="command">allow-update</strong></span> + in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">update-policy</strong></span></span></dt> -<dd><p>Specifies a "Simple Secure Update" policy. See -<a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>.</p></dd> +<dd><p> + Specifies a "Simple Secure Update" policy. See + <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt> -<dd><p>See the description of <span><strong class="command">allow-update-forwarding</strong></span> -in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>.</p></dd> +<dd><p> + See the description of <span><strong class="command">allow-update-forwarding</strong></span> + in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called “Access Control”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">also-notify</strong></span></span></dt> -<dd><p>Only meaningful if <span><strong class="command">notify</strong></span> is -active for this zone. The set of machines that will receive a -<code class="literal">DNS NOTIFY</code> message -for this zone is made up of all the listed name servers (other than -the primary master) for the zone plus any IP addresses specified -with <span><strong class="command">also-notify</strong></span>. A port may be specified -with each <span><strong class="command">also-notify</strong></span> address to send the notify -messages to a port other than the default of 53. -<span><strong class="command">also-notify</strong></span> is not meaningful for stub zones. -The default is the empty list.</p></dd> +<dd><p> + Only meaningful if <span><strong class="command">notify</strong></span> + is + active for this zone. The set of machines that will + receive a + <code class="literal">DNS NOTIFY</code> message + for this zone is made up of all the listed name servers + (other than + the primary master) for the zone plus any IP addresses + specified + with <span><strong class="command">also-notify</strong></span>. A port + may be specified + with each <span><strong class="command">also-notify</strong></span> + address to send the notify + messages to a port other than the default of 53. + <span><strong class="command">also-notify</strong></span> is not + meaningful for stub zones. + The default is the empty list. + </p></dd> <dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt> <dd><p> -This option is used to restrict the character set and syntax of -certain domain names in master files and/or DNS responses received from the -network. The default varies according to zone type. For <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>. For <span><strong class="command">slave</strong></span> -zones the default is <span><strong class="command">warn</strong></span>. -</p></dd> + This option is used to restrict the character set and + syntax of + certain domain names in master files and/or DNS responses + received from the + network. The default varies according to zone type. For <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>. For <span><strong class="command">slave</strong></span> + zones the default is <span><strong class="command">warn</strong></span>. + </p></dd> +<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt> +<dd><p> + See the description of + <span><strong class="command">check-mx</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> +<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt> +<dd><p> + See the description of + <span><strong class="command">check-wildcard</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> +<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt> +<dd><p> + See the description of + <span><strong class="command">check-integrity</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> +<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt> +<dd><p> + See the description of + <span><strong class="command">check-sibling</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> +<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt> +<dd><p> + See the description of + <span><strong class="command">zero-no-soa-ttl</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> +<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt> +<dd><p> + See the description of + <span><strong class="command">update-check-ksk</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">database</strong></span></span></dt> <dd> -<p>Specify the type of database to be used for storing the -zone data. The string following the <span><strong class="command">database</strong></span> keyword -is interpreted as a list of whitespace-delimited words. The first word -identifies the database type, and any subsequent words are passed -as arguments to the database to be interpreted in a way specific -to the database type.</p> -<p>The default is <strong class="userinput"><code>"rbt"</code></strong>, BIND 9's native in-memory -red-black-tree database. This database does not take arguments.</p> -<p>Other values are possible if additional database drivers -have been linked into the server. Some sample drivers are included -with the distribution but none are linked in by default.</p> +<p> + Specify the type of database to be used for storing the + zone data. The string following the <span><strong class="command">database</strong></span> keyword + is interpreted as a list of whitespace-delimited words. + The first word + identifies the database type, and any subsequent words are + passed + as arguments to the database to be interpreted in a way + specific + to the database type. + </p> +<p> + The default is <strong class="userinput"><code>"rbt"</code></strong>, BIND 9's + native in-memory + red-black-tree database. This database does not take + arguments. + </p> +<p> + Other values are possible if additional database drivers + have been linked into the server. Some sample drivers are + included + with the distribution but none are linked in by default. + </p> </dd> <dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">dialup</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">dialup</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">delegation-only</strong></span></span></dt> -<dd><p>The flag only applies to hint and stub zones. If set -to <strong class="userinput"><code>yes</code></strong>, then the zone will also be treated as if it -is also a delegation-only type zone. -</p></dd> +<dd><p> + The flag only applies to hint and stub zones. If set + to <strong class="userinput"><code>yes</code></strong>, then the zone will also be + treated as if it + is also a delegation-only type zone. + </p></dd> <dt><span class="term"><span><strong class="command">forward</strong></span></span></dt> -<dd><p>Only meaningful if the zone has a forwarders -list. The <span><strong class="command">only</strong></span> value causes the lookup to fail -after trying the forwarders and getting no answer, while <span><strong class="command">first</strong></span> would -allow a normal lookup to be tried.</p></dd> +<dd><p> + Only meaningful if the zone has a forwarders + list. The <span><strong class="command">only</strong></span> value causes + the lookup to fail + after trying the forwarders and getting no answer, while <span><strong class="command">first</strong></span> would + allow a normal lookup to be tried. + </p></dd> <dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt> -<dd><p>Used to override the list of global forwarders. -If it is not specified in a zone of type <span><strong class="command">forward</strong></span>, -no forwarding is done for the zone and the global options are not used.</p></dd> +<dd><p> + Used to override the list of global forwarders. + If it is not specified in a zone of type <span><strong class="command">forward</strong></span>, + no forwarding is done for the zone and the global options are + not used. + </p></dd> <dt><span class="term"><span><strong class="command">ixfr-base</strong></span></span></dt> -<dd><p>Was used in <acronym class="acronym">BIND</acronym> 8 to specify the name -of the transaction log (journal) file for dynamic update and IXFR. -<acronym class="acronym">BIND</acronym> 9 ignores the option and constructs the name of the journal -file by appending "<code class="filename">.jnl</code>" to the name of the -zone file.</p></dd> +<dd><p> + Was used in <acronym class="acronym">BIND</acronym> 8 to + specify the name + of the transaction log (journal) file for dynamic update + and IXFR. + <acronym class="acronym">BIND</acronym> 9 ignores the option + and constructs the name of the journal + file by appending "<code class="filename">.jnl</code>" + to the name of the + zone file. + </p></dd> <dt><span class="term"><span><strong class="command">ixfr-tmp-file</strong></span></span></dt> -<dd><p>Was an undocumented option in <acronym class="acronym">BIND</acronym> 8. -Ignored in <acronym class="acronym">BIND</acronym> 9.</p></dd> +<dd><p> + Was an undocumented option in <acronym class="acronym">BIND</acronym> 8. + Ignored in <acronym class="acronym">BIND</acronym> 9. + </p></dd> +<dt><span class="term"><span><strong class="command">journal</strong></span></span></dt> +<dd><p> + Allow the default journal's filename to be overridden. + The default is the zone's filename with "<code class="filename">.jnl</code>" appended. + This is applicable to <span><strong class="command">master</strong></span> and <span><strong class="command">slave</strong></span> zones. + </p></dd> <dt><span class="term"><span><strong class="command">max-transfer-time-in</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">max-transfer-time-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">max-transfer-time-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">max-transfer-idle-in</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">max-transfer-idle-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">max-transfer-idle-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">max-transfer-time-out</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">max-transfer-time-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">max-transfer-time-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">max-transfer-idle-out</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">max-transfer-idle-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">max-transfer-idle-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">notify</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">notify</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">notify</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> +<dt><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt> +<dd><p> + See the description of + <span><strong class="command">notify-delay</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">pubkey</strong></span></span></dt> -<dd><p>In <acronym class="acronym">BIND</acronym> 8, this option was intended for specifying -a public zone key for verification of signatures in DNSSEC signed -zones when they are loaded from disk. <acronym class="acronym">BIND</acronym> 9 does not verify signatures -on load and ignores the option.</p></dd> +<dd><p> + In <acronym class="acronym">BIND</acronym> 8, this option was + intended for specifying + a public zone key for verification of signatures in DNSSEC + signed + zones when they are loaded from disk. <acronym class="acronym">BIND</acronym> 9 does not verify signatures + on load and ignores the option. + </p></dd> <dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt> -<dd><p>If <strong class="userinput"><code>yes</code></strong>, the server will keep statistical -information for this zone, which can be dumped to the -<span><strong class="command">statistics-file</strong></span> defined in the server options.</p></dd> +<dd><p> + If <strong class="userinput"><code>yes</code></strong>, the server will keep + statistical + information for this zone, which can be dumped to the + <span><strong class="command">statistics-file</strong></span> defined in + the server options. + </p></dd> <dt><span class="term"><span><strong class="command">sig-validity-interval</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">sig-validity-interval</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">sig-validity-interval</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">transfer-source</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. -</p></dd> +<dd><p> + See the description of + <span><strong class="command">transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">transfer-source-v6</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. -</p></dd> +<dd><p> + See the description of + <span><strong class="command">transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">alt-transfer-source</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. -</p></dd> +<dd><p> + See the description of + <span><strong class="command">alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">alt-transfer-source-v6</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">alt-transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. -</p></dd> +<dd><p> + See the description of + <span><strong class="command">alt-transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">use-alt-transfer-source</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">use-alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. -</p></dd> +<dd><p> + See the description of + <span><strong class="command">use-alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">notify-source</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">notify-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a> -</p></dd> +<dd><p> + See the description of + <span><strong class="command">notify-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">notify-source-v6</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">notify-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. -</p></dd> +<dd><p> + See the description of + <span><strong class="command">notify-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. + </p></dd> <dt> <span class="term"><span><strong class="command">min-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">max-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">min-retry-time</strong></span>, </span><span class="term"><span><strong class="command">max-retry-time</strong></span></span> </dt> <dd><p> -See the description in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>. -</p></dd> + See the description in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">ixfr-from-differences</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">ixfr-from-differences</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">key-directory</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and Usage”</a>.</p></dd> +<dd><p> + See the description of + <span><strong class="command">key-directory</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and + Usage">the section called “<span><strong class="command">options</strong></span> Statement Definition and + Usage”</a>. + </p></dd> <dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt> -<dd><p>See the description of -<span><strong class="command">multi-master</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>.</p></dd> +<dd><p> + See the description of <span><strong class="command">multi-master</strong></span> in + <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a>. + </p></dd> +<dt><span class="term"><span><strong class="command">masterfile-format</strong></span></span></dt> +<dd><p> + See the description of <span><strong class="command">masterfile-format</strong></span> + in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called “Tuning”</a>. + </p></dd> </dl></div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> <a name="dynamic_update_policies"></a>Dynamic Update Policies</h4></div></div></div> -<p><acronym class="acronym">BIND</acronym> 9 supports two alternative methods of granting clients -the right to perform dynamic updates to a zone, -configured by the <span><strong class="command">allow-update</strong></span> and -<span><strong class="command">update-policy</strong></span> option, respectively.</p> -<p>The <span><strong class="command">allow-update</strong></span> clause works the same -way as in previous versions of <acronym class="acronym">BIND</acronym>. It grants given clients the -permission to update any record of any name in the zone.</p> -<p>The <span><strong class="command">update-policy</strong></span> clause is new in <acronym class="acronym">BIND</acronym> -9 and allows more fine-grained control over what updates are allowed. -A set of rules is specified, where each rule either grants or denies -permissions for one or more names to be updated by one or more identities. - If the dynamic update request message is signed (that is, it includes -either a TSIG or SIG(0) record), the identity of the signer can -be determined.</p> -<p>Rules are specified in the <span><strong class="command">update-policy</strong></span> zone -option, and are only meaningful for master zones. When the <span><strong class="command">update-policy</strong></span> statement -is present, it is a configuration error for the <span><strong class="command">allow-update</strong></span> statement -to be present. The <span><strong class="command">update-policy</strong></span> statement only -examines the signer of a message; the source address is not relevant.</p> -<p>This is how a rule definition looks:</p> +<p> + <acronym class="acronym">BIND</acronym> 9 supports two alternative + methods of granting clients + the right to perform dynamic updates to a zone, + configured by the <span><strong class="command">allow-update</strong></span> + and + <span><strong class="command">update-policy</strong></span> option, + respectively. + </p> +<p> + The <span><strong class="command">allow-update</strong></span> clause works the + same + way as in previous versions of <acronym class="acronym">BIND</acronym>. It grants given clients the + permission to update any record of any name in the zone. + </p> +<p> + The <span><strong class="command">update-policy</strong></span> clause is new + in <acronym class="acronym">BIND</acronym> + 9 and allows more fine-grained control over what updates are + allowed. + A set of rules is specified, where each rule either grants or + denies + permissions for one or more names to be updated by one or more + identities. + If the dynamic update request message is signed (that is, it + includes + either a TSIG or SIG(0) record), the identity of the signer can + be determined. + </p> +<p> + Rules are specified in the <span><strong class="command">update-policy</strong></span> zone + option, and are only meaningful for master zones. When the <span><strong class="command">update-policy</strong></span> statement + is present, it is a configuration error for the <span><strong class="command">allow-update</strong></span> statement + to be present. The <span><strong class="command">update-policy</strong></span> + statement only + examines the signer of a message; the source address is not + relevant. + </p> +<p> + This is how a rule definition looks: + </p> <pre class="programlisting"> ( <span><strong class="command">grant</strong></span> | <span><strong class="command">deny</strong></span> ) <em class="replaceable"><code>identity</code></em> <em class="replaceable"><code>nametype</code></em> <em class="replaceable"><code>name</code></em> [<span class="optional"> <em class="replaceable"><code>types</code></em> </span>] </pre> -<p>Each rule grants or denies privileges. Once a message has -successfully matched a rule, the operation is immediately granted -or denied and no further rules are examined. A rule is matched -when the signer matches the identity field, the name matches the -name field in accordance with the nametype field, and the type matches -the types specified in the type field.</p> -<p>The identity field specifies a name or a wildcard name. Normally, this -is the name of the TSIG or SIG(0) key used to sign the update request. When a -TKEY exchange has been used to create a shared secret, the identity of the -shared secret is the same as the identity of the key used to authenticate the -TKEY exchange. When the <em class="replaceable"><code>identity</code></em> field specifies a -wildcard name, it is subject to DNS wildcard expansion, so the rule will apply -to multiple identities. The <em class="replaceable"><code>identity</code></em> field must -contain a fully qualified domain name.</p> -<p>The <em class="replaceable"><code>nametype</code></em> field has 4 values: -<code class="varname">name</code>, <code class="varname">subdomain</code>, -<code class="varname">wildcard</code>, and <code class="varname">self</code>. -</p> +<p> + Each rule grants or denies privileges. Once a message has + successfully matched a rule, the operation is immediately + granted + or denied and no further rules are examined. A rule is matched + when the signer matches the identity field, the name matches the + name field in accordance with the nametype field, and the type + matches + the types specified in the type field. + </p> +<p> + The identity field specifies a name or a wildcard name. + Normally, this + is the name of the TSIG or SIG(0) key used to sign the update + request. When a + TKEY exchange has been used to create a shared secret, the + identity of the + shared secret is the same as the identity of the key used to + authenticate the + TKEY exchange. When the <em class="replaceable"><code>identity</code></em> field specifies a + wildcard name, it is subject to DNS wildcard expansion, so the + rule will apply + to multiple identities. The <em class="replaceable"><code>identity</code></em> field must + contain a fully-qualified domain name. + </p> +<p> + The <em class="replaceable"><code>nametype</code></em> field has 6 + values: + <code class="varname">name</code>, <code class="varname">subdomain</code>, + <code class="varname">wildcard</code>, <code class="varname">self</code>, + <code class="varname">selfsub</code>, and <code class="varname">selfwild</code>. + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3252,69 +5487,151 @@ contain a fully qualified domain name.</p> </colgroup> <tbody> <tr> -<td><p><code class="varname">name</code></p></td> -<td><p>Exact-match semantics. This rule matches when the -name being updated is identical to the contents of the -<em class="replaceable"><code>name</code></em> field.</p></td> +<td> + <p> + <code class="varname">name</code> + </p> + </td> +<td> + <p> + Exact-match semantics. This rule matches + when the name being updated is identical + to the contents of the + <em class="replaceable"><code>name</code></em> field. + </p> + </td> </tr> <tr> -<td><p><code class="varname">subdomain</code></p></td> -<td><p>This rule matches when the name being updated -is a subdomain of, or identical to, the contents of the -<em class="replaceable"><code>name</code></em> field.</p></td> +<td> + <p> + <code class="varname">subdomain</code> + </p> + </td> +<td> + <p> + This rule matches when the name being updated + is a subdomain of, or identical to, the + contents of the <em class="replaceable"><code>name</code></em> + field. + </p> + </td> </tr> <tr> -<td><p><code class="varname">wildcard</code></p></td> -<td><p>The <em class="replaceable"><code>name</code></em> field is -subject to DNS wildcard expansion, and this rule matches when the name -being updated name is a valid expansion of the wildcard.</p></td> +<td> + <p> + <code class="varname">wildcard</code> + </p> + </td> +<td> + <p> + The <em class="replaceable"><code>name</code></em> field + is subject to DNS wildcard expansion, and + this rule matches when the name being updated + name is a valid expansion of the wildcard. + </p> + </td> </tr> <tr> -<td><p><code class="varname">self</code></p></td> -<td><p>This rule matches when the name being updated -matches the contents of the <em class="replaceable"><code>identity</code></em> field. -The <em class="replaceable"><code>name</code></em> field is ignored, but should be -the same as the <em class="replaceable"><code>identity</code></em> field. The -<code class="varname">self</code> nametype is most useful when allowing using -one key per name to update, where the key has the same name as the name -to be updated. The <em class="replaceable"><code>identity</code></em> would be -specified as <code class="constant">*</code> in this case.</p></td> +<td> + <p> + <code class="varname">self</code> + </p> + </td> +<td> + <p> + This rule matches when the name being updated + matches the contents of the + <em class="replaceable"><code>identity</code></em> field. + The <em class="replaceable"><code>name</code></em> field + is ignored, but should be the same as the + <em class="replaceable"><code>identity</code></em> field. + The <code class="varname">self</code> nametype is + most useful when allowing using one key per + name to update, where the key has the same + name as the name to be updated. The + <em class="replaceable"><code>identity</code></em> would + be specified as <code class="constant">*</code> (an asterisk) in + this case. + </p> + </td> +</tr> +<tr> +<td> + <p> + <code class="varname">selfsub</code> + </p> + </td> +<td> + <p> + This rule is similar to <code class="varname">self</code> + except that subdomains of <code class="varname">self</code> + can also be updated. + </p> + </td> +</tr> +<tr> +<td> + <p> + <code class="varname">selfwild</code> + </p> + </td> +<td> + <p> + This rule is similar to <code class="varname">self</code> + except that only subdomains of + <code class="varname">self</code> can be updated. + </p> + </td> </tr> </tbody> </table></div> -<p>In all cases, the <em class="replaceable"><code>name</code></em> field must -specify a fully qualified domain name.</p> -<p>If no types are explicitly specified, this rule matches all types except -SIG, NS, SOA, and NXT. Types may be specified by name, including -"ANY" (ANY matches all types except NXT, which can never be updated). -Note that when an attempt is made to delete all records associated with a -name, the rules are checked for each existing record type. -</p> +<p> + In all cases, the <em class="replaceable"><code>name</code></em> + field must + specify a fully-qualified domain name. + </p> +<p> + If no types are explicitly specified, this rule matches all + types except + RRSIG, NS, SOA, and NSEC. Types may be specified by name, including + "ANY" (ANY matches all types except NSEC, which can never be + updated). + Note that when an attempt is made to delete all records + associated with a + name, the rules are checked for each existing record type. + </p> </div> </div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2589173"></a>Zone File</h2></div></div></div> +<a name="id2589080"></a>Zone File</h2></div></div></div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="types_of_resource_records_and_when_to_use_them"></a>Types of Resource Records and When to Use Them</h3></div></div></div> -<p>This section, largely borrowed from RFC 1034, describes the -concept of a Resource Record (RR) and explains when each is used. -Since the publication of RFC 1034, several new RRs have been identified -and implemented in the DNS. These are also included.</p> +<p> + This section, largely borrowed from RFC 1034, describes the + concept of a Resource Record (RR) and explains when each is used. + Since the publication of RFC 1034, several new RRs have been + identified + and implemented in the DNS. These are also included. + </p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2589191"></a>Resource Records</h4></div></div></div> -<p>A domain name identifies a node. Each node has a set of - resource information, which may be empty. The set of resource - information associated with a particular name is composed of - separate RRs. The order of RRs in a set is not significant and - need not be preserved by name servers, resolvers, or other - parts of the DNS. However, sorting of multiple RRs is - permitted for optimization purposes, for example, to specify - that a particular nearby server be tried first. See <a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called “The <span><strong class="command">sortlist</strong></span> Statement”</a> and <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called “RRset Ordering”</a>.</p> -<p>The components of a Resource Record are:</p> +<a name="id2589098"></a>Resource Records</h4></div></div></div> +<p> + A domain name identifies a node. Each node has a set of + resource information, which may be empty. The set of resource + information associated with a particular name is composed of + separate RRs. The order of RRs in a set is not significant and + need not be preserved by name servers, resolvers, or other + parts of the DNS. However, sorting of multiple RRs is + permitted for optimization purposes, for example, to specify + that a particular nearby server be tried first. See <a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called “The <span><strong class="command">sortlist</strong></span> Statement”</a> and <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called “RRset Ordering”</a>. + </p> +<p> + The components of a Resource Record are: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3322,34 +5639,78 @@ and implemented in the DNS. These are also included.</p> </colgroup> <tbody> <tr> -<td><p>owner name</p></td> -<td><p>the domain name where the RR is found.</p></td> +<td> + <p> + owner name + </p> + </td> +<td> + <p> + The domain name where the RR is found. + </p> + </td> </tr> <tr> -<td><p>type</p></td> -<td><p>an encoded 16-bit value that specifies -the type of the resource record.</p></td> +<td> + <p> + type + </p> + </td> +<td> + <p> + An encoded 16-bit value that specifies + the type of the resource record. + </p> + </td> </tr> <tr> -<td><p>TTL</p></td> -<td><p>the time-to-live of the RR. This field -is a 32-bit integer in units of seconds, and is primarily used by -resolvers when they cache RRs. The TTL describes how long a RR can -be cached before it should be discarded.</p></td> +<td> + <p> + TTL + </p> + </td> +<td> + <p> + The time-to-live of the RR. This field + is a 32-bit integer in units of seconds, and is + primarily used by + resolvers when they cache RRs. The TTL describes how + long a RR can + be cached before it should be discarded. + </p> + </td> </tr> <tr> -<td><p>class</p></td> -<td><p>an encoded 16-bit value that identifies -a protocol family or instance of a protocol.</p></td> +<td> + <p> + class + </p> + </td> +<td> + <p> + An encoded 16-bit value that identifies + a protocol family or instance of a protocol. + </p> + </td> </tr> <tr> -<td><p>RDATA</p></td> -<td><p>the resource data. The format of the -data is type (and sometimes class) specific.</p></td> +<td> + <p> + RDATA + </p> + </td> +<td> + <p> + The resource data. The format of the + data is type (and sometimes class) specific. + </p> + </td> </tr> </tbody> </table></div> -<p>The following are <span class="emphasis"><em>types</em></span> of valid RRs:</p> +<p> + The following are <span class="emphasis"><em>types</em></span> of valid RRs: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3357,160 +5718,463 @@ data is type (and sometimes class) specific.</p></td> </colgroup> <tbody> <tr> -<td><p>A</p></td> -<td><p>a host address. In the IN class, this is a -32-bit IP address. Described in RFC 1035.</p></td> +<td> + <p> + A + </p> + </td> +<td> + <p> + A host address. In the IN class, this is a + 32-bit IP address. Described in RFC 1035. + </p> + </td> </tr> <tr> -<td><p>AAAA</p></td> -<td><p>IPv6 address. Described in RFC 1886.</p></td> +<td> + <p> + AAAA + </p> + </td> +<td> + <p> + IPv6 address. Described in RFC 1886. + </p> + </td> </tr> <tr> -<td><p>A6</p></td> -<td><p>IPv6 address. This can be a partial -address (a suffix) and an indirection to the name where the rest of the -address (the prefix) can be found. Experimental. Described in RFC 2874.</p></td> +<td> + <p> + A6 + </p> + </td> +<td> + <p> + IPv6 address. This can be a partial + address (a suffix) and an indirection to the name + where the rest of the + address (the prefix) can be found. Experimental. + Described in RFC 2874. + </p> + </td> </tr> <tr> -<td><p>AFSDB</p></td> -<td><p>location of AFS database servers. -Experimental. Described in RFC 1183.</p></td> +<td> + <p> + AFSDB + </p> + </td> +<td> + <p> + Location of AFS database servers. + Experimental. Described in RFC 1183. + </p> + </td> </tr> <tr> -<td><p>APL</p></td> -<td><p>address prefix list. Experimental. -Described in RFC 3123.</p></td> +<td> + <p> + APL + </p> + </td> +<td> + <p> + Address prefix list. Experimental. + Described in RFC 3123. + </p> + </td> </tr> <tr> -<td><p>CERT</p></td> -<td><p>holds a digital certificate. -Described in RFC 2538.</p></td> +<td> + <p> + CERT + </p> + </td> +<td> + <p> + Holds a digital certificate. + Described in RFC 2538. + </p> + </td> </tr> <tr> -<td><p>CNAME</p></td> -<td><p>identifies the canonical name of an alias. -Described in RFC 1035.</p></td> +<td> + <p> + CNAME + </p> + </td> +<td> + <p> + Identifies the canonical name of an alias. + Described in RFC 1035. + </p> + </td> </tr> <tr> -<td><p>DNAME</p></td> -<td><p>Replaces the domain name specified with -another name to be looked up, effectively aliasing an entire -subtree of the domain name space rather than a single record -as in the case of the CNAME RR. -Described in RFC 2672.</p></td> +<td> + <p> + DNAME + </p> + </td> +<td> + <p> + Replaces the domain name specified with + another name to be looked up, effectively aliasing an + entire + subtree of the domain name space rather than a single + record + as in the case of the CNAME RR. + Described in RFC 2672. + </p> + </td> </tr> <tr> -<td><p>GPOS</p></td> -<td><p>Specifies the global position. Superseded by LOC.</p></td> +<td> + <p> + DNSKEY + </p> + </td> +<td> + <p> + Stores a public key associated with a signed + DNS zone. Described in RFC 4034. + </p> + </td> </tr> <tr> -<td><p>HINFO</p></td> -<td><p>identifies the CPU and OS used by a host. -Described in RFC 1035.</p></td> +<td> + <p> + DS + </p> + </td> +<td> + <p> + Stores the hash of a public key associated with a + signed DNS zone. Described in RFC 4034. + </p> + </td> </tr> <tr> -<td><p>ISDN</p></td> -<td><p>representation of ISDN addresses. -Experimental. Described in RFC 1183.</p></td> +<td> + <p> + GPOS + </p> + </td> +<td> + <p> + Specifies the global position. Superseded by LOC. + </p> + </td> </tr> <tr> -<td><p>KEY</p></td> -<td><p>stores a public key associated with a -DNS name. Described in RFC 2535.</p></td> +<td> + <p> + HINFO + </p> + </td> +<td> + <p> + Identifies the CPU and OS used by a host. + Described in RFC 1035. + </p> + </td> </tr> <tr> -<td><p>KX</p></td> -<td><p>identifies a key exchanger for this -DNS name. Described in RFC 2230.</p></td> +<td> + <p> + ISDN + </p> + </td> +<td> + <p> + Representation of ISDN addresses. + Experimental. Described in RFC 1183. + </p> + </td> </tr> <tr> -<td><p>LOC</p></td> -<td><p>for storing GPS info. Described in RFC 1876. -Experimental.</p></td> +<td> + <p> + KEY + </p> + </td> +<td> + <p> + Stores a public key associated with a + DNS name. Used in original DNSSEC; replaced + by DNSKEY in DNSSECbis, but still used with + SIG(0). Described in RFCs 2535 and 2931. + </p> + </td> </tr> <tr> -<td><p>MX</p></td> -<td><p>identifies a mail exchange for the domain. -A 16-bit preference value (lower is better) -followed by the host name of the mail exchange. -Described in RFC 974, RFC 1035.</p></td> +<td> + <p> + KX + </p> + </td> +<td> + <p> + Identifies a key exchanger for this + DNS name. Described in RFC 2230. + </p> + </td> </tr> <tr> -<td><p>NAPTR</p></td> -<td><p>name authority pointer. Described in RFC 2915.</p></td> +<td> + <p> + LOC + </p> + </td> +<td> + <p> + For storing GPS info. Described in RFC 1876. + Experimental. + </p> + </td> </tr> <tr> -<td><p>NSAP</p></td> -<td><p>a network service access point. -Described in RFC 1706.</p></td> +<td> + <p> + MX + </p> + </td> +<td> + <p> + Identifies a mail exchange for the domain with + a 16-bit preference value (lower is better) + followed by the host name of the mail exchange. + Described in RFC 974, RFC 1035. + </p> + </td> </tr> <tr> -<td><p>NS</p></td> -<td><p>the authoritative name server for the -domain. Described in RFC 1035.</p></td> +<td> + <p> + NAPTR + </p> + </td> +<td> + <p> + Name authority pointer. Described in RFC 2915. + </p> + </td> </tr> <tr> -<td><p>NXT</p></td> -<td><p>used in DNSSEC to securely indicate that -RRs with an owner name in a certain name interval do not exist in -a zone and indicate what RR types are present for an existing name. -Described in RFC 2535.</p></td> +<td> + <p> + NSAP + </p> + </td> +<td> + <p> + A network service access point. + Described in RFC 1706. + </p> + </td> </tr> <tr> -<td><p>PTR</p></td> -<td><p>a pointer to another part of the domain -name space. Described in RFC 1035.</p></td> +<td> + <p> + NS + </p> + </td> +<td> + <p> + The authoritative name server for the + domain. Described in RFC 1035. + </p> + </td> </tr> <tr> -<td><p>PX</p></td> -<td><p>provides mappings between RFC 822 and X.400 -addresses. Described in RFC 2163.</p></td> +<td> + <p> + NSEC + </p> + </td> +<td> + <p> + Used in DNSSECbis to securely indicate that + RRs with an owner name in a certain name interval do + not exist in + a zone and indicate what RR types are present for an + existing name. + Described in RFC 4034. + </p> + </td> </tr> <tr> -<td><p>RP</p></td> -<td><p>information on persons responsible -for the domain. Experimental. Described in RFC 1183.</p></td> +<td> + <p> + NXT + </p> + </td> +<td> + <p> + Used in DNSSEC to securely indicate that + RRs with an owner name in a certain name interval do + not exist in + a zone and indicate what RR types are present for an + existing name. + Used in original DNSSEC; replaced by NSEC in + DNSSECbis. + Described in RFC 2535. + </p> + </td> +</tr> +<tr> +<td> + <p> + PTR + </p> + </td> +<td> + <p> + A pointer to another part of the domain + name space. Described in RFC 1035. + </p> + </td> </tr> <tr> -<td><p>RT</p></td> -<td><p>route-through binding for hosts that -do not have their own direct wide area network addresses. -Experimental. Described in RFC 1183.</p></td> +<td> + <p> + PX + </p> + </td> +<td> + <p> + Provides mappings between RFC 822 and X.400 + addresses. Described in RFC 2163. + </p> + </td> </tr> <tr> -<td><p>SIG</p></td> -<td><p>("signature") contains data authenticated -in the secure DNS. Described in RFC 2535.</p></td> +<td> + <p> + RP + </p> + </td> +<td> + <p> + Information on persons responsible + for the domain. Experimental. Described in RFC 1183. + </p> + </td> </tr> <tr> -<td><p>SOA</p></td> -<td><p>identifies the start of a zone of authority. -Described in RFC 1035.</p></td> +<td> + <p> + RRSIG + </p> + </td> +<td> + <p> + Contains DNSSECbis signature data. Described + in RFC 4034. + </p> + </td> </tr> <tr> -<td><p>SRV</p></td> -<td><p>information about well known network -services (replaces WKS). Described in RFC 2782.</p></td> +<td> + <p> + RT + </p> + </td> +<td> + <p> + Route-through binding for hosts that + do not have their own direct wide area network + addresses. + Experimental. Described in RFC 1183. + </p> + </td> +</tr> +<tr> +<td> + <p> + SIG + </p> + </td> +<td> + <p> + Contains DNSSEC signature data. Used in + original DNSSEC; replaced by RRSIG in + DNSSECbis, but still used for SIG(0). + Described in RFCs 2535 and 2931. + </p> + </td> +</tr> +<tr> +<td> + <p> + SOA + </p> + </td> +<td> + <p> + Identifies the start of a zone of authority. + Described in RFC 1035. + </p> + </td> +</tr> +<tr> +<td> + <p> + SRV + </p> + </td> +<td> + <p> + Information about well known network + services (replaces WKS). Described in RFC 2782. + </p> + </td> </tr> <tr> -<td><p>TXT</p></td> -<td><p>text records. Described in RFC 1035.</p></td> +<td> + <p> + TXT + </p> + </td> +<td> + <p> + Text records. Described in RFC 1035. + </p> + </td> </tr> <tr> -<td><p>WKS</p></td> -<td><p>information about which well known -network services, such as SMTP, that a domain supports. Historical. -</p></td> +<td> + <p> + WKS + </p> + </td> +<td> + <p> + Information about which well known + network services, such as SMTP, that a domain + supports. Historical. + </p> + </td> </tr> <tr> -<td><p>X25</p></td> -<td><p>representation of X.25 network addresses. -Experimental. Described in RFC 1183.</p></td> +<td> + <p> + X25 + </p> + </td> +<td> + <p> + Representation of X.25 network addresses. + Experimental. Described in RFC 1183. + </p> + </td> </tr> </tbody> </table></div> -<p>The following <span class="emphasis"><em>classes</em></span> of resource records -are currently valid in the DNS:</p> +<p> + The following <span class="emphasis"><em>classes</em></span> of resource records + are currently valid in the DNS: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3518,72 +6182,131 @@ are currently valid in the DNS:</p> </colgroup> <tbody> <tr> -<td><p>IN</p></td> -<td><p>The Internet.</p></td> +<td> + <p> + IN + </p> + </td> +<td> + <p> + The Internet. + </p> + </td> </tr> <tr> -<td><p>CH</p></td> -<td><p> -CHAOSnet, a LAN protocol created at MIT in the mid-1970s. -Rarely used for its historical purpose, but reused for BIND's -built-in server information zones, e.g., -<code class="literal">version.bind</code>. -</p></td> +<td> + <p> + CH + </p> + </td> +<td> + <p> + Chaosnet, a LAN protocol created at MIT in the + mid-1970s. + Rarely used for its historical purpose, but reused for + BIND's + built-in server information zones, e.g., + <code class="literal">version.bind</code>. + </p> + </td> </tr> <tr> -<td><p>HS</p></td> -<td><p> -Hesiod, an information service -developed by MIT's Project Athena. It is used to share information -about various systems databases, such as users, groups, printers -and so on. -</p></td> +<td> + <p> + HS + </p> + </td> +<td> + <p> + Hesiod, an information service + developed by MIT's Project Athena. It is used to share + information + about various systems databases, such as users, + groups, printers + and so on. + </p> + </td> </tr> </tbody> </table></div> -<p>The owner name is often implicit, rather than forming an integral -part of the RR. For example, many name servers internally form tree -or hash structures for the name space, and chain RRs off nodes. - The remaining RR parts are the fixed header (type, class, TTL) -which is consistent for all RRs, and a variable part (RDATA) that -fits the needs of the resource being described.</p> -<p>The meaning of the TTL field is a time limit on how long an -RR can be kept in a cache. This limit does not apply to authoritative -data in zones; it is also timed out, but by the refreshing policies -for the zone. The TTL is assigned by the administrator for the -zone where the data originates. While short TTLs can be used to -minimize caching, and a zero TTL prohibits caching, the realities -of Internet performance suggest that these times should be on the -order of days for the typical host. If a change can be anticipated, -the TTL can be reduced prior to the change to minimize inconsistency -during the change, and then increased back to its former value following -the change.</p> -<p>The data in the RDATA section of RRs is carried as a combination -of binary strings and domain names. The domain names are frequently -used as "pointers" to other data in the DNS.</p> +<p> + The owner name is often implicit, rather than forming an + integral + part of the RR. For example, many name servers internally form + tree + or hash structures for the name space, and chain RRs off nodes. + The remaining RR parts are the fixed header (type, class, TTL) + which is consistent for all RRs, and a variable part (RDATA) + that + fits the needs of the resource being described. + </p> +<p> + The meaning of the TTL field is a time limit on how long an + RR can be kept in a cache. This limit does not apply to + authoritative + data in zones; it is also timed out, but by the refreshing + policies + for the zone. The TTL is assigned by the administrator for the + zone where the data originates. While short TTLs can be used to + minimize caching, and a zero TTL prohibits caching, the + realities + of Internet performance suggest that these times should be on + the + order of days for the typical host. If a change can be + anticipated, + the TTL can be reduced prior to the change to minimize + inconsistency + during the change, and then increased back to its former value + following + the change. + </p> +<p> + The data in the RDATA section of RRs is carried as a combination + of binary strings and domain names. The domain names are + frequently + used as "pointers" to other data in the DNS. + </p> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2590180"></a>Textual expression of RRs</h4></div></div></div> -<p>RRs are represented in binary form in the packets of the DNS -protocol, and are usually represented in highly encoded form when -stored in a name server or resolver. In the examples provided in -RFC 1034, a style similar to that used in master files was employed -in order to show the contents of RRs. In this format, most RRs -are shown on a single line, although continuation lines are possible -using parentheses.</p> -<p>The start of the line gives the owner of the RR. If a line -begins with a blank, then the owner is assumed to be the same as -that of the previous RR. Blank lines are often included for readability.</p> -<p>Following the owner, we list the TTL, type, and class of the -RR. Class and type use the mnemonics defined above, and TTL is -an integer before the type field. In order to avoid ambiguity in -parsing, type and class mnemonics are disjoint, TTLs are integers, -and the type mnemonic is always last. The IN class and TTL values -are often omitted from examples in the interests of clarity.</p> -<p>The resource data or RDATA section of the RR are given using -knowledge of the typical representation for the data.</p> -<p>For example, we might show the RRs carried in a message as:</p> +<a name="id2590513"></a>Textual expression of RRs</h4></div></div></div> +<p> + RRs are represented in binary form in the packets of the DNS + protocol, and are usually represented in highly encoded form + when + stored in a name server or resolver. In the examples provided + in + RFC 1034, a style similar to that used in master files was + employed + in order to show the contents of RRs. In this format, most RRs + are shown on a single line, although continuation lines are + possible + using parentheses. + </p> +<p> + The start of the line gives the owner of the RR. If a line + begins with a blank, then the owner is assumed to be the same as + that of the previous RR. Blank lines are often included for + readability. + </p> +<p> + Following the owner, we list the TTL, type, and class of the + RR. Class and type use the mnemonics defined above, and TTL is + an integer before the type field. In order to avoid ambiguity + in + parsing, type and class mnemonics are disjoint, TTLs are + integers, + and the type mnemonic is always last. The IN class and TTL + values + are often omitted from examples in the interests of clarity. + </p> +<p> + The resource data or RDATA section of the RR are given using + knowledge of the typical representation for the data. + </p> +<p> + For example, we might show the RRs carried in a message as: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3592,43 +6315,116 @@ knowledge of the typical representation for the data.</p> </colgroup> <tbody> <tr> -<td><p><code class="literal">ISI.EDU.</code></p></td> -<td><p><code class="literal">MX</code></p></td> -<td><p><code class="literal">10 VENERA.ISI.EDU.</code></p></td> +<td> + <p> + <code class="literal">ISI.EDU.</code> + </p> + </td> +<td> + <p> + <code class="literal">MX</code> + </p> + </td> +<td> + <p> + <code class="literal">10 VENERA.ISI.EDU.</code> + </p> + </td> </tr> <tr> -<td><p></p></td> -<td><p><code class="literal">MX</code></p></td> -<td><p><code class="literal">10 VAXA.ISI.EDU</code></p></td> +<td> + <p></p> + </td> +<td> + <p> + <code class="literal">MX</code> + </p> + </td> +<td> + <p> + <code class="literal">10 VAXA.ISI.EDU</code> + </p> + </td> </tr> <tr> -<td><p><code class="literal">VENERA.ISI.EDU</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">128.9.0.32</code></p></td> +<td> + <p> + <code class="literal">VENERA.ISI.EDU</code> + </p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">128.9.0.32</code> + </p> + </td> </tr> <tr> -<td><p></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">10.1.0.52</code></p></td> +<td> + <p></p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">10.1.0.52</code> + </p> + </td> </tr> <tr> -<td><p><code class="literal">VAXA.ISI.EDU</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">10.2.0.27</code></p></td> +<td> + <p> + <code class="literal">VAXA.ISI.EDU</code> + </p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">10.2.0.27</code> + </p> + </td> </tr> <tr> -<td><p></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">128.9.0.33</code></p></td> +<td> + <p></p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">128.9.0.33</code> + </p> + </td> </tr> </tbody> </table></div> -<p>The MX RRs have an RDATA section which consists of a 16-bit -number followed by a domain name. The address RRs use a standard -IP address format to contain a 32-bit internet address.</p> -<p>The above example shows six RRs, with two RRs at each of three -domain names.</p> -<p>Similarly we might see:</p> +<p> + The MX RRs have an RDATA section which consists of a 16-bit + number followed by a domain name. The address RRs use a + standard + IP address format to contain a 32-bit internet address. + </p> +<p> + The above example shows six RRs, with two RRs at each of three + domain names. + </p> +<p> + Similarly we might see: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3637,45 +6433,83 @@ domain names.</p> </colgroup> <tbody> <tr> -<td><p><code class="literal">XX.LCS.MIT.EDU. IN</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">10.0.0.44</code></p></td> +<td> + <p> + <code class="literal">XX.LCS.MIT.EDU.</code> + </p> + </td> +<td> + <p> + <code class="literal">IN A</code> + </p> + </td> +<td> + <p> + <code class="literal">10.0.0.44</code> + </p> + </td> </tr> <tr> -<td><p><code class="literal">CH</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">MIT.EDU. 2420</code></p></td> +<td> </td> +<td> + <p> + <code class="literal">CH A</code> + </p> + </td> +<td> + <p> + <code class="literal">MIT.EDU. 2420</code> + </p> + </td> </tr> </tbody> </table></div> -<p>This example shows two addresses for <code class="literal">XX.LCS.MIT.EDU</code>, -each of a different class.</p> +<p> + This example shows two addresses for + <code class="literal">XX.LCS.MIT.EDU</code>, each of a different class. + </p> </div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2590605"></a>Discussion of MX Records</h3></div></div></div> -<p>As described above, domain servers store information as a -series of resource records, each of which contains a particular -piece of information about a given domain name (which is usually, -but not always, a host). The simplest way to think of a RR is as -a typed pair of data, a domain name matched with a relevant datum, -and stored with some additional type information to help systems -determine when the RR is relevant.</p> -<p>MX records are used to control delivery of email. The data -specified in the record is a priority and a domain name. The priority -controls the order in which email delivery is attempted, with the -lowest number first. If two priorities are the same, a server is -chosen randomly. If no servers at a given priority are responding, -the mail transport agent will fall back to the next largest priority. -Priority numbers do not have any absolute meaning — they are relevant -only respective to other MX records for that domain name. The domain -name given is the machine to which the mail will be delivered. It <span class="emphasis"><em>must</em></span> have -an associated A record — CNAME is not sufficient.</p> -<p>For a given domain, if there is both a CNAME record and an -MX record, the MX record is in error, and will be ignored. Instead, -the mail will be delivered to the server specified in the MX record -pointed to by the CNAME.</p> +<a name="id2591101"></a>Discussion of MX Records</h3></div></div></div> +<p> + As described above, domain servers store information as a + series of resource records, each of which contains a particular + piece of information about a given domain name (which is usually, + but not always, a host). The simplest way to think of a RR is as + a typed pair of data, a domain name matched with a relevant datum, + and stored with some additional type information to help systems + determine when the RR is relevant. + </p> +<p> + MX records are used to control delivery of email. The data + specified in the record is a priority and a domain name. The + priority + controls the order in which email delivery is attempted, with the + lowest number first. If two priorities are the same, a server is + chosen randomly. If no servers at a given priority are responding, + the mail transport agent will fall back to the next largest + priority. + Priority numbers do not have any absolute meaning — they are + relevant + only respective to other MX records for that domain name. The + domain + name given is the machine to which the mail will be delivered. + It <span class="emphasis"><em>must</em></span> have an associated address record + (A or AAAA) — CNAME is not sufficient. + </p> +<p> + For a given domain, if there is both a CNAME record and an + MX record, the MX record is in error, and will be ignored. + Instead, + the mail will be delivered to the server specified in the MX + record + pointed to by the CNAME. + </p> +<p> + For example: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3686,56 +6520,152 @@ pointed to by the CNAME.</p> </colgroup> <tbody> <tr> -<td><p><code class="literal">example.com.</code></p></td> -<td><p><code class="literal">IN</code></p></td> -<td><p><code class="literal">MX</code></p></td> -<td><p><code class="literal">10</code></p></td> -<td><p><code class="literal">mail.example.com.</code></p></td> +<td> + <p> + <code class="literal">example.com.</code> + </p> + </td> +<td> + <p> + <code class="literal">IN</code> + </p> + </td> +<td> + <p> + <code class="literal">MX</code> + </p> + </td> +<td> + <p> + <code class="literal">10</code> + </p> + </td> +<td> + <p> + <code class="literal">mail.example.com.</code> + </p> + </td> </tr> <tr> -<td><p></p></td> -<td><p><code class="literal">IN</code></p></td> -<td><p><code class="literal">MX</code></p></td> -<td><p><code class="literal">10</code></p></td> -<td><p><code class="literal">mail2.example.com.</code></p></td> +<td> + <p></p> + </td> +<td> + <p> + <code class="literal">IN</code> + </p> + </td> +<td> + <p> + <code class="literal">MX</code> + </p> + </td> +<td> + <p> + <code class="literal">10</code> + </p> + </td> +<td> + <p> + <code class="literal">mail2.example.com.</code> + </p> + </td> </tr> <tr> -<td><p></p></td> -<td><p><code class="literal">IN</code></p></td> -<td><p><code class="literal">MX</code></p></td> -<td><p><code class="literal">20</code></p></td> -<td><p><code class="literal">mail.backup.org.</code></p></td> +<td> + <p></p> + </td> +<td> + <p> + <code class="literal">IN</code> + </p> + </td> +<td> + <p> + <code class="literal">MX</code> + </p> + </td> +<td> + <p> + <code class="literal">20</code> + </p> + </td> +<td> + <p> + <code class="literal">mail.backup.org.</code> + </p> + </td> </tr> <tr> -<td><p><code class="literal">mail.example.com.</code></p></td> -<td><p><code class="literal">IN</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">10.0.0.1</code></p></td> -<td><p></p></td> +<td> + <p> + <code class="literal">mail.example.com.</code> + </p> + </td> +<td> + <p> + <code class="literal">IN</code> + </p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">10.0.0.1</code> + </p> + </td> +<td> + <p></p> + </td> </tr> <tr> -<td><p><code class="literal">mail2.example.com.</code></p></td> -<td><p><code class="literal">IN</code></p></td> -<td><p><code class="literal">A</code></p></td> -<td><p><code class="literal">10.0.0.2</code></p></td> -<td><p></p></td> +<td> + <p> + <code class="literal">mail2.example.com.</code> + </p> + </td> +<td> + <p> + <code class="literal">IN</code> + </p> + </td> +<td> + <p> + <code class="literal">A</code> + </p> + </td> +<td> + <p> + <code class="literal">10.0.0.2</code> + </p> + </td> +<td> + <p></p> + </td> </tr> </tbody> </table></div> -<p>For example:</p> -<p>Mail delivery will be attempted to <code class="literal">mail.example.com</code> and -<code class="literal">mail2.example.com</code> (in -any order), and if neither of those succeed, delivery to <code class="literal">mail.backup.org</code> will -be attempted.</p> +<p> + Mail delivery will be attempted to <code class="literal">mail.example.com</code> and + <code class="literal">mail2.example.com</code> (in + any order), and if neither of those succeed, delivery to <code class="literal">mail.backup.org</code> will + be attempted. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="Setting_TTLs"></a>Setting TTLs</h3></div></div></div> -<p>The time-to-live of the RR field is a 32-bit integer represented -in units of seconds, and is primarily used by resolvers when they -cache RRs. The TTL describes how long a RR can be cached before it -should be discarded. The following three types of TTL are currently -used in a zone file.</p> +<p> + The time-to-live of the RR field is a 32-bit integer represented + in units of seconds, and is primarily used by resolvers when they + cache RRs. The TTL describes how long a RR can be cached before it + should be discarded. The following three types of TTL are + currently + used in a zone file. + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3743,46 +6673,79 @@ used in a zone file.</p> </colgroup> <tbody> <tr> -<td><p>SOA</p></td> <td> -<p>The last field in the SOA is the negative -caching TTL. This controls how long other servers will cache no-such-domain -(NXDOMAIN) responses from you.</p> -<p>The maximum time for -negative caching is 3 hours (3h).</p> -</td> + <p> + SOA + </p> + </td> +<td> + <p> + The last field in the SOA is the negative + caching TTL. This controls how long other servers will + cache no-such-domain + (NXDOMAIN) responses from you. + </p> + <p> + The maximum time for + negative caching is 3 hours (3h). + </p> + </td> </tr> <tr> -<td><p>$TTL</p></td> -<td><p>The $TTL directive at the top of the -zone file (before the SOA) gives a default TTL for every RR without -a specific TTL set.</p></td> +<td> + <p> + $TTL + </p> + </td> +<td> + <p> + The $TTL directive at the top of the + zone file (before the SOA) gives a default TTL for every + RR without + a specific TTL set. + </p> + </td> </tr> <tr> -<td><p>RR TTLs</p></td> -<td><p>Each RR can have a TTL as the second -field in the RR, which will control how long other servers can cache -the it.</p></td> +<td> + <p> + RR TTLs + </p> + </td> +<td> + <p> + Each RR can have a TTL as the second + field in the RR, which will control how long other + servers can cache + the it. + </p> + </td> </tr> </tbody> </table></div> -<p>All of these TTLs default to units of seconds, though units -can be explicitly specified, for example, <code class="literal">1h30m</code>. </p> +<p> + All of these TTLs default to units of seconds, though units + can be explicitly specified, for example, <code class="literal">1h30m</code>. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2591102"></a>Inverse Mapping in IPv4</h3></div></div></div> -<p>Reverse name resolution (that is, translation from IP address -to name) is achieved by means of the <span class="emphasis"><em>in-addr.arpa</em></span> domain -and PTR records. Entries in the in-addr.arpa domain are made in -least-to-most significant order, read left to right. This is the -opposite order to the way IP addresses are usually written. Thus, -a machine with an IP address of 10.1.2.3 would have a corresponding -in-addr.arpa name of -3.2.1.10.in-addr.arpa. This name should have a PTR resource record -whose data field is the name of the machine or, optionally, multiple -PTR records if the machine has more than one name. For example, -in the [<span class="optional">example.com</span>] domain:</p> +<a name="id2591653"></a>Inverse Mapping in IPv4</h3></div></div></div> +<p> + Reverse name resolution (that is, translation from IP address + to name) is achieved by means of the <span class="emphasis"><em>in-addr.arpa</em></span> domain + and PTR records. Entries in the in-addr.arpa domain are made in + least-to-most significant order, read left to right. This is the + opposite order to the way IP addresses are usually written. Thus, + a machine with an IP address of 10.1.2.3 would have a + corresponding + in-addr.arpa name of + 3.2.1.10.in-addr.arpa. This name should have a PTR resource record + whose data field is the name of the machine or, optionally, + multiple + PTR records if the machine has more than one name. For example, + in the [<span class="optional">example.com</span>] domain: + </p> <div class="informaltable"><table border="1"> <colgroup> <col> @@ -3790,95 +6753,167 @@ in the [<span class="optional">example.com</span>] domain:</p> </colgroup> <tbody> <tr> -<td><p><code class="literal">$ORIGIN</code></p></td> -<td><p><code class="literal">2.1.10.in-addr.arpa</code></p></td> +<td> + <p> + <code class="literal">$ORIGIN</code> + </p> + </td> +<td> + <p> + <code class="literal">2.1.10.in-addr.arpa</code> + </p> + </td> </tr> <tr> -<td><p><code class="literal">3</code></p></td> -<td><p><code class="literal">IN PTR foo.example.com.</code></p></td> +<td> + <p> + <code class="literal">3</code> + </p> + </td> +<td> + <p> + <code class="literal">IN PTR foo.example.com.</code> + </p> + </td> </tr> </tbody> </table></div> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>The <span><strong class="command">$ORIGIN</strong></span> lines in the examples -are for providing context to the examples only-they do not necessarily -appear in the actual usage. They are only used here to indicate -that the example is relative to the listed origin.</p> +<p> + The <span><strong class="command">$ORIGIN</strong></span> lines in the examples + are for providing context to the examples only — they do not + necessarily + appear in the actual usage. They are only used here to indicate + that the example is relative to the listed origin. + </p> </div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2591208"></a>Other Zone File Directives</h3></div></div></div> -<p>The Master File Format was initially defined in RFC 1035 and -has subsequently been extended. While the Master File Format itself -is class independent all records in a Master File must be of the same -class.</p> -<p>Master File Directives include <span><strong class="command">$ORIGIN</strong></span>, <span><strong class="command">$INCLUDE</strong></span>, -and <span><strong class="command">$TTL.</strong></span></p> +<a name="id2591848"></a>Other Zone File Directives</h3></div></div></div> +<p> + The Master File Format was initially defined in RFC 1035 and + has subsequently been extended. While the Master File Format + itself + is class independent all records in a Master File must be of the + same + class. + </p> +<p> + Master File Directives include <span><strong class="command">$ORIGIN</strong></span>, <span><strong class="command">$INCLUDE</strong></span>, + and <span><strong class="command">$TTL.</strong></span> + </p> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2591227"></a>The <span><strong class="command">$ORIGIN</strong></span> Directive</h4></div></div></div> -<p>Syntax: <span><strong class="command">$ORIGIN -</strong></span><em class="replaceable"><code>domain-name</code></em> [<span class="optional"> <em class="replaceable"><code>comment</code></em></span>]</p> -<p><span><strong class="command">$ORIGIN</strong></span> sets the domain name that will -be appended to any unqualified records. When a zone is first read -in there is an implicit <span><strong class="command">$ORIGIN</strong></span> <<code class="varname">zone-name</code>><span><strong class="command">.</strong></span> The -current <span><strong class="command">$ORIGIN</strong></span> is appended to the domain specified -in the <span><strong class="command">$ORIGIN</strong></span> argument if it is not absolute.</p> -<pre class="programlisting">$ORIGIN example.com. -WWW CNAME MAIN-SERVER</pre> -<p>is equivalent to</p> -<pre class="programlisting">WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.</pre> +<a name="id2591870"></a>The <span><strong class="command">$ORIGIN</strong></span> Directive</h4></div></div></div> +<p> + Syntax: <span><strong class="command">$ORIGIN</strong></span> + <em class="replaceable"><code>domain-name</code></em> + [<span class="optional"><em class="replaceable"><code>comment</code></em></span>] + </p> +<p><span><strong class="command">$ORIGIN</strong></span> + sets the domain name that will be appended to any + unqualified records. When a zone is first read in there + is an implicit <span><strong class="command">$ORIGIN</strong></span> + <<code class="varname">zone-name</code>><span><strong class="command">.</strong></span> + The current <span><strong class="command">$ORIGIN</strong></span> is appended to + the domain specified in the <span><strong class="command">$ORIGIN</strong></span> + argument if it is not absolute. + </p> +<pre class="programlisting"> +$ORIGIN example.com. +WWW CNAME MAIN-SERVER +</pre> +<p> + is equivalent to + </p> +<pre class="programlisting"> +WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM. +</pre> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2591283"></a>The <span><strong class="command">$INCLUDE</strong></span> Directive</h4></div></div></div> -<p>Syntax: <span><strong class="command">$INCLUDE</strong></span> -<em class="replaceable"><code>filename</code></em> [<span class="optional"> -<em class="replaceable"><code>origin</code></em> </span>] [<span class="optional"> <em class="replaceable"><code>comment</code></em> </span>]</p> -<p>Read and process the file <code class="filename">filename</code> as -if it were included into the file at this point. If <span><strong class="command">origin</strong></span> is -specified the file is processed with <span><strong class="command">$ORIGIN</strong></span> set -to that value, otherwise the current <span><strong class="command">$ORIGIN</strong></span> is -used.</p> -<p>The origin and the current domain name -revert to the values they had prior to the <span><strong class="command">$INCLUDE</strong></span> once -the file has been read.</p> +<a name="id2592000"></a>The <span><strong class="command">$INCLUDE</strong></span> Directive</h4></div></div></div> +<p> + Syntax: <span><strong class="command">$INCLUDE</strong></span> + <em class="replaceable"><code>filename</code></em> + [<span class="optional"> +<em class="replaceable"><code>origin</code></em> </span>] + [<span class="optional"> <em class="replaceable"><code>comment</code></em> </span>] + </p> +<p> + Read and process the file <code class="filename">filename</code> as + if it were included into the file at this point. If <span><strong class="command">origin</strong></span> is + specified the file is processed with <span><strong class="command">$ORIGIN</strong></span> set + to that value, otherwise the current <span><strong class="command">$ORIGIN</strong></span> is + used. + </p> +<p> + The origin and the current domain name + revert to the values they had prior to the <span><strong class="command">$INCLUDE</strong></span> once + the file has been read. + </p> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> <p> -RFC 1035 specifies that the current origin should be restored after -an <span><strong class="command">$INCLUDE</strong></span>, but it is silent on whether the current -domain name should also be restored. BIND 9 restores both of them. -This could be construed as a deviation from RFC 1035, a feature, or both. -</p> + RFC 1035 specifies that the current origin should be restored + after + an <span><strong class="command">$INCLUDE</strong></span>, but it is silent + on whether the current + domain name should also be restored. BIND 9 restores both of + them. + This could be construed as a deviation from RFC 1035, a + feature, or both. + </p> </div> </div> <div class="sect3" lang="en"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2591346"></a>The <span><strong class="command">$TTL</strong></span> Directive</h4></div></div></div> -<p>Syntax: <span><strong class="command">$TTL</strong></span> -<em class="replaceable"><code>default-ttl</code></em> [<span class="optional"> -<em class="replaceable"><code>comment</code></em> </span>]</p> -<p>Set the default Time To Live (TTL) for subsequent records -with undefined TTLs. Valid TTLs are of the range 0-2147483647 seconds.</p> -<p><span><strong class="command">$TTL</strong></span> is defined in RFC 2308.</p> +<a name="id2592069"></a>The <span><strong class="command">$TTL</strong></span> Directive</h4></div></div></div> +<p> + Syntax: <span><strong class="command">$TTL</strong></span> + <em class="replaceable"><code>default-ttl</code></em> + [<span class="optional"> +<em class="replaceable"><code>comment</code></em> </span>] + </p> +<p> + Set the default Time To Live (TTL) for subsequent records + with undefined TTLs. Valid TTLs are of the range 0-2147483647 + seconds. + </p> +<p><span><strong class="command">$TTL</strong></span> + is defined in RFC 2308. + </p> </div> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2591377"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</h3></div></div></div> -<p>Syntax: <span><strong class="command">$GENERATE</strong></span> <em class="replaceable"><code>range</code></em> <em class="replaceable"><code>lhs</code></em> [<span class="optional"><em class="replaceable"><code>ttl</code></em></span>] [<span class="optional"><em class="replaceable"><code>class</code></em></span>] <em class="replaceable"><code>type</code></em> <em class="replaceable"><code>rhs</code></em> [<span class="optional"> <em class="replaceable"><code>comment</code></em> </span>]</p> -<p><span><strong class="command">$GENERATE</strong></span> is used to create a series of -resource records that only differ from each other by an iterator. <span><strong class="command">$GENERATE</strong></span> 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.</p> +<a name="id2592173"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</h3></div></div></div> +<p> + Syntax: <span><strong class="command">$GENERATE</strong></span> + <em class="replaceable"><code>range</code></em> + <em class="replaceable"><code>lhs</code></em> + [<span class="optional"><em class="replaceable"><code>ttl</code></em></span>] + [<span class="optional"><em class="replaceable"><code>class</code></em></span>] + <em class="replaceable"><code>type</code></em> + <em class="replaceable"><code>rhs</code></em> + [<span class="optional"><em class="replaceable"><code>comment</code></em></span>] + </p> +<p><span><strong class="command">$GENERATE</strong></span> + is used to create a series of resource records that only + differ from each other by an + iterator. <span><strong class="command">$GENERATE</strong></span> 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. + </p> <pre class="programlisting">$ORIGIN 0.0.192.IN-ADDR.ARPA. $GENERATE 1-2 0 NS SERVER$.EXAMPLE. $GENERATE 1-127 $ CNAME $.0</pre> -<p>is equivalent to</p> +<p> + is equivalent to + </p> <pre class="programlisting">0.0.0.192.IN-ADDR.ARPA NS SERVER1.EXAMPLE. 0.0.0.192.IN-ADDR.ARPA. NS SERVER2.EXAMPLE. 1.0.0.192.IN-ADDR.ARPA. CNAME 1.0.0.0.192.IN-ADDR.ARPA. @@ -3893,72 +6928,168 @@ $GENERATE 1-127 $ CNAME $.0</pre> </colgroup> <tbody> <tr> -<td><p><span><strong class="command">range</strong></span></p></td> -<td><p>This can be one of two forms: start-stop -or start-stop/step. If the first form is used, then step is set to - 1. All of start, stop and step must be positive.</p></td> -</tr> -<tr> -<td><p><span><strong class="command">lhs</strong></span></p></td> -<td> -<p><span><strong class="command">lhs</strong></span> describes the -owner name of the resource records to be created. Any single -<span><strong class="command">$</strong></span> (dollar sign) symbols -within the <span><strong class="command">lhs</strong></span> side are replaced by the iterator -value. -To get a $ in the output you need to escape the <span><strong class="command">$</strong></span> -using a backslash <span><strong class="command">\</strong></span>, -e.g. <span><strong class="command">\$</strong></span>. The <span><strong class="command">$</strong></span> may optionally be followed -by modifiers which change the offset from the iterator, field width and base. -Modifiers are introduced by a <span><strong class="command">{</strong></span> immediately following the -<span><strong class="command">$</strong></span> as <span><strong class="command">${offset[,width[,base]]}</strong></span>. -For example, <span><strong class="command">${-20,3,d}</strong></span> which subtracts 20 from the current value, -prints the result as a decimal in a zero-padded field of width 3. Available -output forms are decimal (<span><strong class="command">d</strong></span>), octal (<span><strong class="command">o</strong></span>) -and hexadecimal (<span><strong class="command">x</strong></span> or <span><strong class="command">X</strong></span> for uppercase). -The default modifier is <span><strong class="command">${0,0,d}</strong></span>. -If the <span><strong class="command">lhs</strong></span> is not -absolute, the current <span><strong class="command">$ORIGIN</strong></span> is appended to -the name.</p> -<p>For compatibility with earlier versions, <span><strong class="command">$$</strong></span> is still -recognized as indicating a literal $ in the output.</p> -</td> +<td> + <p><span><strong class="command">range</strong></span></p> + </td> +<td> + <p> + This can be one of two forms: start-stop + or start-stop/step. If the first form is used, then step + is set to + 1. All of start, stop and step must be positive. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">ttl</strong></span></p></td> <td> -<p>Specifies the - ttl of the generated records. If not specified this will be - inherited using the normal ttl inheritance rules.</p> - <p><span><strong class="command">class</strong></span> and <span><strong class="command">ttl</strong></span> can be - entered in either order.</p> -</td> + <p><span><strong class="command">lhs</strong></span></p> + </td> +<td> + <p>This + describes the owner name of the resource records + to be created. Any single <span><strong class="command">$</strong></span> + (dollar sign) + symbols within the <span><strong class="command">lhs</strong></span> side + are replaced by the iterator value. + + To get a $ in the output, you need to escape the + <span><strong class="command">$</strong></span> using a backslash + <span><strong class="command">\</strong></span>, + e.g. <span><strong class="command">\$</strong></span>. The + <span><strong class="command">$</strong></span> may optionally be followed + by modifiers which change the offset from the + iterator, field width and base. + + Modifiers are introduced by a + <span><strong class="command">{</strong></span> (left brace) immediately following the + <span><strong class="command">$</strong></span> as + <span><strong class="command">${offset[,width[,base]]}</strong></span>. + For example, <span><strong class="command">${-20,3,d}</strong></span> + subtracts 20 from the current value, prints the + result as a decimal in a zero-padded field of + width 3. + + Available output forms are decimal + (<span><strong class="command">d</strong></span>), octal + (<span><strong class="command">o</strong></span>) and hexadecimal + (<span><strong class="command">x</strong></span> or <span><strong class="command">X</strong></span> + for uppercase). The default modifier is + <span><strong class="command">${0,0,d}</strong></span>. If the + <span><strong class="command">lhs</strong></span> is not absolute, the + current <span><strong class="command">$ORIGIN</strong></span> is appended + to the name. + </p> + <p> + For compatibility with earlier versions, <span><strong class="command">$$</strong></span> is still + recognized as indicating a literal $ in the output. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">class</strong></span></p></td> <td> -<p>Specifies the - class of the generated records. This must match the zone class if - it is specified.</p> - <p><span><strong class="command">class</strong></span> and <span><strong class="command">ttl</strong></span> can be - entered in either order.</p> -</td> + <p><span><strong class="command">ttl</strong></span></p> + </td> +<td> + <p> + Specifies the time-to-live of the generated records. If + not specified this will be inherited using the + normal ttl inheritance rules. + </p> + <p><span><strong class="command">class</strong></span> + and <span><strong class="command">ttl</strong></span> can be + entered in either order. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">type</strong></span></p></td> -<td><p>At present the only supported types are -PTR, CNAME, DNAME, A, AAAA and NS.</p></td> +<td> + <p><span><strong class="command">class</strong></span></p> + </td> +<td> + <p> + Specifies the class of the generated records. + This must match the zone class if it is + specified. + </p> + <p><span><strong class="command">class</strong></span> + and <span><strong class="command">ttl</strong></span> can be + entered in either order. + </p> + </td> </tr> <tr> -<td><p><span><strong class="command">rhs</strong></span></p></td> -<td><p>A domain name. It is processed -similarly to lhs.</p></td> +<td> + <p><span><strong class="command">type</strong></span></p> + </td> +<td> + <p> + At present the only supported types are + PTR, CNAME, DNAME, A, AAAA and NS. + </p> + </td> +</tr> +<tr> +<td> + <p><span><strong class="command">rhs</strong></span></p> + </td> +<td> + <p> + <span><strong class="command">rhs</strong></span> is a domain name. It is processed + similarly to lhs. + </p> + </td> </tr> </tbody> </table></div> -<p>The <span><strong class="command">$GENERATE</strong></span> directive is a <acronym class="acronym">BIND</acronym> extension -and not part of the standard zone file format.</p> -<p>BIND 8 does not support the optional TTL and CLASS fields.</p> +<p> + The <span><strong class="command">$GENERATE</strong></span> directive is a <acronym class="acronym">BIND</acronym> extension + and not part of the standard zone file format. + </p> +<p> + BIND 8 does not support the optional TTL and CLASS fields. + </p> +</div> +<div class="sect2" lang="en"> +<div class="titlepage"><div><div><h3 class="title"> +<a name="zonefile_format"></a>Additional File Formats</h3></div></div></div> +<p> + In addition to the standard textual format, BIND 9 + supports the ability to read or dump to zone files in + other formats. The <code class="constant">raw</code> format is + currently available as an additional format. It is a + binary format representing BIND 9's internal data + structure directly, thereby remarkably improving the + loading time. + </p> +<p> + For a primary server, a zone file in the + <code class="constant">raw</code> format is expected to be + generated from a textual zone file by the + <span><strong class="command">named-compilezone</strong></span> command. For a + secondary server or for a dynamic zone, it is automatically + generated (if this format is specified by the + <span><strong class="command">masterfile-format</strong></span> option) when + <span><strong class="command">named</strong></span> dumps the zone contents after + zone transfer or when applying prior updates. + </p> +<p> + If a zone file in a binary format needs manual modification, + it first must be converted to a textual form by the + <span><strong class="command">named-compilezone</strong></span> command. All + necessary modification should go to the text file, which + should then be converted to the binary form by the + <span><strong class="command">named-compilezone</strong></span> command again. + </p> +<p> + Although the <code class="constant">raw</code> format uses the + network byte order and avoids architecture-dependent + data alignment so that it is as much portable as + possible, it is primarily expected to be used inside + the same single system. In order to export a zone + file in the <code class="constant">raw</code> format or make a + portable backup of the file, it is recommended to + convert the file to the standard textual representation. + </p> </div> </div> </div> diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch07.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch07.html index 892db421b88..208ee600191 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch07.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch07.html @@ -1,5 +1,5 @@ <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - Permission to use, copy, modify, and distribute this software for any @@ -14,12 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $ISC: Bv9ARM.ch07.html,v 1.50.2.9.2.33 2006/09/13 02:56:21 marka Exp $ --> +<!-- $ISC: Bv9ARM.ch07.html,v 1.75.18.63 2007/10/31 01:35:59 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Chapter 7. BIND 9 Security Considerations</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="prev" href="Bv9ARM.ch06.html" title="Chapter 6. BIND 9 Configuration Reference"> @@ -46,11 +46,10 @@ <p><b>Table of Contents</b></p> <dl> <dt><span class="sect1"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2591971"><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span> (for -UNIX servers)</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2592714"><span><strong class="command">Chroot</strong></span> and <span><strong class="command">Setuid</strong></span></a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2592046">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2592172">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2592791">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2592851">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt> </dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt> </dl> @@ -58,26 +57,37 @@ UNIX servers)</a></span></dt> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="Access_Control_Lists"></a>Access Control Lists</h2></div></div></div> -<p>Access Control Lists (ACLs), are address match lists that -you can set up and nickname for future use in <span><strong class="command">allow-notify</strong></span>, -<span><strong class="command">allow-query</strong></span>, <span><strong class="command">allow-recursion</strong></span>, -<span><strong class="command">blackhole</strong></span>, <span><strong class="command">allow-transfer</strong></span>, -etc.</p> -<p>Using ACLs allows you to have finer control over who can access -your name server, without cluttering up your config files with huge -lists of IP addresses.</p> -<p>It is a <span class="emphasis"><em>good idea</em></span> to use ACLs, and to -control access to your server. Limiting access to your server by -outside parties can help prevent spoofing and denial of service (DoS) -attacks against your server.</p> -<p>Here is an example of how to properly apply ACLs:</p> +<p> + Access Control Lists (ACLs), are address match lists that + you can set up and nickname for future use in <span><strong class="command">allow-notify</strong></span>, + <span><strong class="command">allow-query</strong></span>, <span><strong class="command">allow-recursion</strong></span>, + <span><strong class="command">blackhole</strong></span>, <span><strong class="command">allow-transfer</strong></span>, + etc. + </p> +<p> + Using ACLs allows you to have finer control over who can access + your name server, without cluttering up your config files with huge + lists of IP addresses. + </p> +<p> + It is a <span class="emphasis"><em>good idea</em></span> to use ACLs, and to + control access to your server. Limiting access to your server by + outside parties can help prevent spoofing and denial of service (DoS) attacks against + your server. + </p> +<p> + Here is an example of how to properly apply ACLs: + </p> <pre class="programlisting"> -// Set up an ACL named "bogusnets" that will block RFC1918 space, -// which is commonly used in spoofing attacks. -acl bogusnets { 0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3; 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; }; +// Set up an ACL named "bogusnets" that will block RFC1918 space +// and some reserved space, which is commonly used in spoofing attacks. +acl bogusnets { + 0.0.0.0/8; 1.0.0.0/8; 2.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3; + 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16; +}; // Set up an ACL called our-nets. Replace this with the real IP numbers. -acl our-nets { x.x.x.x/24; x.x.x.x/21; }; +acl our-nets { x.x.x.x/24; x.x.x.x/21; }; options { ... ... @@ -94,91 +104,132 @@ zone "example.com" { allow-query { any; }; }; </pre> -<p>This allows recursive queries of the server from the outside -unless recursion has been previously disabled.</p> -<p>For more information on how to use ACLs to protect your server, -see the <span class="emphasis"><em>AUSCERT</em></span> advisory at -<a href="ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos" target="_top">ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos</a></p> +<p> + This allows recursive queries of the server from the outside + unless recursion has been previously disabled. + </p> +<p> + For more information on how to use ACLs to protect your server, + see the <span class="emphasis"><em>AUSCERT</em></span> advisory at: + </p> +<p> + <a href="ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos" target="_top">ftp://ftp.auscert.org.au/pub/auscert/advisory/AL-1999.004.dns_dos</a> + </p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2591971"></a><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span> (for -UNIX servers)</h2></div></div></div> -<p>On UNIX servers, it is possible to run <acronym class="acronym">BIND</acronym> in a <span class="emphasis"><em>chrooted</em></span> environment -(using the <span><strong class="command">chroot()</strong></span> function) by specifying the "<code class="option">-t</code>" -option. This can help improve system security by placing <acronym class="acronym">BIND</acronym> in -a "sandbox", which will limit the damage done if a server is compromised.</p> -<p>Another useful feature in the UNIX version of <acronym class="acronym">BIND</acronym> is the -ability to run the daemon as an unprivileged user ( <code class="option">-u</code> <em class="replaceable"><code>user</code></em> ). -We suggest running as an unprivileged user when using the <span><strong class="command">chroot</strong></span> feature.</p> -<p>Here is an example command line to load <acronym class="acronym">BIND</acronym> in a <span><strong class="command">chroot</strong></span> sandbox, -<span><strong class="command">/var/named</strong></span>, and to run <span><strong class="command">named</strong></span> <span><strong class="command">setuid</strong></span> to -user 202:</p> -<p><strong class="userinput"><code>/usr/local/bin/named -u 202 -t /var/named</code></strong></p> +<a name="id2592714"></a><span><strong class="command">Chroot</strong></span> and <span><strong class="command">Setuid</strong></span> +</h2></div></div></div> +<p> + On UNIX servers, it is possible to run <acronym class="acronym">BIND</acronym> in a <span class="emphasis"><em>chrooted</em></span> environment + (using the <span><strong class="command">chroot()</strong></span> function) by specifying the "<code class="option">-t</code>" + option. This can help improve system security by placing <acronym class="acronym">BIND</acronym> in + a "sandbox", which will limit the damage done if a server is + compromised. + </p> +<p> + Another useful feature in the UNIX version of <acronym class="acronym">BIND</acronym> is the + ability to run the daemon as an unprivileged user ( <code class="option">-u</code> <em class="replaceable"><code>user</code></em> ). + We suggest running as an unprivileged user when using the <span><strong class="command">chroot</strong></span> feature. + </p> +<p> + Here is an example command line to load <acronym class="acronym">BIND</acronym> in a <span><strong class="command">chroot</strong></span> sandbox, + <span><strong class="command">/var/named</strong></span>, and to run <span><strong class="command">named</strong></span> <span><strong class="command">setuid</strong></span> to + user 202: + </p> +<p> + <strong class="userinput"><code>/usr/local/bin/named -u 202 -t /var/named</code></strong> + </p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2592046"></a>The <span><strong class="command">chroot</strong></span> Environment</h3></div></div></div> -<p>In order for a <span><strong class="command">chroot</strong></span> environment to -work properly in a particular directory -(for example, <code class="filename">/var/named</code>), -you will need to set up an environment that includes everything -<acronym class="acronym">BIND</acronym> needs to run. -From <acronym class="acronym">BIND</acronym>'s point of view, <code class="filename">/var/named</code> is -the root of the filesystem. You will need to adjust the values of options like -like <span><strong class="command">directory</strong></span> and <span><strong class="command">pid-file</strong></span> to account -for this. -</p> -<p> -Unlike with earlier versions of BIND, you will typically -<span class="emphasis"><em>not</em></span> need to compile <span><strong class="command">named</strong></span> -statically nor install shared libraries under the new root. -However, depending on your operating system, you may need -to set up things like -<code class="filename">/dev/zero</code>, -<code class="filename">/dev/random</code>, -<code class="filename">/dev/log</code>, and -<code class="filename">/etc/localtime</code>. -</p> +<a name="id2592791"></a>The <span><strong class="command">chroot</strong></span> Environment</h3></div></div></div> +<p> + In order for a <span><strong class="command">chroot</strong></span> environment + to + work properly in a particular directory + (for example, <code class="filename">/var/named</code>), + you will need to set up an environment that includes everything + <acronym class="acronym">BIND</acronym> needs to run. + From <acronym class="acronym">BIND</acronym>'s point of view, <code class="filename">/var/named</code> is + the root of the filesystem. You will need to adjust the values of + options like + like <span><strong class="command">directory</strong></span> and <span><strong class="command">pid-file</strong></span> to account + for this. + </p> +<p> + Unlike with earlier versions of BIND, you typically will + <span class="emphasis"><em>not</em></span> need to compile <span><strong class="command">named</strong></span> + statically nor install shared libraries under the new root. + However, depending on your operating system, you may need + to set up things like + <code class="filename">/dev/zero</code>, + <code class="filename">/dev/random</code>, + <code class="filename">/dev/log</code>, and + <code class="filename">/etc/localtime</code>. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2592172"></a>Using the <span><strong class="command">setuid</strong></span> Function</h3></div></div></div> -<p>Prior to running the <span><strong class="command">named</strong></span> daemon, use -the <span><strong class="command">touch</strong></span> utility (to change file access and -modification times) or the <span><strong class="command">chown</strong></span> utility (to -set the user id and/or group id) on files -to which you want <acronym class="acronym">BIND</acronym> -to write. Note that if the <span><strong class="command">named</strong></span> daemon is running as an -unprivileged user, it will not be able to bind to new restricted ports if the -server is reloaded.</p> +<a name="id2592851"></a>Using the <span><strong class="command">setuid</strong></span> Function</h3></div></div></div> +<p> + Prior to running the <span><strong class="command">named</strong></span> daemon, + use + the <span><strong class="command">touch</strong></span> utility (to change file + access and + modification times) or the <span><strong class="command">chown</strong></span> + utility (to + set the user id and/or group id) on files + to which you want <acronym class="acronym">BIND</acronym> + to write. + </p> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<h3 class="title">Note</h3> + Note that if the <span><strong class="command">named</strong></span> daemon is running as an + unprivileged user, it will not be able to bind to new restricted + ports if the server is reloaded. + </div> </div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> <a name="dynamic_update_security"></a>Dynamic Update Security</h2></div></div></div> -<p>Access to the dynamic -update facility should be strictly limited. In earlier versions of -<acronym class="acronym">BIND</acronym>, the only way to do this was based on the IP -address of the host requesting the update, by listing an IP address or -network prefix in the <span><strong class="command">allow-update</strong></span> zone option. -This method is insecure since the source address of the update UDP packet -is easily forged. Also note that if the IP addresses allowed by the -<span><strong class="command">allow-update</strong></span> option include the address of a slave -server which performs forwarding of dynamic updates, the master can be -trivially attacked by sending the update to the slave, which will -forward it to the master with its own source IP address causing the -master to approve it without question.</p> -<p>For these reasons, we strongly recommend that updates be -cryptographically authenticated by means of transaction signatures -(TSIG). That is, the <span><strong class="command">allow-update</strong></span> option should -list only TSIG key names, not IP addresses or network -prefixes. Alternatively, the new <span><strong class="command">update-policy</strong></span> -option can be used.</p> -<p>Some sites choose to keep all dynamically-updated DNS data -in a subdomain and delegate that subdomain to a separate zone. This -way, the top-level zone containing critical data such as the IP addresses -of public web and mail servers need not allow dynamic update at -all.</p> +<p> + Access to the dynamic + update facility should be strictly limited. In earlier versions of + <acronym class="acronym">BIND</acronym>, the only way to do this was + based on the IP + address of the host requesting the update, by listing an IP address + or + network prefix in the <span><strong class="command">allow-update</strong></span> + zone option. + This method is insecure since the source address of the update UDP + packet + is easily forged. Also note that if the IP addresses allowed by the + <span><strong class="command">allow-update</strong></span> option include the + address of a slave + server which performs forwarding of dynamic updates, the master can + be + trivially attacked by sending the update to the slave, which will + forward it to the master with its own source IP address causing the + master to approve it without question. + </p> +<p> + For these reasons, we strongly recommend that updates be + cryptographically authenticated by means of transaction signatures + (TSIG). That is, the <span><strong class="command">allow-update</strong></span> + option should + list only TSIG key names, not IP addresses or network + prefixes. Alternatively, the new <span><strong class="command">update-policy</strong></span> + option can be used. + </p> +<p> + Some sites choose to keep all dynamically-updated DNS data + in a subdomain and delegate that subdomain to a separate zone. This + way, the top-level zone containing critical data such as the IP + addresses + of public web and mail servers need not allow dynamic update at + all. + </p> </div> </div> <div class="navfooter"> diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch08.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch08.html index a7a13219169..4b99b6793be 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch08.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch08.html @@ -1,5 +1,5 @@ <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - Permission to use, copy, modify, and distribute this software for any @@ -14,12 +14,12 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $ISC: Bv9ARM.ch08.html,v 1.50.2.9.2.33 2006/09/13 02:56:22 marka Exp $ --> +<!-- $ISC: Bv9ARM.ch08.html,v 1.75.18.64 2007/10/31 01:35:59 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Chapter 8. Troubleshooting</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="prev" href="Bv9ARM.ch07.html" title="Chapter 7. BIND 9 Security Considerations"> @@ -45,62 +45,77 @@ <div class="toc"> <p><b>Table of Contents</b></p> <dl> -<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2592243">Common Problems</a></span></dt> -<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2592248">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2592260">Incrementing and Changing the Serial Number</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2592277">Where Can I Get Help?</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2592999">Common Problems</a></span></dt> +<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2593004">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd> +<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2593016">Incrementing and Changing the Serial Number</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2593033">Where Can I Get Help?</a></span></dt> </dl> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2592243"></a>Common Problems</h2></div></div></div> +<a name="id2592999"></a>Common Problems</h2></div></div></div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2592248"></a>It's not working; how can I figure out what's wrong?</h3></div></div></div> -<p>The best solution to solving installation and - configuration issues is to take preventative measures by setting - up logging files beforehand. The log files provide a - source of hints and information that can be used to figure out - what went wrong and how to fix the problem.</p> +<a name="id2593004"></a>It's not working; how can I figure out what's wrong?</h3></div></div></div> +<p> + The best solution to solving installation and + configuration issues is to take preventative measures by setting + up logging files beforehand. The log files provide a + source of hints and information that can be used to figure out + what went wrong and how to fix the problem. + </p> </div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2592260"></a>Incrementing and Changing the Serial Number</h2></div></div></div> -<p>Zone serial numbers are just numbers-they aren't date - related. A lot of people set them to a number that represents a - date, usually of the form YYYYMMDDRR. A number of people have been - testing these numbers for Y2K compliance and have set the number - to the year 2000 to see if it will work. They then try to restore - the old serial number. This will cause problems because serial - numbers are used to indicate that a zone has been updated. If the - serial number on the slave server is lower than the serial number - on the master, the slave server will attempt to update its copy of - the zone.</p> -<p>Setting the serial number to a lower number on the master - server than the slave server means that the slave will not perform - updates to its copy of the zone.</p> -<p>The solution to this is to add 2147483647 (2^31-1) to the - number, reload the zone and make sure all slaves have updated to - the new zone serial number, then reset the number to what you want - it to be, and reload the zone again.</p> +<a name="id2593016"></a>Incrementing and Changing the Serial Number</h2></div></div></div> +<p> + Zone serial numbers are just numbers — they aren't + date related. A lot of people set them to a number that + represents a date, usually of the form YYYYMMDDRR. + Occasionally they will make a mistake and set them to a + "date in the future" then try to correct them by setting + them to the "current date". This causes problems because + serial numbers are used to indicate that a zone has been + updated. If the serial number on the slave server is + lower than the serial number on the master, the slave + server will attempt to update its copy of the zone. + </p> +<p> + Setting the serial number to a lower number on the master + server than the slave server means that the slave will not perform + updates to its copy of the zone. + </p> +<p> + The solution to this is to add 2147483647 (2^31-1) to the + number, reload the zone and make sure all slaves have updated to + the new zone serial number, then reset the number to what you want + it to be, and reload the zone again. + </p> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2592277"></a>Where Can I Get Help?</h2></div></div></div> -<p>The Internet Software Consortium (<acronym class="acronym">ISC</acronym>) offers a wide range - of support and service agreements for <acronym class="acronym">BIND</acronym> and <acronym class="acronym">DHCP</acronym> servers. Four - levels of premium support are available and each level includes - support for all <acronym class="acronym">ISC</acronym> programs, significant discounts on products - and training, and a recognized priority on bug fixes and - non-funded feature requests. In addition, <acronym class="acronym">ISC</acronym> offers a standard - support agreement package which includes services ranging from bug - fix announcements to remote support. It also includes training in - <acronym class="acronym">BIND</acronym> and <acronym class="acronym">DHCP</acronym>.</p> -<p>To discuss arrangements for support, contact - <a href="mailto:info@isc.org" target="_top">info@isc.org</a> or visit the - <acronym class="acronym">ISC</acronym> web page at <a href="http://www.isc.org/services/support/" target="_top">http://www.isc.org/services/support/</a> - to read more.</p> +<a name="id2593033"></a>Where Can I Get Help?</h2></div></div></div> +<p> + The Internet Systems Consortium + (<acronym class="acronym">ISC</acronym>) offers a wide range + of support and service agreements for <acronym class="acronym">BIND</acronym> and <acronym class="acronym">DHCP</acronym> servers. Four + levels of premium support are available and each level includes + support for all <acronym class="acronym">ISC</acronym> programs, + significant discounts on products + and training, and a recognized priority on bug fixes and + non-funded feature requests. In addition, <acronym class="acronym">ISC</acronym> offers a standard + support agreement package which includes services ranging from bug + fix announcements to remote support. It also includes training in + <acronym class="acronym">BIND</acronym> and <acronym class="acronym">DHCP</acronym>. + </p> +<p> + To discuss arrangements for support, contact + <a href="mailto:info@isc.org" target="_top">info@isc.org</a> or visit the + <acronym class="acronym">ISC</acronym> web page at + <a href="http://www.isc.org/services/support/" target="_top">http://www.isc.org/services/support/</a> + to read more. + </p> </div> </div> <div class="navfooter"> diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch09.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch09.html index d16593604cc..783224f9772 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch09.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch09.html @@ -1,5 +1,5 @@ <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - Permission to use, copy, modify, and distribute this software for any @@ -14,15 +14,16 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $ISC: Bv9ARM.ch09.html,v 1.50.2.9.2.35 2006/11/15 04:33:42 marka Exp $ --> +<!-- $ISC: Bv9ARM.ch09.html,v 1.75.18.66 2007/10/31 01:35:59 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>Appendix A. Appendices</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> <link rel="prev" href="Bv9ARM.ch08.html" title="Chapter 8. Troubleshooting"> +<link rel="next" href="Bv9ARM.ch10.html" title="Manual pages"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <div class="navheader"> @@ -32,7 +33,8 @@ <td width="20%" align="left"> <a accesskey="p" href="Bv9ARM.ch08.html">Prev</a> </td> <th width="60%" align="center"> </th> -<td width="20%" align="right"> </td> +<td width="20%" align="right"> <a accesskey="n" href="Bv9ARM.ch10.html">Next</a> +</td> </tr> </table> <hr> @@ -43,205 +45,183 @@ <div class="toc"> <p><b>Table of Contents</b></p> <dl> -<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2592339">Acknowledgments</a></span></dt> -<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2592344">A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></a></span></dt></dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch09.html#historical_dns_information">General <acronym class="acronym">DNS</acronym> Reference Information</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2593300">Acknowledgments</a></span></dt> +<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#historical_dns_information">A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></a></span></dt></dl></dd> +<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2593472">General <acronym class="acronym">DNS</acronym> Reference Information</a></span></dt> <dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt></dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch09.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="Bv9ARM.ch09.html#rfcs">Request for Comments (RFCs)</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch09.html#internet_drafts">Internet Drafts</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2594702">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2596683">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt> </dl></dd> </dl> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="id2592339"></a>Acknowledgments</h2></div></div></div> +<a name="id2593300"></a>Acknowledgments</h2></div></div></div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2592344"></a>A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></h3></div></div></div> -<p>Although the "official" beginning of the Domain Name - System occurred in 1984 with the publication of RFC 920, the - core of the new system was described in 1983 in RFCs 882 and - 883. From 1984 to 1987, the ARPAnet (the precursor to today's - Internet) became a testbed of experimentation for developing the - new naming/addressing scheme in a rapidly expanding, - operational network environment. New RFCs were written and - published in 1987 that modified the original documents to - incorporate improvements based on the working model. RFC 1034, - "Domain Names-Concepts and Facilities", and RFC 1035, "Domain - Names-Implementation and Specification" were published and - became the standards upon which all <acronym class="acronym">DNS</acronym> implementations are - built. -</p> -<p>The first working domain name server, called "Jeeves", was -written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20 -machines located at the University of Southern California's Information -Sciences Institute (USC-ISI) and SRI International's Network Information -Center (SRI-NIC). A <acronym class="acronym">DNS</acronym> server for Unix machines, the Berkeley Internet -Name Domain (<acronym class="acronym">BIND</acronym>) package, was written soon after by a group of -graduate students at the University of California at Berkeley under -a grant from the US Defense Advanced Research Projects Administration -(DARPA). -</p> +<a name="historical_dns_information"></a>A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym> +</h3></div></div></div> <p> -Versions of <acronym class="acronym">BIND</acronym> through 4.8.3 were maintained by the Computer -Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark -Painter, David Riggle and Songnian Zhou made up the initial <acronym class="acronym">BIND</acronym> -project team. After that, additional work on the software package -was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation -employee on loan to the CSRG, worked on <acronym class="acronym">BIND</acronym> for 2 years, from 1985 -to 1987. Many other people also contributed to <acronym class="acronym">BIND</acronym> development -during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell, -Mike Muuss, Jim Bloom and Mike Schwartz. <acronym class="acronym">BIND</acronym> maintenance was subsequently -handled by Mike Karels and O. Kure.</p> -<p><acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were released by Digital Equipment -Corporation (now Compaq Computer Corporation). Paul Vixie, then -a DEC employee, became <acronym class="acronym">BIND</acronym>'s primary caretaker. He was assisted -by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew -Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat -Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe -Wolfhugel, and others.</p> -<p><acronym class="acronym">BIND</acronym> version 4.9.2 was sponsored by Vixie Enterprises. Paul -Vixie became <acronym class="acronym">BIND</acronym>'s principal architect/programmer.</p> -<p><acronym class="acronym">BIND</acronym> versions from 4.9.3 onward have been developed and maintained -by the Internet Software Consortium with support being provided -by ISC's sponsors. As co-architects/programmers, Bob Halley and -Paul Vixie released the first production-ready version of <acronym class="acronym">BIND</acronym> version -8 in May 1997.</p> -<p><acronym class="acronym">BIND</acronym> development work is made possible today by the sponsorship -of several corporations, and by the tireless work efforts of numerous -individuals.</p> + Although the "official" beginning of the Domain Name + System occurred in 1984 with the publication of RFC 920, the + core of the new system was described in 1983 in RFCs 882 and + 883. From 1984 to 1987, the ARPAnet (the precursor to today's + Internet) became a testbed of experimentation for developing the + new naming/addressing scheme in a rapidly expanding, + operational network environment. New RFCs were written and + published in 1987 that modified the original documents to + incorporate improvements based on the working model. RFC 1034, + "Domain Names-Concepts and Facilities", and RFC 1035, "Domain + Names-Implementation and Specification" were published and + became the standards upon which all <acronym class="acronym">DNS</acronym> implementations are + built. + </p> +<p> + The first working domain name server, called "Jeeves", was + written in 1983-84 by Paul Mockapetris for operation on DEC + Tops-20 + machines located at the University of Southern California's + Information + Sciences Institute (USC-ISI) and SRI International's Network + Information + Center (SRI-NIC). A <acronym class="acronym">DNS</acronym> server for + Unix machines, the Berkeley Internet + Name Domain (<acronym class="acronym">BIND</acronym>) package, was + written soon after by a group of + graduate students at the University of California at Berkeley + under + a grant from the US Defense Advanced Research Projects + Administration + (DARPA). + </p> +<p> + Versions of <acronym class="acronym">BIND</acronym> through + 4.8.3 were maintained by the Computer + Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark + Painter, David Riggle and Songnian Zhou made up the initial <acronym class="acronym">BIND</acronym> + project team. After that, additional work on the software package + was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment + Corporation + employee on loan to the CSRG, worked on <acronym class="acronym">BIND</acronym> for 2 years, from 1985 + to 1987. Many other people also contributed to <acronym class="acronym">BIND</acronym> development + during that time: Doug Kingston, Craig Partridge, Smoot + Carl-Mitchell, + Mike Muuss, Jim Bloom and Mike Schwartz. <acronym class="acronym">BIND</acronym> maintenance was subsequently + handled by Mike Karels and Øivind Kure. + </p> +<p> + <acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were + released by Digital Equipment + Corporation (now Compaq Computer Corporation). Paul Vixie, then + a DEC employee, became <acronym class="acronym">BIND</acronym>'s + primary caretaker. He was assisted + by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan + Beecher, Andrew + Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat + Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe + Wolfhugel, and others. + </p> +<p> + In 1994, <acronym class="acronym">BIND</acronym> version 4.9.2 was sponsored by + Vixie Enterprises. Paul + Vixie became <acronym class="acronym">BIND</acronym>'s principal + architect/programmer. + </p> +<p> + <acronym class="acronym">BIND</acronym> versions from 4.9.3 onward + have been developed and maintained + by the Internet Systems Consortium and its predecessor, + the Internet Software Consortium, with support being provided + by ISC's sponsors. + </p> +<p> + As co-architects/programmers, Bob Halley and + Paul Vixie released the first production-ready version of + <acronym class="acronym">BIND</acronym> version 8 in May 1997. + </p> +<p> + BIND version 9 was released in September 2000 and is a + major rewrite of nearly all aspects of the underlying + BIND architecture. + </p> +<p> + BIND version 4 is officially deprecated and BIND version + 8 development is considered maintenance-only in favor + of BIND version 9. No additional development is done + on BIND version 4 or BIND version 8 other than for + security-related patches. + </p> +<p> + <acronym class="acronym">BIND</acronym> development work is made + possible today by the sponsorship + of several corporations, and by the tireless work efforts of + numerous individuals. + </p> </div> </div> <div class="sect1" lang="en"> <div class="titlepage"><div><div><h2 class="title" style="clear: both"> -<a name="historical_dns_information"></a>General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div> +<a name="id2593472"></a>General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h3></div></div></div> -<p>IPv6 addresses are 128-bit identifiers for interfaces and -sets of interfaces which were introduced in the <acronym class="acronym">DNS</acronym> to facilitate -scalable Internet routing. There are three types of addresses: <span class="emphasis"><em>Unicast</em></span>, -an identifier for a single interface; <span class="emphasis"><em>Anycast</em></span>, -an identifier for a set of interfaces; and <span class="emphasis"><em>Multicast</em></span>, -an identifier for a set of interfaces. Here we describe the global -Unicast address scheme. For more information, see RFC 2374.</p> -<p>The aggregatable global Unicast address format is as follows:</p> -<div class="informaltable"><table border="1"> -<colgroup> -<col> -<col> -<col> -<col> -<col> -<col> -</colgroup> -<tbody> -<tr> -<td><p>3</p></td> -<td><p>13</p></td> -<td><p>8</p></td> -<td><p>24</p></td> -<td><p>16</p></td> -<td><p>64 bits</p></td> -</tr> -<tr> -<td><p>FP</p></td> -<td><p>TLA ID</p></td> -<td><p>RES</p></td> -<td><p>NLA ID</p></td> -<td><p>SLA ID</p></td> -<td><p>Interface ID</p></td> -</tr> -<tr> -<td colspan="4"><p><------ Public Topology -------></p></td> -<td><p></p></td> -<td><p></p></td> -</tr> -<tr> -<td><p></p></td> -<td><p></p></td> -<td><p></p></td> -<td><p></p></td> -<td><p><-Site Topology-></p></td> -<td><p></p></td> -</tr> -<tr> -<td><p></p></td> -<td><p></p></td> -<td><p></p></td> -<td><p></p></td> -<td><p></p></td> -<td><p><------ Interface Identifier ------></p></td> -</tr> -</tbody> -</table></div> -<p>Where -</p> -<div class="informaltable"><table border="1"> -<colgroup> -<col> -<col> -<col> -</colgroup> -<tbody> -<tr> -<td><p>FP</p></td> -<td><p>=</p></td> -<td><p>Format Prefix (001)</p></td> -</tr> -<tr> -<td><p>TLA ID</p></td> -<td><p>=</p></td> -<td><p>Top-Level Aggregation Identifier</p></td> -</tr> -<tr> -<td><p>RES</p></td> -<td><p>=</p></td> -<td><p>Reserved for future use</p></td> -</tr> -<tr> -<td><p>NLA ID</p></td> -<td><p>=</p></td> -<td><p>Next-Level Aggregation Identifier</p></td> -</tr> -<tr> -<td><p>SLA ID</p></td> -<td><p>=</p></td> -<td><p>Site-Level Aggregation Identifier</p></td> -</tr> -<tr> -<td><p>INTERFACE ID</p></td> -<td><p>=</p></td> -<td><p>Interface Identifier</p></td> -</tr> -</tbody> -</table></div> -<p>The <span class="emphasis"><em>Public Topology</em></span> is provided by the -upstream provider or ISP, and (roughly) corresponds to the IPv4 <span class="emphasis"><em>network</em></span> section -of the address range. The <span class="emphasis"><em>Site Topology</em></span> is -where you can subnet this space, much the same as subnetting an -IPv4 /16 network into /24 subnets. The <span class="emphasis"><em>Interface Identifier</em></span> is -the address of an individual interface on a given network. (With -IPv6, addresses belong to interfaces rather than machines.)</p> -<p>The subnetting capability of IPv6 is much more flexible than -that of IPv4: subnetting can now be carried out on bit boundaries, -in much the same way as Classless InterDomain Routing (CIDR).</p> -<p>The Interface Identifier must be unique on that network. On -ethernet networks, one way to ensure this is to set the address -to the first three bytes of the hardware address, "FFFE", then the -last three bytes of the hardware address. The lowest significant -bit of the first byte should then be complemented. Addresses are -written as 32-bit blocks separated with a colon, and leading zeros -of a block may be omitted, for example:</p> -<p><span><strong class="command">2001:db8:201:9:a00:20ff:fe81:2b32</strong></span></p> -<p>IPv6 address specifications are likely to contain long strings -of zeros, so the architects have included a shorthand for specifying -them. The double colon (`::') indicates the longest possible string -of zeros that can fit, and can be used only once in an address.</p> +<p> + IPv6 addresses are 128-bit identifiers for interfaces and + sets of interfaces which were introduced in the <acronym class="acronym">DNS</acronym> to facilitate + scalable Internet routing. There are three types of addresses: <span class="emphasis"><em>Unicast</em></span>, + an identifier for a single interface; + <span class="emphasis"><em>Anycast</em></span>, + an identifier for a set of interfaces; and <span class="emphasis"><em>Multicast</em></span>, + an identifier for a set of interfaces. Here we describe the global + Unicast address scheme. For more information, see RFC 3587, + "Global Unicast Address Format." + </p> +<p> + IPv6 unicast addresses consist of a + <span class="emphasis"><em>global routing prefix</em></span>, a + <span class="emphasis"><em>subnet identifier</em></span>, and an + <span class="emphasis"><em>interface identifier</em></span>. + </p> +<p> + The global routing prefix is provided by the + upstream provider or ISP, and (roughly) corresponds to the + IPv4 <span class="emphasis"><em>network</em></span> section + of the address range. + + The subnet identifier is for local subnetting, much the + same as subnetting an + IPv4 /16 network into /24 subnets. + + The interface identifier is the address of an individual + interface on a given network; in IPv6, addresses belong to + interfaces rather than to machines. + </p> +<p> + The subnetting capability of IPv6 is much more flexible than + that of IPv4: subnetting can be carried out on bit boundaries, + in much the same way as Classless InterDomain Routing + (CIDR), and the DNS PTR representation ("nibble" format) + makes setting up reverse zones easier. + </p> +<p> + The Interface Identifier must be unique on the local link, + and is usually generated automatically by the IPv6 + implementation, although it is usually possible to + override the default setting if necessary. A typical IPv6 + address might look like: + <span><strong class="command">2001:db8:201:9:a00:20ff:fe81:2b32</strong></span> + </p> +<p> + IPv6 address specifications often contain long strings + of zeros, so the architects have included a shorthand for + specifying + them. The double colon (`::') indicates the longest possible + string + of zeros that can fit, and can be used only once in an address. + </p> </div> </div> <div class="sect1" lang="en"> @@ -250,173 +230,352 @@ of zeros that can fit, and can be used only once in an address.</p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="rfcs"></a>Request for Comments (RFCs)</h3></div></div></div> -<p>Specification documents for the Internet protocol suite, including -the <acronym class="acronym">DNS</acronym>, are published as part of the Request for Comments (RFCs) -series of technical notes. The standards themselves are defined -by the Internet Engineering Task Force (IETF) and the Internet Engineering -Steering Group (IESG). RFCs can be obtained online via FTP at -<a href="ftp://www.isi.edu/in-notes/" target="_top">ftp://www.isi.edu/in-notes/RFC<em class="replaceable"><code>xxx</code></em>.txt</a> (where <em class="replaceable"><code>xxx</code></em> is -the number of the RFC). RFCs are also available via the Web at -<a href="http://www.ietf.org/rfc/" target="_top">http://www.ietf.org/rfc/</a>. -</p> +<p> + Specification documents for the Internet protocol suite, including + the <acronym class="acronym">DNS</acronym>, are published as part of + the Request for Comments (RFCs) + series of technical notes. The standards themselves are defined + by the Internet Engineering Task Force (IETF) and the Internet + Engineering Steering Group (IESG). RFCs can be obtained online via FTP at: + </p> +<p> + <a href="ftp://www.isi.edu/in-notes/" target="_top"> + ftp://www.isi.edu/in-notes/RFC<em class="replaceable"><code>xxxx</code></em>.txt + </a> + </p> +<p> + (where <em class="replaceable"><code>xxxx</code></em> is + the number of the RFC). RFCs are also available via the Web at: + </p> +<p> + <a href="http://www.ietf.org/rfc/" target="_top">http://www.ietf.org/rfc/</a>. + </p> <div class="bibliography"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2593259"></a>Bibliography</h4></div></div></div> +<a name="id2593659"></a>Bibliography</h4></div></div></div> <div class="bibliodiv"> <h3 class="title">Standards</h3> <div class="biblioentry"> -<a name="id2593270"></a><p>[<abbr class="abbrev">RFC974</abbr>] <span class="author"><span class="firstname">C.</span> <span class="surname">Partridge</span>. </span><span class="title"><i>Mail Routing and the Domain System</i>. </span><span class="pubdate">January 1986. </span></p> +<a name="id2593670"></a><p>[<abbr class="abbrev">RFC974</abbr>] <span class="author"><span class="firstname">C.</span> <span class="surname">Partridge</span>. </span><span class="title"><i>Mail Routing and the Domain System</i>. </span><span class="pubdate">January 1986. </span></p> </div> <div class="biblioentry"> -<a name="id2593293"></a><p>[<abbr class="abbrev">RFC1034</abbr>] <span class="author"><span class="firstname">P.V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names — Concepts and Facilities</i>. </span><span class="pubdate">November 1987. </span></p> +<a name="id2593693"></a><p>[<abbr class="abbrev">RFC1034</abbr>] <span class="author"><span class="firstname">P.V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names — Concepts and Facilities</i>. </span><span class="pubdate">November 1987. </span></p> </div> <div class="biblioentry"> -<a name="id2593317"></a><p>[<abbr class="abbrev">RFC1035</abbr>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names — Implementation and -Specification</i>. </span><span class="pubdate">November 1987. </span></p> +<a name="id2593717"></a><p>[<abbr class="abbrev">RFC1035</abbr>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names — Implementation and + Specification</i>. </span><span class="pubdate">November 1987. </span></p> </div> </div> <div class="bibliodiv"> <h3 class="title"> <a name="proposed_standards"></a>Proposed Standards</h3> <div class="biblioentry"> -<a name="id2593354"></a><p>[<abbr class="abbrev">RFC2181</abbr>] <span class="author"><span class="firstname">R., R. Bush</span> <span class="surname">Elz</span>. </span><span class="title"><i>Clarifications to the <acronym class="acronym">DNS</acronym> Specification</i>. </span><span class="pubdate">July 1997. </span></p> +<a name="id2593753"></a><p>[<abbr class="abbrev">RFC2181</abbr>] <span class="author"><span class="firstname">R., R. Bush</span> <span class="surname">Elz</span>. </span><span class="title"><i>Clarifications to the <acronym class="acronym">DNS</acronym> + Specification</i>. </span><span class="pubdate">July 1997. </span></p> +</div> +<div class="biblioentry"> +<a name="id2593780"></a><p>[<abbr class="abbrev">RFC2308</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Andrews</span>. </span><span class="title"><i>Negative Caching of <acronym class="acronym">DNS</acronym> + Queries</i>. </span><span class="pubdate">March 1998. </span></p> +</div> +<div class="biblioentry"> +<a name="id2593805"></a><p>[<abbr class="abbrev">RFC1995</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Ohta</span>. </span><span class="title"><i>Incremental Zone Transfer in <acronym class="acronym">DNS</acronym></i>. </span><span class="pubdate">August 1996. </span></p> +</div> +<div class="biblioentry"> +<a name="id2593830"></a><p>[<abbr class="abbrev">RFC1996</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>A Mechanism for Prompt Notification of Zone Changes</i>. </span><span class="pubdate">August 1996. </span></p> +</div> +<div class="biblioentry"> +<a name="id2593853"></a><p>[<abbr class="abbrev">RFC2136</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">Y.</span> <span class="surname">Rekhter</span>, and <span class="firstname">J.</span> <span class="surname">Bound</span>. </span><span class="title"><i>Dynamic Updates in the Domain Name System</i>. </span><span class="pubdate">April 1997. </span></p> +</div> +<div class="biblioentry"> +<a name="id2593909"></a><p>[<abbr class="abbrev">RFC2671</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Extension Mechanisms for DNS (EDNS0)</i>. </span><span class="pubdate">August 1997. </span></p> +</div> +<div class="biblioentry"> +<a name="id2593936"></a><p>[<abbr class="abbrev">RFC2672</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span>. </span><span class="title"><i>Non-Terminal DNS Name Redirection</i>. </span><span class="pubdate">August 1999. </span></p> </div> <div class="biblioentry"> -<a name="id2593380"></a><p>[<abbr class="abbrev">RFC2308</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Andrews</span>. </span><span class="title"><i>Negative Caching of <acronym class="acronym">DNS</acronym> Queries</i>. </span><span class="pubdate">March 1998. </span></p> +<a name="id2593962"></a><p>[<abbr class="abbrev">RFC2845</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>, <span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, and <span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Secret Key Transaction Authentication for <acronym class="acronym">DNS</acronym> (TSIG)</i>. </span><span class="pubdate">May 2000. </span></p> </div> <div class="biblioentry"> -<a name="id2593405"></a><p>[<abbr class="abbrev">RFC1995</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Ohta</span>. </span><span class="title"><i>Incremental Zone Transfer in <acronym class="acronym">DNS</acronym></i>. </span><span class="pubdate">August 1996. </span></p> +<a name="id2594024"></a><p>[<abbr class="abbrev">RFC2930</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Secret Key Establishment for DNS (TKEY RR)</i>. </span><span class="pubdate">September 2000. </span></p> </div> <div class="biblioentry"> -<a name="id2593430"></a><p>[<abbr class="abbrev">RFC1996</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>A Mechanism for Prompt Notification of Zone Changes</i>. </span><span class="pubdate">August 1996. </span></p> +<a name="id2594054"></a><p>[<abbr class="abbrev">RFC2931</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>DNS Request and Transaction Signatures (SIG(0)s)</i>. </span><span class="pubdate">September 2000. </span></p> </div> <div class="biblioentry"> -<a name="id2593522"></a><p>[<abbr class="abbrev">RFC2136</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">Y.</span> <span class="surname">Rekhter</span>, and <span class="firstname">J.</span> <span class="surname">Bound</span>. </span><span class="title"><i>Dynamic Updates in the Domain Name System</i>. </span><span class="pubdate">April 1997. </span></p> +<a name="id2594084"></a><p>[<abbr class="abbrev">RFC3007</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Secure Domain Name System (DNS) Dynamic Update</i>. </span><span class="pubdate">November 2000. </span></p> </div> <div class="biblioentry"> -<a name="id2593577"></a><p>[<abbr class="abbrev">RFC2845</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>, <span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, and <span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Secret Key Transaction Authentication for <acronym class="acronym">DNS</acronym> (TSIG)</i>. </span><span class="pubdate">May 2000. </span></p> +<a name="id2594110"></a><p>[<abbr class="abbrev">RFC3645</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Kwan</span>, <span class="firstname">P.</span> <span class="surname">Garg</span>, <span class="firstname">J.</span> <span class="surname">Gilroy</span>, <span class="firstname">L.</span> <span class="surname">Esibov</span>, <span class="firstname">J.</span> <span class="surname">Westhead</span>, and <span class="firstname">R.</span> <span class="surname">Hall</span>. </span><span class="title"><i>Generic Security Service Algorithm for Secret + Key Transaction Authentication for DNS + (GSS-TSIG)</i>. </span><span class="pubdate">October 2003. </span></p> </div> </div> <div class="bibliodiv"> -<h3 class="title">Proposed Standards Still Under Development</h3> -<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> -<h3 class="title">Note</h3> -<p><span class="emphasis"><em>Note:</em></span> the following list of -RFCs are undergoing major revision by the IETF.</p> +<h3 class="title"> +<acronym class="acronym">DNS</acronym> Security Proposed Standards</h3> +<div class="biblioentry"> +<a name="id2594193"></a><p>[<abbr class="abbrev">RFC3225</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Conrad</span>. </span><span class="title"><i>Indicating Resolver Support of DNSSEC</i>. </span><span class="pubdate">December 2001. </span></p> </div> <div class="biblioentry"> -<a name="id2593653"></a><p>[<abbr class="abbrev">RFC1886</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Thomson</span> and <span class="firstname">C.</span> <span class="surname">Huitema</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Extensions to support IP version 6</i>. </span><span class="pubdate">December 1995. </span></p> +<a name="id2594288"></a><p>[<abbr class="abbrev">RFC3833</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Atkins</span> and <span class="firstname">R.</span> <span class="surname">Austein</span>. </span><span class="title"><i>Threat Analysis of the Domain Name System (DNS)</i>. </span><span class="pubdate">August 2004. </span></p> </div> <div class="biblioentry"> -<a name="id2593691"></a><p>[<abbr class="abbrev">RFC2065</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">C.</span> <span class="surname">Kaufman</span>. </span><span class="title"><i>Domain Name System Security Extensions</i>. </span><span class="pubdate">January 1997. </span></p> +<a name="id2594324"></a><p>[<abbr class="abbrev">RFC4033</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>DNS Security Introduction and Requirements</i>. </span><span class="pubdate">March 2005. </span></p> </div> <div class="biblioentry"> -<a name="id2593731"></a><p>[<abbr class="abbrev">RFC2137</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Secure Domain Name System Dynamic Update</i>. </span><span class="pubdate">April 1997. </span></p> +<a name="id2594389"></a><p>[<abbr class="abbrev">RFC4044</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Resource Records for the DNS Security Extensions</i>. </span><span class="pubdate">March 2005. </span></p> +</div> +<div class="biblioentry"> +<a name="id2594454"></a><p>[<abbr class="abbrev">RFC4035</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Protocol Modifications for the DNS + Security Extensions</i>. </span><span class="pubdate">March 2005. </span></p> </div> </div> <div class="bibliodiv"> -<h3 class="title">Other Important RFCs About <acronym class="acronym">DNS</acronym> Implementation</h3> +<h3 class="title">Other Important RFCs About <acronym class="acronym">DNS</acronym> + Implementation</h3> +<div class="biblioentry"> +<a name="id2594596"></a><p>[<abbr class="abbrev">RFC1535</abbr>] <span class="author"><span class="firstname">E.</span> <span class="surname">Gavron</span>. </span><span class="title"><i>A Security Problem and Proposed Correction With Widely + Deployed <acronym class="acronym">DNS</acronym> Software.</i>. </span><span class="pubdate">October 1993. </span></p> +</div> <div class="biblioentry"> -<a name="id2593767"></a><p>[<abbr class="abbrev">RFC1535</abbr>] <span class="author"><span class="firstname">E.</span> <span class="surname">Gavron</span>. </span><span class="title"><i>A Security Problem and Proposed Correction With Widely Deployed <acronym class="acronym">DNS</acronym> Software.</i>. </span><span class="pubdate">October 1993. </span></p> +<a name="id2594621"></a><p>[<abbr class="abbrev">RFC1536</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Kumar</span>, <span class="firstname">J.</span> <span class="surname">Postel</span>, <span class="firstname">C.</span> <span class="surname">Neuman</span>, <span class="firstname">P.</span> <span class="surname">Danzig</span>, and <span class="firstname">S.</span> <span class="surname">Miller</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Implementation + Errors and Suggested Fixes</i>. </span><span class="pubdate">October 1993. </span></p> </div> <div class="biblioentry"> -<a name="id2593793"></a><p>[<abbr class="abbrev">RFC1536</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Kumar</span>, <span class="firstname">J.</span> <span class="surname">Postel</span>, <span class="firstname">C.</span> <span class="surname">Neuman</span>, <span class="firstname">P.</span> <span class="surname">Danzig</span>, and <span class="firstname">S.</span> <span class="surname">Miller</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Implementation Errors and Suggested Fixes</i>. </span><span class="pubdate">October 1993. </span></p> +<a name="id2594690"></a><p>[<abbr class="abbrev">RFC1982</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Elz</span> and <span class="firstname">R.</span> <span class="surname">Bush</span>. </span><span class="title"><i>Serial Number Arithmetic</i>. </span><span class="pubdate">August 1996. </span></p> </div> <div class="biblioentry"> -<a name="id2593860"></a><p>[<abbr class="abbrev">RFC1982</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Elz</span> and <span class="firstname">R.</span> <span class="surname">Bush</span>. </span><span class="title"><i>Serial Number Arithmetic</i>. </span><span class="pubdate">August 1996. </span></p> +<a name="id2594725"></a><p>[<abbr class="abbrev">RFC4074</abbr>] <span class="authorgroup"><span class="firstname">Y.</span> <span class="surname">Morishita</span> and <span class="firstname">T.</span> <span class="surname">Jinmei</span>. </span><span class="title"><i>Common Misbehaviour Against <acronym class="acronym">DNS</acronym> + Queries for IPv6 Addresses</i>. </span><span class="pubdate">May 2005. </span></p> </div> </div> <div class="bibliodiv"> <h3 class="title">Resource Record Types</h3> <div class="biblioentry"> -<a name="id2593901"></a><p>[<abbr class="abbrev">RFC1183</abbr>] <span class="authorgroup"><span class="firstname">C.F.</span> <span class="surname">Everhart</span>, <span class="firstname">L. A.</span> <span class="surname">Mamakos</span>, <span class="firstname">R.</span> <span class="surname">Ullmann</span>, and <span class="firstname">P.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>New <acronym class="acronym">DNS</acronym> RR Definitions</i>. </span><span class="pubdate">October 1990. </span></p> +<a name="id2594771"></a><p>[<abbr class="abbrev">RFC1183</abbr>] <span class="authorgroup"><span class="firstname">C.F.</span> <span class="surname">Everhart</span>, <span class="firstname">L. A.</span> <span class="surname">Mamakos</span>, <span class="firstname">R.</span> <span class="surname">Ullmann</span>, and <span class="firstname">P.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>New <acronym class="acronym">DNS</acronym> RR Definitions</i>. </span><span class="pubdate">October 1990. </span></p> </div> <div class="biblioentry"> -<a name="id2593959"></a><p>[<abbr class="abbrev">RFC1706</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">R.</span> <span class="surname">Colella</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> NSAP Resource Records</i>. </span><span class="pubdate">October 1994. </span></p> +<a name="id2594828"></a><p>[<abbr class="abbrev">RFC1706</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">R.</span> <span class="surname">Colella</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> NSAP Resource Records</i>. </span><span class="pubdate">October 1994. </span></p> </div> <div class="biblioentry"> -<a name="id2593996"></a><p>[<abbr class="abbrev">RFC2168</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Daniel</span> and <span class="firstname">M.</span> <span class="surname">Mealling</span>. </span><span class="title"><i>Resolution of Uniform Resource Identifiers using -the Domain Name System</i>. </span><span class="pubdate">June 1997. </span></p> +<a name="id2594866"></a><p>[<abbr class="abbrev">RFC2168</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Daniel</span> and <span class="firstname">M.</span> <span class="surname">Mealling</span>. </span><span class="title"><i>Resolution of Uniform Resource Identifiers using + the Domain Name System</i>. </span><span class="pubdate">June 1997. </span></p> </div> <div class="biblioentry"> -<a name="id2594032"></a><p>[<abbr class="abbrev">RFC1876</abbr>] <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Davis</span>, <span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">T.</span>, and <span class="firstname">I.</span> <span class="surname">Dickinson</span>. </span><span class="title"><i>A Means for Expressing Location Information in the Domain -Name System</i>. </span><span class="pubdate">January 1996. </span></p> +<a name="id2594901"></a><p>[<abbr class="abbrev">RFC1876</abbr>] <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Davis</span>, <span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">T.</span>, and <span class="firstname">I.</span> <span class="surname">Dickinson</span>. </span><span class="title"><i>A Means for Expressing Location Information in the + Domain + Name System</i>. </span><span class="pubdate">January 1996. </span></p> </div> <div class="biblioentry"> -<a name="id2594086"></a><p>[<abbr class="abbrev">RFC2052</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>A <acronym class="acronym">DNS</acronym> RR for Specifying the Location of -Services.</i>. </span><span class="pubdate">October 1996. </span></p> +<a name="id2594955"></a><p>[<abbr class="abbrev">RFC2052</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>A <acronym class="acronym">DNS</acronym> RR for Specifying the + Location of + Services.</i>. </span><span class="pubdate">October 1996. </span></p> </div> <div class="biblioentry"> -<a name="id2594125"></a><p>[<abbr class="abbrev">RFC2163</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Allocchio</span>. </span><span class="title"><i>Using the Internet <acronym class="acronym">DNS</acronym> to Distribute MIXER -Conformant Global Address Mapping</i>. </span><span class="pubdate">January 1998. </span></p> +<a name="id2594994"></a><p>[<abbr class="abbrev">RFC2163</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Allocchio</span>. </span><span class="title"><i>Using the Internet <acronym class="acronym">DNS</acronym> to + Distribute MIXER + Conformant Global Address Mapping</i>. </span><span class="pubdate">January 1998. </span></p> </div> <div class="biblioentry"> -<a name="id2594152"></a><p>[<abbr class="abbrev">RFC2230</abbr>] <span class="author"><span class="firstname">R.</span> <span class="surname">Atkinson</span>. </span><span class="title"><i>Key Exchange Delegation Record for the <acronym class="acronym">DNS</acronym></i>. </span><span class="pubdate">October 1997. </span></p> +<a name="id2595019"></a><p>[<abbr class="abbrev">RFC2230</abbr>] <span class="author"><span class="firstname">R.</span> <span class="surname">Atkinson</span>. </span><span class="title"><i>Key Exchange Delegation Record for the <acronym class="acronym">DNS</acronym></i>. </span><span class="pubdate">October 1997. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595045"></a><p>[<abbr class="abbrev">RFC2536</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>DSA KEYs and SIGs in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595072"></a><p>[<abbr class="abbrev">RFC2537</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595098"></a><p>[<abbr class="abbrev">RFC2538</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Storing Certificates in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595138"></a><p>[<abbr class="abbrev">RFC2539</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Storage of Diffie-Hellman Keys in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595168"></a><p>[<abbr class="abbrev">RFC2540</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Detached Domain Name System (DNS) Information</i>. </span><span class="pubdate">March 1999. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595197"></a><p>[<abbr class="abbrev">RFC2782</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span>. </span><span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="author"><span class="firstname">L.</span> <span class="surname">Esibov</span>. </span><span class="title"><i>A DNS RR for specifying the location of services (DNS SRV)</i>. </span><span class="pubdate">February 2000. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595240"></a><p>[<abbr class="abbrev">RFC2915</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Mealling</span>. </span><span class="author"><span class="firstname">R.</span> <span class="surname">Daniel</span>. </span><span class="title"><i>The Naming Authority Pointer (NAPTR) DNS Resource Record</i>. </span><span class="pubdate">September 2000. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595273"></a><p>[<abbr class="abbrev">RFC3110</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</i>. </span><span class="pubdate">May 2001. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595300"></a><p>[<abbr class="abbrev">RFC3123</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Koch</span>. </span><span class="title"><i>A DNS RR Type for Lists of Address Prefixes (APL RR)</i>. </span><span class="pubdate">June 2001. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595323"></a><p>[<abbr class="abbrev">RFC3596</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">C.</span> <span class="surname">Huitema</span>, <span class="firstname">V.</span> <span class="surname">Ksinant</span>, and <span class="firstname">M.</span> <span class="surname">Souissi</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Extensions to support IP + version 6</i>. </span><span class="pubdate">October 2003. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595381"></a><p>[<abbr class="abbrev">RFC3597</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Gustafsson</span>. </span><span class="title"><i>Handling of Unknown DNS Resource Record (RR) Types</i>. </span><span class="pubdate">September 2003. </span></p> </div> </div> <div class="bibliodiv"> <h3 class="title"> <acronym class="acronym">DNS</acronym> and the Internet</h3> <div class="biblioentry"> -<a name="id2594186"></a><p>[<abbr class="abbrev">RFC1101</abbr>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Encoding of Network Names and Other Types</i>. </span><span class="pubdate">April 1989. </span></p> +<a name="id2595413"></a><p>[<abbr class="abbrev">RFC1101</abbr>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Encoding of Network Names + and Other Types</i>. </span><span class="pubdate">April 1989. </span></p> </div> <div class="biblioentry"> -<a name="id2594212"></a><p>[<abbr class="abbrev">RFC1123</abbr>] <span class="author"><span class="surname">Braden</span>. </span><span class="title"><i>Requirements for Internet Hosts - Application and Support</i>. </span><span class="pubdate">October 1989. </span></p> +<a name="id2595438"></a><p>[<abbr class="abbrev">RFC1123</abbr>] <span class="author"><span class="surname">Braden</span>. </span><span class="title"><i>Requirements for Internet Hosts - Application and + Support</i>. </span><span class="pubdate">October 1989. </span></p> </div> <div class="biblioentry"> -<a name="id2594235"></a><p>[<abbr class="abbrev">RFC1591</abbr>] <span class="author"><span class="firstname">J.</span> <span class="surname">Postel</span>. </span><span class="title"><i>Domain Name System Structure and Delegation</i>. </span><span class="pubdate">March 1994. </span></p> +<a name="id2595461"></a><p>[<abbr class="abbrev">RFC1591</abbr>] <span class="author"><span class="firstname">J.</span> <span class="surname">Postel</span>. </span><span class="title"><i>Domain Name System Structure and Delegation</i>. </span><span class="pubdate">March 1994. </span></p> </div> <div class="biblioentry"> -<a name="id2594257"></a><p>[<abbr class="abbrev">RFC2317</abbr>] <span class="authorgroup"><span class="firstname">H.</span> <span class="surname">Eidnes</span>, <span class="firstname">G.</span> <span class="surname">de Groot</span>, and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Classless IN-ADDR.ARPA Delegation</i>. </span><span class="pubdate">March 1998. </span></p> +<a name="id2595484"></a><p>[<abbr class="abbrev">RFC2317</abbr>] <span class="authorgroup"><span class="firstname">H.</span> <span class="surname">Eidnes</span>, <span class="firstname">G.</span> <span class="surname">de Groot</span>, and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Classless IN-ADDR.ARPA Delegation</i>. </span><span class="pubdate">March 1998. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595530"></a><p>[<abbr class="abbrev">RFC2826</abbr>] <span class="authorgroup"><span class="surname">Internet Architecture Board</span>. </span><span class="title"><i>IAB Technical Comment on the Unique DNS Root</i>. </span><span class="pubdate">May 2000. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595554"></a><p>[<abbr class="abbrev">RFC2929</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, <span class="firstname">E.</span> <span class="surname">Brunner-Williams</span>, and <span class="firstname">B.</span> <span class="surname">Manning</span>. </span><span class="title"><i>Domain Name System (DNS) IANA Considerations</i>. </span><span class="pubdate">September 2000. </span></p> </div> </div> <div class="bibliodiv"> <h3 class="title"> <acronym class="acronym">DNS</acronym> Operations</h3> <div class="biblioentry"> -<a name="id2594311"></a><p>[<abbr class="abbrev">RFC1537</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Beertema</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Data File Configuration Errors</i>. </span><span class="pubdate">October 1993. </span></p> +<a name="id2595611"></a><p>[<abbr class="abbrev">RFC1033</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Lottor</span>. </span><span class="title"><i>Domain administrators operations guide.</i>. </span><span class="pubdate">November 1987. </span></p> </div> <div class="biblioentry"> -<a name="id2594337"></a><p>[<abbr class="abbrev">RFC1912</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Barr</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Operational and Configuration Errors</i>. </span><span class="pubdate">February 1996. </span></p> +<a name="id2595635"></a><p>[<abbr class="abbrev">RFC1537</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Beertema</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Data File + Configuration Errors</i>. </span><span class="pubdate">October 1993. </span></p> </div> <div class="biblioentry"> -<a name="id2594363"></a><p>[<abbr class="abbrev">RFC2010</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Operational Criteria for Root Name Servers.</i>. </span><span class="pubdate">October 1996. </span></p> +<a name="id2595661"></a><p>[<abbr class="abbrev">RFC1912</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Barr</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Operational and + Configuration Errors</i>. </span><span class="pubdate">February 1996. </span></p> </div> <div class="biblioentry"> -<a name="id2594400"></a><p>[<abbr class="abbrev">RFC2219</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Hamilton</span> and <span class="firstname">R.</span> <span class="surname">Wright</span>. </span><span class="title"><i>Use of <acronym class="acronym">DNS</acronym> Aliases for Network Services.</i>. </span><span class="pubdate">October 1997. </span></p> +<a name="id2595688"></a><p>[<abbr class="abbrev">RFC2010</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Operational Criteria for Root Name Servers.</i>. </span><span class="pubdate">October 1996. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595724"></a><p>[<abbr class="abbrev">RFC2219</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Hamilton</span> and <span class="firstname">R.</span> <span class="surname">Wright</span>. </span><span class="title"><i>Use of <acronym class="acronym">DNS</acronym> Aliases for + Network Services.</i>. </span><span class="pubdate">October 1997. </span></p> +</div> +</div> +<div class="bibliodiv"> +<h3 class="title">Internationalized Domain Names</h3> +<div class="biblioentry"> +<a name="id2595770"></a><p>[<abbr class="abbrev">RFC2825</abbr>] <span class="authorgroup"><span class="surname">IAB</span> and <span class="firstname">R.</span> <span class="surname">Daigle</span>. </span><span class="title"><i>A Tangled Web: Issues of I18N, Domain Names, + and the Other Internet protocols</i>. </span><span class="pubdate">May 2000. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595802"></a><p>[<abbr class="abbrev">RFC3490</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Faltstrom</span>, <span class="firstname">P.</span> <span class="surname">Hoffman</span>, and <span class="firstname">A.</span> <span class="surname">Costello</span>. </span><span class="title"><i>Internationalizing Domain Names in Applications (IDNA)</i>. </span><span class="pubdate">March 2003. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595848"></a><p>[<abbr class="abbrev">RFC3491</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Hoffman</span> and <span class="firstname">M.</span> <span class="surname">Blanchet</span>. </span><span class="title"><i>Nameprep: A Stringprep Profile for Internationalized Domain Names</i>. </span><span class="pubdate">March 2003. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595883"></a><p>[<abbr class="abbrev">RFC3492</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Costello</span>. </span><span class="title"><i>Punycode: A Bootstring encoding of Unicode + for Internationalized Domain Names in + Applications (IDNA)</i>. </span><span class="pubdate">March 2003. </span></p> </div> </div> <div class="bibliodiv"> <h3 class="title">Other <acronym class="acronym">DNS</acronym>-related RFCs</h3> <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> <h3 class="title">Note</h3> -<p>Note: the following list of RFCs, although -<acronym class="acronym">DNS</acronym>-related, are not concerned with implementing software.</p> +<p> + Note: the following list of RFCs, although + <acronym class="acronym">DNS</acronym>-related, are not + concerned with implementing software. + </p> +</div> +<div class="biblioentry"> +<a name="id2595928"></a><p>[<abbr class="abbrev">RFC1464</abbr>] <span class="author"><span class="firstname">R.</span> <span class="surname">Rosenbaum</span>. </span><span class="title"><i>Using the Domain Name System To Store Arbitrary String + Attributes</i>. </span><span class="pubdate">May 1993. </span></p> +</div> +<div class="biblioentry"> +<a name="id2595950"></a><p>[<abbr class="abbrev">RFC1713</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Romao</span>. </span><span class="title"><i>Tools for <acronym class="acronym">DNS</acronym> Debugging</i>. </span><span class="pubdate">November 1994. </span></p> </div> <div class="biblioentry"> -<a name="id2594459"></a><p>[<abbr class="abbrev">RFC1464</abbr>] <span class="author"><span class="firstname">R.</span> <span class="surname">Rosenbaum</span>. </span><span class="title"><i>Using the Domain Name System To Store Arbitrary String Attributes</i>. </span><span class="pubdate">May 1993. </span></p> +<a name="id2595976"></a><p>[<abbr class="abbrev">RFC1794</abbr>] <span class="author"><span class="firstname">T.</span> <span class="surname">Brisco</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Support for Load + Balancing</i>. </span><span class="pubdate">April 1995. </span></p> </div> <div class="biblioentry"> -<a name="id2594482"></a><p>[<abbr class="abbrev">RFC1713</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Romao</span>. </span><span class="title"><i>Tools for <acronym class="acronym">DNS</acronym> Debugging</i>. </span><span class="pubdate">November 1994. </span></p> +<a name="id2596002"></a><p>[<abbr class="abbrev">RFC2240</abbr>] <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span><span class="title"><i>A Legal Basis for Domain Name Allocation</i>. </span><span class="pubdate">November 1997. </span></p> </div> <div class="biblioentry"> -<a name="id2594506"></a><p>[<abbr class="abbrev">RFC1794</abbr>] <span class="author"><span class="firstname">T.</span> <span class="surname">Brisco</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Support for Load Balancing</i>. </span><span class="pubdate">April 1995. </span></p> +<a name="id2596025"></a><p>[<abbr class="abbrev">RFC2345</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>, <span class="firstname">T.</span> <span class="surname">Wolf</span>, and <span class="firstname">G.</span> <span class="surname">Oglesby</span>. </span><span class="title"><i>Domain Names and Company Name Retrieval</i>. </span><span class="pubdate">May 1998. </span></p> </div> <div class="biblioentry"> -<a name="id2594531"></a><p>[<abbr class="abbrev">RFC2240</abbr>] <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span><span class="title"><i>A Legal Basis for Domain Name Allocation</i>. </span><span class="pubdate">November 1997. </span></p> +<a name="id2596071"></a><p>[<abbr class="abbrev">RFC2352</abbr>] <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span><span class="title"><i>A Convention For Using Legal Names as Domain Names</i>. </span><span class="pubdate">May 1998. </span></p> </div> <div class="biblioentry"> -<a name="id2594553"></a><p>[<abbr class="abbrev">RFC2345</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>, <span class="firstname">T.</span> <span class="surname">Wolf</span>, and <span class="firstname">G.</span> <span class="surname">Oglesby</span>. </span><span class="title"><i>Domain Names and Company Name Retrieval</i>. </span><span class="pubdate">May 1998. </span></p> +<a name="id2596094"></a><p>[<abbr class="abbrev">RFC3071</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>. </span><span class="title"><i>Reflections on the DNS, RFC 1591, and Categories of Domains</i>. </span><span class="pubdate">February 2001. </span></p> </div> <div class="biblioentry"> -<a name="id2594599"></a><p>[<abbr class="abbrev">RFC2352</abbr>] <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span><span class="title"><i>A Convention For Using Legal Names as Domain Names</i>. </span><span class="pubdate">May 1998. </span></p> +<a name="id2596121"></a><p>[<abbr class="abbrev">RFC3258</abbr>] <span class="authorgroup"><span class="firstname">T.</span> <span class="surname">Hardie</span>. </span><span class="title"><i>Distributing Authoritative Name Servers via + Shared Unicast Addresses</i>. </span><span class="pubdate">April 2002. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596147"></a><p>[<abbr class="abbrev">RFC3901</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Durand</span> and <span class="firstname">J.</span> <span class="surname">Ihren</span>. </span><span class="title"><i>DNS IPv6 Transport Operational Guidelines</i>. </span><span class="pubdate">September 2004. </span></p> +</div> +</div> +<div class="bibliodiv"> +<h3 class="title">Obsolete and Unimplemented Experimental RFC</h3> +<div class="biblioentry"> +<a name="id2596190"></a><p>[<abbr class="abbrev">RFC1712</abbr>] <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Farrell</span>, <span class="firstname">M.</span> <span class="surname">Schulze</span>, <span class="firstname">S.</span> <span class="surname">Pleitner</span>, and <span class="firstname">D.</span> <span class="surname">Baldoni</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Encoding of Geographical + Location</i>. </span><span class="pubdate">November 1994. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596248"></a><p>[<abbr class="abbrev">RFC2673</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span>. </span><span class="title"><i>Binary Labels in the Domain Name System</i>. </span><span class="pubdate">August 1999. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596275"></a><p>[<abbr class="abbrev">RFC2874</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span> and <span class="firstname">C.</span> <span class="surname">Huitema</span>. </span><span class="title"><i>DNS Extensions to Support IPv6 Address Aggregation + and Renumbering</i>. </span><span class="pubdate">July 2000. </span></p> </div> </div> <div class="bibliodiv"> -<h3 class="title">Obsolete and Unimplemented Experimental RRs</h3> +<h3 class="title">Obsoleted DNS Security RFCs</h3> +<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;"> +<h3 class="title">Note</h3> +<p> + Most of these have been consolidated into RFC4033, + RFC4034 and RFC4035 which collectively describe DNSSECbis. + </p> +</div> +<div class="biblioentry"> +<a name="id2596323"></a><p>[<abbr class="abbrev">RFC2065</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">C.</span> <span class="surname">Kaufman</span>. </span><span class="title"><i>Domain Name System Security Extensions</i>. </span><span class="pubdate">January 1997. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596362"></a><p>[<abbr class="abbrev">RFC2137</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Secure Domain Name System Dynamic Update</i>. </span><span class="pubdate">April 1997. </span></p> +</div> <div class="biblioentry"> -<a name="id2594630"></a><p>[<abbr class="abbrev">RFC1712</abbr>] <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Farrell</span>, <span class="firstname">M.</span> <span class="surname">Schulze</span>, <span class="firstname">S.</span> <span class="surname">Pleitner</span>, and <span class="firstname">D.</span> <span class="surname">Baldoni</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Encoding of Geographical -Location</i>. </span><span class="pubdate">November 1994. </span></p> +<a name="id2596389"></a><p>[<abbr class="abbrev">RFC2535</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Domain Name System Security Extensions</i>. </span><span class="pubdate">March 1999. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596419"></a><p>[<abbr class="abbrev">RFC3008</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Domain Name System Security (DNSSEC) + Signing Authority</i>. </span><span class="pubdate">November 2000. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596444"></a><p>[<abbr class="abbrev">RFC3090</abbr>] <span class="authorgroup"><span class="firstname">E.</span> <span class="surname">Lewis</span>. </span><span class="title"><i>DNS Security Extension Clarification on Zone Status</i>. </span><span class="pubdate">March 2001. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596471"></a><p>[<abbr class="abbrev">RFC3445</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Massey</span> and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Limiting the Scope of the KEY Resource Record (RR)</i>. </span><span class="pubdate">December 2002. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596507"></a><p>[<abbr class="abbrev">RFC3655</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span> and <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Redefinition of DNS Authenticated Data (AD) bit</i>. </span><span class="pubdate">November 2003. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596544"></a><p>[<abbr class="abbrev">RFC3658</abbr>] <span class="authorgroup"><span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Delegation Signer (DS) Resource Record (RR)</i>. </span><span class="pubdate">December 2003. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596570"></a><p>[<abbr class="abbrev">RFC3755</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Weiler</span>. </span><span class="title"><i>Legacy Resolver Compatibility for Delegation Signer (DS)</i>. </span><span class="pubdate">May 2004. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596597"></a><p>[<abbr class="abbrev">RFC3757</abbr>] <span class="authorgroup"><span class="firstname">O.</span> <span class="surname">Kolkman</span>, <span class="firstname">J.</span> <span class="surname">Schlyter</span>, and <span class="firstname">E.</span> <span class="surname">Lewis</span>. </span><span class="title"><i>Domain Name System KEY (DNSKEY) Resource Record + (RR) Secure Entry Point (SEP) Flag</i>. </span><span class="pubdate">April 2004. </span></p> +</div> +<div class="biblioentry"> +<a name="id2596642"></a><p>[<abbr class="abbrev">RFC3845</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Schlyter</span>. </span><span class="title"><i>DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format</i>. </span><span class="pubdate">August 2004. </span></p> </div> </div> </div> @@ -424,24 +583,27 @@ Location</i>. </span><span class="pubdate">November 1994. </span></p> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> <a name="internet_drafts"></a>Internet Drafts</h3></div></div></div> -<p>Internet Drafts (IDs) are rough-draft working documents of -the Internet Engineering Task Force. They are, in essence, RFCs -in the preliminary stages of development. Implementors are cautioned not -to regard IDs as archival, and they should not be quoted or cited -in any formal documents unless accompanied by the disclaimer that -they are "works in progress." IDs have a lifespan of six months -after which they are deleted unless updated by their authors. -</p> +<p> + Internet Drafts (IDs) are rough-draft working documents of + the Internet Engineering Task Force. They are, in essence, RFCs + in the preliminary stages of development. Implementors are + cautioned not + to regard IDs as archival, and they should not be quoted or cited + in any formal documents unless accompanied by the disclaimer that + they are "works in progress." IDs have a lifespan of six months + after which they are deleted unless updated by their authors. + </p> </div> <div class="sect2" lang="en"> <div class="titlepage"><div><div><h3 class="title"> -<a name="id2594702"></a>Other Documents About <acronym class="acronym">BIND</acronym></h3></div></div></div> +<a name="id2596683"></a>Other Documents About <acronym class="acronym">BIND</acronym> +</h3></div></div></div> <p></p> <div class="bibliography"> <div class="titlepage"><div><div><h4 class="title"> -<a name="id2594712"></a>Bibliography</h4></div></div></div> +<a name="id2596693"></a>Bibliography</h4></div></div></div> <div class="biblioentry"> -<a name="id2594714"></a><p><span class="authorgroup"><span class="firstname">Paul</span> <span class="surname">Albitz</span> and <span class="firstname">Cricket</span> <span class="surname">Liu</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></i>. </span><span class="copyright">Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. </span></p> +<a name="id2596695"></a><p><span class="authorgroup"><span class="firstname">Paul</span> <span class="surname">Albitz</span> and <span class="firstname">Cricket</span> <span class="surname">Liu</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></i>. </span><span class="copyright">Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. </span></p> </div> </div> </div> @@ -454,12 +616,13 @@ after which they are deleted unless updated by their authors. <td width="40%" align="left"> <a accesskey="p" href="Bv9ARM.ch08.html">Prev</a> </td> <td width="20%" align="center"> </td> -<td width="40%" align="right"> </td> +<td width="40%" align="right"> <a accesskey="n" href="Bv9ARM.ch10.html">Next</a> +</td> </tr> <tr> <td width="40%" align="left" valign="top">Chapter 8. Troubleshooting </td> <td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td> -<td width="40%" align="right" valign="top"> </td> +<td width="40%" align="right" valign="top"> Manual pages</td> </tr> </table> </div> diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.html b/usr.sbin/bind/doc/arm/Bv9ARM.html index 59f87c33a9f..f730286fe60 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.html @@ -1,5 +1,5 @@ <!-- - - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC") + - Copyright (C) 2004-2007 Internet Systems Consortium, Inc. ("ISC") - Copyright (C) 2000-2003 Internet Software Consortium. - - Permission to use, copy, modify, and distribute this software for any @@ -14,14 +14,14 @@ - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR - PERFORMANCE OF THIS SOFTWARE. --> -<!-- $ISC: Bv9ARM.html,v 1.60.2.9.2.38 2006/11/15 04:33:42 marka Exp $ --> +<!-- $ISC: Bv9ARM.html,v 1.85.18.68 2007/10/31 01:35:59 marka Exp $ --> <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"> <title>BIND 9 Administrator Reference Manual</title> -<meta name="generator" content="DocBook XSL Stylesheets V1.70.1"> +<meta name="generator" content="DocBook XSL Stylesheets V1.71.1"> <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual"> -<link rel="next" href="Bv9ARM.ch01.html" title="Chapter 1. Introduction "> +<link rel="next" href="Bv9ARM.ch01.html" title="Chapter 1. Introduction"> </head> <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"> <div class="navheader"> @@ -40,8 +40,8 @@ <div class="titlepage"> <div> <div><h1 class="title"> -<a name="id2482844"></a>BIND 9 Administrator Reference Manual</h1></div> -<div><p class="copyright">Copyright © 2004-2006 Internet Systems Consortium, Inc. ("ISC")</p></div> +<a name="id2563155"></a>BIND 9 Administrator Reference Manual</h1></div> +<div><p class="copyright">Copyright © 2004-2007 Internet Systems Consortium, Inc. ("ISC")</p></div> <div><p class="copyright">Copyright © 2000-2003 Internet Software Consortium.</p></div> </div> <hr> @@ -49,41 +49,41 @@ <div class="toc"> <p><b>Table of Contents</b></p> <dl> -<dt><span class="chapter"><a href="Bv9ARM.ch01.html">1. Introduction </a></span></dt> +<dt><span class="chapter"><a href="Bv9ARM.ch01.html">1. Introduction</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2569434">Scope of Document</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2569460">Organization of This Document</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2569736">Conventions Used in This Document</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2569994">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2564117">Scope of Document</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2564140">Organization of This Document</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2563474">Conventions Used in This Document</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2564816">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570014">DNS Fundamentals</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570323">Domains and Domain Names</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570407">Zones</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570550">Authoritative Name Servers</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570642">Caching Name Servers</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570699">Name Servers in Multiple Roles</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2564837">DNS Fundamentals</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2564871">Domains and Domain Names</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567208">Zones</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567285">Authoritative Name Servers</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567526">Caching Name Servers</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2567588">Name Servers in Multiple Roles</a></span></dt> </dl></dd> </dl></dd> <dt><span class="chapter"><a href="Bv9ARM.ch02.html">2. <acronym class="acronym">BIND</acronym> Resource Requirements</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2570868">Hardware requirements</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2570892">CPU Requirements</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2570903">Memory Requirements</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2570918">Name Server Intensive Environment Issues</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2570995">Supported Operating Systems</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567622">Hardware requirements</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567649">CPU Requirements</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567661">Memory Requirements</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567688">Name Server Intensive Environment Issues</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch02.html#id2567699">Supported Operating Systems</a></span></dt> </dl></dd> <dt><span class="chapter"><a href="Bv9ARM.ch03.html">3. Name Server Configuration</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2571026">A Caching-only Name Server</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2571042">An Authoritative-only Name Server</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568004">A Caching-only Name Server</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568020">An Authoritative-only Name Server</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2571064">Load Balancing</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2571484">Name Server Operations</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568042">Load Balancing</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568465">Name Server Operations</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2571490">Tools for Use With the Name Server Daemon</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2572723">Signals</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568470">Tools for Use With the Name Server Daemon</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2570184">Signals</a></span></dt> </dl></dd> </dl></dd> <dt><span class="chapter"><a href="Bv9ARM.ch04.html">4. Advanced DNS Features</a></span></dt> @@ -92,33 +92,34 @@ <dt><span class="sect1"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt> <dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2573147">Split DNS</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2570642">Split DNS</a></span></dt> +<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570660">Example split DNS setup</a></span></dt></dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573709">Generate Shared Keys for Each Pair of Hosts</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573776">Copying the Shared Secret to Both Machines</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573784">Informing the Servers of the Key's Existence</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573824">Instructing the Server to Use the Key</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573876">TSIG Key Based Access Control</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2573920">Errors</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571095">Generate Shared Keys for Each Pair of Hosts</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571169">Copying the Shared Secret to Both Machines</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571179">Informing the Servers of the Key's Existence</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571219">Instructing the Server to Use the Key</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571413">TSIG Key Based Access Control</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571458">Errors</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2573933">TKEY</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2573982">SIG(0)</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2571472">TKEY</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2571521">SIG(0)</a></span></dt> <dt><span class="sect1"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574049">Generating Keys</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574116">Signing the Zone</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574259">Configuring Servers</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571725">Generating Keys</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571795">Signing the Zone</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571874">Configuring Servers</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2574396">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2572153">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574455">Address Lookups Using AAAA Records</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2574475">Address to Name Lookups Using Nibble Format</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572215">Address Lookups Using AAAA Records</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572236">Address to Name Lookups Using Nibble Format</a></span></dt> </dl></dd> </dl></dd> <dt><span class="chapter"><a href="Bv9ARM.ch05.html">5. The <acronym class="acronym">BIND</acronym> 9 Lightweight Resolver</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="Bv9ARM.ch05.html#id2574507">The Lightweight Resolver Library</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch05.html#id2572269">The Lightweight Resolver Library</a></span></dt> <dt><span class="sect1"><a href="Bv9ARM.ch05.html#lwresd">Running a Resolver Daemon</a></span></dt> </dl></dd> <dt><span class="chapter"><a href="Bv9ARM.ch06.html">6. <acronym class="acronym">BIND</acronym> 9 Configuration Reference</a></span></dt> @@ -126,79 +127,118 @@ <dt><span class="sect1"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575672">Comment Syntax</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2573480">Comment Syntax</a></span></dt> </dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576157"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574092"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#acl"><span><strong class="command">acl</strong></span> Statement Definition and -Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576326"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576672"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576686"><span><strong class="command">include</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576709"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576730"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576870"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577064"><span><strong class="command">logging</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578270"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578343"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578406"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578518"><span><strong class="command">masters</strong></span> Statement Definition and Usage </a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2578533"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and Usage</a></span></dt> + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574282"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574711"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574726"><span><strong class="command">include</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574749"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574771"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574930"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575056"><span><strong class="command">logging</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576406"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576480"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576544"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576587"><span><strong class="command">masters</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2576602"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and + Usage</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and Usage</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2586290"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2586338"><span><strong class="command">trusted-keys</strong></span> Statement Definition - and Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and + Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2585361"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2585410"><span><strong class="command">trusted-keys</strong></span> Statement Definition + and Usage</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span><strong class="command">view</strong></span> Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2586420"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2585490"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span> -Statement Grammar</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2587635"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt> + Statement Grammar</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2586798"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt> </dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2589173">Zone File</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2589080">Zone File</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2590605">Discussion of MX Records</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591101">Discussion of MX Records</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591102">Inverse Mapping in IPv4</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591208">Other Zone File Directives</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591377"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591653">Inverse Mapping in IPv4</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2591848">Other Zone File Directives</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2592173"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt> </dl></dd> </dl></dd> <dt><span class="chapter"><a href="Bv9ARM.ch07.html">7. <acronym class="acronym">BIND</acronym> 9 Security Considerations</a></span></dt> <dd><dl> <dt><span class="sect1"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2591971"><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span> (for -UNIX servers)</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2592714"><span><strong class="command">Chroot</strong></span> and <span><strong class="command">Setuid</strong></span></a></span></dt> <dd><dl> -<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2592046">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2592172">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2592791">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2592851">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt> </dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt> </dl></dd> <dt><span class="chapter"><a href="Bv9ARM.ch08.html">8. Troubleshooting</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2592243">Common Problems</a></span></dt> -<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2592248">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2592260">Incrementing and Changing the Serial Number</a></span></dt> -<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2592277">Where Can I Get Help?</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2592999">Common Problems</a></span></dt> +<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2593004">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd> +<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2593016">Incrementing and Changing the Serial Number</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2593033">Where Can I Get Help?</a></span></dt> </dl></dd> <dt><span class="appendix"><a href="Bv9ARM.ch09.html">A. Appendices</a></span></dt> <dd><dl> -<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2592339">Acknowledgments</a></span></dt> -<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2592344">A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></a></span></dt></dl></dd> -<dt><span class="sect1"><a href="Bv9ARM.ch09.html#historical_dns_information">General <acronym class="acronym">DNS</acronym> Reference Information</a></span></dt> +<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2593300">Acknowledgments</a></span></dt> +<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#historical_dns_information">A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></a></span></dt></dl></dd> +<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2593472">General <acronym class="acronym">DNS</acronym> Reference Information</a></span></dt> <dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt></dl></dd> <dt><span class="sect1"><a href="Bv9ARM.ch09.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt> <dd><dl> <dt><span class="sect2"><a href="Bv9ARM.ch09.html#rfcs">Request for Comments (RFCs)</a></span></dt> <dt><span class="sect2"><a href="Bv9ARM.ch09.html#internet_drafts">Internet Drafts</a></span></dt> -<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2594702">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt> +<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2596683">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt> </dl></dd> </dl></dd> +<dt><span class="reference"><a href="Bv9ARM.ch10.html">I. Manual pages</a></span></dt> +<dd><dl> +<dt> +<span class="refentrytitle"><a href="man.dig.html">dig</a></span><span class="refpurpose"> — DNS lookup utility</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.host.html">host</a></span><span class="refpurpose"> — DNS lookup utility</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.dnssec-keygen.html"><span class="application">dnssec-keygen</span></a></span><span class="refpurpose"> — DNSSEC key generation tool</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.dnssec-signzone.html"><span class="application">dnssec-signzone</span></a></span><span class="refpurpose"> — DNSSEC zone signing tool</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.named-checkconf.html"><span class="application">named-checkconf</span></a></span><span class="refpurpose"> — named configuration file syntax checking tool</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.named-checkzone.html"><span class="application">named-checkzone</span></a></span><span class="refpurpose"> — zone file validity checking or converting tool</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.named.html"><span class="application">named</span></a></span><span class="refpurpose"> — Internet domain name server</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.rndc.html"><span class="application">rndc</span></a></span><span class="refpurpose"> — name server control utility</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.rndc.conf.html"><code class="filename">rndc.conf</code></a></span><span class="refpurpose"> — rndc configuration file</span> +</dt> +<dt> +<span class="refentrytitle"><a href="man.rndc-confgen.html"><span class="application">rndc-confgen</span></a></span><span class="refpurpose"> — rndc key generation tool</span> +</dt> +</dl></dd> </dl> </div> </div> @@ -214,7 +254,7 @@ UNIX servers)</a></span></dt> <tr> <td width="40%" align="left" valign="top"> </td> <td width="20%" align="center"> </td> -<td width="40%" align="right" valign="top"> Chapter 1. Introduction </td> +<td width="40%" align="right" valign="top"> Chapter 1. Introduction</td> </tr> </table> </div> |