1 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
2 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd"
3 [<!ENTITY mdash "—">]>
5 - Copyright (C) 2004-2013 Internet Systems Consortium, Inc. ("ISC")
6 - Copyright (C) 2000-2003 Internet Software Consortium.
8 - Permission to use, copy, modify, and/or distribute this software for any
9 - purpose with or without fee is hereby granted, provided that the above
10 - copyright notice and this permission notice appear in all copies.
12 - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
13 - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
14 - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
15 - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
16 - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
17 - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
18 - PERFORMANCE OF THIS SOFTWARE.
22 <book xmlns:xi="http://www.w3.org/2001/XInclude">
23 <title>BIND 9 Administrator Reference Manual</title>
37 <holder>Internet Systems Consortium, Inc. ("ISC")</holder>
44 <holder>Internet Software Consortium.</holder>
48 <chapter id="Bv9ARM.ch01">
49 <title>Introduction</title>
51 The Internet Domain Name System (<acronym>DNS</acronym>)
52 consists of the syntax
53 to specify the names of entities in the Internet in a hierarchical
54 manner, the rules used for delegating authority over names, and the
55 system implementation that actually maps names to Internet
56 addresses. <acronym>DNS</acronym> data is maintained in a
58 hierarchical databases.
62 <title>Scope of Document</title>
65 The Berkeley Internet Name Domain
66 (<acronym>BIND</acronym>) implements a
67 domain name server for a number of operating systems. This
68 document provides basic information about the installation and
69 care of the Internet Systems Consortium (<acronym>ISC</acronym>)
70 <acronym>BIND</acronym> version 9 software package for
71 system administrators.
75 This version of the manual corresponds to BIND version 9.8.
80 <title>Organization of This Document</title>
82 In this document, <emphasis>Chapter 1</emphasis> introduces
83 the basic <acronym>DNS</acronym> and <acronym>BIND</acronym> concepts. <emphasis>Chapter 2</emphasis>
84 describes resource requirements for running <acronym>BIND</acronym> in various
85 environments. Information in <emphasis>Chapter 3</emphasis> is
86 <emphasis>task-oriented</emphasis> in its presentation and is
87 organized functionally, to aid in the process of installing the
88 <acronym>BIND</acronym> 9 software. The task-oriented
89 section is followed by
90 <emphasis>Chapter 4</emphasis>, which contains more advanced
91 concepts that the system administrator may need for implementing
92 certain options. <emphasis>Chapter 5</emphasis>
93 describes the <acronym>BIND</acronym> 9 lightweight
94 resolver. The contents of <emphasis>Chapter 6</emphasis> are
95 organized as in a reference manual to aid in the ongoing
96 maintenance of the software. <emphasis>Chapter 7</emphasis> addresses
97 security considerations, and
98 <emphasis>Chapter 8</emphasis> contains troubleshooting help. The
99 main body of the document is followed by several
100 <emphasis>appendices</emphasis> which contain useful reference
101 information, such as a <emphasis>bibliography</emphasis> and
102 historic information related to <acronym>BIND</acronym>
108 <title>Conventions Used in This Document</title>
111 In this document, we use the following general typographic
117 <colspec colname="1" colnum="1" colwidth="3.000in"/>
118 <colspec colname="2" colnum="2" colwidth="2.625in"/>
123 <emphasis>To describe:</emphasis>
128 <emphasis>We use the style:</emphasis>
135 a pathname, filename, URL, hostname,
136 mailing list name, or new term or concept
141 <filename>Fixed width</filename>
154 <userinput>Fixed Width Bold</userinput>
166 <computeroutput>Fixed Width</computeroutput>
175 The following conventions are used in descriptions of the
176 <acronym>BIND</acronym> configuration file:<informaltable colsep="0" frame="all" rowsep="0">
177 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="2Level-table">
178 <colspec colname="1" colnum="1" colsep="0" colwidth="3.000in"/>
179 <colspec colname="2" colnum="2" colsep="0" colwidth="2.625in"/>
182 <entry colname="1" colsep="1" rowsep="1">
184 <emphasis>To describe:</emphasis>
187 <entry colname="2" rowsep="1">
189 <emphasis>We use the style:</emphasis>
194 <entry colname="1" colsep="1" rowsep="1">
199 <entry colname="2" rowsep="1">
201 <literal>Fixed Width</literal>
206 <entry colname="1" colsep="1" rowsep="1">
211 <entry colname="2" rowsep="1">
213 <varname>Fixed Width</varname>
218 <entry colname="1" colsep="1">
225 <optional>Text is enclosed in square brackets</optional>
235 <title>The Domain Name System (<acronym>DNS</acronym>)</title>
237 The purpose of this document is to explain the installation
238 and upkeep of the <acronym>BIND</acronym> (Berkeley Internet
239 Name Domain) software package, and we
240 begin by reviewing the fundamentals of the Domain Name System
241 (<acronym>DNS</acronym>) as they relate to <acronym>BIND</acronym>.
245 <title>DNS Fundamentals</title>
248 The Domain Name System (DNS) is a hierarchical, distributed
249 database. It stores information for mapping Internet host names to
251 addresses and vice versa, mail routing information, and other data
252 used by Internet applications.
256 Clients look up information in the DNS by calling a
257 <emphasis>resolver</emphasis> library, which sends queries to one or
258 more <emphasis>name servers</emphasis> and interprets the responses.
259 The <acronym>BIND</acronym> 9 software distribution
261 name server, <command>named</command>, and a resolver
262 library, <command>liblwres</command>. The older
263 <command>libbind</command> resolver library is also available
264 from ISC as a separate download.
268 <title>Domains and Domain Names</title>
271 The data stored in the DNS is identified by <emphasis>domain names</emphasis> that are organized as a tree according to
272 organizational or administrative boundaries. Each node of the tree,
273 called a <emphasis>domain</emphasis>, is given a label. The domain
275 node is the concatenation of all the labels on the path from the
276 node to the <emphasis>root</emphasis> node. This is represented
277 in written form as a string of labels listed from right to left and
278 separated by dots. A label need only be unique within its parent
283 For example, a domain name for a host at the
284 company <emphasis>Example, Inc.</emphasis> could be
285 <literal>ourhost.example.com</literal>,
286 where <literal>com</literal> is the
287 top level domain to which
288 <literal>ourhost.example.com</literal> belongs,
289 <literal>example</literal> is
290 a subdomain of <literal>com</literal>, and
291 <literal>ourhost</literal> is the
296 For administrative purposes, the name space is partitioned into
297 areas called <emphasis>zones</emphasis>, each starting at a node and
298 extending down to the leaf nodes or to nodes where other zones
300 The data for each zone is stored in a <emphasis>name server</emphasis>, which answers queries about the zone using the
301 <emphasis>DNS protocol</emphasis>.
305 The data associated with each domain name is stored in the
306 form of <emphasis>resource records</emphasis> (<acronym>RR</acronym>s).
307 Some of the supported resource record types are described in
308 <xref linkend="types_of_resource_records_and_when_to_use_them"/>.
312 For more detailed information about the design of the DNS and
313 the DNS protocol, please refer to the standards documents listed in
314 <xref linkend="rfcs"/>.
321 To properly operate a name server, it is important to understand
322 the difference between a <emphasis>zone</emphasis>
323 and a <emphasis>domain</emphasis>.
327 As stated previously, a zone is a point of delegation in
328 the <acronym>DNS</acronym> tree. A zone consists of
329 those contiguous parts of the domain
330 tree for which a name server has complete information and over which
331 it has authority. It contains all domain names from a certain point
332 downward in the domain tree except those which are delegated to
333 other zones. A delegation point is marked by one or more
334 <emphasis>NS records</emphasis> in the
335 parent zone, which should be matched by equivalent NS records at
336 the root of the delegated zone.
340 For instance, consider the <literal>example.com</literal>
341 domain which includes names
342 such as <literal>host.aaa.example.com</literal> and
343 <literal>host.bbb.example.com</literal> even though
344 the <literal>example.com</literal> zone includes
345 only delegations for the <literal>aaa.example.com</literal> and
346 <literal>bbb.example.com</literal> zones. A zone can
348 exactly to a single domain, but could also include only part of a
349 domain, the rest of which could be delegated to other
350 name servers. Every name in the <acronym>DNS</acronym>
352 <emphasis>domain</emphasis>, even if it is
353 <emphasis>terminal</emphasis>, that is, has no
354 <emphasis>subdomains</emphasis>. Every subdomain is a domain and
355 every domain except the root is also a subdomain. The terminology is
356 not intuitive and we suggest that you read RFCs 1033, 1034 and 1035
358 gain a complete understanding of this difficult and subtle
363 Though <acronym>BIND</acronym> is called a "domain name
365 it deals primarily in terms of zones. The master and slave
366 declarations in the <filename>named.conf</filename> file
368 zones, not domains. When you ask some other site if it is willing to
369 be a slave server for your <emphasis>domain</emphasis>, you are
370 actually asking for slave service for some collection of zones.
375 <title>Authoritative Name Servers</title>
378 Each zone is served by at least
379 one <emphasis>authoritative name server</emphasis>,
380 which contains the complete data for the zone.
381 To make the DNS tolerant of server and network failures,
382 most zones have two or more authoritative servers, on
387 Responses from authoritative servers have the "authoritative
388 answer" (AA) bit set in the response packets. This makes them
389 easy to identify when debugging DNS configurations using tools like
390 <command>dig</command> (<xref linkend="diagnostic_tools"/>).
394 <title>The Primary Master</title>
397 The authoritative server where the master copy of the zone
398 data is maintained is called the
399 <emphasis>primary master</emphasis> server, or simply the
400 <emphasis>primary</emphasis>. Typically it loads the zone
401 contents from some local file edited by humans or perhaps
402 generated mechanically from some other local file which is
403 edited by humans. This file is called the
404 <emphasis>zone file</emphasis> or
405 <emphasis>master file</emphasis>.
409 In some cases, however, the master file may not be edited
410 by humans at all, but may instead be the result of
411 <emphasis>dynamic update</emphasis> operations.
416 <title>Slave Servers</title>
418 The other authoritative servers, the <emphasis>slave</emphasis>
419 servers (also known as <emphasis>secondary</emphasis> servers)
421 the zone contents from another server using a replication process
422 known as a <emphasis>zone transfer</emphasis>. Typically the data
424 transferred directly from the primary master, but it is also
426 to transfer it from another slave. In other words, a slave server
427 may itself act as a master to a subordinate slave server.
432 <title>Stealth Servers</title>
435 Usually all of the zone's authoritative servers are listed in
436 NS records in the parent zone. These NS records constitute
437 a <emphasis>delegation</emphasis> of the zone from the parent.
438 The authoritative servers are also listed in the zone file itself,
439 at the <emphasis>top level</emphasis> or <emphasis>apex</emphasis>
440 of the zone. You can list servers in the zone's top-level NS
441 records that are not in the parent's NS delegation, but you cannot
442 list servers in the parent's delegation that are not present at
443 the zone's top level.
447 A <emphasis>stealth server</emphasis> is a server that is
448 authoritative for a zone but is not listed in that zone's NS
449 records. Stealth servers can be used for keeping a local copy of
451 zone to speed up access to the zone's records or to make sure that
453 zone is available even if all the "official" servers for the zone
459 A configuration where the primary master server itself is a
460 stealth server is often referred to as a "hidden primary"
461 configuration. One use for this configuration is when the primary
463 is behind a firewall and therefore unable to communicate directly
464 with the outside world.
472 <title>Caching Name Servers</title>
475 - Terminology here is inconsistent. Probably ought to
476 - convert to using "recursive name server" everywhere
477 - with just a note about "caching" terminology.
481 The resolver libraries provided by most operating systems are
482 <emphasis>stub resolvers</emphasis>, meaning that they are not
484 performing the full DNS resolution process by themselves by talking
485 directly to the authoritative servers. Instead, they rely on a
487 name server to perform the resolution on their behalf. Such a
489 is called a <emphasis>recursive</emphasis> name server; it performs
490 <emphasis>recursive lookups</emphasis> for local clients.
494 To improve performance, recursive servers cache the results of
495 the lookups they perform. Since the processes of recursion and
496 caching are intimately connected, the terms
497 <emphasis>recursive server</emphasis> and
498 <emphasis>caching server</emphasis> are often used synonymously.
502 The length of time for which a record may be retained in
503 the cache of a caching name server is controlled by the
504 Time To Live (TTL) field associated with each resource record.
508 <title>Forwarding</title>
511 Even a caching name server does not necessarily perform
512 the complete recursive lookup itself. Instead, it can
513 <emphasis>forward</emphasis> some or all of the queries
514 that it cannot satisfy from its cache to another caching name
516 commonly referred to as a <emphasis>forwarder</emphasis>.
520 There may be one or more forwarders,
521 and they are queried in turn until the list is exhausted or an
523 is found. Forwarders are typically used when you do not
524 wish all the servers at a given site to interact directly with the
526 the Internet servers. A typical scenario would involve a number
527 of internal <acronym>DNS</acronym> servers and an
528 Internet firewall. Servers unable
529 to pass packets through the firewall would forward to the server
530 that can do it, and that server would query the Internet <acronym>DNS</acronym> servers
531 on the internal server's behalf.
538 <title>Name Servers in Multiple Roles</title>
541 The <acronym>BIND</acronym> name server can
542 simultaneously act as
543 a master for some zones, a slave for other zones, and as a caching
544 (recursive) server for a set of local clients.
548 However, since the functions of authoritative name service
549 and caching/recursive name service are logically separate, it is
550 often advantageous to run them on separate server machines.
552 A server that only provides authoritative name service
553 (an <emphasis>authoritative-only</emphasis> server) can run with
554 recursion disabled, improving reliability and security.
556 A server that is not authoritative for any zones and only provides
557 recursive service to local
558 clients (a <emphasis>caching-only</emphasis> server)
559 does not need to be reachable from the Internet at large and can
560 be placed inside a firewall.
568 <chapter id="Bv9ARM.ch02">
569 <title><acronym>BIND</acronym> Resource Requirements</title>
572 <title>Hardware requirements</title>
575 <acronym>DNS</acronym> hardware requirements have
576 traditionally been quite modest.
577 For many installations, servers that have been pensioned off from
578 active duty have performed admirably as <acronym>DNS</acronym> servers.
581 The DNSSEC features of <acronym>BIND</acronym> 9
582 may prove to be quite
583 CPU intensive however, so organizations that make heavy use of these
584 features may wish to consider larger systems for these applications.
585 <acronym>BIND</acronym> 9 is fully multithreaded, allowing
587 multiprocessor systems for installations that need it.
591 <title>CPU Requirements</title>
593 CPU requirements for <acronym>BIND</acronym> 9 range from
595 for serving of static zones without caching, to enterprise-class
596 machines if you intend to process many dynamic updates and DNSSEC
597 signed zones, serving many thousands of queries per second.
602 <title>Memory Requirements</title>
604 The memory of the server has to be large enough to fit the
605 cache and zones loaded off disk. The <command>max-cache-size</command>
606 option can be used to limit the amount of memory used by the cache,
607 at the expense of reducing cache hit rates and causing more <acronym>DNS</acronym>
609 Additionally, if additional section caching
610 (<xref linkend="acache"/>) is enabled,
611 the <command>max-acache-size</command> option can be used to
613 of memory used by the mechanism.
614 It is still good practice to have enough memory to load
615 all zone and cache data into memory — unfortunately, the best
617 to determine this for a given installation is to watch the name server
618 in operation. After a few weeks the server process should reach
619 a relatively stable size where entries are expiring from the cache as
620 fast as they are being inserted.
623 - Add something here about leaving overhead for attacks?
624 - How much overhead? Percentage?
629 <title>Name Server Intensive Environment Issues</title>
631 For name server intensive environments, there are two alternative
632 configurations that may be used. The first is where clients and
633 any second-level internal name servers query a main name server, which
634 has enough memory to build a large cache. This approach minimizes
635 the bandwidth used by external name lookups. The second alternative
636 is to set up second-level internal name servers to make queries
638 In this configuration, none of the individual machines needs to
639 have as much memory or CPU power as in the first alternative, but
640 this has the disadvantage of making many more external queries,
641 as none of the name servers share their cached data.
646 <title>Supported Operating Systems</title>
648 ISC <acronym>BIND</acronym> 9 compiles and runs on a large
650 of Unix-like operating systems and on
651 Microsoft Windows Server 2003 and 2008, and Windows XP and Vista.
653 list of supported systems, see the README file in the top level
655 of the BIND 9 source distribution.
660 <chapter id="Bv9ARM.ch03">
661 <title>Name Server Configuration</title>
663 In this chapter we provide some suggested configurations along
664 with guidelines for their use. We suggest reasonable values for
665 certain option settings.
668 <sect1 id="sample_configuration">
669 <title>Sample Configurations</title>
671 <title>A Caching-only Name Server</title>
673 The following sample configuration is appropriate for a caching-only
674 name server for use by clients internal to a corporation. All
676 from outside clients are refused using the <command>allow-query</command>
677 option. Alternatively, the same effect could be achieved using
683 // Two corporate subnets we wish to allow queries from.
684 acl corpnets { 192.168.4.0/24; 192.168.7.0/24; };
687 directory "/etc/namedb";
689 allow-query { corpnets; };
691 // Provide a reverse mapping for the loopback
693 zone "0.0.127.in-addr.arpa" {
695 file "localhost.rev";
703 <title>An Authoritative-only Name Server</title>
705 This sample configuration is for an authoritative-only server
706 that is the master server for "<filename>example.com</filename>"
707 and a slave for the subdomain "<filename>eng.example.com</filename>".
713 directory "/etc/namedb";
714 // Do not allow access to cache
715 allow-query-cache { none; };
716 // This is the default
717 allow-query { any; };
718 // Do not provide recursive service
722 // Provide a reverse mapping for the loopback
724 zone "0.0.127.in-addr.arpa" {
726 file "localhost.rev";
729 // We are the master server for example.com
732 file "example.com.db";
733 // IP addresses of slave servers allowed to
734 // transfer example.com
740 // We are a slave server for eng.example.com
741 zone "eng.example.com" {
743 file "eng.example.com.bk";
744 // IP address of eng.example.com master server
745 masters { 192.168.4.12; };
753 <title>Load Balancing</title>
755 - Add explanation of why load balancing is fragile at best
756 - and completely pointless in the general case.
760 A primitive form of load balancing can be achieved in
761 the <acronym>DNS</acronym> by using multiple records
762 (such as multiple A records) for one name.
766 For example, if you have three WWW servers with network addresses
767 of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the
768 following means that clients will connect to each machine one third
772 <informaltable colsep="0" rowsep="0">
773 <tgroup cols="5" colsep="0" rowsep="0" tgroupstyle="2Level-table">
774 <colspec colname="1" colnum="1" colsep="0" colwidth="0.875in"/>
775 <colspec colname="2" colnum="2" colsep="0" colwidth="0.500in"/>
776 <colspec colname="3" colnum="3" colsep="0" colwidth="0.750in"/>
777 <colspec colname="4" colnum="4" colsep="0" colwidth="0.750in"/>
778 <colspec colname="5" colnum="5" colsep="0" colwidth="2.028in"/>
803 Resource Record (RR) Data
810 <literal>www</literal>
815 <literal>600</literal>
820 <literal>IN</literal>
830 <literal>10.0.0.1</literal>
840 <literal>600</literal>
845 <literal>IN</literal>
855 <literal>10.0.0.2</literal>
865 <literal>600</literal>
870 <literal>IN</literal>
880 <literal>10.0.0.3</literal>
888 When a resolver queries for these records, <acronym>BIND</acronym> will rotate
889 them and respond to the query with the records in a different
890 order. In the example above, clients will randomly receive
891 records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients
892 will use the first record returned and discard the rest.
895 For more detail on ordering responses, check the
896 <command>rrset-order</command> sub-statement in the
897 <command>options</command> statement, see
898 <xref endterm="rrset_ordering_title" linkend="rrset_ordering"/>.
904 <title>Name Server Operations</title>
907 <title>Tools for Use With the Name Server Daemon</title>
909 This section describes several indispensable diagnostic,
910 administrative and monitoring tools available to the system
911 administrator for controlling and debugging the name server
914 <sect3 id="diagnostic_tools">
915 <title>Diagnostic Tools</title>
917 The <command>dig</command>, <command>host</command>, and
918 <command>nslookup</command> programs are all command
920 for manually querying name servers. They differ in style and
926 <term id="dig"><command>dig</command></term>
929 The domain information groper (<command>dig</command>)
930 is the most versatile and complete of these lookup tools.
931 It has two modes: simple interactive
932 mode for a single query, and batch mode which executes a
934 each in a list of several query lines. All query options are
936 from the command line.
938 <cmdsynopsis label="Usage">
939 <command>dig</command>
940 <arg>@<replaceable>server</replaceable></arg>
941 <arg choice="plain"><replaceable>domain</replaceable></arg>
942 <arg><replaceable>query-type</replaceable></arg>
943 <arg><replaceable>query-class</replaceable></arg>
944 <arg>+<replaceable>query-option</replaceable></arg>
945 <arg>-<replaceable>dig-option</replaceable></arg>
946 <arg>%<replaceable>comment</replaceable></arg>
949 The usual simple use of <command>dig</command> will take the form
952 <command>dig @server domain query-type query-class</command>
955 For more information and a list of available commands and
956 options, see the <command>dig</command> man
963 <term><command>host</command></term>
966 The <command>host</command> utility emphasizes
968 and ease of use. By default, it converts
969 between host names and Internet addresses, but its
971 can be extended with the use of options.
973 <cmdsynopsis label="Usage">
974 <command>host</command>
975 <arg>-aCdlnrsTwv</arg>
976 <arg>-c <replaceable>class</replaceable></arg>
977 <arg>-N <replaceable>ndots</replaceable></arg>
978 <arg>-t <replaceable>type</replaceable></arg>
979 <arg>-W <replaceable>timeout</replaceable></arg>
980 <arg>-R <replaceable>retries</replaceable></arg>
981 <arg>-m <replaceable>flag</replaceable></arg>
984 <arg choice="plain"><replaceable>hostname</replaceable></arg>
985 <arg><replaceable>server</replaceable></arg>
988 For more information and a list of available commands and
989 options, see the <command>host</command> man
996 <term><command>nslookup</command></term>
998 <para><command>nslookup</command>
999 has two modes: interactive and
1000 non-interactive. Interactive mode allows the user to
1001 query name servers for information about various
1002 hosts and domains or to print a list of hosts in a
1003 domain. Non-interactive mode is used to print just
1004 the name and requested information for a host or
1007 <cmdsynopsis label="Usage">
1008 <command>nslookup</command>
1009 <arg rep="repeat">-option</arg>
1011 <arg><replaceable>host-to-find</replaceable></arg>
1012 <arg>- <arg>server</arg></arg>
1016 Interactive mode is entered when no arguments are given (the
1017 default name server will be used) or when the first argument
1019 hyphen (`-') and the second argument is the host name or
1024 Non-interactive mode is used when the name or Internet
1026 of the host to be looked up is given as the first argument.
1028 optional second argument specifies the host name or address
1032 Due to its arcane user interface and frequently inconsistent
1033 behavior, we do not recommend the use of <command>nslookup</command>.
1034 Use <command>dig</command> instead.
1042 <sect3 id="admin_tools">
1043 <title>Administrative Tools</title>
1045 Administrative tools play an integral part in the management
1049 <varlistentry id="named-checkconf" xreflabel="Named Configuration Checking application">
1051 <term><command>named-checkconf</command></term>
1054 The <command>named-checkconf</command> program
1055 checks the syntax of a <filename>named.conf</filename> file.
1057 <cmdsynopsis label="Usage">
1058 <command>named-checkconf</command>
1060 <arg>-t <replaceable>directory</replaceable></arg>
1061 <arg><replaceable>filename</replaceable></arg>
1065 <varlistentry id="named-checkzone" xreflabel="Zone Checking application">
1067 <term><command>named-checkzone</command></term>
1070 The <command>named-checkzone</command> program
1071 checks a master file for
1072 syntax and consistency.
1074 <cmdsynopsis label="Usage">
1075 <command>named-checkzone</command>
1077 <arg>-c <replaceable>class</replaceable></arg>
1078 <arg>-o <replaceable>output</replaceable></arg>
1079 <arg>-t <replaceable>directory</replaceable></arg>
1080 <arg>-w <replaceable>directory</replaceable></arg>
1081 <arg>-k <replaceable>(ignore|warn|fail)</replaceable></arg>
1082 <arg>-n <replaceable>(ignore|warn|fail)</replaceable></arg>
1083 <arg>-W <replaceable>(ignore|warn)</replaceable></arg>
1084 <arg choice="plain"><replaceable>zone</replaceable></arg>
1085 <arg><replaceable>filename</replaceable></arg>
1089 <varlistentry id="named-compilezone" xreflabel="Zone Compilation application">
1090 <term><command>named-compilezone</command></term>
1093 Similar to <command>named-checkzone,</command> but
1094 it always dumps the zone content to a specified file
1095 (typically in a different format).
1099 <varlistentry id="rndc" xreflabel="Remote Name Daemon Control application">
1101 <term><command>rndc</command></term>
1104 The remote name daemon control
1105 (<command>rndc</command>) program allows the
1107 administrator to control the operation of a name server.
1108 Since <acronym>BIND</acronym> 9.2, <command>rndc</command>
1109 supports all the commands of the BIND 8 <command>ndc</command>
1110 utility except <command>ndc start</command> and
1111 <command>ndc restart</command>, which were also
1112 not supported in <command>ndc</command>'s
1114 If you run <command>rndc</command> without any
1116 it will display a usage message as follows:
1118 <cmdsynopsis label="Usage">
1119 <command>rndc</command>
1120 <arg>-c <replaceable>config</replaceable></arg>
1121 <arg>-s <replaceable>server</replaceable></arg>
1122 <arg>-p <replaceable>port</replaceable></arg>
1123 <arg>-y <replaceable>key</replaceable></arg>
1124 <arg choice="plain"><replaceable>command</replaceable></arg>
1125 <arg rep="repeat"><replaceable>command</replaceable></arg>
1128 <para>See <xref linkend="man.rndc"/> for details of
1129 the available <command>rndc</command> commands.
1133 <command>rndc</command> requires a configuration file,
1135 communication with the server is authenticated with
1136 digital signatures that rely on a shared secret, and
1137 there is no way to provide that secret other than with a
1138 configuration file. The default location for the
1139 <command>rndc</command> configuration file is
1140 <filename>/etc/rndc.conf</filename>, but an
1142 location can be specified with the <option>-c</option>
1143 option. If the configuration file is not found,
1144 <command>rndc</command> will also look in
1145 <filename>/etc/rndc.key</filename> (or whatever
1146 <varname>sysconfdir</varname> was defined when
1147 the <acronym>BIND</acronym> build was
1149 The <filename>rndc.key</filename> file is
1151 running <command>rndc-confgen -a</command> as
1153 <xref linkend="controls_statement_definition_and_usage"/>.
1157 The format of the configuration file is similar to
1158 that of <filename>named.conf</filename>, but
1160 only four statements, the <command>options</command>,
1161 <command>key</command>, <command>server</command> and
1162 <command>include</command>
1163 statements. These statements are what associate the
1164 secret keys to the servers with which they are meant to
1165 be shared. The order of statements is not
1170 The <command>options</command> statement has
1172 <command>default-server</command>, <command>default-key</command>,
1173 and <command>default-port</command>.
1174 <command>default-server</command> takes a
1175 host name or address argument and represents the server
1177 be contacted if no <option>-s</option>
1178 option is provided on the command line.
1179 <command>default-key</command> takes
1180 the name of a key as its argument, as defined by a <command>key</command> statement.
1181 <command>default-port</command> specifies the
1183 <command>rndc</command> should connect if no
1184 port is given on the command line or in a
1185 <command>server</command> statement.
1189 The <command>key</command> statement defines a
1191 by <command>rndc</command> when authenticating
1193 <command>named</command>. Its syntax is
1195 <command>key</command> statement in <filename>named.conf</filename>.
1196 The keyword <userinput>key</userinput> is
1197 followed by a key name, which must be a valid
1198 domain name, though it need not actually be hierarchical;
1200 a string like "<userinput>rndc_key</userinput>" is a valid
1202 The <command>key</command> statement has two
1204 <command>algorithm</command> and <command>secret</command>.
1205 While the configuration parser will accept any string as the
1207 to algorithm, currently only the string "<userinput>hmac-md5</userinput>"
1208 has any meaning. The secret is a base-64 encoded string
1209 as specified in RFC 3548.
1213 The <command>server</command> statement
1215 defined using the <command>key</command>
1216 statement with a server.
1217 The keyword <userinput>server</userinput> is followed by a
1218 host name or address. The <command>server</command> statement
1219 has two clauses: <command>key</command> and <command>port</command>.
1220 The <command>key</command> clause specifies the
1222 to be used when communicating with this server, and the
1223 <command>port</command> clause can be used to
1224 specify the port <command>rndc</command> should
1230 A sample minimal configuration file is as follows:
1235 algorithm "hmac-md5";
1237 "c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
1240 default-server 127.0.0.1;
1241 default-key rndc_key;
1246 This file, if installed as <filename>/etc/rndc.conf</filename>,
1247 would allow the command:
1251 <prompt>$ </prompt><userinput>rndc reload</userinput>
1255 to connect to 127.0.0.1 port 953 and cause the name server
1256 to reload, if a name server on the local machine were
1258 following controls statements:
1264 allow { localhost; } keys { rndc_key; };
1269 and it had an identical key statement for
1270 <literal>rndc_key</literal>.
1274 Running the <command>rndc-confgen</command>
1276 conveniently create a <filename>rndc.conf</filename>
1277 file for you, and also display the
1278 corresponding <command>controls</command>
1279 statement that you need to
1280 add to <filename>named.conf</filename>.
1282 you can run <command>rndc-confgen -a</command>
1284 a <filename>rndc.key</filename> file and not
1286 <filename>named.conf</filename> at all.
1297 <title>Signals</title>
1299 Certain UNIX signals cause the name server to take specific
1300 actions, as described in the following table. These signals can
1301 be sent using the <command>kill</command> command.
1303 <informaltable frame="all">
1305 <colspec colname="1" colnum="1" colsep="0" colwidth="1.125in"/>
1306 <colspec colname="2" colnum="2" colsep="0" colwidth="4.000in"/>
1310 <para><command>SIGHUP</command></para>
1314 Causes the server to read <filename>named.conf</filename> and
1315 reload the database.
1321 <para><command>SIGTERM</command></para>
1325 Causes the server to clean up and exit.
1331 <para><command>SIGINT</command></para>
1335 Causes the server to clean up and exit.
1346 <chapter id="Bv9ARM.ch04">
1347 <title>Advanced DNS Features</title>
1351 <title>Notify</title>
1353 <acronym>DNS</acronym> NOTIFY is a mechanism that allows master
1354 servers to notify their slave servers of changes to a zone's data. In
1355 response to a <command>NOTIFY</command> from a master server, the
1356 slave will check to see that its version of the zone is the
1357 current version and, if not, initiate a zone transfer.
1361 For more information about <acronym>DNS</acronym>
1362 <command>NOTIFY</command>, see the description of the
1363 <command>notify</command> option in <xref linkend="boolean_options"/> and
1364 the description of the zone option <command>also-notify</command> in
1365 <xref linkend="zone_transfers"/>. The <command>NOTIFY</command>
1366 protocol is specified in RFC 1996.
1370 As a slave zone can also be a master to other slaves, <command>named</command>,
1371 by default, sends <command>NOTIFY</command> messages for every zone
1372 it loads. Specifying <command>notify master-only;</command> will
1373 cause <command>named</command> to only send <command>NOTIFY</command> for master
1374 zones that it loads.
1379 <sect1 id="dynamic_update">
1380 <title>Dynamic Update</title>
1383 Dynamic Update is a method for adding, replacing or deleting
1384 records in a master server by sending it a special form of DNS
1385 messages. The format and meaning of these messages is specified
1390 Dynamic update is enabled by including an
1391 <command>allow-update</command> or an <command>update-policy</command>
1392 clause in the <command>zone</command> statement.
1396 If the zone's <command>update-policy</command> is set to
1397 <userinput>local</userinput>, updates to the zone
1398 will be permitted for the key <varname>local-ddns</varname>,
1399 which will be generated by <command>named</command> at startup.
1400 See <xref linkend="dynamic_update_policies"/> for more details.
1404 Dynamic updates using Kerberos signed requests can be made
1405 using the TKEY/GSS protocol by setting either the
1406 <command>tkey-gssapi-keytab</command> option, or alternatively
1407 by setting both the <command>tkey-gssapi-credential</command>
1408 and <command>tkey-domain</command> options. Once enabled,
1409 Kerberos signed requests will be matched against the update
1410 policies for the zone, using the Kerberos principal as the
1411 signer for the request.
1415 Updating of secure zones (zones using DNSSEC) follows RFC
1416 3007: RRSIG, NSEC and NSEC3 records affected by updates are
1417 automatically regenerated by the server using an online
1418 zone key. Update authorization is based on transaction
1419 signatures and an explicit server policy.
1422 <sect2 id="journal">
1423 <title>The journal file</title>
1426 All changes made to a zone using dynamic update are stored
1427 in the zone's journal file. This file is automatically created
1428 by the server when the first dynamic update takes place.
1429 The name of the journal file is formed by appending the extension
1430 <filename>.jnl</filename> to the name of the
1432 file unless specifically overridden. The journal file is in a
1433 binary format and should not be edited manually.
1437 The server will also occasionally write ("dump")
1438 the complete contents of the updated zone to its zone file.
1439 This is not done immediately after
1440 each dynamic update, because that would be too slow when a large
1441 zone is updated frequently. Instead, the dump is delayed by
1442 up to 15 minutes, allowing additional updates to take place.
1443 During the dump process, transient files will be created
1444 with the extensions <filename>.jnw</filename> and
1445 <filename>.jbk</filename>; under ordinary circumstances, these
1446 will be removed when the dump is complete, and can be safely
1451 When a server is restarted after a shutdown or crash, it will replay
1452 the journal file to incorporate into the zone any updates that
1454 place after the last zone dump.
1458 Changes that result from incoming incremental zone transfers are
1460 journalled in a similar way.
1464 The zone files of dynamic zones cannot normally be edited by
1465 hand because they are not guaranteed to contain the most recent
1466 dynamic changes — those are only in the journal file.
1467 The only way to ensure that the zone file of a dynamic zone
1468 is up to date is to run <command>rndc stop</command>.
1472 If you have to make changes to a dynamic zone
1473 manually, the following procedure will work: Disable dynamic updates
1475 <command>rndc freeze <replaceable>zone</replaceable></command>.
1476 This will also remove the zone's <filename>.jnl</filename> file
1477 and update the master file. Edit the zone file. Run
1478 <command>rndc thaw <replaceable>zone</replaceable></command>
1479 to reload the changed zone and re-enable dynamic updates.
1486 <sect1 id="incremental_zone_transfers">
1487 <title>Incremental Zone Transfers (IXFR)</title>
1490 The incremental zone transfer (IXFR) protocol is a way for
1491 slave servers to transfer only changed data, instead of having to
1492 transfer the entire zone. The IXFR protocol is specified in RFC
1493 1995. See <xref linkend="proposed_standards"/>.
1497 When acting as a master, <acronym>BIND</acronym> 9
1498 supports IXFR for those zones
1499 where the necessary change history information is available. These
1500 include master zones maintained by dynamic update and slave zones
1501 whose data was obtained by IXFR. For manually maintained master
1502 zones, and for slave zones obtained by performing a full zone
1503 transfer (AXFR), IXFR is supported only if the option
1504 <command>ixfr-from-differences</command> is set
1505 to <userinput>yes</userinput>.
1509 When acting as a slave, <acronym>BIND</acronym> 9 will attempt
1510 to use IXFR unless it is explicitly disabled via the
1511 <command>request-ixfr</command> option or the use of
1512 <command>ixfr-from-differences</command>. For
1513 more information about disabling IXFR, see the description
1514 of the <command>request-ixfr</command> clause of the
1515 <command>server</command> statement.
1520 <title>Split DNS</title>
1522 Setting up different views, or visibility, of the DNS space to
1523 internal and external resolvers is usually referred to as a
1524 <emphasis>Split DNS</emphasis> setup. There are several
1525 reasons an organization would want to set up its DNS this way.
1528 One common reason for setting up a DNS system this way is
1529 to hide "internal" DNS information from "external" clients on the
1530 Internet. There is some debate as to whether or not this is actually
1532 Internal DNS information leaks out in many ways (via email headers,
1533 for example) and most savvy "attackers" can find the information
1534 they need using other means.
1535 However, since listing addresses of internal servers that
1536 external clients cannot possibly reach can result in
1537 connection delays and other annoyances, an organization may
1538 choose to use a Split DNS to present a consistent view of itself
1539 to the outside world.
1542 Another common reason for setting up a Split DNS system is
1543 to allow internal networks that are behind filters or in RFC 1918
1544 space (reserved IP space, as documented in RFC 1918) to resolve DNS
1545 on the Internet. Split DNS can also be used to allow mail from outside
1546 back in to the internal network.
1549 <title>Example split DNS setup</title>
1551 Let's say a company named <emphasis>Example, Inc.</emphasis>
1552 (<literal>example.com</literal>)
1553 has several corporate sites that have an internal network with
1555 Internet Protocol (IP) space and an external demilitarized zone (DMZ),
1556 or "outside" section of a network, that is available to the public.
1559 <emphasis>Example, Inc.</emphasis> wants its internal clients
1560 to be able to resolve external hostnames and to exchange mail with
1561 people on the outside. The company also wants its internal resolvers
1562 to have access to certain internal-only zones that are not available
1563 at all outside of the internal network.
1566 In order to accomplish this, the company will set up two sets
1567 of name servers. One set will be on the inside network (in the
1569 IP space) and the other set will be on bastion hosts, which are
1571 hosts that can talk to both sides of its network, in the DMZ.
1574 The internal servers will be configured to forward all queries,
1575 except queries for <filename>site1.internal</filename>, <filename>site2.internal</filename>, <filename>site1.example.com</filename>,
1576 and <filename>site2.example.com</filename>, to the servers
1578 DMZ. These internal servers will have complete sets of information
1579 for <filename>site1.example.com</filename>, <filename>site2.example.com</filename>, <filename>site1.internal</filename>,
1580 and <filename>site2.internal</filename>.
1583 To protect the <filename>site1.internal</filename> and <filename>site2.internal</filename> domains,
1584 the internal name servers must be configured to disallow all queries
1585 to these domains from any external hosts, including the bastion
1589 The external servers, which are on the bastion hosts, will
1590 be configured to serve the "public" version of the <filename>site1</filename> and <filename>site2.example.com</filename> zones.
1591 This could include things such as the host records for public servers
1592 (<filename>www.example.com</filename> and <filename>ftp.example.com</filename>),
1593 and mail exchange (MX) records (<filename>a.mx.example.com</filename> and <filename>b.mx.example.com</filename>).
1596 In addition, the public <filename>site1</filename> and <filename>site2.example.com</filename> zones
1597 should have special MX records that contain wildcard (`*') records
1598 pointing to the bastion hosts. This is needed because external mail
1599 servers do not have any other way of looking up how to deliver mail
1600 to those internal hosts. With the wildcard records, the mail will
1601 be delivered to the bastion host, which can then forward it on to
1605 Here's an example of a wildcard MX record:
1607 <programlisting>* IN MX 10 external1.example.com.</programlisting>
1609 Now that they accept mail on behalf of anything in the internal
1610 network, the bastion hosts will need to know how to deliver mail
1611 to internal hosts. In order for this to work properly, the resolvers
1613 the bastion hosts will need to be configured to point to the internal
1614 name servers for DNS resolution.
1617 Queries for internal hostnames will be answered by the internal
1618 servers, and queries for external hostnames will be forwarded back
1619 out to the DNS servers on the bastion hosts.
1622 In order for all this to work properly, internal clients will
1623 need to be configured to query <emphasis>only</emphasis> the internal
1624 name servers for DNS queries. This could also be enforced via
1626 filtering on the network.
1629 If everything has been set properly, <emphasis>Example, Inc.</emphasis>'s
1630 internal clients will now be able to:
1635 Look up any hostnames in the <literal>site1</literal>
1637 <literal>site2.example.com</literal> zones.
1642 Look up any hostnames in the <literal>site1.internal</literal> and
1643 <literal>site2.internal</literal> domains.
1647 <simpara>Look up any hostnames on the Internet.</simpara>
1650 <simpara>Exchange mail with both internal and external people.</simpara>
1654 Hosts on the Internet will be able to:
1659 Look up any hostnames in the <literal>site1</literal>
1661 <literal>site2.example.com</literal> zones.
1666 Exchange mail with anyone in the <literal>site1</literal> and
1667 <literal>site2.example.com</literal> zones.
1673 Here is an example configuration for the setup we just
1674 described above. Note that this is only configuration information;
1675 for information on how to configure your zone files, see <xref linkend="sample_configuration"/>.
1679 Internal DNS server config:
1684 acl internals { 172.16.72.0/24; 192.168.1.0/24; };
1686 acl externals { <varname>bastion-ips-go-here</varname>; };
1692 // forward to external servers
1694 <varname>bastion-ips-go-here</varname>;
1696 // sample allow-transfer (no one)
1697 allow-transfer { none; };
1698 // restrict query access
1699 allow-query { internals; externals; };
1700 // restrict recursion
1701 allow-recursion { internals; };
1706 // sample master zone
1707 zone "site1.example.com" {
1709 file "m/site1.example.com";
1710 // do normal iterative resolution (do not forward)
1712 allow-query { internals; externals; };
1713 allow-transfer { internals; };
1716 // sample slave zone
1717 zone "site2.example.com" {
1719 file "s/site2.example.com";
1720 masters { 172.16.72.3; };
1722 allow-query { internals; externals; };
1723 allow-transfer { internals; };
1726 zone "site1.internal" {
1728 file "m/site1.internal";
1730 allow-query { internals; };
1731 allow-transfer { internals; }
1734 zone "site2.internal" {
1736 file "s/site2.internal";
1737 masters { 172.16.72.3; };
1739 allow-query { internals };
1740 allow-transfer { internals; }
1745 External (bastion host) DNS server config:
1749 acl internals { 172.16.72.0/24; 192.168.1.0/24; };
1751 acl externals { bastion-ips-go-here; };
1756 // sample allow-transfer (no one)
1757 allow-transfer { none; };
1758 // default query access
1759 allow-query { any; };
1760 // restrict cache access
1761 allow-query-cache { internals; externals; };
1762 // restrict recursion
1763 allow-recursion { internals; externals; };
1768 // sample slave zone
1769 zone "site1.example.com" {
1771 file "m/site1.foo.com";
1772 allow-transfer { internals; externals; };
1775 zone "site2.example.com" {
1777 file "s/site2.foo.com";
1778 masters { another_bastion_host_maybe; };
1779 allow-transfer { internals; externals; }
1784 In the <filename>resolv.conf</filename> (or equivalent) on
1785 the bastion host(s):
1790 nameserver 172.16.72.2
1791 nameserver 172.16.72.3
1792 nameserver 172.16.72.4
1800 This is a short guide to setting up Transaction SIGnatures
1801 (TSIG) based transaction security in <acronym>BIND</acronym>. It describes changes
1802 to the configuration file as well as what changes are required for
1803 different features, including the process of creating transaction
1804 keys and using transaction signatures with <acronym>BIND</acronym>.
1807 <acronym>BIND</acronym> primarily supports TSIG for server
1808 to server communication.
1809 This includes zone transfer, notify, and recursive query messages.
1810 Resolvers based on newer versions of <acronym>BIND</acronym> 8 have limited support
1815 TSIG can also be useful for dynamic update. A primary
1816 server for a dynamic zone should control access to the dynamic
1817 update service, but IP-based access control is insufficient.
1818 The cryptographic access control provided by TSIG
1819 is far superior. The <command>nsupdate</command>
1820 program supports TSIG via the <option>-k</option> and
1821 <option>-y</option> command line options or inline by use
1822 of the <command>key</command>.
1826 <title>Generate Shared Keys for Each Pair of Hosts</title>
1828 A shared secret is generated to be shared between <emphasis>host1</emphasis> and <emphasis>host2</emphasis>.
1829 An arbitrary key name is chosen: "host1-host2.". The key name must
1830 be the same on both hosts.
1833 <title>Automatic Generation</title>
1835 The following command will generate a 128-bit (16 byte) HMAC-SHA256
1836 key as described above. Longer keys are better, but shorter keys
1837 are easier to read. Note that the maximum key length is the digest
1838 length, here 256 bits.
1841 <userinput>dnssec-keygen -a hmac-sha256 -b 128 -n HOST host1-host2.</userinput>
1844 The key is in the file <filename>Khost1-host2.+163+00000.private</filename>.
1845 Nothing directly uses this file, but the base-64 encoded string
1846 following "<literal>Key:</literal>"
1847 can be extracted from the file and used as a shared secret:
1849 <programlisting>Key: La/E5CjG9O+os1jq0a2jdA==</programlisting>
1851 The string "<literal>La/E5CjG9O+os1jq0a2jdA==</literal>" can
1852 be used as the shared secret.
1856 <title>Manual Generation</title>
1858 The shared secret is simply a random sequence of bits, encoded
1859 in base-64. Most ASCII strings are valid base-64 strings (assuming
1860 the length is a multiple of 4 and only valid characters are used),
1861 so the shared secret can be manually generated.
1864 Also, a known string can be run through <command>mmencode</command> or
1865 a similar program to generate base-64 encoded data.
1870 <title>Copying the Shared Secret to Both Machines</title>
1872 This is beyond the scope of DNS. A secure transport mechanism
1873 should be used. This could be secure FTP, ssh, telephone, etc.
1877 <title>Informing the Servers of the Key's Existence</title>
1879 Imagine <emphasis>host1</emphasis> and <emphasis>host 2</emphasis>
1881 both servers. The following is added to each server's <filename>named.conf</filename> file:
1886 algorithm hmac-sha256;
1887 secret "La/E5CjG9O+os1jq0a2jdA==";
1892 The secret is the one generated above. Since this is a secret, it
1893 is recommended that either <filename>named.conf</filename> be
1894 non-world readable, or the key directive be added to a non-world
1895 readable file that is included by <filename>named.conf</filename>.
1898 At this point, the key is recognized. This means that if the
1899 server receives a message signed by this key, it can verify the
1900 signature. If the signature is successfully verified, the
1901 response is signed by the same key.
1906 <title>Instructing the Server to Use the Key</title>
1908 Since keys are shared between two hosts only, the server must
1909 be told when keys are to be used. The following is added to the <filename>named.conf</filename> file
1910 for <emphasis>host1</emphasis>, if the IP address of <emphasis>host2</emphasis> is
1916 keys { host1-host2. ;};
1921 Multiple keys may be present, but only the first is used.
1922 This directive does not contain any secrets, so it may be in a
1927 If <emphasis>host1</emphasis> sends a message that is a request
1928 to that address, the message will be signed with the specified key. <emphasis>host1</emphasis> will
1929 expect any responses to signed messages to be signed with the same
1933 A similar statement must be present in <emphasis>host2</emphasis>'s
1934 configuration file (with <emphasis>host1</emphasis>'s address) for <emphasis>host2</emphasis> to
1935 sign request messages to <emphasis>host1</emphasis>.
1939 <title>TSIG Key Based Access Control</title>
1941 <acronym>BIND</acronym> allows IP addresses and ranges
1942 to be specified in ACL
1944 <command>allow-{ query | transfer | update }</command>
1946 This has been extended to allow TSIG keys also. The above key would
1947 be denoted <command>key host1-host2.</command>
1950 An example of an <command>allow-update</command> directive would be:
1954 allow-update { key host1-host2. ;};
1958 This allows dynamic updates to succeed only if the request
1959 was signed by a key named "<command>host1-host2.</command>".
1963 See <xref linkend="dynamic_update_policies"/> for a discussion of
1964 the more flexible <command>update-policy</command> statement.
1969 <title>Errors</title>
1972 The processing of TSIG signed messages can result in
1973 several errors. If a signed message is sent to a non-TSIG aware
1974 server, a FORMERR (format error) will be returned, since the server will not
1975 understand the record. This is a result of misconfiguration,
1976 since the server must be explicitly configured to send a TSIG
1977 signed message to a specific server.
1981 If a TSIG aware server receives a message signed by an
1982 unknown key, the response will be unsigned with the TSIG
1983 extended error code set to BADKEY. If a TSIG aware server
1984 receives a message with a signature that does not validate, the
1985 response will be unsigned with the TSIG extended error code set
1986 to BADSIG. If a TSIG aware server receives a message with a time
1987 outside of the allowed range, the response will be signed with
1988 the TSIG extended error code set to BADTIME, and the time values
1989 will be adjusted so that the response can be successfully
1990 verified. In any of these cases, the message's rcode (response code) is set to
1991 NOTAUTH (not authenticated).
1999 <para><command>TKEY</command>
2000 is a mechanism for automatically generating a shared secret
2001 between two hosts. There are several "modes" of
2002 <command>TKEY</command> that specify how the key is generated
2003 or assigned. <acronym>BIND</acronym> 9 implements only one of
2004 these modes, the Diffie-Hellman key exchange. Both hosts are
2005 required to have a Diffie-Hellman KEY record (although this
2006 record is not required to be present in a zone). The
2007 <command>TKEY</command> process must use signed messages,
2008 signed either by TSIG or SIG(0). The result of
2009 <command>TKEY</command> is a shared secret that can be used to
2010 sign messages with TSIG. <command>TKEY</command> can also be
2011 used to delete shared secrets that it had previously
2016 The <command>TKEY</command> process is initiated by a
2018 or server by sending a signed <command>TKEY</command>
2020 (including any appropriate KEYs) to a TKEY-aware server. The
2021 server response, if it indicates success, will contain a
2022 <command>TKEY</command> record and any appropriate keys.
2024 this exchange, both participants have enough information to
2025 determine the shared secret; the exact process depends on the
2026 <command>TKEY</command> mode. When using the
2028 <command>TKEY</command> mode, Diffie-Hellman keys are
2030 and the shared secret is derived by both participants.
2035 <title>SIG(0)</title>
2038 <acronym>BIND</acronym> 9 partially supports DNSSEC SIG(0)
2039 transaction signatures as specified in RFC 2535 and RFC 2931.
2041 uses public/private keys to authenticate messages. Access control
2042 is performed in the same manner as TSIG keys; privileges can be
2043 granted or denied based on the key name.
2047 When a SIG(0) signed message is received, it will only be
2048 verified if the key is known and trusted by the server; the server
2049 will not attempt to locate and/or validate the key.
2053 SIG(0) signing of multiple-message TCP streams is not
2058 The only tool shipped with <acronym>BIND</acronym> 9 that
2059 generates SIG(0) signed messages is <command>nsupdate</command>.
2064 <title>DNSSEC</title>
2067 Cryptographic authentication of DNS information is possible
2068 through the DNS Security (<emphasis>DNSSEC-bis</emphasis>) extensions,
2069 defined in RFC 4033, RFC 4034, and RFC 4035.
2070 This section describes the creation and use of DNSSEC signed zones.
2074 In order to set up a DNSSEC secure zone, there are a series
2075 of steps which must be followed. <acronym>BIND</acronym>
2078 that are used in this process, which are explained in more detail
2079 below. In all cases, the <option>-h</option> option prints a
2080 full list of parameters. Note that the DNSSEC tools require the
2081 keyset files to be in the working directory or the
2082 directory specified by the <option>-d</option> option, and
2083 that the tools shipped with BIND 9.2.x and earlier are not compatible
2084 with the current ones.
2088 There must also be communication with the administrators of
2089 the parent and/or child zone to transmit keys. A zone's security
2090 status must be indicated by the parent zone for a DNSSEC capable
2091 resolver to trust its data. This is done through the presence
2092 or absence of a <literal>DS</literal> record at the
2098 For other servers to trust data in this zone, they must
2099 either be statically configured with this zone's zone key or the
2100 zone key of another zone above this one in the DNS tree.
2104 <title>Generating Keys</title>
2107 The <command>dnssec-keygen</command> program is used to
2112 A secure zone must contain one or more zone keys. The
2113 zone keys will sign all other records in the zone, as well as
2114 the zone keys of any secure delegated zones. Zone keys must
2115 have the same name as the zone, a name type of
2116 <command>ZONE</command>, and must be usable for
2118 It is recommended that zone keys use a cryptographic algorithm
2119 designated as "mandatory to implement" by the IETF; currently
2120 the only one is RSASHA1.
2124 The following command will generate a 768-bit RSASHA1 key for
2125 the <filename>child.example</filename> zone:
2129 <userinput>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</userinput>
2133 Two output files will be produced:
2134 <filename>Kchild.example.+005+12345.key</filename> and
2135 <filename>Kchild.example.+005+12345.private</filename>
2137 12345 is an example of a key tag). The key filenames contain
2138 the key name (<filename>child.example.</filename>),
2140 is DSA, 1 is RSAMD5, 5 is RSASHA1, etc.), and the key tag (12345 in
2142 The private key (in the <filename>.private</filename>
2144 used to generate signatures, and the public key (in the
2145 <filename>.key</filename> file) is used for signature
2150 To generate another key with the same properties (but with
2151 a different key tag), repeat the above command.
2155 The <command>dnssec-keyfromlabel</command> program is used
2156 to get a key pair from a crypto hardware and build the key
2157 files. Its usage is similar to <command>dnssec-keygen</command>.
2161 The public keys should be inserted into the zone file by
2162 including the <filename>.key</filename> files using
2163 <command>$INCLUDE</command> statements.
2168 <title>Signing the Zone</title>
2171 The <command>dnssec-signzone</command> program is used
2176 Any <filename>keyset</filename> files corresponding to
2177 secure subzones should be present. The zone signer will
2178 generate <literal>NSEC</literal>, <literal>NSEC3</literal>
2179 and <literal>RRSIG</literal> records for the zone, as
2180 well as <literal>DS</literal> for the child zones if
2181 <literal>'-g'</literal> is specified. If <literal>'-g'</literal>
2182 is not specified, then DS RRsets for the secure child
2183 zones need to be added manually.
2187 The following command signs the zone, assuming it is in a
2188 file called <filename>zone.child.example</filename>. By
2189 default, all zone keys which have an available private key are
2190 used to generate signatures.
2194 <userinput>dnssec-signzone -o child.example zone.child.example</userinput>
2198 One output file is produced:
2199 <filename>zone.child.example.signed</filename>. This
2201 should be referenced by <filename>named.conf</filename>
2203 input file for the zone.
2206 <para><command>dnssec-signzone</command>
2207 will also produce a keyset and dsset files and optionally a
2208 dlvset file. These are used to provide the parent zone
2209 administrators with the <literal>DNSKEYs</literal> (or their
2210 corresponding <literal>DS</literal> records) that are the
2211 secure entry point to the zone.
2217 <title>Configuring Servers</title>
2220 To enable <command>named</command> to respond appropriately
2221 to DNS requests from DNSSEC aware clients,
2222 <command>dnssec-enable</command> must be set to yes.
2223 (This is the default setting.)
2227 To enable <command>named</command> to validate answers from
2228 other servers, the <command>dnssec-enable</command> option
2229 must be set to <userinput>yes</userinput>, and the
2230 <command>dnssec-validation</command> options must be set to
2231 <userinput>yes</userinput> or <userinput>auto</userinput>.
2235 If <command>dnssec-validation</command> is set to
2236 <userinput>auto</userinput>, then a default
2237 trust anchor for the DNS root zone will be used.
2238 If it is set to <userinput>yes</userinput>, however,
2239 then at least one trust anchor must be configured
2240 with a <command>trusted-keys</command> or
2241 <command>managed-keys</command> statement in
2242 <filename>named.conf</filename>, or DNSSEC validation
2243 will not occur. The default setting is
2244 <userinput>yes</userinput>.
2248 <command>trusted-keys</command> are copies of DNSKEY RRs
2249 for zones that are used to form the first link in the
2250 cryptographic chain of trust. All keys listed in
2251 <command>trusted-keys</command> (and corresponding zones)
2252 are deemed to exist and only the listed keys will be used
2253 to validated the DNSKEY RRset that they are from.
2257 <command>managed-keys</command> are trusted keys which are
2258 automatically kept up to date via RFC 5011 trust anchor
2263 <command>trusted-keys</command> and
2264 <command>managed-keys</command> are described in more detail
2265 later in this document.
2269 Unlike <acronym>BIND</acronym> 8, <acronym>BIND</acronym>
2270 9 does not verify signatures on load, so zone keys for
2271 authoritative zones do not need to be specified in the
2276 After DNSSEC gets established, a typical DNSSEC configuration
2277 will look something like the following. It has one or
2278 more public keys for the root. This allows answers from
2279 outside the organization to be validated. It will also
2280 have several keys for parts of the namespace the organization
2281 controls. These are here to ensure that <command>named</command>
2282 is immune to compromises in the DNSSEC components of the security
2289 "." initial-key 257 3 3 "BNY4wrWM1nCfJ+CXd0rVXyYmobt7sEEfK3clRbGaTwS
2290 JxrGkxJWoZu6I7PzJu/E9gx4UC1zGAHlXKdE4zYIpRh
2291 aBKnvcC2U9mZhkdUpd1Vso/HAdjNe8LmMlnzY3zy2Xy
2292 4klWOADTPzSv9eamj8V18PHGjBLaVtYvk/ln5ZApjYg
2293 hf+6fElrmLkdaz MQ2OCnACR817DF4BBa7UR/beDHyp
2294 5iWTXWSi6XmoJLbG9Scqc7l70KDqlvXR3M/lUUVRbke
2295 g1IPJSidmK3ZyCllh4XSKbje/45SKucHgnwU5jefMtq
2296 66gKodQj+MiA21AfUVe7u99WzTLzY3qlxDhxYQQ20FQ
2297 97S+LKUTpQcq27R7AT3/V5hRQxScINqwcz4jYqZD2fQ
2298 dgxbcDTClU0CRBdiieyLMNzXG3";
2302 /* Key for our organization's forward zone */
2303 example.com. 257 3 5 "AwEAAaxPMcR2x0HbQV4WeZB6oEDX+r0QM6
2304 5KbhTjrW1ZaARmPhEZZe3Y9ifgEuq7vZ/z
2305 GZUdEGNWy+JZzus0lUptwgjGwhUS1558Hb
2306 4JKUbbOTcM8pwXlj0EiX3oDFVmjHO444gL
2307 kBOUKUf/mC7HvfwYH/Be22GnClrinKJp1O
2308 g4ywzO9WglMk7jbfW33gUKvirTHr25GL7S
2309 TQUzBb5Usxt8lgnyTUHs1t3JwCY5hKZ6Cq
2310 FxmAVZP20igTixin/1LcrgX/KMEGd/biuv
2311 F4qJCyduieHukuY3H4XMAcR+xia2nIUPvm
2312 /oyWR8BW/hWdzOvnSCThlHf3xiYleDbt/o
2315 /* Key for our reverse zone. */
2316 2.0.192.IN-ADDRPA.NET. 257 3 5 "AQOnS4xn/IgOUpBPJ3bogzwc
2317 xOdNax071L18QqZnQQQAVVr+i
2318 LhGTnNGp3HoWQLUIzKrJVZ3zg
2319 gy3WwNT6kZo6c0tszYqbtvchm
2320 gQC8CzKojM/W16i6MG/eafGU3
2321 siaOdS0yOI6BgPsw+YZdzlYMa
2322 IJGf4M4dyoKIhzdZyQ2bYQrjy
2323 Q4LB0lC7aOnsMyYKHHYeRvPxj
2324 IQXmdqgOJGq+vsevG06zW+1xg
2325 YJh9rCIfnm1GX/KMgxLPG2vXT
2326 D/RnLX+D3T3UL7HJYHJhAZD5L
2327 59VvjSPsZJHeDCUyWYrvPZesZ
2328 DIRvhDD52SKvbheeTJUm6Ehkz
2329 ytNN2SN96QRk8j/iI8ib";
2335 dnssec-validation yes;
2340 None of the keys listed in this example are valid. In particular,
2341 the root key is not valid.
2345 When DNSSEC validation is enabled and properly configured,
2346 the resolver will reject any answers from signed, secure zones
2347 which fail to validate, and will return SERVFAIL to the client.
2351 Responses may fail to validate for any of several reasons,
2352 including missing, expired, or invalid signatures, a key which
2353 does not match the DS RRset in the parent zone, or an insecure
2354 response from a zone which, according to its parent, should have
2360 When the validator receives a response from an unsigned zone
2361 that has a signed parent, it must confirm with the parent
2362 that the zone was intentionally left unsigned. It does
2363 this by verifying, via signed and validated NSEC/NSEC3 records,
2364 that the parent zone contains no DS records for the child.
2367 If the validator <emphasis>can</emphasis> prove that the zone
2368 is insecure, then the response is accepted. However, if it
2369 cannot, then it must assume an insecure response to be a
2370 forgery; it rejects the response and logs an error.
2373 The logged error reads "insecurity proof failed" and
2374 "got insecure response; parent indicates it should be secure".
2375 (Prior to BIND 9.7, the logged error was "not insecure".
2376 This referred to the zone, not the response.)
2383 <xi:include href="dnssec.xml"/>
2385 <xi:include href="managed-keys.xml"/>
2387 <xi:include href="pkcs11.xml"/>
2390 <title>IPv6 Support in <acronym>BIND</acronym> 9</title>
2393 <acronym>BIND</acronym> 9 fully supports all currently
2394 defined forms of IPv6 name to address and address to name
2395 lookups. It will also use IPv6 addresses to make queries when
2396 running on an IPv6 capable system.
2400 For forward lookups, <acronym>BIND</acronym> 9 supports
2401 only AAAA records. RFC 3363 deprecated the use of A6 records,
2402 and client-side support for A6 records was accordingly removed
2403 from <acronym>BIND</acronym> 9.
2404 However, authoritative <acronym>BIND</acronym> 9 name servers still
2405 load zone files containing A6 records correctly, answer queries
2406 for A6 records, and accept zone transfer for a zone containing A6
2411 For IPv6 reverse lookups, <acronym>BIND</acronym> 9 supports
2412 the traditional "nibble" format used in the
2413 <emphasis>ip6.arpa</emphasis> domain, as well as the older, deprecated
2414 <emphasis>ip6.int</emphasis> domain.
2415 Older versions of <acronym>BIND</acronym> 9
2416 supported the "binary label" (also known as "bitstring") format,
2417 but support of binary labels has been completely removed per
2419 Many applications in <acronym>BIND</acronym> 9 do not understand
2420 the binary label format at all any more, and will return an
2422 In particular, an authoritative <acronym>BIND</acronym> 9
2423 name server will not load a zone file containing binary labels.
2427 For an overview of the format and structure of IPv6 addresses,
2428 see <xref linkend="ipv6addresses"/>.
2432 <title>Address Lookups Using AAAA Records</title>
2435 The IPv6 AAAA record is a parallel to the IPv4 A record,
2436 and, unlike the deprecated A6 record, specifies the entire
2437 IPv6 address in a single record. For example,
2441 $ORIGIN example.com.
2442 host 3600 IN AAAA 2001:db8::1
2446 Use of IPv4-in-IPv6 mapped addresses is not recommended.
2447 If a host has an IPv4 address, use an A record, not
2448 a AAAA, with <literal>::ffff:192.168.42.1</literal> as
2453 <title>Address to Name Lookups Using Nibble Format</title>
2456 When looking up an address in nibble format, the address
2457 components are simply reversed, just as in IPv4, and
2458 <literal>ip6.arpa.</literal> is appended to the
2460 For example, the following would provide reverse name lookup for
2462 <literal>2001:db8::1</literal>.
2466 $ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
2467 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 14400 IN PTR (
2475 <chapter id="Bv9ARM.ch05">
2476 <title>The <acronym>BIND</acronym> 9 Lightweight Resolver</title>
2478 <title>The Lightweight Resolver Library</title>
2480 Traditionally applications have been linked with a stub resolver
2481 library that sends recursive DNS queries to a local caching name
2485 IPv6 once introduced new complexity into the resolution process,
2486 such as following A6 chains and DNAME records, and simultaneous
2487 lookup of IPv4 and IPv6 addresses. Though most of the complexity was
2488 then removed, these are hard or impossible
2489 to implement in a traditional stub resolver.
2492 <acronym>BIND</acronym> 9 therefore can also provide resolution
2493 services to local clients
2494 using a combination of a lightweight resolver library and a resolver
2495 daemon process running on the local host. These communicate using
2496 a simple UDP-based protocol, the "lightweight resolver protocol"
2497 that is distinct from and simpler than the full DNS protocol.
2501 <title>Running a Resolver Daemon</title>
2504 To use the lightweight resolver interface, the system must
2505 run the resolver daemon <command>lwresd</command> or a
2507 name server configured with a <command>lwres</command>
2512 By default, applications using the lightweight resolver library will
2514 UDP requests to the IPv4 loopback address (127.0.0.1) on port 921.
2516 address can be overridden by <command>lwserver</command>
2518 <filename>/etc/resolv.conf</filename>.
2522 The daemon currently only looks in the DNS, but in the future
2523 it may use other sources such as <filename>/etc/hosts</filename>,
2528 The <command>lwresd</command> daemon is essentially a
2529 caching-only name server that responds to requests using the
2531 resolver protocol rather than the DNS protocol. Because it needs
2532 to run on each host, it is designed to require no or minimal
2534 Unless configured otherwise, it uses the name servers listed on
2535 <command>nameserver</command> lines in <filename>/etc/resolv.conf</filename>
2536 as forwarders, but is also capable of doing the resolution
2541 The <command>lwresd</command> daemon may also be
2543 <filename>named.conf</filename> style configuration file,
2545 <filename>/etc/lwresd.conf</filename> by default. A name
2547 be configured to act as a lightweight resolver daemon using the
2548 <command>lwres</command> statement in <filename>named.conf</filename>.
2554 <chapter id="Bv9ARM.ch06">
2555 <title><acronym>BIND</acronym> 9 Configuration Reference</title>
2558 <acronym>BIND</acronym> 9 configuration is broadly similar
2559 to <acronym>BIND</acronym> 8; however, there are a few new
2561 of configuration, such as views. <acronym>BIND</acronym>
2562 8 configuration files should work with few alterations in <acronym>BIND</acronym>
2563 9, although more complex configurations should be reviewed to check
2564 if they can be more efficiently implemented using the new features
2565 found in <acronym>BIND</acronym> 9.
2569 <acronym>BIND</acronym> 4 configuration files can be
2570 converted to the new format
2571 using the shell script
2572 <filename>contrib/named-bootconf/named-bootconf.sh</filename>.
2574 <sect1 id="configuration_file_elements">
2575 <title>Configuration File Elements</title>
2577 Following is a list of elements used throughout the <acronym>BIND</acronym> configuration
2580 <informaltable colsep="0" rowsep="0">
2581 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="2Level-table">
2582 <colspec colname="1" colnum="1" colsep="0" colwidth="1.855in"/>
2583 <colspec colname="2" colnum="2" colsep="0" colwidth="3.770in"/>
2588 <varname>acl_name</varname>
2593 The name of an <varname>address_match_list</varname> as
2594 defined by the <command>acl</command> statement.
2601 <varname>address_match_list</varname>
2606 A list of one or more
2607 <varname>ip_addr</varname>,
2608 <varname>ip_prefix</varname>, <varname>key_id</varname>,
2609 or <varname>acl_name</varname> elements, see
2610 <xref linkend="address_match_lists"/>.
2617 <varname>masters_list</varname>
2622 A named list of one or more <varname>ip_addr</varname>
2623 with optional <varname>key_id</varname> and/or
2624 <varname>ip_port</varname>.
2625 A <varname>masters_list</varname> may include other
2626 <varname>masters_lists</varname>.
2633 <varname>domain_name</varname>
2638 A quoted string which will be used as
2639 a DNS name, for example "<literal>my.test.domain</literal>".
2646 <varname>namelist</varname>
2651 A list of one or more <varname>domain_name</varname>
2659 <varname>dotted_decimal</varname>
2664 One to four integers valued 0 through
2665 255 separated by dots (`.'), such as <command>123</command>,
2666 <command>45.67</command> or <command>89.123.45.67</command>.
2673 <varname>ip4_addr</varname>
2678 An IPv4 address with exactly four elements
2679 in <varname>dotted_decimal</varname> notation.
2686 <varname>ip6_addr</varname>
2691 An IPv6 address, such as <command>2001:db8::1234</command>.
2692 IPv6 scoped addresses that have ambiguity on their
2693 scope zones must be disambiguated by an appropriate
2694 zone ID with the percent character (`%') as
2695 delimiter. It is strongly recommended to use
2696 string zone names rather than numeric identifiers,
2697 in order to be robust against system configuration
2698 changes. However, since there is no standard
2699 mapping for such names and identifier values,
2700 currently only interface names as link identifiers
2701 are supported, assuming one-to-one mapping between
2702 interfaces and links. For example, a link-local
2703 address <command>fe80::1</command> on the link
2704 attached to the interface <command>ne0</command>
2705 can be specified as <command>fe80::1%ne0</command>.
2706 Note that on most systems link-local addresses
2707 always have the ambiguity, and need to be
2715 <varname>ip_addr</varname>
2720 An <varname>ip4_addr</varname> or <varname>ip6_addr</varname>.
2727 <varname>ip_port</varname>
2732 An IP port <varname>number</varname>.
2733 The <varname>number</varname> is limited to 0
2734 through 65535, with values
2735 below 1024 typically restricted to use by processes running
2737 In some cases, an asterisk (`*') character can be used as a
2739 select a random high-numbered port.
2746 <varname>ip_prefix</varname>
2751 An IP network specified as an <varname>ip_addr</varname>,
2752 followed by a slash (`/') and then the number of bits in the
2754 Trailing zeros in a <varname>ip_addr</varname>
2756 For example, <command>127/8</command> is the
2757 network <command>127.0.0.0</command> with
2758 netmask <command>255.0.0.0</command> and <command>1.2.3.0/28</command> is
2759 network <command>1.2.3.0</command> with netmask <command>255.255.255.240</command>.
2762 When specifying a prefix involving a IPv6 scoped address
2763 the scope may be omitted. In that case the prefix will
2764 match packets from any scope.
2771 <varname>key_id</varname>
2776 A <varname>domain_name</varname> representing
2777 the name of a shared key, to be used for transaction
2785 <varname>key_list</varname>
2790 A list of one or more
2791 <varname>key_id</varname>s,
2792 separated by semicolons and ending with a semicolon.
2799 <varname>number</varname>
2804 A non-negative 32-bit integer
2805 (i.e., a number between 0 and 4294967295, inclusive).
2806 Its acceptable value might further
2807 be limited by the context in which it is used.
2814 <varname>path_name</varname>
2819 A quoted string which will be used as
2820 a pathname, such as <filename>zones/master/my.test.domain</filename>.
2827 <varname>port_list</varname>
2832 A list of an <varname>ip_port</varname> or a port
2834 A port range is specified in the form of
2835 <userinput>range</userinput> followed by
2836 two <varname>ip_port</varname>s,
2837 <varname>port_low</varname> and
2838 <varname>port_high</varname>, which represents
2839 port numbers from <varname>port_low</varname> through
2840 <varname>port_high</varname>, inclusive.
2841 <varname>port_low</varname> must not be larger than
2842 <varname>port_high</varname>.
2844 <userinput>range 1024 65535</userinput> represents
2845 ports from 1024 through 65535.
2846 In either case an asterisk (`*') character is not
2847 allowed as a valid <varname>ip_port</varname>.
2854 <varname>size_spec</varname>
2859 A 64-bit unsigned integer, or the keywords
2860 <userinput>unlimited</userinput> or
2861 <userinput>default</userinput>.
2864 Integers may take values
2865 0 <= value <= 18446744073709551615, though
2866 certain parameters may use a more limited range
2867 within these extremes. In most cases, setting a
2868 value to 0 does not literally mean zero; it means
2869 "undefined" or "as big as psosible", depending on
2870 the context. See the expalantions of particular
2871 parameters that use <varname>size_spec</varname>
2872 for details on how they interpret its use.
2875 Numeric values can optionally be followed by a
2877 <userinput>K</userinput> or <userinput>k</userinput>
2879 <userinput>M</userinput> or <userinput>m</userinput>
2881 <userinput>G</userinput> or <userinput>g</userinput>
2882 for gigabytes, which scale by 1024, 1024*1024, and
2883 1024*1024*1024 respectively.
2886 <varname>unlimited</varname> generally means
2887 "as big as possible", though in certain contexts,
2888 (including <option>max-cache-size</option>), it may
2889 mean the largest possible 32-bit unsigned integer
2890 (0xffffffff); this distinction can be important when
2891 dealing with larger quantities.
2892 <varname>unlimited</varname> is usually the best way
2893 to safely set a very large number.
2896 <varname>default</varname>
2897 uses the limit that was in force when the server was started.
2904 <varname>yes_or_no</varname>
2909 Either <userinput>yes</userinput> or <userinput>no</userinput>.
2910 The words <userinput>true</userinput> and <userinput>false</userinput> are
2911 also accepted, as are the numbers <userinput>1</userinput>
2912 and <userinput>0</userinput>.
2919 <varname>dialup_option</varname>
2924 One of <userinput>yes</userinput>,
2925 <userinput>no</userinput>, <userinput>notify</userinput>,
2926 <userinput>notify-passive</userinput>, <userinput>refresh</userinput> or
2927 <userinput>passive</userinput>.
2928 When used in a zone, <userinput>notify-passive</userinput>,
2929 <userinput>refresh</userinput>, and <userinput>passive</userinput>
2930 are restricted to slave and stub zones.
2937 <sect2 id="address_match_lists">
2938 <title>Address Match Lists</title>
2940 <title>Syntax</title>
2942 <programlisting><varname>address_match_list</varname> = address_match_list_element ;
2943 <optional> address_match_list_element; ... </optional>
2944 <varname>address_match_list_element</varname> = <optional> ! </optional> (ip_address <optional>/length</optional> |
2945 key key_id | acl_name | { address_match_list } )
2950 <title>Definition and Usage</title>
2952 Address match lists are primarily used to determine access
2953 control for various server operations. They are also used in
2954 the <command>listen-on</command> and <command>sortlist</command>
2955 statements. The elements which constitute an address match
2956 list can be any of the following:
2960 <simpara>an IP address (IPv4 or IPv6)</simpara>
2963 <simpara>an IP prefix (in `/' notation)</simpara>
2967 a key ID, as defined by the <command>key</command>
2972 <simpara>the name of an address match list defined with
2973 the <command>acl</command> statement
2977 <simpara>a nested address match list enclosed in braces</simpara>
2982 Elements can be negated with a leading exclamation mark (`!'),
2983 and the match list names "any", "none", "localhost", and
2984 "localnets" are predefined. More information on those names
2985 can be found in the description of the acl statement.
2989 The addition of the key clause made the name of this syntactic
2990 element something of a misnomer, since security keys can be used
2991 to validate access without regard to a host or network address.
2992 Nonetheless, the term "address match list" is still used
2993 throughout the documentation.
2997 When a given IP address or prefix is compared to an address
2998 match list, the comparison takes place in approximately O(1)
2999 time. However, key comparisons require that the list of keys
3000 be traversed until a matching key is found, and therefore may
3005 The interpretation of a match depends on whether the list is being
3006 used for access control, defining <command>listen-on</command> ports, or in a
3007 <command>sortlist</command>, and whether the element was negated.
3011 When used as an access control list, a non-negated match
3012 allows access and a negated match denies access. If
3013 there is no match, access is denied. The clauses
3014 <command>allow-notify</command>,
3015 <command>allow-recursion</command>,
3016 <command>allow-recursion-on</command>,
3017 <command>allow-query</command>,
3018 <command>allow-query-on</command>,
3019 <command>allow-query-cache</command>,
3020 <command>allow-query-cache-on</command>,
3021 <command>allow-transfer</command>,
3022 <command>allow-update</command>,
3023 <command>allow-update-forwarding</command>, and
3024 <command>blackhole</command> all use address match
3025 lists. Similarly, the <command>listen-on</command> option will cause the
3026 server to refuse queries on any of the machine's
3027 addresses which do not match the list.
3031 Order of insertion is significant. If more than one element
3032 in an ACL is found to match a given IP address or prefix,
3033 preference will be given to the one that came
3034 <emphasis>first</emphasis> in the ACL definition.
3035 Because of this first-match behavior, an element that
3036 defines a subset of another element in the list should
3037 come before the broader element, regardless of whether
3038 either is negated. For example, in
3039 <command>1.2.3/24; ! 1.2.3.13;</command>
3040 the 1.2.3.13 element is completely useless because the
3041 algorithm will match any lookup for 1.2.3.13 to the 1.2.3/24
3042 element. Using <command>! 1.2.3.13; 1.2.3/24</command> fixes
3043 that problem by having 1.2.3.13 blocked by the negation, but
3044 all other 1.2.3.* hosts fall through.
3050 <title>Comment Syntax</title>
3053 The <acronym>BIND</acronym> 9 comment syntax allows for
3055 anywhere that whitespace may appear in a <acronym>BIND</acronym> configuration
3056 file. To appeal to programmers of all kinds, they can be written
3057 in the C, C++, or shell/perl style.
3061 <title>Syntax</title>
3064 <programlisting>/* This is a <acronym>BIND</acronym> comment as in C */</programlisting>
3065 <programlisting>// This is a <acronym>BIND</acronym> comment as in C++</programlisting>
3066 <programlisting># This is a <acronym>BIND</acronym> comment as in common UNIX shells
3067 # and perl</programlisting>
3071 <title>Definition and Usage</title>
3073 Comments may appear anywhere that whitespace may appear in
3074 a <acronym>BIND</acronym> configuration file.
3077 C-style comments start with the two characters /* (slash,
3078 star) and end with */ (star, slash). Because they are completely
3079 delimited with these characters, they can be used to comment only
3080 a portion of a line or to span multiple lines.
3083 C-style comments cannot be nested. For example, the following
3084 is not valid because the entire comment ends with the first */:
3088 <programlisting>/* This is the start of a comment.
3089 This is still part of the comment.
3090 /* This is an incorrect attempt at nesting a comment. */
3091 This is no longer in any comment. */
3097 C++-style comments start with the two characters // (slash,
3098 slash) and continue to the end of the physical line. They cannot
3099 be continued across multiple physical lines; to have one logical
3100 comment span multiple lines, each line must use the // pair.
3105 <programlisting>// This is the start of a comment. The next line
3106 // is a new comment, even though it is logically
3107 // part of the previous comment.
3112 Shell-style (or perl-style, if you prefer) comments start
3113 with the character <literal>#</literal> (number sign)
3114 and continue to the end of the
3115 physical line, as in C++ comments.
3121 <programlisting># This is the start of a comment. The next line
3122 # is a new comment, even though it is logically
3123 # part of the previous comment.
3130 You cannot use the semicolon (`;') character
3131 to start a comment such as you would in a zone file. The
3132 semicolon indicates the end of a configuration
3140 <sect1 id="Configuration_File_Grammar">
3141 <title>Configuration File Grammar</title>
3144 A <acronym>BIND</acronym> 9 configuration consists of
3145 statements and comments.
3146 Statements end with a semicolon. Statements and comments are the
3147 only elements that can appear without enclosing braces. Many
3148 statements contain a block of sub-statements, which are also
3149 terminated with a semicolon.
3153 The following statements are supported:
3156 <informaltable colsep="0" rowsep="0">
3157 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="2Level-table">
3158 <colspec colname="1" colnum="1" colsep="0" colwidth="1.336in"/>
3159 <colspec colname="2" colnum="2" colsep="0" colwidth="3.778in"/>
3163 <para><command>acl</command></para>
3167 defines a named IP address
3168 matching list, for access control and other uses.
3174 <para><command>controls</command></para>
3178 declares control channels to be used
3179 by the <command>rndc</command> utility.
3185 <para><command>include</command></para>
3195 <para><command>key</command></para>
3199 specifies key information for use in
3200 authentication and authorization using TSIG.
3206 <para><command>logging</command></para>
3210 specifies what the server logs, and where
3211 the log messages are sent.
3217 <para><command>lwres</command></para>
3221 configures <command>named</command> to
3222 also act as a light-weight resolver daemon (<command>lwresd</command>).
3228 <para><command>masters</command></para>
3232 defines a named masters list for
3233 inclusion in stub and slave zone masters clauses.
3239 <para><command>options</command></para>
3243 controls global server configuration
3244 options and sets defaults for other statements.
3250 <para><command>server</command></para>
3254 sets certain configuration options on
3261 <para><command>statistics-channels</command></para>
3265 declares communication channels to get access to
3266 <command>named</command> statistics.
3272 <para><command>trusted-keys</command></para>
3276 defines trusted DNSSEC keys.
3282 <para><command>managed-keys</command></para>
3286 lists DNSSEC keys to be kept up to date
3287 using RFC 5011 trust anchor maintenance.
3293 <para><command>view</command></para>
3303 <para><command>zone</command></para>
3316 The <command>logging</command> and
3317 <command>options</command> statements may only occur once
3323 <title><command>acl</command> Statement Grammar</title>
3325 <programlisting><command>acl</command> acl-name {
3332 <title><command>acl</command> Statement Definition and
3336 The <command>acl</command> statement assigns a symbolic
3337 name to an address match list. It gets its name from a primary
3338 use of address match lists: Access Control Lists (ACLs).
3342 Note that an address match list's name must be defined
3343 with <command>acl</command> before it can be used
3344 elsewhere; no forward references are allowed.
3348 The following ACLs are built-in:
3351 <informaltable colsep="0" rowsep="0">
3352 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table">
3353 <colspec colname="1" colnum="1" colsep="0" colwidth="1.130in"/>
3354 <colspec colname="2" colnum="2" colsep="0" colwidth="4.000in"/>
3358 <para><command>any</command></para>
3368 <para><command>none</command></para>
3378 <para><command>localhost</command></para>
3382 Matches the IPv4 and IPv6 addresses of all network
3383 interfaces on the system.
3389 <para><command>localnets</command></para>
3393 Matches any host on an IPv4 or IPv6 network
3394 for which the system has an interface.
3395 Some systems do not provide a way to determine the prefix
3397 local IPv6 addresses.
3398 In such a case, <command>localnets</command>
3399 only matches the local
3400 IPv6 addresses, just like <command>localhost</command>.
3410 <title><command>controls</command> Statement Grammar</title>
3412 <programlisting><command>controls</command> {
3413 [ inet ( ip_addr | * ) [ port ip_port ]
3414 allow { <replaceable> address_match_list </replaceable> }
3415 keys { <replaceable>key_list</replaceable> }; ]
3417 [ unix <replaceable>path</replaceable> perm <replaceable>number</replaceable> owner <replaceable>number</replaceable> group <replaceable>number</replaceable>
3418 keys { <replaceable>key_list</replaceable> }; ]
3425 <sect2 id="controls_statement_definition_and_usage">
3426 <title><command>controls</command> Statement Definition and
3430 The <command>controls</command> statement declares control
3431 channels to be used by system administrators to control the
3432 operation of the name server. These control channels are
3433 used by the <command>rndc</command> utility to send
3434 commands to and retrieve non-DNS results from a name server.
3438 An <command>inet</command> control channel is a TCP socket
3439 listening at the specified <command>ip_port</command> on the
3440 specified <command>ip_addr</command>, which can be an IPv4 or IPv6
3441 address. An <command>ip_addr</command> of <literal>*</literal> (asterisk) is
3442 interpreted as the IPv4 wildcard address; connections will be
3443 accepted on any of the system's IPv4 addresses.
3444 To listen on the IPv6 wildcard address,
3445 use an <command>ip_addr</command> of <literal>::</literal>.
3446 If you will only use <command>rndc</command> on the local host,
3447 using the loopback address (<literal>127.0.0.1</literal>
3448 or <literal>::1</literal>) is recommended for maximum security.
3452 If no port is specified, port 953 is used. The asterisk
3453 "<literal>*</literal>" cannot be used for <command>ip_port</command>.
3457 The ability to issue commands over the control channel is
3458 restricted by the <command>allow</command> and
3459 <command>keys</command> clauses.
3460 Connections to the control channel are permitted based on the
3461 <command>address_match_list</command>. This is for simple
3462 IP address based filtering only; any <command>key_id</command>
3463 elements of the <command>address_match_list</command>
3468 A <command>unix</command> control channel is a UNIX domain
3469 socket listening at the specified path in the file system.
3470 Access to the socket is specified by the <command>perm</command>,
3471 <command>owner</command> and <command>group</command> clauses.
3472 Note on some platforms (SunOS and Solaris) the permissions
3473 (<command>perm</command>) are applied to the parent directory
3474 as the permissions on the socket itself are ignored.
3478 The primary authorization mechanism of the command
3479 channel is the <command>key_list</command>, which
3480 contains a list of <command>key_id</command>s.
3481 Each <command>key_id</command> in the <command>key_list</command>
3482 is authorized to execute commands over the control channel.
3483 See <xref linkend="rndc"/> in <xref linkend="admin_tools"/>)
3484 for information about configuring keys in <command>rndc</command>.
3488 If no <command>controls</command> statement is present,
3489 <command>named</command> will set up a default
3490 control channel listening on the loopback address 127.0.0.1
3491 and its IPv6 counterpart ::1.
3492 In this case, and also when the <command>controls</command> statement
3493 is present but does not have a <command>keys</command> clause,
3494 <command>named</command> will attempt to load the command channel key
3495 from the file <filename>rndc.key</filename> in
3496 <filename>/etc</filename> (or whatever <varname>sysconfdir</varname>
3497 was specified as when <acronym>BIND</acronym> was built).
3498 To create a <filename>rndc.key</filename> file, run
3499 <userinput>rndc-confgen -a</userinput>.
3503 The <filename>rndc.key</filename> feature was created to
3504 ease the transition of systems from <acronym>BIND</acronym> 8,
3505 which did not have digital signatures on its command channel
3506 messages and thus did not have a <command>keys</command> clause.
3508 It makes it possible to use an existing <acronym>BIND</acronym> 8
3509 configuration file in <acronym>BIND</acronym> 9 unchanged,
3510 and still have <command>rndc</command> work the same way
3511 <command>ndc</command> worked in BIND 8, simply by executing the
3512 command <userinput>rndc-confgen -a</userinput> after BIND 9 is
3517 Since the <filename>rndc.key</filename> feature
3518 is only intended to allow the backward-compatible usage of
3519 <acronym>BIND</acronym> 8 configuration files, this
3521 have a high degree of configurability. You cannot easily change
3522 the key name or the size of the secret, so you should make a
3523 <filename>rndc.conf</filename> with your own key if you
3525 those things. The <filename>rndc.key</filename> file
3527 permissions set such that only the owner of the file (the user that
3528 <command>named</command> is running as) can access it.
3530 desire greater flexibility in allowing other users to access
3531 <command>rndc</command> commands, then you need to create
3533 <filename>rndc.conf</filename> file and make it group
3535 that contains the users who should have access.
3539 To disable the command channel, use an empty
3540 <command>controls</command> statement:
3541 <command>controls { };</command>.
3546 <title><command>include</command> Statement Grammar</title>
3547 <programlisting><command>include</command> <replaceable>filename</replaceable>;</programlisting>
3550 <title><command>include</command> Statement Definition and
3554 The <command>include</command> statement inserts the
3555 specified file at the point where the <command>include</command>
3556 statement is encountered. The <command>include</command>
3557 statement facilitates the administration of configuration
3559 by permitting the reading or writing of some things but not
3560 others. For example, the statement could include private keys
3561 that are readable only by the name server.
3566 <title><command>key</command> Statement Grammar</title>
3568 <programlisting><command>key</command> <replaceable>key_id</replaceable> {
3569 algorithm <replaceable>string</replaceable>;
3570 secret <replaceable>string</replaceable>;
3577 <title><command>key</command> Statement Definition and Usage</title>
3580 The <command>key</command> statement defines a shared
3581 secret key for use with TSIG (see <xref linkend="tsig"/>)
3582 or the command channel
3583 (see <xref linkend="controls_statement_definition_and_usage"/>).
3587 The <command>key</command> statement can occur at the
3589 of the configuration file or inside a <command>view</command>
3590 statement. Keys defined in top-level <command>key</command>
3591 statements can be used in all views. Keys intended for use in
3592 a <command>controls</command> statement
3593 (see <xref linkend="controls_statement_definition_and_usage"/>)
3594 must be defined at the top level.
3598 The <replaceable>key_id</replaceable>, also known as the
3599 key name, is a domain name uniquely identifying the key. It can
3600 be used in a <command>server</command>
3601 statement to cause requests sent to that
3602 server to be signed with this key, or in address match lists to
3603 verify that incoming requests have been signed with a key
3604 matching this name, algorithm, and secret.
3608 The <replaceable>algorithm_id</replaceable> is a string
3609 that specifies a security/authentication algorithm. Named
3610 supports <literal>hmac-md5</literal>,
3611 <literal>hmac-sha1</literal>, <literal>hmac-sha224</literal>,
3612 <literal>hmac-sha256</literal>, <literal>hmac-sha384</literal>
3613 and <literal>hmac-sha512</literal> TSIG authentication.
3614 Truncated hashes are supported by appending the minimum
3615 number of required bits preceded by a dash, e.g.
3616 <literal>hmac-sha1-80</literal>. The
3617 <replaceable>secret_string</replaceable> is the secret
3618 to be used by the algorithm, and is treated as a base-64
3624 <title><command>logging</command> Statement Grammar</title>
3626 <programlisting><command>logging</command> {
3627 [ <command>channel</command> <replaceable>channel_name</replaceable> {
3628 ( <command>file</command> <replaceable>path_name</replaceable>
3629 [ <command>versions</command> ( <replaceable>number</replaceable> | <command>unlimited</command> ) ]
3630 [ <command>size</command> <replaceable>size_spec</replaceable> ]
3631 | <command>syslog</command> <replaceable>syslog_facility</replaceable>
3632 | <command>stderr</command>
3633 | <command>null</command> );
3634 [ <command>severity</command> (<option>critical</option> | <option>error</option> | <option>warning</option> | <option>notice</option> |
3635 <option>info</option> | <option>debug</option> [ <replaceable>level</replaceable> ] | <option>dynamic</option> ); ]
3636 [ <command>print-category</command> <option>yes</option> or <option>no</option>; ]
3637 [ <command>print-severity</command> <option>yes</option> or <option>no</option>; ]
3638 [ <command>print-time</command> <option>yes</option> or <option>no</option>; ]
3640 [ <command>category</command> <replaceable>category_name</replaceable> {
3641 <replaceable>channel_name</replaceable> ; [ <replaceable>channel_name</replaceable> ; ... ]
3650 <title><command>logging</command> Statement Definition and
3654 The <command>logging</command> statement configures a
3656 variety of logging options for the name server. Its <command>channel</command> phrase
3657 associates output methods, format options and severity levels with
3658 a name that can then be used with the <command>category</command> phrase
3659 to select how various classes of messages are logged.
3662 Only one <command>logging</command> statement is used to
3664 as many channels and categories as are wanted. If there is no <command>logging</command> statement,
3665 the logging configuration will be:
3668 <programlisting>logging {
3669 category default { default_syslog; default_debug; };
3670 category unmatched { null; };
3675 In <acronym>BIND</acronym> 9, the logging configuration
3676 is only established when
3677 the entire configuration file has been parsed. In <acronym>BIND</acronym> 8, it was
3678 established as soon as the <command>logging</command>
3680 was parsed. When the server is starting up, all logging messages
3681 regarding syntax errors in the configuration file go to the default
3682 channels, or to standard error if the "<option>-g</option>" option
3687 <title>The <command>channel</command> Phrase</title>
3690 All log output goes to one or more <emphasis>channels</emphasis>;
3691 you can make as many of them as you want.
3695 Every channel definition must include a destination clause that
3696 says whether messages selected for the channel go to a file, to a
3697 particular syslog facility, to the standard error stream, or are
3698 discarded. It can optionally also limit the message severity level
3699 that will be accepted by the channel (the default is
3700 <command>info</command>), and whether to include a
3701 <command>named</command>-generated time stamp, the
3703 and/or severity level (the default is not to include any).
3707 The <command>null</command> destination clause
3708 causes all messages sent to the channel to be discarded;
3709 in that case, other options for the channel are meaningless.
3713 The <command>file</command> destination clause directs
3715 to a disk file. It can include limitations
3716 both on how large the file is allowed to become, and how many
3718 of the file will be saved each time the file is opened.
3722 If you use the <command>versions</command> log file
3724 <command>named</command> will retain that many backup
3725 versions of the file by
3726 renaming them when opening. For example, if you choose to keep
3728 of the file <filename>lamers.log</filename>, then just
3730 <filename>lamers.log.1</filename> is renamed to
3731 <filename>lamers.log.2</filename>, <filename>lamers.log.0</filename> is renamed
3732 to <filename>lamers.log.1</filename>, and <filename>lamers.log</filename> is
3733 renamed to <filename>lamers.log.0</filename>.
3734 You can say <command>versions unlimited</command> to
3736 the number of versions.
3737 If a <command>size</command> option is associated with
3739 then renaming is only done when the file being opened exceeds the
3740 indicated size. No backup versions are kept by default; any
3742 log file is simply appended.
3746 The <command>size</command> option for files is used
3748 growth. If the file ever exceeds the size, then <command>named</command> will
3749 stop writing to the file unless it has a <command>versions</command> option
3750 associated with it. If backup versions are kept, the files are
3752 described above and a new one begun. If there is no
3753 <command>versions</command> option, no more data will
3754 be written to the log
3755 until some out-of-band mechanism removes or truncates the log to
3757 maximum size. The default behavior is not to limit the size of
3763 Example usage of the <command>size</command> and
3764 <command>versions</command> options:
3767 <programlisting>channel an_example_channel {
3768 file "example.log" versions 3 size 20m;
3775 The <command>syslog</command> destination clause
3777 channel to the system log. Its argument is a
3778 syslog facility as described in the <command>syslog</command> man
3779 page. Known facilities are <command>kern</command>, <command>user</command>,
3780 <command>mail</command>, <command>daemon</command>, <command>auth</command>,
3781 <command>syslog</command>, <command>lpr</command>, <command>news</command>,
3782 <command>uucp</command>, <command>cron</command>, <command>authpriv</command>,
3783 <command>ftp</command>, <command>local0</command>, <command>local1</command>,
3784 <command>local2</command>, <command>local3</command>, <command>local4</command>,
3785 <command>local5</command>, <command>local6</command> and
3786 <command>local7</command>, however not all facilities
3788 all operating systems.
3789 How <command>syslog</command> will handle messages
3791 this facility is described in the <command>syslog.conf</command> man
3792 page. If you have a system which uses a very old version of <command>syslog</command> that
3793 only uses two arguments to the <command>openlog()</command> function,
3794 then this clause is silently ignored.
3797 On Windows machines syslog messages are directed to the EventViewer.
3800 The <command>severity</command> clause works like <command>syslog</command>'s
3801 "priorities", except that they can also be used if you are writing
3802 straight to a file rather than using <command>syslog</command>.
3803 Messages which are not at least of the severity level given will
3804 not be selected for the channel; messages of higher severity
3809 If you are using <command>syslog</command>, then the <command>syslog.conf</command> priorities
3810 will also determine what eventually passes through. For example,
3811 defining a channel facility and severity as <command>daemon</command> and <command>debug</command> but
3812 only logging <command>daemon.warning</command> via <command>syslog.conf</command> will
3813 cause messages of severity <command>info</command> and
3814 <command>notice</command> to
3815 be dropped. If the situation were reversed, with <command>named</command> writing
3816 messages of only <command>warning</command> or higher,
3817 then <command>syslogd</command> would
3818 print all messages it received from the channel.
3822 The <command>stderr</command> destination clause
3824 channel to the server's standard error stream. This is intended
3826 use when the server is running as a foreground process, for
3828 when debugging a configuration.
3832 The server can supply extensive debugging information when
3833 it is in debugging mode. If the server's global debug level is
3835 than zero, then debugging mode will be active. The global debug
3836 level is set either by starting the <command>named</command> server
3837 with the <option>-d</option> flag followed by a positive integer,
3838 or by running <command>rndc trace</command>.
3839 The global debug level
3840 can be set to zero, and debugging mode turned off, by running <command>rndc
3841 notrace</command>. All debugging messages in the server have a debug
3842 level, and higher debug levels give more detailed output. Channels
3843 that specify a specific debug severity, for example:
3846 <programlisting>channel specific_debug_level {
3853 will get debugging output of level 3 or less any time the
3854 server is in debugging mode, regardless of the global debugging
3855 level. Channels with <command>dynamic</command>
3857 server's global debug level to determine what messages to print.
3860 If <command>print-time</command> has been turned on,
3862 the date and time will be logged. <command>print-time</command> may
3863 be specified for a <command>syslog</command> channel,
3865 pointless since <command>syslog</command> also logs
3867 time. If <command>print-category</command> is
3869 category of the message will be logged as well. Finally, if <command>print-severity</command> is
3870 on, then the severity level of the message will be logged. The <command>print-</command> options may
3871 be used in any combination, and will always be printed in the
3873 order: time, category, severity. Here is an example where all
3874 three <command>print-</command> options
3879 <computeroutput>28-Feb-2000 15:05:32.863 general: notice: running</computeroutput>
3883 There are four predefined channels that are used for
3884 <command>named</command>'s default logging as follows.
3886 used is described in <xref linkend="the_category_phrase"/>.
3889 <programlisting>channel default_syslog {
3890 // send to syslog's daemon facility
3892 // only send priority info and higher
3895 channel default_debug {
3896 // write to named.run in the working directory
3897 // Note: stderr is used instead of "named.run" if
3898 // the server is started with the '-f' option.
3900 // log at the server's current debug level
3904 channel default_stderr {
3907 // only send priority info and higher
3912 // toss anything sent to this channel
3918 The <command>default_debug</command> channel has the
3920 property that it only produces output when the server's debug
3922 nonzero. It normally writes to a file called <filename>named.run</filename>
3923 in the server's working directory.
3927 For security reasons, when the "<option>-u</option>"
3928 command line option is used, the <filename>named.run</filename> file
3929 is created only after <command>named</command> has
3931 new UID, and any debug output generated while <command>named</command> is
3932 starting up and still running as root is discarded. If you need
3933 to capture this output, you must run the server with the "<option>-g</option>"
3934 option and redirect standard error to a file.
3938 Once a channel is defined, it cannot be redefined. Thus you
3939 cannot alter the built-in channels directly, but you can modify
3940 the default logging by pointing categories at channels you have
3945 <sect3 id="the_category_phrase">
3946 <title>The <command>category</command> Phrase</title>
3949 There are many categories, so you can send the logs you want
3950 to see wherever you want, without seeing logs you don't want. If
3951 you don't specify a list of channels for a category, then log
3953 in that category will be sent to the <command>default</command> category
3954 instead. If you don't specify a default category, the following
3955 "default default" is used:
3958 <programlisting>category default { default_syslog; default_debug; };
3962 As an example, let's say you want to log security events to
3963 a file, but you also want keep the default logging behavior. You'd
3964 specify the following:
3967 <programlisting>channel my_security_channel {
3968 file "my_security_file";
3972 my_security_channel;
3978 To discard all messages in a category, specify the <command>null</command> channel:
3981 <programlisting>category xfer-out { null; };
3982 category notify { null; };
3986 Following are the available categories and brief descriptions
3987 of the types of log information they contain. More
3988 categories may be added in future <acronym>BIND</acronym> releases.
3990 <informaltable colsep="0" rowsep="0">
3991 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
3992 <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
3993 <colspec colname="2" colnum="2" colsep="0" colwidth="3.350in"/>
3997 <para><command>default</command></para>
4001 The default category defines the logging
4002 options for those categories where no specific
4003 configuration has been
4010 <para><command>general</command></para>
4014 The catch-all. Many things still aren't
4015 classified into categories, and they all end up here.
4021 <para><command>database</command></para>
4025 Messages relating to the databases used
4026 internally by the name server to store zone and cache
4033 <para><command>security</command></para>
4037 Approval and denial of requests.
4043 <para><command>config</command></para>
4047 Configuration file parsing and processing.
4053 <para><command>resolver</command></para>
4057 DNS resolution, such as the recursive
4058 lookups performed on behalf of clients by a caching name
4065 <para><command>xfer-in</command></para>
4069 Zone transfers the server is receiving.
4075 <para><command>xfer-out</command></para>
4079 Zone transfers the server is sending.
4085 <para><command>notify</command></para>
4089 The NOTIFY protocol.
4095 <para><command>client</command></para>
4099 Processing of client requests.
4105 <para><command>unmatched</command></para>
4109 Messages that <command>named</command> was unable to determine the
4110 class of or for which there was no matching <command>view</command>.
4111 A one line summary is also logged to the <command>client</command> category.
4112 This category is best sent to a file or stderr, by
4113 default it is sent to
4114 the <command>null</command> channel.
4120 <para><command>network</command></para>
4130 <para><command>update</command></para>
4140 <para><command>update-security</command></para>
4144 Approval and denial of update requests.
4150 <para><command>queries</command></para>
4154 Specify where queries should be logged to.
4157 At startup, specifying the category <command>queries</command> will also
4158 enable query logging unless <command>querylog</command> option has been
4163 The query log entry reports the client's IP
4164 address and port number, and the query name,
4165 class and type. Next it reports whether the
4166 Recursion Desired flag was set (+ if set, -
4167 if not set), if the query was signed (S),
4168 EDNS was in use (E), if TCP was used (T), if
4169 DO (DNSSEC Ok) was set (D), or if CD (Checking
4170 Disabled) was set (C). After this the
4171 destination address the query was sent to is
4176 <computeroutput>client 127.0.0.1#62536: query: www.example.com IN AAAA +SE</computeroutput>
4179 <computeroutput>client ::1#62537: query: www.example.net IN AAAA -SE</computeroutput>
4185 <para><command>query-errors</command></para>
4189 Information about queries that resulted in some
4196 <para><command>dispatch</command></para>
4200 Dispatching of incoming packets to the
4201 server modules where they are to be processed.
4207 <para><command>dnssec</command></para>
4211 DNSSEC and TSIG protocol processing.
4217 <para><command>lame-servers</command></para>
4221 Lame servers. These are misconfigurations
4222 in remote servers, discovered by BIND 9 when trying to
4223 query those servers during resolution.
4229 <para><command>delegation-only</command></para>
4233 Delegation only. Logs queries that have been
4234 forced to NXDOMAIN as the result of a
4235 delegation-only zone or a
4236 <command>delegation-only</command> in a hint
4237 or stub zone declaration.
4243 <para><command>edns-disabled</command></para>
4247 Log queries that have been forced to use plain
4248 DNS due to timeouts. This is often due to
4249 the remote servers not being RFC 1034 compliant
4250 (not always returning FORMERR or similar to
4251 EDNS queries and other extensions to the DNS
4252 when they are not understood). In other words, this is
4253 targeted at servers that fail to respond to
4254 DNS queries that they don't understand.
4257 Note: the log message can also be due to
4258 packet loss. Before reporting servers for
4259 non-RFC 1034 compliance they should be re-tested
4260 to determine the nature of the non-compliance.
4261 This testing should prevent or reduce the
4262 number of false-positive reports.
4265 Note: eventually <command>named</command> will have to stop
4266 treating such timeouts as due to RFC 1034 non
4267 compliance and start treating it as plain
4268 packet loss. Falsely classifying packet
4269 loss as due to RFC 1034 non compliance impacts
4270 on DNSSEC validation which requires EDNS for
4271 the DNSSEC records to be returned.
4277 <para><command>RPZ</command></para>
4281 Information about errors in response policy zone files,
4282 rewritten responses, and at the highest
4283 <command>debug</command> levels, mere rewriting
4293 <title>The <command>query-errors</command> Category</title>
4295 The <command>query-errors</command> category is
4296 specifically intended for debugging purposes: To identify
4297 why and how specific queries result in responses which
4299 Messages of this category are therefore only logged
4300 with <command>debug</command> levels.
4304 At the debug levels of 1 or higher, each response with the
4305 rcode of SERVFAIL is logged as follows:
4308 <computeroutput>client 127.0.0.1#61502: query failed (SERVFAIL) for www.example.com/IN/AAAA at query.c:3880</computeroutput>
4311 This means an error resulting in SERVFAIL was
4312 detected at line 3880 of source file
4313 <filename>query.c</filename>.
4314 Log messages of this level will particularly
4315 help identify the cause of SERVFAIL for an
4316 authoritative server.
4319 At the debug levels of 2 or higher, detailed context
4320 information of recursive resolutions that resulted in
4322 The log message will look like as follows:
4325 <!-- NOTE: newlines and some spaces added so this would fit on page -->
4327 fetch completed at resolver.c:2970 for www.example.com/A
4328 in 30.000183: timed out/success [domain:example.com,
4329 referral:2,restart:7,qrysent:8,timeout:5,lame:0,neterr:0,
4330 badresp:1,adberr:0,findfail:0,valfail:0]
4334 The first part before the colon shows that a recursive
4335 resolution for AAAA records of www.example.com completed
4336 in 30.000183 seconds and the final result that led to the
4337 SERVFAIL was determined at line 2970 of source file
4338 <filename>resolver.c</filename>.
4341 The following part shows the detected final result and the
4342 latest result of DNSSEC validation.
4343 The latter is always success when no validation attempt
4345 In this example, this query resulted in SERVFAIL probably
4346 because all name servers are down or unreachable, leading
4347 to a timeout in 30 seconds.
4348 DNSSEC validation was probably not attempted.
4351 The last part enclosed in square brackets shows statistics
4352 information collected for this particular resolution
4354 The <varname>domain</varname> field shows the deepest zone
4355 that the resolver reached;
4356 it is the zone where the error was finally detected.
4357 The meaning of the other fields is summarized in the
4361 <informaltable colsep="0" rowsep="0">
4362 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
4363 <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
4364 <colspec colname="2" colnum="2" colsep="0" colwidth="3.350in"/>
4368 <para><varname>referral</varname></para>
4372 The number of referrals the resolver received
4373 throughout the resolution process.
4374 In the above example this is 2, which are most
4375 likely com and example.com.
4381 <para><varname>restart</varname></para>
4385 The number of cycles that the resolver tried
4386 remote servers at the <varname>domain</varname>
4388 In each cycle the resolver sends one query
4389 (possibly resending it, depending on the response)
4390 to each known name server of
4391 the <varname>domain</varname> zone.
4397 <para><varname>qrysent</varname></para>
4401 The number of queries the resolver sent at the
4402 <varname>domain</varname> zone.
4408 <para><varname>timeout</varname></para>
4412 The number of timeouts since the resolver
4413 received the last response.
4419 <para><varname>lame</varname></para>
4423 The number of lame servers the resolver detected
4424 at the <varname>domain</varname> zone.
4425 A server is detected to be lame either by an
4426 invalid response or as a result of lookup in
4427 BIND9's address database (ADB), where lame
4434 <para><varname>neterr</varname></para>
4438 The number of erroneous results that the
4439 resolver encountered in sending queries
4440 at the <varname>domain</varname> zone.
4441 One common case is the remote server is
4442 unreachable and the resolver receives an ICMP
4443 unreachable error message.
4449 <para><varname>badresp</varname></para>
4453 The number of unexpected responses (other than
4454 <varname>lame</varname>) to queries sent by the
4455 resolver at the <varname>domain</varname> zone.
4461 <para><varname>adberr</varname></para>
4465 Failures in finding remote server addresses
4466 of the <varname>domain</varname> zone in the ADB.
4467 One common case of this is that the remote
4468 server's name does not have any address records.
4474 <para><varname>findfail</varname></para>
4478 Failures of resolving remote server addresses.
4479 This is a total number of failures throughout
4480 the resolution process.
4486 <para><varname>valfail</varname></para>
4490 Failures of DNSSEC validation.
4491 Validation failures are counted throughout
4492 the resolution process (not limited to
4493 the <varname>domain</varname> zone), but should
4494 only happen in <varname>domain</varname>.
4502 At the debug levels of 3 or higher, the same messages
4503 as those at the debug 1 level are logged for other errors
4505 Note that negative responses such as NXDOMAIN are not
4506 regarded as errors here.
4509 At the debug levels of 4 or higher, the same messages
4510 as those at the debug 2 level are logged for other errors
4512 Unlike the above case of level 3, messages are logged for
4514 This is because any unexpected results can be difficult to
4515 debug in the recursion case.
4521 <title><command>lwres</command> Statement Grammar</title>
4524 This is the grammar of the <command>lwres</command>
4525 statement in the <filename>named.conf</filename> file:
4528 <programlisting><command>lwres</command> {
4529 <optional> listen-on { <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ;
4530 <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
4531 <optional> view <replaceable>view_name</replaceable>; </optional>
4532 <optional> search { <replaceable>domain_name</replaceable> ; <optional> <replaceable>domain_name</replaceable> ; ... </optional> }; </optional>
4533 <optional> ndots <replaceable>number</replaceable>; </optional>
4539 <title><command>lwres</command> Statement Definition and Usage</title>
4542 The <command>lwres</command> statement configures the
4544 server to also act as a lightweight resolver server. (See
4545 <xref linkend="lwresd"/>.) There may be multiple
4546 <command>lwres</command> statements configuring
4547 lightweight resolver servers with different properties.
4551 The <command>listen-on</command> statement specifies a
4553 addresses (and ports) that this instance of a lightweight resolver
4555 should accept requests on. If no port is specified, port 921 is
4557 If this statement is omitted, requests will be accepted on
4563 The <command>view</command> statement binds this
4565 lightweight resolver daemon to a view in the DNS namespace, so that
4567 response will be constructed in the same manner as a normal DNS
4569 matching this view. If this statement is omitted, the default view
4571 used, and if there is no default view, an error is triggered.
4575 The <command>search</command> statement is equivalent to
4577 <command>search</command> statement in
4578 <filename>/etc/resolv.conf</filename>. It provides a
4580 which are appended to relative names in queries.
4584 The <command>ndots</command> statement is equivalent to
4586 <command>ndots</command> statement in
4587 <filename>/etc/resolv.conf</filename>. It indicates the
4589 number of dots in a relative domain name that should result in an
4590 exact match lookup before search path elements are appended.
4594 <title><command>masters</command> Statement Grammar</title>
4597 <command>masters</command> <replaceable>name</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> |
4598 <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> };
4604 <title><command>masters</command> Statement Definition and
4606 <para><command>masters</command>
4607 lists allow for a common set of masters to be easily used by
4608 multiple stub and slave zones.
4613 <title><command>options</command> Statement Grammar</title>
4616 This is the grammar of the <command>options</command>
4617 statement in the <filename>named.conf</filename> file:
4620 <programlisting><command>options</command> {
4621 <optional> attach-cache <replaceable>cache_name</replaceable>; </optional>
4622 <optional> version <replaceable>version_string</replaceable>; </optional>
4623 <optional> hostname <replaceable>hostname_string</replaceable>; </optional>
4624 <optional> server-id <replaceable>server_id_string</replaceable>; </optional>
4625 <optional> directory <replaceable>path_name</replaceable>; </optional>
4626 <optional> key-directory <replaceable>path_name</replaceable>; </optional>
4627 <optional> managed-keys-directory <replaceable>path_name</replaceable>; </optional>
4628 <optional> named-xfer <replaceable>path_name</replaceable>; </optional>
4629 <optional> tkey-gssapi-keytab <replaceable>path_name</replaceable>; </optional>
4630 <optional> tkey-gssapi-credential <replaceable>principal</replaceable>; </optional>
4631 <optional> tkey-domain <replaceable>domainname</replaceable>; </optional>
4632 <optional> tkey-dhkey <replaceable>key_name</replaceable> <replaceable>key_tag</replaceable>; </optional>
4633 <optional> cache-file <replaceable>path_name</replaceable>; </optional>
4634 <optional> dump-file <replaceable>path_name</replaceable>; </optional>
4635 <optional> bindkeys-file <replaceable>path_name</replaceable>; </optional>
4636 <optional> secroots-file <replaceable>path_name</replaceable>; </optional>
4637 <optional> session-keyfile <replaceable>path_name</replaceable>; </optional>
4638 <optional> session-keyname <replaceable>key_name</replaceable>; </optional>
4639 <optional> session-keyalg <replaceable>algorithm_id</replaceable>; </optional>
4640 <optional> memstatistics <replaceable>yes_or_no</replaceable>; </optional>
4641 <optional> memstatistics-file <replaceable>path_name</replaceable>; </optional>
4642 <optional> pid-file <replaceable>path_name</replaceable>; </optional>
4643 <optional> recursing-file <replaceable>path_name</replaceable>; </optional>
4644 <optional> statistics-file <replaceable>path_name</replaceable>; </optional>
4645 <optional> zone-statistics <replaceable>yes_or_no</replaceable>; </optional>
4646 <optional> auth-nxdomain <replaceable>yes_or_no</replaceable>; </optional>
4647 <optional> deallocate-on-exit <replaceable>yes_or_no</replaceable>; </optional>
4648 <optional> dialup <replaceable>dialup_option</replaceable>; </optional>
4649 <optional> fake-iquery <replaceable>yes_or_no</replaceable>; </optional>
4650 <optional> fetch-glue <replaceable>yes_or_no</replaceable>; </optional>
4651 <optional> flush-zones-on-shutdown <replaceable>yes_or_no</replaceable>; </optional>
4652 <optional> has-old-clients <replaceable>yes_or_no</replaceable>; </optional>
4653 <optional> host-statistics <replaceable>yes_or_no</replaceable>; </optional>
4654 <optional> host-statistics-max <replaceable>number</replaceable>; </optional>
4655 <optional> minimal-responses <replaceable>yes_or_no</replaceable>; </optional>
4656 <optional> multiple-cnames <replaceable>yes_or_no</replaceable>; </optional>
4657 <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable> | <replaceable>master-only</replaceable>; </optional>
4658 <optional> recursion <replaceable>yes_or_no</replaceable>; </optional>
4659 <optional> request-nsid <replaceable>yes_or_no</replaceable>; </optional>
4660 <optional> rfc2308-type1 <replaceable>yes_or_no</replaceable>; </optional>
4661 <optional> use-id-pool <replaceable>yes_or_no</replaceable>; </optional>
4662 <optional> maintain-ixfr-base <replaceable>yes_or_no</replaceable>; </optional>
4663 <optional> ixfr-from-differences (<replaceable>yes_or_no</replaceable> | <constant>master</constant> | <constant>slave</constant>); </optional>
4664 <optional> dnssec-enable <replaceable>yes_or_no</replaceable>; </optional>
4665 <optional> dnssec-validation (<replaceable>yes_or_no</replaceable> | <constant>auto</constant>); </optional>
4666 <optional> dnssec-lookaside ( <replaceable>auto</replaceable> |
4667 <replaceable>no</replaceable> |
4668 <replaceable>domain</replaceable> trust-anchor <replaceable>domain</replaceable> ); </optional>
4669 <optional> dnssec-must-be-secure <replaceable>domain yes_or_no</replaceable>; </optional>
4670 <optional> dnssec-accept-expired <replaceable>yes_or_no</replaceable>; </optional>
4671 <optional> forward ( <replaceable>only</replaceable> | <replaceable>first</replaceable> ); </optional>
4672 <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
4673 <optional> dual-stack-servers <optional>port <replaceable>ip_port</replaceable></optional> {
4674 ( <replaceable>domain_name</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> |
4675 <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ) ;
4677 <optional> check-names ( <replaceable>master</replaceable> | <replaceable>slave</replaceable> | <replaceable>response</replaceable> )
4678 ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional>
4679 <optional> check-dup-records ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional>
4680 <optional> check-mx ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional>
4681 <optional> check-wildcard <replaceable>yes_or_no</replaceable>; </optional>
4682 <optional> check-integrity <replaceable>yes_or_no</replaceable>; </optional>
4683 <optional> check-mx-cname ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional>
4684 <optional> check-srv-cname ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional>
4685 <optional> check-sibling <replaceable>yes_or_no</replaceable>; </optional>
4686 <optional> check-spf ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional>
4687 <optional> allow-new-zones { <replaceable>yes_or_no</replaceable> }; </optional>
4688 <optional> allow-notify { <replaceable>address_match_list</replaceable> }; </optional>
4689 <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional>
4690 <optional> allow-query-on { <replaceable>address_match_list</replaceable> }; </optional>
4691 <optional> allow-query-cache { <replaceable>address_match_list</replaceable> }; </optional>
4692 <optional> allow-query-cache-on { <replaceable>address_match_list</replaceable> }; </optional>
4693 <optional> allow-transfer { <replaceable>address_match_list</replaceable> }; </optional>
4694 <optional> allow-recursion { <replaceable>address_match_list</replaceable> }; </optional>
4695 <optional> allow-recursion-on { <replaceable>address_match_list</replaceable> }; </optional>
4696 <optional> allow-update { <replaceable>address_match_list</replaceable> }; </optional>
4697 <optional> allow-update-forwarding { <replaceable>address_match_list</replaceable> }; </optional>
4698 <optional> update-check-ksk <replaceable>yes_or_no</replaceable>; </optional>
4699 <optional> dnssec-dnskey-kskonly <replaceable>yes_or_no</replaceable>; </optional>
4700 <optional> dnssec-secure-to-insecure <replaceable>yes_or_no</replaceable> ;</optional>
4701 <optional> try-tcp-refresh <replaceable>yes_or_no</replaceable>; </optional>
4702 <optional> allow-v6-synthesis { <replaceable>address_match_list</replaceable> }; </optional>
4703 <optional> blackhole { <replaceable>address_match_list</replaceable> }; </optional>
4704 <optional> use-v4-udp-ports { <replaceable>port_list</replaceable> }; </optional>
4705 <optional> avoid-v4-udp-ports { <replaceable>port_list</replaceable> }; </optional>
4706 <optional> use-v6-udp-ports { <replaceable>port_list</replaceable> }; </optional>
4707 <optional> avoid-v6-udp-ports { <replaceable>port_list</replaceable> }; </optional>
4708 <optional> listen-on <optional> port <replaceable>ip_port</replaceable> </optional> { <replaceable>address_match_list</replaceable> }; </optional>
4709 <optional> listen-on-v6 <optional> port <replaceable>ip_port</replaceable> </optional> { <replaceable>address_match_list</replaceable> }; </optional>
4710 <optional> query-source ( ( <replaceable>ip4_addr</replaceable> | <replaceable>*</replaceable> )
4711 <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional> |
4712 <optional> address ( <replaceable>ip4_addr</replaceable> | <replaceable>*</replaceable> ) </optional>
4713 <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional> ) ; </optional>
4714 <optional> query-source-v6 ( ( <replaceable>ip6_addr</replaceable> | <replaceable>*</replaceable> )
4715 <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional> |
4716 <optional> address ( <replaceable>ip6_addr</replaceable> | <replaceable>*</replaceable> ) </optional>
4717 <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional> ) ; </optional>
4718 <optional> use-queryport-pool <replaceable>yes_or_no</replaceable>; </optional>
4719 <optional> queryport-pool-ports <replaceable>number</replaceable>; </optional>
4720 <optional> queryport-pool-updateinterval <replaceable>number</replaceable>; </optional>
4721 <optional> max-transfer-time-in <replaceable>number</replaceable>; </optional>
4722 <optional> max-transfer-time-out <replaceable>number</replaceable>; </optional>
4723 <optional> max-transfer-idle-in <replaceable>number</replaceable>; </optional>
4724 <optional> max-transfer-idle-out <replaceable>number</replaceable>; </optional>
4725 <optional> tcp-clients <replaceable>number</replaceable>; </optional>
4726 <optional> reserved-sockets <replaceable>number</replaceable>; </optional>
4727 <optional> recursive-clients <replaceable>number</replaceable>; </optional>
4728 <optional> serial-query-rate <replaceable>number</replaceable>; </optional>
4729 <optional> serial-queries <replaceable>number</replaceable>; </optional>
4730 <optional> tcp-listen-queue <replaceable>number</replaceable>; </optional>
4731 <optional> transfer-format <replaceable>( one-answer | many-answers )</replaceable>; </optional>
4732 <optional> transfers-in <replaceable>number</replaceable>; </optional>
4733 <optional> transfers-out <replaceable>number</replaceable>; </optional>
4734 <optional> transfers-per-ns <replaceable>number</replaceable>; </optional>
4735 <optional> transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
4736 <optional> transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
4737 <optional> alt-transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
4738 <optional> alt-transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>)
4739 <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
4740 <optional> use-alt-transfer-source <replaceable>yes_or_no</replaceable>; </optional>
4741 <optional> notify-delay <replaceable>seconds</replaceable> ; </optional>
4742 <optional> notify-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
4743 <optional> notify-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
4744 <optional> notify-to-soa <replaceable>yes_or_no</replaceable> ; </optional>
4745 <optional> also-notify { <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ;
4746 <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
4747 <optional> max-ixfr-log-size <replaceable>number</replaceable>; </optional>
4748 <optional> max-journal-size <replaceable>size_spec</replaceable>; </optional>
4749 <optional> coresize <replaceable>size_spec</replaceable> ; </optional>
4750 <optional> datasize <replaceable>size_spec</replaceable> ; </optional>
4751 <optional> files <replaceable>size_spec</replaceable> ; </optional>
4752 <optional> stacksize <replaceable>size_spec</replaceable> ; </optional>
4753 <optional> cleaning-interval <replaceable>number</replaceable>; </optional>
4754 <optional> heartbeat-interval <replaceable>number</replaceable>; </optional>
4755 <optional> interface-interval <replaceable>number</replaceable>; </optional>
4756 <optional> statistics-interval <replaceable>number</replaceable>; </optional>
4757 <optional> topology { <replaceable>address_match_list</replaceable> }</optional>;
4758 <optional> sortlist { <replaceable>address_match_list</replaceable> }</optional>;
4759 <optional> rrset-order { <replaceable>order_spec</replaceable> ; <optional> <replaceable>order_spec</replaceable> ; ... </optional> </optional> };
4760 <optional> lame-ttl <replaceable>number</replaceable>; </optional>
4761 <optional> max-ncache-ttl <replaceable>number</replaceable>; </optional>
4762 <optional> max-cache-ttl <replaceable>number</replaceable>; </optional>
4763 <optional> sig-validity-interval <replaceable>number</replaceable> <optional><replaceable>number</replaceable></optional> ; </optional>
4764 <optional> sig-signing-nodes <replaceable>number</replaceable> ; </optional>
4765 <optional> sig-signing-signatures <replaceable>number</replaceable> ; </optional>
4766 <optional> sig-signing-type <replaceable>number</replaceable> ; </optional>
4767 <optional> min-roots <replaceable>number</replaceable>; </optional>
4768 <optional> use-ixfr <replaceable>yes_or_no</replaceable> ; </optional>
4769 <optional> provide-ixfr <replaceable>yes_or_no</replaceable>; </optional>
4770 <optional> request-ixfr <replaceable>yes_or_no</replaceable>; </optional>
4771 <optional> treat-cr-as-space <replaceable>yes_or_no</replaceable> ; </optional>
4772 <optional> min-refresh-time <replaceable>number</replaceable> ; </optional>
4773 <optional> max-refresh-time <replaceable>number</replaceable> ; </optional>
4774 <optional> min-retry-time <replaceable>number</replaceable> ; </optional>
4775 <optional> max-retry-time <replaceable>number</replaceable> ; </optional>
4776 <optional> port <replaceable>ip_port</replaceable>; </optional>
4777 <optional> additional-from-auth <replaceable>yes_or_no</replaceable> ; </optional>
4778 <optional> additional-from-cache <replaceable>yes_or_no</replaceable> ; </optional>
4779 <optional> random-device <replaceable>path_name</replaceable> ; </optional>
4780 <optional> max-cache-size <replaceable>size_spec</replaceable> ; </optional>
4781 <optional> match-mapped-addresses <replaceable>yes_or_no</replaceable>; </optional>
4782 <optional> filter-aaaa-on-v4 ( <replaceable>yes_or_no</replaceable> | <replaceable>break-dnssec</replaceable> ); </optional>
4783 <optional> filter-aaaa { <replaceable>address_match_list</replaceable> }; </optional>
4784 <optional> dns64 <replaceable>IPv6-prefix</replaceable> {
4785 <optional> clients { <replaceable>address_match_list</replaceable> }; </optional>
4786 <optional> mapped { <replaceable>address_match_list</replaceable> }; </optional>
4787 <optional> exclude { <replaceable>address_match_list</replaceable> }; </optional>
4788 <optional> suffix IPv6-address; </optional>
4789 <optional> recursive-only <replaceable>yes_or_no</replaceable>; </optional>
4790 <optional> break-dnssec <replaceable>yes_or_no</replaceable>; </optional>
4792 <optional> dns64-server <replaceable>name</replaceable> </optional>
4793 <optional> dns64-contact <replaceable>name</replaceable> </optional>
4794 <optional> preferred-glue ( <replaceable>A</replaceable> | <replaceable>AAAA</replaceable> | <replaceable>NONE</replaceable> ); </optional>
4795 <optional> edns-udp-size <replaceable>number</replaceable>; </optional>
4796 <optional> max-udp-size <replaceable>number</replaceable>; </optional>
4797 <optional> root-delegation-only <optional> exclude { <replaceable>namelist</replaceable> } </optional> ; </optional>
4798 <optional> querylog <replaceable>yes_or_no</replaceable> ; </optional>
4799 <optional> disable-algorithms <replaceable>domain</replaceable> { <replaceable>algorithm</replaceable>;
4800 <optional> <replaceable>algorithm</replaceable>; </optional> }; </optional>
4801 <optional> acache-enable <replaceable>yes_or_no</replaceable> ; </optional>
4802 <optional> acache-cleaning-interval <replaceable>number</replaceable>; </optional>
4803 <optional> max-acache-size <replaceable>size_spec</replaceable> ; </optional>
4804 <optional> clients-per-query <replaceable>number</replaceable> ; </optional>
4805 <optional> max-clients-per-query <replaceable>number</replaceable> ; </optional>
4806 <optional> masterfile-format (<constant>text</constant>|<constant>raw</constant>) ; </optional>
4807 <optional> empty-server <replaceable>name</replaceable> ; </optional>
4808 <optional> empty-contact <replaceable>name</replaceable> ; </optional>
4809 <optional> empty-zones-enable <replaceable>yes_or_no</replaceable> ; </optional>
4810 <optional> disable-empty-zone <replaceable>zone_name</replaceable> ; </optional>
4811 <optional> zero-no-soa-ttl <replaceable>yes_or_no</replaceable> ; </optional>
4812 <optional> zero-no-soa-ttl-cache <replaceable>yes_or_no</replaceable> ; </optional>
4813 <optional> resolver-query-timeout <replaceable>number</replaceable> ; </optional>
4814 <optional> deny-answer-addresses { <replaceable>address_match_list</replaceable> } <optional> except-from { <replaceable>namelist</replaceable> } </optional>;</optional>
4815 <optional> deny-answer-aliases { <replaceable>namelist</replaceable> } <optional> except-from { <replaceable>namelist</replaceable> } </optional>;</optional>
4816 <optional> response-policy { <replaceable>zone_name</replaceable>
4817 <optional> policy given | disabled | passthru | nxdomain | nodata | cname <replaceable>domain</replaceable> </optional>
4818 <optional> recursive-only <replaceable>yes_or_no</replaceable> </optional> <optional> max-policy-ttl <replaceable>number</replaceable> </optional> ;
4819 } <optional> recursive-only <replaceable>yes_or_no</replaceable> </optional> <optional> max-policy-ttl <replaceable>number</replaceable> </optional>
4820 <optional> break-dnssec <replaceable>yes_or_no</replaceable> </optional> <optional> min-ns-dots <replaceable>number</replaceable> </optional> ; </optional>
4826 <sect2 id="options">
4827 <title><command>options</command> Statement Definition and
4831 The <command>options</command> statement sets up global
4833 to be used by <acronym>BIND</acronym>. This statement
4835 once in a configuration file. If there is no <command>options</command>
4836 statement, an options block with each option set to its default will
4843 <term><command>attach-cache</command></term>
4846 Allows multiple views to share a single cache
4848 Each view has its own cache database by default, but
4849 if multiple views have the same operational policy
4850 for name resolution and caching, those views can
4851 share a single cache to save memory and possibly
4852 improve resolution efficiency by using this option.
4856 The <command>attach-cache</command> option
4857 may also be specified in <command>view</command>
4858 statements, in which case it overrides the
4859 global <command>attach-cache</command> option.
4863 The <replaceable>cache_name</replaceable> specifies
4864 the cache to be shared.
4865 When the <command>named</command> server configures
4866 views which are supposed to share a cache, it
4867 creates a cache with the specified name for the
4868 first view of these sharing views.
4869 The rest of the views will simply refer to the
4870 already created cache.
4874 One common configuration to share a cache would be to
4875 allow all views to share a single cache.
4876 This can be done by specifying
4877 the <command>attach-cache</command> as a global
4878 option with an arbitrary name.
4882 Another possible operation is to allow a subset of
4883 all views to share a cache while the others to
4884 retain their own caches.
4885 For example, if there are three views A, B, and C,
4886 and only A and B should share a cache, specify the
4887 <command>attach-cache</command> option as a view A (or
4888 B)'s option, referring to the other view name:
4893 // this view has its own cache
4897 // this view refers to A's cache
4901 // this view has its own cache
4907 Views that share a cache must have the same policy
4908 on configurable parameters that may affect caching.
4909 The current implementation requires the following
4910 configurable options be consistent among these
4912 <command>check-names</command>,
4913 <command>cleaning-interval</command>,
4914 <command>dnssec-accept-expired</command>,
4915 <command>dnssec-validation</command>,
4916 <command>max-cache-ttl</command>,
4917 <command>max-ncache-ttl</command>,
4918 <command>max-cache-size</command>, and
4919 <command>zero-no-soa-ttl</command>.
4923 Note that there may be other parameters that may
4924 cause confusion if they are inconsistent for
4925 different views that share a single cache.
4926 For example, if these views define different sets of
4927 forwarders that can return different answers for the
4928 same question, sharing the answer does not make
4929 sense or could even be harmful.
4930 It is administrator's responsibility to ensure
4931 configuration differences in different views do
4932 not cause disruption with a shared cache.
4939 <term><command>directory</command></term>
4942 The working directory of the server.
4943 Any non-absolute pathnames in the configuration file will be
4945 as relative to this directory. The default location for most
4947 output files (e.g. <filename>named.run</filename>)
4949 If a directory is not specified, the working directory
4950 defaults to `<filename>.</filename>', the directory from
4952 was started. The directory specified should be an absolute
4959 <term><command>key-directory</command></term>
4962 When performing dynamic update of secure zones, the
4963 directory where the public and private DNSSEC key files
4964 should be found, if different than the current working
4965 directory. (Note that this option has no effect on the
4966 paths for files containing non-DNSSEC keys such as
4967 <filename>bind.keys</filename>,
4968 <filename>rndc.key</filename> or
4969 <filename>session.key</filename>.)
4975 <term><command>managed-keys-directory</command></term>
4978 Specifies the directory in which to store the files that
4979 track managed DNSSEC keys. By default, this is the working
4983 If <command>named</command> is not configured to use views,
4984 then managed keys for the server will be tracked in a single
4985 file called <filename>managed-keys.bind</filename>.
4986 Otherwise, managed keys will be tracked in separate files,
4987 one file per view; each file name will be the SHA256 hash
4988 of the view name, followed by the extension
4989 <filename>.mkeys</filename>.
4995 <term><command>named-xfer</command></term>
4998 <emphasis>This option is obsolete.</emphasis> It
4999 was used in <acronym>BIND</acronym> 8 to specify
5000 the pathname to the <command>named-xfer</command>
5001 program. In <acronym>BIND</acronym> 9, no separate
5002 <command>named-xfer</command> program is needed;
5003 its functionality is built into the name server.
5009 <term><command>tkey-gssapi-keytab</command></term>
5012 The KRB5 keytab file to use for GSS-TSIG updates. If
5013 this option is set and tkey-gssapi-credential is not
5014 set, then updates will be allowed with any key
5015 matching a principal in the specified keytab.
5021 <term><command>tkey-gssapi-credential</command></term>
5024 The security credential with which the server should
5025 authenticate keys requested by the GSS-TSIG protocol.
5026 Currently only Kerberos 5 authentication is available
5027 and the credential is a Kerberos principal which the
5028 server can acquire through the default system key
5029 file, normally <filename>/etc/krb5.keytab</filename>.
5030 The location keytab file can be overridden using the
5031 tkey-gssapi-keytab option. Normally this principal is
5032 of the form "<userinput>DNS/</userinput><varname>server.domain</varname>".
5033 To use GSS-TSIG, <command>tkey-domain</command> must
5034 also be set if a specific keytab is not set with
5041 <term><command>tkey-domain</command></term>
5044 The domain appended to the names of all shared keys
5045 generated with <command>TKEY</command>. When a
5046 client requests a <command>TKEY</command> exchange,
5047 it may or may not specify the desired name for the
5048 key. If present, the name of the shared key will
5049 be <varname>client specified part</varname> +
5050 <varname>tkey-domain</varname>. Otherwise, the
5051 name of the shared key will be <varname>random hex
5052 digits</varname> + <varname>tkey-domain</varname>.
5053 In most cases, the <command>domainname</command>
5054 should be the server's domain name, or an otherwise
5055 non-existent subdomain like
5056 "_tkey.<varname>domainname</varname>". If you are
5057 using GSS-TSIG, this variable must be defined, unless
5058 you specify a specific keytab using tkey-gssapi-keytab.
5064 <term><command>tkey-dhkey</command></term>
5067 The Diffie-Hellman key used by the server
5068 to generate shared keys with clients using the Diffie-Hellman
5070 of <command>TKEY</command>. The server must be
5072 public and private keys from files in the working directory.
5074 most cases, the keyname should be the server's host name.
5080 <term><command>cache-file</command></term>
5083 This is for testing only. Do not use.
5089 <term><command>dump-file</command></term>
5092 The pathname of the file the server dumps
5093 the database to when instructed to do so with
5094 <command>rndc dumpdb</command>.
5095 If not specified, the default is <filename>named_dump.db</filename>.
5101 <term><command>memstatistics-file</command></term>
5104 The pathname of the file the server writes memory
5105 usage statistics to on exit. If not specified,
5106 the default is <filename>named.memstats</filename>.
5112 <term><command>pid-file</command></term>
5115 The pathname of the file the server writes its process ID
5116 in. If not specified, the default is
5117 <filename>/var/run/named/named.pid</filename>.
5118 The PID file is used by programs that want to send signals to
5120 name server. Specifying <command>pid-file none</command> disables the
5121 use of a PID file — no file will be written and any
5122 existing one will be removed. Note that <command>none</command>
5123 is a keyword, not a filename, and therefore is not enclosed
5131 <term><command>recursing-file</command></term>
5134 The pathname of the file the server dumps
5135 the queries that are currently recursing when instructed
5136 to do so with <command>rndc recursing</command>.
5137 If not specified, the default is <filename>named.recursing</filename>.
5143 <term><command>statistics-file</command></term>
5146 The pathname of the file the server appends statistics
5147 to when instructed to do so using <command>rndc stats</command>.
5148 If not specified, the default is <filename>named.stats</filename> in the
5149 server's current directory. The format of the file is
5151 in <xref linkend="statsfile"/>.
5157 <term><command>bindkeys-file</command></term>
5160 The pathname of a file to override the built-in trusted
5161 keys provided by <command>named</command>.
5162 See the discussion of <command>dnssec-lookaside</command>
5163 and <command>dnssec-validation</command> for details.
5164 If not specified, the default is
5165 <filename>/etc/bind.keys</filename>.
5171 <term><command>secroots-file</command></term>
5174 The pathname of the file the server dumps
5175 security roots to when instructed to do so with
5176 <command>rndc secroots</command>.
5177 If not specified, the default is
5178 <filename>named.secroots</filename>.
5184 <term><command>session-keyfile</command></term>
5187 The pathname of the file into which to write a TSIG
5188 session key generated by <command>named</command> for use by
5189 <command>nsupdate -l</command>. If not specified, the
5190 default is <filename>/var/run/named/session.key</filename>.
5191 (See <xref linkend="dynamic_update_policies"/>, and in
5192 particular the discussion of the
5193 <command>update-policy</command> statement's
5194 <userinput>local</userinput> option for more
5195 information about this feature.)
5201 <term><command>session-keyname</command></term>
5204 The key name to use for the TSIG session key.
5205 If not specified, the default is "local-ddns".
5211 <term><command>session-keyalg</command></term>
5214 The algorithm to use for the TSIG session key.
5215 Valid values are hmac-sha1, hmac-sha224, hmac-sha256,
5216 hmac-sha384, hmac-sha512 and hmac-md5. If not
5217 specified, the default is hmac-sha256.
5223 <term><command>port</command></term>
5226 The UDP/TCP port number the server uses for
5227 receiving and sending DNS protocol traffic.
5228 The default is 53. This option is mainly intended for server
5230 a server using a port other than 53 will not be able to
5238 <term><command>random-device</command></term>
5241 The source of entropy to be used by the server. Entropy is
5243 for DNSSEC operations, such as TKEY transactions and dynamic
5245 zones. This options specifies the device (or file) from which
5247 entropy. If this is a file, operations requiring entropy will
5249 file has been exhausted. If not specified, the default value
5251 <filename>/dev/random</filename>
5252 (or equivalent) when present, and none otherwise. The
5253 <command>random-device</command> option takes
5255 the initial configuration load at server startup time and
5256 is ignored on subsequent reloads.
5262 <term><command>preferred-glue</command></term>
5265 If specified, the listed type (A or AAAA) will be emitted
5267 in the additional section of a query response.
5268 The default is not to prefer any type (NONE).
5273 <varlistentry id="root_delegation_only">
5274 <term><command>root-delegation-only</command></term>
5277 Turn on enforcement of delegation-only in TLDs
5278 (top level domains) and root zones with an optional
5282 DS queries are expected to be made to and be answered by
5283 delegation only zones. Such queries and responses are
5284 treated as an exception to delegation-only processing
5285 and are not converted to NXDOMAIN responses provided
5286 a CNAME is not discovered at the query name.
5289 If a delegation only zone server also serves a child
5290 zone it is not always possible to determine whether
5291 an answer comes from the delegation only zone or the
5292 child zone. SOA NS and DNSKEY records are apex
5293 only records and a matching response that contains
5294 these records or DS is treated as coming from a
5295 child zone. RRSIG records are also examined to see
5296 if they are signed by a child zone or not. The
5297 authority section is also examined to see if there
5298 is evidence that the answer is from the child zone.
5299 Answers that are determined to be from a child zone
5300 are not converted to NXDOMAIN responses. Despite
5301 all these checks there is still a possibility of
5302 false negatives when a child zone is being served.
5305 Similarly false positives can arise from empty nodes
5306 (no records at the name) in the delegation only zone
5307 when the query type is not ANY.
5310 Note some TLDs are not delegation only (e.g. "DE", "LV",
5311 "US" and "MUSEUM"). This list is not exhaustive.
5316 root-delegation-only exclude { "de"; "lv"; "us"; "museum"; };
5324 <term><command>disable-algorithms</command></term>
5327 Disable the specified DNSSEC algorithms at and below the
5329 Multiple <command>disable-algorithms</command>
5330 statements are allowed.
5331 Only the most specific will be applied.
5337 <term><command>dnssec-lookaside</command></term>
5340 When set, <command>dnssec-lookaside</command> provides the
5341 validator with an alternate method to validate DNSKEY
5342 records at the top of a zone. When a DNSKEY is at or
5343 below a domain specified by the deepest
5344 <command>dnssec-lookaside</command>, and the normal DNSSEC
5345 validation has left the key untrusted, the trust-anchor
5346 will be appended to the key name and a DLV record will be
5347 looked up to see if it can validate the key. If the DLV
5348 record validates a DNSKEY (similarly to the way a DS
5349 record does) the DNSKEY RRset is deemed to be trusted.
5352 If <command>dnssec-lookaside</command> is set to
5353 <userinput>auto</userinput>, then built-in default
5354 values for the DLV domain and trust anchor will be
5355 used, along with a built-in key for validation.
5358 If <command>dnssec-lookaside</command> is set to
5359 <userinput>no</userinput>, then dnssec-lookaside
5363 The default DLV key is stored in the file
5364 <filename>bind.keys</filename>;
5365 <command>named</command> will load that key at
5366 startup if <command>dnssec-lookaside</command> is set to
5367 <constant>auto</constant>. A copy of the file is
5368 installed along with <acronym>BIND</acronym> 9, and is
5369 current as of the release date. If the DLV key expires, a
5370 new copy of <filename>bind.keys</filename> can be downloaded
5371 from <ulink url="https://www.isc.org/solutions/dlv/"
5372 >https://www.isc.org/solutions/dlv/</ulink>.
5375 (To prevent problems if <filename>bind.keys</filename> is
5376 not found, the current key is also compiled in to
5377 <command>named</command>. Relying on this is not
5378 recommended, however, as it requires <command>named</command>
5379 to be recompiled with a new key when the DLV key expires.)
5382 NOTE: <command>named</command> only loads certain specific
5383 keys from <filename>bind.keys</filename>: those for the
5384 DLV zone and for the DNS root zone. The file cannot be
5385 used to store keys for other zones.
5391 <term><command>dnssec-must-be-secure</command></term>
5394 Specify hierarchies which must be or may not be secure
5395 (signed and validated). If <userinput>yes</userinput>,
5396 then <command>named</command> will only accept answers if
5397 they are secure. If <userinput>no</userinput>, then normal
5398 DNSSEC validation applies allowing for insecure answers to
5399 be accepted. The specified domain must be under a
5400 <command>trusted-keys</command> or
5401 <command>managed-keys</command> statement, or
5402 <command>dnssec-lookaside</command> must be active.
5408 <term><command>dns64</command></term>
5411 This directive instructs <command>named</command> to
5412 return mapped IPv4 addresses to AAAA queries when
5413 there are no AAAA records. It is intended to be
5414 used in conjunction with a NAT64. Each
5415 <command>dns64</command> defines one DNS64 prefix.
5416 Multiple DNS64 prefixes can be defined.
5419 Compatible IPv6 prefixes have lengths of 32, 40, 48, 56,
5420 64 and 96 as per RFC 6052.
5423 Additionally a reverse IP6.ARPA zone will be created for
5424 the prefix to provide a mapping from the IP6.ARPA names
5425 to the corresponding IN-ADDR.ARPA names using synthesized
5426 CNAMEs. <command>dns64-server</command> and
5427 <command>dns64-contact</command> can be used to specify
5428 the name of the server and contact for the zones. These
5429 are settable at the view / options level. These are
5430 not settable on a per-prefix basis.
5433 Each <command>dns64</command> supports an optional
5434 <command>clients</command> ACL that determines which
5435 clients are affected by this directive. If not defined,
5436 it defaults to <userinput>any;</userinput>.
5439 Each <command>dns64</command> supports an optional
5440 <command>mapped</command> ACL that selects which
5441 IPv4 addresses are to be mapped in the corresponding
5442 A RRset. If not defined it defaults to
5443 <userinput>any;</userinput>.
5446 Normally, DNS64 won't apply to a domain name that
5447 owns one or more AAAA records; these records will
5448 simply be returned. The optional
5449 <command>exclude</command> ACL allows specification
5450 of a list of IPv6 addresses that will be ignored
5451 if they appear in a domain name's AAAA records, and
5452 DNS64 will be applied to any A records the domain
5453 name owns. If not defined, <command>exclude</command>
5457 A optional <command>suffix</command> can also
5458 be defined to set the bits trailing the mapped
5459 IPv4 address bits. By default these bits are
5460 set to <userinput>::</userinput>. The bits
5461 matching the prefix and mapped IPv4 address
5465 If <command>recursive-only</command> is set to
5466 <command>yes</command> the DNS64 synthesis will
5467 only happen for recursive queries. The default
5468 is <command>no</command>.
5471 If <command>break-dnssec</command> is set to
5472 <command>yes</command> the DNS64 synthesis will
5473 happen even if the result, if validated, would
5474 cause a DNSSEC validation failure. If this option
5475 is set to <command>no</command> (the default), the DO
5476 is set on the incoming query, and there are RRSIGs on
5477 the applicable records, then synthesis will not happen.
5480 acl rfc1918 { 10/8; 192.168/16; 172.16/12; };
5482 dns64 64:FF9B::/96 {
5484 mapped { !rfc1918; any; };
5485 exclude { 64:FF9B::/96; ::ffff:0000:0000/96; };
5494 <sect3 id="boolean_options">
5495 <title>Boolean Options</title>
5500 <term><command>allow-new-zones</command></term>
5503 If <userinput>yes</userinput>, then zones can be
5504 added at runtime via <command>rndc addzone</command>
5505 or deleted via <command>rndc delzone</command>.
5506 The default is <userinput>no</userinput>.
5512 <term><command>auth-nxdomain</command></term>
5515 If <userinput>yes</userinput>, then the <command>AA</command> bit
5516 is always set on NXDOMAIN responses, even if the server is
5518 authoritative. The default is <userinput>no</userinput>;
5520 a change from <acronym>BIND</acronym> 8. If you
5521 are using very old DNS software, you
5522 may need to set it to <userinput>yes</userinput>.
5528 <term><command>deallocate-on-exit</command></term>
5531 This option was used in <acronym>BIND</acronym>
5532 8 to enable checking
5533 for memory leaks on exit. <acronym>BIND</acronym> 9 ignores the option and always performs
5540 <term><command>memstatistics</command></term>
5543 Write memory statistics to the file specified by
5544 <command>memstatistics-file</command> at exit.
5545 The default is <userinput>no</userinput> unless
5546 '-m record' is specified on the command line in
5547 which case it is <userinput>yes</userinput>.
5553 <term><command>dialup</command></term>
5556 If <userinput>yes</userinput>, then the
5557 server treats all zones as if they are doing zone transfers
5559 a dial-on-demand dialup link, which can be brought up by
5561 originating from this server. This has different effects
5563 to zone type and concentrates the zone maintenance so that
5565 happens in a short interval, once every <command>heartbeat-interval</command> and
5566 hopefully during the one call. It also suppresses some of
5568 zone maintenance traffic. The default is <userinput>no</userinput>.
5571 The <command>dialup</command> option
5572 may also be specified in the <command>view</command> and
5573 <command>zone</command> statements,
5574 in which case it overrides the global <command>dialup</command>
5578 If the zone is a master zone, then the server will send out a
5580 request to all the slaves (default). This should trigger the
5582 number check in the slave (providing it supports NOTIFY)
5584 to verify the zone while the connection is active.
5585 The set of servers to which NOTIFY is sent can be controlled
5587 <command>notify</command> and <command>also-notify</command>.
5591 zone is a slave or stub zone, then the server will suppress
5593 "zone up to date" (refresh) queries and only perform them
5595 <command>heartbeat-interval</command> expires in
5600 Finer control can be achieved by using
5601 <userinput>notify</userinput> which only sends NOTIFY
5603 <userinput>notify-passive</userinput> which sends NOTIFY
5605 suppresses the normal refresh queries, <userinput>refresh</userinput>
5606 which suppresses normal refresh processing and sends refresh
5608 when the <command>heartbeat-interval</command>
5610 <userinput>passive</userinput> which just disables normal
5615 <informaltable colsep="0" rowsep="0">
5616 <tgroup cols="4" colsep="0" rowsep="0" tgroupstyle="4Level-table">
5617 <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
5618 <colspec colname="2" colnum="2" colsep="0" colwidth="1.150in"/>
5619 <colspec colname="3" colnum="3" colsep="0" colwidth="1.150in"/>
5620 <colspec colname="4" colnum="4" colsep="0" colwidth="1.150in"/>
5646 <para><command>no</command> (default)</para>
5666 <para><command>yes</command></para>
5686 <para><command>notify</command></para>
5706 <para><command>refresh</command></para>
5726 <para><command>passive</command></para>
5746 <para><command>notify-passive</command></para>
5769 Note that normal NOTIFY processing is not affected by
5770 <command>dialup</command>.
5777 <term><command>fake-iquery</command></term>
5780 In <acronym>BIND</acronym> 8, this option
5781 enabled simulating the obsolete DNS query type
5782 IQUERY. <acronym>BIND</acronym> 9 never does
5789 <term><command>fetch-glue</command></term>
5792 This option is obsolete.
5793 In BIND 8, <userinput>fetch-glue yes</userinput>
5794 caused the server to attempt to fetch glue resource records
5796 didn't have when constructing the additional
5797 data section of a response. This is now considered a bad
5799 and BIND 9 never does it.
5805 <term><command>flush-zones-on-shutdown</command></term>
5808 When the nameserver exits due receiving SIGTERM,
5809 flush or do not flush any pending zone writes. The default
5811 <command>flush-zones-on-shutdown</command> <userinput>no</userinput>.
5817 <term><command>has-old-clients</command></term>
5820 This option was incorrectly implemented
5821 in <acronym>BIND</acronym> 8, and is ignored by <acronym>BIND</acronym> 9.
5822 To achieve the intended effect
5824 <command>has-old-clients</command> <userinput>yes</userinput>, specify
5825 the two separate options <command>auth-nxdomain</command> <userinput>yes</userinput>
5826 and <command>rfc2308-type1</command> <userinput>no</userinput> instead.
5832 <term><command>host-statistics</command></term>
5835 In BIND 8, this enables keeping of
5836 statistics for every host that the name server interacts
5838 Not implemented in BIND 9.
5844 <term><command>maintain-ixfr-base</command></term>
5847 <emphasis>This option is obsolete</emphasis>.
5848 It was used in <acronym>BIND</acronym> 8 to
5849 determine whether a transaction log was
5850 kept for Incremental Zone Transfer. <acronym>BIND</acronym> 9 maintains a transaction
5851 log whenever possible. If you need to disable outgoing
5853 transfers, use <command>provide-ixfr</command> <userinput>no</userinput>.
5859 <term><command>minimal-responses</command></term>
5862 If <userinput>yes</userinput>, then when generating
5863 responses the server will only add records to the authority
5864 and additional data sections when they are required (e.g.
5865 delegations, negative responses). This may improve the
5866 performance of the server.
5867 The default is <userinput>no</userinput>.
5873 <term><command>multiple-cnames</command></term>
5876 This option was used in <acronym>BIND</acronym> 8 to allow
5877 a domain name to have multiple CNAME records in violation of
5878 the DNS standards. <acronym>BIND</acronym> 9.2 onwards
5879 always strictly enforces the CNAME rules both in master
5880 files and dynamic updates.
5886 <term><command>notify</command></term>
5889 If <userinput>yes</userinput> (the default),
5890 DNS NOTIFY messages are sent when a zone the server is
5892 changes, see <xref linkend="notify"/>. The messages are
5894 servers listed in the zone's NS records (except the master
5896 in the SOA MNAME field), and to any servers listed in the
5897 <command>also-notify</command> option.
5900 If <userinput>master-only</userinput>, notifies are only
5903 If <userinput>explicit</userinput>, notifies are sent only
5905 servers explicitly listed using <command>also-notify</command>.
5906 If <userinput>no</userinput>, no notifies are sent.
5909 The <command>notify</command> option may also be
5910 specified in the <command>zone</command>
5912 in which case it overrides the <command>options notify</command> statement.
5913 It would only be necessary to turn off this option if it
5921 <term><command>notify-to-soa</command></term>
5924 If <userinput>yes</userinput> do not check the nameservers
5925 in the NS RRset against the SOA MNAME. Normally a NOTIFY
5926 message is not sent to the SOA MNAME (SOA ORIGIN) as it is
5927 supposed to contain the name of the ultimate master.
5928 Sometimes, however, a slave is listed as the SOA MNAME in
5929 hidden master configurations and in that case you would
5930 want the ultimate master to still send NOTIFY messages to
5931 all the nameservers listed in the NS RRset.
5937 <term><command>recursion</command></term>
5940 If <userinput>yes</userinput>, and a
5941 DNS query requests recursion, then the server will attempt
5943 all the work required to answer the query. If recursion is
5945 and the server does not already know the answer, it will
5947 referral response. The default is
5948 <userinput>yes</userinput>.
5949 Note that setting <command>recursion no</command> does not prevent
5950 clients from getting data from the server's cache; it only
5951 prevents new data from being cached as an effect of client
5953 Caching may still occur as an effect the server's internal
5954 operation, such as NOTIFY address lookups.
5955 See also <command>fetch-glue</command> above.
5961 <term><command>request-nsid</command></term>
5964 If <userinput>yes</userinput>, then an empty EDNS(0)
5965 NSID (Name Server Identifier) option is sent with all
5966 queries to authoritative name servers during iterative
5967 resolution. If the authoritative server returns an NSID
5968 option in its response, then its contents are logged in
5969 the <command>resolver</command> category at level
5970 <command>info</command>.
5971 The default is <userinput>no</userinput>.
5977 <term><command>rfc2308-type1</command></term>
5980 Setting this to <userinput>yes</userinput> will
5981 cause the server to send NS records along with the SOA
5983 answers. The default is <userinput>no</userinput>.
5987 Not yet implemented in <acronym>BIND</acronym>
5995 <term><command>use-id-pool</command></term>
5998 <emphasis>This option is obsolete</emphasis>.
5999 <acronym>BIND</acronym> 9 always allocates query
6006 <term><command>zone-statistics</command></term>
6009 If <userinput>yes</userinput>, the server will collect
6010 statistical data on all zones (unless specifically turned
6012 on a per-zone basis by specifying <command>zone-statistics no</command>
6013 in the <command>zone</command> statement).
6014 The default is <userinput>no</userinput>.
6015 These statistics may be accessed
6016 using <command>rndc stats</command>, which will
6017 dump them to the file listed
6018 in the <command>statistics-file</command>. See
6019 also <xref linkend="statsfile"/>.
6025 <term><command>use-ixfr</command></term>
6028 <emphasis>This option is obsolete</emphasis>.
6029 If you need to disable IXFR to a particular server or
6031 the information on the <command>provide-ixfr</command> option
6032 in <xref linkend="server_statement_definition_and_usage"/>.
6034 <xref linkend="incremental_zone_transfers"/>.
6040 <term><command>provide-ixfr</command></term>
6043 See the description of
6044 <command>provide-ixfr</command> in
6045 <xref linkend="server_statement_definition_and_usage"/>.
6051 <term><command>request-ixfr</command></term>
6054 See the description of
6055 <command>request-ixfr</command> in
6056 <xref linkend="server_statement_definition_and_usage"/>.
6062 <term><command>treat-cr-as-space</command></term>
6065 This option was used in <acronym>BIND</acronym>
6067 the server treat carriage return ("<command>\r</command>") characters the same way
6068 as a space or tab character,
6069 to facilitate loading of zone files on a UNIX system that
6071 on an NT or DOS machine. In <acronym>BIND</acronym> 9, both UNIX "<command>\n</command>"
6072 and NT/DOS "<command>\r\n</command>" newlines
6073 are always accepted,
6074 and the option is ignored.
6080 <term><command>additional-from-auth</command></term>
6081 <term><command>additional-from-cache</command></term>
6085 These options control the behavior of an authoritative
6087 answering queries which have additional data, or when
6093 When both of these options are set to <userinput>yes</userinput>
6095 query is being answered from authoritative data (a zone
6096 configured into the server), the additional data section of
6098 reply will be filled in using data from other authoritative
6100 and from the cache. In some situations this is undesirable,
6102 as when there is concern over the correctness of the cache,
6104 in servers where slave zones may be added and modified by
6105 untrusted third parties. Also, avoiding
6106 the search for this additional data will speed up server
6108 at the possible expense of additional queries to resolve
6110 otherwise be provided in the additional section.
6114 For example, if a query asks for an MX record for host <literal>foo.example.com</literal>,
6115 and the record found is "<literal>MX 10 mail.example.net</literal>", normally the address
6116 records (A and AAAA) for <literal>mail.example.net</literal> will be provided as well,
6117 if known, even though they are not in the example.com zone.
6118 Setting these options to <command>no</command>
6119 disables this behavior and makes
6120 the server only search for additional data in the zone it
6125 These options are intended for use in authoritative-only
6126 servers, or in authoritative-only views. Attempts to set
6127 them to <command>no</command> without also
6129 <command>recursion no</command> will cause the
6131 ignore the options and log a warning message.
6135 Specifying <command>additional-from-cache no</command> actually
6136 disables the use of the cache not only for additional data
6138 but also when looking up the answer. This is usually the
6140 behavior in an authoritative-only server where the
6142 the cached data is an issue.
6146 When a name server is non-recursively queried for a name
6148 below the apex of any served zone, it normally answers with
6150 "upwards referral" to the root servers or the servers of
6152 known parent of the query name. Since the data in an
6154 comes from the cache, the server will not be able to provide
6156 referrals when <command>additional-from-cache no</command>
6157 has been specified. Instead, it will respond to such
6159 with REFUSED. This should not cause any problems since
6160 upwards referrals are not required for the resolution
6168 <term><command>match-mapped-addresses</command></term>
6171 If <userinput>yes</userinput>, then an
6172 IPv4-mapped IPv6 address will match any address match
6173 list entries that match the corresponding IPv4 address.
6176 This option was introduced to work around a kernel quirk
6177 in some operating systems that causes IPv4 TCP
6178 connections, such as zone transfers, to be accepted on an
6179 IPv6 socket using mapped addresses. This caused address
6180 match lists designed for IPv4 to fail to match. However,
6181 <command>named</command> now solves this problem
6182 internally. The use of this option is discouraged.
6188 <term><command>filter-aaaa-on-v4</command></term>
6191 This option is only available when
6192 <acronym>BIND</acronym> 9 is compiled with the
6193 <userinput>--enable-filter-aaaa</userinput> option on the
6194 "configure" command line. It is intended to help the
6195 transition from IPv4 to IPv6 by not giving IPv6 addresses
6196 to DNS clients unless they have connections to the IPv6
6197 Internet. This is not recommended unless absolutely
6198 necessary. The default is <userinput>no</userinput>.
6199 The <command>filter-aaaa-on-v4</command> option
6200 may also be specified in <command>view</command> statements
6201 to override the global <command>filter-aaaa-on-v4</command>
6205 If <userinput>yes</userinput>,
6206 the DNS client is at an IPv4 address, in <command>filter-aaaa</command>,
6207 and if the response does not include DNSSEC signatures,
6208 then all AAAA records are deleted from the response.
6209 This filtering applies to all responses and not only
6210 authoritative responses.
6213 If <userinput>break-dnssec</userinput>,
6214 then AAAA records are deleted even when dnssec is enabled.
6215 As suggested by the name, this makes the response not verify,
6216 because the DNSSEC protocol is designed detect deletions.
6219 This mechanism can erroneously cause other servers to
6220 not give AAAA records to their clients.
6221 A recursing server with both IPv6 and IPv4 network connections
6222 that queries an authoritative server using this mechanism
6223 via IPv4 will be denied AAAA records even if its client is
6227 This mechanism is applied to authoritative as well as
6228 non-authoritative records.
6229 A client using IPv4 that is not allowed recursion can
6230 erroneously be given AAAA records because the server is not
6231 allowed to check for A records.
6234 Some AAAA records are given to IPv4 clients in glue records.
6235 IPv4 clients that are servers can then erroneously
6236 answer requests for AAAA records received via IPv4.
6242 <term><command>ixfr-from-differences</command></term>
6245 When <userinput>yes</userinput> and the server loads a new version of a master
6246 zone from its zone file or receives a new version of a slave
6247 file by a non-incremental zone transfer, it will compare
6248 the new version to the previous one and calculate a set
6249 of differences. The differences are then logged in the
6250 zone's journal file such that the changes can be transmitted
6251 to downstream slaves as an incremental zone transfer.
6254 By allowing incremental zone transfers to be used for
6255 non-dynamic zones, this option saves bandwidth at the
6256 expense of increased CPU and memory consumption at the
6258 In particular, if the new version of a zone is completely
6259 different from the previous one, the set of differences
6260 will be of a size comparable to the combined size of the
6261 old and new zone version, and the server will need to
6262 temporarily allocate memory to hold this complete
6265 <para><command>ixfr-from-differences</command>
6266 also accepts <command>master</command> and
6267 <command>slave</command> at the view and options
6269 <command>ixfr-from-differences</command> to be enabled for
6270 all <command>master</command> or
6271 <command>slave</command> zones respectively.
6272 It is off by default.
6278 <term><command>multi-master</command></term>
6281 This should be set when you have multiple masters for a zone
6283 addresses refer to different machines. If <userinput>yes</userinput>, <command>named</command> will
6285 when the serial number on the master is less than what <command>named</command>
6287 has. The default is <userinput>no</userinput>.
6293 <term><command>dnssec-enable</command></term>
6296 Enable DNSSEC support in <command>named</command>. Unless set to <userinput>yes</userinput>,
6297 <command>named</command> behaves as if it does not support DNSSEC.
6298 The default is <userinput>yes</userinput>.
6304 <term><command>dnssec-validation</command></term>
6307 Enable DNSSEC validation in <command>named</command>.
6308 Note <command>dnssec-enable</command> also needs to be
6309 set to <userinput>yes</userinput> to be effective.
6310 If set to <userinput>no</userinput>, DNSSEC validation
6311 is disabled. If set to <userinput>auto</userinput>,
6312 DNSSEC validation is enabled, and a default
6313 trust-anchor for the DNS root zone is used. If set to
6314 <userinput>yes</userinput>, DNSSEC validation is enabled,
6315 but a trust anchor must be manually configured using
6316 a <command>trusted-keys</command> or
6317 <command>managed-keys</command> statement. The default
6318 is <userinput>yes</userinput>.
6324 <term><command>dnssec-accept-expired</command></term>
6327 Accept expired signatures when verifying DNSSEC signatures.
6328 The default is <userinput>no</userinput>.
6329 Setting this option to <userinput>yes</userinput>
6330 leaves <command>named</command> vulnerable to
6337 <term><command>querylog</command></term>
6340 Specify whether query logging should be started when <command>named</command>
6342 If <command>querylog</command> is not specified,
6343 then the query logging
6344 is determined by the presence of the logging category <command>queries</command>.
6350 <term><command>check-names</command></term>
6353 This option is used to restrict the character set and syntax
6355 certain domain names in master files and/or DNS responses
6357 from the network. The default varies according to usage
6359 <command>master</command> zones the default is <command>fail</command>.
6360 For <command>slave</command> zones the default
6361 is <command>warn</command>.
6362 For answers received from the network (<command>response</command>)
6363 the default is <command>ignore</command>.
6366 The rules for legal hostnames and mail domains are derived
6367 from RFC 952 and RFC 821 as modified by RFC 1123.
6369 <para><command>check-names</command>
6370 applies to the owner names of A, AAAA and MX records.
6371 It also applies to the domain names in the RDATA of NS, SOA,
6372 MX, and SRV records.
6373 It also applies to the RDATA of PTR records where the owner
6374 name indicated that it is a reverse lookup of a hostname
6375 (the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT).
6381 <term><command>check-dup-records</command></term>
6384 Check master zones for records that are treated as different
6385 by DNSSEC but are semantically equal in plain DNS. The
6386 default is to <command>warn</command>. Other possible
6387 values are <command>fail</command> and
6388 <command>ignore</command>.
6394 <term><command>check-mx</command></term>
6397 Check whether the MX record appears to refer to a IP address.
6398 The default is to <command>warn</command>. Other possible
6399 values are <command>fail</command> and
6400 <command>ignore</command>.
6406 <term><command>check-wildcard</command></term>
6409 This option is used to check for non-terminal wildcards.
6410 The use of non-terminal wildcards is almost always as a
6412 to understand the wildcard matching algorithm (RFC 1034).
6414 affects master zones. The default (<command>yes</command>) is to check
6415 for non-terminal wildcards and issue a warning.
6421 <term><command>check-integrity</command></term>
6424 Perform post load zone integrity checks on master
6425 zones. This checks that MX and SRV records refer
6426 to address (A or AAAA) records and that glue
6427 address records exist for delegated zones. For
6428 MX and SRV records only in-zone hostnames are
6429 checked (for out-of-zone hostnames use
6430 <command>named-checkzone</command>).
6431 For NS records only names below top of zone are
6432 checked (for out-of-zone names and glue consistency
6433 checks use <command>named-checkzone</command>).
6434 The default is <command>yes</command>.
6437 Check that the two forms of Sender Policy Framework
6438 records (TXT records starting with "v=spf1" and SPF) either
6439 both exist or both don't exist. Warnings are
6440 emitted it they don't and be suppressed with
6441 <command>check-spf</command>.
6447 <term><command>check-mx-cname</command></term>
6450 If <command>check-integrity</command> is set then
6451 fail, warn or ignore MX records that refer
6452 to CNAMES. The default is to <command>warn</command>.
6458 <term><command>check-srv-cname</command></term>
6461 If <command>check-integrity</command> is set then
6462 fail, warn or ignore SRV records that refer
6463 to CNAMES. The default is to <command>warn</command>.
6469 <term><command>check-sibling</command></term>
6472 When performing integrity checks, also check that
6473 sibling glue exists. The default is <command>yes</command>.
6479 <term><command>check-spf</command></term>
6482 When performing integrity checks, check that the
6483 two forms of Sender Policy Framwork records (TXT
6484 records starting with "v=spf1" and SPF) both exist
6485 or both don't exist and issue a warning if not
6486 met. The default is <command>warn</command>.
6492 <term><command>zero-no-soa-ttl</command></term>
6495 When returning authoritative negative responses to
6496 SOA queries set the TTL of the SOA record returned in
6497 the authority section to zero.
6498 The default is <command>yes</command>.
6504 <term><command>zero-no-soa-ttl-cache</command></term>
6507 When caching a negative response to a SOA query
6508 set the TTL to zero.
6509 The default is <command>no</command>.
6515 <term><command>update-check-ksk</command></term>
6518 When set to the default value of <literal>yes</literal>,
6519 check the KSK bit in each key to determine how the key
6520 should be used when generating RRSIGs for a secure zone.
6523 Ordinarily, zone-signing keys (that is, keys without the
6524 KSK bit set) are used to sign the entire zone, while
6525 key-signing keys (keys with the KSK bit set) are only
6526 used to sign the DNSKEY RRset at the zone apex.
6527 However, if this option is set to <literal>no</literal>,
6528 then the KSK bit is ignored; KSKs are treated as if they
6529 were ZSKs and are used to sign the entire zone. This is
6530 similar to the <command>dnssec-signzone -z</command>
6531 command line option.
6534 When this option is set to <literal>yes</literal>, there
6535 must be at least two active keys for every algorithm
6536 represented in the DNSKEY RRset: at least one KSK and one
6537 ZSK per algorithm. If there is any algorithm for which
6538 this requirement is not met, this option will be ignored
6545 <term><command>dnssec-dnskey-kskonly</command></term>
6548 When this option and <command>update-check-ksk</command>
6549 are both set to <literal>yes</literal>, only key-signing
6550 keys (that is, keys with the KSK bit set) will be used
6551 to sign the DNSKEY RRset at the zone apex. Zone-signing
6552 keys (keys without the KSK bit set) will be used to sign
6553 the remainder of the zone, but not the DNSKEY RRset.
6554 This is similar to the
6555 <command>dnssec-signzone -x</command> command line option.
6558 The default is <command>no</command>. If
6559 <command>update-check-ksk</command> is set to
6560 <literal>no</literal>, this option is ignored.
6566 <term><command>try-tcp-refresh</command></term>
6569 Try to refresh the zone using TCP if UDP queries fail.
6570 For BIND 8 compatibility, the default is
6571 <command>yes</command>.
6577 <term><command>dnssec-secure-to-insecure</command></term>
6580 Allow a dynamic zone to transition from secure to
6581 insecure (i.e., signed to unsigned) by deleting all
6582 of the DNSKEY records. The default is <command>no</command>.
6583 If set to <command>yes</command>, and if the DNSKEY RRset
6584 at the zone apex is deleted, all RRSIG and NSEC records
6585 will be removed from the zone as well.
6588 If the zone uses NSEC3, then it is also necessary to
6589 delete the NSEC3PARAM RRset from the zone apex; this will
6590 cause the removal of all corresponding NSEC3 records.
6591 (It is expected that this requirement will be eliminated
6592 in a future release.)
6595 Note that if a zone has been configured with
6596 <command>auto-dnssec maintain</command> and the
6597 private keys remain accessible in the key repository,
6598 then the zone will be automatically signed again the
6599 next time <command>named</command> is started.
6609 <title>Forwarding</title>
6611 The forwarding facility can be used to create a large site-wide
6612 cache on a few servers, reducing traffic over links to external
6613 name servers. It can also be used to allow queries by servers that
6614 do not have direct access to the Internet, but wish to look up
6616 names anyway. Forwarding occurs only on those queries for which
6617 the server is not authoritative and does not have the answer in
6623 <term><command>forward</command></term>
6626 This option is only meaningful if the
6627 forwarders list is not empty. A value of <varname>first</varname>,
6628 the default, causes the server to query the forwarders
6630 if that doesn't answer the question, the server will then
6632 the answer itself. If <varname>only</varname> is
6634 server will only query the forwarders.
6640 <term><command>forwarders</command></term>
6643 Specifies the IP addresses to be used
6644 for forwarding. The default is the empty list (no
6653 Forwarding can also be configured on a per-domain basis, allowing
6654 for the global forwarding options to be overridden in a variety
6655 of ways. You can set particular domains to use different
6657 or have a different <command>forward only/first</command> behavior,
6658 or not forward at all, see <xref linkend="zone_statement_grammar"/>.
6663 <title>Dual-stack Servers</title>
6665 Dual-stack servers are used as servers of last resort to work
6667 problems in reachability due the lack of support for either IPv4
6669 on the host machine.
6674 <term><command>dual-stack-servers</command></term>
6677 Specifies host names or addresses of machines with access to
6678 both IPv4 and IPv6 transports. If a hostname is used, the
6680 to resolve the name using only the transport it has. If the
6682 stacked, then the <command>dual-stack-servers</command> have no effect unless
6683 access to a transport has been disabled on the command line
6684 (e.g. <command>named -4</command>).
6691 <sect3 id="access_control">
6692 <title>Access Control</title>
6695 Access to the server can be restricted based on the IP address
6696 of the requesting system. See <xref linkend="address_match_lists"/> for
6697 details on how to specify IP address lists.
6703 <term><command>allow-notify</command></term>
6706 Specifies which hosts are allowed to
6707 notify this server, a slave, of zone changes in addition
6708 to the zone masters.
6709 <command>allow-notify</command> may also be
6711 <command>zone</command> statement, in which case
6713 <command>options allow-notify</command>
6714 statement. It is only meaningful
6715 for a slave zone. If not specified, the default is to
6716 process notify messages
6717 only from a zone's master.
6723 <term><command>allow-query</command></term>
6726 Specifies which hosts are allowed to ask ordinary
6727 DNS questions. <command>allow-query</command> may
6728 also be specified in the <command>zone</command>
6729 statement, in which case it overrides the
6730 <command>options allow-query</command> statement.
6731 If not specified, the default is to allow queries
6736 <command>allow-query-cache</command> is now
6737 used to specify access to the cache.
6744 <term><command>allow-query-on</command></term>
6747 Specifies which local addresses can accept ordinary
6748 DNS questions. This makes it possible, for instance,
6749 to allow queries on internal-facing interfaces but
6750 disallow them on external-facing ones, without
6751 necessarily knowing the internal network's addresses.
6754 Note that <command>allow-query-on</command> is only
6755 checked for queries that are permitted by
6756 <command>allow-query</command>. A query must be
6757 allowed by both ACLs, or it will be refused.
6760 <command>allow-query-on</command> may
6761 also be specified in the <command>zone</command>
6762 statement, in which case it overrides the
6763 <command>options allow-query-on</command> statement.
6766 If not specified, the default is to allow queries
6771 <command>allow-query-cache</command> is
6772 used to specify access to the cache.
6779 <term><command>allow-query-cache</command></term>
6782 Specifies which hosts are allowed to get answers
6783 from the cache. If <command>allow-query-cache</command>
6784 is not set then <command>allow-recursion</command>
6785 is used if set, otherwise <command>allow-query</command>
6786 is used if set unless <command>recursion no;</command> is
6787 set in which case <command>none;</command> is used,
6788 otherwise the default (<command>localnets;</command>
6789 <command>localhost;</command>) is used.
6795 <term><command>allow-query-cache-on</command></term>
6798 Specifies which local addresses can give answers
6799 from the cache. If not specified, the default is
6800 to allow cache queries on any address,
6801 <command>localnets</command> and
6802 <command>localhost</command>.
6808 <term><command>allow-recursion</command></term>
6811 Specifies which hosts are allowed to make recursive
6812 queries through this server. If
6813 <command>allow-recursion</command> is not set
6814 then <command>allow-query-cache</command> is
6815 used if set, otherwise <command>allow-query</command>
6816 is used if set, otherwise the default
6817 (<command>localnets;</command>
6818 <command>localhost;</command>) is used.
6824 <term><command>allow-recursion-on</command></term>
6827 Specifies which local addresses can accept recursive
6828 queries. If not specified, the default is to allow
6829 recursive queries on all addresses.
6835 <term><command>allow-update</command></term>
6838 Specifies which hosts are allowed to
6839 submit Dynamic DNS updates for master zones. The default is
6841 updates from all hosts. Note that allowing updates based
6842 on the requestor's IP address is insecure; see
6843 <xref linkend="dynamic_update_security"/> for details.
6849 <term><command>allow-update-forwarding</command></term>
6852 Specifies which hosts are allowed to
6853 submit Dynamic DNS updates to slave zones to be forwarded to
6855 master. The default is <userinput>{ none; }</userinput>,
6857 means that no update forwarding will be performed. To
6859 update forwarding, specify
6860 <userinput>allow-update-forwarding { any; };</userinput>.
6861 Specifying values other than <userinput>{ none; }</userinput> or
6862 <userinput>{ any; }</userinput> is usually
6863 counterproductive, since
6864 the responsibility for update access control should rest
6866 master server, not the slaves.
6869 Note that enabling the update forwarding feature on a slave
6871 may expose master servers relying on insecure IP address
6873 access control to attacks; see <xref linkend="dynamic_update_security"/>
6880 <term><command>allow-v6-synthesis</command></term>
6883 This option was introduced for the smooth transition from
6885 to A6 and from "nibble labels" to binary labels.
6886 However, since both A6 and binary labels were then
6888 this option was also deprecated.
6889 It is now ignored with some warning messages.
6895 <term><command>allow-transfer</command></term>
6898 Specifies which hosts are allowed to
6899 receive zone transfers from the server. <command>allow-transfer</command> may
6900 also be specified in the <command>zone</command>
6902 case it overrides the <command>options allow-transfer</command> statement.
6903 If not specified, the default is to allow transfers to all
6910 <term><command>blackhole</command></term>
6913 Specifies a list of addresses that the
6914 server will not accept queries from or use to resolve a
6916 from these addresses will not be responded to. The default
6917 is <userinput>none</userinput>.
6923 <term><command>filter-aaaa</command></term>
6926 Specifies a list of addresses to which
6927 <command>filter-aaaa-on-v4</command>
6928 is applies. The default is <userinput>any</userinput>.
6934 <term><command>resolver-query-timeout</command></term>
6937 The amount of time the resolver will spend attempting
6938 to resolve a recursive query before failing. The default
6939 and minimum is <literal>10</literal> and the maximum is
6940 <literal>30</literal>. Setting it to <literal>0</literal>
6941 will result in the default being used.
6950 <title>Interfaces</title>
6952 The interfaces and ports that the server will answer queries
6953 from may be specified using the <command>listen-on</command> option. <command>listen-on</command> takes
6954 an optional port and an <varname>address_match_list</varname>.
6955 The server will listen on all interfaces allowed by the address
6956 match list. If a port is not specified, port 53 will be used.
6959 Multiple <command>listen-on</command> statements are
6964 <programlisting>listen-on { 5.6.7.8; };
6965 listen-on port 1234 { !1.2.3.4; 1.2/16; };
6969 will enable the name server on port 53 for the IP address
6970 5.6.7.8, and on port 1234 of an address on the machine in net
6971 1.2 that is not 1.2.3.4.
6975 If no <command>listen-on</command> is specified, the
6976 server will listen on port 53 on all IPv4 interfaces.
6980 The <command>listen-on-v6</command> option is used to
6981 specify the interfaces and the ports on which the server will
6983 for incoming queries sent using IPv6.
6987 When <programlisting>{ any; }</programlisting> is
6989 as the <varname>address_match_list</varname> for the
6990 <command>listen-on-v6</command> option,
6991 the server does not bind a separate socket to each IPv6 interface
6992 address as it does for IPv4 if the operating system has enough API
6993 support for IPv6 (specifically if it conforms to RFC 3493 and RFC
6995 Instead, it listens on the IPv6 wildcard address.
6996 If the system only has incomplete API support for IPv6, however,
6997 the behavior is the same as that for IPv4.
7001 A list of particular IPv6 addresses can also be specified, in
7003 the server listens on a separate socket for each specified
7005 regardless of whether the desired API is supported by the system.
7009 Multiple <command>listen-on-v6</command> options can
7014 <programlisting>listen-on-v6 { any; };
7015 listen-on-v6 port 1234 { !2001:db8::/32; any; };
7019 will enable the name server on port 53 for any IPv6 addresses
7020 (with a single wildcard socket),
7021 and on port 1234 of IPv6 addresses that is not in the prefix
7022 2001:db8::/32 (with separate sockets for each matched address.)
7026 To make the server not listen on any IPv6 address, use
7029 <programlisting>listen-on-v6 { none; };
7033 If no <command>listen-on-v6</command> option is
7034 specified, the server will not listen on any IPv6 address
7035 unless <command>-6</command> is specified when <command>named</command> is
7036 invoked. If <command>-6</command> is specified then
7037 <command>named</command> will listen on port 53 on all IPv6 interfaces by default.
7041 <sect3 id="query_address">
7042 <title>Query Address</title>
7044 If the server doesn't know the answer to a question, it will
7045 query other name servers. <command>query-source</command> specifies
7046 the address and port used for such queries. For queries sent over
7047 IPv6, there is a separate <command>query-source-v6</command> option.
7048 If <command>address</command> is <command>*</command> (asterisk) or is omitted,
7049 a wildcard IP address (<command>INADDR_ANY</command>)
7054 If <command>port</command> is <command>*</command> or is omitted,
7055 a random port number from a pre-configured
7056 range is picked up and will be used for each query.
7057 The port range(s) is that specified in
7058 the <command>use-v4-udp-ports</command> (for IPv4)
7059 and <command>use-v6-udp-ports</command> (for IPv6)
7060 options, excluding the ranges specified in
7061 the <command>avoid-v4-udp-ports</command>
7062 and <command>avoid-v6-udp-ports</command> options, respectively.
7066 The defaults of the <command>query-source</command> and
7067 <command>query-source-v6</command> options
7071 <programlisting>query-source address * port *;
7072 query-source-v6 address * port *;
7076 If <command>use-v4-udp-ports</command> or
7077 <command>use-v6-udp-ports</command> is unspecified,
7078 <command>named</command> will check if the operating
7079 system provides a programming interface to retrieve the
7080 system's default range for ephemeral ports.
7081 If such an interface is available,
7082 <command>named</command> will use the corresponding system
7083 default range; otherwise, it will use its own defaults:
7086 <programlisting>use-v4-udp-ports { range 1024 65535; };
7087 use-v6-udp-ports { range 1024 65535; };
7091 Note: make sure the ranges be sufficiently large for
7092 security. A desirable size depends on various parameters,
7093 but we generally recommend it contain at least 16384 ports
7094 (14 bits of entropy).
7095 Note also that the system's default range when used may be
7096 too small for this purpose, and that the range may even be
7097 changed while <command>named</command> is running; the new
7098 range will automatically be applied when <command>named</command>
7101 configure <command>use-v4-udp-ports</command> and
7102 <command>use-v6-udp-ports</command> explicitly so that the
7103 ranges are sufficiently large and are reasonably
7104 independent from the ranges used by other applications.
7108 Note: the operational configuration
7109 where <command>named</command> runs may prohibit the use
7110 of some ports. For example, UNIX systems will not allow
7111 <command>named</command> running without a root privilege
7112 to use ports less than 1024.
7113 If such ports are included in the specified (or detected)
7114 set of query ports, the corresponding query attempts will
7115 fail, resulting in resolution failures or delay.
7116 It is therefore important to configure the set of ports
7117 that can be safely used in the expected operational environment.
7121 The defaults of the <command>avoid-v4-udp-ports</command> and
7122 <command>avoid-v6-udp-ports</command> options
7126 <programlisting>avoid-v4-udp-ports {};
7127 avoid-v6-udp-ports {};
7131 Note: BIND 9.5.0 introduced
7132 the <command>use-queryport-pool</command>
7133 option to support a pool of such random ports, but this
7134 option is now obsolete because reusing the same ports in
7135 the pool may not be sufficiently secure.
7136 For the same reason, it is generally strongly discouraged to
7137 specify a particular port for the
7138 <command>query-source</command> or
7139 <command>query-source-v6</command> options;
7140 it implicitly disables the use of randomized port numbers.
7145 <term><command>use-queryport-pool</command></term>
7148 This option is obsolete.
7154 <term><command>queryport-pool-ports</command></term>
7157 This option is obsolete.
7163 <term><command>queryport-pool-updateinterval</command></term>
7166 This option is obsolete.
7174 The address specified in the <command>query-source</command> option
7175 is used for both UDP and TCP queries, but the port applies only
7176 to UDP queries. TCP queries always use a random
7182 Solaris 2.5.1 and earlier does not support setting the source
7183 address for TCP sockets.
7188 See also <command>transfer-source</command> and
7189 <command>notify-source</command>.
7194 <sect3 id="zone_transfers">
7195 <title>Zone Transfers</title>
7197 <acronym>BIND</acronym> has mechanisms in place to
7198 facilitate zone transfers
7199 and set limits on the amount of load that transfers place on the
7200 system. The following options apply to zone transfers.
7206 <term><command>also-notify</command></term>
7209 Defines a global list of IP addresses of name servers
7210 that are also sent NOTIFY messages whenever a fresh copy of
7212 zone is loaded, in addition to the servers listed in the
7214 This helps to ensure that copies of the zones will
7215 quickly converge on stealth servers.
7216 Optionally, a port may be specified with each
7217 <command>also-notify</command> address to send
7218 the notify messages to a port other than the
7220 If an <command>also-notify</command> list
7221 is given in a <command>zone</command> statement,
7223 the <command>options also-notify</command>
7224 statement. When a <command>zone notify</command>
7226 is set to <command>no</command>, the IP
7227 addresses in the global <command>also-notify</command> list will
7228 not be sent NOTIFY messages for that zone. The default is
7230 list (no global notification list).
7236 <term><command>max-transfer-time-in</command></term>
7239 Inbound zone transfers running longer than
7240 this many minutes will be terminated. The default is 120
7242 (2 hours). The maximum value is 28 days (40320 minutes).
7248 <term><command>max-transfer-idle-in</command></term>
7251 Inbound zone transfers making no progress
7252 in this many minutes will be terminated. The default is 60
7254 (1 hour). The maximum value is 28 days (40320 minutes).
7260 <term><command>max-transfer-time-out</command></term>
7263 Outbound zone transfers running longer than
7264 this many minutes will be terminated. The default is 120
7266 (2 hours). The maximum value is 28 days (40320 minutes).
7272 <term><command>max-transfer-idle-out</command></term>
7275 Outbound zone transfers making no progress
7276 in this many minutes will be terminated. The default is 60
7278 hour). The maximum value is 28 days (40320 minutes).
7284 <term><command>serial-query-rate</command></term>
7287 Slave servers will periodically query master
7288 servers to find out if zone serial numbers have
7289 changed. Each such query uses a minute amount of
7290 the slave server's network bandwidth. To limit
7291 the amount of bandwidth used, BIND 9 limits the
7292 rate at which queries are sent. The value of the
7293 <command>serial-query-rate</command> option, an
7294 integer, is the maximum number of queries sent
7295 per second. The default is 20.
7298 In addition to controlling the rate SOA refresh
7299 queries are issued at
7300 <command>serial-query-rate</command> also controls
7301 the rate at which NOTIFY messages are sent from
7302 both master and slave zones.
7308 <term><command>serial-queries</command></term>
7311 In BIND 8, the <command>serial-queries</command>
7313 set the maximum number of concurrent serial number queries
7314 allowed to be outstanding at any given time.
7315 BIND 9 does not limit the number of outstanding
7316 serial queries and ignores the <command>serial-queries</command> option.
7317 Instead, it limits the rate at which the queries are sent
7318 as defined using the <command>serial-query-rate</command> option.
7324 <term><command>transfer-format</command></term>
7328 Zone transfers can be sent using two different formats,
7329 <command>one-answer</command> and
7330 <command>many-answers</command>.
7331 The <command>transfer-format</command> option is used
7332 on the master server to determine which format it sends.
7333 <command>one-answer</command> uses one DNS message per
7334 resource record transferred.
7335 <command>many-answers</command> packs as many resource
7336 records as possible into a message.
7337 <command>many-answers</command> is more efficient, but is
7338 only supported by relatively new slave servers,
7339 such as <acronym>BIND</acronym> 9, <acronym>BIND</acronym>
7340 8.x and <acronym>BIND</acronym> 4.9.5 onwards.
7341 The <command>many-answers</command> format is also supported by
7342 recent Microsoft Windows nameservers.
7343 The default is <command>many-answers</command>.
7344 <command>transfer-format</command> may be overridden on a
7345 per-server basis by using the <command>server</command>
7353 <term><command>transfers-in</command></term>
7356 The maximum number of inbound zone transfers
7357 that can be running concurrently. The default value is <literal>10</literal>.
7358 Increasing <command>transfers-in</command> may
7359 speed up the convergence
7360 of slave zones, but it also may increase the load on the
7367 <term><command>transfers-out</command></term>
7370 The maximum number of outbound zone transfers
7371 that can be running concurrently. Zone transfer requests in
7373 of the limit will be refused. The default value is <literal>10</literal>.
7379 <term><command>transfers-per-ns</command></term>
7382 The maximum number of inbound zone transfers
7383 that can be concurrently transferring from a given remote
7385 The default value is <literal>2</literal>.
7386 Increasing <command>transfers-per-ns</command>
7388 speed up the convergence of slave zones, but it also may
7390 the load on the remote name server. <command>transfers-per-ns</command> may
7391 be overridden on a per-server basis by using the <command>transfers</command> phrase
7392 of the <command>server</command> statement.
7398 <term><command>transfer-source</command></term>
7400 <para><command>transfer-source</command>
7401 determines which local address will be bound to IPv4
7402 TCP connections used to fetch zones transferred
7403 inbound by the server. It also determines the
7404 source IPv4 address, and optionally the UDP port,
7405 used for the refresh queries and forwarded dynamic
7406 updates. If not set, it defaults to a system
7407 controlled value which will usually be the address
7408 of the interface "closest to" the remote end. This
7409 address must appear in the remote end's
7410 <command>allow-transfer</command> option for the
7411 zone being transferred, if one is specified. This
7413 <command>transfer-source</command> for all zones,
7414 but can be overridden on a per-view or per-zone
7415 basis by including a
7416 <command>transfer-source</command> statement within
7417 the <command>view</command> or
7418 <command>zone</command> block in the configuration
7423 Solaris 2.5.1 and earlier does not support setting the
7424 source address for TCP sockets.
7431 <term><command>transfer-source-v6</command></term>
7434 The same as <command>transfer-source</command>,
7435 except zone transfers are performed using IPv6.
7441 <term><command>alt-transfer-source</command></term>
7444 An alternate transfer source if the one listed in
7445 <command>transfer-source</command> fails and
7446 <command>use-alt-transfer-source</command> is
7450 If you do not wish the alternate transfer source
7451 to be used, you should set
7452 <command>use-alt-transfer-source</command>
7453 appropriately and you should not depend upon
7454 getting an answer back to the first refresh
7461 <term><command>alt-transfer-source-v6</command></term>
7464 An alternate transfer source if the one listed in
7465 <command>transfer-source-v6</command> fails and
7466 <command>use-alt-transfer-source</command> is
7473 <term><command>use-alt-transfer-source</command></term>
7476 Use the alternate transfer sources or not. If views are
7477 specified this defaults to <command>no</command>
7478 otherwise it defaults to
7479 <command>yes</command> (for BIND 8
7486 <term><command>notify-source</command></term>
7488 <para><command>notify-source</command>
7489 determines which local source address, and
7490 optionally UDP port, will be used to send NOTIFY
7491 messages. This address must appear in the slave
7492 server's <command>masters</command> zone clause or
7493 in an <command>allow-notify</command> clause. This
7494 statement sets the <command>notify-source</command>
7495 for all zones, but can be overridden on a per-zone or
7496 per-view basis by including a
7497 <command>notify-source</command> statement within
7498 the <command>zone</command> or
7499 <command>view</command> block in the configuration
7504 Solaris 2.5.1 and earlier does not support setting the
7505 source address for TCP sockets.
7512 <term><command>notify-source-v6</command></term>
7515 Like <command>notify-source</command>,
7516 but applies to notify messages sent to IPv6 addresses.
7526 <title>UDP Port Lists</title>
7528 <command>use-v4-udp-ports</command>,
7529 <command>avoid-v4-udp-ports</command>,
7530 <command>use-v6-udp-ports</command>, and
7531 <command>avoid-v6-udp-ports</command>
7532 specify a list of IPv4 and IPv6 UDP ports that will be
7533 used or not used as source ports for UDP messages.
7534 See <xref linkend="query_address"/> about how the
7535 available ports are determined.
7536 For example, with the following configuration
7540 use-v6-udp-ports { range 32768 65535; };
7541 avoid-v6-udp-ports { 40000; range 50000 60000; };
7545 UDP ports of IPv6 messages sent
7546 from <command>named</command> will be in one
7547 of the following ranges: 32768 to 39999, 40001 to 49999,
7552 <command>avoid-v4-udp-ports</command> and
7553 <command>avoid-v6-udp-ports</command> can be used
7554 to prevent <command>named</command> from choosing as its random source port a
7555 port that is blocked by your firewall or a port that is
7556 used by other applications;
7557 if a query went out with a source port blocked by a
7559 answer would not get by the firewall and the name server would
7560 have to query again.
7561 Note: the desired range can also be represented only with
7562 <command>use-v4-udp-ports</command> and
7563 <command>use-v6-udp-ports</command>, and the
7564 <command>avoid-</command> options are redundant in that
7565 sense; they are provided for backward compatibility and
7566 to possibly simplify the port specification.
7571 <title>Operating System Resource Limits</title>
7574 The server's usage of many system resources can be limited.
7575 Scaled values are allowed when specifying resource limits. For
7576 example, <command>1G</command> can be used instead of
7577 <command>1073741824</command> to specify a limit of
7579 gigabyte. <command>unlimited</command> requests
7580 unlimited use, or the
7581 maximum available amount. <command>default</command>
7583 that was in force when the server was started. See the description
7584 of <command>size_spec</command> in <xref linkend="configuration_file_elements"/>.
7588 The following options set operating system resource limits for
7589 the name server process. Some operating systems don't support
7591 any of the limits. On such systems, a warning will be issued if
7593 unsupported limit is used.
7599 <term><command>coresize</command></term>
7602 The maximum size of a core dump. The default
7603 is <literal>default</literal>.
7609 <term><command>datasize</command></term>
7612 The maximum amount of data memory the server
7613 may use. The default is <literal>default</literal>.
7614 This is a hard limit on server memory usage.
7615 If the server attempts to allocate memory in excess of this
7616 limit, the allocation will fail, which may in turn leave
7617 the server unable to perform DNS service. Therefore,
7618 this option is rarely useful as a way of limiting the
7619 amount of memory used by the server, but it can be used
7620 to raise an operating system data size limit that is
7621 too small by default. If you wish to limit the amount
7622 of memory used by the server, use the
7623 <command>max-cache-size</command> and
7624 <command>recursive-clients</command>
7631 <term><command>files</command></term>
7634 The maximum number of files the server
7635 may have open concurrently. The default is <literal>unlimited</literal>.
7641 <term><command>stacksize</command></term>
7644 The maximum amount of stack memory the server
7645 may use. The default is <literal>default</literal>.
7654 <sect3 id="server_resource_limits">
7655 <title>Server Resource Limits</title>
7658 The following options set limits on the server's
7659 resource consumption that are enforced internally by the
7660 server rather than the operating system.
7666 <term><command>max-ixfr-log-size</command></term>
7669 This option is obsolete; it is accepted
7670 and ignored for BIND 8 compatibility. The option
7671 <command>max-journal-size</command> performs a
7672 similar function in BIND 9.
7678 <term><command>max-journal-size</command></term>
7681 Sets a maximum size for each journal file
7682 (see <xref linkend="journal"/>). When the journal file
7684 the specified size, some of the oldest transactions in the
7686 will be automatically removed. The default is
7687 <literal>unlimited</literal>.
7688 This may also be set on a per-zone basis.
7694 <term><command>host-statistics-max</command></term>
7697 In BIND 8, specifies the maximum number of host statistics
7699 Not implemented in BIND 9.
7705 <term><command>recursive-clients</command></term>
7708 The maximum number of simultaneous recursive lookups
7709 the server will perform on behalf of clients. The default
7711 <literal>1000</literal>. Because each recursing
7713 bit of memory, on the order of 20 kilobytes, the value of
7715 <command>recursive-clients</command> option may
7716 have to be decreased
7717 on hosts with limited memory.
7723 <term><command>tcp-clients</command></term>
7726 The maximum number of simultaneous client TCP
7727 connections that the server will accept.
7728 The default is <literal>100</literal>.
7734 <term><command>reserved-sockets</command></term>
7737 The number of file descriptors reserved for TCP, stdio,
7738 etc. This needs to be big enough to cover the number of
7739 interfaces <command>named</command> listens on, <command>tcp-clients</command> as well as
7740 to provide room for outgoing TCP queries and incoming zone
7741 transfers. The default is <literal>512</literal>.
7742 The minimum value is <literal>128</literal> and the
7743 maximum value is <literal>128</literal> less than
7744 maxsockets (-S). This option may be removed in the future.
7747 This option has little effect on Windows.
7753 <term><command>max-cache-size</command></term>
7756 The maximum amount of memory to use for the
7757 server's cache, in bytes.
7758 When the amount of data in the cache
7759 reaches this limit, the server will cause records to expire
7760 prematurely based on an LRU based strategy so that
7761 the limit is not exceeded.
7762 A value of 0 is special, meaning that
7763 records are purged from the cache only when their
7765 Another special keyword <userinput>unlimited</userinput>
7766 means the maximum value of 32-bit unsigned integers
7767 (0xffffffff), which may not have the same effect as
7768 0 on machines that support more than 32 bits of
7770 Any positive values less than 2MB will be ignored reset
7772 In a server with multiple views, the limit applies
7773 separately to the cache of each view.
7780 <term><command>tcp-listen-queue</command></term>
7783 The listen queue depth. The default and minimum is 10.
7784 If the kernel supports the accept filter "dataready" this
7786 many TCP connections that will be queued in kernel space
7788 some data before being passed to accept. Nonzero values
7789 less than 10 will be silently raised. A value of 0 may also
7790 be used; on most platforms this sets the listen queue
7791 length to a system-defined default value.
7801 <title>Periodic Task Intervals</title>
7806 <term><command>cleaning-interval</command></term>
7809 This interval is effectively obsolete. Previously,
7810 the server would remove expired resource records
7811 from the cache every <command>cleaning-interval</command> minutes.
7812 <acronym>BIND</acronym> 9 now manages cache
7813 memory in a more sophisticated manner and does not
7814 rely on the periodic cleaning any more.
7815 Specifying this option therefore has no effect on
7816 the server's behavior.
7822 <term><command>heartbeat-interval</command></term>
7825 The server will perform zone maintenance tasks
7826 for all zones marked as <command>dialup</command> whenever this
7827 interval expires. The default is 60 minutes. Reasonable
7829 to 1 day (1440 minutes). The maximum value is 28 days
7831 If set to 0, no zone maintenance for these zones will occur.
7837 <term><command>interface-interval</command></term>
7840 The server will scan the network interface list
7841 every <command>interface-interval</command>
7842 minutes. The default
7843 is 60 minutes. The maximum value is 28 days (40320 minutes).
7844 If set to 0, interface scanning will only occur when
7845 the configuration file is loaded. After the scan, the
7847 begin listening for queries on any newly discovered
7848 interfaces (provided they are allowed by the
7849 <command>listen-on</command> configuration), and
7851 stop listening on interfaces that have gone away.
7857 <term><command>statistics-interval</command></term>
7860 Name server statistics will be logged
7861 every <command>statistics-interval</command>
7862 minutes. The default is
7863 60. The maximum value is 28 days (40320 minutes).
7864 If set to 0, no statistics will be logged.
7867 Not yet implemented in
7868 <acronym>BIND</acronym> 9.
7878 <sect3 id="topology">
7879 <title>Topology</title>
7882 All other things being equal, when the server chooses a name
7884 to query from a list of name servers, it prefers the one that is
7885 topologically closest to itself. The <command>topology</command> statement
7886 takes an <command>address_match_list</command> and
7888 in a special way. Each top-level list element is assigned a
7890 Non-negated elements get a distance based on their position in the
7891 list, where the closer the match is to the start of the list, the
7892 shorter the distance is between it and the server. A negated match
7893 will be assigned the maximum distance from the server. If there
7894 is no match, the address will get a distance which is further than
7895 any non-negated list element, and closer than any negated element.
7899 <programlisting>topology {
7906 will prefer servers on network 10 the most, followed by hosts
7907 on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the
7908 exception of hosts on network 1.2.3 (netmask 255.255.255.0), which
7909 is preferred least of all.
7912 The default topology is
7915 <programlisting> topology { localhost; localnets; };
7920 The <command>topology</command> option
7921 is not implemented in <acronym>BIND</acronym> 9.
7926 <sect3 id="the_sortlist_statement">
7928 <title>The <command>sortlist</command> Statement</title>
7931 The response to a DNS query may consist of multiple resource
7932 records (RRs) forming a resource records set (RRset).
7933 The name server will normally return the
7934 RRs within the RRset in an indeterminate order
7935 (but see the <command>rrset-order</command>
7936 statement in <xref linkend="rrset_ordering"/>).
7937 The client resolver code should rearrange the RRs as appropriate,
7938 that is, using any addresses on the local net in preference to
7940 However, not all resolvers can do this or are correctly
7942 When a client is using a local server, the sorting can be performed
7943 in the server, based on the client's address. This only requires
7944 configuring the name servers, not all the clients.
7948 The <command>sortlist</command> statement (see below)
7950 an <command>address_match_list</command> and
7952 more specifically than the <command>topology</command>
7954 does (<xref linkend="topology"/>).
7955 Each top level statement in the <command>sortlist</command> must
7956 itself be an explicit <command>address_match_list</command> with
7957 one or two elements. The first element (which may be an IP
7959 an IP prefix, an ACL name or a nested <command>address_match_list</command>)
7960 of each top level list is checked against the source address of
7961 the query until a match is found.
7964 Once the source address of the query has been matched, if
7965 the top level statement contains only one element, the actual
7967 element that matched the source address is used to select the
7969 in the response to move to the beginning of the response. If the
7970 statement is a list of two elements, then the second element is
7971 treated the same as the <command>address_match_list</command> in
7972 a <command>topology</command> statement. Each top
7974 is assigned a distance and the address in the response with the
7976 distance is moved to the beginning of the response.
7979 In the following example, any queries received from any of
7980 the addresses of the host itself will get responses preferring
7982 on any of the locally connected networks. Next most preferred are
7984 on the 192.168.1/24 network, and after that either the
7987 192.168.3/24 network with no preference shown between these two
7988 networks. Queries received from a host on the 192.168.1/24 network
7989 will prefer other addresses on that network to the 192.168.2/24
7991 192.168.3/24 networks. Queries received from a host on the
7993 or the 192.168.5/24 network will only prefer other addresses on
7994 their directly connected networks.
7997 <programlisting>sortlist {
7998 // IF the local host
7999 // THEN first fit on the following nets
8003 { 192.168.2/24; 192.168.3/24; }; }; };
8004 // IF on class C 192.168.1 THEN use .1, or .2 or .3
8007 { 192.168.2/24; 192.168.3/24; }; }; };
8008 // IF on class C 192.168.2 THEN use .2, or .1 or .3
8011 { 192.168.1/24; 192.168.3/24; }; }; };
8012 // IF on class C 192.168.3 THEN use .3, or .1 or .2
8015 { 192.168.1/24; 192.168.2/24; }; }; };
8016 // IF .4 or .5 THEN prefer that net
8017 { { 192.168.4/24; 192.168.5/24; };
8022 The following example will give reasonable behavior for the
8023 local host and hosts on directly connected networks. It is similar
8024 to the behavior of the address sort in <acronym>BIND</acronym> 4.9.x. Responses sent
8025 to queries from the local host will favor any of the directly
8027 networks. Responses sent to queries from any other hosts on a
8029 connected network will prefer addresses on that same network.
8031 to other queries will not be sorted.
8034 <programlisting>sortlist {
8035 { localhost; localnets; };
8041 <sect3 id="rrset_ordering">
8042 <title id="rrset_ordering_title">RRset Ordering</title>
8044 When multiple records are returned in an answer it may be
8045 useful to configure the order of the records placed into the
8047 The <command>rrset-order</command> statement permits
8049 of the ordering of the records in a multiple record response.
8050 See also the <command>sortlist</command> statement,
8051 <xref linkend="the_sortlist_statement"/>.
8055 An <command>order_spec</command> is defined as
8059 <optional>class <replaceable>class_name</replaceable></optional>
8060 <optional>type <replaceable>type_name</replaceable></optional>
8061 <optional>name <replaceable>"domain_name"</replaceable></optional>
8062 order <replaceable>ordering</replaceable>
8065 If no class is specified, the default is <command>ANY</command>.
8066 If no type is specified, the default is <command>ANY</command>.
8067 If no name is specified, the default is "<command>*</command>" (asterisk).
8070 The legal values for <command>ordering</command> are:
8072 <informaltable colsep="0" rowsep="0">
8073 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
8074 <colspec colname="1" colnum="1" colsep="0" colwidth="0.750in"/>
8075 <colspec colname="2" colnum="2" colsep="0" colwidth="3.750in"/>
8079 <para><command>fixed</command></para>
8083 Records are returned in the order they
8084 are defined in the zone file.
8090 <para><command>random</command></para>
8094 Records are returned in some random order.
8100 <para><command>cyclic</command></para>
8104 Records are returned in a cyclic round-robin order.
8107 If <acronym>BIND</acronym> is configured with the
8108 "--enable-fixed-rrset" option at compile time, then
8109 the initial ordering of the RRset will match the
8110 one specified in the zone file.
8121 <programlisting>rrset-order {
8122 class IN type A name "host.example.com" order random;
8128 will cause any responses for type A records in class IN that
8129 have "<literal>host.example.com</literal>" as a
8130 suffix, to always be returned
8131 in random order. All other records are returned in cyclic order.
8134 If multiple <command>rrset-order</command> statements
8136 they are not combined — the last one applies.
8141 In this release of <acronym>BIND</acronym> 9, the
8142 <command>rrset-order</command> statement does not support
8143 "fixed" ordering by default. Fixed ordering can be enabled
8144 at compile time by specifying "--enable-fixed-rrset" on
8145 the "configure" command line.
8151 <title>Tuning</title>
8156 <term><command>lame-ttl</command></term>
8159 Sets the number of seconds to cache a
8160 lame server indication. 0 disables caching. (This is
8161 <emphasis role="bold">NOT</emphasis> recommended.)
8162 The default is <literal>600</literal> (10 minutes) and the
8164 <literal>1800</literal> (30 minutes).
8168 Lame-ttl also controls the amount of time DNSSEC
8169 validation failures are cached. There is a minimum
8170 of 30 seconds applied to bad cache entries if the
8171 lame-ttl is set to less than 30 seconds.
8178 <term><command>max-ncache-ttl</command></term>
8181 To reduce network traffic and increase performance,
8182 the server stores negative answers. <command>max-ncache-ttl</command> is
8183 used to set a maximum retention time for these answers in
8185 in seconds. The default
8186 <command>max-ncache-ttl</command> is <literal>10800</literal> seconds (3 hours).
8187 <command>max-ncache-ttl</command> cannot exceed
8189 be silently truncated to 7 days if set to a greater value.
8195 <term><command>max-cache-ttl</command></term>
8198 Sets the maximum time for which the server will
8199 cache ordinary (positive) answers. The default is
8201 A value of zero may cause all queries to return
8202 SERVFAIL, because of lost caches of intermediate
8203 RRsets (such as NS and glue AAAA/A records) in the
8210 <term><command>min-roots</command></term>
8213 The minimum number of root servers that
8214 is required for a request for the root servers to be
8215 accepted. The default
8216 is <userinput>2</userinput>.
8220 Not implemented in <acronym>BIND</acronym> 9.
8227 <term><command>sig-validity-interval</command></term>
8230 Specifies the number of days into the future when
8231 DNSSEC signatures automatically generated as a
8232 result of dynamic updates (<xref
8233 linkend="dynamic_update"/>) will expire. There
8234 is an optional second field which specifies how
8235 long before expiry that the signatures will be
8236 regenerated. If not specified, the signatures will
8237 be regenerated at 1/4 of base interval. The second
8238 field is specified in days if the base interval is
8239 greater than 7 days otherwise it is specified in hours.
8240 The default base interval is <literal>30</literal> days
8241 giving a re-signing interval of 7 1/2 days. The maximum
8242 values are 10 years (3660 days).
8245 The signature inception time is unconditionally
8246 set to one hour before the current time to allow
8247 for a limited amount of clock skew.
8250 The <command>sig-validity-interval</command>
8251 should be, at least, several multiples of the SOA
8252 expire interval to allow for reasonable interaction
8253 between the various timer and expiry dates.
8259 <term><command>sig-signing-nodes</command></term>
8262 Specify the maximum number of nodes to be
8263 examined in each quantum when signing a zone with
8264 a new DNSKEY. The default is
8265 <literal>100</literal>.
8271 <term><command>sig-signing-signatures</command></term>
8274 Specify a threshold number of signatures that
8275 will terminate processing a quantum when signing
8276 a zone with a new DNSKEY. The default is
8277 <literal>10</literal>.
8283 <term><command>sig-signing-type</command></term>
8286 Specify a private RDATA type to be used when generating
8287 key signing records. The default is
8288 <literal>65534</literal>.
8291 It is expected that this parameter may be removed
8292 in a future version once there is a standard type.
8298 <term><command>min-refresh-time</command></term>
8299 <term><command>max-refresh-time</command></term>
8300 <term><command>min-retry-time</command></term>
8301 <term><command>max-retry-time</command></term>
8304 These options control the server's behavior on refreshing a
8306 (querying for SOA changes) or retrying failed transfers.
8307 Usually the SOA values for the zone are used, but these
8309 are set by the master, giving slave server administrators
8311 control over their contents.
8314 These options allow the administrator to set a minimum and
8316 refresh and retry time either per-zone, per-view, or
8318 These options are valid for slave and stub zones,
8319 and clamp the SOA refresh and retry times to the specified
8323 The following defaults apply.
8324 <command>min-refresh-time</command> 300 seconds,
8325 <command>max-refresh-time</command> 2419200 seconds
8326 (4 weeks), <command>min-retry-time</command> 500 seconds,
8327 and <command>max-retry-time</command> 1209600 seconds
8334 <term><command>edns-udp-size</command></term>
8337 Sets the advertised EDNS UDP buffer size in bytes
8338 to control the size of packets received.
8339 Valid values are 512 to 4096 (values outside this range
8340 will be silently adjusted). The default value
8341 is 4096. The usual reason for setting
8342 <command>edns-udp-size</command> to a non-default
8343 value is to get UDP answers to pass through broken
8344 firewalls that block fragmented packets and/or
8345 block UDP packets that are greater than 512 bytes.
8348 <command>named</command> will fallback to using 512 bytes
8349 if it get a series of timeout at the initial value. 512
8350 bytes is not being offered to encourage sites to fix their
8351 firewalls. Small EDNS UDP sizes will result in the
8352 excessive use of TCP.
8358 <term><command>max-udp-size</command></term>
8361 Sets the maximum EDNS UDP message size
8362 <command>named</command> will send in bytes.
8363 Valid values are 512 to 4096 (values outside this
8364 range will be silently adjusted). The default
8365 value is 4096. The usual reason for setting
8366 <command>max-udp-size</command> to a non-default
8367 value is to get UDP answers to pass through broken
8368 firewalls that block fragmented packets and/or
8369 block UDP packets that are greater than 512 bytes.
8370 This is independent of the advertised receive
8371 buffer (<command>edns-udp-size</command>).
8374 Setting this to a low value will encourage additional
8375 TCP traffic to the nameserver.
8381 <term><command>masterfile-format</command></term>
8384 the file format of zone files (see
8385 <xref linkend="zonefile_format"/>).
8386 The default value is <constant>text</constant>, which is the
8387 standard textual representation. Files in other formats
8388 than <constant>text</constant> are typically expected
8389 to be generated by the <command>named-compilezone</command> tool.
8390 Note that when a zone file in a different format than
8391 <constant>text</constant> is loaded, <command>named</command>
8392 may omit some of the checks which would be performed for a
8393 file in the <constant>text</constant> format. In particular,
8394 <command>check-names</command> checks do not apply
8395 for the <constant>raw</constant> format. This means
8396 a zone file in the <constant>raw</constant> format
8397 must be generated with the same check level as that
8398 specified in the <command>named</command> configuration
8399 file. This statement sets the
8400 <command>masterfile-format</command> for all zones,
8401 but can be overridden on a per-zone or per-view basis
8402 by including a <command>masterfile-format</command>
8403 statement within the <command>zone</command> or
8404 <command>view</command> block in the configuration
8410 <varlistentry id="clients-per-query">
8411 <term><command>clients-per-query</command></term>
8412 <term><command>max-clients-per-query</command></term>
8415 initial value (minimum) and maximum number of recursive
8416 simultaneous clients for any given query
8417 (<qname,qtype,qclass>) that the server will accept
8418 before dropping additional clients. <command>named</command> will attempt to
8419 self tune this value and changes will be logged. The
8420 default values are 10 and 100.
8423 This value should reflect how many queries come in for
8424 a given name in the time it takes to resolve that name.
8425 If the number of queries exceed this value, <command>named</command> will
8426 assume that it is dealing with a non-responsive zone
8427 and will drop additional queries. If it gets a response
8428 after dropping queries, it will raise the estimate. The
8429 estimate will then be lowered in 20 minutes if it has
8433 If <command>clients-per-query</command> is set to zero,
8434 then there is no limit on the number of clients per query
8435 and no queries will be dropped.
8438 If <command>max-clients-per-query</command> is set to zero,
8439 then there is no upper bound other than imposed by
8440 <command>recursive-clients</command>.
8446 <term><command>notify-delay</command></term>
8449 The delay, in seconds, between sending sets of notify
8450 messages for a zone. The default is five (5) seconds.
8453 The overall rate that NOTIFY messages are sent for all
8454 zones is controlled by <command>serial-query-rate</command>.
8462 <sect3 id="builtin">
8463 <title>Built-in server information zones</title>
8466 The server provides some helpful diagnostic information
8467 through a number of built-in zones under the
8468 pseudo-top-level-domain <literal>bind</literal> in the
8469 <command>CHAOS</command> class. These zones are part
8471 built-in view (see <xref linkend="view_statement_grammar"/>) of
8473 <command>CHAOS</command> which is separate from the
8474 default view of class <command>IN</command>. Most global
8475 configuration options (<command>allow-query</command>,
8476 etc) will apply to this view, but some are locally
8477 overridden: <command>notify</command>,
8478 <command>recursion</command> and
8479 <command>allow-new-zones</command> are
8480 always set to <userinput>no</userinput>.
8483 If you need to disable these zones, use the options
8484 below, or hide the built-in <command>CHAOS</command>
8486 defining an explicit view of class <command>CHAOS</command>
8487 that matches all clients.
8493 <term><command>version</command></term>
8496 The version the server should report
8497 via a query of the name <literal>version.bind</literal>
8498 with type <command>TXT</command>, class <command>CHAOS</command>.
8499 The default is the real version number of this server.
8500 Specifying <command>version none</command>
8501 disables processing of the queries.
8507 <term><command>hostname</command></term>
8510 The hostname the server should report via a query of
8511 the name <filename>hostname.bind</filename>
8512 with type <command>TXT</command>, class <command>CHAOS</command>.
8513 This defaults to the hostname of the machine hosting the
8515 found by the gethostname() function. The primary purpose of such queries
8517 identify which of a group of anycast servers is actually
8518 answering your queries. Specifying <command>hostname none;</command>
8519 disables processing of the queries.
8525 <term><command>server-id</command></term>
8528 The ID the server should report when receiving a Name
8529 Server Identifier (NSID) query, or a query of the name
8530 <filename>ID.SERVER</filename> with type
8531 <command>TXT</command>, class <command>CHAOS</command>.
8532 The primary purpose of such queries is to
8533 identify which of a group of anycast servers is actually
8534 answering your queries. Specifying <command>server-id none;</command>
8535 disables processing of the queries.
8536 Specifying <command>server-id hostname;</command> will cause <command>named</command> to
8537 use the hostname as found by the gethostname() function.
8538 The default <command>server-id</command> is <command>none</command>.
8548 <title>Built-in Empty Zones</title>
8550 Named has some built-in empty zones (SOA and NS records only).
8551 These are for zones that should normally be answered locally
8552 and which queries should not be sent to the Internet's root
8553 servers. The official servers which cover these namespaces
8554 return NXDOMAIN responses to these queries. In particular,
8555 these cover the reverse namespaces for addresses from
8556 RFC 1918, RFC 4193, RFC 5737 and RFC 6598. They also include the
8557 reverse namespace for IPv6 local address (locally assigned),
8558 IPv6 link local addresses, the IPv6 loopback address and the
8559 IPv6 unknown address.
8562 Named will attempt to determine if a built-in zone already exists
8563 or is active (covered by a forward-only forwarding declaration)
8564 and will not create an empty zone in that case.
8567 The current list of empty zones is:
8569 <listitem>10.IN-ADDR.ARPA</listitem>
8570 <listitem>16.172.IN-ADDR.ARPA</listitem>
8571 <listitem>17.172.IN-ADDR.ARPA</listitem>
8572 <listitem>18.172.IN-ADDR.ARPA</listitem>
8573 <listitem>19.172.IN-ADDR.ARPA</listitem>
8574 <listitem>20.172.IN-ADDR.ARPA</listitem>
8575 <listitem>21.172.IN-ADDR.ARPA</listitem>
8576 <listitem>22.172.IN-ADDR.ARPA</listitem>
8577 <listitem>23.172.IN-ADDR.ARPA</listitem>
8578 <listitem>24.172.IN-ADDR.ARPA</listitem>
8579 <listitem>25.172.IN-ADDR.ARPA</listitem>
8580 <listitem>26.172.IN-ADDR.ARPA</listitem>
8581 <listitem>27.172.IN-ADDR.ARPA</listitem>
8582 <listitem>28.172.IN-ADDR.ARPA</listitem>
8583 <listitem>29.172.IN-ADDR.ARPA</listitem>
8584 <listitem>30.172.IN-ADDR.ARPA</listitem>
8585 <listitem>31.172.IN-ADDR.ARPA</listitem>
8586 <listitem>168.192.IN-ADDR.ARPA</listitem>
8587 <listitem>64.100.IN-ADDR.ARPA</listitem>
8588 <listitem>65.100.IN-ADDR.ARPA</listitem>
8589 <listitem>66.100.IN-ADDR.ARPA</listitem>
8590 <listitem>67.100.IN-ADDR.ARPA</listitem>
8591 <listitem>68.100.IN-ADDR.ARPA</listitem>
8592 <listitem>69.100.IN-ADDR.ARPA</listitem>
8593 <listitem>70.100.IN-ADDR.ARPA</listitem>
8594 <listitem>71.100.IN-ADDR.ARPA</listitem>
8595 <listitem>72.100.IN-ADDR.ARPA</listitem>
8596 <listitem>73.100.IN-ADDR.ARPA</listitem>
8597 <listitem>74.100.IN-ADDR.ARPA</listitem>
8598 <listitem>75.100.IN-ADDR.ARPA</listitem>
8599 <listitem>76.100.IN-ADDR.ARPA</listitem>
8600 <listitem>77.100.IN-ADDR.ARPA</listitem>
8601 <listitem>78.100.IN-ADDR.ARPA</listitem>
8602 <listitem>79.100.IN-ADDR.ARPA</listitem>
8603 <listitem>80.100.IN-ADDR.ARPA</listitem>
8604 <listitem>81.100.IN-ADDR.ARPA</listitem>
8605 <listitem>82.100.IN-ADDR.ARPA</listitem>
8606 <listitem>83.100.IN-ADDR.ARPA</listitem>
8607 <listitem>84.100.IN-ADDR.ARPA</listitem>
8608 <listitem>85.100.IN-ADDR.ARPA</listitem>
8609 <listitem>86.100.IN-ADDR.ARPA</listitem>
8610 <listitem>87.100.IN-ADDR.ARPA</listitem>
8611 <listitem>88.100.IN-ADDR.ARPA</listitem>
8612 <listitem>89.100.IN-ADDR.ARPA</listitem>
8613 <listitem>90.100.IN-ADDR.ARPA</listitem>
8614 <listitem>91.100.IN-ADDR.ARPA</listitem>
8615 <listitem>92.100.IN-ADDR.ARPA</listitem>
8616 <listitem>93.100.IN-ADDR.ARPA</listitem>
8617 <listitem>94.100.IN-ADDR.ARPA</listitem>
8618 <listitem>95.100.IN-ADDR.ARPA</listitem>
8619 <listitem>96.100.IN-ADDR.ARPA</listitem>
8620 <listitem>97.100.IN-ADDR.ARPA</listitem>
8621 <listitem>98.100.IN-ADDR.ARPA</listitem>
8622 <listitem>99.100.IN-ADDR.ARPA</listitem>
8623 <listitem>100.100.IN-ADDR.ARPA</listitem>
8624 <listitem>101.100.IN-ADDR.ARPA</listitem>
8625 <listitem>102.100.IN-ADDR.ARPA</listitem>
8626 <listitem>103.100.IN-ADDR.ARPA</listitem>
8627 <listitem>104.100.IN-ADDR.ARPA</listitem>
8628 <listitem>105.100.IN-ADDR.ARPA</listitem>
8629 <listitem>106.100.IN-ADDR.ARPA</listitem>
8630 <listitem>107.100.IN-ADDR.ARPA</listitem>
8631 <listitem>108.100.IN-ADDR.ARPA</listitem>
8632 <listitem>109.100.IN-ADDR.ARPA</listitem>
8633 <listitem>110.100.IN-ADDR.ARPA</listitem>
8634 <listitem>111.100.IN-ADDR.ARPA</listitem>
8635 <listitem>112.100.IN-ADDR.ARPA</listitem>
8636 <listitem>113.100.IN-ADDR.ARPA</listitem>
8637 <listitem>114.100.IN-ADDR.ARPA</listitem>
8638 <listitem>115.100.IN-ADDR.ARPA</listitem>
8639 <listitem>116.100.IN-ADDR.ARPA</listitem>
8640 <listitem>117.100.IN-ADDR.ARPA</listitem>
8641 <listitem>118.100.IN-ADDR.ARPA</listitem>
8642 <listitem>119.100.IN-ADDR.ARPA</listitem>
8643 <listitem>120.100.IN-ADDR.ARPA</listitem>
8644 <listitem>121.100.IN-ADDR.ARPA</listitem>
8645 <listitem>122.100.IN-ADDR.ARPA</listitem>
8646 <listitem>123.100.IN-ADDR.ARPA</listitem>
8647 <listitem>124.100.IN-ADDR.ARPA</listitem>
8648 <listitem>125.100.IN-ADDR.ARPA</listitem>
8649 <listitem>126.100.IN-ADDR.ARPA</listitem>
8650 <listitem>127.100.IN-ADDR.ARPA</listitem>
8651 <listitem>0.IN-ADDR.ARPA</listitem>
8652 <listitem>127.IN-ADDR.ARPA</listitem>
8653 <listitem>254.169.IN-ADDR.ARPA</listitem>
8654 <listitem>2.0.192.IN-ADDR.ARPA</listitem>
8655 <listitem>100.51.198.IN-ADDR.ARPA</listitem>
8656 <listitem>113.0.203.IN-ADDR.ARPA</listitem>
8657 <listitem>255.255.255.255.IN-ADDR.ARPA</listitem>
8658 <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>
8659 <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>
8660 <listitem>8.B.D.0.1.0.0.2.IP6.ARPA</listitem>
8661 <listitem>D.F.IP6.ARPA</listitem>
8662 <listitem>8.E.F.IP6.ARPA</listitem>
8663 <listitem>9.E.F.IP6.ARPA</listitem>
8664 <listitem>A.E.F.IP6.ARPA</listitem>
8665 <listitem>B.E.F.IP6.ARPA</listitem>
8669 Empty zones are settable at the view level and only apply to
8670 views of class IN. Disabled empty zones are only inherited
8671 from options if there are no disabled empty zones specified
8672 at the view level. To override the options list of disabled
8673 zones, you can disable the root zone at the view level, for example:
8675 disable-empty-zone ".";
8679 If you are using the address ranges covered here, you should
8680 already have reverse zones covering the addresses you use.
8681 In practice this appears to not be the case with many queries
8682 being made to the infrastructure servers for names in these
8683 spaces. So many in fact that sacrificial servers were needed
8684 to be deployed to channel the query load away from the
8685 infrastructure servers.
8688 The real parent servers for these zones should disable all
8689 empty zone under the parent zone they serve. For the real
8690 root servers, this is all built-in empty zones. This will
8691 enable them to return referrals to deeper in the tree.
8695 <term><command>empty-server</command></term>
8698 Specify what server name will appear in the returned
8699 SOA record for empty zones. If none is specified, then
8700 the zone's name will be used.
8706 <term><command>empty-contact</command></term>
8709 Specify what contact name will appear in the returned
8710 SOA record for empty zones. If none is specified, then
8717 <term><command>empty-zones-enable</command></term>
8720 Enable or disable all empty zones. By default, they
8727 <term><command>disable-empty-zone</command></term>
8730 Disable individual empty zones. By default, none are
8731 disabled. This option can be specified multiple times.
8739 <title>Additional Section Caching</title>
8742 The additional section cache, also called <command>acache</command>,
8743 is an internal cache to improve the response performance of BIND 9.
8744 When additional section caching is enabled, BIND 9 will
8745 cache an internal short-cut to the additional section content for
8747 Note that <command>acache</command> is an internal caching
8748 mechanism of BIND 9, and is not related to the DNS caching
8753 Additional section caching does not change the
8754 response content (except the RRsets ordering of the additional
8755 section, see below), but can improve the response performance
8757 It is particularly effective when BIND 9 acts as an authoritative
8758 server for a zone that has many delegations with many glue RRs.
8762 In order to obtain the maximum performance improvement
8763 from additional section caching, setting
8764 <command>additional-from-cache</command>
8765 to <command>no</command> is recommended, since the current
8766 implementation of <command>acache</command>
8767 does not short-cut of additional section information from the
8772 One obvious disadvantage of <command>acache</command> is
8773 that it requires much more
8774 memory for the internal cached data.
8775 Thus, if the response performance does not matter and memory
8776 consumption is much more critical, the
8777 <command>acache</command> mechanism can be
8778 disabled by setting <command>acache-enable</command> to
8779 <command>no</command>.
8780 It is also possible to specify the upper limit of memory
8782 for acache by using <command>max-acache-size</command>.
8786 Additional section caching also has a minor effect on the
8787 RRset ordering in the additional section.
8788 Without <command>acache</command>,
8789 <command>cyclic</command> order is effective for the additional
8790 section as well as the answer and authority sections.
8791 However, additional section caching fixes the ordering when it
8792 first caches an RRset for the additional section, and the same
8793 ordering will be kept in succeeding responses, regardless of the
8794 setting of <command>rrset-order</command>.
8795 The effect of this should be minor, however, since an
8796 RRset in the additional section
8797 typically only contains a small number of RRs (and in many cases
8798 it only contains a single RR), in which case the
8799 ordering does not matter much.
8803 The following is a summary of options related to
8804 <command>acache</command>.
8810 <term><command>acache-enable</command></term>
8813 If <command>yes</command>, additional section caching is
8814 enabled. The default value is <command>no</command>.
8820 <term><command>acache-cleaning-interval</command></term>
8823 The server will remove stale cache entries, based on an LRU
8825 algorithm, every <command>acache-cleaning-interval</command> minutes.
8826 The default is 60 minutes.
8827 If set to 0, no periodic cleaning will occur.
8833 <term><command>max-acache-size</command></term>
8836 The maximum amount of memory in bytes to use for the server's acache.
8837 When the amount of data in the acache reaches this limit,
8839 will clean more aggressively so that the limit is not
8841 In a server with multiple views, the limit applies
8843 acache of each view.
8844 The default is <literal>16M</literal>.
8854 <title>Content Filtering</title>
8856 <acronym>BIND</acronym> 9 provides the ability to filter
8857 out DNS responses from external DNS servers containing
8858 certain types of data in the answer section.
8859 Specifically, it can reject address (A or AAAA) records if
8860 the corresponding IPv4 or IPv6 addresses match the given
8861 <varname>address_match_list</varname> of the
8862 <command>deny-answer-addresses</command> option.
8863 It can also reject CNAME or DNAME records if the "alias"
8864 name (i.e., the CNAME alias or the substituted query name
8865 due to DNAME) matches the
8866 given <varname>namelist</varname> of the
8867 <command>deny-answer-aliases</command> option, where
8868 "match" means the alias name is a subdomain of one of
8869 the <varname>name_list</varname> elements.
8870 If the optional <varname>namelist</varname> is specified
8871 with <command>except-from</command>, records whose query name
8872 matches the list will be accepted regardless of the filter
8874 Likewise, if the alias name is a subdomain of the
8875 corresponding zone, the <command>deny-answer-aliases</command>
8876 filter will not apply;
8877 for example, even if "example.com" is specified for
8878 <command>deny-answer-aliases</command>,
8880 <programlisting>www.example.com. CNAME xxx.example.com.</programlisting>
8883 returned by an "example.com" server will be accepted.
8887 In the <varname>address_match_list</varname> of the
8888 <command>deny-answer-addresses</command> option, only
8889 <varname>ip_addr</varname>
8890 and <varname>ip_prefix</varname>
8892 any <varname>key_id</varname> will be silently ignored.
8896 If a response message is rejected due to the filtering,
8897 the entire message is discarded without being cached, and
8898 a SERVFAIL error will be returned to the client.
8902 This filtering is intended to prevent "DNS rebinding attacks," in
8903 which an attacker, in response to a query for a domain name the
8904 attacker controls, returns an IP address within your own network or
8905 an alias name within your own domain.
8906 A naive web browser or script could then serve as an
8907 unintended proxy, allowing the attacker
8908 to get access to an internal node of your local network
8909 that couldn't be externally accessed otherwise.
8910 See the paper available at
8911 <ulink url="http://portal.acm.org/citation.cfm?id=1315245.1315298">
8912 http://portal.acm.org/citation.cfm?id=1315245.1315298
8914 for more details about the attacks.
8918 For example, if you own a domain named "example.net" and
8919 your internal network uses an IPv4 prefix 192.0.2.0/24,
8920 you might specify the following rules:
8923 <programlisting>deny-answer-addresses { 192.0.2.0/24; } except-from { "example.net"; };
8924 deny-answer-aliases { "example.net"; };
8928 If an external attacker lets a web browser in your local
8929 network look up an IPv4 address of "attacker.example.com",
8930 the attacker's DNS server would return a response like this:
8933 <programlisting>attacker.example.com. A 192.0.2.1</programlisting>
8936 in the answer section.
8937 Since the rdata of this record (the IPv4 address) matches
8938 the specified prefix 192.0.2.0/24, this response will be
8943 On the other hand, if the browser looks up a legitimate
8944 internal web server "www.example.net" and the
8945 following response is returned to
8946 the <acronym>BIND</acronym> 9 server
8949 <programlisting>www.example.net. A 192.0.2.2</programlisting>
8952 it will be accepted since the owner name "www.example.net"
8953 matches the <command>except-from</command> element,
8958 Note that this is not really an attack on the DNS per se.
8959 In fact, there is nothing wrong for an "external" name to
8960 be mapped to your "internal" IP address or domain name
8961 from the DNS point of view.
8962 It might actually be provided for a legitimate purpose,
8963 such as for debugging.
8964 As long as the mapping is provided by the correct owner,
8965 it is not possible or does not make sense to detect
8966 whether the intent of the mapping is legitimate or not
8968 The "rebinding" attack must primarily be protected at the
8969 application that uses the DNS.
8970 For a large site, however, it may be difficult to protect
8971 all possible applications at once.
8972 This filtering feature is provided only to help such an
8973 operational environment;
8974 it is generally discouraged to turn it on unless you are
8975 very sure you have no other choice and the attack is a
8976 real threat for your applications.
8980 Care should be particularly taken if you want to use this
8981 option for addresses within 127.0.0.0/8.
8982 These addresses are obviously "internal", but many
8983 applications conventionally rely on a DNS mapping from
8984 some name to such an address.
8985 Filtering out DNS records containing this address
8986 spuriously can break such applications.
8991 <title>Response Policy Zone (RPZ) Rewriting</title>
8993 <acronym>BIND</acronym> 9 includes a limited
8994 mechanism to modify DNS responses for requests
8995 analogous to email anti-spam DNS blacklists.
8996 Responses can be changed to deny the existence of domains(NXDOMAIN),
8997 deny the existence of IP addresses for domains (NODATA),
8998 or contain other IP addresses or data.
9002 Response policy zones are named in the
9003 <command>response-policy</command> option for the view or among the
9004 global options if there is no response-policy option for the view.
9005 RPZs are ordinary DNS zones containing RRsets
9006 that can be queried normally if allowed.
9007 It is usually best to restrict those queries with something like
9008 <command>allow-query { localhost; };</command>.
9012 Four policy triggers are encoded in RPZ records, QNAME, IP, NSIP,
9014 QNAME RPZ records triggered by query names of requests and targets
9015 of CNAME records resolved to generate the response.
9016 The owner name of a QNAME RPZ record is the query name relativized
9021 The second kind of RPZ trigger is an IP address in an A and AAAA
9022 record in the ANSWER section of a response.
9023 IP address triggers are encoded in records that have owner names
9024 that are subdomains of <userinput>rpz-ip</userinput> relativized
9025 to the RPZ origin name and encode an IP address or address block.
9026 IPv4 trigger addresses are represented as
9027 <userinput>prefixlength.B4.B3.B2.B1.rpz-ip</userinput>.
9028 The prefix length must be between 1 and 32.
9029 All four bytes, B4, B3, B2, and B1, must be present.
9030 B4 is the decimal value of the least significant byte of the
9031 IPv4 address as in IN-ADDR.ARPA.
9032 IPv6 addresses are encoded in a format similar to the standard
9033 IPv6 text representation,
9034 <userinput>prefixlength.W8.W7.W6.W5.W4.W3.W2.W1.rpz-ip</userinput>.
9035 Each of W8,...,W1 is a one to four digit hexadecimal number
9036 representing 16 bits of the IPv6 address as in the standard text
9037 representation of IPv6 addresses, but reversed as in IN-ADDR.ARPA.
9038 All 8 words must be present except when consecutive
9039 zero words are replaced with <userinput>.zz.</userinput>
9040 analogous to double colons (::) in standard IPv6 text encodings.
9041 The prefix length must be between 1 and 128.
9045 NSDNAME triggers match names of authoritative servers
9046 for the query name, a parent of the query name, a CNAME for
9047 query name, or a parent of a CNAME.
9048 They are encoded as subdomains of
9049 <userinput>rpz-nsdomain</userinput> relativized
9050 to the RPZ origin name.
9051 NSIP triggers match IP addresses in A and
9052 AAAA RRsets for domains that can be checked against NSDNAME
9054 NSIP triggers are encoded like IP triggers except as subdomains of
9055 <userinput>rpz-nsip</userinput>.
9056 NSDNAME and NSIP triggers are checked only for names with at
9057 least <command>min-ns-dots</command> dots.
9058 The default value of <command>min-ns-dots</command> is 1 to
9059 exclude top level domains.
9063 The query response is checked against all RPZs, so
9064 two or more policy records can be triggered by a response.
9065 Because DNS responses can be rewritten according to at most one
9066 policy record, a single record encoding an action (other than
9067 <command>DISABLED</command> actions) must be chosen.
9068 Triggers or the records that encode them are chosen in
9069 the following order:
9071 <listitem>Choose the triggered record in the zone that appears
9072 first in the response-policy option.
9074 <listitem>Prefer QNAME to IP to NSDNAME to NSIP triggers
9077 <listitem>Among NSDNAME triggers, prefer the
9078 trigger that matches the smallest name under the DNSSEC ordering.
9080 <listitem>Among IP or NSIP triggers, prefer the trigger
9081 with the longest prefix.
9083 <listitem>Among triggers with the same prefex length,
9084 prefer the IP or NSIP trigger that matches
9085 the smallest IP address.
9091 When the processing of a response is restarted to resolve
9092 DNAME or CNAME records and a policy record set has
9094 all RPZs are again consulted for the DNAME or CNAME names
9099 RPZ record sets are sets of any types of DNS record except
9100 DNAME or DNSSEC that encode actions or responses to queries.
9102 <listitem>The <command>NXDOMAIN</command> response is encoded
9103 by a CNAME whose target is the root domain (.)
9105 <listitem>A CNAME whose target is the wildcard top-level
9106 domain (*.) specifies the <command>NODATA</command> action,
9107 which rewrites the response to NODATA or ANCOUNT=1.
9109 <listitem>The <command>Local Data</command> action is
9110 represented by a set ordinary DNS records that are used
9111 to answer queries. Queries for record types not the
9112 set are answered with NODATA.
9114 A special form of local data is a CNAME whose target is a
9115 wildcard such as *.example.com.
9116 It is used as if were an ordinary CNAME after the astrisk (*)
9117 has been replaced with the query name.
9118 The purpose for this special form is query logging in the
9119 walled garden's authority DNS server.
9121 <listitem>The <command>PASSTHRU</command> policy is specified
9122 by a CNAME whose target is <command>rpz-passthru.</command>
9123 It causes the response to not be rewritten
9124 and is most often used to "poke holes" in policies for
9126 (A CNAME whose target is the variable part of its owner name
9127 is an obsolete specification of the PASSTHRU policy.)
9133 The actions specified in an RPZ can be overridden with a
9134 <command>policy</command> clause in the
9135 <command>response-policy</command> option.
9136 An organization using an RPZ provided by another organization might
9137 use this mechanism to redirect domains to its own walled garden.
9139 <listitem><command>GIVEN</command> says "do not override but
9140 perform the action specified in the zone."
9142 <listitem><command>DISABLED</command> causes policy records to do
9143 nothing but log what they might have done.
9144 The response to the DNS query will be written according to
9145 any triggered policy records that are not disabled.
9146 Disabled policy zones should appear first,
9147 because they will often not be logged
9148 if a higher precedence trigger is found first.
9150 <listitem><command>PASSTHRU</command> causes all policy records
9151 to act as if they were CNAME records with targets the variable
9152 part of their owner name. They protect the response from
9155 <listitem><command>NXDOMAIN</command> causes all RPZ records
9156 to specify NXDOMAIN policies.
9158 <listitem><command>NODATA</command> overrides with the
9161 <listitem><command>CNAME domain</command> causes all RPZ
9162 policy records to act as if they were "cname domain" records.
9168 By default, the actions encoded in an RPZ are applied
9169 only to queries that ask for recursion (RD=1).
9170 That default can be changed for a single RPZ or all RPZs in a view
9171 with a <command>recursive-only no</command> clause.
9172 This feature is useful for serving the same zone files
9173 both inside and outside an RFC 1918 cloud and using RPZ to
9174 delete answers that would otherwise contain RFC 1918 values
9175 on the externally visible name server or view.
9179 Also by default, RPZ actions are applied only to DNS requests that
9180 either do not request DNSSEC metadata (DO=0) or when no DNSSEC
9181 records are available for request name in the original zone (not
9182 the response policy zone).
9183 This default can be changed for all RPZs in a view with a
9184 <command>break-dnssec yes</command> clause.
9185 In that case, RPZ actions are applied regardless of DNSSEC.
9186 The name of the clause option reflects the fact that results
9187 rewritten by RPZ actions cannot verify.
9191 The TTL of a record modified by RPZ policies is set from the
9192 TTL of the relevant record in policy zone. It is then limited
9194 The <command>max-policy-ttl</command> clause changes that
9195 maximum from its default of 5.
9199 For example, you might use this option statement
9201 <programlisting> response-policy { zone "badlist"; };</programlisting>
9203 and this zone statement
9205 <programlisting> zone "badlist" {type master; file "master/badlist"; allow-query {none;}; };</programlisting>
9209 <programlisting>$TTL 1H
9210 @ SOA LOCALHOST. named-mgr.example.com (1 1h 15m 30d 2h)
9213 ; QNAME policy records. There are no periods (.) after the owner names.
9214 nxdomain.domain.com CNAME . ; NXDOMAIN policy
9215 nodata.domain.com CNAME *. ; NODATA policy
9216 bad.domain.com A 10.0.0.1 ; redirect to a walled garden
9219 ; do not rewrite (PASSTHRU) OK.DOMAIN.COM
9220 ok.domain.com CNAME rpz-passthru.
9222 bzone.domain.com CNAME garden.example.com.
9224 ; redirect x.bzone.domain.com to x.bzone.domain.com.garden.example.com
9225 *.bzone.domain.com CNAME *.garden.example.com.
9228 ; IP policy records that rewrite all answers for 127/8 except 127.0.0.1
9229 8.0.0.0.127.rpz-ip CNAME .
9230 32.1.0.0.127.rpz-ip CNAME rpz-passthru.
9232 ; NSDNAME and NSIP policy records
9233 ns.domain.com.rpz-nsdname CNAME .
9234 48.zz.2.2001.rpz-nsip CNAME .
9237 RPZ can affect server performance.
9238 Each configured response policy zone requires the server to
9239 perform one to four additional database lookups before a
9240 query can be answered.
9241 For example, a DNS server with four policy zones, each with all
9242 four kinds of response triggers, QNAME, IP, NSIP, and
9243 NSDNAME, requires a total of 17 times as many database
9244 lookups as a similar DNS server with no response policy zones.
9245 A <acronym>BIND9</acronym> server with adequate memory and one
9246 response policy zone with QNAME and IP triggers might achieve a
9247 maximum queries-per-second rate about 20% lower.
9248 A server with four response policy zones with QNAME and IP
9249 triggers might have a maximum QPS rate about 50% lower.
9253 Responses rewritten by RPZ are counted in the
9254 <command>RPZRewrites</command> statistics.
9259 <sect2 id="server_statement_grammar">
9260 <title><command>server</command> Statement Grammar</title>
9262 <programlisting><command>server</command> <replaceable>ip_addr[/prefixlen]</replaceable> {
9263 <optional> bogus <replaceable>yes_or_no</replaceable> ; </optional>
9264 <optional> provide-ixfr <replaceable>yes_or_no</replaceable> ; </optional>
9265 <optional> request-ixfr <replaceable>yes_or_no</replaceable> ; </optional>
9266 <optional> edns <replaceable>yes_or_no</replaceable> ; </optional>
9267 <optional> edns-udp-size <replaceable>number</replaceable> ; </optional>
9268 <optional> max-udp-size <replaceable>number</replaceable> ; </optional>
9269 <optional> transfers <replaceable>number</replaceable> ; </optional>
9270 <optional> transfer-format <replaceable>( one-answer | many-answers )</replaceable> ; ]</optional>
9271 <optional> keys <replaceable>{ string ; <optional> string ; <optional>...</optional></optional> }</replaceable> ; </optional>
9272 <optional> transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9273 <optional> transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9274 <optional> notify-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9275 <optional> notify-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9276 <optional> query-source <optional> address ( <replaceable>ip_addr</replaceable> | <replaceable>*</replaceable> ) </optional>
9277 <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional>; </optional>
9278 <optional> query-source-v6 <optional> address ( <replaceable>ip_addr</replaceable> | <replaceable>*</replaceable> ) </optional>
9279 <optional> port ( <replaceable>ip_port</replaceable> | <replaceable>*</replaceable> ) </optional>; </optional>
9280 <optional> use-queryport-pool <replaceable>yes_or_no</replaceable>; </optional>
9281 <optional> queryport-pool-ports <replaceable>number</replaceable>; </optional>
9282 <optional> queryport-pool-updateinterval <replaceable>number</replaceable>; </optional>
9288 <sect2 id="server_statement_definition_and_usage">
9289 <title><command>server</command> Statement Definition and
9293 The <command>server</command> statement defines
9295 to be associated with a remote name server. If a prefix length is
9296 specified, then a range of servers is covered. Only the most
9298 server clause applies regardless of the order in
9299 <filename>named.conf</filename>.
9303 The <command>server</command> statement can occur at
9304 the top level of the
9305 configuration file or inside a <command>view</command>
9307 If a <command>view</command> statement contains
9308 one or more <command>server</command> statements, only
9310 apply to the view and any top-level ones are ignored.
9311 If a view contains no <command>server</command>
9313 any top-level <command>server</command> statements are
9319 If you discover that a remote server is giving out bad data,
9320 marking it as bogus will prevent further queries to it. The
9322 value of <command>bogus</command> is <command>no</command>.
9325 The <command>provide-ixfr</command> clause determines
9327 the local server, acting as master, will respond with an
9329 zone transfer when the given remote server, a slave, requests it.
9330 If set to <command>yes</command>, incremental transfer
9332 whenever possible. If set to <command>no</command>,
9334 to the remote server will be non-incremental. If not set, the
9336 of the <command>provide-ixfr</command> option in the
9338 global options block is used as a default.
9342 The <command>request-ixfr</command> clause determines
9344 the local server, acting as a slave, will request incremental zone
9345 transfers from the given remote server, a master. If not set, the
9346 value of the <command>request-ixfr</command> option in
9348 global options block is used as a default.
9352 IXFR requests to servers that do not support IXFR will
9354 fall back to AXFR. Therefore, there is no need to manually list
9355 which servers support IXFR and which ones do not; the global
9357 of <command>yes</command> should always work.
9358 The purpose of the <command>provide-ixfr</command> and
9359 <command>request-ixfr</command> clauses is
9360 to make it possible to disable the use of IXFR even when both
9362 and slave claim to support it, for example if one of the servers
9363 is buggy and crashes or corrupts data when IXFR is used.
9367 The <command>edns</command> clause determines whether
9368 the local server will attempt to use EDNS when communicating
9369 with the remote server. The default is <command>yes</command>.
9373 The <command>edns-udp-size</command> option sets the EDNS UDP size
9374 that is advertised by <command>named</command> when querying the remote server.
9375 Valid values are 512 to 4096 bytes (values outside this range will be
9376 silently adjusted). This option is useful when you wish to
9377 advertises a different value to this server than the value you
9378 advertise globally, for example, when there is a firewall at the
9379 remote site that is blocking large replies.
9383 The <command>max-udp-size</command> option sets the
9384 maximum EDNS UDP message size <command>named</command> will send. Valid
9385 values are 512 to 4096 bytes (values outside this range will
9386 be silently adjusted). This option is useful when you
9387 know that there is a firewall that is blocking large
9388 replies from <command>named</command>.
9392 The server supports two zone transfer methods. The first, <command>one-answer</command>,
9393 uses one DNS message per resource record transferred. <command>many-answers</command> packs
9394 as many resource records as possible into a message. <command>many-answers</command> is
9395 more efficient, but is only known to be understood by <acronym>BIND</acronym> 9, <acronym>BIND</acronym>
9396 8.x, and patched versions of <acronym>BIND</acronym>
9397 4.9.5. You can specify which method
9398 to use for a server with the <command>transfer-format</command> option.
9399 If <command>transfer-format</command> is not
9400 specified, the <command>transfer-format</command>
9402 by the <command>options</command> statement will be
9406 <para><command>transfers</command>
9407 is used to limit the number of concurrent inbound zone
9408 transfers from the specified server. If no
9409 <command>transfers</command> clause is specified, the
9410 limit is set according to the
9411 <command>transfers-per-ns</command> option.
9415 The <command>keys</command> clause identifies a
9416 <command>key_id</command> defined by the <command>key</command> statement,
9417 to be used for transaction security (TSIG, <xref linkend="tsig"/>)
9418 when talking to the remote server.
9419 When a request is sent to the remote server, a request signature
9420 will be generated using the key specified here and appended to the
9421 message. A request originating from the remote server is not
9423 to be signed by this key.
9427 Although the grammar of the <command>keys</command>
9429 allows for multiple keys, only a single key per server is
9435 The <command>transfer-source</command> and
9436 <command>transfer-source-v6</command> clauses specify
9437 the IPv4 and IPv6 source
9438 address to be used for zone transfer with the remote server,
9440 For an IPv4 remote server, only <command>transfer-source</command> can
9442 Similarly, for an IPv6 remote server, only
9443 <command>transfer-source-v6</command> can be
9445 For more details, see the description of
9446 <command>transfer-source</command> and
9447 <command>transfer-source-v6</command> in
9448 <xref linkend="zone_transfers"/>.
9452 The <command>notify-source</command> and
9453 <command>notify-source-v6</command> clauses specify the
9454 IPv4 and IPv6 source address to be used for notify
9455 messages sent to remote servers, respectively. For an
9456 IPv4 remote server, only <command>notify-source</command>
9457 can be specified. Similarly, for an IPv6 remote server,
9458 only <command>notify-source-v6</command> can be specified.
9462 The <command>query-source</command> and
9463 <command>query-source-v6</command> clauses specify the
9464 IPv4 and IPv6 source address to be used for queries
9465 sent to remote servers, respectively. For an IPv4
9466 remote server, only <command>query-source</command> can
9467 be specified. Similarly, for an IPv6 remote server,
9468 only <command>query-source-v6</command> can be specified.
9473 <sect2 id="statschannels">
9474 <title><command>statistics-channels</command> Statement Grammar</title>
9476 <programlisting><command>statistics-channels</command> {
9477 [ inet ( ip_addr | * ) [ port ip_port ]
9478 [ allow { <replaceable> address_match_list </replaceable> } ]; ]
9485 <title><command>statistics-channels</command> Statement Definition and
9489 The <command>statistics-channels</command> statement
9490 declares communication channels to be used by system
9491 administrators to get access to statistics information of
9496 This statement intends to be flexible to support multiple
9497 communication protocols in the future, but currently only
9498 HTTP access is supported.
9499 It requires that BIND 9 be compiled with libxml2;
9500 the <command>statistics-channels</command> statement is
9501 still accepted even if it is built without the library,
9502 but any HTTP access will fail with an error.
9506 An <command>inet</command> control channel is a TCP socket
9507 listening at the specified <command>ip_port</command> on the
9508 specified <command>ip_addr</command>, which can be an IPv4 or IPv6
9509 address. An <command>ip_addr</command> of <literal>*</literal> (asterisk) is
9510 interpreted as the IPv4 wildcard address; connections will be
9511 accepted on any of the system's IPv4 addresses.
9512 To listen on the IPv6 wildcard address,
9513 use an <command>ip_addr</command> of <literal>::</literal>.
9517 If no port is specified, port 80 is used for HTTP channels.
9518 The asterisk "<literal>*</literal>" cannot be used for
9519 <command>ip_port</command>.
9523 The attempt of opening a statistics channel is
9524 restricted by the optional <command>allow</command> clause.
9525 Connections to the statistics channel are permitted based on the
9526 <command>address_match_list</command>.
9527 If no <command>allow</command> clause is present,
9528 <command>named</command> accepts connection
9529 attempts from any address; since the statistics may
9530 contain sensitive internal information, it is highly
9531 recommended to restrict the source of connection requests
9536 If no <command>statistics-channels</command> statement is present,
9537 <command>named</command> will not open any communication channels.
9542 <sect2 id="trusted-keys">
9543 <title><command>trusted-keys</command> Statement Grammar</title>
9545 <programlisting><command>trusted-keys</command> {
9546 <replaceable>string</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ;
9547 <optional> <replaceable>string</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; <optional>...</optional></optional>
9553 <title><command>trusted-keys</command> Statement Definition
9556 The <command>trusted-keys</command> statement defines
9557 DNSSEC security roots. DNSSEC is described in <xref
9558 linkend="DNSSEC"/>. A security root is defined when the
9559 public key for a non-authoritative zone is known, but
9560 cannot be securely obtained through DNS, either because
9561 it is the DNS root zone or because its parent zone is
9562 unsigned. Once a key has been configured as a trusted
9563 key, it is treated as if it had been validated and
9564 proven secure. The resolver attempts DNSSEC validation
9565 on all DNS data in subdomains of a security root.
9568 All keys (and corresponding zones) listed in
9569 <command>trusted-keys</command> are deemed to exist regardless
9570 of what parent zones say. Similarly for all keys listed in
9571 <command>trusted-keys</command> only those keys are
9572 used to validate the DNSKEY RRset. The parent's DS RRset
9576 The <command>trusted-keys</command> statement can contain
9577 multiple key entries, each consisting of the key's
9578 domain name, flags, protocol, algorithm, and the Base-64
9579 representation of the key data.
9580 Spaces, tabs, newlines and carriage returns are ignored
9581 in the key data, so the configuration may be split up into
9585 <command>trusted-keys</command> may be set at the top level
9586 of <filename>named.conf</filename> or within a view. If it is
9587 set in both places, they are additive: keys defined at the top
9588 level are inherited by all views, but keys defined in a view
9589 are only used within that view.
9594 <title><command>managed-keys</command> Statement Grammar</title>
9596 <programlisting><command>managed-keys</command> {
9597 <replaceable>name</replaceable> <literal>initial-key</literal> <replaceable>flags</replaceable> <replaceable>protocol</replaceable> <replaceable>algorithm</replaceable> <replaceable>key-data</replaceable> ;
9598 <optional> <replaceable>name</replaceable> <literal>initial-key</literal> <replaceable>flags</replaceable> <replaceable>protocol</replaceable> <replaceable>algorithm</replaceable> <replaceable>key-data</replaceable> ; <optional>...</optional></optional>
9603 <sect2 id="managed-keys">
9604 <title><command>managed-keys</command> Statement Definition
9607 The <command>managed-keys</command> statement, like
9608 <command>trusted-keys</command>, defines DNSSEC
9609 security roots. The difference is that
9610 <command>managed-keys</command> can be kept up to date
9611 automatically, without intervention from the resolver
9615 Suppose, for example, that a zone's key-signing
9616 key was compromised, and the zone owner had to revoke and
9617 replace the key. A resolver which had the old key in a
9618 <command>trusted-keys</command> statement would be
9619 unable to validate this zone any longer; it would
9620 reply with a SERVFAIL response code. This would
9621 continue until the resolver operator had updated the
9622 <command>trusted-keys</command> statement with the new key.
9625 If, however, the zone were listed in a
9626 <command>managed-keys</command> statement instead, then the
9627 zone owner could add a "stand-by" key to the zone in advance.
9628 <command>named</command> would store the stand-by key, and
9629 when the original key was revoked, <command>named</command>
9630 would be able to transition smoothly to the new key. It would
9631 also recognize that the old key had been revoked, and cease
9632 using that key to validate answers, minimizing the damage that
9633 the compromised key could do.
9636 A <command>managed-keys</command> statement contains a list of
9637 the keys to be managed, along with information about how the
9638 keys are to be initialized for the first time. The only
9639 initialization method currently supported (as of
9640 <acronym>BIND</acronym> 9.7.0) is <literal>initial-key</literal>.
9641 This means the <command>managed-keys</command> statement must
9642 contain a copy of the initializing key. (Future releases may
9643 allow keys to be initialized by other methods, eliminating this
9647 Consequently, a <command>managed-keys</command> statement
9648 appears similar to a <command>trusted-keys</command>, differing
9649 in the presence of the second field, containing the keyword
9650 <literal>initial-key</literal>. The difference is, whereas the
9651 keys listed in a <command>trusted-keys</command> continue to be
9652 trusted until they are removed from
9653 <filename>named.conf</filename>, an initializing key listed
9654 in a <command>managed-keys</command> statement is only trusted
9655 <emphasis>once</emphasis>: for as long as it takes to load the
9656 managed key database and start the RFC 5011 key maintenance
9660 The first time <command>named</command> runs with a managed key
9661 configured in <filename>named.conf</filename>, it fetches the
9662 DNSKEY RRset directly from the zone apex, and validates it
9663 using the key specified in the <command>managed-keys</command>
9664 statement. If the DNSKEY RRset is validly signed, then it is
9665 used as the basis for a new managed keys database.
9668 From that point on, whenever <command>named</command> runs, it
9669 sees the <command>managed-keys</command> statement, checks to
9670 make sure RFC 5011 key maintenance has already been initialized
9671 for the specified domain, and if so, it simply moves on. The
9672 key specified in the <command>managed-keys</command> is not
9673 used to validate answers; it has been superseded by the key or
9674 keys stored in the managed keys database.
9677 The next time <command>named</command> runs after a name
9678 has been <emphasis>removed</emphasis> from the
9679 <command>managed-keys</command> statement, the corresponding
9680 zone will be removed from the managed keys database,
9681 and RFC 5011 key maintenance will no longer be used for that
9685 <command>named</command> only maintains a single managed keys
9686 database; consequently, unlike <command>trusted-keys</command>,
9687 <command>managed-keys</command> may only be set at the top
9688 level of <filename>named.conf</filename>, not within a view.
9691 In the current implementation, the managed keys database is
9692 stored as a master-format zone file called
9693 <filename>managed-keys.bind</filename>. When the key database
9694 is changed, the zone is updated. As with any other dynamic
9695 zone, changes will be written into a journal file,
9696 <filename>managed-keys.bind.jnl</filename>. They are committed
9697 to the master file as soon as possible afterward; in the case
9698 of the managed key database, this will usually occur within 30
9699 seconds. So, whenever <command>named</command> is using
9700 automatic key maintenance, those two files can be expected to
9701 exist in the working directory. (For this reason among others,
9702 the working directory should be always be writable by
9703 <command>named</command>.)
9706 If the <command>dnssec-validation</command> option is
9707 set to <userinput>auto</userinput>, <command>named</command>
9708 will automatically initialize a managed key for the
9709 root zone. Similarly, if the <command>dnssec-lookaside</command>
9710 option is set to <userinput>auto</userinput>,
9711 <command>named</command> will automatically initialize
9712 a managed key for the zone <literal>dlv.isc.org</literal>.
9713 In both cases, the key that is used to initialize the key
9714 maintenance process is built into <command>named</command>,
9715 and can be overridden from <command>bindkeys-file</command>.
9719 <sect2 id="view_statement_grammar">
9720 <title><command>view</command> Statement Grammar</title>
9722 <programlisting><command>view</command> <replaceable>view_name</replaceable>
9723 <optional><replaceable>class</replaceable></optional> {
9724 match-clients { <replaceable>address_match_list</replaceable> };
9725 match-destinations { <replaceable>address_match_list</replaceable> };
9726 match-recursive-only <replaceable>yes_or_no</replaceable> ;
9727 <optional> <replaceable>view_option</replaceable>; ...</optional>
9728 <optional> <replaceable>zone_statement</replaceable>; ...</optional>
9734 <title><command>view</command> Statement Definition and Usage</title>
9737 The <command>view</command> statement is a powerful
9739 of <acronym>BIND</acronym> 9 that lets a name server
9740 answer a DNS query differently
9741 depending on who is asking. It is particularly useful for
9743 split DNS setups without having to run multiple servers.
9747 Each <command>view</command> statement defines a view
9749 DNS namespace that will be seen by a subset of clients. A client
9751 a view if its source IP address matches the
9752 <varname>address_match_list</varname> of the view's
9753 <command>match-clients</command> clause and its
9754 destination IP address matches
9755 the <varname>address_match_list</varname> of the
9757 <command>match-destinations</command> clause. If not
9759 <command>match-clients</command> and <command>match-destinations</command>
9760 default to matching all addresses. In addition to checking IP
9762 <command>match-clients</command> and <command>match-destinations</command>
9763 can also take <command>keys</command> which provide an
9765 client to select the view. A view can also be specified
9766 as <command>match-recursive-only</command>, which
9767 means that only recursive
9768 requests from matching clients will match that view.
9769 The order of the <command>view</command> statements is
9771 a client request will be resolved in the context of the first
9772 <command>view</command> that it matches.
9776 Zones defined within a <command>view</command>
9778 only be accessible to clients that match the <command>view</command>.
9779 By defining a zone of the same name in multiple views, different
9780 zone data can be given to different clients, for example,
9782 and "external" clients in a split DNS setup.
9786 Many of the options given in the <command>options</command> statement
9787 can also be used within a <command>view</command>
9789 apply only when resolving queries with that view. When no
9791 value is given, the value in the <command>options</command> statement
9792 is used as a default. Also, zone options can have default values
9794 in the <command>view</command> statement; these
9795 view-specific defaults
9796 take precedence over those in the <command>options</command> statement.
9800 Views are class specific. If no class is given, class IN
9801 is assumed. Note that all non-IN views must contain a hint zone,
9802 since only the IN class has compiled-in default hints.
9806 If there are no <command>view</command> statements in
9808 file, a default view that matches any client is automatically
9810 in class IN. Any <command>zone</command> statements
9812 the top level of the configuration file are considered to be part
9814 this default view, and the <command>options</command>
9816 apply to the default view. If any explicit <command>view</command>
9817 statements are present, all <command>zone</command>
9819 occur inside <command>view</command> statements.
9823 Here is an example of a typical split DNS setup implemented
9824 using <command>view</command> statements:
9827 <programlisting>view "internal" {
9828 // This should match our internal networks.
9829 match-clients { 10.0.0.0/8; };
9831 // Provide recursive service to internal
9835 // Provide a complete view of the example.com
9836 // zone including addresses of internal hosts.
9837 zone "example.com" {
9839 file "example-internal.db";
9844 // Match all clients not matched by the
9846 match-clients { any; };
9848 // Refuse recursive service to external clients.
9851 // Provide a restricted view of the example.com
9852 // zone containing only publicly accessible hosts.
9853 zone "example.com" {
9855 file "example-external.db";
9861 <sect2 id="zone_statement_grammar">
9862 <title><command>zone</command>
9863 Statement Grammar</title>
9865 <programlisting><command>zone</command> <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> {
9867 <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional>
9868 <optional> allow-query-on { <replaceable>address_match_list</replaceable> }; </optional>
9869 <optional> allow-transfer { <replaceable>address_match_list</replaceable> }; </optional>
9870 <optional> allow-update { <replaceable>address_match_list</replaceable> }; </optional>
9871 <optional> update-policy <replaceable>local</replaceable> | { <replaceable>update_policy_rule</replaceable> <optional>...</optional> }; </optional>
9872 <optional> also-notify { <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ;
9873 <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
9874 <optional> check-names (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional>
9875 <optional> check-mx (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional>
9876 <optional> check-wildcard <replaceable>yes_or_no</replaceable>; </optional>
9877 <optional> check-spf ( <replaceable>warn</replaceable> | <replaceable>fail</replaceable> | <replaceable>ignore</replaceable> ); </optional>
9878 <optional> check-integrity <replaceable>yes_or_no</replaceable> ; </optional>
9879 <optional> dialup <replaceable>dialup_option</replaceable> ; </optional>
9880 <optional> file <replaceable>string</replaceable> ; </optional>
9881 <optional> masterfile-format (<constant>text</constant>|<constant>raw</constant>) ; </optional>
9882 <optional> journal <replaceable>string</replaceable> ; </optional>
9883 <optional> max-journal-size <replaceable>size_spec</replaceable>; </optional>
9884 <optional> forward (<constant>only</constant>|<constant>first</constant>) ; </optional>
9885 <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
9886 <optional> ixfr-base <replaceable>string</replaceable> ; </optional>
9887 <optional> ixfr-from-differences <replaceable>yes_or_no</replaceable>; </optional>
9888 <optional> ixfr-tmp-file <replaceable>string</replaceable> ; </optional>
9889 <optional> maintain-ixfr-base <replaceable>yes_or_no</replaceable> ; </optional>
9890 <optional> max-ixfr-log-size <replaceable>number</replaceable> ; </optional>
9891 <optional> max-transfer-idle-out <replaceable>number</replaceable> ; </optional>
9892 <optional> max-transfer-time-out <replaceable>number</replaceable> ; </optional>
9893 <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable> | <replaceable>master-only</replaceable> ; </optional>
9894 <optional> notify-delay <replaceable>seconds</replaceable> ; </optional>
9895 <optional> notify-to-soa <replaceable>yes_or_no</replaceable>; </optional>
9896 <optional> pubkey <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; </optional>
9897 <optional> notify-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9898 <optional> notify-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9899 <optional> zone-statistics <replaceable>yes_or_no</replaceable> ; </optional>
9900 <optional> sig-validity-interval <replaceable>number</replaceable> <optional><replaceable>number</replaceable></optional> ; </optional>
9901 <optional> sig-signing-nodes <replaceable>number</replaceable> ; </optional>
9902 <optional> sig-signing-signatures <replaceable>number</replaceable> ; </optional>
9903 <optional> sig-signing-type <replaceable>number</replaceable> ; </optional>
9904 <optional> database <replaceable>string</replaceable> ; </optional>
9905 <optional> min-refresh-time <replaceable>number</replaceable> ; </optional>
9906 <optional> max-refresh-time <replaceable>number</replaceable> ; </optional>
9907 <optional> min-retry-time <replaceable>number</replaceable> ; </optional>
9908 <optional> max-retry-time <replaceable>number</replaceable> ; </optional>
9909 <optional> key-directory <replaceable>path_name</replaceable>; </optional>
9910 <optional> auto-dnssec <constant>allow</constant>|<constant>maintain</constant>|<constant>off</constant>; </optional>
9911 <optional> zero-no-soa-ttl <replaceable>yes_or_no</replaceable> ; </optional>
9914 zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> {
9916 <optional> allow-notify { <replaceable>address_match_list</replaceable> }; </optional>
9917 <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional>
9918 <optional> allow-query-on { <replaceable>address_match_list</replaceable> }; </optional>
9919 <optional> allow-transfer { <replaceable>address_match_list</replaceable> }; </optional>
9920 <optional> allow-update-forwarding { <replaceable>address_match_list</replaceable> }; </optional>
9921 <optional> update-check-ksk <replaceable>yes_or_no</replaceable>; </optional>
9922 <optional> dnssec-update-mode ( <replaceable>maintain</replaceable> | <replaceable>no-resign</replaceable> ); </optional>
9923 <optional> dnssec-dnskey-kskonly <replaceable>yes_or_no</replaceable>; </optional>
9924 <optional> dnssec-secure-to-insecure <replaceable>yes_or_no</replaceable> ; </optional>
9925 <optional> try-tcp-refresh <replaceable>yes_or_no</replaceable>; </optional>
9926 <optional> also-notify { <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ;
9927 <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
9928 <optional> check-names (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional>
9929 <optional> dialup <replaceable>dialup_option</replaceable> ; </optional>
9930 <optional> file <replaceable>string</replaceable> ; </optional>
9931 <optional> masterfile-format (<constant>text</constant>|<constant>raw</constant>) ; </optional>
9932 <optional> journal <replaceable>string</replaceable> ; </optional>
9933 <optional> max-journal-size <replaceable>size_spec</replaceable>; </optional>
9934 <optional> forward (<constant>only</constant>|<constant>first</constant>) ; </optional>
9935 <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
9936 <optional> ixfr-base <replaceable>string</replaceable> ; </optional>
9937 <optional> ixfr-from-differences <replaceable>yes_or_no</replaceable>; </optional>
9938 <optional> ixfr-tmp-file <replaceable>string</replaceable> ; </optional>
9939 <optional> maintain-ixfr-base <replaceable>yes_or_no</replaceable> ; </optional>
9940 <optional> masters <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> | <replaceable>ip_addr</replaceable>
9941 <optional>port <replaceable>ip_port</replaceable></optional>
9942 <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> }; </optional>
9943 <optional> max-ixfr-log-size <replaceable>number</replaceable> ; </optional>
9944 <optional> max-transfer-idle-in <replaceable>number</replaceable> ; </optional>
9945 <optional> max-transfer-idle-out <replaceable>number</replaceable> ; </optional>
9946 <optional> max-transfer-time-in <replaceable>number</replaceable> ; </optional>
9947 <optional> max-transfer-time-out <replaceable>number</replaceable> ; </optional>
9948 <optional> notify <replaceable>yes_or_no</replaceable> | <replaceable>explicit</replaceable> | <replaceable>master-only</replaceable> ; </optional>
9949 <optional> notify-delay <replaceable>seconds</replaceable> ; </optional>
9950 <optional> notify-to-soa <replaceable>yes_or_no</replaceable>; </optional>
9951 <optional> pubkey <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; </optional>
9952 <optional> transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9953 <optional> transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9954 <optional> alt-transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9955 <optional> alt-transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>)
9956 <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9957 <optional> use-alt-transfer-source <replaceable>yes_or_no</replaceable>; </optional>
9958 <optional> notify-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9959 <optional> notify-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9960 <optional> zone-statistics <replaceable>yes_or_no</replaceable> ; </optional>
9961 <optional> database <replaceable>string</replaceable> ; </optional>
9962 <optional> min-refresh-time <replaceable>number</replaceable> ; </optional>
9963 <optional> max-refresh-time <replaceable>number</replaceable> ; </optional>
9964 <optional> min-retry-time <replaceable>number</replaceable> ; </optional>
9965 <optional> max-retry-time <replaceable>number</replaceable> ; </optional>
9966 <optional> multi-master <replaceable>yes_or_no</replaceable> ; </optional>
9967 <optional> zero-no-soa-ttl <replaceable>yes_or_no</replaceable> ; </optional>
9970 zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> {
9972 file <replaceable>string</replaceable> ;
9973 <optional> delegation-only <replaceable>yes_or_no</replaceable> ; </optional>
9974 <optional> check-names (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional> // Not Implemented.
9977 zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> {
9979 <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional>
9980 <optional> allow-query-on { <replaceable>address_match_list</replaceable> }; </optional>
9981 <optional> check-names (<constant>warn</constant>|<constant>fail</constant>|<constant>ignore</constant>) ; </optional>
9982 <optional> dialup <replaceable>dialup_option</replaceable> ; </optional>
9983 <optional> delegation-only <replaceable>yes_or_no</replaceable> ; </optional>
9984 <optional> file <replaceable>string</replaceable> ; </optional>
9985 <optional> masterfile-format (<constant>text</constant>|<constant>raw</constant>) ; </optional>
9986 <optional> forward (<constant>only</constant>|<constant>first</constant>) ; </optional>
9987 <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
9988 <optional> masters <optional>port <replaceable>ip_port</replaceable></optional> { ( <replaceable>masters_list</replaceable> | <replaceable>ip_addr</replaceable>
9989 <optional>port <replaceable>ip_port</replaceable></optional>
9990 <optional>key <replaceable>key</replaceable></optional> ) ; <optional>...</optional> }; </optional>
9991 <optional> max-transfer-idle-in <replaceable>number</replaceable> ; </optional>
9992 <optional> max-transfer-time-in <replaceable>number</replaceable> ; </optional>
9993 <optional> pubkey <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>number</replaceable> <replaceable>string</replaceable> ; </optional>
9994 <optional> transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9995 <optional> transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>)
9996 <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9997 <optional> alt-transfer-source (<replaceable>ip4_addr</replaceable> | <constant>*</constant>) <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
9998 <optional> alt-transfer-source-v6 (<replaceable>ip6_addr</replaceable> | <constant>*</constant>)
9999 <optional>port <replaceable>ip_port</replaceable></optional> ; </optional>
10000 <optional> use-alt-transfer-source <replaceable>yes_or_no</replaceable>; </optional>
10001 <optional> zone-statistics <replaceable>yes_or_no</replaceable> ; </optional>
10002 <optional> database <replaceable>string</replaceable> ; </optional>
10003 <optional> min-refresh-time <replaceable>number</replaceable> ; </optional>
10004 <optional> max-refresh-time <replaceable>number</replaceable> ; </optional>
10005 <optional> min-retry-time <replaceable>number</replaceable> ; </optional>
10006 <optional> max-retry-time <replaceable>number</replaceable> ; </optional>
10007 <optional> multi-master <replaceable>yes_or_no</replaceable> ; </optional>
10010 zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> {
10012 <optional> allow-query { <replaceable>address_match_list</replaceable> }; </optional>
10013 <optional> server-addresses { <optional> <replaceable>ip_addr</replaceable> ; ... </optional> }; </optional>
10014 <optional> server-names { <optional> <replaceable>namelist</replaceable> </optional> }; </optional>
10015 <optional> zone-statistics <replaceable>yes_or_no</replaceable> ; </optional>
10018 zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> {
10020 <optional> forward (<constant>only</constant>|<constant>first</constant>) ; </optional>
10021 <optional> forwarders { <optional> <replaceable>ip_addr</replaceable> <optional>port <replaceable>ip_port</replaceable></optional> ; ... </optional> }; </optional>
10022 <optional> delegation-only <replaceable>yes_or_no</replaceable> ; </optional>
10025 zone <replaceable>zone_name</replaceable> <optional><replaceable>class</replaceable></optional> {
10026 type delegation-only;
10033 <title><command>zone</command> Statement Definition and Usage</title>
10035 <title>Zone Types</title>
10036 <informaltable colsep="0" rowsep="0">
10037 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table">
10038 <!--colspec colname="1" colnum="1" colsep="0" colwidth="1.108in"/-->
10039 <!--colspec colname="2" colnum="2" colsep="0" colwidth="4.017in"/-->
10040 <colspec colname="1" colnum="1" colsep="0"/>
10041 <colspec colname="2" colnum="2" colsep="0" colwidth="4.017in"/>
10044 <entry colname="1">
10046 <varname>master</varname>
10049 <entry colname="2">
10051 The server has a master copy of the data
10052 for the zone and will be able to provide authoritative
10059 <entry colname="1">
10061 <varname>slave</varname>
10064 <entry colname="2">
10066 A slave zone is a replica of a master
10067 zone. The <command>masters</command> list
10068 specifies one or more IP addresses
10069 of master servers that the slave contacts to update
10070 its copy of the zone.
10071 Masters list elements can also be names of other
10073 By default, transfers are made from port 53 on the
10075 be changed for all servers by specifying a port number
10077 list of IP addresses, or on a per-server basis after
10079 Authentication to the master can also be done with
10080 per-server TSIG keys.
10081 If a file is specified, then the
10082 replica will be written to this file whenever the zone
10084 and reloaded from this file on a server restart. Use
10086 recommended, since it often speeds server startup and
10088 a needless waste of bandwidth. Note that for large
10090 tens or hundreds of thousands) of zones per server, it
10092 use a two-level naming scheme for zone filenames. For
10094 a slave server for the zone <literal>example.com</literal> might place
10095 the zone contents into a file called
10096 <filename>ex/example.com</filename> where <filename>ex/</filename> is
10097 just the first two letters of the zone name. (Most
10099 behave very slowly if you put 100000 files into
10100 a single directory.)
10105 <entry colname="1">
10107 <varname>stub</varname>
10110 <entry colname="2">
10112 A stub zone is similar to a slave zone,
10113 except that it replicates only the NS records of a
10114 master zone instead
10115 of the entire zone. Stub zones are not a standard part
10117 they are a feature specific to the <acronym>BIND</acronym> implementation.
10121 Stub zones can be used to eliminate the need for glue
10123 in a parent zone at the expense of maintaining a stub
10125 a set of name server addresses in <filename>named.conf</filename>.
10126 This usage is not recommended for new configurations,
10128 supports it only in a limited way.
10129 In <acronym>BIND</acronym> 4/8, zone
10130 transfers of a parent zone
10131 included the NS records from stub children of that
10133 that, in some cases, users could get away with
10134 configuring child stubs
10135 only in the master server for the parent zone. <acronym>BIND</acronym>
10136 9 never mixes together zone data from different zones
10138 way. Therefore, if a <acronym>BIND</acronym> 9 master serving a parent
10139 zone has child stub zones configured, all the slave
10141 parent zone also need to have the same child stub
10147 Stub zones can also be used as a way of forcing the
10149 of a given domain to use a particular set of
10150 authoritative servers.
10151 For example, the caching name servers on a private
10153 RFC1918 addressing may be configured with stub zones
10155 <literal>10.in-addr.arpa</literal>
10156 to use a set of internal name servers as the
10158 servers for that domain.
10163 <entry colname="1">
10165 <varname>static-stub</varname>
10168 <entry colname="2">
10170 A static-stub zone is similar to a stub zone
10171 with the following exceptions:
10172 the zone data is statically configured, rather
10173 than transferred from a master server;
10174 when recursion is necessary for a query that
10175 matches a static-stub zone, the locally
10176 configured data (nameserver names and glue addresses)
10177 is always used even if different authoritative
10178 information is cached.
10181 Zone data is configured via the
10182 <command>server-addresses</command> and
10183 <command>server-names</command> zone options.
10186 The zone data is maintained in the form of NS
10187 and (if necessary) glue A or AAAA RRs
10188 internally, which can be seen by dumping zone
10189 databases by <command>rndc dumpdb -all</command>.
10190 The configured RRs are considered local configuration
10191 parameters rather than public data.
10192 Non recursive queries (i.e., those with the RD
10193 bit off) to a static-stub zone are therefore
10194 prohibited and will be responded with REFUSED.
10197 Since the data is statically configured, no
10198 zone maintenance action takes place for a static-stub
10200 For example, there is no periodic refresh
10201 attempt, and an incoming notify message
10202 will be rejected with an rcode of NOTAUTH.
10205 Each static-stub zone is configured with
10206 internally generated NS and (if necessary)
10212 <entry colname="1">
10214 <varname>forward</varname>
10217 <entry colname="2">
10219 A "forward zone" is a way to configure
10220 forwarding on a per-domain basis. A <command>zone</command> statement
10221 of type <command>forward</command> can
10222 contain a <command>forward</command>
10223 and/or <command>forwarders</command>
10225 which will apply to queries within the domain given by
10227 name. If no <command>forwarders</command>
10228 statement is present or
10229 an empty list for <command>forwarders</command> is given, then no
10230 forwarding will be done for the domain, canceling the
10232 any forwarders in the <command>options</command> statement. Thus
10233 if you want to use this type of zone to change the
10235 global <command>forward</command> option
10236 (that is, "forward first"
10237 to, then "forward only", or vice versa, but want to
10239 servers as set globally) you need to re-specify the
10245 <entry colname="1">
10247 <varname>hint</varname>
10250 <entry colname="2">
10252 The initial set of root name servers is
10253 specified using a "hint zone". When the server starts
10255 the root hints to find a root name server and get the
10257 list of root name servers. If no hint zone is
10258 specified for class
10259 IN, the server uses a compiled-in default set of root
10261 Classes other than IN have no built-in defaults hints.
10266 <entry colname="1">
10268 <varname>delegation-only</varname>
10271 <entry colname="2">
10273 This is used to enforce the delegation-only
10274 status of infrastructure zones (e.g. COM,
10275 NET, ORG). Any answer that is received
10276 without an explicit or implicit delegation
10277 in the authority section will be treated
10278 as NXDOMAIN. This does not apply to the
10279 zone apex. This should not be applied to
10283 <varname>delegation-only</varname> has no
10284 effect on answers received from forwarders.
10287 See caveats in <xref linkend="root_delegation_only"/>.
10297 <title>Class</title>
10299 The zone's name may optionally be followed by a class. If
10300 a class is not specified, class <literal>IN</literal> (for <varname>Internet</varname>),
10301 is assumed. This is correct for the vast majority of cases.
10304 The <literal>hesiod</literal> class is
10305 named for an information service from MIT's Project Athena. It
10307 used to share information about various systems databases, such
10308 as users, groups, printers and so on. The keyword
10309 <literal>HS</literal> is
10310 a synonym for hesiod.
10313 Another MIT development is Chaosnet, a LAN protocol created
10314 in the mid-1970s. Zone data for it can be specified with the <literal>CHAOS</literal> class.
10319 <title>Zone Options</title>
10324 <term><command>allow-notify</command></term>
10327 See the description of
10328 <command>allow-notify</command> in <xref linkend="access_control"/>.
10334 <term><command>allow-query</command></term>
10337 See the description of
10338 <command>allow-query</command> in <xref linkend="access_control"/>.
10344 <term><command>allow-query-on</command></term>
10347 See the description of
10348 <command>allow-query-on</command> in <xref linkend="access_control"/>.
10354 <term><command>allow-transfer</command></term>
10357 See the description of <command>allow-transfer</command>
10358 in <xref linkend="access_control"/>.
10364 <term><command>allow-update</command></term>
10367 See the description of <command>allow-update</command>
10368 in <xref linkend="access_control"/>.
10374 <term><command>update-policy</command></term>
10377 Specifies a "Simple Secure Update" policy. See
10378 <xref linkend="dynamic_update_policies"/>.
10384 <term><command>allow-update-forwarding</command></term>
10387 See the description of <command>allow-update-forwarding</command>
10388 in <xref linkend="access_control"/>.
10394 <term><command>also-notify</command></term>
10397 Only meaningful if <command>notify</command>
10399 active for this zone. The set of machines that will
10401 <literal>DNS NOTIFY</literal> message
10402 for this zone is made up of all the listed name servers
10404 the primary master) for the zone plus any IP addresses
10406 with <command>also-notify</command>. A port
10408 with each <command>also-notify</command>
10409 address to send the notify
10410 messages to a port other than the default of 53.
10411 <command>also-notify</command> is not
10412 meaningful for stub zones.
10413 The default is the empty list.
10419 <term><command>check-names</command></term>
10422 This option is used to restrict the character set and
10424 certain domain names in master files and/or DNS responses
10426 network. The default varies according to zone type. For <command>master</command> zones the default is <command>fail</command>. For <command>slave</command>
10427 zones the default is <command>warn</command>.
10428 It is not implemented for <command>hint</command> zones.
10434 <term><command>check-mx</command></term>
10437 See the description of
10438 <command>check-mx</command> in <xref linkend="boolean_options"/>.
10444 <term><command>check-spf</command></term>
10447 See the description of
10448 <command>check-spf</command> in <xref linkend="boolean_options"/>.
10454 <term><command>check-wildcard</command></term>
10457 See the description of
10458 <command>check-wildcard</command> in <xref linkend="boolean_options"/>.
10464 <term><command>check-integrity</command></term>
10467 See the description of
10468 <command>check-integrity</command> in <xref linkend="boolean_options"/>.
10474 <term><command>check-sibling</command></term>
10477 See the description of
10478 <command>check-sibling</command> in <xref linkend="boolean_options"/>.
10484 <term><command>zero-no-soa-ttl</command></term>
10487 See the description of
10488 <command>zero-no-soa-ttl</command> in <xref linkend="boolean_options"/>.
10494 <term><command>update-check-ksk</command></term>
10497 See the description of
10498 <command>update-check-ksk</command> in <xref linkend="boolean_options"/>.
10504 <term><command>dnssec-dnskey-kskonly</command></term>
10507 See the description of
10508 <command>dnssec-dnskey-kskonly</command> in <xref linkend="boolean_options"/>.
10514 <term><command>try-tcp-refresh</command></term>
10517 See the description of
10518 <command>try-tcp-refresh</command> in <xref linkend="boolean_options"/>.
10524 <term><command>database</command></term>
10527 Specify the type of database to be used for storing the
10528 zone data. The string following the <command>database</command> keyword
10529 is interpreted as a list of whitespace-delimited words.
10531 identifies the database type, and any subsequent words are
10533 as arguments to the database to be interpreted in a way
10535 to the database type.
10538 The default is <userinput>"rbt"</userinput>, BIND 9's
10540 red-black-tree database. This database does not take
10544 Other values are possible if additional database drivers
10545 have been linked into the server. Some sample drivers are
10547 with the distribution but none are linked in by default.
10553 <term><command>dialup</command></term>
10556 See the description of
10557 <command>dialup</command> in <xref linkend="boolean_options"/>.
10563 <term><command>delegation-only</command></term>
10566 The flag only applies to hint and stub zones. If set
10567 to <userinput>yes</userinput>, then the zone will also be
10568 treated as if it is also a delegation-only type zone.
10571 See caveats in <xref linkend="root_delegation_only"/>.
10577 <term><command>forward</command></term>
10580 Only meaningful if the zone has a forwarders
10581 list. The <command>only</command> value causes
10583 after trying the forwarders and getting no answer, while <command>first</command> would
10584 allow a normal lookup to be tried.
10590 <term><command>forwarders</command></term>
10593 Used to override the list of global forwarders.
10594 If it is not specified in a zone of type <command>forward</command>,
10595 no forwarding is done for the zone and the global options are
10602 <term><command>ixfr-base</command></term>
10605 Was used in <acronym>BIND</acronym> 8 to
10607 of the transaction log (journal) file for dynamic update
10609 <acronym>BIND</acronym> 9 ignores the option
10610 and constructs the name of the journal
10611 file by appending "<filename>.jnl</filename>"
10619 <term><command>ixfr-tmp-file</command></term>
10622 Was an undocumented option in <acronym>BIND</acronym> 8.
10623 Ignored in <acronym>BIND</acronym> 9.
10629 <term><command>journal</command></term>
10632 Allow the default journal's filename to be overridden.
10633 The default is the zone's filename with "<filename>.jnl</filename>" appended.
10634 This is applicable to <command>master</command> and <command>slave</command> zones.
10640 <term><command>max-journal-size</command></term>
10643 See the description of
10644 <command>max-journal-size</command> in <xref linkend="server_resource_limits"/>.
10650 <term><command>max-transfer-time-in</command></term>
10653 See the description of
10654 <command>max-transfer-time-in</command> in <xref linkend="zone_transfers"/>.
10660 <term><command>max-transfer-idle-in</command></term>
10663 See the description of
10664 <command>max-transfer-idle-in</command> in <xref linkend="zone_transfers"/>.
10670 <term><command>max-transfer-time-out</command></term>
10673 See the description of
10674 <command>max-transfer-time-out</command> in <xref linkend="zone_transfers"/>.
10680 <term><command>max-transfer-idle-out</command></term>
10683 See the description of
10684 <command>max-transfer-idle-out</command> in <xref linkend="zone_transfers"/>.
10690 <term><command>notify</command></term>
10693 See the description of
10694 <command>notify</command> in <xref linkend="boolean_options"/>.
10700 <term><command>notify-delay</command></term>
10703 See the description of
10704 <command>notify-delay</command> in <xref linkend="tuning"/>.
10710 <term><command>notify-to-soa</command></term>
10713 See the description of
10714 <command>notify-to-soa</command> in
10715 <xref linkend="boolean_options"/>.
10721 <term><command>pubkey</command></term>
10724 In <acronym>BIND</acronym> 8, this option was
10725 intended for specifying
10726 a public zone key for verification of signatures in DNSSEC
10728 zones when they are loaded from disk. <acronym>BIND</acronym> 9 does not verify signatures
10729 on load and ignores the option.
10735 <term><command>zone-statistics</command></term>
10738 If <userinput>yes</userinput>, the server will keep
10740 information for this zone, which can be dumped to the
10741 <command>statistics-file</command> defined in
10742 the server options.
10748 <term><command>server-addresses</command></term>
10751 Only meaningful for static-stub zones.
10752 This is a list of IP addresses to which queries
10753 should be sent in recursive resolution for the
10755 A non empty list for this option will internally
10756 configure the apex NS RR with associated glue A or
10760 For example, if "example.com" is configured as a
10761 static-stub zone with 192.0.2.1 and 2001:db8::1234
10762 in a <command>server-addresses</command> option,
10763 the following RRs will be internally configured.
10765 <programlisting>example.com. NS example.com.
10766 example.com. A 192.0.2.1
10767 example.com. AAAA 2001:db8::1234</programlisting>
10769 These records are internally used to resolve
10770 names under the static-stub zone.
10771 For instance, if the server receives a query for
10772 "www.example.com" with the RD bit on, the server
10773 will initiate recursive resolution and send
10774 queries to 192.0.2.1 and/or 2001:db8::1234.
10780 <term><command>server-names</command></term>
10783 Only meaningful for static-stub zones.
10784 This is a list of domain names of nameservers that
10785 act as authoritative servers of the static-stub
10787 These names will be resolved to IP addresses when
10788 <command>named</command> needs to send queries to
10790 To make this supplemental resolution successful,
10791 these names must not be a subdomain of the origin
10792 name of static-stub zone.
10793 That is, when "example.net" is the origin of a
10794 static-stub zone, "ns.example" and
10795 "master.example.com" can be specified in the
10796 <command>server-names</command> option, but
10797 "ns.example.net" cannot, and will be rejected by
10798 the configuration parser.
10801 A non empty list for this option will internally
10802 configure the apex NS RR with the specified names.
10803 For example, if "example.com" is configured as a
10804 static-stub zone with "ns1.example.net" and
10806 in a <command>server-names</command> option,
10807 the following RRs will be internally configured.
10809 <programlisting>example.com. NS ns1.example.net.
10810 example.com. NS ns2.example.net.
10813 These records are internally used to resolve
10814 names under the static-stub zone.
10815 For instance, if the server receives a query for
10816 "www.example.com" with the RD bit on, the server
10817 initiate recursive resolution,
10818 resolve "ns1.example.net" and/or
10819 "ns2.example.net" to IP addresses, and then send
10820 queries to (one or more of) these addresses.
10826 <term><command>sig-validity-interval</command></term>
10829 See the description of
10830 <command>sig-validity-interval</command> in <xref linkend="tuning"/>.
10836 <term><command>sig-signing-nodes</command></term>
10839 See the description of
10840 <command>sig-signing-nodes</command> in <xref linkend="tuning"/>.
10846 <term><command>sig-signing-signatures</command></term>
10849 See the description of
10850 <command>sig-signing-signatures</command> in <xref linkend="tuning"/>.
10856 <term><command>sig-signing-type</command></term>
10859 See the description of
10860 <command>sig-signing-type</command> in <xref linkend="tuning"/>.
10866 <term><command>transfer-source</command></term>
10869 See the description of
10870 <command>transfer-source</command> in <xref linkend="zone_transfers"/>.
10876 <term><command>transfer-source-v6</command></term>
10879 See the description of
10880 <command>transfer-source-v6</command> in <xref linkend="zone_transfers"/>.
10886 <term><command>alt-transfer-source</command></term>
10889 See the description of
10890 <command>alt-transfer-source</command> in <xref linkend="zone_transfers"/>.
10896 <term><command>alt-transfer-source-v6</command></term>
10899 See the description of
10900 <command>alt-transfer-source-v6</command> in <xref linkend="zone_transfers"/>.
10906 <term><command>use-alt-transfer-source</command></term>
10909 See the description of
10910 <command>use-alt-transfer-source</command> in <xref linkend="zone_transfers"/>.
10917 <term><command>notify-source</command></term>
10920 See the description of
10921 <command>notify-source</command> in <xref linkend="zone_transfers"/>.
10927 <term><command>notify-source-v6</command></term>
10930 See the description of
10931 <command>notify-source-v6</command> in <xref linkend="zone_transfers"/>.
10937 <term><command>min-refresh-time</command></term>
10938 <term><command>max-refresh-time</command></term>
10939 <term><command>min-retry-time</command></term>
10940 <term><command>max-retry-time</command></term>
10943 See the description in <xref linkend="tuning"/>.
10949 <term><command>ixfr-from-differences</command></term>
10952 See the description of
10953 <command>ixfr-from-differences</command> in <xref linkend="boolean_options"/>.
10954 (Note that the <command>ixfr-from-differences</command>
10955 <userinput>master</userinput> and
10956 <userinput>slave</userinput> choices are not
10957 available at the zone level.)
10963 <term><command>key-directory</command></term>
10966 See the description of
10967 <command>key-directory</command> in <xref linkend="options"/>.
10973 <term><command>auto-dnssec</command></term>
10976 Zones configured for dynamic DNS may also use this
10977 option to allow varying levels of automatic DNSSEC key
10978 management. There are three possible settings:
10981 <command>auto-dnssec allow;</command> permits
10982 keys to be updated and the zone fully re-signed
10983 whenever the user issues the command <command>rndc sign
10984 <replaceable>zonename</replaceable></command>.
10987 <command>auto-dnssec maintain;</command> includes the
10988 above, but also automatically adjusts the zone's DNSSEC
10989 keys on schedule, according to the keys' timing metadata
10990 (see <xref linkend="man.dnssec-keygen"/> and
10991 <xref linkend="man.dnssec-settime"/>). The command
10993 <replaceable>zonename</replaceable></command> causes
10994 <command>named</command> to load keys from the key
10995 repository and sign the zone with all keys that are
10997 <command>rndc loadkeys
10998 <replaceable>zonename</replaceable></command> causes
10999 <command>named</command> to load keys from the key
11000 repository and schedule key maintenance events to occur
11001 in the future, but it does not sign the full zone
11002 immediately. Note: once keys have been loaded for a
11003 zone the first time, the repository will be searched
11004 for changes periodically, regardless of whether
11005 <command>rndc loadkeys</command> is used. The recheck
11006 interval is hard-coded to
11010 <command>auto-dnssec create;</command> includes the
11011 above, but also allows <command>named</command>
11012 to create new keys in the key repository when needed.
11013 (NOTE: This option is not yet implemented; the syntax is
11014 being reserved for future use.)
11017 The default setting is <command>auto-dnssec off</command>.
11023 <term><command>multi-master</command></term>
11026 See the description of <command>multi-master</command> in
11027 <xref linkend="boolean_options"/>.
11033 <term><command>masterfile-format</command></term>
11036 See the description of <command>masterfile-format</command>
11037 in <xref linkend="tuning"/>.
11043 <term><command>dnssec-secure-to-insecure</command></term>
11046 See the description of
11047 <command>dnssec-secure-to-insecure</command> in <xref linkend="boolean_options"/>.
11055 <sect3 id="dynamic_update_policies">
11056 <title>Dynamic Update Policies</title>
11057 <para><acronym>BIND</acronym> 9 supports two alternative
11058 methods of granting clients the right to perform
11059 dynamic updates to a zone, configured by the
11060 <command>allow-update</command> and
11061 <command>update-policy</command> option, respectively.
11064 The <command>allow-update</command> clause works the
11065 same way as in previous versions of <acronym>BIND</acronym>.
11066 It grants given clients the permission to update any
11067 record of any name in the zone.
11070 The <command>update-policy</command> clause
11071 allows more fine-grained control over what updates are
11072 allowed. A set of rules is specified, where each rule
11073 either grants or denies permissions for one or more
11074 names to be updated by one or more identities. If
11075 the dynamic update request message is signed (that is,
11076 it includes either a TSIG or SIG(0) record), the
11077 identity of the signer can be determined.
11080 Rules are specified in the <command>update-policy</command>
11081 zone option, and are only meaningful for master zones.
11082 When the <command>update-policy</command> statement
11083 is present, it is a configuration error for the
11084 <command>allow-update</command> statement to be
11085 present. The <command>update-policy</command> statement
11086 only examines the signer of a message; the source
11087 address is not relevant.
11090 There is a pre-defined <command>update-policy</command>
11091 rule which can be switched on with the command
11092 <command>update-policy local;</command>.
11093 Switching on this rule in a zone causes
11094 <command>named</command> to generate a TSIG session
11095 key and place it in a file, and to allow that key
11096 to update the zone. (By default, the file is
11097 <filename>/var/run/named/session.key</filename>, the key
11098 name is "local-ddns" and the key algorithm is HMAC-SHA256,
11099 but these values are configurable with the
11100 <command>session-keyfile</command>,
11101 <command>session-keyname</command> and
11102 <command>session-keyalg</command> options, respectively).
11105 A client running on the local system, and with appropriate
11106 permissions, may read that file and use the key to sign update
11107 requests. The zone's update policy will be set to allow that
11108 key to change any record within the zone. Assuming the
11109 key name is "local-ddns", this policy is equivalent to:
11112 <programlisting>update-policy { grant local-ddns zonesub any; };
11116 The command <command>nsupdate -l</command> sends update
11117 requests to localhost, and signs them using the session key.
11121 Other rule definitions look like this:
11125 ( <command>grant</command> | <command>deny</command> ) <replaceable>identity</replaceable> <replaceable>nametype</replaceable> <optional> <replaceable>name</replaceable> </optional> <optional> <replaceable>types</replaceable> </optional>
11129 Each rule grants or denies privileges. Once a message has
11130 successfully matched a rule, the operation is immediately
11131 granted or denied and no further rules are examined. A rule
11132 is matched when the signer matches the identity field, the
11133 name matches the name field in accordance with the nametype
11134 field, and the type matches the types specified in the type
11138 No signer is required for <replaceable>tcp-self</replaceable>
11139 or <replaceable>6to4-self</replaceable> however the standard
11140 reverse mapping / prefix conversion must match the identity
11144 The identity field specifies a name or a wildcard
11145 name. Normally, this is the name of the TSIG or
11146 SIG(0) key used to sign the update request. When a
11147 TKEY exchange has been used to create a shared secret,
11148 the identity of the shared secret is the same as the
11149 identity of the key used to authenticate the TKEY
11150 exchange. TKEY is also the negotiation method used
11151 by GSS-TSIG, which establishes an identity that is
11152 the Kerberos principal of the client, such as
11153 <userinput>"user@host.domain"</userinput>. When the
11154 <replaceable>identity</replaceable> field specifies
11155 a wildcard name, it is subject to DNS wildcard
11156 expansion, so the rule will apply to multiple identities.
11157 The <replaceable>identity</replaceable> field must
11158 contain a fully-qualified domain name.
11161 For nametypes <varname>krb5-self</varname>,
11162 <varname>ms-self</varname>, <varname>krb5-subdomain</varname>,
11163 and <varname>ms-subdomain</varname> the
11164 <replaceable>identity</replaceable> field specifies
11165 the Windows or Kerberos realm of the machine belongs to.
11168 The <replaceable>nametype</replaceable> field has 13
11170 <varname>name</varname>, <varname>subdomain</varname>,
11171 <varname>wildcard</varname>, <varname>self</varname>,
11172 <varname>selfsub</varname>, <varname>selfwild</varname>,
11173 <varname>krb5-self</varname>, <varname>ms-self</varname>,
11174 <varname>krb5-subdomain</varname>,
11175 <varname>ms-subdomain</varname>,
11176 <varname>tcp-self</varname>, <varname>6to4-self</varname>,
11177 <varname>zonesub</varname>, and <varname>external</varname>.
11180 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
11181 <colspec colname="1" colnum="1" colsep="0" colwidth="0.819in"/>
11182 <colspec colname="2" colnum="2" colsep="0" colwidth="3.681in"/>
11185 <entry colname="1">
11187 <varname>name</varname>
11189 </entry> <entry colname="2">
11191 Exact-match semantics. This rule matches
11192 when the name being updated is identical
11193 to the contents of the
11194 <replaceable>name</replaceable> field.
11199 <entry colname="1">
11201 <varname>subdomain</varname>
11203 </entry> <entry colname="2">
11205 This rule matches when the name being updated
11206 is a subdomain of, or identical to, the
11207 contents of the <replaceable>name</replaceable>
11213 <entry colname="1">
11215 <varname>zonesub</varname>
11217 </entry> <entry colname="2">
11219 This rule is similar to subdomain, except that
11220 it matches when the name being updated is a
11221 subdomain of the zone in which the
11222 <command>update-policy</command> statement
11223 appears. This obviates the need to type the zone
11224 name twice, and enables the use of a standard
11225 <command>update-policy</command> statement in
11226 multiple zones without modification.
11229 When this rule is used, the
11230 <replaceable>name</replaceable> field is omitted.
11235 <entry colname="1">
11237 <varname>wildcard</varname>
11239 </entry> <entry colname="2">
11241 The <replaceable>name</replaceable> field
11242 is subject to DNS wildcard expansion, and
11243 this rule matches when the name being updated
11244 name is a valid expansion of the wildcard.
11249 <entry colname="1">
11251 <varname>self</varname>
11254 <entry colname="2">
11256 This rule matches when the name being updated
11257 matches the contents of the
11258 <replaceable>identity</replaceable> field.
11259 The <replaceable>name</replaceable> field
11260 is ignored, but should be the same as the
11261 <replaceable>identity</replaceable> field.
11262 The <varname>self</varname> nametype is
11263 most useful when allowing using one key per
11264 name to update, where the key has the same
11265 name as the name to be updated. The
11266 <replaceable>identity</replaceable> would
11267 be specified as <constant>*</constant> (an asterisk) in
11273 <entry colname="1">
11275 <varname>selfsub</varname>
11277 </entry> <entry colname="2">
11279 This rule is similar to <varname>self</varname>
11280 except that subdomains of <varname>self</varname>
11281 can also be updated.
11286 <entry colname="1">
11288 <varname>selfwild</varname>
11290 </entry> <entry colname="2">
11292 This rule is similar to <varname>self</varname>
11293 except that only subdomains of
11294 <varname>self</varname> can be updated.
11299 <entry colname="1">
11301 <varname>ms-self</varname>
11303 </entry> <entry colname="2">
11305 This rule takes a Windows machine principal
11306 (machine$@REALM) for machine in REALM and
11307 and converts it machine.realm allowing the machine
11308 to update machine.realm. The REALM to be matched
11309 is specified in the <replaceable>identity</replaceable>
11315 <entry colname="1">
11317 <varname>ms-subdomain</varname>
11319 </entry> <entry colname="2">
11321 This rule takes a Windows machine principal
11322 (machine$@REALM) for machine in REALM and
11323 converts it to machine.realm allowing the machine
11324 to update subdomains of machine.realm. The REALM
11325 to be matched is specified in the
11326 <replaceable>identity</replaceable> field.
11331 <entry colname="1">
11333 <varname>krb5-self</varname>
11335 </entry> <entry colname="2">
11337 This rule takes a Kerberos machine principal
11338 (host/machine@REALM) for machine in REALM and
11339 and converts it machine.realm allowing the machine
11340 to update machine.realm. The REALM to be matched
11341 is specified in the <replaceable>identity</replaceable>
11347 <entry colname="1">
11349 <varname>krb5-subdomain</varname>
11351 </entry> <entry colname="2">
11353 This rule takes a Kerberos machine principal
11354 (host/machine@REALM) for machine in REALM and
11355 converts it to machine.realm allowing the machine
11356 to update subdomains of machine.realm. The REALM
11357 to be matched is specified in the
11358 <replaceable>identity</replaceable> field.
11363 <entry colname="1">
11365 <varname>tcp-self</varname>
11367 </entry> <entry colname="2">
11369 Allow updates that have been sent via TCP and
11370 for which the standard mapping from the initiating
11371 IP address into the IN-ADDR.ARPA and IP6.ARPA
11372 namespaces match the name to be updated.
11375 It is theoretically possible to spoof these TCP
11381 <entry colname="1">
11383 <varname>6to4-self</varname>
11385 </entry> <entry colname="2">
11387 Allow the 6to4 prefix to be update by any TCP
11388 connection from the 6to4 network or from the
11389 corresponding IPv4 address. This is intended
11390 to allow NS or DNAME RRsets to be added to the
11394 It is theoretically possible to spoof these TCP
11400 <entry colname="1">
11402 <varname>external</varname>
11404 </entry> <entry colname="2">
11406 This rule allows <command>named</command>
11407 to defer the decision of whether to allow a
11408 given update to an external daemon.
11411 The method of communicating with the daemon is
11412 specified in the <replaceable>identity</replaceable>
11413 field, the format of which is
11414 "<constant>local:</constant><replaceable>path</replaceable>",
11415 where <replaceable>path</replaceable> is the location
11416 of a UNIX-domain socket. (Currently, "local" is the
11417 only supported mechanism.)
11420 Requests to the external daemon are sent over the
11421 UNIX-domain socket as datagrams with the following
11425 Protocol version number (4 bytes, network byte order, currently 1)
11426 Request length (4 bytes, network byte order)
11427 Signer (null-terminated string)
11428 Name (null-terminated string)
11429 TCP source address (null-terminated string)
11430 Rdata type (null-terminated string)
11431 Key (null-terminated string)
11432 TKEY token length (4 bytes, network byte order)
11433 TKEY token (remainder of packet)</programlisting>
11435 The daemon replies with a four-byte value in
11436 network byte order, containing either 0 or 1; 0
11437 indicates that the specified update is not
11438 permitted, and 1 indicates that it is.
11447 In all cases, the <replaceable>name</replaceable>
11448 field must specify a fully-qualified domain name.
11452 If no types are explicitly specified, this rule matches
11453 all types except RRSIG, NS, SOA, NSEC and NSEC3. Types
11454 may be specified by name, including "ANY" (ANY matches
11455 all types except NSEC and NSEC3, which can never be
11456 updated). Note that when an attempt is made to delete
11457 all records associated with a name, the rules are
11458 checked for each existing record type.
11464 <title>Zone File</title>
11465 <sect2 id="types_of_resource_records_and_when_to_use_them">
11466 <title>Types of Resource Records and When to Use Them</title>
11468 This section, largely borrowed from RFC 1034, describes the
11469 concept of a Resource Record (RR) and explains when each is used.
11470 Since the publication of RFC 1034, several new RRs have been
11472 and implemented in the DNS. These are also included.
11475 <title>Resource Records</title>
11478 A domain name identifies a node. Each node has a set of
11479 resource information, which may be empty. The set of resource
11480 information associated with a particular name is composed of
11481 separate RRs. The order of RRs in a set is not significant and
11482 need not be preserved by name servers, resolvers, or other
11483 parts of the DNS. However, sorting of multiple RRs is
11484 permitted for optimization purposes, for example, to specify
11485 that a particular nearby server be tried first. See <xref linkend="the_sortlist_statement"/> and <xref linkend="rrset_ordering"/>.
11489 The components of a Resource Record are:
11491 <informaltable colsep="0" rowsep="0">
11492 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
11493 <colspec colname="1" colnum="1" colsep="0" colwidth="1.000in"/>
11494 <colspec colname="2" colnum="2" colsep="0" colwidth="3.500in"/>
11497 <entry colname="1">
11502 <entry colname="2">
11504 The domain name where the RR is found.
11509 <entry colname="1">
11514 <entry colname="2">
11516 An encoded 16-bit value that specifies
11517 the type of the resource record.
11522 <entry colname="1">
11527 <entry colname="2">
11529 The time-to-live of the RR. This field
11530 is a 32-bit integer in units of seconds, and is
11532 resolvers when they cache RRs. The TTL describes how
11534 be cached before it should be discarded.
11539 <entry colname="1">
11544 <entry colname="2">
11546 An encoded 16-bit value that identifies
11547 a protocol family or instance of a protocol.
11552 <entry colname="1">
11557 <entry colname="2">
11559 The resource data. The format of the
11560 data is type (and sometimes class) specific.
11568 The following are <emphasis>types</emphasis> of valid RRs:
11570 <informaltable colsep="0" rowsep="0">
11571 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
11572 <colspec colname="1" colnum="1" colsep="0" colwidth="0.875in"/>
11573 <colspec colname="2" colnum="2" colsep="0" colwidth="3.625in"/>
11576 <entry colname="1">
11581 <entry colname="2">
11583 A host address. In the IN class, this is a
11584 32-bit IP address. Described in RFC 1035.
11589 <entry colname="1">
11594 <entry colname="2">
11596 IPv6 address. Described in RFC 1886.
11601 <entry colname="1">
11606 <entry colname="2">
11608 IPv6 address. This can be a partial
11609 address (a suffix) and an indirection to the name
11610 where the rest of the
11611 address (the prefix) can be found. Experimental.
11612 Described in RFC 2874.
11617 <entry colname="1">
11622 <entry colname="2">
11624 Location of AFS database servers.
11625 Experimental. Described in RFC 1183.
11630 <entry colname="1">
11635 <entry colname="2">
11637 Address prefix list. Experimental.
11638 Described in RFC 3123.
11643 <entry colname="1">
11648 <entry colname="2">
11650 Holds a digital certificate.
11651 Described in RFC 2538.
11656 <entry colname="1">
11661 <entry colname="2">
11663 Identifies the canonical name of an alias.
11664 Described in RFC 1035.
11669 <entry colname="1">
11674 <entry colname="2">
11676 Is used for identifying which DHCP client is
11677 associated with this name. Described in RFC 4701.
11682 <entry colname="1">
11687 <entry colname="2">
11689 Replaces the domain name specified with
11690 another name to be looked up, effectively aliasing an
11692 subtree of the domain name space rather than a single
11694 as in the case of the CNAME RR.
11695 Described in RFC 2672.
11700 <entry colname="1">
11705 <entry colname="2">
11707 Stores a public key associated with a signed
11708 DNS zone. Described in RFC 4034.
11713 <entry colname="1">
11718 <entry colname="2">
11720 Stores the hash of a public key associated with a
11721 signed DNS zone. Described in RFC 4034.
11726 <entry colname="1">
11731 <entry colname="2">
11733 Specifies the global position. Superseded by LOC.
11738 <entry colname="1">
11743 <entry colname="2">
11745 Identifies the CPU and OS used by a host.
11746 Described in RFC 1035.
11751 <entry colname="1">
11756 <entry colname="2">
11758 Provides a method for storing IPsec keying material in
11759 DNS. Described in RFC 4025.
11764 <entry colname="1">
11769 <entry colname="2">
11771 Representation of ISDN addresses.
11772 Experimental. Described in RFC 1183.
11777 <entry colname="1">
11782 <entry colname="2">
11784 Stores a public key associated with a
11785 DNS name. Used in original DNSSEC; replaced
11786 by DNSKEY in DNSSECbis, but still used with
11787 SIG(0). Described in RFCs 2535 and 2931.
11792 <entry colname="1">
11797 <entry colname="2">
11799 Identifies a key exchanger for this
11800 DNS name. Described in RFC 2230.
11805 <entry colname="1">
11810 <entry colname="2">
11812 For storing GPS info. Described in RFC 1876.
11818 <entry colname="1">
11823 <entry colname="2">
11825 Identifies a mail exchange for the domain with
11826 a 16-bit preference value (lower is better)
11827 followed by the host name of the mail exchange.
11828 Described in RFC 974, RFC 1035.
11833 <entry colname="1">
11838 <entry colname="2">
11840 Name authority pointer. Described in RFC 2915.
11845 <entry colname="1">
11850 <entry colname="2">
11852 A network service access point.
11853 Described in RFC 1706.
11858 <entry colname="1">
11863 <entry colname="2">
11865 The authoritative name server for the
11866 domain. Described in RFC 1035.
11871 <entry colname="1">
11876 <entry colname="2">
11878 Used in DNSSECbis to securely indicate that
11879 RRs with an owner name in a certain name interval do
11881 a zone and indicate what RR types are present for an
11883 Described in RFC 4034.
11888 <entry colname="1">
11893 <entry colname="2">
11895 Used in DNSSECbis to securely indicate that
11896 RRs with an owner name in a certain name
11897 interval do not exist in a zone and indicate
11898 what RR types are present for an existing
11899 name. NSEC3 differs from NSEC in that it
11900 prevents zone enumeration but is more
11901 computationally expensive on both the server
11902 and the client than NSEC. Described in RFC
11908 <entry colname="1">
11913 <entry colname="2">
11915 Used in DNSSECbis to tell the authoritative
11916 server which NSEC3 chains are available to use.
11917 Described in RFC 5155.
11922 <entry colname="1">
11927 <entry colname="2">
11929 Used in DNSSEC to securely indicate that
11930 RRs with an owner name in a certain name interval do
11932 a zone and indicate what RR types are present for an
11934 Used in original DNSSEC; replaced by NSEC in
11936 Described in RFC 2535.
11941 <entry colname="1">
11946 <entry colname="2">
11948 A pointer to another part of the domain
11949 name space. Described in RFC 1035.
11954 <entry colname="1">
11959 <entry colname="2">
11961 Provides mappings between RFC 822 and X.400
11962 addresses. Described in RFC 2163.
11967 <entry colname="1">
11972 <entry colname="2">
11974 Information on persons responsible
11975 for the domain. Experimental. Described in RFC 1183.
11980 <entry colname="1">
11985 <entry colname="2">
11987 Contains DNSSECbis signature data. Described
11993 <entry colname="1">
11998 <entry colname="2">
12000 Route-through binding for hosts that
12001 do not have their own direct wide area network
12003 Experimental. Described in RFC 1183.
12008 <entry colname="1">
12013 <entry colname="2">
12015 Contains DNSSEC signature data. Used in
12016 original DNSSEC; replaced by RRSIG in
12017 DNSSECbis, but still used for SIG(0).
12018 Described in RFCs 2535 and 2931.
12023 <entry colname="1">
12028 <entry colname="2">
12030 Identifies the start of a zone of authority.
12031 Described in RFC 1035.
12036 <entry colname="1">
12041 <entry colname="2">
12043 Contains the Sender Policy Framework information
12044 for a given email domain. Described in RFC 4408.
12049 <entry colname="1">
12054 <entry colname="2">
12056 Information about well known network
12057 services (replaces WKS). Described in RFC 2782.
12062 <entry colname="1">
12067 <entry colname="2">
12069 Provides a way to securely publish a secure shell key's
12070 fingerprint. Described in RFC 4255.
12075 <entry colname="1">
12080 <entry colname="2">
12082 Text records. Described in RFC 1035.
12087 <entry colname="1">
12092 <entry colname="2">
12094 Information about which well known
12095 network services, such as SMTP, that a domain
12096 supports. Historical.
12101 <entry colname="1">
12106 <entry colname="2">
12108 Representation of X.25 network addresses.
12109 Experimental. Described in RFC 1183.
12117 The following <emphasis>classes</emphasis> of resource records
12118 are currently valid in the DNS:
12120 <informaltable colsep="0" rowsep="0"><tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
12121 <colspec colname="1" colnum="1" colsep="0" colwidth="0.875in"/>
12122 <colspec colname="2" colnum="2" colsep="0" colwidth="3.625in"/>
12126 <entry colname="1">
12131 <entry colname="2">
12139 <entry colname="1">
12144 <entry colname="2">
12146 Chaosnet, a LAN protocol created at MIT in the
12148 Rarely used for its historical purpose, but reused for
12150 built-in server information zones, e.g.,
12151 <literal>version.bind</literal>.
12157 <entry colname="1">
12162 <entry colname="2">
12164 Hesiod, an information service
12165 developed by MIT's Project Athena. It is used to share
12167 about various systems databases, such as users,
12179 The owner name is often implicit, rather than forming an
12181 part of the RR. For example, many name servers internally form
12183 or hash structures for the name space, and chain RRs off nodes.
12184 The remaining RR parts are the fixed header (type, class, TTL)
12185 which is consistent for all RRs, and a variable part (RDATA)
12187 fits the needs of the resource being described.
12190 The meaning of the TTL field is a time limit on how long an
12191 RR can be kept in a cache. This limit does not apply to
12193 data in zones; it is also timed out, but by the refreshing
12195 for the zone. The TTL is assigned by the administrator for the
12196 zone where the data originates. While short TTLs can be used to
12197 minimize caching, and a zero TTL prohibits caching, the
12199 of Internet performance suggest that these times should be on
12201 order of days for the typical host. If a change can be
12203 the TTL can be reduced prior to the change to minimize
12205 during the change, and then increased back to its former value
12210 The data in the RDATA section of RRs is carried as a combination
12211 of binary strings and domain names. The domain names are
12213 used as "pointers" to other data in the DNS.
12217 <title>Textual expression of RRs</title>
12219 RRs are represented in binary form in the packets of the DNS
12220 protocol, and are usually represented in highly encoded form
12222 stored in a name server or resolver. In the examples provided
12224 RFC 1034, a style similar to that used in master files was
12226 in order to show the contents of RRs. In this format, most RRs
12227 are shown on a single line, although continuation lines are
12232 The start of the line gives the owner of the RR. If a line
12233 begins with a blank, then the owner is assumed to be the same as
12234 that of the previous RR. Blank lines are often included for
12238 Following the owner, we list the TTL, type, and class of the
12239 RR. Class and type use the mnemonics defined above, and TTL is
12240 an integer before the type field. In order to avoid ambiguity
12242 parsing, type and class mnemonics are disjoint, TTLs are
12244 and the type mnemonic is always last. The IN class and TTL
12246 are often omitted from examples in the interests of clarity.
12249 The resource data or RDATA section of the RR are given using
12250 knowledge of the typical representation for the data.
12253 For example, we might show the RRs carried in a message as:
12255 <informaltable colsep="0" rowsep="0"><tgroup cols="3" colsep="0" rowsep="0" tgroupstyle="4Level-table">
12256 <colspec colname="1" colnum="1" colsep="0" colwidth="1.381in"/>
12257 <colspec colname="2" colnum="2" colsep="0" colwidth="1.020in"/>
12258 <colspec colname="3" colnum="3" colsep="0" colwidth="2.099in"/>
12261 <entry colname="1">
12263 <literal>ISI.EDU.</literal>
12266 <entry colname="2">
12268 <literal>MX</literal>
12271 <entry colname="3">
12273 <literal>10 VENERA.ISI.EDU.</literal>
12278 <entry colname="1">
12281 <entry colname="2">
12283 <literal>MX</literal>
12286 <entry colname="3">
12288 <literal>10 VAXA.ISI.EDU</literal>
12293 <entry colname="1">
12295 <literal>VENERA.ISI.EDU</literal>
12298 <entry colname="2">
12300 <literal>A</literal>
12303 <entry colname="3">
12305 <literal>128.9.0.32</literal>
12310 <entry colname="1">
12313 <entry colname="2">
12315 <literal>A</literal>
12318 <entry colname="3">
12320 <literal>10.1.0.52</literal>
12325 <entry colname="1">
12327 <literal>VAXA.ISI.EDU</literal>
12330 <entry colname="2">
12332 <literal>A</literal>
12335 <entry colname="3">
12337 <literal>10.2.0.27</literal>
12342 <entry colname="1">
12345 <entry colname="2">
12347 <literal>A</literal>
12350 <entry colname="3">
12352 <literal>128.9.0.33</literal>
12360 The MX RRs have an RDATA section which consists of a 16-bit
12361 number followed by a domain name. The address RRs use a
12363 IP address format to contain a 32-bit internet address.
12366 The above example shows six RRs, with two RRs at each of three
12370 Similarly we might see:
12372 <informaltable colsep="0" rowsep="0"><tgroup cols="3" colsep="0" rowsep="0" tgroupstyle="4Level-table">
12373 <colspec colname="1" colnum="1" colsep="0" colwidth="1.491in"/>
12374 <colspec colname="2" colnum="2" colsep="0" colwidth="1.067in"/>
12375 <colspec colname="3" colnum="3" colsep="0" colwidth="2.067in"/>
12378 <entry colname="1">
12380 <literal>XX.LCS.MIT.EDU.</literal>
12383 <entry colname="2">
12385 <literal>IN A</literal>
12388 <entry colname="3">
12390 <literal>10.0.0.44</literal>
12395 <entry colname="1"/>
12396 <entry colname="2">
12398 <literal>CH A</literal>
12401 <entry colname="3">
12403 <literal>MIT.EDU. 2420</literal>
12411 This example shows two addresses for
12412 <literal>XX.LCS.MIT.EDU</literal>, each of a different class.
12418 <title>Discussion of MX Records</title>
12421 As described above, domain servers store information as a
12422 series of resource records, each of which contains a particular
12423 piece of information about a given domain name (which is usually,
12424 but not always, a host). The simplest way to think of a RR is as
12425 a typed pair of data, a domain name matched with a relevant datum,
12426 and stored with some additional type information to help systems
12427 determine when the RR is relevant.
12431 MX records are used to control delivery of email. The data
12432 specified in the record is a priority and a domain name. The
12434 controls the order in which email delivery is attempted, with the
12435 lowest number first. If two priorities are the same, a server is
12436 chosen randomly. If no servers at a given priority are responding,
12437 the mail transport agent will fall back to the next largest
12439 Priority numbers do not have any absolute meaning — they are
12441 only respective to other MX records for that domain name. The
12443 name given is the machine to which the mail will be delivered.
12444 It <emphasis>must</emphasis> have an associated address record
12445 (A or AAAA) — CNAME is not sufficient.
12448 For a given domain, if there is both a CNAME record and an
12449 MX record, the MX record is in error, and will be ignored.
12451 the mail will be delivered to the server specified in the MX
12453 pointed to by the CNAME.
12456 <informaltable colsep="0" rowsep="0">
12457 <tgroup cols="5" colsep="0" rowsep="0" tgroupstyle="3Level-table">
12458 <colspec colname="1" colnum="1" colsep="0" colwidth="1.708in"/>
12459 <colspec colname="2" colnum="2" colsep="0" colwidth="0.444in"/>
12460 <colspec colname="3" colnum="3" colsep="0" colwidth="0.444in"/>
12461 <colspec colname="4" colnum="4" colsep="0" colwidth="0.976in"/>
12462 <colspec colname="5" colnum="5" colsep="0" colwidth="1.553in"/>
12465 <entry colname="1">
12467 <literal>example.com.</literal>
12470 <entry colname="2">
12472 <literal>IN</literal>
12475 <entry colname="3">
12477 <literal>MX</literal>
12480 <entry colname="4">
12482 <literal>10</literal>
12485 <entry colname="5">
12487 <literal>mail.example.com.</literal>
12492 <entry colname="1">
12495 <entry colname="2">
12497 <literal>IN</literal>
12500 <entry colname="3">
12502 <literal>MX</literal>
12505 <entry colname="4">
12507 <literal>10</literal>
12510 <entry colname="5">
12512 <literal>mail2.example.com.</literal>
12517 <entry colname="1">
12520 <entry colname="2">
12522 <literal>IN</literal>
12525 <entry colname="3">
12527 <literal>MX</literal>
12530 <entry colname="4">
12532 <literal>20</literal>
12535 <entry colname="5">
12537 <literal>mail.backup.org.</literal>
12542 <entry colname="1">
12544 <literal>mail.example.com.</literal>
12547 <entry colname="2">
12549 <literal>IN</literal>
12552 <entry colname="3">
12554 <literal>A</literal>
12557 <entry colname="4">
12559 <literal>10.0.0.1</literal>
12562 <entry colname="5">
12567 <entry colname="1">
12569 <literal>mail2.example.com.</literal>
12572 <entry colname="2">
12574 <literal>IN</literal>
12577 <entry colname="3">
12579 <literal>A</literal>
12582 <entry colname="4">
12584 <literal>10.0.0.2</literal>
12587 <entry colname="5">
12593 </informaltable><para>
12594 Mail delivery will be attempted to <literal>mail.example.com</literal> and
12595 <literal>mail2.example.com</literal> (in
12596 any order), and if neither of those succeed, delivery to <literal>mail.backup.org</literal> will
12600 <sect2 id="Setting_TTLs">
12601 <title>Setting TTLs</title>
12603 The time-to-live of the RR field is a 32-bit integer represented
12604 in units of seconds, and is primarily used by resolvers when they
12605 cache RRs. The TTL describes how long a RR can be cached before it
12606 should be discarded. The following three types of TTL are
12608 used in a zone file.
12610 <informaltable colsep="0" rowsep="0">
12611 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table">
12612 <colspec colname="1" colnum="1" colsep="0" colwidth="0.750in"/>
12613 <colspec colname="2" colnum="2" colsep="0" colwidth="4.375in"/>
12616 <entry colname="1">
12621 <entry colname="2">
12623 The last field in the SOA is the negative
12624 caching TTL. This controls how long other servers will
12625 cache no-such-domain
12626 (NXDOMAIN) responses from you.
12629 The maximum time for
12630 negative caching is 3 hours (3h).
12635 <entry colname="1">
12640 <entry colname="2">
12642 The $TTL directive at the top of the
12643 zone file (before the SOA) gives a default TTL for every
12645 a specific TTL set.
12650 <entry colname="1">
12655 <entry colname="2">
12657 Each RR can have a TTL as the second
12658 field in the RR, which will control how long other
12668 All of these TTLs default to units of seconds, though units
12669 can be explicitly specified, for example, <literal>1h30m</literal>.
12673 <title>Inverse Mapping in IPv4</title>
12675 Reverse name resolution (that is, translation from IP address
12676 to name) is achieved by means of the <emphasis>in-addr.arpa</emphasis> domain
12677 and PTR records. Entries in the in-addr.arpa domain are made in
12678 least-to-most significant order, read left to right. This is the
12679 opposite order to the way IP addresses are usually written. Thus,
12680 a machine with an IP address of 10.1.2.3 would have a
12682 in-addr.arpa name of
12683 3.2.1.10.in-addr.arpa. This name should have a PTR resource record
12684 whose data field is the name of the machine or, optionally,
12686 PTR records if the machine has more than one name. For example,
12687 in the <optional>example.com</optional> domain:
12689 <informaltable colsep="0" rowsep="0">
12690 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table">
12691 <colspec colname="1" colnum="1" colsep="0" colwidth="1.125in"/>
12692 <colspec colname="2" colnum="2" colsep="0" colwidth="4.000in"/>
12695 <entry colname="1">
12697 <literal>$ORIGIN</literal>
12700 <entry colname="2">
12702 <literal>2.1.10.in-addr.arpa</literal>
12707 <entry colname="1">
12709 <literal>3</literal>
12712 <entry colname="2">
12714 <literal>IN PTR foo.example.com.</literal>
12723 The <command>$ORIGIN</command> lines in the examples
12724 are for providing context to the examples only — they do not
12726 appear in the actual usage. They are only used here to indicate
12727 that the example is relative to the listed origin.
12732 <title>Other Zone File Directives</title>
12734 The Master File Format was initially defined in RFC 1035 and
12735 has subsequently been extended. While the Master File Format
12737 is class independent all records in a Master File must be of the
12742 Master File Directives include <command>$ORIGIN</command>, <command>$INCLUDE</command>,
12743 and <command>$TTL.</command>
12746 <title>The <command>@</command> (at-sign)</title>
12748 When used in the label (or name) field, the asperand or
12749 at-sign (@) symbol represents the current origin.
12750 At the start of the zone file, it is the
12751 <<varname>zone_name</varname>> (followed by
12756 <title>The <command>$ORIGIN</command> Directive</title>
12758 Syntax: <command>$ORIGIN</command>
12759 <replaceable>domain-name</replaceable>
12760 <optional><replaceable>comment</replaceable></optional>
12762 <para><command>$ORIGIN</command>
12763 sets the domain name that will be appended to any
12764 unqualified records. When a zone is first read in there
12765 is an implicit <command>$ORIGIN</command>
12766 <<varname>zone_name</varname>><command>.</command>
12767 (followed by trailing dot).
12768 The current <command>$ORIGIN</command> is appended to
12769 the domain specified in the <command>$ORIGIN</command>
12770 argument if it is not absolute.
12774 $ORIGIN example.com.
12775 WWW CNAME MAIN-SERVER
12783 WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
12788 <title>The <command>$INCLUDE</command> Directive</title>
12790 Syntax: <command>$INCLUDE</command>
12791 <replaceable>filename</replaceable>
12793 <replaceable>origin</replaceable> </optional>
12794 <optional> <replaceable>comment</replaceable> </optional>
12797 Read and process the file <filename>filename</filename> as
12798 if it were included into the file at this point. If <command>origin</command> is
12799 specified the file is processed with <command>$ORIGIN</command> set
12800 to that value, otherwise the current <command>$ORIGIN</command> is
12804 The origin and the current domain name
12805 revert to the values they had prior to the <command>$INCLUDE</command> once
12806 the file has been read.
12810 RFC 1035 specifies that the current origin should be restored
12812 an <command>$INCLUDE</command>, but it is silent
12813 on whether the current
12814 domain name should also be restored. BIND 9 restores both of
12816 This could be construed as a deviation from RFC 1035, a
12822 <title>The <command>$TTL</command> Directive</title>
12824 Syntax: <command>$TTL</command>
12825 <replaceable>default-ttl</replaceable>
12827 <replaceable>comment</replaceable> </optional>
12830 Set the default Time To Live (TTL) for subsequent records
12831 with undefined TTLs. Valid TTLs are of the range 0-2147483647
12834 <para><command>$TTL</command>
12835 is defined in RFC 2308.
12840 <title><acronym>BIND</acronym> Master File Extension: the <command>$GENERATE</command> Directive</title>
12842 Syntax: <command>$GENERATE</command>
12843 <replaceable>range</replaceable>
12844 <replaceable>lhs</replaceable>
12845 <optional><replaceable>ttl</replaceable></optional>
12846 <optional><replaceable>class</replaceable></optional>
12847 <replaceable>type</replaceable>
12848 <replaceable>rhs</replaceable>
12849 <optional><replaceable>comment</replaceable></optional>
12851 <para><command>$GENERATE</command>
12852 is used to create a series of resource records that only
12853 differ from each other by an
12854 iterator. <command>$GENERATE</command> can be used to
12855 easily generate the sets of records required to support
12856 sub /24 reverse delegations described in RFC 2317:
12857 Classless IN-ADDR.ARPA delegation.
12860 <programlisting>$ORIGIN 0.0.192.IN-ADDR.ARPA.
12861 $GENERATE 1-2 @ NS SERVER$.EXAMPLE.
12862 $GENERATE 1-127 $ CNAME $.0</programlisting>
12868 <programlisting>0.0.0.192.IN-ADDR.ARPA. NS SERVER1.EXAMPLE.
12869 0.0.0.192.IN-ADDR.ARPA. NS SERVER2.EXAMPLE.
12870 1.0.0.192.IN-ADDR.ARPA. CNAME 1.0.0.0.192.IN-ADDR.ARPA.
12871 2.0.0.192.IN-ADDR.ARPA. CNAME 2.0.0.0.192.IN-ADDR.ARPA.
12873 127.0.0.192.IN-ADDR.ARPA. CNAME 127.0.0.0.192.IN-ADDR.ARPA.
12877 Generate a set of A and MX records. Note the MX's right hand
12878 side is a quoted string. The quotes will be stripped when the
12879 right hand side is processed.
12884 $GENERATE 1-127 HOST-$ A 1.2.3.$
12885 $GENERATE 1-127 HOST-$ MX "0 ."</programlisting>
12891 <programlisting>HOST-1.EXAMPLE. A 1.2.3.1
12892 HOST-1.EXAMPLE. MX 0 .
12893 HOST-2.EXAMPLE. A 1.2.3.2
12894 HOST-2.EXAMPLE. MX 0 .
12895 HOST-3.EXAMPLE. A 1.2.3.3
12896 HOST-3.EXAMPLE. MX 0 .
12898 HOST-127.EXAMPLE. A 1.2.3.127
12899 HOST-127.EXAMPLE. MX 0 .
12902 <informaltable colsep="0" rowsep="0">
12903 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="3Level-table">
12904 <colspec colname="1" colnum="1" colsep="0" colwidth="0.875in"/>
12905 <colspec colname="2" colnum="2" colsep="0" colwidth="4.250in"/>
12908 <entry colname="1">
12909 <para><command>range</command></para>
12911 <entry colname="2">
12913 This can be one of two forms: start-stop
12914 or start-stop/step. If the first form is used, then step
12916 1. All of start, stop and step must be positive.
12921 <entry colname="1">
12922 <para><command>lhs</command></para>
12924 <entry colname="2">
12926 describes the owner name of the resource records
12927 to be created. Any single <command>$</command>
12929 symbols within the <command>lhs</command> string
12930 are replaced by the iterator value.
12932 To get a $ in the output, you need to escape the
12933 <command>$</command> using a backslash
12934 <command>\</command>,
12935 e.g. <command>\$</command>. The
12936 <command>$</command> may optionally be followed
12937 by modifiers which change the offset from the
12938 iterator, field width and base.
12940 Modifiers are introduced by a
12941 <command>{</command> (left brace) immediately following the
12942 <command>$</command> as
12943 <command>${offset[,width[,base]]}</command>.
12944 For example, <command>${-20,3,d}</command>
12945 subtracts 20 from the current value, prints the
12946 result as a decimal in a zero-padded field of
12949 Available output forms are decimal
12950 (<command>d</command>), octal
12951 (<command>o</command>), hexadecimal
12952 (<command>x</command> or <command>X</command>
12953 for uppercase) and nibble
12954 (<command>n</command> or <command>N</command>\
12955 for uppercase). The default modifier is
12956 <command>${0,0,d}</command>. If the
12957 <command>lhs</command> is not absolute, the
12958 current <command>$ORIGIN</command> is appended
12962 In nibble mode the value will be treated as
12963 if it was a reversed hexadecimal string
12964 with each hexadecimal digit as a separate
12965 label. The width field includes the label
12969 For compatibility with earlier versions,
12970 <command>$$</command> is still recognized as
12971 indicating a literal $ in the output.
12976 <entry colname="1">
12977 <para><command>ttl</command></para>
12979 <entry colname="2">
12981 Specifies the time-to-live of the generated records. If
12982 not specified this will be inherited using the
12983 normal TTL inheritance rules.
12985 <para><command>class</command>
12986 and <command>ttl</command> can be
12987 entered in either order.
12992 <entry colname="1">
12993 <para><command>class</command></para>
12995 <entry colname="2">
12997 Specifies the class of the generated records.
12998 This must match the zone class if it is
13001 <para><command>class</command>
13002 and <command>ttl</command> can be
13003 entered in either order.
13008 <entry colname="1">
13009 <para><command>type</command></para>
13011 <entry colname="2">
13018 <entry colname="1">
13019 <para><command>rhs</command></para>
13021 <entry colname="2">
13023 <command>rhs</command>, optionally, quoted string.
13031 The <command>$GENERATE</command> directive is a <acronym>BIND</acronym> extension
13032 and not part of the standard zone file format.
13035 BIND 8 does not support the optional TTL and CLASS fields.
13039 <sect2 id="zonefile_format">
13040 <title>Additional File Formats</title>
13042 In addition to the standard textual format, BIND 9
13043 supports the ability to read or dump to zone files in
13044 other formats. The <constant>raw</constant> format is
13045 currently available as an additional format. It is a
13046 binary format representing BIND 9's internal data
13047 structure directly, thereby remarkably improving the
13051 For a primary server, a zone file in the
13052 <constant>raw</constant> format is expected to be
13053 generated from a textual zone file by the
13054 <command>named-compilezone</command> command. For a
13055 secondary server or for a dynamic zone, it is automatically
13056 generated (if this format is specified by the
13057 <command>masterfile-format</command> option) when
13058 <command>named</command> dumps the zone contents after
13059 zone transfer or when applying prior updates.
13062 If a zone file in a binary format needs manual modification,
13063 it first must be converted to a textual form by the
13064 <command>named-compilezone</command> command. All
13065 necessary modification should go to the text file, which
13066 should then be converted to the binary form by the
13067 <command>named-compilezone</command> command again.
13070 Although the <constant>raw</constant> format uses the
13071 network byte order and avoids architecture-dependent
13072 data alignment so that it is as much portable as
13073 possible, it is primarily expected to be used inside
13074 the same single system. In order to export a zone
13075 file in the <constant>raw</constant> format or make a
13076 portable backup of the file, it is recommended to
13077 convert the file to the standard textual representation.
13082 <sect1 id="statistics">
13083 <title>BIND9 Statistics</title>
13085 <acronym>BIND</acronym> 9 maintains lots of statistics
13086 information and provides several interfaces for users to
13087 get access to the statistics.
13088 The available statistics include all statistics counters
13089 that were available in <acronym>BIND</acronym> 8 and
13090 are meaningful in <acronym>BIND</acronym> 9,
13091 and other information that is considered useful.
13095 The statistics information is categorized into the following
13099 <informaltable frame="all">
13101 <colspec colname="1" colnum="1" colsep="0" colwidth="3.300in"/>
13102 <colspec colname="2" colnum="2" colsep="0" colwidth="2.625in"/>
13106 <entry colname="1">
13107 <para>Incoming Requests</para>
13109 <entry colname="2">
13111 The number of incoming DNS requests for each OPCODE.
13117 <entry colname="1">
13118 <para>Incoming Queries</para>
13120 <entry colname="2">
13122 The number of incoming queries for each RR type.
13128 <entry colname="1">
13129 <para>Outgoing Queries</para>
13131 <entry colname="2">
13133 The number of outgoing queries for each RR
13134 type sent from the internal resolver.
13135 Maintained per view.
13141 <entry colname="1">
13142 <para>Name Server Statistics</para>
13144 <entry colname="2">
13146 Statistics counters about incoming request processing.
13152 <entry colname="1">
13153 <para>Zone Maintenance Statistics</para>
13155 <entry colname="2">
13157 Statistics counters regarding zone maintenance
13158 operations such as zone transfers.
13164 <entry colname="1">
13165 <para>Resolver Statistics</para>
13167 <entry colname="2">
13169 Statistics counters about name resolution
13170 performed in the internal resolver.
13171 Maintained per view.
13177 <entry colname="1">
13178 <para>Cache DB RRsets</para>
13180 <entry colname="2">
13182 The number of RRsets per RR type and nonexistent
13183 names stored in the cache database.
13184 If the exclamation mark (!) is printed for a RR
13185 type, it means that particular type of RRset is
13186 known to be nonexistent (this is also known as
13188 Maintained per view.
13194 <entry colname="1">
13195 <para>Socket I/O Statistics</para>
13197 <entry colname="2">
13199 Statistics counters about network related events.
13209 A subset of Name Server Statistics is collected and shown
13210 per zone for which the server has the authority when
13211 <command>zone-statistics</command> is set to
13212 <userinput>yes</userinput>.
13213 These statistics counters are shown with their zone and view
13215 In some cases the view names are omitted for the default view.
13219 There are currently two user interfaces to get access to the
13221 One is in the plain text format dumped to the file specified
13222 by the <command>statistics-file</command> configuration option.
13223 The other is remotely accessible via a statistics channel
13224 when the <command>statistics-channels</command> statement
13225 is specified in the configuration file
13226 (see <xref linkend="statschannels"/>.)
13229 <sect3 id="statsfile">
13230 <title>The Statistics File</title>
13232 The text format statistics dump begins with a line, like:
13235 <command>+++ Statistics Dump +++ (973798949)</command>
13238 The number in parentheses is a standard
13239 Unix-style timestamp, measured as seconds since January 1, 1970.
13242 that line is a set of statistics information, which is categorized
13243 as described above.
13244 Each section begins with a line, like:
13248 <command>++ Name Server Statistics ++</command>
13252 Each section consists of lines, each containing the statistics
13253 counter value followed by its textual description.
13254 See below for available counters.
13255 For brevity, counters that have a value of 0 are not shown
13256 in the statistics file.
13260 The statistics dump ends with the line where the
13261 number is identical to the number in the beginning line; for example:
13264 <command>--- Statistics Dump --- (973798949)</command>
13268 <sect2 id="statistics_counters">
13269 <title>Statistics Counters</title>
13271 The following tables summarize statistics counters that
13272 <acronym>BIND</acronym> 9 provides.
13273 For each row of the tables, the leftmost column is the
13274 abbreviated symbol name of that counter.
13275 These symbols are shown in the statistics information
13276 accessed via an HTTP statistics channel.
13277 The rightmost column gives the description of the counter,
13278 which is also shown in the statistics file
13279 (but, in this document, possibly with slight modification
13280 for better readability).
13281 Additional notes may also be provided in this column.
13282 When a middle column exists between these two columns,
13283 it gives the corresponding counter name of the
13284 <acronym>BIND</acronym> 8 statistics, if applicable.
13288 <title>Name Server Statistics Counters</title>
13290 <informaltable colsep="0" rowsep="0">
13291 <tgroup cols="3" colsep="0" rowsep="0" tgroupstyle="4Level-table">
13292 <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
13293 <colspec colname="2" colnum="2" colsep="0" colwidth="1.150in"/>
13294 <colspec colname="3" colnum="3" colsep="0" colwidth="3.350in"/>
13297 <entry colname="1">
13299 <emphasis>Symbol</emphasis>
13302 <entry colname="2">
13304 <emphasis>BIND8 Symbol</emphasis>
13307 <entry colname="3">
13309 <emphasis>Description</emphasis>
13315 <entry colname="1">
13316 <para><command>Requestv4</command></para>
13318 <entry colname="2">
13319 <para><command>RQ</command></para>
13321 <entry colname="3">
13323 IPv4 requests received.
13324 Note: this also counts non query requests.
13329 <entry colname="1">
13330 <para><command>Requestv6</command></para>
13332 <entry colname="2">
13333 <para><command>RQ</command></para>
13335 <entry colname="3">
13337 IPv6 requests received.
13338 Note: this also counts non query requests.
13343 <entry colname="1">
13344 <para><command>ReqEdns0</command></para>
13346 <entry colname="2">
13347 <para><command></command></para>
13349 <entry colname="3">
13351 Requests with EDNS(0) received.
13356 <entry colname="1">
13357 <para><command>ReqBadEDNSVer</command></para>
13359 <entry colname="2">
13360 <para><command></command></para>
13362 <entry colname="3">
13364 Requests with unsupported EDNS version received.
13369 <entry colname="1">
13370 <para><command>ReqTSIG</command></para>
13372 <entry colname="2">
13373 <para><command></command></para>
13375 <entry colname="3">
13377 Requests with TSIG received.
13382 <entry colname="1">
13383 <para><command>ReqSIG0</command></para>
13385 <entry colname="2">
13386 <para><command></command></para>
13388 <entry colname="3">
13390 Requests with SIG(0) received.
13395 <entry colname="1">
13396 <para><command>ReqBadSIG</command></para>
13398 <entry colname="2">
13399 <para><command></command></para>
13401 <entry colname="3">
13403 Requests with invalid (TSIG or SIG(0)) signature.
13408 <entry colname="1">
13409 <para><command>ReqTCP</command></para>
13411 <entry colname="2">
13412 <para><command>RTCP</command></para>
13414 <entry colname="3">
13416 TCP requests received.
13421 <entry colname="1">
13422 <para><command>AuthQryRej</command></para>
13424 <entry colname="2">
13425 <para><command>RUQ</command></para>
13427 <entry colname="3">
13429 Authoritative (non recursive) queries rejected.
13434 <entry colname="1">
13435 <para><command>RecQryRej</command></para>
13437 <entry colname="2">
13438 <para><command>RURQ</command></para>
13440 <entry colname="3">
13442 Recursive queries rejected.
13447 <entry colname="1">
13448 <para><command>XfrRej</command></para>
13450 <entry colname="2">
13451 <para><command>RUXFR</command></para>
13453 <entry colname="3">
13455 Zone transfer requests rejected.
13460 <entry colname="1">
13461 <para><command>UpdateRej</command></para>
13463 <entry colname="2">
13464 <para><command>RUUpd</command></para>
13466 <entry colname="3">
13468 Dynamic update requests rejected.
13473 <entry colname="1">
13474 <para><command>Response</command></para>
13476 <entry colname="2">
13477 <para><command>SAns</command></para>
13479 <entry colname="3">
13486 <entry colname="1">
13487 <para><command>RespTruncated</command></para>
13489 <entry colname="2">
13490 <para><command></command></para>
13492 <entry colname="3">
13494 Truncated responses sent.
13499 <entry colname="1">
13500 <para><command>RespEDNS0</command></para>
13502 <entry colname="2">
13503 <para><command></command></para>
13505 <entry colname="3">
13507 Responses with EDNS(0) sent.
13512 <entry colname="1">
13513 <para><command>RespTSIG</command></para>
13515 <entry colname="2">
13516 <para><command></command></para>
13518 <entry colname="3">
13520 Responses with TSIG sent.
13525 <entry colname="1">
13526 <para><command>RespSIG0</command></para>
13528 <entry colname="2">
13529 <para><command></command></para>
13531 <entry colname="3">
13533 Responses with SIG(0) sent.
13538 <entry colname="1">
13539 <para><command>QrySuccess</command></para>
13541 <entry colname="2">
13542 <para><command></command></para>
13544 <entry colname="3">
13546 Queries resulted in a successful answer.
13547 This means the query which returns a NOERROR response
13548 with at least one answer RR.
13549 This corresponds to the
13550 <command>success</command> counter
13551 of previous versions of
13552 <acronym>BIND</acronym> 9.
13557 <entry colname="1">
13558 <para><command>QryAuthAns</command></para>
13560 <entry colname="2">
13561 <para><command></command></para>
13563 <entry colname="3">
13565 Queries resulted in authoritative answer.
13570 <entry colname="1">
13571 <para><command>QryNoauthAns</command></para>
13573 <entry colname="2">
13574 <para><command>SNaAns</command></para>
13576 <entry colname="3">
13578 Queries resulted in non authoritative answer.
13583 <entry colname="1">
13584 <para><command>QryReferral</command></para>
13586 <entry colname="2">
13587 <para><command></command></para>
13589 <entry colname="3">
13591 Queries resulted in referral answer.
13592 This corresponds to the
13593 <command>referral</command> counter
13594 of previous versions of
13595 <acronym>BIND</acronym> 9.
13600 <entry colname="1">
13601 <para><command>QryNxrrset</command></para>
13603 <entry colname="2">
13604 <para><command></command></para>
13606 <entry colname="3">
13608 Queries resulted in NOERROR responses with no data.
13609 This corresponds to the
13610 <command>nxrrset</command> counter
13611 of previous versions of
13612 <acronym>BIND</acronym> 9.
13617 <entry colname="1">
13618 <para><command>QrySERVFAIL</command></para>
13620 <entry colname="2">
13621 <para><command>SFail</command></para>
13623 <entry colname="3">
13625 Queries resulted in SERVFAIL.
13630 <entry colname="1">
13631 <para><command>QryFORMERR</command></para>
13633 <entry colname="2">
13634 <para><command>SFErr</command></para>
13636 <entry colname="3">
13638 Queries resulted in FORMERR.
13643 <entry colname="1">
13644 <para><command>QryNXDOMAIN</command></para>
13646 <entry colname="2">
13647 <para><command>SNXD</command></para>
13649 <entry colname="3">
13651 Queries resulted in NXDOMAIN.
13652 This corresponds to the
13653 <command>nxdomain</command> counter
13654 of previous versions of
13655 <acronym>BIND</acronym> 9.
13660 <entry colname="1">
13661 <para><command>QryRecursion</command></para>
13663 <entry colname="2">
13664 <para><command>RFwdQ</command></para>
13666 <entry colname="3">
13668 Queries which caused the server
13669 to perform recursion in order to find the final answer.
13670 This corresponds to the
13671 <command>recursion</command> counter
13672 of previous versions of
13673 <acronym>BIND</acronym> 9.
13678 <entry colname="1">
13679 <para><command>QryDuplicate</command></para>
13681 <entry colname="2">
13682 <para><command>RDupQ</command></para>
13684 <entry colname="3">
13686 Queries which the server attempted to
13687 recurse but discovered an existing query with the same
13688 IP address, port, query ID, name, type and class
13689 already being processed.
13690 This corresponds to the
13691 <command>duplicate</command> counter
13692 of previous versions of
13693 <acronym>BIND</acronym> 9.
13698 <entry colname="1">
13699 <para><command>QryDropped</command></para>
13701 <entry colname="2">
13702 <para><command></command></para>
13704 <entry colname="3">
13706 Recursive queries for which the server
13707 discovered an excessive number of existing
13708 recursive queries for the same name, type and
13709 class and were subsequently dropped.
13710 This is the number of dropped queries due to
13711 the reason explained with the
13712 <command>clients-per-query</command>
13714 <command>max-clients-per-query</command>
13716 (see the description about
13717 <xref linkend="clients-per-query"/>.)
13718 This corresponds to the
13719 <command>dropped</command> counter
13720 of previous versions of
13721 <acronym>BIND</acronym> 9.
13726 <entry colname="1">
13727 <para><command>QryFailure</command></para>
13729 <entry colname="2">
13730 <para><command></command></para>
13732 <entry colname="3">
13734 Other query failures.
13735 This corresponds to the
13736 <command>failure</command> counter
13737 of previous versions of
13738 <acronym>BIND</acronym> 9.
13739 Note: this counter is provided mainly for
13740 backward compatibility with the previous versions.
13741 Normally a more fine-grained counters such as
13742 <command>AuthQryRej</command> and
13743 <command>RecQryRej</command>
13744 that would also fall into this counter are provided,
13745 and so this counter would not be of much
13746 interest in practice.
13751 <entry colname="1">
13752 <para><command>XfrReqDone</command></para>
13754 <entry colname="2">
13755 <para><command></command></para>
13757 <entry colname="3">
13759 Requested zone transfers completed.
13764 <entry colname="1">
13765 <para><command>UpdateReqFwd</command></para>
13767 <entry colname="2">
13768 <para><command></command></para>
13770 <entry colname="3">
13772 Update requests forwarded.
13777 <entry colname="1">
13778 <para><command>UpdateRespFwd</command></para>
13780 <entry colname="2">
13781 <para><command></command></para>
13783 <entry colname="3">
13785 Update responses forwarded.
13790 <entry colname="1">
13791 <para><command>UpdateFwdFail</command></para>
13793 <entry colname="2">
13794 <para><command></command></para>
13796 <entry colname="3">
13798 Dynamic update forward failed.
13803 <entry colname="1">
13804 <para><command>UpdateDone</command></para>
13806 <entry colname="2">
13807 <para><command></command></para>
13809 <entry colname="3">
13811 Dynamic updates completed.
13816 <entry colname="1">
13817 <para><command>UpdateFail</command></para>
13819 <entry colname="2">
13820 <para><command></command></para>
13822 <entry colname="3">
13824 Dynamic updates failed.
13829 <entry colname="1">
13830 <para><command>UpdateBadPrereq</command></para>
13832 <entry colname="2">
13833 <para><command></command></para>
13835 <entry colname="3">
13837 Dynamic updates rejected due to prerequisite failure.
13842 <entry colname="1">
13843 <para><command>RPZRewrites</command></para>
13845 <entry colname="2">
13846 <para><command></command></para>
13848 <entry colname="3">
13850 Response policy zone rewrites.
13860 <title>Zone Maintenance Statistics Counters</title>
13862 <informaltable colsep="0" rowsep="0">
13863 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
13864 <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
13865 <colspec colname="2" colnum="2" colsep="0" colwidth="3.350in"/>
13868 <entry colname="1">
13870 <emphasis>Symbol</emphasis>
13873 <entry colname="2">
13875 <emphasis>Description</emphasis>
13881 <entry colname="1">
13882 <para><command>NotifyOutv4</command></para>
13884 <entry colname="2">
13886 IPv4 notifies sent.
13891 <entry colname="1">
13892 <para><command>NotifyOutv6</command></para>
13894 <entry colname="2">
13896 IPv6 notifies sent.
13901 <entry colname="1">
13902 <para><command>NotifyInv4</command></para>
13904 <entry colname="2">
13906 IPv4 notifies received.
13911 <entry colname="1">
13912 <para><command>NotifyInv6</command></para>
13914 <entry colname="2">
13916 IPv6 notifies received.
13921 <entry colname="1">
13922 <para><command>NotifyRej</command></para>
13924 <entry colname="2">
13926 Incoming notifies rejected.
13931 <entry colname="1">
13932 <para><command>SOAOutv4</command></para>
13934 <entry colname="2">
13936 IPv4 SOA queries sent.
13941 <entry colname="1">
13942 <para><command>SOAOutv6</command></para>
13944 <entry colname="2">
13946 IPv6 SOA queries sent.
13951 <entry colname="1">
13952 <para><command>AXFRReqv4</command></para>
13954 <entry colname="2">
13956 IPv4 AXFR requested.
13961 <entry colname="1">
13962 <para><command>AXFRReqv6</command></para>
13964 <entry colname="2">
13966 IPv6 AXFR requested.
13971 <entry colname="1">
13972 <para><command>IXFRReqv4</command></para>
13974 <entry colname="2">
13976 IPv4 IXFR requested.
13981 <entry colname="1">
13982 <para><command>IXFRReqv6</command></para>
13984 <entry colname="2">
13986 IPv6 IXFR requested.
13991 <entry colname="1">
13992 <para><command>XfrSuccess</command></para>
13994 <entry colname="2">
13996 Zone transfer requests succeeded.
14001 <entry colname="1">
14002 <para><command>XfrFail</command></para>
14004 <entry colname="2">
14006 Zone transfer requests failed.
14016 <title>Resolver Statistics Counters</title>
14018 <informaltable colsep="0" rowsep="0">
14019 <tgroup cols="3" colsep="0" rowsep="0" tgroupstyle="4Level-table">
14020 <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
14021 <colspec colname="2" colnum="2" colsep="0" colwidth="1.150in"/>
14022 <colspec colname="3" colnum="3" colsep="0" colwidth="3.350in"/>
14025 <entry colname="1">
14027 <emphasis>Symbol</emphasis>
14030 <entry colname="2">
14032 <emphasis>BIND8 Symbol</emphasis>
14035 <entry colname="3">
14037 <emphasis>Description</emphasis>
14043 <entry colname="1">
14044 <para><command>Queryv4</command></para>
14046 <entry colname="2">
14047 <para><command>SFwdQ</command></para>
14049 <entry colname="3">
14056 <entry colname="1">
14057 <para><command>Queryv6</command></para>
14059 <entry colname="2">
14060 <para><command>SFwdQ</command></para>
14062 <entry colname="3">
14069 <entry colname="1">
14070 <para><command>Responsev4</command></para>
14072 <entry colname="2">
14073 <para><command>RR</command></para>
14075 <entry colname="3">
14077 IPv4 responses received.
14082 <entry colname="1">
14083 <para><command>Responsev6</command></para>
14085 <entry colname="2">
14086 <para><command>RR</command></para>
14088 <entry colname="3">
14090 IPv6 responses received.
14095 <entry colname="1">
14096 <para><command>NXDOMAIN</command></para>
14098 <entry colname="2">
14099 <para><command>RNXD</command></para>
14101 <entry colname="3">
14108 <entry colname="1">
14109 <para><command>SERVFAIL</command></para>
14111 <entry colname="2">
14112 <para><command>RFail</command></para>
14114 <entry colname="3">
14121 <entry colname="1">
14122 <para><command>FORMERR</command></para>
14124 <entry colname="2">
14125 <para><command>RFErr</command></para>
14127 <entry colname="3">
14134 <entry colname="1">
14135 <para><command>OtherError</command></para>
14137 <entry colname="2">
14138 <para><command>RErr</command></para>
14140 <entry colname="3">
14142 Other errors received.
14147 <entry colname="1">
14148 <para><command>EDNS0Fail</command></para>
14150 <entry colname="2">
14151 <para><command></command></para>
14153 <entry colname="3">
14155 EDNS(0) query failures.
14160 <entry colname="1">
14161 <para><command>Mismatch</command></para>
14163 <entry colname="2">
14164 <para><command>RDupR</command></para>
14166 <entry colname="3">
14168 Mismatch responses received.
14169 The DNS ID, response's source address,
14170 and/or the response's source port does not
14171 match what was expected.
14172 (The port must be 53 or as defined by
14173 the <command>port</command> option.)
14174 This may be an indication of a cache
14180 <entry colname="1">
14181 <para><command>Truncated</command></para>
14183 <entry colname="2">
14184 <para><command></command></para>
14186 <entry colname="3">
14188 Truncated responses received.
14193 <entry colname="1">
14194 <para><command>Lame</command></para>
14196 <entry colname="2">
14197 <para><command>RLame</command></para>
14199 <entry colname="3">
14201 Lame delegations received.
14206 <entry colname="1">
14207 <para><command>Retry</command></para>
14209 <entry colname="2">
14210 <para><command>SDupQ</command></para>
14212 <entry colname="3">
14214 Query retries performed.
14219 <entry colname="1">
14220 <para><command>QueryAbort</command></para>
14222 <entry colname="2">
14223 <para><command></command></para>
14225 <entry colname="3">
14227 Queries aborted due to quota control.
14232 <entry colname="1">
14233 <para><command>QuerySockFail</command></para>
14235 <entry colname="2">
14236 <para><command></command></para>
14238 <entry colname="3">
14240 Failures in opening query sockets.
14241 One common reason for such failures is a
14242 failure of opening a new socket due to a
14243 limitation on file descriptors.
14248 <entry colname="1">
14249 <para><command>QueryTimeout</command></para>
14251 <entry colname="2">
14252 <para><command></command></para>
14254 <entry colname="3">
14261 <entry colname="1">
14262 <para><command>GlueFetchv4</command></para>
14264 <entry colname="2">
14265 <para><command>SSysQ</command></para>
14267 <entry colname="3">
14269 IPv4 NS address fetches invoked.
14274 <entry colname="1">
14275 <para><command>GlueFetchv6</command></para>
14277 <entry colname="2">
14278 <para><command>SSysQ</command></para>
14280 <entry colname="3">
14282 IPv6 NS address fetches invoked.
14287 <entry colname="1">
14288 <para><command>GlueFetchv4Fail</command></para>
14290 <entry colname="2">
14291 <para><command></command></para>
14293 <entry colname="3">
14295 IPv4 NS address fetch failed.
14300 <entry colname="1">
14301 <para><command>GlueFetchv6Fail</command></para>
14303 <entry colname="2">
14304 <para><command></command></para>
14306 <entry colname="3">
14308 IPv6 NS address fetch failed.
14313 <entry colname="1">
14314 <para><command>ValAttempt</command></para>
14316 <entry colname="2">
14317 <para><command></command></para>
14319 <entry colname="3">
14321 DNSSEC validation attempted.
14326 <entry colname="1">
14327 <para><command>ValOk</command></para>
14329 <entry colname="2">
14330 <para><command></command></para>
14332 <entry colname="3">
14334 DNSSEC validation succeeded.
14339 <entry colname="1">
14340 <para><command>ValNegOk</command></para>
14342 <entry colname="2">
14343 <para><command></command></para>
14345 <entry colname="3">
14347 DNSSEC validation on negative information succeeded.
14352 <entry colname="1">
14353 <para><command>ValFail</command></para>
14355 <entry colname="2">
14356 <para><command></command></para>
14358 <entry colname="3">
14360 DNSSEC validation failed.
14365 <entry colname="1">
14366 <para><command>QryRTTnn</command></para>
14368 <entry colname="2">
14369 <para><command></command></para>
14371 <entry colname="3">
14373 Frequency table on round trip times (RTTs) of
14375 Each <command>nn</command> specifies the corresponding
14378 <command>nn_1</command>,
14379 <command>nn_2</command>,
14381 <command>nn_m</command>,
14382 the value of <command>nn_i</command> is the
14383 number of queries whose RTTs are between
14384 <command>nn_(i-1)</command> (inclusive) and
14385 <command>nn_i</command> (exclusive) milliseconds.
14386 For the sake of convenience we define
14387 <command>nn_0</command> to be 0.
14388 The last entry should be represented as
14389 <command>nn_m+</command>, which means the
14390 number of queries whose RTTs are equal to or over
14391 <command>nn_m</command> milliseconds.
14402 <title>Socket I/O Statistics Counters</title>
14405 Socket I/O statistics counters are defined per socket
14407 <command>UDP4</command> (UDP/IPv4),
14408 <command>UDP6</command> (UDP/IPv6),
14409 <command>TCP4</command> (TCP/IPv4),
14410 <command>TCP6</command> (TCP/IPv6),
14411 <command>Unix</command> (Unix Domain), and
14412 <command>FDwatch</command> (sockets opened outside the
14414 In the following table <command><TYPE></command>
14415 represents a socket type.
14416 Not all counters are available for all socket types;
14417 exceptions are noted in the description field.
14420 <informaltable colsep="0" rowsep="0">
14421 <tgroup cols="2" colsep="0" rowsep="0" tgroupstyle="4Level-table">
14422 <colspec colname="1" colnum="1" colsep="0" colwidth="1.150in"/>
14423 <colspec colname="2" colnum="2" colsep="0" colwidth="3.350in"/>
14426 <entry colname="1">
14428 <emphasis>Symbol</emphasis>
14431 <entry colname="2">
14433 <emphasis>Description</emphasis>
14439 <entry colname="1">
14440 <para><command><TYPE>Open</command></para>
14442 <entry colname="2">
14444 Sockets opened successfully.
14445 This counter is not applicable to the
14446 <command>FDwatch</command> type.
14451 <entry colname="1">
14452 <para><command><TYPE>OpenFail</command></para>
14454 <entry colname="2">
14456 Failures of opening sockets.
14457 This counter is not applicable to the
14458 <command>FDwatch</command> type.
14463 <entry colname="1">
14464 <para><command><TYPE>Close</command></para>
14466 <entry colname="2">
14473 <entry colname="1">
14474 <para><command><TYPE>BindFail</command></para>
14476 <entry colname="2">
14478 Failures of binding sockets.
14483 <entry colname="1">
14484 <para><command><TYPE>ConnFail</command></para>
14486 <entry colname="2">
14488 Failures of connecting sockets.
14493 <entry colname="1">
14494 <para><command><TYPE>Conn</command></para>
14496 <entry colname="2">
14498 Connections established successfully.
14503 <entry colname="1">
14504 <para><command><TYPE>AcceptFail</command></para>
14506 <entry colname="2">
14508 Failures of accepting incoming connection requests.
14509 This counter is not applicable to the
14510 <command>UDP</command> and
14511 <command>FDwatch</command> types.
14516 <entry colname="1">
14517 <para><command><TYPE>Accept</command></para>
14519 <entry colname="2">
14521 Incoming connections successfully accepted.
14522 This counter is not applicable to the
14523 <command>UDP</command> and
14524 <command>FDwatch</command> types.
14529 <entry colname="1">
14530 <para><command><TYPE>SendErr</command></para>
14532 <entry colname="2">
14534 Errors in socket send operations.
14535 This counter corresponds
14536 to <command>SErr</command> counter of
14537 <command>BIND</command> 8.
14542 <entry colname="1">
14543 <para><command><TYPE>RecvErr</command></para>
14545 <entry colname="2">
14547 Errors in socket receive operations.
14548 This includes errors of send operations on a
14549 connected UDP socket notified by an ICMP error
14559 <title>Compatibility with <emphasis>BIND</emphasis> 8 Counters</title>
14561 Most statistics counters that were available
14562 in <command>BIND</command> 8 are also supported in
14563 <command>BIND</command> 9 as shown in the above tables.
14564 Here are notes about other counters that do not appear
14570 <term><command>RFwdR,SFwdR</command></term>
14573 These counters are not supported
14574 because <command>BIND</command> 9 does not adopt
14575 the notion of <emphasis>forwarding</emphasis>
14576 as <command>BIND</command> 8 did.
14582 <term><command>RAXFR</command></term>
14585 This counter is accessible in the Incoming Queries section.
14591 <term><command>RIQ</command></term>
14594 This counter is accessible in the Incoming Requests section.
14600 <term><command>ROpts</command></term>
14603 This counter is not supported
14604 because <command>BIND</command> 9 does not care
14605 about IP options in the first place.
14615 <chapter id="Bv9ARM.ch07">
14616 <title><acronym>BIND</acronym> 9 Security Considerations</title>
14617 <sect1 id="Access_Control_Lists">
14618 <title>Access Control Lists</title>
14620 Access Control Lists (ACLs) are address match lists that
14621 you can set up and nickname for future use in <command>allow-notify</command>,
14622 <command>allow-query</command>, <command>allow-query-on</command>,
14623 <command>allow-recursion</command>, <command>allow-recursion-on</command>,
14624 <command>blackhole</command>, <command>allow-transfer</command>,
14628 Using ACLs allows you to have finer control over who can access
14629 your name server, without cluttering up your config files with huge
14630 lists of IP addresses.
14633 It is a <emphasis>good idea</emphasis> to use ACLs, and to
14634 control access to your server. Limiting access to your server by
14635 outside parties can help prevent spoofing and denial of service (DoS) attacks against
14639 Here is an example of how to properly apply ACLs:
14643 // Set up an ACL named "bogusnets" that will block
14644 // RFC1918 space and some reserved space, which is
14645 // commonly used in spoofing attacks.
14647 0.0.0.0/8; 192.0.2.0/24; 224.0.0.0/3;
14648 10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16;
14651 // Set up an ACL called our-nets. Replace this with the
14652 // real IP numbers.
14653 acl our-nets { x.x.x.x/24; x.x.x.x/21; };
14657 allow-query { our-nets; };
14658 allow-recursion { our-nets; };
14660 blackhole { bogusnets; };
14664 zone "example.com" {
14666 file "m/example.com";
14667 allow-query { any; };
14672 This allows recursive queries of the server from the outside
14673 unless recursion has been previously disabled.
14677 <title><command>Chroot</command> and <command>Setuid</command></title>
14679 On UNIX servers, it is possible to run <acronym>BIND</acronym>
14680 in a <emphasis>chrooted</emphasis> environment (using
14681 the <command>chroot()</command> function) by specifying
14682 the "<option>-t</option>" option for <command>named</command>.
14683 This can help improve system security by placing
14684 <acronym>BIND</acronym> in a "sandbox", which will limit
14685 the damage done if a server is compromised.
14688 Another useful feature in the UNIX version of <acronym>BIND</acronym> is the
14689 ability to run the daemon as an unprivileged user ( <option>-u</option> <replaceable>user</replaceable> ).
14690 We suggest running as an unprivileged user when using the <command>chroot</command> feature.
14693 Here is an example command line to load <acronym>BIND</acronym> in a <command>chroot</command> sandbox,
14694 <command>/var/named</command>, and to run <command>named</command> <command>setuid</command> to
14698 <userinput>/usr/local/sbin/named -u 202 -t /var/named</userinput>
14702 <title>The <command>chroot</command> Environment</title>
14705 In order for a <command>chroot</command> environment
14707 work properly in a particular directory
14708 (for example, <filename>/var/named</filename>),
14709 you will need to set up an environment that includes everything
14710 <acronym>BIND</acronym> needs to run.
14711 From <acronym>BIND</acronym>'s point of view, <filename>/var/named</filename> is
14712 the root of the filesystem. You will need to adjust the values of
14714 like <command>directory</command> and <command>pid-file</command> to account
14718 Unlike with earlier versions of BIND, you typically will
14719 <emphasis>not</emphasis> need to compile <command>named</command>
14720 statically nor install shared libraries under the new root.
14721 However, depending on your operating system, you may need
14722 to set up things like
14723 <filename>/dev/zero</filename>,
14724 <filename>/dev/random</filename>,
14725 <filename>/dev/log</filename>, and
14726 <filename>/etc/localtime</filename>.
14731 <title>Using the <command>setuid</command> Function</title>
14734 Prior to running the <command>named</command> daemon,
14736 the <command>touch</command> utility (to change file
14738 modification times) or the <command>chown</command>
14740 set the user id and/or group id) on files
14741 to which you want <acronym>BIND</acronym>
14745 Note that if the <command>named</command> daemon is running as an
14746 unprivileged user, it will not be able to bind to new restricted
14747 ports if the server is reloaded.
14752 <sect1 id="dynamic_update_security">
14753 <title>Dynamic Update Security</title>
14756 Access to the dynamic
14757 update facility should be strictly limited. In earlier versions of
14758 <acronym>BIND</acronym>, the only way to do this was
14760 address of the host requesting the update, by listing an IP address
14762 network prefix in the <command>allow-update</command>
14764 This method is insecure since the source address of the update UDP
14766 is easily forged. Also note that if the IP addresses allowed by the
14767 <command>allow-update</command> option include the
14769 server which performs forwarding of dynamic updates, the master can
14771 trivially attacked by sending the update to the slave, which will
14772 forward it to the master with its own source IP address causing the
14773 master to approve it without question.
14777 For these reasons, we strongly recommend that updates be
14778 cryptographically authenticated by means of transaction signatures
14779 (TSIG). That is, the <command>allow-update</command>
14781 list only TSIG key names, not IP addresses or network
14782 prefixes. Alternatively, the new <command>update-policy</command>
14783 option can be used.
14787 Some sites choose to keep all dynamically-updated DNS data
14788 in a subdomain and delegate that subdomain to a separate zone. This
14789 way, the top-level zone containing critical data such as the IP
14791 of public web and mail servers need not allow dynamic update at
14798 <chapter id="Bv9ARM.ch08">
14799 <title>Troubleshooting</title>
14801 <title>Common Problems</title>
14803 <title>It's not working; how can I figure out what's wrong?</title>
14806 The best solution to solving installation and
14807 configuration issues is to take preventative measures by setting
14808 up logging files beforehand. The log files provide a
14809 source of hints and information that can be used to figure out
14810 what went wrong and how to fix the problem.
14816 <title>Incrementing and Changing the Serial Number</title>
14819 Zone serial numbers are just numbers — they aren't
14820 date related. A lot of people set them to a number that
14821 represents a date, usually of the form YYYYMMDDRR.
14822 Occasionally they will make a mistake and set them to a
14823 "date in the future" then try to correct them by setting
14824 them to the "current date". This causes problems because
14825 serial numbers are used to indicate that a zone has been
14826 updated. If the serial number on the slave server is
14827 lower than the serial number on the master, the slave
14828 server will attempt to update its copy of the zone.
14832 Setting the serial number to a lower number on the master
14833 server than the slave server means that the slave will not perform
14834 updates to its copy of the zone.
14838 The solution to this is to add 2147483647 (2^31-1) to the
14839 number, reload the zone and make sure all slaves have updated to
14840 the new zone serial number, then reset the number to what you want
14841 it to be, and reload the zone again.
14846 <title>Where Can I Get Help?</title>
14849 The Internet Systems Consortium
14850 (<acronym>ISC</acronym>) offers a wide range
14851 of support and service agreements for <acronym>BIND</acronym> and <acronym>DHCP</acronym> servers. Four
14852 levels of premium support are available and each level includes
14853 support for all <acronym>ISC</acronym> programs,
14854 significant discounts on products
14855 and training, and a recognized priority on bug fixes and
14856 non-funded feature requests. In addition, <acronym>ISC</acronym> offers a standard
14857 support agreement package which includes services ranging from bug
14858 fix announcements to remote support. It also includes training in
14859 <acronym>BIND</acronym> and <acronym>DHCP</acronym>.
14863 To discuss arrangements for support, contact
14864 <ulink url="mailto:info@isc.org">info@isc.org</ulink> or visit the
14865 <acronym>ISC</acronym> web page at
14866 <ulink url="http://www.isc.org/services/support/"
14867 >http://www.isc.org/services/support/</ulink>
14872 <appendix id="Bv9ARM.ch09">
14873 <title>Appendices</title>
14875 <title>Acknowledgments</title>
14876 <sect2 id="historical_dns_information">
14877 <title>A Brief History of the <acronym>DNS</acronym> and <acronym>BIND</acronym></title>
14880 Although the "official" beginning of the Domain Name
14881 System occurred in 1984 with the publication of RFC 920, the
14882 core of the new system was described in 1983 in RFCs 882 and
14883 883. From 1984 to 1987, the ARPAnet (the precursor to today's
14884 Internet) became a testbed of experimentation for developing the
14885 new naming/addressing scheme in a rapidly expanding,
14886 operational network environment. New RFCs were written and
14887 published in 1987 that modified the original documents to
14888 incorporate improvements based on the working model. RFC 1034,
14889 "Domain Names-Concepts and Facilities", and RFC 1035, "Domain
14890 Names-Implementation and Specification" were published and
14891 became the standards upon which all <acronym>DNS</acronym> implementations are
14896 The first working domain name server, called "Jeeves", was
14897 written in 1983-84 by Paul Mockapetris for operation on DEC
14899 machines located at the University of Southern California's
14901 Sciences Institute (USC-ISI) and SRI International's Network
14903 Center (SRI-NIC). A <acronym>DNS</acronym> server for
14904 Unix machines, the Berkeley Internet
14905 Name Domain (<acronym>BIND</acronym>) package, was
14906 written soon after by a group of
14907 graduate students at the University of California at Berkeley
14909 a grant from the US Defense Advanced Research Projects
14914 Versions of <acronym>BIND</acronym> through
14915 4.8.3 were maintained by the Computer
14916 Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
14917 Painter, David Riggle and Songnian Zhou made up the initial <acronym>BIND</acronym>
14918 project team. After that, additional work on the software package
14919 was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment
14921 employee on loan to the CSRG, worked on <acronym>BIND</acronym> for 2 years, from 1985
14922 to 1987. Many other people also contributed to <acronym>BIND</acronym> development
14923 during that time: Doug Kingston, Craig Partridge, Smoot
14925 Mike Muuss, Jim Bloom and Mike Schwartz. <acronym>BIND</acronym> maintenance was subsequently
14926 handled by Mike Karels and Øivind Kure.
14929 <acronym>BIND</acronym> versions 4.9 and 4.9.1 were
14930 released by Digital Equipment
14931 Corporation (now Compaq Computer Corporation). Paul Vixie, then
14932 a DEC employee, became <acronym>BIND</acronym>'s
14933 primary caretaker. He was assisted
14934 by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan
14936 Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat
14937 Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
14938 Wolfhugel, and others.
14941 In 1994, <acronym>BIND</acronym> version 4.9.2 was sponsored by
14942 Vixie Enterprises. Paul
14943 Vixie became <acronym>BIND</acronym>'s principal
14944 architect/programmer.
14947 <acronym>BIND</acronym> versions from 4.9.3 onward
14948 have been developed and maintained
14949 by the Internet Systems Consortium and its predecessor,
14950 the Internet Software Consortium, with support being provided
14954 As co-architects/programmers, Bob Halley and
14955 Paul Vixie released the first production-ready version of
14956 <acronym>BIND</acronym> version 8 in May 1997.
14959 BIND version 9 was released in September 2000 and is a
14960 major rewrite of nearly all aspects of the underlying
14964 BIND versions 4 and 8 are officially deprecated.
14965 No additional development is done
14966 on BIND version 4 or BIND version 8.
14969 <acronym>BIND</acronym> development work is made
14970 possible today by the sponsorship
14971 of several corporations, and by the tireless work efforts of
14972 numerous individuals.
14977 <title>General <acronym>DNS</acronym> Reference Information</title>
14978 <sect2 id="ipv6addresses">
14979 <title>IPv6 addresses (AAAA)</title>
14981 IPv6 addresses are 128-bit identifiers for interfaces and
14982 sets of interfaces which were introduced in the <acronym>DNS</acronym> to facilitate
14983 scalable Internet routing. There are three types of addresses: <emphasis>Unicast</emphasis>,
14984 an identifier for a single interface;
14985 <emphasis>Anycast</emphasis>,
14986 an identifier for a set of interfaces; and <emphasis>Multicast</emphasis>,
14987 an identifier for a set of interfaces. Here we describe the global
14988 Unicast address scheme. For more information, see RFC 3587,
14989 "Global Unicast Address Format."
14992 IPv6 unicast addresses consist of a
14993 <emphasis>global routing prefix</emphasis>, a
14994 <emphasis>subnet identifier</emphasis>, and an
14995 <emphasis>interface identifier</emphasis>.
14998 The global routing prefix is provided by the
14999 upstream provider or ISP, and (roughly) corresponds to the
15000 IPv4 <emphasis>network</emphasis> section
15001 of the address range.
15003 The subnet identifier is for local subnetting, much the
15004 same as subnetting an
15005 IPv4 /16 network into /24 subnets.
15007 The interface identifier is the address of an individual
15008 interface on a given network; in IPv6, addresses belong to
15009 interfaces rather than to machines.
15012 The subnetting capability of IPv6 is much more flexible than
15013 that of IPv4: subnetting can be carried out on bit boundaries,
15014 in much the same way as Classless InterDomain Routing
15015 (CIDR), and the DNS PTR representation ("nibble" format)
15016 makes setting up reverse zones easier.
15019 The Interface Identifier must be unique on the local link,
15020 and is usually generated automatically by the IPv6
15021 implementation, although it is usually possible to
15022 override the default setting if necessary. A typical IPv6
15023 address might look like:
15024 <command>2001:db8:201:9:a00:20ff:fe81:2b32</command>
15027 IPv6 address specifications often contain long strings
15028 of zeros, so the architects have included a shorthand for
15030 them. The double colon (`::') indicates the longest possible
15032 of zeros that can fit, and can be used only once in an address.
15036 <sect1 id="bibliography">
15037 <title>Bibliography (and Suggested Reading)</title>
15039 <title>Request for Comments (RFCs)</title>
15041 Specification documents for the Internet protocol suite, including
15042 the <acronym>DNS</acronym>, are published as part of
15043 the Request for Comments (RFCs)
15044 series of technical notes. The standards themselves are defined
15045 by the Internet Engineering Task Force (IETF) and the Internet
15046 Engineering Steering Group (IESG). RFCs can be obtained online via FTP at:
15049 <ulink url="ftp://www.isi.edu/in-notes/">
15050 ftp://www.isi.edu/in-notes/RFC<replaceable>xxxx</replaceable>.txt
15054 (where <replaceable>xxxx</replaceable> is
15055 the number of the RFC). RFCs are also available via the Web at:
15058 <ulink url="http://www.ietf.org/rfc/"
15059 >http://www.ietf.org/rfc/</ulink>.
15063 <!-- one of (BIBLIOENTRY BIBLIOMIXED) -->
15064 <title>Standards</title>
15066 <abbrev>RFC974</abbrev>
15068 <surname>Partridge</surname>
15069 <firstname>C.</firstname>
15071 <title>Mail Routing and the Domain System</title>
15072 <pubdate>January 1986</pubdate>
15075 <abbrev>RFC1034</abbrev>
15077 <surname>Mockapetris</surname>
15078 <firstname>P.V.</firstname>
15080 <title>Domain Names — Concepts and Facilities</title>
15081 <pubdate>November 1987</pubdate>
15084 <abbrev>RFC1035</abbrev>
15086 <surname>Mockapetris</surname>
15087 <firstname>P. V.</firstname>
15088 </author> <title>Domain Names — Implementation and
15089 Specification</title>
15090 <pubdate>November 1987</pubdate>
15093 <bibliodiv id="proposed_standards" xreflabel="Proposed Standards">
15095 <title>Proposed Standards</title>
15096 <!-- one of (BIBLIOENTRY BIBLIOMIXED) -->
15098 <abbrev>RFC2181</abbrev>
15100 <surname>Elz</surname>
15101 <firstname>R., R. Bush</firstname>
15103 <title>Clarifications to the <acronym>DNS</acronym>
15104 Specification</title>
15105 <pubdate>July 1997</pubdate>
15108 <abbrev>RFC2308</abbrev>
15110 <surname>Andrews</surname>
15111 <firstname>M.</firstname>
15113 <title>Negative Caching of <acronym>DNS</acronym>
15115 <pubdate>March 1998</pubdate>
15118 <abbrev>RFC1995</abbrev>
15120 <surname>Ohta</surname>
15121 <firstname>M.</firstname>
15123 <title>Incremental Zone Transfer in <acronym>DNS</acronym></title>
15124 <pubdate>August 1996</pubdate>
15127 <abbrev>RFC1996</abbrev>
15129 <surname>Vixie</surname>
15130 <firstname>P.</firstname>
15132 <title>A Mechanism for Prompt Notification of Zone Changes</title>
15133 <pubdate>August 1996</pubdate>
15136 <abbrev>RFC2136</abbrev>
15139 <surname>Vixie</surname>
15140 <firstname>P.</firstname>
15143 <firstname>S.</firstname>
15144 <surname>Thomson</surname>
15147 <firstname>Y.</firstname>
15148 <surname>Rekhter</surname>
15151 <firstname>J.</firstname>
15152 <surname>Bound</surname>
15155 <title>Dynamic Updates in the Domain Name System</title>
15156 <pubdate>April 1997</pubdate>
15159 <abbrev>RFC2671</abbrev>
15162 <firstname>P.</firstname>
15163 <surname>Vixie</surname>
15166 <title>Extension Mechanisms for DNS (EDNS0)</title>
15167 <pubdate>August 1997</pubdate>
15170 <abbrev>RFC2672</abbrev>
15173 <firstname>M.</firstname>
15174 <surname>Crawford</surname>
15177 <title>Non-Terminal DNS Name Redirection</title>
15178 <pubdate>August 1999</pubdate>
15181 <abbrev>RFC2845</abbrev>
15184 <surname>Vixie</surname>
15185 <firstname>P.</firstname>
15188 <firstname>O.</firstname>
15189 <surname>Gudmundsson</surname>
15192 <firstname>D.</firstname>
15193 <surname>Eastlake</surname>
15194 <lineage>3rd</lineage>
15197 <firstname>B.</firstname>
15198 <surname>Wellington</surname>
15201 <title>Secret Key Transaction Authentication for <acronym>DNS</acronym> (TSIG)</title>
15202 <pubdate>May 2000</pubdate>
15205 <abbrev>RFC2930</abbrev>
15208 <firstname>D.</firstname>
15209 <surname>Eastlake</surname>
15210 <lineage>3rd</lineage>
15213 <title>Secret Key Establishment for DNS (TKEY RR)</title>
15214 <pubdate>September 2000</pubdate>
15217 <abbrev>RFC2931</abbrev>
15220 <firstname>D.</firstname>
15221 <surname>Eastlake</surname>
15222 <lineage>3rd</lineage>
15225 <title>DNS Request and Transaction Signatures (SIG(0)s)</title>
15226 <pubdate>September 2000</pubdate>
15229 <abbrev>RFC3007</abbrev>
15232 <firstname>B.</firstname>
15233 <surname>Wellington</surname>
15236 <title>Secure Domain Name System (DNS) Dynamic Update</title>
15237 <pubdate>November 2000</pubdate>
15240 <abbrev>RFC3645</abbrev>
15243 <firstname>S.</firstname>
15244 <surname>Kwan</surname>
15247 <firstname>P.</firstname>
15248 <surname>Garg</surname>
15251 <firstname>J.</firstname>
15252 <surname>Gilroy</surname>
15255 <firstname>L.</firstname>
15256 <surname>Esibov</surname>
15259 <firstname>J.</firstname>
15260 <surname>Westhead</surname>
15263 <firstname>R.</firstname>
15264 <surname>Hall</surname>
15267 <title>Generic Security Service Algorithm for Secret
15268 Key Transaction Authentication for DNS
15270 <pubdate>October 2003</pubdate>
15274 <title><acronym>DNS</acronym> Security Proposed Standards</title>
15276 <abbrev>RFC3225</abbrev>
15279 <firstname>D.</firstname>
15280 <surname>Conrad</surname>
15283 <title>Indicating Resolver Support of DNSSEC</title>
15284 <pubdate>December 2001</pubdate>
15287 <abbrev>RFC3833</abbrev>
15290 <firstname>D.</firstname>
15291 <surname>Atkins</surname>
15294 <firstname>R.</firstname>
15295 <surname>Austein</surname>
15298 <title>Threat Analysis of the Domain Name System (DNS)</title>
15299 <pubdate>August 2004</pubdate>
15302 <abbrev>RFC4033</abbrev>
15305 <firstname>R.</firstname>
15306 <surname>Arends</surname>
15309 <firstname>R.</firstname>
15310 <surname>Austein</surname>
15313 <firstname>M.</firstname>
15314 <surname>Larson</surname>
15317 <firstname>D.</firstname>
15318 <surname>Massey</surname>
15321 <firstname>S.</firstname>
15322 <surname>Rose</surname>
15325 <title>DNS Security Introduction and Requirements</title>
15326 <pubdate>March 2005</pubdate>
15329 <abbrev>RFC4034</abbrev>
15332 <firstname>R.</firstname>
15333 <surname>Arends</surname>
15336 <firstname>R.</firstname>
15337 <surname>Austein</surname>
15340 <firstname>M.</firstname>
15341 <surname>Larson</surname>
15344 <firstname>D.</firstname>
15345 <surname>Massey</surname>
15348 <firstname>S.</firstname>
15349 <surname>Rose</surname>
15352 <title>Resource Records for the DNS Security Extensions</title>
15353 <pubdate>March 2005</pubdate>
15356 <abbrev>RFC4035</abbrev>
15359 <firstname>R.</firstname>
15360 <surname>Arends</surname>
15363 <firstname>R.</firstname>
15364 <surname>Austein</surname>
15367 <firstname>M.</firstname>
15368 <surname>Larson</surname>
15371 <firstname>D.</firstname>
15372 <surname>Massey</surname>
15375 <firstname>S.</firstname>
15376 <surname>Rose</surname>
15379 <title>Protocol Modifications for the DNS
15380 Security Extensions</title>
15381 <pubdate>March 2005</pubdate>
15385 <title>Other Important RFCs About <acronym>DNS</acronym>
15386 Implementation</title>
15388 <abbrev>RFC1535</abbrev>
15390 <surname>Gavron</surname>
15391 <firstname>E.</firstname>
15393 <title>A Security Problem and Proposed Correction With Widely
15394 Deployed <acronym>DNS</acronym> Software.</title>
15395 <pubdate>October 1993</pubdate>
15398 <abbrev>RFC1536</abbrev>
15401 <surname>Kumar</surname>
15402 <firstname>A.</firstname>
15405 <firstname>J.</firstname>
15406 <surname>Postel</surname>
15409 <firstname>C.</firstname>
15410 <surname>Neuman</surname>
15413 <firstname>P.</firstname>
15414 <surname>Danzig</surname>
15417 <firstname>S.</firstname>
15418 <surname>Miller</surname>
15421 <title>Common <acronym>DNS</acronym> Implementation
15422 Errors and Suggested Fixes</title>
15423 <pubdate>October 1993</pubdate>
15426 <abbrev>RFC1982</abbrev>
15429 <surname>Elz</surname>
15430 <firstname>R.</firstname>
15433 <firstname>R.</firstname>
15434 <surname>Bush</surname>
15437 <title>Serial Number Arithmetic</title>
15438 <pubdate>August 1996</pubdate>
15441 <abbrev>RFC4074</abbrev>
15444 <surname>Morishita</surname>
15445 <firstname>Y.</firstname>
15448 <firstname>T.</firstname>
15449 <surname>Jinmei</surname>
15452 <title>Common Misbehaviour Against <acronym>DNS</acronym>
15453 Queries for IPv6 Addresses</title>
15454 <pubdate>May 2005</pubdate>
15458 <title>Resource Record Types</title>
15460 <abbrev>RFC1183</abbrev>
15463 <surname>Everhart</surname>
15464 <firstname>C.F.</firstname>
15467 <firstname>L. A.</firstname>
15468 <surname>Mamakos</surname>
15471 <firstname>R.</firstname>
15472 <surname>Ullmann</surname>
15475 <firstname>P.</firstname>
15476 <surname>Mockapetris</surname>
15479 <title>New <acronym>DNS</acronym> RR Definitions</title>
15480 <pubdate>October 1990</pubdate>
15483 <abbrev>RFC1706</abbrev>
15486 <surname>Manning</surname>
15487 <firstname>B.</firstname>
15490 <firstname>R.</firstname>
15491 <surname>Colella</surname>
15494 <title><acronym>DNS</acronym> NSAP Resource Records</title>
15495 <pubdate>October 1994</pubdate>
15498 <abbrev>RFC2168</abbrev>
15501 <surname>Daniel</surname>
15502 <firstname>R.</firstname>
15505 <firstname>M.</firstname>
15506 <surname>Mealling</surname>
15509 <title>Resolution of Uniform Resource Identifiers using
15510 the Domain Name System</title>
15511 <pubdate>June 1997</pubdate>
15514 <abbrev>RFC1876</abbrev>
15517 <surname>Davis</surname>
15518 <firstname>C.</firstname>
15521 <firstname>P.</firstname>
15522 <surname>Vixie</surname>
15525 <firstname>T.</firstname>
15526 <firstname>Goodwin</firstname>
15529 <firstname>I.</firstname>
15530 <surname>Dickinson</surname>
15533 <title>A Means for Expressing Location Information in the
15535 Name System</title>
15536 <pubdate>January 1996</pubdate>
15539 <abbrev>RFC2052</abbrev>
15542 <surname>Gulbrandsen</surname>
15543 <firstname>A.</firstname>
15546 <firstname>P.</firstname>
15547 <surname>Vixie</surname>
15550 <title>A <acronym>DNS</acronym> RR for Specifying the
15553 <pubdate>October 1996</pubdate>
15556 <abbrev>RFC2163</abbrev>
15558 <surname>Allocchio</surname>
15559 <firstname>A.</firstname>
15561 <title>Using the Internet <acronym>DNS</acronym> to
15563 Conformant Global Address Mapping</title>
15564 <pubdate>January 1998</pubdate>
15567 <abbrev>RFC2230</abbrev>
15569 <surname>Atkinson</surname>
15570 <firstname>R.</firstname>
15572 <title>Key Exchange Delegation Record for the <acronym>DNS</acronym></title>
15573 <pubdate>October 1997</pubdate>
15576 <abbrev>RFC2536</abbrev>
15578 <surname>Eastlake</surname>
15579 <firstname>D.</firstname>
15580 <lineage>3rd</lineage>
15582 <title>DSA KEYs and SIGs in the Domain Name System (DNS)</title>
15583 <pubdate>March 1999</pubdate>
15586 <abbrev>RFC2537</abbrev>
15588 <surname>Eastlake</surname>
15589 <firstname>D.</firstname>
15590 <lineage>3rd</lineage>
15592 <title>RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)</title>
15593 <pubdate>March 1999</pubdate>
15596 <abbrev>RFC2538</abbrev>
15599 <surname>Eastlake</surname>
15600 <firstname>D.</firstname>
15601 <lineage>3rd</lineage>
15604 <surname>Gudmundsson</surname>
15605 <firstname>O.</firstname>
15608 <title>Storing Certificates in the Domain Name System (DNS)</title>
15609 <pubdate>March 1999</pubdate>
15612 <abbrev>RFC2539</abbrev>
15615 <surname>Eastlake</surname>
15616 <firstname>D.</firstname>
15617 <lineage>3rd</lineage>
15620 <title>Storage of Diffie-Hellman Keys in the Domain Name System (DNS)</title>
15621 <pubdate>March 1999</pubdate>
15624 <abbrev>RFC2540</abbrev>
15627 <surname>Eastlake</surname>
15628 <firstname>D.</firstname>
15629 <lineage>3rd</lineage>
15632 <title>Detached Domain Name System (DNS) Information</title>
15633 <pubdate>March 1999</pubdate>
15636 <abbrev>RFC2782</abbrev>
15638 <surname>Gulbrandsen</surname>
15639 <firstname>A.</firstname>
15642 <surname>Vixie</surname>
15643 <firstname>P.</firstname>
15646 <surname>Esibov</surname>
15647 <firstname>L.</firstname>
15649 <title>A DNS RR for specifying the location of services (DNS SRV)</title>
15650 <pubdate>February 2000</pubdate>
15653 <abbrev>RFC2915</abbrev>
15655 <surname>Mealling</surname>
15656 <firstname>M.</firstname>
15659 <surname>Daniel</surname>
15660 <firstname>R.</firstname>
15662 <title>The Naming Authority Pointer (NAPTR) DNS Resource Record</title>
15663 <pubdate>September 2000</pubdate>
15666 <abbrev>RFC3110</abbrev>
15668 <surname>Eastlake</surname>
15669 <firstname>D.</firstname>
15670 <lineage>3rd</lineage>
15672 <title>RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</title>
15673 <pubdate>May 2001</pubdate>
15676 <abbrev>RFC3123</abbrev>
15678 <surname>Koch</surname>
15679 <firstname>P.</firstname>
15681 <title>A DNS RR Type for Lists of Address Prefixes (APL RR)</title>
15682 <pubdate>June 2001</pubdate>
15685 <abbrev>RFC3596</abbrev>
15688 <surname>Thomson</surname>
15689 <firstname>S.</firstname>
15692 <firstname>C.</firstname>
15693 <surname>Huitema</surname>
15696 <firstname>V.</firstname>
15697 <surname>Ksinant</surname>
15700 <firstname>M.</firstname>
15701 <surname>Souissi</surname>
15704 <title><acronym>DNS</acronym> Extensions to support IP
15706 <pubdate>October 2003</pubdate>
15709 <abbrev>RFC3597</abbrev>
15711 <surname>Gustafsson</surname>
15712 <firstname>A.</firstname>
15714 <title>Handling of Unknown DNS Resource Record (RR) Types</title>
15715 <pubdate>September 2003</pubdate>
15719 <title><acronym>DNS</acronym> and the Internet</title>
15721 <abbrev>RFC1101</abbrev>
15723 <surname>Mockapetris</surname>
15724 <firstname>P. V.</firstname>
15726 <title><acronym>DNS</acronym> Encoding of Network Names
15727 and Other Types</title>
15728 <pubdate>April 1989</pubdate>
15731 <abbrev>RFC1123</abbrev>
15733 <surname>Braden</surname>
15734 <surname>R.</surname>
15736 <title>Requirements for Internet Hosts - Application and
15738 <pubdate>October 1989</pubdate>
15741 <abbrev>RFC1591</abbrev>
15743 <surname>Postel</surname>
15744 <firstname>J.</firstname>
15746 <title>Domain Name System Structure and Delegation</title>
15747 <pubdate>March 1994</pubdate>
15750 <abbrev>RFC2317</abbrev>
15753 <surname>Eidnes</surname>
15754 <firstname>H.</firstname>
15757 <firstname>G.</firstname>
15758 <surname>de Groot</surname>
15761 <firstname>P.</firstname>
15762 <surname>Vixie</surname>
15765 <title>Classless IN-ADDR.ARPA Delegation</title>
15766 <pubdate>March 1998</pubdate>
15769 <abbrev>RFC2826</abbrev>
15772 <surname>Internet Architecture Board</surname>
15775 <title>IAB Technical Comment on the Unique DNS Root</title>
15776 <pubdate>May 2000</pubdate>
15779 <abbrev>RFC2929</abbrev>
15782 <surname>Eastlake</surname>
15783 <firstname>D.</firstname>
15784 <lineage>3rd</lineage>
15787 <surname>Brunner-Williams</surname>
15788 <firstname>E.</firstname>
15791 <surname>Manning</surname>
15792 <firstname>B.</firstname>
15795 <title>Domain Name System (DNS) IANA Considerations</title>
15796 <pubdate>September 2000</pubdate>
15800 <title><acronym>DNS</acronym> Operations</title>
15802 <abbrev>RFC1033</abbrev>
15804 <surname>Lottor</surname>
15805 <firstname>M.</firstname>
15807 <title>Domain administrators operations guide.</title>
15808 <pubdate>November 1987</pubdate>
15811 <abbrev>RFC1537</abbrev>
15813 <surname>Beertema</surname>
15814 <firstname>P.</firstname>
15816 <title>Common <acronym>DNS</acronym> Data File
15817 Configuration Errors</title>
15818 <pubdate>October 1993</pubdate>
15821 <abbrev>RFC1912</abbrev>
15823 <surname>Barr</surname>
15824 <firstname>D.</firstname>
15826 <title>Common <acronym>DNS</acronym> Operational and
15827 Configuration Errors</title>
15828 <pubdate>February 1996</pubdate>
15831 <abbrev>RFC2010</abbrev>
15834 <surname>Manning</surname>
15835 <firstname>B.</firstname>
15838 <firstname>P.</firstname>
15839 <surname>Vixie</surname>
15842 <title>Operational Criteria for Root Name Servers.</title>
15843 <pubdate>October 1996</pubdate>
15846 <abbrev>RFC2219</abbrev>
15849 <surname>Hamilton</surname>
15850 <firstname>M.</firstname>
15853 <firstname>R.</firstname>
15854 <surname>Wright</surname>
15857 <title>Use of <acronym>DNS</acronym> Aliases for
15858 Network Services.</title>
15859 <pubdate>October 1997</pubdate>
15863 <title>Internationalized Domain Names</title>
15865 <abbrev>RFC2825</abbrev>
15868 <surname>IAB</surname>
15871 <surname>Daigle</surname>
15872 <firstname>R.</firstname>
15875 <title>A Tangled Web: Issues of I18N, Domain Names,
15876 and the Other Internet protocols</title>
15877 <pubdate>May 2000</pubdate>
15880 <abbrev>RFC3490</abbrev>
15883 <surname>Faltstrom</surname>
15884 <firstname>P.</firstname>
15887 <surname>Hoffman</surname>
15888 <firstname>P.</firstname>
15891 <surname>Costello</surname>
15892 <firstname>A.</firstname>
15895 <title>Internationalizing Domain Names in Applications (IDNA)</title>
15896 <pubdate>March 2003</pubdate>
15899 <abbrev>RFC3491</abbrev>
15902 <surname>Hoffman</surname>
15903 <firstname>P.</firstname>
15906 <surname>Blanchet</surname>
15907 <firstname>M.</firstname>
15910 <title>Nameprep: A Stringprep Profile for Internationalized Domain Names</title>
15911 <pubdate>March 2003</pubdate>
15914 <abbrev>RFC3492</abbrev>
15917 <surname>Costello</surname>
15918 <firstname>A.</firstname>
15921 <title>Punycode: A Bootstring encoding of Unicode
15922 for Internationalized Domain Names in
15923 Applications (IDNA)</title>
15924 <pubdate>March 2003</pubdate>
15928 <title>Other <acronym>DNS</acronym>-related RFCs</title>
15931 Note: the following list of RFCs, although
15932 <acronym>DNS</acronym>-related, are not
15933 concerned with implementing software.
15937 <abbrev>RFC1464</abbrev>
15939 <surname>Rosenbaum</surname>
15940 <firstname>R.</firstname>
15942 <title>Using the Domain Name System To Store Arbitrary String
15944 <pubdate>May 1993</pubdate>
15947 <abbrev>RFC1713</abbrev>
15949 <surname>Romao</surname>
15950 <firstname>A.</firstname>
15952 <title>Tools for <acronym>DNS</acronym> Debugging</title>
15953 <pubdate>November 1994</pubdate>
15956 <abbrev>RFC1794</abbrev>
15958 <surname>Brisco</surname>
15959 <firstname>T.</firstname>
15961 <title><acronym>DNS</acronym> Support for Load
15963 <pubdate>April 1995</pubdate>
15966 <abbrev>RFC2240</abbrev>
15968 <surname>Vaughan</surname>
15969 <firstname>O.</firstname>
15971 <title>A Legal Basis for Domain Name Allocation</title>
15972 <pubdate>November 1997</pubdate>
15975 <abbrev>RFC2345</abbrev>
15978 <surname>Klensin</surname>
15979 <firstname>J.</firstname>
15982 <firstname>T.</firstname>
15983 <surname>Wolf</surname>
15986 <firstname>G.</firstname>
15987 <surname>Oglesby</surname>
15990 <title>Domain Names and Company Name Retrieval</title>
15991 <pubdate>May 1998</pubdate>
15994 <abbrev>RFC2352</abbrev>
15996 <surname>Vaughan</surname>
15997 <firstname>O.</firstname>
15999 <title>A Convention For Using Legal Names as Domain Names</title>
16000 <pubdate>May 1998</pubdate>
16003 <abbrev>RFC3071</abbrev>
16006 <surname>Klensin</surname>
16007 <firstname>J.</firstname>
16010 <title>Reflections on the DNS, RFC 1591, and Categories of Domains</title>
16011 <pubdate>February 2001</pubdate>
16014 <abbrev>RFC3258</abbrev>
16017 <surname>Hardie</surname>
16018 <firstname>T.</firstname>
16021 <title>Distributing Authoritative Name Servers via
16022 Shared Unicast Addresses</title>
16023 <pubdate>April 2002</pubdate>
16026 <abbrev>RFC3901</abbrev>
16029 <surname>Durand</surname>
16030 <firstname>A.</firstname>
16033 <firstname>J.</firstname>
16034 <surname>Ihren</surname>
16037 <title>DNS IPv6 Transport Operational Guidelines</title>
16038 <pubdate>September 2004</pubdate>
16042 <title>Obsolete and Unimplemented Experimental RFC</title>
16044 <abbrev>RFC1712</abbrev>
16047 <surname>Farrell</surname>
16048 <firstname>C.</firstname>
16051 <firstname>M.</firstname>
16052 <surname>Schulze</surname>
16055 <firstname>S.</firstname>
16056 <surname>Pleitner</surname>
16059 <firstname>D.</firstname>
16060 <surname>Baldoni</surname>
16063 <title><acronym>DNS</acronym> Encoding of Geographical
16065 <pubdate>November 1994</pubdate>
16068 <abbrev>RFC2673</abbrev>
16071 <surname>Crawford</surname>
16072 <firstname>M.</firstname>
16075 <title>Binary Labels in the Domain Name System</title>
16076 <pubdate>August 1999</pubdate>
16079 <abbrev>RFC2874</abbrev>
16082 <surname>Crawford</surname>
16083 <firstname>M.</firstname>
16086 <surname>Huitema</surname>
16087 <firstname>C.</firstname>
16090 <title>DNS Extensions to Support IPv6 Address Aggregation
16091 and Renumbering</title>
16092 <pubdate>July 2000</pubdate>
16096 <title>Obsoleted DNS Security RFCs</title>
16099 Most of these have been consolidated into RFC4033,
16100 RFC4034 and RFC4035 which collectively describe DNSSECbis.
16104 <abbrev>RFC2065</abbrev>
16107 <surname>Eastlake</surname>
16108 <lineage>3rd</lineage>
16109 <firstname>D.</firstname>
16112 <firstname>C.</firstname>
16113 <surname>Kaufman</surname>
16116 <title>Domain Name System Security Extensions</title>
16117 <pubdate>January 1997</pubdate>
16120 <abbrev>RFC2137</abbrev>
16122 <surname>Eastlake</surname>
16123 <lineage>3rd</lineage>
16124 <firstname>D.</firstname>
16126 <title>Secure Domain Name System Dynamic Update</title>
16127 <pubdate>April 1997</pubdate>
16130 <abbrev>RFC2535</abbrev>
16133 <surname>Eastlake</surname>
16134 <lineage>3rd</lineage>
16135 <firstname>D.</firstname>
16138 <title>Domain Name System Security Extensions</title>
16139 <pubdate>March 1999</pubdate>
16142 <abbrev>RFC3008</abbrev>
16145 <surname>Wellington</surname>
16146 <firstname>B.</firstname>
16149 <title>Domain Name System Security (DNSSEC)
16150 Signing Authority</title>
16151 <pubdate>November 2000</pubdate>
16154 <abbrev>RFC3090</abbrev>
16157 <surname>Lewis</surname>
16158 <firstname>E.</firstname>
16161 <title>DNS Security Extension Clarification on Zone Status</title>
16162 <pubdate>March 2001</pubdate>
16165 <abbrev>RFC3445</abbrev>
16168 <surname>Massey</surname>
16169 <firstname>D.</firstname>
16172 <surname>Rose</surname>
16173 <firstname>S.</firstname>
16176 <title>Limiting the Scope of the KEY Resource Record (RR)</title>
16177 <pubdate>December 2002</pubdate>
16180 <abbrev>RFC3655</abbrev>
16183 <surname>Wellington</surname>
16184 <firstname>B.</firstname>
16187 <surname>Gudmundsson</surname>
16188 <firstname>O.</firstname>
16191 <title>Redefinition of DNS Authenticated Data (AD) bit</title>
16192 <pubdate>November 2003</pubdate>
16195 <abbrev>RFC3658</abbrev>
16198 <surname>Gudmundsson</surname>
16199 <firstname>O.</firstname>
16202 <title>Delegation Signer (DS) Resource Record (RR)</title>
16203 <pubdate>December 2003</pubdate>
16206 <abbrev>RFC3755</abbrev>
16209 <surname>Weiler</surname>
16210 <firstname>S.</firstname>
16213 <title>Legacy Resolver Compatibility for Delegation Signer (DS)</title>
16214 <pubdate>May 2004</pubdate>
16217 <abbrev>RFC3757</abbrev>
16220 <surname>Kolkman</surname>
16221 <firstname>O.</firstname>
16224 <surname>Schlyter</surname>
16225 <firstname>J.</firstname>
16228 <surname>Lewis</surname>
16229 <firstname>E.</firstname>
16232 <title>Domain Name System KEY (DNSKEY) Resource Record
16233 (RR) Secure Entry Point (SEP) Flag</title>
16234 <pubdate>April 2004</pubdate>
16237 <abbrev>RFC3845</abbrev>
16240 <surname>Schlyter</surname>
16241 <firstname>J.</firstname>
16244 <title>DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format</title>
16245 <pubdate>August 2004</pubdate>
16250 <sect2 id="internet_drafts">
16251 <title>Internet Drafts</title>
16253 Internet Drafts (IDs) are rough-draft working documents of
16254 the Internet Engineering Task Force. They are, in essence, RFCs
16255 in the preliminary stages of development. Implementors are
16257 to regard IDs as archival, and they should not be quoted or cited
16258 in any formal documents unless accompanied by the disclaimer that
16259 they are "works in progress." IDs have a lifespan of six months
16260 after which they are deleted unless updated by their authors.
16264 <title>Other Documents About <acronym>BIND</acronym></title>
16270 <surname>Albitz</surname>
16271 <firstname>Paul</firstname>
16274 <firstname>Cricket</firstname>
16275 <surname>Liu</surname>
16278 <title><acronym>DNS</acronym> and <acronym>BIND</acronym></title>
16281 <holder>Sebastopol, CA: O'Reilly and Associates</holder>
16288 <xi:include href="libdns.xml"/>
16293 <reference id="Bv9ARM.ch10">
16294 <title>Manual pages</title>
16295 <xi:include href="../../bin/dig/dig.docbook"/>
16296 <xi:include href="../../bin/dig/host.docbook"/>
16297 <xi:include href="../../bin/dnssec/dnssec-dsfromkey.docbook"/>
16298 <xi:include href="../../bin/dnssec/dnssec-keyfromlabel.docbook"/>
16299 <xi:include href="../../bin/dnssec/dnssec-keygen.docbook"/>
16300 <xi:include href="../../bin/dnssec/dnssec-revoke.docbook"/>
16301 <xi:include href="../../bin/dnssec/dnssec-settime.docbook"/>
16302 <xi:include href="../../bin/dnssec/dnssec-signzone.docbook"/>
16303 <xi:include href="../../bin/check/named-checkconf.docbook"/>
16304 <xi:include href="../../bin/check/named-checkzone.docbook"/>
16305 <xi:include href="../../bin/named/named.docbook"/>
16306 <xi:include href="../../bin/tools/named-journalprint.docbook"/>
16307 <!-- named.conf.docbook and others? -->
16308 <xi:include href="../../bin/nsupdate/nsupdate.docbook"/>
16309 <xi:include href="../../bin/rndc/rndc.docbook"/>
16310 <xi:include href="../../bin/rndc/rndc.conf.docbook"/>
16311 <xi:include href="../../bin/confgen/rndc-confgen.docbook"/>
16312 <xi:include href="../../bin/confgen/ddns-confgen.docbook"/>
16313 <xi:include href="../../bin/tools/arpaname.docbook"/>
16314 <xi:include href="../../bin/tools/genrandom.docbook"/>
16315 <xi:include href="../../bin/tools/isc-hmac-fixup.docbook"/>
16316 <xi:include href="../../bin/tools/nsec3hash.docbook"/>