Bv9ARM.ch06.html revision 3e240d6559605696cadf630668683708b18de871
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews<!--
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater - Copyright (C) 2000-2003 Internet Software Consortium.
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater -
1167fc7904c5f0a472f8df207ac46dd52c7f1ec8Automatic Updater - Permission to use, copy, modify, and/or distribute this software for any
0c39b3ed9409ecb277d5e32fa763a4e4d6598df8Automatic Updater - purpose with or without fee is hereby granted, provided that the above
46da3117812814a29432a8d9a9ccf8acdbfdadceAutomatic Updater - copyright notice and this permission notice appear in all copies.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater -
cd0aa2d941d1438fabb5337f1f38c49478edf71dAutomatic Updater - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater - PERFORMANCE OF THIS SOFTWARE.
e171a4137c6ba348957e61b7c4c3541493c0da02Automatic Updater-->
e171a4137c6ba348957e61b7c4c3541493c0da02Automatic Updater<!-- $Id$ -->
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<html>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<head>
3cc98b8ecedcbc8465f1cf2740b966b315662430Automatic Updater<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<title>Chapter�6.�BIND 9 Configuration Reference</title>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
e171a4137c6ba348957e61b7c4c3541493c0da02Automatic Updater<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
831f79c4310a7d38fc3475ccfff531b2b2535641Automatic Updater<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<link rel="prev" href="Bv9ARM.ch05.html" title="Chapter�5.�The BIND 9 Lightweight Resolver">
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<link rel="next" href="Bv9ARM.ch07.html" title="Chapter�7.�BIND 9 Security Considerations">
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews</head>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<div class="navheader">
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<table width="100%" summary="Navigation header">
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<tr><th colspan="3" align="center">Chapter�6.�<acronym class="acronym">BIND</acronym> 9 Configuration Reference</th></tr>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<tr>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<td width="20%" align="left">
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<a accesskey="p" href="Bv9ARM.ch05.html">Prev</a>�</td>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<th width="60%" align="center">�</th>
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch07.html">Next</a>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater</td>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater</tr>
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt</table>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<hr>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater</div>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<div class="chapter" lang="en">
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<div class="titlepage"><div><div><h2 class="title">
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<a name="Bv9ARM.ch06"></a>Chapter�6.�<acronym class="acronym">BIND</acronym> 9 Configuration Reference</h2></div></div></div>
2d2dc37599979c83495510f8af8d1756753aa2c5Automatic Updater<div class="toc">
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<p><b>Table of Contents</b></p>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dl>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect1"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dd><dl>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2573300">Comment Syntax</a></span></dt>
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater</dl></dd>
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater<dt><span class="sect1"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dd><dl>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574165"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#acl"><span><strong class="command">acl</strong></span> Statement Definition and
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater Usage</a></span></dt>
eabc9c3c07cd956d3c436bd7614cb162dabdda76Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574423"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt>
eabc9c3c07cd956d3c436bd7614cb162dabdda76Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and
eabc9c3c07cd956d3c436bd7614cb162dabdda76Mark Andrews Usage</a></span></dt>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574782"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574800"><span><strong class="command">include</strong></span> Statement Definition and
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Usage</a></span></dt>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574891"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt>
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574915"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575009"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt>
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575144"><span><strong class="command">logging</strong></span> Statement Definition and
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Usage</a></span></dt>
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577350"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt>
80faf1588895fd26490f82f95a7a1b771df1c324Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577447"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577611"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577660"><span><strong class="command">masters</strong></span> Statement Definition and
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Usage</a></span></dt>
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577682"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt>
693c4232dfdffaff672197d4b9fea944c64cf80aAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Usage</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater Usage</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#statschannels"><span><strong class="command">statistics-channels</strong></span> Statement Grammar</a></span></dt>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2592668"><span><strong class="command">statistics-channels</strong></span> Statement Definition and
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater Usage</a></span></dt>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<dt><span class="sect2"><a href="Bv9ARM.ch06.html#trusted-keys"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593085"><span><strong class="command">trusted-keys</strong></span> Statement Definition
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater and Usage</a></span></dt>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593139"><span><strong class="command">managed-keys</strong></span> Statement Grammar</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#managed-keys"><span><strong class="command">managed-keys</strong></span> Statement Definition
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater and Usage</a></span></dt>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span><strong class="command">view</strong></span> Statement Grammar</a></span></dt>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593574"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
b1265b5a06df36d490d4bdf54284fb133a1f5a84Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater Statement Grammar</a></span></dt>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2595590"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
2a31bd531072824ef252c18303859d6af7451b00Francis Dupont</dl></dd>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2599216">Zone File</a></span></dt>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater<dd><dl>
2a31bd531072824ef252c18303859d6af7451b00Francis Dupont<dt><span class="sect2"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2601446">Discussion of MX Records</a></span></dt>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2601993">Inverse Mapping in IPv4</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2602120">Other Zone File Directives</a></span></dt>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2602461"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
08e3b6797706a13054bad749dea04e94b514b8e7Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater</dl></dd>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<dt><span class="sect1"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch06.html#statistics_counters">Statistics Counters</a></span></dt></dl></dd>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater</dl>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater</div>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <acronym class="acronym">BIND</acronym> 9 configuration is broadly similar
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater to <acronym class="acronym">BIND</acronym> 8; however, there are a few new
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater areas
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews of configuration, such as views. <acronym class="acronym">BIND</acronym>
0c39b3ed9409ecb277d5e32fa763a4e4d6598df8Automatic Updater 8 configuration files should work with few alterations in <acronym class="acronym">BIND</acronym>
0c39b3ed9409ecb277d5e32fa763a4e4d6598df8Automatic Updater 9, although more complex configurations should be reviewed to check
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater if they can be more efficiently implemented using the new features
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater found in <acronym class="acronym">BIND</acronym> 9.
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater </p>
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater<p>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater <acronym class="acronym">BIND</acronym> 4 configuration files can be
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater converted to the new format
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater using the shell script
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater <code class="filename">contrib/named-bootconf/named-bootconf.sh</code>.
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<div class="sect1" lang="en">
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<div class="titlepage"><div><div><h2 class="title" style="clear: both">
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<a name="configuration_file_elements"></a>Configuration File Elements</h2></div></div></div>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<p>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater Following is a list of elements used throughout the <acronym class="acronym">BIND</acronym> configuration
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater file documentation:
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater </p>
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater<div class="informaltable"><table border="1">
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater<colgroup>
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater<col>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<col>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson</colgroup>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<tbody>
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater<tr>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater <p>
0ce87e5749aabb8eef1e0a37e4bd6e6ffa1d7196Automatic Updater <code class="varname">acl_name</code>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </td>
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater<td>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater <p>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater The name of an <code class="varname">address_match_list</code> as
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater defined by the <span><strong class="command">acl</strong></span> statement.
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater </p>
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater </td>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<td>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater <p>
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater <code class="varname">address_match_list</code>
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
bc0a53583d92309bebcf93c408e2f3247ebd3d3cAutomatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A list of one or more
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="varname">ip_addr</code>,
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater <code class="varname">ip_prefix</code>, <code class="varname">key_id</code>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater or <code class="varname">acl_name</code> elements, see
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called &#8220;Address Match Lists&#8221;</a>.
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater </p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater<tr>
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
19b3dc94bce93fa76bd7e066f9298630dbc9dcb4Automatic Updater <code class="varname">masters_list</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater </td>
7f94d9a8162c9a96b56e66176702b66e79d8e1a2Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A named list of one or more <code class="varname">ip_addr</code>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater with optional <code class="varname">key_id</code> and/or
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater <code class="varname">ip_port</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A <code class="varname">masters_list</code> may include other
71bd43eebd9d6e42dbcae62b730f5b6508d5acd8Automatic Updater <code class="varname">masters_lists</code>.
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </p>
7262eb86f2b465822206122921e2f357218f0cfdAutomatic Updater </td>
96ea71632887c58a9d00f47eb318bf76b35903c3Mark Andrews</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
bbb069be941f649228760edcc241122933c066d2Automatic Updater <p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <code class="varname">domain_name</code>
4cda4fd158d6ded5586bacea8c388445d99611eaAutomatic Updater </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
80faf1588895fd26490f82f95a7a1b771df1c324Automatic Updater <p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews A quoted string which will be used as
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a DNS name, for example "<code class="literal">my.test.domain</code>".
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</tr>
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater<tr>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<td>
f7c88d61cc1ad2435b0b7cfaedfc9d5248c0be25Automatic Updater <p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <code class="varname">namelist</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater </td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater A list of one or more <code class="varname">domain_name</code>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater elements.
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater</tr>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<tr>
cf7e98f59148b559946a7f1ca728471374f1eef3Automatic Updater<td>
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater <p>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater <code class="varname">dotted_decimal</code>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
cf7e98f59148b559946a7f1ca728471374f1eef3Automatic Updater<td>
c3fd32ed29e9e419bb56583f4272a506773b1ea0Automatic Updater <p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson One to four integers valued 0 through
c3fd32ed29e9e419bb56583f4272a506773b1ea0Automatic Updater 255 separated by dots (`.'), such as <span><strong class="command">123</strong></span>,
c3fd32ed29e9e419bb56583f4272a506773b1ea0Automatic Updater <span><strong class="command">45.67</strong></span> or <span><strong class="command">89.123.45.67</strong></span>.
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater </p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </td>
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<td>
3857cb6fcabeb79d85de4b3e3e4ab99912b701f8Mark Andrews <p>
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater <code class="varname">ip4_addr</code>
7858b0168b866c0c2878fc4ea31fb5e581c1a6a9Automatic Updater </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
9174e44c14b1cb91a651fa1dc29470438c246ab9Automatic Updater<td>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson <p>
e2caa7536302de34de6cc04025abcd53dc3a499aAutomatic Updater An IPv4 address with exactly four elements
56e7dc0c24b04210dcbffb180a9e35644fb820daAutomatic Updater in <code class="varname">dotted_decimal</code> notation.
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater </p>
8292deab031e7599cd7622aa7675fbe139ca6095Mark Andrews </td>
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews</tr>
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews<tr>
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews<td>
ca35524ce2b57e6f1b261d23565d1288a355d12fAutomatic Updater <p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews <code class="varname">ip6_addr</code>
b109432c3a939bff66a463be86c371bd88efe3aaAutomatic Updater </p>
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater </td>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<td>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews <p>
3351ccbd5c1961404044f8273d54dad405f53960Mark Andrews An IPv6 address, such as <span><strong class="command">2001:db8::1234</strong></span>.
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater IPv6 scoped addresses that have ambiguity on their
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews scope zones must be disambiguated by an appropriate
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews zone ID with the percent character (`%') as
3351ccbd5c1961404044f8273d54dad405f53960Mark Andrews delimiter. It is strongly recommended to use
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater string zone names rather than numeric identifiers,
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews in order to be robust against system configuration
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews changes. However, since there is no standard
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater mapping for such names and identifier values,
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews currently only interface names as link identifiers
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater are supported, assuming one-to-one mapping between
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater interfaces and links. For example, a link-local
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater address <span><strong class="command">fe80::1</strong></span> on the link
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater attached to the interface <span><strong class="command">ne0</strong></span>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater can be specified as <span><strong class="command">fe80::1%ne0</strong></span>.
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater Note that on most systems link-local addresses
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater always have the ambiguity, and need to be
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater disambiguated.
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater </p>
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<tr>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater <code class="varname">ip_addr</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews An <code class="varname">ip4_addr</code> or <code class="varname">ip6_addr</code>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
06f5acb11f1c32228d93eefd1eb841dbfb1c7f4dAutomatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater<tr>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<td>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson <p>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater <code class="varname">ip_dscp</code>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews </p>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews </td>
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington A <code class="varname">number</code> between 0 and 63, used
b13d89bd89878137c81b36a36596cca3920f27a4Automatic Updater to select a differentiated services code point (DSCP)
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater value for use with outgoing traffic on operating systems
b13d89bd89878137c81b36a36596cca3920f27a4Automatic Updater that support DSCP.
b13d89bd89878137c81b36a36596cca3920f27a4Automatic Updater </p>
b13d89bd89878137c81b36a36596cca3920f27a4Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <code class="varname">ip_port</code>
b1265b5a06df36d490d4bdf54284fb133a1f5a84Automatic Updater </p>
bc0a4c01beede169df81a3ee5b614ed9e82339dbAutomatic Updater </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington An IP port <code class="varname">number</code>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The <code class="varname">number</code> is limited to 0
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington through 65535, with values
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington below 1024 typically restricted to use by processes running
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington as root.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington In some cases, an asterisk (`*') character can be used as a
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington placeholder to
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington select a random high-numbered port.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">ip_prefix</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington An IP network specified as an <code class="varname">ip_addr</code>,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington followed by a slash (`/') and then the number of bits in the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington netmask.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Trailing zeros in a <code class="varname">ip_addr</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington may omitted.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington For example, <span><strong class="command">127/8</strong></span> is the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington network <span><strong class="command">127.0.0.0</strong></span> with
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington netmask <span><strong class="command">255.0.0.0</strong></span> and <span><strong class="command">1.2.3.0/28</strong></span> is
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington network <span><strong class="command">1.2.3.0</strong></span> with netmask <span><strong class="command">255.255.255.240</strong></span>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington When specifying a prefix involving a IPv6 scoped address
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the scope may be omitted. In that case the prefix will
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington match packets from any scope.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">key_id</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington A <code class="varname">domain_name</code> representing
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the name of a shared key, to be used for transaction
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington security.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <code class="varname">key_list</code>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater A list of one or more
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <code class="varname">key_id</code>s,
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater separated by semicolons and ending with a semicolon.
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater</tr>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<tr>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <p>
0d3490f93bb980fde704055e74c1b508987a5fe4Mark Andrews <code class="varname">number</code>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington </p>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington </td>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington<td>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington <p>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews A non-negative 32-bit integer
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews (i.e., a number between 0 and 4294967295, inclusive).
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Its acceptable value might further
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews be limited by the context in which it is used.
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington </p>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews </td>
348040cb2675f1c3711672dadfc29f5ddfd2bb23Automatic Updater</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater<td>
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">path_name</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A quoted string which will be used as
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a pathname, such as <code class="filename">zones/master/my.test.domain</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater<td>
e01f44b37ba11c9d34f4a8394f950efae5c07f33Automatic Updater <p>
e01f44b37ba11c9d34f4a8394f950efae5c07f33Automatic Updater <code class="varname">port_list</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
c01dec514a81ecf8c17ca3ef8c3ba95e437295ebAutomatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A list of an <code class="varname">ip_port</code> or a port
3de6db3208d51de1e138b63b9670430c03f99694Automatic Updater range.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A port range is specified in the form of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <strong class="userinput"><code>range</code></strong> followed by
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington two <code class="varname">ip_port</code>s,
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <code class="varname">port_low</code> and
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">port_high</code>, which represents
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington port numbers from <code class="varname">port_low</code> through
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">port_high</code>, inclusive.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">port_low</code> must not be larger than
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">port_high</code>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington For example,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>range 1024 65535</code></strong> represents
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington ports from 1024 through 65535.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington In either case an asterisk (`*') character is not
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington allowed as a valid <code class="varname">ip_port</code>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">size_spec</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews </td>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington A 64-bit unsigned integer, or the keywords
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater <strong class="userinput"><code>unlimited</code></strong> or
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <strong class="userinput"><code>default</code></strong>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
a26b22914b7bf25f065afb8cdef983766dcd672bAutomatic Updater Integers may take values
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater 0 &lt;= value &lt;= 18446744073709551615, though
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater certain parameters
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater (such as <span><strong class="command">max-journal-size</strong></span>) may
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington use a more limited range within these extremes.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater In most cases, setting a value to 0 does not
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington literally mean zero; it means "undefined" or
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews "as big as possible", depending on the context.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews See the explanations of particular parameters
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington that use <code class="varname">size_spec</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington for details on how they interpret its use.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Numeric values can optionally be followed by a
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington scaling factor:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>K</code></strong> or <strong class="userinput"><code>k</code></strong>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington for kilobytes,
b7aab05edae933e169d5f83c653935b17c7f0a8bMark Andrews <strong class="userinput"><code>M</code></strong> or <strong class="userinput"><code>m</code></strong>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington for megabytes, and
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>G</code></strong> or <strong class="userinput"><code>g</code></strong>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington for gigabytes, which scale by 1024, 1024*1024, and
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews 1024*1024*1024 respectively.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">unlimited</code> generally means
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews "as big as possible", and is usually the best
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington way to safely set a very large number.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater <code class="varname">default</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington uses the limit that was in force when the server was started.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">yes_or_no</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater Either <strong class="userinput"><code>yes</code></strong> or <strong class="userinput"><code>no</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The words <strong class="userinput"><code>true</code></strong> and <strong class="userinput"><code>false</code></strong> are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater also accepted, as are the numbers <strong class="userinput"><code>1</code></strong>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and <strong class="userinput"><code>0</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">dialup_option</code>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews One of <strong class="userinput"><code>yes</code></strong>,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>no</code></strong>, <strong class="userinput"><code>notify</code></strong>,
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews <strong class="userinput"><code>notify-passive</code></strong>, <strong class="userinput"><code>refresh</code></strong> or
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews <strong class="userinput"><code>passive</code></strong>.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews When used in a zone, <strong class="userinput"><code>notify-passive</code></strong>,
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews <strong class="userinput"><code>refresh</code></strong>, and <strong class="userinput"><code>passive</code></strong>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews are restricted to slave and stub zones.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tbody>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</table></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="sect2" lang="en">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="titlepage"><div><div><h3 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="address_match_lists"></a>Address Match Lists</h3></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="sect3" lang="en">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="titlepage"><div><div><h4 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="id2573131"></a>Syntax</h4></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting"><code class="varname">address_match_list</code> = address_match_list_element ;
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater [<span class="optional"> address_match_list_element; ... </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<code class="varname">address_match_list_element</code> = [<span class="optional"> ! </span>] (ip_address [<span class="optional">/length</span>] |
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington key key_id | acl_name | { address_match_list } )
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect3" lang="en">
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater<div class="titlepage"><div><div><h4 class="title">
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater<a name="id2573159"></a>Definition and Usage</h4></div></div></div>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Address match lists are primarily used to determine access
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater control for various server operations. They are also used in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the <span><strong class="command">listen-on</strong></span> and <span><strong class="command">sortlist</strong></span>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater statements. The elements which constitute an address match
b0d566a2ce0f5a67f537ee7f8233f82f2584cc61Automatic Updater list can be any of the following:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater<div class="itemizedlist"><ul type="disc">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<li>an IP address (IPv4 or IPv6)</li>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<li>an IP prefix (in `/' notation)</li>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<li>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater a key ID, as defined by the <span><strong class="command">key</strong></span>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater statement
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater </li>
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater<li>the name of an address match list defined with
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater the <span><strong class="command">acl</strong></span> statement
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater </li>
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater<li>a nested address match list enclosed in braces</li>
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater</ul></div>
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater<p>
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater Elements can be negated with a leading exclamation mark (`!'),
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater and the match list names "any", "none", "localhost", and
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater "localnets" are predefined. More information on those names
e8c17c74535be290abaaa160a434ed80bf0ad2feMark Andrews can be found in the description of the acl statement.
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater </p>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater<p>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater The addition of the key clause made the name of this syntactic
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater element something of a misnomer, since security keys can be used
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater to validate access without regard to a host or network address.
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater Nonetheless, the term "address match list" is still used
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater throughout the documentation.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater When a given IP address or prefix is compared to an address
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater match list, the comparison takes place in approximately O(1)
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater time. However, key comparisons require that the list of keys
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater be traversed until a matching key is found, and therefore may
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater be somewhat slower.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater The interpretation of a match depends on whether the list is being
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater used for access control, defining <span><strong class="command">listen-on</strong></span> ports, or in a
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">sortlist</strong></span>, and whether the element was negated.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater When used as an access control list, a non-negated match
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater allows access and a negated match denies access. If
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater there is no match, access is denied. The clauses
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-notify</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-recursion</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-recursion-on</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-query</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-query-on</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-query-cache</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-query-cache-on</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-transfer</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-update</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">allow-update-forwarding</strong></span>,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">blackhole</strong></span>, and
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">keep-response-order</strong></span> all use address match
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater lists. Similarly, the <span><strong class="command">listen-on</strong></span> option will cause the
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater server to refuse queries on any of the machine's
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater addresses which do not match the list.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater Order of insertion is significant. If more than one element
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater in an ACL is found to match a given IP address or prefix,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater preference will be given to the one that came
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span class="emphasis"><em>first</em></span> in the ACL definition.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater Because of this first-match behavior, an element that
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater defines a subset of another element in the list should
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater come before the broader element, regardless of whether
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater either is negated. For example, in
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <span><strong class="command">1.2.3/24; ! 1.2.3.13;</strong></span>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater the 1.2.3.13 element is completely useless because the
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater algorithm will match any lookup for 1.2.3.13 to the 1.2.3/24
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater element. Using <span><strong class="command">! 1.2.3.13; 1.2.3/24</strong></span> fixes
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater that problem by having 1.2.3.13 blocked by the negation, but
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater all other 1.2.3.* hosts fall through.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater</div>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</div>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<div class="sect2" lang="en">
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews<a name="id2573300"></a>Comment Syntax</h3></div></div></div>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews<p>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews The <acronym class="acronym">BIND</acronym> 9 comment syntax allows for
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews comments to appear
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater anywhere that whitespace may appear in a <acronym class="acronym">BIND</acronym> configuration
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater file. To appeal to programmers of all kinds, they can be written
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater in the C, C++, or shell/perl style.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<div class="sect3" lang="en">
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<div class="titlepage"><div><div><h4 class="title">
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<a name="id2573383"></a>Syntax</h4></div></div></div>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<pre class="programlisting">/* This is a <acronym class="acronym">BIND</acronym> comment as in C */</pre>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<p>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater </p>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater<pre class="programlisting">// This is a <acronym class="acronym">BIND</acronym> comment as in C++</pre>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<pre class="programlisting"># This is a <acronym class="acronym">BIND</acronym> comment as in common UNIX shells
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater# and perl</pre>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</div>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<div class="sect3" lang="en">
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<div class="titlepage"><div><div><h4 class="title">
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<a name="id2573413"></a>Definition and Usage</h4></div></div></div>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater Comments may appear anywhere that whitespace may appear in
19dbf2e20df03f2b81ed1f347e27718084374059Automatic Updater a <acronym class="acronym">BIND</acronym> configuration file.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater C-style comments start with the two characters /* (slash,
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater star) and end with */ (star, slash). Because they are completely
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater delimited with these characters, they can be used to comment only
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater a portion of a line or to span multiple lines.
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater C-style comments cannot be nested. For example, the following
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater is not valid because the entire comment ends with the first */:
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater</p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">/* This is the start of a comment.
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington This is still part of the comment.
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington/* This is an incorrect attempt at nesting a comment. */
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington This is no longer in any comment. */
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater C++-style comments start with the two characters // (slash,
0fde13e46fef2ac9d8250adb92263f436425a914Automatic Updater slash) and continue to the end of the physical line. They cannot
0fde13e46fef2ac9d8250adb92263f436425a914Automatic Updater be continued across multiple physical lines; to have one logical
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater comment span multiple lines, each line must use the // pair.
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater For example:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">// This is the start of a comment. The next line
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater// is a new comment, even though it is logically
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater// part of the previous comment.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater<p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater<p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater Shell-style (or perl-style, if you prefer) comments start
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater with the character <code class="literal">#</code> (number sign)
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and continue to the end of the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater physical line, as in C++ comments.
ff62ab3c2e6274f19190ded15548c723d38bbbe3Automatic Updater For example:
ff62ab3c2e6274f19190ded15548c723d38bbbe3Automatic Updater </p>
ff62ab3c2e6274f19190ded15548c723d38bbbe3Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater</p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting"># This is the start of a comment. The next line
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater# is a new comment, even though it is logically
d9f94d668f4b9342e9367d80e9fc6e81fab303a0Mark Andrews# part of the previous comment.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<h3 class="title">Warning</h3>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington You cannot use the semicolon (`;') character
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to start a comment such as you would in a zone file. The
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater semicolon indicates the end of a configuration
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statement.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect1" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h2 class="title" style="clear: both">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="Configuration_File_Grammar"></a>Configuration File Grammar</h2></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater A <acronym class="acronym">BIND</acronym> 9 configuration consists of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statements and comments.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Statements end with a semicolon. Statements and comments are the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater only elements that can appear without enclosing braces. Many
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statements contain a block of sub-statements, which are also
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater terminated with a semicolon.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The following statements are supported:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="informaltable"><table border="1">
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater<colgroup>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<col>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<col>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</colgroup>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tbody>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater <p><span><strong class="command">acl</strong></span></p>
9fa39c73fc1d8bc44fdbbb79a1d26b837e7dd555Mark Andrews </td>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater<td>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater <p>
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater defines a named IP address
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater matching list, for access control and other uses.
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater </p>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater </td>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater</tr>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater<tr>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater<td>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater <p><span><strong class="command">controls</strong></span></p>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater </td>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater<td>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews <p>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews declares control channels to be used
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews by the <span><strong class="command">rndc</strong></span> utility.
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews </p>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews </td>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews</tr>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews<tr>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<td>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater <p><span><strong class="command">include</strong></span></p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </td>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<td>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater <p>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater includes a file.
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </td>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater</tr>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<tr>
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont<td>
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont <p><span><strong class="command">key</strong></span></p>
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont </td>
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont<td>
4dca64bb8991502db368028aeeba2f832d3b971dAutomatic Updater <p>
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont specifies key information for use in
4dca64bb8991502db368028aeeba2f832d3b971dAutomatic Updater authentication and authorization using TSIG.
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater </p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater </td>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater</tr>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<tr>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<td>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater <p><span><strong class="command">logging</strong></span></p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater </td>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<td>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater <p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater specifies what the server logs, and where
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater the log messages are sent.
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater </p>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater </td>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater</tr>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<tr>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<td>
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater <p><span><strong class="command">lwres</strong></span></p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater </td>
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater<td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater <p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater configures <span><strong class="command">named</strong></span> to
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater also act as a light-weight resolver daemon (<span><strong class="command">lwresd</strong></span>).
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</tr>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p><span><strong class="command">masters</strong></span></p>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater </td>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<td>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater defines a named masters list for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater inclusion in stub and slave zones'
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater <span><strong class="command">masters</strong></span> or
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">also-notify</strong></span> lists.
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
2da2220fe7af2c45724b50b0187523b1fab0cf08Rob Austein</tr>
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater<tr>
e171a4137c6ba348957e61b7c4c3541493c0da02Automatic Updater<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p><span><strong class="command">options</strong></span></p>
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater </td>
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater controls global server configuration
5acd63107041b5b0bed444e2bc29f4bca0c13e28Automatic Updater options and sets defaults for other statements.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</tr>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater <p><span><strong class="command">server</strong></span></p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </td>
5acd63107041b5b0bed444e2bc29f4bca0c13e28Automatic Updater<td>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater sets certain configuration options on
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater a per-server basis.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </td>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</tr>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<tr>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<td>
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater <p><span><strong class="command">statistics-channels</strong></span></p>
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater </td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater <p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater declares communication channels to get access to
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <span><strong class="command">named</strong></span> statistics.
5acd63107041b5b0bed444e2bc29f4bca0c13e28Automatic Updater </p>
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater </td>
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater</tr>
664917bedafa65dee4349c84324a31731aa1e228Francis Dupont<tr>
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p><span><strong class="command">trusted-keys</strong></span></p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater defines trusted DNSSEC keys.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater </td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater</tr>
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater<tr>
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater<td>
f8a9a38ee40c139a8d145ac76ecbff3a0f986453Mark Andrews <p><span><strong class="command">managed-keys</strong></span></p>
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater </td>
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater<td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater <p>
9d80d23172c30fd63e5046a7e69b8445e564ff31Automatic Updater lists DNSSEC keys to be kept up to date
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater using RFC 5011 trust anchor maintenance.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews</tr>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<tr>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews <p><span><strong class="command">view</strong></span></p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews <p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews defines a view.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews</tr>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<tr>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews <p><span><strong class="command">zone</strong></span></p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews <p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews defines a zone.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </td>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews</tr>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews</tbody>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews</table></div>
8c9c79e5fea0cb698026a74821695907c8312a46Mark Andrews<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater The <span><strong class="command">logging</strong></span> and
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <span><strong class="command">options</strong></span> statements may only occur once
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater per
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater configuration.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<div class="sect2" lang="en">
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<a name="id2574165"></a><span><strong class="command">acl</strong></span> Statement Grammar</h3></div></div></div>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<pre class="programlisting"><span><strong class="command">acl</strong></span> acl-name {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater address_match_list
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington};
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect2" lang="en">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="titlepage"><div><div><h3 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="acl"></a><span><strong class="command">acl</strong></span> Statement Definition and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Usage</h3></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The <span><strong class="command">acl</strong></span> statement assigns a symbolic
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater name to an address match list. It gets its name from a primary
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater use of address match lists: Access Control Lists (ACLs).
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The following ACLs are built-in:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater<div class="informaltable"><table border="1">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<colgroup>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<col>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<col>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</colgroup>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tbody>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
bbf7c3fd96ae5e02cb84743c581862e35327032aAutomatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">any</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Matches all hosts.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews </td>
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater</tr>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater<tr>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater<td>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater <p><span><strong class="command">none</strong></span></p>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater </td>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater<td>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater <p>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater Matches no hosts.
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater </p>
06795359e2bc153a46f9f2f793a732b0e508f61dAutomatic Updater </td>
7a6ad11e0185a73984410f3252f3c49c3a301dbdBrian Wellington</tr>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
7a6ad11e0185a73984410f3252f3c49c3a301dbdBrian Wellington <p><span><strong class="command">localhost</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Matches the IPv4 and IPv6 addresses of all network
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington interfaces on the system. When addresses are
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington added or removed, the <span><strong class="command">localhost</strong></span>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington ACL element is updated to reflect the changes.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">localnets</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<td>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater <p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater Matches any host on an IPv4 or IPv6 network
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater for which the system has an interface.
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater When addresses are added or removed,
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater the <span><strong class="command">localnets</strong></span>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater ACL element is updated to reflect the changes.
792b362aef91cab66c7075ad89b86194b6312d8bScott Mann Some systems do not provide a way to determine the prefix
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater lengths of
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington local IPv6 addresses.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater In such a case, <span><strong class="command">localnets</strong></span>
f65d2e1c04c806a185bf9f3120e80692f5ccd5e6Automatic Updater only matches the local
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington IPv6 addresses, just like <span><strong class="command">localhost</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
bbb069be941f649228760edcc241122933c066d2Automatic Updater</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tbody>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</table></div>
e062b72f783cdb436a1a57a630bdff471dbb3038Mark Andrews</div>
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="id2574423"></a><span><strong class="command">controls</strong></span> Statement Grammar</h3></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting"><span><strong class="command">controls</strong></span> {
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater [ inet ( ip_addr | * ) [ port ip_port ]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater allow { <em class="replaceable"><code> address_match_list </code></em> }
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater keys { <em class="replaceable"><code>key_list</code></em> }; ]
3e79333aa37d3b88959372431a02af8a3eb7cfd9Automatic Updater [ inet ...; ]
e076d0c88be69de7c190ab924d095e69d2e11f7aAndreas Gustafsson [ unix <em class="replaceable"><code>path</code></em> perm <em class="replaceable"><code>number</code></em> owner <em class="replaceable"><code>number</code></em> group <em class="replaceable"><code>number</code></em>
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater keys { <em class="replaceable"><code>key_list</code></em> }; ]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [ unix ...; ]
e076d0c88be69de7c190ab924d095e69d2e11f7aAndreas Gustafsson};
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="controls_statement_definition_and_usage"></a><span><strong class="command">controls</strong></span> Statement Definition and
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater Usage</h3></div></div></div>
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater<p>
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater The <span><strong class="command">controls</strong></span> statement declares control
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater channels to be used by system administrators to control the
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater operation of the name server. These control channels are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater used by the <span><strong class="command">rndc</strong></span> utility to send
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater commands to and retrieve non-DNS results from a name server.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater An <span><strong class="command">inet</strong></span> control channel is a TCP socket
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater listening at the specified <span><strong class="command">ip_port</strong></span> on the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater specified <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater address. An <span><strong class="command">ip_addr</strong></span> of <code class="literal">*</code> (asterisk) is
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater interpreted as the IPv4 wildcard address; connections will be
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater accepted on any of the system's IPv4 addresses.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater To listen on the IPv6 wildcard address,
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>.
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater If you will only use <span><strong class="command">rndc</strong></span> on the local host,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater using the loopback address (<code class="literal">127.0.0.1</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington or <code class="literal">::1</code>) is recommended for maximum security.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington If no port is specified, port 953 is used. The asterisk
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater "<code class="literal">*</code>" cannot be used for <span><strong class="command">ip_port</strong></span>.
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater </p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater The ability to issue commands over the control channel is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater restricted by the <span><strong class="command">allow</strong></span> and
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">keys</strong></span> clauses.
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater Connections to the control channel are permitted based on the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">address_match_list</strong></span>. This is for simple
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IP address based filtering only; any <span><strong class="command">key_id</strong></span>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington elements of the <span><strong class="command">address_match_list</strong></span>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater are ignored.
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater </p>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater A <span><strong class="command">unix</strong></span> control channel is a UNIX domain
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington socket listening at the specified path in the file system.
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater Access to the socket is specified by the <span><strong class="command">perm</strong></span>,
47ce374fcf4bac7a56bb69f5dae1d30be5b4376dAutomatic Updater <span><strong class="command">owner</strong></span> and <span><strong class="command">group</strong></span> clauses.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Note on some platforms (SunOS and Solaris) the permissions
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater (<span><strong class="command">perm</strong></span>) are applied to the parent directory
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater as the permissions on the socket itself are ignored.
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater </p>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater<p>
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater The primary authorization mechanism of the command
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater channel is the <span><strong class="command">key_list</strong></span>, which
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater contains a list of <span><strong class="command">key_id</strong></span>s.
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater Each <span><strong class="command">key_id</strong></span> in the <span><strong class="command">key_list</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater is authorized to execute commands over the control channel.
fd8fb4df8499e292daeac765f599ac7c507d9ca3Mark Andrews See <a href="Bv9ARM.ch03.html#rndc">Remote Name Daemon Control application</a> in <a href="Bv9ARM.ch03.html#admin_tools" title="Administrative Tools">the section called &#8220;Administrative Tools&#8221;</a>)
fd8fb4df8499e292daeac765f599ac7c507d9ca3Mark Andrews for information about configuring keys in <span><strong class="command">rndc</strong></span>.
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater </p>
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater<p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater If no <span><strong class="command">controls</strong></span> statement is present,
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater <span><strong class="command">named</strong></span> will set up a default
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater control channel listening on the loopback address 127.0.0.1
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater and its IPv6 counterpart ::1.
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater In this case, and also when the <span><strong class="command">controls</strong></span> statement
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater is present but does not have a <span><strong class="command">keys</strong></span> clause,
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater <span><strong class="command">named</strong></span> will attempt to load the command channel key
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater from the file <code class="filename">rndc.key</code> in
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater <code class="filename">/etc</code> (or whatever <code class="varname">sysconfdir</code>
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater was specified as when <acronym class="acronym">BIND</acronym> was built).
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater To create a <code class="filename">rndc.key</code> file, run
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater <strong class="userinput"><code>rndc-confgen -a</code></strong>.
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater </p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater<p>
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater The <code class="filename">rndc.key</code> feature was created to
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater ease the transition of systems from <acronym class="acronym">BIND</acronym> 8,
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater which did not have digital signatures on its command channel
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater messages and thus did not have a <span><strong class="command">keys</strong></span> clause.
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater It makes it possible to use an existing <acronym class="acronym">BIND</acronym> 8
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews configuration file in <acronym class="acronym">BIND</acronym> 9 unchanged,
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater and still have <span><strong class="command">rndc</strong></span> work the same way
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <span><strong class="command">ndc</strong></span> worked in BIND 8, simply by executing the
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater command <strong class="userinput"><code>rndc-confgen -a</code></strong> after BIND 9 is
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater installed.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Since the <code class="filename">rndc.key</code> feature
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater is only intended to allow the backward-compatible usage of
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <acronym class="acronym">BIND</acronym> 8 configuration files, this
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater feature does not
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater have a high degree of configurability. You cannot easily change
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater the key name or the size of the secret, so you should make a
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <code class="filename">rndc.conf</code> with your own key if you
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater wish to change
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater those things. The <code class="filename">rndc.key</code> file
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater also has its
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater permissions set such that only the owner of the file (the user that
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <span><strong class="command">named</strong></span> is running as) can access it.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If you
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington desire greater flexibility in allowing other users to access
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">rndc</strong></span> commands, then you need to create
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="filename">rndc.conf</code> file and make it group
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater readable by a group
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater that contains the users who should have access.
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater </p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater To disable the command channel, use an empty
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">controls</strong></span> statement:
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater <span><strong class="command">controls { };</strong></span>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
53aed64e0f8553762fc0c380ee41cb42f514c7d5Brian Wellington<a name="id2574782"></a><span><strong class="command">include</strong></span> Statement Grammar</h3></div></div></div>
19dbf2e20df03f2b81ed1f347e27718084374059Automatic Updater<pre class="programlisting"><span><strong class="command">include</strong></span> <em class="replaceable"><code>filename</code></em>;</pre>
53aed64e0f8553762fc0c380ee41cb42f514c7d5Brian Wellington</div>
6de27e27ad6056d7c049feb912df5a6b9a56d1b8Automatic Updater<div class="sect2" lang="en">
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater<div class="titlepage"><div><div><h3 class="title">
53aed64e0f8553762fc0c380ee41cb42f514c7d5Brian Wellington<a name="id2574800"></a><span><strong class="command">include</strong></span> Statement Definition and
6de27e27ad6056d7c049feb912df5a6b9a56d1b8Automatic Updater Usage</h3></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater The <span><strong class="command">include</strong></span> statement inserts the
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater specified file at the point where the <span><strong class="command">include</strong></span>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater statement is encountered. The <span><strong class="command">include</strong></span>
a6e1f63f50af688610ebd2521ba7f028767b51f3Mark Andrews statement facilitates the administration of configuration
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater files
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater by permitting the reading or writing of some things but not
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater others. For example, the statement could include private keys
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater that are readable only by the name server.
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</div>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<div class="sect2" lang="en">
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater<div class="titlepage"><div><div><h3 class="title">
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<a name="id2574891"></a><span><strong class="command">key</strong></span> Statement Grammar</h3></div></div></div>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater<pre class="programlisting"><span><strong class="command">key</strong></span> <em class="replaceable"><code>key_id</code></em> {
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater algorithm <em class="replaceable"><code>string</code></em>;
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater secret <em class="replaceable"><code>string</code></em>;
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater};
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater</div>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater<div class="sect2" lang="en">
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater<div class="titlepage"><div><div><h3 class="title">
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater<a name="id2574915"></a><span><strong class="command">key</strong></span> Statement Definition and Usage</h3></div></div></div>
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater<p>
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater The <span><strong class="command">key</strong></span> statement defines a shared
2f76b9339e44a89cc5195e9c18ea6b01d71c85deAutomatic Updater secret key for use with TSIG (see <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called &#8220;TSIG&#8221;</a>)
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater or the command channel
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater Usage">the section called &#8220;<span><strong class="command">controls</strong></span> Statement Definition and
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater Usage&#8221;</a>).
bde1625cbc0256920625797a2cd4f05312f02ffaMark Andrews </p>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater<p>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater The <span><strong class="command">key</strong></span> statement can occur at the
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater top level
bde1625cbc0256920625797a2cd4f05312f02ffaMark Andrews of the configuration file or inside a <span><strong class="command">view</strong></span>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater statement. Keys defined in top-level <span><strong class="command">key</strong></span>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater statements can be used in all views. Keys intended for use in
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater a <span><strong class="command">controls</strong></span> statement
5645e0c82a55b05abb975bd91b9566823dc5efb0Evan Hunt (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
5645e0c82a55b05abb975bd91b9566823dc5efb0Evan Hunt Usage">the section called &#8220;<span><strong class="command">controls</strong></span> Statement Definition and
5645e0c82a55b05abb975bd91b9566823dc5efb0Evan Hunt Usage&#8221;</a>)
5645e0c82a55b05abb975bd91b9566823dc5efb0Evan Hunt must be defined at the top level.
5645e0c82a55b05abb975bd91b9566823dc5efb0Evan Hunt </p>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater<p>
af3e516f771c8ba376a8cd954a7233badfce8cdcAutomatic Updater The <em class="replaceable"><code>key_id</code></em>, also known as the
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews key name, is a domain name uniquely identifying the key. It can
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews be used in a <span><strong class="command">server</strong></span>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews statement to cause requests sent to that
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews server to be signed with this key, or in address match lists to
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews verify that incoming requests have been signed with a key
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews matching this name, algorithm, and secret.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews The <em class="replaceable"><code>algorithm_id</code></em> is a string
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews that specifies a security/authentication algorithm. The
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <span><strong class="command">named</strong></span> server supports <code class="literal">hmac-md5</code>,
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>,
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews and <code class="literal">hmac-sha512</code> TSIG authentication.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews Truncated hashes are supported by appending the minimum
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews number of required bits preceded by a dash, e.g.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <code class="literal">hmac-sha1-80</code>. The
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <em class="replaceable"><code>secret_string</code></em> is the secret
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews to be used by the algorithm, and is treated as a base-64
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews encoded string.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</div>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<div class="sect2" lang="en">
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<div class="titlepage"><div><div><h3 class="title">
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<a name="id2575009"></a><span><strong class="command">logging</strong></span> Statement Grammar</h3></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting"><span><strong class="command">logging</strong></span> {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [ <span><strong class="command">channel</strong></span> <em class="replaceable"><code>channel_name</code></em> {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater ( <span><strong class="command">file</strong></span> <em class="replaceable"><code>path_name</code></em>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater [ <span><strong class="command">versions</strong></span> ( <em class="replaceable"><code>number</code></em> | <span><strong class="command">unlimited</strong></span> ) ]
af3e516f771c8ba376a8cd954a7233badfce8cdcAutomatic Updater [ <span><strong class="command">size</strong></span> <em class="replaceable"><code>size_spec</code></em> ]
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater | <span><strong class="command">syslog</strong></span> <em class="replaceable"><code>syslog_facility</code></em>
129090f0f6f91753b4a085ab635e28549fd018adAutomatic Updater | <span><strong class="command">stderr</strong></span>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater | <span><strong class="command">null</strong></span> );
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [ <span><strong class="command">severity</strong></span> (<code class="option">critical</code> | <code class="option">error</code> | <code class="option">warning</code> | <code class="option">notice</code> |
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater <code class="option">info</code> | <code class="option">debug</code> [ <em class="replaceable"><code>level</code></em> ] | <code class="option">dynamic</code> ); ]
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater [ <span><strong class="command">print-category</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater [ <span><strong class="command">print-severity</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater [ <span><strong class="command">print-time</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater [ <span><strong class="command">buffered</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater }; ]
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater [ <span><strong class="command">category</strong></span> <em class="replaceable"><code>category_name</code></em> {
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <em class="replaceable"><code>channel_name</code></em> ; [ <em class="replaceable"><code>channel_name</code></em> ; ... ]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater }; ]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater ...
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater};
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater</div>
f55369d776907119cd8699a4119d9c80daa7cae4Mark Andrews<div class="sect2" lang="en">
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<a name="id2575144"></a><span><strong class="command">logging</strong></span> Statement Definition and
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater Usage</h3></div></div></div>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater The <span><strong class="command">logging</strong></span> statement configures a
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater wide
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater variety of logging options for the name server. Its <span><strong class="command">channel</strong></span> phrase
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater associates output methods, format options and severity levels with
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater a name that can then be used with the <span><strong class="command">category</strong></span> phrase
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater to select how various classes of messages are logged.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater Only one <span><strong class="command">logging</strong></span> statement is used to
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater define
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater as many channels and categories as are wanted. If there is no <span><strong class="command">logging</strong></span> statement,
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater the logging configuration will be:
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<pre class="programlisting">logging {
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater category default { default_syslog; default_debug; };
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater category unmatched { null; };
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater};
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater</pre>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater If <span><strong class="command">named</strong></span> is started with the
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <code class="option">-L</code> option, it logs to the specified file
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater at startup, instead of using syslog. In this case the logging
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater configuration will be:
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<pre class="programlisting">logging {
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater category default { default_logfile; default_debug; };
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater category unmatched { null; };
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater};
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
f55369d776907119cd8699a4119d9c80daa7cae4Mark Andrews In <acronym class="acronym">BIND</acronym> 9, the logging configuration
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater is only established when
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the entire configuration file has been parsed. In <acronym class="acronym">BIND</acronym> 8, it was
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater established as soon as the <span><strong class="command">logging</strong></span>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington statement
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater was parsed. When the server is starting up, all logging messages
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington regarding syntax errors in the configuration file go to the default
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater channels, or to standard error if the <code class="option">-g</code> option
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington was specified.
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect3" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h4 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="id2575209"></a>The <span><strong class="command">channel</strong></span> Phrase</h4></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater All log output goes to one or more <span class="emphasis"><em>channels</em></span>;
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington you can make as many of them as you want.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Every channel definition must include a destination clause that
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater says whether messages selected for the channel go to a file, to a
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington particular syslog facility, to the standard error stream, or are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater discarded. It can optionally also limit the message severity level
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater that will be accepted by the channel (the default is
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">info</strong></span>), and whether to include a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">named</strong></span>-generated time stamp, the
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater category name
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and/or severity level (the default is not to include any).
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
06795359e2bc153a46f9f2f793a732b0e508f61dAutomatic Updater<p>
73eb75dc212911e4da58a3ce0a4672d3910193ebBrian Wellington The <span><strong class="command">null</strong></span> destination clause
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater causes all messages sent to the channel to be discarded;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in that case, other options for the channel are meaningless.
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater </p>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater<p>
73eb75dc212911e4da58a3ce0a4672d3910193ebBrian Wellington The <span><strong class="command">file</strong></span> destination clause directs
bbf7c3fd96ae5e02cb84743c581862e35327032aAutomatic Updater the channel
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater to a disk file. It can include limitations
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater both on how large the file is allowed to become, and how many
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater versions
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater of the file will be saved each time the file is opened.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If you use the <span><strong class="command">versions</strong></span> log file
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater option, then
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater <span><strong class="command">named</strong></span> will retain that many backup
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater versions of the file by
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater renaming them when opening. For example, if you choose to keep
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater three old versions
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater of the file <code class="filename">lamers.log</code>, then just
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater before it is opened
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater <code class="filename">lamers.log.1</code> is renamed to
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater <code class="filename">lamers.log.2</code>, <code class="filename">lamers.log.0</code> is renamed
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater to <code class="filename">lamers.log.1</code>, and <code class="filename">lamers.log</code> is
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater renamed to <code class="filename">lamers.log.0</code>.
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater You can say <span><strong class="command">versions unlimited</strong></span> to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater not limit
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the number of versions.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If a <span><strong class="command">size</strong></span> option is associated with
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the log file,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater then renaming is only done when the file being opened exceeds the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater indicated size. No backup versions are kept by default; any
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater existing
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater log file is simply appended.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <span><strong class="command">size</strong></span> option for files is used
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to limit log
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater growth. If the file ever exceeds the size, then <span><strong class="command">named</strong></span> will
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington stop writing to the file unless it has a <span><strong class="command">versions</strong></span> option
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington associated with it. If backup versions are kept, the files are
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington rolled as
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington described above and a new one begun. If there is no
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">versions</strong></span> option, no more data will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater be written to the log
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater until some out-of-band mechanism removes or truncates the log to
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington less than the
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater maximum size. The default behavior is not to limit the size of
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater file.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Example usage of the <span><strong class="command">size</strong></span> and
8227257b1c0224a7991e04bb79dc5059d5062dfbAndreas Gustafsson <span><strong class="command">versions</strong></span> options:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">channel an_example_channel {
8227257b1c0224a7991e04bb79dc5059d5062dfbAndreas Gustafsson file "example.log" versions 3 size 20m;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater print-time yes;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater print-category yes;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater};
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater</pre>
8227257b1c0224a7991e04bb79dc5059d5062dfbAndreas Gustafsson<p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater The <span><strong class="command">syslog</strong></span> destination clause
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater directs the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington channel to the system log. Its argument is a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater syslog facility as described in the <span><strong class="command">syslog</strong></span> man
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington page. Known facilities are <span><strong class="command">kern</strong></span>, <span><strong class="command">user</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">mail</strong></span>, <span><strong class="command">daemon</strong></span>, <span><strong class="command">auth</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">syslog</strong></span>, <span><strong class="command">lpr</strong></span>, <span><strong class="command">news</strong></span>,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">uucp</strong></span>, <span><strong class="command">cron</strong></span>, <span><strong class="command">authpriv</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">ftp</strong></span>, <span><strong class="command">local0</strong></span>, <span><strong class="command">local1</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">local2</strong></span>, <span><strong class="command">local3</strong></span>, <span><strong class="command">local4</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">local5</strong></span>, <span><strong class="command">local6</strong></span> and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">local7</strong></span>, however not all facilities
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater are supported on
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington all operating systems.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater How <span><strong class="command">syslog</strong></span> will handle messages
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater sent to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater this facility is described in the <span><strong class="command">syslog.conf</strong></span> man
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater page. If you have a system which uses a very old version of <span><strong class="command">syslog</strong></span> that
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater only uses two arguments to the <span><strong class="command">openlog()</strong></span> function,
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater then this clause is silently ignored.
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater On Windows machines syslog messages are directed to the EventViewer.
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<p>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater The <span><strong class="command">severity</strong></span> clause works like <span><strong class="command">syslog</strong></span>'s
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater "priorities", except that they can also be used if you are writing
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater straight to a file rather than using <span><strong class="command">syslog</strong></span>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Messages which are not at least of the severity level given will
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater not be selected for the channel; messages of higher severity
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater levels
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington will be accepted.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater If you are using <span><strong class="command">syslog</strong></span>, then the <span><strong class="command">syslog.conf</strong></span> priorities
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater will also determine what eventually passes through. For example,
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater defining a channel facility and severity as <span><strong class="command">daemon</strong></span> and <span><strong class="command">debug</strong></span> but
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater only logging <span><strong class="command">daemon.warning</strong></span> via <span><strong class="command">syslog.conf</strong></span> will
7be29b99f8c13c432db3822102412a32bc1dbaa4Automatic Updater cause messages of severity <span><strong class="command">info</strong></span> and
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater <span><strong class="command">notice</strong></span> to
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater be dropped. If the situation were reversed, with <span><strong class="command">named</strong></span> writing
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater messages of only <span><strong class="command">warning</strong></span> or higher,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington then <span><strong class="command">syslogd</strong></span> would
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater print all messages it received from the channel.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <span><strong class="command">stderr</strong></span> destination clause
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington directs the
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater channel to the server's standard error stream. This is intended
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater use when the server is running as a foreground process, for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater example
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater when debugging a configuration.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The server can supply extensive debugging information when
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater it is in debugging mode. If the server's global debug level is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater greater
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater than zero, then debugging mode will be active. The global debug
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater level is set either by starting the <span><strong class="command">named</strong></span> server
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater with the <code class="option">-d</code> flag followed by a positive integer,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater or by running <span><strong class="command">rndc trace</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The global debug level
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington can be set to zero, and debugging mode turned off, by running <span><strong class="command">rndc
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updaternotrace</strong></span>. All debugging messages in the server have a debug
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater level, and higher debug levels give more detailed output. Channels
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater that specify a specific debug severity, for example:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater<pre class="programlisting">channel specific_debug_level {
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater file "foo";
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater severity debug 3;
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater};
17198e77b87667f796e910d31a4f47a80e256d09Mark Andrews</pre>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater<p>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater will get debugging output of level 3 or less any time the
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater server is in debugging mode, regardless of the global debugging
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater level. Channels with <span><strong class="command">dynamic</strong></span>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater severity use the
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater server's global debug level to determine what messages to print.
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater </p>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater<p>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater If <span><strong class="command">print-time</strong></span> has been turned on,
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater then
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater the date and time will be logged. <span><strong class="command">print-time</strong></span> may
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater be specified for a <span><strong class="command">syslog</strong></span> channel,
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater but is usually
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater pointless since <span><strong class="command">syslog</strong></span> also logs
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater the date and
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater time. If <span><strong class="command">print-category</strong></span> is
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater requested, then the
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater category of the message will be logged as well. Finally, if <span><strong class="command">print-severity</strong></span> is
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater on, then the severity level of the message will be logged. The <span><strong class="command">print-</strong></span> options may
de73ef7ecdb9e009155993a6fa8dee5cd1bde319Mark Andrews be used in any combination, and will always be printed in the
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater following
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater order: time, category, severity. Here is an example where all
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater three <span><strong class="command">print-</strong></span> options
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater are on:
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater </p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater<p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater <code class="computeroutput">28-Feb-2000 15:05:32.863 general: notice: running</code>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater </p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater<p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater If <span><strong class="command">buffered</strong></span> has been turned on the output
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater to files will not be flushed after each log entry. By default
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater all log messages are flushed.
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater </p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater<p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater There are four predefined channels that are used for
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater <span><strong class="command">named</strong></span>'s default logging as follows.
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater If <span><strong class="command">named</strong></span> is started with the
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater <code class="option">-L</code> then a
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater fifth channel <span><strong class="command">default_logfile</strong></span> is added.
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater How they are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater used is described in <a href="Bv9ARM.ch06.html#the_category_phrase" title="The category Phrase">the section called &#8220;The <span><strong class="command">category</strong></span> Phrase&#8221;</a>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting">channel default_syslog {
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington // send to syslog's daemon facility
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington syslog daemon;
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater // only send priority info and higher
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater severity info;
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrewschannel default_debug {
0df8ead472f207020f8da22a185fe4b945248ab8Automatic Updater // write to named.run in the working directory
0df8ead472f207020f8da22a185fe4b945248ab8Automatic Updater // Note: stderr is used instead of "named.run" if
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews // the server is started with the '-g' option.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews file "named.run";
4d95e549ed8f84373e5eb7346a0c7ab7f3b0e9a8Automatic Updater // log at the server's current debug level
4d95e549ed8f84373e5eb7346a0c7ab7f3b0e9a8Automatic Updater severity dynamic;
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews};
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updaterchannel default_stderr {
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater // writes to stderr
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews stderr;
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews // only send priority info and higher
71ba75c604df3604673232828a68bb28c420e698Mark Andrews severity info;
71ba75c604df3604673232828a68bb28c420e698Mark Andrews};
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrewschannel null {
510f19039bcd402dff28c85114551179670f482aAutomatic Updater // toss anything sent to this channel
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater null;
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews};
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updaterchannel default_logfile {
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater // this channel is only present if named is
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater // started with the -L option, whose argument
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater // provides the file name
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater file "...";
56334ccb2d4b5a04fc12b70b5852049db5d24088Evan Hunt // log at the server's current debug level
56334ccb2d4b5a04fc12b70b5852049db5d24088Evan Hunt severity dynamic;
56334ccb2d4b5a04fc12b70b5852049db5d24088Evan Hunt};
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater</pre>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater The <span><strong class="command">default_debug</strong></span> channel has the
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater special
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater property that it only produces output when the server's debug
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater level is
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater nonzero. It normally writes to a file called <code class="filename">named.run</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in the server's working directory.
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater </p>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson For security reasons, when the <code class="option">-u</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater command line option is used, the <code class="filename">named.run</code> file
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater is created only after <span><strong class="command">named</strong></span> has
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater changed to the
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater new UID, and any debug output generated while <span><strong class="command">named</strong></span> is
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater starting up and still running as root is discarded. If you need
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to capture this output, you must run the server with the <code class="option">-L</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater option to specify a default logfile, or the <code class="option">-g</code>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson option to log to standard error which you can redirect to a file.
3341c8b653577f2f0cb8b72702ea6197035334ffMark Andrews </p>
7932a7637170550bc53b38c35db9a0187dcb3d3bAutomatic Updater<p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson Once a channel is defined, it cannot be redefined. Thus you
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson cannot alter the built-in channels directly, but you can modify
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson the default logging by pointing categories at channels you have
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater defined.
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater</div>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater<div class="sect3" lang="en">
c3fd32ed29e9e419bb56583f4272a506773b1ea0Automatic Updater<div class="titlepage"><div><div><h4 class="title">
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews<a name="the_category_phrase"></a>The <span><strong class="command">category</strong></span> Phrase</h4></div></div></div>
a3fdc395a6f4811b536066801d5468399224be25Automatic Updater<p>
b13d89bd89878137c81b36a36596cca3920f27a4Automatic Updater There are many categories, so you can send the logs you want
b13d89bd89878137c81b36a36596cca3920f27a4Automatic Updater to see wherever you want, without seeing logs you don't want. If
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater you don't specify a list of channels for a category, then log
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater messages
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in that category will be sent to the <span><strong class="command">default</strong></span> category
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater instead. If you don't specify a default category, the following
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater "default default" is used:
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater </p>
0ece47f7c1cf03718726d9dff183b02fa35115e6Mark Andrews<pre class="programlisting">category default { default_syslog; default_debug; };
8fca573ba41a1669fff64f234275e956551eb6e5Mark Andrews</pre>
8fca573ba41a1669fff64f234275e956551eb6e5Mark Andrews<p>
0ca8fddd5b5e26d8a05f0936fc4b2666a025b9c0Mark Andrews If you start <span><strong class="command">named</strong></span> with the
0ca8fddd5b5e26d8a05f0936fc4b2666a025b9c0Mark Andrews <code class="option">-L</code> option then the default category is:
8fca573ba41a1669fff64f234275e956551eb6e5Mark Andrews </p>
8fca573ba41a1669fff64f234275e956551eb6e5Mark Andrews<pre class="programlisting">category default { default_logfile; default_debug; };
8fca573ba41a1669fff64f234275e956551eb6e5Mark Andrews</pre>
0ca8fddd5b5e26d8a05f0936fc4b2666a025b9c0Mark Andrews<p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater As an example, let's say you want to log security events to
8fca573ba41a1669fff64f234275e956551eb6e5Mark Andrews a file, but you also want keep the default logging behavior. You'd
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater specify the following:
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater </p>
8fca573ba41a1669fff64f234275e956551eb6e5Mark Andrews<pre class="programlisting">channel my_security_channel {
8fca573ba41a1669fff64f234275e956551eb6e5Mark Andrews file "my_security_file";
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews severity info;
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater};
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrewscategory security {
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater my_security_channel;
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews default_syslog;
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater default_debug;
fbfdea68e4a66d25286de4172ac63df869bd569aAutomatic Updater};</pre>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater To discard all messages in a category, specify the <span><strong class="command">null</strong></span> channel:
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater </p>
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater<pre class="programlisting">category xfer-out { null; };
ede7b1df75ac53a9530bbbc9fc9db534cab82f44Automatic Updatercategory notify { null; };
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater</pre>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater<p>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater Following are the available categories and brief descriptions
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews of the types of log information they contain. More
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews categories may be added in future <acronym class="acronym">BIND</acronym> releases.
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </p>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<div class="informaltable"><table border="1">
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<colgroup>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<col>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<col>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews</colgroup>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<tbody>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<tr>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<td>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater <p><span><strong class="command">default</strong></span></p>
c453a50776145e9c1c3fc9c846cfa11f42505081Automatic Updater </td>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater<td>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater <p>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater The default category defines the logging
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater options for those categories where no specific
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater configuration has been
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater defined.
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </td>
2ec4ab21838e218863d052ebfa3e106e04f50820Evan Hunt</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">general</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The catch-all. Many things still aren't
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews classified into categories, and they all end up here.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">database</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Messages relating to the databases used
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews internally by the name server to store zone and cache
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews data.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">security</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Approval and denial of requests.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">config</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Configuration file parsing and processing.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">resolver</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews DNS resolution, such as the recursive
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews lookups performed on behalf of clients by a caching name
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews server.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">xfer-in</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Zone transfers the server is receiving.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">xfer-out</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Zone transfers the server is sending.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">notify</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The NOTIFY protocol.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">client</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Processing of client requests.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">unmatched</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Messages that <span><strong class="command">named</strong></span> was unable to determine the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews class of or for which there was no matching <span><strong class="command">view</strong></span>.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews A one line summary is also logged to the <span><strong class="command">client</strong></span> category.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews This category is best sent to a file or stderr, by
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews default it is sent to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the <span><strong class="command">null</strong></span> channel.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">network</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Network operations.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">update</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Dynamic updates.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">update-security</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Approval and denial of update requests.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">queries</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Specify where queries should be logged to.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews At startup, specifying the category <span><strong class="command">queries</strong></span> will also
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews enable query logging unless <span><strong class="command">querylog</strong></span> option has been
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews specified.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The query log entry reports the client's IP
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews address and port number, and the query name,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews class and type. Next it reports whether the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Recursion Desired flag was set (+ if set, -
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews if not set), if the query was signed (S),
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews EDNS was in use (E), if TCP was used (T), if
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews DO (DNSSEC Ok) was set (D), or if CD (Checking
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Disabled) was set (C). After this the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews destination address the query was sent to is
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews reported.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="computeroutput">client 127.0.0.1#62536 (www.example.com): query: www.example.com IN AAAA +SE</code>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="computeroutput">client ::1#62537 (www.example.net): query: www.example.net IN AAAA -SE</code>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews (The first part of this log message, showing the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews client address/port number and query name, is
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews repeated in all subsequent log messages related
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews to the same query.)
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><span><strong class="command">query-errors</strong></span></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Information about queries that resulted in some
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews failure.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews<td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews <p><span><strong class="command">dispatch</strong></span></p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </td>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews <p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews Dispatching of incoming packets to the
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews server modules where they are to be processed.
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews</tr>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews<tr>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews<td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews <p><span><strong class="command">dnssec</strong></span></p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews<td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews <p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews DNSSEC and TSIG protocol processing.
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews</tr>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews<tr>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews<td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews <p><span><strong class="command">lame-servers</strong></span></p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </td>
78cb74fab4665da2e2641ba909c6f59f74cc4193Automatic Updater<td>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater <p>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater Lame servers. These are misconfigurations
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater in remote servers, discovered by BIND 9 when trying to
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater query those servers during resolution.
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater </p>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater </td>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater</tr>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater<tr>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater<td>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater <p><span><strong class="command">delegation-only</strong></span></p>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater </td>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater<td>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater <p>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater Delegation only. Logs queries that have been
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater forced to NXDOMAIN as the result of a
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater delegation-only zone or a
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater <span><strong class="command">delegation-only</strong></span> in a
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews forward, hint or stub zone declaration.
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson </p>
309b912841e8b97bf0b0df0d96c3eaf16990c080Automatic Updater </td>
56874aef380a64a2c183b7c282c3e7a361d67fa1Automatic Updater</tr>
56874aef380a64a2c183b7c282c3e7a361d67fa1Automatic Updater<tr>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson<td>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson <p><span><strong class="command">edns-disabled</strong></span></p>
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews </td>
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews<td>
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews <p>
309b912841e8b97bf0b0df0d96c3eaf16990c080Automatic Updater Log queries that have been forced to use plain
94df856897945fe58f130ba78765c57308bc5400Automatic Updater DNS due to timeouts. This is often due to
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews the remote servers not being RFC 1034 compliant
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews (not always returning FORMERR or similar to
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews EDNS queries and other extensions to the DNS
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater when they are not understood). In other words, this is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater targeted at servers that fail to respond to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater DNS queries that they don't understand.
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews </p>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews <p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews Note: the log message can also be due to
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews packet loss. Before reporting servers for
da93950363b307b718d156514b95b9df93a63776Mark Andrews non-RFC 1034 compliance they should be re-tested
da93950363b307b718d156514b95b9df93a63776Mark Andrews to determine the nature of the non-compliance.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater This testing should prevent or reduce the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater number of false-positive reports.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater Note: eventually <span><strong class="command">named</strong></span> will have to stop
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater treating such timeouts as due to RFC 1034 non
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater compliance and start treating it as plain
e23256e740b238bddb4ba41ffac5f81a01c92245Automatic Updater packet loss. Falsely classifying packet
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater loss as due to RFC 1034 non compliance impacts
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater on DNSSEC validation which requires EDNS for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the DNSSEC records to be returned.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</tr>
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater<tr>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <p><span><strong class="command">RPZ</strong></span></p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater Information about errors in response policy zone files,
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater rewritten responses, and at the highest
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <span><strong class="command">debug</strong></span> levels, mere rewriting
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater attempts.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</tr>
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater<tr>
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater<td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <p><span><strong class="command">rate-limit</strong></span></p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater The start, periodic, and final notices of the
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater rate limiting of a stream of responses are logged at
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <span><strong class="command">info</strong></span> severity in this category.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater These messages include a hash value of the domain name
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater of the response and the name itself,
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater except when there is insufficient memory to record
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater the name for the final notice
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater The final notice is normally delayed until about one
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater minute after rate limit stops.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater A lack of memory can hurry the final notice,
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater in which case it starts with an asterisk (*).
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater Various internal events are logged at debug 1 level
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater and higher.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater Rate limiting of individual requests
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater is logged in the <span><strong class="command">query-errors</strong></span> category.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</tr>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<tr>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <p><span><strong class="command">cname</strong></span></p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater Logs nameservers that are skipped due to them being
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater a CNAME rather than A / AAAA records.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </td>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</tr>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</tbody>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</table></div>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</div>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<div class="sect3" lang="en">
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<div class="titlepage"><div><div><h4 class="title">
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<a name="id2576830"></a>The <span><strong class="command">query-errors</strong></span> Category</h4></div></div></div>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater The <span><strong class="command">query-errors</strong></span> category is
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater specifically intended for debugging purposes: To identify
0b580e05aec89f501a9c20cc00ceb42d043d3928Automatic Updater why and how specific queries result in responses which
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater indicate an error.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater Messages of this category are therefore only logged
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater with <span><strong class="command">debug</strong></span> levels.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater At the debug levels of 1 or higher, each response with the
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater rcode of SERVFAIL is logged as follows:
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <code class="computeroutput">client 127.0.0.1#61502: query failed (SERVFAIL) for www.example.com/IN/AAAA at query.c:3880</code>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater This means an error resulting in SERVFAIL was
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater detected at line 3880 of source file
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater <code class="filename">query.c</code>.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater Log messages of this level will particularly
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater help identify the cause of SERVFAIL for an
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater authoritative server.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater At the debug levels of 2 or higher, detailed context
0b580e05aec89f501a9c20cc00ceb42d043d3928Automatic Updater information of recursive resolutions that resulted in
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater SERVFAIL is logged.
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater The log message will look like as follows:
0b580e05aec89f501a9c20cc00ceb42d043d3928Automatic Updater </p>
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<pre class="programlisting">
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updaterfetch completed at resolver.c:2970 for www.example.com/A
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updaterin 30.000183: timed out/success [domain:example.com,
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updaterreferral:2,restart:7,qrysent:8,timeout:5,lame:0,neterr:0,
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updaterbadresp:1,adberr:0,findfail:0,valfail:0]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </pre>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater The first part before the colon shows that a recursive
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater resolution for AAAA records of www.example.com completed
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater in 30.000183 seconds and the final result that led to the
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater SERVFAIL was determined at line 2970 of source file
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater <code class="filename">resolver.c</code>.
0ece47f7c1cf03718726d9dff183b02fa35115e6Mark Andrews </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The following part shows the detected final result and the
ea206aebcafe1ed5d470dd99daab9a1cedc81c7cMark Andrews latest result of DNSSEC validation.
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater The latter is always success when no validation attempt
db854396212d4195bbbf9de89951d9c2a5770e91Automatic Updater is made.
db854396212d4195bbbf9de89951d9c2a5770e91Automatic Updater In this example, this query resulted in SERVFAIL probably
db854396212d4195bbbf9de89951d9c2a5770e91Automatic Updater because all name servers are down or unreachable, leading
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater to a timeout in 30 seconds.
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater DNSSEC validation was probably not attempted.
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater The last part enclosed in square brackets shows statistics
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater information collected for this particular resolution
db854396212d4195bbbf9de89951d9c2a5770e91Automatic Updater attempt.
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater The <code class="varname">domain</code> field shows the deepest zone
c3fd32ed29e9e419bb56583f4272a506773b1ea0Automatic Updater that the resolver reached;
0429fc942ef48b8ab07a01648b22f98174a2ae6fAutomatic Updater it is the zone where the error was finally detected.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The meaning of the other fields is summarized in the
418cc932318b1d67f88a36904d88d8a5a0a2ba09Automatic Updater following table.
644973f327e9db74779e7c0426db90909173b284Automatic Updater </p>
644973f327e9db74779e7c0426db90909173b284Automatic Updater<div class="informaltable"><table border="1">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<colgroup>
418cc932318b1d67f88a36904d88d8a5a0a2ba09Automatic Updater<col>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<col>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater</colgroup>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<tbody>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<tr>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater <p><code class="varname">referral</code></p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater <p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater The number of referrals the resolver received
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater throughout the resolution process.
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater In the above example this is 2, which are most
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater likely com and example.com.
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater</tr>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<tr>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater <p><code class="varname">restart</code></p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </td>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<td>
418cc932318b1d67f88a36904d88d8a5a0a2ba09Automatic Updater <p>
418cc932318b1d67f88a36904d88d8a5a0a2ba09Automatic Updater The number of cycles that the resolver tried
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews remote servers at the <code class="varname">domain</code>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews zone.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews In each cycle the resolver sends one query
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews (possibly resending it, depending on the response)
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews to each known name server of
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews the <code class="varname">domain</code> zone.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </td>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews</tr>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<tr>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<td>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <p><code class="varname">qrysent</code></p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </td>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<td>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The number of queries the resolver sent at the
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <code class="varname">domain</code> zone.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<tr>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><code class="varname">timeout</code></p>
68e1b398b5b1b417723e90b5e52b9148f8f93294Automatic Updater </td>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<td>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The number of timeouts since the resolver
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews received the last response.
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews <p><code class="varname">lame</code></p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </td>
cff0e0b52cf0928123bad6f3bccf56e22bbc07f5Automatic Updater<td>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The number of lame servers the resolver detected
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews at the <code class="varname">domain</code> zone.
872a5b83f68b8058945298715b0fa53442aad52fAutomatic Updater A server is detected to be lame either by an
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews invalid response or as a result of lookup in
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater BIND9's address database (ADB), where lame
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews servers are cached.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </td>
90eba8a49d580f9e718983fa39d8e5ee483558c9Automatic Updater</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<td>
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater <p><code class="varname">neterr</code></p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews </td>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater<td>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The number of erroneous results that the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington resolver encountered in sending queries
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington at the <code class="varname">domain</code> zone.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington One common case is the remote server is
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington unreachable and the resolver receives an ICMP
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington unreachable error message.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
ed178efa9ab8f813538fce4ff603b81ded9f1799Mark Andrews<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
cff0e0b52cf0928123bad6f3bccf56e22bbc07f5Automatic Updater <p><code class="varname">badresp</code></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
644973f327e9db74779e7c0426db90909173b284Automatic Updater The number of unexpected responses (other than
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="varname">lame</code>) to queries sent by the
c28a1243429dfaf8dc5f6c1db0dccdc6ce386baeMark Andrews resolver at the <code class="varname">domain</code> zone.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
6c68e68fc550c947100581eb7b5340b81c062c94Andreas Gustafsson </td>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews</tr>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<tr>
5f7e0eb1cb917b788906d3e2aa01bfc4885dcae4Mark Andrews<td>
bf1263835e8e35421960f65088c043f42aacef13Mark Andrews <p><code class="varname">adberr</code></p>
15ae68f3db8261770fc33b8e0f83f5d8c7021e84Mark Andrews </td>
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews<td>
0190c262f99d8afa4cece60e3775d76840826f68Automatic Updater <p>
2bb3422dc683c013db7042f5736240de6b86f182Automatic Updater Failures in finding remote server addresses
0190c262f99d8afa4cece60e3775d76840826f68Automatic Updater of the <code class="varname">domain</code> zone in the ADB.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater One common case of this is that the remote
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews server's name does not have any address records.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews</tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<tr>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater<td>
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater <p><code class="varname">findfail</code></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews Failures of resolving remote server addresses.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This is a total number of failures throughout
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the resolution process.
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<tr>
10640b2e3efc7bc8034108136d7487f7407fbf37Andreas Gustafsson<td>
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater <p><code class="varname">valfail</code></p>
10640b2e3efc7bc8034108136d7487f7407fbf37Andreas Gustafsson </td>
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews Failures of DNSSEC validation.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Validation failures are counted throughout
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater the resolution process (not limited to
bf46736ab182c4663beb5a08cb2ebf7c364e0aa9Automatic Updater the <code class="varname">domain</code> zone), but should
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater only happen in <code class="varname">domain</code>.
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater </p>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater </td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater</tr>
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater</tbody>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</table></div>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater At the debug levels of 3 or higher, the same messages
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater as those at the debug 1 level are logged for other errors
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater than SERVFAIL.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Note that negative responses such as NXDOMAIN are not
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater regarded as errors here.
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater </p>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<p>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater At the debug levels of 4 or higher, the same messages
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater as those at the debug 2 level are logged for other errors
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater than SERVFAIL.
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater Unlike the above case of level 3, messages are logged for
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater negative responses.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This is because any unexpected results can be difficult to
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater debug in the recursion case.
b05b66d498e68d0ff0b391b1fd1a41f542eed721Automatic Updater </p>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater</div>
bb93c8542756719b53096b9939e4041d0966026fAutomatic Updater</div>
3de6db3208d51de1e138b63b9670430c03f99694Automatic Updater<div class="sect2" lang="en">
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<a name="id2577350"></a><span><strong class="command">lwres</strong></span> Statement Grammar</h3></div></div></div>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater This is the grammar of the <span><strong class="command">lwres</strong></span>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater statement in the <code class="filename">named.conf</code> file:
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater </p>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater<pre class="programlisting"><span><strong class="command">lwres</strong></span> {
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews [<span class="optional"> listen-on { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews [<span class="optional"> view <em class="replaceable"><code>view_name</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> search { <em class="replaceable"><code>domain_name</code></em> ; [<span class="optional"> <em class="replaceable"><code>domain_name</code></em> ; ... </span>] }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> ndots <em class="replaceable"><code>number</code></em>; </span>]
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater [<span class="optional"> lwres-tasks <em class="replaceable"><code>number</code></em>; </span>]
ca904804e43f663f08eb1ac9d6d617930b9a3cd3Automatic Updater [<span class="optional"> lwres-clients <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater};
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<a name="id2577447"></a><span><strong class="command">lwres</strong></span> Statement Definition and Usage</h3></div></div></div>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<p>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater The <span><strong class="command">lwres</strong></span> statement configures the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater name
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater server to also act as a lightweight resolver server. (See
478d64f58f5ce7a5e3ea08426d72faca8427c96dAutomatic Updater <a href="Bv9ARM.ch05.html#lwresd" title="Running a Resolver Daemon">the section called &#8220;Running a Resolver Daemon&#8221;</a>.) There may be multiple
0ce87e5749aabb8eef1e0a37e4bd6e6ffa1d7196Automatic Updater <span><strong class="command">lwres</strong></span> statements configuring
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater lightweight resolver servers with different properties.
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater </p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<p>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater The <span><strong class="command">listen-on</strong></span> statement specifies a
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater list of
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater IPv4 addresses (and ports) that this instance of a lightweight
6ffd34dcf046bdc3f83484bfdc6d951c746147cfAutomatic Updater resolver daemon
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater should accept requests on. If no port is specified, port 921 is
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater used.
3a32066d653b39a3f602b697a0fb98a399b88f88Automatic Updater If this statement is omitted, requests will be accepted on
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater 127.0.0.1,
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater port 921.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
8c6328ab5890aa79d84b86ed672e185dc111bb68Automatic Updater<p>
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater The <span><strong class="command">view</strong></span> statement binds this
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater instance of a
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater lightweight resolver daemon to a view in the DNS namespace, so that
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater the
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater response will be constructed in the same manner as a normal DNS
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater query
129090f0f6f91753b4a085ab635e28549fd018adAutomatic Updater matching this view. If this statement is omitted, the default view
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater is
c453a50776145e9c1c3fc9c846cfa11f42505081Automatic Updater used, and if there is no default view, an error is triggered.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
d7a77415c13bb2fc2d1acb857486d97e4466e3b8Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <span><strong class="command">search</strong></span> statement is equivalent to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater <span><strong class="command">search</strong></span> statement in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">/etc/resolv.conf</code>. It provides a
3f802a977eb8ac127c1d6d0d76b8e38d032403daAutomatic Updater list of domains
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater which are appended to relative names in queries.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <span><strong class="command">ndots</strong></span> statement is equivalent to
ca904804e43f663f08eb1ac9d6d617930b9a3cd3Automatic Updater the
233f603cc1e6dd17b8912796f3fff5cfbbb76c90Automatic Updater <span><strong class="command">ndots</strong></span> statement in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">/etc/resolv.conf</code>. It indicates the
713a5e3080f112b3efde9235e9c92035056ff966Automatic Updater minimum
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater number of dots in a relative domain name that should result in an
129090f0f6f91753b4a085ab635e28549fd018adAutomatic Updater exact match lookup before search path elements are appended.
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater </p>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <code class="option">lwres-tasks</code> statement specifies the number
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater of worker threads the lightweight resolver will dedicate to serving
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater clients. By default the number is the same as the number of CPUs on
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater the system; this can be overridden using the <code class="option">-n</code>
c3fd32ed29e9e419bb56583f4272a506773b1ea0Automatic Updater command line option when starting the server.
c243d779731a410f8dc2d2feeed20c15f299b6e3Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater The <code class="option">lwres-clients</code> specifies
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater the number of client objects per thread the lightweight
0ce87e5749aabb8eef1e0a37e4bd6e6ffa1d7196Automatic Updater resolver should create to serve client queries.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater By default, if the lightweight resolver runs as a part
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater of <span><strong class="command">named</strong></span>, 256 client objects are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater created for each task; if it runs as <span><strong class="command">lwresd</strong></span>,
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater 1024 client objects are created for each thread. The maximum
da24e725ff982595d74da7e75e9fbd6a696367ccAutomatic Updater value is 32768; higher values will be silently ignored and
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater the maximum will be used instead.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Note that setting too high a value may overconsume
c453a50776145e9c1c3fc9c846cfa11f42505081Automatic Updater system resources.
233f603cc1e6dd17b8912796f3fff5cfbbb76c90Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater The maximum number of client queries that the lightweight
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater resolver can handle at any one time equals
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <code class="option">lwres-tasks</code> times <code class="option">lwres-clients</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater<a name="id2577611"></a><span><strong class="command">masters</strong></span> Statement Grammar</h3></div></div></div>
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater<pre class="programlisting">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<span><strong class="command">masters</strong></span> <em class="replaceable"><code>name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> |
bb93c8542756719b53096b9939e4041d0966026fAutomatic Updater <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] };
2bb3422dc683c013db7042f5736240de6b86f182Automatic Updater</pre>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater</div>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater<div class="sect2" lang="en">
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
f4029eb7463e99df00618de89f0bee5ac062a237Automatic Updater<a name="id2577660"></a><span><strong class="command">masters</strong></span> Statement Definition and
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater Usage</h3></div></div></div>
59edd79b878b51ce5572cb2c6efe38b82242f108Automatic Updater<p><span><strong class="command">masters</strong></span>
3e79333aa37d3b88959372431a02af8a3eb7cfd9Automatic Updater lists allow for a common set of masters to be easily used by
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater multiple stub and slave zones in their <span><strong class="command">masters</strong></span>
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater or <span><strong class="command">also-notify</strong></span> lists.
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater </p>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater</div>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater<div class="sect2" lang="en">
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<div class="titlepage"><div><div><h3 class="title">
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<a name="id2577682"></a><span><strong class="command">options</strong></span> Statement Grammar</h3></div></div></div>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<p>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater This is the grammar of the <span><strong class="command">options</strong></span>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater statement in the <code class="filename">named.conf</code> file:
16a8f020ff1fe2fa6e40c2ed72fcf87d08f59ff7Automatic Updater </p>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater<pre class="programlisting"><span><strong class="command">options</strong></span> {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> attach-cache <em class="replaceable"><code>cache_name</code></em>; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> version <em class="replaceable"><code>version_string</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> hostname <em class="replaceable"><code>hostname_string</code></em>; </span>]
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater [<span class="optional"> server-id <em class="replaceable"><code>server_id_string</code></em>; </span>]
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater [<span class="optional"> directory <em class="replaceable"><code>path_name</code></em>; </span>]
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> geoip-directory <em class="replaceable"><code>path_name</code></em>; </span>]
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater [<span class="optional"> key-directory <em class="replaceable"><code>path_name</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> managed-keys-directory <em class="replaceable"><code>path_name</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> named-xfer <em class="replaceable"><code>path_name</code></em>; </span>]
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater [<span class="optional"> tkey-gssapi-keytab <em class="replaceable"><code>path_name</code></em>; </span>]
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> tkey-gssapi-credential <em class="replaceable"><code>principal</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> tkey-domain <em class="replaceable"><code>domainname</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> tkey-dhkey <em class="replaceable"><code>key_name</code></em> <em class="replaceable"><code>key_tag</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> cache-file <em class="replaceable"><code>path_name</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dump-file <em class="replaceable"><code>path_name</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> bindkeys-file <em class="replaceable"><code>path_name</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> secroots-file <em class="replaceable"><code>path_name</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> session-keyfile <em class="replaceable"><code>path_name</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> session-keyname <em class="replaceable"><code>key_name</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> session-keyalg <em class="replaceable"><code>algorithm_id</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> memstatistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> memstatistics-file <em class="replaceable"><code>path_name</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> pid-file <em class="replaceable"><code>path_name</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> recursing-file <em class="replaceable"><code>path_name</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> statistics-file <em class="replaceable"><code>path_name</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> zone-statistics <em class="replaceable"><code>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> auth-nxdomain <em class="replaceable"><code>yes_or_no</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> deallocate-on-exit <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> fake-iquery <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> fetch-glue <em class="replaceable"><code>yes_or_no</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> flush-zones-on-shutdown <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> has-old-clients <em class="replaceable"><code>yes_or_no</code></em>; </span>]
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> host-statistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
59b277af9d9aac08d16be63aed5ae60ac9eef0d5Automatic Updater [<span class="optional"> host-statistics-max <em class="replaceable"><code>number</code></em>; </span>]
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> minimal-responses <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> multiple-cnames <em class="replaceable"><code>yes_or_no</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <em class="replaceable"><code>master-only</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> recursion <em class="replaceable"><code>yes_or_no</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> request-sit <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> sit-secret <em class="replaceable"><code>secret_string</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> request-nsid <em class="replaceable"><code>yes_or_no</code></em>; </span>]
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater [<span class="optional"> rfc2308-type1 <em class="replaceable"><code>yes_or_no</code></em>; </span>]
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater [<span class="optional"> use-id-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> ixfr-from-differences (<em class="replaceable"><code>yes_or_no</code></em> | <code class="constant">master</code> | <code class="constant">slave</code>); </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dnssec-enable <em class="replaceable"><code>yes_or_no</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> dnssec-validation (<em class="replaceable"><code>yes_or_no</code></em> | <code class="constant">auto</code>); </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dnssec-lookaside ( <em class="replaceable"><code>auto</code></em> |
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <em class="replaceable"><code>no</code></em> |
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <em class="replaceable"><code>domain</code></em> trust-anchor <em class="replaceable"><code>domain</code></em> ); </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> dnssec-must-be-secure <em class="replaceable"><code>domain yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dnssec-accept-expired <em class="replaceable"><code>yes_or_no</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> forward ( <em class="replaceable"><code>only</code></em> | <em class="replaceable"><code>first</code></em> ); </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> dual-stack-servers [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater ( <em class="replaceable"><code>domain_name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] |
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]) ;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater ... }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> check-names ( <em class="replaceable"><code>master</code></em> | <em class="replaceable"><code>slave</code></em> | <em class="replaceable"><code>response</code></em> )
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> check-dup-records ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater [<span class="optional"> check-mx ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater [<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater [<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em>; </span>]
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> check-mx-cname ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
1b670d35282f1b9352692ad212be3c0aa97b0689Automatic Updater [<span class="optional"> check-srv-cname ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> check-sibling <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> check-spf ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> allow-new-zones { <em class="replaceable"><code>yes_or_no</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> allow-query-cache { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> allow-query-cache-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> allow-recursion { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> allow-recursion-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> automatic-interface-scan { <em class="replaceable"><code>yes_or_no</code></em> }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> geoip-use-ecs <em class="replaceable"><code>yes_or_no</code></em>;</span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> dnssec-update-mode ( <em class="replaceable"><code>maintain</code></em> | <em class="replaceable"><code>no-resign</code></em> ); </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dnssec-dnskey-kskonly <em class="replaceable"><code>yes_or_no</code></em>; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> dnssec-loadkeys-interval <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dnssec-secure-to-insecure <em class="replaceable"><code>yes_or_no</code></em> ;</span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> try-tcp-refresh <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> allow-v6-synthesis { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> blackhole { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> keep-response-order { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> no-case-compress { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> use-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> avoid-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> use-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> avoid-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> listen-on [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em> </span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
2188d48d2dc0ed15bce6260f2125981a69898141Francis Dupont [<span class="optional"> listen-on-v6 [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
2188d48d2dc0ed15bce6260f2125981a69898141Francis Dupont{ <em class="replaceable"><code>address_match_list</code></em> }; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> query-source ( ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> )
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] |
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> address ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] )
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> query-source-v6 ( ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> )
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] |
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> address ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] )
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater [<span class="optional"> use-queryport-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> queryport-pool-ports <em class="replaceable"><code>number</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> queryport-pool-updateinterval <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em>; </span>]
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater [<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> tcp-clients <em class="replaceable"><code>number</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> reserved-sockets <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> recursive-clients <em class="replaceable"><code>number</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> notify-rate <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> startup-notify-rate <em class="replaceable"><code>number</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> serial-query-rate <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> serial-queries <em class="replaceable"><code>number</code></em>; </span>]
96713299d08c0735c18ebe8772dd2cc1ecd4356aAutomatic Updater [<span class="optional"> tcp-listen-queue <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> transfer-format <em class="replaceable"><code>( one-answer | many-answers )</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> transfers-in <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> transfers-out <em class="replaceable"><code>number</code></em>; </span>]
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater [<span class="optional"> transfers-per-ns <em class="replaceable"><code>number</code></em>; </span>]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater [<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater [<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater [<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater [<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
3c761103e8d2f80fb50c95af18cb0d5dd81ce005Automatic Updater [<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>]
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater [<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
2178b22c8f4a20a0dfc17c93f67789d58530b6e6Automatic Updater [<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> notify-to-soa <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater [<span class="optional"> also-notify { <em class="replaceable"><code>ip_addr</code></em>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] [<span class="optional">key <em class="replaceable"><code>keyname</code></em></span>] ;
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] [<span class="optional">key <em class="replaceable"><code>keyname</code></em></span>] ; ... </span>] }; </span>]
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater [<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em>; </span>]
0d3490f93bb980fde704055e74c1b508987a5fe4Mark Andrews [<span class="optional"> max-journal-size <em class="replaceable"><code>size_spec</code></em>; </span>]
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater [<span class="optional"> coresize <em class="replaceable"><code>size_spec</code></em> ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> datasize <em class="replaceable"><code>size_spec</code></em> ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> files <em class="replaceable"><code>size_spec</code></em> ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> stacksize <em class="replaceable"><code>size_spec</code></em> ; </span>]
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater [<span class="optional"> cleaning-interval <em class="replaceable"><code>number</code></em>; </span>]
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater [<span class="optional"> heartbeat-interval <em class="replaceable"><code>number</code></em>; </span>]
0ce87e5749aabb8eef1e0a37e4bd6e6ffa1d7196Automatic Updater [<span class="optional"> interface-interval <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> statistics-interval <em class="replaceable"><code>number</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> topology { <em class="replaceable"><code>address_match_list</code></em> }</span>];
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> sortlist { <em class="replaceable"><code>address_match_list</code></em> }</span>];
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> rrset-order { <em class="replaceable"><code>order_spec</code></em> ; [<span class="optional"> <em class="replaceable"><code>order_spec</code></em> ; ... </span>] </span>] };
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> lame-ttl <em class="replaceable"><code>number</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> max-ncache-ttl <em class="replaceable"><code>number</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> max-cache-ttl <em class="replaceable"><code>number</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> max-zone-ttl <em class="replaceable"><code>number</code></em> ; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> servfail-ttl <em class="replaceable"><code>number</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> sig-validity-interval <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>number</code></em></span>] ; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> sig-signing-nodes <em class="replaceable"><code>number</code></em> ; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> sig-signing-signatures <em class="replaceable"><code>number</code></em> ; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> sig-signing-type <em class="replaceable"><code>number</code></em> ; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> min-roots <em class="replaceable"><code>number</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> use-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> provide-ixfr <em class="replaceable"><code>yes_or_no</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em>; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> request-expire <em class="replaceable"><code>yes_or_no</code></em>; </span>]
361ef0a3e2983a5a3497a3aa7d19d31e21c9e93cAutomatic Updater [<span class="optional"> treat-cr-as-space <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
361ef0a3e2983a5a3497a3aa7d19d31e21c9e93cAutomatic Updater [<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater [<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
da24e725ff982595d74da7e75e9fbd6a696367ccAutomatic Updater [<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater [<span class="optional"> nta-lifetime <em class="replaceable"><code>duration</code></em> ; </span>]
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater [<span class="optional"> nta-recheck <em class="replaceable"><code>duration</code></em> ; </span>]
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ;
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater [<span class="optional"> additional-from-auth <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater [<span class="optional"> additional-from-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> random-device <em class="replaceable"><code>path_name</code></em> ; </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> max-cache-size <em class="replaceable"><code>size_spec</code></em> ; </span>]
992616aaf75643a0c9f84826f0a1ed5a27e84328Mark Andrews [<span class="optional"> match-mapped-addresses <em class="replaceable"><code>yes_or_no</code></em>; </span>]
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater [<span class="optional"> filter-aaaa-on-v4 ( <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>break-dnssec</code></em> ); </span>]
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater [<span class="optional"> filter-aaaa-on-v6 ( <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>break-dnssec</code></em> ); </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> filter-aaaa { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
765c97d56ccddc9d7904c7d9ff2e2d825d9687e4Automatic Updater [<span class="optional"> dns64 <em class="replaceable"><code>ipv6-prefix</code></em> {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> clients { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
e6a6028987f9b57473bb321be55304c7dbf19d8bAutomatic Updater [<span class="optional"> mapped { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater [<span class="optional"> exclude { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> suffix IPv6-address; </span>]
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater [<span class="optional"> recursive-only <em class="replaceable"><code>yes_or_no</code></em>; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> break-dnssec <em class="replaceable"><code>yes_or_no</code></em>; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater }; </span>];
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> dns64-server <em class="replaceable"><code>name</code></em> </span>]
8a507eb20351ee478e8c05620c6899f0a04c1853Automatic Updater [<span class="optional"> dns64-contact <em class="replaceable"><code>name</code></em> </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> preferred-glue ( <em class="replaceable"><code>A</code></em> | <em class="replaceable"><code>AAAA</code></em> | <em class="replaceable"><code>NONE</code></em> ); </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em>; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em>; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> max-rsa-exponent-size <em class="replaceable"><code>number</code></em>; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> root-delegation-only [<span class="optional"> exclude { <em class="replaceable"><code>namelist</code></em> } </span>] ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> querylog <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> disable-algorithms <em class="replaceable"><code>domain</code></em> { <em class="replaceable"><code>algorithm</code></em>;
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> <em class="replaceable"><code>algorithm</code></em>; </span>] }; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> disable-ds-digests <em class="replaceable"><code>domain</code></em> { <em class="replaceable"><code>digest_type</code></em>;
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> <em class="replaceable"><code>digest_type</code></em>; </span>] }; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> acache-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> acache-cleaning-interval <em class="replaceable"><code>number</code></em>; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> max-acache-size <em class="replaceable"><code>size_spec</code></em> ; </span>]
8a507eb20351ee478e8c05620c6899f0a04c1853Automatic Updater [<span class="optional"> clients-per-query <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> max-clients-per-query <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> max-recursion-depth <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> max-recursion-queries <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> masterfile-format
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> masterfile-style
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater (<code class="constant">relative</code>|<code class="constant">full</code>) ; </span>]
06f5acb11f1c32228d93eefd1eb841dbfb1c7f4dAutomatic Updater [<span class="optional"> empty-server <em class="replaceable"><code>name</code></em> ; </span>]
8a507eb20351ee478e8c05620c6899f0a04c1853Automatic Updater [<span class="optional"> empty-contact <em class="replaceable"><code>name</code></em> ; </span>]
06f5acb11f1c32228d93eefd1eb841dbfb1c7f4dAutomatic Updater [<span class="optional"> empty-zones-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> disable-empty-zone <em class="replaceable"><code>zone_name</code></em> ; </span>]
06f5acb11f1c32228d93eefd1eb841dbfb1c7f4dAutomatic Updater [<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> zero-no-soa-ttl-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> resolver-query-timeout <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> deny-answer-addresses { <em class="replaceable"><code>address_match_list</code></em> } [<span class="optional"> except-from { <em class="replaceable"><code>namelist</code></em> } </span>];</span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> deny-answer-aliases { <em class="replaceable"><code>namelist</code></em> } [<span class="optional"> except-from { <em class="replaceable"><code>namelist</code></em> } </span>];</span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> prefetch <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>number</code></em></span>] ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> rate-limit {
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> responses-per-second <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> referrals-per-second <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> nodata-per-second <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> nxdomains-per-second <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> errors-per-second <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> all-per-second <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> window <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> log-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> qps-scale <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> ipv4-prefix-length <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> ipv6-prefix-length <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> slip <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> exempt-clients { <em class="replaceable"><code>address_match_list</code></em> } ; </span>]
7fc3b88c3a6e18f8a085406c36fddc2af63619efMark Andrews [<span class="optional"> max-table-size <em class="replaceable"><code>number</code></em> ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> min-table-size <em class="replaceable"><code>number</code></em> ; </span>]
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater } ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> response-policy {
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater zone <em class="replaceable"><code>zone_name</code></em>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> policy <em class="replaceable"><code>(given | disabled | passthru | drop |
da24e725ff982595d74da7e75e9fbd6a696367ccAutomatic Updater tcp-only | nxdomain | nodata | cname domain</code></em>) </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> recursive-only <em class="replaceable"><code>yes_or_no</code></em> </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> max-policy-ttl <em class="replaceable"><code>number</code></em> </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> break-dnssec <em class="replaceable"><code>yes_or_no</code></em> </span>]
5a28dc400e0e85382e83a479ca60ca3054e6cfccAutomatic Updater [<span class="optional"> min-ns-dots <em class="replaceable"><code>number</code></em> </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> qname-wait-recurse <em class="replaceable"><code>yes_or_no</code></em> </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater ; [<span class="optional">...</span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater } ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater};
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater</pre>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater</div>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<div class="sect2" lang="en">
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<a name="options"></a><span><strong class="command">options</strong></span> Statement Definition and
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater Usage</h3></div></div></div>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater The <span><strong class="command">options</strong></span> statement sets up global
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater options
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater to be used by <acronym class="acronym">BIND</acronym>. This statement
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater may appear only
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater once in a configuration file. If there is no <span><strong class="command">options</strong></span>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater statement, an options block with each option set to its default will
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater be used.
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews </p>
693c4232dfdffaff672197d4b9fea944c64cf80aAutomatic Updater<div class="variablelist"><dl>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<dt><span class="term"><span><strong class="command">attach-cache</strong></span></span></dt>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<dd>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<p>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater Allows multiple views to share a single cache
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater database.
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater Each view has its own cache database by default, but
603cf17f33da24d460616389ec40d6f2a6e110a0Automatic Updater if multiple views have the same operational policy
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater for name resolution and caching, those views can
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater share a single cache to save memory and possibly
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater improve resolution efficiency by using this option.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<p>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater The <span><strong class="command">attach-cache</strong></span> option
55aec75784a22e9d06d52b2b8a7d5aa42d31dc00Automatic Updater may also be specified in <span><strong class="command">view</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statements, in which case it overrides the
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater global <span><strong class="command">attach-cache</strong></span> option.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<p>
93bd88e172a36b549938bce1731df7c10a8f3fb5Automatic Updater The <em class="replaceable"><code>cache_name</code></em> specifies
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the cache to be shared.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater When the <span><strong class="command">named</strong></span> server configures
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater views which are supposed to share a cache, it
db5b7e2cdf150c46e8242d3e2e3ad3f5c7300258Automatic Updater creates a cache with the specified name for the
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater first view of these sharing views.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater The rest of the views will simply refer to the
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater already created cache.
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater </p>
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater<p>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater One common configuration to share a cache would be to
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater allow all views to share a single cache.
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater This can be done by specifying
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater the <span><strong class="command">attach-cache</strong></span> as a global
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater option with an arbitrary name.
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater </p>
67f4b01f01bc7fd1ddf938be8367f6b0ce29a520Automatic Updater<p>
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews Another possible operation is to allow a subset of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater all views to share a cache while the others to
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews retain their own caches.
0429fc942ef48b8ab07a01648b22f98174a2ae6fAutomatic Updater For example, if there are three views A, B, and C,
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater and only A and B should share a cache, specify the
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater <span><strong class="command">attach-cache</strong></span> option as a view A (or
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater B)'s option, referring to the other view name:
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">
47ff70af9e842bf0f69d209433995216f560fe4aAutomatic Updater view "A" {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater // this view has its own cache
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater ...
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater };
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater view "B" {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater // this view refers to A's cache
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater attach-cache "A";
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater };
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater view "C" {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater // this view has its own cache
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater ...
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater };
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater</pre>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater Views that share a cache must have the same policy
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater on configurable parameters that may affect caching.
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater The current implementation requires the following
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater configurable options be consistent among these
19b3dc94bce93fa76bd7e066f9298630dbc9dcb4Automatic Updater views:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">check-names</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">cleaning-interval</strong></span>,
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <span><strong class="command">dnssec-accept-expired</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">dnssec-validation</strong></span>,
83d29eff2912ef967596eb5ed148de7668b35564Automatic Updater <span><strong class="command">max-cache-ttl</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">max-ncache-ttl</strong></span>,
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <span><strong class="command">max-cache-size</strong></span>, and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">zero-no-soa-ttl</strong></span>.
71bd43eebd9d6e42dbcae62b730f5b6508d5acd8Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater Note that there may be other parameters that may
129090f0f6f91753b4a085ab635e28549fd018adAutomatic Updater cause confusion if they are inconsistent for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater different views that share a single cache.
098097efb95046a4a5285b6dae95dea3e3b70853Automatic Updater For example, if these views define different sets of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater forwarders that can return different answers for the
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater same question, sharing the answer does not make
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater sense or could even be harmful.
78bc8fdc2488c92d7228e8de19827e2c114c56caAutomatic Updater It is administrator's responsibility to ensure
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater configuration differences in different views do
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater not cause disruption with a shared cache.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
9d80d23172c30fd63e5046a7e69b8445e564ff31Automatic Updater</dd>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<dt><span class="term"><span><strong class="command">directory</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The working directory of the server.
19b3dc94bce93fa76bd7e066f9298630dbc9dcb4Automatic Updater Any non-absolute pathnames in the configuration file will be
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater taken
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater as relative to this directory. The default location for most
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater server
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater output files (e.g. <code class="filename">named.run</code>)
e705db6d5d886dc14f4a75a2046a075c0750e7eeAutomatic Updater is this directory.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater If a directory is not specified, the working directory
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater defaults to `<code class="filename">.</code>', the directory from
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater which the server
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater was started. The directory specified should be an absolute
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater path.
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater </p></dd>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater<dt><span class="term"><span><strong class="command">geoip-directory</strong></span></span></dt>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater<dd><p>
0ce87e5749aabb8eef1e0a37e4bd6e6ffa1d7196Automatic Updater Specifies the directory containing GeoIP
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">.dat</code> database files for GeoIP
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater initialization. By default, this option is unset
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and the GeoIP support will use libGeoIP's
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater built-in directory.
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater (For details, see <a href="Bv9ARM.ch06.html#acl" title="acl Statement Definition and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Usage">the section called &#8220;<span><strong class="command">acl</strong></span> Statement Definition and
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater Usage&#8221;</a> about the
0ce87e5749aabb8eef1e0a37e4bd6e6ffa1d7196Automatic Updater <span><strong class="command">geoip</strong></span> ACL.)
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater When performing dynamic update of secure zones, the
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater directory where the public and private DNSSEC key files
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater should be found, if different than the current working
2bb3422dc683c013db7042f5736240de6b86f182Automatic Updater directory. (Note that this option has no effect on the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater paths for files containing non-DNSSEC keys such as
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">bind.keys</code>,
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <code class="filename">rndc.key</code> or
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater <code class="filename">session.key</code>.)
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater </p></dd>
129090f0f6f91753b4a085ab635e28549fd018adAutomatic Updater<dt><span class="term"><span><strong class="command">managed-keys-directory</strong></span></span></dt>
8f1b19fb7ee72b09e360531691c5e5e941ef2d4eAutomatic Updater<dd>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<p>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater Specifies the directory in which to store the files that
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater track managed DNSSEC keys. By default, this is the working
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater directory.
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater </p>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <span><strong class="command">named</strong></span> is not configured to use views,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater then managed keys for the server will be tracked in a single
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater file called <code class="filename">managed-keys.bind</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Otherwise, managed keys will be tracked in separate files,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington one file per view; each file name will be the view name
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater (or, if it contains characters that are incompatible with
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater use as a file name, the SHA256 hash of the view name),
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater followed by the extension
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater <code class="filename">.mkeys</code>.
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater </p>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<p>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater (Note: in previous releases, file names for views
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater always used the SHA256 hash of the view name. To ensure
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater compatibility after upgrade, if a file using the old
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington name format is found to exist, it will be used instead
8a507eb20351ee478e8c05620c6899f0a04c1853Automatic Updater of the new format.)
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">named-xfer</strong></span></span></dt>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="emphasis"><em>This option is obsolete.</em></span> It
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater was used in <acronym class="acronym">BIND</acronym> 8 to specify
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the pathname to the <span><strong class="command">named-xfer</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater program. In <acronym class="acronym">BIND</acronym> 9, no separate
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">named-xfer</strong></span> program is needed;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater its functionality is built into the name server.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">tkey-gssapi-keytab</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
681beefc668253b3e469a1de282fbc33a3752422Automatic Updater The KRB5 keytab file to use for GSS-TSIG updates. If
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater this option is set and tkey-gssapi-credential is not
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater set, then updates will be allowed with any key
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater matching a principal in the specified keytab.
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater </p></dd>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<dt><span class="term"><span><strong class="command">tkey-gssapi-credential</strong></span></span></dt>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<dd><p>
aa620c4f3a002a87e8d2076b6909cfeda81d71ddAutomatic Updater The security credential with which the server should
b16e2045ac28229c31f1ea3ebad15cbcb13e1d24Automatic Updater authenticate keys requested by the GSS-TSIG protocol.
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews Currently only Kerberos 5 authentication is available
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater and the credential is a Kerberos principal which the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater server can acquire through the default system key
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews file, normally <code class="filename">/etc/krb5.keytab</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The location keytab file can be overridden using the
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews tkey-gssapi-keytab option. Normally this principal is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater of the form "<strong class="userinput"><code>DNS/</code></strong><code class="varname">server.domain</code>".
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater To use GSS-TSIG, <span><strong class="command">tkey-domain</strong></span> must
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater also be set if a specific keytab is not set with
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater tkey-gssapi-keytab.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<dt><span class="term"><span><strong class="command">tkey-domain</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The domain appended to the names of all shared keys
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater generated with <span><strong class="command">TKEY</strong></span>. When a
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater client requests a <span><strong class="command">TKEY</strong></span> exchange,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater it may or may not specify the desired name for the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater key. If present, the name of the shared key will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater be <code class="varname">client specified part</code> +
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <code class="varname">tkey-domain</code>. Otherwise, the
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater name of the shared key will be <code class="varname">random hex
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater digits</code> + <code class="varname">tkey-domain</code>.
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater In most cases, the <span><strong class="command">domainname</strong></span>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater should be the server's domain name, or an otherwise
930f6069e5aa157cf6987cdafd412f5757a5a558Automatic Updater non-existent subdomain like
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater "_tkey.<code class="varname">domainname</code>". If you are
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater using GSS-TSIG, this variable must be defined, unless
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater you specify a specific keytab using tkey-gssapi-keytab.
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater </p></dd>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<dt><span class="term"><span><strong class="command">tkey-dhkey</strong></span></span></dt>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater<dd><p>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater The Diffie-Hellman key used by the server
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to generate shared keys with clients using the Diffie-Hellman
0ce87e5749aabb8eef1e0a37e4bd6e6ffa1d7196Automatic Updater mode
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater of <span><strong class="command">TKEY</strong></span>. The server must be
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater able to load the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater public and private keys from files in the working directory.
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater In
415827fa645306ee54b7c5480f52c19217035103Automatic Updater most cases, the keyname should be the server's host name.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p></dd>
96ea71632887c58a9d00f47eb318bf76b35903c3Mark Andrews<dt><span class="term"><span><strong class="command">cache-file</strong></span></span></dt>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater<dd><p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater This is for testing only. Do not use.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p></dd>
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews<dt><span class="term"><span><strong class="command">dump-file</strong></span></span></dt>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dd><p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater The pathname of the file the server dumps
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater the database to when instructed to do so with
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater <span><strong class="command">rndc dumpdb</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If not specified, the default is <code class="filename">named_dump.db</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater<dt><span class="term"><span><strong class="command">memstatistics-file</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater The pathname of the file the server writes memory
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater usage statistics to on exit. If not specified,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the default is <code class="filename">named.memstats</code>.
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">pid-file</strong></span></span></dt>
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The pathname of the file the server writes its process ID
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in. If not specified, the default is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">/var/run/named/named.pid</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The PID file is used by programs that want to send signals to
681beefc668253b3e469a1de282fbc33a3752422Automatic Updater the running
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater name server. Specifying <span><strong class="command">pid-file none</strong></span> disables the
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater use of a PID file &#8212; no file will be written and any
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater existing one will be removed. Note that <span><strong class="command">none</strong></span>
4dca64bb8991502db368028aeeba2f832d3b971dAutomatic Updater is a keyword, not a filename, and therefore is not enclosed
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater double quotes.
71bd43eebd9d6e42dbcae62b730f5b6508d5acd8Automatic Updater </p></dd>
c01dec514a81ecf8c17ca3ef8c3ba95e437295ebAutomatic Updater<dt><span class="term"><span><strong class="command">recursing-file</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The pathname of the file the server dumps
681beefc668253b3e469a1de282fbc33a3752422Automatic Updater the queries that are currently recursing when instructed
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to do so with <span><strong class="command">rndc recursing</strong></span>.
ce0fd07045292942bfa3e755d9ce596941528a63Automatic Updater If not specified, the default is <code class="filename">named.recursing</code>.
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater </p></dd>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dt><span class="term"><span><strong class="command">statistics-file</strong></span></span></dt>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The pathname of the file the server appends statistics
96713299d08c0735c18ebe8772dd2cc1ecd4356aAutomatic Updater to when instructed to do so using <span><strong class="command">rndc stats</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If not specified, the default is <code class="filename">named.stats</code> in the
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater server's current directory. The format of the file is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater described
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington in <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called &#8220;The Statistics File&#8221;</a>.
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p></dd>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dt><span class="term"><span><strong class="command">bindkeys-file</strong></span></span></dt>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dd><p>
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater The pathname of a file to override the built-in trusted
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater keys provided by <span><strong class="command">named</strong></span>.
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater See the discussion of <span><strong class="command">dnssec-lookaside</strong></span>
6a6965084d061016f7ba44637c7c50e096cac36aAutomatic Updater and <span><strong class="command">dnssec-validation</strong></span> for details.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If not specified, the default is
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater <code class="filename">/etc/bind.keys</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<dt><span class="term"><span><strong class="command">secroots-file</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The pathname of the file the server dumps
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater security roots to when instructed to do so with
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">rndc secroots</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If not specified, the default is
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater <code class="filename">named.secroots</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">session-keyfile</strong></span></span></dt>
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The pathname of the file into which to write a TSIG
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater session key generated by <span><strong class="command">named</strong></span> for use by
0c42fc3acc95ea284cf1bfdf6869d1836756ebb9Automatic Updater <span><strong class="command">nsupdate -l</strong></span>. If not specified, the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater default is <code class="filename">/var/run/named/session.key</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater (See <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>, and in
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater particular the discussion of the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">update-policy</strong></span> statement's
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <strong class="userinput"><code>local</code></strong> option for more
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater information about this feature.)
098097efb95046a4a5285b6dae95dea3e3b70853Automatic Updater </p></dd>
4dca64bb8991502db368028aeeba2f832d3b971dAutomatic Updater<dt><span class="term"><span><strong class="command">session-keyname</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The key name to use for the TSIG session key.
98215f712033f868cc65cc2e54894bf770517883Automatic Updater If not specified, the default is "local-ddns".
71bd43eebd9d6e42dbcae62b730f5b6508d5acd8Automatic Updater </p></dd>
78bc8fdc2488c92d7228e8de19827e2c114c56caAutomatic Updater<dt><span class="term"><span><strong class="command">session-keyalg</strong></span></span></dt>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The algorithm to use for the TSIG session key.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Valid values are hmac-sha1, hmac-sha224, hmac-sha256,
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater hmac-sha384, hmac-sha512 and hmac-md5. If not
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater specified, the default is hmac-sha256.
0429fc942ef48b8ab07a01648b22f98174a2ae6fAutomatic Updater </p></dd>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson<dt><span class="term"><span><strong class="command">port</strong></span></span></dt>
0429fc942ef48b8ab07a01648b22f98174a2ae6fAutomatic Updater<dd><p>
9f0225ba7e69a36e546ef40107d86c1ba04f10dbAutomatic Updater The UDP/TCP port number the server uses for
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater receiving and sending DNS protocol traffic.
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater The default is 53. This option is mainly intended for server
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater testing;
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater a server using a port other than 53 will not be able to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater communicate with
e705db6d5d886dc14f4a75a2046a075c0750e7eeAutomatic Updater the global DNS.
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">dscp</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The global Differentiated Services Code Point (DSCP)
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater value to classify outgoing DNS traffic on operating
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater systems that support DSCP. Valid values are 0 through 63.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater It is not configured by default.
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater </p></dd>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="term"><span><strong class="command">random-device</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The source of entropy to be used by the server. Entropy is
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater primarily needed
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater for DNSSEC operations, such as TKEY transactions and dynamic
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater update of signed
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater zones. This options specifies the device (or file) from which
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater to read
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater entropy. If this is a file, operations requiring entropy will
40696c4c389a780082fb77840c173b201ce696d6Automatic Updater fail when the
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater file has been exhausted. If not specified, the default value
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater is
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater <code class="filename">/dev/random</code>
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater (or equivalent) when present, and none otherwise. The
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater <span><strong class="command">random-device</strong></span> option takes
30cd5217f750e75c24b4fe4b5ecf92e832ba64c3Automatic Updater effect during
40696c4c389a780082fb77840c173b201ce696d6Automatic Updater the initial configuration load at server startup time and
1d92d8a2456b23842a649b6104c60a9d6ea25333Brian Wellington is ignored on subsequent reloads.
22efac94468806d25459fa9d4faa6b1eb16c30a8Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">preferred-glue</strong></span></span></dt>
5a28dc400e0e85382e83a479ca60ca3054e6cfccAutomatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If specified, the listed type (A or AAAA) will be emitted
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater before other glue
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in the additional section of a query response.
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington The default is not to prefer any type (NONE).
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
1d92d8a2456b23842a649b6104c60a9d6ea25333Brian Wellington<dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="root_delegation_only"></a><span class="term"><span><strong class="command">root-delegation-only</strong></span></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Turn on enforcement of delegation-only in TLDs
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater (top level domains) and root zones with an optional
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater exclude list.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater DS queries are expected to be made to and be answered by
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater delegation only zones. Such queries and responses are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater treated as an exception to delegation-only processing
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and are not converted to NXDOMAIN responses provided
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a CNAME is not discovered at the query name.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If a delegation only zone server also serves a child
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater zone it is not always possible to determine whether
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater an answer comes from the delegation only zone or the
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater child zone. SOA NS and DNSKEY records are apex
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson only records and a matching response that contains
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater these records or DS is treated as coming from a
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson child zone. RRSIG records are also examined to see
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater if they are signed by a child zone or not. The
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater authority section is also examined to see if there
be7f27304337afbf078e8bd8db0f951a33abe33bAndreas Gustafsson is evidence that the answer is from the child zone.
22efac94468806d25459fa9d4faa6b1eb16c30a8Automatic Updater Answers that are determined to be from a child zone
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater are not converted to NXDOMAIN responses. Despite
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater all these checks there is still a possibility of
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater false negatives when a child zone is being served.
11ba7973f989b3657cbb27447bdcdd976c71ac56Brian Wellington </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
11ba7973f989b3657cbb27447bdcdd976c71ac56Brian Wellington Similarly false positives can arise from empty nodes
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater (no records at the name) in the delegation only zone
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater when the query type is not ANY.
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater Note some TLDs are not delegation only (e.g. "DE", "LV",
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater "US" and "MUSEUM"). This list is not exhaustive.
e5fe07a7ebff18f7ed4ac434b37daff6c8ee5d5bAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updateroptions {
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater root-delegation-only exclude { "de"; "lv"; "us"; "museum"; };
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater};
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater</dd>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater<dt><span class="term"><span><strong class="command">disable-algorithms</strong></span></span></dt>
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater<dd>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson<p>
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater Disable the specified DNSSEC algorithms at and below the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater specified name.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Multiple <span><strong class="command">disable-algorithms</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statements are allowed.
5a28dc400e0e85382e83a479ca60ca3054e6cfccAutomatic Updater Only the best match <span><strong class="command">disable-algorithms</strong></span>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater clause will be used to determine which algorithms are used.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
a900e4f99ff134b567b6df5ac2c841c7d0c551d3Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If all supported algorithms are disabled, the zones covered
a9638b6e8997c3c96a23a7df973aa126061ff34fAutomatic Updater by the <span><strong class="command">disable-algorithms</strong></span> will be treated
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater as insecure.
bde521789ec55f11ac6966d16bcd187e8fa1d4bfAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">disable-ds-digests</strong></span></span></dt>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<dd>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Disable the specified DS/DLV digest types at and below the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington specified name.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Multiple <span><strong class="command">disable-ds-digests</strong></span>
a900e4f99ff134b567b6df5ac2c841c7d0c551d3Automatic Updater statements are allowed.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Only the best match <span><strong class="command">disable-ds-digests</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater clause will be used to determine which digest types are used.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If all supported digest types are disabled, the zones covered
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater by the <span><strong class="command">disable-ds-digests</strong></span> will be treated
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater as insecure.
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">dnssec-lookaside</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater When set, <span><strong class="command">dnssec-lookaside</strong></span> provides the
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater validator with an alternate method to validate DNSKEY
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater records at the top of a zone. When a DNSKEY is at or
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater below a domain specified by the deepest
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">dnssec-lookaside</strong></span>, and the normal DNSSEC
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater validation has left the key untrusted, the trust-anchor
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater will be appended to the key name and a DLV record will be
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater looked up to see if it can validate the key. If the DLV
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater record validates a DNSKEY (similarly to the way a DS
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater record does) the DNSKEY RRset is deemed to be trusted.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <span><strong class="command">dnssec-lookaside</strong></span> is set to
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <strong class="userinput"><code>auto</code></strong>, then built-in default
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews values for the DLV domain and trust anchor will be
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews used, along with a built-in key for validation.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews If <span><strong class="command">dnssec-lookaside</strong></span> is set to
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <strong class="userinput"><code>no</code></strong>, then dnssec-lookaside
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews is not used.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews The default DLV key is stored in the file
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <code class="filename">bind.keys</code>;
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <span><strong class="command">named</strong></span> will load that key at
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews startup if <span><strong class="command">dnssec-lookaside</strong></span> is set to
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <code class="constant">auto</code>. A copy of the file is
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews installed along with <acronym class="acronym">BIND</acronym> 9, and is
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews current as of the release date. If the DLV key expires, a
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews new copy of <code class="filename">bind.keys</code> can be downloaded
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews from <a href="https://www.isc.org/solutions/dlv/" target="_top">https://www.isc.org/solutions/dlv/</a>.
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews (To prevent problems if <code class="filename">bind.keys</code> is
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews not found, the current key is also compiled in to
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <span><strong class="command">named</strong></span>. Relying on this is not
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews recommended, however, as it requires <span><strong class="command">named</strong></span>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews to be recompiled with a new key when the DLV key expires.)
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews NOTE: <span><strong class="command">named</strong></span> only loads certain specific
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews keys from <code class="filename">bind.keys</code>: those for the
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews DLV zone and for the DNS root zone. The file cannot be
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews used to store keys for other zones.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</dd>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<dt><span class="term"><span><strong class="command">dnssec-must-be-secure</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd><p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Specify hierarchies which must be or may not be secure
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews (signed and validated). If <strong class="userinput"><code>yes</code></strong>,
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews then <span><strong class="command">named</strong></span> will only accept answers if
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews they are secure. If <strong class="userinput"><code>no</code></strong>, then normal
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews DNSSEC validation applies allowing for insecure answers to
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews be accepted. The specified domain must be under a
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <span><strong class="command">trusted-keys</strong></span> or
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews <span><strong class="command">managed-keys</strong></span> statement, or
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <span><strong class="command">dnssec-lookaside</strong></span> must be active.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p></dd>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<dt><span class="term"><span><strong class="command">dns64</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews This directive instructs <span><strong class="command">named</strong></span> to
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews return mapped IPv4 addresses to AAAA queries when
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater there are no AAAA records. It is intended to be
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater used in conjunction with a NAT64. Each
e23256e740b238bddb4ba41ffac5f81a01c92245Automatic Updater <span><strong class="command">dns64</strong></span> defines one DNS64 prefix.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Multiple DNS64 prefixes can be defined.
34729dbcb3526974cf98ee03ec20a107d9458417Andreas Gustafsson </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
34729dbcb3526974cf98ee03ec20a107d9458417Andreas Gustafsson Compatible IPv6 prefixes have lengths of 32, 40, 48, 56,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater 64 and 96 as per RFC 6052.
34729dbcb3526974cf98ee03ec20a107d9458417Andreas Gustafsson </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Additionally a reverse IP6.ARPA zone will be created for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the prefix to provide a mapping from the IP6.ARPA names
34729dbcb3526974cf98ee03ec20a107d9458417Andreas Gustafsson to the corresponding IN-ADDR.ARPA names using synthesized
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater CNAMEs. <span><strong class="command">dns64-server</strong></span> and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">dns64-contact</strong></span> can be used to specify
34729dbcb3526974cf98ee03ec20a107d9458417Andreas Gustafsson the name of the server and contact for the zones. These
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater are settable at the view / options level. These are
34729dbcb3526974cf98ee03ec20a107d9458417Andreas Gustafsson not settable on a per-prefix basis.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Each <span><strong class="command">dns64</strong></span> supports an optional
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">clients</strong></span> ACL that determines which
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater clients are affected by this directive. If not defined,
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson it defaults to <strong class="userinput"><code>any;</code></strong>.
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<p>
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater Each <span><strong class="command">dns64</strong></span> supports an optional
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater <span><strong class="command">mapped</strong></span> ACL that selects which
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater IPv4 addresses are to be mapped in the corresponding
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A RRset. If not defined it defaults to
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>any;</code></strong>.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
713c3d5b18463f2479973e4d14f73248e60a5df7Mark Andrews<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Normally, DNS64 won't apply to a domain name that
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater owns one or more AAAA records; these records will
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington simply be returned. The optional
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">exclude</strong></span> ACL allows specification
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater of a list of IPv6 addresses that will be ignored
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater if they appear in a domain name's AAAA records, and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater DNS64 will be applied to any A records the domain
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson name owns. If not defined, <span><strong class="command">exclude</strong></span>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson defaults to none.
992616aaf75643a0c9f84826f0a1ed5a27e84328Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
2fd97723b2ec7fc1975672780ab0c1c9a8c369d6Automatic Updater A optional <span><strong class="command">suffix</strong></span> can also
2fd97723b2ec7fc1975672780ab0c1c9a8c369d6Automatic Updater be defined to set the bits trailing the mapped
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews IPv4 address bits. By default these bits are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater set to <strong class="userinput"><code>::</code></strong>. The bits
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater matching the prefix and mapped IPv4 address
0d3490f93bb980fde704055e74c1b508987a5fe4Mark Andrews must be zero.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
922e6a3c2ac4ef900dd9dc99f0cc137f18372583Andreas Gustafsson<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If <span><strong class="command">recursive-only</strong></span> is set to
990743075cd7b0ee4bc0c8bf013bb1d9662a3167Mark Andrews <span><strong class="command">yes</strong></span> the DNS64 synthesis will
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews only happen for recursive queries. The default
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews is <span><strong class="command">no</strong></span>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If <span><strong class="command">break-dnssec</strong></span> is set to
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">yes</strong></span> the DNS64 synthesis will
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews happen even if the result, if validated, would
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews cause a DNSSEC validation failure. If this option
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews is set to <span><strong class="command">no</strong></span> (the default), the DO
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews is set on the incoming query, and there are RRSIGs on
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews the applicable records, then synthesis will not happen.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<pre class="programlisting">
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews acl rfc1918 { 10/8; 192.168/16; 172.16/12; };
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater dns64 64:FF9B::/96 {
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater clients { any; };
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater mapped { !rfc1918; any; };
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews exclude { 64:FF9B::/96; ::ffff:0000:0000/96; };
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews suffix ::;
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews };
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</pre>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">dnssec-update-mode</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If this option is set to its default value of
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <code class="literal">maintain</code> in a zone of type
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <code class="literal">master</code> which is DNSSEC-signed
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews and configured to allow dynamic updates (see
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>), and
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews if <span><strong class="command">named</strong></span> has access to the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews private signing key(s) for the zone, then
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">named</strong></span> will automatically sign all new
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews or changed records and maintain signatures for the zone
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews by regenerating RRSIG records whenever they approach
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews their expiration date.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If the option is changed to <code class="literal">no-resign</code>,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews then <span><strong class="command">named</strong></span> will sign all new or
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews changed records, but scheduled maintenance of
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater signatures is disabled.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater With either of these settings, <span><strong class="command">named</strong></span>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater will reject updates to a DNSSEC-signed zone when the
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater signing keys are inactive or unavailable to
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">named</strong></span>. (A planned third option,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <code class="literal">external</code>, will disable all automatic
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater signing and allow DNSSEC data to be submitted into a zone
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater via dynamic update; this is not yet implemented.)
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater</dd>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<dt><span class="term"><span><strong class="command">nta-lifetime</strong></span></span></dt>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<dd>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Species the default lifetime, in seconds,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews that will be used for negative trust anchors added
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater via <span><strong class="command">rndc nta</strong></span>.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater A negative trust anchor selectively disables
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater DNSSEC validation for zones that are known to be
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater failing because of misconfiguration rather than
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater an attack. When data to be validated is
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater at or below an active NTA (and above any other
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater configured trust anchors), <span><strong class="command">named</strong></span> will
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater abort the DNSSEC validation process and treat the data as
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater insecure rather than bogus. This continues until the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews NTA's lifetime is elapsed. NTAs persist
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews across <span><strong class="command">named</strong></span> restarts.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews For convenience, TTL-style time unit suffixes can be
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater used to specify the NTA lifetime in seconds, minutes
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews or hours. <code class="option">nta-lifetime</code> defaults to
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater one hour. It cannot exceed one week.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater</dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">nta-recheck</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Species how often to check whether negative
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews trust anchors added via <span><strong class="command">rndc nta</strong></span>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews are still necessary.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews A negative trust anchor is normally used when a
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews domain has stopped validating due to operator error;
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews it temporarily disables DNSSEC validation for that
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews domain. In the interest of ensuring that DNSSEC
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews validation is turned back on as soon as possible,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">named</strong></span> will periodically send a
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews query to the domain, ignoring negative trust anchors,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews to find out whether it can now be validated. If so,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews the negative trust anchor is allowed to expire early.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Validity checks can be disabled for an individual
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews NTA by using <span><strong class="command">rndc nta -f</strong></span>, or
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews for all NTAs by setting <code class="option">nta-recheck</code>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews to zero.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews For convenience, TTL-style time unit suffixes can be
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews used to specify the NTA recheck interval in seconds,
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater minutes or hours. The default is five minutes. It
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews cannot be longer than <code class="option">nta-lifetime</code>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews (which cannot be longer than a week).
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">max-zone-ttl</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Specifies a maximum permissible TTL value.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews When loading a zone file using a
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <code class="option">masterfile-format</code> of
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <code class="constant">text</code> or <code class="constant">raw</code>,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews any record encountered with a TTL higher than
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <code class="option">max-zone-ttl</code> will cause the zone to
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews be rejected.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews This is useful in DNSSEC-signed zones because when
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews rolling to a new DNSKEY, the old key needs to remain
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater available until RRSIG records have expired from
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater caches. The<code class="option">max-zone-ttl</code> option guarantees
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater that the largest TTL in the zone will be no higher
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater the set value.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews (NOTE: Because <code class="constant">map</code>-format files
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews load directly into memory, this option cannot be
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews used with them.)
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If <strong class="userinput"><code>full</code></strong>, the server will collect
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews statistical data on all zones (unless specifically
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews turned off on a per-zone basis by specifying
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">zone-statistics terse</strong></span> or
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">zone-statistics none</strong></span>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews in the <span><strong class="command">zone</strong></span> statement).
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The default is <strong class="userinput"><code>terse</code></strong>, providing
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews minimal statistics on zones (including name and
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews current serial number, but not query type
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews counters).
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews These statistics may be accessed via the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">statistics-channel</strong></span> or
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews using <span><strong class="command">rndc stats</strong></span>, which
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews will dump them to the file listed
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews in the <span><strong class="command">statistics-file</strong></span>. See
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater also <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called &#8220;The Statistics File&#8221;</a>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater For backward compatibility with earlier versions
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews of BIND 9, the <span><strong class="command">zone-statistics</strong></span>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews option can also accept <strong class="userinput"><code>yes</code></strong>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater or <strong class="userinput"><code>no</code></strong>; <strong class="userinput"><code>yes</code></strong>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews has the same meaning as <strong class="userinput"><code>full</code></strong>.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater As of <acronym class="acronym">BIND</acronym> 9.10,
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <strong class="userinput"><code>no</code></strong> has the same meaning
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater as <strong class="userinput"><code>none</code></strong>; previously, it
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater was the same as <strong class="userinput"><code>terse</code></strong>.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</dl></div>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<div class="sect3" lang="en">
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<div class="titlepage"><div><div><h4 class="title">
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<a name="boolean_options"></a>Boolean Options</h4></div></div></div>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<div class="variablelist"><dl>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">automatic-interface-scan</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If <strong class="userinput"><code>yes</code></strong> and supported by the OS,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews automatically rescan network interfaces when the interface
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews addresses are added or removed. The default is
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <strong class="userinput"><code>yes</code></strong>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Currently the OS needs to support routing sockets for
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">automatic-interface-scan</strong></span> to be
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews supported.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">allow-new-zones</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd><p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then zones can be
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews added at runtime via <span><strong class="command">rndc addzone</strong></span>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The default is <strong class="userinput"><code>no</code></strong>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">auth-nxdomain</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd><p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If <strong class="userinput"><code>yes</code></strong>, then the <span><strong class="command">AA</strong></span> bit
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews is always set on NXDOMAIN responses, even if the server is
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater not actually
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater authoritative. The default is <strong class="userinput"><code>no</code></strong>;
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater this is
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater a change from <acronym class="acronym">BIND</acronym> 8. If you
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater are using very old DNS software, you
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews may need to set it to <strong class="userinput"><code>yes</code></strong>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">deallocate-on-exit</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd><p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews This option was used in <acronym class="acronym">BIND</acronym>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater 8 to enable checking
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews for memory leaks on exit. <acronym class="acronym">BIND</acronym> 9 ignores the option and always performs
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews the checks.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">memstatistics</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd><p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Write memory statistics to the file specified by
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">memstatistics-file</strong></span> at exit.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The default is <strong class="userinput"><code>no</code></strong> unless
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews '-m record' is specified on the command line in
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews which case it is <strong class="userinput"><code>yes</code></strong>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If <strong class="userinput"><code>yes</code></strong>, then the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews server treats all zones as if they are doing zone transfers
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews across
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater a dial-on-demand dialup link, which can be brought up by
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews traffic
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews originating from this server. This has different effects
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews according
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews to zone type and concentrates the zone maintenance so that
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews it all
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews happens in a short interval, once every <span><strong class="command">heartbeat-interval</strong></span> and
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater hopefully during the one call. It also suppresses some of
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater the normal
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater zone maintenance traffic. The default is <strong class="userinput"><code>no</code></strong>.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The <span><strong class="command">dialup</strong></span> option
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater may also be specified in the <span><strong class="command">view</strong></span> and
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <span><strong class="command">zone</strong></span> statements,
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater in which case it overrides the global <span><strong class="command">dialup</strong></span>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater option.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater If the zone is a master zone, then the server will send out a
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews NOTIFY
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews request to all the slaves (default). This should trigger the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews zone serial
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater number check in the slave (providing it supports NOTIFY)
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater allowing the slave
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater to verify the zone while the connection is active.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The set of servers to which NOTIFY is sent can be controlled
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater by
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <span><strong class="command">notify</strong></span> and <span><strong class="command">also-notify</strong></span>.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater If the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews zone is a slave or stub zone, then the server will suppress
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews the regular
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews "zone up to date" (refresh) queries and only perform them
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews when the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">heartbeat-interval</strong></span> expires in
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews addition to sending
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews NOTIFY requests.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Finer control can be achieved by using
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <strong class="userinput"><code>notify</code></strong> which only sends NOTIFY
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews messages,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <strong class="userinput"><code>notify-passive</code></strong> which sends NOTIFY
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews messages and
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews suppresses the normal refresh queries, <strong class="userinput"><code>refresh</code></strong>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews which suppresses normal refresh processing and sends refresh
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews queries
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews when the <span><strong class="command">heartbeat-interval</strong></span>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews expires, and
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <strong class="userinput"><code>passive</code></strong> which just disables normal
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews refresh
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews processing.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<div class="informaltable"><table border="1">
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<colgroup>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<col>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<col>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<col>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<col>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</colgroup>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<tbody>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<tr>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater dialup mode
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
990743075cd7b0ee4bc0c8bf013bb1d9662a3167Mark Andrews <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington normal refresh
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews </td>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<td>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater <p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater heart-beat refresh
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater heart-beat notify
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
db854396212d4195bbbf9de89951d9c2a5770e91Automatic Updater</tr>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">no</strong></span> (default)</p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater yes
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater no
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
195e7b7a6e0bdc80373d65085e12a2950e9a1226Mark Andrews </td>
96249c843a6d0df50c583579b0be030e323acc37Automatic Updater<td>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater <p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater no
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater </p>
63d98873e29dee9608c27f40613cb69d130a56e7Mark Andrews </td>
46da3117812814a29432a8d9a9ccf8acdbfdadceAutomatic Updater</tr>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<tr>
ca9a8f6d0b0f2a400a96f868193471510364336fMark Andrews<td>
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater <p><span><strong class="command">yes</strong></span></p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
72628f51c75245fa522fc27ac982392891e7bf87Automatic Updater <p>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater no
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater </p>
3ab6f6505bccd551415e6007c068ab73ec043833Automatic Updater </td>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<td>
<p>
yes
</p>
</td>
<td>
<p>
yes
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">notify</strong></span></p>
</td>
<td>
<p>
yes
</p>
</td>
<td>
<p>
no
</p>
</td>
<td>
<p>
yes
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">refresh</strong></span></p>
</td>
<td>
<p>
no
</p>
</td>
<td>
<p>
yes
</p>
</td>
<td>
<p>
no
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">passive</strong></span></p>
</td>
<td>
<p>
no
</p>
</td>
<td>
<p>
no
</p>
</td>
<td>
<p>
no
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">notify-passive</strong></span></p>
</td>
<td>
<p>
no
</p>
</td>
<td>
<p>
no
</p>
</td>
<td>
<p>
yes
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
Note that normal NOTIFY processing is not affected by
<span><strong class="command">dialup</strong></span>.
</p>
</dd>
<dt><span class="term"><span><strong class="command">fake-iquery</strong></span></span></dt>
<dd><p>
In <acronym class="acronym">BIND</acronym> 8, this option
enabled simulating the obsolete DNS query type
IQUERY. <acronym class="acronym">BIND</acronym> 9 never does
IQUERY simulation.
</p></dd>
<dt><span class="term"><span><strong class="command">fetch-glue</strong></span></span></dt>
<dd><p>
This option is obsolete.
In BIND 8, <strong class="userinput"><code>fetch-glue yes</code></strong>
caused the server to attempt to fetch glue resource records
it
didn't have when constructing the additional
data section of a response. This is now considered a bad
idea
and BIND 9 never does it.
</p></dd>
<dt><span class="term"><span><strong class="command">flush-zones-on-shutdown</strong></span></span></dt>
<dd><p>
When the nameserver exits due receiving SIGTERM,
flush or do not flush any pending zone writes. The default
is
<span><strong class="command">flush-zones-on-shutdown</strong></span> <strong class="userinput"><code>no</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">geoip-use-ecs</strong></span></span></dt>
<dd><p>
When BIND is compiled with GeoIP support and configured
with "geoip" ACL elements, this option indicates whether
the EDNS Client Subnet option, if present in a request,
should be used for matching against the GeoIP database.
The default is
<span><strong class="command">geoip-use-ecs</strong></span> <strong class="userinput"><code>yes</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">has-old-clients</strong></span></span></dt>
<dd><p>
This option was incorrectly implemented
in <acronym class="acronym">BIND</acronym> 8, and is ignored by <acronym class="acronym">BIND</acronym> 9.
To achieve the intended effect
of
<span><strong class="command">has-old-clients</strong></span> <strong class="userinput"><code>yes</code></strong>, specify
the two separate options <span><strong class="command">auth-nxdomain</strong></span> <strong class="userinput"><code>yes</code></strong>
and <span><strong class="command">rfc2308-type1</strong></span> <strong class="userinput"><code>no</code></strong> instead.
</p></dd>
<dt><span class="term"><span><strong class="command">host-statistics</strong></span></span></dt>
<dd><p>
In BIND 8, this enables keeping of
statistics for every host that the name server interacts
with.
Not implemented in BIND 9.
</p></dd>
<dt><span class="term"><span><strong class="command">maintain-ixfr-base</strong></span></span></dt>
<dd><p>
<span class="emphasis"><em>This option is obsolete</em></span>.
It was used in <acronym class="acronym">BIND</acronym> 8 to
determine whether a transaction log was
kept for Incremental Zone Transfer. <acronym class="acronym">BIND</acronym> 9 maintains a transaction
log whenever possible. If you need to disable outgoing
incremental zone
transfers, use <span><strong class="command">provide-ixfr</strong></span> <strong class="userinput"><code>no</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">minimal-responses</strong></span></span></dt>
<dd><p>
If <strong class="userinput"><code>yes</code></strong>, then when generating
responses the server will only add records to the authority
and additional data sections when they are required (e.g.
delegations, negative responses). This may improve the
performance of the server.
The default is <strong class="userinput"><code>no</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">multiple-cnames</strong></span></span></dt>
<dd><p>
This option was used in <acronym class="acronym">BIND</acronym> 8 to allow
a domain name to have multiple CNAME records in violation of
the DNS standards. <acronym class="acronym">BIND</acronym> 9.2 onwards
always strictly enforces the CNAME rules both in master
files and dynamic updates.
</p></dd>
<dt><span class="term"><span><strong class="command">notify</strong></span></span></dt>
<dd>
<p>
If <strong class="userinput"><code>yes</code></strong> (the default),
DNS NOTIFY messages are sent when a zone the server is
authoritative for
changes, see <a href="Bv9ARM.ch04.html#notify" title="Notify">the section called &#8220;Notify&#8221;</a>. The messages are
sent to the
servers listed in the zone's NS records (except the master
server identified
in the SOA MNAME field), and to any servers listed in the
<span><strong class="command">also-notify</strong></span> option.
</p>
<p>
If <strong class="userinput"><code>master-only</code></strong>, notifies are only
sent
for master zones.
If <strong class="userinput"><code>explicit</code></strong>, notifies are sent only
to
servers explicitly listed using <span><strong class="command">also-notify</strong></span>.
If <strong class="userinput"><code>no</code></strong>, no notifies are sent.
</p>
<p>
The <span><strong class="command">notify</strong></span> option may also be
specified in the <span><strong class="command">zone</strong></span>
statement,
in which case it overrides the <span><strong class="command">options notify</strong></span> statement.
It would only be necessary to turn off this option if it
caused slaves
to crash.
</p>
</dd>
<dt><span class="term"><span><strong class="command">notify-to-soa</strong></span></span></dt>
<dd><p>
If <strong class="userinput"><code>yes</code></strong> do not check the nameservers
in the NS RRset against the SOA MNAME. Normally a NOTIFY
message is not sent to the SOA MNAME (SOA ORIGIN) as it is
supposed to contain the name of the ultimate master.
Sometimes, however, a slave is listed as the SOA MNAME in
hidden master configurations and in that case you would
want the ultimate master to still send NOTIFY messages to
all the nameservers listed in the NS RRset.
</p></dd>
<dt><span class="term"><span><strong class="command">recursion</strong></span></span></dt>
<dd><p>
If <strong class="userinput"><code>yes</code></strong>, and a
DNS query requests recursion, then the server will attempt
to do
all the work required to answer the query. If recursion is
off
and the server does not already know the answer, it will
return a
referral response. The default is
<strong class="userinput"><code>yes</code></strong>.
Note that setting <span><strong class="command">recursion no</strong></span> does not prevent
clients from getting data from the server's cache; it only
prevents new data from being cached as an effect of client
queries.
Caching may still occur as an effect the server's internal
operation, such as NOTIFY address lookups.
See also <span><strong class="command">fetch-glue</strong></span> above.
</p></dd>
<dt><span class="term"><span><strong class="command">request-nsid</strong></span></span></dt>
<dd><p>
If <strong class="userinput"><code>yes</code></strong>, then an empty EDNS(0)
NSID (Name Server Identifier) option is sent with all
queries to authoritative name servers during iterative
resolution. If the authoritative server returns an NSID
option in its response, then its contents are logged in
the <span><strong class="command">resolver</strong></span> category at level
<span><strong class="command">info</strong></span>.
The default is <strong class="userinput"><code>no</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">request-sit</strong></span></span></dt>
<dd><p>
If <strong class="userinput"><code>yes</code></strong>, then a SIT (Source
Identity Token) EDNS option is sent along with
the query. If the resolver has previously talked
to the server, the SIT returned in the previous
transaction is sent. This is used by the server
to determine whether the resolver has talked to
it before. A resolver sending the correct SIT is
assumed not to be an off-path attacker sending a
spoofed-source query; the query is therefore
unlikely to be part of a reflection/amplification
attack, so resolvers sending a correct SIT option
are not subject to response rate limiting (RRL).
Resolvers which do not send a correct SIT option
may be limited to receiving smaller responses via
the <span><strong class="command">nosit-udp-size</strong></span> option.
</p></dd>
<dt><span class="term"><span><strong class="command">sit-secret</strong></span></span></dt>
<dd><p>
If set, this is a shared secret used for generating
and verifying Source Identity Token EDNS options
within an anycast cluster. If not set, the system
will generate a random secret at startup. The
shared secret is encoded as a hex string and needs
to be 128 bits for AES128, 160 bits for SHA1 and
256 bits for SHA256.
</p></dd>
<dt><span class="term"><span><strong class="command">rfc2308-type1</strong></span></span></dt>
<dd>
<p>
Setting this to <strong class="userinput"><code>yes</code></strong> will
cause the server to send NS records along with the SOA
record for negative
answers. The default is <strong class="userinput"><code>no</code></strong>.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Not yet implemented in <acronym class="acronym">BIND</acronym>
9.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">use-id-pool</strong></span></span></dt>
<dd><p>
<span class="emphasis"><em>This option is obsolete</em></span>.
<acronym class="acronym">BIND</acronym> 9 always allocates query
IDs from a pool.
</p></dd>
<dt><span class="term"><span><strong class="command">use-ixfr</strong></span></span></dt>
<dd><p>
<span class="emphasis"><em>This option is obsolete</em></span>.
If you need to disable IXFR to a particular server or
servers, see
the information on the <span><strong class="command">provide-ixfr</strong></span> option
in <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
Usage&#8221;</a>.
See also
<a href="Bv9ARM.ch04.html#incremental_zone_transfers" title="Incremental Zone Transfers (IXFR)">the section called &#8220;Incremental Zone Transfers (IXFR)&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">provide-ixfr</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">provide-ixfr</strong></span> in
<a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">request-ixfr</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">request-ixfr</strong></span> in
<a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">request-expire</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">request-expire</strong></span> in
<a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">treat-cr-as-space</strong></span></span></dt>
<dd><p>
This option was used in <acronym class="acronym">BIND</acronym>
8 to make
the server treat carriage return ("<span><strong class="command">\r</strong></span>") characters the same way
as a space or tab character,
to facilitate loading of zone files on a UNIX system that
were generated
on an NT or DOS machine. In <acronym class="acronym">BIND</acronym> 9, both UNIX "<span><strong class="command">\n</strong></span>"
and NT/DOS "<span><strong class="command">\r\n</strong></span>" newlines
are always accepted,
and the option is ignored.
</p></dd>
<dt>
<span class="term"><span><strong class="command">additional-from-auth</strong></span>, </span><span class="term"><span><strong class="command">additional-from-cache</strong></span></span>
</dt>
<dd>
<p>
These options control the behavior of an authoritative
server when
answering queries which have additional data, or when
following CNAME
and DNAME chains.
</p>
<p>
When both of these options are set to <strong class="userinput"><code>yes</code></strong>
(the default) and a
query is being answered from authoritative data (a zone
configured into the server), the additional data section of
the
reply will be filled in using data from other authoritative
zones
and from the cache. In some situations this is undesirable,
such
as when there is concern over the correctness of the cache,
or
in servers where slave zones may be added and modified by
untrusted third parties. Also, avoiding
the search for this additional data will speed up server
operations
at the possible expense of additional queries to resolve
what would
otherwise be provided in the additional section.
</p>
<p>
For example, if a query asks for an MX record for host <code class="literal">foo.example.com</code>,
and the record found is "<code class="literal">MX 10 mail.example.net</code>", normally the address
records (A and AAAA) for <code class="literal">mail.example.net</code> will be provided as well,
if known, even though they are not in the example.com zone.
Setting these options to <span><strong class="command">no</strong></span>
disables this behavior and makes
the server only search for additional data in the zone it
answers from.
</p>
<p>
These options are intended for use in authoritative-only
servers, or in authoritative-only views. Attempts to set
them to <span><strong class="command">no</strong></span> without also
specifying
<span><strong class="command">recursion no</strong></span> will cause the
server to
ignore the options and log a warning message.
</p>
<p>
Specifying <span><strong class="command">additional-from-cache no</strong></span> actually
disables the use of the cache not only for additional data
lookups
but also when looking up the answer. This is usually the
desired
behavior in an authoritative-only server where the
correctness of
the cached data is an issue.
</p>
<p>
When a name server is non-recursively queried for a name
that is not
below the apex of any served zone, it normally answers with
an
"upwards referral" to the root servers or the servers of
some other
known parent of the query name. Since the data in an
upwards referral
comes from the cache, the server will not be able to provide
upwards
referrals when <span><strong class="command">additional-from-cache no</strong></span>
has been specified. Instead, it will respond to such
queries
with REFUSED. This should not cause any problems since
upwards referrals are not required for the resolution
process.
</p>
</dd>
<dt><span class="term"><span><strong class="command">match-mapped-addresses</strong></span></span></dt>
<dd>
<p>
If <strong class="userinput"><code>yes</code></strong>, then an
IPv4-mapped IPv6 address will match any address match
list entries that match the corresponding IPv4 address.
</p>
<p>
This option was introduced to work around a kernel quirk
in some operating systems that causes IPv4 TCP
connections, such as zone transfers, to be accepted on an
IPv6 socket using mapped addresses. This caused address
match lists designed for IPv4 to fail to match. However,
<span><strong class="command">named</strong></span> now solves this problem
internally. The use of this option is discouraged.
</p>
</dd>
<dt><span class="term"><span><strong class="command">filter-aaaa-on-v4</strong></span></span></dt>
<dd>
<p>
This option is only available when
<acronym class="acronym">BIND</acronym> 9 is compiled with the
<strong class="userinput"><code>--enable-filter-aaaa</code></strong> option on the
"configure" command line. It is intended to help the
transition from IPv4 to IPv6 by not giving IPv6 addresses
to DNS clients unless they have connections to the IPv6
Internet. This is not recommended unless absolutely
necessary. The default is <strong class="userinput"><code>no</code></strong>.
The <span><strong class="command">filter-aaaa-on-v4</strong></span> option
may also be specified in <span><strong class="command">view</strong></span> statements
to override the global <span><strong class="command">filter-aaaa-on-v4</strong></span>
option.
</p>
<p>
If <strong class="userinput"><code>yes</code></strong>,
the DNS client is at an IPv4 address, in <span><strong class="command">filter-aaaa</strong></span>,
and if the response does not include DNSSEC signatures,
then all AAAA records are deleted from the response.
This filtering applies to all responses and not only
authoritative responses.
</p>
<p>
If <strong class="userinput"><code>break-dnssec</code></strong>,
then AAAA records are deleted even when DNSSEC is enabled.
As suggested by the name, this makes the response not verify,
because the DNSSEC protocol is designed detect deletions.
</p>
<p>
This mechanism can erroneously cause other servers to
not give AAAA records to their clients.
A recursing server with both IPv6 and IPv4 network connections
that queries an authoritative server using this mechanism
via IPv4 will be denied AAAA records even if its client is
using IPv6.
</p>
<p>
This mechanism is applied to authoritative as well as
non-authoritative records.
A client using IPv4 that is not allowed recursion can
erroneously be given AAAA records because the server is not
allowed to check for A records.
</p>
<p>
Some AAAA records are given to IPv4 clients in glue records.
IPv4 clients that are servers can then erroneously
answer requests for AAAA records received via IPv4.
</p>
</dd>
<dt><span class="term"><span><strong class="command">filter-aaaa-on-v6</strong></span></span></dt>
<dd><p>
Identical to <span><strong class="command">filter-aaaa-on-v4</strong></span>,
except it filters AAAA responses to queries from IPv6
clients instead of IPv4 clients. To filter all
responses, set both options to <strong class="userinput"><code>yes</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt>
<dd>
<p>
When <strong class="userinput"><code>yes</code></strong> and the server loads a new
version of a master zone from its zone file or receives a
new version of a slave file via zone transfer, it will
compare the new version to the previous one and calculate
a set of differences. The differences are then logged in
the zone's journal file such that the changes can be
transmitted to downstream slaves as an incremental zone
transfer.
</p>
<p>
By allowing incremental zone transfers to be used for
non-dynamic zones, this option saves bandwidth at the
expense of increased CPU and memory consumption at the
master.
In particular, if the new version of a zone is completely
different from the previous one, the set of differences
will be of a size comparable to the combined size of the
old and new zone version, and the server will need to
temporarily allocate memory to hold this complete
difference set.
</p>
<p><span><strong class="command">ixfr-from-differences</strong></span>
also accepts <span><strong class="command">master</strong></span> and
<span><strong class="command">slave</strong></span> at the view and options
levels which causes
<span><strong class="command">ixfr-from-differences</strong></span> to be enabled for
all <span><strong class="command">master</strong></span> or
<span><strong class="command">slave</strong></span> zones respectively.
It is off by default.
</p>
</dd>
<dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt>
<dd><p>
This should be set when you have multiple masters for a zone
and the
addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, <span><strong class="command">named</strong></span> will
not log
when the serial number on the master is less than what <span><strong class="command">named</strong></span>
currently
has. The default is <strong class="userinput"><code>no</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-enable</strong></span></span></dt>
<dd><p>
Enable DNSSEC support in <span><strong class="command">named</strong></span>. Unless set to <strong class="userinput"><code>yes</code></strong>,
<span><strong class="command">named</strong></span> behaves as if it does not support DNSSEC.
The default is <strong class="userinput"><code>yes</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-validation</strong></span></span></dt>
<dd><p>
Enable DNSSEC validation in <span><strong class="command">named</strong></span>.
Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
set to <strong class="userinput"><code>yes</code></strong> to be effective.
If set to <strong class="userinput"><code>no</code></strong>, DNSSEC validation
is disabled. If set to <strong class="userinput"><code>auto</code></strong>,
DNSSEC validation is enabled, and a default
trust-anchor for the DNS root zone is used. If set to
<strong class="userinput"><code>yes</code></strong>, DNSSEC validation is enabled,
but a trust anchor must be manually configured using
a <span><strong class="command">trusted-keys</strong></span> or
<span><strong class="command">managed-keys</strong></span> statement. The default
is <strong class="userinput"><code>yes</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-accept-expired</strong></span></span></dt>
<dd><p>
Accept expired signatures when verifying DNSSEC signatures.
The default is <strong class="userinput"><code>no</code></strong>.
Setting this option to <strong class="userinput"><code>yes</code></strong>
leaves <span><strong class="command">named</strong></span> vulnerable to
replay attacks.
</p></dd>
<dt><span class="term"><span><strong class="command">querylog</strong></span></span></dt>
<dd><p>
Specify whether query logging should be started when <span><strong class="command">named</strong></span>
starts.
If <span><strong class="command">querylog</strong></span> is not specified,
then the query logging
is determined by the presence of the logging category <span><strong class="command">queries</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt>
<dd>
<p>
This option is used to restrict the character set and syntax
of
certain domain names in master files and/or DNS responses
received
from the network. The default varies according to usage
area. For
<span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>.
For <span><strong class="command">slave</strong></span> zones the default
is <span><strong class="command">warn</strong></span>.
For answers received from the network (<span><strong class="command">response</strong></span>)
the default is <span><strong class="command">ignore</strong></span>.
</p>
<p>
The rules for legal hostnames and mail domains are derived
from RFC 952 and RFC 821 as modified by RFC 1123.
</p>
<p><span><strong class="command">check-names</strong></span>
applies to the owner names of A, AAAA and MX records.
It also applies to the domain names in the RDATA of NS, SOA,
MX, and SRV records.
It also applies to the RDATA of PTR records where the owner
name indicated that it is a reverse lookup of a hostname
(the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT).
</p>
</dd>
<dt><span class="term"><span><strong class="command">check-dup-records</strong></span></span></dt>
<dd><p>
Check master zones for records that are treated as different
by DNSSEC but are semantically equal in plain DNS. The
default is to <span><strong class="command">warn</strong></span>. Other possible
values are <span><strong class="command">fail</strong></span> and
<span><strong class="command">ignore</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt>
<dd><p>
Check whether the MX record appears to refer to a IP address.
The default is to <span><strong class="command">warn</strong></span>. Other possible
values are <span><strong class="command">fail</strong></span> and
<span><strong class="command">ignore</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt>
<dd><p>
This option is used to check for non-terminal wildcards.
The use of non-terminal wildcards is almost always as a
result of a failure
to understand the wildcard matching algorithm (RFC 1034).
This option
affects master zones. The default (<span><strong class="command">yes</strong></span>) is to check
for non-terminal wildcards and issue a warning.
</p></dd>
<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt>
<dd>
<p>
Perform post load zone integrity checks on master
zones. This checks that MX and SRV records refer
to address (A or AAAA) records and that glue
address records exist for delegated zones. For
MX and SRV records only in-zone hostnames are
checked (for out-of-zone hostnames use
<span><strong class="command">named-checkzone</strong></span>).
For NS records only names below top of zone are
checked (for out-of-zone names and glue consistency
checks use <span><strong class="command">named-checkzone</strong></span>).
The default is <span><strong class="command">yes</strong></span>.
</p>
<p>
The use of the SPF record for publishing Sender
Policy Framework is deprecated as the migration
from using TXT records to SPF records was abandoned.
Enabling this option also checks that a TXT Sender
Policy Framework record exists (starts with "v=spf1")
if there is an SPF record. Warnings are emitted if the
TXT record does not exist and can be suppressed with
<span><strong class="command">check-spf</strong></span>.
</p>
</dd>
<dt><span class="term"><span><strong class="command">check-mx-cname</strong></span></span></dt>
<dd><p>
If <span><strong class="command">check-integrity</strong></span> is set then
fail, warn or ignore MX records that refer
to CNAMES. The default is to <span><strong class="command">warn</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-srv-cname</strong></span></span></dt>
<dd><p>
If <span><strong class="command">check-integrity</strong></span> is set then
fail, warn or ignore SRV records that refer
to CNAMES. The default is to <span><strong class="command">warn</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt>
<dd><p>
When performing integrity checks, also check that
sibling glue exists. The default is <span><strong class="command">yes</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-spf</strong></span></span></dt>
<dd><p>
If <span><strong class="command">check-integrity</strong></span> is set then
check that there is a TXT Sender Policy Framework
record present (starts with "v=spf1") if there is an
SPF record present. The default is
<span><strong class="command">warn</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt>
<dd><p>
When returning authoritative negative responses to
SOA queries set the TTL of the SOA record returned in
the authority section to zero.
The default is <span><strong class="command">yes</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">zero-no-soa-ttl-cache</strong></span></span></dt>
<dd><p>
When caching a negative response to a SOA query
set the TTL to zero.
The default is <span><strong class="command">no</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt>
<dd>
<p>
When set to the default value of <code class="literal">yes</code>,
check the KSK bit in each key to determine how the key
should be used when generating RRSIGs for a secure zone.
</p>
<p>
Ordinarily, zone-signing keys (that is, keys without the
KSK bit set) are used to sign the entire zone, while
key-signing keys (keys with the KSK bit set) are only
used to sign the DNSKEY RRset at the zone apex.
However, if this option is set to <code class="literal">no</code>,
then the KSK bit is ignored; KSKs are treated as if they
were ZSKs and are used to sign the entire zone. This is
similar to the <span><strong class="command">dnssec-signzone -z</strong></span>
command line option.
</p>
<p>
When this option is set to <code class="literal">yes</code>, there
must be at least two active keys for every algorithm
represented in the DNSKEY RRset: at least one KSK and one
ZSK per algorithm. If there is any algorithm for which
this requirement is not met, this option will be ignored
for that algorithm.
</p>
</dd>
<dt><span class="term"><span><strong class="command">dnssec-dnskey-kskonly</strong></span></span></dt>
<dd>
<p>
When this option and <span><strong class="command">update-check-ksk</strong></span>
are both set to <code class="literal">yes</code>, only key-signing
keys (that is, keys with the KSK bit set) will be used
to sign the DNSKEY RRset at the zone apex. Zone-signing
keys (keys without the KSK bit set) will be used to sign
the remainder of the zone, but not the DNSKEY RRset.
This is similar to the
<span><strong class="command">dnssec-signzone -x</strong></span> command line option.
</p>
<p>
The default is <span><strong class="command">no</strong></span>. If
<span><strong class="command">update-check-ksk</strong></span> is set to
<code class="literal">no</code>, this option is ignored.
</p>
</dd>
<dt><span class="term"><span><strong class="command">dnssec-loadkeys-interval</strong></span></span></dt>
<dd><p>
When a zone is configured with <span><strong class="command">auto-dnssec
maintain;</strong></span> its key repository must be checked
periodically to see if any new keys have been added
or any existing keys' timing metadata has been updated
(see <a href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
<a href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The
<span><strong class="command">dnssec-loadkeys-interval</strong></span> option
sets the frequency of automatic repository checks, in
minutes. The default is <code class="literal">60</code> (1 hour),
the minimum is <code class="literal">1</code> (1 minute), and the
maximum is <code class="literal">1440</code> (24 hours); any higher
value is silently reduced.
</p></dd>
<dt><span class="term"><span><strong class="command">try-tcp-refresh</strong></span></span></dt>
<dd><p>
Try to refresh the zone using TCP if UDP queries fail.
For BIND 8 compatibility, the default is
<span><strong class="command">yes</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-secure-to-insecure</strong></span></span></dt>
<dd>
<p>
Allow a dynamic zone to transition from secure to
insecure (i.e., signed to unsigned) by deleting all
of the DNSKEY records. The default is <span><strong class="command">no</strong></span>.
If set to <span><strong class="command">yes</strong></span>, and if the DNSKEY RRset
at the zone apex is deleted, all RRSIG and NSEC records
will be removed from the zone as well.
</p>
<p>
If the zone uses NSEC3, then it is also necessary to
delete the NSEC3PARAM RRset from the zone apex; this will
cause the removal of all corresponding NSEC3 records.
(It is expected that this requirement will be eliminated
in a future release.)
</p>
<p>
Note that if a zone has been configured with
<span><strong class="command">auto-dnssec maintain</strong></span> and the
private keys remain accessible in the key repository,
then the zone will be automatically signed again the
next time <span><strong class="command">named</strong></span> is started.
</p>
</dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2584397"></a>Forwarding</h4></div></div></div>
<p>
The forwarding facility can be used to create a large site-wide
cache on a few servers, reducing traffic over links to external
name servers. It can also be used to allow queries by servers that
do not have direct access to the Internet, but wish to look up
exterior
names anyway. Forwarding occurs only on those queries for which
the server is not authoritative and does not have the answer in
its cache.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">forward</strong></span></span></dt>
<dd><p>
This option is only meaningful if the
forwarders list is not empty. A value of <code class="varname">first</code>,
the default, causes the server to query the forwarders
first &#8212; and
if that doesn't answer the question, the server will then
look for
the answer itself. If <code class="varname">only</code> is
specified, the
server will only query the forwarders.
</p></dd>
<dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt>
<dd><p>
Specifies the IP addresses to be used
for forwarding. The default is the empty list (no
forwarding).
</p></dd>
</dl></div>
<p>
Forwarding can also be configured on a per-domain basis, allowing
for the global forwarding options to be overridden in a variety
of ways. You can set particular domains to use different
forwarders,
or have a different <span><strong class="command">forward only/first</strong></span> behavior,
or not forward at all, see <a href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone
Statement Grammar">the section called &#8220;<span><strong class="command">zone</strong></span>
Statement Grammar&#8221;</a>.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2584524"></a>Dual-stack Servers</h4></div></div></div>
<p>
Dual-stack servers are used as servers of last resort to work
around
problems in reachability due the lack of support for either IPv4
or IPv6
on the host machine.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">dual-stack-servers</strong></span></span></dt>
<dd><p>
Specifies host names or addresses of machines with access to
both IPv4 and IPv6 transports. If a hostname is used, the
server must be able
to resolve the name using only the transport it has. If the
machine is dual
stacked, then the <span><strong class="command">dual-stack-servers</strong></span> have no effect unless
access to a transport has been disabled on the command line
(e.g. <span><strong class="command">named -4</strong></span>).
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="access_control"></a>Access Control</h4></div></div></div>
<p>
Access to the server can be restricted based on the IP address
of the requesting system. See <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called &#8220;Address Match Lists&#8221;</a> for
details on how to specify IP address lists.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to
notify this server, a slave, of zone changes in addition
to the zone masters.
<span><strong class="command">allow-notify</strong></span> may also be
specified in the
<span><strong class="command">zone</strong></span> statement, in which case
it overrides the
<span><strong class="command">options allow-notify</strong></span>
statement. It is only meaningful
for a slave zone. If not specified, the default is to
process notify messages
only from a zone's master.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt>
<dd>
<p>
Specifies which hosts are allowed to ask ordinary
DNS questions. <span><strong class="command">allow-query</strong></span> may
also be specified in the <span><strong class="command">zone</strong></span>
statement, in which case it overrides the
<span><strong class="command">options allow-query</strong></span> statement.
If not specified, the default is to allow queries
from all hosts.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
<span><strong class="command">allow-query-cache</strong></span> is now
used to specify access to the cache.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">allow-query-on</strong></span></span></dt>
<dd>
<p>
Specifies which local addresses can accept ordinary
DNS questions. This makes it possible, for instance,
to allow queries on internal-facing interfaces but
disallow them on external-facing ones, without
necessarily knowing the internal network's addresses.
</p>
<p>
Note that <span><strong class="command">allow-query-on</strong></span> is only
checked for queries that are permitted by
<span><strong class="command">allow-query</strong></span>. A query must be
allowed by both ACLs, or it will be refused.
</p>
<p>
<span><strong class="command">allow-query-on</strong></span> may
also be specified in the <span><strong class="command">zone</strong></span>
statement, in which case it overrides the
<span><strong class="command">options allow-query-on</strong></span> statement.
</p>
<p>
If not specified, the default is to allow queries
on all addresses.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
<span><strong class="command">allow-query-cache</strong></span> is
used to specify access to the cache.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">allow-query-cache</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to get answers
from the cache. If <span><strong class="command">allow-query-cache</strong></span>
is not set then <span><strong class="command">allow-recursion</strong></span>
is used if set, otherwise <span><strong class="command">allow-query</strong></span>
is used if set unless <span><strong class="command">recursion no;</strong></span> is
set in which case <span><strong class="command">none;</strong></span> is used,
otherwise the default (<span><strong class="command">localnets;</strong></span>
<span><strong class="command">localhost;</strong></span>) is used.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-query-cache-on</strong></span></span></dt>
<dd><p>
Specifies which local addresses can give answers
from the cache. If not specified, the default is
to allow cache queries on any address,
<span><strong class="command">localnets</strong></span> and
<span><strong class="command">localhost</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-recursion</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to make recursive
queries through this server. If
<span><strong class="command">allow-recursion</strong></span> is not set
then <span><strong class="command">allow-query-cache</strong></span> is
used if set, otherwise <span><strong class="command">allow-query</strong></span>
is used if set, otherwise the default
(<span><strong class="command">localnets;</strong></span>
<span><strong class="command">localhost;</strong></span>) is used.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-recursion-on</strong></span></span></dt>
<dd><p>
Specifies which local addresses can accept recursive
queries. If not specified, the default is to allow
recursive queries on all addresses.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to
submit Dynamic DNS updates for master zones. The default is
to deny
updates from all hosts. Note that allowing updates based
on the requestor's IP address is insecure; see
<a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called &#8220;Dynamic Update Security&#8221;</a> for details.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt>
<dd>
<p>
Specifies which hosts are allowed to
submit Dynamic DNS updates to slave zones to be forwarded to
the
master. The default is <strong class="userinput"><code>{ none; }</code></strong>,
which
means that no update forwarding will be performed. To
enable
update forwarding, specify
<strong class="userinput"><code>allow-update-forwarding { any; };</code></strong>.
Specifying values other than <strong class="userinput"><code>{ none; }</code></strong> or
<strong class="userinput"><code>{ any; }</code></strong> is usually
counterproductive, since
the responsibility for update access control should rest
with the
master server, not the slaves.
</p>
<p>
Note that enabling the update forwarding feature on a slave
server
may expose master servers relying on insecure IP address
based
access control to attacks; see <a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called &#8220;Dynamic Update Security&#8221;</a>
for more details.
</p>
</dd>
<dt><span class="term"><span><strong class="command">allow-v6-synthesis</strong></span></span></dt>
<dd><p>
This option was introduced for the smooth transition from
AAAA
to A6 and from "nibble labels" to binary labels.
However, since both A6 and binary labels were then
deprecated,
this option was also deprecated.
It is now ignored with some warning messages.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to
receive zone transfers from the server. <span><strong class="command">allow-transfer</strong></span> may
also be specified in the <span><strong class="command">zone</strong></span>
statement, in which
case it overrides the <span><strong class="command">options allow-transfer</strong></span> statement.
If not specified, the default is to allow transfers to all
hosts.
</p></dd>
<dt><span class="term"><span><strong class="command">blackhole</strong></span></span></dt>
<dd><p>
Specifies a list of addresses that the
server will not accept queries from or use to resolve a
query. Queries
from these addresses will not be responded to. The default
is <strong class="userinput"><code>none</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">filter-aaaa</strong></span></span></dt>
<dd><p>
Specifies a list of addresses to which
<span><strong class="command">filter-aaaa-on-v4</strong></span>
is applies. The default is <strong class="userinput"><code>any</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">keep-response-order</strong></span></span></dt>
<dd><p>
Specifies a list of addresses to which the server
will send responses to TCP queries in the same order
in which they were received. This disables the
processing of TCP queries in parallel. The default
is <strong class="userinput"><code>none</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">no-case-compress</strong></span></span></dt>
<dd>
<p>
Specifies a list of addresses which require responses
to use case-insensitive compression. This ACL can be
used when <span><strong class="command">named</strong></span> needs to work with
clients that do not comply with the requirement in RFC
1034 to use case-insensitive name comparisons when
checking for matching domain names.
</p>
<p>
If left undefined, the ACL defaults to
<span><strong class="command">none</strong></span>: case-insensitive compression
will be used for all clients. If the ACL is defined and
matches a client, then case will be ignored when
compressing domain names in DNS responses sent to that
client.
</p>
<p>
This can result in slightly smaller responses: if
a response contains the names "example.com" and
"example.COM", case-insensitive compression would treat
the second one as a duplicate. It also ensures
that the case of the query name exactly matches the
case of the owner names of returned records, rather
than matching the case of the records entered in
the zone file. This allows responses to exactly
match the query, which is required by some clients
due to incorrect use of case-sensitive comparisons.
</p>
<p>
Case-insensitive compression is <span class="emphasis"><em>always</em></span>
used in AXFR and IXFR responses, regardless of whether
the client matches this ACL.
</p>
<p>
There are circumstances in which <span><strong class="command">named</strong></span>
will not preserve the case of owner names of records:
if a zone file defines records of different types with
the same name, but the capitalization of the name is
different (e.g., "www.example.com/A" and
"WWW.EXAMPLE.COM/AAAA"), then all responses for that
name will use the <span class="emphasis"><em>first</em></span> version
of the name that was used in the zone file. This
limitation may be addressed in a future release. However,
domain names specified in the rdata of resource records
(i.e., records of type NS, MX, CNAME, etc) will always
have their case preserved unless the client matches this
ACL.
</p>
</dd>
<dt><span class="term"><span><strong class="command">resolver-query-timeout</strong></span></span></dt>
<dd><p>
The amount of time the resolver will spend attempting
to resolve a recursive query before failing. The default
and minimum is <code class="literal">10</code> and the maximum is
<code class="literal">30</code>. Setting it to <code class="literal">0</code>
will result in the default being used.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2585352"></a>Interfaces</h4></div></div></div>
<p>
The interfaces and ports that the server will answer queries
from may be specified using the <span><strong class="command">listen-on</strong></span> option. <span><strong class="command">listen-on</strong></span> takes
an optional port and an <code class="varname">address_match_list</code>
of IPv4 addresses. (IPv6 addresses are ignored, with a
logged warning.)
The server will listen on all interfaces allowed by the address
match list. If a port is not specified, port 53 will be used.
</p>
<p>
Multiple <span><strong class="command">listen-on</strong></span> statements are
allowed.
For example,
</p>
<pre class="programlisting">listen-on { 5.6.7.8; };
listen-on port 1234 { !1.2.3.4; 1.2/16; };
</pre>
<p>
will enable the name server on port 53 for the IP address
5.6.7.8, and on port 1234 of an address on the machine in net
1.2 that is not 1.2.3.4.
</p>
<p>
If no <span><strong class="command">listen-on</strong></span> is specified, the
server will listen on port 53 on all IPv4 interfaces.
</p>
<p>
The <span><strong class="command">listen-on-v6</strong></span> option is used to
specify the interfaces and the ports on which the server will
listen for incoming queries sent using IPv6. If not specified,
the server will listen on port 53 on all IPv6 interfaces.
</p>
<p>
When </p>
<pre class="programlisting">{ any; }</pre>
<p> is
specified
as the <code class="varname">address_match_list</code> for the
<span><strong class="command">listen-on-v6</strong></span> option,
the server does not bind a separate socket to each IPv6 interface
address as it does for IPv4 if the operating system has enough API
support for IPv6 (specifically if it conforms to RFC 3493 and RFC
3542).
Instead, it listens on the IPv6 wildcard address.
If the system only has incomplete API support for IPv6, however,
the behavior is the same as that for IPv4.
</p>
<p>
A list of particular IPv6 addresses can also be specified, in
which case
the server listens on a separate socket for each specified
address,
regardless of whether the desired API is supported by the system.
IPv4 addresses specified in <span><strong class="command">listen-on-v6</strong></span>
will be ignored, with a logged warning.
</p>
<p>
Multiple <span><strong class="command">listen-on-v6</strong></span> options can
be used.
For example,
</p>
<pre class="programlisting">listen-on-v6 { any; };
listen-on-v6 port 1234 { !2001:db8::/32; any; };
</pre>
<p>
will enable the name server on port 53 for any IPv6 addresses
(with a single wildcard socket),
and on port 1234 of IPv6 addresses that is not in the prefix
2001:db8::/32 (with separate sockets for each matched address.)
</p>
<p>
To make the server not listen on any IPv6 address, use
</p>
<pre class="programlisting">listen-on-v6 { none; };
</pre>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="query_address"></a>Query Address</h4></div></div></div>
<p>
If the server doesn't know the answer to a question, it will
query other name servers. <span><strong class="command">query-source</strong></span> specifies
the address and port used for such queries. For queries sent over
IPv6, there is a separate <span><strong class="command">query-source-v6</strong></span> option.
If <span><strong class="command">address</strong></span> is <span><strong class="command">*</strong></span> (asterisk) or is omitted,
a wildcard IP address (<span><strong class="command">INADDR_ANY</strong></span>)
will be used.
</p>
<p>
If <span><strong class="command">port</strong></span> is <span><strong class="command">*</strong></span> or is omitted,
a random port number from a pre-configured
range is picked up and will be used for each query.
The port range(s) is that specified in
the <span><strong class="command">use-v4-udp-ports</strong></span> (for IPv4)
and <span><strong class="command">use-v6-udp-ports</strong></span> (for IPv6)
options, excluding the ranges specified in
the <span><strong class="command">avoid-v4-udp-ports</strong></span>
and <span><strong class="command">avoid-v6-udp-ports</strong></span> options, respectively.
</p>
<p>
The defaults of the <span><strong class="command">query-source</strong></span> and
<span><strong class="command">query-source-v6</strong></span> options
are:
</p>
<pre class="programlisting">query-source address * port *;
query-source-v6 address * port *;
</pre>
<p>
If <span><strong class="command">use-v4-udp-ports</strong></span> or
<span><strong class="command">use-v6-udp-ports</strong></span> is unspecified,
<span><strong class="command">named</strong></span> will check if the operating
system provides a programming interface to retrieve the
system's default range for ephemeral ports.
If such an interface is available,
<span><strong class="command">named</strong></span> will use the corresponding system
default range; otherwise, it will use its own defaults:
</p>
<pre class="programlisting">use-v4-udp-ports { range 1024 65535; };
use-v6-udp-ports { range 1024 65535; };
</pre>
<p>
Note: make sure the ranges be sufficiently large for
security. A desirable size depends on various parameters,
but we generally recommend it contain at least 16384 ports
(14 bits of entropy).
Note also that the system's default range when used may be
too small for this purpose, and that the range may even be
changed while <span><strong class="command">named</strong></span> is running; the new
range will automatically be applied when <span><strong class="command">named</strong></span>
is reloaded.
It is encouraged to
configure <span><strong class="command">use-v4-udp-ports</strong></span> and
<span><strong class="command">use-v6-udp-ports</strong></span> explicitly so that the
ranges are sufficiently large and are reasonably
independent from the ranges used by other applications.
</p>
<p>
Note: the operational configuration
where <span><strong class="command">named</strong></span> runs may prohibit the use
of some ports. For example, UNIX systems will not allow
<span><strong class="command">named</strong></span> running without a root privilege
to use ports less than 1024.
If such ports are included in the specified (or detected)
set of query ports, the corresponding query attempts will
fail, resulting in resolution failures or delay.
It is therefore important to configure the set of ports
that can be safely used in the expected operational environment.
</p>
<p>
The defaults of the <span><strong class="command">avoid-v4-udp-ports</strong></span> and
<span><strong class="command">avoid-v6-udp-ports</strong></span> options
are:
</p>
<pre class="programlisting">avoid-v4-udp-ports {};
avoid-v6-udp-ports {};
</pre>
<p>
Note: BIND 9.5.0 introduced
the <span><strong class="command">use-queryport-pool</strong></span>
option to support a pool of such random ports, but this
option is now obsolete because reusing the same ports in
the pool may not be sufficiently secure.
For the same reason, it is generally strongly discouraged to
specify a particular port for the
<span><strong class="command">query-source</strong></span> or
<span><strong class="command">query-source-v6</strong></span> options;
it implicitly disables the use of randomized port numbers.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">use-queryport-pool</strong></span></span></dt>
<dd><p>
This option is obsolete.
</p></dd>
<dt><span class="term"><span><strong class="command">queryport-pool-ports</strong></span></span></dt>
<dd><p>
This option is obsolete.
</p></dd>
<dt><span class="term"><span><strong class="command">queryport-pool-updateinterval</strong></span></span></dt>
<dd><p>
This option is obsolete.
</p></dd>
</dl></div>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
The address specified in the <span><strong class="command">query-source</strong></span> option
is used for both UDP and TCP queries, but the port applies only
to UDP queries. TCP queries always use a random
unprivileged port.
</p>
</div>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Solaris 2.5.1 and earlier does not support setting the source
address for TCP sockets.
</p>
</div>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
See also <span><strong class="command">transfer-source</strong></span> and
<span><strong class="command">notify-source</strong></span>.
</p>
</div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="zone_transfers"></a>Zone Transfers</h4></div></div></div>
<p>
<acronym class="acronym">BIND</acronym> has mechanisms in place to
facilitate zone transfers
and set limits on the amount of load that transfers place on the
system. The following options apply to zone transfers.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">also-notify</strong></span></span></dt>
<dd>
<p>
Defines a global list of IP addresses of name servers
that are also sent NOTIFY messages whenever a fresh copy of
the
zone is loaded, in addition to the servers listed in the
zone's NS records.
This helps to ensure that copies of the zones will
quickly converge on stealth servers.
Optionally, a port may be specified with each
<span><strong class="command">also-notify</strong></span> address to send
the notify messages to a port other than the
default of 53.
An optional TSIG key can also be specified with each
address to cause the notify messages to be signed; this
can be useful when sending notifies to multiple views.
In place of explicit addresses, one or more named
<span><strong class="command">masters</strong></span> lists can be used.
</p>
<p>
If an <span><strong class="command">also-notify</strong></span> list
is given in a <span><strong class="command">zone</strong></span> statement,
it will override
the <span><strong class="command">options also-notify</strong></span>
statement. When a <span><strong class="command">zone notify</strong></span>
statement
is set to <span><strong class="command">no</strong></span>, the IP
addresses in the global <span><strong class="command">also-notify</strong></span> list will
not be sent NOTIFY messages for that zone. The default is
the empty
list (no global notification list).
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-transfer-time-in</strong></span></span></dt>
<dd><p>
Inbound zone transfers running longer than
this many minutes will be terminated. The default is 120
minutes
(2 hours). The maximum value is 28 days (40320 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-idle-in</strong></span></span></dt>
<dd><p>
Inbound zone transfers making no progress
in this many minutes will be terminated. The default is 60
minutes
(1 hour). The maximum value is 28 days (40320 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-time-out</strong></span></span></dt>
<dd><p>
Outbound zone transfers running longer than
this many minutes will be terminated. The default is 120
minutes
(2 hours). The maximum value is 28 days (40320 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-idle-out</strong></span></span></dt>
<dd><p>
Outbound zone transfers making no progress
in this many minutes will be terminated. The default is 60
minutes (1
hour). The maximum value is 28 days (40320 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">notify-rate</strong></span></span></dt>
<dd><p>
The rate at which NOTIFY requests will be sent
during normal zone maintenance operations. (NOTIFY
requests due to initial zone loading are subject
to a separate rate limit; see below.) The default is
20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
</p></dd>
<dt><span class="term"><span><strong class="command">startup-notify-rate</strong></span></span></dt>
<dd><p>
The rate at which NOTIFY requests will be sent
when the name server is first starting up, or when
zones have been newly added to the nameserver.
The default is 20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
</p></dd>
<dt><span class="term"><span><strong class="command">serial-query-rate</strong></span></span></dt>
<dd><p>
Slave servers will periodically query master
servers to find out if zone serial numbers have
changed. Each such query uses a minute amount of
the slave server's network bandwidth. To limit
the amount of bandwidth used, BIND 9 limits the
rate at which queries are sent. The value of the
<span><strong class="command">serial-query-rate</strong></span> option, an
integer, is the maximum number of queries sent
per second. The default is 20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
</p></dd>
<dt><span class="term"><span><strong class="command">serial-queries</strong></span></span></dt>
<dd><p>
In BIND 8, the <span><strong class="command">serial-queries</strong></span>
option
set the maximum number of concurrent serial number queries
allowed to be outstanding at any given time.
BIND 9 does not limit the number of outstanding
serial queries and ignores the <span><strong class="command">serial-queries</strong></span> option.
Instead, it limits the rate at which the queries are sent
as defined using the <span><strong class="command">serial-query-rate</strong></span> option.
</p></dd>
<dt><span class="term"><span><strong class="command">transfer-format</strong></span></span></dt>
<dd><p>
Zone transfers can be sent using two different formats,
<span><strong class="command">one-answer</strong></span> and
<span><strong class="command">many-answers</strong></span>.
The <span><strong class="command">transfer-format</strong></span> option is used
on the master server to determine which format it sends.
<span><strong class="command">one-answer</strong></span> uses one DNS message per
resource record transferred.
<span><strong class="command">many-answers</strong></span> packs as many resource
records as possible into a message.
<span><strong class="command">many-answers</strong></span> is more efficient, but is
only supported by relatively new slave servers,
such as <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym>
8.x and <acronym class="acronym">BIND</acronym> 4.9.5 onwards.
The <span><strong class="command">many-answers</strong></span> format is also supported by
recent Microsoft Windows nameservers.
The default is <span><strong class="command">many-answers</strong></span>.
<span><strong class="command">transfer-format</strong></span> may be overridden on a
per-server basis by using the <span><strong class="command">server</strong></span>
statement.
</p></dd>
<dt><span class="term"><span><strong class="command">transfers-in</strong></span></span></dt>
<dd><p>
The maximum number of inbound zone transfers
that can be running concurrently. The default value is <code class="literal">10</code>.
Increasing <span><strong class="command">transfers-in</strong></span> may
speed up the convergence
of slave zones, but it also may increase the load on the
local system.
</p></dd>
<dt><span class="term"><span><strong class="command">transfers-out</strong></span></span></dt>
<dd><p>
The maximum number of outbound zone transfers
that can be running concurrently. Zone transfer requests in
excess
of the limit will be refused. The default value is <code class="literal">10</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">transfers-per-ns</strong></span></span></dt>
<dd><p>
The maximum number of inbound zone transfers
that can be concurrently transferring from a given remote
name server.
The default value is <code class="literal">2</code>.
Increasing <span><strong class="command">transfers-per-ns</strong></span>
may
speed up the convergence of slave zones, but it also may
increase
the load on the remote name server. <span><strong class="command">transfers-per-ns</strong></span> may
be overridden on a per-server basis by using the <span><strong class="command">transfers</strong></span> phrase
of the <span><strong class="command">server</strong></span> statement.
</p></dd>
<dt><span class="term"><span><strong class="command">transfer-source</strong></span></span></dt>
<dd>
<p><span><strong class="command">transfer-source</strong></span>
determines which local address will be bound to IPv4
TCP connections used to fetch zones transferred
inbound by the server. It also determines the
source IPv4 address, and optionally the UDP port,
used for the refresh queries and forwarded dynamic
updates. If not set, it defaults to a system
controlled value which will usually be the address
of the interface "closest to" the remote end. This
address must appear in the remote end's
<span><strong class="command">allow-transfer</strong></span> option for the
zone being transferred, if one is specified. This
statement sets the
<span><strong class="command">transfer-source</strong></span> for all zones,
but can be overridden on a per-view or per-zone
basis by including a
<span><strong class="command">transfer-source</strong></span> statement within
the <span><strong class="command">view</strong></span> or
<span><strong class="command">zone</strong></span> block in the configuration
file.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Solaris 2.5.1 and earlier does not support setting the
source address for TCP sockets.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">transfer-source-v6</strong></span></span></dt>
<dd><p>
The same as <span><strong class="command">transfer-source</strong></span>,
except zone transfers are performed using IPv6.
</p></dd>
<dt><span class="term"><span><strong class="command">alt-transfer-source</strong></span></span></dt>
<dd>
<p>
An alternate transfer source if the one listed in
<span><strong class="command">transfer-source</strong></span> fails and
<span><strong class="command">use-alt-transfer-source</strong></span> is
set.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
If you do not wish the alternate transfer source
to be used, you should set
<span><strong class="command">use-alt-transfer-source</strong></span>
appropriately and you should not depend upon
getting an answer back to the first refresh
query.
</div>
</dd>
<dt><span class="term"><span><strong class="command">alt-transfer-source-v6</strong></span></span></dt>
<dd><p>
An alternate transfer source if the one listed in
<span><strong class="command">transfer-source-v6</strong></span> fails and
<span><strong class="command">use-alt-transfer-source</strong></span> is
set.
</p></dd>
<dt><span class="term"><span><strong class="command">use-alt-transfer-source</strong></span></span></dt>
<dd><p>
Use the alternate transfer sources or not. If views are
specified this defaults to <span><strong class="command">no</strong></span>
otherwise it defaults to
<span><strong class="command">yes</strong></span> (for BIND 8
compatibility).
</p></dd>
<dt><span class="term"><span><strong class="command">notify-source</strong></span></span></dt>
<dd>
<p><span><strong class="command">notify-source</strong></span>
determines which local source address, and
optionally UDP port, will be used to send NOTIFY
messages. This address must appear in the slave
server's <span><strong class="command">masters</strong></span> zone clause or
in an <span><strong class="command">allow-notify</strong></span> clause. This
statement sets the <span><strong class="command">notify-source</strong></span>
for all zones, but can be overridden on a per-zone or
per-view basis by including a
<span><strong class="command">notify-source</strong></span> statement within
the <span><strong class="command">zone</strong></span> or
<span><strong class="command">view</strong></span> block in the configuration
file.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Solaris 2.5.1 and earlier does not support setting the
source address for TCP sockets.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">notify-source-v6</strong></span></span></dt>
<dd><p>
Like <span><strong class="command">notify-source</strong></span>,
but applies to notify messages sent to IPv6 addresses.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2586780"></a>UDP Port Lists</h4></div></div></div>
<p>
<span><strong class="command">use-v4-udp-ports</strong></span>,
<span><strong class="command">avoid-v4-udp-ports</strong></span>,
<span><strong class="command">use-v6-udp-ports</strong></span>, and
<span><strong class="command">avoid-v6-udp-ports</strong></span>
specify a list of IPv4 and IPv6 UDP ports that will be
used or not used as source ports for UDP messages.
See <a href="Bv9ARM.ch06.html#query_address" title="Query Address">the section called &#8220;Query Address&#8221;</a> about how the
available ports are determined.
For example, with the following configuration
</p>
<pre class="programlisting">
use-v6-udp-ports { range 32768 65535; };
avoid-v6-udp-ports { 40000; range 50000 60000; };
</pre>
<p>
UDP ports of IPv6 messages sent
from <span><strong class="command">named</strong></span> will be in one
of the following ranges: 32768 to 39999, 40001 to 49999,
and 60001 to 65535.
</p>
<p>
<span><strong class="command">avoid-v4-udp-ports</strong></span> and
<span><strong class="command">avoid-v6-udp-ports</strong></span> can be used
to prevent <span><strong class="command">named</strong></span> from choosing as its random source port a
port that is blocked by your firewall or a port that is
used by other applications;
if a query went out with a source port blocked by a
firewall, the
answer would not get by the firewall and the name server would
have to query again.
Note: the desired range can also be represented only with
<span><strong class="command">use-v4-udp-ports</strong></span> and
<span><strong class="command">use-v6-udp-ports</strong></span>, and the
<span><strong class="command">avoid-</strong></span> options are redundant in that
sense; they are provided for backward compatibility and
to possibly simplify the port specification.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2586840"></a>Operating System Resource Limits</h4></div></div></div>
<p>
The server's usage of many system resources can be limited.
Scaled values are allowed when specifying resource limits. For
example, <span><strong class="command">1G</strong></span> can be used instead of
<span><strong class="command">1073741824</strong></span> to specify a limit of
one
gigabyte. <span><strong class="command">unlimited</strong></span> requests
unlimited use, or the
maximum available amount. <span><strong class="command">default</strong></span>
uses the limit
that was in force when the server was started. See the description
of <span><strong class="command">size_spec</strong></span> in <a href="Bv9ARM.ch06.html#configuration_file_elements" title="Configuration File Elements">the section called &#8220;Configuration File Elements&#8221;</a>.
</p>
<p>
The following options set operating system resource limits for
the name server process. Some operating systems don't support
some or
any of the limits. On such systems, a warning will be issued if
the
unsupported limit is used.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">coresize</strong></span></span></dt>
<dd><p>
The maximum size of a core dump. The default
is <code class="literal">default</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">datasize</strong></span></span></dt>
<dd><p>
The maximum amount of data memory the server
may use. The default is <code class="literal">default</code>.
This is a hard limit on server memory usage.
If the server attempts to allocate memory in excess of this
limit, the allocation will fail, which may in turn leave
the server unable to perform DNS service. Therefore,
this option is rarely useful as a way of limiting the
amount of memory used by the server, but it can be used
to raise an operating system data size limit that is
too small by default. If you wish to limit the amount
of memory used by the server, use the
<span><strong class="command">max-cache-size</strong></span> and
<span><strong class="command">recursive-clients</strong></span>
options instead.
</p></dd>
<dt><span class="term"><span><strong class="command">files</strong></span></span></dt>
<dd><p>
The maximum number of files the server
may have open concurrently. The default is <code class="literal">unlimited</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">stacksize</strong></span></span></dt>
<dd><p>
The maximum amount of stack memory the server
may use. The default is <code class="literal">default</code>.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="server_resource_limits"></a>Server Resource Limits</h4></div></div></div>
<p>
The following options set limits on the server's
resource consumption that are enforced internally by the
server rather than the operating system.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">max-ixfr-log-size</strong></span></span></dt>
<dd><p>
This option is obsolete; it is accepted
and ignored for BIND 8 compatibility. The option
<span><strong class="command">max-journal-size</strong></span> performs a
similar function in BIND 9.
</p></dd>
<dt><span class="term"><span><strong class="command">max-journal-size</strong></span></span></dt>
<dd><p>
Sets a maximum size for each journal file
(see <a href="Bv9ARM.ch04.html#journal" title="The journal file">the section called &#8220;The journal file&#8221;</a>). When the journal file
approaches
the specified size, some of the oldest transactions in the
journal
will be automatically removed. The largest permitted
value is 2 gigabytes. The default is
<code class="literal">unlimited</code>, which also
means 2 gigabytes.
This may also be set on a per-zone basis.
</p></dd>
<dt><span class="term"><span><strong class="command">host-statistics-max</strong></span></span></dt>
<dd><p>
In BIND 8, specifies the maximum number of host statistics
entries to be kept.
Not implemented in BIND 9.
</p></dd>
<dt><span class="term"><span><strong class="command">recursive-clients</strong></span></span></dt>
<dd><p>
The maximum number of simultaneous recursive lookups
the server will perform on behalf of clients. The default
is
<code class="literal">1000</code>. Because each recursing
client uses a fair
bit of memory, on the order of 20 kilobytes, the value of
the
<span><strong class="command">recursive-clients</strong></span> option may
have to be decreased
on hosts with limited memory.
</p></dd>
<dt><span class="term"><span><strong class="command">tcp-clients</strong></span></span></dt>
<dd><p>
The maximum number of simultaneous client TCP
connections that the server will accept.
The default is <code class="literal">100</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">reserved-sockets</strong></span></span></dt>
<dd>
<p>
The number of file descriptors reserved for TCP, stdio,
etc. This needs to be big enough to cover the number of
interfaces <span><strong class="command">named</strong></span> listens on, <span><strong class="command">tcp-clients</strong></span> as well as
to provide room for outgoing TCP queries and incoming zone
transfers. The default is <code class="literal">512</code>.
The minimum value is <code class="literal">128</code> and the
maximum value is <code class="literal">128</code> less than
maxsockets (-S). This option may be removed in the future.
</p>
<p>
This option has little effect on Windows.
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-cache-size</strong></span></span></dt>
<dd><p>
The maximum amount of memory to use for the
server's cache, in bytes.
When the amount of data in the cache
reaches this limit, the server will cause records to
expire prematurely based on an LRU based strategy so
that the limit is not exceeded.
The keyword <strong class="userinput"><code>unlimited</code></strong>,
or the value 0, will place no limit on cache size;
records will be purged from the cache only when their
TTLs expire.
Any positive values less than 2MB will be ignored
and reset to 2MB.
In a server with multiple views, the limit applies
separately to the cache of each view.
The default is <strong class="userinput"><code>unlimited</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">tcp-listen-queue</strong></span></span></dt>
<dd><p>
The listen queue depth. The default and minimum is 10.
If the kernel supports the accept filter "dataready" this
also controls how
many TCP connections that will be queued in kernel space
waiting for
some data before being passed to accept. Nonzero values
less than 10 will be silently raised. A value of 0 may also
be used; on most platforms this sets the listen queue
length to a system-defined default value.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2587197"></a>Periodic Task Intervals</h4></div></div></div>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">cleaning-interval</strong></span></span></dt>
<dd><p>
This interval is effectively obsolete. Previously,
the server would remove expired resource records
from the cache every <span><strong class="command">cleaning-interval</strong></span> minutes.
<acronym class="acronym">BIND</acronym> 9 now manages cache
memory in a more sophisticated manner and does not
rely on the periodic cleaning any more.
Specifying this option therefore has no effect on
the server's behavior.
</p></dd>
<dt><span class="term"><span><strong class="command">heartbeat-interval</strong></span></span></dt>
<dd><p>
The server will perform zone maintenance tasks
for all zones marked as <span><strong class="command">dialup</strong></span> whenever this
interval expires. The default is 60 minutes. Reasonable
values are up
to 1 day (1440 minutes). The maximum value is 28 days
(40320 minutes).
If set to 0, no zone maintenance for these zones will occur.
</p></dd>
<dt><span class="term"><span><strong class="command">interface-interval</strong></span></span></dt>
<dd><p>
The server will scan the network interface list
every <span><strong class="command">interface-interval</strong></span>
minutes. The default
is 60 minutes. The maximum value is 28 days (40320 minutes).
If set to 0, interface scanning will only occur when
the configuration file is loaded. After the scan, the
server will
begin listening for queries on any newly discovered
interfaces (provided they are allowed by the
<span><strong class="command">listen-on</strong></span> configuration), and
will
stop listening on interfaces that have gone away.
</p></dd>
<dt><span class="term"><span><strong class="command">statistics-interval</strong></span></span></dt>
<dd>
<p>
Name server statistics will be logged
every <span><strong class="command">statistics-interval</strong></span>
minutes. The default is
60. The maximum value is 28 days (40320 minutes).
If set to 0, no statistics will be logged.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Not yet implemented in
<acronym class="acronym">BIND</acronym> 9.
</p>
</div>
</dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="topology"></a>Topology</h4></div></div></div>
<p>
All other things being equal, when the server chooses a name
server
to query from a list of name servers, it prefers the one that is
topologically closest to itself. The <span><strong class="command">topology</strong></span> statement
takes an <span><strong class="command">address_match_list</strong></span> and
interprets it
in a special way. Each top-level list element is assigned a
distance.
Non-negated elements get a distance based on their position in the
list, where the closer the match is to the start of the list, the
shorter the distance is between it and the server. A negated match
will be assigned the maximum distance from the server. If there
is no match, the address will get a distance which is further than
any non-negated list element, and closer than any negated element.
For example,
</p>
<pre class="programlisting">topology {
10/8;
!1.2.3/24;
{ 1.2/16; 3/8; };
};</pre>
<p>
will prefer servers on network 10 the most, followed by hosts
on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the
exception of hosts on network 1.2.3 (netmask 255.255.255.0), which
is preferred least of all.
</p>
<p>
The default topology is
</p>
<pre class="programlisting"> topology { localhost; localnets; };
</pre>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
The <span><strong class="command">topology</strong></span> option
is not implemented in <acronym class="acronym">BIND</acronym> 9.
</p>
</div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="the_sortlist_statement"></a>The <span><strong class="command">sortlist</strong></span> Statement</h4></div></div></div>
<p>
The response to a DNS query may consist of multiple resource
records (RRs) forming a resource records set (RRset).
The name server will normally return the
RRs within the RRset in an indeterminate order
(but see the <span><strong class="command">rrset-order</strong></span>
statement in <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called &#8220;RRset Ordering&#8221;</a>).
The client resolver code should rearrange the RRs as appropriate,
that is, using any addresses on the local net in preference to
other addresses.
However, not all resolvers can do this or are correctly
configured.
When a client is using a local server, the sorting can be performed
in the server, based on the client's address. This only requires
configuring the name servers, not all the clients.
</p>
<p>
The <span><strong class="command">sortlist</strong></span> statement (see below)
takes
an <span><strong class="command">address_match_list</strong></span> and
interprets it even
more specifically than the <span><strong class="command">topology</strong></span>
statement
does (<a href="Bv9ARM.ch06.html#topology" title="Topology">the section called &#8220;Topology&#8221;</a>).
Each top level statement in the <span><strong class="command">sortlist</strong></span> must
itself be an explicit <span><strong class="command">address_match_list</strong></span> with
one or two elements. The first element (which may be an IP
address,
an IP prefix, an ACL name or a nested <span><strong class="command">address_match_list</strong></span>)
of each top level list is checked against the source address of
the query until a match is found.
</p>
<p>
Once the source address of the query has been matched, if
the top level statement contains only one element, the actual
primitive
element that matched the source address is used to select the
address
in the response to move to the beginning of the response. If the
statement is a list of two elements, then the second element is
treated the same as the <span><strong class="command">address_match_list</strong></span> in
a <span><strong class="command">topology</strong></span> statement. Each top
level element
is assigned a distance and the address in the response with the
minimum
distance is moved to the beginning of the response.
</p>
<p>
In the following example, any queries received from any of
the addresses of the host itself will get responses preferring
addresses
on any of the locally connected networks. Next most preferred are
addresses
on the 192.168.1/24 network, and after that either the
192.168.2/24
or
192.168.3/24 network with no preference shown between these two
networks. Queries received from a host on the 192.168.1/24 network
will prefer other addresses on that network to the 192.168.2/24
and
192.168.3/24 networks. Queries received from a host on the
192.168.4/24
or the 192.168.5/24 network will only prefer other addresses on
their directly connected networks.
</p>
<pre class="programlisting">sortlist {
// IF the local host
// THEN first fit on the following nets
{ localhost;
{ localnets;
192.168.1/24;
{ 192.168.2/24; 192.168.3/24; }; }; };
// IF on class C 192.168.1 THEN use .1, or .2 or .3
{ 192.168.1/24;
{ 192.168.1/24;
{ 192.168.2/24; 192.168.3/24; }; }; };
// IF on class C 192.168.2 THEN use .2, or .1 or .3
{ 192.168.2/24;
{ 192.168.2/24;
{ 192.168.1/24; 192.168.3/24; }; }; };
// IF on class C 192.168.3 THEN use .3, or .1 or .2
{ 192.168.3/24;
{ 192.168.3/24;
{ 192.168.1/24; 192.168.2/24; }; }; };
// IF .4 or .5 THEN prefer that net
{ { 192.168.4/24; 192.168.5/24; };
};
};</pre>
<p>
The following example will give reasonable behavior for the
local host and hosts on directly connected networks. It is similar
to the behavior of the address sort in <acronym class="acronym">BIND</acronym> 4.9.x. Responses sent
to queries from the local host will favor any of the directly
connected
networks. Responses sent to queries from any other hosts on a
directly
connected network will prefer addresses on that same network.
Responses
to other queries will not be sorted.
</p>
<pre class="programlisting">sortlist {
{ localhost; localnets; };
{ localnets; };
};
</pre>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="rrset_ordering"></a>RRset Ordering</h4></div></div></div>
<p>
When multiple records are returned in an answer it may be
useful to configure the order of the records placed into the
response.
The <span><strong class="command">rrset-order</strong></span> statement permits
configuration
of the ordering of the records in a multiple record response.
See also the <span><strong class="command">sortlist</strong></span> statement,
<a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called &#8220;The <span><strong class="command">sortlist</strong></span> Statement&#8221;</a>.
</p>
<p>
An <span><strong class="command">order_spec</strong></span> is defined as
follows:
</p>
<p>
[<span class="optional">class <em class="replaceable"><code>class_name</code></em></span>]
[<span class="optional">type <em class="replaceable"><code>type_name</code></em></span>]
[<span class="optional">name <em class="replaceable"><code>"domain_name"</code></em></span>]
order <em class="replaceable"><code>ordering</code></em>
</p>
<p>
If no class is specified, the default is <span><strong class="command">ANY</strong></span>.
If no type is specified, the default is <span><strong class="command">ANY</strong></span>.
If no name is specified, the default is "<span><strong class="command">*</strong></span>" (asterisk).
</p>
<p>
The legal values for <span><strong class="command">ordering</strong></span> are:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p><span><strong class="command">fixed</strong></span></p>
</td>
<td>
<p>
Records are returned in the order they
are defined in the zone file.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">random</strong></span></p>
</td>
<td>
<p>
Records are returned in some random order.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">cyclic</strong></span></p>
</td>
<td>
<p>
Records are returned in a cyclic round-robin order.
</p>
<p>
If <acronym class="acronym">BIND</acronym> is configured with the
"--enable-fixed-rrset" option at compile time, then
the initial ordering of the RRset will match the
one specified in the zone file.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
For example:
</p>
<pre class="programlisting">rrset-order {
class IN type A name "host.example.com" order random;
order cyclic;
};
</pre>
<p>
will cause any responses for type A records in class IN that
have "<code class="literal">host.example.com</code>" as a
suffix, to always be returned
in random order. All other records are returned in cyclic order.
</p>
<p>
If multiple <span><strong class="command">rrset-order</strong></span> statements
appear, they are not combined &#8212; the last one applies.
</p>
<p>
By default, all records are returned in random order.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
In this release of <acronym class="acronym">BIND</acronym> 9, the
<span><strong class="command">rrset-order</strong></span> statement does not support
"fixed" ordering by default. Fixed ordering can be enabled
at compile time by specifying "--enable-fixed-rrset" on
the "configure" command line.
</p>
</div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="tuning"></a>Tuning</h4></div></div></div>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">lame-ttl</strong></span></span></dt>
<dd><p>
Sets the number of seconds to cache a
lame server indication. 0 disables caching. (This is
<span class="bold"><strong>NOT</strong></span> recommended.)
The default is <code class="literal">600</code> (10 minutes) and the
maximum value is
<code class="literal">1800</code> (30 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">servfail-ttl</strong></span></span></dt>
<dd>
<p>
Sets the number of seconds to cache a
SERVFAIL response due to DNSSEC validation failure or
other general server failure. If set to
<code class="literal">0</code>, SERVFAIL caching is disabled.
The SERVFAIL cache is not consulted if a query has
the CD (Checking Disabled) bit set; this allows a
query that failed due to DNSSEC validation to be retried
without waiting for the SERVFAIL TTL to expire.
</p>
<p>
The maximum value is <code class="literal">300</code>
(5 minutes); any higher value will be silently
reduced. The default is <code class="literal">10</code>
seconds.
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-ncache-ttl</strong></span></span></dt>
<dd><p>
To reduce network traffic and increase performance,
the server stores negative answers. <span><strong class="command">max-ncache-ttl</strong></span> is
used to set a maximum retention time for these answers in
the server
in seconds. The default
<span><strong class="command">max-ncache-ttl</strong></span> is <code class="literal">10800</code> seconds (3 hours).
<span><strong class="command">max-ncache-ttl</strong></span> cannot exceed
7 days and will
be silently truncated to 7 days if set to a greater value.
</p></dd>
<dt><span class="term"><span><strong class="command">max-cache-ttl</strong></span></span></dt>
<dd><p>
Sets the maximum time for which the server will
cache ordinary (positive) answers. The default is
one week (7 days).
A value of zero may cause all queries to return
SERVFAIL, because of lost caches of intermediate
RRsets (such as NS and glue AAAA/A records) in the
resolution process.
</p></dd>
<dt><span class="term"><span><strong class="command">min-roots</strong></span></span></dt>
<dd>
<p>
The minimum number of root servers that
is required for a request for the root servers to be
accepted. The default
is <strong class="userinput"><code>2</code></strong>.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Not implemented in <acronym class="acronym">BIND</acronym> 9.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">sig-validity-interval</strong></span></span></dt>
<dd>
<p>
Specifies the number of days into the future when
DNSSEC signatures automatically generated as a
result of dynamic updates (<a href="Bv9ARM.ch04.html#dynamic_update" title="Dynamic Update">the section called &#8220;Dynamic Update&#8221;</a>) will expire. There
is an optional second field which specifies how
long before expiry that the signatures will be
regenerated. If not specified, the signatures will
be regenerated at 1/4 of base interval. The second
field is specified in days if the base interval is
greater than 7 days otherwise it is specified in hours.
The default base interval is <code class="literal">30</code> days
giving a re-signing interval of 7 1/2 days. The maximum
values are 10 years (3660 days).
</p>
<p>
The signature inception time is unconditionally
set to one hour before the current time to allow
for a limited amount of clock skew.
</p>
<p>
The <span><strong class="command">sig-validity-interval</strong></span>
should be, at least, several multiples of the SOA
expire interval to allow for reasonable interaction
between the various timer and expiry dates.
</p>
</dd>
<dt><span class="term"><span><strong class="command">sig-signing-nodes</strong></span></span></dt>
<dd><p>
Specify the maximum number of nodes to be
examined in each quantum when signing a zone with
a new DNSKEY. The default is
<code class="literal">100</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-signatures</strong></span></span></dt>
<dd><p>
Specify a threshold number of signatures that
will terminate processing a quantum when signing
a zone with a new DNSKEY. The default is
<code class="literal">10</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-type</strong></span></span></dt>
<dd>
<p>
Specify a private RDATA type to be used when generating
signing state records. The default is
<code class="literal">65534</code>.
</p>
<p>
It is expected that this parameter may be removed
in a future version once there is a standard type.
</p>
<p>
Signing state records are used to internally by
<span><strong class="command">named</strong></span> to track the current state of
a zone-signing process, i.e., whether it is still active
or has been completed. The records can be inspected
using the command
<span><strong class="command">rndc signing -list <em class="replaceable"><code>zone</code></em></strong></span>.
Once <span><strong class="command">named</strong></span> has finished signing
a zone with a particular key, the signing state
record associated with that key can be removed from
the zone by running
<span><strong class="command">rndc signing -clear <em class="replaceable"><code>keyid/algorithm</code></em> <em class="replaceable"><code>zone</code></em></strong></span>.
To clear all of the completed signing state
records for a zone, use
<span><strong class="command">rndc signing -clear all <em class="replaceable"><code>zone</code></em></strong></span>.
</p>
</dd>
<dt>
<span class="term"><span><strong class="command">min-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">max-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">min-retry-time</strong></span>, </span><span class="term"><span><strong class="command">max-retry-time</strong></span></span>
</dt>
<dd>
<p>
These options control the server's behavior on refreshing a
zone
(querying for SOA changes) or retrying failed transfers.
Usually the SOA values for the zone are used, but these
values
are set by the master, giving slave server administrators
little
control over their contents.
</p>
<p>
These options allow the administrator to set a minimum and
maximum
refresh and retry time either per-zone, per-view, or
globally.
These options are valid for slave and stub zones,
and clamp the SOA refresh and retry times to the specified
values.
</p>
<p>
The following defaults apply.
<span><strong class="command">min-refresh-time</strong></span> 300 seconds,
<span><strong class="command">max-refresh-time</strong></span> 2419200 seconds
(4 weeks), <span><strong class="command">min-retry-time</strong></span> 500 seconds,
and <span><strong class="command">max-retry-time</strong></span> 1209600 seconds
(2 weeks).
</p>
</dd>
<dt><span class="term"><span><strong class="command">edns-udp-size</strong></span></span></dt>
<dd>
<p>
Sets the initial advertised EDNS UDP buffer size in
bytes, to control the size of packets received from
authoritative servers in response to recursive queries.
Valid values are 512 to 4096 (values outside this range
will be silently adjusted to the nearest value within
it). The default value is 4096.
</p>
<p>
The usual reason for setting
<span><strong class="command">edns-udp-size</strong></span> to a non-default value
is to get UDP answers to pass through broken firewalls
that block fragmented packets and/or block UDP DNS
packets that are greater than 512 bytes.
</p>
<p>
When <span><strong class="command">named</strong></span> first queries a remote
server, it will advertise a UDP buffer size of 512, as
this has the greatest chance of success on the first try.
</p>
<p>
If the initial response times out, <span><strong class="command">named</strong></span>
will try again with plain DNS, and if that is successful,
it will be taken as evidence that the server does not
support EDNS. After enough failures using EDNS and
successes using plain DNS, <span><strong class="command">named</strong></span>
will default to plain DNS for future communications
with that server. (Periodically, <span><strong class="command">named</strong></span>
will send an EDNS query to see if the situation has
improved.)
</p>
<p>
However, if the initial query is successful with
EDNS advertising a buffer size of 512, then
<span><strong class="command">named</strong></span> will advertise progressively
larger buffer sizes on successive queries, until
responses begin timing out or
<span><strong class="command">edns-udp-size</strong></span> is reached.
</p>
<p>
The default buffer sizes used by <span><strong class="command">named</strong></span>
are 512, 1232, 1432, and 4096, but never exceeding
<span><strong class="command">edns-udp-size</strong></span>. (The values 1232 and
1432 are chosen to allow for an IPv4/IPv6 encapsulated
UDP message to be sent without fragmentation at the
minimum MTU sizes for Ethernet and IPv6 networks.)
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-udp-size</strong></span></span></dt>
<dd>
<p>
Sets the maximum EDNS UDP message size
<span><strong class="command">named</strong></span> will send in bytes.
Valid values are 512 to 4096 (values outside this
range will be silently adjusted to the nearest
value within it). The default value is 4096.
</p>
<p>
This value applies to responses sent by a server; to
set the advertised buffer size in queries, see
<span><strong class="command">edns-udp-size</strong></span>.
</p>
<p>
The usual reason for setting
<span><strong class="command">max-udp-size</strong></span> to a non-default
value is to get UDP answers to pass through broken
firewalls that block fragmented packets and/or
block UDP packets that are greater than 512 bytes.
This is independent of the advertised receive
buffer (<span><strong class="command">edns-udp-size</strong></span>).
</p>
<p>
Setting this to a low value will encourage additional
TCP traffic to the nameserver.
</p>
</dd>
<dt><span class="term"><span><strong class="command">masterfile-format</strong></span></span></dt>
<dd>
<p>Specifies
the file format of zone files (see
<a href="Bv9ARM.ch06.html#zonefile_format" title="Additional File Formats">the section called &#8220;Additional File Formats&#8221;</a>).
The default value is <code class="constant">text</code>, which is the
standard textual representation, except for slave zones,
in which the default value is <code class="constant">raw</code>.
Files in other formats than <code class="constant">text</code> are
typically expected to be generated by the
<span><strong class="command">named-compilezone</strong></span> tool, or dumped by
<span><strong class="command">named</strong></span>.
</p>
<p>
Note that when a zone file in a different format than
<code class="constant">text</code> is loaded, <span><strong class="command">named</strong></span>
may omit some of the checks which would be performed for a
file in the <code class="constant">text</code> format. In particular,
<span><strong class="command">check-names</strong></span> checks do not apply
for the <code class="constant">raw</code> format. This means
a zone file in the <code class="constant">raw</code> format
must be generated with the same check level as that
specified in the <span><strong class="command">named</strong></span> configuration
file. Also, <code class="constant">map</code> format files are
loaded directly into memory via memory mapping, with only
minimal checking.
</p>
<p>
This statement sets the
<span><strong class="command">masterfile-format</strong></span> for all zones,
but can be overridden on a per-zone or per-view basis
by including a <span><strong class="command">masterfile-format</strong></span>
statement within the <span><strong class="command">zone</strong></span> or
<span><strong class="command">view</strong></span> block in the configuration
file.
</p>
</dd>
<dt><span class="term"><span><strong class="command">masterfile-style</strong></span></span></dt>
<dd>
<p>
Specifies the formatting of zone files during dump
when the <code class="option">masterfile-format</code> is
<code class="constant">text</code>. (This option is ignored
with any other <code class="option">masterfile-format</code>.)
</p>
<p>
When set to <code class="constant">relative</code>,
records are printed in a multi-line format with owner
names expressed relative to a shared origin. When set
to <code class="constant">full</code>, records are printed in
a single-line format with absolute owner names.
The <code class="constant">full</code> format is most suitable
when a zone file needs to be processed automatically
by a script. The <code class="constant">relative</code> format
is more human-readable, and is thus suitable when a
zone is to be edited by hand. The default is
<code class="constant">relative</code>.
</p>
</dd>
<dt>
<a name="clients-per-query"></a><span class="term"><span><strong class="command">clients-per-query</strong></span>, </span><span class="term"><span><strong class="command">max-clients-per-query</strong></span></span>
</dt>
<dd>
<p>These set the
initial value (minimum) and maximum number of recursive
simultaneous clients for any given query
(&lt;qname,qtype,qclass&gt;) that the server will accept
before dropping additional clients.
<span><strong class="command">named</strong></span> will attempt to
self tune this value and changes will be logged. The
default values are 10 and 100.
</p>
<p>
This value should reflect how many queries come in for
a given name in the time it takes to resolve that name.
If the number of queries exceed this value, <span><strong class="command">named</strong></span> will
assume that it is dealing with a non-responsive zone
and will drop additional queries. If it gets a response
after dropping queries, it will raise the estimate. The
estimate will then be lowered in 20 minutes if it has
remained unchanged.
</p>
<p>
If <span><strong class="command">clients-per-query</strong></span> is set to zero,
then there is no limit on the number of clients per query
and no queries will be dropped.
</p>
<p>
If <span><strong class="command">max-clients-per-query</strong></span> is set to zero,
then there is no upper bound other than imposed by
<span><strong class="command">recursive-clients</strong></span>.
</p>
</dd>
<dt>
<a name="max-recursion-depth"></a><span class="term"><span><strong class="command">max-recursion-depth</strong></span></span>
</dt>
<dd><p>
Sets the maximum number of levels of recursion
that are permitted at any one time while servicing
a recursive query. Resolving a name may require
looking up a name server address, which in turn
requires resolving another name, etc; if the number
of indirections exceeds this value, the recursive
query is terminated and returns SERVFAIL. The
default is 7.
</p></dd>
<dt>
<a name="max-recursion-queries"></a><span class="term"><span><strong class="command">max-recursion-queries</strong></span></span>
</dt>
<dd><p>
Sets the maximum number of iterative queries that
may be sent while servicing a recursive query.
If more queries are sent, the recursive query
is terminated and returns SERVFAIL. Queries to
look up top level comains such as "com" and "net"
and the DNS root zone are exempt from this limitation.
The default is 75.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt>
<dd>
<p>
The delay, in seconds, between sending sets of notify
messages for a zone. The default is five (5) seconds.
</p>
<p>
The overall rate that NOTIFY messages are sent for all
zones is controlled by <span><strong class="command">serial-query-rate</strong></span>.
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-rsa-exponent-size</strong></span></span></dt>
<dd><p>
The maximum RSA exponent size, in bits, that will
be accepted when validating. Valid values are 35
to 4096 bits. The default zero (0) is also accepted
and is equivalent to 4096.
</p></dd>
<dt><span class="term"><span><strong class="command">prefetch</strong></span></span></dt>
<dd>
<p>
When a query is received for cached data which
is to expire shortly, <span><strong class="command">named</strong></span> can
refresh the data from the authoritative server
immediately, ensuring that the cache always has an
answer available.
</p>
<p>
The <code class="option">prefetch</code> specifies the
"trigger" TTL value at which prefetch of the current
query will take place: when a cache record with a
lower TTL value is encountered during query processing,
it will be refreshed. Valid trigger TTL values are 1 to
10 seconds. Values larger than 10 seconds will be silently
reduced to 10.
Setting a trigger TTL to zero (0) causes
prefetch to be disabled.
The default trigger TTL is <code class="literal">2</code>.
</p>
<p>
An optional second argument specifies the "eligibility"
TTL: the smallest <span class="emphasis"><em>original</em></span>
TTL value that will be accepted for a record to be
eligible for prefetching. The eligibility TTL must
be at least six seconds longer than the trigger TTL;
if it isn't, <span><strong class="command">named</strong></span> will silently
adjust it upward.
The default eligibility TTL is <code class="literal">9</code>.
</p>
</dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="builtin"></a>Built-in server information zones</h4></div></div></div>
<p>
The server provides some helpful diagnostic information
through a number of built-in zones under the
pseudo-top-level-domain <code class="literal">bind</code> in the
<span><strong class="command">CHAOS</strong></span> class. These zones are part
of a
built-in view (see <a href="Bv9ARM.ch06.html#view_statement_grammar" title="view Statement Grammar">the section called &#8220;<span><strong class="command">view</strong></span> Statement Grammar&#8221;</a>) of
class
<span><strong class="command">CHAOS</strong></span> which is separate from the
default view of class <span><strong class="command">IN</strong></span>. Most global
configuration options (<span><strong class="command">allow-query</strong></span>,
etc) will apply to this view, but some are locally
overridden: <span><strong class="command">notify</strong></span>,
<span><strong class="command">recursion</strong></span> and
<span><strong class="command">allow-new-zones</strong></span> are
always set to <strong class="userinput"><code>no</code></strong>, and
<span><strong class="command">rate-limit</strong></span> is set to allow
three responses per second.
</p>
<p>
If you need to disable these zones, use the options
below, or hide the built-in <span><strong class="command">CHAOS</strong></span>
view by
defining an explicit view of class <span><strong class="command">CHAOS</strong></span>
that matches all clients.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">version</strong></span></span></dt>
<dd><p>
The version the server should report
via a query of the name <code class="literal">version.bind</code>
with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
The default is the real version number of this server.
Specifying <span><strong class="command">version none</strong></span>
disables processing of the queries.
</p></dd>
<dt><span class="term"><span><strong class="command">hostname</strong></span></span></dt>
<dd><p>
The hostname the server should report via a query of
the name <code class="filename">hostname.bind</code>
with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
This defaults to the hostname of the machine hosting the
name server as
found by the gethostname() function. The primary purpose of such queries
is to
identify which of a group of anycast servers is actually
answering your queries. Specifying <span><strong class="command">hostname none;</strong></span>
disables processing of the queries.
</p></dd>
<dt><span class="term"><span><strong class="command">server-id</strong></span></span></dt>
<dd><p>
The ID the server should report when receiving a Name
Server Identifier (NSID) query, or a query of the name
<code class="filename">ID.SERVER</code> with type
<span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
The primary purpose of such queries is to
identify which of a group of anycast servers is actually
answering your queries. Specifying <span><strong class="command">server-id none;</strong></span>
disables processing of the queries.
Specifying <span><strong class="command">server-id hostname;</strong></span> will cause <span><strong class="command">named</strong></span> to
use the hostname as found by the gethostname() function.
The default <span><strong class="command">server-id</strong></span> is <span><strong class="command">none</strong></span>.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="empty"></a>Built-in Empty Zones</h4></div></div></div>
<p>
The <span><strong class="command">named</strong></span> server has some built-in
empty zones (SOA and NS records only).
These are for zones that should normally be answered locally
and which queries should not be sent to the Internet's root
servers. The official servers which cover these namespaces
return NXDOMAIN responses to these queries. In particular,
these cover the reverse namespaces for addresses from
RFC 1918, RFC 4193, RFC 5737 and RFC 6598. They also include the
reverse namespace for IPv6 local address (locally assigned),
IPv6 link local addresses, the IPv6 loopback address and the
IPv6 unknown address.
</p>
<p>
The server will attempt to determine if a built-in zone
already exists or is active (covered by a forward-only
forwarding declaration) and will not create an empty
zone in that case.
</p>
<p>
The current list of empty zones is:
</p>
<div class="itemizedlist"><ul type="disc">
<li>10.IN-ADDR.ARPA</li>
<li>16.172.IN-ADDR.ARPA</li>
<li>17.172.IN-ADDR.ARPA</li>
<li>18.172.IN-ADDR.ARPA</li>
<li>19.172.IN-ADDR.ARPA</li>
<li>20.172.IN-ADDR.ARPA</li>
<li>21.172.IN-ADDR.ARPA</li>
<li>22.172.IN-ADDR.ARPA</li>
<li>23.172.IN-ADDR.ARPA</li>
<li>24.172.IN-ADDR.ARPA</li>
<li>25.172.IN-ADDR.ARPA</li>
<li>26.172.IN-ADDR.ARPA</li>
<li>27.172.IN-ADDR.ARPA</li>
<li>28.172.IN-ADDR.ARPA</li>
<li>29.172.IN-ADDR.ARPA</li>
<li>30.172.IN-ADDR.ARPA</li>
<li>31.172.IN-ADDR.ARPA</li>
<li>168.192.IN-ADDR.ARPA</li>
<li>64.100.IN-ADDR.ARPA</li>
<li>65.100.IN-ADDR.ARPA</li>
<li>66.100.IN-ADDR.ARPA</li>
<li>67.100.IN-ADDR.ARPA</li>
<li>68.100.IN-ADDR.ARPA</li>
<li>69.100.IN-ADDR.ARPA</li>
<li>70.100.IN-ADDR.ARPA</li>
<li>71.100.IN-ADDR.ARPA</li>
<li>72.100.IN-ADDR.ARPA</li>
<li>73.100.IN-ADDR.ARPA</li>
<li>74.100.IN-ADDR.ARPA</li>
<li>75.100.IN-ADDR.ARPA</li>
<li>76.100.IN-ADDR.ARPA</li>
<li>77.100.IN-ADDR.ARPA</li>
<li>78.100.IN-ADDR.ARPA</li>
<li>79.100.IN-ADDR.ARPA</li>
<li>80.100.IN-ADDR.ARPA</li>
<li>81.100.IN-ADDR.ARPA</li>
<li>82.100.IN-ADDR.ARPA</li>
<li>83.100.IN-ADDR.ARPA</li>
<li>84.100.IN-ADDR.ARPA</li>
<li>85.100.IN-ADDR.ARPA</li>
<li>86.100.IN-ADDR.ARPA</li>
<li>87.100.IN-ADDR.ARPA</li>
<li>88.100.IN-ADDR.ARPA</li>
<li>89.100.IN-ADDR.ARPA</li>
<li>90.100.IN-ADDR.ARPA</li>
<li>91.100.IN-ADDR.ARPA</li>
<li>92.100.IN-ADDR.ARPA</li>
<li>93.100.IN-ADDR.ARPA</li>
<li>94.100.IN-ADDR.ARPA</li>
<li>95.100.IN-ADDR.ARPA</li>
<li>96.100.IN-ADDR.ARPA</li>
<li>97.100.IN-ADDR.ARPA</li>
<li>98.100.IN-ADDR.ARPA</li>
<li>99.100.IN-ADDR.ARPA</li>
<li>100.100.IN-ADDR.ARPA</li>
<li>101.100.IN-ADDR.ARPA</li>
<li>102.100.IN-ADDR.ARPA</li>
<li>103.100.IN-ADDR.ARPA</li>
<li>104.100.IN-ADDR.ARPA</li>
<li>105.100.IN-ADDR.ARPA</li>
<li>106.100.IN-ADDR.ARPA</li>
<li>107.100.IN-ADDR.ARPA</li>
<li>108.100.IN-ADDR.ARPA</li>
<li>109.100.IN-ADDR.ARPA</li>
<li>110.100.IN-ADDR.ARPA</li>
<li>111.100.IN-ADDR.ARPA</li>
<li>112.100.IN-ADDR.ARPA</li>
<li>113.100.IN-ADDR.ARPA</li>
<li>114.100.IN-ADDR.ARPA</li>
<li>115.100.IN-ADDR.ARPA</li>
<li>116.100.IN-ADDR.ARPA</li>
<li>117.100.IN-ADDR.ARPA</li>
<li>118.100.IN-ADDR.ARPA</li>
<li>119.100.IN-ADDR.ARPA</li>
<li>120.100.IN-ADDR.ARPA</li>
<li>121.100.IN-ADDR.ARPA</li>
<li>122.100.IN-ADDR.ARPA</li>
<li>123.100.IN-ADDR.ARPA</li>
<li>124.100.IN-ADDR.ARPA</li>
<li>125.100.IN-ADDR.ARPA</li>
<li>126.100.IN-ADDR.ARPA</li>
<li>127.100.IN-ADDR.ARPA</li>
<li>0.IN-ADDR.ARPA</li>
<li>127.IN-ADDR.ARPA</li>
<li>254.169.IN-ADDR.ARPA</li>
<li>2.0.192.IN-ADDR.ARPA</li>
<li>100.51.198.IN-ADDR.ARPA</li>
<li>113.0.203.IN-ADDR.ARPA</li>
<li>255.255.255.255.IN-ADDR.ARPA</li>
<li>0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
<li>1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
<li>8.B.D.0.1.0.0.2.IP6.ARPA</li>
<li>D.F.IP6.ARPA</li>
<li>8.E.F.IP6.ARPA</li>
<li>9.E.F.IP6.ARPA</li>
<li>A.E.F.IP6.ARPA</li>
<li>B.E.F.IP6.ARPA</li>
</ul></div>
<p>
</p>
<p>
Empty zones are settable at the view level and only apply to
views of class IN. Disabled empty zones are only inherited
from options if there are no disabled empty zones specified
at the view level. To override the options list of disabled
zones, you can disable the root zone at the view level, for example:
</p>
<pre class="programlisting">
disable-empty-zone ".";
</pre>
<p>
</p>
<p>
If you are using the address ranges covered here, you should
already have reverse zones covering the addresses you use.
In practice this appears to not be the case with many queries
being made to the infrastructure servers for names in these
spaces. So many in fact that sacrificial servers were needed
to be deployed to channel the query load away from the
infrastructure servers.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
The real parent servers for these zones should disable all
empty zone under the parent zone they serve. For the real
root servers, this is all built-in empty zones. This will
enable them to return referrals to deeper in the tree.
</div>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">empty-server</strong></span></span></dt>
<dd><p>
Specify what server name will appear in the returned
SOA record for empty zones. If none is specified, then
the zone's name will be used.
</p></dd>
<dt><span class="term"><span><strong class="command">empty-contact</strong></span></span></dt>
<dd><p>
Specify what contact name will appear in the returned
SOA record for empty zones. If none is specified, then
"." will be used.
</p></dd>
<dt><span class="term"><span><strong class="command">empty-zones-enable</strong></span></span></dt>
<dd><p>
Enable or disable all empty zones. By default, they
are enabled.
</p></dd>
<dt><span class="term"><span><strong class="command">disable-empty-zone</strong></span></span></dt>
<dd><p>
Disable individual empty zones. By default, none are
disabled. This option can be specified multiple times.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="acache"></a>Additional Section Caching</h4></div></div></div>
<p>
The additional section cache, also called <span><strong class="command">acache</strong></span>,
is an internal cache to improve the response performance of BIND 9.
When additional section caching is enabled, BIND 9 will
cache an internal short-cut to the additional section content for
each answer RR.
Note that <span><strong class="command">acache</strong></span> is an internal caching
mechanism of BIND 9, and is not related to the DNS caching
server function.
</p>
<p>
Additional section caching does not change the
response content (except the RRsets ordering of the additional
section, see below), but can improve the response performance
significantly.
It is particularly effective when BIND 9 acts as an authoritative
server for a zone that has many delegations with many glue RRs.
</p>
<p>
In order to obtain the maximum performance improvement
from additional section caching, setting
<span><strong class="command">additional-from-cache</strong></span>
to <span><strong class="command">no</strong></span> is recommended, since the current
implementation of <span><strong class="command">acache</strong></span>
does not short-cut of additional section information from the
DNS cache data.
</p>
<p>
One obvious disadvantage of <span><strong class="command">acache</strong></span> is
that it requires much more
memory for the internal cached data.
Thus, if the response performance does not matter and memory
consumption is much more critical, the
<span><strong class="command">acache</strong></span> mechanism can be
disabled by setting <span><strong class="command">acache-enable</strong></span> to
<span><strong class="command">no</strong></span>.
It is also possible to specify the upper limit of memory
consumption
for acache by using <span><strong class="command">max-acache-size</strong></span>.
</p>
<p>
Additional section caching also has a minor effect on the
RRset ordering in the additional section.
Without <span><strong class="command">acache</strong></span>,
<span><strong class="command">cyclic</strong></span> order is effective for the additional
section as well as the answer and authority sections.
However, additional section caching fixes the ordering when it
first caches an RRset for the additional section, and the same
ordering will be kept in succeeding responses, regardless of the
setting of <span><strong class="command">rrset-order</strong></span>.
The effect of this should be minor, however, since an
RRset in the additional section
typically only contains a small number of RRs (and in many cases
it only contains a single RR), in which case the
ordering does not matter much.
</p>
<p>
The following is a summary of options related to
<span><strong class="command">acache</strong></span>.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">acache-enable</strong></span></span></dt>
<dd><p>
If <span><strong class="command">yes</strong></span>, additional section caching is
enabled. The default value is <span><strong class="command">no</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">acache-cleaning-interval</strong></span></span></dt>
<dd><p>
The server will remove stale cache entries, based on an LRU
based
algorithm, every <span><strong class="command">acache-cleaning-interval</strong></span> minutes.
The default is 60 minutes.
If set to 0, no periodic cleaning will occur.
</p></dd>
<dt><span class="term"><span><strong class="command">max-acache-size</strong></span></span></dt>
<dd><p>
The maximum amount of memory in bytes to use for the server's acache.
When the amount of data in the acache reaches this limit,
the server
will clean more aggressively so that the limit is not
exceeded.
In a server with multiple views, the limit applies
separately to the
acache of each view.
The default is <code class="literal">16M</code>.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2590129"></a>Content Filtering</h4></div></div></div>
<p>
<acronym class="acronym">BIND</acronym> 9 provides the ability to filter
out DNS responses from external DNS servers containing
certain types of data in the answer section.
Specifically, it can reject address (A or AAAA) records if
the corresponding IPv4 or IPv6 addresses match the given
<code class="varname">address_match_list</code> of the
<span><strong class="command">deny-answer-addresses</strong></span> option.
It can also reject CNAME or DNAME records if the "alias"
name (i.e., the CNAME alias or the substituted query name
due to DNAME) matches the
given <code class="varname">namelist</code> of the
<span><strong class="command">deny-answer-aliases</strong></span> option, where
"match" means the alias name is a subdomain of one of
the <code class="varname">name_list</code> elements.
If the optional <code class="varname">namelist</code> is specified
with <span><strong class="command">except-from</strong></span>, records whose query name
matches the list will be accepted regardless of the filter
setting.
Likewise, if the alias name is a subdomain of the
corresponding zone, the <span><strong class="command">deny-answer-aliases</strong></span>
filter will not apply;
for example, even if "example.com" is specified for
<span><strong class="command">deny-answer-aliases</strong></span>,
</p>
<pre class="programlisting">www.example.com. CNAME xxx.example.com.</pre>
<p>
returned by an "example.com" server will be accepted.
</p>
<p>
In the <code class="varname">address_match_list</code> of the
<span><strong class="command">deny-answer-addresses</strong></span> option, only
<code class="varname">ip_addr</code>
and <code class="varname">ip_prefix</code>
are meaningful;
any <code class="varname">key_id</code> will be silently ignored.
</p>
<p>
If a response message is rejected due to the filtering,
the entire message is discarded without being cached, and
a SERVFAIL error will be returned to the client.
</p>
<p>
This filtering is intended to prevent "DNS rebinding attacks," in
which an attacker, in response to a query for a domain name the
attacker controls, returns an IP address within your own network or
an alias name within your own domain.
A naive web browser or script could then serve as an
unintended proxy, allowing the attacker
to get access to an internal node of your local network
that couldn't be externally accessed otherwise.
See the paper available at
<a href="http://portal.acm.org/citation.cfm?id=1315245.1315298" target="_top">
http://portal.acm.org/citation.cfm?id=1315245.1315298
</a>
for more details about the attacks.
</p>
<p>
For example, if you own a domain named "example.net" and
your internal network uses an IPv4 prefix 192.0.2.0/24,
you might specify the following rules:
</p>
<pre class="programlisting">deny-answer-addresses { 192.0.2.0/24; } except-from { "example.net"; };
deny-answer-aliases { "example.net"; };
</pre>
<p>
If an external attacker lets a web browser in your local
network look up an IPv4 address of "attacker.example.com",
the attacker's DNS server would return a response like this:
</p>
<pre class="programlisting">attacker.example.com. A 192.0.2.1</pre>
<p>
in the answer section.
Since the rdata of this record (the IPv4 address) matches
the specified prefix 192.0.2.0/24, this response will be
ignored.
</p>
<p>
On the other hand, if the browser looks up a legitimate
internal web server "www.example.net" and the
following response is returned to
the <acronym class="acronym">BIND</acronym> 9 server
</p>
<pre class="programlisting">www.example.net. A 192.0.2.2</pre>
<p>
it will be accepted since the owner name "www.example.net"
matches the <span><strong class="command">except-from</strong></span> element,
"example.net".
</p>
<p>
Note that this is not really an attack on the DNS per se.
In fact, there is nothing wrong for an "external" name to
be mapped to your "internal" IP address or domain name
from the DNS point of view.
It might actually be provided for a legitimate purpose,
such as for debugging.
As long as the mapping is provided by the correct owner,
it is not possible or does not make sense to detect
whether the intent of the mapping is legitimate or not
within the DNS.
The "rebinding" attack must primarily be protected at the
application that uses the DNS.
For a large site, however, it may be difficult to protect
all possible applications at once.
This filtering feature is provided only to help such an
operational environment;
it is generally discouraged to turn it on unless you are
very sure you have no other choice and the attack is a
real threat for your applications.
</p>
<p>
Care should be particularly taken if you want to use this
option for addresses within 127.0.0.0/8.
These addresses are obviously "internal", but many
applications conventionally rely on a DNS mapping from
some name to such an address.
Filtering out DNS records containing this address
spuriously can break such applications.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2590323"></a>Response Policy Zone (RPZ) Rewriting</h4></div></div></div>
<p>
<acronym class="acronym">BIND</acronym> 9 includes a limited
mechanism to modify DNS responses for requests
analogous to email anti-spam DNS blacklists.
Responses can be changed to deny the existence of domains (NXDOMAIN),
deny the existence of IP addresses for domains (NODATA),
or contain other IP addresses or data.
</p>
<p>
Response policy zones are named in the
<span><strong class="command">response-policy</strong></span> option for the view or among the
global options if there is no response-policy option for the view.
Response policy zones are ordinary DNS zones containing RRsets
that can be queried normally if allowed.
It is usually best to restrict those queries with something like
<span><strong class="command">allow-query { localhost; };</strong></span>.
</p>
<p>
A <span><strong class="command">response-policy</strong></span> option can support
multiple policy zones. To maximize performance, a radix
tree is used to quickly identify response policy zones
containing triggers that match the current query. This
imposes an upper limit of 32 on the number of policy zones
in a single <span><strong class="command">response-policy</strong></span> option; more
than that is a configuration error.
</p>
<p>
Five policy triggers can be encoded in RPZ records.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">RPZ-CLIENT-IP</strong></span></span></dt>
<dd>
<p>
IP records are triggered by the IP address of the
DNS client.
Client IP address triggers are encoded in records that have
owner names that are subdomains of
<span><strong class="command">rpz-client-ip</strong></span> relativized to the
policy zone origin name
and encode an address or address block.
IPv4 addresses are represented as
<strong class="userinput"><code>prefixlength.B4.B3.B2.B1.rpz-ip</code></strong>.
The IPv4 prefix length must be between 1 and 32.
All four bytes, B4, B3, B2, and B1, must be present.
B4 is the decimal value of the least significant byte of the
IPv4 address as in IN-ADDR.ARPA.
</p>
<p>
IPv6 addresses are encoded in a format similar
to the standard IPv6 text representation,
<strong class="userinput"><code>prefixlength.W8.W7.W6.W5.W4.W3.W2.W1.rpz-ip</code></strong>.
Each of W8,...,W1 is a one to four digit hexadecimal number
representing 16 bits of the IPv6 address as in the standard
text representation of IPv6 addresses,
but reversed as in IN-ADDR.ARPA.
All 8 words must be present except when one set of consecutive
zero words is replaced with <strong class="userinput"><code>.zz.</code></strong>
analogous to double colons (::) in standard IPv6 text
encodings.
The IPv6 prefix length must be between 64 and 128.
</p>
</dd>
<dt><span class="term"><span><strong class="command">QNAME</strong></span></span></dt>
<dd><p>
QNAME policy records are triggered by query names of
requests and targets of CNAME records resolved to generate
the response.
The owner name of a QNAME policy record is
the query name relativized to the policy zone.
</p></dd>
<dt><span class="term"><span><strong class="command">RPZ-IP</strong></span></span></dt>
<dd><p>
IP triggers are IP addresses in an
A or AAAA record in the ANSWER section of a response.
They are encoded like client-IP triggers except as
subdomains of <span><strong class="command">rpz-ip</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">RPZ-NSDNAME</strong></span></span></dt>
<dd><p>
NSDNAME triggers match names of authoritative servers
for the query name, a parent of the query name, a CNAME for
query name, or a parent of a CNAME.
They are encoded as subdomains of
<span><strong class="command">rpz-nsdname</strong></span> relativized
to the RPZ origin name.
NSIP triggers match IP addresses in A and
AAAA RRsets for domains that can be checked against NSDNAME
policy records.
</p></dd>
<dt><span class="term"><span><strong class="command">RPZ-NSIP</strong></span></span></dt>
<dd><p>
NSIP triggers are encoded like IP triggers except as
subdomains of <span><strong class="command">rpz-nsip</strong></span>.
NSDNAME and NSIP triggers are checked only for names with at
least <span><strong class="command">min-ns-dots</strong></span> dots.
The default value of <span><strong class="command">min-ns-dots</strong></span> is 1 to
exclude top level domains.
</p></dd>
</dl></div>
<p>
</p>
<p>
The query response is checked against all response policy zones,
so two or more policy records can be triggered by a response.
Because DNS responses are rewritten according to at most one
policy record, a single record encoding an action (other than
<span><strong class="command">DISABLED</strong></span> actions) must be chosen.
Triggers or the records that encode them are chosen for the
rewriting in the following order:
</p>
<div class="itemizedlist"><ul type="disc">
<li>Choose the triggered record in the zone that appears
first in the <span><strong class="command">response-policy</strong></span> option.
</li>
<li>Prefer CLIENT-IP to QNAME to IP to NSDNAME to NSIP
triggers in a single zone.
</li>
<li>Among NSDNAME triggers, prefer the
trigger that matches the smallest name under the DNSSEC ordering.
</li>
<li>Among IP or NSIP triggers, prefer the trigger
with the longest prefix.
</li>
<li>Among triggers with the same prefix length,
prefer the IP or NSIP trigger that matches
the smallest IP address.
</li>
</ul></div>
<p>
</p>
<p>
When the processing of a response is restarted to resolve
DNAME or CNAME records and a policy record set has
not been triggered,
all response policy zones are again consulted for the
DNAME or CNAME names and addresses.
</p>
<p>
RPZ record sets are any types of DNS record except
DNAME or DNSSEC that encode actions or responses to
individual queries.
Any of the policies can be used with any of the triggers.
For example, while the <span><strong class="command">TCP-only</strong></span> policy is
commonly used with <span><strong class="command">client-IP</strong></span> triggers,
it can be used with any type of trigger to force the use of
TCP for responses with owner names in a zone.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">PASSTHRU</strong></span></span></dt>
<dd><p>
The whitelist policy is specified
by a CNAME whose target is <span><strong class="command">rpz-passthru</strong></span>.
It causes the response to not be rewritten
and is most often used to "poke holes" in policies for
CIDR blocks.
</p></dd>
<dt><span class="term"><span><strong class="command">DROP</strong></span></span></dt>
<dd><p>
The blacklist policy is specified
by a CNAME whose target is <span><strong class="command">rpz-drop</strong></span>.
It causes the response to be discarded.
Nothing is sent to the DNS client.
</p></dd>
<dt><span class="term"><span><strong class="command">TCP-Only</strong></span></span></dt>
<dd><p>
The "slip" policy is specified
by a CNAME whose target is <span><strong class="command">rpz-tcp-only</strong></span>.
It changes UDP responses to short, truncated DNS responses
that require the DNS client to try again with TCP.
It is used to mitigate distributed DNS reflection attacks.
</p></dd>
<dt><span class="term"><span><strong class="command">NXDOMAIN</strong></span></span></dt>
<dd><p>
The domain undefined response is encoded
by a CNAME whose target is the root domain (.)
</p></dd>
<dt><span class="term"><span><strong class="command">NODATA</strong></span></span></dt>
<dd><p>
The empty set of resource records is specified by
CNAME whose target is the wildcard top-level
domain (*.).
It rewrites the response to NODATA or ANCOUNT=1.
</p></dd>
<dt><span class="term"><span><strong class="command">Local Data</strong></span></span></dt>
<dd>
<p>
A set of ordinary DNS records can be used to answer queries.
Queries for record types not the set are answered with
NODATA.
</p>
<p>
A special form of local data is a CNAME whose target is a
wildcard such as *.example.com.
It is used as if were an ordinary CNAME after the astrisk (*)
has been replaced with the query name.
The purpose for this special form is query logging in the
walled garden's authority DNS server.
</p>
</dd>
</dl></div>
<p>
</p>
<p>
All of the actions specified in all of the individual records
in a policy zone
can be overridden with a <span><strong class="command">policy</strong></span> clause in the
<span><strong class="command">response-policy</strong></span> option.
An organization using a policy zone provided by another
organization might use this mechanism to redirect domains
to its own walled garden.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">GIVEN</strong></span></span></dt>
<dd><p>The placeholder policy says "do not override but
perform the action specified in the zone."
</p></dd>
<dt><span class="term"><span><strong class="command">DISABLED</strong></span></span></dt>
<dd><p>
The testing override policy causes policy zone records to do
nothing but log what they would have done if the
policy zone were not disabled.
The response to the DNS query will be written (or not)
according to any triggered policy records that are not
disabled.
Disabled policy zones should appear first,
because they will often not be logged
if a higher precedence trigger is found first.
</p></dd>
<dt>
<span class="term"><span><strong class="command">PASSTHRU</strong></span>, </span><span class="term"><span><strong class="command">DROP</strong></span>, </span><span class="term"><span><strong class="command">TCP-Only</strong></span>, </span><span class="term"><span><strong class="command">NXDOMAIN</strong></span>, </span><span class="term"><span><strong class="command">NODATA</strong></span></span>
</dt>
<dd><p>
override with the corresponding per-record policy.
</p></dd>
<dt><span class="term"><span><strong class="command">CNAME domain</strong></span></span></dt>
<dd><p>
causes all RPZ policy records to act as if they were
"cname domain" records.
</p></dd>
</dl></div>
<p>
</p>
<p>
By default, the actions encoded in a response policy zone
are applied only to queries that ask for recursion (RD=1).
That default can be changed for a single policy zone or
all response policy zones in a view
with a <span><strong class="command">recursive-only no</strong></span> clause.
This feature is useful for serving the same zone files
both inside and outside an RFC 1918 cloud and using RPZ to
delete answers that would otherwise contain RFC 1918 values
on the externally visible name server or view.
</p>
<p>
Also by default, RPZ actions are applied only to DNS requests
that either do not request DNSSEC metadata (DO=0) or when no
DNSSEC records are available for request name in the original
zone (not the response policy zone). This default can be
changed for all response policy zones in a view with a
<span><strong class="command">break-dnssec yes</strong></span> clause. In that case, RPZ
actions are applied regardless of DNSSEC. The name of the
clause option reflects the fact that results rewritten by RPZ
actions cannot verify.
</p>
<p>
No DNS records are needed for a QNAME or Client-IP trigger.
The name or IP address itself is sufficient,
so in principle the query name need not be recursively resolved.
However, not resolving the requested
name can leak the fact that response policy rewriting is in use
and that the name is listed in a policy zone to operators of
servers for listed names. To prevent that information leak, by
default any recursion needed for a request is done before any
policy triggers are considered. Because listed domains often
have slow authoritative servers, this default behavior can cost
significant time.
The <span><strong class="command">qname-wait-recurse no</strong></span> option
overrides that default behavior when recursion cannot
change a non-error response.
The option does not affect QNAME or client-IP triggers
in policy zones listed
after other zones containing IP, NSIP and NSDNAME triggers, because
those may depend on the A, AAAA, and NS records that would be
found during recursive resolution. It also does not affect
DNSSEC requests (DO=1) unless <span><strong class="command">break-dnssec yes</strong></span>
is in use, because the response would depend on whether or not
RRSIG records were found during resolution.
Using this option can cause error responses such as SERVFAIL to
appear to be rewritten, since no recursion is being done to
discover problems at the authoritative server.
</p>
<p>
The TTL of a record modified by RPZ policies is set from the
TTL of the relevant record in policy zone. It is then limited
to a maximum value.
The <span><strong class="command">max-policy-ttl</strong></span> clause changes that
maximum from its default of 5.
</p>
<p>
For example, you might use this option statement
</p>
<pre class="programlisting"> response-policy { zone "badlist"; };</pre>
<p>
and this zone statement
</p>
<pre class="programlisting"> zone "badlist" {type master; file "master/badlist"; allow-query {none;}; };</pre>
<p>
with this zone file
</p>
<pre class="programlisting">$TTL 1H
@ SOA LOCALHOST. named-mgr.example.com (1 1h 15m 30d 2h)
NS LOCALHOST.
; QNAME policy records. There are no periods (.) after the owner names.
nxdomain.domain.com CNAME . ; NXDOMAIN policy
*.nxdomain.domain.com CNAME . ; NXDOMAIN policy
nodata.domain.com CNAME *. ; NODATA policy
*.nodata.domain.com CNAME *. ; NODATA policy
bad.domain.com A 10.0.0.1 ; redirect to a walled garden
AAAA 2001:2::1
bzone.domain.com CNAME garden.example.com.
; do not rewrite (PASSTHRU) OK.DOMAIN.COM
ok.domain.com CNAME rpz-passthru.
; redirect x.bzone.domain.com to x.bzone.domain.com.garden.example.com
*.bzone.domain.com CNAME *.garden.example.com.
; IP policy records that rewrite all responses containing A records in 127/8
; except 127.0.0.1
8.0.0.0.127.rpz-ip CNAME .
32.1.0.0.127.rpz-ip CNAME rpz-passthru.
; NSDNAME and NSIP policy records
ns.domain.com.rpz-nsdname CNAME .
48.zz.2.2001.rpz-nsip CNAME .
; blacklist and whitelist some DNS clients
112.zz.2001.rpz-client-ip CNAME rpz-drop.
8.0.0.0.127.rpz-client-ip CNAME rpz-drop.
; force some DNS clients and responses in the example.com zone to TCP
16.0.0.1.10.rpz-client-ip CNAME rpz-tcp-only.
example.com CNAME rpz-tcp-only.
*.example.com CNAME rpz-tcp-only.
</pre>
<p>
RPZ can affect server performance.
Each configured response policy zone requires the server to
perform one to four additional database lookups before a
query can be answered.
For example, a DNS server with four policy zones, each with all
four kinds of response triggers, QNAME, IP, NSIP, and
NSDNAME, requires a total of 17 times as many database
lookups as a similar DNS server with no response policy zones.
A <acronym class="acronym">BIND9</acronym> server with adequate memory and one
response policy zone with QNAME and IP triggers might achieve a
maximum queries-per-second rate about 20% lower.
A server with four response policy zones with QNAME and IP
triggers might have a maximum QPS rate about 50% lower.
</p>
<p>
Responses rewritten by RPZ are counted in the
<span><strong class="command">RPZRewrites</strong></span> statistics.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2591168"></a>Response Rate Limiting</h4></div></div></div>
<p>
Excessive almost identical UDP <span class="emphasis"><em>responses</em></span>
can be controlled by configuring a
<span><strong class="command">rate-limit</strong></span> clause in an
<span><strong class="command">options</strong></span> or <span><strong class="command">view</strong></span> statement.
This mechanism keeps authoritative BIND 9 from being used
in amplifying reflection denial of service (DoS) attacks.
Short truncated (TC=1) responses can be sent to provide
rate-limited responses to legitimate clients within
a range of forged, attacked IP addresses.
Legitimate clients react to dropped or truncated response
by retrying with UDP or with TCP respectively.
</p>
<p>
This mechanism is intended for authoritative DNS servers.
It can be used on recursive servers but can slow
applications such as SMTP servers (mail receivers) and
HTTP clients (web browsers) that repeatedly request the
same domains.
When possible, closing "open" recursive servers is better.
</p>
<p>
Response rate limiting uses a "credit" or "token bucket" scheme.
Each combination of identical response and client
has a conceptual account that earns a specified number
of credits every second.
A prospective response debits its account by one.
Responses are dropped or truncated
while the account is negative.
Responses are tracked within a rolling window of time
which defaults to 15 seconds, but can be configured with
the <span><strong class="command">window</strong></span> option to any value from
1 to 3600 seconds (1 hour).
The account cannot become more positive than
the per-second limit
or more negative than <span><strong class="command">window</strong></span>
times the per-second limit.
When the specified number of credits for a class of
responses is set to 0, those responses are not rate limited.
</p>
<p>
The notions of "identical response" and "DNS client"
for rate limiting are not simplistic.
All responses to an address block are counted as if to a
single client.
The prefix lengths of addresses blocks are
specified with <span><strong class="command">ipv4-prefix-length</strong></span> (default 24)
and <span><strong class="command">ipv6-prefix-length</strong></span> (default 56).
</p>
<p>
All non-empty responses for a valid domain name (qname)
and record type (qtype) are identical and have a limit specified
with <span><strong class="command">responses-per-second</strong></span>
(default 0 or no limit).
All empty (NODATA) responses for a valid domain,
regardless of query type, are identical.
Responses in the NODATA class are limited by
<span><strong class="command">nodata-per-second</strong></span>
(default <span><strong class="command">responses-per-second</strong></span>).
Requests for any and all undefined subdomains of a given
valid domain result in NXDOMAIN errors, and are identical
regardless of query type.
They are limited by <span><strong class="command">nxdomains-per-second</strong></span>
(default <span><strong class="command">responses-per-second</strong></span>).
This controls some attacks using random names, but
can be relaxed or turned off (set to 0)
on servers that expect many legitimate
NXDOMAIN responses, such as from anti-spam blacklists.
Referrals or delegations to the server of a given
domain are identical and are limited by
<span><strong class="command">referrals-per-second</strong></span>
(default <span><strong class="command">responses-per-second</strong></span>).
</p>
<p>
Responses generated from local wildcards are counted and limited
as if they were for the parent domain name.
This controls flooding using random.wild.example.com.
</p>
<p>
All requests that result in DNS errors other
than NXDOMAIN, such as SERVFAIL and FORMERR, are identical
regardless of requested name (qname) or record type (qtype).
This controls attacks using invalid requests or distant,
broken authoritative servers.
By default the limit on errors is the same as the
<span><strong class="command">responses-per-second</strong></span> value,
but it can be set separately with
<span><strong class="command">errors-per-second</strong></span>.
</p>
<p>
Many attacks using DNS involve UDP requests with forged source
addresses.
Rate limiting prevents the use of BIND 9 to flood a network
with responses to requests with forged source addresses,
but could let a third party block responses to legitimate requests.
There is a mechanism that can answer some legitimate
requests from a client whose address is being forged in a flood.
Setting <span><strong class="command">slip</strong></span> to 2 (its default) causes every
other UDP request to be answered with a small truncated (TC=1)
response.
The small size and reduced frequency, and so lack of
amplification, of "slipped" responses make them unattractive
for reflection DoS attacks.
<span><strong class="command">slip</strong></span> must be between 0 and 10.
A value of 0 does not "slip":
no truncated responses are sent due to rate limiting,
all responses are dropped.
A value of 1 causes every response to slip;
values between 2 and 10 cause every n'th response to slip.
Some error responses including REFUSED and SERVFAIL
cannot be replaced with truncated responses and are instead
leaked at the <span><strong class="command">slip</strong></span> rate.
</p>
<p>
(NOTE: Dropped responses from an authoritative server may
reduce the difficulty of a third party successfully forging
a response to a recursive resolver. The best security
against forged responses is for authoritative operators
to sign their zones using DNSSEC and for resolver operators
to validate the responses. When this is not an option,
operators who are more concerned with response integrity
than with flood mitigation may consider setting
<span><strong class="command">slip</strong></span> to 1, causing all rate-limited
responses to be truncated rather than dropped. This reduces
the effectiveness of rate-limiting against reflection attacks.)
</p>
<p>
When the approximate query per second rate exceeds
the <span><strong class="command">qps-scale</strong></span> value,
then the <span><strong class="command">responses-per-second</strong></span>,
<span><strong class="command">errors-per-second</strong></span>,
<span><strong class="command">nxdomains-per-second</strong></span> and
<span><strong class="command">all-per-second</strong></span> values are reduced by the
ratio of the current rate to the <span><strong class="command">qps-scale</strong></span> value.
This feature can tighten defenses during attacks.
For example, with
<span><strong class="command">qps-scale 250; responses-per-second 20;</strong></span> and
a total query rate of 1000 queries/second for all queries from
all DNS clients including via TCP,
then the effective responses/second limit changes to
(250/1000)*20 or 5.
Responses sent via TCP are not limited
but are counted to compute the query per second rate.
</p>
<p>
The optional <span><strong class="command">domain</strong></span> clause specifies
the namespace to which rate limits will apply. It
is possible to use different rate limits for different names
by specifying multiple <span><strong class="command">rate-limit</strong></span> blocks
with different <span><strong class="command">domain</strong></span> clauses.
The <span><strong class="command">rate-limit</strong></span> statement's
<span><strong class="command">domain</strong></span> most closely matches the query
name will be the one applied to a given query.
</p>
<p>
Rate limiters for different name spaces maintain
separate counters: If, for example, there is a
<span><strong class="command">rate-limit</strong></span> statement for "com" and
another for "example.com", queries matching "example.com"
will not be debited against the rate limiter for "com".
</p>
<p>
If a <span><strong class="command">rate-limit</strong></span> statement does not specify a
<span><strong class="command">domain</strong></span>, then it applies to the root domain
(".") and thus affects the entire DNS namespace, except those
portions covered by other <span><strong class="command">rate-limit</strong></span>
statements.
</p>
<p>
Communities of DNS clients can be given their own parameters or no
rate limiting by putting
<span><strong class="command">rate-limit</strong></span> statements in <span><strong class="command">view</strong></span>
statements instead of the global <span><strong class="command">option</strong></span>
statement.
A <span><strong class="command">rate-limit</strong></span> statement in a view replaces,
rather than supplementing, a <span><strong class="command">rate-limit</strong></span>
statement among the main options.
DNS clients within a view can be exempted from rate limits
with the <span><strong class="command">exempt-clients</strong></span> clause.
</p>
<p>
UDP responses of all kinds can be limited with the
<span><strong class="command">all-per-second</strong></span> phrase. This rate
limiting is unlike the rate limiting provided by
<span><strong class="command">responses-per-second</strong></span>,
<span><strong class="command">errors-per-second</strong></span>, and
<span><strong class="command">nxdomains-per-second</strong></span> on a DNS server
which are often invisible to the victim of a DNS
reflection attack. Unless the forged requests of the
attack are the same as the legitimate requests of the
victim, the victim's requests are not affected. Responses
affected by an <span><strong class="command">all-per-second</strong></span> limit
are always dropped; the <span><strong class="command">slip</strong></span> value
has no effect. An <span><strong class="command">all-per-second</strong></span>
limit should be at least 4 times as large as the other
limits, because single DNS clients often send bursts
of legitimate requests. For example, the receipt of a
single mail message can prompt requests from an SMTP
server for NS, PTR, A, and AAAA records as the incoming
SMTP/TCP/IP connection is considered. The SMTP server
can need additional NS, A, AAAA, MX, TXT, and SPF records
as it considers the STMP <span><strong class="command">Mail From</strong></span>
command. Web browsers often repeatedly resolve the
same names that are repeated in HTML &lt;IMG&gt; tags
in a page. <span><strong class="command">all-per-second</strong></span> is similar
to the rate limiting offered by firewalls but often
inferior. Attacks that justify ignoring the contents
of DNS responses are likely to be attacks on the DNS
server itself. They usually should be discarded before
the DNS server spends resources make TCP connections
or parsing DNS requests, but that rate limiting must
be done before the DNS server sees the requests.
</p>
<p>
The maximum size of the table used to track requests and
rate limit responses is set with <span><strong class="command">max-table-size</strong></span>.
Each entry in the table is between 40 and 80 bytes.
The table needs approximately as many entries as the number
of requests received per second.
The default is 20,000.
To reduce the cold start of growing the table,
<span><strong class="command">min-table-size</strong></span> (default 500)
can set the minimum table size.
Enable <span><strong class="command">rate-limit</strong></span> category logging to monitor
expansions of the table and inform
choices for the initial and maximum table size.
</p>
<p>
Use <span><strong class="command">log-only yes</strong></span> to test rate limiting parameters
without actually dropping any requests.
</p>
<p>
Responses dropped by rate limits are included in the
<span><strong class="command">RateDropped</strong></span> and <span><strong class="command">QryDropped</strong></span>
statistics.
Responses that truncated by rate limits are included in
<span><strong class="command">RateSlipped</strong></span> and <span><strong class="command">RespTruncated</strong></span>.
</p>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="server_statement_grammar"></a><span><strong class="command">server</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">server</strong></span> <em class="replaceable"><code>ip_addr[/prefixlen]</code></em> {
[<span class="optional"> bogus <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> provide-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> request-expire <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> request-nsid <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> request-sit <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> edns <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> edns-version <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> nosit-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> tcp-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> transfers <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> transfer-format <em class="replaceable"><code>( one-answer | many-answers )</code></em> ; ]</span>]
[<span class="optional"> keys <em class="replaceable"><code>{ string ; [<span class="optional"> string ; [<span class="optional">...</span>]</span>] }</code></em> ; </span>]
[<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> query-source [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
[<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> query-source-v6 [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
[<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> use-queryport-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> queryport-pool-ports <em class="replaceable"><code>number</code></em>; </span>]
[<span class="optional"> queryport-pool-updateinterval <em class="replaceable"><code>number</code></em>; </span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="server_statement_definition_and_usage"></a><span><strong class="command">server</strong></span> Statement Definition and
Usage</h3></div></div></div>
<p>
The <span><strong class="command">server</strong></span> statement defines
characteristics
to be associated with a remote name server. If a prefix length is
specified, then a range of servers is covered. Only the most
specific
server clause applies regardless of the order in
<code class="filename">named.conf</code>.
</p>
<p>
The <span><strong class="command">server</strong></span> statement can occur at
the top level of the
configuration file or inside a <span><strong class="command">view</strong></span>
statement.
If a <span><strong class="command">view</strong></span> statement contains
one or more <span><strong class="command">server</strong></span> statements, only
those
apply to the view and any top-level ones are ignored.
If a view contains no <span><strong class="command">server</strong></span>
statements,
any top-level <span><strong class="command">server</strong></span> statements are
used as
defaults.
</p>
<p>
If you discover that a remote server is giving out bad data,
marking it as bogus will prevent further queries to it. The
default
value of <span><strong class="command">bogus</strong></span> is <span><strong class="command">no</strong></span>.
</p>
<p>
The <span><strong class="command">provide-ixfr</strong></span> clause determines
whether
the local server, acting as master, will respond with an
incremental
zone transfer when the given remote server, a slave, requests it.
If set to <span><strong class="command">yes</strong></span>, incremental transfer
will be provided
whenever possible. If set to <span><strong class="command">no</strong></span>,
all transfers
to the remote server will be non-incremental. If not set, the
value
of the <span><strong class="command">provide-ixfr</strong></span> option in the
view or
global options block is used as a default.
</p>
<p>
The <span><strong class="command">request-ixfr</strong></span> clause determines
whether
the local server, acting as a slave, will request incremental zone
transfers from the given remote server, a master. If not set, the
value of the <span><strong class="command">request-ixfr</strong></span> option in
the view or global options block is used as a default. It may
also be set in the zone block and, if set there, it will
override the global or view setting for that zone.
</p>
<p>
IXFR requests to servers that do not support IXFR will
automatically
fall back to AXFR. Therefore, there is no need to manually list
which servers support IXFR and which ones do not; the global
default
of <span><strong class="command">yes</strong></span> should always work.
The purpose of the <span><strong class="command">provide-ixfr</strong></span> and
<span><strong class="command">request-ixfr</strong></span> clauses is
to make it possible to disable the use of IXFR even when both
master
and slave claim to support it, for example if one of the servers
is buggy and crashes or corrupts data when IXFR is used.
</p>
<p>
The <span><strong class="command">request-expire</strong></span> clause determines
whether the local server, when acting as a slave, will
request the EDNS EXPIRE value. The EDNS EXPIRE value
indicates the remaining time before the zone data will
expire and need to be be refreshed. This is used
when a secondary server transfers a zone from another
secondary server; when transferring from the primary, the
expiration timer is set from the EXPIRE field of the SOA
record instead.
The default is <span><strong class="command">yes</strong></span>.
</p>
<p>
The <span><strong class="command">edns</strong></span> clause determines whether
the local server will attempt to use EDNS when communicating
with the remote server. The default is <span><strong class="command">yes</strong></span>.
</p>
<p>
The <span><strong class="command">edns-udp-size</strong></span> option sets the
EDNS UDP size that is advertised by <span><strong class="command">named</strong></span>
when querying the remote server. Valid values are 512
to 4096 bytes (values outside this range will be silently
adjusted to the nearest value within it). This option
is useful when you wish to advertise a different value
to this server than the value you advertise globally,
for example, when there is a firewall at the remote
site that is blocking large replies.
</p>
<p>
The <span><strong class="command">edns-version</strong></span> option sets the
maximum EDNS VERSION that will be sent to the server(s)
by the resolver. The actual EDNS version sent is still
subject to normal EDNS version negotiation rules (see
RFC 6891), the maximum EDNS version supported by the
server, and any other heuristics that indicate that a
lower version should be sent. This option is intended
to be used when a remote server reacts badly to a given
EDNS version or higher; it should be set to the highest
version the remote server is known to support. Valid
values are 0 to 255; higher values will be silently
adjusted. This option will not be needed until higher
EDNS versions than 0 are in use.
</p>
<p>
The <span><strong class="command">max-udp-size</strong></span> option sets the
maximum EDNS UDP message size <span><strong class="command">named</strong></span>
will send. Valid values are 512 to 4096 bytes (values
outside this range will be silently adjusted). This
option is useful when you know that there is a firewall
that is blocking large replies from <span><strong class="command">named</strong></span>.
</p>
<p>
The <span><strong class="command">nosit-udp-size</strong></span> option sets the
maximum size of UDP responses that will be sent to
queries without a valid source identity token. The command
<span><strong class="command">max-udp-size</strong></span> option may further limit
the response size.
</p>
<p>
The <span><strong class="command">tcp-only</strong></span> option sets the transport
protocol to TCP. The default is to use the UDP transport
and to fallback on TCP only when a truncated response
is received.
</p>
<p>
The server supports two zone transfer methods. The first, <span><strong class="command">one-answer</strong></span>,
uses one DNS message per resource record transferred. <span><strong class="command">many-answers</strong></span> packs
as many resource records as possible into a message. <span><strong class="command">many-answers</strong></span> is
more efficient, but is only known to be understood by <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym>
8.x, and patched versions of <acronym class="acronym">BIND</acronym>
4.9.5. You can specify which method
to use for a server with the <span><strong class="command">transfer-format</strong></span> option.
If <span><strong class="command">transfer-format</strong></span> is not
specified, the <span><strong class="command">transfer-format</strong></span>
specified
by the <span><strong class="command">options</strong></span> statement will be
used.
</p>
<p><span><strong class="command">transfers</strong></span>
is used to limit the number of concurrent inbound zone
transfers from the specified server. If no
<span><strong class="command">transfers</strong></span> clause is specified, the
limit is set according to the
<span><strong class="command">transfers-per-ns</strong></span> option.
</p>
<p>
The <span><strong class="command">keys</strong></span> clause identifies a
<span><strong class="command">key_id</strong></span> defined by the <span><strong class="command">key</strong></span> statement,
to be used for transaction security (TSIG, <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called &#8220;TSIG&#8221;</a>)
when talking to the remote server.
When a request is sent to the remote server, a request signature
will be generated using the key specified here and appended to the
message. A request originating from the remote server is not
required
to be signed by this key.
</p>
<p>
Although the grammar of the <span><strong class="command">keys</strong></span>
clause
allows for multiple keys, only a single key per server is
currently
supported.
</p>
<p>
The <span><strong class="command">transfer-source</strong></span> and
<span><strong class="command">transfer-source-v6</strong></span> clauses specify
the IPv4 and IPv6 source
address to be used for zone transfer with the remote server,
respectively.
For an IPv4 remote server, only <span><strong class="command">transfer-source</strong></span> can
be specified.
Similarly, for an IPv6 remote server, only
<span><strong class="command">transfer-source-v6</strong></span> can be
specified.
For more details, see the description of
<span><strong class="command">transfer-source</strong></span> and
<span><strong class="command">transfer-source-v6</strong></span> in
<a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p>
<p>
The <span><strong class="command">notify-source</strong></span> and
<span><strong class="command">notify-source-v6</strong></span> clauses specify the
IPv4 and IPv6 source address to be used for notify
messages sent to remote servers, respectively. For an
IPv4 remote server, only <span><strong class="command">notify-source</strong></span>
can be specified. Similarly, for an IPv6 remote server,
only <span><strong class="command">notify-source-v6</strong></span> can be specified.
</p>
<p>
The <span><strong class="command">query-source</strong></span> and
<span><strong class="command">query-source-v6</strong></span> clauses specify the
IPv4 and IPv6 source address to be used for queries
sent to remote servers, respectively. For an IPv4
remote server, only <span><strong class="command">query-source</strong></span> can
be specified. Similarly, for an IPv6 remote server,
only <span><strong class="command">query-source-v6</strong></span> can be specified.
</p>
<p>
The <span><strong class="command">request-nsid</strong></span> clause determines
whether the local server will add a NSID EDNS option
to requests sent to the server. This overrides
<span><strong class="command">request-nsid</strong></span> set at the view or
option level.
</p>
<p>
The <span><strong class="command">request-sit</strong></span> clause determines
whether the local server will add a SIT EDNS option
to requests sent to the server. This overrides
<span><strong class="command">request-sit</strong></span> set at the view or
option level. The <span><strong class="command">named</strong></span> server may
determine that SIT is not supported by the remote server
and not add a SIT EDNS option to requests.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="statschannels"></a><span><strong class="command">statistics-channels</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">statistics-channels</strong></span> {
[ inet ( ip_addr | * ) [ port ip_port ]
[ allow { <em class="replaceable"><code> address_match_list </code></em> } ]; ]
[ inet ...; ]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2592668"></a><span><strong class="command">statistics-channels</strong></span> Statement Definition and
Usage</h3></div></div></div>
<p>
The <span><strong class="command">statistics-channels</strong></span> statement
declares communication channels to be used by system
administrators to get access to statistics information of
the name server.
</p>
<p>
This statement intends to be flexible to support multiple
communication protocols in the future, but currently only
HTTP access is supported.
It requires that BIND 9 be compiled with libxml2 and/or
json-c (also known as libjson0); the
<span><strong class="command">statistics-channels</strong></span> statement is
still accepted even if it is built without the library,
but any HTTP access will fail with an error.
</p>
<p>
An <span><strong class="command">inet</strong></span> control channel is a TCP socket
listening at the specified <span><strong class="command">ip_port</strong></span> on the
specified <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6
address. An <span><strong class="command">ip_addr</strong></span> of <code class="literal">*</code>
(asterisk) is
interpreted as the IPv4 wildcard address; connections will be
accepted on any of the system's IPv4 addresses.
To listen on the IPv6 wildcard address,
use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>.
</p>
<p>
If no port is specified, port 80 is used for HTTP channels.
The asterisk "<code class="literal">*</code>" cannot be used for
<span><strong class="command">ip_port</strong></span>.
</p>
<p>
The attempt of opening a statistics channel is
restricted by the optional <span><strong class="command">allow</strong></span> clause.
Connections to the statistics channel are permitted based on the
<span><strong class="command">address_match_list</strong></span>.
If no <span><strong class="command">allow</strong></span> clause is present,
<span><strong class="command">named</strong></span> accepts connection
attempts from any address; since the statistics may
contain sensitive internal information, it is highly
recommended to restrict the source of connection requests
appropriately.
</p>
<p>
If no <span><strong class="command">statistics-channels</strong></span> statement is present,
<span><strong class="command">named</strong></span> will not open any communication channels.
</p>
<p>
The statistics are available in various formats and views
depending on the URI used to access them. For example, if
the statistics channel is configured to listen on 127.0.0.1
port 8888, then the statistics are accessible in XML format at
<a href="http://127.0.0.1:8888/" target="_top">http://127.0.0.1:8888/</a> or
<a href="http://127.0.0.1:8888/xml" target="_top">http://127.0.0.1:8888/xml</a>. A CSS file is
included which can format the XML statistics into tables
when viewed with a stylesheet-capable browser, and into
charts and graphs using the Google Charts API when using a
javascript-capable browser.
</p>
<p>
Applications that depend on a particular XML schema
can request
<a href="http://127.0.0.1:8888/xml/v2" target="_top">http://127.0.0.1:8888/xml/v2</a> for version 2
of the statistics XML schema or
<a href="http://127.0.0.1:8888/xml/v3" target="_top">http://127.0.0.1:8888/xml/v3</a> for version 3.
If the requested schema is supported by the server, then
it will respond; if not, it will return a "page not found"
error.
</p>
<p>
Broken-out subsets of the statistics can be viewed at
<a href="http://127.0.0.1:8888/xml/v3/status" target="_top">http://127.0.0.1:8888/xml/v3/status</a>
(server uptime and last reconfiguration time),
<a href="http://127.0.0.1:8888/xml/v3/server" target="_top">http://127.0.0.1:8888/xml/v3/server</a>
(server and resolver statistics),
<a href="http://127.0.0.1:8888/xml/v3/zones" target="_top">http://127.0.0.1:8888/xml/v3/zones</a>
(zone statistics),
<a href="http://127.0.0.1:8888/xml/v3/net" target="_top">http://127.0.0.1:8888/xml/v3/net</a>
(network status and socket statistics),
<a href="http://127.0.0.1:8888/xml/v3/mem" target="_top">http://127.0.0.1:8888/xml/v3/mem</a>
(memory manager statistics),
<a href="http://127.0.0.1:8888/xml/v3/tasks" target="_top">http://127.0.0.1:8888/xml/v3/tasks</a>
(task manager statistics).
</p>
<p>
The full set of statistics can also be read in JSON format at
<a href="http://127.0.0.1:8888/json" target="_top">http://127.0.0.1:8888/json</a>,
with the broken-out subsets at
<a href="http://127.0.0.1:8888/json/v1/status" target="_top">http://127.0.0.1:8888/json/v1/status</a>
(server uptime and last reconfiguration time),
<a href="http://127.0.0.1:8888/json/v1/server" target="_top">http://127.0.0.1:8888/json/v1/server</a>
(server and resolver statistics),
<a href="http://127.0.0.1:8888/json/v1/zones" target="_top">http://127.0.0.1:8888/json/v1/zones</a>
(zone statistics),
<a href="http://127.0.0.1:8888/json/v1/net" target="_top">http://127.0.0.1:8888/json/v1/net</a>
(network status and socket statistics),
<a href="http://127.0.0.1:8888/json/v1/mem" target="_top">http://127.0.0.1:8888/json/v1/mem</a>
(memory manager statistics),
<a href="http://127.0.0.1:8888/json/v1/tasks" target="_top">http://127.0.0.1:8888/json/v1/tasks</a>
(task manager statistics).
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="trusted-keys"></a><span><strong class="command">trusted-keys</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">trusted-keys</strong></span> {
<em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ;
[<span class="optional"> <em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; [<span class="optional">...</span>]</span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2593085"></a><span><strong class="command">trusted-keys</strong></span> Statement Definition
and Usage</h3></div></div></div>
<p>
The <span><strong class="command">trusted-keys</strong></span> statement defines
DNSSEC security roots. DNSSEC is described in <a href="Bv9ARM.ch04.html#DNSSEC" title="DNSSEC">the section called &#8220;DNSSEC&#8221;</a>. A security root is defined when the
public key for a non-authoritative zone is known, but
cannot be securely obtained through DNS, either because
it is the DNS root zone or because its parent zone is
unsigned. Once a key has been configured as a trusted
key, it is treated as if it had been validated and
proven secure. The resolver attempts DNSSEC validation
on all DNS data in subdomains of a security root.
</p>
<p>
All keys (and corresponding zones) listed in
<span><strong class="command">trusted-keys</strong></span> are deemed to exist regardless
of what parent zones say. Similarly for all keys listed in
<span><strong class="command">trusted-keys</strong></span> only those keys are
used to validate the DNSKEY RRset. The parent's DS RRset
will not be used.
</p>
<p>
The <span><strong class="command">trusted-keys</strong></span> statement can contain
multiple key entries, each consisting of the key's
domain name, flags, protocol, algorithm, and the Base-64
representation of the key data.
Spaces, tabs, newlines and carriage returns are ignored
in the key data, so the configuration may be split up into
multiple lines.
</p>
<p>
<span><strong class="command">trusted-keys</strong></span> may be set at the top level
of <code class="filename">named.conf</code> or within a view. If it is
set in both places, they are additive: keys defined at the top
level are inherited by all views, but keys defined in a view
are only used within that view.
</p>
<p>
Validation below specified names can be temporarily disabled
by using <span><strong class="command">rndc nta</strong></span>.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2593139"></a><span><strong class="command">managed-keys</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">managed-keys</strong></span> {
<em class="replaceable"><code>name</code></em> initial-key <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key-data</code></em> ;
[<span class="optional"> <em class="replaceable"><code>name</code></em> initial-key <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key-data</code></em> ; [<span class="optional">...</span>]</span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="managed-keys"></a><span><strong class="command">managed-keys</strong></span> Statement Definition
and Usage</h3></div></div></div>
<p>
The <span><strong class="command">managed-keys</strong></span> statement, like
<span><strong class="command">trusted-keys</strong></span>, defines DNSSEC
security roots. The difference is that
<span><strong class="command">managed-keys</strong></span> can be kept up to date
automatically, without intervention from the resolver
operator.
</p>
<p>
Suppose, for example, that a zone's key-signing
key was compromised, and the zone owner had to revoke and
replace the key. A resolver which had the old key in a
<span><strong class="command">trusted-keys</strong></span> statement would be
unable to validate this zone any longer; it would
reply with a SERVFAIL response code. This would
continue until the resolver operator had updated the
<span><strong class="command">trusted-keys</strong></span> statement with the new key.
</p>
<p>
If, however, the zone were listed in a
<span><strong class="command">managed-keys</strong></span> statement instead, then the
zone owner could add a "stand-by" key to the zone in advance.
<span><strong class="command">named</strong></span> would store the stand-by key, and
when the original key was revoked, <span><strong class="command">named</strong></span>
would be able to transition smoothly to the new key. It would
also recognize that the old key had been revoked, and cease
using that key to validate answers, minimizing the damage that
the compromised key could do.
</p>
<p>
A <span><strong class="command">managed-keys</strong></span> statement contains a list of
the keys to be managed, along with information about how the
keys are to be initialized for the first time. The only
initialization method currently supported (as of
<acronym class="acronym">BIND</acronym> 9.7.0) is <code class="literal">initial-key</code>.
This means the <span><strong class="command">managed-keys</strong></span> statement must
contain a copy of the initializing key. (Future releases may
allow keys to be initialized by other methods, eliminating this
requirement.)
</p>
<p>
Consequently, a <span><strong class="command">managed-keys</strong></span> statement
appears similar to a <span><strong class="command">trusted-keys</strong></span>, differing
in the presence of the second field, containing the keyword
<code class="literal">initial-key</code>. The difference is, whereas the
keys listed in a <span><strong class="command">trusted-keys</strong></span> continue to be
trusted until they are removed from
<code class="filename">named.conf</code>, an initializing key listed
in a <span><strong class="command">managed-keys</strong></span> statement is only trusted
<span class="emphasis"><em>once</em></span>: for as long as it takes to load the
managed key database and start the RFC 5011 key maintenance
process.
</p>
<p>
The first time <span><strong class="command">named</strong></span> runs with a managed key
configured in <code class="filename">named.conf</code>, it fetches the
DNSKEY RRset directly from the zone apex, and validates it
using the key specified in the <span><strong class="command">managed-keys</strong></span>
statement. If the DNSKEY RRset is validly signed, then it is
used as the basis for a new managed keys database.
</p>
<p>
From that point on, whenever <span><strong class="command">named</strong></span> runs, it
sees the <span><strong class="command">managed-keys</strong></span> statement, checks to
make sure RFC 5011 key maintenance has already been initialized
for the specified domain, and if so, it simply moves on. The
key specified in the <span><strong class="command">managed-keys</strong></span> is not
used to validate answers; it has been superseded by the key or
keys stored in the managed keys database.
</p>
<p>
The next time <span><strong class="command">named</strong></span> runs after a name
has been <span class="emphasis"><em>removed</em></span> from the
<span><strong class="command">managed-keys</strong></span> statement, the corresponding
zone will be removed from the managed keys database,
and RFC 5011 key maintenance will no longer be used for that
domain.
</p>
<p>
<span><strong class="command">named</strong></span> only maintains a single managed keys
database; consequently, unlike <span><strong class="command">trusted-keys</strong></span>,
<span><strong class="command">managed-keys</strong></span> may only be set at the top
level of <code class="filename">named.conf</code>, not within a view.
</p>
<p>
In the current implementation, the managed keys database is
stored as a master-format zone file called
<code class="filename">managed-keys.bind</code>. When the key database
is changed, the zone is updated. As with any other dynamic
zone, changes will be written into a journal file,
<code class="filename">managed-keys.bind.jnl</code>. They are committed
to the master file as soon as possible afterward; in the case
of the managed key database, this will usually occur within 30
seconds. So, whenever <span><strong class="command">named</strong></span> is using
automatic key maintenance, those two files can be expected to
exist in the working directory. (For this reason among others,
the working directory should be always be writable by
<span><strong class="command">named</strong></span>.)
</p>
<p>
If the <span><strong class="command">dnssec-validation</strong></span> option is
set to <strong class="userinput"><code>auto</code></strong>, <span><strong class="command">named</strong></span>
will automatically initialize a managed key for the
root zone. Similarly, if the <span><strong class="command">dnssec-lookaside</strong></span>
option is set to <strong class="userinput"><code>auto</code></strong>,
<span><strong class="command">named</strong></span> will automatically initialize
a managed key for the zone <code class="literal">dlv.isc.org</code>.
In both cases, the key that is used to initialize the key
maintenance process is built into <span><strong class="command">named</strong></span>,
and can be overridden from <span><strong class="command">bindkeys-file</strong></span>.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="view_statement_grammar"></a><span><strong class="command">view</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">view</strong></span> <em class="replaceable"><code>view_name</code></em>
[<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
match-clients { <em class="replaceable"><code>address_match_list</code></em> };
match-destinations { <em class="replaceable"><code>address_match_list</code></em> };
match-recursive-only <em class="replaceable"><code>yes_or_no</code></em> ;
[<span class="optional"> <em class="replaceable"><code>view_option</code></em>; ...</span>]
[<span class="optional"> <em class="replaceable"><code>zone_statement</code></em>; ...</span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2593574"></a><span><strong class="command">view</strong></span> Statement Definition and Usage</h3></div></div></div>
<p>
The <span><strong class="command">view</strong></span> statement is a powerful
feature
of <acronym class="acronym">BIND</acronym> 9 that lets a name server
answer a DNS query differently
depending on who is asking. It is particularly useful for
implementing
split DNS setups without having to run multiple servers.
</p>
<p>
Each <span><strong class="command">view</strong></span> statement defines a view
of the
DNS namespace that will be seen by a subset of clients. A client
matches
a view if its source IP address matches the
<code class="varname">address_match_list</code> of the view's
<span><strong class="command">match-clients</strong></span> clause and its
destination IP address matches
the <code class="varname">address_match_list</code> of the
view's
<span><strong class="command">match-destinations</strong></span> clause. If not
specified, both
<span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span>
default to matching all addresses. In addition to checking IP
addresses
<span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span>
can also take <span><strong class="command">keys</strong></span> which provide an
mechanism for the
client to select the view. A view can also be specified
as <span><strong class="command">match-recursive-only</strong></span>, which
means that only recursive
requests from matching clients will match that view.
The order of the <span><strong class="command">view</strong></span> statements is
significant &#8212;
a client request will be resolved in the context of the first
<span><strong class="command">view</strong></span> that it matches.
</p>
<p>
Zones defined within a <span><strong class="command">view</strong></span>
statement will
only be accessible to clients that match the <span><strong class="command">view</strong></span>.
By defining a zone of the same name in multiple views, different
zone data can be given to different clients, for example,
"internal"
and "external" clients in a split DNS setup.
</p>
<p>
Many of the options given in the <span><strong class="command">options</strong></span> statement
can also be used within a <span><strong class="command">view</strong></span>
statement, and then
apply only when resolving queries with that view. When no
view-specific
value is given, the value in the <span><strong class="command">options</strong></span> statement
is used as a default. Also, zone options can have default values
specified
in the <span><strong class="command">view</strong></span> statement; these
view-specific defaults
take precedence over those in the <span><strong class="command">options</strong></span> statement.
</p>
<p>
Views are class specific. If no class is given, class IN
is assumed. Note that all non-IN views must contain a hint zone,
since only the IN class has compiled-in default hints.
</p>
<p>
If there are no <span><strong class="command">view</strong></span> statements in
the config
file, a default view that matches any client is automatically
created
in class IN. Any <span><strong class="command">zone</strong></span> statements
specified on
the top level of the configuration file are considered to be part
of
this default view, and the <span><strong class="command">options</strong></span>
statement will
apply to the default view. If any explicit <span><strong class="command">view</strong></span>
statements are present, all <span><strong class="command">zone</strong></span>
statements must
occur inside <span><strong class="command">view</strong></span> statements.
</p>
<p>
Here is an example of a typical split DNS setup implemented
using <span><strong class="command">view</strong></span> statements:
</p>
<pre class="programlisting">view "internal" {
// This should match our internal networks.
match-clients { 10.0.0.0/8; };
// Provide recursive service to internal
// clients only.
recursion yes;
// Provide a complete view of the example.com
// zone including addresses of internal hosts.
zone "example.com" {
type master;
file "example-internal.db";
};
};
view "external" {
// Match all clients not matched by the
// previous view.
match-clients { any; };
// Refuse recursive service to external clients.
recursion no;
// Provide a restricted view of the example.com
// zone containing only publicly accessible hosts.
zone "example.com" {
type master;
file "example-external.db";
};
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zone_statement_grammar"></a><span><strong class="command">zone</strong></span>
Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">zone</strong></span> <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type master;
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> dnssec-dnskey-kskonly <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> dnssec-loadkeys-interval <em class="replaceable"><code>number</code></em>; </span>]
[<span class="optional"> update-policy <em class="replaceable"><code>local</code></em> | { <em class="replaceable"><code>update_policy_rule</code></em> [<span class="optional">...</span>] }; </span>]
[<span class="optional"> also-notify { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ;
[<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> check-mx (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> check-spf ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
[<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>]
[<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
[<span class="optional"> journal <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> max-journal-size <em class="replaceable"><code>size_spec</code></em>; </span>]
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> ixfr-base <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> ixfr-from-differences <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> ixfr-tmp-file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <em class="replaceable"><code>master-only</code></em> ; </span>]
[<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>]
[<span class="optional"> notify-to-soa <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</code></em>; </span>]
[<span class="optional"> sig-validity-interval <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>number</code></em></span>] ; </span>]
[<span class="optional"> sig-signing-nodes <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> sig-signing-signatures <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> sig-signing-type <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> database <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> key-directory <em class="replaceable"><code>path_name</code></em>; </span>]
[<span class="optional"> auto-dnssec <code class="constant">allow</code>|<code class="constant">maintain</code>|<code class="constant">off</code>; </span>]
[<span class="optional"> inline-signing <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> serial-update-method <code class="constant">increment</code>|<code class="constant">unixtime</code>|<code class="constant">date</code>; </span>]
[<span class="optional"> max-zone-ttl <em class="replaceable"><code>number</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type slave;
[<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> dnssec-update-mode ( <em class="replaceable"><code>maintain</code></em> | <em class="replaceable"><code>no-resign</code></em> ); </span>]
[<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> dnssec-dnskey-kskonly <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> dnssec-loadkeys-interval <em class="replaceable"><code>number</code></em>; </span>]
[<span class="optional"> dnssec-secure-to-insecure <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> try-tcp-refresh <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> also-notify [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em>
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
[<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>]
[<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
[<span class="optional"> journal <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> max-journal-size <em class="replaceable"><code>size_spec</code></em>; </span>]
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> ixfr-base <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> ixfr-from-differences <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> ixfr-tmp-file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em>
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
[<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>]
[<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <em class="replaceable"><code>master-only</code></em> ; </span>]
[<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>]
[<span class="optional"> notify-to-soa <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</code></em>; </span>]
[<span class="optional"> sig-validity-interval <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>number</code></em></span>] ; </span>]
[<span class="optional"> sig-signing-nodes <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> sig-signing-signatures <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> sig-signing-type <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> database <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> key-directory <em class="replaceable"><code>path_name</code></em>; </span>]
[<span class="optional"> auto-dnssec <code class="constant">allow</code>|<code class="constant">maintain</code>|<code class="constant">off</code>; </span>]
[<span class="optional"> inline-signing <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> multi-master <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type hint;
file <em class="replaceable"><code>string</code></em> ;
[<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>] // Not Implemented.
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type stub;
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>]
[<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em>
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
[<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>]
[<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> database <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> multi-master <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type static-stub;
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> server-addresses { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> ; ... </span>] }; </span>]
[<span class="optional"> server-names { [<span class="optional"> <em class="replaceable"><code>namelist</code></em> </span>] }; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type forward;
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>"."</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type redirect;
file <em class="replaceable"><code>string</code></em> ;
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> max-zone-ttl <em class="replaceable"><code>number</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type delegation-only;
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
[<span class="optional"> in-view <em class="replaceable"><code>string</code></em> ; </span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2595590"></a><span><strong class="command">zone</strong></span> Statement Definition and Usage</h3></div></div></div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2595597"></a>Zone Types</h4></div></div></div>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="varname">master</code>
</p>
</td>
<td>
<p>
The server has a master copy of the data
for the zone and will be able to provide authoritative
answers for
it.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">slave</code>
</p>
</td>
<td>
<p>
A slave zone is a replica of a master
zone. The <span><strong class="command">masters</strong></span> list
specifies one or more IP addresses
of master servers that the slave contacts to update
its copy of the zone.
Masters list elements can also be names of other
masters lists.
By default, transfers are made from port 53 on the
servers; this can
be changed for all servers by specifying a port number
before the
list of IP addresses, or on a per-server basis after
the IP address.
Authentication to the master can also be done with
per-server TSIG keys.
If a file is specified, then the
replica will be written to this file whenever the zone
is changed,
and reloaded from this file on a server restart. Use
of a file is
recommended, since it often speeds server startup and
eliminates
a needless waste of bandwidth. Note that for large
numbers (in the
tens or hundreds of thousands) of zones per server, it
is best to
use a two-level naming scheme for zone filenames. For
example,
a slave server for the zone <code class="literal">example.com</code> might place
the zone contents into a file called
<code class="filename">ex/example.com</code> where <code class="filename">ex/</code> is
just the first two letters of the zone name. (Most
operating systems
behave very slowly if you put 100000 files into
a single directory.)
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">stub</code>
</p>
</td>
<td>
<p>
A stub zone is similar to a slave zone,
except that it replicates only the NS records of a
master zone instead
of the entire zone. Stub zones are not a standard part
of the DNS;
they are a feature specific to the <acronym class="acronym">BIND</acronym> implementation.
</p>
<p>
Stub zones can be used to eliminate the need for glue
NS record
in a parent zone at the expense of maintaining a stub
zone entry and
a set of name server addresses in <code class="filename">named.conf</code>.
This usage is not recommended for new configurations,
and BIND 9
supports it only in a limited way.
In <acronym class="acronym">BIND</acronym> 4/8, zone
transfers of a parent zone
included the NS records from stub children of that
zone. This meant
that, in some cases, users could get away with
configuring child stubs
only in the master server for the parent zone. <acronym class="acronym">BIND</acronym>
9 never mixes together zone data from different zones
in this
way. Therefore, if a <acronym class="acronym">BIND</acronym> 9 master serving a parent
zone has child stub zones configured, all the slave
servers for the
parent zone also need to have the same child stub
zones
configured.
</p>
<p>
Stub zones can also be used as a way of forcing the
resolution
of a given domain to use a particular set of
authoritative servers.
For example, the caching name servers on a private
network using
RFC1918 addressing may be configured with stub zones
for
<code class="literal">10.in-addr.arpa</code>
to use a set of internal name servers as the
authoritative
servers for that domain.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">static-stub</code>
</p>
</td>
<td>
<p>
A static-stub zone is similar to a stub zone
with the following exceptions:
the zone data is statically configured, rather
than transferred from a master server;
when recursion is necessary for a query that
matches a static-stub zone, the locally
configured data (nameserver names and glue addresses)
is always used even if different authoritative
information is cached.
</p>
<p>
Zone data is configured via the
<span><strong class="command">server-addresses</strong></span> and
<span><strong class="command">server-names</strong></span> zone options.
</p>
<p>
The zone data is maintained in the form of NS
and (if necessary) glue A or AAAA RRs
internally, which can be seen by dumping zone
databases by <span><strong class="command">rndc dumpdb -all</strong></span>.
The configured RRs are considered local configuration
parameters rather than public data.
Non recursive queries (i.e., those with the RD
bit off) to a static-stub zone are therefore
prohibited and will be responded with REFUSED.
</p>
<p>
Since the data is statically configured, no
zone maintenance action takes place for a static-stub
zone.
For example, there is no periodic refresh
attempt, and an incoming notify message
will be rejected with an rcode of NOTAUTH.
</p>
<p>
Each static-stub zone is configured with
internally generated NS and (if necessary)
glue A or AAAA RRs
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">forward</code>
</p>
</td>
<td>
<p>
A "forward zone" is a way to configure
forwarding on a per-domain basis. A <span><strong class="command">zone</strong></span> statement
of type <span><strong class="command">forward</strong></span> can
contain a <span><strong class="command">forward</strong></span>
and/or <span><strong class="command">forwarders</strong></span>
statement,
which will apply to queries within the domain given by
the zone
name. If no <span><strong class="command">forwarders</strong></span>
statement is present or
an empty list for <span><strong class="command">forwarders</strong></span> is given, then no
forwarding will be done for the domain, canceling the
effects of
any forwarders in the <span><strong class="command">options</strong></span> statement. Thus
if you want to use this type of zone to change the
behavior of the
global <span><strong class="command">forward</strong></span> option
(that is, "forward first"
to, then "forward only", or vice versa, but want to
use the same
servers as set globally) you need to re-specify the
global forwarders.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">hint</code>
</p>
</td>
<td>
<p>
The initial set of root name servers is
specified using a "hint zone". When the server starts
up, it uses
the root hints to find a root name server and get the
most recent
list of root name servers. If no hint zone is
specified for class
IN, the server uses a compiled-in default set of root
servers hints.
Classes other than IN have no built-in defaults hints.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">redirect</code>
</p>
</td>
<td>
<p>
Redirect zones are used to provide answers to
queries when normal resolution would result in
NXDOMAIN being returned.
Only one redirect zone is supported
per view. <span><strong class="command">allow-query</strong></span> can be
used to restrict which clients see these answers.
</p>
<p>
If the client has requested DNSSEC records (DO=1) and
the NXDOMAIN response is signed then no substitution
will occur.
</p>
<p>
To redirect all NXDOMAIN responses to
100.100.100.2 and
2001:ffff:ffff::100.100.100.2, one would
configure a type redirect zone named ".",
with the zone file containing wildcard records
that point to the desired addresses:
<code class="literal">"*. IN A 100.100.100.2"</code>
and
<code class="literal">"*. IN AAAA 2001:ffff:ffff::100.100.100.2"</code>.
</p>
<p>
To redirect all Spanish names (under .ES) one
would use similar entries but with the names
"*.ES." instead of "*.". To redirect all
commercial Spanish names (under COM.ES) one
would use wildcard entries called "*.COM.ES.".
</p>
<p>
Note that the redirect zone supports all
possible types; it is not limited to A and
AAAA records.
</p>
<p>
Because redirect zones are not referenced
directly by name, they are not kept in the
zone lookup table with normal master and slave
zones. Consequently, it is not currently possible
to use
<span><strong class="command">rndc reload
<em class="replaceable"><code>zonename</code></em></strong></span>
to reload a redirect zone. However, when using
<span><strong class="command">rndc reload</strong></span> without specifying
a zone name, redirect zones will be reloaded along
with other zones.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">delegation-only</code>
</p>
</td>
<td>
<p>
This is used to enforce the delegation-only
status of infrastructure zones (e.g. COM,
NET, ORG). Any answer that is received
without an explicit or implicit delegation
in the authority section will be treated
as NXDOMAIN. This does not apply to the
zone apex. This should not be applied to
leaf zones.
</p>
<p>
<code class="varname">delegation-only</code> has no
effect on answers received from forwarders.
</p>
<p>
See caveats in <a href="Bv9ARM.ch06.html#root_delegation_only"><span><strong class="command">root-delegation-only</strong></span></a>.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2596205"></a>Class</h4></div></div></div>
<p>
The zone's name may optionally be followed by a class. If
a class is not specified, class <code class="literal">IN</code> (for <code class="varname">Internet</code>),
is assumed. This is correct for the vast majority of cases.
</p>
<p>
The <code class="literal">hesiod</code> class is
named for an information service from MIT's Project Athena. It
is
used to share information about various systems databases, such
as users, groups, printers and so on. The keyword
<code class="literal">HS</code> is
a synonym for hesiod.
</p>
<p>
Another MIT development is Chaosnet, a LAN protocol created
in the mid-1970s. Zone data for it can be specified with the <code class="literal">CHAOS</code> class.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2596238"></a>Zone Options</h4></div></div></div>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">allow-notify</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">allow-query</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-query-on</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">allow-query-on</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">allow-transfer</strong></span>
in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">allow-update</strong></span>
in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">update-policy</strong></span></span></dt>
<dd><p>
Specifies a "Simple Secure Update" policy. See
<a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">allow-update-forwarding</strong></span>
in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">also-notify</strong></span></span></dt>
<dd><p>
Only meaningful if <span><strong class="command">notify</strong></span>
is
active for this zone. The set of machines that will
receive a
<code class="literal">DNS NOTIFY</code> message
for this zone is made up of all the listed name servers
(other than
the primary master) for the zone plus any IP addresses
specified
with <span><strong class="command">also-notify</strong></span>. A port
may be specified
with each <span><strong class="command">also-notify</strong></span>
address to send the notify
messages to a port other than the default of 53.
A TSIG key may also be specified to cause the
<code class="literal">NOTIFY</code> to be signed by the
given key.
<span><strong class="command">also-notify</strong></span> is not
meaningful for stub zones.
The default is the empty list.
</p></dd>
<dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt>
<dd><p>
This option is used to restrict the character set and
syntax of
certain domain names in master files and/or DNS responses
received from the
network. The default varies according to zone type. For <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>. For <span><strong class="command">slave</strong></span>
zones the default is <span><strong class="command">warn</strong></span>.
It is not implemented for <span><strong class="command">hint</strong></span> zones.
</p></dd>
<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-mx</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-spf</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-spf</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-wildcard</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-integrity</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-sibling</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">zero-no-soa-ttl</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">update-check-ksk</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-update-mode</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">dnssec-update-mode</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
Usage">the section called &#8220;<span><strong class="command">options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-dnskey-kskonly</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">dnssec-dnskey-kskonly</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">try-tcp-refresh</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">try-tcp-refresh</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">database</strong></span></span></dt>
<dd>
<p>
Specify the type of database to be used for storing the
zone data. The string following the <span><strong class="command">database</strong></span> keyword
is interpreted as a list of whitespace-delimited words.
The first word
identifies the database type, and any subsequent words are
passed
as arguments to the database to be interpreted in a way
specific
to the database type.
</p>
<p>
The default is <strong class="userinput"><code>"rbt"</code></strong>, BIND 9's
native in-memory
red-black-tree database. This database does not take
arguments.
</p>
<p>
Other values are possible if additional database drivers
have been linked into the server. Some sample drivers are
included
with the distribution but none are linked in by default.
</p>
</dd>
<dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">dialup</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">delegation-only</strong></span></span></dt>
<dd>
<p>
The flag only applies to forward, hint and stub
zones. If set to <strong class="userinput"><code>yes</code></strong>,
then the zone will also be treated as if it is
also a delegation-only type zone.
</p>
<p>
See caveats in <a href="Bv9ARM.ch06.html#root_delegation_only"><span><strong class="command">root-delegation-only</strong></span></a>.
</p>
</dd>
<dt><span class="term"><span><strong class="command">forward</strong></span></span></dt>
<dd><p>
Only meaningful if the zone has a forwarders
list. The <span><strong class="command">only</strong></span> value causes
the lookup to fail
after trying the forwarders and getting no answer, while <span><strong class="command">first</strong></span> would
allow a normal lookup to be tried.
</p></dd>
<dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt>
<dd><p>
Used to override the list of global forwarders.
If it is not specified in a zone of type <span><strong class="command">forward</strong></span>,
no forwarding is done for the zone and the global options are
not used.
</p></dd>
<dt><span class="term"><span><strong class="command">ixfr-base</strong></span></span></dt>
<dd><p>
Was used in <acronym class="acronym">BIND</acronym> 8 to
specify the name
of the transaction log (journal) file for dynamic update
and IXFR.
<acronym class="acronym">BIND</acronym> 9 ignores the option
and constructs the name of the journal
file by appending "<code class="filename">.jnl</code>"
to the name of the
zone file.
</p></dd>
<dt><span class="term"><span><strong class="command">ixfr-tmp-file</strong></span></span></dt>
<dd><p>
Was an undocumented option in <acronym class="acronym">BIND</acronym> 8.
Ignored in <acronym class="acronym">BIND</acronym> 9.
</p></dd>
<dt><span class="term"><span><strong class="command">journal</strong></span></span></dt>
<dd><p>
Allow the default journal's filename to be overridden.
The default is the zone's filename with "<code class="filename">.jnl</code>" appended.
This is applicable to <span><strong class="command">master</strong></span> and <span><strong class="command">slave</strong></span> zones.
</p></dd>
<dt><span class="term"><span><strong class="command">max-journal-size</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-journal-size</strong></span> in <a href="Bv9ARM.ch06.html#server_resource_limits" title="Server Resource Limits">the section called &#8220;Server Resource Limits&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-time-in</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-transfer-time-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-idle-in</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-transfer-idle-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-time-out</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-transfer-time-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-idle-out</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-transfer-idle-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify-delay</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-to-soa</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify-to-soa</strong></span> in
<a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">pubkey</strong></span></span></dt>
<dd><p>
In <acronym class="acronym">BIND</acronym> 8, this option was
intended for specifying
a public zone key for verification of signatures in DNSSEC
signed
zones when they are loaded from disk. <acronym class="acronym">BIND</acronym> 9 does not verify signatures
on load and ignores the option.
</p></dd>
<dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt>
<dd><p>
If <strong class="userinput"><code>yes</code></strong>, the server will keep
statistical
information for this zone, which can be dumped to the
<span><strong class="command">statistics-file</strong></span> defined in
the server options.
</p></dd>
<dt><span class="term"><span><strong class="command">server-addresses</strong></span></span></dt>
<dd>
<p>
Only meaningful for static-stub zones.
This is a list of IP addresses to which queries
should be sent in recursive resolution for the
zone.
A non empty list for this option will internally
configure the apex NS RR with associated glue A or
AAAA RRs.
</p>
<p>
For example, if "example.com" is configured as a
static-stub zone with 192.0.2.1 and 2001:db8::1234
in a <span><strong class="command">server-addresses</strong></span> option,
the following RRs will be internally configured.
</p>
<pre class="programlisting">example.com. NS example.com.
example.com. A 192.0.2.1
example.com. AAAA 2001:db8::1234</pre>
<p>
These records are internally used to resolve
names under the static-stub zone.
For instance, if the server receives a query for
"www.example.com" with the RD bit on, the server
will initiate recursive resolution and send
queries to 192.0.2.1 and/or 2001:db8::1234.
</p>
</dd>
<dt><span class="term"><span><strong class="command">server-names</strong></span></span></dt>
<dd>
<p>
Only meaningful for static-stub zones.
This is a list of domain names of nameservers that
act as authoritative servers of the static-stub
zone.
These names will be resolved to IP addresses when
<span><strong class="command">named</strong></span> needs to send queries to
these servers.
To make this supplemental resolution successful,
these names must not be a subdomain of the origin
name of static-stub zone.
That is, when "example.net" is the origin of a
static-stub zone, "ns.example" and
"master.example.com" can be specified in the
<span><strong class="command">server-names</strong></span> option, but
"ns.example.net" cannot, and will be rejected by
the configuration parser.
</p>
<p>
A non empty list for this option will internally
configure the apex NS RR with the specified names.
For example, if "example.com" is configured as a
static-stub zone with "ns1.example.net" and
"ns2.example.net"
in a <span><strong class="command">server-names</strong></span> option,
the following RRs will be internally configured.
</p>
<pre class="programlisting">example.com. NS ns1.example.net.
example.com. NS ns2.example.net.
</pre>
<p>
These records are internally used to resolve
names under the static-stub zone.
For instance, if the server receives a query for
"www.example.com" with the RD bit on, the server
initiate recursive resolution,
resolve "ns1.example.net" and/or
"ns2.example.net" to IP addresses, and then send
queries to (one or more of) these addresses.
</p>
</dd>
<dt><span class="term"><span><strong class="command">sig-validity-interval</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">sig-validity-interval</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-nodes</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">sig-signing-nodes</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-signatures</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">sig-signing-signatures</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-type</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">sig-signing-type</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">transfer-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">alt-transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">alt-transfer-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">alt-transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">use-alt-transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">use-alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-source</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt>
<span class="term"><span><strong class="command">min-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">max-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">min-retry-time</strong></span>, </span><span class="term"><span><strong class="command">max-retry-time</strong></span></span>
</dt>
<dd><p>
See the description in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">ixfr-from-differences</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
(Note that the <span><strong class="command">ixfr-from-differences</strong></span>
<strong class="userinput"><code>master</code></strong> and
<strong class="userinput"><code>slave</code></strong> choices are not
available at the zone level.)
</p></dd>
<dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">key-directory</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
Usage">the section called &#8220;<span><strong class="command">options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">auto-dnssec</strong></span></span></dt>
<dd>
<p>
Zones configured for dynamic DNS may also use this
option to allow varying levels of automatic DNSSEC key
management. There are three possible settings:
</p>
<p>
<span><strong class="command">auto-dnssec allow;</strong></span> permits
keys to be updated and the zone fully re-signed
whenever the user issues the command <span><strong class="command">rndc sign
<em class="replaceable"><code>zonename</code></em></strong></span>.
</p>
<p>
<span><strong class="command">auto-dnssec maintain;</strong></span> includes the
above, but also automatically adjusts the zone's DNSSEC
keys on schedule, according to the keys' timing metadata
(see <a href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
<a href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The command
<span><strong class="command">rndc sign
<em class="replaceable"><code>zonename</code></em></strong></span> causes
<span><strong class="command">named</strong></span> to load keys from the key
repository and sign the zone with all keys that are
active.
<span><strong class="command">rndc loadkeys
<em class="replaceable"><code>zonename</code></em></strong></span> causes
<span><strong class="command">named</strong></span> to load keys from the key
repository and schedule key maintenance events to occur
in the future, but it does not sign the full zone
immediately. Note: once keys have been loaded for a
zone the first time, the repository will be searched
for changes periodically, regardless of whether
<span><strong class="command">rndc loadkeys</strong></span> is used. The recheck
interval is defined by
<span><strong class="command">dnssec-loadkeys-interval</strong></span>.)
</p>
<p>
The default setting is <span><strong class="command">auto-dnssec off</strong></span>.
</p>
</dd>
<dt><span class="term"><span><strong class="command">serial-update-method</strong></span></span></dt>
<dd>
<p>
Zones configured for dynamic DNS may use this
option to set the update method that will be used for
the zone serial number in the SOA record.
</p>
<p>
With the default setting of
<span><strong class="command">serial-update-method increment;</strong></span>, the
SOA serial number will be incremented by one each time
the zone is updated.
</p>
<p>
When set to
<span><strong class="command">serial-update-method unixtime;</strong></span>, the
SOA serial number will be set to the number of seconds
since the UNIX epoch, unless the serial number is
already greater than or equal to that value, in which
case it is simply incremented by one.
</p>
<p>
When set to
<span><strong class="command">serial-update-method date;</strong></span>, the
new SOA serial number will be the current date
in the form "YYYYMMDD", followed by two zeroes,
unless the existing serial number is already greater
than or equal to that value, in which case it is
incremented by one.
</p>
</dd>
<dt><span class="term"><span><strong class="command">inline-signing</strong></span></span></dt>
<dd><p>
If <code class="literal">yes</code>, this enables
"bump in the wire" signing of a zone, where a
unsigned zone is transferred in or loaded from
disk and a signed version of the zone is served,
with possibly, a different serial number. This
behaviour is disabled by default.
</p></dd>
<dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">multi-master</strong></span> in
<a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">masterfile-format</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">masterfile-format</strong></span>
in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-zone-ttl</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">max-zone-ttl</strong></span>
in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
Usage">the section called &#8220;<span><strong class="command">options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-secure-to-insecure</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">dnssec-secure-to-insecure</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="dynamic_update_policies"></a>Dynamic Update Policies</h4></div></div></div>
<p><acronym class="acronym">BIND</acronym> 9 supports two alternative
methods of granting clients the right to perform
dynamic updates to a zone, configured by the
<span><strong class="command">allow-update</strong></span> and
<span><strong class="command">update-policy</strong></span> option, respectively.
</p>
<p>
The <span><strong class="command">allow-update</strong></span> clause works the
same way as in previous versions of <acronym class="acronym">BIND</acronym>.
It grants given clients the permission to update any
record of any name in the zone.
</p>
<p>
The <span><strong class="command">update-policy</strong></span> clause
allows more fine-grained control over what updates are
allowed. A set of rules is specified, where each rule
either grants or denies permissions for one or more
names to be updated by one or more identities. If
the dynamic update request message is signed (that is,
it includes either a TSIG or SIG(0) record), the
identity of the signer can be determined.
</p>
<p>
Rules are specified in the <span><strong class="command">update-policy</strong></span>
zone option, and are only meaningful for master zones.
When the <span><strong class="command">update-policy</strong></span> statement
is present, it is a configuration error for the
<span><strong class="command">allow-update</strong></span> statement to be
present. The <span><strong class="command">update-policy</strong></span> statement
only examines the signer of a message; the source
address is not relevant.
</p>
<p>
There is a pre-defined <span><strong class="command">update-policy</strong></span>
rule which can be switched on with the command
<span><strong class="command">update-policy local;</strong></span>.
Switching on this rule in a zone causes
<span><strong class="command">named</strong></span> to generate a TSIG session
key and place it in a file, and to allow that key
to update the zone. (By default, the file is
<code class="filename">/var/run/named/session.key</code>, the key
name is "local-ddns" and the key algorithm is HMAC-SHA256,
but these values are configurable with the
<span><strong class="command">session-keyfile</strong></span>,
<span><strong class="command">session-keyname</strong></span> and
<span><strong class="command">session-keyalg</strong></span> options, respectively).
</p>
<p>
A client running on the local system, and with appropriate
permissions, may read that file and use the key to sign update
requests. The zone's update policy will be set to allow that
key to change any record within the zone. Assuming the
key name is "local-ddns", this policy is equivalent to:
</p>
<pre class="programlisting">update-policy { grant local-ddns zonesub any; };
</pre>
<p>
The command <span><strong class="command">nsupdate -l</strong></span> sends update
requests to localhost, and signs them using the session key.
</p>
<p>
Other rule definitions look like this:
</p>
<pre class="programlisting">
( <span><strong class="command">grant</strong></span> | <span><strong class="command">deny</strong></span> ) <em class="replaceable"><code>identity</code></em> <em class="replaceable"><code>nametype</code></em> [<span class="optional"> <em class="replaceable"><code>name</code></em> </span>] [<span class="optional"> <em class="replaceable"><code>types</code></em> </span>]
</pre>
<p>
Each rule grants or denies privileges. Once a message has
successfully matched a rule, the operation is immediately
granted or denied and no further rules are examined. A rule
is matched when the signer matches the identity field, the
name matches the name field in accordance with the nametype
field, and the type matches the types specified in the type
field.
</p>
<p>
No signer is required for <em class="replaceable"><code>tcp-self</code></em>
or <em class="replaceable"><code>6to4-self</code></em> however the standard
reverse mapping / prefix conversion must match the identity
field.
</p>
<p>
The identity field specifies a name or a wildcard
name. Normally, this is the name of the TSIG or
SIG(0) key used to sign the update request. When a
TKEY exchange has been used to create a shared secret,
the identity of the shared secret is the same as the
identity of the key used to authenticate the TKEY
exchange. TKEY is also the negotiation method used
by GSS-TSIG, which establishes an identity that is
the Kerberos principal of the client, such as
<strong class="userinput"><code>"user@host.domain"</code></strong>. When the
<em class="replaceable"><code>identity</code></em> field specifies
a wildcard name, it is subject to DNS wildcard
expansion, so the rule will apply to multiple identities.
The <em class="replaceable"><code>identity</code></em> field must
contain a fully-qualified domain name.
</p>
<p>
For nametypes <code class="varname">krb5-self</code>,
<code class="varname">ms-self</code>, <code class="varname">krb5-subdomain</code>,
and <code class="varname">ms-subdomain</code> the
<em class="replaceable"><code>identity</code></em> field specifies
the Windows or Kerberos realm of the machine belongs to.
</p>
<p>
The <em class="replaceable"><code>nametype</code></em> field has 13
values:
<code class="varname">name</code>, <code class="varname">subdomain</code>,
<code class="varname">wildcard</code>, <code class="varname">self</code>,
<code class="varname">selfsub</code>, <code class="varname">selfwild</code>,
<code class="varname">krb5-self</code>, <code class="varname">ms-self</code>,
<code class="varname">krb5-subdomain</code>,
<code class="varname">ms-subdomain</code>,
<code class="varname">tcp-self</code>, <code class="varname">6to4-self</code>,
<code class="varname">zonesub</code>, and <code class="varname">external</code>.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="varname">name</code>
</p>
</td>
<td>
<p>
Exact-match semantics. This rule matches
when the name being updated is identical
to the contents of the
<em class="replaceable"><code>name</code></em> field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">subdomain</code>
</p>
</td>
<td>
<p>
This rule matches when the name being updated
is a subdomain of, or identical to, the
contents of the <em class="replaceable"><code>name</code></em>
field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">zonesub</code>
</p>
</td>
<td>
<p>
This rule is similar to subdomain, except that
it matches when the name being updated is a
subdomain of the zone in which the
<span><strong class="command">update-policy</strong></span> statement
appears. This obviates the need to type the zone
name twice, and enables the use of a standard
<span><strong class="command">update-policy</strong></span> statement in
multiple zones without modification.
</p>
<p>
When this rule is used, the
<em class="replaceable"><code>name</code></em> field is omitted.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">wildcard</code>
</p>
</td>
<td>
<p>
The <em class="replaceable"><code>name</code></em> field
is subject to DNS wildcard expansion, and
this rule matches when the name being updated
name is a valid expansion of the wildcard.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">self</code>
</p>
</td>
<td>
<p>
This rule matches when the name being updated
matches the contents of the
<em class="replaceable"><code>identity</code></em> field.
The <em class="replaceable"><code>name</code></em> field
is ignored, but should be the same as the
<em class="replaceable"><code>identity</code></em> field.
The <code class="varname">self</code> nametype is
most useful when allowing using one key per
name to update, where the key has the same
name as the name to be updated. The
<em class="replaceable"><code>identity</code></em> would
be specified as <code class="constant">*</code> (an asterisk) in
this case.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">selfsub</code>
</p>
</td>
<td>
<p>
This rule is similar to <code class="varname">self</code>
except that subdomains of <code class="varname">self</code>
can also be updated.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">selfwild</code>
</p>
</td>
<td>
<p>
This rule is similar to <code class="varname">self</code>
except that only subdomains of
<code class="varname">self</code> can be updated.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">ms-self</code>
</p>
</td>
<td>
<p>
This rule takes a Windows machine principal
(machine$@REALM) for machine in REALM and
and converts it machine.realm allowing the machine
to update machine.realm. The REALM to be matched
is specified in the <em class="replaceable"><code>identity</code></em>
field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">ms-subdomain</code>
</p>
</td>
<td>
<p>
This rule takes a Windows machine principal
(machine$@REALM) for machine in REALM and
converts it to machine.realm allowing the machine
to update subdomains of machine.realm. The REALM
to be matched is specified in the
<em class="replaceable"><code>identity</code></em> field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">krb5-self</code>
</p>
</td>
<td>
<p>
This rule takes a Kerberos machine principal
(host/machine@REALM) for machine in REALM and
and converts it machine.realm allowing the machine
to update machine.realm. The REALM to be matched
is specified in the <em class="replaceable"><code>identity</code></em>
field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">krb5-subdomain</code>
</p>
</td>
<td>
<p>
This rule takes a Kerberos machine principal
(host/machine@REALM) for machine in REALM and
converts it to machine.realm allowing the machine
to update subdomains of machine.realm. The REALM
to be matched is specified in the
<em class="replaceable"><code>identity</code></em> field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">tcp-self</code>
</p>
</td>
<td>
<p>
Allow updates that have been sent via TCP and
for which the standard mapping from the initiating
IP address into the IN-ADDR.ARPA and IP6.ARPA
namespaces match the name to be updated.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
It is theoretically possible to spoof these TCP
sessions.
</div>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">6to4-self</code>
</p>
</td>
<td>
<p>
Allow the 6to4 prefix to be update by any TCP
connection from the 6to4 network or from the
corresponding IPv4 address. This is intended
to allow NS or DNAME RRsets to be added to the
reverse tree.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
It is theoretically possible to spoof these TCP
sessions.
</div>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">external</code>
</p>
</td>
<td>
<p>
This rule allows <span><strong class="command">named</strong></span>
to defer the decision of whether to allow a
given update to an external daemon.
</p>
<p>
The method of communicating with the daemon is
specified in the <em class="replaceable"><code>identity</code></em>
field, the format of which is
"<code class="constant">local:</code><em class="replaceable"><code>path</code></em>",
where <em class="replaceable"><code>path</code></em> is the location
of a UNIX-domain socket. (Currently, "local" is the
only supported mechanism.)
</p>
<p>
Requests to the external daemon are sent over the
UNIX-domain socket as datagrams with the following
format:
</p>
<pre class="programlisting">
Protocol version number (4 bytes, network byte order, currently 1)
Request length (4 bytes, network byte order)
Signer (null-terminated string)
Name (null-terminated string)
TCP source address (null-terminated string)
Rdata type (null-terminated string)
Key (null-terminated string)
TKEY token length (4 bytes, network byte order)
TKEY token (remainder of packet)</pre>
<p>
The daemon replies with a four-byte value in
network byte order, containing either 0 or 1; 0
indicates that the specified update is not
permitted, and 1 indicates that it is.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
In all cases, the <em class="replaceable"><code>name</code></em>
field must specify a fully-qualified domain name.
</p>
<p>
If no types are explicitly specified, this rule matches
all types except RRSIG, NS, SOA, NSEC and NSEC3. Types
may be specified by name, including "ANY" (ANY matches
all types except NSEC and NSEC3, which can never be
updated). Note that when an attempt is made to delete
all records associated with a name, the rules are
checked for each existing record type.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2599168"></a>Multiple views</h4></div></div></div>
<p>
When multiple views are in use, a zone may be
referenced by more than one of them. Often, the views
will contain different zones with the same name, allowing
different clients to receive different answers for the same
queries. At times, however, it is desirable for multiple
views to contain identical zones. The
<span><strong class="command">in-view</strong></span> zone option provides an efficient
way to do this: it allows a view to reference a zone that
was defined in a previously configured view. Example:
</p>
<pre class="programlisting">
view internal {
match-clients { 10/8; };
zone example.com {
type master;
file "example-external.db";
};
};
view external {
match-clients { any; };
zone example.com {
in-view internal;
};
};
</pre>
<p>
An <span><strong class="command">in-view</strong></span> option cannot refer to a view
that is configured later in the configuration file.
</p>
<p>
A <span><strong class="command">zone</strong></span> statement which uses the
<span><strong class="command">in-view</strong></span> option may not use any other
options with the exception of <span><strong class="command">forward</strong></span>
and <span><strong class="command">forwarders</strong></span>. (These options control
the behavior of the containing view, rather than changing
the zone object itself.)
</p>
<p>
An <span><strong class="command">in-view</strong></span> zone cannot be used as a
response policy zone.
</p>
</div>
</div>
</div>
<div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="id2599216"></a>Zone File</h2></div></div></div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="types_of_resource_records_and_when_to_use_them"></a>Types of Resource Records and When to Use Them</h3></div></div></div>
<p>
This section, largely borrowed from RFC 1034, describes the
concept of a Resource Record (RR) and explains when each is used.
Since the publication of RFC 1034, several new RRs have been
identified
and implemented in the DNS. These are also included.
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2599234"></a>Resource Records</h4></div></div></div>
<p>
A domain name identifies a node. Each node has a set of
resource information, which may be empty. The set of resource
information associated with a particular name is composed of
separate RRs. The order of RRs in a set is not significant and
need not be preserved by name servers, resolvers, or other
parts of the DNS. However, sorting of multiple RRs is
permitted for optimization purposes, for example, to specify
that a particular nearby server be tried first. See <a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called &#8220;The <span><strong class="command">sortlist</strong></span> Statement&#8221;</a> and <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called &#8220;RRset Ordering&#8221;</a>.
</p>
<p>
The components of a Resource Record are:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
owner name
</p>
</td>
<td>
<p>
The domain name where the RR is found.
</p>
</td>
</tr>
<tr>
<td>
<p>
type
</p>
</td>
<td>
<p>
An encoded 16-bit value that specifies
the type of the resource record.
</p>
</td>
</tr>
<tr>
<td>
<p>
TTL
</p>
</td>
<td>
<p>
The time-to-live of the RR. This field
is a 32-bit integer in units of seconds, and is
primarily used by
resolvers when they cache RRs. The TTL describes how
long a RR can
be cached before it should be discarded.
</p>
</td>
</tr>
<tr>
<td>
<p>
class
</p>
</td>
<td>
<p>
An encoded 16-bit value that identifies
a protocol family or instance of a protocol.
</p>
</td>
</tr>
<tr>
<td>
<p>
RDATA
</p>
</td>
<td>
<p>
The resource data. The format of the
data is type (and sometimes class) specific.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
The following are <span class="emphasis"><em>types</em></span> of valid RRs:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
A
</p>
</td>
<td>
<p>
A host address. In the IN class, this is a
32-bit IP address. Described in RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
AAAA
</p>
</td>
<td>
<p>
IPv6 address. Described in RFC 1886.
</p>
</td>
</tr>
<tr>
<td>
<p>
A6
</p>
</td>
<td>
<p>
IPv6 address. This can be a partial
address (a suffix) and an indirection to the name
where the rest of the
address (the prefix) can be found. Experimental.
Described in RFC 2874.
</p>
</td>
</tr>
<tr>
<td>
<p>
AFSDB
</p>
</td>
<td>
<p>
Location of AFS database servers.
Experimental. Described in RFC 1183.
</p>
</td>
</tr>
<tr>
<td>
<p>
APL
</p>
</td>
<td>
<p>
Address prefix list. Experimental.
Described in RFC 3123.
</p>
</td>
</tr>
<tr>
<td>
<p>
CERT
</p>
</td>
<td>
<p>
Holds a digital certificate.
Described in RFC 2538.
</p>
</td>
</tr>
<tr>
<td>
<p>
CNAME
</p>
</td>
<td>
<p>
Identifies the canonical name of an alias.
Described in RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
DHCID
</p>
</td>
<td>
<p>
Is used for identifying which DHCP client is
associated with this name. Described in RFC 4701.
</p>
</td>
</tr>
<tr>
<td>
<p>
DNAME
</p>
</td>
<td>
<p>
Replaces the domain name specified with
another name to be looked up, effectively aliasing an
entire
subtree of the domain name space rather than a single
record
as in the case of the CNAME RR.
Described in RFC 2672.
</p>
</td>
</tr>
<tr>
<td>
<p>
DNSKEY
</p>
</td>
<td>
<p>
Stores a public key associated with a signed
DNS zone. Described in RFC 4034.
</p>
</td>
</tr>
<tr>
<td>
<p>
DS
</p>
</td>
<td>
<p>
Stores the hash of a public key associated with a
signed DNS zone. Described in RFC 4034.
</p>
</td>
</tr>
<tr>
<td>
<p>
GPOS
</p>
</td>
<td>
<p>
Specifies the global position. Superseded by LOC.
</p>
</td>
</tr>
<tr>
<td>
<p>
HINFO
</p>
</td>
<td>
<p>
Identifies the CPU and OS used by a host.
Described in RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
IPSECKEY
</p>
</td>
<td>
<p>
Provides a method for storing IPsec keying material in
DNS. Described in RFC 4025.
</p>
</td>
</tr>
<tr>
<td>
<p>
ISDN
</p>
</td>
<td>
<p>
Representation of ISDN addresses.
Experimental. Described in RFC 1183.
</p>
</td>
</tr>
<tr>
<td>
<p>
KEY
</p>
</td>
<td>
<p>
Stores a public key associated with a
DNS name. Used in original DNSSEC; replaced
by DNSKEY in DNSSECbis, but still used with
SIG(0). Described in RFCs 2535 and 2931.
</p>
</td>
</tr>
<tr>
<td>
<p>
KX
</p>
</td>
<td>
<p>
Identifies a key exchanger for this
DNS name. Described in RFC 2230.
</p>
</td>
</tr>
<tr>
<td>
<p>
LOC
</p>
</td>
<td>
<p>
For storing GPS info. Described in RFC 1876.
Experimental.
</p>
</td>
</tr>
<tr>
<td>
<p>
MX
</p>
</td>
<td>
<p>
Identifies a mail exchange for the domain with
a 16-bit preference value (lower is better)
followed by the host name of the mail exchange.
Described in RFC 974, RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
NAPTR
</p>
</td>
<td>
<p>
Name authority pointer. Described in RFC 2915.
</p>
</td>
</tr>
<tr>
<td>
<p>
NSAP
</p>
</td>
<td>
<p>
A network service access point.
Described in RFC 1706.
</p>
</td>
</tr>
<tr>
<td>
<p>
NS
</p>
</td>
<td>
<p>
The authoritative name server for the
domain. Described in RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
NSEC
</p>
</td>
<td>
<p>
Used in DNSSECbis to securely indicate that
RRs with an owner name in a certain name interval do
not exist in
a zone and indicate what RR types are present for an
existing name.
Described in RFC 4034.
</p>
</td>
</tr>
<tr>
<td>
<p>
NSEC3
</p>
</td>
<td>
<p>
Used in DNSSECbis to securely indicate that
RRs with an owner name in a certain name
interval do not exist in a zone and indicate
what RR types are present for an existing
name. NSEC3 differs from NSEC in that it
prevents zone enumeration but is more
computationally expensive on both the server
and the client than NSEC. Described in RFC
5155.
</p>
</td>
</tr>
<tr>
<td>
<p>
NSEC3PARAM
</p>
</td>
<td>
<p>
Used in DNSSECbis to tell the authoritative
server which NSEC3 chains are available to use.
Described in RFC 5155.
</p>
</td>
</tr>
<tr>
<td>
<p>
NXT
</p>
</td>
<td>
<p>
Used in DNSSEC to securely indicate that
RRs with an owner name in a certain name interval do
not exist in
a zone and indicate what RR types are present for an
existing name.
Used in original DNSSEC; replaced by NSEC in
DNSSECbis.
Described in RFC 2535.
</p>
</td>
</tr>
<tr>
<td>
<p>
PTR
</p>
</td>
<td>
<p>
A pointer to another part of the domain
name space. Described in RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
PX
</p>
</td>
<td>
<p>
Provides mappings between RFC 822 and X.400
addresses. Described in RFC 2163.
</p>
</td>
</tr>
<tr>
<td>
<p>
RP
</p>
</td>
<td>
<p>
Information on persons responsible
for the domain. Experimental. Described in RFC 1183.
</p>
</td>
</tr>
<tr>
<td>
<p>
RRSIG
</p>
</td>
<td>
<p>
Contains DNSSECbis signature data. Described
in RFC 4034.
</p>
</td>
</tr>
<tr>
<td>
<p>
RT
</p>
</td>
<td>
<p>
Route-through binding for hosts that
do not have their own direct wide area network
addresses.
Experimental. Described in RFC 1183.
</p>
</td>
</tr>
<tr>
<td>
<p>
SIG
</p>
</td>
<td>
<p>
Contains DNSSEC signature data. Used in
original DNSSEC; replaced by RRSIG in
DNSSECbis, but still used for SIG(0).
Described in RFCs 2535 and 2931.
</p>
</td>
</tr>
<tr>
<td>
<p>
SOA
</p>
</td>
<td>
<p>
Identifies the start of a zone of authority.
Described in RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
SPF
</p>
</td>
<td>
<p>
Contains the Sender Policy Framework information
for a given email domain. Described in RFC 4408.
</p>
</td>
</tr>
<tr>
<td>
<p>
SRV
</p>
</td>
<td>
<p>
Information about well known network
services (replaces WKS). Described in RFC 2782.
</p>
</td>
</tr>
<tr>
<td>
<p>
SSHFP
</p>
</td>
<td>
<p>
Provides a way to securely publish a secure shell key's
fingerprint. Described in RFC 4255.
</p>
</td>
</tr>
<tr>
<td>
<p>
TXT
</p>
</td>
<td>
<p>
Text records. Described in RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
WKS
</p>
</td>
<td>
<p>
Information about which well known
network services, such as SMTP, that a domain
supports. Historical.
</p>
</td>
</tr>
<tr>
<td>
<p>
X25
</p>
</td>
<td>
<p>
Representation of X.25 network addresses.
Experimental. Described in RFC 1183.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
The following <span class="emphasis"><em>classes</em></span> of resource records
are currently valid in the DNS:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
IN
</p>
</td>
<td>
<p>
The Internet.
</p>
</td>
</tr>
<tr>
<td>
<p>
CH
</p>
</td>
<td>
<p>
Chaosnet, a LAN protocol created at MIT in the
mid-1970s.
Rarely used for its historical purpose, but reused for
BIND's
built-in server information zones, e.g.,
<code class="literal">version.bind</code>.
</p>
</td>
</tr>
<tr>
<td>
<p>
HS
</p>
</td>
<td>
<p>
Hesiod, an information service
developed by MIT's Project Athena. It is used to share
information
about various systems databases, such as users,
groups, printers
and so on.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
The owner name is often implicit, rather than forming an
integral
part of the RR. For example, many name servers internally form
tree
or hash structures for the name space, and chain RRs off nodes.
The remaining RR parts are the fixed header (type, class, TTL)
which is consistent for all RRs, and a variable part (RDATA)
that
fits the needs of the resource being described.
</p>
<p>
The meaning of the TTL field is a time limit on how long an
RR can be kept in a cache. This limit does not apply to
authoritative
data in zones; it is also timed out, but by the refreshing
policies
for the zone. The TTL is assigned by the administrator for the
zone where the data originates. While short TTLs can be used to
minimize caching, and a zero TTL prohibits caching, the
realities
of Internet performance suggest that these times should be on
the
order of days for the typical host. If a change can be
anticipated,
the TTL can be reduced prior to the change to minimize
inconsistency
during the change, and then increased back to its former value
following
the change.
</p>
<p>
The data in the RDATA section of RRs is carried as a combination
of binary strings and domain names. The domain names are
frequently
used as "pointers" to other data in the DNS.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2600925"></a>Textual expression of RRs</h4></div></div></div>
<p>
RRs are represented in binary form in the packets of the DNS
protocol, and are usually represented in highly encoded form
when
stored in a name server or resolver. In the examples provided
in
RFC 1034, a style similar to that used in master files was
employed
in order to show the contents of RRs. In this format, most RRs
are shown on a single line, although continuation lines are
possible
using parentheses.
</p>
<p>
The start of the line gives the owner of the RR. If a line
begins with a blank, then the owner is assumed to be the same as
that of the previous RR. Blank lines are often included for
readability.
</p>
<p>
Following the owner, we list the TTL, type, and class of the
RR. Class and type use the mnemonics defined above, and TTL is
an integer before the type field. In order to avoid ambiguity
in
parsing, type and class mnemonics are disjoint, TTLs are
integers,
and the type mnemonic is always last. The IN class and TTL
values
are often omitted from examples in the interests of clarity.
</p>
<p>
The resource data or RDATA section of the RR are given using
knowledge of the typical representation for the data.
</p>
<p>
For example, we might show the RRs carried in a message as:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="literal">ISI.EDU.</code>
</p>
</td>
<td>
<p>
<code class="literal">MX</code>
</p>
</td>
<td>
<p>
<code class="literal">10 VENERA.ISI.EDU.</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">MX</code>
</p>
</td>
<td>
<p>
<code class="literal">10 VAXA.ISI.EDU</code>
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="literal">VENERA.ISI.EDU</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">128.9.0.32</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.1.0.52</code>
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="literal">VAXA.ISI.EDU</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.2.0.27</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">128.9.0.33</code>
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
The MX RRs have an RDATA section which consists of a 16-bit
number followed by a domain name. The address RRs use a
standard
IP address format to contain a 32-bit internet address.
</p>
<p>
The above example shows six RRs, with two RRs at each of three
domain names.
</p>
<p>
Similarly we might see:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="literal">XX.LCS.MIT.EDU.</code>
</p>
</td>
<td>
<p>
<code class="literal">IN A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.0.0.44</code>
</p>
</td>
</tr>
<tr>
<td>�</td>
<td>
<p>
<code class="literal">CH A</code>
</p>
</td>
<td>
<p>
<code class="literal">MIT.EDU. 2420</code>
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
This example shows two addresses for
<code class="literal">XX.LCS.MIT.EDU</code>, each of a different class.
</p>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2601446"></a>Discussion of MX Records</h3></div></div></div>
<p>
As described above, domain servers store information as a
series of resource records, each of which contains a particular
piece of information about a given domain name (which is usually,
but not always, a host). The simplest way to think of a RR is as
a typed pair of data, a domain name matched with a relevant datum,
and stored with some additional type information to help systems
determine when the RR is relevant.
</p>
<p>
MX records are used to control delivery of email. The data
specified in the record is a priority and a domain name. The
priority
controls the order in which email delivery is attempted, with the
lowest number first. If two priorities are the same, a server is
chosen randomly. If no servers at a given priority are responding,
the mail transport agent will fall back to the next largest
priority.
Priority numbers do not have any absolute meaning &#8212; they are
relevant
only respective to other MX records for that domain name. The
domain
name given is the machine to which the mail will be delivered.
It <span class="emphasis"><em>must</em></span> have an associated address record
(A or AAAA) &#8212; CNAME is not sufficient.
</p>
<p>
For a given domain, if there is both a CNAME record and an
MX record, the MX record is in error, and will be ignored.
Instead,
the mail will be delivered to the server specified in the MX
record
pointed to by the CNAME.
For example:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
<col>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="literal">example.com.</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">MX</code>
</p>
</td>
<td>
<p>
<code class="literal">10</code>
</p>
</td>
<td>
<p>
<code class="literal">mail.example.com.</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">MX</code>
</p>
</td>
<td>
<p>
<code class="literal">10</code>
</p>
</td>
<td>
<p>
<code class="literal">mail2.example.com.</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">MX</code>
</p>
</td>
<td>
<p>
<code class="literal">20</code>
</p>
</td>
<td>
<p>
<code class="literal">mail.backup.org.</code>
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="literal">mail.example.com.</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.0.0.1</code>
</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>
<code class="literal">mail2.example.com.</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.0.0.2</code>
</p>
</td>
<td>
<p></p>
</td>
</tr>
</tbody>
</table></div>
<p>
Mail delivery will be attempted to <code class="literal">mail.example.com</code> and
<code class="literal">mail2.example.com</code> (in
any order), and if neither of those succeed, delivery to <code class="literal">mail.backup.org</code> will
be attempted.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="Setting_TTLs"></a>Setting TTLs</h3></div></div></div>
<p>
The time-to-live of the RR field is a 32-bit integer represented
in units of seconds, and is primarily used by resolvers when they
cache RRs. The TTL describes how long a RR can be cached before it
should be discarded. The following three types of TTL are
currently
used in a zone file.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
SOA
</p>
</td>
<td>
<p>
The last field in the SOA is the negative
caching TTL. This controls how long other servers will
cache no-such-domain
(NXDOMAIN) responses from you.
</p>
<p>
The maximum time for
negative caching is 3 hours (3h).
</p>
</td>
</tr>
<tr>
<td>
<p>
$TTL
</p>
</td>
<td>
<p>
The $TTL directive at the top of the
zone file (before the SOA) gives a default TTL for every
RR without
a specific TTL set.
</p>
</td>
</tr>
<tr>
<td>
<p>
RR TTLs
</p>
</td>
<td>
<p>
Each RR can have a TTL as the second
field in the RR, which will control how long other
servers can cache it.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
All of these TTLs default to units of seconds, though units
can be explicitly specified, for example, <code class="literal">1h30m</code>.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2601993"></a>Inverse Mapping in IPv4</h3></div></div></div>
<p>
Reverse name resolution (that is, translation from IP address
to name) is achieved by means of the <span class="emphasis"><em>in-addr.arpa</em></span> domain
and PTR records. Entries in the in-addr.arpa domain are made in
least-to-most significant order, read left to right. This is the
opposite order to the way IP addresses are usually written. Thus,
a machine with an IP address of 10.1.2.3 would have a
corresponding
in-addr.arpa name of
3.2.1.10.in-addr.arpa. This name should have a PTR resource record
whose data field is the name of the machine or, optionally,
multiple
PTR records if the machine has more than one name. For example,
in the [<span class="optional">example.com</span>] domain:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="literal">$ORIGIN</code>
</p>
</td>
<td>
<p>
<code class="literal">2.1.10.in-addr.arpa</code>
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="literal">3</code>
</p>
</td>
<td>
<p>
<code class="literal">IN PTR foo.example.com.</code>
</p>
</td>
</tr>
</tbody>
</table></div>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
The <span><strong class="command">$ORIGIN</strong></span> lines in the examples
are for providing context to the examples only &#8212; they do not
necessarily
appear in the actual usage. They are only used here to indicate
that the example is relative to the listed origin.
</p>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2602120"></a>Other Zone File Directives</h3></div></div></div>
<p>
The Master File Format was initially defined in RFC 1035 and
has subsequently been extended. While the Master File Format
itself
is class independent all records in a Master File must be of the
same
class.
</p>
<p>
Master File Directives include <span><strong class="command">$ORIGIN</strong></span>, <span><strong class="command">$INCLUDE</strong></span>,
and <span><strong class="command">$TTL.</strong></span>
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2602142"></a>The <span><strong class="command">@</strong></span> (at-sign)</h4></div></div></div>
<p>
When used in the label (or name) field, the asperand or
at-sign (@) symbol represents the current origin.
At the start of the zone file, it is the
&lt;<code class="varname">zone_name</code>&gt; (followed by
trailing dot).
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2602158"></a>The <span><strong class="command">$ORIGIN</strong></span> Directive</h4></div></div></div>
<p>
Syntax: <span><strong class="command">$ORIGIN</strong></span>
<em class="replaceable"><code>domain-name</code></em>
[<span class="optional"><em class="replaceable"><code>comment</code></em></span>]
</p>
<p><span><strong class="command">$ORIGIN</strong></span>
sets the domain name that will be appended to any
unqualified records. When a zone is first read in there
is an implicit <span><strong class="command">$ORIGIN</strong></span>
&lt;<code class="varname">zone_name</code>&gt;<span><strong class="command">.</strong></span>
(followed by trailing dot).
The current <span><strong class="command">$ORIGIN</strong></span> is appended to
the domain specified in the <span><strong class="command">$ORIGIN</strong></span>
argument if it is not absolute.
</p>
<pre class="programlisting">
$ORIGIN example.com.
WWW CNAME MAIN-SERVER
</pre>
<p>
is equivalent to
</p>
<pre class="programlisting">
WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
</pre>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2602356"></a>The <span><strong class="command">$INCLUDE</strong></span> Directive</h4></div></div></div>
<p>
Syntax: <span><strong class="command">$INCLUDE</strong></span>
<em class="replaceable"><code>filename</code></em>
[<span class="optional">
<em class="replaceable"><code>origin</code></em> </span>]
[<span class="optional"> <em class="replaceable"><code>comment</code></em> </span>]
</p>
<p>
Read and process the file <code class="filename">filename</code> as
if it were included into the file at this point. If <span><strong class="command">origin</strong></span> is
specified the file is processed with <span><strong class="command">$ORIGIN</strong></span> set
to that value, otherwise the current <span><strong class="command">$ORIGIN</strong></span> is
used.
</p>
<p>
The origin and the current domain name
revert to the values they had prior to the <span><strong class="command">$INCLUDE</strong></span> once
the file has been read.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
RFC 1035 specifies that the current origin should be restored
after
an <span><strong class="command">$INCLUDE</strong></span>, but it is silent
on whether the current
domain name should also be restored. BIND 9 restores both of
them.
This could be construed as a deviation from RFC 1035, a
feature, or both.
</p>
</div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2602425"></a>The <span><strong class="command">$TTL</strong></span> Directive</h4></div></div></div>
<p>
Syntax: <span><strong class="command">$TTL</strong></span>
<em class="replaceable"><code>default-ttl</code></em>
[<span class="optional">
<em class="replaceable"><code>comment</code></em> </span>]
</p>
<p>
Set the default Time To Live (TTL) for subsequent records
with undefined TTLs. Valid TTLs are of the range 0-2147483647
seconds.
</p>
<p><span><strong class="command">$TTL</strong></span>
is defined in RFC 2308.
</p>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2602461"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</h3></div></div></div>
<p>
Syntax: <span><strong class="command">$GENERATE</strong></span>
<em class="replaceable"><code>range</code></em>
<em class="replaceable"><code>lhs</code></em>
[<span class="optional"><em class="replaceable"><code>ttl</code></em></span>]
[<span class="optional"><em class="replaceable"><code>class</code></em></span>]
<em class="replaceable"><code>type</code></em>
<em class="replaceable"><code>rhs</code></em>
[<span class="optional"><em class="replaceable"><code>comment</code></em></span>]
</p>
<p><span><strong class="command">$GENERATE</strong></span>
is used to create a series of resource records that only
differ from each other by an
iterator. <span><strong class="command">$GENERATE</strong></span> can be used to
easily generate the sets of records required to support
sub /24 reverse delegations described in RFC 2317:
Classless IN-ADDR.ARPA delegation.
</p>
<pre class="programlisting">$ORIGIN 0.0.192.IN-ADDR.ARPA.
$GENERATE 1-2 @ NS SERVER$.EXAMPLE.
$GENERATE 1-127 $ CNAME $.0</pre>
<p>
is equivalent to
</p>
<pre class="programlisting">0.0.0.192.IN-ADDR.ARPA. NS SERVER1.EXAMPLE.
0.0.0.192.IN-ADDR.ARPA. NS SERVER2.EXAMPLE.
1.0.0.192.IN-ADDR.ARPA. CNAME 1.0.0.0.192.IN-ADDR.ARPA.
2.0.0.192.IN-ADDR.ARPA. CNAME 2.0.0.0.192.IN-ADDR.ARPA.
...
127.0.0.192.IN-ADDR.ARPA. CNAME 127.0.0.0.192.IN-ADDR.ARPA.
</pre>
<p>
Generate a set of A and MX records. Note the MX's right hand
side is a quoted string. The quotes will be stripped when the
right hand side is processed.
</p>
<pre class="programlisting">
$ORIGIN EXAMPLE.
$GENERATE 1-127 HOST-$ A 1.2.3.$
$GENERATE 1-127 HOST-$ MX "0 ."</pre>
<p>
is equivalent to
</p>
<pre class="programlisting">HOST-1.EXAMPLE. A 1.2.3.1
HOST-1.EXAMPLE. MX 0 .
HOST-2.EXAMPLE. A 1.2.3.2
HOST-2.EXAMPLE. MX 0 .
HOST-3.EXAMPLE. A 1.2.3.3
HOST-3.EXAMPLE. MX 0 .
...
HOST-127.EXAMPLE. A 1.2.3.127
HOST-127.EXAMPLE. MX 0 .
</pre>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p><span><strong class="command">range</strong></span></p>
</td>
<td>
<p>
This can be one of two forms: start-stop
or start-stop/step. If the first form is used, then step
is set to 1. start, stop and step must be positive
integers between 0 and (2^31)-1. start must not be
larger than stop.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">lhs</strong></span></p>
</td>
<td>
<p>This
describes the owner name of the resource records
to be created. Any single <span><strong class="command">$</strong></span>
(dollar sign)
symbols within the <span><strong class="command">lhs</strong></span> string
are replaced by the iterator value.
To get a $ in the output, you need to escape the
<span><strong class="command">$</strong></span> using a backslash
<span><strong class="command">\</strong></span>,
e.g. <span><strong class="command">\$</strong></span>. The
<span><strong class="command">$</strong></span> may optionally be followed
by modifiers which change the offset from the
iterator, field width and base.
Modifiers are introduced by a
<span><strong class="command">{</strong></span> (left brace) immediately following the
<span><strong class="command">$</strong></span> as
<span><strong class="command">${offset[,width[,base]]}</strong></span>.
For example, <span><strong class="command">${-20,3,d}</strong></span>
subtracts 20 from the current value, prints the
result as a decimal in a zero-padded field of
width 3.
Available output forms are decimal
(<span><strong class="command">d</strong></span>), octal
(<span><strong class="command">o</strong></span>), hexadecimal
(<span><strong class="command">x</strong></span> or <span><strong class="command">X</strong></span>
for uppercase) and nibble
(<span><strong class="command">n</strong></span> or <span><strong class="command">N</strong></span>\
for uppercase). The default modifier is
<span><strong class="command">${0,0,d}</strong></span>. If the
<span><strong class="command">lhs</strong></span> is not absolute, the
current <span><strong class="command">$ORIGIN</strong></span> is appended
to the name.
</p>
<p>
In nibble mode the value will be treated as
if it was a reversed hexadecimal string
with each hexadecimal digit as a separate
label. The width field includes the label
separator.
</p>
<p>
For compatibility with earlier versions,
<span><strong class="command">$$</strong></span> is still recognized as
indicating a literal $ in the output.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ttl</strong></span></p>
</td>
<td>
<p>
Specifies the time-to-live of the generated records. If
not specified this will be inherited using the
normal TTL inheritance rules.
</p>
<p><span><strong class="command">class</strong></span>
and <span><strong class="command">ttl</strong></span> can be
entered in either order.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">class</strong></span></p>
</td>
<td>
<p>
Specifies the class of the generated records.
This must match the zone class if it is
specified.
</p>
<p><span><strong class="command">class</strong></span>
and <span><strong class="command">ttl</strong></span> can be
entered in either order.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">type</strong></span></p>
</td>
<td>
<p>
Any valid type.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">rhs</strong></span></p>
</td>
<td>
<p>
<span><strong class="command">rhs</strong></span>, optionally, quoted string.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
The <span><strong class="command">$GENERATE</strong></span> directive is a <acronym class="acronym">BIND</acronym> extension
and not part of the standard zone file format.
</p>
<p>
BIND 8 does not support the optional TTL and CLASS fields.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zonefile_format"></a>Additional File Formats</h3></div></div></div>
<p>
In addition to the standard textual format, BIND 9
supports the ability to read or dump to zone files in
other formats.
</p>
<p>
The <code class="constant">raw</code> format is
a binary representation of zone data in a manner similar
to that used in zone transfers. Since it does not require
parsing text, load time is significantly reduced.
</p>
<p>
An even faster alternative is the <code class="constant">map</code>
format, which is an image of a <acronym class="acronym">BIND</acronym> 9
in-memory zone database; it is capable of being loaded
directly into memory via the <span><strong class="command">mmap()</strong></span>
function; the zone can begin serving queries almost
immediately.
</p>
<p>
For a primary server, a zone file in
<code class="constant">raw</code> or <code class="constant">map</code>
format is expected to be generated from a textual zone
file by the <span><strong class="command">named-compilezone</strong></span> command.
For a secondary server or for a dynamic zone, it is automatically
generated (if this format is specified by the
<span><strong class="command">masterfile-format</strong></span> option) when
<span><strong class="command">named</strong></span> dumps the zone contents after
zone transfer or when applying prior updates.
</p>
<p>
If a zone file in a binary format needs manual modification,
it first must be converted to a textual form by the
<span><strong class="command">named-compilezone</strong></span> command. All
necessary modification should go to the text file, which
should then be converted to the binary form by the
<span><strong class="command">named-compilezone</strong></span> command again.
</p>
<p>
Note that <span><strong class="command">map</strong></span> format is extremely
architecture-specific. A <code class="constant">map</code>
file <span class="emphasis"><em>cannot</em></span> be used on a system
with different pointer size, endianness or data alignment
than the system on which it was generated, and should in
general be used only inside a single system.
While <code class="constant">raw</code> format uses
network byte order and avoids architecture-dependent
data alignment so that it is as portable as
possible, it is also primarily expected to be used
inside the same single system. To export a
zone file in either <code class="constant">raw</code> or
<code class="constant">map</code> format, or make a
portable backup of such a file, conversion to
<code class="constant">text</code> format is recommended.
</p>
</div>
</div>
<div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="statistics"></a>BIND9 Statistics</h2></div></div></div>
<p>
<acronym class="acronym">BIND</acronym> 9 maintains lots of statistics
information and provides several interfaces for users to
get access to the statistics.
The available statistics include all statistics counters
that were available in <acronym class="acronym">BIND</acronym> 8 and
are meaningful in <acronym class="acronym">BIND</acronym> 9,
and other information that is considered useful.
</p>
<p>
The statistics information is categorized into the following
sections.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>Incoming Requests</p>
</td>
<td>
<p>
The number of incoming DNS requests for each OPCODE.
</p>
</td>
</tr>
<tr>
<td>
<p>Incoming Queries</p>
</td>
<td>
<p>
The number of incoming queries for each RR type.
</p>
</td>
</tr>
<tr>
<td>
<p>Outgoing Queries</p>
</td>
<td>
<p>
The number of outgoing queries for each RR
type sent from the internal resolver.
Maintained per view.
</p>
</td>
</tr>
<tr>
<td>
<p>Name Server Statistics</p>
</td>
<td>
<p>
Statistics counters about incoming request processing.
</p>
</td>
</tr>
<tr>
<td>
<p>Zone Maintenance Statistics</p>
</td>
<td>
<p>
Statistics counters regarding zone maintenance
operations such as zone transfers.
</p>
</td>
</tr>
<tr>
<td>
<p>Resolver Statistics</p>
</td>
<td>
<p>
Statistics counters about name resolution
performed in the internal resolver.
Maintained per view.
</p>
</td>
</tr>
<tr>
<td>
<p>Cache DB RRsets</p>
</td>
<td>
<p>
The number of RRsets per RR type and nonexistent
names stored in the cache database.
If the exclamation mark (!) is printed for a RR
type, it means that particular type of RRset is
known to be nonexistent (this is also known as
"NXRRSET"). If a hash mark (#) is present then
the RRset is marked for garbage collection.
Maintained per view.
</p>
</td>
</tr>
<tr>
<td>
<p>Socket I/O Statistics</p>
</td>
<td>
<p>
Statistics counters about network related events.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
A subset of Name Server Statistics is collected and shown
per zone for which the server has the authority when
<span><strong class="command">zone-statistics</strong></span> is set to
<strong class="userinput"><code>yes</code></strong>.
These statistics counters are shown with their zone and view
names.
In some cases the view names are omitted for the default view.
</p>
<p>
There are currently two user interfaces to get access to the
statistics.
One is in the plain text format dumped to the file specified
by the <span><strong class="command">statistics-file</strong></span> configuration option.
The other is remotely accessible via a statistics channel
when the <span><strong class="command">statistics-channels</strong></span> statement
is specified in the configuration file
(see <a href="Bv9ARM.ch06.html#statschannels" title="statistics-channels Statement Grammar">the section called &#8220;<span><strong class="command">statistics-channels</strong></span> Statement Grammar&#8221;</a>.)
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="statsfile"></a>The Statistics File</h4></div></div></div>
<p>
The text format statistics dump begins with a line, like:
</p>
<p>
<span><strong class="command">+++ Statistics Dump +++ (973798949)</strong></span>
</p>
<p>
The number in parentheses is a standard
Unix-style timestamp, measured as seconds since January 1, 1970.
Following
that line is a set of statistics information, which is categorized
as described above.
Each section begins with a line, like:
</p>
<p>
<span><strong class="command">++ Name Server Statistics ++</strong></span>
</p>
<p>
Each section consists of lines, each containing the statistics
counter value followed by its textual description.
See below for available counters.
For brevity, counters that have a value of 0 are not shown
in the statistics file.
</p>
<p>
The statistics dump ends with the line where the
number is identical to the number in the beginning line; for example:
</p>
<p>
<span><strong class="command">--- Statistics Dump --- (973798949)</strong></span>
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="statistics_counters"></a>Statistics Counters</h3></div></div></div>
<p>
The following tables summarize statistics counters that
<acronym class="acronym">BIND</acronym> 9 provides.
For each row of the tables, the leftmost column is the
abbreviated symbol name of that counter.
These symbols are shown in the statistics information
accessed via an HTTP statistics channel.
The rightmost column gives the description of the counter,
which is also shown in the statistics file
(but, in this document, possibly with slight modification
for better readability).
Additional notes may also be provided in this column.
When a middle column exists between these two columns,
it gives the corresponding counter name of the
<acronym class="acronym">BIND</acronym> 8 statistics, if applicable.
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2603592"></a>Name Server Statistics Counters</h4></div></div></div>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<span class="emphasis"><em>Symbol</em></span>
</p>
</td>
<td>
<p>
<span class="emphasis"><em>BIND8 Symbol</em></span>
</p>
</td>
<td>
<p>
<span class="emphasis"><em>Description</em></span>
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Requestv4</strong></span></p>
</td>
<td>
<p><span><strong class="command">RQ</strong></span></p>
</td>
<td>
<p>
IPv4 requests received.
Note: this also counts non query requests.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Requestv6</strong></span></p>
</td>
<td>
<p><span><strong class="command">RQ</strong></span></p>
</td>
<td>
<p>
IPv6 requests received.
Note: this also counts non query requests.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ReqEdns0</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Requests with EDNS(0) received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ReqBadEDNSVer</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Requests with unsupported EDNS version received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ReqTSIG</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Requests with TSIG received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ReqSIG0</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Requests with SIG(0) received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ReqBadSIG</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Requests with invalid (TSIG or SIG(0)) signature.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ReqTCP</strong></span></p>
</td>
<td>
<p><span><strong class="command">RTCP</strong></span></p>
</td>
<td>
<p>
TCP requests received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">AuthQryRej</strong></span></p>
</td>
<td>
<p><span><strong class="command">RUQ</strong></span></p>
</td>
<td>
<p>
Authoritative (non recursive) queries rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RecQryRej</strong></span></p>
</td>
<td>
<p><span><strong class="command">RURQ</strong></span></p>
</td>
<td>
<p>
Recursive queries rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">XfrRej</strong></span></p>
</td>
<td>
<p><span><strong class="command">RUXFR</strong></span></p>
</td>
<td>
<p>
Zone transfer requests rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateRej</strong></span></p>
</td>
<td>
<p><span><strong class="command">RUUpd</strong></span></p>
</td>
<td>
<p>
Dynamic update requests rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Response</strong></span></p>
</td>
<td>
<p><span><strong class="command">SAns</strong></span></p>
</td>
<td>
<p>
Responses sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RespTruncated</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Truncated responses sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RespEDNS0</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Responses with EDNS(0) sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RespTSIG</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Responses with TSIG sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RespSIG0</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Responses with SIG(0) sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QrySuccess</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Queries resulted in a successful answer.
This means the query which returns a NOERROR response
with at least one answer RR.
This corresponds to the
<span><strong class="command">success</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryAuthAns</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Queries resulted in authoritative answer.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryNoauthAns</strong></span></p>
</td>
<td>
<p><span><strong class="command">SNaAns</strong></span></p>
</td>
<td>
<p>
Queries resulted in non authoritative answer.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryReferral</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Queries resulted in referral answer.
This corresponds to the
<span><strong class="command">referral</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryNxrrset</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Queries resulted in NOERROR responses with no data.
This corresponds to the
<span><strong class="command">nxrrset</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QrySERVFAIL</strong></span></p>
</td>
<td>
<p><span><strong class="command">SFail</strong></span></p>
</td>
<td>
<p>
Queries resulted in SERVFAIL.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryFORMERR</strong></span></p>
</td>
<td>
<p><span><strong class="command">SFErr</strong></span></p>
</td>
<td>
<p>
Queries resulted in FORMERR.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryNXDOMAIN</strong></span></p>
</td>
<td>
<p><span><strong class="command">SNXD</strong></span></p>
</td>
<td>
<p>
Queries resulted in NXDOMAIN.
This corresponds to the
<span><strong class="command">nxdomain</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryRecursion</strong></span></p>
</td>
<td>
<p><span><strong class="command">RFwdQ</strong></span></p>
</td>
<td>
<p>
Queries which caused the server
to perform recursion in order to find the final answer.
This corresponds to the
<span><strong class="command">recursion</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryDuplicate</strong></span></p>
</td>
<td>
<p><span><strong class="command">RDupQ</strong></span></p>
</td>
<td>
<p>
Queries which the server attempted to
recurse but discovered an existing query with the same
IP address, port, query ID, name, type and class
already being processed.
This corresponds to the
<span><strong class="command">duplicate</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryDropped</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Recursive queries for which the server
discovered an excessive number of existing
recursive queries for the same name, type and
class and were subsequently dropped.
This is the number of dropped queries due to
the reason explained with the
<span><strong class="command">clients-per-query</strong></span>
and
<span><strong class="command">max-clients-per-query</strong></span>
options
(see the description about
<a href="Bv9ARM.ch06.html#clients-per-query"><span><strong class="command">clients-per-query</strong></span></a>.)
This corresponds to the
<span><strong class="command">dropped</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryFailure</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Other query failures.
This corresponds to the
<span><strong class="command">failure</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
Note: this counter is provided mainly for
backward compatibility with the previous versions.
Normally a more fine-grained counters such as
<span><strong class="command">AuthQryRej</strong></span> and
<span><strong class="command">RecQryRej</strong></span>
that would also fall into this counter are provided,
and so this counter would not be of much
interest in practice.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">XfrReqDone</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Requested zone transfers completed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateReqFwd</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Update requests forwarded.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateRespFwd</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Update responses forwarded.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateFwdFail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Dynamic update forward failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateDone</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Dynamic updates completed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateFail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Dynamic updates failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateBadPrereq</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Dynamic updates rejected due to prerequisite failure.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RateDropped</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Responses dropped by rate limits.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RateSlipped</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Responses truncated by rate limits.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RPZRewrites</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Response policy zone rewrites.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2605161"></a>Zone Maintenance Statistics Counters</h4></div></div></div>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<span class="emphasis"><em>Symbol</em></span>
</p>
</td>
<td>
<p>
<span class="emphasis"><em>Description</em></span>
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">NotifyOutv4</strong></span></p>
</td>
<td>
<p>
IPv4 notifies sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">NotifyOutv6</strong></span></p>
</td>
<td>
<p>
IPv6 notifies sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">NotifyInv4</strong></span></p>
</td>
<td>
<p>
IPv4 notifies received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">NotifyInv6</strong></span></p>
</td>
<td>
<p>
IPv6 notifies received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">NotifyRej</strong></span></p>
</td>
<td>
<p>
Incoming notifies rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">SOAOutv4</strong></span></p>
</td>
<td>
<p>
IPv4 SOA queries sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">SOAOutv6</strong></span></p>
</td>
<td>
<p>
IPv6 SOA queries sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">AXFRReqv4</strong></span></p>
</td>
<td>
<p>
IPv4 AXFR requested.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">AXFRReqv6</strong></span></p>
</td>
<td>
<p>
IPv6 AXFR requested.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">IXFRReqv4</strong></span></p>
</td>
<td>
<p>
IPv4 IXFR requested.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">IXFRReqv6</strong></span></p>
</td>
<td>
<p>
IPv6 IXFR requested.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">XfrSuccess</strong></span></p>
</td>
<td>
<p>
Zone transfer requests succeeded.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">XfrFail</strong></span></p>
</td>
<td>
<p>
Zone transfer requests failed.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2605612"></a>Resolver Statistics Counters</h4></div></div></div>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<span class="emphasis"><em>Symbol</em></span>
</p>
</td>
<td>
<p>
<span class="emphasis"><em>BIND8 Symbol</em></span>
</p>
</td>
<td>
<p>
<span class="emphasis"><em>Description</em></span>
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Queryv4</strong></span></p>
</td>
<td>
<p><span><strong class="command">SFwdQ</strong></span></p>
</td>
<td>
<p>
IPv4 queries sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Queryv6</strong></span></p>
</td>
<td>
<p><span><strong class="command">SFwdQ</strong></span></p>
</td>
<td>
<p>
IPv6 queries sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Responsev4</strong></span></p>
</td>
<td>
<p><span><strong class="command">RR</strong></span></p>
</td>
<td>
<p>
IPv4 responses received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Responsev6</strong></span></p>
</td>
<td>
<p><span><strong class="command">RR</strong></span></p>
</td>
<td>
<p>
IPv6 responses received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">NXDOMAIN</strong></span></p>
</td>
<td>
<p><span><strong class="command">RNXD</strong></span></p>
</td>
<td>
<p>
NXDOMAIN received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">SERVFAIL</strong></span></p>
</td>
<td>
<p><span><strong class="command">RFail</strong></span></p>
</td>
<td>
<p>
SERVFAIL received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">FORMERR</strong></span></p>
</td>
<td>
<p><span><strong class="command">RFErr</strong></span></p>
</td>
<td>
<p>
FORMERR received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">OtherError</strong></span></p>
</td>
<td>
<p><span><strong class="command">RErr</strong></span></p>
</td>
<td>
<p>
Other errors received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">EDNS0Fail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
EDNS(0) query failures.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Mismatch</strong></span></p>
</td>
<td>
<p><span><strong class="command">RDupR</strong></span></p>
</td>
<td>
<p>
Mismatch responses received.
The DNS ID, response's source address,
and/or the response's source port does not
match what was expected.
(The port must be 53 or as defined by
the <span><strong class="command">port</strong></span> option.)
This may be an indication of a cache
poisoning attempt.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Truncated</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Truncated responses received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Lame</strong></span></p>
</td>
<td>
<p><span><strong class="command">RLame</strong></span></p>
</td>
<td>
<p>
Lame delegations received.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">Retry</strong></span></p>
</td>
<td>
<p><span><strong class="command">SDupQ</strong></span></p>
</td>
<td>
<p>
Query retries performed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QueryAbort</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Queries aborted due to quota control.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QuerySockFail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Failures in opening query sockets.
One common reason for such failures is a
failure of opening a new socket due to a
limitation on file descriptors.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QueryTimeout</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Query timeouts.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">GlueFetchv4</strong></span></p>
</td>
<td>
<p><span><strong class="command">SSysQ</strong></span></p>
</td>
<td>
<p>
IPv4 NS address fetches invoked.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">GlueFetchv6</strong></span></p>
</td>
<td>
<p><span><strong class="command">SSysQ</strong></span></p>
</td>
<td>
<p>
IPv6 NS address fetches invoked.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">GlueFetchv4Fail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
IPv4 NS address fetch failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">GlueFetchv6Fail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
IPv6 NS address fetch failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ValAttempt</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
DNSSEC validation attempted.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ValOk</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
DNSSEC validation succeeded.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ValNegOk</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
DNSSEC validation on negative information succeeded.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ValFail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
DNSSEC validation failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryRTTnn</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Frequency table on round trip times (RTTs) of
queries.
Each <span><strong class="command">nn</strong></span> specifies the corresponding
frequency.
In the sequence of
<span><strong class="command">nn_1</strong></span>,
<span><strong class="command">nn_2</strong></span>,
...,
<span><strong class="command">nn_m</strong></span>,
the value of <span><strong class="command">nn_i</strong></span> is the
number of queries whose RTTs are between
<span><strong class="command">nn_(i-1)</strong></span> (inclusive) and
<span><strong class="command">nn_i</strong></span> (exclusive) milliseconds.
For the sake of convenience we define
<span><strong class="command">nn_0</strong></span> to be 0.
The last entry should be represented as
<span><strong class="command">nn_m+</strong></span>, which means the
number of queries whose RTTs are equal to or over
<span><strong class="command">nn_m</strong></span> milliseconds.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2606566"></a>Socket I/O Statistics Counters</h4></div></div></div>
<p>
Socket I/O statistics counters are defined per socket
types, which are
<span><strong class="command">UDP4</strong></span> (UDP/IPv4),
<span><strong class="command">UDP6</strong></span> (UDP/IPv6),
<span><strong class="command">TCP4</strong></span> (TCP/IPv4),
<span><strong class="command">TCP6</strong></span> (TCP/IPv6),
<span><strong class="command">Unix</strong></span> (Unix Domain), and
<span><strong class="command">FDwatch</strong></span> (sockets opened outside the
socket module).
In the following table <span><strong class="command">&lt;TYPE&gt;</strong></span>
represents a socket type.
Not all counters are available for all socket types;
exceptions are noted in the description field.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<span class="emphasis"><em>Symbol</em></span>
</p>
</td>
<td>
<p>
<span class="emphasis"><em>Description</em></span>
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;Open</strong></span></p>
</td>
<td>
<p>
Sockets opened successfully.
This counter is not applicable to the
<span><strong class="command">FDwatch</strong></span> type.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;OpenFail</strong></span></p>
</td>
<td>
<p>
Failures of opening sockets.
This counter is not applicable to the
<span><strong class="command">FDwatch</strong></span> type.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;Close</strong></span></p>
</td>
<td>
<p>
Sockets closed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;BindFail</strong></span></p>
</td>
<td>
<p>
Failures of binding sockets.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;ConnFail</strong></span></p>
</td>
<td>
<p>
Failures of connecting sockets.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;Conn</strong></span></p>
</td>
<td>
<p>
Connections established successfully.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;AcceptFail</strong></span></p>
</td>
<td>
<p>
Failures of accepting incoming connection requests.
This counter is not applicable to the
<span><strong class="command">UDP</strong></span> and
<span><strong class="command">FDwatch</strong></span> types.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;Accept</strong></span></p>
</td>
<td>
<p>
Incoming connections successfully accepted.
This counter is not applicable to the
<span><strong class="command">UDP</strong></span> and
<span><strong class="command">FDwatch</strong></span> types.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;SendErr</strong></span></p>
</td>
<td>
<p>
Errors in socket send operations.
This counter corresponds
to <span><strong class="command">SErr</strong></span> counter of
<span><strong class="command">BIND</strong></span> 8.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">&lt;TYPE&gt;RecvErr</strong></span></p>
</td>
<td>
<p>
Errors in socket receive operations.
This includes errors of send operations on a
connected UDP socket notified by an ICMP error
message.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2607076"></a>Compatibility with <span class="emphasis"><em>BIND</em></span> 8 Counters</h4></div></div></div>
<p>
Most statistics counters that were available
in <span><strong class="command">BIND</strong></span> 8 are also supported in
<span><strong class="command">BIND</strong></span> 9 as shown in the above tables.
Here are notes about other counters that do not appear
in these tables.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">RFwdR,SFwdR</strong></span></span></dt>
<dd><p>
These counters are not supported
because <span><strong class="command">BIND</strong></span> 9 does not adopt
the notion of <span class="emphasis"><em>forwarding</em></span>
as <span><strong class="command">BIND</strong></span> 8 did.
</p></dd>
<dt><span class="term"><span><strong class="command">RAXFR</strong></span></span></dt>
<dd><p>
This counter is accessible in the Incoming Queries section.
</p></dd>
<dt><span class="term"><span><strong class="command">RIQ</strong></span></span></dt>
<dd><p>
This counter is accessible in the Incoming Requests section.
</p></dd>
<dt><span class="term"><span><strong class="command">ROpts</strong></span></span></dt>
<dd><p>
This counter is not supported
because <span><strong class="command">BIND</strong></span> 9 does not care
about IP options in the first place.
</p></dd>
</dl></div>
</div>
</div>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="Bv9ARM.ch05.html">Prev</a>�</td>
<td width="20%" align="center">�</td>
<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch07.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Chapter�5.�The <acronym class="acronym">BIND</acronym> 9 Lightweight Resolver�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�Chapter�7.�<acronym class="acronym">BIND</acronym> 9 Security Considerations</td>
</tr>
</table>
</div>
<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>