Bv9ARM.ch06.html revision 81199ce5ba7bd719add38189b06987e0a6e583a1
436aad11e01e916f75e68a2e9cb89ac217a990d3Tinderbox User<!--
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User - Copyright (C) 2000-2003 Internet Software Consortium.
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User -
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User - 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
c57668a2fbbe558c1bd21652813616f2f517c469Tinderbox User - copyright notice and this permission notice appear in all copies.
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews -
1f4c645185bd8fc70048e0a69eee46193a284e5cTinderbox User - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
02b47c5d62e1e827743684c28a08e871da454a2dMark Andrews - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
e20309353e6246485c521278131d3fced73d7957Tinderbox User - PERFORMANCE OF THIS SOFTWARE.
e20309353e6246485c521278131d3fced73d7957Tinderbox User-->
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<!-- $Id$ -->
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews<html>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews<head>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<title>Chapter�6.�BIND 9 Configuration Reference</title>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
e20309353e6246485c521278131d3fced73d7957Tinderbox User<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<link rel="prev" href="Bv9ARM.ch05.html" title="Chapter�5.�The BIND 9 Lightweight Resolver">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<link rel="next" href="Bv9ARM.ch07.html" title="Chapter�7.�BIND 9 Security Considerations">
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</head>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<div class="navheader">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<table width="100%" summary="Navigation header">
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<tr><th colspan="3" align="center">Chapter�6.�<acronym class="acronym">BIND</acronym> 9 Configuration Reference</th></tr>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td width="20%" align="left">
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<a accesskey="p" href="Bv9ARM.ch05.html">Prev</a>�</td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<th width="60%" align="center">�</th>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch07.html">Next</a>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</table>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<hr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</div>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<div class="chapter" lang="en">
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<div class="titlepage"><div><div><h2 class="title">
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<a name="Bv9ARM.ch06"></a>Chapter�6.�<acronym class="acronym">BIND</acronym> 9 Configuration Reference</h2></div></div></div>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<div class="toc">
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<p><b>Table of Contents</b></p>
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<dl>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect1"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
24934f08b9ff81c2be711e566e8002d145573031Tinderbox User<dd><dl>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2573300">Comment Syntax</a></span></dt>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User</dl></dd>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<dt><span class="sect1"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<dd><dl>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574165"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#acl"><span><strong class="command">acl</strong></span> Statement Definition and
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater Usage</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574423"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574782"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574800"><span><strong class="command">include</strong></span> Statement Definition and
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574891"><span><strong class="command">key</strong></span> Statement Grammar</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2574915"><span><strong class="command">key</strong></span> Statement Definition and Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575009"><span><strong class="command">logging</strong></span> Statement Grammar</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2575144"><span><strong class="command">logging</strong></span> Statement Definition and
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577350"><span><strong class="command">lwres</strong></span> Statement Grammar</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577447"><span><strong class="command">lwres</strong></span> Statement Definition and Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577611"><span><strong class="command">masters</strong></span> Statement Grammar</a></span></dt>
eabc9c3c07cd956d3c436bd7614cb162dabdda76Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577660"><span><strong class="command">masters</strong></span> Statement Definition and
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2577682"><span><strong class="command">options</strong></span> Statement Grammar</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#options"><span><strong class="command">options</strong></span> Statement Definition and
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Usage</a></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Usage</a></span></dt>
24934f08b9ff81c2be711e566e8002d145573031Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#statschannels"><span><strong class="command">statistics-channels</strong></span> Statement Grammar</a></span></dt>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593078"><span><strong class="command">statistics-channels</strong></span> Statement Definition and
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Usage</a></span></dt>
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#trusted-keys"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593580"><span><strong class="command">trusted-keys</strong></span> Statement Definition
ad411d8ccf8a27eb903b842ab507ba6729d0246bTinderbox User and Usage</a></span></dt>
80faf1588895fd26490f82f95a7a1b771df1c324Automatic Updater<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2593634"><span><strong class="command">managed-keys</strong></span> Statement Grammar</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#managed-keys"><span><strong class="command">managed-keys</strong></span> Statement Definition
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User and Usage</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark 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>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2594001"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Statement Grammar</a></span></dt>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2596017"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson</dl></dd>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2599724">Zone File</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dd><dl>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<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>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2602642">Discussion of MX Records</a></span></dt>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603325">Inverse Mapping in IPv4</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603589">Other Zone File Directives</a></span></dt>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2603794"><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</dl></dd>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<dt><span class="sect1"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch06.html#statistics_counters">Statistics Counters</a></span></dt></dl></dd>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</dl>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <acronym class="acronym">BIND</acronym> 9 configuration is broadly similar
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson to <acronym class="acronym">BIND</acronym> 8; however, there are a few new
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User areas
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews of configuration, such as views. <acronym class="acronym">BIND</acronym>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User 8 configuration files should work with few alterations in <acronym class="acronym">BIND</acronym>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews 9, although more complex configurations should be reviewed to check
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews if they can be more efficiently implemented using the new features
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews found in <acronym class="acronym">BIND</acronym> 9.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User <acronym class="acronym">BIND</acronym> 4 configuration files can be
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews converted to the new format
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews using the shell script
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User <code class="filename">contrib/named-bootconf/named-bootconf.sh</code>.
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User </p>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<div class="sect1" lang="en">
2a31bd531072824ef252c18303859d6af7451b00Francis Dupont<div class="titlepage"><div><div><h2 class="title" style="clear: both">
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<a name="configuration_file_elements"></a>Configuration File Elements</h2></div></div></div>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
2a31bd531072824ef252c18303859d6af7451b00Francis Dupont Following is a list of elements used throughout the <acronym class="acronym">BIND</acronym> configuration
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews file documentation:
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<div class="informaltable"><table border="1">
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<colgroup>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<col>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<col>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</colgroup>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<tbody>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews <code class="varname">acl_name</code>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
e20788e1216ed720aefa84f3295f7899d9f28c22Mark Andrews The name of an <code class="varname">address_match_list</code> as
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews defined by the <span><strong class="command">acl</strong></span> statement.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
01a5c5503482fb3ba52088bf0178a7213273bf96Mark Andrews </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User</tr>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User<tr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">address_match_list</code>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater <p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User A list of one or more
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">ip_addr</code>,
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <code class="varname">ip_prefix</code>, <code class="varname">key_id</code>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews or <code class="varname">acl_name</code> elements, see
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called &#8220;Address Match Lists&#8221;</a>.
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User </p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <p>
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater <code class="varname">masters_list</code>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User A named list of one or more <code class="varname">ip_addr</code>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson with optional <code class="varname">key_id</code> and/or
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <code class="varname">ip_port</code>.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews A <code class="varname">masters_list</code> may include other
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <code class="varname">masters_lists</code>.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </td>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater</tr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">domain_name</code>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </p>
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User A quoted string which will be used as
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews a DNS name, for example "<code class="literal">my.test.domain</code>".
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <code class="varname">namelist</code>
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User </p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews A list of one or more <code class="varname">domain_name</code>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User elements.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </td>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews</tr>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews<tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User <code class="varname">dotted_decimal</code>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<td>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews <p>
7ca715ad1587a68a531ea1cdea07515d7232567eTinderbox User One to four integers valued 0 through
269519eeb959d905ed125f96426e01d725c3b597Tinderbox User 255 separated by dots (`.'), such as <span><strong class="command">123</strong></span>,
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater <span><strong class="command">45.67</strong></span> or <span><strong class="command">89.123.45.67</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </td>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews</tr>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User<tr>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <code class="varname">ip4_addr</code>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
bc0a53583d92309bebcf93c408e2f3247ebd3d3cAutomatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater An IPv4 address with exactly four elements
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in <code class="varname">dotted_decimal</code> notation.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User<td>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="varname">ip6_addr</code>
19b3dc94bce93fa76bd7e066f9298630dbc9dcb4Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<td>
7f94d9a8162c9a96b56e66176702b66e79d8e1a2Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater An IPv6 address, such as <span><strong class="command">2001:db8::1234</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv6 scoped addresses that have ambiguity on their
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater scope zones must be disambiguated by an appropriate
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User zone ID with the percent character (`%') as
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews delimiter. It is strongly recommended to use
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User string zone names rather than numeric identifiers,
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User in order to be robust against system configuration
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User changes. However, since there is no standard
96ea71632887c58a9d00f47eb318bf76b35903c3Mark Andrews mapping for such names and identifier values,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater currently only interface names as link identifiers
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater are supported, assuming one-to-one mapping between
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User interfaces and links. For example, a link-local
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User address <span><strong class="command">fe80::1</strong></span> on the link
4cda4fd158d6ded5586bacea8c388445d99611eaAutomatic Updater attached to the interface <span><strong class="command">ne0</strong></span>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews can be specified as <span><strong class="command">fe80::1%ne0</strong></span>.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews Note that on most systems link-local addresses
80faf1588895fd26490f82f95a7a1b771df1c324Automatic Updater always have the ambiguity, and need to be
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews disambiguated.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User </td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</tr>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<tr>
bf5e2127e92e52cbf661e77dd6a76e5aef43542fTinderbox User<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <code class="varname">ip_addr</code>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater An <code class="varname">ip4_addr</code> or <code class="varname">ip6_addr</code>.
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User<td>
cf7e98f59148b559946a7f1ca728471374f1eef3Automatic Updater <p>
0ea1646bf1253f50946ed5e4d3c01c1d2767012bTinderbox User <code class="varname">ip_dscp</code>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews </p>
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
cf7e98f59148b559946a7f1ca728471374f1eef3Automatic Updater <p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews A <code class="varname">number</code> between 0 and 63, used
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson to select a differentiated services code point (DSCP)
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews value for use with outgoing traffic on operating systems
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews that support DSCP.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <code class="varname">ip_port</code>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
3857cb6fcabeb79d85de4b3e3e4ab99912b701f8Mark Andrews </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews An IP port <code class="varname">number</code>.
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User The <code class="varname">number</code> is limited to 0
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson through 65535, with values
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User below 1024 typically restricted to use by processes running
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews as root.
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User In some cases, an asterisk (`*') character can be used as a
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews placeholder to
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews select a random high-numbered port.
8292deab031e7599cd7622aa7675fbe139ca6095Mark Andrews </p>
e31cfd80616deb9781902306b34a69aa7309b6cbTinderbox User </td>
7ac34650fa344f42211d6da744ae486b0145a083Tinderbox User</tr>
7ac34650fa344f42211d6da744ae486b0145a083Tinderbox User<tr>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <code class="varname">ip_prefix</code>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews An IP network specified as an <code class="varname">ip_addr</code>,
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews followed by a slash (`/') and then the number of bits in the
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews netmask.
7d12a6b412fe47e6d6582923fd6954ab8cd0baebAutomatic Updater Trailing zeros in a <code class="varname">ip_addr</code>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews may omitted.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews For example, <span><strong class="command">127/8</strong></span> is the
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews network <span><strong class="command">127.0.0.0</strong></span> with
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews netmask <span><strong class="command">255.0.0.0</strong></span> and <span><strong class="command">1.2.3.0/28</strong></span> is
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews network <span><strong class="command">1.2.3.0</strong></span> with netmask <span><strong class="command">255.255.255.240</strong></span>.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater <p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews When specifying a prefix involving a IPv6 scoped address
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews the scope may be omitted. In that case the prefix will
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews match packets from any scope.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">key_id</code>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews A <code class="varname">domain_name</code> representing
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews the name of a shared key, to be used for transaction
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews security.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <code class="varname">key_list</code>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </p>
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User </td>
01a5c5503482fb3ba52088bf0178a7213273bf96Mark Andrews<td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <p>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User A list of one or more
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User <code class="varname">key_id</code>s,
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User separated by semicolons and ending with a semicolon.
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <code class="varname">number</code>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User A non-negative 32-bit integer
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews (i.e., a number between 0 and 4294967295, inclusive).
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Its acceptable value might further
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater be limited by the context in which it is used.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">path_name</code>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User 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>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">port_list</code>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User A list of an <code class="varname">ip_port</code> or a port
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User range.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews A port range is specified in the form of
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews <strong class="userinput"><code>range</code></strong> followed by
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews two <code class="varname">ip_port</code>s,
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews <code class="varname">port_low</code> and
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews <code class="varname">port_high</code>, which represents
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews port numbers from <code class="varname">port_low</code> through
f7369b2881b5e63d69600adcedc8ba938303d30cTinderbox User <code class="varname">port_high</code>, inclusive.
f7369b2881b5e63d69600adcedc8ba938303d30cTinderbox User <code class="varname">port_low</code> must not be larger than
d6317350b1180aa4517f2e8a92fa8fbcbf904ad8Automatic Updater <code class="varname">port_high</code>.
bc0a4c01beede169df81a3ee5b614ed9e82339dbAutomatic Updater For example,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <strong class="userinput"><code>range 1024 65535</code></strong> represents
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington ports from 1024 through 65535.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington In either case an asterisk (`*') character is not
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington allowed as a valid <code class="varname">ip_port</code>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">size_spec</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington A 64-bit unsigned integer, or the keywords
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>unlimited</code></strong> or
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>default</code></strong>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Integers may take values
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington 0 &lt;= value &lt;= 18446744073709551615, though
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington certain parameters
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington (such as <span><strong class="command">max-journal-size</strong></span>) may
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington use a more limited range within these extremes.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington In most cases, setting a value to 0 does not
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington literally mean zero; it means "undefined" or
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington "as big as possible", depending on the context.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington See the explanations of particular parameters
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington that use <code class="varname">size_spec</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington for details on how they interpret its use.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Numeric values can optionally be followed by a
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington scaling factor:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>K</code></strong> or <strong class="userinput"><code>k</code></strong>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington for kilobytes,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>M</code></strong> or <strong class="userinput"><code>m</code></strong>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington for megabytes, and
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <strong class="userinput"><code>G</code></strong> or <strong class="userinput"><code>g</code></strong>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington for gigabytes, which scale by 1024, 1024*1024, and
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington 1024*1024*1024 respectively.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">unlimited</code> generally means
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington "as big as possible", and is usually the best
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington way to safely set a very large number.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">default</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington uses the limit that was in force when the server was started.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">yes_or_no</code>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User </p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater Either <strong class="userinput"><code>yes</code></strong> or <strong class="userinput"><code>no</code></strong>.
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater The words <strong class="userinput"><code>true</code></strong> and <strong class="userinput"><code>false</code></strong> are
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater also accepted, as are the numbers <strong class="userinput"><code>1</code></strong>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User and <strong class="userinput"><code>0</code></strong>.
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater</tr>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<tr>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <code class="varname">dialup_option</code>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <p>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User One of <strong class="userinput"><code>yes</code></strong>,
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <strong class="userinput"><code>no</code></strong>, <strong class="userinput"><code>notify</code></strong>,
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <strong class="userinput"><code>notify-passive</code></strong>, <strong class="userinput"><code>refresh</code></strong> or
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <strong class="userinput"><code>passive</code></strong>.
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User When used in a zone, <strong class="userinput"><code>notify-passive</code></strong>,
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <strong class="userinput"><code>refresh</code></strong>, and <strong class="userinput"><code>passive</code></strong>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User are restricted to slave and stub zones.
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</tbody>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</table></div>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<div class="sect2" lang="en">
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<div class="titlepage"><div><div><h3 class="title">
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<a name="address_match_lists"></a>Address Match Lists</h3></div></div></div>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<div class="sect3" lang="en">
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<div class="titlepage"><div><div><h4 class="title">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<a name="id2573131"></a>Syntax</h4></div></div></div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<pre class="programlisting"><code class="varname">address_match_list</code> = address_match_list_element ;
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> address_match_list_element; ... </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<code class="varname">address_match_list_element</code> = [<span class="optional"> ! </span>] (ip_address [<span class="optional">/length</span>] |
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews key key_id | acl_name | { address_match_list } )
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</pre>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect3" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h4 class="title">
febbdb34a7f7759922e239655e7429d78d3a8d26Tinderbox User<a name="id2573159"></a>Definition and Usage</h4></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Address match lists are primarily used to determine access
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User control for various server operations. They are also used in
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews the <span><strong class="command">listen-on</strong></span> and <span><strong class="command">sortlist</strong></span>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews statements. The elements which constitute an address match
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews list can be any of the following:
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="itemizedlist"><ul type="disc">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<li>an IP address (IPv4 or IPv6)</li>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<li>an IP prefix (in `/' notation)</li>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<li>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User a key ID, as defined by the <span><strong class="command">key</strong></span>
c01dec514a81ecf8c17ca3ef8c3ba95e437295ebAutomatic Updater statement
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </li>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<li>the name of an address match list defined with
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the <span><strong class="command">acl</strong></span> statement
e8c42d50cdaf3a3b841074d8bf72b40ffbae2a4bTinderbox User </li>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<li>a nested address match list enclosed in braces</li>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</ul></div>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews Elements can be negated with a leading exclamation mark (`!'),
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington and the match list names "any", "none", "localhost", and
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington "localnets" are predefined. More information on those names
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington can be found in the description of the acl statement.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The addition of the key clause made the name of this syntactic
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington element something of a misnomer, since security keys can be used
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington 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>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews The interpretation of a match depends on whether the list is being
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington used for access control, defining <span><strong class="command">listen-on</strong></span> ports, or in a
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">sortlist</strong></span>, and whether the element was negated.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews When used as an access control list, a non-negated match
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews allows access and a negated match denies access. If
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews there is no match, access is denied. The clauses
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">allow-notify</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">allow-recursion</strong></span>,
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <span><strong class="command">allow-recursion-on</strong></span>,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span><strong class="command">allow-query</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">allow-query-on</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">allow-query-cache</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">allow-query-cache-on</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">allow-transfer</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">allow-update</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">allow-update-forwarding</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">blackhole</strong></span>, and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">keep-response-order</strong></span> all use address match
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater lists. Similarly, the <span><strong class="command">listen-on</strong></span> option will cause the
79cea03ba823e2d3a34895f0ba91d7fb5ad799e7Automatic Updater server to refuse queries on any of the machine's
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews addresses which do not match the list.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews Order of insertion is significant. If more than one element
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington in an ACL is found to match a given IP address or prefix,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington preference will be given to the one that came
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span class="emphasis"><em>first</em></span> in the ACL definition.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington Because of this first-match behavior, an element that
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington defines a subset of another element in the list should
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington come before the broader element, regardless of whether
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington either is negated. For example, in
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">1.2.3/24; ! 1.2.3.13;</strong></span>
b7aab05edae933e169d5f83c653935b17c7f0a8bMark Andrews the 1.2.3.13 element is completely useless because the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington algorithm will match any lookup for 1.2.3.13 to the 1.2.3/24
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington element. Using <span><strong class="command">! 1.2.3.13; 1.2.3/24</strong></span> fixes
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington that problem by having 1.2.3.13 blocked by the negation, but
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User all other 1.2.3.* hosts fall through.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</div>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<div class="sect2" lang="en">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="titlepage"><div><div><h3 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="id2573300"></a>Comment Syntax</h3></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User The <acronym class="acronym">BIND</acronym> 9 comment syntax allows for
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews comments to appear
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews anywhere that whitespace may appear in a <acronym class="acronym">BIND</acronym> configuration
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews file. To appeal to programmers of all kinds, they can be written
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews in the C, C++, or shell/perl style.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="sect3" lang="en">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="titlepage"><div><div><h4 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="id2573383"></a>Syntax</h4></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting">/* This is a <acronym class="acronym">BIND</acronym> comment as in C */</pre>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting">// This is a <acronym class="acronym">BIND</acronym> comment as in C++</pre>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting"># This is a <acronym class="acronym">BIND</acronym> comment as in common UNIX shells
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews# and perl</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect3" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h4 class="title">
56effd2e3f579fd77b1fb37d47871d1bf1286bc4Automatic Updater<a name="id2573413"></a>Definition and Usage</h4></div></div></div>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
0e91f17da8a29086876a88962e0a3482094b6057Evan Hunt Comments may appear anywhere that whitespace may appear in
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews a <acronym class="acronym">BIND</acronym> configuration file.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews C-style comments start with the two characters /* (slash,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews star) and end with */ (star, slash). Because they are completely
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews delimited with these characters, they can be used to comment only
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews a portion of a line or to span multiple lines.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews C-style comments cannot be nested. For example, the following
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews is not valid because the entire comment ends with the first */:
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews
42bee07ebb8152a6ec2f87f4790d87368c24704cAutomatic Updater</p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">/* This is the start of a comment.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This is still part of the comment.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews/* This is an incorrect attempt at nesting a comment. */
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington This is no longer in any comment. */
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews</pre>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews C++-style comments start with the two characters // (slash,
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews slash) and continue to the end of the physical line. They cannot
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews be continued across multiple physical lines; to have one logical
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews comment span multiple lines, each line must use the // pair.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington For example:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting">// This is the start of a comment. The next line
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington// is a new comment, even though it is logically
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington// part of the previous comment.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</pre>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Shell-style (or perl-style, if you prefer) comments start
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews with the character <code class="literal">#</code> (number sign)
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews and continue to the end of the
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews physical line, as in C++ comments.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews For example:
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
89623368b8f662d458d9964b923050f33c5f75b0Tinderbox User<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<pre class="programlisting"># This is the start of a comment. The next line
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User# is a new comment, even though it is logically
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews# part of the previous comment.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews</pre>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="warning" style="margin-left: 0.5in; margin-right: 0.5in;">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<h3 class="title">Warning</h3>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews You cannot use the semicolon (`;') character
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to start a comment such as you would in a zone file. The
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User semicolon indicates the end of a configuration
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User statement.
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="sect1" lang="en">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="titlepage"><div><div><h2 class="title" style="clear: both">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<a name="Configuration_File_Grammar"></a>Configuration File Grammar</h2></div></div></div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews A <acronym class="acronym">BIND</acronym> 9 configuration consists of
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User statements and comments.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Statements end with a semicolon. Statements and comments are the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User only elements that can appear without enclosing braces. Many
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User statements contain a block of sub-statements, which are also
cc5a9ce75af9870f2cb9e2bf00548c2f7e6398d6Automatic Updater terminated with a semicolon.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User<p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews The following statements are supported:
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="informaltable"><table border="1">
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater<colgroup>
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater<col>
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater<col>
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater</colgroup>
91faa748a27dee38f6caea461d3e87f15b93abeaTinderbox User<tbody>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
91faa748a27dee38f6caea461d3e87f15b93abeaTinderbox User<td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <p><span><strong class="command">acl</strong></span></p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews defines a named IP address
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews matching list, for access control and other uses.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews</tr>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<tr>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<td>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User <p><span><strong class="command">controls</strong></span></p>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User </td>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User<td>
861836e5f5df62bfaea9ad8923a05278d5ab2f3dTinderbox User <p>
e8c17c74535be290abaaa160a434ed80bf0ad2feMark Andrews declares control channels to be used
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User by the <span><strong class="command">rndc</strong></span> utility.
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater </p>
9c446b72069d0ab9f710502f4d7048e50875fccbAutomatic Updater </td>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater</tr>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater<tr>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User<td>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User <p><span><strong class="command">include</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater includes a file.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p><span><strong class="command">key</strong></span></p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater specifies key information for use in
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater authentication and authorization using TSIG.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p><span><strong class="command">logging</strong></span></p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater specifies what the server logs, and where
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater the log messages are sent.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p><span><strong class="command">lwres</strong></span></p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater configures <span><strong class="command">named</strong></span> to
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater also act as a light-weight resolver daemon (<span><strong class="command">lwresd</strong></span>).
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User <p><span><strong class="command">masters</strong></span></p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User defines a named masters list for
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User inclusion in stub and slave zones'
fe84edc17e0d582cf7b4270f8df9d4742a107b1cAutomatic Updater <span><strong class="command">masters</strong></span> or
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <span><strong class="command">also-notify</strong></span> lists.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater</tr>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews<tr>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews<td>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews <p><span><strong class="command">options</strong></span></p>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews </td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater <p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater controls global server configuration
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater options and sets defaults for other statements.
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</tr>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<td>
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User <p><span><strong class="command">server</strong></span></p>
4ea3649f028ea6a1e42377082a7ccf8f789fb950Automatic Updater </td>
40072ce70bc4125329addb4aaa56d18a1230bc17Automatic Updater<td>
60d5d17479b47c03b9c7c86f54269718103750b8Automatic Updater <p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater sets certain configuration options on
3040b455151b1e1173193933664b2891b6159f24Mark Andrews a per-server basis.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
60d5d17479b47c03b9c7c86f54269718103750b8Automatic Updater </td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater</tr>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater <p><span><strong class="command">statistics-channels</strong></span></p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater <p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater declares communication channels to get access to
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater <span><strong class="command">named</strong></span> statistics.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater</tr>
19dbf2e20df03f2b81ed1f347e27718084374059Automatic Updater<tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater <p><span><strong class="command">trusted-keys</strong></span></p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater<td>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater <p>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater defines trusted DNSSEC keys.
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater </p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p><span><strong class="command">managed-keys</strong></span></p>
7dd02af3c9350553e1d52d980a7812425b3f1295Automatic Updater </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington lists DNSSEC keys to be kept up to date
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington using RFC 5011 trust anchor maintenance.
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews </p>
01f91b9cd440833f66e7476e43659655cb52ad10Automatic Updater </td>
3e5b24a74c03d5b52f32d138e64e427bd2cbc8f3Automatic Updater</tr>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<tr>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<td>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User <p><span><strong class="command">view</strong></span></p>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User </td>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User<td>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User <p>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User defines a view.
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </td>
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews</tr>
aa49af836ce7a7a2888f5cedf4cbb14ff4dc1d11Mark Andrews<tr>
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews<td>
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews <p><span><strong class="command">zone</strong></span></p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </td>
f6ba5791728d244650c1887d8dd8ed771fd50a1dMark Andrews<td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <p>
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews defines a zone.
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews </p>
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews </td>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews</tr>
08a1e53c738c425390557196a2ba5039e5afd364Mark Andrews</tbody>
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews</table></div>
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews<p>
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews The <span><strong class="command">logging</strong></span> and
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <span><strong class="command">options</strong></span> statements may only occur once
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews per
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews configuration.
f6ba5791728d244650c1887d8dd8ed771fd50a1dMark Andrews </p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<div class="sect2" lang="en">
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<div class="titlepage"><div><div><h3 class="title">
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<a name="id2574165"></a><span><strong class="command">acl</strong></span> Statement Grammar</h3></div></div></div>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<pre class="programlisting"><span><strong class="command">acl</strong></span> acl-name {
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt address_match_list
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt};
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt</pre>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt</div>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<div class="sect2" lang="en">
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<div class="titlepage"><div><div><h3 class="title">
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<a name="acl"></a><span><strong class="command">acl</strong></span> Statement Definition and
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User Usage</h3></div></div></div>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<p>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt The <span><strong class="command">acl</strong></span> statement assigns a symbolic
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt name to an address match list. It gets its name from a primary
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt use of address match lists: Access Control Lists (ACLs).
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The following ACLs are built-in:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="informaltable"><table border="1">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<colgroup>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<col>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<col>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</colgroup>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<tbody>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">any</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<td>
e20309353e6246485c521278131d3fced73d7957Tinderbox User <p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User Matches all hosts.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
ff62ab3c2e6274f19190ded15548c723d38bbbe3Automatic Updater </td>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User</tr>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<tr>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">none</strong></span></p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User Matches no hosts.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews</tr>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<tr>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <p><span><strong class="command">localhost</strong></span></p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews Matches the IPv4 and IPv6 addresses of all network
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews interfaces on the system. When addresses are
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews added or removed, the <span><strong class="command">localhost</strong></span>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews ACL element is updated to reflect the changes.
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews</tr>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<tr>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p><span><strong class="command">localnets</strong></span></p>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt </td>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User<td>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Matches any host on an IPv4 or IPv6 network
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User for which the system has an interface.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User When addresses are added or removed,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the <span><strong class="command">localnets</strong></span>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User ACL element is updated to reflect the changes.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Some systems do not provide a way to determine the prefix
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater lengths of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater local IPv6 addresses.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater In such a case, <span><strong class="command">localnets</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater only matches the local
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv6 addresses, just like <span><strong class="command">localhost</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</tr>
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User</tbody>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</table></div>
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater</div>
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<a name="id2574423"></a><span><strong class="command">controls</strong></span> Statement Grammar</h3></div></div></div>
88d58d79c5bc7ce3c20a42461a5070116c736836Automatic Updater<pre class="programlisting"><span><strong class="command">controls</strong></span> {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [ inet ( ip_addr | * ) [ port ip_port ]
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater allow { <em class="replaceable"><code> address_match_list </code></em> }
3040b455151b1e1173193933664b2891b6159f24Mark Andrews keys { <em class="replaceable"><code>key_list</code></em> }; ]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [ inet ...; ]
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater [ 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>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater keys { <em class="replaceable"><code>key_list</code></em> }; ]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [ unix ...; ]
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater};
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="controls_statement_definition_and_usage"></a><span><strong class="command">controls</strong></span> Statement Definition and
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User Usage</h3></div></div></div>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<p>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater The <span><strong class="command">controls</strong></span> statement declares control
9fa39c73fc1d8bc44fdbbb79a1d26b837e7dd555Mark Andrews channels to be used by system administrators to control the
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater operation of the name server. These control channels are
3040b455151b1e1173193933664b2891b6159f24Mark Andrews used by the <span><strong class="command">rndc</strong></span> utility to send
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt commands to and retrieve non-DNS results from a name server.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews An <span><strong class="command">inet</strong></span> control channel is a TCP socket
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater listening at the specified <span><strong class="command">ip_port</strong></span> on the
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater specified <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater address. An <span><strong class="command">ip_addr</strong></span> of <code class="literal">*</code> (asterisk) is
3040b455151b1e1173193933664b2891b6159f24Mark Andrews interpreted as the IPv4 wildcard address; connections will be
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User accepted on any of the system's IPv4 addresses.
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt To listen on the IPv6 wildcard address,
3040b455151b1e1173193933664b2891b6159f24Mark Andrews use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User If you will only use <span><strong class="command">rndc</strong></span> on the local host,
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User using the loopback address (<code class="literal">127.0.0.1</code>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User or <code class="literal">::1</code>) is recommended for maximum security.
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews </p>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews<p>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews If no port is specified, port 953 is used. The asterisk
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews "<code class="literal">*</code>" cannot be used for <span><strong class="command">ip_port</strong></span>.
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
560d6da48f066000541dd43f5d407644dee12bebTinderbox User The ability to issue commands over the control channel is
7addb3e8b5cf6e0c4df0e3cb8135aa71269f0261Tinderbox User restricted by the <span><strong class="command">allow</strong></span> and
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <span><strong class="command">keys</strong></span> clauses.
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater Connections to the control channel are permitted based on the
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User <span><strong class="command">address_match_list</strong></span>. This is for simple
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater IP address based filtering only; any <span><strong class="command">key_id</strong></span>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User elements of the <span><strong class="command">address_match_list</strong></span>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User are ignored.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<p>
90b25b84f037ec923efaee84d2c0dc599293d04eTinderbox User A <span><strong class="command">unix</strong></span> control channel is a UNIX domain
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews socket listening at the specified path in the file system.
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews Access to the socket is specified by the <span><strong class="command">perm</strong></span>,
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews <span><strong class="command">owner</strong></span> and <span><strong class="command">group</strong></span> clauses.
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews Note on some platforms (SunOS and Solaris) the permissions
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews (<span><strong class="command">perm</strong></span>) are applied to the parent directory
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews as the permissions on the socket itself are ignored.
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews </p>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<p>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews The primary authorization mechanism of the command
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User channel is the <span><strong class="command">key_list</strong></span>, which
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont contains a list of <span><strong class="command">key_id</strong></span>s.
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont Each <span><strong class="command">key_id</strong></span> in the <span><strong class="command">key_list</strong></span>
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont is authorized to execute commands over the control channel.
4dca64bb8991502db368028aeeba2f832d3b971dAutomatic Updater 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>)
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont for information about configuring keys in <span><strong class="command">rndc</strong></span>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater If no <span><strong class="command">controls</strong></span> statement is present,
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater <span><strong class="command">named</strong></span> will set up a default
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater control channel listening on the loopback address 127.0.0.1
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater and its IPv6 counterpart ::1.
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater In this case, and also when the <span><strong class="command">controls</strong></span> statement
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater is present but does not have a <span><strong class="command">keys</strong></span> clause,
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User <span><strong class="command">named</strong></span> will attempt to load the command channel key
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User from the file <code class="filename">rndc.key</code> in
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User <code class="filename">/etc</code> (or whatever <code class="varname">sysconfdir</code>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater was specified as when <acronym class="acronym">BIND</acronym> was built).
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater To create a <code class="filename">rndc.key</code> file, run
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater <strong class="userinput"><code>rndc-confgen -a</code></strong>.
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater </p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<p>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User The <code class="filename">rndc.key</code> feature was created to
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater ease the transition of systems from <acronym class="acronym">BIND</acronym> 8,
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater which did not have digital signatures on its command channel
3040b455151b1e1173193933664b2891b6159f24Mark Andrews messages and thus did not have a <span><strong class="command">keys</strong></span> clause.
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User It makes it possible to use an existing <acronym class="acronym">BIND</acronym> 8
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt configuration file in <acronym class="acronym">BIND</acronym> 9 unchanged,
3040b455151b1e1173193933664b2891b6159f24Mark Andrews and still have <span><strong class="command">rndc</strong></span> work the same way
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User <span><strong class="command">ndc</strong></span> worked in BIND 8, simply by executing the
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater command <strong class="userinput"><code>rndc-confgen -a</code></strong> after BIND 9 is
3040b455151b1e1173193933664b2891b6159f24Mark Andrews installed.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User Since the <code class="filename">rndc.key</code> feature
3040b455151b1e1173193933664b2891b6159f24Mark Andrews is only intended to allow the backward-compatible usage of
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <acronym class="acronym">BIND</acronym> 8 configuration files, this
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater feature does not
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater have a high degree of configurability. You cannot easily change
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater the key name or the size of the secret, so you should make a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">rndc.conf</code> with your own key if you
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater wish to change
50fa300826799727204b93cbe63bebc341c5eadeTinderbox User those things. The <code class="filename">rndc.key</code> file
50fa300826799727204b93cbe63bebc341c5eadeTinderbox User also has its
da82e232161d67b77df2d67898bdac693f647be1Automatic Updater permissions set such that only the owner of the file (the user that
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">named</strong></span> is running as) can access it.
2da2220fe7af2c45724b50b0187523b1fab0cf08Rob Austein If you
3040b455151b1e1173193933664b2891b6159f24Mark Andrews desire greater flexibility in allowing other users to access
e171a4137c6ba348957e61b7c4c3541493c0da02Automatic Updater <span><strong class="command">rndc</strong></span> commands, then you need to create
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater a
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater <code class="filename">rndc.conf</code> file and make it group
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater readable by a group
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater that contains the users who should have access.
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User </p>
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User<p>
b3386fba31414344f38f0c30849c056dceb22dceTinderbox User To disable the command channel, use an empty
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <span><strong class="command">controls</strong></span> statement:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">controls { };</strong></span>.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect2" lang="en">
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<div class="titlepage"><div><div><h3 class="title">
af9cf290cea6ada6ce27b51c724ab77ad5d73fa0Tinderbox User<a name="id2574782"></a><span><strong class="command">include</strong></span> Statement Grammar</h3></div></div></div>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<pre class="programlisting"><span><strong class="command">include</strong></span> <em class="replaceable"><code>filename</code></em>;</pre>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</div>
6671e343b8c7e44ac10a7900fde59555fbc71571Automatic Updater<div class="sect2" lang="en">
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<div class="titlepage"><div><div><h3 class="title">
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<a name="id2574800"></a><span><strong class="command">include</strong></span> Statement Definition and
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater Usage</h3></div></div></div>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater The <span><strong class="command">include</strong></span> statement inserts the
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater specified file at the point where the <span><strong class="command">include</strong></span>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater statement is encountered. The <span><strong class="command">include</strong></span>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater statement facilitates the administration of configuration
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User files
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater by permitting the reading or writing of some things but not
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater others. For example, the statement could include private keys
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater that are readable only by the name server.
50fa300826799727204b93cbe63bebc341c5eadeTinderbox User </p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</div>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<div class="sect2" lang="en">
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<div class="titlepage"><div><div><h3 class="title">
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<a name="id2574891"></a><span><strong class="command">key</strong></span> Statement Grammar</h3></div></div></div>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<pre class="programlisting"><span><strong class="command">key</strong></span> <em class="replaceable"><code>key_id</code></em> {
3040b455151b1e1173193933664b2891b6159f24Mark Andrews algorithm <em class="replaceable"><code>algorithm_id</code></em>;
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater secret <em class="replaceable"><code>secret_string</code></em>;
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater};
664917bedafa65dee4349c84324a31731aa1e228Francis Dupont</pre>
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater</div>
af9cf290cea6ada6ce27b51c724ab77ad5d73fa0Tinderbox User<div class="sect2" lang="en">
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<div class="titlepage"><div><div><h3 class="title">
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<a name="id2574915"></a><span><strong class="command">key</strong></span> Statement Definition and Usage</h3></div></div></div>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<p>
50fa300826799727204b93cbe63bebc341c5eadeTinderbox User The <span><strong class="command">key</strong></span> statement defines a shared
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater secret key for use with TSIG (see <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called &#8220;TSIG&#8221;</a>)
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater or the command channel
e20309353e6246485c521278131d3fced73d7957Tinderbox User (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
e20309353e6246485c521278131d3fced73d7957Tinderbox User Usage">the section called &#8220;<span><strong class="command">controls</strong></span> Statement Definition and
e20309353e6246485c521278131d3fced73d7957Tinderbox User Usage&#8221;</a>).
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater<p>
f8a9a38ee40c139a8d145ac76ecbff3a0f986453Mark Andrews The <span><strong class="command">key</strong></span> statement can occur at the
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater top level
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews of the configuration file or inside a <span><strong class="command">view</strong></span>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews statement. Keys defined in top-level <span><strong class="command">key</strong></span>
9d80d23172c30fd63e5046a7e69b8445e564ff31Automatic Updater statements can be used in all views. Keys intended for use in
1f4c645185bd8fc70048e0a69eee46193a284e5cTinderbox User a <span><strong class="command">controls</strong></span> statement
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews (see <a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews Usage">the section called &#8220;<span><strong class="command">controls</strong></span> Statement Definition and
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews Usage&#8221;</a>)
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews must be defined at the top level.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews The <em class="replaceable"><code>key_id</code></em>, also known as the
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews key name, is a domain name uniquely identifying the key. It can
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews be used in a <span><strong class="command">server</strong></span>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews statement to cause requests sent to that
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews server to be signed with this key, or in address match lists to
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews verify that incoming requests have been signed with a key
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews matching this name, algorithm, and secret.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews The <em class="replaceable"><code>algorithm_id</code></em> is a string
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews that specifies a security/authentication algorithm. The
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <span><strong class="command">named</strong></span> server supports <code class="literal">hmac-md5</code>,
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>,
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User and <code class="literal">hmac-sha512</code> TSIG authentication.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews Truncated hashes are supported by appending the minimum
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User number of required bits preceded by a dash, e.g.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User <code class="literal">hmac-sha1-80</code>. The
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <em class="replaceable"><code>secret_string</code></em> is the secret
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User to be used by the algorithm, and is treated as a base-64
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User encoded string.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</div>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User<div class="sect2" lang="en">
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User<div class="titlepage"><div><div><h3 class="title">
61932ed91732417e05c8c6fd335acf1be896c778Mark Andrews<a name="id2575009"></a><span><strong class="command">logging</strong></span> Statement Grammar</h3></div></div></div>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<pre class="programlisting"><span><strong class="command">logging</strong></span> {
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User [ <span><strong class="command">channel</strong></span> <em class="replaceable"><code>channel_name</code></em> {
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User ( <span><strong class="command">file</strong></span> <em class="replaceable"><code>path_name</code></em>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews [ <span><strong class="command">versions</strong></span> ( <em class="replaceable"><code>number</code></em> | <span><strong class="command">unlimited</strong></span> ) ]
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User [ <span><strong class="command">size</strong></span> <em class="replaceable"><code>size_spec</code></em> ]
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User | <span><strong class="command">syslog</strong></span> <em class="replaceable"><code>syslog_facility</code></em>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews | <span><strong class="command">stderr</strong></span>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User | <span><strong class="command">null</strong></span> );
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [ <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> |
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <code class="option">info</code> | <code class="option">debug</code> [ <em class="replaceable"><code>level</code></em> ] | <code class="option">dynamic</code> ); ]
e80c7005e3d59dfeb04dad186d36f3c15622954cTinderbox User [ <span><strong class="command">print-category</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews [ <span><strong class="command">print-severity</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews [ <span><strong class="command">print-time</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews [ <span><strong class="command">buffered</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews }; ]
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews [ <span><strong class="command">category</strong></span> <em class="replaceable"><code>category_name</code></em> {
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews <em class="replaceable"><code>channel_name</code></em> ; [ <em class="replaceable"><code>channel_name</code></em> ; ... ]
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews }; ]
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews ...
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User};
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</pre>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</div>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<div class="sect2" lang="en">
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<div class="titlepage"><div><div><h3 class="title">
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<a name="id2575144"></a><span><strong class="command">logging</strong></span> Statement Definition and
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews Usage</h3></div></div></div>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews The <span><strong class="command">logging</strong></span> statement configures a
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews wide
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews variety of logging options for the name server. Its <span><strong class="command">channel</strong></span> phrase
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews associates output methods, format options and severity levels with
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews a name that can then be used with the <span><strong class="command">category</strong></span> phrase
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews to select how various classes of messages are logged.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews Only one <span><strong class="command">logging</strong></span> statement is used to
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User define
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User as many channels and categories as are wanted. If there is no <span><strong class="command">logging</strong></span> statement,
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User the logging configuration will be:
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<pre class="programlisting">logging {
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater category default { default_syslog; default_debug; };
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater category unmatched { null; };
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews};
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</pre>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<p>
8c9c79e5fea0cb698026a74821695907c8312a46Mark Andrews If <span><strong class="command">named</strong></span> is started with the
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <code class="option">-L</code> option, it logs to the specified file
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User at startup, instead of using syslog. In this case the logging
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User configuration will be:
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater<pre class="programlisting">logging {
3040b455151b1e1173193933664b2891b6159f24Mark Andrews category default { default_logfile; default_debug; };
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater category unmatched { null; };
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater};
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</pre>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<p>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater In <acronym class="acronym">BIND</acronym> 9, the logging configuration
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews is only established when
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews the entire configuration file has been parsed. In <acronym class="acronym">BIND</acronym> 8, it was
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews established as soon as the <span><strong class="command">logging</strong></span>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews statement
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews was parsed. When the server is starting up, all logging messages
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews regarding syntax errors in the configuration file go to the default
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews channels, or to standard error if the <code class="option">-g</code> option
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews was specified.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="sect3" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h4 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="id2575209"></a>The <span><strong class="command">channel</strong></span> Phrase</h4></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
166c467a9414778bdd0f2a1e4a32220843c0fde3Tinderbox User All log output goes to one or more <span class="emphasis"><em>channels</em></span>;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater you can make as many of them as you want.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
166c467a9414778bdd0f2a1e4a32220843c0fde3Tinderbox User Every channel definition must include a destination clause that
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater says whether messages selected for the channel go to a file, to a
e007e3e5b0316c6c05698a71101885743aca22bdAutomatic Updater particular syslog facility, to the standard error stream, or are
e007e3e5b0316c6c05698a71101885743aca22bdAutomatic Updater discarded. It can optionally also limit the message severity level
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews that will be accepted by the channel (the default is
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <span><strong class="command">info</strong></span>), and whether to include a
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews <span><strong class="command">named</strong></span>-generated time stamp, the
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews category name
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User and/or severity level (the default is not to include any).
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The <span><strong class="command">null</strong></span> destination clause
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews causes all messages sent to the channel to be discarded;
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews in that case, other options for the channel are meaningless.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The <span><strong class="command">file</strong></span> destination clause directs
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews the channel
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews to a disk file. It can include limitations
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews both on how large the file is allowed to become, and how many
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews versions
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews of the file will be saved each time the file is opened.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews If you use the <span><strong class="command">versions</strong></span> log file
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews option, then
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews <span><strong class="command">named</strong></span> will retain that many backup
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews versions of the file by
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews renaming them when opening. For example, if you choose to keep
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews three old versions
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews of the file <code class="filename">lamers.log</code>, then just
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews before it is opened
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews <code class="filename">lamers.log.1</code> is renamed to
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews <code class="filename">lamers.log.2</code>, <code class="filename">lamers.log.0</code> is renamed
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews to <code class="filename">lamers.log.1</code>, and <code class="filename">lamers.log</code> is
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews renamed to <code class="filename">lamers.log.0</code>.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews You can say <span><strong class="command">versions unlimited</strong></span> to
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User not limit
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews the number of versions.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews If a <span><strong class="command">size</strong></span> option is associated with
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews the log file,
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews then renaming is only done when the file being opened exceeds the
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews indicated size. No backup versions are kept by default; any
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews existing
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews log file is simply appended.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The <span><strong class="command">size</strong></span> option for files is used
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User to limit log
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User growth. If the file ever exceeds the size, then <span><strong class="command">named</strong></span> will
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington stop writing to the file unless it has a <span><strong class="command">versions</strong></span> option
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington associated with it. If backup versions are kept, the files are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater rolled as
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater described above and a new one begun. If there is no
bbf7c3fd96ae5e02cb84743c581862e35327032aAutomatic Updater <span><strong class="command">versions</strong></span> option, no more data will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater be written to the log
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater until some out-of-band mechanism removes or truncates the log to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater less than the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User maximum size. The default behavior is not to limit the size of
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington file.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews </p>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User<p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews Example usage of the <span><strong class="command">size</strong></span> and
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater <span><strong class="command">versions</strong></span> options:
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<pre class="programlisting">channel an_example_channel {
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater file "example.log" versions 3 size 20m;
61932ed91732417e05c8c6fd335acf1be896c778Mark Andrews print-time yes;
3040b455151b1e1173193933664b2891b6159f24Mark Andrews print-category yes;
e80c7005e3d59dfeb04dad186d36f3c15622954cTinderbox User};
e135e3c4b1f4f986f00997f5ad5866effb203139Tinderbox User</pre>
0e91f17da8a29086876a88962e0a3482094b6057Evan Hunt<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews The <span><strong class="command">syslog</strong></span> destination clause
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater directs the
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User channel to the system log. Its argument is a
3040b455151b1e1173193933664b2891b6159f24Mark Andrews syslog facility as described in the <span><strong class="command">syslog</strong></span> man
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater page. Known facilities are <span><strong class="command">kern</strong></span>, <span><strong class="command">user</strong></span>,
6fd5f289d8455283fad33d1051e6fbaa3bec43d5Tinderbox User <span><strong class="command">mail</strong></span>, <span><strong class="command">daemon</strong></span>, <span><strong class="command">auth</strong></span>,
08d53af7d51409036462fa80fb1bde7a8c2ac123Automatic Updater <span><strong class="command">syslog</strong></span>, <span><strong class="command">lpr</strong></span>, <span><strong class="command">news</strong></span>,
08d53af7d51409036462fa80fb1bde7a8c2ac123Automatic Updater <span><strong class="command">uucp</strong></span>, <span><strong class="command">cron</strong></span>, <span><strong class="command">authpriv</strong></span>,
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater <span><strong class="command">ftp</strong></span>, <span><strong class="command">local0</strong></span>, <span><strong class="command">local1</strong></span>,
ec7751119a08c6a7250f3187beed69a8b836d349Tinderbox User <span><strong class="command">local2</strong></span>, <span><strong class="command">local3</strong></span>, <span><strong class="command">local4</strong></span>,
6fd5f289d8455283fad33d1051e6fbaa3bec43d5Tinderbox User <span><strong class="command">local5</strong></span>, <span><strong class="command">local6</strong></span> and
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span><strong class="command">local7</strong></span>, however not all facilities
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater are supported on
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater all operating systems.
07d9d0dbcc0c79deb3c34f4a8af05ac68a6800e4Mark Andrews How <span><strong class="command">syslog</strong></span> will handle messages
07d9d0dbcc0c79deb3c34f4a8af05ac68a6800e4Mark Andrews sent to
a66012b52c20200f118781463db4e4ee44454298Automatic Updater this facility is described in the <span><strong class="command">syslog.conf</strong></span> man
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt page. If you have a system which uses a very old version of <span><strong class="command">syslog</strong></span> that
3040b455151b1e1173193933664b2891b6159f24Mark Andrews only uses two arguments to the <span><strong class="command">openlog()</strong></span> function,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews then this clause is silently ignored.
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </p>
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User On Windows machines syslog messages are directed to the EventViewer.
e135e3c4b1f4f986f00997f5ad5866effb203139Tinderbox User </p>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User<p>
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater The <span><strong class="command">severity</strong></span> clause works like <span><strong class="command">syslog</strong></span>'s
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater "priorities", except that they can also be used if you are writing
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater straight to a file rather than using <span><strong class="command">syslog</strong></span>.
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User Messages which are not at least of the severity level given will
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater not be selected for the channel; messages of higher severity
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater levels
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User will be accepted.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<p>
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User If you are using <span><strong class="command">syslog</strong></span>, then the <span><strong class="command">syslog.conf</strong></span> priorities
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User will also determine what eventually passes through. For example,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User defining a channel facility and severity as <span><strong class="command">daemon</strong></span> and <span><strong class="command">debug</strong></span> but
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington only logging <span><strong class="command">daemon.warning</strong></span> via <span><strong class="command">syslog.conf</strong></span> will
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington cause messages of severity <span><strong class="command">info</strong></span> and
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span><strong class="command">notice</strong></span> to
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington be dropped. If the situation were reversed, with <span><strong class="command">named</strong></span> writing
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington messages of only <span><strong class="command">warning</strong></span> or higher,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater then <span><strong class="command">syslogd</strong></span> would
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater print all messages it received from the channel.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The <span><strong class="command">stderr</strong></span> destination clause
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User directs the
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User channel to the server's standard error stream. This is intended
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User for
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User use when the server is running as a foreground process, for
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User example
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater when debugging a configuration.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
6a9d2121152c94cb9e35832126c3f2e4d18d81edTinderbox User<p>
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews The server can supply extensive debugging information when
85b52a5959291f5014442814488ccb267cdea369Tinderbox User it is in debugging mode. If the server's global debug level is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater greater
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User than zero, then debugging mode will be active. The global debug
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews level is set either by starting the <span><strong class="command">named</strong></span> server
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater with the <code class="option">-d</code> flag followed by a positive integer,
e062b72f783cdb436a1a57a630bdff471dbb3038Mark Andrews or by running <span><strong class="command">rndc trace</strong></span>.
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater The global debug level
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater can be set to zero, and debugging mode turned off, by running <span><strong class="command">rndc
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updaternotrace</strong></span>. All debugging messages in the server have a debug
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater level, and higher debug levels give more detailed output. Channels
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater that specify a specific debug severity, for example:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<pre class="programlisting">channel specific_debug_level {
85b52a5959291f5014442814488ccb267cdea369Tinderbox User file "foo";
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User severity debug 3;
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews};
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater will get debugging output of level 3 or less any time the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater server is in debugging mode, regardless of the global debugging
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater level. Channels with <span><strong class="command">dynamic</strong></span>
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater severity use the
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater server's global debug level to determine what messages to print.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews If <span><strong class="command">print-time</strong></span> has been turned on,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater then
52cfbde0bd391cfb37e3c1a1b460c16ba6bf1a73Automatic Updater the date and time will be logged. <span><strong class="command">print-time</strong></span> may
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User be specified for a <span><strong class="command">syslog</strong></span> channel,
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User but is usually
24e0e8d17df315d5d494ca933874e545eadce773Automatic Updater pointless since <span><strong class="command">syslog</strong></span> also logs
52cfbde0bd391cfb37e3c1a1b460c16ba6bf1a73Automatic Updater the date and
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews time. If <span><strong class="command">print-category</strong></span> is
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt requested, then the
3040b455151b1e1173193933664b2891b6159f24Mark Andrews category of the message will be logged as well. Finally, if <span><strong class="command">print-severity</strong></span> is
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews on, then the severity level of the message will be logged. The <span><strong class="command">print-</strong></span> options may
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater be used in any combination, and will always be printed in the
3040b455151b1e1173193933664b2891b6159f24Mark Andrews following
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater order: time, category, severity. Here is an example where all
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews three <span><strong class="command">print-</strong></span> options
3040b455151b1e1173193933664b2891b6159f24Mark Andrews are on:
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="computeroutput">28-Feb-2000 15:05:32.863 general: notice: running</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater If <span><strong class="command">buffered</strong></span> has been turned on the output
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater to files will not be flushed after each log entry. By default
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater all log messages are flushed.
0c7657e9302e7f9a8fe4f32fe561dc7e7e7ee6b5Automatic Updater </p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User There are four predefined channels that are used for
dcff0bfce2963a14e5af5774fd8901a42f18c720Tinderbox User <span><strong class="command">named</strong></span>'s default logging as follows.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews If <span><strong class="command">named</strong></span> is started with the
12ee3c02ab36d7e7430bd705cc289db1a69a5733Mark Andrews <code class="option">-L</code> then a
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater fifth channel <span><strong class="command">default_logfile</strong></span> is added.
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews How they are
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater used is described in <a href="Bv9ARM.ch06.html#the_category_phrase" title="The category Phrase">the section called &#8220;The <span><strong class="command">category</strong></span> Phrase&#8221;</a>.
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater </p>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User<pre class="programlisting">channel default_syslog {
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews // send to syslog's daemon facility
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater syslog daemon;
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater // only send priority info and higher
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews severity info;
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater
3040b455151b1e1173193933664b2891b6159f24Mark Andrewschannel default_debug {
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt // write to named.run in the working directory
3040b455151b1e1173193933664b2891b6159f24Mark Andrews // Note: stderr is used instead of "named.run" if
3040b455151b1e1173193933664b2891b6159f24Mark Andrews // the server is started with the '-g' option.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User file "named.run";
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews // log at the server's current debug level
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews severity dynamic;
fd8fb4df8499e292daeac765f599ac7c507d9ca3Mark Andrews};
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User
3040b455151b1e1173193933664b2891b6159f24Mark Andrewschannel default_stderr {
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater // writes to stderr
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater stderr;
3040b455151b1e1173193933664b2891b6159f24Mark Andrews // only send priority info and higher
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater severity info;
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater};
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updaterchannel null {
3040b455151b1e1173193933664b2891b6159f24Mark Andrews // toss anything sent to this channel
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater null;
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater};
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updaterchannel default_logfile {
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews // this channel is only present if named is
3040b455151b1e1173193933664b2891b6159f24Mark Andrews // started with the -L option, whose argument
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User // provides the file name
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User file "...";
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews // log at the server's current debug level
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater severity dynamic;
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews};
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</pre>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews The <span><strong class="command">default_debug</strong></span> channel has the
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews special
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews property that it only produces output when the server's debug
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews level is
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews nonzero. It normally writes to a file called <code class="filename">named.run</code>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews in the server's working directory.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews For security reasons, when the <code class="option">-u</code>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews command line option is used, the <code class="filename">named.run</code> file
3040b455151b1e1173193933664b2891b6159f24Mark Andrews is created only after <span><strong class="command">named</strong></span> has
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater changed to the
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater new UID, and any debug output generated while <span><strong class="command">named</strong></span> is
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater starting up and still running as root is discarded. If you need
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater to capture this output, you must run the server with the <code class="option">-L</code>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater option to specify a default logfile, or the <code class="option">-g</code>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater option to log to standard error which you can redirect to a file.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Once a channel is defined, it cannot be redefined. Thus you
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater cannot alter the built-in channels directly, but you can modify
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater the default logging by pointing categories at channels you have
3040b455151b1e1173193933664b2891b6159f24Mark Andrews defined.
560d6da48f066000541dd43f5d407644dee12bebTinderbox User </p>
560d6da48f066000541dd43f5d407644dee12bebTinderbox User</div>
9bc394fffdd50f6e47614b2d317da7274122366fTinderbox User<div class="sect3" lang="en">
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt<div class="titlepage"><div><div><h4 class="title">
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<a name="the_category_phrase"></a>The <span><strong class="command">category</strong></span> Phrase</h4></div></div></div>
560d6da48f066000541dd43f5d407644dee12bebTinderbox User<p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews There are many categories, so you can send the logs you want
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User to see wherever you want, without seeing logs you don't want. If
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater you don't specify a list of channels for a category, then log
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater messages
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater in that category will be sent to the <span><strong class="command">default</strong></span> category
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater instead. If you don't specify a default category, the following
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater "default default" is used:
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">category default { default_syslog; default_debug; };
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater</pre>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User If you start <span><strong class="command">named</strong></span> with the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <code class="option">-L</code> option then the default category is:
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<pre class="programlisting">category default { default_logfile; default_debug; };
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User</pre>
90b25b84f037ec923efaee84d2c0dc599293d04eTinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater As an example, let's say you want to log security events to
e0bf4fc289705375be65c05a8fb085d514a98c97Tinderbox User a file, but you also want keep the default logging behavior. You'd
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater specify the following:
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<pre class="programlisting">channel my_security_channel {
a6e1f63f50af688610ebd2521ba7f028767b51f3Mark Andrews file "my_security_file";
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater severity info;
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User};
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox Usercategory security {
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater my_security_channel;
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater default_syslog;
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User default_debug;
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater};</pre>
e0bf4fc289705375be65c05a8fb085d514a98c97Tinderbox User<p>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User To discard all messages in a category, specify the <span><strong class="command">null</strong></span> channel:
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater<pre class="programlisting">category xfer-out { null; };
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox Usercategory notify { null; };
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater</pre>
4d813066e967a36c407ee641155ada0c614d4dc6Automatic Updater<p>
dbd021853bb1cd6ab128e8da8865f5965030aedcTinderbox User Following are the available categories and brief descriptions
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User of the types of log information they contain. More
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User categories may be added in future <acronym class="acronym">BIND</acronym> releases.
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater<div class="informaltable"><table border="1">
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<colgroup>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<col>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User<col>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</colgroup>
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews<tbody>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<tr>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <p><span><strong class="command">default</strong></span></p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <p>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User The default category defines the logging
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews options for those categories where no specific
3040b455151b1e1173193933664b2891b6159f24Mark Andrews configuration has been
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews defined.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User</tr>
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User<tr>
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p><span><strong class="command">general</strong></span></p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews The catch-all. Many things still aren't
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews classified into categories, and they all end up here.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews</tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p><span><strong class="command">database</strong></span></p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt Messages relating to the databases used
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews internally by the name server to store zone and cache
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews data.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews</tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p><span><strong class="command">security</strong></span></p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
015f044f7f916eb18d053f2e5dcbee481425bc66Mark Andrews Approval and denial of requests.
e7d35dad55e8deae14f29aabfb20d540b4b6ab3dMark Andrews </p>
015f044f7f916eb18d053f2e5dcbee481425bc66Mark Andrews </td>
e7d35dad55e8deae14f29aabfb20d540b4b6ab3dMark Andrews</tr>
015f044f7f916eb18d053f2e5dcbee481425bc66Mark Andrews<tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p><span><strong class="command">config</strong></span></p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews Configuration file parsing and processing.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews</tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p><span><strong class="command">resolver</strong></span></p>
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User </td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews DNS resolution, such as the recursive
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews lookups performed on behalf of clients by a caching name
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews server.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</tr>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<tr>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <p><span><strong class="command">xfer-in</strong></span></p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews Zone transfers the server is receiving.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</tr>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<tr>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <p><span><strong class="command">xfer-out</strong></span></p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews Zone transfers the server is sending.
bbd726b86a5b0f97a192b6027958dc7b763dc48bTinderbox User </p>
7a2a1b8b14fc804ac80612d7b98064095e445be5Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<tr>
7a2a1b8b14fc804ac80612d7b98064095e445be5Automatic Updater<td>
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User <p><span><strong class="command">notify</strong></span></p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews The NOTIFY protocol.
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </td>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews</tr>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<tr>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<td>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews <p><span><strong class="command">client</strong></span></p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews <p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews Processing of client requests.
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </td>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews</tr>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<tr>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<td>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews <p><span><strong class="command">unmatched</strong></span></p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </td>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews Messages that <span><strong class="command">named</strong></span> was unable to determine the
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews class of or for which there was no matching <span><strong class="command">view</strong></span>.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews A one line summary is also logged to the <span><strong class="command">client</strong></span> category.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User This category is best sent to a file or stderr, by
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User default it is sent to
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the <span><strong class="command">null</strong></span> channel.
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p><span><strong class="command">network</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Network operations.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User </td>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User</tr>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User<tr>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User<td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews <p><span><strong class="command">update</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater Dynamic updates.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater</tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p><span><strong class="command">update-security</strong></span></p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater Approval and denial of update requests.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater</tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<tr>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p><span><strong class="command">queries</strong></span></p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater Specify where queries should be logged to.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater At startup, specifying the category <span><strong class="command">queries</strong></span> will also
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater enable query logging unless <span><strong class="command">querylog</strong></span> option has been
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater specified.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt The query log entry reports the client's IP
3040b455151b1e1173193933664b2891b6159f24Mark Andrews address and port number, and the query name,
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews class and type. Next it reports whether the
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User Recursion Desired flag was set (+ if set, -
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User if not set), if the query was signed (S),
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User EDNS was in used along with the EDNS version
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User number (E(#)), if TCP was used (T), if DO
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User (DNSSEC Ok) was set (D), if CD (Checking
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User Disabled) was set (C), if a valid DNS Server
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User COOKIE was received (V), or if a DNS COOKIE
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User option without a valid Server COOKIE was
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User present (K). After this the destination
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User address the query was sent to is reported.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <code class="computeroutput">client 127.0.0.1#62536 (www.example.com): query: www.example.com IN AAAA +SE</code>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="computeroutput">client ::1#62537 (www.example.net): query: www.example.net IN AAAA -SE</code>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User (The first part of this log message, showing the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User client address/port number and query name, is
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User repeated in all subsequent log messages related
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User to the same query.)
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">query-errors</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater <p>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews Information about queries that resulted in some
3040b455151b1e1173193933664b2891b6159f24Mark Andrews failure.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</tr>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p><span><strong class="command">dispatch</strong></span></p>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews Dispatching of incoming packets to the
3040b455151b1e1173193933664b2891b6159f24Mark Andrews server modules where they are to be processed.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
ec7751119a08c6a7250f3187beed69a8b836d349Tinderbox User</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><span><strong class="command">dnssec</strong></span></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
879391501ee0ffba072433120bf1baa4087f8899Automatic Updater <p>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater DNSSEC and TSIG protocol processing.
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater </p>
8f536463f9fdfa7da6a8310e4f4895373beb2961Mark Andrews </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</tr>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater<tr>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p><span><strong class="command">lame-servers</strong></span></p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </td>
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews<td>
dcd42a39d311b44877161ffd1e27fa62700c0171Mark Andrews <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic 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>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User<td>
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User <p><span><strong class="command">delegation-only</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User<td>
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User <p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews Delegation only. Logs queries that have been
3040b455151b1e1173193933664b2891b6159f24Mark Andrews forced to NXDOMAIN as the result of a
3040b455151b1e1173193933664b2891b6159f24Mark Andrews delegation-only zone or a
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews <span><strong class="command">delegation-only</strong></span> in a
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews forward, hint or stub zone declaration.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p><span><strong class="command">edns-disabled</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater <p>
63654fea53d6a58a65112234bc8d0c322e0c81b5Automatic Updater Log queries that have been forced to use plain
63654fea53d6a58a65112234bc8d0c322e0c81b5Automatic Updater DNS due to timeouts. This is often due to
3040b455151b1e1173193933664b2891b6159f24Mark Andrews the remote servers not being RFC 1034 compliant
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User (not always returning FORMERR or similar to
64d59a0480180940d855a3431ac5ff617b53e997Tinderbox User EDNS queries and other extensions to the DNS
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User when they are not understood). In other words, this is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater targeted at servers that fail to respond to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater DNS queries that they don't understand.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Note: the log message can also be due to
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater packet loss. Before reporting servers for
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater non-RFC 1034 compliance they should be re-tested
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User to determine the nature of the non-compliance.
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews This testing should prevent or reduce the
3040b455151b1e1173193933664b2891b6159f24Mark Andrews number of false-positive reports.
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User Note: eventually <span><strong class="command">named</strong></span> will have to stop
3040b455151b1e1173193933664b2891b6159f24Mark Andrews treating such timeouts as due to RFC 1034 non
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews compliance and start treating it as plain
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews packet loss. Falsely classifying packet
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater loss as due to RFC 1034 non compliance impacts
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater on DNSSEC validation which requires EDNS for
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User the DNSSEC records to be returned.
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews<td>
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews <p><span><strong class="command">RPZ</strong></span></p>
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User </td>
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User Information about errors in response policy zone files,
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User rewritten responses, and at the highest
80f05de86cd3cd8e4a4215c4501643891b942dafTinderbox User <span><strong class="command">debug</strong></span> levels, mere rewriting
80f05de86cd3cd8e4a4215c4501643891b942dafTinderbox User attempts.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</tr>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews<tr>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews<td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <p><span><strong class="command">rate-limit</strong></span></p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<td>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User <p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User The start, periodic, and final notices of the
3040b455151b1e1173193933664b2891b6159f24Mark Andrews rate limiting of a stream of responses are logged at
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews <span><strong class="command">info</strong></span> severity in this category.
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews These messages include a hash value of the domain name
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews of the response and the name itself,
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews except when there is insufficient memory to record
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews the name for the final notice
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews The final notice is normally delayed until about one
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews minute after rate limit stops.
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt A lack of memory can hurry the final notice,
3040b455151b1e1173193933664b2891b6159f24Mark Andrews in which case it starts with an asterisk (*).
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews Various internal events are logged at debug 1 level
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater and higher.
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater <p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater Rate limiting of individual requests
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater is logged in the <span><strong class="command">query-errors</strong></span> category.
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </p>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User </td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews</tr>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<tr>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">cname</strong></span></p>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User </td>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User<td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User Logs nameservers that are skipped due to them being
183b6c7fca54001820078f324d102fc33e64bbc6Automatic Updater a CNAME rather than A / AAAA records.
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater </p>
e130ab53e992670e2a2ecf043976ac09f21358d1Automatic Updater </td>
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews</tr>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User</tbody>
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User</table></div>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect3" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h4 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="id2576830"></a>The <span><strong class="command">query-errors</strong></span> Category</h4></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater The <span><strong class="command">query-errors</strong></span> category is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater specifically intended for debugging purposes: To identify
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User why and how specific queries result in responses which
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User indicate an error.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Messages of this category are therefore only logged
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User with <span><strong class="command">debug</strong></span> levels.
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User </p>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User<p>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User At the debug levels of 1 or higher, each response with the
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User rcode of SERVFAIL is logged as follows:
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User </p>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User<p>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User <code class="computeroutput">client 127.0.0.1#61502: query failed (SERVFAIL) for www.example.com/IN/AAAA at query.c:3880</code>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This means an error resulting in SERVFAIL was
3040b455151b1e1173193933664b2891b6159f24Mark Andrews detected at line 3880 of source file
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">query.c</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Log messages of this level will particularly
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater help identify the cause of SERVFAIL for an
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User authoritative server.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt At the debug levels of 2 or higher, detailed context
3040b455151b1e1173193933664b2891b6159f24Mark Andrews information of recursive resolutions that resulted in
3497d225321ed571428ed011650deb229ccfc977Tinderbox User SERVFAIL is logged.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The log message will look like as follows:
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<pre class="programlisting">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrewsfetch completed at resolver.c:2970 for www.example.com/A
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrewsin 30.000183: timed out/success [domain:example.com,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrewsreferral:2,restart:7,qrysent:8,timeout:5,lame:0,neterr:0,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrewsbadresp:1,adberr:0,findfail:0,valfail:0]
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User </pre>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews The first part before the colon shows that a recursive
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews resolution for AAAA records of www.example.com completed
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews in 30.000183 seconds and the final result that led to the
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews SERVFAIL was determined at line 2970 of source file
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="filename">resolver.c</code>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
17198e77b87667f796e910d31a4f47a80e256d09Mark Andrews<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The following part shows the detected final result and the
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater latest result of DNSSEC validation.
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater The latter is always success when no validation attempt
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater is made.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User In this example, this query resulted in SERVFAIL probably
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User because all name servers are down or unreachable, leading
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User to a timeout in 30 seconds.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User DNSSEC validation was probably not attempted.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater<p>
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater The last part enclosed in square brackets shows statistics
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater information collected for this particular resolution
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User attempt.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The <code class="varname">domain</code> field shows the deepest zone
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User that the resolver reached;
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User it is the zone where the error was finally detected.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The meaning of the other fields is summarized in the
de73ef7ecdb9e009155993a6fa8dee5cd1bde319Mark Andrews following table.
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater </p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater<div class="informaltable"><table border="1">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<colgroup>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<col>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<col>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</colgroup>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tbody>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater<tr>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater<td>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater <p><code class="varname">referral</code></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The number of referrals the resolver received
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User throughout the resolution process.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User In the above example this is 2, which are most
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User likely com and example.com.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p><code class="varname">restart</code></p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews The number of cycles that the resolver tried
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews remote servers at the <code class="varname">domain</code>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews zone.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews In each cycle the resolver sends one query
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews (possibly resending it, depending on the response)
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews to each known name server of
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews the <code class="varname">domain</code> zone.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p><code class="varname">qrysent</code></p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews The number of queries the resolver sent at the
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">domain</code> zone.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p><code class="varname">timeout</code></p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews The number of timeouts since the resolver
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews received the last response.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p><code class="varname">lame</code></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The number of lame servers the resolver detected
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington at the <code class="varname">domain</code> zone.
febbdb34a7f7759922e239655e7429d78d3a8d26Tinderbox User A server is detected to be lame either by an
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User invalid response or as a result of lookup in
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews BIND9's address database (ADB), where lame
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews servers are cached.
0df8ead472f207020f8da22a185fe4b945248ab8Automatic Updater </p>
0df8ead472f207020f8da22a185fe4b945248ab8Automatic Updater </td>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews</tr>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<tr>
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User<td>
6fab60452ed15c1039aee974a32d692d07eda4d2Automatic Updater <p><code class="varname">neterr</code></p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </td>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<td>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater <p>
b4846627b60aff904d523a433b44482b3b1825a7Tinderbox User The number of erroneous results that the
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews resolver encountered in sending queries
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews at the <code class="varname">domain</code> zone.
71ba75c604df3604673232828a68bb28c420e698Mark Andrews One common case is the remote server is
71ba75c604df3604673232828a68bb28c420e698Mark Andrews unreachable and the resolver receives an ICMP
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews unreachable error message.
e7d35dad55e8deae14f29aabfb20d540b4b6ab3dMark Andrews </p>
e7d35dad55e8deae14f29aabfb20d540b4b6ab3dMark Andrews </td>
e7d35dad55e8deae14f29aabfb20d540b4b6ab3dMark Andrews</tr>
e7d35dad55e8deae14f29aabfb20d540b4b6ab3dMark Andrews<tr>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<td>
dfd613f037c1385db661f17e086d34ea57fea9b0Automatic Updater <p><code class="varname">badresp</code></p>
6c6a121295b30772cbf3dd75a51fb9d883051a0eAutomatic Updater </td>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater The number of unexpected responses (other than
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">lame</code>) to queries sent by the
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews resolver at the <code class="varname">domain</code> zone.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p><code class="varname">adberr</code></p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <p>
56334ccb2d4b5a04fc12b70b5852049db5d24088Evan Hunt Failures in finding remote server addresses
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User of the <code class="varname">domain</code> zone in the ADB.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews One common case of this is that the remote
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User server's name does not have any address records.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p><code class="varname">findfail</code></p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User Failures of resolving remote server addresses.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews This is a total number of failures throughout
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User the resolution process.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
51901858be9d4632c1d0bed28cfa8f29932c1967Tinderbox User</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p><code class="varname">valfail</code></p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater Failures of DNSSEC validation.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews Validation failures are counted throughout
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson the resolution process (not limited to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the <code class="varname">domain</code> zone), but should
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews only happen in <code class="varname">domain</code>.
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tbody>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</table></div>
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater At the debug levels of 3 or higher, the same messages
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater as those at the debug 1 level are logged for other errors
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson than SERVFAIL.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Note that negative responses such as NXDOMAIN are not
7932a7637170550bc53b38c35db9a0187dcb3d3bAutomatic Updater regarded as errors here.
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson At the debug levels of 4 or higher, the same messages
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater as those at the debug 2 level are logged for other errors
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater than SERVFAIL.
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox User Unlike the above case of level 3, messages are logged for
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews negative responses.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews This is because any unexpected results can be difficult to
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox User debug in the recursion case.
de7b9a1dac0c293b39994c91d4376883da25554fTinderbox User </p>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews</div>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="sect2" lang="en">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<a name="id2577350"></a><span><strong class="command">lwres</strong></span> Statement Grammar</h3></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User This is the grammar of the <span><strong class="command">lwres</strong></span>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User statement in the <code class="filename">named.conf</code> file:
467a823e57af687ebd486dfd73ea32f9d2a145beTinderbox User </p>
467a823e57af687ebd486dfd73ea32f9d2a145beTinderbox User<pre class="programlisting"><span><strong class="command">lwres</strong></span> {
7d704e522860496310bb29c28e76064868401a9cMark Andrews [<span class="optional"> listen-on { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ;
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark 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 class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater [<span class="optional"> view <em class="replaceable"><code>view_name</code></em>; </span>]
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User [<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>]
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews [<span class="optional"> ndots <em class="replaceable"><code>number</code></em>; </span>]
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews [<span class="optional"> lwres-tasks <em class="replaceable"><code>number</code></em>; </span>]
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater [<span class="optional"> lwres-clients <em class="replaceable"><code>number</code></em>; </span>]
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater};
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User</pre>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User</div>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User<div class="sect2" lang="en">
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User<div class="titlepage"><div><div><h3 class="title">
402eda3e7d4254ffac1543bf2917c71248a09e4cTinderbox User<a name="id2577447"></a><span><strong class="command">lwres</strong></span> Statement Definition and Usage</h3></div></div></div>
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews<p>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews The <span><strong class="command">lwres</strong></span> statement configures the
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews name
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater server to also act as a lightweight resolver server. (See
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark 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
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews <span><strong class="command">lwres</strong></span> statements configuring
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews lightweight resolver servers with different properties.
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews </p>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews<p>
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews The <span><strong class="command">listen-on</strong></span> statement specifies a
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews list of
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews IPv4 addresses (and ports) that this instance of a lightweight
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater resolver daemon
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User should accept requests on. If no port is specified, port 921 is
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User used.
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User If this statement is omitted, requests will be accepted on
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User 127.0.0.1,
24bf1e02f03577db0feb50b80238c4150c96d05dAutomatic Updater port 921.
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater </p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater The <span><strong class="command">view</strong></span> statement binds this
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User instance of a
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User lightweight resolver daemon to a view in the DNS namespace, so that
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User the
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User response will be constructed in the same manner as a normal DNS
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User query
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User matching this view. If this statement is omitted, the default view
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User is
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User used, and if there is no default view, an error is triggered.
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User </p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User<p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User The <span><strong class="command">search</strong></span> statement is equivalent to
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User the
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User <span><strong class="command">search</strong></span> statement in
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User <code class="filename">/etc/resolv.conf</code>. It provides a
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User list of domains
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User which are appended to relative names in queries.
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User </p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User<p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User The <span><strong class="command">ndots</strong></span> statement is equivalent to
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User the
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User <span><strong class="command">ndots</strong></span> statement in
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User <code class="filename">/etc/resolv.conf</code>. It indicates the
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User minimum
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User number of dots in a relative domain name that should result in an
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User exact match lookup before search path elements are appended.
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User </p>
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User<p>
b8cc0c5d896c361525708a2be2e5af7df76c96d7Tinderbox User The <code class="option">lwres-tasks</code> statement specifies the number
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User of worker threads the lightweight resolver will dedicate to serving
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User clients. By default the number is the same as the number of CPUs on
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User the system; this can be overridden using the <code class="option">-n</code>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User command line option when starting the server.
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User </p>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User<p>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User The <code class="option">lwres-clients</code> specifies
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User the number of client objects per thread the lightweight
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User resolver should create to serve client queries.
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User By default, if the lightweight resolver runs as a part
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User of <span><strong class="command">named</strong></span>, 256 client objects are
2ec4ab21838e218863d052ebfa3e106e04f50820Evan Hunt created for each task; if it runs as <span><strong class="command">lwresd</strong></span>,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews 1024 client objects are created for each thread. The maximum
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews value is 32768; higher values will be silently ignored and
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the maximum will be used instead.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Note that setting too high a value may overconsume
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews system resources.
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The maximum number of client queries that the lightweight
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews resolver can handle at any one time equals
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="option">lwres-tasks</code> times <code class="option">lwres-clients</code>.
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="id2577611"></a><span><strong class="command">masters</strong></span> Statement Grammar</h3></div></div></div>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<pre class="programlisting">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<span><strong class="command">masters</strong></span> <em class="replaceable"><code>name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> |
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="id2577660"></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 in their <span><strong class="command">masters</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews or <span><strong class="command">also-notify</strong></span> lists.
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="id2577682"></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"> geoip-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"> managed-keys-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-keytab <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"> lock-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> secroots-file <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> session-keyfile <em class="replaceable"><code>path_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> session-keyname <em class="replaceable"><code>key_name</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> session-keyalg <em class="replaceable"><code>algorithm_id</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> memstatistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark 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>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</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>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> flush-zones-on-shutdown <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> has-old-clients <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> host-statistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> host-statistics-max <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> minimal-responses <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> multiple-cnames <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark 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>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> recursion <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> send-cookie <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> require-server-cookie <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> cookie-algorithm <em class="replaceable"><code>secret_string</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> cookie-secret <em class="replaceable"><code>secret_string</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> request-nsid <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> rfc2308-type1 <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> use-id-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em>; </span>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark 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>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-enable <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-validation (<em class="replaceable"><code>yes_or_no</code></em> | <code class="constant">auto</code>); </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-lookaside ( <em class="replaceable"><code>auto</code></em> |
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <em class="replaceable"><code>no</code></em> |
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <em class="replaceable"><code>domain</code></em> trust-anchor <em class="replaceable"><code>domain</code></em> ); </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-must-be-secure <em class="replaceable"><code>domain yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-accept-expired <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> forward ( <em class="replaceable"><code>only</code></em> | <em class="replaceable"><code>first</code></em> ); </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark 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 class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dual-stack-servers [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] {
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews ( <em class="replaceable"><code>domain_name</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] |
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">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]) ;
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews ... }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark 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> )
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> check-dup-records ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark 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>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<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>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<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>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> check-sibling <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> check-spf ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-new-zones { <em class="replaceable"><code>yes_or_no</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-query-cache { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-query-cache-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-recursion { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-recursion-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> automatic-interface-scan { <em class="replaceable"><code>yes_or_no</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> geoip-use-ecs <em class="replaceable"><code>yes_or_no</code></em>;</span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-update-mode ( <em class="replaceable"><code>maintain</code></em> | <em class="replaceable"><code>no-resign</code></em> ); </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-dnskey-kskonly <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-loadkeys-interval <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dnssec-secure-to-insecure <em class="replaceable"><code>yes_or_no</code></em> ;</span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> try-tcp-refresh <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> allow-v6-synthesis { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> blackhole { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> keep-response-order { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> no-case-compress { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> use-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> avoid-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> use-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> avoid-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> listen-on [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em> </span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> listen-on-v6 [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews{ <em class="replaceable"><code>address_match_list</code></em> }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> query-source ( ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> )
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] |
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> address ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark 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"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> query-source-v6 ( ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> )
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] |
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> address ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] )
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> use-queryport-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> queryport-pool-ports <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> queryport-pool-updateinterval <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> reserved-sockets <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> recursive-clients <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> tcp-clients <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> clients-per-query <em class="replaceable"><code>number</code></em> ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> max-clients-per-query <em class="replaceable"><code>number</code></em> ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> fetches-per-server <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>(drop | fail)</code></em></span>]; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> fetch-quota-params <em class="replaceable"><code>number fixedpoint fixedpoint fixedpoint</code></em> ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> fetches-per-zone<em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>(drop | fail)</code></em></span>]; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> notify-rate <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> startup-notify-rate <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> serial-query-rate <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> serial-queries <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> tcp-listen-queue <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> transfer-format <em class="replaceable"><code>( one-answer | many-answers )</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> transfers-in <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> transfers-out <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> transfers-per-ns <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> notify-to-soa <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> also-notify { <em class="replaceable"><code>ip_addr</code></em>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] [<span class="optional">key <em class="replaceable"><code>keyname</code></em></span>] ;
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 class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] [<span class="optional">key <em class="replaceable"><code>keyname</code></em></span>] ; ... </span>] }; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em>; </span>]
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews [<span class="optional"> max-journal-size <em class="replaceable"><code>size_spec</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> coresize <em class="replaceable"><code>size_spec</code></em> ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> datasize <em class="replaceable"><code>size_spec</code></em> ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> files <em class="replaceable"><code>size_spec</code></em> ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> stacksize <em class="replaceable"><code>size_spec</code></em> ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> cleaning-interval <em class="replaceable"><code>number</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> heartbeat-interval <em class="replaceable"><code>number</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> interface-interval <em class="replaceable"><code>number</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> statistics-interval <em class="replaceable"><code>number</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> topology { <em class="replaceable"><code>address_match_list</code></em> }</span>];
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> sortlist { <em class="replaceable"><code>address_match_list</code></em> }</span>];
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<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>] };
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> lame-ttl <em class="replaceable"><code>number</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> max-ncache-ttl <em class="replaceable"><code>number</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> max-cache-ttl <em class="replaceable"><code>number</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> max-zone-ttl ( <code class="constant">unlimited</code> | <em class="replaceable"><code>number</code></em> ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> servfail-ttl <em class="replaceable"><code>number</code></em>; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<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>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> sig-signing-nodes <em class="replaceable"><code>number</code></em> ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> sig-signing-signatures <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> sig-signing-type <em class="replaceable"><code>number</code></em> ; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> min-roots <em class="replaceable"><code>number</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> use-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> provide-ixfr <em class="replaceable"><code>yes_or_no</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> request-expire <em class="replaceable"><code>yes_or_no</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> treat-cr-as-space <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
c57668a2fbbe558c1bd21652813616f2f517c469Tinderbox User [<span class="optional"> nta-lifetime <em class="replaceable"><code>duration</code></em> ; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> nta-recheck <em class="replaceable"><code>duration</code></em> ; </span>]
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em>; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ;
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> additional-from-auth <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater [<span class="optional"> additional-from-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [<span class="optional"> random-device <em class="replaceable"><code>path_name</code></em> ; </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> max-cache-size <em class="replaceable"><code>size_spec</code></em> ; </span>]
309b912841e8b97bf0b0df0d96c3eaf16990c080Automatic Updater [<span class="optional"> match-mapped-addresses <em class="replaceable"><code>yes_or_no</code></em>; </span>]
66d24a46538c7c2d29fdb5611ab1173e83685b1dTinderbox User [<span class="optional"> filter-aaaa-on-v4 ( <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>break-dnssec</code></em> ); </span>]
66d24a46538c7c2d29fdb5611ab1173e83685b1dTinderbox User [<span class="optional"> filter-aaaa-on-v6 ( <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>break-dnssec</code></em> ); </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> filter-aaaa { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson [<span class="optional"> dns64 <em class="replaceable"><code>ipv6-prefix</code></em> {
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews [<span class="optional"> clients { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews [<span class="optional"> mapped { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews [<span class="optional"> exclude { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews [<span class="optional"> suffix IPv6-address; </span>]
94df856897945fe58f130ba78765c57308bc5400Automatic Updater [<span class="optional"> recursive-only <em class="replaceable"><code>yes_or_no</code></em>; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> break-dnssec <em class="replaceable"><code>yes_or_no</code></em>; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User }; </span>];
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> dns64-server <em class="replaceable"><code>name</code></em> </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> dns64-contact <em class="replaceable"><code>name</code></em> </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<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>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em>; </span>]
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews [<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em>; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> max-rsa-exponent-size <em class="replaceable"><code>number</code></em>; </span>]
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews [<span class="optional"> root-delegation-only [<span class="optional"> exclude { <em class="replaceable"><code>namelist</code></em> } </span>] ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> querylog <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> disable-algorithms <em class="replaceable"><code>domain</code></em> { <em class="replaceable"><code>algorithm</code></em>;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> <em class="replaceable"><code>algorithm</code></em>; </span>] }; </span>]
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [<span class="optional"> disable-ds-digests <em class="replaceable"><code>domain</code></em> { <em class="replaceable"><code>digest_type</code></em>;
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews [<span class="optional"> <em class="replaceable"><code>digest_type</code></em>; </span>] }; </span>]
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews [<span class="optional"> acache-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> acache-cleaning-interval <em class="replaceable"><code>number</code></em>; </span>]
da93950363b307b718d156514b95b9df93a63776Mark Andrews [<span class="optional"> max-acache-size <em class="replaceable"><code>size_spec</code></em> ; </span>]
da93950363b307b718d156514b95b9df93a63776Mark Andrews [<span class="optional"> max-recursion-depth <em class="replaceable"><code>number</code></em> ; </span>]
35bc7055d1b9b816e68a4180d46a49963e45c233Automatic Updater [<span class="optional"> max-recursion-queries <em class="replaceable"><code>number</code></em> ; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> masterfile-format
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater [<span class="optional"> masterfile-style
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater (<code class="constant">relative</code>|<code class="constant">full</code>) ; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> empty-server <em class="replaceable"><code>name</code></em> ; </span>]
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater [<span class="optional"> empty-contact <em class="replaceable"><code>name</code></em> ; </span>]
fbcaee30a27f47fe337152c27e7d90489dc8fd63Tinderbox User [<span class="optional"> empty-zones-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> disable-empty-zone <em class="replaceable"><code>zone_name</code></em> ; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> zero-no-soa-ttl-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater [<span class="optional"> resolver-query-timeout <em class="replaceable"><code>number</code></em> ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic 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>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<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>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> prefetch <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>number</code></em></span>] ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> rate-limit {
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> responses-per-second <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> referrals-per-second <em class="replaceable"><code>number</code></em> ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> nodata-per-second <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> nxdomains-per-second <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> errors-per-second <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> all-per-second <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> window <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> log-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> qps-scale <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> ipv4-prefix-length <em class="replaceable"><code>number</code></em> ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> ipv6-prefix-length <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> slip <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> exempt-clients { <em class="replaceable"><code>address_match_list</code></em> } ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> max-table-size <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> min-table-size <em class="replaceable"><code>number</code></em> ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User } ; </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> response-policy {
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt zone <em class="replaceable"><code>zone_name</code></em>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> policy <em class="replaceable"><code>(given | disabled | passthru | drop |
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User tcp-only | nxdomain | nodata | cname domain</code></em>) </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> recursive-only <em class="replaceable"><code>yes_or_no</code></em> </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> log <em class="replaceable"><code>yes_or_no</code></em> </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> max-policy-ttl <em class="replaceable"><code>number</code></em> </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt ; [<span class="optional">...</span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt } [<span class="optional"> recursive-only <em class="replaceable"><code>yes_or_no</code></em> </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> max-policy-ttl <em class="replaceable"><code>number</code></em> </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> break-dnssec <em class="replaceable"><code>yes_or_no</code></em> </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User [<span class="optional"> min-ns-dots <em class="replaceable"><code>number</code></em> </span>]
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt [<span class="optional"> qname-wait-recurse <em class="replaceable"><code>yes_or_no</code></em> </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User ; </span>]
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User};
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User</pre>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User</div>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<div class="sect2" lang="en">
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<div class="titlepage"><div><div><h3 class="title">
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<a name="options"></a><span><strong class="command">options</strong></span> Statement Definition and
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Usage</h3></div></div></div>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User The <span><strong class="command">options</strong></span> statement sets up global
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User options
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User to be used by <acronym class="acronym">BIND</acronym>. This statement
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt may appear only
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt once in a configuration file. If there is no <span><strong class="command">options</strong></span>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt statement, an options block with each option set to its default will
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User be used.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<div class="variablelist"><dl>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dt><span class="term"><span><strong class="command">attach-cache</strong></span></span></dt>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Allows multiple views to share a single cache
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User database.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Each view has its own cache database by default, but
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User if multiple views have the same operational policy
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User for name resolution and caching, those views can
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User share a single cache to save memory and possibly
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User improve resolution efficiency by using this option.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User The <span><strong class="command">attach-cache</strong></span> option
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User may also be specified in <span><strong class="command">view</strong></span>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User statements, in which case it overrides the
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User global <span><strong class="command">attach-cache</strong></span> option.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User The <em class="replaceable"><code>cache_name</code></em> specifies
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User the cache to be shared.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User When the <span><strong class="command">named</strong></span> server configures
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User views which are supposed to share a cache, it
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User creates a cache with the specified name for the
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User first view of these sharing views.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User The rest of the views will simply refer to the
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User already created cache.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt One common configuration to share a cache would be to
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User allow all views to share a single cache.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User This can be done by specifying
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User the <span><strong class="command">attach-cache</strong></span> as a global
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User option with an arbitrary name.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Another possible operation is to allow a subset of
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User all views to share a cache while the others to
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User retain their own caches.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User For example, if there are three views A, B, and C,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User and only A and B should share a cache, specify the
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">attach-cache</strong></span> option as a view A (or
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User B)'s option, referring to the other view name:
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<pre class="programlisting">
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User view "A" {
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User // this view has its own cache
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User ...
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User };
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User view "B" {
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User // this view refers to A's cache
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User attach-cache "A";
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User };
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User view "C" {
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User // this view has its own cache
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User ...
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User };
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User</pre>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Views that share a cache must have the same policy
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User on configurable parameters that may affect caching.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User The current implementation requires the following
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User configurable options be consistent among these
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User views:
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">check-names</strong></span>,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">cleaning-interval</strong></span>,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">dnssec-accept-expired</strong></span>,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">dnssec-validation</strong></span>,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">max-cache-ttl</strong></span>,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">max-ncache-ttl</strong></span>,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">max-cache-size</strong></span>, and
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">zero-no-soa-ttl</strong></span>.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Note that there may be other parameters that may
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User cause confusion if they are inconsistent for
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User different views that share a single cache.
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt For example, if these views define different sets of
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt forwarders that can return different answers for the
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User same question, sharing the answer does not make
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User sense or could even be harmful.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User It is administrator's responsibility to ensure
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User configuration differences in different views do
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User not cause disruption with a shared cache.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User</dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dt><span class="term"><span><strong class="command">directory</strong></span></span></dt>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dd><p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User The working directory of the server.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Any non-absolute pathnames in the configuration file will be
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User taken
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User as relative to this directory. The default location for most
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User server
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User output files (e.g. <code class="filename">named.run</code>)
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User is this directory.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User If a directory is not specified, the working directory
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User defaults to `<code class="filename">.</code>', the directory from
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User which the server
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User was started. The directory specified should be an absolute
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User path.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p></dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dt><span class="term"><span><strong class="command">geoip-directory</strong></span></span></dt>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dd><p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Specifies the directory containing GeoIP
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <code class="filename">.dat</code> database files for GeoIP
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User initialization. By default, this option is unset
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User and the GeoIP support will use libGeoIP's
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User built-in directory.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User (For details, see <a href="Bv9ARM.ch06.html#acl" title="acl Statement Definition and
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Usage">the section called &#8220;<span><strong class="command">acl</strong></span> Statement Definition and
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Usage&#8221;</a> about the
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span><strong class="command">geoip</strong></span> ACL.)
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p></dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dd><p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User When performing dynamic update of secure zones, the
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User directory where the public and private DNSSEC key files
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User should be found, if different than the current working
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User directory. (Note that this option has no effect on the
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt paths for files containing non-DNSSEC keys such as
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <code class="filename">bind.keys</code>,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <code class="filename">rndc.key</code> or
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <code class="filename">session.key</code>.)
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p></dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dt><span class="term"><span><strong class="command">managed-keys-directory</strong></span></span></dt>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt<dd>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt<p>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt Specifies the directory in which to store the files that
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User track managed DNSSEC keys. By default, this is the working
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User directory.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User If <span><strong class="command">named</strong></span> is not configured to use views,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User then managed keys for the server will be tracked in a single
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User file called <code class="filename">managed-keys.bind</code>.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User Otherwise, managed keys will be tracked in separate files,
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User one file per view; each file name will be the view name
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User (or, if it contains characters that are incompatible with
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User use as a file name, the SHA256 hash of the view name),
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User followed by the extension
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <code class="filename">.mkeys</code>.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt (Note: in previous releases, file names for views
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt always used the SHA256 hash of the view name. To ensure
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt compatibility after upgrade, if a file using the old
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt name format is found to exist, it will be used instead
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User of the new format.)
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User</dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dt><span class="term"><span><strong class="command">named-xfer</strong></span></span></dt>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dd><p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User <span class="emphasis"><em>This option is obsolete.</em></span> It
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User was used in <acronym class="acronym">BIND</acronym> 8 to specify
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User the pathname to the <span><strong class="command">named-xfer</strong></span>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User program. In <acronym class="acronym">BIND</acronym> 9, no separate
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt <span><strong class="command">named-xfer</strong></span> program is needed;
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User its functionality is built into the name server.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p></dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dt><span class="term"><span><strong class="command">tkey-gssapi-keytab</strong></span></span></dt>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dd><p>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User The KRB5 keytab file to use for GSS-TSIG updates. If
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User this option is set and tkey-gssapi-credential is not
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User set, then updates will be allowed with any key
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User matching a principal in the specified keytab.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews<dt><span class="term"><span><strong class="command">tkey-gssapi-credential</strong></span></span></dt>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User<dd><p>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User The security credential with which the server should
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User authenticate keys requested by the GSS-TSIG protocol.
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User Currently only Kerberos 5 authentication is available
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User and the credential is a Kerberos principal which the
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User server can acquire through the default system key
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User file, normally <code class="filename">/etc/krb5.keytab</code>.
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User The location keytab file can be overridden using the
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User tkey-gssapi-keytab option. Normally this principal is
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User of the form "<strong class="userinput"><code>DNS/</code></strong><code class="varname">server.domain</code>".
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User To use GSS-TSIG, <span><strong class="command">tkey-domain</strong></span> must
6a0d2961c04b20f0114cca12157cfed64c5b126fTinderbox User also be set if a specific keytab is not set with
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User tkey-gssapi-keytab.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p></dd>
c7ef13f6c9ef4436bc804b150e0a93307b11fa27Tinderbox User<dt><span class="term"><span><strong class="command">tkey-domain</strong></span></span></dt>
4ea3649f028ea6a1e42377082a7ccf8f789fb950Automatic Updater<dd><p>
644973f327e9db74779e7c0426db90909173b284Automatic Updater The domain appended to the names of all shared keys
644973f327e9db74779e7c0426db90909173b284Automatic Updater generated with <span><strong class="command">TKEY</strong></span>. When a
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User client requests a <span><strong class="command">TKEY</strong></span> exchange,
418cc932318b1d67f88a36904d88d8a5a0a2ba09Automatic Updater it may or may not specify the desired name for the
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User key. If present, the name of the shared key will
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User be <code class="varname">client specified part</code> +
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User <code class="varname">tkey-domain</code>. Otherwise, the
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User name of the shared key will be <code class="varname">random hex
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User digits</code> + <code class="varname">tkey-domain</code>.
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User In most cases, the <span><strong class="command">domainname</strong></span>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User should be the server's domain name, or an otherwise
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User non-existent subdomain like
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User "_tkey.<code class="varname">domainname</code>". If you are
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User using GSS-TSIG, this variable must be defined, unless
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User you specify a specific keytab using tkey-gssapi-keytab.
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User </p></dd>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User<dt><span class="term"><span><strong class="command">tkey-dhkey</strong></span></span></dt>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User<dd><p>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User The Diffie-Hellman key used by the server
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User to generate shared keys with clients using the Diffie-Hellman
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User mode
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User of <span><strong class="command">TKEY</strong></span>. The server must be
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User able to load the
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User public and private keys from files in the working directory.
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User In
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User most cases, the keyname should be the server's host name.
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User </p></dd>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User<dt><span class="term"><span><strong class="command">cache-file</strong></span></span></dt>
418cc932318b1d67f88a36904d88d8a5a0a2ba09Automatic Updater<dd><p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews This is for testing only. Do not use.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p></dd>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dt><span class="term"><span><strong class="command">dump-file</strong></span></span></dt>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dd><p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The pathname of the file the server dumps
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews the database to when instructed to do so with
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <span><strong class="command">rndc dumpdb</strong></span>.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews If not specified, the default is <code class="filename">named_dump.db</code>.
90863a6f9bfb06062c7fdf269bb675e7b674fc31Mark Andrews </p></dd>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dt><span class="term"><span><strong class="command">memstatistics-file</strong></span></span></dt>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dd><p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The pathname of the file the server writes memory
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews usage statistics to on exit. If not specified,
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews the default is <code class="filename">named.memstats</code>.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p></dd>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dt><span class="term"><span><strong class="command">lock-file</strong></span></span></dt>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dd>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews<p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The pathname of a file on which <span><strong class="command">named</strong></span> will
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews attempt to acquire a file lock when starting up for
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews the first time; if unsuccessful, the server will
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews will terminate, under the assumption that another
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews server is already running. If not specified, the default is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">/var/run/named/named.lock</code>.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Specifying <span><strong class="command">lock-file none</strong></span> disables the
68e1b398b5b1b417723e90b5e52b9148f8f93294Automatic Updater use of a lock file. <span><strong class="command">lock-file</strong></span> is
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews ignored if <span><strong class="command">named</strong></span> was run using the <code class="option">-X</code>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews option, which overrides it. Changes to
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews <span><strong class="command">lock-file</strong></span> are ignored if
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <span><strong class="command">named</strong></span> is being reloaded or
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews reconfigured; it is only effective when the server is
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User first started up.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">pid-file</strong></span></span></dt>
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The pathname of the file the server writes its process ID
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews in. If not specified, the default is
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <code class="filename">/var/run/named/named.pid</code>.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews The PID file is used by programs that want to send signals to
872a5b83f68b8058945298715b0fa53442aad52fAutomatic Updater the running
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews name server. Specifying <span><strong class="command">pid-file none</strong></span> disables the
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User use of a PID file &#8212; no file will be written and any
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews existing one will be removed. Note that <span><strong class="command">none</strong></span>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews is a keyword, not a filename, and therefore is not enclosed
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews in
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User double quotes.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p></dd>
7a2a1b8b14fc804ac80612d7b98064095e445be5Automatic Updater<dt><span class="term"><span><strong class="command">recursing-file</strong></span></span></dt>
7a42357217528037bdfedcb17eeebfe96ae4266aAutomatic Updater<dd><p>
a7038d1a0513c8e804937ebc95fc9cb3a46c04f5Mark Andrews The pathname of the file the server dumps
e007e3e5b0316c6c05698a71101885743aca22bdAutomatic Updater the queries that are currently recursing when instructed
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews to do so with <span><strong class="command">rndc recursing</strong></span>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington If not specified, the default is <code class="filename">named.recursing</code>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p></dd>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<dt><span class="term"><span><strong class="command">statistics-file</strong></span></span></dt>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<dd><p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The pathname of the file the server appends statistics
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington to when instructed to do so using <span><strong class="command">rndc stats</strong></span>.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington If not specified, the default is <code class="filename">named.stats</code> in the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington server's current directory. The format of the file is
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington described
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User in <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called &#8220;The Statistics File&#8221;</a>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
cff0e0b52cf0928123bad6f3bccf56e22bbc07f5Automatic Updater<dt><span class="term"><span><strong class="command">bindkeys-file</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The pathname of a file to override the built-in trusted
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater keys provided by <span><strong class="command">named</strong></span>.
644973f327e9db74779e7c0426db90909173b284Automatic Updater See the discussion of <span><strong class="command">dnssec-lookaside</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and <span><strong class="command">dnssec-validation</strong></span> for details.
c28a1243429dfaf8dc5f6c1db0dccdc6ce386baeMark Andrews If not specified, the default is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">/etc/bind.keys</code>.
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews </p></dd>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<dt><span class="term"><span><strong class="command">secroots-file</strong></span></span></dt>
5f7e0eb1cb917b788906d3e2aa01bfc4885dcae4Mark Andrews<dd><p>
bf1263835e8e35421960f65088c043f42aacef13Mark Andrews The pathname of the file the server dumps
15ae68f3db8261770fc33b8e0f83f5d8c7021e84Mark Andrews security roots to when instructed to do so with
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews <span><strong class="command">rndc secroots</strong></span>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User If not specified, the default is
2bb3422dc683c013db7042f5736240de6b86f182Automatic Updater <code class="filename">named.secroots</code>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
9bc394fffdd50f6e47614b2d317da7274122366fTinderbox User<dt><span class="term"><span><strong class="command">session-keyfile</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater The pathname of the file into which to write a TSIG
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews session key generated by <span><strong class="command">named</strong></span> for use by
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">nsupdate -l</strong></span>. If not specified, the
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User default is <code class="filename">/var/run/named/session.key</code>.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User (See <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>, and in
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User particular the discussion of the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">update-policy</strong></span> statement's
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <strong class="userinput"><code>local</code></strong> option for more
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater information about this feature.)
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">session-keyname</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater The key name to use for the TSIG session key.
10640b2e3efc7bc8034108136d7487f7407fbf37Andreas Gustafsson If not specified, the default is "local-ddns".
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p></dd>
10640b2e3efc7bc8034108136d7487f7407fbf37Andreas Gustafsson<dt><span class="term"><span><strong class="command">session-keyalg</strong></span></span></dt>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<dd><p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews The algorithm to use for the TSIG session key.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews Valid values are hmac-sha1, hmac-sha224, hmac-sha256,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews hmac-sha384, hmac-sha512 and hmac-md5. If not
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater specified, the default is hmac-sha256.
436aad11e01e916f75e68a2e9cb89ac217a990d3Tinderbox User </p></dd>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<dt><span class="term"><span><strong class="command">port</strong></span></span></dt>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<dd><p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The UDP/TCP port number the server uses for
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User receiving and sending DNS protocol traffic.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User The default is 53. This option is mainly intended for server
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User testing;
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User a server using a port other than 53 will not be able to
a792d42c3cdd6cd4608b936c0a06437b8c2d99ccTinderbox User communicate with
a01aa536188bb3535dfc1107a623e6355a8e6b7cMark Andrews the global DNS.
0a50626faa2f8941f55bf435d3965d490bb5d026Tinderbox User </p></dd>
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater<dt><span class="term"><span><strong class="command">dscp</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews The global Differentiated Services Code Point (DSCP)
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater value to classify outgoing DNS traffic on operating
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User systems that support DSCP. Valid values are 0 through 63.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User It is not configured by default.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p></dd>
8d0e57cdac5e28964ebe7c0d925d158f17b401a6Tinderbox User<dt><span class="term"><span><strong class="command">random-device</strong></span></span></dt>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dd><p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User The source of entropy to be used by the server. Entropy is
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews primarily needed
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews for DNSSEC operations, such as TKEY transactions and dynamic
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews update of signed
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews zones. This options specifies the device (or file) from which
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to read
e10d61d84e0b735f1e8eca18644cfdb1b06cad33Tinderbox User entropy. If this is a file, operations requiring entropy will
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews fail when the
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews file has been exhausted. If not specified, the default value
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews is
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User <code class="filename">/dev/random</code>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews (or equivalent) when present, and none otherwise. The
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <span><strong class="command">random-device</strong></span> option takes
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater effect during
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User the initial configuration load at server startup time and
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User is ignored on subsequent reloads.
90cde4c188ac5bdea4f402b241c387c9cc9d4cc4Tinderbox User </p></dd>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dt><span class="term"><span><strong class="command">preferred-glue</strong></span></span></dt>
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews<dd><p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User If specified, the listed type (A or AAAA) will be emitted
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User before other glue
4c9f230f7ca5b2b08ea8fd7a6944135801dbe152Tinderbox User in the additional section of a query response.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews The default is not to prefer any type (NONE).
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User </p></dd>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="root_delegation_only"></a><span class="term"><span><strong class="command">root-delegation-only</strong></span></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dt>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<dd>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Turn on enforcement of delegation-only in TLDs
608c08fec9e45832e66649bbdb219c25167e654aTinderbox User (top level domains) and root zones with an optional
1d4f4d2db2d69e48fec2dde5c1535853677d22a7Automatic Updater exclude list.
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater </p>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater DS queries are expected to be made to and be answered by
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater delegation only zones. Such queries and responses are
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews treated as an exception to delegation-only processing
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews and are not converted to NXDOMAIN responses provided
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews a CNAME is not discovered at the query name.
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User </p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<p>
e80c7005e3d59dfeb04dad186d36f3c15622954cTinderbox User If a delegation only zone server also serves a child
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews zone it is not always possible to determine whether
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User an answer comes from the delegation only zone or the
02b3e44a996e9753d86306b6a1b6b579a73787fcTinderbox User child zone. SOA NS and DNSKEY records are apex
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater only records and a matching response that contains
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater these records or DS is treated as coming from a
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews child zone. RRSIG records are also examined to see
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews if they are signed by a child zone or not. The
53b97c9873a923f504893d1e2ab62000dfac221fTinderbox User authority section is also examined to see if there
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews is evidence that the answer is from the child zone.
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater Answers that are determined to be from a child zone
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater are not converted to NXDOMAIN responses. Despite
8c6328ab5890aa79d84b86ed672e185dc111bb68Automatic Updater all these checks there is still a possibility of
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User false negatives when a child zone is being served.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater Similarly false positives can arise from empty nodes
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews (no records at the name) in the delegation only zone
f89eb76a7516649f8717c6397fc496ca906ddb57Tinderbox User when the query type is not ANY.
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews </p>
cd34c1adb0fa2120327fc8c11cda0d4a5f722aeeTinderbox User<p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User Note some TLDs are not delegation only (e.g. "DE", "LV",
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews "US" and "MUSEUM"). This list is not exhaustive.
c74518d655c1c563060f49569dce71e4a00f5f4eTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updateroptions {
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews root-delegation-only exclude { "de"; "lv"; "us"; "museum"; };
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater};
53b97c9873a923f504893d1e2ab62000dfac221fTinderbox User</pre>
e8c42d50cdaf3a3b841074d8bf72b40ffbae2a4bTinderbox User</dd>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<dt><span class="term"><span><strong class="command">disable-algorithms</strong></span></span></dt>
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ca904804e43f663f08eb1ac9d6d617930b9a3cd3Automatic Updater Disable the specified DNSSEC algorithms at and below the
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User specified name.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Multiple <span><strong class="command">disable-algorithms</strong></span>
713a5e3080f112b3efde9235e9c92035056ff966Automatic Updater statements are allowed.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater Only the best match <span><strong class="command">disable-algorithms</strong></span>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews clause will be used to determine which algorithms are used.
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User </p>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If all supported algorithms are disabled, the zones covered
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews by the <span><strong class="command">disable-algorithms</strong></span> will be treated
f8b9948a4116226ac41b5509cca152849006c66cAutomatic Updater as insecure.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
be46cb4bee9253ee4832340c719920642e00c41aTinderbox User</dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">disable-ds-digests</strong></span></span></dt>
c243d779731a410f8dc2d2feeed20c15f299b6e3Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater Disable the specified DS/DLV digest types at and below the
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater specified name.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User Multiple <span><strong class="command">disable-ds-digests</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statements are allowed.
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater Only the best match <span><strong class="command">disable-ds-digests</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater clause will be used to determine which digest types are used.
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater </p>
02b3e44a996e9753d86306b6a1b6b579a73787fcTinderbox User<p>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater If all supported digest types are disabled, the zones covered
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater by the <span><strong class="command">disable-ds-digests</strong></span> will be treated
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews as insecure.
f22980c16f244b7d7f33b5248f2d38bd4885f108Automatic Updater </p>
e20309353e6246485c521278131d3fced73d7957Tinderbox User</dd>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews<dt><span class="term"><span><strong class="command">dnssec-lookaside</strong></span></span></dt>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User<dd>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User When set, <span><strong class="command">dnssec-lookaside</strong></span> provides the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater validator with an alternate method to validate DNSKEY
d630ef2ff74445949a482660938e9fa9da52ca14Automatic Updater records at the top of a zone. When a DNSKEY is at or
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User below a domain specified by the deepest
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span><strong class="command">dnssec-lookaside</strong></span>, and the normal DNSSEC
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews validation has left the key untrusted, the trust-anchor
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater will be appended to the key name and a DLV record will be
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User looked up to see if it can validate the key. If the DLV
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User record validates a DNSKEY (similarly to the way a DS
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User record does) the DNSKEY RRset is deemed to be trusted.
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User If <span><strong class="command">dnssec-lookaside</strong></span> is set to
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews <strong class="userinput"><code>auto</code></strong>, then built-in default
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews values for the DLV domain and trust anchor will be
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User used, along with a built-in key for validation.
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews </p>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User If <span><strong class="command">dnssec-lookaside</strong></span> is set to
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <strong class="userinput"><code>no</code></strong>, then dnssec-lookaside
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User is not used.
e20309353e6246485c521278131d3fced73d7957Tinderbox User </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User The default DLV key is stored in the file
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <code class="filename">bind.keys</code>;
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span><strong class="command">named</strong></span> will load that key at
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews startup if <span><strong class="command">dnssec-lookaside</strong></span> is set to
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <code class="constant">auto</code>. A copy of the file is
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User installed along with <acronym class="acronym">BIND</acronym> 9, and is
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User current as of the release date. If the DLV key expires, a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater new copy of <code class="filename">bind.keys</code> can be downloaded
90b25b84f037ec923efaee84d2c0dc599293d04eTinderbox User from <a href="https://www.isc.org/solutions/dlv/" target="_top">https://www.isc.org/solutions/dlv/</a>.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews (To prevent problems if <code class="filename">bind.keys</code> is
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews not found, the current key is also compiled in to
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span><strong class="command">named</strong></span>. Relying on this is not
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews recommended, however, as it requires <span><strong class="command">named</strong></span>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User to be recompiled with a new key when the DLV key expires.)
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User NOTE: <span><strong class="command">named</strong></span> only loads certain specific
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User keys from <code class="filename">bind.keys</code>: those for the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater DLV zone and for the DNS root zone. The file cannot be
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater used to store keys for other zones.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User</dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">dnssec-must-be-secure</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User Specify hierarchies which must be or may not be secure
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater (signed and validated). If <strong class="userinput"><code>yes</code></strong>,
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User then <span><strong class="command">named</strong></span> will only accept answers if
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater they are secure. If <strong class="userinput"><code>no</code></strong>, then normal
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User DNSSEC validation applies allowing for insecure answers to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater be accepted. The specified domain must be under a
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <span><strong class="command">trusted-keys</strong></span> or
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">managed-keys</strong></span> statement, or
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span><strong class="command">dnssec-lookaside</strong></span> must be active.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<dt><span class="term"><span><strong class="command">dns64</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
f89eb76a7516649f8717c6397fc496ca906ddb57Tinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This directive instructs <span><strong class="command">named</strong></span> to
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews return mapped IPv4 addresses to AAAA queries when
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater there are no AAAA records. It is intended to be
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User used in conjunction with a NAT64. Each
a61158fed2e0281a40e3e97e0b7c3f9789a07b4eTinderbox User <span><strong class="command">dns64</strong></span> defines one DNS64 prefix.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User Multiple DNS64 prefixes can be defined.
a61158fed2e0281a40e3e97e0b7c3f9789a07b4eTinderbox User </p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Compatible IPv6 prefixes have lengths of 32, 40, 48, 56,
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater 64 and 96 as per RFC 6052.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
59b277af9d9aac08d16be63aed5ae60ac9eef0d5Automatic Updater Additionally a reverse IP6.ARPA zone will be created for
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User the prefix to provide a mapping from the IP6.ARPA names
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to the corresponding IN-ADDR.ARPA names using synthesized
a1788473b239588464bdeac4ab9f3fbcae959450Tinderbox User CNAMEs. <span><strong class="command">dns64-server</strong></span> and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">dns64-contact</strong></span> can be used to specify
c7f4dfc8decb44451cff27ef160d539d4954dc31Tinderbox User the name of the server and contact for the zones. These
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater are settable at the view / options level. These are
f34958b7669dfca333cc0cd20113b1f55a89e1deTinderbox User not settable on a per-prefix basis.
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews Each <span><strong class="command">dns64</strong></span> supports an optional
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <span><strong class="command">clients</strong></span> ACL that determines which
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews clients are affected by this directive. If not defined,
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater it defaults to <strong class="userinput"><code>any;</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews Each <span><strong class="command">dns64</strong></span> supports an optional
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <span><strong class="command">mapped</strong></span> ACL that selects which
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv4 addresses are to be mapped in the corresponding
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater A RRset. If not defined it defaults to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <strong class="userinput"><code>any;</code></strong>.
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater Normally, DNS64 won't apply to a domain name that
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater owns one or more AAAA records; these records will
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater simply be returned. The optional
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">exclude</strong></span> ACL allows specification
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater of a list of IPv6 addresses that will be ignored
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater if they appear in a domain name's AAAA records, and
c762a0e4141c8eb9d7567c614cf6dde994f6a76dTinderbox User DNS64 will be applied to any A records the domain
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater name owns. If not defined, <span><strong class="command">exclude</strong></span>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews defaults to none.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews A optional <span><strong class="command">suffix</strong></span> can also
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater be defined to set the bits trailing the mapped
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv4 address bits. By default these bits are
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User set to <strong class="userinput"><code>::</code></strong>. The bits
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User matching the prefix and mapped IPv4 address
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater must be zero.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
3f616e6f846be57b1717c6beaba0f74de9d5a7c6Automatic Updater<p>
1b670d35282f1b9352692ad212be3c0aa97b0689Automatic Updater If <span><strong class="command">recursive-only</strong></span> is set to
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <span><strong class="command">yes</strong></span> the DNS64 synthesis will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater only happen for recursive queries. The default
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater is <span><strong class="command">no</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <span><strong class="command">break-dnssec</strong></span> is set to
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <span><strong class="command">yes</strong></span> the DNS64 synthesis will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater happen even if the result, if validated, would
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater cause a DNSSEC validation failure. If this option
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater is set to <span><strong class="command">no</strong></span> (the default), the DO
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater is set on the incoming query, and there are RRSIGs on
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the applicable records, then synthesis will not happen.
1f4c645185bd8fc70048e0a69eee46193a284e5cTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User acl rfc1918 { 10/8; 192.168/16; 172.16/12; };
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User dns64 64:FF9B::/96 {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater clients { any; };
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User mapped { !rfc1918; any; };
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater exclude { 64:FF9B::/96; ::ffff:0000:0000/96; };
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User suffix ::;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater };
324a8797b46d646fe8d3b2eef6785e0b2b3ac956Tinderbox User</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">dnssec-update-mode</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
79b627f399ce925988bb326315e6742d5316cb6bTinderbox User<p>
79b627f399ce925988bb326315e6742d5316cb6bTinderbox User If this option is set to its default value of
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <code class="literal">maintain</code> in a zone of type
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="literal">master</code> which is DNSSEC-signed
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater and configured to allow dynamic updates (see
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>), and
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User if <span><strong class="command">named</strong></span> has access to the
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User private signing key(s) for the zone, then
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <span><strong class="command">named</strong></span> will automatically sign all new
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater or changed records and maintain signatures for the zone
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User by regenerating RRSIG records whenever they approach
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater their expiration date.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User If the option is changed to <code class="literal">no-resign</code>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater then <span><strong class="command">named</strong></span> will sign all new or
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User changed records, but scheduled maintenance of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater signatures is disabled.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User With either of these settings, <span><strong class="command">named</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater will reject updates to a DNSSEC-signed zone when the
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater signing keys are inactive or unavailable to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">named</strong></span>. (A planned third option,
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater <code class="literal">external</code>, will disable all automatic
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater signing and allow DNSSEC data to be submitted into a zone
324a8797b46d646fe8d3b2eef6785e0b2b3ac956Tinderbox User via dynamic update; this is not yet implemented.)
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">nta-lifetime</strong></span></span></dt>
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User Species the default lifetime, in seconds,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater that will be used for negative trust anchors added
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater via <span><strong class="command">rndc nta</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater A negative trust anchor selectively disables
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User DNSSEC validation for zones that are known to be
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater failing because of misconfiguration rather than
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User an attack. When data to be validated is
402eda3e7d4254ffac1543bf2917c71248a09e4cTinderbox User at or below an active NTA (and above any other
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User configured trust anchors), <span><strong class="command">named</strong></span> will
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User abort the DNSSEC validation process and treat the data as
b4846627b60aff904d523a433b44482b3b1825a7Tinderbox User insecure rather than bogus. This continues until the
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User NTA's lifetime is elapsed. NTAs persist
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User across <span><strong class="command">named</strong></span> restarts.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<p>
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User For convenience, TTL-style time unit suffixes can be
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater used to specify the NTA lifetime in seconds, minutes
0d3490f93bb980fde704055e74c1b508987a5fe4Mark Andrews or hours. <code class="option">nta-lifetime</code> defaults to
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User one hour. It cannot exceed one week.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews</dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="term"><span><strong class="command">nta-recheck</strong></span></span></dt>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dd>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
114f7780384371121918624ae2c80ecfce545683Tinderbox User Species how often to check whether negative
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater trust anchors added via <span><strong class="command">rndc nta</strong></span>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater are still necessary.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
49ab13eefc8841ea42865ae09d5a2f760577089eTinderbox User<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User A negative trust anchor is normally used when a
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User domain has stopped validating due to operator error;
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User it temporarily disables DNSSEC validation for that
f7369b2881b5e63d69600adcedc8ba938303d30cTinderbox User domain. In the interest of ensuring that DNSSEC
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User validation is turned back on as soon as possible,
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <span><strong class="command">named</strong></span> will periodically send a
7ca715ad1587a68a531ea1cdea07515d7232567eTinderbox User query to the domain, ignoring negative trust anchors,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews to find out whether it can now be validated. If so,
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User the negative trust anchor is allowed to expire early.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User Validity checks can be disabled for an individual
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User NTA by using <span><strong class="command">rndc nta -f</strong></span>, or
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews for all NTAs by setting <code class="option">nta-recheck</code>
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User to zero.
114f7780384371121918624ae2c80ecfce545683Tinderbox User </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
42c81cf2de732ec6d00e73fc755a399ca037e543Mark Andrews For convenience, TTL-style time unit suffixes can be
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User used to specify the NTA recheck interval in seconds,
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User minutes or hours. The default is five minutes. It
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User cannot be longer than <code class="option">nta-lifetime</code>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User (which cannot be longer than a week).
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater</dd>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<dt><span class="term"><span><strong class="command">max-zone-ttl</strong></span></span></dt>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews<dd>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews<p>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews Specifies a maximum permissible TTL value in seconds.
7d704e522860496310bb29c28e76064868401a9cMark Andrews For convenience, TTL-style time unit suffixes may be
7d704e522860496310bb29c28e76064868401a9cMark Andrews used to specify the maximum value.
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews When loading a zone file using a
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <code class="option">masterfile-format</code> of
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <code class="constant">text</code> or <code class="constant">raw</code>,
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater any record encountered with a TTL higher than
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <code class="option">max-zone-ttl</code> will cause the zone to
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater be rejected.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater This is useful in DNSSEC-signed zones because when
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater rolling to a new DNSKEY, the old key needs to remain
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater available until RRSIG records have expired from
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater caches. The <code class="option">max-zone-ttl</code> option guarantees
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater that the largest TTL in the zone will be no higher
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater than the set value.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User (NOTE: Because <code class="constant">map</code>-format files
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User load directly into memory, this option cannot be
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User used with them.)
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User The default value is <code class="constant">unlimited</code>.
da24e725ff982595d74da7e75e9fbd6a696367ccAutomatic Updater A <code class="option">max-zone-ttl</code> of zero is treated as
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <code class="constant">unlimited</code>.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User</dd>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews<dd>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User<p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater If <strong class="userinput"><code>full</code></strong>, the server will collect
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews statistical data on all zones (unless specifically
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson turned off on a per-zone basis by specifying
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">zone-statistics terse</strong></span> or
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">zone-statistics none</strong></span>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews in the <span><strong class="command">zone</strong></span> statement).
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews The default is <strong class="userinput"><code>terse</code></strong>, providing
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews minimal statistics on zones (including name and
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews current serial number, but not query type
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson counters).
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews These statistics may be accessed via the
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">statistics-channel</strong></span> or
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox User using <span><strong class="command">rndc stats</strong></span>, which
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User will dump them to the file listed
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User in the <span><strong class="command">statistics-file</strong></span>. See
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater also <a href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called &#8220;The Statistics File&#8221;</a>.
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews </p>
90cde4c188ac5bdea4f402b241c387c9cc9d4cc4Tinderbox User<p>
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User For backward compatibility with earlier versions
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater of BIND 9, the <span><strong class="command">zone-statistics</strong></span>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User option can also accept <strong class="userinput"><code>yes</code></strong>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater or <strong class="userinput"><code>no</code></strong>; <strong class="userinput"><code>yes</code></strong>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User has the same meaning as <strong class="userinput"><code>full</code></strong>.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews As of <acronym class="acronym">BIND</acronym> 9.10,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <strong class="userinput"><code>no</code></strong> has the same meaning
4c9f230f7ca5b2b08ea8fd7a6944135801dbe152Tinderbox User as <strong class="userinput"><code>none</code></strong>; previously, it
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater was the same as <strong class="userinput"><code>terse</code></strong>.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater</dd>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater</dl></div>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<div class="sect3" lang="en">
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<div class="titlepage"><div><div><h4 class="title">
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<a name="boolean_options"></a>Boolean Options</h4></div></div></div>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<div class="variablelist"><dl>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dt><span class="term"><span><strong class="command">automatic-interface-scan</strong></span></span></dt>
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews<dd>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User If <strong class="userinput"><code>yes</code></strong> and supported by the OS,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User automatically rescan network interfaces when the interface
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User addresses are added or removed. The default is
603cf17f33da24d460616389ec40d6f2a6e110a0Automatic Updater <strong class="userinput"><code>yes</code></strong>.
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User </p>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater Currently the OS needs to support routing sockets for
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <span><strong class="command">automatic-interface-scan</strong></span> to be
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews supported.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User</dd>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<dt><span class="term"><span><strong class="command">allow-new-zones</strong></span></span></dt>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then zones can be
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User added at runtime via <span><strong class="command">rndc addzone</strong></span>.
b5423cbff7175727ed9046c8c670d8a7bb4d01eaTinderbox User The default is <strong class="userinput"><code>no</code></strong>.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">auth-nxdomain</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then the <span><strong class="command">AA</strong></span> bit
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User is always set on NXDOMAIN responses, even if the server is
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User not actually
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User authoritative. The default is <strong class="userinput"><code>no</code></strong>;
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User this is
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User a change from <acronym class="acronym">BIND</acronym> 8. If you
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews are using very old DNS software, you
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User may need to set it to <strong class="userinput"><code>yes</code></strong>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="term"><span><strong class="command">deallocate-on-exit</strong></span></span></dt>
365bb6f27eace1836cb5bc6b5f9ed8c88fe22e4aTinderbox User<dd><p>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User This option was used in <acronym class="acronym">BIND</acronym>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews 8 to enable checking
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews for memory leaks on exit. <acronym class="acronym">BIND</acronym> 9 ignores the option and always performs
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater the checks.
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </p></dd>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<dt><span class="term"><span><strong class="command">memstatistics</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews Write memory statistics to the file specified by
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">memstatistics-file</strong></span> at exit.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User The default is <strong class="userinput"><code>no</code></strong> unless
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater '-m record' is specified on the command line in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater which case it is <strong class="userinput"><code>yes</code></strong>.
b5423cbff7175727ed9046c8c670d8a7bb4d01eaTinderbox User </p></dd>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then the
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User server treats all zones as if they are doing zone transfers
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater across
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater a dial-on-demand dialup link, which can be brought up by
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews traffic
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews originating from this server. This has different effects
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater according
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews to zone type and concentrates the zone maintenance so that
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews it all
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews 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
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the normal
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater zone maintenance traffic. The default is <strong class="userinput"><code>no</code></strong>.
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
83d29eff2912ef967596eb5ed148de7668b35564Automatic 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
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <span><strong class="command">zone</strong></span> statements,
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User in which case it overrides the global <span><strong class="command">dialup</strong></span>
71bd43eebd9d6e42dbcae62b730f5b6508d5acd8Automatic Updater option.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User If the zone is a master zone, then the server will send out a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater NOTIFY
098097efb95046a4a5285b6dae95dea3e3b70853Automatic Updater request to all the slaves (default). This should trigger the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater zone serial
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater number check in the slave (providing it supports NOTIFY)
78bc8fdc2488c92d7228e8de19827e2c114c56caAutomatic Updater allowing the slave
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to verify the zone while the connection is active.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The set of servers to which NOTIFY is sent can be controlled
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater by
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews <span><strong class="command">notify</strong></span> and <span><strong class="command">also-notify</strong></span>.
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User </p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If the
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User zone is a slave or stub zone, then the server will suppress
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the regular
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User "zone up to date" (refresh) queries and only perform them
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater when the
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater <span><strong class="command">heartbeat-interval</strong></span> expires in
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater addition to sending
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews NOTIFY requests.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
e705db6d5d886dc14f4a75a2046a075c0750e7eeAutomatic Updater<p>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater Finer control can be achieved by using
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <strong class="userinput"><code>notify</code></strong> which only sends NOTIFY
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater messages,
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User <strong class="userinput"><code>notify-passive</code></strong> which sends NOTIFY
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater messages and
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews suppresses the normal refresh queries, <strong class="userinput"><code>refresh</code></strong>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews which suppresses normal refresh processing and sends refresh
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User queries
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User when the <span><strong class="command">heartbeat-interval</strong></span>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User expires, and
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User <strong class="userinput"><code>passive</code></strong> which just disables normal
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater refresh
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews processing.
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews </p>
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User<div class="informaltable"><table border="1">
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<colgroup>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<col>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<col>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews<col>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<col>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</colgroup>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tbody>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<tr>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<td>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt <p>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt dialup mode
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt </p>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt </td>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<td>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt <p>
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User normal refresh
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </td>
2bb3422dc683c013db7042f5736240de6b86f182Automatic Updater<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater heart-beat refresh
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User heart-beat notify
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<tr>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">no</strong></span> (default)</p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User yes
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User no
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
4cde88fbf4c5e78a785d40f364cdcf60f3575f0cTinderbox User no
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
1ac49378a458420bc685293d12e567d7222d17b6Tinderbox User<tr>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<td>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User <p><span><strong class="command">yes</strong></span></p>
681beefc668253b3e469a1de282fbc33a3752422Automatic Updater </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User no
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
b16e2045ac28229c31f1ea3ebad15cbcb13e1d24Automatic Updater </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
b3386fba31414344f38f0c30849c056dceb22dceTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User yes
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
4cde88fbf4c5e78a785d40f364cdcf60f3575f0cTinderbox User yes
71bfd0968456cc0c69fd400d2dafd02977c649d2Tinderbox User </p>
83e281baf1b4149dc637d24dd41141129ae712c6Tinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td>
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User <p><span><strong class="command">notify</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater yes
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User no
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User yes
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User</tr>
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User<tr>
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User<td>
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User <p><span><strong class="command">refresh</strong></span></p>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </td>
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User<td>
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews <p>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews no
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<td>
b6e12209e3e7df826f5f8f949ad400ec6d1f6371Tinderbox User <p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User yes
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
d3ba57ed92b7095fdeabc444af5dd18ac4781064Tinderbox User <p>
6c910bd5e4a85a56e3a61fdf7b237a45bb2553eeTinderbox User no
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
049728912c39135db248f9b48f8f26675f456e9dTinderbox User </td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User</tr>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<tr>
fd0f3e7cd8bc0e7fd08cc81ceb6ced861b706c97Mark Andrews<td>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews <p><span><strong class="command">passive</strong></span></p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User <p>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews no
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </td>
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User no
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User no
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span><strong class="command">notify-passive</strong></span></p>
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <p>
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater no
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews </td>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<td>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt <p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User no
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt yes
ce0fd07045292942bfa3e755d9ce596941528a63Automatic Updater </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater</tr>
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User</tbody>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</table></div>
96713299d08c0735c18ebe8772dd2cc1ecd4356aAutomatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Note that normal NOTIFY processing is not affected by
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews <span><strong class="command">dialup</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater</dd>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User<dt><span class="term"><span><strong class="command">fake-iquery</strong></span></span></dt>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<dd><p>
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater In <acronym class="acronym">BIND</acronym> 8, this option
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews enabled simulating the obsolete DNS query type
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews IQUERY. <acronym class="acronym">BIND</acronym> 9 never does
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User IQUERY simulation.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<dt><span class="term"><span><strong class="command">fetch-glue</strong></span></span></dt>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<dd><p>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User This option is obsolete.
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User In BIND 8, <strong class="userinput"><code>fetch-glue yes</code></strong>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews caused the server to attempt to fetch glue resource records
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater it
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater didn't have when constructing the additional
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater data section of a response. This is now considered a bad
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater idea
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and BIND 9 never does it.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">flush-zones-on-shutdown</strong></span></span></dt>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater<dd><p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews When the nameserver exits due receiving SIGTERM,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater flush or do not flush any pending zone writes. The default
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater is
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater <span><strong class="command">flush-zones-on-shutdown</strong></span> <strong class="userinput"><code>no</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">geoip-use-ecs</strong></span></span></dt>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews<dd><p>
0ead2ac0a4b59c3e4a731027f0f66fbe602b1289Tinderbox User When BIND is compiled with GeoIP support and configured
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User with "geoip" ACL elements, this option indicates whether
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the EDNS Client Subnet option, if present in a request,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater should be used for matching against the GeoIP database.
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews The default is
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews <span><strong class="command">geoip-use-ecs</strong></span> <strong class="userinput"><code>yes</code></strong>.
78bc8fdc2488c92d7228e8de19827e2c114c56caAutomatic Updater </p></dd>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<dt><span class="term"><span><strong class="command">has-old-clients</strong></span></span></dt>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<dd><p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User This option was incorrectly implemented
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in <acronym class="acronym">BIND</acronym> 8, and is ignored by <acronym class="acronym">BIND</acronym> 9.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater To achieve the intended effect
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater of
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews <span><strong class="command">has-old-clients</strong></span> <strong class="userinput"><code>yes</code></strong>, specify
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews the two separate options <span><strong class="command">auth-nxdomain</strong></span> <strong class="userinput"><code>yes</code></strong>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson and <span><strong class="command">rfc2308-type1</strong></span> <strong class="userinput"><code>no</code></strong> instead.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p></dd>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<dt><span class="term"><span><strong class="command">host-statistics</strong></span></span></dt>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<dd><p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews In BIND 8, this enables keeping of
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews statistics for every host that the name server interacts
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews with.
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User Not implemented in BIND 9.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p></dd>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="term"><span><strong class="command">maintain-ixfr-base</strong></span></span></dt>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<dd><p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <span class="emphasis"><em>This option is obsolete</em></span>.
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt It was used in <acronym class="acronym">BIND</acronym> 8 to
e705db6d5d886dc14f4a75a2046a075c0750e7eeAutomatic Updater determine whether a transaction log was
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User kept for Incremental Zone Transfer. <acronym class="acronym">BIND</acronym> 9 maintains a transaction
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User log whenever possible. If you need to disable outgoing
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews incremental zone
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater transfers, use <span><strong class="command">provide-ixfr</strong></span> <strong class="userinput"><code>no</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">minimal-responses</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews If <strong class="userinput"><code>yes</code></strong>, then when generating
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater responses the server will only add records to the authority
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and additional data sections when they are required (e.g.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews delegations, negative responses). This may improve the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User performance of the server.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The default is <strong class="userinput"><code>no</code></strong>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
40696c4c389a780082fb77840c173b201ce696d6Automatic Updater<dt><span class="term"><span><strong class="command">multiple-cnames</strong></span></span></dt>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User This option was used in <acronym class="acronym">BIND</acronym> 8 to allow
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User a domain name to have multiple CNAME records in violation of
40696c4c389a780082fb77840c173b201ce696d6Automatic Updater the DNS standards. <acronym class="acronym">BIND</acronym> 9.2 onwards
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User always strictly enforces the CNAME rules both in master
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater files and dynamic updates.
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User </p></dd>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="term"><span><strong class="command">notify</strong></span></span></dt>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User If <strong class="userinput"><code>yes</code></strong> (the default),
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User DNS NOTIFY messages are sent when a zone the server is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater authoritative for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater changes, see <a href="Bv9ARM.ch04.html#notify" title="Notify">the section called &#8220;Notify&#8221;</a>. The messages are
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User sent to the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater servers listed in the zone's NS records (except the master
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater server identified
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in the SOA MNAME field), and to any servers listed in the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">also-notify</strong></span> option.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>master-only</code></strong>, notifies are only
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater sent
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User for master zones.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>explicit</code></strong>, notifies are sent only
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater servers explicitly listed using <span><strong class="command">also-notify</strong></span>.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User If <strong class="userinput"><code>no</code></strong>, no notifies are sent.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater The <span><strong class="command">notify</strong></span> option may also be
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson specified in the <span><strong class="command">zone</strong></span>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews statement,
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson in which case it overrides the <span><strong class="command">options notify</strong></span> statement.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews It would only be necessary to turn off this option if it
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews caused slaves
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews to crash.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews<dt><span class="term"><span><strong class="command">notify-to-soa</strong></span></span></dt>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<dd><p>
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User If <strong class="userinput"><code>yes</code></strong> do not check the nameservers
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater in the NS RRset against the SOA MNAME. Normally a NOTIFY
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User message is not sent to the SOA MNAME (SOA ORIGIN) as it is
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User supposed to contain the name of the ultimate master.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews Sometimes, however, a slave is listed as the SOA MNAME in
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews hidden master configurations and in that case you would
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater want the ultimate master to still send NOTIFY messages to
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews all the nameservers listed in the NS RRset.
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater </p></dd>
e5fe07a7ebff18f7ed4ac434b37daff6c8ee5d5bAutomatic Updater<dt><span class="term"><span><strong class="command">recursion</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, and a
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User DNS query requests recursion, then the server will attempt
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User to do
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater all the work required to answer the query. If recursion is
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater off
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews and the server does not already know the answer, it will
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews return a
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson referral response. The default is
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <strong class="userinput"><code>yes</code></strong>.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Note that setting <span><strong class="command">recursion no</strong></span> does not prevent
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews clients from getting data from the server's cache; it only
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews prevents new data from being cached as an effect of client
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater queries.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Caching may still occur as an effect the server's internal
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User operation, such as NOTIFY address lookups.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User See also <span><strong class="command">fetch-glue</strong></span> above.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p></dd>
a900e4f99ff134b567b6df5ac2c841c7d0c551d3Automatic Updater<dt><span class="term"><span><strong class="command">request-nsid</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User If <strong class="userinput"><code>yes</code></strong>, then an empty EDNS(0)
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User NSID (Name Server Identifier) option is sent with all
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User queries to authoritative name servers during iterative
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews resolution. If the authoritative server returns an NSID
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User option in its response, then its contents are logged in
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User the <span><strong class="command">resolver</strong></span> category at level
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">info</strong></span>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The default is <strong class="userinput"><code>no</code></strong>.
a900e4f99ff134b567b6df5ac2c841c7d0c551d3Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">request-sit</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">require-server-cookie</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">send-cookie</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then a COOKIE EDNS
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater option is sent along with the query. If the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater resolver has previously talked to the server, the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater COOKIE returned in the previous transaction is sent.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This is used by the server to determine whether
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the resolver has talked to it before. A resolver
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User sending the correct COOKIE is assumed not to be an
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User off-path attacker sending a spoofed-source query;
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User the query is therefore unlikely to be part of a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater reflection/amplification attack, so resolvers
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User sending a correct COOKIE option are not subject to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater response rate limiting (RRL). Resolvers which
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews do not send a correct COOKIE option may be limited
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews to receiving smaller responses via the
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">nocookie-udp-size</strong></span> option.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p></dd>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dt><span class="term"><span><strong class="command">sit-secret</strong></span></span></dt>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dd><p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews This experimental option is obsolete.
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews </p></dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="term"><span><strong class="command">cookie-algorithm</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd><p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews Set the algorithm to be used when generating the
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews server cookie. One of "aes", "sha1" or "sha256".
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews The default is "aes" if supported by the cryptographic
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews library or otherwise "sha256".
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p></dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="term"><span><strong class="command">cookie-secret</strong></span></span></dt>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<dd><p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews If set, this is a shared secret used for generating
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews and verifying Source Identity Token EDNS options
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews within an anycast cluster. If not set, the system
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews will generate a random secret at startup. The
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews shared secret is encoded as a hex string and needs
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews to be 128 bits for AES128, 160 bits for SHA1 and
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews 256 bits for SHA256.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p></dd>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<dt><span class="term"><span><strong class="command">rfc2308-type1</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews Setting this to <strong class="userinput"><code>yes</code></strong> will
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews cause the server to send NS records along with the SOA
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews record for negative
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews answers. The default is <strong class="userinput"><code>no</code></strong>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews<h3 class="title">Note</h3>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Not yet implemented in <acronym class="acronym">BIND</acronym>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews 9.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</div>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews</dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="term"><span><strong class="command">use-id-pool</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd><p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews <span class="emphasis"><em>This option is obsolete</em></span>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <acronym class="acronym">BIND</acronym> 9 always allocates query
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews IDs from a pool.
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews </p></dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="term"><span><strong class="command">use-ixfr</strong></span></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd><p>
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews <span class="emphasis"><em>This option is obsolete</em></span>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews If you need to disable IXFR to a particular server or
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews servers, see
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews the information on the <span><strong class="command">provide-ixfr</strong></span> option
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews in <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
4b2cb1422c7c600fbc13b1cb06a8b4693bc11af8Mark Andrews Usage&#8221;</a>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews 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>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
e23256e740b238bddb4ba41ffac5f81a01c92245Automatic Updater<dt><span class="term"><span><strong class="command">provide-ixfr</strong></span></span></dt>
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User See the description of
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span><strong class="command">provide-ixfr</strong></span> in
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <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>.
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p></dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="term"><span><strong class="command">request-ixfr</strong></span></span></dt>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User See the description of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span><strong class="command">request-ixfr</strong></span> in
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater Usage&#8221;</a>.
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson </p></dd>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<dt><span class="term"><span><strong class="command">request-expire</strong></span></span></dt>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<dd><p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews See the description of
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span><strong class="command">request-expire</strong></span> in
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <a href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Usage">the section called &#8220;<span><strong class="command">server</strong></span> Statement Definition and
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews Usage&#8221;</a>.
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span><strong class="command">treat-cr-as-space</strong></span></span></dt>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User<dd><p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews This option was used in <acronym class="acronym">BIND</acronym>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews 8 to make
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User the server treat carriage return ("<span><strong class="command">\r</strong></span>") characters the same way
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User as a space or tab character,
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User to facilitate loading of zone files on a UNIX system that
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User were generated
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User on an NT or DOS machine. In <acronym class="acronym">BIND</acronym> 9, both UNIX "<span><strong class="command">\n</strong></span>"
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User and NT/DOS "<span><strong class="command">\r\n</strong></span>" newlines
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User are always accepted,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User and the option is ignored.
713c3d5b18463f2479973e4d14f73248e60a5df7Mark Andrews </p></dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<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>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User</dt>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User<dd>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews These options control the behavior of an authoritative
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews server when
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews answering queries which have additional data, or when
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews following CNAME
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews and DNAME chains.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater When both of these options are set to <strong class="userinput"><code>yes</code></strong>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews (the default) and a
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson query is being answered from authoritative data (a zone
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews configured into the server), the additional data section of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews reply will be filled in using data from other authoritative
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User zones
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews and from the cache. In some situations this is undesirable,
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews such
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews as when there is concern over the correctness of the cache,
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews or
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews in servers where slave zones may be added and modified by
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews untrusted third parties. Also, avoiding
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews the search for this additional data will speed up server
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User operations
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User at the possible expense of additional queries to resolve
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews what would
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User otherwise be provided in the additional section.
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </p>
922e6a3c2ac4ef900dd9dc99f0cc137f18372583Andreas Gustafsson<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User For example, if a query asks for an MX record for host <code class="literal">foo.example.com</code>,
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User and the record found is "<code class="literal">MX 10 mail.example.net</code>", normally the address
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User records (A and AAAA) for <code class="literal">mail.example.net</code> will be provided as well,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User if known, even though they are not in the example.com zone.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Setting these options to <span><strong class="command">no</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User disables this behavior and makes
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the server only search for additional data in the zone it
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User answers from.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User These options are intended for use in authoritative-only
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews servers, or in authoritative-only views. Attempts to set
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User them to <span><strong class="command">no</strong></span> without also
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User specifying
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">recursion no</strong></span> will cause the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User server to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User ignore the options and log a warning message.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifying <span><strong class="command">additional-from-cache no</strong></span> actually
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User disables the use of the cache not only for additional data
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User lookups
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews but also when looking up the answer. This is usually the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews desired
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User behavior in an authoritative-only server where the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User correctness of
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the cached data is an issue.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews When a name server is non-recursively queried for a name
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User that is not
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User below the apex of any served zone, it normally answers with
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User an
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User "upwards referral" to the root servers or the servers of
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews some other
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews known parent of the query name. Since the data in an
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews upwards referral
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews comes from the cache, the server will not be able to provide
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews upwards
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User referrals when <span><strong class="command">additional-from-cache no</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User has been specified. Instead, it will respond to such
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User queries
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User with REFUSED. This should not cause any problems since
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User upwards referrals are not required for the resolution
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User process.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">match-mapped-addresses</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <strong class="userinput"><code>yes</code></strong>, then an
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User IPv4-mapped IPv6 address will match any address match
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User list entries that match the corresponding IPv4 address.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This option was introduced to work around a kernel quirk
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User in some operating systems that causes IPv4 TCP
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User connections, such as zone transfers, to be accepted on an
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User IPv6 socket using mapped addresses. This caused address
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User match lists designed for IPv4 to fail to match. However,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">named</strong></span> now solves this problem
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User internally. The use of this option is discouraged.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">filter-aaaa-on-v4</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This option is only available when
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <acronym class="acronym">BIND</acronym> 9 is compiled with the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <strong class="userinput"><code>--enable-filter-aaaa</code></strong> option on the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User "configure" command line. It is intended to help the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User transition from IPv4 to IPv6 by not giving IPv6 addresses
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater to DNS clients unless they have connections to the IPv6
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Internet. This is not recommended unless absolutely
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User necessary. The default is <strong class="userinput"><code>no</code></strong>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The <span><strong class="command">filter-aaaa-on-v4</strong></span> option
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User may also be specified in <span><strong class="command">view</strong></span> statements
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to override the global <span><strong class="command">filter-aaaa-on-v4</strong></span>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews option.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <strong class="userinput"><code>yes</code></strong>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the DNS client is at an IPv4 address, in <span><strong class="command">filter-aaaa</strong></span>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User and if the response does not include DNSSEC signatures,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User then all AAAA records are deleted from the response.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This filtering applies to all responses and not only
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User authoritative responses.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <strong class="userinput"><code>break-dnssec</code></strong>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User then AAAA records are deleted even when DNSSEC is enabled.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User As suggested by the name, this makes the response not verify,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User because the DNSSEC protocol is designed detect deletions.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This mechanism can erroneously cause other servers to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User not give AAAA records to their clients.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User A recursing server with both IPv6 and IPv4 network connections
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User that queries an authoritative server using this mechanism
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews via IPv4 will be denied AAAA records even if its client is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User using IPv6.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews This mechanism is applied to authoritative as well as
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews non-authoritative records.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User A client using IPv4 that is not allowed recursion can
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User erroneously be given AAAA records because the server is not
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User allowed to check for A records.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Some AAAA records are given to IPv4 clients in glue records.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User IPv4 clients that are servers can then erroneously
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User answer requests for AAAA records received via IPv4.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">filter-aaaa-on-v6</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Identical to <span><strong class="command">filter-aaaa-on-v4</strong></span>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User except it filters AAAA responses to queries from IPv6
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews clients instead of IPv4 clients. To filter all
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User responses, set both options to <strong class="userinput"><code>yes</code></strong>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User When <strong class="userinput"><code>yes</code></strong> and the server loads a new
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User version of a master zone from its zone file or receives a
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User new version of a slave file via zone transfer, it will
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User compare the new version to the previous one and calculate
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User a set of differences. The differences are then logged in
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the zone's journal file such that the changes can be
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User transmitted to downstream slaves as an incremental zone
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User transfer.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
d3be47a4a841ca6fc07e8f18004cf72174e2d117Tinderbox User By allowing incremental zone transfers to be used for
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User non-dynamic zones, this option saves bandwidth at the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User expense of increased CPU and memory consumption at the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User master.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User In particular, if the new version of a zone is completely
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User different from the previous one, the set of differences
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User will be of a size comparable to the combined size of the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User old and new zone version, and the server will need to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User temporarily allocate memory to hold this complete
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User difference set.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p><span><strong class="command">ixfr-from-differences</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User also accepts <span><strong class="command">master</strong></span> and
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">slave</strong></span> at the view and options
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User levels which causes
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">ixfr-from-differences</strong></span> to be enabled for
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User all <span><strong class="command">master</strong></span> or
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">slave</strong></span> zones respectively.
3d2e052eb879189e6d853097f8b568d887323bebTinderbox User It is off by default.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This should be set when you have multiple masters for a zone
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User and the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, <span><strong class="command">named</strong></span> will
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User not log
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User when the serial number on the master is less than what <span><strong class="command">named</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User currently
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User has. The default is <strong class="userinput"><code>no</code></strong>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">dnssec-enable</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This indicates whether DNSSEC-related resource
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User records are to be returned by <span><strong class="command">named</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If set to <strong class="userinput"><code>no</code></strong>,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">named</strong></span> will not return DNSSEC-related
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User resource records unless specifically queried for.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The default is <strong class="userinput"><code>yes</code></strong>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">dnssec-validation</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Enable DNSSEC validation in <span><strong class="command">named</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Note <span><strong class="command">dnssec-enable</strong></span> also needs to be
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User set to <strong class="userinput"><code>yes</code></strong> to be effective.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If set to <strong class="userinput"><code>no</code></strong>, DNSSEC validation
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is disabled. If set to <strong class="userinput"><code>auto</code></strong>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User DNSSEC validation is enabled, and a default
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User trust-anchor for the DNS root zone is used. If set to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <strong class="userinput"><code>yes</code></strong>, DNSSEC validation is enabled,
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews but a trust anchor must be manually configured using
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User a <span><strong class="command">trusted-keys</strong></span> or
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">managed-keys</strong></span> statement. The default
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is <strong class="userinput"><code>yes</code></strong>.
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>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Whenever the resolver sends out queries to an
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User EDNS-compliant server, it always sets the DO bit
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews indicating it can support DNSSEC responses even if
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">dnssec-validation</strong></span> is off.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">dnssec-accept-expired</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Accept expired signatures when verifying DNSSEC signatures.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The default is <strong class="userinput"><code>no</code></strong>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Setting this option to <strong class="userinput"><code>yes</code></strong>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User leaves <span><strong class="command">named</strong></span> vulnerable to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User replay attacks.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span><strong class="command">querylog</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Specify whether query logging should be started when <span><strong class="command">named</strong></span>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater starts.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <span><strong class="command">querylog</strong></span> is not specified,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User then the query logging
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is determined by the presence of the logging category <span><strong class="command">queries</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This option is used to restrict the character set and syntax
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User of
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User certain domain names in master files and/or DNS responses
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews received
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from the network. The default varies according to usage
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User area. For
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews For <span><strong class="command">slave</strong></span> zones the default
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is <span><strong class="command">warn</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User For answers received from the network (<span><strong class="command">response</strong></span>)
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the default is <span><strong class="command">ignore</strong></span>.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The rules for legal hostnames and mail domains are derived
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews from RFC 952 and RFC 821 as modified by RFC 1123.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p><span><strong class="command">check-names</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User applies to the owner names of A, AAAA and MX records.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User It also applies to the domain names in the RDATA of NS, SOA,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User MX, and SRV records.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater It also applies to the RDATA of PTR records where the owner
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User name indicated that it is a reverse lookup of a hostname
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User (the owner name ends in IN-ADDR.ARPA, IP6.ARPA, or IP6.INT).
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">check-dup-records</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Check master zones for records that are treated as different
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User by DNSSEC but are semantically equal in plain DNS. The
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User default is to <span><strong class="command">warn</strong></span>. Other possible
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews values are <span><strong class="command">fail</strong></span> and
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">ignore</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Check whether the MX record appears to refer to a IP address.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The default is to <span><strong class="command">warn</strong></span>. Other possible
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User values are <span><strong class="command">fail</strong></span> and
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">ignore</strong></span>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This option is used to check for non-terminal wildcards.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The use of non-terminal wildcards is almost always as a
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User result of a failure
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to understand the wildcard matching algorithm (RFC 1034).
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This option
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User affects master zones. The default (<span><strong class="command">yes</strong></span>) is to check
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User for non-terminal wildcards and issue a warning.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Perform post load zone integrity checks on master
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User zones. This checks that MX and SRV records refer
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to address (A or AAAA) records and that glue
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User address records exist for delegated zones. For
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User MX and SRV records only in-zone hostnames are
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User checked (for out-of-zone hostnames use
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span><strong class="command">named-checkzone</strong></span>).
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User For NS records only names below top of zone are
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User checked (for out-of-zone names and glue consistency
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews checks use <span><strong class="command">named-checkzone</strong></span>).
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The default is <span><strong class="command">yes</strong></span>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The use of the SPF record for publishing Sender
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Policy Framework is deprecated as the migration
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from using TXT records to SPF records was abandoned.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Enabling this option also checks that a TXT Sender
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Policy Framework record exists (starts with "v=spf1")
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User if there is an SPF record. Warnings are emitted if the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User TXT record does not exist and can be suppressed with
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews <span><strong class="command">check-spf</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">check-mx-cname</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews If <span><strong class="command">check-integrity</strong></span> is set then
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User fail, warn or ignore MX records that refer
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to CNAMES. The default is to <span><strong class="command">warn</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span><strong class="command">check-srv-cname</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <span><strong class="command">check-integrity</strong></span> is set then
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User fail, warn or ignore SRV records that refer
017d755d7a606dfb1e02a9d6e2b29e49e39fde16Tinderbox User to CNAMES. The default is to <span><strong class="command">warn</strong></span>.
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p></dd>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<dd><p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater When performing integrity checks, also check that
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater sibling glue exists. The default is <span><strong class="command">yes</strong></span>.
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">check-spf</strong></span></span></dt>
081a44bd3019b18aec03c5c0746538fdc901da48Evan Hunt<dd><p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User If <span><strong class="command">check-integrity</strong></span> is set then
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User check that there is a TXT Sender Policy Framework
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User record present (starts with "v=spf1") if there is an
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User SPF record present. The default is
be41770245bd56746fbb61f9b5ba0aca683f318eTinderbox User <span><strong class="command">warn</strong></span>.
200a9e7da827b67d99193bf793aea9f3e3fa1b43Tinderbox User </p></dd>
4c9f230f7ca5b2b08ea8fd7a6944135801dbe152Tinderbox User<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt>
af9dbf1ccdd53933aaae9300d13ce0965d39b067Evan Hunt<dd><p>
bb5fe714ce8625e6744dd84526828c36bcff12f6Tinderbox User When returning authoritative negative responses to
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User SOA queries set the TTL of the SOA record returned in
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User the authority section to zero.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User The default is <span><strong class="command">yes</strong></span>.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p></dd>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater<dt><span class="term"><span><strong class="command">zero-no-soa-ttl-cache</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User When caching a negative response to a SOA query
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User set the TTL to zero.
af9dbf1ccdd53933aaae9300d13ce0965d39b067Evan Hunt The default is <span><strong class="command">no</strong></span>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
6508846efcd15de6b43b7da44c0bfcd665947630Tinderbox User When set to the default value of <code class="literal">yes</code>,
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User check the KSK bit in each key to determine how the key
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User should be used when generating RRSIGs for a secure zone.
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews Ordinarily, zone-signing keys (that is, keys without the
7ac34650fa344f42211d6da744ae486b0145a083Tinderbox User KSK bit set) are used to sign the entire zone, while
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User key-signing keys (keys with the KSK bit set) are only
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews used to sign the DNSKEY RRset at the zone apex.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews However, if this option is set to <code class="literal">no</code>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews then the KSK bit is ignored; KSKs are treated as if they
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews were ZSKs and are used to sign the entire zone. This is
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews similar to the <span><strong class="command">dnssec-signzone -z</strong></span>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User command line option.
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User </p>
<p>
When this option is set to <code class="literal">yes</code>, there
must be at least two active keys for every algorithm
represented in the DNSKEY RRset: at least one KSK and one
ZSK per algorithm. If there is any algorithm for which
this requirement is not met, this option will be ignored
for that algorithm.
</p>
</dd>
<dt><span class="term"><span><strong class="command">dnssec-dnskey-kskonly</strong></span></span></dt>
<dd>
<p>
When this option and <span><strong class="command">update-check-ksk</strong></span>
are both set to <code class="literal">yes</code>, only key-signing
keys (that is, keys with the KSK bit set) will be used
to sign the DNSKEY RRset at the zone apex. Zone-signing
keys (keys without the KSK bit set) will be used to sign
the remainder of the zone, but not the DNSKEY RRset.
This is similar to the
<span><strong class="command">dnssec-signzone -x</strong></span> command line option.
</p>
<p>
The default is <span><strong class="command">no</strong></span>. If
<span><strong class="command">update-check-ksk</strong></span> is set to
<code class="literal">no</code>, this option is ignored.
</p>
</dd>
<dt><span class="term"><span><strong class="command">dnssec-loadkeys-interval</strong></span></span></dt>
<dd><p>
When a zone is configured with <span><strong class="command">auto-dnssec
maintain;</strong></span> its key repository must be checked
periodically to see if any new keys have been added
or any existing keys' timing metadata has been updated
(see <a href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
<a href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The
<span><strong class="command">dnssec-loadkeys-interval</strong></span> option
sets the frequency of automatic repository checks, in
minutes. The default is <code class="literal">60</code> (1 hour),
the minimum is <code class="literal">1</code> (1 minute), and the
maximum is <code class="literal">1440</code> (24 hours); any higher
value is silently reduced.
</p></dd>
<dt><span class="term"><span><strong class="command">try-tcp-refresh</strong></span></span></dt>
<dd><p>
Try to refresh the zone using TCP if UDP queries fail.
For BIND 8 compatibility, the default is
<span><strong class="command">yes</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-secure-to-insecure</strong></span></span></dt>
<dd>
<p>
Allow a dynamic zone to transition from secure to
insecure (i.e., signed to unsigned) by deleting all
of the DNSKEY records. The default is <span><strong class="command">no</strong></span>.
If set to <span><strong class="command">yes</strong></span>, and if the DNSKEY RRset
at the zone apex is deleted, all RRSIG and NSEC records
will be removed from the zone as well.
</p>
<p>
If the zone uses NSEC3, then it is also necessary to
delete the NSEC3PARAM RRset from the zone apex; this will
cause the removal of all corresponding NSEC3 records.
(It is expected that this requirement will be eliminated
in a future release.)
</p>
<p>
Note that if a zone has been configured with
<span><strong class="command">auto-dnssec maintain</strong></span> and the
private keys remain accessible in the key repository,
then the zone will be automatically signed again the
next time <span><strong class="command">named</strong></span> is started.
</p>
</dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2584654"></a>Forwarding</h4></div></div></div>
<p>
The forwarding facility can be used to create a large site-wide
cache on a few servers, reducing traffic over links to external
name servers. It can also be used to allow queries by servers that
do not have direct access to the Internet, but wish to look up
exterior
names anyway. Forwarding occurs only on those queries for which
the server is not authoritative and does not have the answer in
its cache.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">forward</strong></span></span></dt>
<dd><p>
This option is only meaningful if the
forwarders list is not empty. A value of <code class="varname">first</code>,
the default, causes the server to query the forwarders
first &#8212; and
if that doesn't answer the question, the server will then
look for
the answer itself. If <code class="varname">only</code> is
specified, the
server will only query the forwarders.
</p></dd>
<dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt>
<dd><p>
Specifies the IP addresses to be used
for forwarding. The default is the empty list (no
forwarding).
</p></dd>
</dl></div>
<p>
Forwarding can also be configured on a per-domain basis, allowing
for the global forwarding options to be overridden in a variety
of ways. You can set particular domains to use different
forwarders,
or have a different <span><strong class="command">forward only/first</strong></span> behavior,
or not forward at all, see <a href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone
Statement Grammar">the section called &#8220;<span><strong class="command">zone</strong></span>
Statement Grammar&#8221;</a>.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2584850"></a>Dual-stack Servers</h4></div></div></div>
<p>
Dual-stack servers are used as servers of last resort to work
around
problems in reachability due the lack of support for either IPv4
or IPv6
on the host machine.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">dual-stack-servers</strong></span></span></dt>
<dd><p>
Specifies host names or addresses of machines with access to
both IPv4 and IPv6 transports. If a hostname is used, the
server must be able
to resolve the name using only the transport it has. If the
machine is dual
stacked, then the <span><strong class="command">dual-stack-servers</strong></span> have no effect unless
access to a transport has been disabled on the command line
(e.g. <span><strong class="command">named -4</strong></span>).
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="access_control"></a>Access Control</h4></div></div></div>
<p>
Access to the server can be restricted based on the IP address
of the requesting system. See <a href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called &#8220;Address Match Lists&#8221;</a> for
details on how to specify IP address lists.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to
notify this server, a slave, of zone changes in addition
to the zone masters.
<span><strong class="command">allow-notify</strong></span> may also be
specified in the
<span><strong class="command">zone</strong></span> statement, in which case
it overrides the
<span><strong class="command">options allow-notify</strong></span>
statement. It is only meaningful
for a slave zone. If not specified, the default is to
process notify messages
only from a zone's master.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt>
<dd>
<p>
Specifies which hosts are allowed to ask ordinary
DNS questions. <span><strong class="command">allow-query</strong></span> may
also be specified in the <span><strong class="command">zone</strong></span>
statement, in which case it overrides the
<span><strong class="command">options allow-query</strong></span> statement.
If not specified, the default is to allow queries
from all hosts.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
<span><strong class="command">allow-query-cache</strong></span> is now
used to specify access to the cache.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">allow-query-on</strong></span></span></dt>
<dd>
<p>
Specifies which local addresses can accept ordinary
DNS questions. This makes it possible, for instance,
to allow queries on internal-facing interfaces but
disallow them on external-facing ones, without
necessarily knowing the internal network's addresses.
</p>
<p>
Note that <span><strong class="command">allow-query-on</strong></span> is only
checked for queries that are permitted by
<span><strong class="command">allow-query</strong></span>. A query must be
allowed by both ACLs, or it will be refused.
</p>
<p>
<span><strong class="command">allow-query-on</strong></span> may
also be specified in the <span><strong class="command">zone</strong></span>
statement, in which case it overrides the
<span><strong class="command">options allow-query-on</strong></span> statement.
</p>
<p>
If not specified, the default is to allow queries
on all addresses.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
<span><strong class="command">allow-query-cache</strong></span> is
used to specify access to the cache.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">allow-query-cache</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to get answers
from the cache. If <span><strong class="command">allow-query-cache</strong></span>
is not set then <span><strong class="command">allow-recursion</strong></span>
is used if set, otherwise <span><strong class="command">allow-query</strong></span>
is used if set unless <span><strong class="command">recursion no;</strong></span> is
set in which case <span><strong class="command">none;</strong></span> is used,
otherwise the default (<span><strong class="command">localnets;</strong></span>
<span><strong class="command">localhost;</strong></span>) is used.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-query-cache-on</strong></span></span></dt>
<dd><p>
Specifies which local addresses can give answers
from the cache. If not specified, the default is
to allow cache queries on any address,
<span><strong class="command">localnets</strong></span> and
<span><strong class="command">localhost</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-recursion</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to make recursive
queries through this server. If
<span><strong class="command">allow-recursion</strong></span> is not set
then <span><strong class="command">allow-query-cache</strong></span> is
used if set, otherwise <span><strong class="command">allow-query</strong></span>
is used if set, otherwise the default
(<span><strong class="command">localnets;</strong></span>
<span><strong class="command">localhost;</strong></span>) is used.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-recursion-on</strong></span></span></dt>
<dd><p>
Specifies which local addresses can accept recursive
queries. If not specified, the default is to allow
recursive queries on all addresses.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to
submit Dynamic DNS updates for master zones. The default is
to deny
updates from all hosts. Note that allowing updates based
on the requestor's IP address is insecure; see
<a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called &#8220;Dynamic Update Security&#8221;</a> for details.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt>
<dd>
<p>
Specifies which hosts are allowed to
submit Dynamic DNS updates to slave zones to be forwarded to
the
master. The default is <strong class="userinput"><code>{ none; }</code></strong>,
which
means that no update forwarding will be performed. To
enable
update forwarding, specify
<strong class="userinput"><code>allow-update-forwarding { any; };</code></strong>.
Specifying values other than <strong class="userinput"><code>{ none; }</code></strong> or
<strong class="userinput"><code>{ any; }</code></strong> is usually
counterproductive, since
the responsibility for update access control should rest
with the
master server, not the slaves.
</p>
<p>
Note that enabling the update forwarding feature on a slave
server
may expose master servers relying on insecure IP address
based
access control to attacks; see <a href="Bv9ARM.ch07.html#dynamic_update_security" title="Dynamic Update Security">the section called &#8220;Dynamic Update Security&#8221;</a>
for more details.
</p>
</dd>
<dt><span class="term"><span><strong class="command">allow-v6-synthesis</strong></span></span></dt>
<dd><p>
This option was introduced for the smooth transition from
AAAA
to A6 and from "nibble labels" to binary labels.
However, since both A6 and binary labels were then
deprecated,
this option was also deprecated.
It is now ignored with some warning messages.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to
receive zone transfers from the server. <span><strong class="command">allow-transfer</strong></span> may
also be specified in the <span><strong class="command">zone</strong></span>
statement, in which
case it overrides the <span><strong class="command">options allow-transfer</strong></span> statement.
If not specified, the default is to allow transfers to all
hosts.
</p></dd>
<dt><span class="term"><span><strong class="command">blackhole</strong></span></span></dt>
<dd><p>
Specifies a list of addresses that the
server will not accept queries from or use to resolve a
query. Queries
from these addresses will not be responded to. The default
is <strong class="userinput"><code>none</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">filter-aaaa</strong></span></span></dt>
<dd><p>
Specifies a list of addresses to which
<span><strong class="command">filter-aaaa-on-v4</strong></span>
is applies. The default is <strong class="userinput"><code>any</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">keep-response-order</strong></span></span></dt>
<dd><p>
Specifies a list of addresses to which the server
will send responses to TCP queries in the same order
in which they were received. This disables the
processing of TCP queries in parallel. The default
is <strong class="userinput"><code>none</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">no-case-compress</strong></span></span></dt>
<dd>
<p>
Specifies a list of addresses which require responses
to use case-insensitive compression. This ACL can be
used when <span><strong class="command">named</strong></span> needs to work with
clients that do not comply with the requirement in RFC
1034 to use case-insensitive name comparisons when
checking for matching domain names.
</p>
<p>
If left undefined, the ACL defaults to
<span><strong class="command">none</strong></span>: case-insensitive compression
will be used for all clients. If the ACL is defined and
matches a client, then case will be ignored when
compressing domain names in DNS responses sent to that
client.
</p>
<p>
This can result in slightly smaller responses: if
a response contains the names "example.com" and
"example.COM", case-insensitive compression would treat
the second one as a duplicate. It also ensures
that the case of the query name exactly matches the
case of the owner names of returned records, rather
than matching the case of the records entered in
the zone file. This allows responses to exactly
match the query, which is required by some clients
due to incorrect use of case-sensitive comparisons.
</p>
<p>
Case-insensitive compression is <span class="emphasis"><em>always</em></span>
used in AXFR and IXFR responses, regardless of whether
the client matches this ACL.
</p>
<p>
There are circumstances in which <span><strong class="command">named</strong></span>
will not preserve the case of owner names of records:
if a zone file defines records of different types with
the same name, but the capitalization of the name is
different (e.g., "www.example.com/A" and
"WWW.EXAMPLE.COM/AAAA"), then all responses for that
name will use the <span class="emphasis"><em>first</em></span> version
of the name that was used in the zone file. This
limitation may be addressed in a future release. However,
domain names specified in the rdata of resource records
(i.e., records of type NS, MX, CNAME, etc) will always
have their case preserved unless the client matches this
ACL.
</p>
</dd>
<dt><span class="term"><span><strong class="command">resolver-query-timeout</strong></span></span></dt>
<dd><p>
The amount of time in seconds that the resolver
will spend attempting to resolve a recursive
query before failing. The default and minimum
is <code class="literal">10</code> and the maximum is
<code class="literal">30</code>. Setting it to
<code class="literal">0</code> will result in the default
being used.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2585610"></a>Interfaces</h4></div></div></div>
<p>
The interfaces and ports that the server will answer queries
from may be specified using the <span><strong class="command">listen-on</strong></span> option. <span><strong class="command">listen-on</strong></span> takes
an optional port and an <code class="varname">address_match_list</code>
of IPv4 addresses. (IPv6 addresses are ignored, with a
logged warning.)
The server will listen on all interfaces allowed by the address
match list. If a port is not specified, port 53 will be used.
</p>
<p>
Multiple <span><strong class="command">listen-on</strong></span> statements are
allowed.
For example,
</p>
<pre class="programlisting">listen-on { 5.6.7.8; };
listen-on port 1234 { !1.2.3.4; 1.2/16; };
</pre>
<p>
will enable the name server on port 53 for the IP address
5.6.7.8, and on port 1234 of an address on the machine in net
1.2 that is not 1.2.3.4.
</p>
<p>
If no <span><strong class="command">listen-on</strong></span> is specified, the
server will listen on port 53 on all IPv4 interfaces.
</p>
<p>
The <span><strong class="command">listen-on-v6</strong></span> option is used to
specify the interfaces and the ports on which the server will
listen for incoming queries sent using IPv6. If not specified,
the server will listen on port 53 on all IPv6 interfaces.
</p>
<p>
When </p>
<pre class="programlisting">{ any; }</pre>
<p> is
specified
as the <code class="varname">address_match_list</code> for the
<span><strong class="command">listen-on-v6</strong></span> option,
the server does not bind a separate socket to each IPv6 interface
address as it does for IPv4 if the operating system has enough API
support for IPv6 (specifically if it conforms to RFC 3493 and RFC
3542).
Instead, it listens on the IPv6 wildcard address.
If the system only has incomplete API support for IPv6, however,
the behavior is the same as that for IPv4.
</p>
<p>
A list of particular IPv6 addresses can also be specified, in
which case
the server listens on a separate socket for each specified
address,
regardless of whether the desired API is supported by the system.
IPv4 addresses specified in <span><strong class="command">listen-on-v6</strong></span>
will be ignored, with a logged warning.
</p>
<p>
Multiple <span><strong class="command">listen-on-v6</strong></span> options can
be used.
For example,
</p>
<pre class="programlisting">listen-on-v6 { any; };
listen-on-v6 port 1234 { !2001:db8::/32; any; };
</pre>
<p>
will enable the name server on port 53 for any IPv6 addresses
(with a single wildcard socket),
and on port 1234 of IPv6 addresses that is not in the prefix
2001:db8::/32 (with separate sockets for each matched address.)
</p>
<p>
To make the server not listen on any IPv6 address, use
</p>
<pre class="programlisting">listen-on-v6 { none; };
</pre>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="query_address"></a>Query Address</h4></div></div></div>
<p>
If the server doesn't know the answer to a question, it will
query other name servers. <span><strong class="command">query-source</strong></span> specifies
the address and port used for such queries. For queries sent over
IPv6, there is a separate <span><strong class="command">query-source-v6</strong></span> option.
If <span><strong class="command">address</strong></span> is <span><strong class="command">*</strong></span> (asterisk) or is omitted,
a wildcard IP address (<span><strong class="command">INADDR_ANY</strong></span>)
will be used.
</p>
<p>
If <span><strong class="command">port</strong></span> is <span><strong class="command">*</strong></span> or is omitted,
a random port number from a pre-configured
range is picked up and will be used for each query.
The port range(s) is that specified in
the <span><strong class="command">use-v4-udp-ports</strong></span> (for IPv4)
and <span><strong class="command">use-v6-udp-ports</strong></span> (for IPv6)
options, excluding the ranges specified in
the <span><strong class="command">avoid-v4-udp-ports</strong></span>
and <span><strong class="command">avoid-v6-udp-ports</strong></span> options, respectively.
</p>
<p>
The defaults of the <span><strong class="command">query-source</strong></span> and
<span><strong class="command">query-source-v6</strong></span> options
are:
</p>
<pre class="programlisting">query-source address * port *;
query-source-v6 address * port *;
</pre>
<p>
If <span><strong class="command">use-v4-udp-ports</strong></span> or
<span><strong class="command">use-v6-udp-ports</strong></span> is unspecified,
<span><strong class="command">named</strong></span> will check if the operating
system provides a programming interface to retrieve the
system's default range for ephemeral ports.
If such an interface is available,
<span><strong class="command">named</strong></span> will use the corresponding system
default range; otherwise, it will use its own defaults:
</p>
<pre class="programlisting">use-v4-udp-ports { range 1024 65535; };
use-v6-udp-ports { range 1024 65535; };
</pre>
<p>
Note: make sure the ranges be sufficiently large for
security. A desirable size depends on various parameters,
but we generally recommend it contain at least 16384 ports
(14 bits of entropy).
Note also that the system's default range when used may be
too small for this purpose, and that the range may even be
changed while <span><strong class="command">named</strong></span> is running; the new
range will automatically be applied when <span><strong class="command">named</strong></span>
is reloaded.
It is encouraged to
configure <span><strong class="command">use-v4-udp-ports</strong></span> and
<span><strong class="command">use-v6-udp-ports</strong></span> explicitly so that the
ranges are sufficiently large and are reasonably
independent from the ranges used by other applications.
</p>
<p>
Note: the operational configuration
where <span><strong class="command">named</strong></span> runs may prohibit the use
of some ports. For example, UNIX systems will not allow
<span><strong class="command">named</strong></span> running without a root privilege
to use ports less than 1024.
If such ports are included in the specified (or detected)
set of query ports, the corresponding query attempts will
fail, resulting in resolution failures or delay.
It is therefore important to configure the set of ports
that can be safely used in the expected operational environment.
</p>
<p>
The defaults of the <span><strong class="command">avoid-v4-udp-ports</strong></span> and
<span><strong class="command">avoid-v6-udp-ports</strong></span> options
are:
</p>
<pre class="programlisting">avoid-v4-udp-ports {};
avoid-v6-udp-ports {};
</pre>
<p>
Note: BIND 9.5.0 introduced
the <span><strong class="command">use-queryport-pool</strong></span>
option to support a pool of such random ports, but this
option is now obsolete because reusing the same ports in
the pool may not be sufficiently secure.
For the same reason, it is generally strongly discouraged to
specify a particular port for the
<span><strong class="command">query-source</strong></span> or
<span><strong class="command">query-source-v6</strong></span> options;
it implicitly disables the use of randomized port numbers.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">use-queryport-pool</strong></span></span></dt>
<dd><p>
This option is obsolete.
</p></dd>
<dt><span class="term"><span><strong class="command">queryport-pool-ports</strong></span></span></dt>
<dd><p>
This option is obsolete.
</p></dd>
<dt><span class="term"><span><strong class="command">queryport-pool-updateinterval</strong></span></span></dt>
<dd><p>
This option is obsolete.
</p></dd>
</dl></div>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
The address specified in the <span><strong class="command">query-source</strong></span> option
is used for both UDP and TCP queries, but the port applies only
to UDP queries. TCP queries always use a random
unprivileged port.
</p>
</div>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Solaris 2.5.1 and earlier does not support setting the source
address for TCP sockets.
</p>
</div>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
See also <span><strong class="command">transfer-source</strong></span> and
<span><strong class="command">notify-source</strong></span>.
</p>
</div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="zone_transfers"></a>Zone Transfers</h4></div></div></div>
<p>
<acronym class="acronym">BIND</acronym> has mechanisms in place to
facilitate zone transfers
and set limits on the amount of load that transfers place on the
system. The following options apply to zone transfers.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">also-notify</strong></span></span></dt>
<dd>
<p>
Defines a global list of IP addresses of name servers
that are also sent NOTIFY messages whenever a fresh copy of
the
zone is loaded, in addition to the servers listed in the
zone's NS records.
This helps to ensure that copies of the zones will
quickly converge on stealth servers.
Optionally, a port may be specified with each
<span><strong class="command">also-notify</strong></span> address to send
the notify messages to a port other than the
default of 53.
An optional TSIG key can also be specified with each
address to cause the notify messages to be signed; this
can be useful when sending notifies to multiple views.
In place of explicit addresses, one or more named
<span><strong class="command">masters</strong></span> lists can be used.
</p>
<p>
If an <span><strong class="command">also-notify</strong></span> list
is given in a <span><strong class="command">zone</strong></span> statement,
it will override
the <span><strong class="command">options also-notify</strong></span>
statement. When a <span><strong class="command">zone notify</strong></span>
statement
is set to <span><strong class="command">no</strong></span>, the IP
addresses in the global <span><strong class="command">also-notify</strong></span> list will
not be sent NOTIFY messages for that zone. The default is
the empty
list (no global notification list).
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-transfer-time-in</strong></span></span></dt>
<dd><p>
Inbound zone transfers running longer than
this many minutes will be terminated. The default is 120
minutes
(2 hours). The maximum value is 28 days (40320 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-idle-in</strong></span></span></dt>
<dd><p>
Inbound zone transfers making no progress
in this many minutes will be terminated. The default is 60
minutes
(1 hour). The maximum value is 28 days (40320 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-time-out</strong></span></span></dt>
<dd><p>
Outbound zone transfers running longer than
this many minutes will be terminated. The default is 120
minutes
(2 hours). The maximum value is 28 days (40320 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-idle-out</strong></span></span></dt>
<dd><p>
Outbound zone transfers making no progress
in this many minutes will be terminated. The default is 60
minutes (1
hour). The maximum value is 28 days (40320 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">notify-rate</strong></span></span></dt>
<dd><p>
The rate at which NOTIFY requests will be sent
during normal zone maintenance operations. (NOTIFY
requests due to initial zone loading are subject
to a separate rate limit; see below.) The default is
20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
</p></dd>
<dt><span class="term"><span><strong class="command">startup-notify-rate</strong></span></span></dt>
<dd><p>
The rate at which NOTIFY requests will be sent
when the name server is first starting up, or when
zones have been newly added to the nameserver.
The default is 20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
</p></dd>
<dt><span class="term"><span><strong class="command">serial-query-rate</strong></span></span></dt>
<dd><p>
Slave servers will periodically query master
servers to find out if zone serial numbers have
changed. Each such query uses a minute amount of
the slave server's network bandwidth. To limit
the amount of bandwidth used, BIND 9 limits the
rate at which queries are sent. The value of the
<span><strong class="command">serial-query-rate</strong></span> option, an
integer, is the maximum number of queries sent
per second. The default is 20 per second.
The lowest possible rate is one per second; when set
to zero, it will be silently raised to one.
</p></dd>
<dt><span class="term"><span><strong class="command">serial-queries</strong></span></span></dt>
<dd><p>
In BIND 8, the <span><strong class="command">serial-queries</strong></span>
option
set the maximum number of concurrent serial number queries
allowed to be outstanding at any given time.
BIND 9 does not limit the number of outstanding
serial queries and ignores the <span><strong class="command">serial-queries</strong></span> option.
Instead, it limits the rate at which the queries are sent
as defined using the <span><strong class="command">serial-query-rate</strong></span> option.
</p></dd>
<dt><span class="term"><span><strong class="command">transfer-format</strong></span></span></dt>
<dd><p>
Zone transfers can be sent using two different formats,
<span><strong class="command">one-answer</strong></span> and
<span><strong class="command">many-answers</strong></span>.
The <span><strong class="command">transfer-format</strong></span> option is used
on the master server to determine which format it sends.
<span><strong class="command">one-answer</strong></span> uses one DNS message per
resource record transferred.
<span><strong class="command">many-answers</strong></span> packs as many resource
records as possible into a message.
<span><strong class="command">many-answers</strong></span> is more efficient, but is
only supported by relatively new slave servers,
such as <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym>
8.x and <acronym class="acronym">BIND</acronym> 4.9.5 onwards.
The <span><strong class="command">many-answers</strong></span> format is also supported by
recent Microsoft Windows nameservers.
The default is <span><strong class="command">many-answers</strong></span>.
<span><strong class="command">transfer-format</strong></span> may be overridden on a
per-server basis by using the <span><strong class="command">server</strong></span>
statement.
</p></dd>
<dt><span class="term"><span><strong class="command">transfers-in</strong></span></span></dt>
<dd><p>
The maximum number of inbound zone transfers
that can be running concurrently. The default value is <code class="literal">10</code>.
Increasing <span><strong class="command">transfers-in</strong></span> may
speed up the convergence
of slave zones, but it also may increase the load on the
local system.
</p></dd>
<dt><span class="term"><span><strong class="command">transfers-out</strong></span></span></dt>
<dd><p>
The maximum number of outbound zone transfers
that can be running concurrently. Zone transfer requests in
excess
of the limit will be refused. The default value is <code class="literal">10</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">transfers-per-ns</strong></span></span></dt>
<dd><p>
The maximum number of inbound zone transfers
that can be concurrently transferring from a given remote
name server.
The default value is <code class="literal">2</code>.
Increasing <span><strong class="command">transfers-per-ns</strong></span>
may
speed up the convergence of slave zones, but it also may
increase
the load on the remote name server. <span><strong class="command">transfers-per-ns</strong></span> may
be overridden on a per-server basis by using the <span><strong class="command">transfers</strong></span> phrase
of the <span><strong class="command">server</strong></span> statement.
</p></dd>
<dt><span class="term"><span><strong class="command">transfer-source</strong></span></span></dt>
<dd>
<p><span><strong class="command">transfer-source</strong></span>
determines which local address will be bound to IPv4
TCP connections used to fetch zones transferred
inbound by the server. It also determines the
source IPv4 address, and optionally the UDP port,
used for the refresh queries and forwarded dynamic
updates. If not set, it defaults to a system
controlled value which will usually be the address
of the interface "closest to" the remote end. This
address must appear in the remote end's
<span><strong class="command">allow-transfer</strong></span> option for the
zone being transferred, if one is specified. This
statement sets the
<span><strong class="command">transfer-source</strong></span> for all zones,
but can be overridden on a per-view or per-zone
basis by including a
<span><strong class="command">transfer-source</strong></span> statement within
the <span><strong class="command">view</strong></span> or
<span><strong class="command">zone</strong></span> block in the configuration
file.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Solaris 2.5.1 and earlier does not support setting the
source address for TCP sockets.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">transfer-source-v6</strong></span></span></dt>
<dd><p>
The same as <span><strong class="command">transfer-source</strong></span>,
except zone transfers are performed using IPv6.
</p></dd>
<dt><span class="term"><span><strong class="command">alt-transfer-source</strong></span></span></dt>
<dd>
<p>
An alternate transfer source if the one listed in
<span><strong class="command">transfer-source</strong></span> fails and
<span><strong class="command">use-alt-transfer-source</strong></span> is
set.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
If you do not wish the alternate transfer source
to be used, you should set
<span><strong class="command">use-alt-transfer-source</strong></span>
appropriately and you should not depend upon
getting an answer back to the first refresh
query.
</div>
</dd>
<dt><span class="term"><span><strong class="command">alt-transfer-source-v6</strong></span></span></dt>
<dd><p>
An alternate transfer source if the one listed in
<span><strong class="command">transfer-source-v6</strong></span> fails and
<span><strong class="command">use-alt-transfer-source</strong></span> is
set.
</p></dd>
<dt><span class="term"><span><strong class="command">use-alt-transfer-source</strong></span></span></dt>
<dd><p>
Use the alternate transfer sources or not. If views are
specified this defaults to <span><strong class="command">no</strong></span>
otherwise it defaults to
<span><strong class="command">yes</strong></span> (for BIND 8
compatibility).
</p></dd>
<dt><span class="term"><span><strong class="command">notify-source</strong></span></span></dt>
<dd>
<p><span><strong class="command">notify-source</strong></span>
determines which local source address, and
optionally UDP port, will be used to send NOTIFY
messages. This address must appear in the slave
server's <span><strong class="command">masters</strong></span> zone clause or
in an <span><strong class="command">allow-notify</strong></span> clause. This
statement sets the <span><strong class="command">notify-source</strong></span>
for all zones, but can be overridden on a per-zone or
per-view basis by including a
<span><strong class="command">notify-source</strong></span> statement within
the <span><strong class="command">zone</strong></span> or
<span><strong class="command">view</strong></span> block in the configuration
file.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Solaris 2.5.1 and earlier does not support setting the
source address for TCP sockets.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">notify-source-v6</strong></span></span></dt>
<dd><p>
Like <span><strong class="command">notify-source</strong></span>,
but applies to notify messages sent to IPv6 addresses.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2586834"></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="id2586893"></a>Operating System Resource Limits</h4></div></div></div>
<p>
The server's usage of many system resources can be limited.
Scaled values are allowed when specifying resource limits. For
example, <span><strong class="command">1G</strong></span> can be used instead of
<span><strong class="command">1073741824</strong></span> to specify a limit of
one
gigabyte. <span><strong class="command">unlimited</strong></span> requests
unlimited use, or the
maximum available amount. <span><strong class="command">default</strong></span>
uses the limit
that was in force when the server was started. See the description
of <span><strong class="command">size_spec</strong></span> in <a href="Bv9ARM.ch06.html#configuration_file_elements" title="Configuration File Elements">the section called &#8220;Configuration File Elements&#8221;</a>.
</p>
<p>
The following options set operating system resource limits for
the name server process. Some operating systems don't support
some or
any of the limits. On such systems, a warning will be issued if
the
unsupported limit is used.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">coresize</strong></span></span></dt>
<dd><p>
The maximum size of a core dump. The default
is <code class="literal">default</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">datasize</strong></span></span></dt>
<dd><p>
The maximum amount of data memory the server
may use. The default is <code class="literal">default</code>.
This is a hard limit on server memory usage.
If the server attempts to allocate memory in excess of this
limit, the allocation will fail, which may in turn leave
the server unable to perform DNS service. Therefore,
this option is rarely useful as a way of limiting the
amount of memory used by the server, but it can be used
to raise an operating system data size limit that is
too small by default. If you wish to limit the amount
of memory used by the server, use the
<span><strong class="command">max-cache-size</strong></span> and
<span><strong class="command">recursive-clients</strong></span>
options instead.
</p></dd>
<dt><span class="term"><span><strong class="command">files</strong></span></span></dt>
<dd><p>
The maximum number of files the server
may have open concurrently. The default is <code class="literal">unlimited</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">stacksize</strong></span></span></dt>
<dd><p>
The maximum amount of stack memory the server
may use. The default is <code class="literal">default</code>.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="server_resource_limits"></a>Server Resource Limits</h4></div></div></div>
<p>
The following options set limits on the server's
resource consumption that are enforced internally by the
server rather than the operating system.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">max-ixfr-log-size</strong></span></span></dt>
<dd><p>
This option is obsolete; it is accepted
and ignored for BIND 8 compatibility. The option
<span><strong class="command">max-journal-size</strong></span> performs a
similar function in BIND 9.
</p></dd>
<dt><span class="term"><span><strong class="command">max-journal-size</strong></span></span></dt>
<dd><p>
Sets a maximum size for each journal file
(see <a href="Bv9ARM.ch04.html#journal" title="The journal file">the section called &#8220;The journal file&#8221;</a>). When the journal file
approaches
the specified size, some of the oldest transactions in the
journal
will be automatically removed. The largest permitted
value is 2 gigabytes. The default is
<code class="literal">unlimited</code>, which also
means 2 gigabytes.
This may also be set on a per-zone basis.
</p></dd>
<dt><span class="term"><span><strong class="command">host-statistics-max</strong></span></span></dt>
<dd><p>
In BIND 8, specifies the maximum number of host statistics
entries to be kept.
Not implemented in BIND 9.
</p></dd>
<dt><span class="term"><span><strong class="command">recursive-clients</strong></span></span></dt>
<dd>
<p>
The maximum number ("hard quota") 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>
<p>
<code class="option">recursive-clients</code> defines a "hard
quota" limit for pending recursive clients: when more
clients than this are pending, new incoming requests
will not be accepted, and for each incoming request
a previous pending request will also be dropped.
</p>
<p>
A "soft quota" is also set. When this lower
quota is exceeded, incoming requests are accepted, but
for each one, a pending request will be dropped.
If <code class="option">recursive-clients</code> is greater than
1000, the soft quota is set to
<code class="option">recursive-clients</code> minus 100;
otherwise it is set to 90% of
<code class="option">recursive-clients</code>.
</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>
<a name="clients-per-query"></a><span class="term"><span><strong class="command">clients-per-query</strong></span>, </span><span class="term"><span><strong class="command">max-clients-per-query</strong></span></span>
</dt>
<dd>
<p>These set the
initial value (minimum) and maximum number of recursive
simultaneous clients for any given query
(&lt;qname,qtype,qclass&gt;) that the server will accept
before dropping additional clients. <span><strong class="command">named</strong></span> will attempt to
self tune this value and changes will be logged. The
default values are 10 and 100.
</p>
<p>
This value should reflect how many queries come in for
a given name in the time it takes to resolve that name.
If the number of queries exceed this value, <span><strong class="command">named</strong></span> will
assume that it is dealing with a non-responsive zone
and will drop additional queries. If it gets a response
after dropping queries, it will raise the estimate. The
estimate will then be lowered in 20 minutes if it has
remained unchanged.
</p>
<p>
If <span><strong class="command">clients-per-query</strong></span> is set to zero,
then there is no limit on the number of clients per query
and no queries will be dropped.
</p>
<p>
If <span><strong class="command">max-clients-per-query</strong></span> is set to zero,
then there is no upper bound other than imposed by
<span><strong class="command">recursive-clients</strong></span>.
</p>
</dd>
<dt>
<a name="fetches-per-zone"></a><span class="term"><span><strong class="command">fetches-per-zone</strong></span></span>
</dt>
<dd>
<p>
The maximum number of simultaneous iterative
queries to any one domain that the server will
permit before blocking new queries for data
in or beneath that zone.
This value should reflect how many fetches would
normally be sent to any one zone in the time it
would take to resolve them. It should be smaller
than <code class="option">recursive-clients</code>.
</p>
<p>
When many clients simultaneously query for the
same name and type, the clients will all be attached
to the same fetch, up to the
<code class="option">max-clients-per-query</code> limit,
and only one iterative query will be sent.
However, when clients are simultaneously
querying for <span class="emphasis"><em>different</em></span> names
or types, multiple queries will be sent and
<code class="option">max-clients-per-query</code> is not
effective as a limit.
</p>
<p>
Optionally, this value may be followed by the keyword
<code class="literal">drop</code> or <code class="literal">fail</code>,
indicating whether queries which exceed the fetch
quota for a zone will be dropped with no response,
or answered with SERVFAIL. The default is
<code class="literal">drop</code>.
</p>
<p>
If <span><strong class="command">fetches-per-zone</strong></span> is set to zero,
then there is no limit on the number of fetches per query
and no queries will be dropped. The default is zero.
</p>
<p>
The current list of active fetches can be dumped by
running <span><strong class="command">rndc recursing</strong></span>. The list
includes the number of active fetches for each
domain and the number of queries that have been
passed or dropped as a result of the
<code class="option">fetches-per-zone</code> limit. (Note:
these counters are not cumulative over time; whenever
the number of active fetches for a domain drops to
zero, the counter for that domain is deleted, and the
next time a fetch is sent to that domain, it is
recreated with the counters set to zero.)
</p>
</dd>
<dt>
<a name="fetches-per-server"></a><span class="term"><span><strong class="command">fetches-per-server</strong></span></span>
</dt>
<dd>
<p>
The maximum number of simultaneous iterative
queries that the server will allow to be sent to
a single upstream name server before blocking
additional queries.
This value should reflect how many fetches would
normally be sent to any one server in the time it
would take to resolve them. It should be smaller
than <code class="option">recursive-clients</code>.
</p>
<p>
Optionally, this value may be followed by the keyword
<code class="literal">drop</code> or <code class="literal">fail</code>,
indicating whether queries will be dropped with no
response, or answered with SERVFAIL, when all of the
servers authoritative for a zone are found to have
exceeded the per-server quota. The default is
<code class="literal">fail</code>.
</p>
<p>
If <span><strong class="command">fetches-per-server</strong></span> is set to zero,
then there is no limit on the number of fetches per query
and no queries will be dropped. The default is zero.
</p>
<p>
The <span><strong class="command">fetches-per-server</strong></span> quota is
dynamically adjusted in response to detected
congestion. As queries are sent to a server
and are either answered or time out, an
exponentially weighted moving average is calculated
of the ratio of timeouts to responses. If the
current average timeout ratio rises above a "high"
threshold, then <span><strong class="command">fetches-per-server</strong></span>
is reduced for that server. If the timeout ratio
drops below a "low" threshold, then
<span><strong class="command">fetches-per-server</strong></span> is increased.
The <span><strong class="command">fetch-quota-params</strong></span> options
can be used to adjust the parameters for this
calculation.
</p>
</dd>
<dt><span class="term"><span><strong class="command">fetch-quota-params</strong></span></span></dt>
<dd>
<p>
Sets the parameters to use for dynamic resizing of
the <code class="option">fetches-per-server</code> quota in
response to detected congestion.
</p>
<p>
The first argument is an integer value indicating
how frequently to recalculate the moving average
of the ratio of timeouts to responses for each
server. The default is 100, meaning we recalculate
the average ratio after every 100 queries have either
been answered or timed out.
</p>
<p>
The remaining three arguments represent the "low"
threshold (defaulting to a timeout ratio of 0.1),
the "high" threshold (defaulting to a timeout
ratio of 0.3), and the discount rate for
the moving average (defaulting to 0.7).
A higher discount rate causes recent events to
weigh more heavily when calculating the moving
average; a lower discount rate causes past
events to weigh more heavily, smoothing out
short-term blips in the timeout ratio.
These arguments are all fixed-point numbers with
precision of 1/100: at most two places after
the decimal point are significant.
</p>
</dd>
<dt><span class="term"><span><strong class="command">reserved-sockets</strong></span></span></dt>
<dd>
<p>
The number of file descriptors reserved for TCP, stdio,
etc. This needs to be big enough to cover the number of
interfaces <span><strong class="command">named</strong></span> listens on, <span><strong class="command">tcp-clients</strong></span> as well as
to provide room for outgoing TCP queries and incoming zone
transfers. The default is <code class="literal">512</code>.
The minimum value is <code class="literal">128</code> and the
maximum value is <code class="literal">128</code> less than
maxsockets (-S). This option may be removed in the future.
</p>
<p>
This option has little effect on Windows.
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-cache-size</strong></span></span></dt>
<dd><p>
The maximum amount of memory to use for the
server's cache, in bytes.
When the amount of data in the cache
reaches this limit, the server will cause records to
expire prematurely based on an LRU based strategy so
that the limit is not exceeded.
The keyword <strong class="userinput"><code>unlimited</code></strong>,
or the value 0, will place no limit on cache size;
records will be purged from the cache only when their
TTLs expire.
Any positive values less than 2MB will be ignored
and reset to 2MB.
In a server with multiple views, the limit applies
separately to the cache of each view.
The default is <strong class="userinput"><code>unlimited</code></strong>.
</p></dd>
<dt><span class="term"><span><strong class="command">tcp-listen-queue</strong></span></span></dt>
<dd><p>
The listen queue depth. The default and minimum is 10.
If the kernel supports the accept filter "dataready" this
also controls how
many TCP connections that will be queued in kernel space
waiting for
some data before being passed to accept. Nonzero values
less than 10 will be silently raised. A value of 0 may also
be used; on most platforms this sets the listen queue
length to a system-defined default value.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2587729"></a>Periodic Task Intervals</h4></div></div></div>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">cleaning-interval</strong></span></span></dt>
<dd><p>
This interval is effectively obsolete. Previously,
the server would remove expired resource records
from the cache every <span><strong class="command">cleaning-interval</strong></span> minutes.
<acronym class="acronym">BIND</acronym> 9 now manages cache
memory in a more sophisticated manner and does not
rely on the periodic cleaning any more.
Specifying this option therefore has no effect on
the server's behavior.
</p></dd>
<dt><span class="term"><span><strong class="command">heartbeat-interval</strong></span></span></dt>
<dd><p>
The server will perform zone maintenance tasks
for all zones marked as <span><strong class="command">dialup</strong></span> whenever this
interval expires. The default is 60 minutes. Reasonable
values are up
to 1 day (1440 minutes). The maximum value is 28 days
(40320 minutes).
If set to 0, no zone maintenance for these zones will occur.
</p></dd>
<dt><span class="term"><span><strong class="command">interface-interval</strong></span></span></dt>
<dd><p>
The server will scan the network interface list
every <span><strong class="command">interface-interval</strong></span>
minutes. The default
is 60 minutes. The maximum value is 28 days (40320 minutes).
If set to 0, interface scanning will only occur when
the configuration file is loaded. After the scan, the
server will
begin listening for queries on any newly discovered
interfaces (provided they are allowed by the
<span><strong class="command">listen-on</strong></span> configuration), and
will
stop listening on interfaces that have gone away.
</p></dd>
<dt><span class="term"><span><strong class="command">statistics-interval</strong></span></span></dt>
<dd>
<p>
Name server statistics will be logged
every <span><strong class="command">statistics-interval</strong></span>
minutes. The default is
60. The maximum value is 28 days (40320 minutes).
If set to 0, no statistics will be logged.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Not yet implemented in
<acronym class="acronym">BIND</acronym> 9.
</p>
</div>
</dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="topology"></a>Topology</h4></div></div></div>
<p>
All other things being equal, when the server chooses a name
server
to query from a list of name servers, it prefers the one that is
topologically closest to itself. The <span><strong class="command">topology</strong></span> statement
takes an <span><strong class="command">address_match_list</strong></span> and
interprets it
in a special way. Each top-level list element is assigned a
distance.
Non-negated elements get a distance based on their position in the
list, where the closer the match is to the start of the list, the
shorter the distance is between it and the server. A negated match
will be assigned the maximum distance from the server. If there
is no match, the address will get a distance which is further than
any non-negated list element, and closer than any negated element.
For example,
</p>
<pre class="programlisting">topology {
10/8;
!1.2.3/24;
{ 1.2/16; 3/8; };
};</pre>
<p>
will prefer servers on network 10 the most, followed by hosts
on network 1.2.0.0 (netmask 255.255.0.0) and network 3, with the
exception of hosts on network 1.2.3 (netmask 255.255.255.0), which
is preferred least of all.
</p>
<p>
The default topology is
</p>
<pre class="programlisting"> topology { localhost; localnets; };
</pre>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
The <span><strong class="command">topology</strong></span> option
is not implemented in <acronym class="acronym">BIND</acronym> 9.
</p>
</div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="the_sortlist_statement"></a>The <span><strong class="command">sortlist</strong></span> Statement</h4></div></div></div>
<p>
The response to a DNS query may consist of multiple resource
records (RRs) forming a resource records set (RRset).
The name server will normally return the
RRs within the RRset in an indeterminate order
(but see the <span><strong class="command">rrset-order</strong></span>
statement in <a href="Bv9ARM.ch06.html#rrset_ordering" title="RRset Ordering">the section called &#8220;RRset Ordering&#8221;</a>).
The client resolver code should rearrange the RRs as appropriate,
that is, using any addresses on the local net in preference to
other addresses.
However, not all resolvers can do this or are correctly
configured.
When a client is using a local server, the sorting can be performed
in the server, based on the client's address. This only requires
configuring the name servers, not all the clients.
</p>
<p>
The <span><strong class="command">sortlist</strong></span> statement (see below)
takes
an <span><strong class="command">address_match_list</strong></span> and
interprets it even
more specifically than the <span><strong class="command">topology</strong></span>
statement
does (<a href="Bv9ARM.ch06.html#topology" title="Topology">the section called &#8220;Topology&#8221;</a>).
Each top level statement in the <span><strong class="command">sortlist</strong></span> must
itself be an explicit <span><strong class="command">address_match_list</strong></span> with
one or two elements. The first element (which may be an IP
address,
an IP prefix, an ACL name or a nested <span><strong class="command">address_match_list</strong></span>)
of each top level list is checked against the source address of
the query until a match is found.
</p>
<p>
Once the source address of the query has been matched, if
the top level statement contains only one element, the actual
primitive
element that matched the source address is used to select the
address
in the response to move to the beginning of the response. If the
statement is a list of two elements, then the second element is
treated the same as the <span><strong class="command">address_match_list</strong></span> in
a <span><strong class="command">topology</strong></span> statement. Each top
level element
is assigned a distance and the address in the response with the
minimum
distance is moved to the beginning of the response.
</p>
<p>
In the following example, any queries received from any of
the addresses of the host itself will get responses preferring
addresses
on any of the locally connected networks. Next most preferred are
addresses
on the 192.168.1/24 network, and after that either the
192.168.2/24
or
192.168.3/24 network with no preference shown between these two
networks. Queries received from a host on the 192.168.1/24 network
will prefer other addresses on that network to the 192.168.2/24
and
192.168.3/24 networks. Queries received from a host on the
192.168.4/24
or the 192.168.5/24 network will only prefer other addresses on
their directly connected networks.
</p>
<pre class="programlisting">sortlist {
// IF the local host
// THEN first fit on the following nets
{ localhost;
{ localnets;
192.168.1/24;
{ 192.168.2/24; 192.168.3/24; }; }; };
// IF on class C 192.168.1 THEN use .1, or .2 or .3
{ 192.168.1/24;
{ 192.168.1/24;
{ 192.168.2/24; 192.168.3/24; }; }; };
// IF on class C 192.168.2 THEN use .2, or .1 or .3
{ 192.168.2/24;
{ 192.168.2/24;
{ 192.168.1/24; 192.168.3/24; }; }; };
// IF on class C 192.168.3 THEN use .3, or .1 or .2
{ 192.168.3/24;
{ 192.168.3/24;
{ 192.168.1/24; 192.168.2/24; }; }; };
// IF .4 or .5 THEN prefer that net
{ { 192.168.4/24; 192.168.5/24; };
};
};</pre>
<p>
The following example will give reasonable behavior for the
local host and hosts on directly connected networks. It is similar
to the behavior of the address sort in <acronym class="acronym">BIND</acronym> 4.9.x. Responses sent
to queries from the local host will favor any of the directly
connected
networks. Responses sent to queries from any other hosts on a
directly
connected network will prefer addresses on that same network.
Responses
to other queries will not be sorted.
</p>
<pre class="programlisting">sortlist {
{ localhost; localnets; };
{ localnets; };
};
</pre>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="rrset_ordering"></a>RRset Ordering</h4></div></div></div>
<p>
When multiple records are returned in an answer it may be
useful to configure the order of the records placed into the
response.
The <span><strong class="command">rrset-order</strong></span> statement permits
configuration
of the ordering of the records in a multiple record response.
See also the <span><strong class="command">sortlist</strong></span> statement,
<a href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called &#8220;The <span><strong class="command">sortlist</strong></span> Statement&#8221;</a>.
</p>
<p>
An <span><strong class="command">order_spec</strong></span> is defined as
follows:
</p>
<p>
[<span class="optional">class <em class="replaceable"><code>class_name</code></em></span>]
[<span class="optional">type <em class="replaceable"><code>type_name</code></em></span>]
[<span class="optional">name <em class="replaceable"><code>"domain_name"</code></em></span>]
order <em class="replaceable"><code>ordering</code></em>
</p>
<p>
If no class is specified, the default is <span><strong class="command">ANY</strong></span>.
If no type is specified, the default is <span><strong class="command">ANY</strong></span>.
If no name is specified, the default is "<span><strong class="command">*</strong></span>" (asterisk).
</p>
<p>
The legal values for <span><strong class="command">ordering</strong></span> are:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p><span><strong class="command">fixed</strong></span></p>
</td>
<td>
<p>
Records are returned in the order they
are defined in the zone file.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">random</strong></span></p>
</td>
<td>
<p>
Records are returned in some random order.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">cyclic</strong></span></p>
</td>
<td>
<p>
Records are returned in a cyclic round-robin order.
</p>
<p>
If <acronym class="acronym">BIND</acronym> is configured with the
"--enable-fixed-rrset" option at compile time, then
the initial ordering of the RRset will match the
one specified in the zone file.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
For example:
</p>
<pre class="programlisting">rrset-order {
class IN type A name "host.example.com" order random;
order cyclic;
};
</pre>
<p>
will cause any responses for type A records in class IN that
have "<code class="literal">host.example.com</code>" as a
suffix, to always be returned
in random order. All other records are returned in cyclic order.
</p>
<p>
If multiple <span><strong class="command">rrset-order</strong></span> statements
appear, they are not combined &#8212; the last one applies.
</p>
<p>
By default, all records are returned in random order.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
In this release of <acronym class="acronym">BIND</acronym> 9, the
<span><strong class="command">rrset-order</strong></span> statement does not support
"fixed" ordering by default. Fixed ordering can be enabled
at compile time by specifying "--enable-fixed-rrset" on
the "configure" command line.
</p>
</div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="tuning"></a>Tuning</h4></div></div></div>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">lame-ttl</strong></span></span></dt>
<dd><p>
Sets the number of seconds to cache a
lame server indication. 0 disables caching. (This is
<span class="bold"><strong>NOT</strong></span> recommended.)
The default is <code class="literal">600</code> (10 minutes) and the
maximum value is
<code class="literal">1800</code> (30 minutes).
</p></dd>
<dt><span class="term"><span><strong class="command">servfail-ttl</strong></span></span></dt>
<dd>
<p>
Sets the number of seconds to cache a
SERVFAIL response due to DNSSEC validation failure or
other general server failure. If set to
<code class="literal">0</code>, SERVFAIL caching is disabled.
The SERVFAIL cache is not consulted if a query has
the CD (Checking Disabled) bit set; this allows a
query that failed due to DNSSEC validation to be retried
without waiting for the SERVFAIL TTL to expire.
</p>
<p>
The maximum value is <code class="literal">300</code>
(5 minutes); any higher value will be silently
reduced. The default is <code class="literal">10</code>
seconds.
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-ncache-ttl</strong></span></span></dt>
<dd><p>
To reduce network traffic and increase performance,
the server stores negative answers. <span><strong class="command">max-ncache-ttl</strong></span> is
used to set a maximum retention time for these answers in
the server
in seconds. The default
<span><strong class="command">max-ncache-ttl</strong></span> is <code class="literal">10800</code> seconds (3 hours).
<span><strong class="command">max-ncache-ttl</strong></span> cannot exceed
7 days and will
be silently truncated to 7 days if set to a greater value.
</p></dd>
<dt><span class="term"><span><strong class="command">max-cache-ttl</strong></span></span></dt>
<dd><p>
Sets the maximum time for which the server will
cache ordinary (positive) answers in seconds.
The default is 604800 (one week).
A value of zero may cause all queries to return
SERVFAIL, because of lost caches of intermediate
RRsets (such as NS and glue AAAA/A records) in the
resolution process.
</p></dd>
<dt><span class="term"><span><strong class="command">min-roots</strong></span></span></dt>
<dd>
<p>
The minimum number of root servers that
is required for a request for the root servers to be
accepted. The default
is <strong class="userinput"><code>2</code></strong>.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
<p>
Not implemented in <acronym class="acronym">BIND</acronym> 9.
</p>
</div>
</dd>
<dt><span class="term"><span><strong class="command">sig-validity-interval</strong></span></span></dt>
<dd>
<p>
Specifies the number of days into the future when
DNSSEC signatures automatically generated as a
result of dynamic updates (<a href="Bv9ARM.ch04.html#dynamic_update" title="Dynamic Update">the section called &#8220;Dynamic Update&#8221;</a>) will expire. There
is an optional second field which specifies how
long before expiry that the signatures will be
regenerated. If not specified, the signatures will
be regenerated at 1/4 of base interval. The second
field is specified in days if the base interval is
greater than 7 days otherwise it is specified in hours.
The default base interval is <code class="literal">30</code> days
giving a re-signing interval of 7 1/2 days. The maximum
values are 10 years (3660 days).
</p>
<p>
The signature inception time is unconditionally
set to one hour before the current time to allow
for a limited amount of clock skew.
</p>
<p>
The <span><strong class="command">sig-validity-interval</strong></span>
should be, at least, several multiples of the SOA
expire interval to allow for reasonable interaction
between the various timer and expiry dates.
</p>
</dd>
<dt><span class="term"><span><strong class="command">sig-signing-nodes</strong></span></span></dt>
<dd><p>
Specify the maximum number of nodes to be
examined in each quantum when signing a zone with
a new DNSKEY. The default is
<code class="literal">100</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-signatures</strong></span></span></dt>
<dd><p>
Specify a threshold number of signatures that
will terminate processing a quantum when signing
a zone with a new DNSKEY. The default is
<code class="literal">10</code>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-type</strong></span></span></dt>
<dd>
<p>
Specify a private RDATA type to be used when generating
signing state records. The default is
<code class="literal">65534</code>.
</p>
<p>
It is expected that this parameter may be removed
in a future version once there is a standard type.
</p>
<p>
Signing state records are used to internally by
<span><strong class="command">named</strong></span> to track the current state of
a zone-signing process, i.e., whether it is still active
or has been completed. The records can be inspected
using the command
<span><strong class="command">rndc signing -list <em class="replaceable"><code>zone</code></em></strong></span>.
Once <span><strong class="command">named</strong></span> has finished signing
a zone with a particular key, the signing state
record associated with that key can be removed from
the zone by running
<span><strong class="command">rndc signing -clear <em class="replaceable"><code>keyid/algorithm</code></em> <em class="replaceable"><code>zone</code></em></strong></span>.
To clear all of the completed signing state
records for a zone, use
<span><strong class="command">rndc signing -clear all <em class="replaceable"><code>zone</code></em></strong></span>.
</p>
</dd>
<dt>
<span class="term"><span><strong class="command">min-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">max-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">min-retry-time</strong></span>, </span><span class="term"><span><strong class="command">max-retry-time</strong></span></span>
</dt>
<dd>
<p>
These options control the server's behavior on refreshing a
zone
(querying for SOA changes) or retrying failed transfers.
Usually the SOA values for the zone are used, but these
values
are set by the master, giving slave server administrators
little
control over their contents.
</p>
<p>
These options allow the administrator to set a minimum and
maximum refresh and retry time in seconds per-zone,
per-view, or globally.
These options are valid for slave and stub zones,
and clamp the SOA refresh and retry times to the specified
values.
</p>
<p>
The following defaults apply.
<span><strong class="command">min-refresh-time</strong></span> 300 seconds,
<span><strong class="command">max-refresh-time</strong></span> 2419200 seconds
(4 weeks), <span><strong class="command">min-retry-time</strong></span> 500 seconds,
and <span><strong class="command">max-retry-time</strong></span> 1209600 seconds
(2 weeks).
</p>
</dd>
<dt><span class="term"><span><strong class="command">edns-udp-size</strong></span></span></dt>
<dd>
<p>
Sets the maximum advertised EDNS UDP buffer size in
bytes, to control the size of packets received from
authoritative servers in response to recursive queries.
Valid values are 512 to 4096 (values outside this range
will be silently adjusted to the nearest value within
it). The default value is 4096.
</p>
<p>
The usual reason for setting
<span><strong class="command">edns-udp-size</strong></span> to a non-default value
is to get UDP answers to pass through broken firewalls
that block fragmented packets and/or block UDP DNS
packets that are greater than 512 bytes.
</p>
<p>
When <span><strong class="command">named</strong></span> first queries a remote
server, it will advertise a UDP buffer size of 512, as
this has the greatest chance of success on the first try.
</p>
<p>
If the initial response times out, <span><strong class="command">named</strong></span>
will try again with plain DNS, and if that is successful,
it will be taken as evidence that the server does not
support EDNS. After enough failures using EDNS and
successes using plain DNS, <span><strong class="command">named</strong></span>
will default to plain DNS for future communications
with that server. (Periodically, <span><strong class="command">named</strong></span>
will send an EDNS query to see if the situation has
improved.)
</p>
<p>
However, if the initial query is successful with
EDNS advertising a buffer size of 512, then
<span><strong class="command">named</strong></span> will advertise progressively
larger buffer sizes on successive queries, until
responses begin timing out or
<span><strong class="command">edns-udp-size</strong></span> is reached.
</p>
<p>
The default buffer sizes used by <span><strong class="command">named</strong></span>
are 512, 1232, 1432, and 4096, but never exceeding
<span><strong class="command">edns-udp-size</strong></span>. (The values 1232 and
1432 are chosen to allow for an IPv4/IPv6 encapsulated
UDP message to be sent without fragmentation at the
minimum MTU sizes for Ethernet and IPv6 networks.)
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-udp-size</strong></span></span></dt>
<dd>
<p>
Sets the maximum EDNS UDP message size
<span><strong class="command">named</strong></span> will send in bytes.
Valid values are 512 to 4096 (values outside this
range will be silently adjusted to the nearest
value within it). The default value is 4096.
</p>
<p>
This value applies to responses sent by a server; to
set the advertised buffer size in queries, see
<span><strong class="command">edns-udp-size</strong></span>.
</p>
<p>
The usual reason for setting
<span><strong class="command">max-udp-size</strong></span> to a non-default
value is to get UDP answers to pass through broken
firewalls that block fragmented packets and/or
block UDP packets that are greater than 512 bytes.
This is independent of the advertised receive
buffer (<span><strong class="command">edns-udp-size</strong></span>).
</p>
<p>
Setting this to a low value will encourage additional
TCP traffic to the nameserver.
</p>
</dd>
<dt><span class="term"><span><strong class="command">masterfile-format</strong></span></span></dt>
<dd>
<p>Specifies
the file format of zone files (see
<a href="Bv9ARM.ch06.html#zonefile_format" title="Additional File Formats">the section called &#8220;Additional File Formats&#8221;</a>).
The default value is <code class="constant">text</code>, which is the
standard textual representation, except for slave zones,
in which the default value is <code class="constant">raw</code>.
Files in other formats than <code class="constant">text</code> are
typically expected to be generated by the
<span><strong class="command">named-compilezone</strong></span> tool, or dumped by
<span><strong class="command">named</strong></span>.
</p>
<p>
Note that when a zone file in a different format than
<code class="constant">text</code> is loaded, <span><strong class="command">named</strong></span>
may omit some of the checks which would be performed for a
file in the <code class="constant">text</code> format. In particular,
<span><strong class="command">check-names</strong></span> checks do not apply
for the <code class="constant">raw</code> format. This means
a zone file in the <code class="constant">raw</code> format
must be generated with the same check level as that
specified in the <span><strong class="command">named</strong></span> configuration
file. Also, <code class="constant">map</code> format files are
loaded directly into memory via memory mapping, with only
minimal checking.
</p>
<p>
This statement sets the
<span><strong class="command">masterfile-format</strong></span> for all zones,
but can be overridden on a per-zone or per-view basis
by including a <span><strong class="command">masterfile-format</strong></span>
statement within the <span><strong class="command">zone</strong></span> or
<span><strong class="command">view</strong></span> block in the configuration
file.
</p>
</dd>
<dt><span class="term"><span><strong class="command">masterfile-style</strong></span></span></dt>
<dd>
<p>
Specifies the formatting of zone files during dump
when the <code class="option">masterfile-format</code> is
<code class="constant">text</code>. (This option is ignored
with any other <code class="option">masterfile-format</code>.)
</p>
<p>
When set to <code class="constant">relative</code>,
records are printed in a multi-line format with owner
names expressed relative to a shared origin. When set
to <code class="constant">full</code>, records are printed in
a single-line format with absolute owner names.
The <code class="constant">full</code> format is most suitable
when a zone file needs to be processed automatically
by a script. The <code class="constant">relative</code> format
is more human-readable, and is thus suitable when a
zone is to be edited by hand. The default is
<code class="constant">relative</code>.
</p>
</dd>
<dt>
<a name="max-recursion-depth"></a><span class="term"><span><strong class="command">max-recursion-depth</strong></span></span>
</dt>
<dd><p>
Sets the maximum number of levels of recursion
that are permitted at any one time while servicing
a recursive query. Resolving a name may require
looking up a name server address, which in turn
requires resolving another name, etc; if the number
of indirections exceeds this value, the recursive
query is terminated and returns SERVFAIL. The
default is 7.
</p></dd>
<dt>
<a name="max-recursion-queries"></a><span class="term"><span><strong class="command">max-recursion-queries</strong></span></span>
</dt>
<dd><p>
Sets the maximum number of iterative queries that
may be sent while servicing a recursive query.
If more queries are sent, the recursive query
is terminated and returns SERVFAIL. Queries to
look up top level comains such as "com" and "net"
and the DNS root zone are exempt from this limitation.
The default is 75.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt>
<dd>
<p>
The delay, in seconds, between sending sets of notify
messages for a zone. The default is five (5) seconds.
</p>
<p>
The overall rate that NOTIFY messages are sent for all
zones is controlled by <span><strong class="command">serial-query-rate</strong></span>.
</p>
</dd>
<dt><span class="term"><span><strong class="command">max-rsa-exponent-size</strong></span></span></dt>
<dd><p>
The maximum RSA exponent size, in bits, that will
be accepted when validating. Valid values are 35
to 4096 bits. The default zero (0) is also accepted
and is equivalent to 4096.
</p></dd>
<dt><span class="term"><span><strong class="command">prefetch</strong></span></span></dt>
<dd>
<p>
When a query is received for cached data which
is to expire shortly, <span><strong class="command">named</strong></span> can
refresh the data from the authoritative server
immediately, ensuring that the cache always has an
answer available.
</p>
<p>
The <code class="option">prefetch</code> specifies the
"trigger" TTL value at which prefetch of the current
query will take place: when a cache record with a
lower TTL value is encountered during query processing,
it will be refreshed. Valid trigger TTL values are 1 to
10 seconds. Values larger than 10 seconds will be silently
reduced to 10.
Setting a trigger TTL to zero (0) causes
prefetch to be disabled.
The default trigger TTL is <code class="literal">2</code>.
</p>
<p>
An optional second argument specifies the "eligibility"
TTL: the smallest <span class="emphasis"><em>original</em></span>
TTL value that will be accepted for a record to be
eligible for prefetching. The eligibility TTL must
be at least six seconds longer than the trigger TTL;
if it isn't, <span><strong class="command">named</strong></span> will silently
adjust it upward.
The default eligibility TTL is <code class="literal">9</code>.
</p>
</dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="builtin"></a>Built-in server information zones</h4></div></div></div>
<p>
The server provides some helpful diagnostic information
through a number of built-in zones under the
pseudo-top-level-domain <code class="literal">bind</code> in the
<span><strong class="command">CHAOS</strong></span> class. These zones are part
of a
built-in view (see <a href="Bv9ARM.ch06.html#view_statement_grammar" title="view Statement Grammar">the section called &#8220;<span><strong class="command">view</strong></span> Statement Grammar&#8221;</a>) of
class
<span><strong class="command">CHAOS</strong></span> which is separate from the
default view of class <span><strong class="command">IN</strong></span>. Most global
configuration options (<span><strong class="command">allow-query</strong></span>,
etc) will apply to this view, but some are locally
overridden: <span><strong class="command">notify</strong></span>,
<span><strong class="command">recursion</strong></span> and
<span><strong class="command">allow-new-zones</strong></span> are
always set to <strong class="userinput"><code>no</code></strong>, and
<span><strong class="command">rate-limit</strong></span> is set to allow
three responses per second.
</p>
<p>
If you need to disable these zones, use the options
below, or hide the built-in <span><strong class="command">CHAOS</strong></span>
view by
defining an explicit view of class <span><strong class="command">CHAOS</strong></span>
that matches all clients.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">version</strong></span></span></dt>
<dd><p>
The version the server should report
via a query of the name <code class="literal">version.bind</code>
with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
The default is the real version number of this server.
Specifying <span><strong class="command">version none</strong></span>
disables processing of the queries.
</p></dd>
<dt><span class="term"><span><strong class="command">hostname</strong></span></span></dt>
<dd><p>
The hostname the server should report via a query of
the name <code class="filename">hostname.bind</code>
with type <span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
This defaults to the hostname of the machine hosting the
name server as
found by the gethostname() function. The primary purpose of such queries
is to
identify which of a group of anycast servers is actually
answering your queries. Specifying <span><strong class="command">hostname none;</strong></span>
disables processing of the queries.
</p></dd>
<dt><span class="term"><span><strong class="command">server-id</strong></span></span></dt>
<dd><p>
The ID the server should report when receiving a Name
Server Identifier (NSID) query, or a query of the name
<code class="filename">ID.SERVER</code> with type
<span><strong class="command">TXT</strong></span>, class <span><strong class="command">CHAOS</strong></span>.
The primary purpose of such queries is to
identify which of a group of anycast servers is actually
answering your queries. Specifying <span><strong class="command">server-id none;</strong></span>
disables processing of the queries.
Specifying <span><strong class="command">server-id hostname;</strong></span> will cause <span><strong class="command">named</strong></span> to
use the hostname as found by the gethostname() function.
The default <span><strong class="command">server-id</strong></span> is <span><strong class="command">none</strong></span>.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="empty"></a>Built-in Empty Zones</h4></div></div></div>
<p>
The <span><strong class="command">named</strong></span> server has some built-in
empty zones (SOA and NS records only).
These are for zones that should normally be answered locally
and which queries should not be sent to the Internet's root
servers. The official servers which cover these namespaces
return NXDOMAIN responses to these queries. In particular,
these cover the reverse namespaces for addresses from
RFC 1918, RFC 4193, RFC 5737 and RFC 6598. They also include the
reverse namespace for IPv6 local address (locally assigned),
IPv6 link local addresses, the IPv6 loopback address and the
IPv6 unknown address.
</p>
<p>
The server will attempt to determine if a built-in zone
already exists or is active (covered by a forward-only
forwarding declaration) and will not create an empty
zone in that case.
</p>
<p>
The current list of empty zones is:
</p>
<div class="itemizedlist"><ul type="disc">
<li>10.IN-ADDR.ARPA</li>
<li>16.172.IN-ADDR.ARPA</li>
<li>17.172.IN-ADDR.ARPA</li>
<li>18.172.IN-ADDR.ARPA</li>
<li>19.172.IN-ADDR.ARPA</li>
<li>20.172.IN-ADDR.ARPA</li>
<li>21.172.IN-ADDR.ARPA</li>
<li>22.172.IN-ADDR.ARPA</li>
<li>23.172.IN-ADDR.ARPA</li>
<li>24.172.IN-ADDR.ARPA</li>
<li>25.172.IN-ADDR.ARPA</li>
<li>26.172.IN-ADDR.ARPA</li>
<li>27.172.IN-ADDR.ARPA</li>
<li>28.172.IN-ADDR.ARPA</li>
<li>29.172.IN-ADDR.ARPA</li>
<li>30.172.IN-ADDR.ARPA</li>
<li>31.172.IN-ADDR.ARPA</li>
<li>168.192.IN-ADDR.ARPA</li>
<li>64.100.IN-ADDR.ARPA</li>
<li>65.100.IN-ADDR.ARPA</li>
<li>66.100.IN-ADDR.ARPA</li>
<li>67.100.IN-ADDR.ARPA</li>
<li>68.100.IN-ADDR.ARPA</li>
<li>69.100.IN-ADDR.ARPA</li>
<li>70.100.IN-ADDR.ARPA</li>
<li>71.100.IN-ADDR.ARPA</li>
<li>72.100.IN-ADDR.ARPA</li>
<li>73.100.IN-ADDR.ARPA</li>
<li>74.100.IN-ADDR.ARPA</li>
<li>75.100.IN-ADDR.ARPA</li>
<li>76.100.IN-ADDR.ARPA</li>
<li>77.100.IN-ADDR.ARPA</li>
<li>78.100.IN-ADDR.ARPA</li>
<li>79.100.IN-ADDR.ARPA</li>
<li>80.100.IN-ADDR.ARPA</li>
<li>81.100.IN-ADDR.ARPA</li>
<li>82.100.IN-ADDR.ARPA</li>
<li>83.100.IN-ADDR.ARPA</li>
<li>84.100.IN-ADDR.ARPA</li>
<li>85.100.IN-ADDR.ARPA</li>
<li>86.100.IN-ADDR.ARPA</li>
<li>87.100.IN-ADDR.ARPA</li>
<li>88.100.IN-ADDR.ARPA</li>
<li>89.100.IN-ADDR.ARPA</li>
<li>90.100.IN-ADDR.ARPA</li>
<li>91.100.IN-ADDR.ARPA</li>
<li>92.100.IN-ADDR.ARPA</li>
<li>93.100.IN-ADDR.ARPA</li>
<li>94.100.IN-ADDR.ARPA</li>
<li>95.100.IN-ADDR.ARPA</li>
<li>96.100.IN-ADDR.ARPA</li>
<li>97.100.IN-ADDR.ARPA</li>
<li>98.100.IN-ADDR.ARPA</li>
<li>99.100.IN-ADDR.ARPA</li>
<li>100.100.IN-ADDR.ARPA</li>
<li>101.100.IN-ADDR.ARPA</li>
<li>102.100.IN-ADDR.ARPA</li>
<li>103.100.IN-ADDR.ARPA</li>
<li>104.100.IN-ADDR.ARPA</li>
<li>105.100.IN-ADDR.ARPA</li>
<li>106.100.IN-ADDR.ARPA</li>
<li>107.100.IN-ADDR.ARPA</li>
<li>108.100.IN-ADDR.ARPA</li>
<li>109.100.IN-ADDR.ARPA</li>
<li>110.100.IN-ADDR.ARPA</li>
<li>111.100.IN-ADDR.ARPA</li>
<li>112.100.IN-ADDR.ARPA</li>
<li>113.100.IN-ADDR.ARPA</li>
<li>114.100.IN-ADDR.ARPA</li>
<li>115.100.IN-ADDR.ARPA</li>
<li>116.100.IN-ADDR.ARPA</li>
<li>117.100.IN-ADDR.ARPA</li>
<li>118.100.IN-ADDR.ARPA</li>
<li>119.100.IN-ADDR.ARPA</li>
<li>120.100.IN-ADDR.ARPA</li>
<li>121.100.IN-ADDR.ARPA</li>
<li>122.100.IN-ADDR.ARPA</li>
<li>123.100.IN-ADDR.ARPA</li>
<li>124.100.IN-ADDR.ARPA</li>
<li>125.100.IN-ADDR.ARPA</li>
<li>126.100.IN-ADDR.ARPA</li>
<li>127.100.IN-ADDR.ARPA</li>
<li>0.IN-ADDR.ARPA</li>
<li>127.IN-ADDR.ARPA</li>
<li>254.169.IN-ADDR.ARPA</li>
<li>2.0.192.IN-ADDR.ARPA</li>
<li>100.51.198.IN-ADDR.ARPA</li>
<li>113.0.203.IN-ADDR.ARPA</li>
<li>255.255.255.255.IN-ADDR.ARPA</li>
<li>0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
<li>1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
<li>8.B.D.0.1.0.0.2.IP6.ARPA</li>
<li>D.F.IP6.ARPA</li>
<li>8.E.F.IP6.ARPA</li>
<li>9.E.F.IP6.ARPA</li>
<li>A.E.F.IP6.ARPA</li>
<li>B.E.F.IP6.ARPA</li>
</ul></div>
<p>
</p>
<p>
Empty zones are settable at the view level and only apply to
views of class IN. Disabled empty zones are only inherited
from options if there are no disabled empty zones specified
at the view level. To override the options list of disabled
zones, you can disable the root zone at the view level, for example:
</p>
<pre class="programlisting">
disable-empty-zone ".";
</pre>
<p>
</p>
<p>
If you are using the address ranges covered here, you should
already have reverse zones covering the addresses you use.
In practice this appears to not be the case with many queries
being made to the infrastructure servers for names in these
spaces. So many in fact that sacrificial servers were needed
to be deployed to channel the query load away from the
infrastructure servers.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
The real parent servers for these zones should disable all
empty zone under the parent zone they serve. For the real
root servers, this is all built-in empty zones. This will
enable them to return referrals to deeper in the tree.
</div>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">empty-server</strong></span></span></dt>
<dd><p>
Specify what server name will appear in the returned
SOA record for empty zones. If none is specified, then
the zone's name will be used.
</p></dd>
<dt><span class="term"><span><strong class="command">empty-contact</strong></span></span></dt>
<dd><p>
Specify what contact name will appear in the returned
SOA record for empty zones. If none is specified, then
"." will be used.
</p></dd>
<dt><span class="term"><span><strong class="command">empty-zones-enable</strong></span></span></dt>
<dd><p>
Enable or disable all empty zones. By default, they
are enabled.
</p></dd>
<dt><span class="term"><span><strong class="command">disable-empty-zone</strong></span></span></dt>
<dd><p>
Disable individual empty zones. By default, none are
disabled. This option can be specified multiple times.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="acache"></a>Additional Section Caching</h4></div></div></div>
<p>
The additional section cache, also called <span><strong class="command">acache</strong></span>,
is an internal cache to improve the response performance of BIND 9.
When additional section caching is enabled, BIND 9 will
cache an internal short-cut to the additional section content for
each answer RR.
Note that <span><strong class="command">acache</strong></span> is an internal caching
mechanism of BIND 9, and is not related to the DNS caching
server function.
</p>
<p>
Additional section caching does not change the
response content (except the RRsets ordering of the additional
section, see below), but can improve the response performance
significantly.
It is particularly effective when BIND 9 acts as an authoritative
server for a zone that has many delegations with many glue RRs.
</p>
<p>
In order to obtain the maximum performance improvement
from additional section caching, setting
<span><strong class="command">additional-from-cache</strong></span>
to <span><strong class="command">no</strong></span> is recommended, since the current
implementation of <span><strong class="command">acache</strong></span>
does not short-cut of additional section information from the
DNS cache data.
</p>
<p>
One obvious disadvantage of <span><strong class="command">acache</strong></span> is
that it requires much more
memory for the internal cached data.
Thus, if the response performance does not matter and memory
consumption is much more critical, the
<span><strong class="command">acache</strong></span> mechanism can be
disabled by setting <span><strong class="command">acache-enable</strong></span> to
<span><strong class="command">no</strong></span>.
It is also possible to specify the upper limit of memory
consumption
for acache by using <span><strong class="command">max-acache-size</strong></span>.
</p>
<p>
Additional section caching also has a minor effect on the
RRset ordering in the additional section.
Without <span><strong class="command">acache</strong></span>,
<span><strong class="command">cyclic</strong></span> order is effective for the additional
section as well as the answer and authority sections.
However, additional section caching fixes the ordering when it
first caches an RRset for the additional section, and the same
ordering will be kept in succeeding responses, regardless of the
setting of <span><strong class="command">rrset-order</strong></span>.
The effect of this should be minor, however, since an
RRset in the additional section
typically only contains a small number of RRs (and in many cases
it only contains a single RR), in which case the
ordering does not matter much.
</p>
<p>
The following is a summary of options related to
<span><strong class="command">acache</strong></span>.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">acache-enable</strong></span></span></dt>
<dd><p>
If <span><strong class="command">yes</strong></span>, additional section caching is
enabled. The default value is <span><strong class="command">no</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">acache-cleaning-interval</strong></span></span></dt>
<dd><p>
The server will remove stale cache entries, based on an LRU
based
algorithm, every <span><strong class="command">acache-cleaning-interval</strong></span> minutes.
The default is 60 minutes.
If set to 0, no periodic cleaning will occur.
</p></dd>
<dt><span class="term"><span><strong class="command">max-acache-size</strong></span></span></dt>
<dd><p>
The maximum amount of memory in bytes to use for the server's acache.
When the amount of data in the acache reaches this limit,
the server
will clean more aggressively so that the limit is not
exceeded.
In a server with multiple views, the limit applies
separately to the
acache of each view.
The default is <code class="literal">16M</code>.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2590341"></a>Content Filtering</h4></div></div></div>
<p>
<acronym class="acronym">BIND</acronym> 9 provides the ability to filter
out DNS responses from external DNS servers containing
certain types of data in the answer section.
Specifically, it can reject address (A or AAAA) records if
the corresponding IPv4 or IPv6 addresses match the given
<code class="varname">address_match_list</code> of the
<span><strong class="command">deny-answer-addresses</strong></span> option.
It can also reject CNAME or DNAME records if the "alias"
name (i.e., the CNAME alias or the substituted query name
due to DNAME) matches the
given <code class="varname">namelist</code> of the
<span><strong class="command">deny-answer-aliases</strong></span> option, where
"match" means the alias name is a subdomain of one of
the <code class="varname">name_list</code> elements.
If the optional <code class="varname">namelist</code> is specified
with <span><strong class="command">except-from</strong></span>, records whose query name
matches the list will be accepted regardless of the filter
setting.
Likewise, if the alias name is a subdomain of the
corresponding zone, the <span><strong class="command">deny-answer-aliases</strong></span>
filter will not apply;
for example, even if "example.com" is specified for
<span><strong class="command">deny-answer-aliases</strong></span>,
</p>
<pre class="programlisting">www.example.com. CNAME xxx.example.com.</pre>
<p>
returned by an "example.com" server will be accepted.
</p>
<p>
In the <code class="varname">address_match_list</code> of the
<span><strong class="command">deny-answer-addresses</strong></span> option, only
<code class="varname">ip_addr</code>
and <code class="varname">ip_prefix</code>
are meaningful;
any <code class="varname">key_id</code> will be silently ignored.
</p>
<p>
If a response message is rejected due to the filtering,
the entire message is discarded without being cached, and
a SERVFAIL error will be returned to the client.
</p>
<p>
This filtering is intended to prevent "DNS rebinding attacks," in
which an attacker, in response to a query for a domain name the
attacker controls, returns an IP address within your own network or
an alias name within your own domain.
A naive web browser or script could then serve as an
unintended proxy, allowing the attacker
to get access to an internal node of your local network
that couldn't be externally accessed otherwise.
See the paper available at
<a href="http://portal.acm.org/citation.cfm?id=1315245.1315298" target="_top">
http://portal.acm.org/citation.cfm?id=1315245.1315298
</a>
for more details about the attacks.
</p>
<p>
For example, if you own a domain named "example.net" and
your internal network uses an IPv4 prefix 192.0.2.0/24,
you might specify the following rules:
</p>
<pre class="programlisting">deny-answer-addresses { 192.0.2.0/24; } except-from { "example.net"; };
deny-answer-aliases { "example.net"; };
</pre>
<p>
If an external attacker lets a web browser in your local
network look up an IPv4 address of "attacker.example.com",
the attacker's DNS server would return a response like this:
</p>
<pre class="programlisting">attacker.example.com. A 192.0.2.1</pre>
<p>
in the answer section.
Since the rdata of this record (the IPv4 address) matches
the specified prefix 192.0.2.0/24, this response will be
ignored.
</p>
<p>
On the other hand, if the browser looks up a legitimate
internal web server "www.example.net" and the
following response is returned to
the <acronym class="acronym">BIND</acronym> 9 server
</p>
<pre class="programlisting">www.example.net. A 192.0.2.2</pre>
<p>
it will be accepted since the owner name "www.example.net"
matches the <span><strong class="command">except-from</strong></span> element,
"example.net".
</p>
<p>
Note that this is not really an attack on the DNS per se.
In fact, there is nothing wrong for an "external" name to
be mapped to your "internal" IP address or domain name
from the DNS point of view.
It might actually be provided for a legitimate purpose,
such as for debugging.
As long as the mapping is provided by the correct owner,
it is not possible or does not make sense to detect
whether the intent of the mapping is legitimate or not
within the DNS.
The "rebinding" attack must primarily be protected at the
application that uses the DNS.
For a large site, however, it may be difficult to protect
all possible applications at once.
This filtering feature is provided only to help such an
operational environment;
it is generally discouraged to turn it on unless you are
very sure you have no other choice and the attack is a
real threat for your applications.
</p>
<p>
Care should be particularly taken if you want to use this
option for addresses within 127.0.0.0/8.
These addresses are obviously "internal", but many
applications conventionally rely on a DNS mapping from
some name to such an address.
Filtering out DNS records containing this address
spuriously can break such applications.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2590672"></a>Response Policy Zone (RPZ) Rewriting</h4></div></div></div>
<p>
<acronym class="acronym">BIND</acronym> 9 includes a limited
mechanism to modify DNS responses for requests
analogous to email anti-spam DNS blacklists.
Responses can be changed to deny the existence of domains (NXDOMAIN),
deny the existence of IP addresses for domains (NODATA),
or contain other IP addresses or data.
</p>
<p>
Response policy zones are named in the
<span><strong class="command">response-policy</strong></span> option for the view or among the
global options if there is no response-policy option for the view.
Response policy zones are ordinary DNS zones containing RRsets
that can be queried normally if allowed.
It is usually best to restrict those queries with something like
<span><strong class="command">allow-query { localhost; };</strong></span>.
</p>
<p>
A <span><strong class="command">response-policy</strong></span> option can support
multiple policy zones. To maximize performance, a radix
tree is used to quickly identify response policy zones
containing triggers that match the current query. This
imposes an upper limit of 32 on the number of policy zones
in a single <span><strong class="command">response-policy</strong></span> option; more
than that is a configuration error.
</p>
<p>
Five policy triggers can be encoded in RPZ records.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">RPZ-CLIENT-IP</strong></span></span></dt>
<dd>
<p>
IP records are triggered by the IP address of the
DNS client.
Client IP address triggers are encoded in records that have
owner names that are subdomains of
<span><strong class="command">rpz-client-ip</strong></span> relativized to the
policy zone origin name
and encode an address or address block.
IPv4 addresses are represented as
<strong class="userinput"><code>prefixlength.B4.B3.B2.B1.rpz-client-ip</code></strong>.
The IPv4 prefix length must be between 1 and 32.
All four bytes, B4, B3, B2, and B1, must be present.
B4 is the decimal value of the least significant byte of the
IPv4 address as in IN-ADDR.ARPA.
</p>
<p>
IPv6 addresses are encoded in a format similar
to the standard IPv6 text representation,
<strong class="userinput"><code>prefixlength.W8.W7.W6.W5.W4.W3.W2.W1.rpz-client-ip</code></strong>.
Each of W8,...,W1 is a one to four digit hexadecimal number
representing 16 bits of the IPv6 address as in the standard
text representation of IPv6 addresses, but reversed as in
IP6.ARPA. (Note that this representation of IPv6
address is different from IP6.ARPA where each hex
digit occupies a label.)
All 8 words must be present except when one set of consecutive
zero words is replaced with <strong class="userinput"><code>.zz.</code></strong>
analogous to double colons (::) in standard IPv6 text
encodings.
The IPv6 prefix length must be between 1 and 128.
</p>
</dd>
<dt><span class="term"><span><strong class="command">QNAME</strong></span></span></dt>
<dd><p>
QNAME policy records are triggered by query names of
requests and targets of CNAME records resolved to generate
the response.
The owner name of a QNAME policy record is
the query name relativized to the policy zone.
</p></dd>
<dt><span class="term"><span><strong class="command">RPZ-IP</strong></span></span></dt>
<dd><p>
IP triggers are IP addresses in an
A or AAAA record in the ANSWER section of a response.
They are encoded like client-IP triggers except as
subdomains of <span><strong class="command">rpz-ip</strong></span>.
</p></dd>
<dt><span class="term"><span><strong class="command">RPZ-NSDNAME</strong></span></span></dt>
<dd><p>
NSDNAME triggers match names of authoritative servers
for the query name, a parent of the query name, a CNAME for
query name, or a parent of a CNAME.
They are encoded as subdomains of
<span><strong class="command">rpz-nsdname</strong></span> relativized
to the RPZ origin name.
NSIP triggers match IP addresses in A and
AAAA RRsets for domains that can be checked against NSDNAME
policy records.
</p></dd>
<dt><span class="term"><span><strong class="command">RPZ-NSIP</strong></span></span></dt>
<dd><p>
NSIP triggers are encoded like IP triggers except as
subdomains of <span><strong class="command">rpz-nsip</strong></span>.
NSDNAME and NSIP triggers are checked only for names with at
least <span><strong class="command">min-ns-dots</strong></span> dots.
The default value of <span><strong class="command">min-ns-dots</strong></span> is 1 to
exclude top level domains.
</p></dd>
</dl></div>
<p>
</p>
<p>
The query response is checked against all response policy zones,
so two or more policy records can be triggered by a response.
Because DNS responses are rewritten according to at most one
policy record, a single record encoding an action (other than
<span><strong class="command">DISABLED</strong></span> actions) must be chosen.
Triggers or the records that encode them are chosen for the
rewriting in the following order:
</p>
<div class="orderedlist"><ol type="1">
<li>Choose the triggered record in the zone that appears
first in the <span><strong class="command">response-policy</strong></span> option.
</li>
<li>Prefer CLIENT-IP to QNAME to IP to NSDNAME to NSIP
triggers in a single zone.
</li>
<li>Among NSDNAME triggers, prefer the
trigger that matches the smallest name under the DNSSEC ordering.
</li>
<li>Among IP or NSIP triggers, prefer the trigger
with the longest prefix.
</li>
<li>Among triggers with the same prefix length,
prefer the IP or NSIP trigger that matches
the smallest IP address.
</li>
</ol></div>
<p>
</p>
<p>
When the processing of a response is restarted to resolve
DNAME or CNAME records and a policy record set has
not been triggered,
all response policy zones are again consulted for the
DNAME or CNAME names and addresses.
</p>
<p>
RPZ record sets are any types of DNS record except
DNAME or DNSSEC that encode actions or responses to
individual queries.
Any of the policies can be used with any of the triggers.
For example, while the <span><strong class="command">TCP-only</strong></span> policy is
commonly used with <span><strong class="command">client-IP</strong></span> triggers,
it can be used with any type of trigger to force the use of
TCP for responses with owner names in a zone.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">PASSTHRU</strong></span></span></dt>
<dd><p>
The whitelist policy is specified
by a CNAME whose target is <span><strong class="command">rpz-passthru</strong></span>.
It causes the response to not be rewritten
and is most often used to "poke holes" in policies for
CIDR blocks.
</p></dd>
<dt><span class="term"><span><strong class="command">DROP</strong></span></span></dt>
<dd><p>
The blacklist policy is specified
by a CNAME whose target is <span><strong class="command">rpz-drop</strong></span>.
It causes the response to be discarded.
Nothing is sent to the DNS client.
</p></dd>
<dt><span class="term"><span><strong class="command">TCP-Only</strong></span></span></dt>
<dd><p>
The "slip" policy is specified
by a CNAME whose target is <span><strong class="command">rpz-tcp-only</strong></span>.
It changes UDP responses to short, truncated DNS responses
that require the DNS client to try again with TCP.
It is used to mitigate distributed DNS reflection attacks.
</p></dd>
<dt><span class="term"><span><strong class="command">NXDOMAIN</strong></span></span></dt>
<dd><p>
The domain undefined response is encoded
by a CNAME whose target is the root domain (.)
</p></dd>
<dt><span class="term"><span><strong class="command">NODATA</strong></span></span></dt>
<dd><p>
The empty set of resource records is specified by
CNAME whose target is the wildcard top-level
domain (*.).
It rewrites the response to NODATA or ANCOUNT=1.
</p></dd>
<dt><span class="term"><span><strong class="command">Local Data</strong></span></span></dt>
<dd>
<p>
A set of ordinary DNS records can be used to answer queries.
Queries for record types not the set are answered with
NODATA.
</p>
<p>
A special form of local data is a CNAME whose target is a
wildcard such as *.example.com.
It is used as if were an ordinary CNAME after the astrisk (*)
has been replaced with the query name.
The purpose for this special form is query logging in the
walled garden's authority DNS server.
</p>
</dd>
</dl></div>
<p>
</p>
<p>
All of the actions specified in all of the individual records
in a policy zone
can be overridden with a <span><strong class="command">policy</strong></span> clause in the
<span><strong class="command">response-policy</strong></span> option.
An organization using a policy zone provided by another
organization might use this mechanism to redirect domains
to its own walled garden.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">GIVEN</strong></span></span></dt>
<dd><p>The placeholder policy says "do not override but
perform the action specified in the zone."
</p></dd>
<dt><span class="term"><span><strong class="command">DISABLED</strong></span></span></dt>
<dd><p>
The testing override policy causes policy zone records to do
nothing but log what they would have done if the
policy zone were not disabled.
The response to the DNS query will be written (or not)
according to any triggered policy records that are not
disabled.
Disabled policy zones should appear first,
because they will often not be logged
if a higher precedence trigger is found first.
</p></dd>
<dt>
<span class="term"><span><strong class="command">PASSTHRU</strong></span>, </span><span class="term"><span><strong class="command">DROP</strong></span>, </span><span class="term"><span><strong class="command">TCP-Only</strong></span>, </span><span class="term"><span><strong class="command">NXDOMAIN</strong></span>, </span><span class="term"><span><strong class="command">NODATA</strong></span></span>
</dt>
<dd><p>
override with the corresponding per-record policy.
</p></dd>
<dt><span class="term"><span><strong class="command">CNAME domain</strong></span></span></dt>
<dd><p>
causes all RPZ policy records to act as if they were
"cname domain" records.
</p></dd>
</dl></div>
<p>
</p>
<p>
By default, the actions encoded in a response policy zone
are applied only to queries that ask for recursion (RD=1).
That default can be changed for a single policy zone or
all response policy zones in a view
with a <span><strong class="command">recursive-only no</strong></span> clause.
This feature is useful for serving the same zone files
both inside and outside an RFC 1918 cloud and using RPZ to
delete answers that would otherwise contain RFC 1918 values
on the externally visible name server or view.
</p>
<p>
Also by default, RPZ actions are applied only to DNS requests
that either do not request DNSSEC metadata (DO=0) or when no
DNSSEC records are available for request name in the original
zone (not the response policy zone). This default can be
changed for all response policy zones in a view with a
<span><strong class="command">break-dnssec yes</strong></span> clause. In that case, RPZ
actions are applied regardless of DNSSEC. The name of the
clause option reflects the fact that results rewritten by RPZ
actions cannot verify.
</p>
<p>
No DNS records are needed for a QNAME or Client-IP trigger.
The name or IP address itself is sufficient,
so in principle the query name need not be recursively resolved.
However, not resolving the requested
name can leak the fact that response policy rewriting is in use
and that the name is listed in a policy zone to operators of
servers for listed names. To prevent that information leak, by
default any recursion needed for a request is done before any
policy triggers are considered. Because listed domains often
have slow authoritative servers, this default behavior can cost
significant time.
The <span><strong class="command">qname-wait-recurse no</strong></span> option
overrides that default behavior when recursion cannot
change a non-error response.
The option does not affect QNAME or client-IP triggers
in policy zones listed
after other zones containing IP, NSIP and NSDNAME triggers, because
those may depend on the A, AAAA, and NS records that would be
found during recursive resolution. It also does not affect
DNSSEC requests (DO=1) unless <span><strong class="command">break-dnssec yes</strong></span>
is in use, because the response would depend on whether or not
RRSIG records were found during resolution.
Using this option can cause error responses such as SERVFAIL to
appear to be rewritten, since no recursion is being done to
discover problems at the authoritative server.
</p>
<p>
The TTL of a record modified by RPZ policies is set from the
TTL of the relevant record in policy zone. It is then limited
to a maximum value.
The <span><strong class="command">max-policy-ttl</strong></span> clause changes the
maximum seconds from its default of 5.
</p>
<p>
For example, you might use this option statement
</p>
<pre class="programlisting"> response-policy { zone "badlist"; };</pre>
<p>
and this zone statement
</p>
<pre class="programlisting"> zone "badlist" {type master; file "master/badlist"; allow-query {none;}; };</pre>
<p>
with this zone file
</p>
<pre class="programlisting">$TTL 1H
@ SOA LOCALHOST. named-mgr.example.com (1 1h 15m 30d 2h)
NS LOCALHOST.
; QNAME policy records. There are no periods (.) after the owner names.
nxdomain.domain.com CNAME . ; NXDOMAIN policy
*.nxdomain.domain.com CNAME . ; NXDOMAIN policy
nodata.domain.com CNAME *. ; NODATA policy
*.nodata.domain.com CNAME *. ; NODATA policy
bad.domain.com A 10.0.0.1 ; redirect to a walled garden
AAAA 2001:2::1
bzone.domain.com CNAME garden.example.com.
; do not rewrite (PASSTHRU) OK.DOMAIN.COM
ok.domain.com CNAME rpz-passthru.
; redirect x.bzone.domain.com to x.bzone.domain.com.garden.example.com
*.bzone.domain.com CNAME *.garden.example.com.
; IP policy records that rewrite all responses containing A records in 127/8
; except 127.0.0.1
8.0.0.0.127.rpz-ip CNAME .
32.1.0.0.127.rpz-ip CNAME rpz-passthru.
; NSDNAME and NSIP policy records
ns.domain.com.rpz-nsdname CNAME .
48.zz.2.2001.rpz-nsip CNAME .
; blacklist and whitelist some DNS clients
112.zz.2001.rpz-client-ip CNAME rpz-drop.
8.0.0.0.127.rpz-client-ip CNAME rpz-drop.
; force some DNS clients and responses in the example.com zone to TCP
16.0.0.1.10.rpz-client-ip CNAME rpz-tcp-only.
example.com CNAME rpz-tcp-only.
*.example.com CNAME rpz-tcp-only.
</pre>
<p>
RPZ can affect server performance.
Each configured response policy zone requires the server to
perform one to four additional database lookups before a
query can be answered.
For example, a DNS server with four policy zones, each with all
four kinds of response triggers, QNAME, IP, NSIP, and
NSDNAME, requires a total of 17 times as many database
lookups as a similar DNS server with no response policy zones.
A <acronym class="acronym">BIND9</acronym> server with adequate memory and one
response policy zone with QNAME and IP triggers might achieve a
maximum queries-per-second rate about 20% lower.
A server with four response policy zones with QNAME and IP
triggers might have a maximum QPS rate about 50% lower.
</p>
<p>
Responses rewritten by RPZ are counted in the
<span><strong class="command">RPZRewrites</strong></span> statistics.
</p>
<p>
The <span><strong class="command">log</strong></span> clause can be used to optionally
turn off rewrite logging for a particular response policy
zone. By default, all rewrites are logged.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2591456"></a>Response Rate Limiting</h4></div></div></div>
<p>
Excessive almost identical UDP <span class="emphasis"><em>responses</em></span>
can be controlled by configuring a
<span><strong class="command">rate-limit</strong></span> clause in an
<span><strong class="command">options</strong></span> or <span><strong class="command">view</strong></span> statement.
This mechanism keeps authoritative BIND 9 from being used
in amplifying reflection denial of service (DoS) attacks.
Short truncated (TC=1) responses can be sent to provide
rate-limited responses to legitimate clients within
a range of forged, attacked IP addresses.
Legitimate clients react to dropped or truncated response
by retrying with UDP or with TCP respectively.
</p>
<p>
This mechanism is intended for authoritative DNS servers.
It can be used on recursive servers but can slow
applications such as SMTP servers (mail receivers) and
HTTP clients (web browsers) that repeatedly request the
same domains.
When possible, closing "open" recursive servers is better.
</p>
<p>
Response rate limiting uses a "credit" or "token bucket" scheme.
Each combination of identical response and client
has a conceptual account that earns a specified number
of credits every second.
A prospective response debits its account by one.
Responses are dropped or truncated
while the account is negative.
Responses are tracked within a rolling window of time
which defaults to 15 seconds, but can be configured with
the <span><strong class="command">window</strong></span> option to any value from
1 to 3600 seconds (1 hour).
The account cannot become more positive than
the per-second limit
or more negative than <span><strong class="command">window</strong></span>
times the per-second limit.
When the specified number of credits for a class of
responses is set to 0, those responses are not rate limited.
</p>
<p>
The notions of "identical response" and "DNS client"
for rate limiting are not simplistic.
All responses to an address block are counted as if to a
single client.
The prefix lengths of addresses blocks are
specified with <span><strong class="command">ipv4-prefix-length</strong></span> (default 24)
and <span><strong class="command">ipv6-prefix-length</strong></span> (default 56).
</p>
<p>
All non-empty responses for a valid domain name (qname)
and record type (qtype) are identical and have a limit specified
with <span><strong class="command">responses-per-second</strong></span>
(default 0 or no limit).
All empty (NODATA) responses for a valid domain,
regardless of query type, are identical.
Responses in the NODATA class are limited by
<span><strong class="command">nodata-per-second</strong></span>
(default <span><strong class="command">responses-per-second</strong></span>).
Requests for any and all undefined subdomains of a given
valid domain result in NXDOMAIN errors, and are identical
regardless of query type.
They are limited by <span><strong class="command">nxdomains-per-second</strong></span>
(default <span><strong class="command">responses-per-second</strong></span>).
This controls some attacks using random names, but
can be relaxed or turned off (set to 0)
on servers that expect many legitimate
NXDOMAIN responses, such as from anti-spam blacklists.
Referrals or delegations to the server of a given
domain are identical and are limited by
<span><strong class="command">referrals-per-second</strong></span>
(default <span><strong class="command">responses-per-second</strong></span>).
</p>
<p>
Responses generated from local wildcards are counted and limited
as if they were for the parent domain name.
This controls flooding using random.wild.example.com.
</p>
<p>
All requests that result in DNS errors other
than NXDOMAIN, such as SERVFAIL and FORMERR, are identical
regardless of requested name (qname) or record type (qtype).
This controls attacks using invalid requests or distant,
broken authoritative servers.
By default the limit on errors is the same as the
<span><strong class="command">responses-per-second</strong></span> value,
but it can be set separately with
<span><strong class="command">errors-per-second</strong></span>.
</p>
<p>
Many attacks using DNS involve UDP requests with forged source
addresses.
Rate limiting prevents the use of BIND 9 to flood a network
with responses to requests with forged source addresses,
but could let a third party block responses to legitimate requests.
There is a mechanism that can answer some legitimate
requests from a client whose address is being forged in a flood.
Setting <span><strong class="command">slip</strong></span> to 2 (its default) causes every
other UDP request to be answered with a small truncated (TC=1)
response.
The small size and reduced frequency, and so lack of
amplification, of "slipped" responses make them unattractive
for reflection DoS attacks.
<span><strong class="command">slip</strong></span> must be between 0 and 10.
A value of 0 does not "slip":
no truncated responses are sent due to rate limiting,
all responses are dropped.
A value of 1 causes every response to slip;
values between 2 and 10 cause every n'th response to slip.
Some error responses including REFUSED and SERVFAIL
cannot be replaced with truncated responses and are instead
leaked at the <span><strong class="command">slip</strong></span> rate.
</p>
<p>
(NOTE: Dropped responses from an authoritative server may
reduce the difficulty of a third party successfully forging
a response to a recursive resolver. The best security
against forged responses is for authoritative operators
to sign their zones using DNSSEC and for resolver operators
to validate the responses. When this is not an option,
operators who are more concerned with response integrity
than with flood mitigation may consider setting
<span><strong class="command">slip</strong></span> to 1, causing all rate-limited
responses to be truncated rather than dropped. This reduces
the effectiveness of rate-limiting against reflection attacks.)
</p>
<p>
When the approximate query per second rate exceeds
the <span><strong class="command">qps-scale</strong></span> value,
then the <span><strong class="command">responses-per-second</strong></span>,
<span><strong class="command">errors-per-second</strong></span>,
<span><strong class="command">nxdomains-per-second</strong></span> and
<span><strong class="command">all-per-second</strong></span> values are reduced by the
ratio of the current rate to the <span><strong class="command">qps-scale</strong></span> value.
This feature can tighten defenses during attacks.
For example, with
<span><strong class="command">qps-scale 250; responses-per-second 20;</strong></span> and
a total query rate of 1000 queries/second for all queries from
all DNS clients including via TCP,
then the effective responses/second limit changes to
(250/1000)*20 or 5.
Responses sent via TCP are not limited
but are counted to compute the query per second rate.
</p>
<p>
The optional <span><strong class="command">domain</strong></span> clause specifies
the namespace to which rate limits will apply. It
is possible to use different rate limits for different names
by specifying multiple <span><strong class="command">rate-limit</strong></span> blocks
with different <span><strong class="command">domain</strong></span> clauses.
The <span><strong class="command">rate-limit</strong></span> statement's
<span><strong class="command">domain</strong></span> most closely matches the query
name will be the one applied to a given query.
</p>
<p>
Rate limiters for different name spaces maintain
separate counters: If, for example, there is a
<span><strong class="command">rate-limit</strong></span> statement for "com" and
another for "example.com", queries matching "example.com"
will not be debited against the rate limiter for "com".
</p>
<p>
If a <span><strong class="command">rate-limit</strong></span> statement does not specify a
<span><strong class="command">domain</strong></span>, then it applies to the root domain
(".") and thus affects the entire DNS namespace, except those
portions covered by other <span><strong class="command">rate-limit</strong></span>
statements.
</p>
<p>
Communities of DNS clients can be given their own parameters or no
rate limiting by putting
<span><strong class="command">rate-limit</strong></span> statements in <span><strong class="command">view</strong></span>
statements instead of the global <span><strong class="command">option</strong></span>
statement.
A <span><strong class="command">rate-limit</strong></span> statement in a view replaces,
rather than supplementing, a <span><strong class="command">rate-limit</strong></span>
statement among the main options.
DNS clients within a view can be exempted from rate limits
with the <span><strong class="command">exempt-clients</strong></span> clause.
</p>
<p>
UDP responses of all kinds can be limited with the
<span><strong class="command">all-per-second</strong></span> phrase. This rate
limiting is unlike the rate limiting provided by
<span><strong class="command">responses-per-second</strong></span>,
<span><strong class="command">errors-per-second</strong></span>, and
<span><strong class="command">nxdomains-per-second</strong></span> on a DNS server
which are often invisible to the victim of a DNS
reflection attack. Unless the forged requests of the
attack are the same as the legitimate requests of the
victim, the victim's requests are not affected. Responses
affected by an <span><strong class="command">all-per-second</strong></span> limit
are always dropped; the <span><strong class="command">slip</strong></span> value
has no effect. An <span><strong class="command">all-per-second</strong></span>
limit should be at least 4 times as large as the other
limits, because single DNS clients often send bursts
of legitimate requests. For example, the receipt of a
single mail message can prompt requests from an SMTP
server for NS, PTR, A, and AAAA records as the incoming
SMTP/TCP/IP connection is considered. The SMTP server
can need additional NS, A, AAAA, MX, TXT, and SPF records
as it considers the STMP <span><strong class="command">Mail From</strong></span>
command. Web browsers often repeatedly resolve the
same names that are repeated in HTML &lt;IMG&gt; tags
in a page. <span><strong class="command">all-per-second</strong></span> is similar
to the rate limiting offered by firewalls but often
inferior. Attacks that justify ignoring the contents
of DNS responses are likely to be attacks on the DNS
server itself. They usually should be discarded before
the DNS server spends resources make TCP connections
or parsing DNS requests, but that rate limiting must
be done before the DNS server sees the requests.
</p>
<p>
The maximum size of the table used to track requests and
rate limit responses is set with <span><strong class="command">max-table-size</strong></span>.
Each entry in the table is between 40 and 80 bytes.
The table needs approximately as many entries as the number
of requests received per second.
The default is 20,000.
To reduce the cold start of growing the table,
<span><strong class="command">min-table-size</strong></span> (default 500)
can set the minimum table size.
Enable <span><strong class="command">rate-limit</strong></span> category logging to monitor
expansions of the table and inform
choices for the initial and maximum table size.
</p>
<p>
Use <span><strong class="command">log-only yes</strong></span> to test rate limiting parameters
without actually dropping any requests.
</p>
<p>
Responses dropped by rate limits are included in the
<span><strong class="command">RateDropped</strong></span> and <span><strong class="command">QryDropped</strong></span>
statistics.
Responses that truncated by rate limits are included in
<span><strong class="command">RateSlipped</strong></span> and <span><strong class="command">RespTruncated</strong></span>.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"></div>
<p>
Named supports NXDOMAIN redirection via two methods:
</p>
<div class="itemizedlist"><ul type="disc">
<li>Redirect zone <a href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone
Statement Grammar">the section called &#8220;<span><strong class="command">zone</strong></span>
Statement Grammar&#8221;</a>
</li>
<li>Redirect namespace</li>
</ul></div>
<p>
</p>
<p>
With both methods when named gets a NXDOMAIN response
it examines a seperate namespace to see if the NXDOMAIN
response should be replaced with a alternative response.
</p>
<p>
With a redirect zone (<span><strong class="command">zone "." { type redirect; };</strong></span>), the
data used to replace the NXDOMAIN is held in a single
zone which is not part of the normal namespace. All the
redirect information is contained in the zone; there are
no delegations.
</p>
<p>
With a redirect namespace (<span><strong class="command">option { nxdomain-redirect
&lt;suffix&gt; };</strong></span>) the data used to replace the
NXDOMAIN is part of the normal namespace and is looked up by
appending the specified suffix to the original query name.
This roughly doubles the cache required to process NXDOMAIN
responses as you have the original NXDOMAIN response and
the replacement data or a NXDOMAIN indicating that there
is no replacement.
</p>
<p>
If both a redirect zone and a redirect namespace are configured,
the redirect zone is tried first.
</p>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="server_statement_grammar"></a><span><strong class="command">server</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">server</strong></span> <em class="replaceable"><code>ip_addr[/prefixlen]</code></em> {
[<span class="optional"> bogus <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> provide-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> request-expire <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> request-nsid <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> send-cookie <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> edns <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> edns-version <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> nocookie-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> tcp-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> transfers <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> transfer-format <em class="replaceable"><code>( one-answer | many-answers )</code></em> ; ]</span>]
[<span class="optional"> keys { <em class="replaceable"><code>key_id</code></em> }; </span>]
[<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> query-source [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
[<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> query-source-v6 [<span class="optional"> address ( <em class="replaceable"><code>ip_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
[<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> use-queryport-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> queryport-pool-ports <em class="replaceable"><code>number</code></em>; </span>]
[<span class="optional"> queryport-pool-updateinterval <em class="replaceable"><code>number</code></em>; </span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="server_statement_definition_and_usage"></a><span><strong class="command">server</strong></span> Statement Definition and
Usage</h3></div></div></div>
<p>
The <span><strong class="command">server</strong></span> statement defines
characteristics
to be associated with a remote name server. If a prefix length is
specified, then a range of servers is covered. Only the most
specific
server clause applies regardless of the order in
<code class="filename">named.conf</code>.
</p>
<p>
The <span><strong class="command">server</strong></span> statement can occur at
the top level of the
configuration file or inside a <span><strong class="command">view</strong></span>
statement.
If a <span><strong class="command">view</strong></span> statement contains
one or more <span><strong class="command">server</strong></span> statements, only
those
apply to the view and any top-level ones are ignored.
If a view contains no <span><strong class="command">server</strong></span>
statements,
any top-level <span><strong class="command">server</strong></span> statements are
used as
defaults.
</p>
<p>
If you discover that a remote server is giving out bad data,
marking it as bogus will prevent further queries to it. The
default
value of <span><strong class="command">bogus</strong></span> is <span><strong class="command">no</strong></span>.
</p>
<p>
The <span><strong class="command">provide-ixfr</strong></span> clause determines
whether
the local server, acting as master, will respond with an
incremental
zone transfer when the given remote server, a slave, requests it.
If set to <span><strong class="command">yes</strong></span>, incremental transfer
will be provided
whenever possible. If set to <span><strong class="command">no</strong></span>,
all transfers
to the remote server will be non-incremental. If not set, the
value
of the <span><strong class="command">provide-ixfr</strong></span> option in the
view or
global options block is used as a default.
</p>
<p>
The <span><strong class="command">request-ixfr</strong></span> clause determines
whether
the local server, acting as a slave, will request incremental zone
transfers from the given remote server, a master. If not set, the
value of the <span><strong class="command">request-ixfr</strong></span> option in
the view or global options block is used as a default. It may
also be set in the zone block and, if set there, it will
override the global or view setting for that zone.
</p>
<p>
IXFR requests to servers that do not support IXFR will
automatically
fall back to AXFR. Therefore, there is no need to manually list
which servers support IXFR and which ones do not; the global
default
of <span><strong class="command">yes</strong></span> should always work.
The purpose of the <span><strong class="command">provide-ixfr</strong></span> and
<span><strong class="command">request-ixfr</strong></span> clauses is
to make it possible to disable the use of IXFR even when both
master
and slave claim to support it, for example if one of the servers
is buggy and crashes or corrupts data when IXFR is used.
</p>
<p>
The <span><strong class="command">request-expire</strong></span> clause determines
whether the local server, when acting as a slave, will
request the EDNS EXPIRE value. The EDNS EXPIRE value
indicates the remaining time before the zone data will
expire and need to be be refreshed. This is used
when a secondary server transfers a zone from another
secondary server; when transferring from the primary, the
expiration timer is set from the EXPIRE field of the SOA
record instead.
The default is <span><strong class="command">yes</strong></span>.
</p>
<p>
The <span><strong class="command">edns</strong></span> clause determines whether
the local server will attempt to use EDNS when communicating
with the remote server. The default is <span><strong class="command">yes</strong></span>.
</p>
<p>
The <span><strong class="command">edns-udp-size</strong></span> option sets the
EDNS UDP size that is advertised by <span><strong class="command">named</strong></span>
when querying the remote server. Valid values are 512
to 4096 bytes (values outside this range will be silently
adjusted to the nearest value within it). This option
is useful when you wish to advertise a different value
to this server than the value you advertise globally,
for example, when there is a firewall at the remote
site that is blocking large replies. (Note: Currently,
this sets a single UDP size for all packets sent to the
server; <span><strong class="command">named</strong></span> will not deviate from
this value. This differs from the behavior of
<span><strong class="command">edns-udp-size</strong></span> in <span><strong class="command">options</strong></span>
or <span><strong class="command">view</strong></span> statements, where it specifies
a maximum value. The <span><strong class="command">server</strong></span> statement
behavior may be brought into conformance with the
<span><strong class="command">options/view</strong></span> behavior in future releases.)
</p>
<p>
The <span><strong class="command">edns-version</strong></span> option sets the
maximum EDNS VERSION that will be sent to the server(s)
by the resolver. The actual EDNS version sent is still
subject to normal EDNS version negotiation rules (see
RFC 6891), the maximum EDNS version supported by the
server, and any other heuristics that indicate that a
lower version should be sent. This option is intended
to be used when a remote server reacts badly to a given
EDNS version or higher; it should be set to the highest
version the remote server is known to support. Valid
values are 0 to 255; higher values will be silently
adjusted. This option will not be needed until higher
EDNS versions than 0 are in use.
</p>
<p>
The <span><strong class="command">max-udp-size</strong></span> option sets the
maximum EDNS UDP message size <span><strong class="command">named</strong></span>
will send. Valid values are 512 to 4096 bytes (values
outside this range will be silently adjusted). This
option is useful when you know that there is a firewall
that is blocking large replies from <span><strong class="command">named</strong></span>.
</p>
<p>
The <span><strong class="command">nocookie-udp-size</strong></span> option sets the
maximum size of UDP responses that will be sent to
queries without a valid server COOKIE. The command
<span><strong class="command">max-udp-size</strong></span> option may further limit
the response size.
</p>
<p>
The <span><strong class="command">tcp-only</strong></span> option sets the transport
protocol to TCP. The default is to use the UDP transport
and to fallback on TCP only when a truncated response
is received.
</p>
<p>
The server supports two zone transfer methods. The first, <span><strong class="command">one-answer</strong></span>,
uses one DNS message per resource record transferred. <span><strong class="command">many-answers</strong></span> packs
as many resource records as possible into a message. <span><strong class="command">many-answers</strong></span> is
more efficient, but is only known to be understood by <acronym class="acronym">BIND</acronym> 9, <acronym class="acronym">BIND</acronym>
8.x, and patched versions of <acronym class="acronym">BIND</acronym>
4.9.5. You can specify which method
to use for a server with the <span><strong class="command">transfer-format</strong></span> option.
If <span><strong class="command">transfer-format</strong></span> is not
specified, the <span><strong class="command">transfer-format</strong></span>
specified
by the <span><strong class="command">options</strong></span> statement will be
used.
</p>
<p><span><strong class="command">transfers</strong></span>
is used to limit the number of concurrent inbound zone
transfers from the specified server. If no
<span><strong class="command">transfers</strong></span> clause is specified, the
limit is set according to the
<span><strong class="command">transfers-per-ns</strong></span> option.
</p>
<p>
The <span><strong class="command">keys</strong></span> clause identifies a
<span><strong class="command">key_id</strong></span> defined by the <span><strong class="command">key</strong></span> statement,
to be used for transaction security (TSIG, <a href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called &#8220;TSIG&#8221;</a>)
when talking to the remote server.
When a request is sent to the remote server, a request signature
will be generated using the key specified here and appended to the
message. A request originating from the remote server is not
required
to be signed by this key.
</p>
<p>
Only a single key per server is currently supported.
</p>
<p>
The <span><strong class="command">transfer-source</strong></span> and
<span><strong class="command">transfer-source-v6</strong></span> clauses specify
the IPv4 and IPv6 source
address to be used for zone transfer with the remote server,
respectively.
For an IPv4 remote server, only <span><strong class="command">transfer-source</strong></span> can
be specified.
Similarly, for an IPv6 remote server, only
<span><strong class="command">transfer-source-v6</strong></span> can be
specified.
For more details, see the description of
<span><strong class="command">transfer-source</strong></span> and
<span><strong class="command">transfer-source-v6</strong></span> in
<a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p>
<p>
The <span><strong class="command">notify-source</strong></span> and
<span><strong class="command">notify-source-v6</strong></span> clauses specify the
IPv4 and IPv6 source address to be used for notify
messages sent to remote servers, respectively. For an
IPv4 remote server, only <span><strong class="command">notify-source</strong></span>
can be specified. Similarly, for an IPv6 remote server,
only <span><strong class="command">notify-source-v6</strong></span> can be specified.
</p>
<p>
The <span><strong class="command">query-source</strong></span> and
<span><strong class="command">query-source-v6</strong></span> clauses specify the
IPv4 and IPv6 source address to be used for queries
sent to remote servers, respectively. For an IPv4
remote server, only <span><strong class="command">query-source</strong></span> can
be specified. Similarly, for an IPv6 remote server,
only <span><strong class="command">query-source-v6</strong></span> can be specified.
</p>
<p>
The <span><strong class="command">request-nsid</strong></span> clause determines
whether the local server will add a NSID EDNS option
to requests sent to the server. This overrides
<span><strong class="command">request-nsid</strong></span> set at the view or
option level.
</p>
<p>
The <span><strong class="command">send-cookie</strong></span> clause determines
whether the local server will add a COOKIE EDNS option
to requests sent to the server. This overrides
<span><strong class="command">send-cookie</strong></span> set at the view or
option level. The <span><strong class="command">named</strong></span> server may
determine that COOKIE is not supported by the remote server
and not add a COOKIE EDNS option to requests.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="statschannels"></a><span><strong class="command">statistics-channels</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">statistics-channels</strong></span> {
[ inet ( ip_addr | * ) [ port ip_port ]
[ allow { <em class="replaceable"><code> address_match_list </code></em> } ]; ]
[ inet ...; ]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2593078"></a><span><strong class="command">statistics-channels</strong></span> Statement Definition and
Usage</h3></div></div></div>
<p>
The <span><strong class="command">statistics-channels</strong></span> statement
declares communication channels to be used by system
administrators to get access to statistics information of
the name server.
</p>
<p>
This statement intends to be flexible to support multiple
communication protocols in the future, but currently only
HTTP access is supported.
It requires that BIND 9 be compiled with libxml2 and/or
json-c (also known as libjson0); the
<span><strong class="command">statistics-channels</strong></span> statement is
still accepted even if it is built without the library,
but any HTTP access will fail with an error.
</p>
<p>
An <span><strong class="command">inet</strong></span> control channel is a TCP socket
listening at the specified <span><strong class="command">ip_port</strong></span> on the
specified <span><strong class="command">ip_addr</strong></span>, which can be an IPv4 or IPv6
address. An <span><strong class="command">ip_addr</strong></span> of <code class="literal">*</code>
(asterisk) is
interpreted as the IPv4 wildcard address; connections will be
accepted on any of the system's IPv4 addresses.
To listen on the IPv6 wildcard address,
use an <span><strong class="command">ip_addr</strong></span> of <code class="literal">::</code>.
</p>
<p>
If no port is specified, port 80 is used for HTTP channels.
The asterisk "<code class="literal">*</code>" cannot be used for
<span><strong class="command">ip_port</strong></span>.
</p>
<p>
The attempt of opening a statistics channel is
restricted by the optional <span><strong class="command">allow</strong></span> clause.
Connections to the statistics channel are permitted based on the
<span><strong class="command">address_match_list</strong></span>.
If no <span><strong class="command">allow</strong></span> clause is present,
<span><strong class="command">named</strong></span> accepts connection
attempts from any address; since the statistics may
contain sensitive internal information, it is highly
recommended to restrict the source of connection requests
appropriately.
</p>
<p>
If no <span><strong class="command">statistics-channels</strong></span> statement is present,
<span><strong class="command">named</strong></span> will not open any communication channels.
</p>
<p>
The statistics are available in various formats and views
depending on the URI used to access them. For example, if
the statistics channel is configured to listen on 127.0.0.1
port 8888, then the statistics are accessible in XML format at
<a href="http://127.0.0.1:8888/" target="_top">http://127.0.0.1:8888/</a> or
<a href="http://127.0.0.1:8888/xml" target="_top">http://127.0.0.1:8888/xml</a>. A CSS file is
included which can format the XML statistics into tables
when viewed with a stylesheet-capable browser, and into
charts and graphs using the Google Charts API when using a
javascript-capable browser.
</p>
<p>
Applications that depend on a particular XML schema
can request
<a href="http://127.0.0.1:8888/xml/v2" target="_top">http://127.0.0.1:8888/xml/v2</a> for version 2
of the statistics XML schema or
<a href="http://127.0.0.1:8888/xml/v3" target="_top">http://127.0.0.1:8888/xml/v3</a> for version 3.
If the requested schema is supported by the server, then
it will respond; if not, it will return a "page not found"
error.
</p>
<p>
Broken-out subsets of the statistics can be viewed at
<a href="http://127.0.0.1:8888/xml/v3/status" target="_top">http://127.0.0.1:8888/xml/v3/status</a>
(server uptime and last reconfiguration time),
<a href="http://127.0.0.1:8888/xml/v3/server" target="_top">http://127.0.0.1:8888/xml/v3/server</a>
(server and resolver statistics),
<a href="http://127.0.0.1:8888/xml/v3/zones" target="_top">http://127.0.0.1:8888/xml/v3/zones</a>
(zone statistics),
<a href="http://127.0.0.1:8888/xml/v3/net" target="_top">http://127.0.0.1:8888/xml/v3/net</a>
(network status and socket statistics),
<a href="http://127.0.0.1:8888/xml/v3/mem" target="_top">http://127.0.0.1:8888/xml/v3/mem</a>
(memory manager statistics),
<a href="http://127.0.0.1:8888/xml/v3/tasks" target="_top">http://127.0.0.1:8888/xml/v3/tasks</a>
(task manager statistics), and
<a href="http://127.0.0.1:8888/xml/v3/traffic" target="_top">http://127.0.0.1:8888/xml/v3/traffic</a>
(traffic sizes).
</p>
<p>
The full set of statistics can also be read in JSON format at
<a href="http://127.0.0.1:8888/json" target="_top">http://127.0.0.1:8888/json</a>,
with the broken-out subsets at
<a href="http://127.0.0.1:8888/json/v1/status" target="_top">http://127.0.0.1:8888/json/v1/status</a>
(server uptime and last reconfiguration time),
<a href="http://127.0.0.1:8888/json/v1/server" target="_top">http://127.0.0.1:8888/json/v1/server</a>
(server and resolver statistics),
<a href="http://127.0.0.1:8888/json/v1/zones" target="_top">http://127.0.0.1:8888/json/v1/zones</a>
(zone statistics),
<a href="http://127.0.0.1:8888/json/v1/net" target="_top">http://127.0.0.1:8888/json/v1/net</a>
(network status and socket statistics),
<a href="http://127.0.0.1:8888/json/v1/mem" target="_top">http://127.0.0.1:8888/json/v1/mem</a>
(memory manager statistics),
<a href="http://127.0.0.1:8888/json/v1/tasks" target="_top">http://127.0.0.1:8888/json/v1/tasks</a>
(task manager statistics), and
<a href="http://127.0.0.1:8888/json/v1/traffic" target="_top">http://127.0.0.1:8888/json/v1/traffic</a>
(traffic sizes).
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="trusted-keys"></a><span><strong class="command">trusted-keys</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">trusted-keys</strong></span> {
<em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ;
[<span class="optional"> <em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; [<span class="optional">...</span>]</span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2593580"></a><span><strong class="command">trusted-keys</strong></span> Statement Definition
and Usage</h3></div></div></div>
<p>
The <span><strong class="command">trusted-keys</strong></span> statement defines
DNSSEC security roots. DNSSEC is described in <a href="Bv9ARM.ch04.html#DNSSEC" title="DNSSEC">the section called &#8220;DNSSEC&#8221;</a>. A security root is defined when the
public key for a non-authoritative zone is known, but
cannot be securely obtained through DNS, either because
it is the DNS root zone or because its parent zone is
unsigned. Once a key has been configured as a trusted
key, it is treated as if it had been validated and
proven secure. The resolver attempts DNSSEC validation
on all DNS data in subdomains of a security root.
</p>
<p>
All keys (and corresponding zones) listed in
<span><strong class="command">trusted-keys</strong></span> are deemed to exist regardless
of what parent zones say. Similarly for all keys listed in
<span><strong class="command">trusted-keys</strong></span> only those keys are
used to validate the DNSKEY RRset. The parent's DS RRset
will not be used.
</p>
<p>
The <span><strong class="command">trusted-keys</strong></span> statement can contain
multiple key entries, each consisting of the key's
domain name, flags, protocol, algorithm, and the Base-64
representation of the key data.
Spaces, tabs, newlines and carriage returns are ignored
in the key data, so the configuration may be split up into
multiple lines.
</p>
<p>
<span><strong class="command">trusted-keys</strong></span> may be set at the top level
of <code class="filename">named.conf</code> or within a view. If it is
set in both places, they are additive: keys defined at the top
level are inherited by all views, but keys defined in a view
are only used within that view.
</p>
<p>
Validation below specified names can be temporarily disabled
by using <span><strong class="command">rndc nta</strong></span>.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2593634"></a><span><strong class="command">managed-keys</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">managed-keys</strong></span> {
<em class="replaceable"><code>name</code></em> initial-key <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key-data</code></em> ;
[<span class="optional"> <em class="replaceable"><code>name</code></em> initial-key <em class="replaceable"><code>flags</code></em> <em class="replaceable"><code>protocol</code></em> <em class="replaceable"><code>algorithm</code></em> <em class="replaceable"><code>key-data</code></em> ; [<span class="optional">...</span>]</span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="managed-keys"></a><span><strong class="command">managed-keys</strong></span> Statement Definition
and Usage</h3></div></div></div>
<p>
The <span><strong class="command">managed-keys</strong></span> statement, like
<span><strong class="command">trusted-keys</strong></span>, defines DNSSEC
security roots. The difference is that
<span><strong class="command">managed-keys</strong></span> can be kept up to date
automatically, without intervention from the resolver
operator.
</p>
<p>
Suppose, for example, that a zone's key-signing
key was compromised, and the zone owner had to revoke and
replace the key. A resolver which had the old key in a
<span><strong class="command">trusted-keys</strong></span> statement would be
unable to validate this zone any longer; it would
reply with a SERVFAIL response code. This would
continue until the resolver operator had updated the
<span><strong class="command">trusted-keys</strong></span> statement with the new key.
</p>
<p>
If, however, the zone were listed in a
<span><strong class="command">managed-keys</strong></span> statement instead, then the
zone owner could add a "stand-by" key to the zone in advance.
<span><strong class="command">named</strong></span> would store the stand-by key, and
when the original key was revoked, <span><strong class="command">named</strong></span>
would be able to transition smoothly to the new key. It would
also recognize that the old key had been revoked, and cease
using that key to validate answers, minimizing the damage that
the compromised key could do.
</p>
<p>
A <span><strong class="command">managed-keys</strong></span> statement contains a list of
the keys to be managed, along with information about how the
keys are to be initialized for the first time. The only
initialization method currently supported (as of
<acronym class="acronym">BIND</acronym> 9.7.0) is <code class="literal">initial-key</code>.
This means the <span><strong class="command">managed-keys</strong></span> statement must
contain a copy of the initializing key. (Future releases may
allow keys to be initialized by other methods, eliminating this
requirement.)
</p>
<p>
Consequently, a <span><strong class="command">managed-keys</strong></span> statement
appears similar to a <span><strong class="command">trusted-keys</strong></span>, differing
in the presence of the second field, containing the keyword
<code class="literal">initial-key</code>. The difference is, whereas the
keys listed in a <span><strong class="command">trusted-keys</strong></span> continue to be
trusted until they are removed from
<code class="filename">named.conf</code>, an initializing key listed
in a <span><strong class="command">managed-keys</strong></span> statement is only trusted
<span class="emphasis"><em>once</em></span>: for as long as it takes to load the
managed key database and start the RFC 5011 key maintenance
process.
</p>
<p>
The first time <span><strong class="command">named</strong></span> runs with a managed key
configured in <code class="filename">named.conf</code>, it fetches the
DNSKEY RRset directly from the zone apex, and validates it
using the key specified in the <span><strong class="command">managed-keys</strong></span>
statement. If the DNSKEY RRset is validly signed, then it is
used as the basis for a new managed keys database.
</p>
<p>
From that point on, whenever <span><strong class="command">named</strong></span> runs, it
sees the <span><strong class="command">managed-keys</strong></span> statement, checks to
make sure RFC 5011 key maintenance has already been initialized
for the specified domain, and if so, it simply moves on. The
key specified in the <span><strong class="command">managed-keys</strong></span> is not
used to validate answers; it has been superseded by the key or
keys stored in the managed keys database.
</p>
<p>
The next time <span><strong class="command">named</strong></span> runs after a name
has been <span class="emphasis"><em>removed</em></span> from the
<span><strong class="command">managed-keys</strong></span> statement, the corresponding
zone will be removed from the managed keys database,
and RFC 5011 key maintenance will no longer be used for that
domain.
</p>
<p>
<span><strong class="command">named</strong></span> only maintains a single managed keys
database; consequently, unlike <span><strong class="command">trusted-keys</strong></span>,
<span><strong class="command">managed-keys</strong></span> may only be set at the top
level of <code class="filename">named.conf</code>, not within a view.
</p>
<p>
In the current implementation, the managed keys database is
stored as a master-format zone file called
<code class="filename">managed-keys.bind</code>. When the key database
is changed, the zone is updated. As with any other dynamic
zone, changes will be written into a journal file,
<code class="filename">managed-keys.bind.jnl</code>. They are committed
to the master file as soon as possible afterward; in the case
of the managed key database, this will usually occur within 30
seconds. So, whenever <span><strong class="command">named</strong></span> is using
automatic key maintenance, those two files can be expected to
exist in the working directory. (For this reason among others,
the working directory should be always be writable by
<span><strong class="command">named</strong></span>.)
</p>
<p>
If the <span><strong class="command">dnssec-validation</strong></span> option is
set to <strong class="userinput"><code>auto</code></strong>, <span><strong class="command">named</strong></span>
will automatically initialize a managed key for the
root zone. Similarly, if the <span><strong class="command">dnssec-lookaside</strong></span>
option is set to <strong class="userinput"><code>auto</code></strong>,
<span><strong class="command">named</strong></span> will automatically initialize
a managed key for the zone <code class="literal">dlv.isc.org</code>.
In both cases, the key that is used to initialize the key
maintenance process is built into <span><strong class="command">named</strong></span>,
and can be overridden from <span><strong class="command">bindkeys-file</strong></span>.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="view_statement_grammar"></a><span><strong class="command">view</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">view</strong></span> <em class="replaceable"><code>view_name</code></em>
[<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
match-clients { <em class="replaceable"><code>address_match_list</code></em> };
match-destinations { <em class="replaceable"><code>address_match_list</code></em> };
match-recursive-only <em class="replaceable"><code>yes_or_no</code></em> ;
[<span class="optional"> <em class="replaceable"><code>view_option</code></em>; ...</span>]
[<span class="optional"> <em class="replaceable"><code>zone_statement</code></em>; ...</span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2594001"></a><span><strong class="command">view</strong></span> Statement Definition and Usage</h3></div></div></div>
<p>
The <span><strong class="command">view</strong></span> statement is a powerful
feature
of <acronym class="acronym">BIND</acronym> 9 that lets a name server
answer a DNS query differently
depending on who is asking. It is particularly useful for
implementing
split DNS setups without having to run multiple servers.
</p>
<p>
Each <span><strong class="command">view</strong></span> statement defines a view
of the
DNS namespace that will be seen by a subset of clients. A client
matches
a view if its source IP address matches the
<code class="varname">address_match_list</code> of the view's
<span><strong class="command">match-clients</strong></span> clause and its
destination IP address matches
the <code class="varname">address_match_list</code> of the
view's
<span><strong class="command">match-destinations</strong></span> clause. If not
specified, both
<span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span>
default to matching all addresses. In addition to checking IP
addresses
<span><strong class="command">match-clients</strong></span> and <span><strong class="command">match-destinations</strong></span>
can also take <span><strong class="command">keys</strong></span> which provide an
mechanism for the
client to select the view. A view can also be specified
as <span><strong class="command">match-recursive-only</strong></span>, which
means that only recursive
requests from matching clients will match that view.
The order of the <span><strong class="command">view</strong></span> statements is
significant &#8212;
a client request will be resolved in the context of the first
<span><strong class="command">view</strong></span> that it matches.
</p>
<p>
Zones defined within a <span><strong class="command">view</strong></span>
statement will
only be accessible to clients that match the <span><strong class="command">view</strong></span>.
By defining a zone of the same name in multiple views, different
zone data can be given to different clients, for example,
"internal"
and "external" clients in a split DNS setup.
</p>
<p>
Many of the options given in the <span><strong class="command">options</strong></span> statement
can also be used within a <span><strong class="command">view</strong></span>
statement, and then
apply only when resolving queries with that view. When no
view-specific
value is given, the value in the <span><strong class="command">options</strong></span> statement
is used as a default. Also, zone options can have default values
specified
in the <span><strong class="command">view</strong></span> statement; these
view-specific defaults
take precedence over those in the <span><strong class="command">options</strong></span> statement.
</p>
<p>
Views are class specific. If no class is given, class IN
is assumed. Note that all non-IN views must contain a hint zone,
since only the IN class has compiled-in default hints.
</p>
<p>
If there are no <span><strong class="command">view</strong></span> statements in
the config
file, a default view that matches any client is automatically
created
in class IN. Any <span><strong class="command">zone</strong></span> statements
specified on
the top level of the configuration file are considered to be part
of
this default view, and the <span><strong class="command">options</strong></span>
statement will
apply to the default view. If any explicit <span><strong class="command">view</strong></span>
statements are present, all <span><strong class="command">zone</strong></span>
statements must
occur inside <span><strong class="command">view</strong></span> statements.
</p>
<p>
Here is an example of a typical split DNS setup implemented
using <span><strong class="command">view</strong></span> statements:
</p>
<pre class="programlisting">view "internal" {
// This should match our internal networks.
match-clients { 10.0.0.0/8; };
// Provide recursive service to internal
// clients only.
recursion yes;
// Provide a complete view of the example.com
// zone including addresses of internal hosts.
zone "example.com" {
type master;
file "example-internal.db";
};
};
view "external" {
// Match all clients not matched by the
// previous view.
match-clients { any; };
// Refuse recursive service to external clients.
recursion no;
// Provide a restricted view of the example.com
// zone containing only publicly accessible hosts.
zone "example.com" {
type master;
file "example-external.db";
};
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zone_statement_grammar"></a><span><strong class="command">zone</strong></span>
Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span><strong class="command">zone</strong></span> <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type master;
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> dnssec-dnskey-kskonly <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> dnssec-loadkeys-interval <em class="replaceable"><code>number</code></em>; </span>]
[<span class="optional"> update-policy <em class="replaceable"><code>local</code></em> | { <em class="replaceable"><code>update_policy_rule</code></em> [<span class="optional">...</span>] }; </span>]
[<span class="optional"> also-notify { <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ;
[<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> check-mx (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> check-spf ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
[<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>]
[<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
[<span class="optional"> journal <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> max-journal-size <em class="replaceable"><code>size_spec</code></em>; </span>]
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> ixfr-base <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> ixfr-from-differences <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> ixfr-tmp-file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <em class="replaceable"><code>master-only</code></em> ; </span>]
[<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>]
[<span class="optional"> notify-to-soa <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</code></em>; </span>]
[<span class="optional"> sig-validity-interval <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>number</code></em></span>] ; </span>]
[<span class="optional"> sig-signing-nodes <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> sig-signing-signatures <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> sig-signing-type <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> database <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> key-directory <em class="replaceable"><code>path_name</code></em>; </span>]
[<span class="optional"> auto-dnssec <code class="constant">allow</code>|<code class="constant">maintain</code>|<code class="constant">off</code>; </span>]
[<span class="optional"> inline-signing <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> serial-update-method <code class="constant">increment</code>|<code class="constant">unixtime</code>|<code class="constant">date</code>; </span>]
[<span class="optional"> max-zone-ttl <em class="replaceable"><code>number</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type slave;
[<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> dnssec-update-mode ( <em class="replaceable"><code>maintain</code></em> | <em class="replaceable"><code>no-resign</code></em> ); </span>]
[<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> dnssec-dnskey-kskonly <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> dnssec-loadkeys-interval <em class="replaceable"><code>number</code></em>; </span>]
[<span class="optional"> dnssec-secure-to-insecure <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> try-tcp-refresh <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> also-notify [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em>
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
[<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>]
[<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
[<span class="optional"> journal <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> max-journal-size <em class="replaceable"><code>size_spec</code></em>; </span>]
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> ixfr-base <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> ixfr-from-differences <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> ixfr-tmp-file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em>
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
[<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>]
[<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> notify <em class="replaceable"><code>yes_or_no</code></em> | <em class="replaceable"><code>explicit</code></em> | <em class="replaceable"><code>master-only</code></em> ; </span>]
[<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>]
[<span class="optional"> notify-to-soa <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> notify-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</code></em>; </span>]
[<span class="optional"> sig-validity-interval <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>number</code></em></span>] ; </span>]
[<span class="optional"> sig-signing-nodes <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> sig-signing-signatures <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> sig-signing-type <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> database <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> key-directory <em class="replaceable"><code>path_name</code></em>; </span>]
[<span class="optional"> auto-dnssec <code class="constant">allow</code>|<code class="constant">maintain</code>|<code class="constant">off</code>; </span>]
[<span class="optional"> inline-signing <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> multi-master <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type hint;
file <em class="replaceable"><code>string</code></em> ;
[<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>] // Not Implemented.
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type stub;
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> check-names (<code class="constant">warn</code>|<code class="constant">fail</code>|<code class="constant">ignore</code>) ; </span>]
[<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em> ; </span>]
[<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> file <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> masters [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em>
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
[<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
[<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }; </span>]
[<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> pubkey <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source (<em class="replaceable"><code>ip4_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> alt-transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>)
[<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
[<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
[<span class="optional"> database <em class="replaceable"><code>string</code></em> ; </span>]
[<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
[<span class="optional"> multi-master <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type static-stub;
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> server-addresses { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> ; ... </span>] }; </span>]
[<span class="optional"> server-names { [<span class="optional"> <em class="replaceable"><code>namelist</code></em> </span>] }; </span>]
[<span class="optional"> zone-statistics <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type forward;
[<span class="optional"> forward (<code class="constant">only</code>|<code class="constant">first</code>) ; </span>]
[<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
[<span class="optional"> delegation-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
};
zone <em class="replaceable"><code>"."</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type redirect;
file <em class="replaceable"><code>string</code></em> ;
[<span class="optional"> masterfile-format (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
[<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
[<span class="optional"> max-zone-ttl <em class="replaceable"><code>number</code></em> ; </span>]
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
type delegation-only;
};
zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"><em class="replaceable"><code>class</code></em></span>] {
[<span class="optional"> in-view <em class="replaceable"><code>string</code></em> ; </span>]
};
</pre>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2596017"></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="id2596024"></a>Zone Types</h4></div></div></div>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="varname">master</code>
</p>
</td>
<td>
<p>
The server has a master copy of the data
for the zone and will be able to provide authoritative
answers for
it.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">slave</code>
</p>
</td>
<td>
<p>
A slave zone is a replica of a master
zone. The <span><strong class="command">masters</strong></span> list
specifies one or more IP addresses
of master servers that the slave contacts to update
its copy of the zone.
Masters list elements can also be names of other
masters lists.
By default, transfers are made from port 53 on the
servers; this can
be changed for all servers by specifying a port number
before the
list of IP addresses, or on a per-server basis after
the IP address.
Authentication to the master can also be done with
per-server TSIG keys.
If a file is specified, then the
replica will be written to this file whenever the zone
is changed,
and reloaded from this file on a server restart. Use
of a file is
recommended, since it often speeds server startup and
eliminates
a needless waste of bandwidth. Note that for large
numbers (in the
tens or hundreds of thousands) of zones per server, it
is best to
use a two-level naming scheme for zone filenames. For
example,
a slave server for the zone <code class="literal">example.com</code> might place
the zone contents into a file called
<code class="filename">ex/example.com</code> where <code class="filename">ex/</code> is
just the first two letters of the zone name. (Most
operating systems
behave very slowly if you put 100000 files into
a single directory.)
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">stub</code>
</p>
</td>
<td>
<p>
A stub zone is similar to a slave zone,
except that it replicates only the NS records of a
master zone instead
of the entire zone. Stub zones are not a standard part
of the DNS;
they are a feature specific to the <acronym class="acronym">BIND</acronym> implementation.
</p>
<p>
Stub zones can be used to eliminate the need for glue
NS record
in a parent zone at the expense of maintaining a stub
zone entry and
a set of name server addresses in <code class="filename">named.conf</code>.
This usage is not recommended for new configurations,
and BIND 9
supports it only in a limited way.
In <acronym class="acronym">BIND</acronym> 4/8, zone
transfers of a parent zone
included the NS records from stub children of that
zone. This meant
that, in some cases, users could get away with
configuring child stubs
only in the master server for the parent zone. <acronym class="acronym">BIND</acronym>
9 never mixes together zone data from different zones
in this
way. Therefore, if a <acronym class="acronym">BIND</acronym> 9 master serving a parent
zone has child stub zones configured, all the slave
servers for the
parent zone also need to have the same child stub
zones
configured.
</p>
<p>
Stub zones can also be used as a way of forcing the
resolution
of a given domain to use a particular set of
authoritative servers.
For example, the caching name servers on a private
network using
RFC1918 addressing may be configured with stub zones
for
<code class="literal">10.in-addr.arpa</code>
to use a set of internal name servers as the
authoritative
servers for that domain.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">static-stub</code>
</p>
</td>
<td>
<p>
A static-stub zone is similar to a stub zone
with the following exceptions:
the zone data is statically configured, rather
than transferred from a master server;
when recursion is necessary for a query that
matches a static-stub zone, the locally
configured data (nameserver names and glue addresses)
is always used even if different authoritative
information is cached.
</p>
<p>
Zone data is configured via the
<span><strong class="command">server-addresses</strong></span> and
<span><strong class="command">server-names</strong></span> zone options.
</p>
<p>
The zone data is maintained in the form of NS
and (if necessary) glue A or AAAA RRs
internally, which can be seen by dumping zone
databases by <span><strong class="command">rndc dumpdb -all</strong></span>.
The configured RRs are considered local configuration
parameters rather than public data.
Non recursive queries (i.e., those with the RD
bit off) to a static-stub zone are therefore
prohibited and will be responded with REFUSED.
</p>
<p>
Since the data is statically configured, no
zone maintenance action takes place for a static-stub
zone.
For example, there is no periodic refresh
attempt, and an incoming notify message
will be rejected with an rcode of NOTAUTH.
</p>
<p>
Each static-stub zone is configured with
internally generated NS and (if necessary)
glue A or AAAA RRs
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">forward</code>
</p>
</td>
<td>
<p>
A "forward zone" is a way to configure
forwarding on a per-domain basis. A <span><strong class="command">zone</strong></span> statement
of type <span><strong class="command">forward</strong></span> can
contain a <span><strong class="command">forward</strong></span>
and/or <span><strong class="command">forwarders</strong></span>
statement,
which will apply to queries within the domain given by
the zone
name. If no <span><strong class="command">forwarders</strong></span>
statement is present or
an empty list for <span><strong class="command">forwarders</strong></span> is given, then no
forwarding will be done for the domain, canceling the
effects of
any forwarders in the <span><strong class="command">options</strong></span> statement. Thus
if you want to use this type of zone to change the
behavior of the
global <span><strong class="command">forward</strong></span> option
(that is, "forward first"
to, then "forward only", or vice versa, but want to
use the same
servers as set globally) you need to re-specify the
global forwarders.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">hint</code>
</p>
</td>
<td>
<p>
The initial set of root name servers is
specified using a "hint zone". When the server starts
up, it uses
the root hints to find a root name server and get the
most recent
list of root name servers. If no hint zone is
specified for class
IN, the server uses a compiled-in default set of root
servers hints.
Classes other than IN have no built-in defaults hints.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">redirect</code>
</p>
</td>
<td>
<p>
Redirect zones are used to provide answers to
queries when normal resolution would result in
NXDOMAIN being returned.
Only one redirect zone is supported
per view. <span><strong class="command">allow-query</strong></span> can be
used to restrict which clients see these answers.
</p>
<p>
If the client has requested DNSSEC records (DO=1) and
the NXDOMAIN response is signed then no substitution
will occur.
</p>
<p>
To redirect all NXDOMAIN responses to
100.100.100.2 and
2001:ffff:ffff::100.100.100.2, one would
configure a type redirect zone named ".",
with the zone file containing wildcard records
that point to the desired addresses:
<code class="literal">"*. IN A 100.100.100.2"</code>
and
<code class="literal">"*. IN AAAA 2001:ffff:ffff::100.100.100.2"</code>.
</p>
<p>
To redirect all Spanish names (under .ES) one
would use similar entries but with the names
"*.ES." instead of "*.". To redirect all
commercial Spanish names (under COM.ES) one
would use wildcard entries called "*.COM.ES.".
</p>
<p>
Note that the redirect zone supports all
possible types; it is not limited to A and
AAAA records.
</p>
<p>
Because redirect zones are not referenced
directly by name, they are not kept in the
zone lookup table with normal master and slave
zones. Consequently, it is not currently possible
to use
<span><strong class="command">rndc reload
<em class="replaceable"><code>zonename</code></em></strong></span>
to reload a redirect zone. However, when using
<span><strong class="command">rndc reload</strong></span> without specifying
a zone name, redirect zones will be reloaded along
with other zones.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">delegation-only</code>
</p>
</td>
<td>
<p>
This is used to enforce the delegation-only
status of infrastructure zones (e.g. COM,
NET, ORG). Any answer that is received
without an explicit or implicit delegation
in the authority section will be treated
as NXDOMAIN. This does not apply to the
zone apex. This should not be applied to
leaf zones.
</p>
<p>
<code class="varname">delegation-only</code> has no
effect on answers received from forwarders.
</p>
<p>
See caveats in <a href="Bv9ARM.ch06.html#root_delegation_only"><span><strong class="command">root-delegation-only</strong></span></a>.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2596632"></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="id2596733"></a>Zone Options</h4></div></div></div>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">allow-notify</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-query</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">allow-query</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-query-on</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">allow-query-on</strong></span> in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-transfer</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">allow-transfer</strong></span>
in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-update</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">allow-update</strong></span>
in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">update-policy</strong></span></span></dt>
<dd><p>
Specifies a "Simple Secure Update" policy. See
<a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">allow-update-forwarding</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">allow-update-forwarding</strong></span>
in <a href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">also-notify</strong></span></span></dt>
<dd><p>
Only meaningful if <span><strong class="command">notify</strong></span>
is
active for this zone. The set of machines that will
receive a
<code class="literal">DNS NOTIFY</code> message
for this zone is made up of all the listed name servers
(other than
the primary master) for the zone plus any IP addresses
specified
with <span><strong class="command">also-notify</strong></span>. A port
may be specified
with each <span><strong class="command">also-notify</strong></span>
address to send the notify
messages to a port other than the default of 53.
A TSIG key may also be specified to cause the
<code class="literal">NOTIFY</code> to be signed by the
given key.
<span><strong class="command">also-notify</strong></span> is not
meaningful for stub zones.
The default is the empty list.
</p></dd>
<dt><span class="term"><span><strong class="command">check-names</strong></span></span></dt>
<dd><p>
This option is used to restrict the character set and
syntax of
certain domain names in master files and/or DNS responses
received from the
network. The default varies according to zone type. For <span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>. For <span><strong class="command">slave</strong></span>
zones the default is <span><strong class="command">warn</strong></span>.
It is not implemented for <span><strong class="command">hint</strong></span> zones.
</p></dd>
<dt><span class="term"><span><strong class="command">check-mx</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-mx</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-spf</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-spf</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-wildcard</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-wildcard</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-integrity</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-integrity</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">check-sibling</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">zero-no-soa-ttl</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">update-check-ksk</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">update-check-ksk</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-update-mode</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">dnssec-update-mode</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
Usage">the section called &#8220;<span><strong class="command">options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-dnskey-kskonly</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">dnssec-dnskey-kskonly</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">try-tcp-refresh</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">try-tcp-refresh</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">database</strong></span></span></dt>
<dd>
<p>
Specify the type of database to be used for storing the
zone data. The string following the <span><strong class="command">database</strong></span> keyword
is interpreted as a list of whitespace-delimited words.
The first word
identifies the database type, and any subsequent words are
passed
as arguments to the database to be interpreted in a way
specific
to the database type.
</p>
<p>
The default is <strong class="userinput"><code>"rbt"</code></strong>, BIND 9's
native in-memory
red-black-tree database. This database does not take
arguments.
</p>
<p>
Other values are possible if additional database drivers
have been linked into the server. Some sample drivers are
included
with the distribution but none are linked in by default.
</p>
</dd>
<dt><span class="term"><span><strong class="command">dialup</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">dialup</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">delegation-only</strong></span></span></dt>
<dd>
<p>
The flag only applies to forward, hint and stub
zones. If set to <strong class="userinput"><code>yes</code></strong>,
then the zone will also be treated as if it is
also a delegation-only type zone.
</p>
<p>
See caveats in <a href="Bv9ARM.ch06.html#root_delegation_only"><span><strong class="command">root-delegation-only</strong></span></a>.
</p>
</dd>
<dt><span class="term"><span><strong class="command">forward</strong></span></span></dt>
<dd><p>
Only meaningful if the zone has a forwarders
list. The <span><strong class="command">only</strong></span> value causes
the lookup to fail
after trying the forwarders and getting no answer, while <span><strong class="command">first</strong></span> would
allow a normal lookup to be tried.
</p></dd>
<dt><span class="term"><span><strong class="command">forwarders</strong></span></span></dt>
<dd><p>
Used to override the list of global forwarders.
If it is not specified in a zone of type <span><strong class="command">forward</strong></span>,
no forwarding is done for the zone and the global options are
not used.
</p></dd>
<dt><span class="term"><span><strong class="command">ixfr-base</strong></span></span></dt>
<dd><p>
Was used in <acronym class="acronym">BIND</acronym> 8 to
specify the name
of the transaction log (journal) file for dynamic update
and IXFR.
<acronym class="acronym">BIND</acronym> 9 ignores the option
and constructs the name of the journal
file by appending "<code class="filename">.jnl</code>"
to the name of the
zone file.
</p></dd>
<dt><span class="term"><span><strong class="command">ixfr-tmp-file</strong></span></span></dt>
<dd><p>
Was an undocumented option in <acronym class="acronym">BIND</acronym> 8.
Ignored in <acronym class="acronym">BIND</acronym> 9.
</p></dd>
<dt><span class="term"><span><strong class="command">journal</strong></span></span></dt>
<dd><p>
Allow the default journal's filename to be overridden.
The default is the zone's filename with "<code class="filename">.jnl</code>" appended.
This is applicable to <span><strong class="command">master</strong></span> and <span><strong class="command">slave</strong></span> zones.
</p></dd>
<dt><span class="term"><span><strong class="command">max-journal-size</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-journal-size</strong></span> in <a href="Bv9ARM.ch06.html#server_resource_limits" title="Server Resource Limits">the section called &#8220;Server Resource Limits&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-time-in</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-transfer-time-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-idle-in</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-transfer-idle-in</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-time-out</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-transfer-time-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-transfer-idle-out</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">max-transfer-idle-out</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-delay</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify-delay</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-to-soa</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify-to-soa</strong></span> in
<a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">pubkey</strong></span></span></dt>
<dd><p>
In <acronym class="acronym">BIND</acronym> 8, this option was
intended for specifying
a public zone key for verification of signatures in DNSSEC
signed
zones when they are loaded from disk. <acronym class="acronym">BIND</acronym> 9 does not verify signatures
on load and ignores the option.
</p></dd>
<dt><span class="term"><span><strong class="command">zone-statistics</strong></span></span></dt>
<dd><p>
If <strong class="userinput"><code>yes</code></strong>, the server will keep
statistical
information for this zone, which can be dumped to the
<span><strong class="command">statistics-file</strong></span> defined in
the server options.
</p></dd>
<dt><span class="term"><span><strong class="command">server-addresses</strong></span></span></dt>
<dd>
<p>
Only meaningful for static-stub zones.
This is a list of IP addresses to which queries
should be sent in recursive resolution for the
zone.
A non empty list for this option will internally
configure the apex NS RR with associated glue A or
AAAA RRs.
</p>
<p>
For example, if "example.com" is configured as a
static-stub zone with 192.0.2.1 and 2001:db8::1234
in a <span><strong class="command">server-addresses</strong></span> option,
the following RRs will be internally configured.
</p>
<pre class="programlisting">example.com. NS example.com.
example.com. A 192.0.2.1
example.com. AAAA 2001:db8::1234</pre>
<p>
These records are internally used to resolve
names under the static-stub zone.
For instance, if the server receives a query for
"www.example.com" with the RD bit on, the server
will initiate recursive resolution and send
queries to 192.0.2.1 and/or 2001:db8::1234.
</p>
</dd>
<dt><span class="term"><span><strong class="command">server-names</strong></span></span></dt>
<dd>
<p>
Only meaningful for static-stub zones.
This is a list of domain names of nameservers that
act as authoritative servers of the static-stub
zone.
These names will be resolved to IP addresses when
<span><strong class="command">named</strong></span> needs to send queries to
these servers.
To make this supplemental resolution successful,
these names must not be a subdomain of the origin
name of static-stub zone.
That is, when "example.net" is the origin of a
static-stub zone, "ns.example" and
"master.example.com" can be specified in the
<span><strong class="command">server-names</strong></span> option, but
"ns.example.net" cannot, and will be rejected by
the configuration parser.
</p>
<p>
A non empty list for this option will internally
configure the apex NS RR with the specified names.
For example, if "example.com" is configured as a
static-stub zone with "ns1.example.net" and
"ns2.example.net"
in a <span><strong class="command">server-names</strong></span> option,
the following RRs will be internally configured.
</p>
<pre class="programlisting">example.com. NS ns1.example.net.
example.com. NS ns2.example.net.
</pre>
<p>
These records are internally used to resolve
names under the static-stub zone.
For instance, if the server receives a query for
"www.example.com" with the RD bit on, the server
initiate recursive resolution,
resolve "ns1.example.net" and/or
"ns2.example.net" to IP addresses, and then send
queries to (one or more of) these addresses.
</p>
</dd>
<dt><span class="term"><span><strong class="command">sig-validity-interval</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">sig-validity-interval</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-nodes</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">sig-signing-nodes</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-signatures</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">sig-signing-signatures</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">sig-signing-type</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">sig-signing-type</strong></span> in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">transfer-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">alt-transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">alt-transfer-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">alt-transfer-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">use-alt-transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">use-alt-transfer-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-source</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify-source</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">notify-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">notify-source-v6</strong></span> in <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt>
<span class="term"><span><strong class="command">min-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">max-refresh-time</strong></span>, </span><span class="term"><span><strong class="command">min-retry-time</strong></span>, </span><span class="term"><span><strong class="command">max-retry-time</strong></span></span>
</dt>
<dd><p>
See the description in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">ixfr-from-differences</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
(Note that the <span><strong class="command">ixfr-from-differences</strong></span>
<strong class="userinput"><code>master</code></strong> and
<strong class="userinput"><code>slave</code></strong> choices are not
available at the zone level.)
</p></dd>
<dt><span class="term"><span><strong class="command">key-directory</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">key-directory</strong></span> in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
Usage">the section called &#8220;<span><strong class="command">options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">auto-dnssec</strong></span></span></dt>
<dd>
<p>
Zones configured for dynamic DNS may also use this
option to allow varying levels of automatic DNSSEC key
management. There are three possible settings:
</p>
<p>
<span><strong class="command">auto-dnssec allow;</strong></span> permits
keys to be updated and the zone fully re-signed
whenever the user issues the command <span><strong class="command">rndc sign
<em class="replaceable"><code>zonename</code></em></strong></span>.
</p>
<p>
<span><strong class="command">auto-dnssec maintain;</strong></span> includes the
above, but also automatically adjusts the zone's DNSSEC
keys on schedule, according to the keys' timing metadata
(see <a href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
<a href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The command
<span><strong class="command">rndc sign
<em class="replaceable"><code>zonename</code></em></strong></span> causes
<span><strong class="command">named</strong></span> to load keys from the key
repository and sign the zone with all keys that are
active.
<span><strong class="command">rndc loadkeys
<em class="replaceable"><code>zonename</code></em></strong></span> causes
<span><strong class="command">named</strong></span> to load keys from the key
repository and schedule key maintenance events to occur
in the future, but it does not sign the full zone
immediately. Note: once keys have been loaded for a
zone the first time, the repository will be searched
for changes periodically, regardless of whether
<span><strong class="command">rndc loadkeys</strong></span> is used. The recheck
interval is defined by
<span><strong class="command">dnssec-loadkeys-interval</strong></span>.)
</p>
<p>
The default setting is <span><strong class="command">auto-dnssec off</strong></span>.
</p>
</dd>
<dt><span class="term"><span><strong class="command">serial-update-method</strong></span></span></dt>
<dd>
<p>
Zones configured for dynamic DNS may use this
option to set the update method that will be used for
the zone serial number in the SOA record.
</p>
<p>
With the default setting of
<span><strong class="command">serial-update-method increment;</strong></span>, the
SOA serial number will be incremented by one each time
the zone is updated.
</p>
<p>
When set to
<span><strong class="command">serial-update-method unixtime;</strong></span>, the
SOA serial number will be set to the number of seconds
since the UNIX epoch, unless the serial number is
already greater than or equal to that value, in which
case it is simply incremented by one.
</p>
<p>
When set to
<span><strong class="command">serial-update-method date;</strong></span>, the
new SOA serial number will be the current date
in the form "YYYYMMDD", followed by two zeroes,
unless the existing serial number is already greater
than or equal to that value, in which case it is
incremented by one.
</p>
</dd>
<dt><span class="term"><span><strong class="command">inline-signing</strong></span></span></dt>
<dd><p>
If <code class="literal">yes</code>, this enables
"bump in the wire" signing of a zone, where a
unsigned zone is transferred in or loaded from
disk and a signed version of the zone is served,
with possibly, a different serial number. This
behaviour is disabled by default.
</p></dd>
<dt><span class="term"><span><strong class="command">multi-master</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">multi-master</strong></span> in
<a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">masterfile-format</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">masterfile-format</strong></span>
in <a href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">max-zone-ttl</strong></span></span></dt>
<dd><p>
See the description of <span><strong class="command">max-zone-ttl</strong></span>
in <a href="Bv9ARM.ch06.html#options" title="options Statement Definition and
Usage">the section called &#8220;<span><strong class="command">options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span><strong class="command">dnssec-secure-to-insecure</strong></span></span></dt>
<dd><p>
See the description of
<span><strong class="command">dnssec-secure-to-insecure</strong></span> in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="dynamic_update_policies"></a>Dynamic Update Policies</h4></div></div></div>
<p><acronym class="acronym">BIND</acronym> 9 supports two alternative
methods of granting clients the right to perform
dynamic updates to a zone, configured by the
<span><strong class="command">allow-update</strong></span> and
<span><strong class="command">update-policy</strong></span> option, respectively.
</p>
<p>
The <span><strong class="command">allow-update</strong></span> clause works the
same way as in previous versions of <acronym class="acronym">BIND</acronym>.
It grants given clients the permission to update any
record of any name in the zone.
</p>
<p>
The <span><strong class="command">update-policy</strong></span> clause
allows more fine-grained control over what updates are
allowed. A set of rules is specified, where each rule
either grants or denies permissions for one or more
names to be updated by one or more identities. If
the dynamic update request message is signed (that is,
it includes either a TSIG or SIG(0) record), the
identity of the signer can be determined.
</p>
<p>
Rules are specified in the <span><strong class="command">update-policy</strong></span>
zone option, and are only meaningful for master zones.
When the <span><strong class="command">update-policy</strong></span> statement
is present, it is a configuration error for the
<span><strong class="command">allow-update</strong></span> statement to be
present. The <span><strong class="command">update-policy</strong></span> statement
only examines the signer of a message; the source
address is not relevant.
</p>
<p>
There is a pre-defined <span><strong class="command">update-policy</strong></span>
rule which can be switched on with the command
<span><strong class="command">update-policy local;</strong></span>.
Switching on this rule in a zone causes
<span><strong class="command">named</strong></span> to generate a TSIG session
key and place it in a file, and to allow that key
to update the zone. (By default, the file is
<code class="filename">/var/run/named/session.key</code>, the key
name is "local-ddns" and the key algorithm is HMAC-SHA256,
but these values are configurable with the
<span><strong class="command">session-keyfile</strong></span>,
<span><strong class="command">session-keyname</strong></span> and
<span><strong class="command">session-keyalg</strong></span> options, respectively).
</p>
<p>
A client running on the local system, and with appropriate
permissions, may read that file and use the key to sign update
requests. The zone's update policy will be set to allow that
key to change any record within the zone. Assuming the
key name is "local-ddns", this policy is equivalent to:
</p>
<pre class="programlisting">update-policy { grant local-ddns zonesub any; };
</pre>
<p>
The command <span><strong class="command">nsupdate -l</strong></span> sends update
requests to localhost, and signs them using the session key.
</p>
<p>
Other rule definitions look like this:
</p>
<pre class="programlisting">
( <span><strong class="command">grant</strong></span> | <span><strong class="command">deny</strong></span> ) <em class="replaceable"><code>identity</code></em> <em class="replaceable"><code>nametype</code></em> [<span class="optional"> <em class="replaceable"><code>name</code></em> </span>] [<span class="optional"> <em class="replaceable"><code>types</code></em> </span>]
</pre>
<p>
Each rule grants or denies privileges. Once a message has
successfully matched a rule, the operation is immediately
granted or denied and no further rules are examined. A rule
is matched when the signer matches the identity field, the
name matches the name field in accordance with the nametype
field, and the type matches the types specified in the type
field.
</p>
<p>
No signer is required for <em class="replaceable"><code>tcp-self</code></em>
or <em class="replaceable"><code>6to4-self</code></em> however the standard
reverse mapping / prefix conversion must match the identity
field.
</p>
<p>
The identity field specifies a name or a wildcard
name. Normally, this is the name of the TSIG or
SIG(0) key used to sign the update request. When a
TKEY exchange has been used to create a shared secret,
the identity of the shared secret is the same as the
identity of the key used to authenticate the TKEY
exchange. TKEY is also the negotiation method used
by GSS-TSIG, which establishes an identity that is
the Kerberos principal of the client, such as
<strong class="userinput"><code>"user@host.domain"</code></strong>. When the
<em class="replaceable"><code>identity</code></em> field specifies
a wildcard name, it is subject to DNS wildcard
expansion, so the rule will apply to multiple identities.
The <em class="replaceable"><code>identity</code></em> field must
contain a fully-qualified domain name.
</p>
<p>
For nametypes <code class="varname">krb5-self</code>,
<code class="varname">ms-self</code>, <code class="varname">krb5-subdomain</code>,
and <code class="varname">ms-subdomain</code> the
<em class="replaceable"><code>identity</code></em> field specifies
the Windows or Kerberos realm of the machine belongs to.
</p>
<p>
The <em class="replaceable"><code>nametype</code></em> field has 13
values:
<code class="varname">name</code>, <code class="varname">subdomain</code>,
<code class="varname">wildcard</code>, <code class="varname">self</code>,
<code class="varname">selfsub</code>, <code class="varname">selfwild</code>,
<code class="varname">krb5-self</code>, <code class="varname">ms-self</code>,
<code class="varname">krb5-subdomain</code>,
<code class="varname">ms-subdomain</code>,
<code class="varname">tcp-self</code>, <code class="varname">6to4-self</code>,
<code class="varname">zonesub</code>, and <code class="varname">external</code>.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="varname">name</code>
</p>
</td>
<td>
<p>
Exact-match semantics. This rule matches
when the name being updated is identical
to the contents of the
<em class="replaceable"><code>name</code></em> field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">subdomain</code>
</p>
</td>
<td>
<p>
This rule matches when the name being updated
is a subdomain of, or identical to, the
contents of the <em class="replaceable"><code>name</code></em>
field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">zonesub</code>
</p>
</td>
<td>
<p>
This rule is similar to subdomain, except that
it matches when the name being updated is a
subdomain of the zone in which the
<span><strong class="command">update-policy</strong></span> statement
appears. This obviates the need to type the zone
name twice, and enables the use of a standard
<span><strong class="command">update-policy</strong></span> statement in
multiple zones without modification.
</p>
<p>
When this rule is used, the
<em class="replaceable"><code>name</code></em> field is omitted.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">wildcard</code>
</p>
</td>
<td>
<p>
The <em class="replaceable"><code>name</code></em> field
is subject to DNS wildcard expansion, and
this rule matches when the name being updated
name is a valid expansion of the wildcard.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">self</code>
</p>
</td>
<td>
<p>
This rule matches when the name being updated
matches the contents of the
<em class="replaceable"><code>identity</code></em> field.
The <em class="replaceable"><code>name</code></em> field
is ignored, but should be the same as the
<em class="replaceable"><code>identity</code></em> field.
The <code class="varname">self</code> nametype is
most useful when allowing using one key per
name to update, where the key has the same
name as the name to be updated. The
<em class="replaceable"><code>identity</code></em> would
be specified as <code class="constant">*</code> (an asterisk) in
this case.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">selfsub</code>
</p>
</td>
<td>
<p>
This rule is similar to <code class="varname">self</code>
except that subdomains of <code class="varname">self</code>
can also be updated.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">selfwild</code>
</p>
</td>
<td>
<p>
This rule is similar to <code class="varname">self</code>
except that only subdomains of
<code class="varname">self</code> can be updated.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">ms-self</code>
</p>
</td>
<td>
<p>
This rule takes a Windows machine principal
(machine$@REALM) for machine in REALM and
and converts it machine.realm allowing the machine
to update machine.realm. The REALM to be matched
is specified in the <em class="replaceable"><code>identity</code></em>
field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">ms-subdomain</code>
</p>
</td>
<td>
<p>
This rule takes a Windows machine principal
(machine$@REALM) for machine in REALM and
converts it to machine.realm allowing the machine
to update subdomains of machine.realm. The REALM
to be matched is specified in the
<em class="replaceable"><code>identity</code></em> field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">krb5-self</code>
</p>
</td>
<td>
<p>
This rule takes a Kerberos machine principal
(host/machine@REALM) for machine in REALM and
and converts it machine.realm allowing the machine
to update machine.realm. The REALM to be matched
is specified in the <em class="replaceable"><code>identity</code></em>
field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">krb5-subdomain</code>
</p>
</td>
<td>
<p>
This rule takes a Kerberos machine principal
(host/machine@REALM) for machine in REALM and
converts it to machine.realm allowing the machine
to update subdomains of machine.realm. The REALM
to be matched is specified in the
<em class="replaceable"><code>identity</code></em> field.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">tcp-self</code>
</p>
</td>
<td>
<p>
Allow updates that have been sent via TCP and
for which the standard mapping from the initiating
IP address into the IN-ADDR.ARPA and IP6.ARPA
namespaces match the name to be updated.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
It is theoretically possible to spoof these TCP
sessions.
</div>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">6to4-self</code>
</p>
</td>
<td>
<p>
Allow the 6to4 prefix to be update by any TCP
connection from the 6to4 network or from the
corresponding IPv4 address. This is intended
to allow NS or DNAME RRsets to be added to the
reverse tree.
</p>
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
It is theoretically possible to spoof these TCP
sessions.
</div>
</td>
</tr>
<tr>
<td>
<p>
<code class="varname">external</code>
</p>
</td>
<td>
<p>
This rule allows <span><strong class="command">named</strong></span>
to defer the decision of whether to allow a
given update to an external daemon.
</p>
<p>
The method of communicating with the daemon is
specified in the <em class="replaceable"><code>identity</code></em>
field, the format of which is
"<code class="constant">local:</code><em class="replaceable"><code>path</code></em>",
where <em class="replaceable"><code>path</code></em> is the location
of a UNIX-domain socket. (Currently, "local" is the
only supported mechanism.)
</p>
<p>
Requests to the external daemon are sent over the
UNIX-domain socket as datagrams with the following
format:
</p>
<pre class="programlisting">
Protocol version number (4 bytes, network byte order, currently 1)
Request length (4 bytes, network byte order)
Signer (null-terminated string)
Name (null-terminated string)
TCP source address (null-terminated string)
Rdata type (null-terminated string)
Key (null-terminated string)
TKEY token length (4 bytes, network byte order)
TKEY token (remainder of packet)</pre>
<p>
The daemon replies with a four-byte value in
network byte order, containing either 0 or 1; 0
indicates that the specified update is not
permitted, and 1 indicates that it is.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
In all cases, the <em class="replaceable"><code>name</code></em>
field must specify a fully-qualified domain name.
</p>
<p>
If no types are explicitly specified, this rule matches
all types except RRSIG, NS, SOA, NSEC and NSEC3. Types
may be specified by name, including "ANY" (ANY matches
all types except NSEC and NSEC3, which can never be
updated). Note that when an attempt is made to delete
all records associated with a name, the rules are
checked for each existing record type.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2599662"></a>Multiple views</h4></div></div></div>
<p>
When multiple views are in use, a zone may be
referenced by more than one of them. Often, the views
will contain different zones with the same name, allowing
different clients to receive different answers for the same
queries. At times, however, it is desirable for multiple
views to contain identical zones. The
<span><strong class="command">in-view</strong></span> zone option provides an efficient
way to do this: it allows a view to reference a zone that
was defined in a previously configured view. Example:
</p>
<pre class="programlisting">
view internal {
match-clients { 10/8; };
zone example.com {
type master;
file "example-external.db";
};
};
view external {
match-clients { any; };
zone example.com {
in-view internal;
};
};
</pre>
<p>
An <span><strong class="command">in-view</strong></span> option cannot refer to a view
that is configured later in the configuration file.
</p>
<p>
A <span><strong class="command">zone</strong></span> statement which uses the
<span><strong class="command">in-view</strong></span> option may not use any other
options with the exception of <span><strong class="command">forward</strong></span>
and <span><strong class="command">forwarders</strong></span>. (These options control
the behavior of the containing view, rather than changing
the zone object itself.)
</p>
<p>
Zone level acls (e.g. allow-query, allow-transfer) and
other configuration details of the zone are all set
in the view the referenced zone is defined in. Care
need to be taken to ensure that acls are wide enough
for all views referencing the zone.
</p>
<p>
An <span><strong class="command">in-view</strong></span> zone cannot be used as a
response policy zone.
</p>
<p>
An <span><strong class="command">in-view</strong></span> zone is not intended to reference
a <span><strong class="command">forward</strong></span> zone.
</p>
</div>
</div>
</div>
<div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="id2599724"></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="id2599742"></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>
ATMA
</p>
</td>
<td>
<p>
ATM Address.
</p>
</td>
</tr>
<tr>
<td>
<p>
CAA
</p>
</td>
<td>
<p>
Identifies which Certificate Authorities can issue
certificates for this domain and what rules they
need to follow when doing so. Defined in RFC 6844.
</p>
</td>
</tr>
<tr>
<td>
<p>
CDNSKEY
</p>
</td>
<td>
<p>
Identifies which DNSKEY records should be published
as DS records in the parent zone.
</p>
</td>
</tr>
<tr>
<td>
<p>
CDS
</p>
</td>
<td>
<p>
Contains the set of DS records that should be published
by the parent zone.
</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>
DLV
</p>
</td>
<td>
<p>
A DNS Look-aside Validation record which contains
the records that are used as trust anchors for
zones in a DLV namespace. Described in RFC 4431.
</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>
EID
</p>
</td>
<td>
<p>
End Point Identifier.
</p>
</td>
</tr>
<tr>
<td>
<p>
EUI48
</p>
</td>
<td>
<p>
A 48-bit EUI address. Described in RFC 7043.
</p>
</td>
</tr>
<tr>
<td>
<p>
EUI64
</p>
</td>
<td>
<p>
A 64-bit EUI address. Described in RFC 7043.
</p>
</td>
</tr>
<tr>
<td>
<p>
GID
</p>
</td>
<td>
<p>
Reserved.
</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>
HIP
</p>
</td>
<td>
<p>
Host Identity Protocol Address.
Described in RFC 5205.
</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>
L32
</p>
</td>
<td>
<p>
Holds 32-bit Locator values for
Identifier-Locator Network Protocol. Described
in RFC 6742.
</p>
</td>
</tr>
<tr>
<td>
<p>
L64
</p>
</td>
<td>
<p>
Holds 64-bit Locator values for
Identifier-Locator Network Protocol. Described
in RFC 6742.
</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>
LP
</p>
</td>
<td>
<p>
Identifier-Locator Network Protocol.
Described in RFC 6742.
</p>
</td>
</tr>
<tr>
<td>
<p>
MB
</p>
</td>
<td>
<p>
Mail Box. Historical.
</p>
</td>
</tr>
<tr>
<td>
<p>
MD
</p>
</td>
<td>
<p>
Mail Destination. Historical.
</p>
</td>
</tr>
<tr>
<td>
<p>
MF
</p>
</td>
<td>
<p>
Mail Forwarder. Historical.
</p>
</td>
</tr>
<tr>
<td>
<p>
MG
</p>
</td>
<td>
<p>
Mail Group. Historical.
</p>
</td>
</tr>
<tr>
<td>
<p>
MINFO
</p>
</td>
<td>
<p>
Mail Information.
</p>
</td>
</tr>
<tr>
<td>
<p>
MR
</p>
</td>
<td>
<p>
Mail Rename. Historical.
</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>
NID
</p>
</td>
<td>
<p>
Holds values for Node Identifiers in
Identifier-Locator Network Protocol. Described
in RFC 6742.
</p>
</td>
</tr>
<tr>
<td>
<p>
NIMLOC
</p>
</td>
<td>
<p>
Nimrod Locator.
</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>
NSAP-PTR
</p>
</td>
<td>
<p>
Historical.
</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>
NULL
</p>
</td>
<td>
<p>
This is an opaque container.
</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>
OPENPGPKEY
</p>
</td>
<td>
<p>
Used to hold an OPENPGPKEY.
</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>
TLSA
</p>
</td>
<td>
<p>
Transport Layer Security Certificate Association.
Described in RFC 6698.
</p>
</td>
</tr>
<tr>
<td>
<p>
TXT
</p>
</td>
<td>
<p>
Text records. Described in RFC 1035.
</p>
</td>
</tr>
<tr>
<td>
<p>
UID
</p>
</td>
<td>
<p>
Reserved.
</p>
</td>
</tr>
<tr>
<td>
<p>
UINFO
</p>
</td>
<td>
<p>
Reserved.
</p>
</td>
</tr>
<tr>
<td>
<p>
UNSPEC
</p>
</td>
<td>
<p>
Reserved. Historical.
</p>
</td>
</tr>
<tr>
<td>
<p>
URI
</p>
</td>
<td>
<p>
Holds a URI. Described in RFC 7553.
</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="id2602121"></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="id2602642"></a>Discussion of MX Records</h3></div></div></div>
<p>
As described above, domain servers store information as a
series of resource records, each of which contains a particular
piece of information about a given domain name (which is usually,
but not always, a host). The simplest way to think of a RR is as
a typed pair of data, a domain name matched with a relevant datum,
and stored with some additional type information to help systems
determine when the RR is relevant.
</p>
<p>
MX records are used to control delivery of email. The data
specified in the record is a priority and a domain name. The
priority
controls the order in which email delivery is attempted, with the
lowest number first. If two priorities are the same, a server is
chosen randomly. If no servers at a given priority are responding,
the mail transport agent will fall back to the next largest
priority.
Priority numbers do not have any absolute meaning &#8212; they are
relevant
only respective to other MX records for that domain name. The
domain
name given is the machine to which the mail will be delivered.
It <span class="emphasis"><em>must</em></span> have an associated address record
(A or AAAA) &#8212; CNAME is not sufficient.
</p>
<p>
For a given domain, if there is both a CNAME record and an
MX record, the MX record is in error, and will be ignored.
Instead,
the mail will be delivered to the server specified in the MX
record
pointed to by the CNAME.
For example:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
<col>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
<code class="literal">example.com.</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">MX</code>
</p>
</td>
<td>
<p>
<code class="literal">10</code>
</p>
</td>
<td>
<p>
<code class="literal">mail.example.com.</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">MX</code>
</p>
</td>
<td>
<p>
<code class="literal">10</code>
</p>
</td>
<td>
<p>
<code class="literal">mail2.example.com.</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">MX</code>
</p>
</td>
<td>
<p>
<code class="literal">20</code>
</p>
</td>
<td>
<p>
<code class="literal">mail.backup.org.</code>
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="literal">mail.example.com.</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.0.0.1</code>
</p>
</td>
<td>
<p></p>
</td>
</tr>
<tr>
<td>
<p>
<code class="literal">mail2.example.com.</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.0.0.2</code>
</p>
</td>
<td>
<p></p>
</td>
</tr>
</tbody>
</table></div>
<p>
Mail delivery will be attempted to <code class="literal">mail.example.com</code> and
<code class="literal">mail2.example.com</code> (in
any order), and if neither of those succeed, delivery to <code class="literal">mail.backup.org</code> will
be attempted.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="Setting_TTLs"></a>Setting TTLs</h3></div></div></div>
<p>
The time-to-live of the RR field is a 32-bit integer represented
in units of seconds, and is primarily used by resolvers when they
cache RRs. The TTL describes how long a RR can be cached before it
should be discarded. The following three types of TTL are
currently
used in a zone file.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
SOA
</p>
</td>
<td>
<p>
The last field in the SOA is the negative
caching TTL. This controls how long other servers will
cache no-such-domain
(NXDOMAIN) responses from you.
</p>
<p>
The maximum time for
negative caching is 3 hours (3h).
</p>
</td>
</tr>
<tr>
<td>
<p>
$TTL
</p>
</td>
<td>
<p>
The $TTL directive at the top of the
zone file (before the SOA) gives a default TTL for every
RR without
a specific TTL set.
</p>
</td>
</tr>
<tr>
<td>
<p>
RR TTLs
</p>
</td>
<td>
<p>
Each RR can have a TTL as the second
field in the RR, which will control how long other
servers can cache it.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
All of these TTLs default to units of seconds, though units
can be explicitly specified, for example, <code class="literal">1h30m</code>.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2603325"></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="id2603589"></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="id2603611"></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="id2603627"></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="id2603688"></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="id2603757"></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="id2603794"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</h3></div></div></div>
<p>
Syntax: <span><strong class="command">$GENERATE</strong></span>
<em class="replaceable"><code>range</code></em>
<em class="replaceable"><code>lhs</code></em>
[<span class="optional"><em class="replaceable"><code>ttl</code></em></span>]
[<span class="optional"><em class="replaceable"><code>class</code></em></span>]
<em class="replaceable"><code>type</code></em>
<em class="replaceable"><code>rhs</code></em>
[<span class="optional"><em class="replaceable"><code>comment</code></em></span>]
</p>
<p><span><strong class="command">$GENERATE</strong></span>
is used to create a series of resource records that only
differ from each other by an
iterator. <span><strong class="command">$GENERATE</strong></span> can be used to
easily generate the sets of records required to support
sub /24 reverse delegations described in RFC 2317:
Classless IN-ADDR.ARPA delegation.
</p>
<pre class="programlisting">$ORIGIN 0.0.192.IN-ADDR.ARPA.
$GENERATE 1-2 @ NS SERVER$.EXAMPLE.
$GENERATE 1-127 $ CNAME $.0</pre>
<p>
is equivalent to
</p>
<pre class="programlisting">0.0.0.192.IN-ADDR.ARPA. NS SERVER1.EXAMPLE.
0.0.0.192.IN-ADDR.ARPA. NS SERVER2.EXAMPLE.
1.0.0.192.IN-ADDR.ARPA. CNAME 1.0.0.0.192.IN-ADDR.ARPA.
2.0.0.192.IN-ADDR.ARPA. CNAME 2.0.0.0.192.IN-ADDR.ARPA.
...
127.0.0.192.IN-ADDR.ARPA. CNAME 127.0.0.0.192.IN-ADDR.ARPA.
</pre>
<p>
Generate a set of A and MX records. Note the MX's right hand
side is a quoted string. The quotes will be stripped when the
right hand side is processed.
</p>
<pre class="programlisting">
$ORIGIN EXAMPLE.
$GENERATE 1-127 HOST-$ A 1.2.3.$
$GENERATE 1-127 HOST-$ MX "0 ."</pre>
<p>
is equivalent to
</p>
<pre class="programlisting">HOST-1.EXAMPLE. A 1.2.3.1
HOST-1.EXAMPLE. MX 0 .
HOST-2.EXAMPLE. A 1.2.3.2
HOST-2.EXAMPLE. MX 0 .
HOST-3.EXAMPLE. A 1.2.3.3
HOST-3.EXAMPLE. MX 0 .
...
HOST-127.EXAMPLE. A 1.2.3.127
HOST-127.EXAMPLE. MX 0 .
</pre>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p><span><strong class="command">range</strong></span></p>
</td>
<td>
<p>
This can be one of two forms: start-stop
or start-stop/step. If the first form is used, then step
is set to 1. start, stop and step must be positive
integers between 0 and (2^31)-1. start must not be
larger than stop.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">lhs</strong></span></p>
</td>
<td>
<p>This
describes the owner name of the resource records
to be created. Any single <span><strong class="command">$</strong></span>
(dollar sign)
symbols within the <span><strong class="command">lhs</strong></span> string
are replaced by the iterator value.
To get a $ in the output, you need to escape the
<span><strong class="command">$</strong></span> using a backslash
<span><strong class="command">\</strong></span>,
e.g. <span><strong class="command">\$</strong></span>. The
<span><strong class="command">$</strong></span> may optionally be followed
by modifiers which change the offset from the
iterator, field width and base.
Modifiers are introduced by a
<span><strong class="command">{</strong></span> (left brace) immediately following the
<span><strong class="command">$</strong></span> as
<span><strong class="command">${offset[,width[,base]]}</strong></span>.
For example, <span><strong class="command">${-20,3,d}</strong></span>
subtracts 20 from the current value, prints the
result as a decimal in a zero-padded field of
width 3.
Available output forms are decimal
(<span><strong class="command">d</strong></span>), octal
(<span><strong class="command">o</strong></span>), hexadecimal
(<span><strong class="command">x</strong></span> or <span><strong class="command">X</strong></span>
for uppercase) and nibble
(<span><strong class="command">n</strong></span> or <span><strong class="command">N</strong></span>\
for uppercase). The default modifier is
<span><strong class="command">${0,0,d}</strong></span>. If the
<span><strong class="command">lhs</strong></span> is not absolute, the
current <span><strong class="command">$ORIGIN</strong></span> is appended
to the name.
</p>
<p>
In nibble mode the value will be treated as
if it was a reversed hexadecimal string
with each hexadecimal digit as a separate
label. The width field includes the label
separator.
</p>
<p>
For compatibility with earlier versions,
<span><strong class="command">$$</strong></span> is still recognized as
indicating a literal $ in the output.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">ttl</strong></span></p>
</td>
<td>
<p>
Specifies the time-to-live of the generated records. If
not specified this will be inherited using the
normal TTL inheritance rules.
</p>
<p><span><strong class="command">class</strong></span>
and <span><strong class="command">ttl</strong></span> can be
entered in either order.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">class</strong></span></p>
</td>
<td>
<p>
Specifies the class of the generated records.
This must match the zone class if it is
specified.
</p>
<p><span><strong class="command">class</strong></span>
and <span><strong class="command">ttl</strong></span> can be
entered in either order.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">type</strong></span></p>
</td>
<td>
<p>
Any valid type.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">rhs</strong></span></p>
</td>
<td>
<p>
<span><strong class="command">rhs</strong></span>, optionally, quoted string.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
The <span><strong class="command">$GENERATE</strong></span> directive is a <acronym class="acronym">BIND</acronym> extension
and not part of the standard zone file format.
</p>
<p>
BIND 8 does not support the optional TTL and CLASS fields.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="zonefile_format"></a>Additional File Formats</h3></div></div></div>
<p>
In addition to the standard textual format, BIND 9
supports the ability to read or dump to zone files in
other formats.
</p>
<p>
The <code class="constant">raw</code> format is
a binary representation of zone data in a manner similar
to that used in zone transfers. Since it does not require
parsing text, load time is significantly reduced.
</p>
<p>
An even faster alternative is the <code class="constant">map</code>
format, which is an image of a <acronym class="acronym">BIND</acronym> 9
in-memory zone database; it is capable of being loaded
directly into memory via the <span><strong class="command">mmap()</strong></span>
function; the zone can begin serving queries almost
immediately.
</p>
<p>
For a primary server, a zone file in
<code class="constant">raw</code> or <code class="constant">map</code>
format is expected to be generated from a textual zone
file by the <span><strong class="command">named-compilezone</strong></span> command.
For a secondary server or for a dynamic zone, it is automatically
generated (if this format is specified by the
<span><strong class="command">masterfile-format</strong></span> option) when
<span><strong class="command">named</strong></span> dumps the zone contents after
zone transfer or when applying prior updates.
</p>
<p>
If a zone file in a binary format needs manual modification,
it first must be converted to a textual form by the
<span><strong class="command">named-compilezone</strong></span> command. All
necessary modification should go to the text file, which
should then be converted to the binary form by the
<span><strong class="command">named-compilezone</strong></span> command again.
</p>
<p>
Note that <span><strong class="command">map</strong></span> format is extremely
architecture-specific. A <code class="constant">map</code>
file <span class="emphasis"><em>cannot</em></span> be used on a system
with different pointer size, endianness or data alignment
than the system on which it was generated, and should in
general be used only inside a single system.
While <code class="constant">raw</code> format uses
network byte order and avoids architecture-dependent
data alignment so that it is as portable as
possible, it is also primarily expected to be used
inside the same single system. To export a
zone file in either <code class="constant">raw</code> or
<code class="constant">map</code> format, or make a
portable backup of such a file, conversion to
<code class="constant">text</code> format is recommended.
</p>
</div>
</div>
<div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="statistics"></a>BIND9 Statistics</h2></div></div></div>
<p>
<acronym class="acronym">BIND</acronym> 9 maintains lots of statistics
information and provides several interfaces for users to
get access to the statistics.
The available statistics include all statistics counters
that were available in <acronym class="acronym">BIND</acronym> 8 and
are meaningful in <acronym class="acronym">BIND</acronym> 9,
and other information that is considered useful.
</p>
<p>
The statistics information is categorized into the following
sections.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>Incoming Requests</p>
</td>
<td>
<p>
The number of incoming DNS requests for each OPCODE.
</p>
</td>
</tr>
<tr>
<td>
<p>Incoming Queries</p>
</td>
<td>
<p>
The number of incoming queries for each RR type.
</p>
</td>
</tr>
<tr>
<td>
<p>Outgoing Queries</p>
</td>
<td>
<p>
The number of outgoing queries for each RR
type sent from the internal resolver.
Maintained per view.
</p>
</td>
</tr>
<tr>
<td>
<p>Name Server Statistics</p>
</td>
<td>
<p>
Statistics counters about incoming request processing.
</p>
</td>
</tr>
<tr>
<td>
<p>Zone Maintenance Statistics</p>
</td>
<td>
<p>
Statistics counters regarding zone maintenance
operations such as zone transfers.
</p>
</td>
</tr>
<tr>
<td>
<p>Resolver Statistics</p>
</td>
<td>
<p>
Statistics counters about name resolution
performed in the internal resolver.
Maintained per view.
</p>
</td>
</tr>
<tr>
<td>
<p>Cache DB RRsets</p>
</td>
<td>
<p>
The number of RRsets per RR type and nonexistent
names stored in the cache database.
If the exclamation mark (!) is printed for a RR
type, it means that particular type of RRset is
known to be nonexistent (this is also known as
"NXRRSET"). If a hash mark (#) is present then
the RRset is marked for garbage collection.
Maintained per view.
</p>
</td>
</tr>
<tr>
<td>
<p>Socket I/O Statistics</p>
</td>
<td>
<p>
Statistics counters about network related events.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
A subset of Name Server Statistics is collected and shown
per zone for which the server has the authority when
<span><strong class="command">zone-statistics</strong></span> is set to
<strong class="userinput"><code>yes</code></strong>.
These statistics counters are shown with their zone and view
names.
In some cases the view names are omitted for the default view.
</p>
<p>
There are currently two user interfaces to get access to the
statistics.
One is in the plain text format dumped to the file specified
by the <span><strong class="command">statistics-file</strong></span> configuration option.
The other is remotely accessible via a statistics channel
when the <span><strong class="command">statistics-channels</strong></span> statement
is specified in the configuration file
(see <a href="Bv9ARM.ch06.html#statschannels" title="statistics-channels Statement Grammar">the section called &#8220;<span><strong class="command">statistics-channels</strong></span> Statement Grammar&#8221;</a>.)
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="statsfile"></a>The Statistics File</h4></div></div></div>
<p>
The text format statistics dump begins with a line, like:
</p>
<p>
<span><strong class="command">+++ Statistics Dump +++ (973798949)</strong></span>
</p>
<p>
The number in parentheses is a standard
Unix-style timestamp, measured as seconds since January 1, 1970.
Following
that line is a set of statistics information, which is categorized
as described above.
Each section begins with a line, like:
</p>
<p>
<span><strong class="command">++ Name Server Statistics ++</strong></span>
</p>
<p>
Each section consists of lines, each containing the statistics
counter value followed by its textual description.
See below for available counters.
For brevity, counters that have a value of 0 are not shown
in the statistics file.
</p>
<p>
The statistics dump ends with the line where the
number is identical to the number in the beginning line; for example:
</p>
<p>
<span><strong class="command">--- Statistics Dump --- (973798949)</strong></span>
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="statistics_counters"></a>Statistics Counters</h3></div></div></div>
<p>
The following tables summarize statistics counters that
<acronym class="acronym">BIND</acronym> 9 provides.
For each row of the tables, the leftmost column is the
abbreviated symbol name of that counter.
These symbols are shown in the statistics information
accessed via an HTTP statistics channel.
The rightmost column gives the description of the counter,
which is also shown in the statistics file
(but, in this document, possibly with slight modification
for better readability).
Additional notes may also be provided in this column.
When a middle column exists between these two columns,
it gives the corresponding counter name of the
<acronym class="acronym">BIND</acronym> 8 statistics, if applicable.
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2604856"></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">QryNXRedir</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Queries resulted in NXDOMAIN that were redirected.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">QryNXRedirRLookup</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Queries resulted in NXDOMAIN that were redirected
and resulted in a successful remote lookup.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">XfrReqDone</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Requested zone transfers completed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateReqFwd</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Update requests forwarded.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateRespFwd</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Update responses forwarded.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateFwdFail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Dynamic update forward failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateDone</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Dynamic updates completed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateFail</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Dynamic updates failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">UpdateBadPrereq</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Dynamic updates rejected due to prerequisite failure.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RateDropped</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Responses dropped by rate limits.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RateSlipped</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Responses truncated by rate limits.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">RPZRewrites</strong></span></p>
</td>
<td>
<p><span><strong class="command"></strong></span></p>
</td>
<td>
<p>
Response policy zone rewrites.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2606557"></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="id2607009"></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="id2608030"></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="id2608540"></a>Compatibility with <span class="emphasis"><em>BIND</em></span> 8 Counters</h4></div></div></div>
<p>
Most statistics counters that were available
in <span><strong class="command">BIND</strong></span> 8 are also supported in
<span><strong class="command">BIND</strong></span> 9 as shown in the above tables.
Here are notes about other counters that do not appear
in these tables.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><span><strong class="command">RFwdR,SFwdR</strong></span></span></dt>
<dd><p>
These counters are not supported
because <span><strong class="command">BIND</strong></span> 9 does not adopt
the notion of <span class="emphasis"><em>forwarding</em></span>
as <span><strong class="command">BIND</strong></span> 8 did.
</p></dd>
<dt><span class="term"><span><strong class="command">RAXFR</strong></span></span></dt>
<dd><p>
This counter is accessible in the Incoming Queries section.
</p></dd>
<dt><span class="term"><span><strong class="command">RIQ</strong></span></span></dt>
<dd><p>
This counter is accessible in the Incoming Requests section.
</p></dd>
<dt><span class="term"><span><strong class="command">ROpts</strong></span></span></dt>
<dd><p>
This counter is not supported
because <span><strong class="command">BIND</strong></span> 9 does not care
about IP options in the first place.
</p></dd>
</dl></div>
</div>
</div>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="Bv9ARM.ch05.html">Prev</a>�</td>
<td width="20%" align="center">�</td>
<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch07.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Chapter�5.�The <acronym class="acronym">BIND</acronym> 9 Lightweight Resolver�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�Chapter�7.�<acronym class="acronym">BIND</acronym> 9 Security Considerations</td>
</tr>
</table>
</div>
<p style="text-align: center;">BIND 9.11.0pre-alpha</p>
</body>
</html>