Bv9ARM.ch06.html revision b05106c7e68077d805893fbae006fae125494fd6
436aad11e01e916f75e68a2e9cb89ac217a990d3Tinderbox User<!--
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater - Copyright (C) 2004-2009 Internet Systems Consortium, Inc. ("ISC")
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User - Copyright (C) 2000-2003 Internet Software Consortium.
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User -
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews - Permission to use, copy, modify, and/or distribute this software for any
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User - purpose with or without fee is hereby granted, provided that the above
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User - copyright notice and this permission notice appear in all copies.
c57668a2fbbe558c1bd21652813616f2f517c469Tinderbox User -
5e047890ac9b745db060d95f7d1b4f876511240dTinderbox User - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
02b47c5d62e1e827743684c28a08e871da454a2dMark Andrews - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User - PERFORMANCE OF THIS SOFTWARE.
e20309353e6246485c521278131d3fced73d7957Tinderbox User-->
e20309353e6246485c521278131d3fced73d7957Tinderbox User<!-- $Id: Bv9ARM.ch06.html,v 1.234 2009/10/09 01:14:47 tbox Exp $ -->
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<html>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User<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">
e20309353e6246485c521278131d3fced73d7957Tinderbox User<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
e20309353e6246485c521278131d3fced73d7957Tinderbox User<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">
df4ebd8217d02dafc12145b55c4d93d0255d1ec7Tinderbox User<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">
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<a accesskey="p" href="Bv9ARM.ch05.html">Prev</a>�</td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<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>
24934f08b9ff81c2be711e566e8002d145573031Tinderbox User</div>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<div class="chapter" lang="en">
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<div class="titlepage"><div><div><h2 class="title">
24934f08b9ff81c2be711e566e8002d145573031Tinderbox User<a name="Bv9ARM.ch06"></a>Chapter�6.�<acronym class="acronym">BIND</acronym> 9 Configuration Reference</h2></div></div></div>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<div class="toc">
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<p><b>Table of Contents</b></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<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>
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2573733">Comment Syntax</a></span></dt>
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater</dl></dd>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic 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#id2574387"><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
eabc9c3c07cd956d3c436bd7614cb162dabdda76Mark Andrews Usage</a></span></dt>
eabc9c3c07cd956d3c436bd7614cb162dabdda76Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574577"><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
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User Usage</a></span></dt>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575073"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575090"><span><strong class="command">include</strong></span> Statement Definition and
24934f08b9ff81c2be711e566e8002d145573031Tinderbox User Usage</a></span></dt>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575113"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575137"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt>
7feccf248d2a20a2ae48b290f58ded5abc853e9aTinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575227"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575353"><span><strong class="command">logging</strong></span> Statement Definition and
c59750de3ea3c7d5890000fb4606e8f5835a52aaTinderbox User Usage</a></span></dt>
80faf1588895fd26490f82f95a7a1b771df1c324Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577420"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577494"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt>
ec7751119a08c6a7250f3187beed69a8b836d349Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577558"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577602"><span><strong class="command">masters</strong></span> Statement Definition and
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews Usage</a></span></dt>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577617"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater Usage</a></span></dt>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<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>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#statschannels"><span><strong class="command">statistics-channels</strong></span> Statement Grammar</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2587582"><span><strong class="command">statistics-channels</strong></span> Statement Definition and
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson Usage</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2587737"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2587857"><span><strong class="command">trusted-keys</strong></span> Statement Definition
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson and Usage</a></span></dt>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2587904"><span><strong class="command">managed-keys</strong></span> Statement Grammar</a></span></dt>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2587955"><span><strong class="command">managed-keys</strong></span> Statement Definition
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews and Usage</a></span></dt>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span><strong class="command">view</strong></span> Statement Grammar</a></span></dt>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2588172"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews Statement Grammar</a></span></dt>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2589860"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews</dl></dd>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2592584">Zone File</a></span></dt>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<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>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2594746">Discussion of MX Records</a></span></dt>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
2a31bd531072824ef252c18303859d6af7451b00Francis Dupont<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2595362">Inverse Mapping in IPv4</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2595489">Other Zone File Directives</a></span></dt>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2595693"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</dl></dd>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<dt><span class="sect1"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch06.html#statistics_counters">Statistics Counters</a></span></dt></dl></dd>
24bf1e02f03577db0feb50b80238c4150c96d05dAutomatic Updater</dl>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews</div>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<p>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User <acronym class="acronym">BIND</acronym> 9 configuration is broadly similar
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater to <acronym class="acronym">BIND</acronym> 8; however, there are a few new
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews areas
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews of configuration, such as views. <acronym class="acronym">BIND</acronym>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User 8 configuration files should work with few alterations in <acronym class="acronym">BIND</acronym>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews 9, although more complex configurations should be reviewed to check
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews if they can be more efficiently implemented using the new features
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews found in <acronym class="acronym">BIND</acronym> 9.
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews </p>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews<p>
01a5c5503482fb3ba52088bf0178a7213273bf96Mark Andrews <acronym class="acronym">BIND</acronym> 4 configuration files can be
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User converted to the new format
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews using the shell script
df4ebd8217d02dafc12145b55c4d93d0255d1ec7Tinderbox User <code class="filename">contrib/named-bootconf/named-bootconf.sh</code>.
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater </p>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<div class="sect1" lang="en">
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater<div class="titlepage"><div><div><h2 class="title" style="clear: both">
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<a name="configuration_file_elements"></a>Configuration File Elements</h2></div></div></div>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User<p>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User Following is a list of elements used throughout the <acronym class="acronym">BIND</acronym> configuration
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User file documentation:
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater </p>
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater<div class="informaltable"><table border="1">
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<colgroup>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater<col>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<col>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater</colgroup>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<tbody>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<tr>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater<td>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater <p>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater <code class="varname">acl_name</code>
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater </p>
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater </td>
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater<td>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater <p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson The name of an <code class="varname">address_match_list</code> as
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater defined by the <span><strong class="command">acl</strong></span> statement.
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User </p>
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User </td>
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User</tr>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<tr>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User <code class="varname">address_match_list</code>
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
f132a836c4e386b1af045dd8fe7106ae61b90bffAutomatic Updater<td>
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews <p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews A list of one or more
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <code class="varname">ip_addr</code>,
5f33078b538b3d317917deb962bd057b2a888db1Tinderbox User <code class="varname">ip_prefix</code>, <code class="varname">key_id</code>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User or <code class="varname">acl_name</code> elements, see
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called &#8220;Address Match Lists&#8221;</a>.
269519eeb959d905ed125f96426e01d725c3b597Tinderbox User </p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<tr>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<td>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater <p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews <code class="varname">masters_list</code>
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </td>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<td>
bc0a53583d92309bebcf93c408e2f3247ebd3d3cAutomatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A named list of one or more <code class="varname">ip_addr</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater with optional <code class="varname">key_id</code> and/or
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater <code class="varname">ip_port</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A <code class="varname">masters_list</code> may include other
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="varname">masters_lists</code>.
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater </p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
19b3dc94bce93fa76bd7e066f9298630dbc9dcb4Automatic Updater <code class="varname">domain_name</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater </td>
7f94d9a8162c9a96b56e66176702b66e79d8e1a2Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater A quoted string which will be used as
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater a DNS name, for example "<code class="literal">my.test.domain</code>".
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </td>
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User</tr>
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User<tr>
7262eb86f2b465822206122921e2f357218f0cfdAutomatic Updater<td>
96ea71632887c58a9d00f47eb318bf76b35903c3Mark Andrews <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="varname">namelist</code>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
bbb069be941f649228760edcc241122933c066d2Automatic Updater </td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
4cda4fd158d6ded5586bacea8c388445d99611eaAutomatic Updater <p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews A list of one or more <code class="varname">domain_name</code>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews elements.
80faf1588895fd26490f82f95a7a1b771df1c324Automatic Updater </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User<tr>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews <code class="varname">dotted_decimal</code>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User </td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User One to four integers valued 0 through
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User 255 separated by dots (`.'), such as <span><strong class="command">123</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">45.67</strong></span> or <span><strong class="command">89.123.45.67</strong></span>.
a792d42c3cdd6cd4608b936c0a06437b8c2d99ccTinderbox User </p>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User </td>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User<td>
cf7e98f59148b559946a7f1ca728471374f1eef3Automatic Updater <p>
0ea1646bf1253f50946ed5e4d3c01c1d2767012bTinderbox User <code class="varname">ip4_addr</code>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews </p>
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
cf7e98f59148b559946a7f1ca728471374f1eef3Automatic Updater <p>
c3fd32ed29e9e419bb56583f4272a506773b1ea0Automatic Updater An IPv4 address with exactly four elements
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson in <code class="varname">dotted_decimal</code> notation.
c3fd32ed29e9e419bb56583f4272a506773b1ea0Automatic Updater </p>
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User </td>
a382ca49c874d38ad3ac8995b49f9f27128e4ca9Automatic Updater</tr>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User<tr>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User <code class="varname">ip6_addr</code>
3857cb6fcabeb79d85de4b3e3e4ab99912b701f8Mark Andrews </p>
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews </td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
9174e44c14b1cb91a651fa1dc29470438c246ab9Automatic Updater An IPv6 address, such as <span><strong class="command">2001:db8::1234</strong></span>.
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson IPv6 scoped addresses that have ambiguity on their
e2caa7536302de34de6cc04025abcd53dc3a499aAutomatic Updater scope zones must be disambiguated by an appropriate
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User zone ID with the percent character (`%') as
8292deab031e7599cd7622aa7675fbe139ca6095Mark Andrews delimiter. It is strongly recommended to use
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews string zone names rather than numeric identifiers,
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews in order to be robust against system configuration
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews changes. However, since there is no standard
e31cfd80616deb9781902306b34a69aa7309b6cbTinderbox User mapping for such names and identifier values,
e31cfd80616deb9781902306b34a69aa7309b6cbTinderbox User currently only interface names as link identifiers
e31cfd80616deb9781902306b34a69aa7309b6cbTinderbox User are supported, assuming one-to-one mapping between
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews interfaces and links. For example, a link-local
b109432c3a939bff66a463be86c371bd88efe3aaAutomatic Updater address <span><strong class="command">fe80::1</strong></span> on the link
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater attached to the interface <span><strong class="command">ne0</strong></span>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews can be specified as <span><strong class="command">fe80::1%ne0</strong></span>.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews Note that on most systems link-local addresses
3351ccbd5c1961404044f8273d54dad405f53960Mark Andrews always have the ambiguity, and need to be
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater disambiguated.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </td>
3351ccbd5c1961404044f8273d54dad405f53960Mark Andrews</tr>
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater<tr>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<td>
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews <p>
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater <code class="varname">ip_addr</code>
0b57424d28c9a67018107133f9fbc0a7dcf057e2Mark Andrews </p>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater </td>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater<td>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater <p>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater An <code class="varname">ip4_addr</code> or <code class="varname">ip6_addr</code>.
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater </p>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater </td>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater</tr>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater<tr>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater<td>
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater <p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <code class="varname">ip_port</code>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </td>
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User<td>
01a5c5503482fb3ba52088bf0178a7213273bf96Mark Andrews <p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User An IP port <code class="varname">number</code>.
dc435f1033bcba88b748074987db6cfd34c057a4Tinderbox User The <code class="varname">number</code> is limited to 0
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews through 65535, with values
dc435f1033bcba88b748074987db6cfd34c057a4Tinderbox User below 1024 typically restricted to use by processes running
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews as root.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User In some cases, an asterisk (`*') character can be used as a
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User placeholder to
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater select a random high-numbered port.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</tr>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<tr>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <code class="varname">ip_prefix</code>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater<td>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater <p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson An IP network specified as an <code class="varname">ip_addr</code>,
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater followed by a slash (`/') and then the number of bits in the
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews netmask.
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews Trailing zeros in a <code class="varname">ip_addr</code>
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User 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
e20309353e6246485c521278131d3fced73d7957Tinderbox User netmask <span><strong class="command">255.0.0.0</strong></span> and <span><strong class="command">1.2.3.0/28</strong></span> is
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews network <span><strong class="command">1.2.3.0</strong></span> with netmask <span><strong class="command">255.255.255.240</strong></span>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
b13d89bd89878137c81b36a36596cca3920f27a4Automatic Updater <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User When specifying a prefix involving a IPv6 scoped address
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the scope may be omitted. In that case the prefix will
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater match packets from any scope.
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews </p>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews </td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews</tr>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<tr>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<td>
f7369b2881b5e63d69600adcedc8ba938303d30cTinderbox User <p>
f7369b2881b5e63d69600adcedc8ba938303d30cTinderbox User <code class="varname">key_id</code>
d6317350b1180aa4517f2e8a92fa8fbcbf904ad8Automatic Updater </p>
bc0a4c01beede169df81a3ee5b614ed9e82339dbAutomatic Updater </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<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>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">key_list</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington A list of one or more
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">key_id</code>s,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington separated by semicolons and ending with a semicolon.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">number</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington A non-negative 32-bit integer
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington (i.e., a number between 0 and 4294967295, inclusive).
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Its acceptable value might further
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington be limited by the context in which it is used.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">path_name</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington A quoted string which will be used as
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington a pathname, such as <code class="filename">zones/master/my.test.domain</code>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User<td>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User <p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <code class="varname">port_list</code>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater A list of an <code class="varname">ip_port</code> or a port
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User range.
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater A port range is specified in the form of
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <strong class="userinput"><code>range</code></strong> followed by
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater two <code class="varname">ip_port</code>s,
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <code class="varname">port_low</code> and
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <code class="varname">port_high</code>, which represents
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater port numbers from <code class="varname">port_low</code> through
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <code class="varname">port_high</code>, inclusive.
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <code class="varname">port_low</code> must not be larger than
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <code class="varname">port_high</code>.
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User For example,
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <strong class="userinput"><code>range 1024 65535</code></strong> represents
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User ports from 1024 through 65535.
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User In either case an asterisk (`*') character is not
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User allowed as a valid <code class="varname">ip_port</code>.
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User </p>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User </td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User</tr>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<tr>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<td>
02b47c5d62e1e827743684c28a08e871da454a2dMark Andrews <p>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <code class="varname">size_spec</code>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User </p>
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater </td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <p>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User A number, the word <strong class="userinput"><code>unlimited</code></strong>,
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User or the word <strong class="userinput"><code>default</code></strong>.
e10d61d84e0b735f1e8eca18644cfdb1b06cad33Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater An <code class="varname">unlimited</code> <code class="varname">size_spec</code> requests unlimited
febbdb34a7f7759922e239655e7429d78d3a8d26Tinderbox User use, or the maximum available amount. A <code class="varname">default size_spec</code> uses
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the limit that was in force when the server was started.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User A <code class="varname">number</code> can optionally be
e01f44b37ba11c9d34f4a8394f950efae5c07f33Automatic Updater followed by a scaling factor:
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <strong class="userinput"><code>K</code></strong> or <strong class="userinput"><code>k</code></strong>
c01dec514a81ecf8c17ca3ef8c3ba95e437295ebAutomatic Updater for kilobytes,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <strong class="userinput"><code>M</code></strong> or <strong class="userinput"><code>m</code></strong>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for megabytes, and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <strong class="userinput"><code>G</code></strong> or <strong class="userinput"><code>g</code></strong> for gigabytes,
3de6db3208d51de1e138b63b9670430c03f99694Automatic Updater which scale by 1024, 1024*1024, and 1024*1024*1024
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater respectively.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The value must be representable as a 64-bit unsigned integer
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington (0 to 18446744073709551615, inclusive).
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Using <code class="varname">unlimited</code> is the best
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington way
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington to safely set a really large number.
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>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Either <strong class="userinput"><code>yes</code></strong> or <strong class="userinput"><code>no</code></strong>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The words <strong class="userinput"><code>true</code></strong> and <strong class="userinput"><code>false</code></strong> are
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington also accepted, as are the numbers <strong class="userinput"><code>1</code></strong>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews and <strong class="userinput"><code>0</code></strong>.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
a26b22914b7bf25f065afb8cdef983766dcd672bAutomatic Updater <code class="varname">dialup_option</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </td>
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington One of <strong class="userinput"><code>yes</code></strong>,
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews <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
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>passive</code></strong>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington When used in a zone, <strong class="userinput"><code>notify-passive</code></strong>,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>refresh</code></strong>, and <strong class="userinput"><code>passive</code></strong>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington are restricted to slave and stub zones.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tbody>
b7aab05edae933e169d5f83c653935b17c7f0a8bMark Andrews</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>
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User<div class="sect3" lang="en">
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<div class="titlepage"><div><div><h4 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="id2573568"></a>Syntax</h4></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting"><code class="varname">address_match_list</code> = address_match_list_element ;
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews [<span class="optional"> address_match_list_element; ... </span>]
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<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 } )
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</pre>
7d704e522860496310bb29c28e76064868401a9cMark Andrews</div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="sect3" lang="en">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="titlepage"><div><div><h4 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="id2573595"></a>Definition and Usage</h4></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Address match lists are primarily used to determine access
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington control for various server operations. They are also used in
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the <span><strong class="command">listen-on</strong></span> and <span><strong class="command">sortlist</strong></span>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington statements. The elements which constitute an address match
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington list can be any of the following:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="itemizedlist"><ul type="disc">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<li>an IP address (IPv4 or IPv6)</li>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<li>an IP prefix (in `/' notation)</li>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<li>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a key ID, as defined by the <span><strong class="command">key</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statement
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </li>
56effd2e3f579fd77b1fb37d47871d1bf1286bc4Automatic Updater<li>the name of an address match list defined with
42bee07ebb8152a6ec2f87f4790d87368c24704cAutomatic Updater the <span><strong class="command">acl</strong></span> statement
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </li>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<li>a nested address match list enclosed in braces</li>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</ul></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews Elements can be negated with a leading exclamation mark (`!'),
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington and the match list names "any", "none", "localhost", and
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews "localnets" are predefined. More information on those names
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington can be found in the description of the acl statement.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews </p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews The addition of the key clause made the name of this syntactic
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews element something of a misnomer, since security keys can be used
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews to validate access without regard to a host or network address.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Nonetheless, the term "address match list" is still used
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington throughout the documentation.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington When a given IP address or prefix is compared to an address
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington match list, the comparison takes place in approximately O(1)
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington time. However, key comparisons require that the list of keys
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington be traversed until a matching key is found, and therefore may
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington be somewhat slower.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The interpretation of a match depends on whether the list is being
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User used for access control, defining <span><strong class="command">listen-on</strong></span> ports, or in a
89623368b8f662d458d9964b923050f33c5f75b0Tinderbox User <span><strong class="command">sortlist</strong></span>, and whether the element was negated.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
febbdb34a7f7759922e239655e7429d78d3a8d26Tinderbox User When used as an access control list, a non-negated match
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User allows access and a negated match denies access. If
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User there is no match, access is denied. The clauses
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <span><strong class="command">allow-notify</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">allow-recursion</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">allow-recursion-on</strong></span>,
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User <span><strong class="command">allow-query</strong></span>,
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User <span><strong class="command">allow-query-on</strong></span>,
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User <span><strong class="command">allow-query-cache</strong></span>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">allow-query-cache-on</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">allow-transfer</strong></span>,
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews <span><strong class="command">allow-update</strong></span>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">allow-update-forwarding</strong></span>, and
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">blackhole</strong></span> all use address match
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User lists. Similarly, the <span><strong class="command">listen-on</strong></span> option will cause the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User server to refuse queries on any of the machine's
cc5a9ce75af9870f2cb9e2bf00548c2f7e6398d6Automatic Updater addresses which do not match the list.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews Order of insertion is significant. If more than one element
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews in an ACL is found to match a given IP address or prefix,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User preference will be given to the one that came
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater <span class="emphasis"><em>first</em></span> in the ACL definition.
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater Because of this first-match behavior, an element that
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater defines a subset of another element in the list should
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater come before the broader element, regardless of whether
91faa748a27dee38f6caea461d3e87f15b93abeaTinderbox User either is negated. For example, in
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">1.2.3/24; ! 1.2.3.13;</strong></span>
91faa748a27dee38f6caea461d3e87f15b93abeaTinderbox User the 1.2.3.13 element is completely useless because the
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews algorithm will match any lookup for 1.2.3.13 to the 1.2.3/24
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews element. Using <span><strong class="command">! 1.2.3.13; 1.2.3/24</strong></span> fixes
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews that problem by having 1.2.3.13 blocked by the negation, but
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews all other 1.2.3.* hosts fall through.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews</div>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews</div>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<div class="sect2" lang="en">
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<div class="titlepage"><div><div><h3 class="title">
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<a name="id2573733"></a>Comment Syntax</h3></div></div></div>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<p>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User The <acronym class="acronym">BIND</acronym> 9 comment syntax allows for
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User comments to appear
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User anywhere that whitespace may appear in a <acronym class="acronym">BIND</acronym> configuration
861836e5f5df62bfaea9ad8923a05278d5ab2f3dTinderbox User file. To appeal to programmers of all kinds, they can be written
e8c17c74535be290abaaa160a434ed80bf0ad2feMark Andrews in the C, C++, or shell/perl style.
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User </p>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater<div class="sect3" lang="en">
9c446b72069d0ab9f710502f4d7048e50875fccbAutomatic Updater<div class="titlepage"><div><div><h4 class="title">
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater<a name="id2573748"></a>Syntax</h4></div></div></div>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater<p>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User </p>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User<pre class="programlisting">/* This is a <acronym class="acronym">BIND</acronym> comment as in C */</pre>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<pre class="programlisting">// This is a <acronym class="acronym">BIND</acronym> comment as in C++</pre>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<pre class="programlisting"># This is a <acronym class="acronym">BIND</acronym> comment as in common UNIX shells
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater# and perl</pre>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</div>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<div class="sect3" lang="en">
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<div class="titlepage"><div><div><h4 class="title">
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<a name="id2573778"></a>Definition and Usage</h4></div></div></div>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater Comments may appear anywhere that whitespace may appear in
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater a <acronym class="acronym">BIND</acronym> configuration file.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater C-style comments start with the two characters /* (slash,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater star) and end with */ (star, slash). Because they are completely
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater delimited with these characters, they can be used to comment only
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater a portion of a line or to span multiple lines.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater C-style comments cannot be nested. For example, the following
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater is not valid because the entire comment ends with the first */:
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<pre class="programlisting">/* This is the start of a comment.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater This is still part of the comment.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater/* This is an incorrect attempt at nesting a comment. */
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater This is no longer in any comment. */
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</pre>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater C++-style comments start with the two characters // (slash,
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater slash) and continue to the end of the physical line. They cannot
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater be continued across multiple physical lines; to have one logical
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User comment span multiple lines, each line must use the // pair.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater For example:
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User</p>
fe84edc17e0d582cf7b4270f8df9d4742a107b1cAutomatic Updater<pre class="programlisting">// This is the start of a comment. The next line
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User// is a new comment, even though it is logically
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User// part of the previous comment.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</pre>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<p>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews </p>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews<p>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews Shell-style (or perl-style, if you prefer) comments start
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater with the character <code class="literal">#</code> (number sign)
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater and continue to the end of the
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater physical line, as in C++ comments.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater For example:
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<pre class="programlisting"># This is the start of a comment. The next line
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User# is a new comment, even though it is logically
4ea3649f028ea6a1e42377082a7ccf8f789fb950Automatic Updater# part of the previous comment.
40072ce70bc4125329addb4aaa56d18a1230bc17Automatic Updater</pre>
60d5d17479b47c03b9c7c86f54269718103750b8Automatic Updater<p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater
a382ca49c874d38ad3ac8995b49f9f27128e4ca9Automatic Updater </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
60d5d17479b47c03b9c7c86f54269718103750b8Automatic Updater<h3 class="title">Warning</h3>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater You cannot use the semicolon (`;') character
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater to start a comment such as you would in a zone file. The
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater semicolon indicates the end of a configuration
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater statement.
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</div>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</div>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</div>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</div>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<div class="sect1" lang="en">
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<div class="titlepage"><div><div><h2 class="title" style="clear: both">
19dbf2e20df03f2b81ed1f347e27718084374059Automatic Updater<a name="Configuration_File_Grammar"></a>Configuration File Grammar</h2></div></div></div>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater A <acronym class="acronym">BIND</acronym> 9 configuration consists of
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater statements and comments.
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater Statements end with a semicolon. Statements and comments are the
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater only elements that can appear without enclosing braces. Many
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater statements contain a block of sub-statements, which are also
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater terminated with a semicolon.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The following statements are supported:
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User<div class="informaltable"><table border="1">
7dd02af3c9350553e1d52d980a7812425b3f1295Automatic Updater<colgroup>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<col>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<col>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington</colgroup>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington<tbody>
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews<tr>
01f91b9cd440833f66e7476e43659655cb52ad10Automatic Updater<td>
3e5b24a74c03d5b52f32d138e64e427bd2cbc8f3Automatic Updater <p><span><strong class="command">acl</strong></span></p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<td>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User <p>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User defines a named IP address
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User matching list, for access control and other uses.
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User </p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User</tr>
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews<tr>
aa49af836ce7a7a2888f5cedf4cbb14ff4dc1d11Mark Andrews<td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <p><span><strong class="command">controls</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<td>
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews <p>
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews declares control channels to be used
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews by the <span><strong class="command">rndc</strong></span> utility.
be5e43393922d459eae5c8c467c0320d4a018666Tinderbox User </p>
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews </td>
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews</tr>
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews<tr>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<td>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <p><span><strong class="command">include</strong></span></p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<td>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt <p>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt includes a file.
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt </p>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt </td>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt</tr>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<tr>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<td>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt <p><span><strong class="command">key</strong></span></p>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt </td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <p>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt specifies key information for use in
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt authentication and authorization using TSIG.
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">logging</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater specifies what the server logs, and where
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater the log messages are sent.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<td>
e20309353e6246485c521278131d3fced73d7957Tinderbox User <p><span><strong class="command">lwres</strong></span></p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User </td>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<td>
ff62ab3c2e6274f19190ded15548c723d38bbbe3Automatic Updater <p>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User configures <span><strong class="command">named</strong></span> to
e20309353e6246485c521278131d3fced73d7957Tinderbox User also act as a light-weight resolver daemon (<span><strong class="command">lwresd</strong></span>).
e20309353e6246485c521278131d3fced73d7957Tinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<tr>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <p><span><strong class="command">masters</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews defines a named masters list for
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews inclusion in stub and slave zone masters clauses.
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews</tr>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<tr>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <p><span><strong class="command">options</strong></span></p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews controls global server configuration
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews options and sets defaults for other statements.
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews</tr>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<tr>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">server</strong></span></p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User sets certain configuration options on
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a per-server basis.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">statistics-channels</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User declares communication channels to get access to
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater <span><strong class="command">named</strong></span> statistics.
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
88d58d79c5bc7ce3c20a42461a5070116c736836Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater <p><span><strong class="command">trusted-keys</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater defines trusted DNSSEC keys.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">managed-keys</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <p>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater lists DNSSEC keys to be kept up to date
9fa39c73fc1d8bc44fdbbb79a1d26b837e7dd555Mark Andrews using RFC 5011 trust anchor maintenance.
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater <p><span><strong class="command">view</strong></span></p>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater </td>
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User defines a view.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews<td>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews <p><span><strong class="command">zone</strong></span></p>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews </td>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews<td>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User defines a zone.
560d6da48f066000541dd43f5d407644dee12bebTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User</tr>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater</tbody>
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User</table></div>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<p>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User The <span><strong class="command">logging</strong></span> and
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <span><strong class="command">options</strong></span> statements may only occur once
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User per
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User configuration.
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User </p>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<div class="sect2" lang="en">
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<div class="titlepage"><div><div><h3 class="title">
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<a name="id2574387"></a><span><strong class="command">acl</strong></span> Statement Grammar</h3></div></div></div>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<pre class="programlisting"><span><strong class="command">acl</strong></span> acl-name {
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews address_match_list
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews};
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews</pre>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews</div>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<div class="sect2" lang="en">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="titlepage"><div><div><h3 class="title">
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont<a name="acl"></a><span><strong class="command">acl</strong></span> Statement Definition and
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont Usage</h3></div></div></div>
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont<p>
4dca64bb8991502db368028aeeba2f832d3b971dAutomatic Updater The <span><strong class="command">acl</strong></span> statement assigns a symbolic
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont name to an address match list. It gets its name from a primary
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User use of address match lists: Access Control Lists (ACLs).
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater Note that an address match list's name must be defined
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater with <span><strong class="command">acl</strong></span> before it can be used
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater elsewhere; no forward references are allowed.
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater </p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<p>
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User The following ACLs are built-in:
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User </p>
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User<div class="informaltable"><table border="1">
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<colgroup>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<col>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<col>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater</colgroup>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<tbody>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User<tr>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<td>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater <p><span><strong class="command">any</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User<td>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Matches all hosts.
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User </p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater </td>
e20309353e6246485c521278131d3fced73d7957Tinderbox User</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
e20309353e6246485c521278131d3fced73d7957Tinderbox User <p><span><strong class="command">none</strong></span></p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater <p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater Matches no hosts.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
af9cf290cea6ada6ce27b51c724ab77ad5d73fa0Tinderbox User<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater <p><span><strong class="command">localhost</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
2da2220fe7af2c45724b50b0187523b1fab0cf08Rob Austein<td>
af9cf290cea6ada6ce27b51c724ab77ad5d73fa0Tinderbox User <p>
e171a4137c6ba348957e61b7c4c3541493c0da02Automatic Updater Matches the IPv4 and IPv6 addresses of all network
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater interfaces on the system.
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User<tr>
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User<td>
b3386fba31414344f38f0c30849c056dceb22dceTinderbox User <p><span><strong class="command">localnets</strong></span></p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater Matches any host on an IPv4 or IPv6 network
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for which the system has an interface.
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater Some systems do not provide a way to determine the prefix
af9cf290cea6ada6ce27b51c724ab77ad5d73fa0Tinderbox User lengths of
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater local IPv6 addresses.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User In such a case, <span><strong class="command">localnets</strong></span>
6671e343b8c7e44ac10a7900fde59555fbc71571Automatic Updater only matches the local
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater IPv6 addresses, just like <span><strong class="command">localhost</strong></span>.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </td>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</tr>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</tbody>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</table></div>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</div>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<div class="sect2" lang="en">
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User<div class="titlepage"><div><div><h3 class="title">
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater<a name="id2574577"></a><span><strong class="command">controls</strong></span> Statement Grammar</h3></div></div></div>
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater<pre class="programlisting"><span><strong class="command">controls</strong></span> {
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [ inet ( ip_addr | * ) [ port ip_port ]
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User allow { <em class="replaceable"><code> address_match_list </code></em> }
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater keys { <em class="replaceable"><code>key_list</code></em> }; ]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater [ inet ...; ]
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews [ 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>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews keys { <em class="replaceable"><code>key_list</code></em> }; ]
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews [ unix ...; ]
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User};
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater</pre>
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater</div>
664917bedafa65dee4349c84324a31731aa1e228Francis Dupont<div class="sect2" lang="en">
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
af9cf290cea6ada6ce27b51c724ab77ad5d73fa0Tinderbox User<a name="controls_statement_definition_and_usage"></a><span><strong class="command">controls</strong></span> Statement Definition and
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User Usage</h3></div></div></div>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User The <span><strong class="command">controls</strong></span> statement declares control
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater channels to be used by system administrators to control the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater operation of the name server. These control channels are
e20309353e6246485c521278131d3fced73d7957Tinderbox User used by the <span><strong class="command">rndc</strong></span> utility to send
e20309353e6246485c521278131d3fced73d7957Tinderbox User commands to and retrieve non-DNS results from a name server.
e20309353e6246485c521278131d3fced73d7957Tinderbox User </p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<p>
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater An <span><strong class="command">inet</strong></span> control channel is a TCP socket
f8a9a38ee40c139a8d145ac76ecbff3a0f986453Mark Andrews listening at the specified <span><strong class="command">ip_port</strong></span> on the
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater specified <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User address. An <span><strong class="command">ip_addr</strong></span> of <code class="literal">*</code> (asterisk) is
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews interpreted as the IPv4 wildcard address; connections will be
9d80d23172c30fd63e5046a7e69b8445e564ff31Automatic Updater accepted on any of the system's IPv4 addresses.
e20309353e6246485c521278131d3fced73d7957Tinderbox User To listen on the IPv6 wildcard address,
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews If you will only use <span><strong class="command">rndc</strong></span> on the local host,
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews using the loopback address (<code class="literal">127.0.0.1</code>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews or <code class="literal">::1</code>) is recommended for maximum security.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews If no port is specified, port 953 is used. The asterisk
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews "<code class="literal">*</code>" cannot be used for <span><strong class="command">ip_port</strong></span>.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews The ability to issue commands over the control channel is
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews restricted by the <span><strong class="command">allow</strong></span> and
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <span><strong class="command">keys</strong></span> clauses.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews Connections to the control channel are permitted based on the
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <span><strong class="command">address_match_list</strong></span>. This is for simple
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews IP address based filtering only; any <span><strong class="command">key_id</strong></span>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews elements of the <span><strong class="command">address_match_list</strong></span>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews are ignored.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User A <span><strong class="command">unix</strong></span> control channel is a UNIX domain
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User socket listening at the specified path in the file system.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User Access to the socket is specified by the <span><strong class="command">perm</strong></span>,
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User <span><strong class="command">owner</strong></span> and <span><strong class="command">group</strong></span> clauses.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User Note on some platforms (SunOS and Solaris) the permissions
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User (<span><strong class="command">perm</strong></span>) are applied to the parent directory
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User as the permissions on the socket itself are ignored.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </p>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User<p>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User The primary authorization mechanism of the command
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User channel is the <span><strong class="command">key_list</strong></span>, which
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User contains a list of <span><strong class="command">key_id</strong></span>s.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User Each <span><strong class="command">key_id</strong></span> in the <span><strong class="command">key_list</strong></span>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User is authorized to execute commands over the control channel.
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User 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>)
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User for information about configuring keys in <span><strong class="command">rndc</strong></span>.
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User </p>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User<p>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User If no <span><strong class="command">controls</strong></span> statement is present,
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User <span><strong class="command">named</strong></span> will set up a default
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User control channel listening on the loopback address 127.0.0.1
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User and its IPv6 counterpart ::1.
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User In this case, and also when the <span><strong class="command">controls</strong></span> statement
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User is present but does not have a <span><strong class="command">keys</strong></span> clause,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">named</strong></span> will attempt to load the command channel key
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User from the file <code class="filename">rndc.key</code> in
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews <code class="filename">/etc</code> (or whatever <code class="varname">sysconfdir</code>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews was specified as when <acronym class="acronym">BIND</acronym> was built).
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews To create a <code class="filename">rndc.key</code> file, run
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews <strong class="userinput"><code>rndc-confgen -a</code></strong>.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews The <code class="filename">rndc.key</code> feature was created to
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews ease the transition of systems from <acronym class="acronym">BIND</acronym> 8,
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews which did not have digital signatures on its command channel
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews messages and thus did not have a <span><strong class="command">keys</strong></span> clause.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews It makes it possible to use an existing <acronym class="acronym">BIND</acronym> 8
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews configuration file in <acronym class="acronym">BIND</acronym> 9 unchanged,
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews and still have <span><strong class="command">rndc</strong></span> work the same way
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User <span><strong class="command">ndc</strong></span> worked in BIND 8, simply by executing the
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User command <strong class="userinput"><code>rndc-confgen -a</code></strong> after BIND 9 is
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User installed.
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater Since the <code class="filename">rndc.key</code> feature
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater is only intended to allow the backward-compatible usage of
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews <acronym class="acronym">BIND</acronym> 8 configuration files, this
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User feature does not
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User have a high degree of configurability. You cannot easily change
8c9c79e5fea0cb698026a74821695907c8312a46Mark Andrews the key name or the size of the secret, so you should make a
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <code class="filename">rndc.conf</code> with your own key if you
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User wish to change
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User those things. The <code class="filename">rndc.key</code> file
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User also has its
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater permissions set such that only the owner of the file (the user that
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">named</strong></span> is running as) can access it.
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater If you
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater desire greater flexibility in allowing other users to access
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">rndc</strong></span> commands, then you need to create
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User a
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater <code class="filename">rndc.conf</code> file and make it group
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews readable by a group
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews that contains the users who should have access.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews To disable the command channel, use an empty
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <span><strong class="command">controls</strong></span> statement:
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <span><strong class="command">controls { };</strong></span>.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="id2575073"></a><span><strong class="command">include</strong></span> Statement Grammar</h3></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting"><span><strong class="command">include</strong></span> <em class="replaceable"><code>filename</code></em>;</pre>
166c467a9414778bdd0f2a1e4a32220843c0fde3Tinderbox User</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="id2575090"></a><span><strong class="command">include</strong></span> Statement Definition and
166c467a9414778bdd0f2a1e4a32220843c0fde3Tinderbox User Usage</h3></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
e007e3e5b0316c6c05698a71101885743aca22bdAutomatic Updater The <span><strong class="command">include</strong></span> statement inserts the
e007e3e5b0316c6c05698a71101885743aca22bdAutomatic Updater specified file at the point where the <span><strong class="command">include</strong></span>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews statement is encountered. The <span><strong class="command">include</strong></span>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews statement facilitates the administration of configuration
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews files
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews by permitting the reading or writing of some things but not
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews others. For example, the statement could include private keys
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews that are readable only by the name server.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews</div>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<div class="sect2" lang="en">
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<div class="titlepage"><div><div><h3 class="title">
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<a name="id2575113"></a><span><strong class="command">key</strong></span> Statement Grammar</h3></div></div></div>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<pre class="programlisting"><span><strong class="command">key</strong></span> <em class="replaceable"><code>key_id</code></em> {
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews algorithm <em class="replaceable"><code>string</code></em>;
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews secret <em class="replaceable"><code>string</code></em>;
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews};
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews</pre>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews</div>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<div class="sect2" lang="en">
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<div class="titlepage"><div><div><h3 class="title">
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<a name="id2575137"></a><span><strong class="command">key</strong></span> Statement Definition and Usage</h3></div></div></div>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The <span><strong class="command">key</strong></span> statement defines a shared
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews secret key for use with TSIG (see <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called &#8220;TSIG&#8221;</a>)
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews or the command channel
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews Usage">the section called &#8220;<span><strong class="command">controls</strong></span> Statement Definition and
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews Usage&#8221;</a>).
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The <span><strong class="command">key</strong></span> statement can occur at the
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews top level
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews of the configuration file or inside a <span><strong class="command">view</strong></span>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews statement. Keys defined in top-level <span><strong class="command">key</strong></span>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews statements can be used in all views. Keys intended for use in
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews a <span><strong class="command">controls</strong></span> statement
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews Usage">the section called &#8220;<span><strong class="command">controls</strong></span> Statement Definition and
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews Usage&#8221;</a>)
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews must be defined at the top level.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The <em class="replaceable"><code>key_id</code></em>, also known as the
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews key name, is a domain name uniquely identifying the key. It can
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews be used in a <span><strong class="command">server</strong></span>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User statement to cause requests sent to that
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington server to be signed with this key, or in address match lists to
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington verify that incoming requests have been signed with a key
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater matching this name, algorithm, and secret.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
bbf7c3fd96ae5e02cb84743c581862e35327032aAutomatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <em class="replaceable"><code>algorithm_id</code></em> is a string
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater that specifies a security/authentication algorithm. Named
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater supports <code class="literal">hmac-md5</code>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>,
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User <code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington and <code class="literal">hmac-sha512</code> TSIG authentication.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews Truncated hashes are supported by appending the minimum
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User number of required bits preceded by a dash, e.g.
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User <code class="literal">hmac-sha1-80</code>. The
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater <em class="replaceable"><code>secret_string</code></em> is the secret
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater to be used by the algorithm, and is treated as a base-64
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User encoded string.
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</div>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="sect2" lang="en">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="titlepage"><div><div><h3 class="title">
e135e3c4b1f4f986f00997f5ad5866effb203139Tinderbox User<a name="id2575227"></a><span><strong class="command">logging</strong></span> Statement Grammar</h3></div></div></div>
6fd5f289d8455283fad33d1051e6fbaa3bec43d5Tinderbox User<pre class="programlisting"><span><strong class="command">logging</strong></span> {
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater [ <span><strong class="command">channel</strong></span> <em class="replaceable"><code>channel_name</code></em> {
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User ( <span><strong class="command">file</strong></span> <em class="replaceable"><code>path_name</code></em>
5e1503eb9464c2284bb782228d4c315087a2415fAutomatic Updater [ <span><strong class="command">versions</strong></span> ( <em class="replaceable"><code>number</code></em> | <span><strong class="command">unlimited</strong></span> ) ]
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater [ <span><strong class="command">size</strong></span> <em class="replaceable"><code>size spec</code></em> ]
6fd5f289d8455283fad33d1051e6fbaa3bec43d5Tinderbox User | <span><strong class="command">syslog</strong></span> <em class="replaceable"><code>syslog_facility</code></em>
08d53af7d51409036462fa80fb1bde7a8c2ac123Automatic Updater | <span><strong class="command">stderr</strong></span>
08d53af7d51409036462fa80fb1bde7a8c2ac123Automatic Updater | <span><strong class="command">null</strong></span> );
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic 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> |
ec7751119a08c6a7250f3187beed69a8b836d349Tinderbox User <code class="option">info</code> | <code class="option">debug</code> [ <em class="replaceable"><code>level</code></em> ] | <code class="option">dynamic</code> ); ]
6fd5f289d8455283fad33d1051e6fbaa3bec43d5Tinderbox User [ <span><strong class="command">print-category</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
6fd5f289d8455283fad33d1051e6fbaa3bec43d5Tinderbox User [ <span><strong class="command">print-severity</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater [ <span><strong class="command">print-time</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater }; ]
07d9d0dbcc0c79deb3c34f4a8af05ac68a6800e4Mark Andrews [ <span><strong class="command">category</strong></span> <em class="replaceable"><code>category_name</code></em> {
07d9d0dbcc0c79deb3c34f4a8af05ac68a6800e4Mark Andrews <em class="replaceable"><code>channel_name</code></em> ; [ <em class="replaceable"><code>channel_name</code></em> ; ... ]
a66012b52c20200f118781463db4e4ee44454298Automatic Updater }; ]
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User ...
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User};
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater</pre>
e2e3f655d133f08056c9035412d4c013aab234e7Automatic Updater</div>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<div class="sect2" lang="en">
e135e3c4b1f4f986f00997f5ad5866effb203139Tinderbox User<div class="titlepage"><div><div><h3 class="title">
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User<a name="id2575353"></a><span><strong class="command">logging</strong></span> Statement Definition and
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater Usage</h3></div></div></div>
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater<p>
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater The <span><strong class="command">logging</strong></span> statement configures a
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User wide
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater variety of logging options for the name server. Its <span><strong class="command">channel</strong></span> phrase
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater associates output methods, format options and severity levels with
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User a name that can then be used with the <span><strong class="command">category</strong></span> phrase
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User to select how various classes of messages are logged.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<p>
e2e3f655d133f08056c9035412d4c013aab234e7Automatic Updater Only one <span><strong class="command">logging</strong></span> statement is used to
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User define
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington as many channels and categories as are wanted. If there is no <span><strong class="command">logging</strong></span> statement,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the logging configuration will be:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting">logging {
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington category default { default_syslog; default_debug; };
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater category unmatched { null; };
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater};
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User In <acronym class="acronym">BIND</acronym> 9, the logging configuration
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User is only established when
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User the entire configuration file has been parsed. In <acronym class="acronym">BIND</acronym> 8, it was
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User established as soon as the <span><strong class="command">logging</strong></span>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User statement
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User was parsed. When the server is starting up, all logging messages
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater regarding syntax errors in the configuration file go to the default
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User channels, or to standard error if the "<code class="option">-g</code>" option
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User was specified.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
85b52a5959291f5014442814488ccb267cdea369Tinderbox User<div class="sect3" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h4 class="title">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<a name="id2575405"></a>The <span><strong class="command">channel</strong></span> Phrase</h4></div></div></div>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater All log output goes to one or more <span class="emphasis"><em>channels</em></span>;
e062b72f783cdb436a1a57a630bdff471dbb3038Mark Andrews you can make as many of them as you want.
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<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
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater particular syslog facility, to the standard error stream, or are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater discarded. It can optionally also limit the message severity level
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User that will be accepted by the channel (the default is
85b52a5959291f5014442814488ccb267cdea369Tinderbox User <span><strong class="command">info</strong></span>), and whether to include a
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">named</strong></span>-generated time stamp, the
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews category name
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews and/or severity level (the default is not to include any).
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <span><strong class="command">null</strong></span> destination clause
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater causes all messages sent to the channel to be discarded;
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater in that case, other options for the channel are meaningless.
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews The <span><strong class="command">file</strong></span> destination clause directs
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews the channel
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to a disk file. It can include limitations
52cfbde0bd391cfb37e3c1a1b460c16ba6bf1a73Automatic Updater both on how large the file is allowed to become, and how many
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User versions
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User of the file will be saved each time the file is opened.
24e0e8d17df315d5d494ca933874e545eadce773Automatic Updater </p>
52cfbde0bd391cfb37e3c1a1b460c16ba6bf1a73Automatic Updater<p>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews If you use the <span><strong class="command">versions</strong></span> log file
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User option, then
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews <span><strong class="command">named</strong></span> will retain that many backup
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater versions of the file by
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User renaming them when opening. For example, if you choose to keep
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater three old versions
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User of the file <code class="filename">lamers.log</code>, then just
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User before it is opened
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User <code class="filename">lamers.log.1</code> is renamed to
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <code class="filename">lamers.log.2</code>, <code class="filename">lamers.log.0</code> is renamed
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to <code class="filename">lamers.log.1</code>, and <code class="filename">lamers.log</code> is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater renamed to <code class="filename">lamers.log.0</code>.
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater You can say <span><strong class="command">versions unlimited</strong></span> to
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater not limit
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater the number of versions.
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater If a <span><strong class="command">size</strong></span> option is associated with
0c7657e9302e7f9a8fe4f32fe561dc7e7e7ee6b5Automatic Updater the log file,
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater then renaming is only done when the file being opened exceeds the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User indicated size. No backup versions are kept by default; any
dcff0bfce2963a14e5af5774fd8901a42f18c720Tinderbox User existing
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User log file is simply appended.
12ee3c02ab36d7e7430bd705cc289db1a69a5733Mark Andrews </p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<p>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews The <span><strong class="command">size</strong></span> option for files is used
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater to limit log
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater growth. If the file ever exceeds the size, then <span><strong class="command">named</strong></span> will
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User stop writing to the file unless it has a <span><strong class="command">versions</strong></span> option
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews associated with it. If backup versions are kept, the files are
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater rolled as
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater described above and a new one begun. If there is no
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <span><strong class="command">versions</strong></span> option, no more data will
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater be written to the log
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User until some out-of-band mechanism removes or truncates the log to
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User less than the
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User maximum size. The default behavior is not to limit the size of
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews file.
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews </p>
fd8fb4df8499e292daeac765f599ac7c507d9ca3Mark Andrews<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Example usage of the <span><strong class="command">size</strong></span> and
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">versions</strong></span> options:
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater </p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater<pre class="programlisting">channel an_example_channel {
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User file "example.log" versions 3 size 20m;
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater print-time yes;
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater print-category yes;
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater};
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater</pre>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater The <span><strong class="command">syslog</strong></span> destination clause
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater directs the
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater channel to the system log. Its argument is a
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater syslog facility as described in the <span><strong class="command">syslog</strong></span> man
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User page. Known facilities are <span><strong class="command">kern</strong></span>, <span><strong class="command">user</strong></span>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">mail</strong></span>, <span><strong class="command">daemon</strong></span>, <span><strong class="command">auth</strong></span>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">syslog</strong></span>, <span><strong class="command">lpr</strong></span>, <span><strong class="command">news</strong></span>,
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User <span><strong class="command">uucp</strong></span>, <span><strong class="command">cron</strong></span>, <span><strong class="command">authpriv</strong></span>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">ftp</strong></span>, <span><strong class="command">local0</strong></span>, <span><strong class="command">local1</strong></span>,
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater <span><strong class="command">local2</strong></span>, <span><strong class="command">local3</strong></span>, <span><strong class="command">local4</strong></span>,
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <span><strong class="command">local5</strong></span>, <span><strong class="command">local6</strong></span> and
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">local7</strong></span>, however not all facilities
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User are supported on
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User all operating systems.
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews How <span><strong class="command">syslog</strong></span> will handle messages
560d6da48f066000541dd43f5d407644dee12bebTinderbox User sent to
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater this facility is described in the <span><strong class="command">syslog.conf</strong></span> man
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater page. If you have a system which uses a very old version of <span><strong class="command">syslog</strong></span> that
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater only uses two arguments to the <span><strong class="command">openlog()</strong></span> function,
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater then this clause is silently ignored.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater The <span><strong class="command">severity</strong></span> clause works like <span><strong class="command">syslog</strong></span>'s
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater "priorities", except that they can also be used if you are writing
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater straight to a file rather than using <span><strong class="command">syslog</strong></span>.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Messages which are not at least of the severity level given will
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater not be selected for the channel; messages of higher severity
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User levels
560d6da48f066000541dd43f5d407644dee12bebTinderbox User will be accepted.
560d6da48f066000541dd43f5d407644dee12bebTinderbox User </p>
9bc394fffdd50f6e47614b2d317da7274122366fTinderbox User<p>
560d6da48f066000541dd43f5d407644dee12bebTinderbox User If you are using <span><strong class="command">syslog</strong></span>, then the <span><strong class="command">syslog.conf</strong></span> priorities
560d6da48f066000541dd43f5d407644dee12bebTinderbox User will also determine what eventually passes through. For example,
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews defining a channel facility and severity as <span><strong class="command">daemon</strong></span> and <span><strong class="command">debug</strong></span> but
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User only logging <span><strong class="command">daemon.warning</strong></span> via <span><strong class="command">syslog.conf</strong></span> will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater cause messages of severity <span><strong class="command">info</strong></span> and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">notice</strong></span> to
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater be dropped. If the situation were reversed, with <span><strong class="command">named</strong></span> writing
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater messages of only <span><strong class="command">warning</strong></span> or higher,
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater then <span><strong class="command">syslogd</strong></span> would
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater print all messages it received from the channel.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater The <span><strong class="command">stderr</strong></span> destination clause
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User directs the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User channel to the server's standard error stream. This is intended
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User for
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User use when the server is running as a foreground process, for
0a50626faa2f8941f55bf435d3965d490bb5d026Tinderbox User example
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews when debugging a configuration.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
e0bf4fc289705375be65c05a8fb085d514a98c97Tinderbox User<p>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater The server can supply extensive debugging information when
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater it is in debugging mode. If the server's global debug level is
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User greater
a6e1f63f50af688610ebd2521ba7f028767b51f3Mark Andrews than zero, then debugging mode will be active. The global debug
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater level is set either by starting the <span><strong class="command">named</strong></span> server
4d813066e967a36c407ee641155ada0c614d4dc6Automatic Updater with the <code class="option">-d</code> flag followed by a positive integer,
4d813066e967a36c407ee641155ada0c614d4dc6Automatic Updater or by running <span><strong class="command">rndc trace</strong></span>.
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater The global debug level
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater can be set to zero, and debugging mode turned off, by running <span><strong class="command">rndc
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrewsnotrace</strong></span>. All debugging messages in the server have a debug
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater level, and higher debug levels give more detailed output. Channels
e0bf4fc289705375be65c05a8fb085d514a98c97Tinderbox User that specify a specific debug severity, for example:
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<pre class="programlisting">channel specific_debug_level {
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater file "foo";
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews severity debug 3;
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater};
4d813066e967a36c407ee641155ada0c614d4dc6Automatic Updater</pre>
dbd021853bb1cd6ab128e8da8865f5965030aedcTinderbox User<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews will get debugging output of level 3 or less any time the
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater server is in debugging mode, regardless of the global debugging
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater level. Channels with <span><strong class="command">dynamic</strong></span>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User severity use the
4d813066e967a36c407ee641155ada0c614d4dc6Automatic Updater server's global debug level to determine what messages to print.
0a50626faa2f8941f55bf435d3965d490bb5d026Tinderbox User </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<p>
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews If <span><strong class="command">print-time</strong></span> has been turned on,
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User then
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User the date and time will be logged. <span><strong class="command">print-time</strong></span> may
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User be specified for a <span><strong class="command">syslog</strong></span> channel,
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User but is usually
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User pointless since <span><strong class="command">syslog</strong></span> also logs
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User the date and
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User time. If <span><strong class="command">print-category</strong></span> is
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews requested, then the
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews category of the message will be logged as well. Finally, if <span><strong class="command">print-severity</strong></span> is
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews on, then the severity level of the message will be logged. The <span><strong class="command">print-</strong></span> options may
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews be used in any combination, and will always be printed in the
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews following
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User order: time, category, severity. Here is an example where all
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User three <span><strong class="command">print-</strong></span> options
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User are on:
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <code class="computeroutput">28-Feb-2000 15:05:32.863 general: notice: running</code>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews There are four predefined channels that are used for
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <span><strong class="command">named</strong></span>'s default logging as follows.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews How they are
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews 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>.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<pre class="programlisting">channel default_syslog {
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // send to syslog's daemon facility
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews syslog daemon;
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // only send priority info and higher
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews severity info;
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrewschannel default_debug {
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // write to named.run in the working directory
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // Note: stderr is used instead of "named.run" if
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // the server is started with the '-f' option.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews file "named.run";
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // log at the server's current debug level
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews severity dynamic;
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews};
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrewschannel default_stderr {
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // writes to stderr
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews stderr;
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // only send priority info and higher
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews severity info;
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews};
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrewschannel null {
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews // toss anything sent to this channel
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews null;
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews};
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews</pre>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<p>
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User The <span><strong class="command">default_debug</strong></span> channel has the
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews special
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews property that it only produces output when the server's debug
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews level is
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews nonzero. It normally writes to a file called <code class="filename">named.run</code>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews in the server's working directory.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews For security reasons, when the "<code class="option">-u</code>"
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews command line option is used, the <code class="filename">named.run</code> file
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews is created only after <span><strong class="command">named</strong></span> has
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews changed to the
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews new UID, and any debug output generated while <span><strong class="command">named</strong></span> is
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews starting up and still running as root is discarded. If you need
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews to capture this output, you must run the server with the "<code class="option">-g</code>"
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews option and redirect standard error to a file.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews Once a channel is defined, it cannot be redefined. Thus you
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews cannot alter the built-in channels directly, but you can modify
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews the default logging by pointing categories at channels you have
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews defined.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</div>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<div class="sect3" lang="en">
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<div class="titlepage"><div><div><h4 class="title">
bbd726b86a5b0f97a192b6027958dc7b763dc48bTinderbox User<a name="the_category_phrase"></a>The <span><strong class="command">category</strong></span> Phrase</h4></div></div></div>
7a2a1b8b14fc804ac80612d7b98064095e445be5Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater There are many categories, so you can send the logs you want
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater to see wherever you want, without seeing logs you don't want. If
7a2a1b8b14fc804ac80612d7b98064095e445be5Automatic Updater you don't specify a list of channels for a category, then log
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User messages
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews in that category will be sent to the <span><strong class="command">default</strong></span> category
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews instead. If you don't specify a default category, the following
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews "default default" is used:
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<pre class="programlisting">category default { default_syslog; default_debug; };
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews</pre>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews As an example, let's say you want to log security events to
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews a file, but you also want keep the default logging behavior. You'd
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews specify the following:
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<pre class="programlisting">channel my_security_channel {
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews file "my_security_file";
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews severity info;
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews};
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrewscategory security {
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews my_security_channel;
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews default_syslog;
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews default_debug;
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews};</pre>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews To discard all messages in a category, specify the <span><strong class="command">null</strong></span> channel:
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<pre class="programlisting">category xfer-out { null; };
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrewscategory notify { null; };
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</pre>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Following are the available categories and brief descriptions
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User of the types of log information they contain. More
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater categories may be added in future <acronym class="acronym">BIND</acronym> releases.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<div class="informaltable"><table border="1">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<colgroup>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<col>
4d813066e967a36c407ee641155ada0c614d4dc6Automatic Updater<col>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</colgroup>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tbody>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">default</strong></span></p>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User </td>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User<td>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User <p>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User The default category defines the logging
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews options for those categories where no specific
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User configuration has been
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User defined.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater</tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p><span><strong class="command">general</strong></span></p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater The catch-all. Many things still aren't
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater classified into categories, and they all end up here.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater</tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews <p><span><strong class="command">database</strong></span></p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater Messages relating to the databases used
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater internally by the name server to store zone and cache
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User data.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater</tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">security</strong></span></p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews <p>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User Approval and denial of requests.
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User </p>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User </td>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User</tr>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User<tr>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User<td>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User <p><span><strong class="command">config</strong></span></p>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<td>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User <p>
059cd1994d4ac5c1b967ce777d2c7409dc829a42Tinderbox User Configuration file parsing and processing.
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">resolver</strong></span></p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User DNS resolution, such as the recursive
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User lookups performed on behalf of clients by a caching name
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User server.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">xfer-in</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater <p>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews Zone transfers the server is receiving.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews<tr>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User<td>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater <p><span><strong class="command">xfer-out</strong></span></p>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews </td>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Zone transfers the server is sending.
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews </p>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
ec7751119a08c6a7250f3187beed69a8b836d349Tinderbox User<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">notify</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
ace530234c82bbfcd03bbfd4ba6c6a04293d497fMark Andrews <p>
879391501ee0ffba072433120bf1baa4087f8899Automatic Updater The NOTIFY protocol.
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater </p>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater </td>
8f536463f9fdfa7da6a8310e4f4895373beb2961Mark Andrews</tr>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<tr>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">client</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
ace530234c82bbfcd03bbfd4ba6c6a04293d497fMark Andrews<td>
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews <p>
dcd42a39d311b44877161ffd1e27fa62700c0171Mark Andrews Processing of client requests.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">unmatched</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User<td>
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Messages that <span><strong class="command">named</strong></span> was unable to determine the
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User class of or for which there was no matching <span><strong class="command">view</strong></span>.
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User A one line summary is also logged to the <span><strong class="command">client</strong></span> category.
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User This category is best sent to a file or stderr, by
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User default it is sent to
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews the <span><strong class="command">null</strong></span> channel.
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p><span><strong class="command">network</strong></span></p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater <p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater Network operations.
63654fea53d6a58a65112234bc8d0c322e0c81b5Automatic Updater </p>
63654fea53d6a58a65112234bc8d0c322e0c81b5Automatic Updater </td>
27aa770222192dda4ba4ff4b76defd4b8c846226Automatic Updater</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
64d59a0480180940d855a3431ac5ff617b53e997Tinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">update</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Dynamic updates.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater </td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews<td>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews <p><span><strong class="command">update-security</strong></span></p>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews </td>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User<td>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User <p>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews Approval and denial of update requests.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">queries</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User Specify where queries should be logged to.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User At startup, specifying the category <span><strong class="command">queries</strong></span> will also
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User enable query logging unless <span><strong class="command">querylog</strong></span> option has been
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User specified.
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews </p>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews <p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User The query log entry reports the client's IP
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User address and port number, and the query name,
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User class and type. Next it reports whether the
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User Recursion Desired flag was set (+ if set, -
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User if not set), if the query was signed (S),
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews EDNS was in use (E), if DO (DNSSEC Ok) was
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews set (D), or if CD (Checking Disabled) was set
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews (C). After this the destination address the
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews query was sent to is reported.
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews </p>
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews <p>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews <code class="computeroutput">client 127.0.0.1#62536: query: www.example.com IN AAAA +SE</code>
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews </p>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews <p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater <code class="computeroutput">client ::1#62537: query: www.example.net IN AAAA -SE</code>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </td>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater</tr>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<tr>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<td>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User <p><span><strong class="command">query-errors</strong></span></p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<td>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Information about queries that resulted in some
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User failure.
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</tr>
183b6c7fca54001820078f324d102fc33e64bbc6Automatic Updater<tr>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<td>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater <p><span><strong class="command">dispatch</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User<td>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Dispatching of incoming packets to the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater server modules where they are to be processed.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">dnssec</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User <p>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User DNSSEC and TSIG protocol processing.
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User </p>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User </td>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User</tr>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User<tr>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User<td>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User <p><span><strong class="command">lame-servers</strong></span></p>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater Lame servers. These are misconfigurations
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in remote servers, discovered by BIND 9 when trying to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater query those servers during resolution.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater<td>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater <p><span><strong class="command">delegation-only</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater Delegation only. Logs queries that have been
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User forced to NXDOMAIN as the result of a
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User delegation-only zone or a
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater <span><strong class="command">delegation-only</strong></span> in a hint
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User or stub zone declaration.
17198e77b87667f796e910d31a4f47a80e256d09Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater</tr>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater<tr>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">edns-disabled</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Log queries that have been forced to use plain
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater DNS due to timeouts. This is often due to
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater the remote servers not being RFC 1034 compliant
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater (not always returning FORMERR or similar to
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User EDNS queries and other extensions to the DNS
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User when they are not understood). In other words, this is
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User targeted at servers that fail to respond to
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User DNS queries that they don't understand.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
de73ef7ecdb9e009155993a6fa8dee5cd1bde319Mark Andrews <p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater Note: the log message can also be due to
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater packet loss. Before reporting servers for
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User non-RFC 1034 compliance they should be re-tested
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User to determine the nature of the non-compliance.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User This testing should prevent or reduce the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User number of false-positive reports.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater <p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater Note: eventually <span><strong class="command">named</strong></span> will have to stop
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater treating such timeouts as due to RFC 1034 non
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User compliance and start treating it as plain
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User packet loss. Falsely classifying packet
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User loss as due to RFC 1034 non compliance impacts
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User on DNSSEC validation which requires EDNS for
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the DNSSEC records to be returned.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater</tbody>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</table></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="sect3" lang="en">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="titlepage"><div><div><h4 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="id2576901"></a>The <span><strong class="command">query-errors</strong></span> Category</h4></div></div></div>
febbdb34a7f7759922e239655e7429d78d3a8d26Tinderbox User<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User The <span><strong class="command">query-errors</strong></span> category is
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User specifically intended for debugging purposes: To identify
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews why and how specific queries result in responses which
0df8ead472f207020f8da22a185fe4b945248ab8Automatic Updater indicate an error.
0df8ead472f207020f8da22a185fe4b945248ab8Automatic Updater Messages of this category are therefore only logged
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews with <span><strong class="command">debug</strong></span> levels.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User<p>
6fab60452ed15c1039aee974a32d692d07eda4d2Automatic Updater At the debug levels of 1 or higher, each response with the
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews rcode of SERVFAIL is logged as follows:
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater<p>
b4846627b60aff904d523a433b44482b3b1825a7Tinderbox User <code class="computeroutput">client 127.0.0.1#61502: query failed (SERVFAIL) for www.example.com/IN/AAAA at query.c:3880</code>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<p>
71ba75c604df3604673232828a68bb28c420e698Mark Andrews This means an error resulting in SERVFAIL was
71ba75c604df3604673232828a68bb28c420e698Mark Andrews detected at line 3880 of source file
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews <code class="filename">query.c</code>.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews Log messages of this level will particularly
dfd613f037c1385db661f17e086d34ea57fea9b0Automatic Updater help identify the cause of SERVFAIL for an
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater authoritative server.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater At the debug levels of 2 or higher, detailed context
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater information of recursive resolutions that resulted in
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater SERVFAIL is logged.
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater The log message will look like as follows:
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater </p>
56334ccb2d4b5a04fc12b70b5852049db5d24088Evan Hunt<p>
56334ccb2d4b5a04fc12b70b5852049db5d24088Evan Hunt
56334ccb2d4b5a04fc12b70b5852049db5d24088Evan Hunt </p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<pre class="programlisting">
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updaterfetch completed at resolver.c:2970 for www.example.com/A
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updaterin 30.000183: timed out/success [domain:example.com,
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updaterreferral:2,restart:7,qrysent:8,timeout:5,lame:0,neterr:0,
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updaterbadresp:1,adberr:0,findfail:0,valfail:0]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater </pre>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater<p>
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater The first part before the colon shows that a recursive
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson resolution for AAAA records of www.example.com completed
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in 30.000183 seconds and the final result that led to the
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater SERVFAIL was determined at line 2970 of source file
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater <code class="filename">resolver.c</code>.
ace6bfc72265153cb6123f7bb9e2751031f27150Tinderbox User </p>
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The following part shows the detected final result and the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater latest result of DNSSEC validation.
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson The latter is always success when no validation attempt
a8a1d4629ed697be4b0c0bb96b3c59d494450eedAutomatic Updater is made.
7932a7637170550bc53b38c35db9a0187dcb3d3bAutomatic Updater In this example, this query resulted in SERVFAIL probably
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson because all name servers are down or unreachable, leading
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson to a timeout in 30 seconds.
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson DNSSEC validation was probably not attempted.
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater </p>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater<p>
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox User The last part enclosed in square brackets shows statistics
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews information collected for this particular resolution
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews attempt.
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox User The <code class="varname">domain</code> field shows the deepest zone
de7b9a1dac0c293b39994c91d4376883da25554fTinderbox User that the resolver reached;
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User it is the zone where the error was finally detected.
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User The meaning of the other fields is summarized in the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater following table.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="informaltable"><table border="1">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<colgroup>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<col>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<col>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</colgroup>
0a50626faa2f8941f55bf435d3965d490bb5d026Tinderbox User<tbody>
467a823e57af687ebd486dfd73ea32f9d2a145beTinderbox User<tr>
467a823e57af687ebd486dfd73ea32f9d2a145beTinderbox User<td>
7d704e522860496310bb29c28e76064868401a9cMark Andrews <p><code class="varname">referral</code></p>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews </td>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews The number of referrals the resolver received
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews throughout the resolution process.
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater In the above example this is 2, which are most
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater likely com and example.com.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </p>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </td>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User</tr>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<tr>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<td>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews <p><code class="varname">restart</code></p>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews </td>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<td>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater <p>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews The number of cycles that the resolver tried
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews remote servers at the <code class="varname">domain</code>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews zone.
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews In each cycle the resolver sends one query
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews (possibly resending it, depending on the response)
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews to each known name server of
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews the <code class="varname">domain</code> zone.
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews </p>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater </td>
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User</tr>
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User<tr>
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User<td>
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User <p><code class="varname">qrysent</code></p>
24bf1e02f03577db0feb50b80238c4150c96d05dAutomatic Updater </td>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<td>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater <p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater The number of queries the resolver sent at the
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater <code class="varname">domain</code> zone.
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </p>
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User </td>
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User</tr>
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User<tr>
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User<td>
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User <p><code class="varname">timeout</code></p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User </td>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User<td>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User <p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User The number of timeouts since the resolver
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User received the last response.
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User </p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User </td>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User</tr>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User<tr>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User<td>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User <p><code class="varname">lame</code></p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User </td>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User<td>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User <p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User The number of lame servers the resolver detected
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User at the <code class="varname">domain</code> zone.
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User A server is detected to be lame either by an
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User invalid response or as a result of lookup in
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User BIND9's address database (ADB), where lame
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User servers are cached.
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User </p>
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User </td>
b8cc0c5d896c361525708a2be2e5af7df76c96d7Tinderbox User</tr>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User<tr>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User<td>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User <p><code class="varname">neterr</code></p>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User </td>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User<td>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User <p>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User The number of erroneous results that the
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User resolver encountered in sending queries
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User at the <code class="varname">domain</code> zone.
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User One common case is the remote server is
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User unreachable and the resolver receives an ICMP
2ec4ab21838e218863d052ebfa3e106e04f50820Evan Hunt unreachable error message.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews <p><code class="varname">badresp</code></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The number of unexpected responses (other than
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="varname">lame</code>) to queries sent by the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews resolver at the <code class="varname">domain</code> zone.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><code class="varname">adberr</code></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Failures in finding remote server addresses
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews of the <code class="varname">domain</code> zone in the ADB.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews One common case of this is that the remote
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews server's name does not have any address records.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><code class="varname">findfail</code></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Failures of resolving remote server addresses.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews This is a total number of failures throughout
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the resolution process.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p><code class="varname">valfail</code></p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Failures of DNSSEC validation.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Validation failures are counted throughout
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the resolution process (not limited to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the <code class="varname">domain</code> zone), but should
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews only happen in <code class="varname">domain</code>.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </td>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tr>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</tbody>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</table></div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews At the debug levels of 3 or higher, the same messages
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews as those at the debug 1 level are logged for other errors
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews than SERVFAIL.
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews Note that negative responses such as NXDOMAIN are not
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews regarded as errors here.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews At the debug levels of 4 or higher, the same messages
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews as those at the debug 2 level are logged for other errors
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews than SERVFAIL.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Unlike the above case of level 3, messages are logged for
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews negative responses.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews This is because any unexpected results can be difficult to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews debug in the recursion case.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="sect2" lang="en">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="titlepage"><div><div><h3 class="title">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<a name="id2577420"></a><span><strong class="command">lwres</strong></span> Statement Grammar</h3></div></div></div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews This is the grammar of the <span><strong class="command">lwres</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews statement in the <code class="filename">named.conf</code> file:
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<pre class="programlisting"><span><strong class="command">lwres</strong></span> {
4f087942583014b241adca1bc78c6db89ed96e94Mark 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>] ;
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> view <em class="replaceable"><code>view_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<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>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [<span class="optional"> ndots <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews};
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</pre>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="sect2" lang="en">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="titlepage"><div><div><h3 class="title">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<a name="id2577494"></a><span><strong class="command">lwres</strong></span> Statement Definition and Usage</h3></div></div></div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The <span><strong class="command">lwres</strong></span> statement configures the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews name
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews server to also act as a lightweight resolver server. (See
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <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
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span><strong class="command">lwres</strong></span> statements configuring
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews lightweight resolver servers with different properties.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The <span><strong class="command">listen-on</strong></span> statement specifies a
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews list of
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews addresses (and ports) that this instance of a lightweight resolver
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews daemon
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews should accept requests on. If no port is specified, port 921 is
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews used.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews If this statement is omitted, requests will be accepted on
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews 127.0.0.1,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews port 921.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The <span><strong class="command">view</strong></span> statement binds this
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews instance of a
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews lightweight resolver daemon to a view in the DNS namespace, so that
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews response will be constructed in the same manner as a normal DNS
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews query
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews matching this view. If this statement is omitted, the default view
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews is
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews used, and if there is no default view, an error is triggered.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The <span><strong class="command">search</strong></span> statement is equivalent to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span><strong class="command">search</strong></span> statement in
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="filename">/etc/resolv.conf</code>. It provides a
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews list of domains
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews which are appended to relative names in queries.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The <span><strong class="command">ndots</strong></span> statement is equivalent to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span><strong class="command">ndots</strong></span> statement in
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="filename">/etc/resolv.conf</code>. It indicates the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews minimum
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews number of dots in a relative domain name that should result in an
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews exact match lookup before search path elements are appended.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="sect2" lang="en">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="titlepage"><div><div><h3 class="title">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<a name="id2577558"></a><span><strong class="command">masters</strong></span> Statement Grammar</h3></div></div></div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<pre class="programlisting">
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic 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>] { ( <em class="replaceable"><code>masters_list</code></em> |
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <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>] };
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</pre>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="sect2" lang="en">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="titlepage"><div><div><h3 class="title">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<a name="id2577602"></a><span><strong class="command">masters</strong></span> Statement Definition and
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Usage</h3></div></div></div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p><span><strong class="command">masters</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews lists allow for a common set of masters to be easily used by
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews multiple stub and slave zones.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="sect2" lang="en">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<div class="titlepage"><div><div><h3 class="title">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<a name="id2577617"></a><span><strong class="command">options</strong></span> Statement Grammar</h3></div></div></div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews This is the grammar of the <span><strong class="command">options</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews statement in the <code class="filename">named.conf</code> file:
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<pre class="programlisting"><span><strong class="command">options</strong></span> {
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> attach-cache <em class="replaceable"><code>cache_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> version <em class="replaceable"><code>version_string</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> hostname <em class="replaceable"><code>hostname_string</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> server-id <em class="replaceable"><code>server_id_string</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> directory <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> key-directory <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> named-xfer <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> tkey-gssapi-credential <em class="replaceable"><code>principal</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> tkey-domain <em class="replaceable"><code>domainname</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> tkey-dhkey <em class="replaceable"><code>key_name</code></em> <em class="replaceable"><code>key_tag</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> cache-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dump-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> bindkeys-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> memstatistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> memstatistics-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> pid-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> recursing-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> statistics-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> zone-statistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> auth-nxdomain <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> deallocate-on-exit <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> fake-iquery <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> fetch-glue <em class="replaceable"><code>yes_or_no</code></em>; </span>]
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington [<span class="optional"> flush-zones-on-shutdown <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> has-old-clients <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> host-statistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> host-statistics-max <em class="replaceable"><code>number</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> minimal-responses <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> multiple-cnames <em class="replaceable"><code>yes_or_no</code></em>; </span>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [<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>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> recursion <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> rfc2308-type1 <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> use-id-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<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>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> dnssec-enable <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> dnssec-validation <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> dnssec-lookaside ( <em class="replaceable"><code>auto</code></em> |
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews <em class="replaceable"><code>domain</code></em> trust-anchor <em class="replaceable"><code>domain</code></em> ); </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> dnssec-must-be-secure <em class="replaceable"><code>domain yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> dnssec-accept-expired <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> forward ( <em class="replaceable"><code>only</code></em> | <em class="replaceable"><code>first</code></em> ); </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> dual-stack-servers [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] {
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews ( <em class="replaceable"><code>domain_name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] |
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ) ;
35bc7055d1b9b816e68a4180d46a49963e45c233Automatic Updater ... }; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<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> )
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<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>]
78cb74fab4665da2e2641ba909c6f59f74cc4193Automatic Updater [<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic 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>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic 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>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> check-sibling <em class="replaceable"><code>yes_or_no</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-query-cache { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-query-cache-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
c57668a2fbbe558c1bd21652813616f2f517c469Tinderbox User [<span class="optional"> allow-recursion { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-recursion-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> secure-to-insecure <em class="replaceable"><code>yes_or_no</code></em> ;</span>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [<span class="optional"> try-tcp-refresh <em class="replaceable"><code>yes_or_no</code></em>; </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> allow-v6-synthesis { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
309b912841e8b97bf0b0df0d96c3eaf16990c080Automatic Updater [<span class="optional"> blackhole { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
66d24a46538c7c2d29fdb5611ab1173e83685b1dTinderbox User [<span class="optional"> use-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
66d24a46538c7c2d29fdb5611ab1173e83685b1dTinderbox User [<span class="optional"> avoid-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> use-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> avoid-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews [<span class="optional"> listen-on [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em> </span>] { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews [<span class="optional"> listen-on-v6 [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em> </span>] { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews [<span class="optional"> query-source ( ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> )
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] |
94df856897945fe58f130ba78765c57308bc5400Automatic Updater [<span class="optional"> address ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] ) ; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> query-source-v6 ( ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> )
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] |
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> address ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] ) ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> use-queryport-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [<span class="optional"> queryport-pool-ports <em class="replaceable"><code>number</code></em>; </span>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [<span class="optional"> queryport-pool-interval <em class="replaceable"><code>number</code></em>; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em>; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em>; </span>]
da93950363b307b718d156514b95b9df93a63776Mark Andrews [<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em>; </span>]
da93950363b307b718d156514b95b9df93a63776Mark Andrews [<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em>; </span>]
35bc7055d1b9b816e68a4180d46a49963e45c233Automatic Updater [<span class="optional"> tcp-clients <em class="replaceable"><code>number</code></em>; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic 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>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> serial-query-rate <em class="replaceable"><code>number</code></em>; </span>]
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater [<span class="optional"> serial-queries <em class="replaceable"><code>number</code></em>; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> tcp-listen-queue <em class="replaceable"><code>number</code></em>; </span>]
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater [<span class="optional"> transfer-format <em class="replaceable"><code>( one-answer | many-answers )</code></em>; </span>]
fbcaee30a27f47fe337152c27e7d90489dc8fd63Tinderbox User [<span class="optional"> transfers-in <em class="replaceable"><code>number</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> transfers-out <em class="replaceable"><code>number</code></em>; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> transfers-per-ns <em class="replaceable"><code>number</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic 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>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic 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>]
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>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic 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>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic 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>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> notify-to-soa <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<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>] ;
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic 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>] }; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em>; </span>]
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater [<span class="optional"> max-journal-size <em class="replaceable"><code>size_spec</code></em>; </span>]
c57668a2fbbe558c1bd21652813616f2f517c469Tinderbox User [<span class="optional"> coresize <em class="replaceable"><code>size_spec</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> datasize <em class="replaceable"><code>size_spec</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> files <em class="replaceable"><code>size_spec</code></em> ; </span>]
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater [<span class="optional"> stacksize <em class="replaceable"><code>size_spec</code></em> ; </span>]
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater [<span class="optional"> cleaning-interval <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> heartbeat-interval <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> interface-interval <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> statistics-interval <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> topology { <em class="replaceable"><code>address_match_list</code></em> }</span>];
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> sortlist { <em class="replaceable"><code>address_match_list</code></em> }</span>];
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic 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>] };
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> lame-ttl <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-ncache-ttl <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-cache-ttl <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic 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>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> sig-signing-nodes <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> sig-signing-signatures <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> sig-signing-type <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> min-roots <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> use-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> provide-ixfr <em class="replaceable"><code>yes_or_no</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> treat-cr-as-space <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> additional-from-auth <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> additional-from-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> random-device <em class="replaceable"><code>path_name</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-cache-size <em class="replaceable"><code>size_spec</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> match-mapped-addresses <em class="replaceable"><code>yes_or_no</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic 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>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> root-delegation-only [<span class="optional"> exclude { <em class="replaceable"><code>namelist</code></em> } </span>] ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> querylog <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> disable-algorithms <em class="replaceable"><code>domain</code></em> { <em class="replaceable"><code>algorithm</code></em>;
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> <em class="replaceable"><code>algorithm</code></em>; </span>] }; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> acache-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> acache-cleaning-interval <em class="replaceable"><code>number</code></em>; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-acache-size <em class="replaceable"><code>size_spec</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> clients-per-query <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> max-clients-per-query <em class="replaceable"><code>number</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>) ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> empty-server <em class="replaceable"><code>name</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> empty-contact <em class="replaceable"><code>name</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> empty-zones-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
0b580e05aec89f501a9c20cc00ceb42d043d3928Automatic Updater [<span class="optional"> disable-empty-zone <em class="replaceable"><code>zone_name</code></em> ; </span>]
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater [<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater [<span class="optional"> zero-no-soa-ttl-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic 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>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic 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>]
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater};
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</pre>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater</div>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<div class="sect2" lang="en">
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<a name="options"></a><span><strong class="command">options</strong></span> Statement Definition and
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater Usage</h3></div></div></div>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater The <span><strong class="command">options</strong></span> statement sets up global
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater options
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater to be used by <acronym class="acronym">BIND</acronym>. This statement
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater may appear only
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater once in a configuration file. If there is no <span><strong class="command">options</strong></span>
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater statement, an options block with each option set to its default will
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater be used.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<div class="variablelist"><dl>
0b580e05aec89f501a9c20cc00ceb42d043d3928Automatic Updater<dt><span class="term"><span><strong class="command">attach-cache</strong></span></span></dt>
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater<dd>
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater<p>
0b580e05aec89f501a9c20cc00ceb42d043d3928Automatic Updater Allows multiple views to share a single cache
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater database.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater Each view has its own cache database by default, but
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater if multiple views have the same operational policy
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater for name resolution and caching, those views can
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater share a single cache to save memory and possibly
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater improve resolution efficiency by using this option.
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater The <span><strong class="command">attach-cache</strong></span> option
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater may also be specified in <span><strong class="command">view</strong></span>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater statements, in which case it overrides the
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater global <span><strong class="command">attach-cache</strong></span> option.
c57668a2fbbe558c1bd21652813616f2f517c469Tinderbox User </p>
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater<p>
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater The <em class="replaceable"><code>cache_name</code></em> specifies
782b50b4ebbd48d570831f66d8ffc550e0db340cAutomatic Updater the cache to be shared.
f8e61212a1b83e60f521577cc522e8bc1509c8cfAutomatic Updater When the <span><strong class="command">named</strong></span> server configures
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User views which are supposed to share a cache, it
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User creates a cache with the specified name for the
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User first view of these sharing views.
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User The rest of the views will simply refer to the
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User already created cache.
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User </p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<p>
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User One common configuration to share a cache would be to
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User allow all views to share a single cache.
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User This can be done by specifying
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User the <span><strong class="command">attach-cache</strong></span> as a global
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User option with an arbitrary name.
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User </p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<p>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews Another possible operation is to allow a subset of
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User all views to share a cache while the others to
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews retain their own caches.
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User For example, if there are three views A, B, and C,
4ea3649f028ea6a1e42377082a7ccf8f789fb950Automatic Updater and only A and B should share a cache, specify the
644973f327e9db74779e7c0426db90909173b284Automatic Updater <span><strong class="command">attach-cache</strong></span> option as a view A (or
644973f327e9db74779e7c0426db90909173b284Automatic Updater B)'s option, referring to the other view name:
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
418cc932318b1d67f88a36904d88d8a5a0a2ba09Automatic Updater<pre class="programlisting">
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User view "A" {
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User // this view has its own cache
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User ...
e567288a21dcd95266e123238c669230b4c4bc62Tinderbox User };
e567288a21dcd95266e123238c669230b4c4bc62Tinderbox User view "B" {
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User // this view refers to A's cache
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User attach-cache "A";
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User };
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User view "C" {
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User // this view has its own cache
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User ...
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User };
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User</pre>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User Views that share a cache must have the same policy
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User on configurable parameters that may affect caching.
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User The current implementation requires the following
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User configurable options be consistent among these
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User views:
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <span><strong class="command">check-names</strong></span>,
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <span><strong class="command">cleaning-interval</strong></span>,
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <span><strong class="command">dnssec-accept-expired</strong></span>,
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <span><strong class="command">dnssec-validation</strong></span>,
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <span><strong class="command">max-cache-ttl</strong></span>,
418cc932318b1d67f88a36904d88d8a5a0a2ba09Automatic Updater <span><strong class="command">max-ncache-ttl</strong></span>,
e31cfd80616deb9781902306b34a69aa7309b6cbTinderbox User <span><strong class="command">max-cache-size</strong></span>, and
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <span><strong class="command">zero-no-soa-ttl</strong></span>.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews Note that there may be other parameters that may
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews cause confusion if they are inconsistent for
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews different views that share a single cache.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews For example, if these views define different sets of
90863a6f9bfb06062c7fdf269bb675e7b674fc31Mark Andrews forwarders that can return different answers for the
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews same question, sharing the answer does not make
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews sense or could even be harmful.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews It is administrator's responsibility to ensure
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews configuration differences in different views do
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews not cause disruption with a shared cache.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews</dd>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dt><span class="term"><span><strong class="command">directory</strong></span></span></dt>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews<dd><p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The working directory of the server.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews Any non-absolute pathnames in the configuration file will be
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews taken
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews as relative to this directory. The default location for most
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews server
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater output files (e.g. <code class="filename">named.run</code>)
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews is this directory.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews If a directory is not specified, the working directory
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater defaults to `<code class="filename">.</code>', the directory from
68e1b398b5b1b417723e90b5e52b9148f8f93294Automatic Updater which the server
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews was started. The directory specified should be an absolute
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews path.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt>
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User When performing dynamic update of secure zones, the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User directory where the public and private DNSSEC key files
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater should be found, if different than the current working
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater directory. The directory specified must be an absolute
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews path. (Note that this option has no effect on the paths
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User for files containing non-DNSSEC keys such as
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <code class="filename">bind.keys</code>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <code class="filename">rndc.key</code> or
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <code class="filename">session.key</code>.)
872a5b83f68b8058945298715b0fa53442aad52fAutomatic Updater </p></dd>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dt><span class="term"><span><strong class="command">named-xfer</strong></span></span></dt>
8f7809dd50b2471151ad272d083dd8c6a29d070eTinderbox User<dd><p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <span class="emphasis"><em>This option is obsolete.</em></span> It
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews was used in <acronym class="acronym">BIND</acronym> 8 to specify
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews the pathname to the <span><strong class="command">named-xfer</strong></span>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User program. In <acronym class="acronym">BIND</acronym> 9, no separate
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">named-xfer</strong></span> program is needed;
7a2a1b8b14fc804ac80612d7b98064095e445be5Automatic Updater its functionality is built into the name server.
7a42357217528037bdfedcb17eeebfe96ae4266aAutomatic Updater </p></dd>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews<dt><span class="term"><span><strong class="command">tkey-gssapi-credential</strong></span></span></dt>
e007e3e5b0316c6c05698a71101885743aca22bdAutomatic Updater<dd><p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The security credential with which the server should
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington authenticate keys requested by the GSS-TSIG protocol.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Currently only Kerberos 5 authentication is available
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington and the credential is a Kerberos principal which
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the server can acquire through the default system
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington key file, normally <code class="filename">/etc/krb5.keytab</code>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Normally this principal is of the form
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington "<strong class="userinput"><code>dns/</code></strong><code class="varname">server.domain</code>".
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington To use GSS-TSIG, <span><strong class="command">tkey-domain</strong></span>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington must also be set.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="term"><span><strong class="command">tkey-domain</strong></span></span></dt>
cff0e0b52cf0928123bad6f3bccf56e22bbc07f5Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The domain appended to the names of all shared keys
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater generated with <span><strong class="command">TKEY</strong></span>. When a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater client requests a <span><strong class="command">TKEY</strong></span> exchange,
644973f327e9db74779e7c0426db90909173b284Automatic Updater it may or may not specify the desired name for the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater key. If present, the name of the shared key will
c28a1243429dfaf8dc5f6c1db0dccdc6ce386baeMark Andrews be <code class="varname">client specified part</code> +
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="varname">tkey-domain</code>. Otherwise, the
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews name of the shared key will be <code class="varname">random hex
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews digits</code> + <code class="varname">tkey-domain</code>.
5f7e0eb1cb917b788906d3e2aa01bfc4885dcae4Mark Andrews In most cases, the <span><strong class="command">domainname</strong></span>
bf1263835e8e35421960f65088c043f42aacef13Mark Andrews should be the server's domain name, or an otherwise
15ae68f3db8261770fc33b8e0f83f5d8c7021e84Mark Andrews non-existent subdomain like
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews "_tkey.<code class="varname">domainname</code>". If you are
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User using GSS-TSIG, this variable must be defined.
2bb3422dc683c013db7042f5736240de6b86f182Automatic Updater </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">tkey-dhkey</strong></span></span></dt>
9bc394fffdd50f6e47614b2d317da7274122366fTinderbox User<dd><p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User The Diffie-Hellman key used by the server
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater to generate shared keys with clients using the Diffie-Hellman
02b47c5d62e1e827743684c28a08e871da454a2dMark Andrews mode
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User of <span><strong class="command">TKEY</strong></span>. The server must be
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews able to load the
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews public and private keys from files in the working directory.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater In
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User most cases, the keyname should be the server's host name.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">cache-file</strong></span></span></dt>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This is for testing only. Do not use.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<dt><span class="term"><span><strong class="command">dump-file</strong></span></span></dt>
10640b2e3efc7bc8034108136d7487f7407fbf37Andreas Gustafsson<dd><p>
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater The pathname of the file the server dumps
10640b2e3efc7bc8034108136d7487f7407fbf37Andreas Gustafsson the database to when instructed to do so with
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater <span><strong class="command">rndc dumpdb</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If not specified, the default is <code class="filename">named_dump.db</code>.
436aad11e01e916f75e68a2e9cb89ac217a990d3Tinderbox User </p></dd>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<dt><span class="term"><span><strong class="command">memstatistics-file</strong></span></span></dt>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews<dd><p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The pathname of the file the server writes memory
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User usage statistics to on exit. If not specified,
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews the default is <code class="filename">named.memstats</code>.
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User </p></dd>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User<dt><span class="term"><span><strong class="command">pid-file</strong></span></span></dt>
a792d42c3cdd6cd4608b936c0a06437b8c2d99ccTinderbox User<dd><p>
a01aa536188bb3535dfc1107a623e6355a8e6b7cMark Andrews The pathname of the file the server writes its process ID
0a50626faa2f8941f55bf435d3965d490bb5d026Tinderbox User in. If not specified, the default is
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic 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
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews the running
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater name server. Specifying <span><strong class="command">pid-file none</strong></span> disables the
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User use of a PID file &#8212; no file will be written and any
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User existing one will be removed. Note that <span><strong class="command">none</strong></span>
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User is a keyword, not a filename, and therefore is not enclosed
8d0e57cdac5e28964ebe7c0d925d158f17b401a6Tinderbox User in
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater double quotes.
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User </p></dd>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User<dt><span class="term"><span><strong class="command">recursing-file</strong></span></span></dt>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews<dd><p>
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User The pathname of the file the server dumps
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the queries that are currently recursing when instructed
e10d61d84e0b735f1e8eca18644cfdb1b06cad33Tinderbox User to do so with <span><strong class="command">rndc recursing</strong></span>.
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews If not specified, the default is <code class="filename">named.recursing</code>.
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User </p></dd>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<dt><span class="term"><span><strong class="command">statistics-file</strong></span></span></dt>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<dd><p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews The pathname of the file the server appends statistics
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater to when instructed to do so using <span><strong class="command">rndc stats</strong></span>.
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater If not specified, the default is <code class="filename">named.stats</code> in the
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User server's current directory. The format of the file is
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews described
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews in <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called &#8220;The Statistics File&#8221;</a>.
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews </p></dd>
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User<dt><span class="term"><span><strong class="command">bindkeys-file</strong></span></span></dt>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dd><p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The pathname of a file to override the built-in trusted
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews keys provided by named. See the discussion of
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews <span><strong class="command">dnssec-lookaside</strong></span> for details.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews If not specified, the default is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">/etc/bind.keys</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<dt><span class="term"><span><strong class="command">session-keyfile</strong></span></span></dt>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The pathname of the file into which to write a TSIG
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater session key generated by <span><strong class="command">named</strong></span> for use by
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater <span><strong class="command">nsupdate -l</strong></span>. If not specified, the
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater default is <code class="filename">/var/run/named/session.key</code>.
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews (See <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>, and in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater particular the discussion of the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">update-policy</strong></span> statement's
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews <strong class="userinput"><code>local</code></strong> option for more
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews information about this feature.)
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </p></dd>
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User<dt><span class="term"><span><strong class="command">session-keyname</strong></span></span></dt>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<dd><p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User The key name to use for the TSIG session key.
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User If not specified, the default is "local-ddns".
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </p></dd>
02b3e44a996e9753d86306b6a1b6b579a73787fcTinderbox User<dt><span class="term"><span><strong class="command">session-keyalg</strong></span></span></dt>
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The algorithm to use for the TSIG session key.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews Valid values are hmac-sha1, hmac-sha224, hmac-sha256,
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews hmac-sha384, hmac-sha512 and hmac-md5. If not
53b97c9873a923f504893d1e2ab62000dfac221fTinderbox User specified, the default is hmac-sha256.
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews </p></dd>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater<dt><span class="term"><span><strong class="command">session-keyfile</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
8c6328ab5890aa79d84b86ed672e185dc111bb68Automatic Updater The pathname of the file into which to write a session TSIG
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User key for use by <span><strong class="command">nsupdate -l</strong></span>. (See the
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater discussion of the <span><strong class="command">update-policy</strong></span>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews statement's <strong class="userinput"><code>local</code></strong> option for more
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater details on this feature.)
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews </p></dd>
f89eb76a7516649f8717c6397fc496ca906ddb57Tinderbox User<dt><span class="term"><span><strong class="command">port</strong></span></span></dt>
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews<dd><p>
cd34c1adb0fa2120327fc8c11cda0d4a5f722aeeTinderbox User The UDP/TCP port number the server uses for
e20309353e6246485c521278131d3fced73d7957Tinderbox User receiving and sending DNS protocol traffic.
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews The default is 53. This option is mainly intended for server
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews testing;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a server using a port other than 53 will not be able to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater communicate with
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews the global DNS.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
53b97c9873a923f504893d1e2ab62000dfac221fTinderbox User<dt><span class="term"><span><strong class="command">random-device</strong></span></span></dt>
fbcaee30a27f47fe337152c27e7d90489dc8fd63Tinderbox User<dd><p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater The source of entropy to be used by the server. Entropy is
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews primarily needed
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for DNSSEC operations, such as TKEY transactions and dynamic
ca904804e43f663f08eb1ac9d6d617930b9a3cd3Automatic Updater update of signed
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User zones. This options specifies the device (or file) from which
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to read
713a5e3080f112b3efde9235e9c92035056ff966Automatic Updater entropy. If this is a file, operations requiring entropy will
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater fail when the
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews file has been exhausted. If not specified, the default value
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews is
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User <code class="filename">/dev/random</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater (or equivalent) when present, and none otherwise. The
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <span><strong class="command">random-device</strong></span> option takes
f8b9948a4116226ac41b5509cca152849006c66cAutomatic Updater effect during
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews the initial configuration load at server startup time and
be46cb4bee9253ee4832340c719920642e00c41aTinderbox User is ignored on subsequent reloads.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
c243d779731a410f8dc2d2feeed20c15f299b6e3Automatic Updater<dt><span class="term"><span><strong class="command">preferred-glue</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater If specified, the listed type (A or AAAA) will be emitted
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater before other glue
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User in the additional section of a query response.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default is not to prefer any type (NONE).
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt>
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater<a name="root_delegation_only"></a><span class="term"><span><strong class="command">root-delegation-only</strong></span></span>
02b3e44a996e9753d86306b6a1b6b579a73787fcTinderbox User</dt>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews Turn on enforcement of delegation-only in TLDs
f22980c16f244b7d7f33b5248f2d38bd4885f108Automatic Updater (top level domains) and root zones with an optional
e20309353e6246485c521278131d3fced73d7957Tinderbox User exclude list.
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews DS queries are expected to be made to and be answered by
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User delegation only zones. Such queries and responses are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater treated as an exception to delegation-only processing
d630ef2ff74445949a482660938e9fa9da52ca14Automatic Updater and are not converted to NXDOMAIN responses provided
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User a CNAME is not discovered at the query name.
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User </p>
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If a delegation only zone server also serves a child
e10d61d84e0b735f1e8eca18644cfdb1b06cad33Tinderbox User zone it is not always possible to determine whether
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User an answer comes from the delegation only zone or the
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User child zone. SOA NS and DNSKEY records are apex
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater only records and a matching response that contains
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater these records or DS is treated as coming from a
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User child zone. RRSIG records are also examined to see
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews if they are signed by a child zone or not. The
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews authority section is also examined to see if there
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User is evidence that the answer is from the child zone.
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews Answers that are determined to be from a child zone
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User are not converted to NXDOMAIN responses. Despite
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews all these checks there is still a possibility of
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User false negatives when a child zone is being served.
cd34c1adb0fa2120327fc8c11cda0d4a5f722aeeTinderbox User </p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User Similarly false positives can arise from empty nodes
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews (no records at the name) in the delegation only zone
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User when the query type is not ANY.
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<p>
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User Note some TLDs are not delegation only (e.g. "DE", "LV",
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews "US" and "MUSEUM"). This list is not exhaustive.
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrewsoptions {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater root-delegation-only exclude { "de"; "lv"; "us"; "museum"; };
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User};
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews</pre>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews</dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">disable-algorithms</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Disable the specified DNSSEC algorithms at and below the
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User specified name.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews Multiple <span><strong class="command">disable-algorithms</strong></span>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User statements are allowed.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Only the most specific will be applied.
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">dnssec-lookaside</strong></span></span></dt>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User When set, <span><strong class="command">dnssec-lookaside</strong></span> provides the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater validator with an alternate method to validate DNSKEY
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater records at the top of a zone. When a DNSKEY is at or
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater below a domain specified by the deepest
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <span><strong class="command">dnssec-lookaside</strong></span>, and the normal dnssec
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater validation has left the key untrusted, the trust-anchor
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater will be append 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
f89eb76a7516649f8717c6397fc496ca906ddb57Tinderbox User record validates a DNSKEY (similarly to the way a DS record
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater does) the DNSKEY RRset is deemed to be trusted.
f89eb76a7516649f8717c6397fc496ca906ddb57Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
a61158fed2e0281a40e3e97e0b7c3f9789a07b4eTinderbox User If <span><strong class="command">dnssec-lookaside</strong></span> is set to
a61158fed2e0281a40e3e97e0b7c3f9789a07b4eTinderbox User "auto", then built-in default values for
a61158fed2e0281a40e3e97e0b7c3f9789a07b4eTinderbox User the domain and trust anchor will be used, along
a61158fed2e0281a40e3e97e0b7c3f9789a07b4eTinderbox User with a built-in key for validation.
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater NOTE: Since the built-in key may expire, it can be
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater overridden without recompiling named by placing a new key
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater in the file <code class="filename">bind.keys</code>.
59b277af9d9aac08d16be63aed5ae60ac9eef0d5Automatic Updater </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">dnssec-must-be-secure</strong></span></span></dt>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Specify hierarchies which must be or may not be secure
c7f4dfc8decb44451cff27ef160d539d4954dc31Tinderbox User (signed and validated). If <strong class="userinput"><code>yes</code></strong>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater then <span><strong class="command">named</strong></span> will only accept answers if
f34958b7669dfca333cc0cd20113b1f55a89e1deTinderbox User they are secure. If <strong class="userinput"><code>no</code></strong>, then normal
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater DNSSEC validation applies allowing for insecure answers to
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews be accepted. The specified domain must be under a
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <span><strong class="command">trusted-keys</strong></span> or
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <span><strong class="command">managed-keys</strong></span> statement, or
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <span><strong class="command">dnssec-lookaside</strong></span> must be active.
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dl></div>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<div class="sect3" lang="en">
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<div class="titlepage"><div><div><h4 class="title">
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<a name="boolean_options"></a>Boolean Options</h4></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="variablelist"><dl>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<dt><span class="term"><span><strong class="command">auth-nxdomain</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then the <span><strong class="command">AA</strong></span> bit
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater is always set on NXDOMAIN responses, even if the server is
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater not actually
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater authoritative. The default is <strong class="userinput"><code>no</code></strong>;
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater this is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a change from <acronym class="acronym">BIND</acronym> 8. If you
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater are using very old DNS software, you
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater may need to set it to <strong class="userinput"><code>yes</code></strong>.
c762a0e4141c8eb9d7567c614cf6dde994f6a76dTinderbox User </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">deallocate-on-exit</strong></span></span></dt>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<dd><p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User This option was used in <acronym class="acronym">BIND</acronym>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews 8 to enable checking
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews for memory leaks on exit. <acronym class="acronym">BIND</acronym> 9 ignores the option and always performs
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater the checks.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">memstatistics</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater Write memory statistics to the file specified by
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <span><strong class="command">memstatistics-file</strong></span> at exit.
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater The default is <strong class="userinput"><code>no</code></strong> unless
1b670d35282f1b9352692ad212be3c0aa97b0689Automatic Updater '-m record' is specified on the command line in
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User which case it is <strong class="userinput"><code>yes</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then the
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater server treats all zones as if they are doing zone transfers
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater across
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater a dial-on-demand dialup link, which can be brought up by
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater traffic
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater originating from this server. This has different effects
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater according
f89eb76a7516649f8717c6397fc496ca906ddb57Tinderbox User to zone type and concentrates the zone maintenance so that
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater it all
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater happens in a short interval, once every <span><strong class="command">heartbeat-interval</strong></span> and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater hopefully during the one call. It also suppresses some of
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User the normal
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater zone maintenance traffic. The default is <strong class="userinput"><code>no</code></strong>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater The <span><strong class="command">dialup</strong></span> option
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater may also be specified in the <span><strong class="command">view</strong></span> and
324a8797b46d646fe8d3b2eef6785e0b2b3ac956Tinderbox User <span><strong class="command">zone</strong></span> statements,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in which case it overrides the global <span><strong class="command">dialup</strong></span>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User option.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User<p>
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User If the zone is a master zone, then the server will send out a
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User NOTIFY
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater request to all the slaves (default). This should trigger the
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater zone serial
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater number check in the slave (providing it supports NOTIFY)
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User allowing the slave
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User to verify the zone while the connection is active.
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater The set of servers to which NOTIFY is sent can be controlled
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater by
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <span><strong class="command">notify</strong></span> and <span><strong class="command">also-notify</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If the
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater zone is a slave or stub zone, then the server will suppress
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the regular
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater "zone up to date" (refresh) queries and only perform them
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater when the
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <span><strong class="command">heartbeat-interval</strong></span> expires in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater addition to sending
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User NOTIFY requests.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Finer control can be achieved by using
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <strong class="userinput"><code>notify</code></strong> which only sends NOTIFY
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater messages,
324a8797b46d646fe8d3b2eef6785e0b2b3ac956Tinderbox User <strong class="userinput"><code>notify-passive</code></strong> which sends NOTIFY
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater messages and
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater suppresses the normal refresh queries, <strong class="userinput"><code>refresh</code></strong>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater which suppresses normal refresh processing and sends refresh
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater queries
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater when the <span><strong class="command">heartbeat-interval</strong></span>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User expires, and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <strong class="userinput"><code>passive</code></strong> which just disables normal
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater refresh
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater processing.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<div class="informaltable"><table border="1">
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<colgroup>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<col>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<col>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews<col>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<col>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User</colgroup>
b4846627b60aff904d523a433b44482b3b1825a7Tinderbox User<tbody>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews dialup mode
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User </p>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater </td>
0d3490f93bb980fde704055e74c1b508987a5fe4Mark Andrews<td>
8f7809dd50b2471151ad272d083dd8c6a29d070eTinderbox User <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater normal refresh
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
114f7780384371121918624ae2c80ecfce545683Tinderbox User heart-beat refresh
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </td>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User heart-beat notify
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
f7369b2881b5e63d69600adcedc8ba938303d30cTinderbox User </td>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User</tr>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<tr>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<td>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User <p><span><strong class="command">no</strong></span> (default)</p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </td>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
bb5fe714ce8625e6744dd84526828c36bcff12f6Tinderbox User yes
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews </p>
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User </td>
114f7780384371121918624ae2c80ecfce545683Tinderbox User<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
42c81cf2de732ec6d00e73fc755a399ca037e543Mark Andrews no
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater no
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </td>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews</tr>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews<tr>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews<td>
7d704e522860496310bb29c28e76064868401a9cMark Andrews <p><span><strong class="command">yes</strong></span></p>
7d704e522860496310bb29c28e76064868401a9cMark Andrews </td>
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews<td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater no
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater yes
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater </td>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater<td>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater <p>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater yes
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User</tr>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<tr>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p><span><strong class="command">notify</strong></span></p>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
8d0e57cdac5e28964ebe7c0d925d158f17b401a6Tinderbox User <p>
da24e725ff982595d74da7e75e9fbd6a696367ccAutomatic Updater yes
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </td>
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User<td>
e20309353e6246485c521278131d3fced73d7957Tinderbox User <p>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews no
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </td>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson<td>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson <p>
992616aaf75643a0c9f84826f0a1ed5a27e84328Mark Andrews yes
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson</tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox User<td>
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User <p><span><strong class="command">refresh</strong></span></p>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User no
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </td>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User<td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User yes
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater no
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater</tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p><span><strong class="command">passive</strong></span></p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </td>
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews<td>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User no
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
603cf17f33da24d460616389ec40d6f2a6e110a0Automatic Updater<td>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews <p>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews no
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater <p>
55aec75784a22e9d06d52b2b8a7d5aa42d31dc00Automatic Updater no
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<td>
b5423cbff7175727ed9046c8c670d8a7bb4d01eaTinderbox User <p><span><strong class="command">notify-passive</strong></span></p>
93bd88e172a36b549938bce1731df7c10a8f3fb5Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater no
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </td>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<td>
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User <p>
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User no
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
365bb6f27eace1836cb5bc6b5f9ed8c88fe22e4aTinderbox User yes
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews</tr>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater</tbody>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater</table></div>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Note that normal NOTIFY processing is not affected by
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews <span><strong class="command">dialup</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User<dt><span class="term"><span><strong class="command">fake-iquery</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater In <acronym class="acronym">BIND</acronym> 8, this option
b5423cbff7175727ed9046c8c670d8a7bb4d01eaTinderbox User enabled simulating the obsolete DNS query type
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater IQUERY. <acronym class="acronym">BIND</acronym> 9 never does
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater IQUERY simulation.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">fetch-glue</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This option is obsolete.
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater In BIND 8, <strong class="userinput"><code>fetch-glue yes</code></strong>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater caused the server to attempt to fetch glue resource records
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews it
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater didn't have when constructing the additional
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater data section of a response. This is now considered a bad
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater idea
19b3dc94bce93fa76bd7e066f9298630dbc9dcb4Automatic Updater and BIND 9 never does it.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">flush-zones-on-shutdown</strong></span></span></dt>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<dd><p>
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User When the nameserver exits due receiving SIGTERM,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater flush or do not flush any pending zone writes. The default
83d29eff2912ef967596eb5ed148de7668b35564Automatic Updater is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">flush-zones-on-shutdown</strong></span> <strong class="userinput"><code>no</code></strong>.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p></dd>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User<dt><span class="term"><span><strong class="command">has-old-clients</strong></span></span></dt>
71bd43eebd9d6e42dbcae62b730f5b6508d5acd8Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This option was incorrectly implemented
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater in <acronym class="acronym">BIND</acronym> 8, and is ignored by <acronym class="acronym">BIND</acronym> 9.
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User To achieve the intended effect
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater of
098097efb95046a4a5285b6dae95dea3e3b70853Automatic Updater <span><strong class="command">has-old-clients</strong></span> <strong class="userinput"><code>yes</code></strong>, specify
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the two separate options <span><strong class="command">auth-nxdomain</strong></span> <strong class="userinput"><code>yes</code></strong>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater and <span><strong class="command">rfc2308-type1</strong></span> <strong class="userinput"><code>no</code></strong> instead.
78bc8fdc2488c92d7228e8de19827e2c114c56caAutomatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">host-statistics</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater In BIND 8, this enables keeping of
9d80d23172c30fd63e5046a7e69b8445e564ff31Automatic Updater statistics for every host that the name server interacts
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User with.
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater Not implemented in BIND 9.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<dt><span class="term"><span><strong class="command">maintain-ixfr-base</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User <span class="emphasis"><em>This option is obsolete</em></span>.
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater It was used in <acronym class="acronym">BIND</acronym> 8 to
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater determine whether a transaction log was
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater kept for Incremental Zone Transfer. <acronym class="acronym">BIND</acronym> 9 maintains a transaction
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews log whenever possible. If you need to disable outgoing
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews incremental zone
e705db6d5d886dc14f4a75a2046a075c0750e7eeAutomatic Updater transfers, use <span><strong class="command">provide-ixfr</strong></span> <strong class="userinput"><code>no</code></strong>.
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater </p></dd>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dt><span class="term"><span><strong class="command">minimal-responses</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User If <strong class="userinput"><code>yes</code></strong>, then when generating
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater responses the server will only add records to the authority
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater and additional data sections when they are required (e.g.
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater delegations, negative responses). This may improve the
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User performance of the server.
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User The default is <strong class="userinput"><code>no</code></strong>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User<dt><span class="term"><span><strong class="command">multiple-cnames</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This option was used in <acronym class="acronym">BIND</acronym> 8 to allow
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User a domain name to have multiple CNAME records in violation of
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User the DNS standards. <acronym class="acronym">BIND</acronym> 9.2 onwards
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User always strictly enforces the CNAME rules both in master
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews files and dynamic updates.
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">notify</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User If <strong class="userinput"><code>yes</code></strong> (the default),
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater DNS NOTIFY messages are sent when a zone the server is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater authoritative for
2bb3422dc683c013db7042f5736240de6b86f182Automatic Updater changes, see <a href="Bv9ARM.ch04.html#notify" title="Notify">the section called &#8220;Notify&#8221;</a>. The messages are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater sent to the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater servers listed in the zone's NS records (except the master
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews server identified
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User in the SOA MNAME field), and to any servers listed in the
b4cebdb6ccde66a8f3e397a1b90b0cf788519d69Automatic Updater <span><strong class="command">also-notify</strong></span> option.
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User If <strong class="userinput"><code>master-only</code></strong>, notifies are only
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User sent
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for master zones.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User If <strong class="userinput"><code>explicit</code></strong>, notifies are sent only
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater servers explicitly listed using <span><strong class="command">also-notify</strong></span>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User If <strong class="userinput"><code>no</code></strong>, no notifies are sent.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The <span><strong class="command">notify</strong></span> option may also be
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User specified in the <span><strong class="command">zone</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statement,
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User in which case it overrides the <span><strong class="command">options notify</strong></span> statement.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater It would only be necessary to turn off this option if it
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User caused slaves
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User to crash.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">notify-to-soa</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong> do not check the nameservers
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in the NS RRset against the SOA MNAME. Normally a NOTIFY
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater message is not sent to the SOA MNAME (SOA ORIGIN) as it is
1ac49378a458420bc685293d12e567d7222d17b6Tinderbox User supposed to contain the name of the ultimate master.
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User Sometimes, however, a slave is listed as the SOA MNAME in
681beefc668253b3e469a1de282fbc33a3752422Automatic Updater hidden master configurations and in that case you would
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User want the ultimate master to still send NOTIFY messages to
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User all the nameservers listed in the NS RRset.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">recursion</strong></span></span></dt>
b16e2045ac28229c31f1ea3ebad15cbcb13e1d24Automatic Updater<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User If <strong class="userinput"><code>yes</code></strong>, and a
b3386fba31414344f38f0c30849c056dceb22dceTinderbox User DNS query requests recursion, then the server will attempt
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User to do
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User all the work required to answer the query. If recursion is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater off
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and the server does not already know the answer, it will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater return a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater referral response. The default is
71bfd0968456cc0c69fd400d2dafd02977c649d2Tinderbox User <strong class="userinput"><code>yes</code></strong>.
83e281baf1b4149dc637d24dd41141129ae712c6Tinderbox User Note that setting <span><strong class="command">recursion no</strong></span> does not prevent
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater clients from getting data from the server's cache; it only
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User prevents new data from being cached as an effect of client
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater queries.
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User Caching may still occur as an effect the server's internal
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater operation, such as NOTIFY address lookups.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews See also <span><strong class="command">fetch-glue</strong></span> above.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater<dt><span class="term"><span><strong class="command">rfc2308-type1</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd>
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Setting this to <strong class="userinput"><code>yes</code></strong> will
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User cause the server to send NS records along with the SOA
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User record for negative
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User answers. The default is <strong class="userinput"><code>no</code></strong>.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<h3 class="title">Note</h3>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews Not yet implemented in <acronym class="acronym">BIND</acronym>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User 9.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User</dd>
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User<dt><span class="term"><span><strong class="command">use-id-pool</strong></span></span></dt>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<dd><p>
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User <span class="emphasis"><em>This option is obsolete</em></span>.
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews <acronym class="acronym">BIND</acronym> 9 always allocates query
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User IDs from a pool.
b5423cbff7175727ed9046c8c670d8a7bb4d01eaTinderbox User </p></dd>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User If <strong class="userinput"><code>yes</code></strong>, the server will collect
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User statistical data on all zones (unless specifically turned
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User off
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews on a per-zone basis by specifying <span><strong class="command">zone-statistics no</strong></span>
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User in the <span><strong class="command">zone</strong></span> statement).
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User The default is <strong class="userinput"><code>no</code></strong>.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews These statistics may be accessed
049728912c39135db248f9b48f8f26675f456e9dTinderbox User using <span><strong class="command">rndc stats</strong></span>, which will
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User dump them to the file listed
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User in the <span><strong class="command">statistics-file</strong></span>. See
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews also <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called &#8220;The Statistics File&#8221;</a>.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p></dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="term"><span><strong class="command">use-ixfr</strong></span></span></dt>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<dd><p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <span class="emphasis"><em>This option is obsolete</em></span>.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User If you need to disable IXFR to a particular server or
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User servers, see
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User the information on the <span><strong class="command">provide-ixfr</strong></span> option
be5e43393922d459eae5c8c467c0320d4a018666Tinderbox User in <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
78d7186253dfed549ec0ce2d7c2b08a7978ede9cAutomatic Updater Usage&#8221;</a>.
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater See also
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <a href="Bv9ARM.ch04.html#incremental_zone_transfers" title="Incremental Zone Transfers (IXFR)">the section called &#8220;Incremental Zone Transfers (IXFR)&#8221;</a>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User<dt><span class="term"><span><strong class="command">provide-ixfr</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater See the description of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">provide-ixfr</strong></span> in
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater Usage&#8221;</a>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">request-ixfr</strong></span></span></dt>
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater See the description of
c904ec617fe9e711c6743660a66b7dee1e213756Tinderbox User <span><strong class="command">request-ixfr</strong></span> in
c01dec514a81ecf8c17ca3ef8c3ba95e437295ebAutomatic Updater <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Usage&#8221;</a>.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">treat-cr-as-space</strong></span></span></dt>
ce0fd07045292942bfa3e755d9ce596941528a63Automatic Updater<dd><p>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User This option was used in <acronym class="acronym">BIND</acronym>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater 8 to make
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User the server treat carriage return ("<span><strong class="command">\r</strong></span>") characters the same way
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater as a space or tab character,
96713299d08c0735c18ebe8772dd2cc1ecd4356aAutomatic Updater to facilitate loading of zone files on a UNIX system that
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater were generated
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User on an NT or DOS machine. In <acronym class="acronym">BIND</acronym> 9, both UNIX "<span><strong class="command">\n</strong></span>"
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and NT/DOS "<span><strong class="command">\r\n</strong></span>" newlines
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater are always accepted,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User and the option is ignored.
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </p></dd>
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater<dt>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<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>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews</dt>
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews These options control the behavior of an authoritative
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews server when
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User answering queries which have additional data, or when
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User following CNAME
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and DNAME chains.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater When both of these options are set to <strong class="userinput"><code>yes</code></strong>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater (the default) and a
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User query is being answered from authoritative data (a zone
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater configured into the server), the additional data section of
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater the
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews reply will be filled in using data from other authoritative
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater zones
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and from the cache. In some situations this is undesirable,
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater such
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater as when there is concern over the correctness of the cache,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater or
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater in servers where slave zones may be added and modified by
0ead2ac0a4b59c3e4a731027f0f66fbe602b1289Tinderbox User untrusted third parties. Also, avoiding
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User the search for this additional data will speed up server
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater operations
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater at the possible expense of additional queries to resolve
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews what would
c904ec617fe9e711c6743660a66b7dee1e213756Tinderbox User otherwise be provided in the additional section.
78bc8fdc2488c92d7228e8de19827e2c114c56caAutomatic Updater </p>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater For example, if a query asks for an MX record for host <code class="literal">foo.example.com</code>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and the record found is "<code class="literal">MX 10 mail.example.net</code>", normally the address
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater records (A and AAAA) for <code class="literal">mail.example.net</code> will be provided as well,
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User if known, even though they are not in the example.com zone.
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User Setting these options to <span><strong class="command">no</strong></span>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson disables this behavior and makes
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User the server only search for additional data in the zone it
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews answers from.
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater These options are intended for use in authoritative-only
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater servers, or in authoritative-only views. Attempts to set
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews them to <span><strong class="command">no</strong></span> without also
e705db6d5d886dc14f4a75a2046a075c0750e7eeAutomatic Updater specifying
c57668a2fbbe558c1bd21652813616f2f517c469Tinderbox User <span><strong class="command">recursion no</strong></span> will cause the
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User server to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater ignore the options and log a warning message.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Specifying <span><strong class="command">additional-from-cache no</strong></span> actually
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater disables the use of the cache not only for additional data
dc435f1033bcba88b748074987db6cfd34c057a4Tinderbox User lookups
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater but also when looking up the answer. This is usually the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater desired
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews behavior in an authoritative-only server where the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User correctness of
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the cached data is an issue.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
40696c4c389a780082fb77840c173b201ce696d6Automatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User When a name server is non-recursively queried for a name
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User that is not
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User below the apex of any served zone, it normally answers with
40696c4c389a780082fb77840c173b201ce696d6Automatic Updater an
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User "upwards referral" to the root servers or the servers of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater some other
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews known parent of the query name. Since the data in an
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater upwards referral
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User comes from the cache, the server will not be able to provide
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater upwards
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User referrals when <span><strong class="command">additional-from-cache no</strong></span>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User has been specified. Instead, it will respond to such
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater queries
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater with REFUSED. This should not cause any problems since
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User upwards referrals are not required for the resolution
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater process.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">match-mapped-addresses</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then an
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv4-mapped IPv6 address will match any address match
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater list entries that match the corresponding IPv4 address.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This option was introduced to work around a kernel quirk
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in some operating systems that causes IPv4 TCP
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater connections, such as zone transfers, to be accepted on an
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv6 socket using mapped addresses. This caused address
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater match lists designed for IPv4 to fail to match. However,
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson <span><strong class="command">named</strong></span> now solves this problem
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater internally. The use of this option is discouraged.
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson </p>
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<dd>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews When <strong class="userinput"><code>yes</code></strong> and the server loads a new version of a master
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater zone from its zone file or receives a new version of a slave
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User file by a non-incremental zone transfer, it will compare
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the new version to the previous one and calculate a set
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews of differences. The differences are then logged in the
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User zone's journal file such that the changes can be transmitted
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater to downstream slaves as an incremental zone transfer.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater<p>
e5fe07a7ebff18f7ed4ac434b37daff6c8ee5d5bAutomatic Updater By allowing incremental zone transfers to be used for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater non-dynamic zones, this option saves bandwidth at the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater expense of increased CPU and memory consumption at the
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews master.
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User In particular, if the new version of a zone is completely
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater different from the previous one, the set of differences
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater will be of a size comparable to the combined size of the
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews old and new zone version, and the server will need to
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater temporarily allocate memory to hold this complete
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson difference set.
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p><span><strong class="command">ixfr-from-differences</strong></span>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User also accepts <span><strong class="command">master</strong></span> and
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews <span><strong class="command">slave</strong></span> at the view and options
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User levels which causes
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User <span><strong class="command">ixfr-from-differences</strong></span> to be enabled for
a900e4f99ff134b567b6df5ac2c841c7d0c551d3Automatic Updater all <span><strong class="command">master</strong></span> or
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">slave</strong></span> zones respectively.
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews It is off by default.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User</dd>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews<dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt>
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User<dd><p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User This should be set when you have multiple masters for a zone
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User and the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, <span><strong class="command">named</strong></span> will
a900e4f99ff134b567b6df5ac2c841c7d0c551d3Automatic Updater not log
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater when the serial number on the master is less than what <span><strong class="command">named</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater currently
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater has. The default is <strong class="userinput"><code>no</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">dnssec-enable</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Enable DNSSEC support in <span><strong class="command">named</strong></span>. Unless set to <strong class="userinput"><code>yes</code></strong>,
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater <span><strong class="command">named</strong></span> behaves as if it does not support DNSSEC.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default is <strong class="userinput"><code>yes</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">dnssec-validation</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Enable DNSSEC validation in <span><strong class="command">named</strong></span>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User set to <strong class="userinput"><code>yes</code></strong> to be effective.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default is <strong class="userinput"><code>yes</code></strong>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">dnssec-accept-expired</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Accept expired signatures when verifying DNSSEC signatures.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default is <strong class="userinput"><code>no</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Setting this option to "yes" leaves <span><strong class="command">named</strong></span> vulnerable to replay attacks.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="term"><span><strong class="command">querylog</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd><p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews Specify whether query logging should be started when <span><strong class="command">named</strong></span>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews starts.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews If <span><strong class="command">querylog</strong></span> is not specified,
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews then the query logging
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews is determined by the presence of the logging category <span><strong class="command">queries</strong></span>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p></dd>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews This option is used to restrict the character set and syntax
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews of
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews certain domain names in master files and/or DNS responses
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews received
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews from the network. The default varies according to usage
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews area. For
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews For <span><strong class="command">slave</strong></span> zones the default
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews is <span><strong class="command">warn</strong></span>.
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews For answers received from the network (<span><strong class="command">response</strong></span>)
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews the default is <span><strong class="command">ignore</strong></span>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews The rules for legal hostnames and mail domains are derived
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews from RFC 952 and RFC 821 as modified by RFC 1123.
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p><span><strong class="command">check-names</strong></span>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews applies to the owner names of A, AAAA and MX records.
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews It also applies to the domain names in the RDATA of NS, SOA,
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews MX, and SRV records.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews It also applies to the RDATA of PTR records where the owner
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews name indicated that it is a reverse lookup of a hostname
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews (the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT).
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews</dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd><p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews Check whether the MX record appears to refer to a IP address.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews The default is to <span><strong class="command">warn</strong></span>. Other possible
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews values are <span><strong class="command">fail</strong></span> and
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews <span><strong class="command">ignore</strong></span>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p></dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<dd><p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews This option is used to check for non-terminal wildcards.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews The use of non-terminal wildcards is almost always as a
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews result of a failure
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews to understand the wildcard matching algorithm (RFC 1034).
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews This option
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews affects master zones. The default (<span><strong class="command">yes</strong></span>) is to check
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews for non-terminal wildcards and issue a warning.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt>
e23256e740b238bddb4ba41ffac5f81a01c92245Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Perform post load zone integrity checks on master
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User zones. This checks that MX and SRV records refer
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User to address (A or AAAA) records and that glue
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User address records exist for delegated zones. For
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater MX and SRV records only in-zone hostnames are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater checked (for out-of-zone hostnames use
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater <span><strong class="command">named-checkzone</strong></span>).
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User For NS records only names below top of zone are
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User checked (for out-of-zone names and glue consistency
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User checks use <span><strong class="command">named-checkzone</strong></span>).
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default is <span><strong class="command">yes</strong></span>.
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User </p></dd>
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User<dt><span class="term"><span><strong class="command">check-mx-cname</strong></span></span></dt>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<dd><p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson If <span><strong class="command">check-integrity</strong></span> is set then
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater fail, warn or ignore MX records that refer
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson to CNAMES. The default is to <span><strong class="command">warn</strong></span>.
02973ab41430678c285ef7ae6d1183003469a3bcAutomatic Updater </p></dd>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<dt><span class="term"><span><strong class="command">check-srv-cname</strong></span></span></dt>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <span><strong class="command">check-integrity</strong></span> is set then
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User fail, warn or ignore SRV records that refer
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User to CNAMES. The default is to <span><strong class="command">warn</strong></span>.
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </p></dd>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt>
794f12f4ff199731c66e06a271ccc2794177ef85Mark Andrews<dd><p>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User When performing integrity checks, also check that
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User sibling glue exists. The default is <span><strong class="command">yes</strong></span>.
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User </p></dd>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User When returning authoritative negative responses to
713c3d5b18463f2479973e4d14f73248e60a5df7Mark Andrews SOA queries set the TTL of the SOA record returned in
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the authority section to zero.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The default is <span><strong class="command">yes</strong></span>.
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater </p></dd>
0a50626faa2f8941f55bf435d3965d490bb5d026Tinderbox User<dt><span class="term"><span><strong class="command">zero-no-soa-ttl-cache</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson When caching a negative response to a SOA query
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson set the TTL to zero.
992616aaf75643a0c9f84826f0a1ed5a27e84328Mark Andrews The default is <span><strong class="command">no</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt>
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews<dd><p>
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews When regenerating the RRSIGs following a UPDATE
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews request to a secure zone, check the KSK flag on
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews the DNSKEY RR to determine if this key should be
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews used to generate the RRSIG. This flag is ignored
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User if there are not DNSKEY RRs both with and without
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User a KSK.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The default is <span><strong class="command">yes</strong></span>.
9fa6e3bdb4ec36d8734c63c4366375a681aa3a4dAutomatic Updater </p></dd>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<dt><span class="term"><span><strong class="command">try-tcp-refresh</strong></span></span></dt>
922e6a3c2ac4ef900dd9dc99f0cc137f18372583Andreas Gustafsson<dd><p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User Try to refresh the zone using TCP if UDP queries fail.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User For BIND 8 compatibility, the default is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">yes</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">secure-to-insecure</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Allow a zone to transition from secure to insecure by
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User deleting all DNSKEY records. The default is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">no</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dl></div>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="sect3" lang="en">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="titlepage"><div><div><h4 class="title">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<a name="id2582228"></a>Forwarding</h4></div></div></div>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The forwarding facility can be used to create a large site-wide
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User cache on a few servers, reducing traffic over links to external
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User name servers. It can also be used to allow queries by servers that
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User do not have direct access to the Internet, but wish to look up
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User exterior
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User names anyway. Forwarding occurs only on those queries for which
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the server is not authoritative and does not have the answer in
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews its cache.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="variablelist"><dl>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">forward</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This option is only meaningful if the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User forwarders list is not empty. A value of <code class="varname">first</code>,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews the default, causes the server to query the forwarders
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User first &#8212; and
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User if that doesn't answer the question, the server will then
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User look for
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the answer itself. If <code class="varname">only</code> is
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews specified, the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews server will only query the forwarders.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies the IP addresses to be used
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User for forwarding. The default is the empty list (no
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User forwarding).
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dl></div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Forwarding can also be configured on a per-domain basis, allowing
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User for the global forwarding options to be overridden in a variety
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User of ways. You can set particular domains to use different
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User forwarders,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User or have a different <span><strong class="command">forward only/first</strong></span> behavior,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User or not forward at all, see <a href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Statement Grammar">the section called &#8220;<span><strong class="command">zone</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Statement Grammar&#8221;</a>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="sect3" lang="en">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="titlepage"><div><div><h4 class="title">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<a name="id2582286"></a>Dual-stack Servers</h4></div></div></div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Dual-stack servers are used as servers of last resort to work
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User around
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User problems in reachability due the lack of support for either IPv4
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User or IPv6
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User on the host machine.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="variablelist"><dl>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">dual-stack-servers</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies host names or addresses of machines with access to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User both IPv4 and IPv6 transports. If a hostname is used, the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User server must be able
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to resolve the name using only the transport it has. If the
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater machine is dual
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User stacked, then the <span><strong class="command">dual-stack-servers</strong></span> have no effect unless
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User access to a transport has been disabled on the command line
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User (e.g. <span><strong class="command">named -4</strong></span>).
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dl></div>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="sect3" lang="en">
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<div class="titlepage"><div><div><h4 class="title">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<a name="access_control"></a>Access Control</h4></div></div></div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Access to the server can be restricted based on the IP address
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User 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
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User details on how to specify IP address lists.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="variablelist"><dl>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies which hosts are allowed to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User notify this server, a slave, of zone changes in addition
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to the zone masters.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">allow-notify</strong></span> may also be
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User specified in the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">zone</strong></span> statement, in which case
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User it overrides the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">options allow-notify</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User statement. It is only meaningful
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews for a slave zone. If not specified, the default is to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User process notify messages
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User only from a zone's master.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies which hosts are allowed to ask ordinary
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User DNS questions. <span><strong class="command">allow-query</strong></span> may
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User also be specified in the <span><strong class="command">zone</strong></span>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews statement, in which case it overrides the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">options allow-query</strong></span> statement.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If not specified, the default is to allow queries
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from all hosts.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<h3 class="title">Note</h3>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">allow-query-cache</strong></span> is now
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User used to specify access to the cache.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">allow-query-on</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies which local addresses can accept ordinary
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User DNS questions. This makes it possible, for instance,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to allow queries on internal-facing interfaces but
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User disallow them on external-facing ones, without
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User necessarily knowing the internal network's addresses.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">allow-query-on</strong></span> may
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User also be specified in the <span><strong class="command">zone</strong></span>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews statement, in which case it overrides the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">options allow-query-on</strong></span> statement.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If not specified, the default is to allow queries
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater on all addresses.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<h3 class="title">Note</h3>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">allow-query-cache</strong></span> is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User used to specify access to the cache.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">allow-query-cache</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Specifies which hosts are allowed to get answers
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from the cache. If <span><strong class="command">allow-query-cache</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is not set then <span><strong class="command">allow-recursion</strong></span>
3d2e052eb879189e6d853097f8b568d887323bebTinderbox User is used if set, otherwise <span><strong class="command">allow-query</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is used if set unless <span><strong class="command">recursion no;</strong></span> is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User set in which case <span><strong class="command">none;</strong></span> is used,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User otherwise the default (<span><strong class="command">localnets;</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">localhost;</strong></span>) is used.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">allow-query-cache-on</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies which local addresses can give answers
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from the cache. If not specified, the default is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to allow cache queries on any address,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">localnets</strong></span> and
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">localhost</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">allow-recursion</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies which hosts are allowed to make recursive
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User queries through this server. If
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">allow-recursion</strong></span> is not set
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User then <span><strong class="command">allow-query-cache</strong></span> is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User used if set, otherwise <span><strong class="command">allow-query</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is used if set, otherwise the default
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User (<span><strong class="command">localnets;</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">localhost;</strong></span>) is used.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">allow-recursion-on</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies which local addresses can accept recursive
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User queries. If not specified, the default is to allow
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User recursive queries on all addresses.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Specifies which hosts are allowed to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User submit Dynamic DNS updates for master zones. The default is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to deny
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User updates from all hosts. Note that allowing updates based
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User on the requestor's IP address is insecure; see
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called &#8220;Dynamic Update Security&#8221;</a> for details.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Specifies which hosts are allowed to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User submit Dynamic DNS updates to slave zones to be forwarded to
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User master. The default is <strong class="userinput"><code>{ none; }</code></strong>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User which
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User means that no update forwarding will be performed. To
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User enable
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User update forwarding, specify
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <strong class="userinput"><code>allow-update-forwarding { any; };</code></strong>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifying values other than <strong class="userinput"><code>{ none; }</code></strong> or
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <strong class="userinput"><code>{ any; }</code></strong> is usually
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User counterproductive, since
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the responsibility for update access control should rest
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews with the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User master server, not the slaves.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Note that enabling the update forwarding feature on a slave
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User server
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User may expose master servers relying on insecure IP address
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User based
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User 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>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User for more details.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">allow-v6-synthesis</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews This option was introduced for the smooth transition from
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User AAAA
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to A6 and from "nibble labels" to binary labels.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User However, since both A6 and binary labels were then
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews deprecated,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User this option was also deprecated.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User It is now ignored with some warning messages.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies which hosts are allowed to
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews receive zone transfers from the server. <span><strong class="command">allow-transfer</strong></span> may
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User also be specified in the <span><strong class="command">zone</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User statement, in which
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User case it overrides the <span><strong class="command">options allow-transfer</strong></span> statement.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If not specified, the default is to allow transfers to all
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User hosts.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">blackhole</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies a list of addresses that the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User server will not accept queries from or use to resolve a
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User query. Queries
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from these addresses will not be responded to. The default
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is <strong class="userinput"><code>none</code></strong>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dl></div>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="sect3" lang="en">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="titlepage"><div><div><h4 class="title">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<a name="id2582929"></a>Interfaces</h4></div></div></div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The interfaces and ports that the server will answer queries
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from may be specified using the <span><strong class="command">listen-on</strong></span> option. <span><strong class="command">listen-on</strong></span> takes
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User an optional port and an <code class="varname">address_match_list</code>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The server will listen on all interfaces allowed by the address
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews match list. If a port is not specified, port 53 will be used.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Multiple <span><strong class="command">listen-on</strong></span> statements are
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User allowed.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User For example,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<pre class="programlisting">listen-on { 5.6.7.8; };
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox Userlisten-on port 1234 { !1.2.3.4; 1.2/16; };
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</pre>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User will enable the name server on port 53 for the IP address
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User 5.6.7.8, and on port 1234 of an address on the machine in net
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User 1.2 that is not 1.2.3.4.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If no <span><strong class="command">listen-on</strong></span> is specified, the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User server will listen on port 53 on all IPv4 interfaces.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The <span><strong class="command">listen-on-v6</strong></span> option is used to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User specify the interfaces and the ports on which the server will
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User listen
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews for incoming queries sent using IPv6.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews When </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<pre class="programlisting">{ any; }</pre>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p> is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User specified
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User as the <code class="varname">address_match_list</code> for the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">listen-on-v6</strong></span> option,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the server does not bind a separate socket to each IPv6 interface
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User address as it does for IPv4 if the operating system has enough API
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews support for IPv6 (specifically if it conforms to RFC 3493 and RFC
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User 3542).
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Instead, it listens on the IPv6 wildcard address.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If the system only has incomplete API support for IPv6, however,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the behavior is the same as that for IPv4.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User A list of particular IPv6 addresses can also be specified, in
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User which case
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater the server listens on a separate socket for each specified
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User address,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User regardless of whether the desired API is supported by the system.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
017d755d7a606dfb1e02a9d6e2b29e49e39fde16Tinderbox User Multiple <span><strong class="command">listen-on-v6</strong></span> options can
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater be used.
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews For example,
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<pre class="programlisting">listen-on-v6 { any; };
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updaterlisten-on-v6 port 1234 { !2001:db8::/32; any; };
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater</pre>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
081a44bd3019b18aec03c5c0746538fdc901da48Evan Hunt will enable the name server on port 53 for any IPv6 addresses
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User (with a single wildcard socket),
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User and on port 1234 of IPv6 addresses that is not in the prefix
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User 2001:db8::/32 (with separate sockets for each matched address.)
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
200a9e7da827b67d99193bf793aea9f3e3fa1b43Tinderbox User To make the server not listen on any IPv6 address, use
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </p>
af9dbf1ccdd53933aaae9300d13ce0965d39b067Evan Hunt<pre class="programlisting">listen-on-v6 { none; };
bb5fe714ce8625e6744dd84526828c36bcff12f6Tinderbox User</pre>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User If no <span><strong class="command">listen-on-v6</strong></span> option is
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User specified, the server will not listen on any IPv6 address
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User unless <span><strong class="command">-6</strong></span> is specified when <span><strong class="command">named</strong></span> is
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater invoked. If <span><strong class="command">-6</strong></span> is specified then
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <span><strong class="command">named</strong></span> will listen on port 53 on all IPv6 interfaces by default.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User</div>
af9dbf1ccdd53933aaae9300d13ce0965d39b067Evan Hunt<div class="sect3" lang="en">
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<div class="titlepage"><div><div><h4 class="title">
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<a name="query_address"></a>Query Address</h4></div></div></div>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User If the server doesn't know the answer to a question, it will
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User query other name servers. <span><strong class="command">query-source</strong></span> specifies
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User the address and port used for such queries. For queries sent over
b87da030df926d03cf53f299cc73b046cfd5e9fbTinderbox User IPv6, there is a separate <span><strong class="command">query-source-v6</strong></span> option.
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User If <span><strong class="command">address</strong></span> is <span><strong class="command">*</strong></span> (asterisk) or is omitted,
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User a wildcard IP address (<span><strong class="command">INADDR_ANY</strong></span>)
63d98873e29dee9608c27f40613cb69d130a56e7Mark Andrews will be used.
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
ca9a8f6d0b0f2a400a96f868193471510364336fMark Andrews If <span><strong class="command">port</strong></span> is <span><strong class="command">*</strong></span> or is omitted,
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User a random port number from a pre-configured
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User range is picked up and will be used for each query.
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews The port range(s) is that specified in
5f33078b538b3d317917deb962bd057b2a888db1Tinderbox User the <span><strong class="command">use-v4-udp-ports</strong></span> (for IPv4)
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User and <span><strong class="command">use-v6-udp-ports</strong></span> (for IPv6)
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews options, excluding the ranges specified in
b8cc0c5d896c361525708a2be2e5af7df76c96d7Tinderbox User the <span><strong class="command">avoid-v4-udp-ports</strong></span>
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User and <span><strong class="command">avoid-v6-udp-ports</strong></span> options, respectively.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User<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.
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">serial-query-rate</strong></span></span></dt>
<dd><p>
Slave servers will periodically query master servers
to find out if zone serial numbers have changed. Each such
query uses
a minute amount of the slave server's network bandwidth. To
limit the
amount of bandwidth used, BIND 9 limits the rate at which
queries are
sent. The value of the <span><strong class="command">serial-query-rate</strong></span> option,
an integer, is the maximum number of queries sent per
second.
The default is 20.
</p></dd>
<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="id2583995"></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="id2584055"></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 default is
<code class="literal">unlimited</code>.
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.
A value of 0 is special, meaning that
records are purged from the cache only when their
TTLs expire.
Another special keyword <strong class="userinput"><code>unlimited</code></strong>
means the maximum value of 32-bit unsigned integers
(0xffffffff), which may not have the same effect as
0 on machines that support more than 32 bits of
memory space.
Any positive values less than 2MB will be ignored reset
to 2MB.
In a server with multiple views, the limit applies
separately to the cache of each view.
The default is 0.
</p></dd>
<dt><span class="term"><span><strong class="command">tcp-listen-queue</strong></span></span></dt>
<dd><p>
The listen queue depth. The default and minimum is 3.
If the kernel supports the accept filter "dataready" this
also controls how
many TCP connections that will be queued in kernel space
waiting for
some data before being passed to accept. Values less than 3
will be
silently raised.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2584614"></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>
<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">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
key signing records. The default is
<code class="literal">65535</code>.
</p>
<p>
It is expected that this parameter may be removed
in a future version once there is a standard type.
</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>
</dd>
<dt><span class="term"><span><strong class="command">edns-udp-size</strong></span></span></dt>
<dd>
<p>
Sets the advertised EDNS UDP buffer size in bytes
to control the size of packets received.
Valid values are 1024 to 4096 (values outside this range
will be silently adjusted). The default value
is 4096. 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 packets that are greater than 512 bytes.
</p>
<p>
<span><strong class="command">named</strong></span> will fallback to using 512 bytes
if it get a series of timeout at the initial value. 512
bytes is not being offered to encourage sites to fix their
firewalls. Small EDNS UDP sizes will result in the
excessive use of TCP.
</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). The default
value is 4096. 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 encourge 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. Files in other formats
than <code class="constant">text</code> are typically expected
to be generated by the <span><strong class="command">named-compilezone</strong></span> tool.
Note that when a zone file in a different format than
<code class="constant">text</code> is loaded, <span><strong class="command">named</strong></span>
may omit some of the checks which would be performed for a
file in the <code class="constant">text</code> format. In particular,
<span><strong class="command">check-names</strong></span> checks do not apply
for the <code class="constant">raw</code> format. This means
a zone file in the <code class="constant">raw</code> format
must be generated with the same check level as that
specified in the <span><strong class="command">named</strong></span> configuration
file. This statement sets the
<span><strong class="command">masterfile-format</strong></span> for all zones,
but can be overridden on a per-zone or per-view basis
by including a <span><strong class="command">masterfile-format</strong></span>
statement within the <span><strong class="command">zone</strong></span> or
<span><strong class="command">view</strong></span> block in the configuration
file.
</p></dd>
<dt>
<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><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt>
<dd><p>
The delay, in seconds, between sending sets of notify
messages for a zone. The default is zero.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="builtin"></a>Built-in server information zones</h4></div></div></div>
<p>
The server provides some helpful diagnostic information
through a number of built-in zones under the
pseudo-top-level-domain <code class="literal">bind</code> in the
<span><strong class="command">CHAOS</strong></span> class. These zones are part
of a
built-in view (see <a href="Bv9ARM.ch06.html#view_statement_grammar" title="view Statement Grammar">the section called &#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>; therefore, any global
server options
such as <span><strong class="command">allow-query</strong></span> do not apply
the these zones.
If you feel the need to disable these zones, use the options
below, or hide the built-in <span><strong class="command">CHAOS</strong></span>
view by
defining an explicit view of class <span><strong class="command">CHAOS</strong></span>
that matches all clients.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">version</strong></span></span></dt>
<dd><p>
The version the server should report
via a query of the name <code class="literal">version.bind</code>
with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
The default is the real version number of this server.
Specifying <span><strong class="command">version none</strong></span>
disables processing of the queries.
</p></dd>
<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>
Named has some built-in empty zones (SOA and NS records only).
These are for zones that should normally be answered locally
and which queries should not be sent to the Internet's root
servers. The official servers which cover these namespaces
return NXDOMAIN responses to these queries. In particular,
these cover the reverse namespace for addresses from RFC 1918 and
RFC 3330. They also include the reverse namespace for IPv6 local
address (locally assigned), IPv6 link local addresses, the IPv6
loopback address and the IPv6 unknown address.
</p>
<p>
Named will attempt to determine if a built-in zone already exists
or is active (covered by a forward-only forwarding declaration)
and will not create an empty zone in that case.
</p>
<p>
The current list of empty zones is:
</p>
<div class="itemizedlist"><ul type="disc">
<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>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>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="id2586830"></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="" 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>
<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"> edns <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> transfers <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> transfer-format <em class="replaceable"><code>( one-answer | many-answers )</code></em> ; ]</span>]
[<span class="optional"> keys <em class="replaceable"><code>{ string ; [<span class="optional"> string ; [<span class="optional">...</span>]</span>] }</code></em> ; </span>]
[<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> query-source [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
[<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]; </span>]
[<span class="optional"> query-source-v6 [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
[<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]; </span>]
[<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-interval <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.
</p>
<p>
IXFR requests to servers that do not support IXFR will
automatically
fall back to AXFR. Therefore, there is no need to manually list
which servers support IXFR and which ones do not; the global
default
of <span><strong class="command">yes</strong></span> should always work.
The purpose of the <span><strong class="command">provide-ixfr</strong></span> and
<span><strong class="command">request-ixfr</strong></span> clauses is
to make it possible to disable the use of IXFR even when both
master
and slave claim to support it, for example if one of the servers
is buggy and crashes or corrupts data when IXFR is used.
</p>
<p>
The <span><strong class="command">edns</strong></span> clause determines whether
the local server will attempt to use EDNS when communicating
with the remote server. The default is <span><strong class="command">yes</strong></span>.
</p>
<p>
The <span><strong class="command">edns-udp-size</strong></span> option sets the EDNS UDP size
that is advertised by <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). This option is useful when you wish to
advertises a different value to this server than the value you
advertise globally, for example, when there is a firewall at the
remote site that is blocking large replies.
</p>
<p>
The <span><strong class="command">max-udp-size</strong></span> option sets the
maximum EDNS UDP message size <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 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>
</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="id2587582"></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;
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>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2587737"></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="id2587857"></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>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2587904"></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>string</code></em> initial-key <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> initial-key <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="id2587955"></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>
If the <span><strong class="command">dnssec-lookaside</strong></span> option is set to
"auto", <span><strong class="command">named</strong></span> will automatically initialize
a managed key for the zone <code class="literal">dlv.isc.org</code>. 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="id2588172"></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-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"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> check-mx (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>]
[<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>) ; </span>]
[<span class="optional"> journal <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> 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>] }; </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"> 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>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> sig-validity-interval <em class="replaceable"><code>number</code></em> [<span 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"> 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 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"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> 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 { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ;
[<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>]
[<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>) ; </span>]
[<span class="optional"> journal <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> 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>] }; </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>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em>
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>]
[<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <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>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> 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>]
[<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>) ; </span>]
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em>
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>]
[<span class="optional"> 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>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; </span>]
[<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> 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 forward;
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type delegation-only;
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2589860"></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="id2589867"></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">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">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="id2590295"></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="id2590328"></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.
<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-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">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 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">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">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">secure-to-insecure</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">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>
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>,
and <code class="varname">zonesub</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">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>
</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>
</div>
<div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="id2592584"></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="id2592602"></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="id2594157"></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="id2594746"></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
the it.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
All of these TTLs default to units of seconds, though units
can be explicitly specified, for example, <code class="literal">1h30m</code>.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2595362"></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="id2595489"></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="id2595511"></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="id2595527"></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="id2595588"></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="id2595657"></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="id2595693"></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. All of start, stop and step must be positive.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">lhs</strong></span></p>
</td>
<td>
<p>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. The <code class="constant">raw</code> format is
currently available as an additional format. It is a
binary format representing BIND 9's internal data
structure directly, thereby remarkably improving the
loading time.
</p>
<p>
For a primary server, a zone file in the
<code class="constant">raw</code> format is expected to be
generated from a textual zone file by the
<span><strong class="command">named-compilezone</strong></span> command. For a
secondary server or for a dynamic zone, it is automatically
generated (if this format is specified by the
<span><strong class="command">masterfile-format</strong></span> option) when
<span><strong class="command">named</strong></span> dumps the zone contents after
zone transfer or when applying prior updates.
</p>
<p>
If a zone file in a binary format needs manual modification,
it first must be converted to a textual form by the
<span><strong class="command">named-compilezone</strong></span> command. All
necessary modification should go to the text file, which
should then be converted to the binary form by the
<span><strong class="command">named-compilezone</strong></span> command again.
</p>
<p>
Although the <code class="constant">raw</code> format uses the
network byte order and avoids architecture-dependent
data alignment so that it is as much portable as
possible, it is primarily expected to be used inside
the same single system. In order to export a zone
file in the <code class="constant">raw</code> format or make a
portable backup of the file, it is recommended to
convert the file to the standard textual representation.
</p>
</div>
</div>
<div 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").
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="id2596784"></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>
</tbody>
</table></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2598393"></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="id2598776"></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="id2599798"></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="id2600240"></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>
</body>
</html>