Bv9ARM.ch06.html revision e191be096ca7a731d7cd5095b3c0f9584c0a5453
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<!--
59602f2a7c4e4809941583bed3e94cd26e628f1aTinderbox User - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater - Copyright (C) 2000-2003 Internet Software Consortium.
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User -
19558a04decde0e7261d489d92d04ad88104217bTinderbox User - Permission to use, copy, modify, and/or distribute this software for any
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews - purpose with or without fee is hereby granted, provided that the above
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews - copyright notice and this permission notice appear in all copies.
c57668a2fbbe558c1bd21652813616f2f517c469Tinderbox User -
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
287a6a8f9040dc43560cd69cddf83bfc0f53b76fTinderbox User - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
8de3f14f1c300c3e1ed99084cc03485b42c92bf1Tinderbox User - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
950d203b64f512b85fcc093ee1e9e3e531a1aea3Tinderbox User - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User - PERFORMANCE OF THIS SOFTWARE.
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User-->
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<html>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews<head>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<title>Chapter�6.�BIND 9 Configuration Reference</title>
d5637bdbb931ff79fced3d4858d83212ea58ed15Tinderbox User<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<link rel="prev" href="Bv9ARM.ch05.html" title="Chapter�5.�The BIND 9 Lightweight Resolver">
d5637bdbb931ff79fced3d4858d83212ea58ed15Tinderbox User<link rel="next" href="Bv9ARM.ch07.html" title="Chapter�7.�BIND 9 Security Considerations">
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</head>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="navheader">
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<table width="100%" summary="Navigation header">
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<tr><th colspan="3" align="center">Chapter�6.�<acronym class="acronym">BIND</acronym> 9 Configuration Reference</th></tr>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<td width="20%" align="left">
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<a accesskey="p" href="Bv9ARM.ch05.html">Prev</a>�</td>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews<th width="60%" align="center">�</th>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch07.html">Next</a>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User</td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</table>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<hr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</div>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<div class="chapter">
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<div class="titlepage"><div><div><h1 class="title">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<a name="Bv9ARM.ch06"></a>Chapter�6.�<acronym class="acronym">BIND</acronym> 9 Configuration Reference</h1></div></div></div>
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User<div class="toc">
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<p><b>Table of Contents</b></p>
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<dl class="toc">
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#configuration_file_elements">Configuration File Elements</a></span></dt>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<dd><dl>
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<dt><span class="section"><a href="Bv9ARM.ch06.html#address_match_lists">Address Match Lists</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="section"><a href="Bv9ARM.ch06.html#comment_syntax">Comment Syntax</a></span></dt>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont</dl></dd>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="section"><a href="Bv9ARM.ch06.html#Configuration_File_Grammar">Configuration File Grammar</a></span></dt>
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt<dd><dl>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#acl_grammar"><span class="command"><strong>acl</strong></span> Statement Grammar</a></span></dt>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#acl"><span class="command"><strong>acl</strong></span> Statement Definition and
aa9c561961e9d877946ebaa8795fa2be054ab7bfEvan Hunt Usage</a></span></dt>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#controls_grammar"><span class="command"><strong>controls</strong></span> Statement Grammar</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="section"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span class="command"><strong>controls</strong></span> Statement Definition and
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont Usage</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="section"><a href="Bv9ARM.ch06.html#include_grammar"><span class="command"><strong>include</strong></span> Statement Grammar</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#include_statement"><span class="command"><strong>include</strong></span> Statement Definition and Usage</a></span></dt>
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch06.html#key_grammar"><span class="command"><strong>key</strong></span> Statement Grammar</a></span></dt>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#key_statement"><span class="command"><strong>key</strong></span> Statement Definition and Usage</a></span></dt>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#logging_grammar"><span class="command"><strong>logging</strong></span> Statement Grammar</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#logging_statement"><span class="command"><strong>logging</strong></span> Statement Definition and Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#lwres_grammar"><span class="command"><strong>lwres</strong></span> Statement Grammar</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="section"><a href="Bv9ARM.ch06.html#lwres_statement"><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#masters_grammar"><span class="command"><strong>masters</strong></span> Statement Grammar</a></span></dt>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#masters_statement"><span class="command"><strong>masters</strong></span> Statement Definition and
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User Usage</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#options_grammar"><span class="command"><strong>options</strong></span> Statement Grammar</a></span></dt>
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater<dt><span class="section"><a href="Bv9ARM.ch06.html#options"><span class="command"><strong>options</strong></span> Statement Definition and
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Usage</a></span></dt>
eabc9c3c07cd956d3c436bd7614cb162dabdda76Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span class="command"><strong>server</strong></span> Statement Grammar</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span class="command"><strong>server</strong></span> Statement Definition and
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews Usage</a></span></dt>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#statschannels"><span class="command"><strong>statistics-channels</strong></span> Statement Grammar</a></span></dt>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics_channels"><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User Usage</a></span></dt>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#trusted-keys"><span class="command"><strong>trusted-keys</strong></span> Statement Grammar</a></span></dt>
294e9d4c34462d29a3e766c88f452b46aeb3702fTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#trusted_keys"><span class="command"><strong>trusted-keys</strong></span> Statement Definition
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User and Usage</a></span></dt>
4c6bae917bec70e1fc4d1b761a9765075af78441Tinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#managed_keys"><span class="command"><strong>managed-keys</strong></span> Statement Grammar</a></span></dt>
294e9d4c34462d29a3e766c88f452b46aeb3702fTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#managed-keys"><span class="command"><strong>managed-keys</strong></span> Statement Definition
2ae159b376dac23870d8005563c585acf85a4b5aEvan Hunt and Usage</a></span></dt>
2ae159b376dac23870d8005563c585acf85a4b5aEvan Hunt<dt><span class="section"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span class="command"><strong>view</strong></span> Statement Grammar</a></span></dt>
2ae159b376dac23870d8005563c585acf85a4b5aEvan Hunt<dt><span class="section"><a href="Bv9ARM.ch06.html#view_statement"><span class="command"><strong>view</strong></span> Statement Definition and Usage</a></span></dt>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span class="command"><strong>zone</strong></span>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User Statement Grammar</a></span></dt>
2ae159b376dac23870d8005563c585acf85a4b5aEvan Hunt<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_statement"><span class="command"><strong>zone</strong></span> Statement Definition and Usage</a></span></dt>
7cc0a5d21ef046bfd630c4769943d896a7d7472cTinderbox User</dl></dd>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_file">Zone File</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd><dl>
ee11dfc481f2ef6a032a715454f6290961a722d2Tinderbox User<dt><span class="section"><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>
ee11dfc481f2ef6a032a715454f6290961a722d2Tinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#mx_records">Discussion of MX Records</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#ipv4_reverse">Inverse Mapping in IPv4</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#zone_directives">Other Zone File Directives</a></span></dt>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#generate_directive"><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</a></span></dt>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</dl></dd>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics">BIND9 Statistics</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dd><dl>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#statsfile">The Statistics File</a></span></dt>
aef6cf0f147a5014d4891c9689b9f463399e16e7Tinderbox User<dt><span class="section"><a href="Bv9ARM.ch06.html#statistics_counters">Statistics Counters</a></span></dt>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</dl></dd>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</dl>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson</div>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <acronym class="acronym">BIND</acronym> 9 configuration is broadly similar
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User to <acronym class="acronym">BIND</acronym> 8; however, there are a few new
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews areas
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User of configuration, such as views. <acronym class="acronym">BIND</acronym>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews 8 configuration files should work with few alterations in <acronym class="acronym">BIND</acronym>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews 9, although more complex configurations should be reviewed to check
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User if they can be more efficiently implemented using the new features
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews found in <acronym class="acronym">BIND</acronym> 9.
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <acronym class="acronym">BIND</acronym> 4 configuration files can be
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews converted to the new format
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User using the shell script
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="filename">contrib/named-bootconf/named-bootconf.sh</code>.
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson<div class="section">
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<div class="titlepage"><div><div><h2 class="title" style="clear: both">
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<a name="configuration_file_elements"></a>Configuration File Elements</h2></div></div></div>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews Following is a list of elements used throughout the <acronym class="acronym">BIND</acronym> configuration
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews file documentation:
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User </p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<div class="informaltable"><table border="1">
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<colgroup>
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews<col width="1.855in" class="1">
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<col width="3.770in" class="2">
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews</colgroup>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<tbody>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<tr>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<td>
2a31bd531072824ef252c18303859d6af7451b00Francis Dupont <p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User <code class="varname">acl_name</code>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
2a31bd531072824ef252c18303859d6af7451b00Francis Dupont </td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<td>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User <p>
5747235bf35e7398984fd6b4632743396895ea7aTinderbox User The name of an <code class="varname">address_match_list</code> as
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews defined by the <span class="command"><strong>acl</strong></span> statement.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews </td>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews</tr>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<tr>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<td>
7f9e2fff07b9c17e0d7a0ea7abc9304ce9d01b61Tinderbox User <p>
5747235bf35e7398984fd6b4632743396895ea7aTinderbox User <code class="varname">address_match_list</code>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<td>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews <p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews A list of one or more
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews <code class="varname">ip_addr</code>,
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User <code class="varname">ip_prefix</code>, <code class="varname">key_id</code>,
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews or <code class="varname">acl_name</code> elements, see
01a5c5503482fb3ba52088bf0178a7213273bf96Mark Andrews <a class="xref" href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called &#8220;Address Match Lists&#8221;</a>.
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User </p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</tr>
cdfc81e048bd34c1d628380247bda6b80a89e20eAutomatic Updater<tr>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<td>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">masters_list</code>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </p>
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <p>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User A named list of one or more <code class="varname">ip_addr</code>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews with optional <code class="varname">key_id</code> and/or
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <code class="varname">ip_port</code>.
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User A <code class="varname">masters_list</code> may include other
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <code class="varname">masters_lists</code>.
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews </p>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<tr>
fe80a4909bf62b602feaf246866e9d29f7654194Automatic Updater<td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <code class="varname">domain_name</code>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson <p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User A quoted string which will be used as
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews a DNS name, for example "<code class="literal">my.test.domain</code>".
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User</tr>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater<tr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <p>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User <code class="varname">namelist</code>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </td>
133e6d43fa82e80d3798be4de00f4540f485ec6cAutomatic Updater<td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews A list of one or more <code class="varname">domain_name</code>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User elements.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </td>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson</tr>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<tr>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<td>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">dotted_decimal</code>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </p>
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User </td>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User<td>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <p>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User One to four integers valued 0 through
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews 255 separated by dots (`.'), such as <span class="command"><strong>123</strong></span>,
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User <span class="command"><strong>45.67</strong></span> or <span class="command"><strong>89.123.45.67</strong></span>.
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews </p>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User </td>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User</tr>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<tr>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<td>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User <p>
1fce11b1d3f2d461d261156b8cdc64ab864f06a9Tinderbox User <code class="varname">ip4_addr</code>
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User </p>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews </td>
7ca715ad1587a68a531ea1cdea07515d7232567eTinderbox User<td>
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User <p>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater An IPv4 address with exactly four elements
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in <code class="varname">dotted_decimal</code> notation.
bac4435d473c9a0281507524f084480c34aa942aTinderbox User </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </td>
933799f3641f4f78445d015008bad0038900a82aTinderbox User</tr>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<tr>
933799f3641f4f78445d015008bad0038900a82aTinderbox User<td>
4151211e6649332f7b5a55870cbe37128bcc7b29Tinderbox User <p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <code class="varname">ip6_addr</code>
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
f525041ae26958385b697cf82a30f108577024b6Tinderbox User <p>
b02be031b9ff37b042adc8e68e36b8bbc1f672b7Tinderbox User An IPv6 address, such as <span class="command"><strong>2001:db8::1234</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv6 scoped addresses that have ambiguity on their
ba8b771c371967dd1254c7fa82ebe4158ee04b24Tinderbox User scope zones must be disambiguated by an appropriate
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater zone ID with the percent character (`%') as
3ec8f7777ea2b04fc1ebb63077f0916f63b1011aTinderbox User delimiter. It is strongly recommended to use
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User string zone names rather than numeric identifiers,
b02be031b9ff37b042adc8e68e36b8bbc1f672b7Tinderbox User in order to be robust against system configuration
933799f3641f4f78445d015008bad0038900a82aTinderbox User changes. However, since there is no standard
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater mapping for such names and identifier values,
19b3dc94bce93fa76bd7e066f9298630dbc9dcb4Automatic Updater currently only interface names as link identifiers
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater are supported, assuming one-to-one mapping between
9513a2a6670951f5cf5477fcfec9f933fcaff628Automatic Updater interfaces and links. For example, a link-local
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews address <span class="command"><strong>fe80::1</strong></span> on the link
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater attached to the interface <span class="command"><strong>ne0</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater can be specified as <span class="command"><strong>fe80::1%ne0</strong></span>.
bac4435d473c9a0281507524f084480c34aa942aTinderbox User Note that on most systems link-local addresses
39ae0eafed076ef769fef5c18b22a8051df5c93aTinderbox User always have the ambiguity, and need to be
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews disambiguated.
c2abd6efeb9affa70aabb63da2acb23e135cf7f2Mark Andrews </p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User</tr>
f525041ae26958385b697cf82a30f108577024b6Tinderbox User<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <code class="varname">ip_addr</code>
5e82fe9a56d17bfbd120817d00d28c5952ab4ddcTinderbox User </p>
4cda4fd158d6ded5586bacea8c388445d99611eaAutomatic Updater </td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<td>
f2f7a53ba0ba69cfe8c505eea16f71bad9d8d449Tinderbox User <p>
c26604a73c4ce907ef6392f38b3fac838b1873a9Tinderbox User An <code class="varname">ip4_addr</code> or <code class="varname">ip6_addr</code>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
e08cdffb3ae4ad409f37e3e5a218fe4b7e0e3904Tinderbox User</tr>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<tr>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<td>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User <p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <code class="varname">ip_dscp</code>
ba8b771c371967dd1254c7fa82ebe4158ee04b24Tinderbox User </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
76408aae412cda298c5e43da0eebb23c875a4426Tinderbox User <p>
7f9e2fff07b9c17e0d7a0ea7abc9304ce9d01b61Tinderbox User A <code class="varname">number</code> between 0 and 63, used
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to select a differentiated services code point (DSCP)
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User value for use with outgoing traffic on operating systems
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews that support DSCP.
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
757ff043760e4743dda1a10e7d58349275934902Tinderbox User</tr>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews<tr>
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews<td>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <p>
757ff043760e4743dda1a10e7d58349275934902Tinderbox User <code class="varname">ip_port</code>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews </td>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<td>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson <p>
1bcc3273a80c256f11d9098a00ba2c041939e233Mark Andrews An IP port <code class="varname">number</code>.
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User The <code class="varname">number</code> is limited to 0
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User through 65535, with values
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews below 1024 typically restricted to use by processes running
ba8b771c371967dd1254c7fa82ebe4158ee04b24Tinderbox User as root.
bac4435d473c9a0281507524f084480c34aa942aTinderbox User In some cases, an asterisk (`*') character can be used as a
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews placeholder to
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User select a random high-numbered port.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User </td>
3857cb6fcabeb79d85de4b3e3e4ab99912b701f8Mark Andrews</tr>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<tr>
e64202536ea72d8f371dd0df9fc763f8d70bf886Tinderbox User<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User <code class="varname">ip_prefix</code>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson </p>
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User </td>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<td>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews An IP network specified as an <code class="varname">ip_addr</code>,
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User followed by a slash (`/') and then the number of bits in the
ebdf202f2198158ab4d30f22c370a9c63760d071Tinderbox User netmask.
8292deab031e7599cd7622aa7675fbe139ca6095Mark Andrews Trailing zeros in a <code class="varname">ip_addr</code>
c1e2310a3725eeed45e5e7c86750c64c5a02e993Francis Dupont may omitted.
c1e2310a3725eeed45e5e7c86750c64c5a02e993Francis Dupont For example, <span class="command"><strong>127/8</strong></span> is the
c1e2310a3725eeed45e5e7c86750c64c5a02e993Francis Dupont network <span class="command"><strong>127.0.0.0</strong></span> with
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews netmask <span class="command"><strong>255.0.0.0</strong></span> and <span class="command"><strong>1.2.3.0/28</strong></span> is
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont network <span class="command"><strong>1.2.3.0</strong></span> with netmask <span class="command"><strong>255.255.255.240</strong></span>.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews <p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews When specifying a prefix involving a IPv6 scoped address
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont the scope may be omitted. In that case the prefix will
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews match packets from any scope.
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </p>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews </td>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont</tr>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<tr>
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <code class="varname">key_id</code>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater <p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews A <code class="varname">domain_name</code> representing
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews the name of a shared key, to be used for transaction
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User security.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<td>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">key_list</code>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
e8fc8c884b44371784805e1e0d3100da403dd3f1Automatic Updater </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <p>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User A list of one or more
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">key_id</code>s,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews separated by semicolons and ending with a semicolon.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews</tr>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <p>
39cad8fb7d7ff3436bb24ce761354afcb80d295aMark Andrews <code class="varname">number</code>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </td>
01a5c5503482fb3ba52088bf0178a7213273bf96Mark Andrews<td>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User <p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews A non-negative 32-bit integer
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews (i.e., a number between 0 and 4294967295, inclusive).
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews Its acceptable value might further
e64202536ea72d8f371dd0df9fc763f8d70bf886Tinderbox User be limited by the context in which it is used.
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User </p>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User </td>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater</tr>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<tr>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<td>
757ff043760e4743dda1a10e7d58349275934902Tinderbox User <p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <code class="varname">path_name</code>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </td>
933799f3641f4f78445d015008bad0038900a82aTinderbox User<td>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont A quoted string which will be used as
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater a pathname, such as <code class="filename">zones/master/my.test.domain</code>.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson </td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<tr>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">port_list</code>
efb0e886f18894a1d2489f1ad74ad14b579e11c7Mark Andrews </p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews </td>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User A list of an <code class="varname">ip_port</code> or a port
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington range.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington A port range is specified in the form of
a3ffa9ab0644ae2b52f2e13a00b5e85b879f612fTinderbox User <strong class="userinput"><code>range</code></strong> followed by
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont two <code class="varname">ip_port</code>s,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <code class="varname">port_low</code> and
1bf507ca635310b340aea42d6c3e567819974a99Tinderbox User <code class="varname">port_high</code>, which represents
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews port numbers from <code class="varname">port_low</code> through
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">port_high</code>, inclusive.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <code class="varname">port_low</code> must not be larger than
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <code class="varname">port_high</code>.
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User For example,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <strong class="userinput"><code>range 1024 65535</code></strong> represents
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User ports from 1024 through 65535.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User In either case an asterisk (`*') character is not
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont allowed as a valid <code class="varname">ip_port</code>.
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews </p>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews </td>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews</tr>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<tr>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews<td>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <code class="varname">size_spec</code>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </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 class="command"><strong>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.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<tr>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">size_or_percent</code>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<td>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">size_spec</code> or integer value
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews followed by '%' to represent percents.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews The behavior is exactly the same as
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <code class="varname">size_spec</code>, but
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User <code class="varname">size_or_percent</code> allows also
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews to specify a positive integer value followed by
646fed0d28be4387e3e32fb0f5732a1f58b572baTinderbox User '%' sign to represent percents.
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </p>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater</tr>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<tr>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater<td>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <code class="varname">yes_or_no</code>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater </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>
ae7e54b14c946e0984c191554db9abb4893f9349Automatic Updater and <strong class="userinput"><code>0</code></strong>.
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </p>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User </td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User</tr>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<tr>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <p>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <code class="varname">dialup_option</code>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User </p>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User </td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User<td>
c11c7b47726c02eb05e29ff7be56a3343146e396Tinderbox User <p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews 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>,
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <strong class="userinput"><code>notify-passive</code></strong>, <strong class="userinput"><code>refresh</code></strong> or
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews <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>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tr>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</tbody>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</table></div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="section">
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<div class="titlepage"><div><div><h3 class="title">
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<a name="address_match_lists"></a>Address Match Lists</h3></div></div></div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="section">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<div class="titlepage"><div><div><h4 class="title">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<a name="id-1.7.4.4.2"></a>Syntax</h4></div></div></div>
a3ffa9ab0644ae2b52f2e13a00b5e85b879f612fTinderbox User<pre class="programlisting"><code class="varname">address_match_list</code> = address_match_list_element ;
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<span class="optional"> address_match_list_element; ... </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<code class="varname">address_match_list_element</code> = [<span class="optional"> ! </span>] (ip_address [<span class="optional">/length</span>] |
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont key key_id | acl_name | { address_match_list } )
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont</pre>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="section">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="titlepage"><div><div><h4 class="title">
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<a name="id-1.7.4.4.3"></a>Definition and Usage</h4></div></div></div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews Address match lists are primarily used to determine access
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User control for various server operations. They are also used in
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews the <span class="command"><strong>listen-on</strong></span> and <span class="command"><strong>sortlist</strong></span>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User statements. The elements which constitute an address match
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont list can be any of the following:
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<li class="listitem">an IP address (IPv4 or IPv6)</li>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<li class="listitem">an IP prefix (in `/' notation)</li>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<li class="listitem">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont a key ID, as defined by the <span class="command"><strong>key</strong></span>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont statement
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </li>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<li class="listitem">the name of an address match list defined with
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the <span class="command"><strong>acl</strong></span> statement
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </li>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<li class="listitem">a nested address match list enclosed in braces</li>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</ul></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington 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>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews 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
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews be traversed until a matching key is found, and therefore may
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews be somewhat slower.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews The interpretation of a match depends on whether the list is being
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User used for access control, defining <span class="command"><strong>listen-on</strong></span> ports, or in a
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span class="command"><strong>sortlist</strong></span>, and whether the element was negated.
33d1cff1dd63494ffa00fac695a793f00c4ebf0bTinderbox User </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark 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 class="command"><strong>allow-notify</strong></span>,
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <span class="command"><strong>allow-recursion</strong></span>,
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User <span class="command"><strong>allow-recursion-on</strong></span>,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span class="command"><strong>allow-query</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>allow-query-on</strong></span>,
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <span class="command"><strong>allow-query-cache</strong></span>,
bac4435d473c9a0281507524f084480c34aa942aTinderbox User <span class="command"><strong>allow-query-cache-on</strong></span>,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span class="command"><strong>allow-transfer</strong></span>,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span class="command"><strong>allow-update</strong></span>,
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews <span class="command"><strong>allow-update-forwarding</strong></span>,
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews <span class="command"><strong>blackhole</strong></span>, and
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span class="command"><strong>keep-response-order</strong></span> all use address match
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington lists. Similarly, the <span class="command"><strong>listen-on</strong></span> option will cause the
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington server to refuse queries on any of the machine's
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington addresses which do not match the list.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington 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,
b7aab05edae933e169d5f83c653935b17c7f0a8bMark Andrews 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
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User come before the broader element, regardless of whether
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews either is negated. For example, in
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <span class="command"><strong>1.2.3/24; ! 1.2.3.13;</strong></span>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington the 1.2.3.13 element is completely useless because the
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews algorithm will match any lookup for 1.2.3.13 to the 1.2.3/24
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington element. Using <span class="command"><strong>! 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
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington all other 1.2.3.* hosts fall through.
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews</div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<div class="section">
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<div class="titlepage"><div><div><h3 class="title">
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<a name="comment_syntax"></a>Comment Syntax</h3></div></div></div>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington The <acronym class="acronym">BIND</acronym> 9 comment syntax allows for
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington comments to appear
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington anywhere that whitespace may appear in a <acronym class="acronym">BIND</acronym> configuration
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington file. To appeal to programmers of all kinds, they can be written
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington in the C, C++, or shell/perl style.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="section">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<div class="titlepage"><div><div><h4 class="title">
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<a name="id-1.7.4.5.3"></a>Syntax</h4></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<pre class="programlisting">/* This is a <acronym class="acronym">BIND</acronym> comment as in C */</pre>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<pre class="programlisting">// This is a <acronym class="acronym">BIND</acronym> comment as in C++</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
6d114a4c5cddb176ae5199eee154c0273d652ba4Tinderbox User<pre class="programlisting"># This is a <acronym class="acronym">BIND</acronym> comment as in common UNIX shells
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User# and perl</pre>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
0e91f17da8a29086876a88962e0a3482094b6057Evan Hunt </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</div>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<div class="section">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<div class="titlepage"><div><div><h4 class="title">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<a name="id-1.7.4.5.4"></a>Definition and Usage</h4></div></div></div>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews Comments may appear anywhere that whitespace may appear in
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews a <acronym class="acronym">BIND</acronym> configuration file.
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont C-style comments start with the two characters /* (slash,
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont star) and end with */ (star, slash). Because they are completely
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont delimited with these characters, they can be used to comment only
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont a portion of a line or to span multiple lines.
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews C-style comments cannot be nested. For example, the following
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington is not valid because the entire comment ends with the first */:
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</p>
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews<pre class="programlisting">/* This is the start of a comment.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews This is still part of the comment.
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews/* This is an incorrect attempt at nesting a comment. */
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews This is no longer in any comment. */
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews</pre>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington C++-style comments start with the two characters // (slash,
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington slash) and continue to the end of the physical line. They cannot
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington be continued across multiple physical lines; to have one logical
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington comment span multiple lines, each line must use the // pair.
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington For example:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews</p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<pre class="programlisting">// This is the start of a comment. The next line
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews// is a new comment, even though it is logically
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews// part of the previous comment.
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews</pre>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Shell-style (or perl-style, if you prefer) comments start
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont with the character <code class="literal">#</code> (number sign)
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User and continue to the end of the
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews physical line, as in C++ comments.
757ff043760e4743dda1a10e7d58349275934902Tinderbox User For example:
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews</p>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User<pre class="programlisting"># This is the start of a comment. The next line
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews# is a new comment, even though it is logically
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews# part of the previous comment.
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont</pre>
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User<p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont
646fed0d28be4387e3e32fb0f5732a1f58b572baTinderbox User </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark 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
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews to start a comment such as you would in a zone file. The
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews semicolon indicates the end of a configuration
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User statement.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews</div>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</div>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</div>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</div>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="section">
cc5a9ce75af9870f2cb9e2bf00548c2f7e6398d6Automatic Updater<div class="titlepage"><div><div><h2 class="title" style="clear: both">
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<a name="Configuration_File_Grammar"></a>Configuration File Grammar</h2></div></div></div>
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User<p>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User A <acronym class="acronym">BIND</acronym> 9 configuration consists of
ba8b771c371967dd1254c7fa82ebe4158ee04b24Tinderbox User statements and comments.
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User Statements end with a semicolon. Statements and comments are the
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater only elements that can appear without enclosing braces. Many
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater statements contain a block of sub-statements, which are also
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater terminated with a semicolon.
532d27b39244fadfcf8d8b4593f4c65434c9c664Automatic Updater </p>
91faa748a27dee38f6caea461d3e87f15b93abeaTinderbox User<p>
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews The following statements are supported:
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews </p>
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User<div class="informaltable"><table border="1">
f33f2b8afe60de897c53cdcb17911f10b552699fTinderbox User<colgroup>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews<col width="1.336in" class="1">
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews<col width="3.778in" class="2">
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews</colgroup>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<tbody>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<tr>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <p><span class="command"><strong>acl</strong></span></p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<td>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews <p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews defines a named IP address
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User matching list, for access control and other uses.
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User </p>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User </td>
861836e5f5df62bfaea9ad8923a05278d5ab2f3dTinderbox User</tr>
e8c17c74535be290abaaa160a434ed80bf0ad2feMark Andrews<tr>
93089a352d6903b0d7845a039de4ec2df9a0e35aTinderbox User<td>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater <p><span class="command"><strong>controls</strong></span></p>
9c446b72069d0ab9f710502f4d7048e50875fccbAutomatic Updater </td>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater<td>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater <p>
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User declares control channels to be used
933799f3641f4f78445d015008bad0038900a82aTinderbox User by the <span class="command"><strong>rndc</strong></span> utility.
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<tr>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p><span class="command"><strong>include</strong></span></p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>lwres</strong></span></p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater configures <span class="command"><strong>named</strong></span> to
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User also act as a light-weight resolver daemon (<span class="command"><strong>lwresd</strong></span>).
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater </td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater</tr>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<tr>
bbc0e1c4f47f101c4a64db3469352c49a49e734fTinderbox User<td>
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User <p><span class="command"><strong>masters</strong></span></p>
7f9e2fff07b9c17e0d7a0ea7abc9304ce9d01b61Tinderbox User </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater defines a named masters list for
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews inclusion in stub and slave zones'
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews <span class="command"><strong>masters</strong></span> or
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews <span class="command"><strong>also-notify</strong></span> lists.
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews </p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater <p><span class="command"><strong>options</strong></span></p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User<td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater controls global server configuration
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User options and sets defaults for other statements.
4ea3649f028ea6a1e42377082a7ccf8f789fb950Automatic Updater </p>
40072ce70bc4125329addb4aaa56d18a1230bc17Automatic Updater </td>
60d5d17479b47c03b9c7c86f54269718103750b8Automatic Updater</tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<tr>
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User<td>
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User <p><span class="command"><strong>server</strong></span></p>
60d5d17479b47c03b9c7c86f54269718103750b8Automatic Updater </td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater <p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater sets certain configuration options on
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater a per-server basis.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater</tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater <p><span class="command"><strong>statistics-channels</strong></span></p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<td>
19dbf2e20df03f2b81ed1f347e27718084374059Automatic Updater <p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater declares communication channels to get access to
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater <span class="command"><strong>named</strong></span> statistics.
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </p>
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User </td>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater</tr>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater<tr>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater<td>
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater <p><span class="command"><strong>trusted-keys</strong></span></p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews defines trusted DNSSEC keys.
7f9e2fff07b9c17e0d7a0ea7abc9304ce9d01b61Tinderbox User </p>
3e1a17d65ec6227900f388ba2f7561365f7d4f5cTinderbox User </td>
33d1cff1dd63494ffa00fac695a793f00c4ebf0bTinderbox User</tr>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews<tr>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<td>
7dd02af3c9350553e1d52d980a7812425b3f1295Automatic Updater <p><span class="command"><strong>managed-keys</strong></span></p>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews </td>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews<td>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <p>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User lists DNSSEC keys to be kept up to date
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington using RFC 5011 trust anchor maintenance.
d4ef65050feac78554addf6e16a06c6e2e0bd331Brian Wellington </p>
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews </td>
4fe0411487e8e4401477684c0a2bac041ca7c2d5Tinderbox User</tr>
01f91b9cd440833f66e7476e43659655cb52ad10Automatic Updater<tr>
4fe0411487e8e4401477684c0a2bac041ca7c2d5Tinderbox User<td>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <p><span class="command"><strong>view</strong></span></p>
4fe0411487e8e4401477684c0a2bac041ca7c2d5Tinderbox User </td>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews<td>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews defines a view.
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User </p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews </td>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews</tr>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews<tr>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews<td>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <p><span class="command"><strong>zone</strong></span></p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews </td>
f45f40ec2814a5ff1ed443c968772a1b2e25c462Mark Andrews<td>
f45f40ec2814a5ff1ed443c968772a1b2e25c462Mark Andrews <p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User defines a zone.
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </p>
2bd56b2684882faf74a2b29cb0914e6671d8005bTinderbox User </td>
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews</tr>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User</tbody>
169f44b082b340b952e26c0fdb930c102a957752Mark Andrews</table></div>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User<p>
54890cfd30f01bdd33b7fb997f9b89fb084c3438Tinderbox User The <span class="command"><strong>logging</strong></span> and
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews <span class="command"><strong>options</strong></span> statements may only occur once
a8677ecad546c955406b341eb8344ed06768b11eTinderbox User per
11b6b0d74bb8dd6bd1ce0b60ba7f9b66323f06d4Tinderbox User configuration.
11b6b0d74bb8dd6bd1ce0b60ba7f9b66323f06d4Tinderbox User </p>
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews<div class="section">
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews<div class="titlepage"><div><div><h3 class="title">
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<a name="acl_grammar"></a><span class="command"><strong>acl</strong></span> Statement Grammar</h3></div></div></div>
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews<pre class="programlisting"><span class="command"><strong>acl</strong></span> acl-name {
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews address_match_list
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews};
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews</pre>
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews</div>
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews<div class="section">
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews<div class="titlepage"><div><div><h3 class="title">
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews<a name="acl"></a><span class="command"><strong>acl</strong></span> Statement Definition and
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews Usage</h3></div></div></div>
05d81eae94425a5124e07626af4bcc178960bd0eMark Andrews<p>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews The <span class="command"><strong>acl</strong></span> statement assigns a symbolic
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User name to an address match list. It gets its name from a primary
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews use of address match lists: Access Control Lists (ACLs).
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews </p>
789875a1bd6d50c00d3bd883cad17ead1d3c21cdMark Andrews<p>
c0cc232ba92b92c1c5a48d49449ef56f7ca05b56Tinderbox User The following ACLs are built-in:
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User </p>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User<div class="informaltable"><table border="1">
08a1e53c738c425390557196a2ba5039e5afd364Mark Andrews<colgroup>
1efe84be7849c5327001ad7dbad93d92c66c1389Mark Andrews<col width="1.130in" class="1">
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews<col width="4.000in" class="2">
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews</colgroup>
7e8129652903780873ba91f379f9ffca1f59773cMark Andrews<tbody>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<tr>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews<td>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews <p><span class="command"><strong>any</strong></span></p>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews </td>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p>
1efe84be7849c5327001ad7dbad93d92c66c1389Mark Andrews Matches all hosts.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
1efe84be7849c5327001ad7dbad93d92c66c1389Mark Andrews </td>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User</tr>
f6ba5791728d244650c1887d8dd8ed771fd50a1dMark Andrews<tr>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews<td>
95c3a5e116c1da135f669c3f15398172fac6279dMark Andrews <p><span class="command"><strong>none</strong></span></p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </td>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<td>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt <p>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt Matches no hosts.
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt </p>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt </td>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt</tr>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<tr>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt<td>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt <p><span class="command"><strong>localhost</strong></span></p>
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User </td>
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User<td>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt <p>
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt Matches the IPv4 and IPv6 addresses of all network
b123be91958e0bc58a10c165be64d47661199e3bEvan Hunt interfaces on the system. When addresses are
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User added or removed, the <span class="command"><strong>localhost</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater ACL element is updated to reflect the changes.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span class="command"><strong>localnets</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater Matches any host on an IPv4 or IPv6 network
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for which the system has an interface.
9c2cf9e2017e6dd196e3b866808f32c6206eeedcMark Andrews When addresses are added or removed,
9c2cf9e2017e6dd196e3b866808f32c6206eeedcMark Andrews the <span class="command"><strong>localnets</strong></span>
9c2cf9e2017e6dd196e3b866808f32c6206eeedcMark Andrews ACL element is updated to reflect the changes.
9c2cf9e2017e6dd196e3b866808f32c6206eeedcMark Andrews Some systems do not provide a way to determine the prefix
cb40461f8744c5aeb369b84d5f48395a13a221a0Mark Andrews lengths of
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews local IPv6 addresses.
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews In such a case, <span class="command"><strong>localnets</strong></span>
9f8051ea406dc3d98bb205df82cfc4d668a25d6eTinderbox User only matches the local
8f3657636521817d2971ae29aa3fb66e33709753Mark Andrews IPv6 addresses, just like <span class="command"><strong>localhost</strong></span>.
8f3657636521817d2971ae29aa3fb66e33709753Mark Andrews </p>
66458d12f373fb75e8543d36fd76864a7567057bTinderbox User </td>
c19bf21885cdf78b52eee017dc1189a300657995Tinderbox User</tr>
f525041ae26958385b697cf82a30f108577024b6Tinderbox User</tbody>
f525041ae26958385b697cf82a30f108577024b6Tinderbox User</table></div>
be0d1ec971748020cb0382e02b4642b493ea1e7bTinderbox User</div>
be0d1ec971748020cb0382e02b4642b493ea1e7bTinderbox User<div class="section">
f525041ae26958385b697cf82a30f108577024b6Tinderbox User<div class="titlepage"><div><div><h3 class="title">
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<a name="controls_grammar"></a><span class="command"><strong>controls</strong></span> Statement Grammar</h3></div></div></div>
5b56652059e2c22185a0b2bb1f5e58eb89a44426Tinderbox User<pre class="programlisting"><span class="command"><strong>controls</strong></span> {
c78c39caab4cf8b5daefc9c65878f7f5ed3eb7a0Tinderbox User [ inet ( ip_addr | * ) [ port ip_port ]
c78c39caab4cf8b5daefc9c65878f7f5ed3eb7a0Tinderbox User allow { <em class="replaceable"><code> address_match_list </code></em> }
8e86e8a779f37378fdb85a92c4ba77e394013729Tinderbox User [ keys { <em class="replaceable"><code>key_list</code></em> } ]
c19bf21885cdf78b52eee017dc1189a300657995Tinderbox User [ read-only <em class="replaceable"><code>yes_or_no</code></em> ] ; ]
9f8051ea406dc3d98bb205df82cfc4d668a25d6eTinderbox User [ inet ...; ]
f525041ae26958385b697cf82a30f108577024b6Tinderbox User [ 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>
be0d1ec971748020cb0382e02b4642b493ea1e7bTinderbox User [ keys { <em class="replaceable"><code>key_list</code></em> } ]
ff62ab3c2e6274f19190ded15548c723d38bbbe3Automatic Updater [ read-only <em class="replaceable"><code>yes_or_no</code></em> ] ; ]
ee23b913b6acccad68cf5af480b9e289a3d00510Tinderbox User [ unix ...; ]
ee23b913b6acccad68cf5af480b9e289a3d00510Tinderbox User};
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User</pre>
e20309353e6246485c521278131d3fced73d7957Tinderbox User</div>
e20309353e6246485c521278131d3fced73d7957Tinderbox User<div class="section">
ee23b913b6acccad68cf5af480b9e289a3d00510Tinderbox User<div class="titlepage"><div><div><h3 class="title">
ee23b913b6acccad68cf5af480b9e289a3d00510Tinderbox User<a name="controls_statement_definition_and_usage"></a><span class="command"><strong>controls</strong></span> Statement Definition and
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User Usage</h3></div></div></div>
9e8ee4ffd77aa2974cecbdbb2b122156b8d3a27aTinderbox User<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews The <span class="command"><strong>controls</strong></span> statement declares control
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User channels to be used by system administrators to control the
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User operation of the name server. These control channels are
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User used by the <span class="command"><strong>rndc</strong></span> utility to send
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater commands to and retrieve non-DNS results from a name server.
bac4435d473c9a0281507524f084480c34aa942aTinderbox User </p>
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews<p>
21b353c36cb484d022a0df8cb39c602649a46ae6Tinderbox User An <span class="command"><strong>inet</strong></span> control channel is a TCP socket
21b353c36cb484d022a0df8cb39c602649a46ae6Tinderbox User listening at the specified <span class="command"><strong>ip_port</strong></span> on the
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews specified <span class="command"><strong>ip_addr</strong></span>, which can be an IPv4 or IPv6
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews address. An <span class="command"><strong>ip_addr</strong></span> of <code class="literal">*</code> (asterisk) is
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews interpreted as the IPv4 wildcard address; connections will be
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews accepted on any of the system's IPv4 addresses.
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews To listen on the IPv6 wildcard address,
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews use an <span class="command"><strong>ip_addr</strong></span> of <code class="literal">::</code>.
c0cc232ba92b92c1c5a48d49449ef56f7ca05b56Tinderbox User If you will only use <span class="command"><strong>rndc</strong></span> on the local host,
c0cc232ba92b92c1c5a48d49449ef56f7ca05b56Tinderbox User using the loopback address (<code class="literal">127.0.0.1</code>
ce67023ae3ad39a77da5361d0187ab6f3f0219cbMark Andrews or <code class="literal">::1</code>) is recommended for maximum security.
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews If no port is specified, port 953 is used. The asterisk
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews "<code class="literal">*</code>" cannot be used for <span class="command"><strong>ip_port</strong></span>.
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews The ability to issue commands over the control channel is
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews restricted by the <span class="command"><strong>allow</strong></span> and
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <span class="command"><strong>keys</strong></span> clauses.
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews Connections to the control channel are permitted based on the
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews <span class="command"><strong>address_match_list</strong></span>. This is for simple
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews IP address based filtering only; any <span class="command"><strong>key_id</strong></span>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews elements of the <span class="command"><strong>address_match_list</strong></span>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews are ignored.
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews </p>
b30ec46fec40a1b246f7965fbcd341fc6cfd1cc1Mark Andrews<p>
95c3a5e116c1da135f669c3f15398172fac6279dMark Andrews A <span class="command"><strong>unix</strong></span> control channel is a UNIX domain
95c3a5e116c1da135f669c3f15398172fac6279dMark Andrews socket listening at the specified path in the file system.
95c3a5e116c1da135f669c3f15398172fac6279dMark Andrews Access to the socket is specified by the <span class="command"><strong>perm</strong></span>,
95c3a5e116c1da135f669c3f15398172fac6279dMark Andrews <span class="command"><strong>owner</strong></span> and <span class="command"><strong>group</strong></span> clauses.
95c3a5e116c1da135f669c3f15398172fac6279dMark Andrews Note on some platforms (SunOS and Solaris) the permissions
95c3a5e116c1da135f669c3f15398172fac6279dMark Andrews (<span class="command"><strong>perm</strong></span>) are applied to the parent directory
3040b455151b1e1173193933664b2891b6159f24Mark Andrews as the permissions on the socket itself are ignored.
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt </p>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User<p>
d585233c52e283d9a8849f16f04f452419a2484eTinderbox User The primary authorization mechanism of the command
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews channel is the <span class="command"><strong>key_list</strong></span>, which
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User contains a list of <span class="command"><strong>key_id</strong></span>s.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User Each <span class="command"><strong>key_id</strong></span> in the <span class="command"><strong>key_list</strong></span>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User is authorized to execute commands over the control channel.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User See <a class="xref" href="Bv9ARM.ch03.html#rndc">Remote Name Daemon Control application</a> in <a class="xref" href="Bv9ARM.ch03.html#admin_tools" title="Administrative Tools">the section called &#8220;Administrative Tools&#8221;</a>)
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for information about configuring keys in <span class="command"><strong>rndc</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If the <span class="command"><strong>read-only</strong></span> clause is enabled, the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater control channel is limited to the following set of read-only
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater commands: <span class="command"><strong>nta -dump</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>null</strong></span>, <span class="command"><strong>status</strong></span>,
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span class="command"><strong>showzone</strong></span>, <span class="command"><strong>testgen</strong></span>, and
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span class="command"><strong>zonestatus</strong></span>. By default,
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User <span class="command"><strong>read-only</strong></span> is not enabled and the control
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User channel allows read-write access.
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User </p>
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User<p>
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User If no <span class="command"><strong>controls</strong></span> statement is present,
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User <span class="command"><strong>named</strong></span> will set up a default
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User control channel listening on the loopback address 127.0.0.1
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User and its IPv6 counterpart ::1.
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User In this case, and also when the <span class="command"><strong>controls</strong></span> statement
3040b455151b1e1173193933664b2891b6159f24Mark Andrews is present but does not have a <span class="command"><strong>keys</strong></span> clause,
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater <span class="command"><strong>named</strong></span> will attempt to load the command channel key
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater from the file <code class="filename">rndc.key</code> in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="filename">/etc</code> (or whatever <code class="varname">sysconfdir</code>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews was specified as when <acronym class="acronym">BIND</acronym> was built).
88d58d79c5bc7ce3c20a42461a5070116c736836Automatic Updater To create a <code class="filename">rndc.key</code> file, run
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <strong class="userinput"><code>rndc-confgen -a</code></strong>.
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <code class="filename">rndc.key</code> feature was created to
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater ease the transition of systems from <acronym class="acronym">BIND</acronym> 8,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater which did not have digital signatures on its command channel
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater messages and thus did not have a <span class="command"><strong>keys</strong></span> clause.
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater
3040b455151b1e1173193933664b2891b6159f24Mark Andrews It makes it possible to use an existing <acronym class="acronym">BIND</acronym> 8
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater configuration file in <acronym class="acronym">BIND</acronym> 9 unchanged,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and still have <span class="command"><strong>rndc</strong></span> work the same way
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>ndc</strong></span> worked in BIND 8, simply by executing the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater command <strong class="userinput"><code>rndc-confgen -a</code></strong> after BIND 9 is
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User installed.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
48b36fa08b2b5bc0d552dc2a4425b3f7007b3d59Automatic Updater<p>
9fa39c73fc1d8bc44fdbbb79a1d26b837e7dd555Mark Andrews Since the <code class="filename">rndc.key</code> feature
7f814b8b164ae04916a8487cdc5e88ee3ff51a58Automatic Updater is only intended to allow the backward-compatible usage of
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <acronym class="acronym">BIND</acronym> 8 configuration files, this
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt feature does not
3040b455151b1e1173193933664b2891b6159f24Mark Andrews have a high degree of configurability. You cannot easily change
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User the key name or the size of the secret, so you should make a
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <code class="filename">rndc.conf</code> with your own key if you
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater wish to change
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater those things. The <code class="filename">rndc.key</code> file
1959fd489a8832e4e3d311670f64ae18e5d08156Automatic Updater also has its
3040b455151b1e1173193933664b2891b6159f24Mark Andrews permissions set such that only the owner of the file (the user that
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <span class="command"><strong>named</strong></span> is running as) can access it.
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt If you
3040b455151b1e1173193933664b2891b6159f24Mark Andrews desire greater flexibility in allowing other users to access
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <span class="command"><strong>rndc</strong></span> commands, then you need to create
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User a
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews <code class="filename">rndc.conf</code> file and make it group
d2247b4740cc5f740bf7d89ef9ce67fef015c95cMark Andrews readable by a group
d2247b4740cc5f740bf7d89ef9ce67fef015c95cMark Andrews that contains the users who should have access.
d2247b4740cc5f740bf7d89ef9ce67fef015c95cMark Andrews </p>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews<p>
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews To disable the command channel, use an empty
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews <span class="command"><strong>controls</strong></span> statement:
8bc194b266a17f89e6c54469d4dfbb408070f39eMark Andrews <span class="command"><strong>controls { };</strong></span>.
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</div>
d2247b4740cc5f740bf7d89ef9ce67fef015c95cMark Andrews<div class="section">
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<div class="titlepage"><div><div><h3 class="title">
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User<a name="include_grammar"></a><span class="command"><strong>include</strong></span> Statement Grammar</h3></div></div></div>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<pre class="programlisting"><span class="command"><strong>include</strong></span> <em class="replaceable"><code>filename</code></em>;</pre>
1f471f3b06fae27f4b42ee4f0d6dac0cc7e5bc81Tinderbox User</div>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater<div class="section">
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User<div class="titlepage"><div><div><h3 class="title">
8d8f9f7f86a33a155dd74b9b2c1317afca555d54Evan Hunt<a name="include_statement"></a><span class="command"><strong>include</strong></span> Statement Definition and Usage</h3></div></div></div>
8d8f9f7f86a33a155dd74b9b2c1317afca555d54Evan Hunt<p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews The <span class="command"><strong>include</strong></span> statement inserts the
3040b455151b1e1173193933664b2891b6159f24Mark Andrews specified file at the point where the <span class="command"><strong>include</strong></span>
213dd665a9f45c3acb5f6c5f853bbbd5fd1598a2Tinderbox User statement is encountered. The <span class="command"><strong>include</strong></span>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User statement facilitates the administration of configuration
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont files
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont by permitting the reading or writing of some things but not
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont others. For example, the statement could include private keys
4dca64bb8991502db368028aeeba2f832d3b971dAutomatic Updater that are readable only by the name server.
e5bf83fe0bbca838a0749e9071bd76d9ee0fb59bFrancis Dupont </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User</div>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User<div class="section">
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<a name="key_grammar"></a><span class="command"><strong>key</strong></span> Statement Grammar</h3></div></div></div>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<pre class="programlisting"><span class="command"><strong>key</strong></span> <em class="replaceable"><code>key_id</code></em> {
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater algorithm <em class="replaceable"><code>algorithm_id</code></em>;
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater secret <em class="replaceable"><code>secret_string</code></em>;
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater};
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User</pre>
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User</div>
7169f76a893666eb20fc7750782e7f411db742d6Tinderbox User<div class="section">
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<a name="key_statement"></a><span class="command"><strong>key</strong></span> Statement Definition and Usage</h3></div></div></div>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater<p>
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater The <span class="command"><strong>key</strong></span> statement defines a shared
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater secret key for use with TSIG (see <a class="xref" href="Bv9ARM.ch04.html#tsig" title="TSIG">the section called &#8220;TSIG&#8221;</a>)
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User or the command channel
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater (see <a class="xref" href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and Usage">the section called &#8220;<span class="command"><strong>controls</strong></span> Statement Definition and
ead8aa3182c5805fccb6c7c1636cede6a24a5fc1Automatic Updater Usage&#8221;</a>).
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User<p>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User The <span class="command"><strong>key</strong></span> statement can occur at the
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt top level
3040b455151b1e1173193933664b2891b6159f24Mark Andrews of the configuration file or inside a <span class="command"><strong>view</strong></span>
536da846f6cc03ad8abbb8bb9d5d8a6f607b8c33Mark Andrews statement. Keys defined in top-level <span class="command"><strong>key</strong></span>
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater statements can be used in all views. Keys intended for use in
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User a <span class="command"><strong>controls</strong></span> statement
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User (see <a class="xref" href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and Usage">the section called &#8220;<span class="command"><strong>controls</strong></span> Statement Definition and
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Usage&#8221;</a>)
8eb631bc4a219650906a6dc6ca51af3034b6ba54Tinderbox User must be defined at the top level.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater<p>
665ba746c0585088d0c314dcfc4671aa2c7b2dc1Automatic Updater The <em class="replaceable"><code>key_id</code></em>, also known as the
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews key name, is a domain name uniquely identifying the key. It can
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews be used in a <span class="command"><strong>server</strong></span>
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews statement to cause requests sent to that
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews server to be signed with this key, or in address match lists to
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews verify that incoming requests have been signed with a key
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews matching this name, algorithm, and secret.
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater </p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The <em class="replaceable"><code>algorithm_id</code></em> is a string
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater that specifies a security/authentication algorithm. The
7fdbd6fc9df8728852ccaecb2d66241ab96a4084Tinderbox User <span class="command"><strong>named</strong></span> server supports <code class="literal">hmac-md5</code>,
8eb631bc4a219650906a6dc6ca51af3034b6ba54Tinderbox User <code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>,
50fa300826799727204b93cbe63bebc341c5eadeTinderbox User <code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code>
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews and <code class="literal">hmac-sha512</code> TSIG authentication.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Truncated hashes are supported by appending the minimum
2da2220fe7af2c45724b50b0187523b1fab0cf08Rob Austein number of required bits preceded by a dash, e.g.
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews <code class="literal">hmac-sha1-80</code>. The
e171a4137c6ba348957e61b7c4c3541493c0da02Automatic Updater <em class="replaceable"><code>secret_string</code></em> is the secret
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater to be used by the algorithm, and is treated as a base-64
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater encoded string.
7fdbd6fc9df8728852ccaecb2d66241ab96a4084Tinderbox User </p>
e21f41f6504b3381be86cbe7f457f9ee1fff947bTinderbox User</div>
e21f41f6504b3381be86cbe7f457f9ee1fff947bTinderbox User<div class="section">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User<a name="logging_grammar"></a><span class="command"><strong>logging</strong></span> Statement Grammar</h3></div></div></div>
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User<pre class="programlisting"><span class="command"><strong>logging</strong></span> {
22bed5c0fa8aa33ebca97235c0509db335440811Tinderbox User [ <span class="command"><strong>channel</strong></span> <em class="replaceable"><code>channel_name</code></em> {
b3386fba31414344f38f0c30849c056dceb22dceTinderbox User ( <span class="command"><strong>file</strong></span> <em class="replaceable"><code>path_name</code></em>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater [ <span class="command"><strong>versions</strong></span> ( <em class="replaceable"><code>number</code></em> | <span class="command"><strong>unlimited</strong></span> ) ]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [ <span class="command"><strong>size</strong></span> <em class="replaceable"><code>size_spec</code></em> ]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater | <span class="command"><strong>syslog</strong></span> <em class="replaceable"><code>syslog_facility</code></em>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater | <span class="command"><strong>stderr</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater | <span class="command"><strong>null</strong></span> );
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater [ <span class="command"><strong>severity</strong></span> (<code class="option">critical</code> | <code class="option">error</code> | <code class="option">warning</code> | <code class="option">notice</code> |
af9cf290cea6ada6ce27b51c724ab77ad5d73fa0Tinderbox User <code class="option">info</code> | <code class="option">debug</code> [ <em class="replaceable"><code>level</code></em> ] | <code class="option">dynamic</code> ); ]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater [ <span class="command"><strong>print-category</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
7fdbd6fc9df8728852ccaecb2d66241ab96a4084Tinderbox User [ <span class="command"><strong>print-severity</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
6671e343b8c7e44ac10a7900fde59555fbc71571Automatic Updater [ <span class="command"><strong>print-time</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater [ <span class="command"><strong>buffered</strong></span> <code class="option">yes</code> or <code class="option">no</code>; ]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater }; ]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater [ <span class="command"><strong>category</strong></span> <em class="replaceable"><code>category_name</code></em> {
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <em class="replaceable"><code>channel_name</code></em> ; [ <em class="replaceable"><code>channel_name</code></em> ; ... ]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater }; ]
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater ...
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater};
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater</pre>
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User</div>
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater<div class="section">
4104e236f71eb5108fcfda6711878a97f6f4a8e7Automatic Updater<div class="titlepage"><div><div><h3 class="title">
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<a name="logging_statement"></a><span class="command"><strong>logging</strong></span> Statement Definition and Usage</h3></div></div></div>
7fdbd6fc9df8728852ccaecb2d66241ab96a4084Tinderbox User<p>
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater The <span class="command"><strong>logging</strong></span> statement configures a
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater wide
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews variety of logging options for the name server. Its <span class="command"><strong>channel</strong></span> phrase
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews associates output methods, format options and severity levels with
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews a name that can then be used with the <span class="command"><strong>category</strong></span> phrase
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User to select how various classes of messages are logged.
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater </p>
8e9f3b69914ee02a80b87c97b1f8093edb3e9ae0Automatic Updater<p>
664917bedafa65dee4349c84324a31731aa1e228Francis Dupont Only one <span class="command"><strong>logging</strong></span> statement is used to
c53a6f37deaa396660adb6a4ca600c4a58adfd3fAutomatic Updater define
af9cf290cea6ada6ce27b51c724ab77ad5d73fa0Tinderbox User as many channels and categories as are wanted. If there is no <span class="command"><strong>logging</strong></span> statement,
7fdbd6fc9df8728852ccaecb2d66241ab96a4084Tinderbox User the logging configuration will be:
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<pre class="programlisting">logging {
50fa300826799727204b93cbe63bebc341c5eadeTinderbox User category default { default_syslog; default_debug; };
82b96702f09ed6bc5cd0f1aa5e54198c04cc192bTinderbox User category unmatched { null; };
e97ad980e88f16c50e8fcd571a4f51121672e477Tinderbox User};
e97ad980e88f16c50e8fcd571a4f51121672e477Tinderbox User</pre>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <span class="command"><strong>named</strong></span> is started with the
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews <code class="option">-L</code> option, it logs to the specified file
e20309353e6246485c521278131d3fced73d7957Tinderbox User at startup, instead of using syslog. In this case the logging
e20309353e6246485c521278131d3fced73d7957Tinderbox User configuration will be:
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
39cad8fb7d7ff3436bb24ce761354afcb80d295aMark Andrews<pre class="programlisting">logging {
f8a9a38ee40c139a8d145ac76ecbff3a0f986453Mark Andrews category default { default_logfile; default_debug; };
e628576d3b3d91c8954679077f4c208f1e43b433Automatic Updater category unmatched { null; };
39cad8fb7d7ff3436bb24ce761354afcb80d295aMark Andrews};
39cad8fb7d7ff3436bb24ce761354afcb80d295aMark Andrews</pre>
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User<p>
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User In <acronym class="acronym">BIND</acronym> 9, the logging configuration
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User is only established when
9d80d23172c30fd63e5046a7e69b8445e564ff31Automatic Updater the entire configuration file has been parsed. In <acronym class="acronym">BIND</acronym> 8, it was
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User established as soon as the <span class="command"><strong>logging</strong></span>
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt statement
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt was parsed. When the server is starting up, all logging messages
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt regarding syntax errors in the configuration file go to the default
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt channels, or to standard error if the <code class="option">-g</code> option
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt was specified.
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt </p>
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt<div class="section">
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User<div class="titlepage"><div><div><h4 class="title">
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews<a name="channel"></a>The <span class="command"><strong>channel</strong></span> Phrase</h4></div></div></div>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews All log output goes to one or more <span class="emphasis"><em>channels</em></span>;
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews you can make as many of them as you want.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews Every channel definition must include a destination clause that
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews says whether messages selected for the channel go to a file, to a
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews particular syslog facility, to the standard error stream, or are
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews discarded. It can optionally also limit the message severity level
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews that will be accepted by the channel (the default is
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews <span class="command"><strong>info</strong></span>), and whether to include a
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews <span class="command"><strong>named</strong></span>-generated time stamp, the
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews category name
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews and/or severity level (the default is not to include any).
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews<p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews The <span class="command"><strong>null</strong></span> destination clause
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews causes all messages sent to the channel to be discarded;
3040b455151b1e1173193933664b2891b6159f24Mark Andrews in that case, other options for the channel are meaningless.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </p>
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User<p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews The <span class="command"><strong>file</strong></span> destination clause directs
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User the channel
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User to a disk file. It can include limitations
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User both on how large the file is allowed to become, and how many
3040b455151b1e1173193933664b2891b6159f24Mark Andrews versions
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User of the file will be saved each time the file is opened.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </p>
61932ed91732417e05c8c6fd335acf1be896c778Mark Andrews<p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews If you use the <span class="command"><strong>versions</strong></span> log file
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User option, then
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews <span class="command"><strong>named</strong></span> will retain that many backup
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews versions of the file by
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews renaming them when opening. For example, if you choose to keep
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews three old versions
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews of the file <code class="filename">lamers.log</code>, then just
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews before it is opened
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews <code class="filename">lamers.log.1</code> is renamed to
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews <code class="filename">lamers.log.2</code>, <code class="filename">lamers.log.0</code> is renamed
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews to <code class="filename">lamers.log.1</code>, and <code class="filename">lamers.log</code> is
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews renamed to <code class="filename">lamers.log.0</code>.
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews You can say <span class="command"><strong>versions unlimited</strong></span> to
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews not limit
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews the number of versions.
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews If a <span class="command"><strong>size</strong></span> option is associated with
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews the log file,
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews then renaming is only done when the file being opened exceeds the
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews indicated size. No backup versions are kept by default; any
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews existing
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews log file is simply appended.
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews </p>
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews<p>
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews The <span class="command"><strong>size</strong></span> option for files is used
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews to limit log
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews growth. If the file ever exceeds the size, then <span class="command"><strong>named</strong></span> will
3040b455151b1e1173193933664b2891b6159f24Mark Andrews stop writing to the file unless it has a <span class="command"><strong>versions</strong></span> option
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User associated with it. If backup versions are kept, the files are
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User rolled as
3040b455151b1e1173193933664b2891b6159f24Mark Andrews described above and a new one begun. If there is no
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User <span class="command"><strong>versions</strong></span> option, no more data will
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt be written to the log
3040b455151b1e1173193933664b2891b6159f24Mark Andrews until some out-of-band mechanism removes or truncates the log to
0a2ff769ecd0b5a6bda54b62bc1ec5fa6fd198a0Tinderbox User less than the
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User maximum size. The default behavior is not to limit the size of
182bfea3ae9912f6d5e2f4fe3e13737719e06f97Tinderbox User the
182bfea3ae9912f6d5e2f4fe3e13737719e06f97Tinderbox User file.
09ee43766e232bd04066445db114c2703dd02bf8Tinderbox User </p>
af60449fe472b8bea5ad04bf538c777c6b151112Tinderbox User<p>
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews Example usage of the <span class="command"><strong>size</strong></span> and
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews <span class="command"><strong>versions</strong></span> options:
af60449fe472b8bea5ad04bf538c777c6b151112Tinderbox User </p>
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews<pre class="programlisting">channel an_example_channel {
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews file "example.log" versions 3 size 20m;
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews print-time yes;
af60449fe472b8bea5ad04bf538c777c6b151112Tinderbox User print-category yes;
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User};
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User</pre>
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User<p>
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User The <span class="command"><strong>syslog</strong></span> destination clause
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User directs the
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User channel to the system log. Its argument is a
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User syslog facility as described in the <span class="command"><strong>syslog</strong></span> man
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User page. Known facilities are <span class="command"><strong>kern</strong></span>, <span class="command"><strong>user</strong></span>,
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User <span class="command"><strong>mail</strong></span>, <span class="command"><strong>daemon</strong></span>, <span class="command"><strong>auth</strong></span>,
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User <span class="command"><strong>syslog</strong></span>, <span class="command"><strong>lpr</strong></span>, <span class="command"><strong>news</strong></span>,
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User <span class="command"><strong>uucp</strong></span>, <span class="command"><strong>cron</strong></span>, <span class="command"><strong>authpriv</strong></span>,
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User <span class="command"><strong>ftp</strong></span>, <span class="command"><strong>local0</strong></span>, <span class="command"><strong>local1</strong></span>,
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User <span class="command"><strong>local2</strong></span>, <span class="command"><strong>local3</strong></span>, <span class="command"><strong>local4</strong></span>,
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User <span class="command"><strong>local5</strong></span>, <span class="command"><strong>local6</strong></span> and
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User <span class="command"><strong>local7</strong></span>, however not all facilities
3040b455151b1e1173193933664b2891b6159f24Mark Andrews are supported on
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews all operating systems.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews How <span class="command"><strong>syslog</strong></span> will handle messages
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews sent to
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews this facility is described in the <span class="command"><strong>syslog.conf</strong></span> man
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews page. If you have a system which uses a very old version of <span class="command"><strong>syslog</strong></span> that
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews only uses two arguments to the <span class="command"><strong>openlog()</strong></span> function,
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews then this clause is silently ignored.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews On Windows machines syslog messages are directed to the EventViewer.
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews </p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews<p>
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews The <span class="command"><strong>severity</strong></span> clause works like <span class="command"><strong>syslog</strong></span>'s
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews "priorities", except that they can also be used if you are writing
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User straight to a file rather than using <span class="command"><strong>syslog</strong></span>.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User Messages which are not at least of the severity level given will
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User not be selected for the channel; messages of higher severity
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater levels
3040b455151b1e1173193933664b2891b6159f24Mark Andrews will be accepted.
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater </p>
f09f1bf18e3ad40a0e8a6cc3dabf1c11f04992cbMark Andrews<p>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater If you are using <span class="command"><strong>syslog</strong></span>, then the <span class="command"><strong>syslog.conf</strong></span> priorities
48dfee71508886d86fe8fb12f91961b5daf3141dMark Andrews will also determine what eventually passes through. For example,
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User defining a channel facility and severity as <span class="command"><strong>daemon</strong></span> and <span class="command"><strong>debug</strong></span> but
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User only logging <span class="command"><strong>daemon.warning</strong></span> via <span class="command"><strong>syslog.conf</strong></span> will
8c9c79e5fea0cb698026a74821695907c8312a46Mark Andrews cause messages of severity <span class="command"><strong>info</strong></span> and
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User <span class="command"><strong>notice</strong></span> to
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User be dropped. If the situation were reversed, with <span class="command"><strong>named</strong></span> writing
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User messages of only <span class="command"><strong>warning</strong></span> or higher,
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User then <span class="command"><strong>syslogd</strong></span> would
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater print all messages it received from the channel.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater<p>
f09f1bf18e3ad40a0e8a6cc3dabf1c11f04992cbMark Andrews The <span class="command"><strong>stderr</strong></span> destination clause
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater directs the
3040b455151b1e1173193933664b2891b6159f24Mark Andrews channel to the server's standard error stream. This is intended
3040b455151b1e1173193933664b2891b6159f24Mark Andrews for
4c6bae917bec70e1fc4d1b761a9765075af78441Tinderbox User use when the server is running as a foreground process, for
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User example
6025cbbe8408f4b09d53d5ec1e95cb6da97e0a8dTinderbox User when debugging a configuration.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews The server can supply extensive debugging information when
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews it is in debugging mode. If the server's global debug level is
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews greater
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews than zero, then debugging mode will be active. The global debug
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User level is set either by starting the <span class="command"><strong>named</strong></span> server
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington with the <code class="option">-d</code> flag followed by a positive integer,
7cc0a5d21ef046bfd630c4769943d896a7d7472cTinderbox User or by running <span class="command"><strong>rndc trace</strong></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The global debug level
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington can be set to zero, and debugging mode turned off, by running <span class="command"><strong>rndc
169f44b082b340b952e26c0fdb930c102a957752Mark Andrewsnotrace</strong></span>. All debugging messages in the server have a debug
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater level, and higher debug levels give more detailed output. Channels
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater that specify a specific debug severity, for example:
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
169f44b082b340b952e26c0fdb930c102a957752Mark Andrews<pre class="programlisting">channel specific_debug_level {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater file "foo";
e007e3e5b0316c6c05698a71101885743aca22bdAutomatic Updater severity debug 3;
e007e3e5b0316c6c05698a71101885743aca22bdAutomatic Updater};
169f44b082b340b952e26c0fdb930c102a957752Mark Andrews</pre>
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews will get debugging output of level 3 or less any time the
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User server is in debugging mode, regardless of the global debugging
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User level. Channels with <span class="command"><strong>dynamic</strong></span>
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews severity use the
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews server's global debug level to determine what messages to print.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews If <span class="command"><strong>print-time</strong></span> has been turned on,
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews then
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews the date and time will be logged. <span class="command"><strong>print-time</strong></span> may
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews be specified for a <span class="command"><strong>syslog</strong></span> channel,
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews but is usually
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews pointless since <span class="command"><strong>syslog</strong></span> also logs
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews the date and
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews time. If <span class="command"><strong>print-category</strong></span> is
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews requested, then the
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews category of the message will be logged as well. Finally, if <span class="command"><strong>print-severity</strong></span> is
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews on, then the severity level of the message will be logged. The <span class="command"><strong>print-</strong></span> options may
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews be used in any combination, and will always be printed in the
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews following
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews order: time, category, severity. Here is an example where all
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews three <span class="command"><strong>print-</strong></span> options
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews are on:
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
3a26bfc09c833a8dc4d4c12b7cd271ed6d0843cbTinderbox User <code class="computeroutput">28-Feb-2000 15:05:32.863 general: notice: running</code>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<p>
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews If <span class="command"><strong>buffered</strong></span> has been turned on the output
180319f572fb6c1ca7000d22ea79a8dd77ae3f91Evan Hunt to files will not be flushed after each log entry. By default
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews all log messages are flushed.
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews </p>
7019b0441a234153dde155622c405960b0d35946Tinderbox User<p>
180319f572fb6c1ca7000d22ea79a8dd77ae3f91Evan Hunt There are four predefined channels that are used for
2a3eef7f65270e3f9a954573d866b368b7857584Tinderbox User <span class="command"><strong>named</strong></span>'s default logging as follows.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews If <span class="command"><strong>named</strong></span> is started with the
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews <code class="option">-L</code> then a
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews fifth channel <span class="command"><strong>default_logfile</strong></span> is added.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews How they are
2a3eef7f65270e3f9a954573d866b368b7857584Tinderbox User used is described in <a class="xref" href="Bv9ARM.ch06.html#the_category_phrase" title="The category Phrase">the section called &#8220;The <span class="command"><strong>category</strong></span> Phrase&#8221;</a>.
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews </p>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews<pre class="programlisting">channel default_syslog {
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews // send to syslog's daemon facility
0bb05fe2c2fa40c635ddc5fa38ff65e523b11d8eEvan Hunt syslog daemon;
95de440e8d2b07bb130505b4146059e5734e2eeaTinderbox User // only send priority info and higher
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User severity info;
0bb05fe2c2fa40c635ddc5fa38ff65e523b11d8eEvan Hunt
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox Userchannel default_debug {
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington // write to named.run in the working directory
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington // Note: stderr is used instead of "named.run" if
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater // the server is started with the '-g' option.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater file "named.run";
bbf7c3fd96ae5e02cb84743c581862e35327032aAutomatic Updater // log at the server's current debug level
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater severity dynamic;
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater};
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox Userchannel default_stderr {
fa0326cc2cf428f67575b6ba3b97b528a31b0010Tinderbox User // writes to stderr
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington stderr;
7adcb4de92bf4383a4c5624c4ed256736d02bc6dMark Andrews // only send priority info and higher
3040b455151b1e1173193933664b2891b6159f24Mark Andrews severity info;
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater};
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater
3040b455151b1e1173193933664b2891b6159f24Mark Andrewschannel null {
95cfad51a3f71246d263af79a7861a6821f7a0beAutomatic Updater // toss anything sent to this channel
61932ed91732417e05c8c6fd335acf1be896c778Mark Andrews null;
3040b455151b1e1173193933664b2891b6159f24Mark Andrews};
e80c7005e3d59dfeb04dad186d36f3c15622954cTinderbox User
e135e3c4b1f4f986f00997f5ad5866effb203139Tinderbox Userchannel default_logfile {
bec9d04b657e1582d2531bdc02503bebde2aa978Tinderbox User // this channel is only present if named is
0e91f17da8a29086876a88962e0a3482094b6057Evan Hunt // started with the -L option, whose argument
28e0061dbcc2ae45d34541267a00d8b4de5b4a41Tinderbox User // provides the file name
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater file "...";
99c231a3bd27893583204cd0a3e3103dc78dbc28Tinderbox User // log at the server's current debug level
3040b455151b1e1173193933664b2891b6159f24Mark Andrews severity dynamic;
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater};
11b6b0d74bb8dd6bd1ce0b60ba7f9b66323f06d4Tinderbox User</pre>
08d53af7d51409036462fa80fb1bde7a8c2ac123Automatic Updater<p>
08d53af7d51409036462fa80fb1bde7a8c2ac123Automatic Updater The <span class="command"><strong>default_debug</strong></span> channel has the
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater special
ec7751119a08c6a7250f3187beed69a8b836d349Tinderbox User property that it only produces output when the server's debug
28e0061dbcc2ae45d34541267a00d8b4de5b4a41Tinderbox User level is
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews nonzero. It normally writes to a file called <code class="filename">named.run</code>
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater in the server's working directory.
5ecad47f69b3fd945472ab2900a9ff826a7ce2f6Automatic Updater </p>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews<p>
07d9d0dbcc0c79deb3c34f4a8af05ac68a6800e4Mark Andrews For security reasons, when the <code class="option">-u</code>
a66012b52c20200f118781463db4e4ee44454298Automatic Updater command line option is used, the <code class="filename">named.run</code> file
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt is created only after <span class="command"><strong>named</strong></span> has
3040b455151b1e1173193933664b2891b6159f24Mark Andrews changed to the
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews new UID, and any debug output generated while <span class="command"><strong>named</strong></span> is
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater starting up and still running as root is discarded. If you need
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User to capture this output, you must run the server with the <code class="option">-L</code>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User option to specify a default logfile, or the <code class="option">-g</code>
e135e3c4b1f4f986f00997f5ad5866effb203139Tinderbox User option to log to standard error which you can redirect to a file.
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater </p>
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater<p>
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater Once a channel is defined, it cannot be redefined. Thus you
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User cannot alter the built-in channels directly, but you can modify
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater the default logging by pointing categories at channels you have
2fd1e3918971180155c10d09454a277f015daecaAutomatic Updater defined.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</div>
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User<div class="section">
18920d790825d96ca3943aa2dcb6eb80dc611c5fTinderbox User<div class="titlepage"><div><div><h4 class="title">
fdd0516065be2316409d0cc7dfb4e4f54eadc5afMark Andrews<a name="the_category_phrase"></a>The <span class="command"><strong>category</strong></span> Phrase</h4></div></div></div>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User<p>
f0877b0237674d0519006ca7f8436e5f92250d30Mark Andrews There are many categories, so you can send the logs you want
f0877b0237674d0519006ca7f8436e5f92250d30Mark Andrews to see wherever you want, without seeing logs you don't want. If
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User you don't specify a list of channels for a category, then log
f0877b0237674d0519006ca7f8436e5f92250d30Mark Andrews messages
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User in that category will be sent to the <span class="command"><strong>default</strong></span> category
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User instead. If you don't specify a default category, the following
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User "default default" is used:
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User </p>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User<pre class="programlisting">category default { default_syslog; default_debug; };
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User</pre>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User<p>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User If you start <span class="command"><strong>named</strong></span> with the
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User <code class="option">-L</code> option then the default category is:
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User </p>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User<pre class="programlisting">category default { default_logfile; default_debug; };
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User</pre>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User<p>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User As an example, let's say you want to log security events to
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User a file, but you also want keep the default logging behavior. You'd
fdd0516065be2316409d0cc7dfb4e4f54eadc5afMark Andrews specify the following:
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User </p>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User<pre class="programlisting">channel my_security_channel {
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User file "my_security_file";
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User severity info;
fdd0516065be2316409d0cc7dfb4e4f54eadc5afMark Andrews};
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox Usercategory security {
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User my_security_channel;
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User default_syslog;
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User default_debug;
f0877b0237674d0519006ca7f8436e5f92250d30Mark Andrews};</pre>
287a6a8f9040dc43560cd69cddf83bfc0f53b76fTinderbox User<p>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User To discard all messages in a category, specify the <span class="command"><strong>null</strong></span> channel:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<pre class="programlisting">category xfer-out { null; };
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellingtoncategory notify { null; };
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington</pre>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Following are the available categories and brief descriptions
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater of the types of log information they contain. More
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater categories may be added in future <acronym class="acronym">BIND</acronym> releases.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User<div class="informaltable"><table border="1">
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<colgroup>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<col width="1.150in" class="1">
e21f41f6504b3381be86cbe7f457f9ee1fff947bTinderbox User<col width="3.350in" class="2">
c2abd6efeb9affa70aabb63da2acb23e135cf7f2Mark Andrews</colgroup>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<tbody>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User<tr>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<td>
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User <p><span class="command"><strong>client</strong></span></p>
c2abd6efeb9affa70aabb63da2acb23e135cf7f2Mark Andrews </td>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<td>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Processing of client requests.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
e062b72f783cdb436a1a57a630bdff471dbb3038Mark Andrews<tr>
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span class="command"><strong>cname</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
d145b64cacc8d9cda51f9924ec70cd4661c3e2cfAutomatic Updater <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Logs nameservers that are skipped due to them being
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User a CNAME rather than A / AAAA records.
4ba21f60009e18c5950d18546a127e70be537effMark Andrews </p>
c855e7170a7ddb5d4ebab69a771f35dc93e95e43Mark Andrews </td>
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews</tr>
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><span class="command"><strong>config</strong></span></p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater <p>
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater Configuration file parsing and processing.
c855e7170a7ddb5d4ebab69a771f35dc93e95e43Mark Andrews </p>
c855e7170a7ddb5d4ebab69a771f35dc93e95e43Mark Andrews </td>
c855e7170a7ddb5d4ebab69a771f35dc93e95e43Mark Andrews</tr>
c855e7170a7ddb5d4ebab69a771f35dc93e95e43Mark Andrews<tr>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p><span class="command"><strong>database</strong></span></p>
7fdbd6fc9df8728852ccaecb2d66241ab96a4084Tinderbox User </td>
52cfbde0bd391cfb37e3c1a1b460c16ba6bf1a73Automatic Updater<td>
4fda24d843edac463c98785ec0c850d912592dc1Tinderbox User <p>
5f7586ddbd3edd11272cdd30ed613d936129328bTinderbox User Messages relating to the databases used
24e0e8d17df315d5d494ca933874e545eadce773Automatic Updater internally by the name server to store zone and cache
4fda24d843edac463c98785ec0c850d912592dc1Tinderbox User data.
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews </p>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</tr>
4fda24d843edac463c98785ec0c850d912592dc1Tinderbox User<tr>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p><span class="command"><strong>default</strong></span></p>
31a540386a9abaf681d8952f1b2cdf5c75a0ba6cAutomatic Updater </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews The default category defines the logging
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User options for those categories where no specific
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User configuration has been
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User defined.
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User </p>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User </td>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User</tr>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User<tr>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User<td>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User <p><span class="command"><strong>delegation-only</strong></span></p>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User </td>
3b9123da1962e9e8240b4d99463d8dcd131b79bdTinderbox User<td>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User <p>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User Delegation only. Logs queries that have been
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User forced to NXDOMAIN as the result of a
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User delegation-only zone or a
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User <span class="command"><strong>delegation-only</strong></span> in a
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User forward, hint or stub zone declaration.
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User </p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<td>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater <p><span class="command"><strong>dispatch</strong></span></p>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater </td>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<td>
11b6b0d74bb8dd6bd1ce0b60ba7f9b66323f06d4Tinderbox User <p>
11b6b0d74bb8dd6bd1ce0b60ba7f9b66323f06d4Tinderbox User Dispatching of incoming packets to the
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater server modules where they are to be processed.
b577ce9ed2153db6539fb975b4a7aa16d9b3baeeTinderbox User </p>
b577ce9ed2153db6539fb975b4a7aa16d9b3baeeTinderbox User </td>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User</tr>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<tr>
b577ce9ed2153db6539fb975b4a7aa16d9b3baeeTinderbox User<td>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User <p><span class="command"><strong>dnssec</strong></span></p>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User </td>
ac2ad7b4e4e41e7e788dbe103c581f1605209d3bTinderbox User<td>
ac2ad7b4e4e41e7e788dbe103c581f1605209d3bTinderbox User <p>
ac2ad7b4e4e41e7e788dbe103c581f1605209d3bTinderbox User DNSSEC and TSIG protocol processing.
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User </p>
12ee3c02ab36d7e7430bd705cc289db1a69a5733Mark Andrews </td>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater</tr>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<tr>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater<td>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater <p><span class="command"><strong>dnstap</strong></span></p>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews </td>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews<td>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews <p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews The "dnstap" DNS traffic capture system.
8ccd7da886e93cd490fcb6f4c4e98a6514f35820Automatic Updater </p>
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater </td>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews</tr>
cd839f5cf5f84cf163f55ff05cb88ce37efd24d1Automatic Updater<tr>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<td>
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User <p><span class="command"><strong>edns-disabled</strong></span></p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </td>
735e1ed9685077e25f744d692acf77c5bf5d4490Tinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
d642d3857129678797a01adee14fbd70335b05a9Mark Andrews Log queries that have been forced to use plain
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews DNS due to timeouts. This is often due to
fd8fb4df8499e292daeac765f599ac7c507d9ca3Mark Andrews the remote servers not being RFC 1034 compliant
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User (not always returning FORMERR or similar to
3040b455151b1e1173193933664b2891b6159f24Mark Andrews EDNS queries and other extensions to the DNS
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater when they are not understood). In other words, this is
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater targeted at servers that fail to respond to
3040b455151b1e1173193933664b2891b6159f24Mark Andrews DNS queries that they don't understand.
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater </p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater <p>
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater Note: the log message can also be due to
f9119ad8f6114b2255e7545bf5cd187f4db0a89bAutomatic Updater packet loss. Before reporting servers for
3040b455151b1e1173193933664b2891b6159f24Mark Andrews non-RFC 1034 compliance they should be re-tested
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater to determine the nature of the non-compliance.
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater This testing should prevent or reduce the
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater number of false-positive reports.
c95f536d78842fbc8ebcef653d88e1f2270054f8Automatic Updater </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews Note: eventually <span class="command"><strong>named</strong></span> will have to stop
cb40461f8744c5aeb369b84d5f48395a13a221a0Mark Andrews treating such timeouts as due to RFC 1034 non
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User compliance and start treating it as plain
bac4435d473c9a0281507524f084480c34aa942aTinderbox User packet loss. Falsely classifying packet
bac4435d473c9a0281507524f084480c34aa942aTinderbox User loss as due to RFC 1034 non compliance impacts
bac4435d473c9a0281507524f084480c34aa942aTinderbox User on DNSSEC validation which requires EDNS for
bac4435d473c9a0281507524f084480c34aa942aTinderbox User the DNSSEC records to be returned.
bac4435d473c9a0281507524f084480c34aa942aTinderbox User </p>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User </td>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User</tr>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User<tr>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User<td>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User <p><span class="command"><strong>general</strong></span></p>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User </td>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User<td>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <p>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User The catch-all. Many things still aren't
bac4435d473c9a0281507524f084480c34aa942aTinderbox User classified into categories, and they all end up here.
bac4435d473c9a0281507524f084480c34aa942aTinderbox User </p>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User </td>
ec8755f605d7dcb2de1076040e77bc2d7ec33b4aTinderbox User</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
45c349c278fd83acd4dcb91eec3482401a623e47Automatic Updater<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p><span class="command"><strong>lame-servers</strong></span></p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p>
bf8c3776f1bf1a1270e5e0443ae5a8df022632a8Mark Andrews Lame servers. These are misconfigurations
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews in remote servers, discovered by BIND 9 when trying to
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews query those servers during resolution.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<tr>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <p><span class="command"><strong>network</strong></span></p>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User </td>
28e0061dbcc2ae45d34541267a00d8b4de5b4a41Tinderbox User<td>
9692d283bb43c9eab49a7fadfc1b74a6e20e6151Tinderbox User <p>
9692d283bb43c9eab49a7fadfc1b74a6e20e6151Tinderbox User Network operations.
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User </p>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User </td>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User</tr>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User<tr>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User<td>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User <p><span class="command"><strong>notify</strong></span></p>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User </td>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User<td>
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User <p>
3a28155fe228cd6d59b15f1ca0b568be6620a9d2Tinderbox User The NOTIFY protocol.
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User </p>
28e0061dbcc2ae45d34541267a00d8b4de5b4a41Tinderbox User </td>
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User</tr>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<tr>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <p><span class="command"><strong>queries</strong></span></p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Specify where queries should be logged to.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater At startup, specifying the category <span class="command"><strong>queries</strong></span> will also
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater enable query logging unless <span class="command"><strong>querylog</strong></span> option has been
3040b455151b1e1173193933664b2891b6159f24Mark Andrews specified.
560d6da48f066000541dd43f5d407644dee12bebTinderbox User </p>
560d6da48f066000541dd43f5d407644dee12bebTinderbox User
9bc394fffdd50f6e47614b2d317da7274122366fTinderbox User <p>
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User The query log entry reports the client's IP
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User address and port number, and the query name,
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User class and type. Next it reports whether the
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User Recursion Desired flag was set (+ if set, -
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User if not set), if the query was signed (S),
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User EDNS was in used along with the EDNS version
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User number (E(#)), if TCP was used (T), if DO
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User (DNSSEC Ok) was set (D), if CD (Checking
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt Disabled) was set (C), if a valid DNS Server
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User COOKIE was received (V), or if a DNS COOKIE
c218e22e3e6cbd409b61a14f1480b5ce5c70bfc1Tinderbox User option without a valid Server COOKIE was
2c1632c71e2f4d8afa35efce3080b31602a6608cTinderbox User present (K). After this the destination
1f471f3b06fae27f4b42ee4f0d6dac0cc7e5bc81Tinderbox User address the query was sent to is reported.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User <p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <code class="computeroutput">client 127.0.0.1#62536 (www.example.com): query: www.example.com IN AAAA +SE</code>
1efe84be7849c5327001ad7dbad93d92c66c1389Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p>
e0bf4fc289705375be65c05a8fb085d514a98c97Tinderbox User <code class="computeroutput">client ::1#62537 (www.example.net): query: www.example.net IN AAAA -SE</code>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater </p>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater <p>
3a28155fe228cd6d59b15f1ca0b568be6620a9d2Tinderbox User (The first part of this log message, showing the
a6e1f63f50af688610ebd2521ba7f028767b51f3Mark Andrews client address/port number and query name, is
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User repeated in all subsequent log messages related
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User to the same query.)
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User </p>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater </td>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater</tr>
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User<tr>
2cdbfcdad94eba75f3f8e77343a0eefabf553b8eAutomatic Updater<td>
e0bf4fc289705375be65c05a8fb085d514a98c97Tinderbox User <p><span class="command"><strong>query-errors</strong></span></p>
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User </td>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater Information about queries that resulted in some
3a28155fe228cd6d59b15f1ca0b568be6620a9d2Tinderbox User failure.
2c1632c71e2f4d8afa35efce3080b31602a6608cTinderbox User </p>
2c1632c71e2f4d8afa35efce3080b31602a6608cTinderbox User </td>
4d813066e967a36c407ee641155ada0c614d4dc6Automatic Updater</tr>
c849f7acb025c73f56a8e28902a473f2aeaba39fTinderbox User<tr>
2c1632c71e2f4d8afa35efce3080b31602a6608cTinderbox User<td>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews <p><span class="command"><strong>rate-limit</strong></span></p>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User </td>
d7d105151a78d35afb4233d2a6dbd47b7ec0d9a5Tinderbox User<td>
44e3b272904bfd85556771d30cf1bc6fa539dd03Automatic Updater <p>
f42fc714eda962112e45b904d1f846c61a080114Automatic Updater The start, periodic, and final notices of the
3040b455151b1e1173193933664b2891b6159f24Mark Andrews rate limiting of a stream of responses are logged at
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <span class="command"><strong>info</strong></span> severity in this category.
cb40461f8744c5aeb369b84d5f48395a13a221a0Mark Andrews These messages include a hash value of the domain name
7c112f7d8f632412901d9f3c4445eb0db6db95feTinderbox User of the response and the name itself,
850cfa4e86da9f63c1b97ec8c743c091ffd3546bFrancis Dupont except when there is insufficient memory to record
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User the name for the final notice
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont The final notice is normally delayed until about one
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews minute after rate limit stops.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User A lack of memory can hurry the final notice,
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User in which case it starts with an asterisk (*).
862cad747c24bc3e608f31cde1d7eddb2409a316Tinderbox User Various internal events are logged at debug 1 level
5ec43255341c8ae12eac2ff340d6c378d9aca7ccTinderbox User and higher.
862cad747c24bc3e608f31cde1d7eddb2409a316Tinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p>
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User Rate limiting of individual requests
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User is logged in the <span class="command"><strong>query-errors</strong></span> category.
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews</tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User <p><span class="command"><strong>resolver</strong></span></p>
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User </td>
e8e87ede5c36b95806c77bcd34894ad9c4b39a78Tinderbox User<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews DNS resolution, such as the recursive
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews lookups performed on behalf of clients by a caching name
2706fce75f04398595d9648122c6b67164e94fccTinderbox User server.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews</tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p><span class="command"><strong>rpz</strong></span></p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
eac5382be368b43df62e4ac32075131fb4997f03Tinderbox User<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews Information about errors in response policy zone files,
eac5382be368b43df62e4ac32075131fb4997f03Tinderbox User rewritten responses, and at the highest
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <span class="command"><strong>debug</strong></span> levels, mere rewriting
536da846f6cc03ad8abbb8bb9d5d8a6f607b8c33Mark Andrews attempts.
536da846f6cc03ad8abbb8bb9d5d8a6f607b8c33Mark Andrews </p>
ac5ed748602c890d596bed07b0b23b8b5f42b2f6Mark Andrews </td>
ac5ed748602c890d596bed07b0b23b8b5f42b2f6Mark Andrews</tr>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt<tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p><span class="command"><strong>security</strong></span></p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews Approval and denial of requests.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews</tr>
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews<tr>
2706fce75f04398595d9648122c6b67164e94fccTinderbox User<td>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews <p><span class="command"><strong>spill</strong></span></p>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews </td>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews<td>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews <p>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews Logs queries that have been terminated, either by dropping
cb40461f8744c5aeb369b84d5f48395a13a221a0Mark Andrews or responding with SERVFAIL, as a result of a fetchlimit
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews quota being exceeded.
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews </p>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews </td>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews</tr>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews<tr>
0d13a9584b9f97693ab22d54322f1c484d578701Mark Andrews<td>
0d13a9584b9f97693ab22d54322f1c484d578701Mark Andrews <p><span class="command"><strong>unmatched</strong></span></p>
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews </td>
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews<td>
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews <p>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews Messages that <span class="command"><strong>named</strong></span> was unable to determine the
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews class of or for which there was no matching <span class="command"><strong>view</strong></span>.
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews A one line summary is also logged to the <span class="command"><strong>client</strong></span> category.
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews This category is best sent to a file or stderr, by
0d13a9584b9f97693ab22d54322f1c484d578701Mark Andrews default it is sent to
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews the <span class="command"><strong>null</strong></span> channel.
cb40461f8744c5aeb369b84d5f48395a13a221a0Mark Andrews </p>
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews </td>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews</tr>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews<tr>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews<td>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews <p><span class="command"><strong>update</strong></span></p>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews </td>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews<td>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews <p>
d56349eff4a1ebb8f4370df5a8a507f1a8ecd0dfMark Andrews Dynamic updates.
015f044f7f916eb18d053f2e5dcbee481425bc66Mark Andrews </p>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews </td>
015f044f7f916eb18d053f2e5dcbee481425bc66Mark Andrews</tr>
6284b9b877d2205240dce1cf7f88d4dca888e44aTinderbox User<tr>
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User<td>
bec9d04b657e1582d2531bdc02503bebde2aa978Tinderbox User <p><span class="command"><strong>update-security</strong></span></p>
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt </td>
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews Approval and denial of update requests.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews</tr>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<tr>
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt<td>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews <p><span class="command"><strong>xfer-in</strong></span></p>
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt </td>
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt<td>
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt <p>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews Zone transfers the server is receiving.
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt </p>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews </td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</tr>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<tr>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <p><span class="command"><strong>xfer-out</strong></span></p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews <p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews Zone transfers the server is sending.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </td>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</tr>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</tbody>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</table></div>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews</div>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<div class="section">
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<div class="titlepage"><div><div><h4 class="title">
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<a name="query_errors"></a>The <span class="command"><strong>query-errors</strong></span> Category</h4></div></div></div>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews<p>
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews The <span class="command"><strong>query-errors</strong></span> category is
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews specifically intended for debugging purposes: To identify
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews why and how specific queries result in responses which
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews indicate an error.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews Messages of this category are therefore only logged
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews with <span class="command"><strong>debug</strong></span> levels.
7e1a8f402e3881388db37152f71c698cb1f1c426Mark Andrews </p>
bbd726b86a5b0f97a192b6027958dc7b763dc48bTinderbox User<p>
7a2a1b8b14fc804ac80612d7b98064095e445be5Automatic Updater At the debug levels of 1 or higher, each response with the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater rcode of SERVFAIL is logged as follows:
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater </p>
c19bf21885cdf78b52eee017dc1189a300657995Tinderbox User<p>
213dd665a9f45c3acb5f6c5f853bbbd5fd1598a2Tinderbox User <code class="computeroutput">client 127.0.0.1#61502: query failed (SERVFAIL) for www.example.com/IN/AAAA at query.c:3880</code>
3a988722ad9e209ba4064604d482dc4efe0e19ebTinderbox User </p>
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews<p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont This means an error resulting in SERVFAIL was
3040b455151b1e1173193933664b2891b6159f24Mark Andrews detected at line 3880 of source file
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews <code class="filename">query.c</code>.
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews Log messages of this level will particularly
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews help identify the cause of SERVFAIL for an
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews authoritative server.
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews At the debug levels of 2 or higher, detailed context
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews information of recursive resolutions that resulted in
3040b455151b1e1173193933664b2891b6159f24Mark Andrews SERVFAIL is logged.
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews The log message will look like as follows:
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews<pre class="programlisting">
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrewsfetch completed at resolver.c:2970 for www.example.com/A
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrewsin 30.000183: timed out/success [domain:example.com,
3040b455151b1e1173193933664b2891b6159f24Mark Andrewsreferral:2,restart:7,qrysent:8,timeout:5,lame:0,neterr:0,
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrewsbadresp:1,adberr:0,findfail:0,valfail:0]
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </pre>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<p>
351eca011cf38fd3272b325029afce144a9a1ebaMark Andrews </p>
31de528a5f7fae26452f6f68625702c4e4d10af9Tinderbox User<p>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User The first part before the colon shows that a recursive
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews resolution for AAAA records of www.example.com completed
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews in 30.000183 seconds and the final result that led to the
4ba21f60009e18c5950d18546a127e70be537effMark Andrews SERVFAIL was determined at line 2970 of source file
4ba21f60009e18c5950d18546a127e70be537effMark Andrews <code class="filename">resolver.c</code>.
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews </p>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews<p>
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews The following part shows the detected final result and the
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews latest result of DNSSEC validation.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User The latter is always success when no validation attempt
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User is made.
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews In this example, this query resulted in SERVFAIL probably
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User because all name servers are down or unreachable, leading
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews to a timeout in 30 seconds.
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews DNSSEC validation was probably not attempted.
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews </p>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews<p>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews The last part enclosed in square brackets shows statistics
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews information collected for this particular resolution
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews attempt.
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews The <code class="varname">domain</code> field shows the deepest zone
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews that the resolver reached;
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews it is the zone where the error was finally detected.
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews The meaning of the other fields is summarized in the
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater following table.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
ff8ec39ce4afc2d774ce99f2386474d2c8539cd4Automatic Updater<div class="informaltable"><table border="1">
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<colgroup>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<col width="1.150in" class="1">
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<col width="3.350in" class="2">
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User</colgroup>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tbody>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><code class="varname">referral</code></p>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews </td>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User<td>
9a5217f827ac0e006016745e5305b31dc0c7767fTinderbox User <p>
9c2cf9e2017e6dd196e3b866808f32c6206eeedcMark Andrews The number of referrals the resolver received
ba8b771c371967dd1254c7fa82ebe4158ee04b24Tinderbox User throughout the resolution process.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User In the above example this is 2, which are most
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews likely com and example.com.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater</tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p><code class="varname">restart</code></p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater The number of cycles that the resolver tried
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater remote servers at the <code class="varname">domain</code>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater zone.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater In each cycle the resolver sends one query
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater (possibly resending it, depending on the response)
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater to each known name server of
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater the <code class="varname">domain</code> zone.
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater</tr>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews<tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<td>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <p><code class="varname">qrysent</code></p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews </td>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews<td>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater The number of queries the resolver sent at the
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater <code class="varname">domain</code> zone.
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </p>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</tr>
8aa53dcb1d26277e8e805464bfff7bb7136f60cbAutomatic Updater<tr>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt<td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <p><code class="varname">timeout</code></p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews </td>
59602f2a7c4e4809941583bed3e94cd26e628f1aTinderbox User<td>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews <p>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User The number of timeouts since the resolver
4c6bae917bec70e1fc4d1b761a9765075af78441Tinderbox User received the last response.
4c6bae917bec70e1fc4d1b761a9765075af78441Tinderbox User </p>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User </td>
4c6bae917bec70e1fc4d1b761a9765075af78441Tinderbox User</tr>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User<tr>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User<td>
3d015b2a0aeaa8d763fc783c23f895125ca1e0b8Tinderbox User <p><code class="varname">lame</code></p>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User </td>
3d015b2a0aeaa8d763fc783c23f895125ca1e0b8Tinderbox User<td>
1368e4b34cef64604c874fcc40201c78e548714cTinderbox User <p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews The number of lame servers the resolver detected
4c6bae917bec70e1fc4d1b761a9765075af78441Tinderbox User at the <code class="varname">domain</code> zone.
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews A server is detected to be lame either by an
70d987def5a58ebeb8243017c0ec2e9b2c326cf4Evan Hunt invalid response or as a result of lookup in
3d015b2a0aeaa8d763fc783c23f895125ca1e0b8Tinderbox User BIND9's address database (ADB), where lame
70d987def5a58ebeb8243017c0ec2e9b2c326cf4Evan Hunt servers are cached.
70d987def5a58ebeb8243017c0ec2e9b2c326cf4Evan Hunt </p>
70d987def5a58ebeb8243017c0ec2e9b2c326cf4Evan Hunt </td>
3d015b2a0aeaa8d763fc783c23f895125ca1e0b8Tinderbox User</tr>
3d015b2a0aeaa8d763fc783c23f895125ca1e0b8Tinderbox User<tr>
1bf507ca635310b340aea42d6c3e567819974a99Tinderbox User<td>
3d015b2a0aeaa8d763fc783c23f895125ca1e0b8Tinderbox User <p><code class="varname">neterr</code></p>
3d015b2a0aeaa8d763fc783c23f895125ca1e0b8Tinderbox User </td>
70d987def5a58ebeb8243017c0ec2e9b2c326cf4Evan Hunt<td>
70d987def5a58ebeb8243017c0ec2e9b2c326cf4Evan Hunt <p>
70d987def5a58ebeb8243017c0ec2e9b2c326cf4Evan Hunt The number of erroneous results that the
2706fce75f04398595d9648122c6b67164e94fccTinderbox User resolver encountered in sending queries
2706fce75f04398595d9648122c6b67164e94fccTinderbox User at the <code class="varname">domain</code> zone.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User One common case is the remote server is
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User unreachable and the resolver receives an ICMP
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews unreachable error message.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User</tr>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<tr>
3a28155fe228cd6d59b15f1ca0b568be6620a9d2Tinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p><code class="varname">badresp</code></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
3a28155fe228cd6d59b15f1ca0b568be6620a9d2Tinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User The number of unexpected responses (other than
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington <code class="varname">lame</code>) to queries sent by the
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews resolver at the <code class="varname">domain</code> zone.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater <p><code class="varname">adberr</code></p>
a5636b773fa05a272b6876afd99309c0b3090e2fMark Andrews </td>
5c5c6d289db78e41f714007426a387498e15963cFrancis Dupont<td>
5c5c6d289db78e41f714007426a387498e15963cFrancis Dupont <p>
5c5c6d289db78e41f714007426a387498e15963cFrancis Dupont Failures in finding remote server addresses
5c5c6d289db78e41f714007426a387498e15963cFrancis Dupont of the <code class="varname">domain</code> zone in the ADB.
5c5c6d289db78e41f714007426a387498e15963cFrancis Dupont One common case of this is that the remote
5c5c6d289db78e41f714007426a387498e15963cFrancis Dupont server's name does not have any address records.
5c5c6d289db78e41f714007426a387498e15963cFrancis Dupont </p>
5c5c6d289db78e41f714007426a387498e15963cFrancis Dupont </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</tr>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<tr>
95de440e8d2b07bb130505b4146059e5734e2eeaTinderbox User<td>
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews <p><code class="varname">findfail</code></p>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User </td>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<td>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <p>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews Failures of resolving remote server addresses.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews This is a total number of failures throughout
3040b455151b1e1173193933664b2891b6159f24Mark Andrews the resolution process.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </td>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</tr>
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews<tr>
ec7751119a08c6a7250f3187beed69a8b836d349Tinderbox User<td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <p><code class="varname">valfail</code></p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <p>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User Failures of DNSSEC validation.
879391501ee0ffba072433120bf1baa4087f8899Automatic Updater Validation failures are counted throughout
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater the resolution process (not limited to
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater the <code class="varname">domain</code> zone), but should
8f536463f9fdfa7da6a8310e4f4895373beb2961Mark Andrews only happen in <code class="varname">domain</code>.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User </p>
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater </td>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt</tr>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</tbody>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</table></div>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User<p>
dcd42a39d311b44877161ffd1e27fa62700c0171Mark Andrews 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
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater than SERVFAIL.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Note that negative responses such as NXDOMAIN are not
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater regarded as errors here.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater At the debug levels of 4 or higher, the same messages
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User as those at the debug 2 level are logged for other errors
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User than SERVFAIL.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Unlike the above case of level 3, messages are logged for
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User negative responses.
3f68e9c0e5a6ce475d15eef04bfed9b08a22afa9Tinderbox User This is because any unexpected results can be difficult to
3040b455151b1e1173193933664b2891b6159f24Mark Andrews debug in the recursion case.
3040b455151b1e1173193933664b2891b6159f24Mark Andrews </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews</div>
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews</div>
c5f7f6aa6c51d35353a9485b32abbabfe8358b4eMark Andrews<div class="section">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="titlepage"><div><div><h3 class="title">
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User<a name="lwres_grammar"></a><span class="command"><strong>lwres</strong></span> Statement Grammar</h3></div></div></div>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington<p>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington This is the grammar of the <span class="command"><strong>lwres</strong></span>
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington statement in the <code class="filename">named.conf</code> file:
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting"><span class="command"><strong>lwres</strong></span> {
22bed5c0fa8aa33ebca97235c0509db335440811Tinderbox User [<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>] ;
22bed5c0fa8aa33ebca97235c0509db335440811Tinderbox User [<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>]
22bed5c0fa8aa33ebca97235c0509db335440811Tinderbox User [<span class="optional"> view <em class="replaceable"><code>view_name</code></em>; </span>]
63654fea53d6a58a65112234bc8d0c322e0c81b5Automatic Updater [<span class="optional"> search { <em class="replaceable"><code>domain_name</code></em> ; [<span class="optional"> <em class="replaceable"><code>domain_name</code></em> ; ... </span>] }; </span>]
3040b455151b1e1173193933664b2891b6159f24Mark Andrews [<span class="optional"> ndots <em class="replaceable"><code>number</code></em>; </span>]
22bed5c0fa8aa33ebca97235c0509db335440811Tinderbox User [<span class="optional"> lwres-tasks <em class="replaceable"><code>number</code></em>; </span>]
22bed5c0fa8aa33ebca97235c0509db335440811Tinderbox User [<span class="optional"> lwres-clients <em class="replaceable"><code>number</code></em>; </span>]
ae454ec746d1d4db8d04e107d4d25ff13158c37fMark Andrews};
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="section">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<a name="lwres_statement"></a><span class="command"><strong>lwres</strong></span> Statement Definition and Usage</h3></div></div></div>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater<p>
fd7c65dce9c2b1a3d12ca4df9074cd38019fdb5fAutomatic Updater The <span class="command"><strong>lwres</strong></span> statement configures the
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User name
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews server to also act as a lightweight resolver server. (See
3040b455151b1e1173193933664b2891b6159f24Mark Andrews <a class="xref" href="Bv9ARM.ch05.html#lwresd" title="Running a Resolver Daemon">the section called &#8220;Running a Resolver Daemon&#8221;</a>.) There may be multiple
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt <span class="command"><strong>lwres</strong></span> statements configuring
3040b455151b1e1173193933664b2891b6159f24Mark Andrews lightweight resolver servers with different properties.
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User </p>
3040b455151b1e1173193933664b2891b6159f24Mark Andrews<p>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews The <span class="command"><strong>listen-on</strong></span> statement specifies a
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User list of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv4 addresses (and ports) that this instance of a lightweight
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater resolver daemon
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User should accept requests on. If no port is specified, port 921 is
63d024b4a80b39753d7b2976d46b1478913cc6a1Tinderbox User used.
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews If this statement is omitted, requests will be accepted on
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater 127.0.0.1,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater port 921.
ab496cc3df1648e9ad992a87c35c2c0870fdc69dTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ab496cc3df1648e9ad992a87c35c2c0870fdc69dTinderbox User The <span class="command"><strong>view</strong></span> statement binds this
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews instance of a
63d024b4a80b39753d7b2976d46b1478913cc6a1Tinderbox User lightweight resolver daemon to a view in the DNS namespace, so that
b6561016dc8a813bfd91cef5b876b3dfc3f08ffaTinderbox User the
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews response will be constructed in the same manner as a normal DNS
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater query
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User matching this view. If this statement is omitted, the default view
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User is
80f05de86cd3cd8e4a4215c4501643891b942dafTinderbox User used, and if there is no default view, an error is triggered.
80f05de86cd3cd8e4a4215c4501643891b942dafTinderbox User </p>
ab496cc3df1648e9ad992a87c35c2c0870fdc69dTinderbox User<p>
ab496cc3df1648e9ad992a87c35c2c0870fdc69dTinderbox User The <span class="command"><strong>search</strong></span> statement is equivalent to
3040b455151b1e1173193933664b2891b6159f24Mark Andrews the
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews <span class="command"><strong>search</strong></span> statement in
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews <code class="filename">/etc/resolv.conf</code>. It provides a
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User list of domains
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User which are appended to relative names in queries.
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User </p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User<p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User The <span class="command"><strong>ndots</strong></span> statement is equivalent to
3040b455151b1e1173193933664b2891b6159f24Mark Andrews the
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews <span class="command"><strong>ndots</strong></span> statement in
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews <code class="filename">/etc/resolv.conf</code>. It indicates the
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews minimum
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews number of dots in a relative domain name that should result in an
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews exact match lookup before search path elements are appended.
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews </p>
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews<p>
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt The <code class="option">lwres-tasks</code> statement specifies the number
3040b455151b1e1173193933664b2891b6159f24Mark Andrews of worker threads the lightweight resolver will dedicate to serving
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews clients. By default the number is the same as the number of CPUs on
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater the system; this can be overridden using the <code class="option">-n</code>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater command line option when starting the server.
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater </p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater<p>
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater The <code class="option">lwres-clients</code> specifies
82447d835d3ff5c658749b4e9b4f66166407b3eaAutomatic Updater the number of client objects per thread the lightweight
50cfe402e61ba8d816d845a9f297e3de18f4fc15Tinderbox User resolver should create to serve client queries.
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User By default, if the lightweight resolver runs as a part
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User of <span class="command"><strong>named</strong></span>, 256 client objects are
9563f388c8ca1bb9ebb04db54e122815b0008c8aTinderbox User created for each task; if it runs as <span class="command"><strong>lwresd</strong></span>,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater 1024 client objects are created for each thread. The maximum
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User value is 32768; higher values will be silently ignored and
551271d8198ae06e37edf5da519d8ee153eeac0fTinderbox User the maximum will be used instead.
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User Note that setting too high a value may overconsume
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User system resources.
183b6c7fca54001820078f324d102fc33e64bbc6Automatic Updater </p>
9563f388c8ca1bb9ebb04db54e122815b0008c8aTinderbox User<p>
9563f388c8ca1bb9ebb04db54e122815b0008c8aTinderbox User The maximum number of client queries that the lightweight
50cfe402e61ba8d816d845a9f297e3de18f4fc15Tinderbox User resolver can handle at any one time equals
50cfe402e61ba8d816d845a9f297e3de18f4fc15Tinderbox User <code class="option">lwres-tasks</code> times <code class="option">lwres-clients</code>.
50cfe402e61ba8d816d845a9f297e3de18f4fc15Tinderbox User </p>
08190bd4d89153cee463b34f9233ad6dd88965fcMark Andrews</div>
50cfe402e61ba8d816d845a9f297e3de18f4fc15Tinderbox User<div class="section">
735e1ed9685077e25f744d692acf77c5bf5d4490Tinderbox User<div class="titlepage"><div><div><h3 class="title">
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User<a name="masters_grammar"></a><span class="command"><strong>masters</strong></span> Statement Grammar</h3></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<span class="command"><strong>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> |
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] };
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</pre>
601c1908d06375f5dea00ab98671a6c934d8a840Automatic Updater</div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="section">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<div class="titlepage"><div><div><h3 class="title">
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<a name="masters_statement"></a><span class="command"><strong>masters</strong></span> Statement Definition and
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Usage</h3></div></div></div>
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User<p><span class="command"><strong>masters</strong></span>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User lists allow for a common set of masters to be easily used by
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User multiple stub and slave zones in their <span class="command"><strong>masters</strong></span>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User or <span class="command"><strong>also-notify</strong></span> lists.
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User </p>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User</div>
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User<div class="section">
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User<div class="titlepage"><div><div><h3 class="title">
f46621af221784fd08339c6fe9509d9e48334561Tinderbox User<a name="options_grammar"></a><span class="command"><strong>options</strong></span> Statement Grammar</h3></div></div></div>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This is the grammar of the <span class="command"><strong>options</strong></span>
dd53726b246db5cc63c1c87ca86dae39568eeaa3Tinderbox User statement in the <code class="filename">named.conf</code> file:
2beefc22e6debdb72d7b2a069787ff565fc79ec4Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<pre class="programlisting"><span class="command"><strong>options</strong></span> {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> attach-cache <em class="replaceable"><code>cache_name</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> version <em class="replaceable"><code>version_string</code></em>; </span>]
dd53726b246db5cc63c1c87ca86dae39568eeaa3Tinderbox User [<span class="optional"> hostname <em class="replaceable"><code>hostname_string</code></em>; </span>]
e9e4257668ff6c4e583b0c0db2508650b0b677b8Tinderbox User [<span class="optional"> server-id <em class="replaceable"><code>server_id_string</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> directory <em class="replaceable"><code>path_name</code></em>; </span>]
d58e33bfabfee19a035031dac633d36659738d56Evan Hunt [<span class="optional"> dnstap { <em class="replaceable"><code>message_type</code></em>; ... }; </span>]
dd53726b246db5cc63c1c87ca86dae39568eeaa3Tinderbox User [<span class="optional"> dnstap-output ( <code class="literal">file</code> | <code class="literal">unix</code> ) <em class="replaceable"><code>path_name</code></em>; </span>]
dd53726b246db5cc63c1c87ca86dae39568eeaa3Tinderbox User [<span class="optional"> dnstap-identity ( <em class="replaceable"><code>string</code></em> | <code class="literal">hostname</code> | <code class="literal">none</code> ); </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> dnstap-version ( <em class="replaceable"><code>string</code></em> | <code class="literal">none</code> ); </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<span class="optional"> geoip-directory <em class="replaceable"><code>path_name</code></em>; </span>]
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews [<span class="optional"> key-directory <em class="replaceable"><code>path_name</code></em>; </span>]
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews [<span class="optional"> managed-keys-directory <em class="replaceable"><code>path_name</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> named-xfer <em class="replaceable"><code>path_name</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> tkey-gssapi-keytab <em class="replaceable"><code>path_name</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> tkey-gssapi-credential <em class="replaceable"><code>principal</code></em>; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> tkey-domain <em class="replaceable"><code>domainname</code></em>; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> tkey-dhkey <em class="replaceable"><code>key_name</code></em> <em class="replaceable"><code>key_tag</code></em>; </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<span class="optional"> cache-file <em class="replaceable"><code>path_name</code></em>; </span>]
33d1cff1dd63494ffa00fac695a793f00c4ebf0bTinderbox User [<span class="optional"> dump-file <em class="replaceable"><code>path_name</code></em>; </span>]
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews [<span class="optional"> bindkeys-file <em class="replaceable"><code>path_name</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> lock-file <em class="replaceable"><code>path_name</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> secroots-file <em class="replaceable"><code>path_name</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> session-keyfile <em class="replaceable"><code>path_name</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> session-keyname <em class="replaceable"><code>key_name</code></em>; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> session-keyalg <em class="replaceable"><code>algorithm_id</code></em>; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> memstatistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> memstatistics-file <em class="replaceable"><code>path_name</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> pid-file <em class="replaceable"><code>path_name</code></em>; </span>]
17198e77b87667f796e910d31a4f47a80e256d09Mark Andrews [<span class="optional"> recursing-file <em class="replaceable"><code>path_name</code></em>; </span>]
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User [<span class="optional"> statistics-file <em class="replaceable"><code>path_name</code></em>; </span>]
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater [<span class="optional"> zone-statistics <em class="replaceable"><code>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</code></em>; </span>]
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater [<span class="optional"> auth-nxdomain <em class="replaceable"><code>yes_or_no</code></em>; </span>]
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater [<span class="optional"> nxdomain-redirect <em class="replaceable"><code>string</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> deallocate-on-exit <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> dialup <em class="replaceable"><code>dialup_option</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> fake-iquery <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> fetch-glue <em class="replaceable"><code>yes_or_no</code></em>; </span>]
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User [<span class="optional"> flush-zones-on-shutdown <em class="replaceable"><code>yes_or_no</code></em>; </span>]
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater [<span class="optional"> has-old-clients <em class="replaceable"><code>yes_or_no</code></em>; </span>]
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater [<span class="optional"> host-statistics <em class="replaceable"><code>yes_or_no</code></em>; </span>]
c07cdac6cf5bf3e9affc1aed25f8350087691f1eAutomatic Updater [<span class="optional"> host-statistics-max <em class="replaceable"><code>number</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> minimal-any <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> minimal-responses <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> multiple-cnames <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<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>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> recursion <em class="replaceable"><code>yes_or_no</code></em>; </span>]
de73ef7ecdb9e009155993a6fa8dee5cd1bde319Mark Andrews [<span class="optional"> send-cookie <em class="replaceable"><code>yes_or_no</code></em>; </span>]
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater [<span class="optional"> require-server-cookie <em class="replaceable"><code>yes_or_no</code></em>; </span>]
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater [<span class="optional"> cookie-algorithm <em class="replaceable"><code>secret_string</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> cookie-secret <em class="replaceable"><code>secret_string</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> nocookie-udp-size <em class="replaceable"><code>number</code></em> ; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> request-nsid <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> rfc2308-type1 <em class="replaceable"><code>yes_or_no</code></em>; </span>]
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User [<span class="optional"> use-id-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater [<span class="optional"> maintain-ixfr-base <em class="replaceable"><code>yes_or_no</code></em>; </span>]
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater [<span class="optional"> ixfr-from-differences (<em class="replaceable"><code>yes_or_no</code></em> | <code class="constant">master</code> | <code class="constant">slave</code>); </span>]
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater [<span class="optional"> auto-dnssec <code class="constant">allow</code>|<code class="constant">maintain</code>|<code class="constant">off</code>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> dnssec-enable <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> dnssec-validation (<em class="replaceable"><code>yes_or_no</code></em> | <code class="constant">auto</code>); </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> dnssec-lookaside ( <em class="replaceable"><code>auto</code></em> |
0e98665878103743dac92b6e8e1556d927e5bc30Tinderbox User <em class="replaceable"><code>no</code></em> |
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <em class="replaceable"><code>domain</code></em> trust-anchor <em class="replaceable"><code>domain</code></em> ); </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> dnssec-must-be-secure <em class="replaceable"><code>domain yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> dnssec-accept-expired <em class="replaceable"><code>yes_or_no</code></em>; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> forward ( <em class="replaceable"><code>only</code></em> | <em class="replaceable"><code>first</code></em> ); </span>]
7c899ff8af55a6855100e7fb4f5dd9a0a04b48a0Automatic Updater [<span class="optional"> forwarders { [<span class="optional"> <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; ... </span>] }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>] {
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>] |
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>]) ;
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews ... }; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<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> )
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>fail</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> check-wildcard <em class="replaceable"><code>yes_or_no</code></em>; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> check-integrity <em class="replaceable"><code>yes_or_no</code></em>; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<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>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> check-sibling <em class="replaceable"><code>yes_or_no</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> check-spf ( <em class="replaceable"><code>warn</code></em> | <em class="replaceable"><code>ignore</code></em> ); </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> allow-new-zones { <em class="replaceable"><code>yes_or_no</code></em> }; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> allow-notify { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> allow-query { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> allow-query-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> allow-query-cache { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> allow-query-cache-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> allow-transfer { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> allow-recursion { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> allow-recursion-on { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> allow-update { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> allow-update-forwarding { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> automatic-interface-scan { <em class="replaceable"><code>yes_or_no</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> geoip-use-ecs <em class="replaceable"><code>yes_or_no</code></em>;</span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> update-check-ksk <em class="replaceable"><code>yes_or_no</code></em>; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> dnssec-update-mode ( <em class="replaceable"><code>maintain</code></em> | <em class="replaceable"><code>no-resign</code></em> ); </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> dnssec-dnskey-kskonly <em class="replaceable"><code>yes_or_no</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> dnssec-loadkeys-interval <em class="replaceable"><code>number</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> dnssec-secure-to-insecure <em class="replaceable"><code>yes_or_no</code></em> ;</span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> try-tcp-refresh <em class="replaceable"><code>yes_or_no</code></em>; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> allow-v6-synthesis { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> blackhole { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> keep-response-order { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> no-case-compress { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> message-compression <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> use-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> avoid-v4-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> use-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> avoid-v6-udp-ports { <em class="replaceable"><code>port_list</code></em> }; </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<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>]
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington [<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>]
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington{ <em class="replaceable"><code>address_match_list</code></em> }; </span>]
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington [<span class="optional"> query-source ( ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> )
9e3a7b0faf417a10f5f689edf288807b2d5eedc5Brian Wellington [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] |
7c8e44a2dc1121dbe3b615c9c934f37fb1741bb9Tinderbox User [<span class="optional"> address ( <em class="replaceable"><code>ip4_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
ee11dfc481f2ef6a032a715454f6290961a722d2Tinderbox User [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] )
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<span class="optional"> query-source-v6 ( ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> )
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] |
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt [<span class="optional"> address ( <em class="replaceable"><code>ip6_addr</code></em> | <em class="replaceable"><code>*</code></em> ) </span>]
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt [<span class="optional"> port ( <em class="replaceable"><code>ip_port</code></em> | <em class="replaceable"><code>*</code></em> ) </span>] )
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt [<span class="optional"> use-queryport-pool <em class="replaceable"><code>yes_or_no</code></em>; </span>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> queryport-pool-ports <em class="replaceable"><code>number</code></em>; </span>]
0accdb26ead1fe520a9820b52efbea64bdf564e3Tinderbox User [<span class="optional"> queryport-pool-updateinterval <em class="replaceable"><code>number</code></em>; </span>]
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews [<span class="optional"> max-transfer-time-in <em class="replaceable"><code>number</code></em>; </span>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> max-transfer-time-out <em class="replaceable"><code>number</code></em>; </span>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> max-transfer-idle-in <em class="replaceable"><code>number</code></em>; </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<span class="optional"> max-transfer-idle-out <em class="replaceable"><code>number</code></em>; </span>]
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews [<span class="optional"> reserved-sockets <em class="replaceable"><code>number</code></em>; </span>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> recursive-clients <em class="replaceable"><code>number</code></em>; </span>]
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<span class="optional"> tcp-clients <em class="replaceable"><code>number</code></em>; </span>]
ee11dfc481f2ef6a032a715454f6290961a722d2Tinderbox User [<span class="optional"> clients-per-query <em class="replaceable"><code>number</code></em> ; </span>]
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<span class="optional"> max-clients-per-query <em class="replaceable"><code>number</code></em> ; </span>]
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<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>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> fetch-quota-params <em class="replaceable"><code>number fixedpoint fixedpoint fixedpoint</code></em> ; </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<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>]
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews [<span class="optional"> notify-rate <em class="replaceable"><code>number</code></em>; </span>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> startup-notify-rate <em class="replaceable"><code>number</code></em>; </span>]
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews [<span class="optional"> serial-query-rate <em class="replaceable"><code>number</code></em>; </span>]
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont [<span class="optional"> serial-queries <em class="replaceable"><code>number</code></em>; </span>]
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews [<span class="optional"> tcp-listen-queue <em class="replaceable"><code>number</code></em>; </span>]
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews [<span class="optional"> transfer-format <em class="replaceable"><code>( one-answer | many-answers )</code></em>; </span>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> transfer-message-size <em class="replaceable"><code>number</code></em>; </span>]
757ff043760e4743dda1a10e7d58349275934902Tinderbox User [<span class="optional"> transfers-in <em class="replaceable"><code>number</code></em>; </span>]
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews [<span class="optional"> transfers-out <em class="replaceable"><code>number</code></em>; </span>]
78f3ed4bc2fcd3d270bfd599804f3b27a1db4d91Mark Andrews [<span class="optional"> transfers-per-ns <em class="replaceable"><code>number</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> transfer-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark 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>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> use-alt-transfer-source <em class="replaceable"><code>yes_or_no</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> notify-delay <em class="replaceable"><code>seconds</code></em> ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark 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>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> notify-source-v6 (<em class="replaceable"><code>ip6_addr</code></em> | <code class="constant">*</code>) [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> notify-to-soa <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<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</code></em> | <em class="replaceable"><code>ip_addr</code></em>
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] ) [<span class="optional">key <em class="replaceable"><code>keyname</code></em></span>] ; ... }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> max-ixfr-log-size <em class="replaceable"><code>number</code></em>; </span>]
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User [<span class="optional"> max-journal-size <em class="replaceable"><code>size_spec</code></em>; </span>]
56334ccb2d4b5a04fc12b70b5852049db5d24088Evan Hunt [<span class="optional"> coresize <em class="replaceable"><code>size_spec</code></em> ; </span>]
9ecb5d33470ebfb3719a1b8d56bcefdf4b27f7b2Tinderbox User [<span class="optional"> datasize <em class="replaceable"><code>size_spec</code></em> ; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> files <em class="replaceable"><code>size_spec</code></em> ; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> stacksize <em class="replaceable"><code>size_spec</code></em> ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> cleaning-interval <em class="replaceable"><code>number</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> heartbeat-interval <em class="replaceable"><code>number</code></em>; </span>]
979e02d122cddf1624cca8a4dab8d084c900fa48Automatic Updater [<span class="optional"> interface-interval <em class="replaceable"><code>number</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> statistics-interval <em class="replaceable"><code>number</code></em>; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> topology { <em class="replaceable"><code>address_match_list</code></em> }</span>];
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> sortlist { <em class="replaceable"><code>address_match_list</code></em> }</span>];
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<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>] };
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<span class="optional"> lame-ttl <em class="replaceable"><code>number</code></em>; </span>]
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<span class="optional"> max-ncache-ttl <em class="replaceable"><code>number</code></em>; </span>]
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<span class="optional"> max-cache-ttl <em class="replaceable"><code>number</code></em>; </span>]
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<span class="optional"> max-zone-ttl ( <code class="constant">unlimited</code> | <em class="replaceable"><code>number</code></em> ; </span>]
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<span class="optional"> serial-update-method <code class="constant">increment</code>|<code class="constant">unixtime</code>|<code class="constant">date</code>; </span>]
088a5ec3df14e7af67b4602b143869a09f7eefb3Francis Dupont [<span class="optional"> servfail-ttl <em class="replaceable"><code>number</code></em>; </span>]
c7f686829f05e44169d46746cfb25cadcf078585Tinderbox User [<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>]
c7f686829f05e44169d46746cfb25cadcf078585Tinderbox User [<span class="optional"> sig-signing-nodes <em class="replaceable"><code>number</code></em> ; </span>]
c7f686829f05e44169d46746cfb25cadcf078585Tinderbox User [<span class="optional"> sig-signing-signatures <em class="replaceable"><code>number</code></em> ; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> sig-signing-type <em class="replaceable"><code>number</code></em> ; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> min-roots <em class="replaceable"><code>number</code></em>; </span>]
c7f686829f05e44169d46746cfb25cadcf078585Tinderbox User [<span class="optional"> use-ixfr <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> provide-ixfr <em class="replaceable"><code>yes_or_no</code></em>; </span>]
51901858be9d4632c1d0bed28cfa8f29932c1967Tinderbox User [<span class="optional"> request-ixfr <em class="replaceable"><code>yes_or_no</code></em>; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> request-expire <em class="replaceable"><code>yes_or_no</code></em>; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> treat-cr-as-space <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> min-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> max-refresh-time <em class="replaceable"><code>number</code></em> ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> min-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> max-retry-time <em class="replaceable"><code>number</code></em> ; </span>]
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater [<span class="optional"> nta-lifetime <em class="replaceable"><code>duration</code></em> ; </span>]
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews [<span class="optional"> nta-recheck <em class="replaceable"><code>duration</code></em> ; </span>]
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson [<span class="optional"> port <em class="replaceable"><code>ip_port</code></em>; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dscp <em class="replaceable"><code>ip_dscp</code></em></span>] ;
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews [<span class="optional"> additional-from-auth <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
4fe0411487e8e4401477684c0a2bac041ca7c2d5Tinderbox User [<span class="optional"> additional-from-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews [<span class="optional"> random-device <em class="replaceable"><code>path_name</code></em> ; </span>]
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User [<span class="optional"> max-cache-size <em class="replaceable"><code>size_or_percent</code></em> ; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> match-mapped-addresses <em class="replaceable"><code>yes_or_no</code></em>; </span>]
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox 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>]
6284b9b877d2205240dce1cf7f88d4dca888e44aTinderbox 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>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> filter-aaaa { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> dns64 <em class="replaceable"><code>ipv6-prefix</code></em> {
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson [<span class="optional"> clients { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews [<span class="optional"> mapped { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User [<span class="optional"> exclude { <em class="replaceable"><code>address_match_list</code></em> }; </span>]
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson [<span class="optional"> suffix <em class="replaceable"><code>IPv6-address</code></em>; </span>]
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson [<span class="optional"> recursive-only <em class="replaceable"><code>yes_or_no</code></em>; </span>]
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson [<span class="optional"> break-dnssec <em class="replaceable"><code>yes_or_no</code></em>; </span>]
3a9593055ead76cbbb417aee2d2e656c2c92cf46Automatic Updater }; </span>];
229ea4644b3a7d9c7fdaa43888e7f55ba01e2ee3Automatic Updater [<span class="optional"> dns64-server <em class="replaceable"><code>name</code></em> </span>]
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews [<span class="optional"> dns64-contact <em class="replaceable"><code>name</code></em> </span>]
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox 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>]
e64202536ea72d8f371dd0df9fc763f8d70bf886Tinderbox User [<span class="optional"> edns-udp-size <em class="replaceable"><code>number</code></em>; </span>]
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User [<span class="optional"> max-udp-size <em class="replaceable"><code>number</code></em>; </span>]
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox User [<span class="optional"> max-rsa-exponent-size <em class="replaceable"><code>number</code></em>; </span>]
de7b9a1dac0c293b39994c91d4376883da25554fTinderbox User [<span class="optional"> root-delegation-only [<span class="optional"> exclude { <em class="replaceable"><code>namelist</code></em> } </span>] ; </span>]
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User [<span class="optional"> querylog <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User [<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>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> disable-ds-digests <em class="replaceable"><code>domain</code></em> { <em class="replaceable"><code>digest_type</code></em>;
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> <em class="replaceable"><code>digest_type</code></em>; </span>] }; </span>]
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater [<span class="optional"> acache-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User [<span class="optional"> acache-cleaning-interval <em class="replaceable"><code>number</code></em>; </span>]
ab103cf2caf211985be8c4296d379e43d26268c4Tinderbox User [<span class="optional"> max-acache-size <em class="replaceable"><code>size_spec</code></em> ; </span>]
467a823e57af687ebd486dfd73ea32f9d2a145beTinderbox User [<span class="optional"> max-recursion-depth <em class="replaceable"><code>number</code></em> ; </span>]
467a823e57af687ebd486dfd73ea32f9d2a145beTinderbox User [<span class="optional"> max-recursion-queries <em class="replaceable"><code>number</code></em> ; </span>]
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User [<span class="optional"> masterfile-format
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User (<code class="constant">text</code>|<code class="constant">raw</code>|<code class="constant">map</code>) ; </span>]
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User [<span class="optional"> masterfile-style
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews (<code class="constant">relative</code>|<code class="constant">full</code>) ; </span>]
950d203b64f512b85fcc093ee1e9e3e531a1aea3Tinderbox User [<span class="optional"> empty-server <em class="replaceable"><code>name</code></em> ; </span>]
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User [<span class="optional"> empty-contact <em class="replaceable"><code>name</code></em> ; </span>]
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews [<span class="optional"> empty-zones-enable <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews [<span class="optional"> disable-empty-zone <em class="replaceable"><code>zone_name</code></em> ; </span>]
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater [<span class="optional"> zero-no-soa-ttl <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater [<span class="optional"> zero-no-soa-ttl-cache <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User [<span class="optional"> resolver-query-timeout <em class="replaceable"><code>number</code></em> ; </span>]
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User [<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>]
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox 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>]
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User [<span class="optional"> prefetch <em class="replaceable"><code>number</code></em> [<span class="optional"><em class="replaceable"><code>number</code></em></span>] ; </span>]
402eda3e7d4254ffac1543bf2917c71248a09e4cTinderbox User
e6fc17ec5ad5ba1c4bf5730b2b97c82d1f2b8f3cMark Andrews [<span class="optional"> rate-limit {
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> responses-per-second <em class="replaceable"><code>number</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> referrals-per-second <em class="replaceable"><code>number</code></em> ; </span>]
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater [<span class="optional"> nodata-per-second <em class="replaceable"><code>number</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> nxdomains-per-second <em class="replaceable"><code>number</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> errors-per-second <em class="replaceable"><code>number</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> all-per-second <em class="replaceable"><code>number</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> window <em class="replaceable"><code>number</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> log-only <em class="replaceable"><code>yes_or_no</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> qps-scale <em class="replaceable"><code>number</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> ipv4-prefix-length <em class="replaceable"><code>number</code></em> ; </span>]
821d2613356f81e5bb5c107288d6d5cf35c2a1e8Mark Andrews [<span class="optional"> ipv6-prefix-length <em class="replaceable"><code>number</code></em> ; </span>]
f7a71eef29bcbf892270460269c79664f600cffdAutomatic Updater [<span class="optional"> slip <em class="replaceable"><code>number</code></em> ; </span>]
409ba95e573b40cf36acf97dd62ee7e9c7775851Tinderbox User [<span class="optional"> exempt-clients { <em class="replaceable"><code>address_match_list</code></em> } ; </span>]
f751b1576ee6fef4023bf7101d10167e4fe520f3Tinderbox User [<span class="optional"> max-table-size <em class="replaceable"><code>number</code></em> ; </span>]
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User [<span class="optional"> min-table-size <em class="replaceable"><code>number</code></em> ; </span>]
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User } ; </span>]
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User [<span class="optional"> response-policy {
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater zone <em class="replaceable"><code>zone_name</code></em>
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater [<span class="optional"> policy <em class="replaceable"><code>(given | disabled | passthru | drop |
8711e5c73ca872d59810760af0332194cbdd619bAutomatic Updater tcp-only | nxdomain | nodata | cname domain</code></em>) </span>]
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User [<span class="optional"> recursive-only <em class="replaceable"><code>yes_or_no</code></em> </span>]
22870a9f8df95488abe2b17ab92b7cb6a9fe6f14Tinderbox User [<span class="optional"> log <em class="replaceable"><code>yes_or_no</code></em> </span>]
22870a9f8df95488abe2b17ab92b7cb6a9fe6f14Tinderbox User [<span class="optional"> max-policy-ttl <em class="replaceable"><code>number</code></em> </span>]
22870a9f8df95488abe2b17ab92b7cb6a9fe6f14Tinderbox User ; [<span class="optional">...</span>]
261ef37955c3468cbcb55d54b83c9a3b14e114dfTinderbox User } [<span class="optional"> recursive-only <em class="replaceable"><code>yes_or_no</code></em> </span>]
22870a9f8df95488abe2b17ab92b7cb6a9fe6f14Tinderbox User [<span class="optional"> max-policy-ttl <em class="replaceable"><code>number</code></em> </span>]
22870a9f8df95488abe2b17ab92b7cb6a9fe6f14Tinderbox User [<span class="optional"> break-dnssec <em class="replaceable"><code>yes_or_no</code></em> </span>]
7a6494cfb6cc7d3f67af07359561e05e6bb8c0edTinderbox User [<span class="optional"> min-ns-dots <em class="replaceable"><code>number</code></em> </span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User [<span class="optional"> nsip-wait-recurse <em class="replaceable"><code>yes_or_no</code></em> </span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User [<span class="optional"> qname-wait-recurse <em class="replaceable"><code>yes_or_no</code></em> </span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User [<span class="optional"> automatic-interface-scan <em class="replaceable"><code>yes_or_no</code></em> </span>]
0a2ff769ecd0b5a6bda54b62bc1ec5fa6fd198a0Tinderbox User ; </span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User [<span class="optional"> catalog-zones {
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User zone <em class="replaceable"><code>quoted_string</code></em>
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User [<span class="optional"> default-masters
6d114a4c5cddb176ae5199eee154c0273d652ba4Tinderbox User [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User [<span class="optional">dscp <em class="replaceable"><code>ip_dscp</code></em></span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User { ( <em class="replaceable"><code>masters_list</code></em> | <em class="replaceable"><code>ip_addr</code></em> [<span class="optional">port <em class="replaceable"><code>ip_port</code></em></span>] [<span class="optional">key <em class="replaceable"><code>key</code></em></span>] ) ; [<span class="optional">...</span>] }</span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User [<span class="optional">in-memory <em class="replaceable"><code>yes_or_no</code></em></span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User [<span class="optional">min-update-interval <em class="replaceable"><code>interval</code></em></span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User ; [<span class="optional">...</span>] };
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User ; </span>]
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User [<span class="optional">v6-bias <em class="replaceable"><code>number</code></em> ; </span>]
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User};
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User</pre>
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User</div>
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User<div class="section">
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User<div class="titlepage"><div><div><h3 class="title">
87d422bb38fa1c8f0fb29c2a1b8c044870a7df46Tinderbox User<a name="options"></a><span class="command"><strong>options</strong></span> Statement Definition and
6d114a4c5cddb176ae5199eee154c0273d652ba4Tinderbox User Usage</h3></div></div></div>
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User<p>
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User The <span class="command"><strong>options</strong></span> statement sets up global
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User options
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User to be used by <acronym class="acronym">BIND</acronym>. This statement
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User may appear only
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User once in a configuration file. If there is no <span class="command"><strong>options</strong></span>
b8cc0c5d896c361525708a2be2e5af7df76c96d7Tinderbox User statement, an options block with each option set to its default will
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User be used.
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User </p>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User<div class="variablelist"><dl class="variablelist">
0a2ff769ecd0b5a6bda54b62bc1ec5fa6fd198a0Tinderbox User<dt><span class="term"><span class="command"><strong>attach-cache</strong></span></span></dt>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User<dd>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User<p>
959e5da49a2cff7dfd8fdb885cd11c5d7d94a292Tinderbox User Allows multiple views to share a single cache
7a6494cfb6cc7d3f67af07359561e05e6bb8c0edTinderbox User database.
7a6494cfb6cc7d3f67af07359561e05e6bb8c0edTinderbox User Each view has its own cache database by default, but
7a6494cfb6cc7d3f67af07359561e05e6bb8c0edTinderbox User if multiple views have the same operational policy
7a6494cfb6cc7d3f67af07359561e05e6bb8c0edTinderbox User for name resolution and caching, those views can
7a6494cfb6cc7d3f67af07359561e05e6bb8c0edTinderbox User share a single cache to save memory and possibly
7a6494cfb6cc7d3f67af07359561e05e6bb8c0edTinderbox User improve resolution efficiency by using this option.
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User </p>
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User<p>
43c88753060df6335a789cd9bef2994d724d8be5Tinderbox User The <span class="command"><strong>attach-cache</strong></span> option
02d20c5d79600704d617d248642c477e9b5e6a2aTinderbox User may also be specified in <span class="command"><strong>view</strong></span>
2ec4ab21838e218863d052ebfa3e106e04f50820Evan Hunt statements, in which case it overrides the
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User global <span class="command"><strong>attach-cache</strong></span> option.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The <em class="replaceable"><code>cache_name</code></em> specifies
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the cache to be shared.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews When the <span class="command"><strong>named</strong></span> server configures
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews views which are supposed to share a cache, it
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews creates a cache with the specified name for the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews first view of these sharing views.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The rest of the views will simply refer to the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews already created cache.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews One common configuration to share a cache would be to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews allow all views to share a single cache.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews This can be done by specifying
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the <span class="command"><strong>attach-cache</strong></span> as a global
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews option with an arbitrary name.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Another possible operation is to allow a subset of
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews all views to share a cache while the others to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews retain their own caches.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews For example, if there are three views A, B, and C,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews and only A and B should share a cache, specify the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>attach-cache</strong></span> option as a view A (or
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews B)'s option, referring to the other view name:
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<pre class="programlisting">
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews view "A" {
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews // this view has its own cache
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews ...
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews };
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews view "B" {
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews // this view refers to A's cache
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews attach-cache "A";
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews };
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews view "C" {
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews // this view has its own cache
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews ...
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews };
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</pre>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Views that share a cache must have the same policy
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews on configurable parameters that may affect caching.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The current implementation requires the following
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews configurable options be consistent among these
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews views:
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>check-names</strong></span>,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>cleaning-interval</strong></span>,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>dnssec-accept-expired</strong></span>,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>dnssec-validation</strong></span>,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>max-cache-ttl</strong></span>,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>max-ncache-ttl</strong></span>,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>max-cache-size</strong></span>, and
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>zero-no-soa-ttl</strong></span>.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Note that there may be other parameters that may
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews cause confusion if they are inconsistent for
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews different views that share a single cache.
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews For example, if these views define different sets of
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews forwarders that can return different answers for the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews same question, sharing the answer does not make
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews sense or could even be harmful.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews It is administrator's responsibility to ensure
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews configuration differences in different views do
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews not cause disruption with a shared cache.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</dd>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dt><span class="term"><span class="command"><strong>directory</strong></span></span></dt>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dd><p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The working directory of the server.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Any non-absolute pathnames in the configuration file will be
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews taken
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews as relative to this directory. The default location for most
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews server
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews output files (e.g. <code class="filename">named.run</code>)
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews is this directory.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews If a directory is not specified, the working directory
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews defaults to `<code class="filename">.</code>', the directory from
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews which the server
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews was started. The directory specified should be an absolute
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews path.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p></dd>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dt><span class="term"><span class="command"><strong>dnstap</strong></span></span></dt>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dd>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>dnstap</strong></span> is a fast, flexible method
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews for capturing and logging DNS traffic. Developed by
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Robert Edmonds at Farsight Security, Inc., and supported
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews by multiple DNS implementations, <span class="command"><strong>dnstap</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews uses
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>libfstrm</strong></span> (a lightweight high-speed
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews framing library, see
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <a class="link" href="https://github.com/farsightsec/fstrm" target="_top">https://github.com/farsightsec/fstrm</a>) to send
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews event payloads which are encoded using Protocol Buffers
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews (<span class="command"><strong>libprotobuf-c</strong></span>, a mechanism for
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews serializing structured data developed
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews by Google, Inc.; see
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <a class="link" href="https://developers.google.com/protocol-buffers/" target="_top">https://developers.google.com/protocol-buffers</a>).
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews To enable <span class="command"><strong>dnstap</strong></span> at compile time,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the <span class="command"><strong>fstrm</strong></span> and <span class="command"><strong>protobuf-c</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews libraries must be available, and BIND must be configured with
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="option">--enable-dnstap</code>.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The <span class="command"><strong>dnstap</strong></span> option is a bracketed list
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews of message types to be logged. These may be set differently
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews for each view. Supported types are <code class="literal">client</code>,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="literal">auth</code>, <code class="literal">resolver</code>, and
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="literal">forwarder</code>. Specifying type
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="literal">all</code> will cause all <span class="command"><strong>dnstap</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews messages to be logged, regardless of type.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Each type may take an additional argument to indicate whether
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews to log <code class="literal">query</code> messages or
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="literal">response</code> messages; if not specified,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews both queries and responses are logged.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Example: To log all authoritative queries and responses,
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews recursive client responses, and upstream queries sent by
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the resolver, use:
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<pre class="programlisting">dnstap {
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews auth;
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews client response;
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews resolver query;
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews};
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</pre>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Logged <span class="command"><strong>dnstap</strong></span> messages can be parsed
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews using the <span class="command"><strong>dnstap-read</strong></span> utility (see
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <a class="xref" href="man.dnstap-read.html" title="dnstap-read"><span class="refentrytitle"><span class="application">dnstap-read</span></span>(1)</a> for details).
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews For more information on <span class="command"><strong>dnstap</strong></span>, see
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <a class="link" href="http://dnstap.info" target="_top">http://dnstap.info</a>.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</dd>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dt><span class="term"><span class="command"><strong>dnstap-output</strong></span></span></dt>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dd>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Configures the path to which the <span class="command"><strong>dnstap</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews frame stream will be sent if <span class="command"><strong>dnstap</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews is enabled at compile time and active.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews The first argument is either <code class="literal">file</code> or
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="literal">unix</code>, indicating whether the destination
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews is a file or a UNIX domain socket. The second argument
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews is the path of the file or socket. (Note: when using a
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User socket, <span class="command"><strong>dnstap</strong></span> messages will
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews only be sent if another process such as
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>fstrm_capture</strong></span>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews (provided with <span class="command"><strong>libfstrm</strong></span>) is listening on
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews the socket.)
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>dnstap-output</strong></span> can only be set globally
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews in <span class="command"><strong>options</strong></span>. Currently, it can only be
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews set once while <span class="command"><strong>named</strong></span> is running;
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews once set, it cannot be changed by
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>rndc reload</strong></span> or
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>rndc reconfig</strong></span>.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews</dd>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dt><span class="term"><span class="command"><strong>dnstap-identity</strong></span></span></dt>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dd><p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Specifies an <span class="command"><strong>identity</strong></span> string to send in
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>dnstap</strong></span> messages. If set to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="literal">hostname</code>, which is the default, the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews server's hostname will be sent. If set to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="literal">none</code>, no identity string will be sent.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p></dd>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dt><span class="term"><span class="command"><strong>dnstap-version</strong></span></span></dt>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dd><p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Specifies a <span class="command"><strong>version</strong></span> string to send in
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <span class="command"><strong>dnstap</strong></span> messages. The default is the
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews version number of the BIND release. If set to
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="literal">none</code>, no version string will be sent.
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews </p></dd>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dt><span class="term"><span class="command"><strong>geoip-directory</strong></span></span></dt>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews<dd><p>
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews Specifies the directory containing GeoIP
4f087942583014b241adca1bc78c6db89ed96e94Mark Andrews <code class="filename">.dat</code> database files for GeoIP
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User initialization. By default, this option is unset
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt and the GeoIP support will use libGeoIP's
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt built-in directory.
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt (For details, see <a class="xref" href="Bv9ARM.ch06.html#acl" title="acl Statement Definition and Usage">the section called &#8220;<span class="command"><strong>acl</strong></span> Statement Definition and
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt Usage&#8221;</a> about the
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt <span class="command"><strong>geoip</strong></span> ACL.)
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt </p></dd>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt<dt><span class="term"><span class="command"><strong>key-directory</strong></span></span></dt>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt<dd><p>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt When performing dynamic update of secure zones, the
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt directory where the public and private DNSSEC key files
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt should be found, if different than the current working
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt directory. (Note that this option has no effect on the
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt paths for files containing non-DNSSEC keys such as
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt <code class="filename">bind.keys</code>,
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt <code class="filename">rndc.key</code> or
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt <code class="filename">session.key</code>.)
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt </p></dd>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt<dt><span class="term"><span class="command"><strong>managed-keys-directory</strong></span></span></dt>
e2d635d630f6f61fefd3d4475c45b097b16b8a2aEvan Hunt<dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<p>
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User Specifies the directory in which to store the files that
ab272d2204a075b5ed0798d04733a9028782b8daEvan Hunt track managed DNSSEC keys. By default, this is the working
214af784e91553d387246fd9ce46cb1291697b9aTinderbox User directory.
ab272d2204a075b5ed0798d04733a9028782b8daEvan Hunt </p>
ab272d2204a075b5ed0798d04733a9028782b8daEvan Hunt<p>
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater If <span class="command"><strong>named</strong></span> is not configured to use views,
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater then managed keys for the server will be tracked in a single
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater file called <code class="filename">managed-keys.bind</code>.
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater Otherwise, managed keys will be tracked in separate files,
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater one file per view; each file name will be the view name
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater (or, if it contains characters that are incompatible with
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User use as a file name, the SHA256 hash of the view name),
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User followed by the extension
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User <code class="filename">.mkeys</code>.
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater </p>
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User<p>
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User (Note: in previous releases, file names for views
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User always used the SHA256 hash of the view name. To ensure
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater compatibility after upgrade, if a file using the old
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater name format is found to exist, it will be used instead
97669cab1f7e6f953dbf39ef1b2c4206ecb50d9eAutomatic Updater of the new format.)
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User </p>
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews</dd>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson<dt><span class="term"><span class="command"><strong>named-xfer</strong></span></span></dt>
309b912841e8b97bf0b0df0d96c3eaf16990c080Automatic Updater<dd><p>
66d24a46538c7c2d29fdb5611ab1173e83685b1dTinderbox User <span class="emphasis"><em>This option is obsolete.</em></span> It
66d24a46538c7c2d29fdb5611ab1173e83685b1dTinderbox User was used in <acronym class="acronym">BIND</acronym> 8 to specify
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson the pathname to the <span class="command"><strong>named-xfer</strong></span>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson program. In <acronym class="acronym">BIND</acronym> 9, no separate
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews <span class="command"><strong>named-xfer</strong></span> program is needed;
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews its functionality is built into the name server.
754ebd37e782356aedbb2987e3c1a8ab4f29574eMark Andrews </p></dd>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<dt><span class="term"><span class="command"><strong>tkey-gssapi-keytab</strong></span></span></dt>
94df856897945fe58f130ba78765c57308bc5400Automatic Updater<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
089d5091b781af7dfef225fbc828eb4e6d04bf4fTinderbox User matching a principal in the specified keytab.
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User </p></dd>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dt><span class="term"><span class="command"><strong>tkey-gssapi-credential</strong></span></span></dt>
776a8e3ff8889711a1f61a9362607c42716563f4Tinderbox User<dd><p>
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews The security credential with which the server should
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User authenticate keys requested by the GSS-TSIG protocol.
5c679dbb66df92766f6a7e7bb93c18d61275d1feMark Andrews Currently only Kerberos 5 authentication is available
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater and the credential is a Kerberos principal which the
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User server can acquire through the default system key
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater file, normally <code class="filename">/etc/krb5.keytab</code>.
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews The location keytab file can be overridden using the
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews tkey-gssapi-keytab option. Normally this principal is
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User of the form "<strong class="userinput"><code>DNS/</code></strong><code class="varname">server.domain</code>".
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User To use GSS-TSIG, <span class="command"><strong>tkey-domain</strong></span> must
da93950363b307b718d156514b95b9df93a63776Mark Andrews also be set if a specific keytab is not set with
da93950363b307b718d156514b95b9df93a63776Mark Andrews tkey-gssapi-keytab.
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User </p></dd>
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User<dt><span class="term"><span class="command"><strong>tkey-domain</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User The domain appended to the names of all shared keys
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater generated with <span class="command"><strong>TKEY</strong></span>. When a
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User client requests a <span class="command"><strong>TKEY</strong></span> exchange,
f6056ad06781c95198505ae3a361e6dd98df4b91Automatic Updater it may or may not specify the desired name for the
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User key. If present, the name of the shared key will
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User be <code class="varname">client specified part</code> +
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User <code class="varname">tkey-domain</code>. Otherwise, the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater name of the shared key will be <code class="varname">random hex
9a9ca3c4f120971b7091b28a5530e5eaf362f7e6Tinderbox User digits</code> + <code class="varname">tkey-domain</code>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater In most cases, the <span class="command"><strong>domainname</strong></span>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User should be the server's domain name, or an otherwise
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User non-existent subdomain like
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User "_tkey.<code class="varname">domainname</code>". If you are
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User using GSS-TSIG, this variable must be defined, unless
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User you specify a specific keytab using tkey-gssapi-keytab.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>tkey-dhkey</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The Diffie-Hellman key used by the server
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User to generate shared keys with clients using the Diffie-Hellman
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User mode
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User of <span class="command"><strong>TKEY</strong></span>. The server must be
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User able to load the
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User public and private keys from files in the working directory.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User In
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User most cases, the keyname should be the server's host name.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>cache-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User This is for testing only. Do not use.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>dump-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of the file the server dumps
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User the database to when instructed to do so with
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <span class="command"><strong>rndc dumpdb</strong></span>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User If not specified, the default is <code class="filename">named_dump.db</code>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>memstatistics-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of the file the server writes memory
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User usage statistics to on exit. If not specified,
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User the default is <code class="filename">named.memstats</code>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>lock-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of a file on which <span class="command"><strong>named</strong></span> will
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User attempt to acquire a file lock when starting up for
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User the first time; if unsuccessful, the server will
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User will terminate, under the assumption that another
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User server is already running. If not specified, the default is
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <code class="filename">/var/run/named/named.lock</code>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User Specifying <span class="command"><strong>lock-file none</strong></span> disables the
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User use of a lock file. <span class="command"><strong>lock-file</strong></span> is
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User ignored if <span class="command"><strong>named</strong></span> was run using the <code class="option">-X</code>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User option, which overrides it. Changes to
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <span class="command"><strong>lock-file</strong></span> are ignored if
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <span class="command"><strong>named</strong></span> is being reloaded or
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User reconfigured; it is only effective when the server is
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User first started up.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User</dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>pid-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of the file the server writes its process ID
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User in. If not specified, the default is
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <code class="filename">/var/run/named/named.pid</code>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The PID file is used by programs that want to send signals to
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User the running
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User name server. Specifying <span class="command"><strong>pid-file none</strong></span> disables the
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User use of a PID file &#8212; no file will be written and any
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User existing one will be removed. Note that <span class="command"><strong>none</strong></span>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User is a keyword, not a filename, and therefore is not enclosed
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User in
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User double quotes.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>recursing-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of the file the server dumps
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User the queries that are currently recursing when instructed
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User to do so with <span class="command"><strong>rndc recursing</strong></span>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User If not specified, the default is <code class="filename">named.recursing</code>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>statistics-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of the file the server appends statistics
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User to when instructed to do so using <span class="command"><strong>rndc stats</strong></span>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User If not specified, the default is <code class="filename">named.stats</code> in the
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User server's current directory. The format of the file is
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User described
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User in <a class="xref" href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called &#8220;The Statistics File&#8221;</a>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>bindkeys-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of a file to override the built-in trusted
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User keys provided by <span class="command"><strong>named</strong></span>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User See the discussion of <span class="command"><strong>dnssec-lookaside</strong></span>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User and <span class="command"><strong>dnssec-validation</strong></span> for details.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User If not specified, the default is
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <code class="filename">/etc/bind.keys</code>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>secroots-file</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of the file the server dumps
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User security roots to when instructed to do so with
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <span class="command"><strong>rndc secroots</strong></span>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User If not specified, the default is
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <code class="filename">named.secroots</code>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>session-keyfile</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The pathname of the file into which to write a TSIG
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User session key generated by <span class="command"><strong>named</strong></span> for use by
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <span class="command"><strong>nsupdate -l</strong></span>. If not specified, the
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User default is <code class="filename">/var/run/named/session.key</code>.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User (See <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>, and in
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User particular the discussion of the
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <span class="command"><strong>update-policy</strong></span> statement's
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User <strong class="userinput"><code>local</code></strong> option for more
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User information about this feature.)
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>session-keyname</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The key name to use for the TSIG session key.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User If not specified, the default is "local-ddns".
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>session-keyalg</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The algorithm to use for the TSIG session key.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User Valid values are hmac-sha1, hmac-sha224, hmac-sha256,
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User hmac-sha384, hmac-sha512 and hmac-md5. If not
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User specified, the default is hmac-sha256.
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User </p></dd>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dt><span class="term"><span class="command"><strong>port</strong></span></span></dt>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User<dd><p>
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User The UDP/TCP port number the server uses for
05c0db3923b93c36afa488bffc7862e0ae554698Tinderbox User receiving and sending DNS protocol traffic.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews The default is 53. This option is mainly intended for server
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews testing;
933799f3641f4f78445d015008bad0038900a82aTinderbox User a server using a port other than 53 will not be able to
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User communicate with
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User the global DNS.
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User </p></dd>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<dt><span class="term"><span class="command"><strong>dscp</strong></span></span></dt>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<dd><p>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User The global Differentiated Services Code Point (DSCP)
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User value to classify outgoing DNS traffic on operating
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User systems that support DSCP. Valid values are 0 through 63.
19558a04decde0e7261d489d92d04ad88104217bTinderbox User It is not configured by default.
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User </p></dd>
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User<dt><span class="term"><span class="command"><strong>random-device</strong></span></span></dt>
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User<dd><p>
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User The source of entropy to be used by the server. Entropy is
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews primarily needed
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User for DNSSEC operations, such as TKEY transactions and dynamic
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews update of signed
39a3b65090ccfc86b66e416c949c6a938c7f1d4aTinderbox User zones. This options specifies the device (or file) from which
1bf507ca635310b340aea42d6c3e567819974a99Tinderbox User to read
d5637bdbb931ff79fced3d4858d83212ea58ed15Tinderbox User entropy. If this is a file, operations requiring entropy will
5747235bf35e7398984fd6b4632743396895ea7aTinderbox User fail when the
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews file has been exhausted. If not specified, the default value
644973f327e9db74779e7c0426db90909173b284Automatic Updater is
644973f327e9db74779e7c0426db90909173b284Automatic Updater <code class="filename">/dev/random</code>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews (or equivalent) when present, and none otherwise. The
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews <span class="command"><strong>random-device</strong></span> option takes
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User effect during
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User the initial configuration load at server startup time and
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User is ignored on subsequent reloads.
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User </p></dd>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<dt><span class="term"><span class="command"><strong>preferred-glue</strong></span></span></dt>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<dd><p>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User If specified, the listed type (A or AAAA) will be emitted
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User before other glue
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User in the additional section of a query response.
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User The default is to prefer A records when responding
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User to queries that arrived via IPv4 and AAAA when
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User responding to queries that arrived via IPv6.
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User </p></dd>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<dt>
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt<a name="root_delegation_only"></a><span class="term"><span class="command"><strong>root-delegation-only</strong></span></span>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User</dt>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<dd>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<p>
ff8d6ca9d58a398b66cee8079cbbd6bfe2c80f0dTinderbox User Turn on enforcement of delegation-only in TLDs
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User (top level domains) and root zones with an optional
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User exclude list.
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User </p>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<p>
ff8d6ca9d58a398b66cee8079cbbd6bfe2c80f0dTinderbox User DS queries are expected to be made to and be answered by
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User delegation only zones. Such queries and responses are
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User treated as an exception to delegation-only processing
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User and are not converted to NXDOMAIN responses provided
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User a CNAME is not discovered at the query name.
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User </p>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews If a delegation only zone server also serves a child
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User zone it is not always possible to determine whether
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews an answer comes from the delegation only zone or the
19558a04decde0e7261d489d92d04ad88104217bTinderbox User child zone. SOA NS and DNSKEY records are apex
e98d2156a997b64b61475539dceb4c1f3fbcd26dTinderbox User only records and a matching response that contains
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User these records or DS is treated as coming from a
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User child zone. RRSIG records are also examined to see
af60449fe472b8bea5ad04bf538c777c6b151112Tinderbox User if they are signed by a child zone or not. The
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User authority section is also examined to see if there
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User is evidence that the answer is from the child zone.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews Answers that are determined to be from a child zone
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews are not converted to NXDOMAIN responses. Despite
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews all these checks there is still a possibility of
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews false negatives when a child zone is being served.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews Similarly false positives can arise from empty nodes
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews (no records at the name) in the delegation only zone
90863a6f9bfb06062c7fdf269bb675e7b674fc31Mark Andrews when the query type is not ANY.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews Note some TLDs are not delegation only (e.g. "DE", "LV",
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews "US" and "MUSEUM"). This list is not exhaustive.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<pre class="programlisting">
068a66979695c77359e7a9181bb3f831c965b21cMark Andrewsoptions {
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews root-delegation-only exclude { "de"; "lv"; "us"; "museum"; };
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews};
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews</pre>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews</dd>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dt><span class="term"><span class="command"><strong>disable-algorithms</strong></span></span></dt>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dd>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Disable the specified DNSSEC algorithms at and below the
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews specified name.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews Multiple <span class="command"><strong>disable-algorithms</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statements are allowed.
8de3f14f1c300c3e1ed99084cc03485b42c92bf1Tinderbox User Only the best match <span class="command"><strong>disable-algorithms</strong></span>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews clause will be used to determine which algorithms are used.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User If all supported algorithms are disabled, the zones covered
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews by the <span class="command"><strong>disable-algorithms</strong></span> will be treated
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User as insecure.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>disable-ds-digests</strong></span></span></dt>
45eca3a5d46ed15aee14d81f6cb6c9fb6f365344Mark Andrews<dd>
6306dd073e0eba562491222821c4d3b39f440718Evan Hunt<p>
6306dd073e0eba562491222821c4d3b39f440718Evan Hunt Disable the specified DS/DLV digest types at and below the
6634faa55bb26d8e995dd5ad4755060f1bedc2f0Tinderbox User specified name.
6306dd073e0eba562491222821c4d3b39f440718Evan Hunt Multiple <span class="command"><strong>disable-ds-digests</strong></span>
6306dd073e0eba562491222821c4d3b39f440718Evan Hunt statements are allowed.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Only the best match <span class="command"><strong>disable-ds-digests</strong></span>
f4193c2021ab0aeaad33fe0b3d1d49c80db5c725Mark Andrews clause will be used to determine which digest types are used.
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews If all supported digest types are disabled, the zones covered
872a5b83f68b8058945298715b0fa53442aad52fAutomatic Updater by the <span class="command"><strong>disable-ds-digests</strong></span> will be treated
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews as insecure.
bac4435d473c9a0281507524f084480c34aa942aTinderbox User </p>
7a1fdd4b82824cb0ad74552bfcf353a5c7f72b87Tinderbox User</dd>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dt><span class="term"><span class="command"><strong>dnssec-lookaside</strong></span></span></dt>
068a66979695c77359e7a9181bb3f831c965b21cMark Andrews<dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews When set, <span class="command"><strong>dnssec-lookaside</strong></span> provides the
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews validator with an alternate method to validate DNSKEY
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews records at the top of a zone. When a DNSKEY is at or
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews below a domain specified by the deepest
5de1cdae8a44312ca0dbb2a0fd0388fa35676a84Tinderbox User <span class="command"><strong>dnssec-lookaside</strong></span>, and the normal DNSSEC
5de1cdae8a44312ca0dbb2a0fd0388fa35676a84Tinderbox User validation has left the key untrusted, the trust-anchor
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews will be appended to the key name and a DLV record will be
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews looked up to see if it can validate the key. If the DLV
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews record validates a DNSKEY (similarly to the way a DS
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews record does) the DNSKEY RRset is deemed to be trusted.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews If <span class="command"><strong>dnssec-lookaside</strong></span> is set to
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews <strong class="userinput"><code>auto</code></strong>, then built-in default
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews values for the DLV domain and trust anchor will be
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews used, along with a built-in key for validation.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews If <span class="command"><strong>dnssec-lookaside</strong></span> is set to
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews <strong class="userinput"><code>no</code></strong>, then dnssec-lookaside
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews is not used.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User<p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews The default DLV key is stored in the file
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews <code class="filename">bind.keys</code>;
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews <span class="command"><strong>named</strong></span> will load that key at
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews startup if <span class="command"><strong>dnssec-lookaside</strong></span> is set to
5f7e0eb1cb917b788906d3e2aa01bfc4885dcae4Mark Andrews <code class="constant">auto</code>. A copy of the file is
bf1263835e8e35421960f65088c043f42aacef13Mark Andrews installed along with <acronym class="acronym">BIND</acronym> 9, and is
15ae68f3db8261770fc33b8e0f83f5d8c7021e84Mark Andrews current as of the release date. If the DLV key expires, a
ac4e70ff8955669341f435bc0a734a17c01af124Mark Andrews new copy of <code class="filename">bind.keys</code> can be downloaded
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews from <a class="link" href="https://www.isc.org/solutions/dlv/" target="_top">https://www.isc.org/solutions/dlv/</a>.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<p>
cb40461f8744c5aeb369b84d5f48395a13a221a0Mark Andrews (To prevent problems if <code class="filename">bind.keys</code> is
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User not found, the current key is also compiled in to
a04588e781b513ae3b30e061ac98035802b5e8e8Mark Andrews <span class="command"><strong>named</strong></span>. Relying on this is not
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews recommended, however, as it requires <span class="command"><strong>named</strong></span>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User to be recompiled with a new key when the DLV key expires.)
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User </p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User NOTE: <span class="command"><strong>named</strong></span> only loads certain specific
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User keys from <code class="filename">bind.keys</code>: those for the
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User DLV zone and for the DNS root zone. The file cannot be
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater used to store keys for other zones.
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>dnssec-must-be-secure</strong></span></span></dt>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<dd><p>
10640b2e3efc7bc8034108136d7487f7407fbf37Andreas Gustafsson Specify hierarchies which must be or may not be secure
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User (signed and validated). If <strong class="userinput"><code>yes</code></strong>,
10640b2e3efc7bc8034108136d7487f7407fbf37Andreas Gustafsson then <span class="command"><strong>named</strong></span> will only accept answers if
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User they are secure. If <strong class="userinput"><code>no</code></strong>, then normal
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User DNSSEC validation applies allowing for insecure answers to
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User be accepted. The specified domain must be under a
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span class="command"><strong>trusted-keys</strong></span> or
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>managed-keys</strong></span> statement, or
436aad11e01e916f75e68a2e9cb89ac217a990d3Tinderbox User <span class="command"><strong>dnssec-lookaside</strong></span> must be active.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p></dd>
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews<dt><span class="term"><span class="command"><strong>dns64</strong></span></span></dt>
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews<dd>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
d97783f18169fc9c5220a0b91fe53653efcd6b10Tinderbox User This directive instructs <span class="command"><strong>named</strong></span> to
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User return mapped IPv4 addresses to AAAA queries when
af682c183e3448c34da1145018a085ac45b1b660Tinderbox User there are no AAAA records. It is intended to be
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User used in conjunction with a NAT64. Each
e97aa53515cec97b9a4bb5f24a89cdc5c7d4c5e0Tinderbox User <span class="command"><strong>dns64</strong></span> defines one DNS64 prefix.
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont Multiple DNS64 prefixes can be defined.
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews </p>
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User<p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews Compatible IPv6 prefixes have lengths of 32, 40, 48, 56,
09ee43766e232bd04066445db114c2703dd02bf8Tinderbox User 64 and 96 as per RFC 6052.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User<p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User Additionally a reverse IP6.ARPA zone will be created for
bac4435d473c9a0281507524f084480c34aa942aTinderbox User the prefix to provide a mapping from the IP6.ARPA names
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews to the corresponding IN-ADDR.ARPA names using synthesized
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User CNAMEs. <span class="command"><strong>dns64-server</strong></span> and
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews <span class="command"><strong>dns64-contact</strong></span> can be used to specify
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt the name of the server and contact for the zones. These
6715db6593ce9a271ac3131cd7a886feaa386a2eEvan Hunt are settable at the view / options level. These are
6715db6593ce9a271ac3131cd7a886feaa386a2eEvan Hunt not settable on a per-prefix basis.
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<p>
aef6cf0f147a5014d4891c9689b9f463399e16e7Tinderbox User Each <span class="command"><strong>dns64</strong></span> supports an optional
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span class="command"><strong>clients</strong></span> ACL that determines which
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews clients are affected by this directive. If not defined,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater it defaults to <strong class="userinput"><code>any;</code></strong>.
0197efed438a96881ebd8d165f8479a89f1ba62fTinderbox User </p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews Each <span class="command"><strong>dns64</strong></span> supports an optional
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span class="command"><strong>mapped</strong></span> ACL that selects which
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User IPv4 addresses are to be mapped in the corresponding
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User A RRset. If not defined it defaults to
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <strong class="userinput"><code>any;</code></strong>.
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt </p>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<p>
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User Normally, DNS64 won't apply to a domain name that
8f1a00cf8b3d9dc8d419a797b7ff4fb6ddba428eTinderbox User owns one or more AAAA records; these records will
2846972c703e9c588e88726c10caf62c7cdbefd0Tinderbox User simply be returned. The optional
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <span class="command"><strong>exclude</strong></span> ACL allows specification
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews of a list of IPv6 addresses that will be ignored
d6487e3c0a981bd8ac1e155d3a2d590c078d6c85Tinderbox User if they appear in a domain name's AAAA records, and
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User DNS64 will be applied to any A records the domain
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews name owns. If not defined, <span class="command"><strong>exclude</strong></span>
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews defaults to ::ffff:0.0.0.0/96.
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User </p>
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews<p>
8aa098c6334de11c8fd117d30851cc457813c410Mark Andrews A optional <span class="command"><strong>suffix</strong></span> can also
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater be defined to set the bits trailing the mapped
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IPv4 address bits. By default these bits are
8e5fce1f9ceba17dd7e3ff0eb287e1e999c14249Mark Andrews set to <strong class="userinput"><code>::</code></strong>. The bits
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews matching the prefix and mapped IPv4 address
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater must be zero.
950d203b64f512b85fcc093ee1e9e3e531a1aea3Tinderbox User </p>
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User<p>
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User If <span class="command"><strong>recursive-only</strong></span> is set to
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <span class="command"><strong>yes</strong></span> the DNS64 synthesis will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater only happen for recursive queries. The default
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater is <span class="command"><strong>no</strong></span>.
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews </p>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User<p>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews If <span class="command"><strong>break-dnssec</strong></span> is set to
dc5552b4df5e3821783821c8d4e734c1608c446eTinderbox User <span class="command"><strong>yes</strong></span> the DNS64 synthesis will
e23761df2059ed612c8fb7cc248d93bb2c4f62dbTinderbox User happen even if the result, if validated, would
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User cause a DNSSEC validation failure. If this option
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt is set to <span class="command"><strong>no</strong></span> (the default), the DO
6715db6593ce9a271ac3131cd7a886feaa386a2eEvan Hunt is set on the incoming query, and there are RRSIGs on
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews the applicable records, then synthesis will not happen.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </p>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<pre class="programlisting">
02b3e44a996e9753d86306b6a1b6b579a73787fcTinderbox User acl rfc1918 { 10/8; 192.168/16; 172.16/12; };
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews
616c05f95f9a9683d73c108df2eda56bf70b77ccTinderbox User dns64 64:FF9B::/96 {
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater clients { any; };
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt mapped { !rfc1918; any; };
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews exclude { 64:FF9B::/96; ::ffff:0000:0000/96; };
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews suffix ::;
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews };
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater</pre>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User<dt><span class="term"><span class="command"><strong>dnssec-loadkeys-interval</strong></span></span></dt>
3349f0044fda807e1fd6681c833d3593a22dad86Tinderbox User<dd><p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater When a zone is configured with <span class="command"><strong>auto-dnssec
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User maintain;</strong></span> its key repository must be checked
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater periodically to see if any new keys have been added
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews or any existing keys' timing metadata has been updated
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt (see <a class="xref" href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
e5be5a9f94d7db1c4eceac028749084c042420ebTinderbox User <a class="xref" href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <span class="command"><strong>dnssec-loadkeys-interval</strong></span> option
e20309353e6246485c521278131d3fced73d7957Tinderbox User sets the frequency of automatic repository checks, in
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews minutes. The default is <code class="literal">60</code> (1 hour),
c74518d655c1c563060f49569dce71e4a00f5f4eTinderbox User the minimum is <code class="literal">1</code> (1 minute), and the
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User maximum is <code class="literal">1440</code> (24 hours); any higher
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater value is silently reduced.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews<dt><span class="term"><span class="command"><strong>dnssec-update-mode</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
53b97c9873a923f504893d1e2ab62000dfac221fTinderbox User<p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User If this option is set to its default value of
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <code class="literal">maintain</code> in a zone of type
28a5dd720187fddb16055a0f64b63a7b66f29f64Mark Andrews <code class="literal">master</code> which is DNSSEC-signed
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and configured to allow dynamic updates (see
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called &#8220;Dynamic Update Policies&#8221;</a>), and
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews if <span class="command"><strong>named</strong></span> has access to the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater private signing key(s) for the zone, then
713a5e3080f112b3efde9235e9c92035056ff966Automatic Updater <span class="command"><strong>named</strong></span> will automatically sign all new
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater or changed records and maintain signatures for the zone
bac4435d473c9a0281507524f084480c34aa942aTinderbox User by regenerating RRSIG records whenever they approach
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User their expiration date.
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
cb40461f8744c5aeb369b84d5f48395a13a221a0Mark Andrews If the option is changed to <code class="literal">no-resign</code>,
f8b9948a4116226ac41b5509cca152849006c66cAutomatic Updater then <span class="command"><strong>named</strong></span> will sign all new or
8add7cdaa81ec881fe17df02ed8833722dc9e690Tinderbox User changed records, but scheduled maintenance of
be46cb4bee9253ee4832340c719920642e00c41aTinderbox User signatures is disabled.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
c243d779731a410f8dc2d2feeed20c15f299b6e3Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater With either of these settings, <span class="command"><strong>named</strong></span>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater will reject updates to a DNSSEC-signed zone when the
099b86fb8136a7dff81df85cf395978c16eb254cAutomatic Updater signing keys are inactive or unavailable to
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews <span class="command"><strong>named</strong></span>. (A planned third option,
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <code class="literal">external</code>, will disable all automatic
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater signing and allow DNSSEC data to be submitted into a zone
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater via dynamic update; this is not yet implemented.)
572cb2c1c931f6bc6a4a019c103ae88239b0eb96Automatic Updater </p>
02b3e44a996e9753d86306b6a1b6b579a73787fcTinderbox User</dd>
3e5340279d8875d136a4dd815cccad0044aa2644Automatic Updater<dt><span class="term"><span class="command"><strong>nta-lifetime</strong></span></span></dt>
c2abd6efeb9affa70aabb63da2acb23e135cf7f2Mark Andrews<dd>
28e0061dbcc2ae45d34541267a00d8b4de5b4a41Tinderbox User<p>
28e0061dbcc2ae45d34541267a00d8b4de5b4a41Tinderbox User Species the default lifetime, in seconds,
950d203b64f512b85fcc093ee1e9e3e531a1aea3Tinderbox User that will be used for negative trust anchors added
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews via <span class="command"><strong>rndc nta</strong></span>.
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User </p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<p>
87d570d3531d3d0eef29c4f2007cef1dbd6aed2cTinderbox User A negative trust anchor selectively disables
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater DNSSEC validation for zones that are known to be
d630ef2ff74445949a482660938e9fa9da52ca14Automatic Updater failing because of misconfiguration rather than
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User an attack. When data to be validated is
d6487e3c0a981bd8ac1e155d3a2d590c078d6c85Tinderbox User at or below an active NTA (and above any other
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews configured trust anchors), <span class="command"><strong>named</strong></span> will
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater abort the DNSSEC validation process and treat the data as
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User insecure rather than bogus. This continues until the
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews NTA's lifetime is elapsed. NTAs persist
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews across <span class="command"><strong>named</strong></span> restarts.
a308b69ac66fadf66863484f301314d6e6a3f1d2Automatic Updater </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User For convenience, TTL-style time unit suffixes can be
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews used to specify the NTA lifetime in seconds, minutes
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User or hours. <code class="option">nta-lifetime</code> defaults to
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User one hour. It cannot exceed one week.
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews </p>
2706fce75f04398595d9648122c6b67164e94fccTinderbox User</dd>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<dt><span class="term"><span class="command"><strong>nta-recheck</strong></span></span></dt>
aef6cf0f147a5014d4891c9689b9f463399e16e7Tinderbox User<dd>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews<p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews Species how often to check whether negative
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews trust anchors added via <span class="command"><strong>rndc nta</strong></span>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User are still necessary.
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User </p>
0197efed438a96881ebd8d165f8479a89f1ba62fTinderbox User<p>
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews A negative trust anchor is normally used when a
0197efed438a96881ebd8d165f8479a89f1ba62fTinderbox User domain has stopped validating due to operator error;
d6487e3c0a981bd8ac1e155d3a2d590c078d6c85Tinderbox User it temporarily disables DNSSEC validation for that
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews domain. In the interest of ensuring that DNSSEC
bcb68be0a8f3c3eca58d6a6a869267e5c1841de2Francis Dupont validation is turned back on as soon as possible,
c19bf21885cdf78b52eee017dc1189a300657995Tinderbox User <span class="command"><strong>named</strong></span> will periodically send a
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews query to the domain, ignoring negative trust anchors,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews to find out whether it can now be validated. If so,
d6487e3c0a981bd8ac1e155d3a2d590c078d6c85Tinderbox User the negative trust anchor is allowed to expire early.
d6487e3c0a981bd8ac1e155d3a2d590c078d6c85Tinderbox User </p>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews<p>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews Validity checks can be disabled for an individual
bcb68be0a8f3c3eca58d6a6a869267e5c1841de2Francis Dupont NTA by using <span class="command"><strong>rndc nta -f</strong></span>, or
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User for all NTAs by setting <code class="option">nta-recheck</code>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User to zero.
aef6cf0f147a5014d4891c9689b9f463399e16e7Tinderbox User </p>
2706fce75f04398595d9648122c6b67164e94fccTinderbox User<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User For convenience, TTL-style time unit suffixes can be
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater used to specify the NTA recheck interval in seconds,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater minutes or hours. The default is five minutes. It
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews cannot be longer than <code class="option">nta-lifetime</code>
c505effec1da6664c37f0e4dbfc1c4f6b0e73367Tinderbox User (which cannot be longer than a week).
c0cc232ba92b92c1c5a48d49449ef56f7ca05b56Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<dt><span class="term"><span class="command"><strong>max-zone-ttl</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Specifies a maximum permissible TTL value in seconds.
66458d12f373fb75e8543d36fd76864a7567057bTinderbox User For convenience, TTL-style time unit suffixes may be
ee36de8388ec31d28244d62a24050eaa2bbc8d44Tinderbox User used to specify the maximum value.
00ce5d1add91ba5664de4da3cda8c3a5017ba6a7Tinderbox User When loading a zone file using a
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User <code class="option">masterfile-format</code> of
00ce5d1add91ba5664de4da3cda8c3a5017ba6a7Tinderbox User <code class="constant">text</code> or <code class="constant">raw</code>,
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User any record encountered with a TTL higher than
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User <code class="option">max-zone-ttl</code> will cause the zone to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater be rejected.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
8f1a00cf8b3d9dc8d419a797b7ff4fb6ddba428eTinderbox User This is useful in DNSSEC-signed zones because when
8f1a00cf8b3d9dc8d419a797b7ff4fb6ddba428eTinderbox User rolling to a new DNSKEY, the old key needs to remain
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User available until RRSIG records have expired from
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User caches. The <code class="option">max-zone-ttl</code> option guarantees
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User that the largest TTL in the zone will be no higher
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater than the set value.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p>
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User<p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User (NOTE: Because <code class="constant">map</code>-format files
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater load directly into memory, this option cannot be
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User used with them.)
a61158fed2e0281a40e3e97e0b7c3f9789a07b4eTinderbox User </p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<p>
a61158fed2e0281a40e3e97e0b7c3f9789a07b4eTinderbox User The default value is <code class="constant">unlimited</code>.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User A <code class="option">max-zone-ttl</code> of zero is treated as
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <code class="constant">unlimited</code>.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<dt><span class="term"><span class="command"><strong>serial-update-method</strong></span></span></dt>
59b277af9d9aac08d16be63aed5ae60ac9eef0d5Automatic Updater<dd>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Zones configured for dynamic DNS may use this
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User option to set the update method that will be used for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the zone serial number in the SOA record.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p>
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User<p>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User With the default setting of
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater <span class="command"><strong>serial-update-method increment;</strong></span>, the
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User SOA serial number will be incremented by one each time
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews the zone is updated.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User When set to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>serial-update-method unixtime;</strong></span>, the
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User SOA serial number will be set to the number of seconds
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews since the UNIX epoch, unless the serial number is
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User already greater than or equal to that value, in which
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater case it is simply incremented by one.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User When set to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>serial-update-method date;</strong></span>, the
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User new SOA serial number will be the current date
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in the form "YYYYMMDD", followed by two zeroes,
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User unless the existing serial number is already greater
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater than or equal to that value, in which case it is
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User incremented by one.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>zone-statistics</strong></span></span></dt>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User If <strong class="userinput"><code>full</code></strong>, the server will collect
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews statistical data on all zones (unless specifically
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User turned off on a per-zone basis by specifying
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User <span class="command"><strong>zone-statistics terse</strong></span> or
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User <span class="command"><strong>zone-statistics none</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in the <span class="command"><strong>zone</strong></span> statement).
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User The default is <strong class="userinput"><code>terse</code></strong>, providing
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User minimal statistics on zones (including name and
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User current serial number, but not query type
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater counters).
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p>
1b670d35282f1b9352692ad212be3c0aa97b0689Automatic Updater<p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User These statistics may be accessed via the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>statistics-channel</strong></span> or
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User using <span class="command"><strong>rndc stats</strong></span>, which
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater will dump them to the file listed
c0cc232ba92b92c1c5a48d49449ef56f7ca05b56Tinderbox User in the <span class="command"><strong>statistics-file</strong></span>. See
316cd2460aa66e157f72890974ca5c21d65e70e6Tinderbox User also <a class="xref" href="Bv9ARM.ch06.html#statsfile" title="The Statistics File">the section called &#8220;The Statistics File&#8221;</a>.
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User For backward compatibility with earlier versions
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater of BIND 9, the <span class="command"><strong>zone-statistics</strong></span>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User option can also accept <strong class="userinput"><code>yes</code></strong>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater or <strong class="userinput"><code>no</code></strong>; <strong class="userinput"><code>yes</code></strong>
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User has the same meaning as <strong class="userinput"><code>full</code></strong>.
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User As of <acronym class="acronym">BIND</acronym> 9.10,
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User <strong class="userinput"><code>no</code></strong> has the same meaning
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater as <strong class="userinput"><code>none</code></strong>; previously, it
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User was the same as <strong class="userinput"><code>terse</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User</dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dl></div>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<div class="section">
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<div class="titlepage"><div><div><h4 class="title">
6284b9b877d2205240dce1cf7f88d4dca888e44aTinderbox User<a name="boolean_options"></a>Boolean Options</h4></div></div></div>
6284b9b877d2205240dce1cf7f88d4dca888e44aTinderbox User<div class="variablelist"><dl class="variablelist">
36c0c1405d4dd31afaf614668f4512e69637e159Tinderbox User<dt><span class="term"><span class="command"><strong>automatic-interface-scan</strong></span></span></dt>
36c0c1405d4dd31afaf614668f4512e69637e159Tinderbox User<dd>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong> and supported by the OS,
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User automatically rescan network interfaces when the interface
6ee455a915d0e5cab50865da23152efe59ea1decTinderbox User addresses are added or removed. The default is
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User <strong class="userinput"><code>yes</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User<p>
e5a6871cd0635ecdb2bf792316a2d8c53206f4b2Tinderbox User Currently the OS needs to support routing sockets for
0a2ff769ecd0b5a6bda54b62bc1ec5fa6fd198a0Tinderbox User <span class="command"><strong>automatic-interface-scan</strong></span> to be
0a2ff769ecd0b5a6bda54b62bc1ec5fa6fd198a0Tinderbox User supported.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dd>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<dt><span class="term"><span class="command"><strong>allow-new-zones</strong></span></span></dt>
79b627f399ce925988bb326315e6742d5316cb6bTinderbox User<dd><p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User If <strong class="userinput"><code>yes</code></strong>, then zones can be
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater added at runtime via <span class="command"><strong>rndc addzone</strong></span>.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User The default is <strong class="userinput"><code>no</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<dt><span class="term"><span class="command"><strong>auth-nxdomain</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User If <strong class="userinput"><code>yes</code></strong>, then the <span class="command"><strong>AA</strong></span> bit
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater is always set on NXDOMAIN responses, even if the server is
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User not actually
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater authoritative. The default is <strong class="userinput"><code>no</code></strong>;
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User this is
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a change from <acronym class="acronym">BIND</acronym> 8. If you
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User are using very old DNS software, you
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater may need to set it to <strong class="userinput"><code>yes</code></strong>.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>deallocate-on-exit</strong></span></span></dt>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater This option was used in <acronym class="acronym">BIND</acronym>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User 8 to enable checking
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for memory leaks on exit. <acronym class="acronym">BIND</acronym> 9 ignores the option and always performs
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User the checks.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<dt><span class="term"><span class="command"><strong>memstatistics</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
f525041ae26958385b697cf82a30f108577024b6Tinderbox User Write memory statistics to the file specified by
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>memstatistics-file</strong></span> at exit.
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User The default is <strong class="userinput"><code>no</code></strong> unless
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater '-m record' is specified on the command line in
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User which case it is <strong class="userinput"><code>yes</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
a05244bb01d5a5f71b2ac9abe1601589cde79570Tinderbox User<dt><span class="term"><span class="command"><strong>dialup</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then the
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews server treats all zones as if they are doing zone transfers
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews across
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User a dial-on-demand dialup link, which can be brought up by
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater traffic
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews originating from this server. This has different effects
af60449fe472b8bea5ad04bf538c777c6b151112Tinderbox User according
aef6cf0f147a5014d4891c9689b9f463399e16e7Tinderbox User to zone type and concentrates the zone maintenance so that
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User it all
a9d14bf051644716b5db9209c453d2c5eb83f174Tinderbox User happens in a short interval, once every <span class="command"><strong>heartbeat-interval</strong></span> and
5a23eb8cb48cee59999acc9af33f643dbcd76feaTinderbox User hopefully during the one call. It also suppresses some of
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews the normal
a450977e98155f6e828fe6f8d52cf24674231831Mark Andrews zone maintenance traffic. The default is <strong class="userinput"><code>no</code></strong>.
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews </p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews<p>
dd65eb1efb40b1c47d57963192bfc54873b219beAutomatic Updater The <span class="command"><strong>dialup</strong></span> option
0d3490f93bb980fde704055e74c1b508987a5fe4Mark Andrews may also be specified in the <span class="command"><strong>view</strong></span> and
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <span class="command"><strong>zone</strong></span> statements,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater in which case it overrides the global <span class="command"><strong>dialup</strong></span>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User option.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews If the zone is a master zone, then the server will send out a
114f7780384371121918624ae2c80ecfce545683Tinderbox User NOTIFY
33d1cff1dd63494ffa00fac695a793f00c4ebf0bTinderbox User request to all the slaves (default). This should trigger the
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater zone serial
169f44b082b340b952e26c0fdb930c102a957752Mark Andrews number check in the slave (providing it supports NOTIFY)
8f1a00cf8b3d9dc8d419a797b7ff4fb6ddba428eTinderbox User allowing the slave
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User to verify the zone while the connection is active.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User The set of servers to which NOTIFY is sent can be controlled
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User by
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User <span class="command"><strong>notify</strong></span> and <span class="command"><strong>also-notify</strong></span>.
169f44b082b340b952e26c0fdb930c102a957752Mark Andrews </p>
757ff043760e4743dda1a10e7d58349275934902Tinderbox User<p>
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt If the
e64202536ea72d8f371dd0df9fc763f8d70bf886Tinderbox User zone is a slave or stub zone, then the server will suppress
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt the regular
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont "zone up to date" (refresh) queries and only perform them
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User when the
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User <span class="command"><strong>heartbeat-interval</strong></span> expires in
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User addition to sending
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User NOTIFY requests.
1404d301dd9e7e487a247b803f63909cd10cdf72Tinderbox User </p>
36c0c1405d4dd31afaf614668f4512e69637e159Tinderbox User<p>
904890e38b74005395451501400718d759bfc064Tinderbox User Finer control can be achieved by using
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <strong class="userinput"><code>notify</code></strong> which only sends NOTIFY
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User messages,
646fed0d28be4387e3e32fb0f5732a1f58b572baTinderbox User <strong class="userinput"><code>notify-passive</code></strong> which sends NOTIFY
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews messages and
19ad308d84cbf446a144e5a91f2032389a9d65c1Tinderbox User suppresses the normal refresh queries, <strong class="userinput"><code>refresh</code></strong>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont which suppresses normal refresh processing and sends refresh
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User queries
42c81cf2de732ec6d00e73fc755a399ca037e543Mark Andrews when the <span class="command"><strong>heartbeat-interval</strong></span>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User expires, and
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <strong class="userinput"><code>passive</code></strong> which just disables normal
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User refresh
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt processing.
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt </p>
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt<div class="informaltable"><table border="1">
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt<colgroup>
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt<col width="1.150in" class="1">
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt<col width="1.150in" class="2">
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<col width="1.150in" class="3">
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<col width="1.150in" class="4">
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater</colgroup>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<tbody>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews<tr>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews<td>
71fc4775d04aea66809e3eb5b5159c55413bdc5cMark Andrews <p>
7d704e522860496310bb29c28e76064868401a9cMark Andrews dialup mode
7d704e522860496310bb29c28e76064868401a9cMark Andrews </p>
cc17f4a672fc4ce67327902dd797c4465f12c4c9Mark Andrews </td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater normal refresh
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<td>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater <p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater heart-beat refresh
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater </p>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater </td>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater<td>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater <p>
66cf4a406525db9c42977d8034a60e0a8e2a9290Automatic Updater heart-beat notify
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </td>
b7fcdb0bee7680fe9536bec3b204aea094bc514eTinderbox User</tr>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<tr>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p><span class="command"><strong>no</strong></span> (default)</p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<td>
da24e725ff982595d74da7e75e9fbd6a696367ccAutomatic Updater <p>
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews yes
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
28e0061dbcc2ae45d34541267a00d8b4de5b4a41Tinderbox User </td>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<td>
27c3c21f41520e8d6336d80a8094389e321cb6d2Mark Andrews <p>
d2f313886122eeb989e5c58cd9a70373222210c4Tinderbox User no
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews no
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </td>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User</tr>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<tr>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson<td>
5e82fe9a56d17bfbd120817d00d28c5952ab4ddcTinderbox User <p><span class="command"><strong>yes</strong></span></p>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User </td>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<td>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <p>
8bc3d252395842452a6d2c775cf8445f6349e331Tinderbox User no
735e1ed9685077e25f744d692acf77c5bf5d4490Tinderbox User </p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
7d19af23a7cff2908a35657dc3e35d1e6fbac2c1Tinderbox User <p>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User yes
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User </p>
757ff043760e4743dda1a10e7d58349275934902Tinderbox User </td>
da59e63e7af147a8bcef985b98b04443e04c3a0eTinderbox User<td>
0e573cdd111e060e5f6c18249b5ccacbe8abe278Tinderbox User <p>
4c6bae917bec70e1fc4d1b761a9765075af78441Tinderbox User yes
6ee455a915d0e5cab50865da23152efe59ea1decTinderbox User </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
4c9f230f7ca5b2b08ea8fd7a6944135801dbe152Tinderbox User</tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<tr>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p><span class="command"><strong>notify</strong></span></p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </td>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews<td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater yes
8f1a00cf8b3d9dc8d419a797b7ff4fb6ddba428eTinderbox User </p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater </td>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt<td>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt <p>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt no
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User </p>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt </td>
a8677ecad546c955406b341eb8344ed06768b11eTinderbox User<td>
a8677ecad546c955406b341eb8344ed06768b11eTinderbox User <p>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt yes
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt </p>
0e573cdd111e060e5f6c18249b5ccacbe8abe278Tinderbox User </td>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt</tr>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<tr>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<td>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt <p><span class="command"><strong>refresh</strong></span></p>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt </td>
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User<td>
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews <p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews no
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews </p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </td>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<td>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User <p>
603cf17f33da24d460616389ec40d6f2a6e110a0Automatic Updater yes
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User </p>
e64202536ea72d8f371dd0df9fc763f8d70bf886Tinderbox User </td>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews no
6d114a4c5cddb176ae5199eee154c0273d652ba4Tinderbox User </p>
6d114a4c5cddb176ae5199eee154c0273d652ba4Tinderbox User </td>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews</tr>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User<tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
7711228a135a2fe85765ba13a67b8e397ed73489Mark Andrews <p><span class="command"><strong>passive</strong></span></p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </td>
9692d283bb43c9eab49a7fadfc1b74a6e20e6151Tinderbox User<td>
b5423cbff7175727ed9046c8c670d8a7bb4d01eaTinderbox User <p>
c505effec1da6664c37f0e4dbfc1c4f6b0e73367Tinderbox User no
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont </p>
be0d1ec971748020cb0382e02b4642b493ea1e7bTinderbox User </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
22870a9f8df95488abe2b17ab92b7cb6a9fe6f14Tinderbox User <p>
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews no
6d114a4c5cddb176ae5199eee154c0273d652ba4Tinderbox User </p>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews </td>
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews<td>
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User <p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User no
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User </td>
365bb6f27eace1836cb5bc6b5f9ed8c88fe22e4aTinderbox User</tr>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User<tr>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<td>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews <p><span class="command"><strong>notify-passive</strong></span></p>
e64202536ea72d8f371dd0df9fc763f8d70bf886Tinderbox User </td>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater<td>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater <p>
be0d1ec971748020cb0382e02b4642b493ea1e7bTinderbox User no
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews </td>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<td>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User <p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater no
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews </p>
9692d283bb43c9eab49a7fadfc1b74a6e20e6151Tinderbox User </td>
b5423cbff7175727ed9046c8c670d8a7bb4d01eaTinderbox User<td>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater <p>
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater yes
be0d1ec971748020cb0382e02b4642b493ea1e7bTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </td>
6d114a4c5cddb176ae5199eee154c0273d652ba4Tinderbox User</tr>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</tbody>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater</table></div>
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews<p>
b871c7156eb037d41f53828c6fcb9cc876128962Mark Andrews Note that normal NOTIFY processing is not affected by
7af91d15b2ce1ce32f7320f6d5cc3b83621c241aAutomatic Updater <span class="command"><strong>dialup</strong></span>.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews </p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews</dd>
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews<dt><span class="term"><span class="command"><strong>fake-iquery</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater In <acronym class="acronym">BIND</acronym> 8, this option
0accdb26ead1fe520a9820b52efbea64bdf564e3Tinderbox User enabled simulating the obsolete DNS query type
8b8e37f252b0411e00a0a2775d570562aedce439Tinderbox User IQUERY. <acronym class="acronym">BIND</acronym> 9 never does
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater IQUERY simulation.
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>fetch-glue</strong></span></span></dt>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater<dd><p>
2ba8f584b97cbab864570e38fd26b8cb90961428Tinderbox User This option is obsolete.
950d203b64f512b85fcc093ee1e9e3e531a1aea3Tinderbox User In BIND 8, <strong class="userinput"><code>fetch-glue yes</code></strong>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater caused the server to attempt to fetch glue resource records
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews it
ba8b771c371967dd1254c7fa82ebe4158ee04b24Tinderbox User didn't have when constructing the additional
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews data section of a response. This is now considered a bad
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater idea
098097efb95046a4a5285b6dae95dea3e3b70853Automatic Updater and BIND 9 never does it.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
2964b1f272bab3e7ed3fbb4a0811da5e93646d34Tinderbox User<dt><span class="term"><span class="command"><strong>flush-zones-on-shutdown</strong></span></span></dt>
78bc8fdc2488c92d7228e8de19827e2c114c56caAutomatic Updater<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater When the nameserver exits due receiving SIGTERM,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater flush or do not flush any pending zone writes. The default
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater is
0d13a9584b9f97693ab22d54322f1c484d578701Mark Andrews <span class="command"><strong>flush-zones-on-shutdown</strong></span> <strong class="userinput"><code>no</code></strong>.
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User </p></dd>
59528addd704f8d5757b54e540520f74e588a7c7Automatic Updater<dt><span class="term"><span class="command"><strong>geoip-use-ecs</strong></span></span></dt>
0d13a9584b9f97693ab22d54322f1c484d578701Mark Andrews<dd><p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User When BIND is compiled with GeoIP support and configured
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater with "geoip" ACL elements, this option indicates whether
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User the EDNS Client Subnet option, if present in a request,
1fff4d36fb18ccdca15acb0bae20c2aa8e833ceeTinderbox User should be used for matching against the GeoIP database.
11b6b0d74bb8dd6bd1ce0b60ba7f9b66323f06d4Tinderbox User The default is
7f79131f9a8e804b93c57f3c679065cce878b726Automatic Updater <span class="command"><strong>geoip-use-ecs</strong></span> <strong class="userinput"><code>yes</code></strong>.
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews </p></dd>
609b8d08176469485edce25f3c2f50365bbd3819Mark Andrews<dt><span class="term"><span class="command"><strong>has-old-clients</strong></span></span></dt>
e705db6d5d886dc14f4a75a2046a075c0750e7eeAutomatic Updater<dd><p>
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User This option was incorrectly implemented
a8677ecad546c955406b341eb8344ed06768b11eTinderbox User in <acronym class="acronym">BIND</acronym> 8, and is ignored by <acronym class="acronym">BIND</acronym> 9.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater To achieve the intended effect
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews of
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater <span class="command"><strong>has-old-clients</strong></span> <strong class="userinput"><code>yes</code></strong>, specify
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews the two separate options <span class="command"><strong>auth-nxdomain</strong></span> <strong class="userinput"><code>yes</code></strong>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews and <span class="command"><strong>rfc2308-type1</strong></span> <strong class="userinput"><code>no</code></strong> instead.
2964b1f272bab3e7ed3fbb4a0811da5e93646d34Tinderbox User </p></dd>
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User<dt><span class="term"><span class="command"><strong>host-statistics</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User In BIND 8, this enables keeping of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater statistics for every host that the name server interacts
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews with.
fedd407a76adfdd745eb7d2461673693c6f9fea9Mark Andrews Not implemented in BIND 9.
1921b850640ae984448e8b87870c8527fa9cddb6Evan Hunt </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span class="command"><strong>maintain-ixfr-base</strong></span></span></dt>
955ee8b865d70d02ad1fdc959382e6f8a07c1d14Tinderbox User<dd><p>
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span class="emphasis"><em>This option is obsolete</em></span>.
a7c412f37cc73d0332887a746e81220cbf09dd00Mark Andrews It was used in <acronym class="acronym">BIND</acronym> 8 to
51374c645c0e6dd77c369c13834c751785f96f14Tinderbox User determine whether a transaction log was
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater kept for Incremental Zone Transfer. <acronym class="acronym">BIND</acronym> 9 maintains a transaction
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater log whenever possible. If you need to disable outgoing
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User incremental zone
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt transfers, use <span class="command"><strong>provide-ixfr</strong></span> <strong class="userinput"><code>no</code></strong>.
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt </p></dd>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<dt><span class="term"><span class="command"><strong>message-compression</strong></span></span></dt>
a8677ecad546c955406b341eb8344ed06768b11eTinderbox User<dd><p>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User If <strong class="userinput"><code>yes</code></strong>, DNS name compression is
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt used in responses to regular queries (not including
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt AXFR or IXFR, which always uses compression). Setting
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt this option to <strong class="userinput"><code>no</code></strong> reduces CPU
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User usage on servers and may improve throughput. However,
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater it increases response size, which may cause more queries
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User to be processed using TCP; a server with compression
2bb3422dc683c013db7042f5736240de6b86f182Automatic Updater disabled is out of compliance with RFC 1123 Section
c855e7170a7ddb5d4ebab69a771f35dc93e95e43Mark Andrews 6.1.3.2. The default is <strong class="userinput"><code>yes</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<dt><span class="term"><span class="command"><strong>minimal-responses</strong></span></span></dt>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dd><p>
a907c61823c4715248b259c4d495fc0c9d1b9889Tinderbox User If <strong class="userinput"><code>yes</code></strong>, then when generating
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User responses the server will only add records to the authority
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User and additional data sections when they are required (e.g.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User delegations, negative responses). This may improve the
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User performance of the server.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default is <strong class="userinput"><code>no</code></strong>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
2964b1f272bab3e7ed3fbb4a0811da5e93646d34Tinderbox User<dt><span class="term"><span class="command"><strong>minimal-any</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User If set to <strong class="userinput"><code>yes</code></strong>, then when
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater generating a positive response to a query of type
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User ANY over UDP, the server will reply with only one
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User of the RRsets for the query name, and its covering
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User RRSIGs if any, instead of replying with all known
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater RRsets for the name. Similarly, a query for type
137fdbc214e99c4cbe57551e9e14f2015c2e42aeTinderbox User RRSIG will be answered with the RRSIG records covering
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater only one type. This can reduce the impact of some kinds
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User of attack traffic, without harming legitimate
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User clients. (Note, however, that the RRset returned is the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater first one found in the database; it is not necessarily
e64202536ea72d8f371dd0df9fc763f8d70bf886Tinderbox User the smallest available RRset.)
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Additionally, <code class="option">minimal-responses</code> is
4cde88fbf4c5e78a785d40f364cdcf60f3575f0cTinderbox User turned on for these queries, so no unnecessary records
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater will be added to the authority or additional sections.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default is <strong class="userinput"><code>no</code></strong>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
1ac49378a458420bc685293d12e567d7222d17b6Tinderbox User<dt><span class="term"><span class="command"><strong>multiple-cnames</strong></span></span></dt>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<dd><p>
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User This option was used in <acronym class="acronym">BIND</acronym> 8 to allow
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews a domain name to have multiple CNAME records in violation of
681beefc668253b3e469a1de282fbc33a3752422Automatic Updater the DNS standards. <acronym class="acronym">BIND</acronym> 9.2 onwards
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User always strictly enforces the CNAME rules both in master
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User files and dynamic updates.
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span class="command"><strong>notify</strong></span></span></dt>
0d13a9584b9f97693ab22d54322f1c484d578701Mark Andrews<dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<p>
b3386fba31414344f38f0c30849c056dceb22dceTinderbox User If <strong class="userinput"><code>yes</code></strong> (the default),
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User DNS NOTIFY messages are sent when a zone the server is
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User authoritative for
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater changes, see <a class="xref" href="Bv9ARM.ch04.html#notify" title="Notify">the section called &#8220;Notify&#8221;</a>. The messages are
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater sent to the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater servers listed in the zone's NS records (except the master
4cde88fbf4c5e78a785d40f364cdcf60f3575f0cTinderbox User server identified
572048aa7bf7b449d60dfb2dbebf861454626f96Tinderbox User in the SOA MNAME field), and to any servers listed in the
83e281baf1b4149dc637d24dd41141129ae712c6Tinderbox User <span class="command"><strong>also-notify</strong></span> option.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User<p>
9e898948ed76bf5f175bf178866c90c449843c3eTinderbox User If <strong class="userinput"><code>master-only</code></strong>, notifies are only
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User sent
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater for master zones.
33d1cff1dd63494ffa00fac695a793f00c4ebf0bTinderbox User If <strong class="userinput"><code>explicit</code></strong>, notifies are sent only
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User servers explicitly listed using <span class="command"><strong>also-notify</strong></span>.
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont If <strong class="userinput"><code>no</code></strong>, no notifies are sent.
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User The <span class="command"><strong>notify</strong></span> option may also be
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User specified in the <span class="command"><strong>zone</strong></span>
2964b1f272bab3e7ed3fbb4a0811da5e93646d34Tinderbox User statement,
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews in which case it overrides the <span class="command"><strong>options notify</strong></span> statement.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User It would only be necessary to turn off this option if it
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User caused slaves
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User to crash.
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews </p>
9e8ee4ffd77aa2974cecbdbb2b122156b8d3a27aTinderbox User</dd>
6d114a4c5cddb176ae5199eee154c0273d652ba4Tinderbox User<dt><span class="term"><span class="command"><strong>notify-to-soa</strong></span></span></dt>
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User<dd><p>
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User If <strong class="userinput"><code>yes</code></strong> do not check the nameservers
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews in the NS RRset against the SOA MNAME. Normally a NOTIFY
71fa3534bfaf174f6a938dc1ba3522f66606c4e1Mark Andrews message is not sent to the SOA MNAME (SOA ORIGIN) as it is
ca5ba35827e475a824ec79d489dbcdb3341a35ccTinderbox User supposed to contain the name of the ultimate master.
1fdd58445074579ee3b65c871137a7a1740eb542Mark Andrews Sometimes, however, a slave is listed as the SOA MNAME in
e08cdffb3ae4ad409f37e3e5a218fe4b7e0e3904Tinderbox User hidden master configurations and in that case you would
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews want the ultimate master to still send NOTIFY messages to
9e295ad801d5c986eb6c7745637b5dc0efb28711Tinderbox User all the nameservers listed in the NS RRset.
9692d283bb43c9eab49a7fadfc1b74a6e20e6151Tinderbox User </p></dd>
5ee9f7f23852d92772c08ca6e4b46c549beaf660Mark Andrews<dt><span class="term"><span class="command"><strong>recursion</strong></span></span></dt>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<dd><p>
757ff043760e4743dda1a10e7d58349275934902Tinderbox User If <strong class="userinput"><code>yes</code></strong>, and a
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User DNS query requests recursion, then the server will attempt
b6e12209e3e7df826f5f8f949ad400ec6d1f6371Tinderbox User to do
e08cdffb3ae4ad409f37e3e5a218fe4b7e0e3904Tinderbox User all the work required to answer the query. If recursion is
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User off
fe600c3ad88c0bb078283a953d048087d227c0e5Tinderbox User and the server does not already know the answer, it will
0d13a9584b9f97693ab22d54322f1c484d578701Mark Andrews return a
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User referral response. The default is
316cd2460aa66e157f72890974ca5c21d65e70e6Tinderbox User <strong class="userinput"><code>yes</code></strong>.
646fed0d28be4387e3e32fb0f5732a1f58b572baTinderbox User Note that setting <span class="command"><strong>recursion no</strong></span> does not prevent
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont clients from getting data from the server's cache; it only
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User prevents new data from being cached as an effect of client
5a6d22a5b3b014f6dd0b36999864bd2c3e0d8465Mark Andrews queries.
2964b1f272bab3e7ed3fbb4a0811da5e93646d34Tinderbox User Caching may still occur as an effect the server's internal
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont operation, such as NOTIFY address lookups.
049728912c39135db248f9b48f8f26675f456e9dTinderbox User </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span class="command"><strong>request-nsid</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
5ee9f7f23852d92772c08ca6e4b46c549beaf660Mark Andrews If <strong class="userinput"><code>yes</code></strong>, then an empty EDNS(0)
4aec4843241dca64de7eb6363944df0b09cb83ecTinderbox User NSID (Name Server Identifier) option is sent with all
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont queries to authoritative name servers during iterative
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater resolution. If the authoritative server returns an NSID
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews option in its response, then its contents are logged in
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews the <span class="command"><strong>resolver</strong></span> category at level
af60449fe472b8bea5ad04bf538c777c6b151112Tinderbox User <span class="command"><strong>info</strong></span>.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User The default is <strong class="userinput"><code>no</code></strong>.
a80993946f29ff39df38818ee9b2e58a4e46cb7eTinderbox User </p></dd>
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User<dt><span class="term"><span class="command"><strong>request-sit</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd><p>
4f538e852f20912e629338e911e46ce26de3e965Tinderbox User This experimental option is obsolete.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<dt><span class="term"><span class="command"><strong>require-server-cookie</strong></span></span></dt>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<dd><p>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont Require a valid server cookie before sending a full
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User response to a UDP request from a cookie aware client.
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User BADCOOKIE is sent if there is a bad or no existent
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater server cookie.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>send-cookie</strong></span></span></dt>
fae2925c4d1b45056302be96e5e334f3ad5809c5Tinderbox User<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater If <strong class="userinput"><code>yes</code></strong>, then a COOKIE EDNS
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater option is sent along with the query. If the
c288e47fb7d4baa1ed887156b1c5e5db394d4f52Tinderbox User resolver has previously talked to the server, the
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User COOKIE returned in the previous transaction is sent.
90ff38a0d8deaf5f9c2aa5916d99b2e572d28738Automatic Updater This is used by the server to determine whether
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the resolver has talked to it before. A resolver
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt sending the correct COOKIE is assumed not to be an
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt off-path attacker sending a spoofed-source query;
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt the query is therefore unlikely to be part of a
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User reflection/amplification attack, so resolvers
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater sending a correct COOKIE option are not subject to
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater response rate limiting (RRL). Resolvers which
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews do not send a correct COOKIE option may be limited
39ae0eafed076ef769fef5c18b22a8051df5c93aTinderbox User to receiving smaller responses via the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>nocookie-udp-size</strong></span> option.
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt </p></dd>
ce0fd07045292942bfa3e755d9ce596941528a63Automatic Updater<dt><span class="term"><span class="command"><strong>nocookie-udp-size</strong></span></span></dt>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User<dd><p>
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater Sets the maximum size of UDP responses that will be
6ee455a915d0e5cab50865da23152efe59ea1decTinderbox User sent to queries without a valid server COOKIE. A value
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater below 128 will be silently raised to 128. The default
96713299d08c0735c18ebe8772dd2cc1ecd4356aAutomatic Updater value is 4096, but the <span class="command"><strong>max-udp-size</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater option may further limit the response size.
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>sit-secret</strong></span></span></dt>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<dd><p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews This experimental option is obsolete.
0e573cdd111e060e5f6c18249b5ccacbe8abe278Tinderbox User </p></dd>
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater<dt><span class="term"><span class="command"><strong>cookie-algorithm</strong></span></span></dt>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<dd><p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews Set the algorithm to be used when generating the
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User server cookie. One of "aes", "sha1" or "sha256".
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default is "aes" if supported by the cryptographic
4f538e852f20912e629338e911e46ce26de3e965Tinderbox User library or otherwise "sha256".
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p></dd>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User<dt><span class="term"><span class="command"><strong>cookie-secret</strong></span></span></dt>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<dd><p>
1bf507ca635310b340aea42d6c3e567819974a99Tinderbox User If set, this is a shared secret used for generating
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and verifying Source Identity Token EDNS options
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater within an anycast cluster. If not set, the system
c6517a807173827b8f638d31303805ee4c1d8054Automatic Updater will generate a random secret at startup. The
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater shared secret is encoded as a hex string and needs
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater to be 128 bits for AES128, 160 bits for SHA1 and
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User 256 bits for SHA256.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater<dt><span class="term"><span class="command"><strong>rfc2308-type1</strong></span></span></dt>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Setting this to <strong class="userinput"><code>yes</code></strong> will
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews cause the server to send NS records along with the SOA
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater record for negative
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater answers. The default is <strong class="userinput"><code>no</code></strong>.
ecbc7ebb243a1f8a5dc6f28185ffe9e61d3b2102Mark Andrews </p>
0ead2ac0a4b59c3e4a731027f0f66fbe602b1289Tinderbox User<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<h3 class="title">Note</h3>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater Not yet implemented in <acronym class="acronym">BIND</acronym>
d98b4b724343547314bde32a54966c8f124a5f03Mark Andrews 9.
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt </p>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User</div>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt</dd>
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt<dt><span class="term"><span class="command"><strong>use-id-pool</strong></span></span></dt>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont<dd><p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="emphasis"><em>This option is obsolete</em></span>.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <acronym class="acronym">BIND</acronym> 9 always allocates query
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater IDs from a pool.
1bcc3273a80c256f11d9098a00ba2c041939e233Mark Andrews </p></dd>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<dt><span class="term"><span class="command"><strong>use-ixfr</strong></span></span></dt>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<dd><p>
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson <span class="emphasis"><em>This option is obsolete</em></span>.
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User If you need to disable IXFR to a particular server or
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User servers, see
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User the information on the <span class="command"><strong>provide-ixfr</strong></span> option
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews in <a class="xref" href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called &#8220;<span class="command"><strong>server</strong></span> Statement Definition and
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews Usage&#8221;</a>.
6e38a18aef54c7f0ab35576e0fedf65d6ee84214Tinderbox User See also
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User <a class="xref" href="Bv9ARM.ch04.html#incremental_zone_transfers" title="Incremental Zone Transfers (IXFR)">the section called &#8220;Incremental Zone Transfers (IXFR)&#8221;</a>.
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews </p></dd>
f520803b46dc189fdaf84adc87ef327d3587b435Mark Andrews<dt><span class="term"><span class="command"><strong>provide-ixfr</strong></span></span></dt>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<dd><p>
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews See the description of
dbb012765c735ee0d82dedb116cdc7cf18957814Evan Hunt <span class="command"><strong>provide-ixfr</strong></span> in
e705db6d5d886dc14f4a75a2046a075c0750e7eeAutomatic Updater <a class="xref" href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called &#8220;<span class="command"><strong>server</strong></span> Statement Definition and
bac4435d473c9a0281507524f084480c34aa942aTinderbox User Usage&#8221;</a>.
04bc14c887243e624469fdbd336c1d3cb8ed7cc7Tinderbox User </p></dd>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="term"><span class="command"><strong>request-ixfr</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
757ff043760e4743dda1a10e7d58349275934902Tinderbox User See the description of
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <span class="command"><strong>request-ixfr</strong></span> in
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater <a class="xref" href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called &#8220;<span class="command"><strong>server</strong></span> Statement Definition and
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt Usage&#8221;</a>.
f2770f6b39a9b2a98afb7a11ed105f73f1570c1eAutomatic Updater </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>request-expire</strong></span></span></dt>
bac4435d473c9a0281507524f084480c34aa942aTinderbox User<dd><p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User See the description of
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <span class="command"><strong>request-expire</strong></span> in
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User <a class="xref" href="Bv9ARM.ch06.html#server_statement_definition_and_usage" title="server Statement Definition and Usage">the section called &#8220;<span class="command"><strong>server</strong></span> Statement Definition and
1bf507ca635310b340aea42d6c3e567819974a99Tinderbox User Usage&#8221;</a>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User<dt><span class="term"><span class="command"><strong>treat-cr-as-space</strong></span></span></dt>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<dd><p>
1bf507ca635310b340aea42d6c3e567819974a99Tinderbox User This option was used in <acronym class="acronym">BIND</acronym>
df3e5272b491e553904437a282a1fa0a1c2746e5Tinderbox User 8 to make
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont the server treat carriage return ("<span class="command"><strong>\r</strong></span>") characters the same way
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User as a space or tab character,
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews to facilitate loading of zone files on a UNIX system that
bcb68be0a8f3c3eca58d6a6a869267e5c1841de2Francis Dupont were generated
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater on an NT or DOS machine. In <acronym class="acronym">BIND</acronym> 9, both UNIX "<span class="command"><strong>\n</strong></span>"
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User and NT/DOS "<span class="command"><strong>\r\n</strong></span>" newlines
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User are always accepted,
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater and the option is ignored.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p></dd>
b779e1efb14f9616a35befd2b1cfc2578f1a4d70Tinderbox User<dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<span class="term"><span class="command"><strong>additional-from-auth</strong></span>, </span><span class="term"><span class="command"><strong>additional-from-cache</strong></span></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater</dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater These options control the behavior of an authoritative
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater server when
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater answering queries which have additional data, or when
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater following CNAME
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User and DNAME chains.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
f0c5e918974bf778af6cd1e25309ad13e30a79a6Tinderbox User When both of these options are set to <strong class="userinput"><code>yes</code></strong>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont (the default) and a
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater query is being answered from authoritative data (a zone
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater configured into the server), the additional data section of
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater the
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson reply will be filled in using data from other authoritative
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User zones
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson and from the cache. In some situations this is undesirable,
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews such
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User as when there is concern over the correctness of the cache,
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User or
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews in servers where slave zones may be added and modified by
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater untrusted third parties. Also, avoiding
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User the search for this additional data will speed up server
0bb05fe2c2fa40c635ddc5fa38ff65e523b11d8eEvan Hunt operations
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User at the possible expense of additional queries to resolve
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater what would
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User otherwise be provided in the additional section.
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User </p>
e213b38b48486b3a6349329655d9169085001fa0Tinderbox User<p>
933799f3641f4f78445d015008bad0038900a82aTinderbox User For example, if a query asks for an MX record for host <code class="literal">foo.example.com</code>,
9cd5eb6fe0f26d65724b99216cb31dcdd12e4afdAutomatic Updater and the record found is "<code class="literal">MX 10 mail.example.net</code>", normally the address
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User records (A and AAAA) for <code class="literal">mail.example.net</code> will be provided as well,
faa406d25d1d73b04a1351d1e62ab55557ed61ebAutomatic Updater if known, even though they are not in the example.com zone.
1a63fb1d1448ed3f8fd7227ae57be67c2e71279eMark Andrews Setting these options to <span class="command"><strong>no</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater disables this behavior and makes
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater the server only search for additional data in the zone it
933799f3641f4f78445d015008bad0038900a82aTinderbox User answers from.
933799f3641f4f78445d015008bad0038900a82aTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater These options are intended for use in authoritative-only
933799f3641f4f78445d015008bad0038900a82aTinderbox User servers, or in authoritative-only views. Attempts to set
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User them to <span class="command"><strong>no</strong></span> without also
e4757e3dafe50ae59f693eec828f68c42c197a70Andreas Gustafsson specifying
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews <span class="command"><strong>recursion no</strong></span> will cause the
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User server to
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User ignore the options and log a warning message.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
a04588e781b513ae3b30e061ac98035802b5e8e8Mark Andrews Specifying <span class="command"><strong>additional-from-cache no</strong></span> actually
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User disables the use of the cache not only for additional data
76fbdc591b3d46df28878a6ff844798622b85265Tinderbox User lookups
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User but also when looking up the answer. This is usually the
a04588e781b513ae3b30e061ac98035802b5e8e8Mark Andrews desired
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User behavior in an authoritative-only server where the
a900e4f99ff134b567b6df5ac2c841c7d0c551d3Automatic Updater correctness of
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User the cached data is an issue.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User When a name server is non-recursively queried for a name
5b4ef313da4283079786e516b4b07a1691e1dc50Mark Andrews that is not
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User below the apex of any served zone, it normally answers with
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont an
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User "upwards referral" to the root servers or the servers of
c288e47fb7d4baa1ed887156b1c5e5db394d4f52Tinderbox User some other
a900e4f99ff134b567b6df5ac2c841c7d0c551d3Automatic Updater known parent of the query name. Since the data in an
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater upwards referral
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater comes from the cache, the server will not be able to provide
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater upwards
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater referrals when <span class="command"><strong>additional-from-cache no</strong></span>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater has been specified. Instead, it will respond to such
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater queries
4fda24d843edac463c98785ec0c850d912592dc1Tinderbox User with REFUSED. This should not cause any problems since
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User upwards referrals are not required for the resolution
a04588e781b513ae3b30e061ac98035802b5e8e8Mark Andrews process.
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater </p>
550d89df4dd30f214eedd18f399e280fd1b15953Evan Hunt</dd>
9563f388c8ca1bb9ebb04db54e122815b0008c8aTinderbox User<dt><span class="term"><span class="command"><strong>match-mapped-addresses</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User<p>
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User If <strong class="userinput"><code>yes</code></strong>, then an
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User IPv4-mapped IPv6 address will match any address match
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater list entries that match the corresponding IPv4 address.
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User </p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<p>
bcb68be0a8f3c3eca58d6a6a869267e5c1841de2Francis Dupont This option was introduced to work around a kernel quirk
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews in some operating systems that causes IPv4 TCP
bcb68be0a8f3c3eca58d6a6a869267e5c1841de2Francis Dupont connections, such as zone transfers, to be accepted on an
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews IPv6 socket using mapped addresses. This caused address
dc238a06bffa79de141ee7655765e2df91498a8aTinderbox User match lists designed for IPv4 to fail to match. However,
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User <span class="command"><strong>named</strong></span> now solves this problem
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews internally. The use of this option is discouraged.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews</dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<dt><span class="term"><span class="command"><strong>filter-aaaa-on-v4</strong></span></span></dt>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<dd>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews This option is only available when
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews <acronym class="acronym">BIND</acronym> 9 is compiled with the
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews <strong class="userinput"><code>--enable-filter-aaaa</code></strong> option on the
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews "configure" command line. It is intended to help the
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews transition from IPv4 to IPv6 by not giving IPv6 addresses
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews to DNS clients unless they have connections to the IPv6
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews Internet. This is not recommended unless absolutely
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews necessary. The default is <strong class="userinput"><code>no</code></strong>.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews The <span class="command"><strong>filter-aaaa-on-v4</strong></span> option
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews may also be specified in <span class="command"><strong>view</strong></span> statements
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews to override the global <span class="command"><strong>filter-aaaa-on-v4</strong></span>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews option.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews<p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews If <strong class="userinput"><code>yes</code></strong>,
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews the DNS client is at an IPv4 address, in <span class="command"><strong>filter-aaaa</strong></span>,
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews and if the response does not include DNSSEC signatures,
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews then all AAAA records are deleted from the response.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews This filtering applies to all responses and not only
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews authoritative responses.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews If <strong class="userinput"><code>break-dnssec</code></strong>,
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews then AAAA records are deleted even when DNSSEC is enabled.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews As suggested by the name, this makes the response not verify,
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews because the DNSSEC protocol is designed detect deletions.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews This mechanism can erroneously cause other servers to
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews not give AAAA records to their clients.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews A recursing server with both IPv6 and IPv4 network connections
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews that queries an authoritative server using this mechanism
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews via IPv4 will be denied AAAA records even if its client is
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews using IPv6.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews This mechanism is applied to authoritative as well as
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews non-authoritative records.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews A client using IPv4 that is not allowed recursion can
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews erroneously be given AAAA records because the server is not
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews allowed to check for A records.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews </p>
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews<p>
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews Some AAAA records are given to IPv4 clients in glue records.
c651f15b30f1dae5cc2f00878fb5da5b3a35a468Mark Andrews IPv4 clients that are servers can then erroneously
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater answer requests for AAAA records received via IPv4.
fca737c98d2be3ef944cc96320c040fdb5f160e3Tinderbox User </p>
e23256e740b238bddb4ba41ffac5f81a01c92245Automatic Updater</dd>
a04588e781b513ae3b30e061ac98035802b5e8e8Mark Andrews<dt><span class="term"><span class="command"><strong>filter-aaaa-on-v6</strong></span></span></dt>
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User<dd><p>
a04588e781b513ae3b30e061ac98035802b5e8e8Mark Andrews Identical to <span class="command"><strong>filter-aaaa-on-v4</strong></span>,
a04588e781b513ae3b30e061ac98035802b5e8e8Mark Andrews except it filters AAAA responses to queries from IPv6
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User clients instead of IPv4 clients. To filter all
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User responses, set both options to <strong class="userinput"><code>yes</code></strong>.
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User </p></dd>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dt><span class="term"><span class="command"><strong>ixfr-from-differences</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd>
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User When <strong class="userinput"><code>yes</code></strong> and the server loads a new
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User version of a master zone from its zone file or receives a
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User new version of a slave file via zone transfer, it will
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User compare the new version to the previous one and calculate
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater a set of differences. The differences are then logged in
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User the zone's journal file such that the changes can be
cd6e9010079a4e58f7e30063df3dec0ff154ad59Tinderbox User transmitted to downstream slaves as an incremental zone
f33f2b8afe60de897c53cdcb17911f10b552699fTinderbox User transfer.
397c35b074ed59592cac25bafeb7e082f50f9ac1Tinderbox User </p>
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User<p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson By allowing incremental zone transfers to be used for
b7f4a6fd8ac70ebf889179ee84c1dd35647bfc73Evan Hunt non-dynamic zones, this option saves bandwidth at the
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User expense of increased CPU and memory consumption at the
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User master.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews In particular, if the new version of a zone is completely
91d187ce035f39073f0732ff2a401a45c3c955fbMark Andrews different from the previous one, the set of differences
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont will be of a size comparable to the combined size of the
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater old and new zone version, and the server will need to
950d203b64f512b85fcc093ee1e9e3e531a1aea3Tinderbox User temporarily allocate memory to hold this complete
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews difference set.
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User </p>
e40c4e4c17d4df338e2a7db0f84d8dbb3858964cTinderbox User<p><span class="command"><strong>ixfr-from-differences</strong></span>
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont also accepts <span class="command"><strong>master</strong></span> and
22d32791e5daa0bc80335a0f10ab2de95f41ccdbTinderbox User <span class="command"><strong>slave</strong></span> at the view and options
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont levels which causes
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont <span class="command"><strong>ixfr-from-differences</strong></span> to be enabled for
3759f10fc543747668b1ca4b4671f35b0dea8445Francis Dupont all <span class="command"><strong>master</strong></span> or
a03cb08d0c4f1ca5fbc121d2f02bdffa7eb52286Mark Andrews <span class="command"><strong>slave</strong></span> zones respectively.
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt It is off by default.
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt </p>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt</dd>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<dt><span class="term"><span class="command"><strong>multi-master</strong></span></span></dt>
f190095cae5e5a8734e0ff16055488d471569499Tinderbox User<dd><p>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt This should be set when you have multiple masters for a zone
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt and the
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, <span class="command"><strong>named</strong></span> will
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt not log
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews when the serial number on the master is less than what <span class="command"><strong>named</strong></span>
f190095cae5e5a8734e0ff16055488d471569499Tinderbox User currently
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt has. The default is <strong class="userinput"><code>no</code></strong>.
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt </p></dd>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt<dt><span class="term"><span class="command"><strong>auto-dnssec</strong></span></span></dt>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt<dd>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews<p>
f190095cae5e5a8734e0ff16055488d471569499Tinderbox User Zones configured for dynamic DNS may use this
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt option to allow varying levels of automatic DNSSEC key
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt management. There are three possible settings:
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt </p>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt<p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <span class="command"><strong>auto-dnssec allow;</strong></span> permits
f190095cae5e5a8734e0ff16055488d471569499Tinderbox User keys to be updated and the zone fully re-signed
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt whenever the user issues the command <span class="command"><strong>rndc sign
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt <em class="replaceable"><code>zonename</code></em></strong></span>.
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt </p>
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt<p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <span class="command"><strong>auto-dnssec maintain;</strong></span> includes the
f190095cae5e5a8734e0ff16055488d471569499Tinderbox User above, but also automatically adjusts the zone's DNSSEC
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt keys on schedule, according to the keys' timing metadata
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt (see <a class="xref" href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt <a class="xref" href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a>). The command
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt <span class="command"><strong>rndc sign
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <em class="replaceable"><code>zonename</code></em></strong></span> causes
f190095cae5e5a8734e0ff16055488d471569499Tinderbox User <span class="command"><strong>named</strong></span> to load keys from the key
98922b2b2b024dcca25be7c220cf3b16b1e6c4b5Evan Hunt repository and sign the zone with all keys that are
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User active.
713c3d5b18463f2479973e4d14f73248e60a5df7Mark Andrews <span class="command"><strong>rndc loadkeys
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User <em class="replaceable"><code>zonename</code></em></strong></span> causes
03ebc228ee3725738b067b6bd7082a9a731822a1Tinderbox User <span class="command"><strong>named</strong></span> to load keys from the key
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User repository and schedule key maintenance events to occur
37d8e0a4455876fe1e4cca511076cc2c5ab9eedeTinderbox User in the future, but it does not sign the full zone
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews immediately. Note: once keys have been loaded for a
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews zone the first time, the repository will be searched
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews for changes periodically, regardless of whether
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews <span class="command"><strong>rndc loadkeys</strong></span> is used. The recheck
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews interval is defined by
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews <span class="command"><strong>dnssec-loadkeys-interval</strong></span>.)
280a8a0544b4aeb52414d20e8c6e6c5b1108562eTinderbox User </p>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<p>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater The default setting is <span class="command"><strong>auto-dnssec off</strong></span>.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews </p>
91216cff91b34c9ff6e846dc23f248219cafe660Andreas Gustafsson</dd>
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews<dt><span class="term"><span class="command"><strong>dnssec-enable</strong></span></span></dt>
ce9cad6bb04869c5e94d9dc721032b25117f9210Automatic Updater<dd><p>
e813f036c8251b6d9d2a72fa84f80c2c9d2795afMark Andrews This indicates whether DNSSEC-related resource
f190095cae5e5a8734e0ff16055488d471569499Tinderbox User records are to be returned by <span class="command"><strong>named</strong></span>.
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews If set to <strong class="userinput"><code>no</code></strong>,
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews <span class="command"><strong>named</strong></span> will not return DNSSEC-related
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews resource records unless specifically queried for.
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews The default is <strong class="userinput"><code>yes</code></strong>.
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews </p></dd>
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews<dt><span class="term"><span class="command"><strong>dnssec-validation</strong></span></span></dt>
bed0874e1a09e810575328c4bfc346a47514b69fMark Andrews<dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
710bce1a85c96e85ca1a90471382055acd29d51fTinderbox User Enable DNSSEC validation in <span class="command"><strong>named</strong></span>.
dedefc0bdbb4e6e39eeb98aa2fc6883efec2ddb0Mark Andrews Note <span class="command"><strong>dnssec-enable</strong></span> also needs to be
77932ac533c711eca5cd86de4e7eca8d91102b43Tinderbox User set to <strong class="userinput"><code>yes</code></strong> to be effective.
827f8cccb5280f4da66c46186e792d1cb9d73503Mark Andrews If set to <strong class="userinput"><code>no</code></strong>, DNSSEC validation
922e6a3c2ac4ef900dd9dc99f0cc137f18372583Andreas Gustafsson is disabled. If set to <strong class="userinput"><code>auto</code></strong>,
015055b6e23f5c08f6a5b34726f90b62597e9e45Tinderbox User DNSSEC validation is enabled, and a default
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox 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,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User but a trust anchor must be manually configured using
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User a <span class="command"><strong>trusted-keys</strong></span> or
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>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>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Whenever the resolver sends out queries to an
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User EDNS-compliant server, it always sets the DO bit
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User indicating it can support DNSSEC responses even if
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>dnssec-validation</strong></span> is off.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>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>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Setting this option to <strong class="userinput"><code>yes</code></strong>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews leaves <span class="command"><strong>named</strong></span> vulnerable to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User replay attacks.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>querylog</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specify whether query logging should be started when <span class="command"><strong>named</strong></span>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews starts.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <span class="command"><strong>querylog</strong></span> is not specified,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User then the query logging
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is determined by the presence of the logging category <span class="command"><strong>queries</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span class="command"><strong>check-names</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews This option is used to restrict the character set and syntax
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews of
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User certain domain names in master files and/or DNS responses
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User received
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from the network. The default varies according to usage
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User area. For
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>master</strong></span> zones the default is <span class="command"><strong>fail</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User For <span class="command"><strong>slave</strong></span> zones the default
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User is <span class="command"><strong>warn</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User For answers received from the network (<span class="command"><strong>response</strong></span>)
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the default is <span class="command"><strong>ignore</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The rules for legal hostnames and mail domains are derived
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User from RFC 952 and RFC 821 as modified by RFC 1123.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p><span class="command"><strong>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.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User 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 class="command"><strong>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 class="command"><strong>warn</strong></span>. Other possible
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User values are <span class="command"><strong>fail</strong></span> and
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>ignore</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>check-mx</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater Check whether the MX record appears to refer to a IP address.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The default is to <span class="command"><strong>warn</strong></span>. Other possible
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User values are <span class="command"><strong>fail</strong></span> and
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>ignore</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>check-wildcard</strong></span></span></dt>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This option is used to check for non-terminal wildcards.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater 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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>named-checkzone</strong></span>).
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The default is <span class="command"><strong>yes</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews The use of the SPF record for publishing Sender
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews 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
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews TXT record does not exist and can be suppressed with
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>check-spf</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>check-mx-cname</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <span class="command"><strong>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 class="command"><strong>warn</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span class="command"><strong>check-srv-cname</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <span class="command"><strong>check-integrity</strong></span> is set then
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User fail, warn or ignore SRV records that refer
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to CNAMES. The default is to <span class="command"><strong>warn</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>check-sibling</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User When performing integrity checks, also check that
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User sibling glue exists. The default is <span class="command"><strong>yes</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>check-spf</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If <span class="command"><strong>check-integrity</strong></span> is set then
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User check that there is a TXT Sender Policy Framework
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews record present (starts with "v=spf1") if there is an
d3be47a4a841ca6fc07e8f18004cf72174e2d117Tinderbox User SPF record present. The default is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>warn</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>zero-no-soa-ttl</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User When returning authoritative negative responses to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User SOA queries set the TTL of the SOA record returned in
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the authority section to zero.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The default is <span class="command"><strong>yes</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>zero-no-soa-ttl-cache</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User When caching a negative response to a SOA query
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews set the TTL to zero.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The default is <span class="command"><strong>no</strong></span>.
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>update-check-ksk</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
3d2e052eb879189e6d853097f8b568d887323bebTinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User When set to the default value of <code class="literal">yes</code>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User check the KSK bit in each key to determine how the key
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User should be used when generating RRSIGs for a secure zone.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Ordinarily, zone-signing keys (that is, keys without the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User KSK bit set) are used to sign the entire zone, while
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User key-signing keys (keys with the KSK bit set) are only
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User used to sign the DNSKEY RRset at the zone apex.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User However, if this option is set to <code class="literal">no</code>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User then the KSK bit is ignored; KSKs are treated as if they
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews were ZSKs and are used to sign the entire zone. This is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User similar to the <span class="command"><strong>dnssec-signzone -z</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User command line option.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User When this option is set to <code class="literal">yes</code>, there
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews must be at least two active keys for every algorithm
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User represented in the DNSKEY RRset: at least one KSK and one
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User ZSK per algorithm. If there is any algorithm for which
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User this requirement is not met, this option will be ignored
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User for that algorithm.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>dnssec-dnskey-kskonly</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User When this option and <span class="command"><strong>update-check-ksk</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User are both set to <code class="literal">yes</code>, only key-signing
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User keys (that is, keys with the KSK bit set) will be used
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to sign the DNSKEY RRset at the zone apex. Zone-signing
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User keys (keys without the KSK bit set) will be used to sign
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews the remainder of the zone, but not the DNSKEY RRset.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This is similar to the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>dnssec-signzone -x</strong></span> command line option.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The default is <span class="command"><strong>no</strong></span>. If
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>update-check-ksk</strong></span> is set to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <code class="literal">no</code>, this option is ignored.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span class="command"><strong>try-tcp-refresh</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Try to refresh the zone using TCP if UDP queries fail.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User For BIND 8 compatibility, the default is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>yes</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>dnssec-secure-to-insecure</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Allow a dynamic zone to transition from secure to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User insecure (i.e., signed to unsigned) by deleting all
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User of the DNSKEY records. The default is <span class="command"><strong>no</strong></span>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If set to <span class="command"><strong>yes</strong></span>, and if the DNSKEY RRset
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews at the zone apex is deleted, all RRSIG and NSEC records
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User will be removed from the zone as well.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User If the zone uses NSEC3, then it is also necessary to
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User delete the NSEC3PARAM RRset from the zone apex; this will
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User cause the removal of all corresponding NSEC3 records.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User (It is expected that this requirement will be eliminated
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User in a future release.)
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Note that if a zone has been configured with
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User <span class="command"><strong>auto-dnssec maintain</strong></span> and the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User private keys remain accessible in the key repository,
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews then the zone will be automatically signed again the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User next time <span class="command"><strong>named</strong></span> is started.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dd>
3e1a17d65ec6227900f388ba2f7561365f7d4f5cTinderbox User</dl></div>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="section">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="titlepage"><div><div><h4 class="title">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<a name="forwarding"></a>Forwarding</h4></div></div></div>
10702d681eb650391bcaa0e2704aa3cf2dbf0e98Mark Andrews<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User The forwarding facility can be used to create a large site-wide
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User cache on a few servers, reducing traffic over links to external
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews name servers. It can also be used to allow queries by servers that
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User do not have direct access to the Internet, but wish to look up
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User exterior
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User names anyway. Forwarding occurs only on those queries for which
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the server is not authoritative and does not have the answer in
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User its cache.
6fe48fb46e53ffc37542853a1edb74cb481b7d94Automatic Updater </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="variablelist"><dl class="variablelist">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>forward</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User This option is only meaningful if the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User forwarders list is not empty. A value of <code class="varname">first</code>,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User the default, causes the server to query the forwarders
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User first &#8212; and
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User if that doesn't answer the question, the server will then
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User look for
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews the answer itself. If <code class="varname">only</code> is
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User specified, the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User server will only query the forwarders.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>forwarders</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd><p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Specifies the IP addresses to be used
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User for forwarding. The default is the empty list (no
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews forwarding).
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews </p></dd>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</dl></div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Forwarding can also be configured on a per-domain basis, allowing
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User for the global forwarding options to be overridden in a variety
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User of ways. You can set particular domains to use different
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User forwarders,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User or have a different <span class="command"><strong>forward only/first</strong></span> behavior,
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User or not forward at all, see <a class="xref" href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone Statement Grammar">the section called &#8220;<span class="command"><strong>zone</strong></span>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Statement Grammar&#8221;</a>.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="section">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="titlepage"><div><div><h4 class="title">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<a name="dual_stack"></a>Dual-stack Servers</h4></div></div></div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Dual-stack servers are used as servers of last resort to work
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User around
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User problems in reachability due the lack of support for either IPv4
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User or IPv6
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User on the host machine.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="variablelist"><dl class="variablelist">
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dt><span class="term"><span class="command"><strong>dual-stack-servers</strong></span></span></dt>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<dd><p>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews Specifies host names or addresses of machines with access to
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews both IPv4 and IPv6 transports. If a hostname is used, the
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews server must be able
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User to resolve the name using only the transport it has. If the
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User machine is dual
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User stacked, then the <span class="command"><strong>dual-stack-servers</strong></span> have no effect unless
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User access to a transport has been disabled on the command line
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User (e.g. <span class="command"><strong>named -4</strong></span>).
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p></dd>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews</dl></div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User</div>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="section">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="titlepage"><div><div><h4 class="title">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<a name="access_control"></a>Access Control</h4></div></div></div>
e9ab17d95e4288ab5ddedb7c89a9588c13c74bddMark Andrews<p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User Access to the server can be restricted based on the IP address
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User of the requesting system. See <a class="xref" href="Bv9ARM.ch06.html#address_match_lists" title="Address Match Lists">the section called &#8220;Address Match Lists&#8221;</a> for
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User details on how to specify IP address lists.
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User </p>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<div class="variablelist"><dl class="variablelist">
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dt><span class="term"><span class="command"><strong>allow-notify</strong></span></span></dt>
9f6827a4afb75224214ea96452e787e7f710b8b6Tinderbox User<dd><p>
5ca309a0fb9a75162852653f881d1e6290e28c2aTinderbox User Specifies which hosts are allowed to
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater notify this server, a slave, of zone changes in addition
aa1d397c4736cd86540555193d71e55fa3b37b2aMark Andrews to the zone masters.
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater <span class="command"><strong>allow-notify</strong></span> may also be
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater specified in the
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater <span class="command"><strong>zone</strong></span> statement, in which case
2f60dbd3787caa91e8ab1d7ae39ea312ad5ba31fAutomatic Updater it overrides the
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <span class="command"><strong>options allow-notify</strong></span>
e676a596869d8a80a644c99a848afb53d1c5975eMark Andrews statement. It is only meaningful
081a44bd3019b18aec03c5c0746538fdc901da48Evan Hunt for a slave zone. If not specified, the default is to
ac2e2800b4ac9cbe4cb756d967f4583c611eb75eMark Andrews process notify messages
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User only from a zone's master.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User </p></dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span class="command"><strong>allow-query</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd>
be41770245bd56746fbb61f9b5ba0aca683f318eTinderbox User<p>
200a9e7da827b67d99193bf793aea9f3e3fa1b43Tinderbox User Specifies which hosts are allowed to ask ordinary
5f76877508748558eeb2e07254b0edbcbf2f2e43Tinderbox User DNS questions. <span class="command"><strong>allow-query</strong></span> may
af9dbf1ccdd53933aaae9300d13ce0965d39b067Evan Hunt also be specified in the <span class="command"><strong>zone</strong></span>
f32d9699320a279df50fae9ff48dbadef13f619fTinderbox User statement, in which case it overrides the
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <span class="command"><strong>options allow-query</strong></span> statement.
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User If not specified, the default is to allow queries
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User from all hosts.
f536382c59dd492a14667b753816d920f9981f1cTinderbox User </p>
8f2c45a35dd8c40bcc9caba8f7d40ce64fc27bcdAutomatic Updater<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
c505effec1da6664c37f0e4dbfc1c4f6b0e73367Tinderbox User<h3 class="title">Note</h3>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User <span class="command"><strong>allow-query-cache</strong></span> is now
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User used to specify access to the cache.
af9dbf1ccdd53933aaae9300d13ce0965d39b067Evan Hunt </p>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User</div>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User</dd>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dt><span class="term"><span class="command"><strong>allow-query-on</strong></span></span></dt>
b886b04d8d2b085cbf3e1bf4442dee87f43ba5e4Tinderbox User<dd>
f536382c59dd492a14667b753816d920f9981f1cTinderbox User<p>
82a986aaa5d3384a541b5a7d6dae8cf0726d6513Tinderbox User Specifies which local addresses can accept ordinary
3e9c07abfd4ad76b1f8085f0f96f5646f2d9e219Tinderbox User DNS questions. This makes it possible, for instance,
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User to allow queries on internal-facing interfaces but
0eb371ca0dab50ae3462e98794a6126198c52f4bMark Andrews disallow them on external-facing ones, without
ee11dfc481f2ef6a032a715454f6290961a722d2Tinderbox User necessarily knowing the internal network's addresses.
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User </p>
f190095cae5e5a8734e0ff16055488d471569499Tinderbox User<p>
ee11dfc481f2ef6a032a715454f6290961a722d2Tinderbox User Note that <span class="command"><strong>allow-query-on</strong></span> is only
ee11dfc481f2ef6a032a715454f6290961a722d2Tinderbox User checked for queries that are permitted by
16f6050f29b6b0422cee858e609f65e474e70ef2Tinderbox User <span class="command"><strong>allow-query</strong></span>. A query must be
5affecff6e148a8e124d03f5dbac0da11e30dcc5Tinderbox User allowed by both ACLs, or it will be refused.
4fe0411487e8e4401477684c0a2bac041ca7c2d5Tinderbox User </p>
27739dd25026283c24645c8a1044b95ef9eb5ac6Tinderbox User<p>
ee11dfc481f2ef6a032a715454f6290961a722d2Tinderbox User <span class="command"><strong>allow-query-on</strong></span> may
also be specified in the <span class="command"><strong>zone</strong></span>
statement, in which case it overrides the
<span class="command"><strong>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 class="command"><strong>allow-query-cache</strong></span> is
used to specify access to the cache.
</p>
</div>
</dd>
<dt><span class="term"><span class="command"><strong>allow-query-cache</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to get answers
from the cache. If <span class="command"><strong>allow-query-cache</strong></span>
is not set then <span class="command"><strong>allow-recursion</strong></span>
is used if set, otherwise <span class="command"><strong>allow-query</strong></span>
is used if set unless <span class="command"><strong>recursion no;</strong></span> is
set in which case <span class="command"><strong>none;</strong></span> is used,
otherwise the default (<span class="command"><strong>localnets;</strong></span>
<span class="command"><strong>localhost;</strong></span>) is used.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>localnets</strong></span> and
<span class="command"><strong>localhost</strong></span>.
</p></dd>
<dt><span class="term"><span class="command"><strong>allow-recursion</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to make recursive
queries through this server. If
<span class="command"><strong>allow-recursion</strong></span> is not set
then <span class="command"><strong>allow-query-cache</strong></span> is
used if set, otherwise <span class="command"><strong>allow-query</strong></span>
is used if set, otherwise the default
(<span class="command"><strong>localnets;</strong></span>
<span class="command"><strong>localhost;</strong></span>) is used.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="xref" 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 class="command"><strong>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 class="xref" 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 class="command"><strong>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 class="command"><strong>allow-transfer</strong></span></span></dt>
<dd><p>
Specifies which hosts are allowed to
receive zone transfers from the server. <span class="command"><strong>allow-transfer</strong></span> may
also be specified in the <span class="command"><strong>zone</strong></span>
statement, in which
case it overrides the <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>filter-aaaa</strong></span></span></dt>
<dd><p>
Specifies a list of addresses to which
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="interfaces"></a>Interfaces</h4></div></div></div>
<p>
The interfaces and ports that the server will answer queries
from may be specified using the <span class="command"><strong>listen-on</strong></span> option. <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>listen-on</strong></span> is specified, the
server will listen on port 53 on all IPv4 interfaces.
</p>
<p>
The <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>listen-on-v6</strong></span>
will be ignored, with a logged warning.
</p>
<p>
Multiple <span class="command"><strong>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="section">
<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 class="command"><strong>query-source</strong></span> specifies
the address and port used for such queries. For queries sent over
IPv6, there is a separate <span class="command"><strong>query-source-v6</strong></span> option.
If <span class="command"><strong>address</strong></span> is <span class="command"><strong>*</strong></span> (asterisk) or is omitted,
a wildcard IP address (<span class="command"><strong>INADDR_ANY</strong></span>)
will be used.
</p>
<p>
If <span class="command"><strong>port</strong></span> is <span class="command"><strong>*</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 class="command"><strong>use-v4-udp-ports</strong></span> (for IPv4)
and <span class="command"><strong>use-v6-udp-ports</strong></span> (for IPv6)
options, excluding the ranges specified in
the <span class="command"><strong>avoid-v4-udp-ports</strong></span>
and <span class="command"><strong>avoid-v6-udp-ports</strong></span> options, respectively.
</p>
<p>
The defaults of the <span class="command"><strong>query-source</strong></span> and
<span class="command"><strong>query-source-v6</strong></span> options
are:
</p>
<pre class="programlisting">query-source address * port *;
query-source-v6 address * port *;
</pre>
<p>
If <span class="command"><strong>use-v4-udp-ports</strong></span> or
<span class="command"><strong>use-v6-udp-ports</strong></span> is unspecified,
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>named</strong></span> is running; the new
range will automatically be applied when <span class="command"><strong>named</strong></span>
is reloaded.
It is encouraged to
configure <span class="command"><strong>use-v4-udp-ports</strong></span> and
<span class="command"><strong>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 class="command"><strong>named</strong></span> runs may prohibit the use
of some ports. For example, UNIX systems will not allow
<span class="command"><strong>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 class="command"><strong>avoid-v4-udp-ports</strong></span> and
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>query-source</strong></span> or
<span class="command"><strong>query-source-v6</strong></span> options;
it implicitly disables the use of randomized port numbers.
</p>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><span class="command"><strong>use-queryport-pool</strong></span></span></dt>
<dd><p>
This option is obsolete.
</p></dd>
<dt><span class="term"><span class="command"><strong>queryport-pool-ports</strong></span></span></dt>
<dd><p>
This option is obsolete.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>transfer-source</strong></span> and
<span class="command"><strong>notify-source</strong></span>.
</p>
</div>
</div>
<div class="section">
<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 class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>masters</strong></span> lists can be used.
</p>
<p>
If an <span class="command"><strong>also-notify</strong></span> list
is given in a <span class="command"><strong>zone</strong></span> statement,
it will override
the <span class="command"><strong>options also-notify</strong></span>
statement. When a <span class="command"><strong>zone notify</strong></span>
statement
is set to <span class="command"><strong>no</strong></span>, the IP
addresses in the global <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>serial-queries</strong></span></span></dt>
<dd><p>
In BIND 8, the <span class="command"><strong>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 class="command"><strong>serial-queries</strong></span> option.
Instead, it limits the rate at which the queries are sent
as defined using the <span class="command"><strong>serial-query-rate</strong></span> option.
</p></dd>
<dt><span class="term"><span class="command"><strong>transfer-format</strong></span></span></dt>
<dd><p>
Zone transfers can be sent using two different formats,
<span class="command"><strong>one-answer</strong></span> and
<span class="command"><strong>many-answers</strong></span>.
The <span class="command"><strong>transfer-format</strong></span> option is used
on the master server to determine which format it sends.
<span class="command"><strong>one-answer</strong></span> uses one DNS message per
resource record transferred.
<span class="command"><strong>many-answers</strong></span> packs as many resource
records as possible into a message.
<span class="command"><strong>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 class="command"><strong>many-answers</strong></span> format is also supported by
recent Microsoft Windows nameservers.
The default is <span class="command"><strong>many-answers</strong></span>.
<span class="command"><strong>transfer-format</strong></span> may be overridden on a
per-server basis by using the <span class="command"><strong>server</strong></span>
statement.
</p></dd>
<dt><span class="term"><span class="command"><strong>transfer-message-size</strong></span></span></dt>
<dd>
<p>
This is an upper bound on the uncompressed size of DNS
messages used in zone transfers over TCP. If a message
grows larger than this size, additional messages will be
used to complete the zone transfer. (Note, however,
that this is a hint, not a hard limit; if a message
contains a single resource record whose RDATA does not
fit within the size limit, a larger message will be
permitted so the record can be transferred.)
</p>
<p>
Valid values are between 512 and 65535 octets, and any
values outside that range will be adjusted to the nearest
value within it. The default is <code class="literal">20480</code>,
which was selected to improve message compression:
most DNS messages of this size will compress to less
than 16536 bytes. Larger messages cannot be compressed
as effectively, because 16536 is the largest permissible
compression offset pointer in a DNS message.
</p>
<p>
This option is mainly intended for server testing;
there is rarely any benefit in setting a value other
than the default.
</p>
</dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>transfers-per-ns</strong></span> may
be overridden on a per-server basis by using the <span class="command"><strong>transfers</strong></span> phrase
of the <span class="command"><strong>server</strong></span> statement.
</p></dd>
<dt><span class="term"><span class="command"><strong>transfer-source</strong></span></span></dt>
<dd>
<p><span class="command"><strong>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 class="command"><strong>allow-transfer</strong></span> option for the
zone being transferred, if one is specified. This
statement sets the
<span class="command"><strong>transfer-source</strong></span> for all zones,
but can be overridden on a per-view or per-zone
basis by including a
<span class="command"><strong>transfer-source</strong></span> statement within
the <span class="command"><strong>view</strong></span> or
<span class="command"><strong>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 class="command"><strong>transfer-source-v6</strong></span></span></dt>
<dd><p>
The same as <span class="command"><strong>transfer-source</strong></span>,
except zone transfers are performed using IPv6.
</p></dd>
<dt><span class="term"><span class="command"><strong>alt-transfer-source</strong></span></span></dt>
<dd>
<p>
An alternate transfer source if the one listed in
<span class="command"><strong>transfer-source</strong></span> fails and
<span class="command"><strong>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>
<p>
If you do not wish the alternate transfer source
to be used, you should set
<span class="command"><strong>use-alt-transfer-source</strong></span>
appropriately and you should not depend upon
getting an answer back to the first refresh
query.
</p>
</div>
</dd>
<dt><span class="term"><span class="command"><strong>alt-transfer-source-v6</strong></span></span></dt>
<dd><p>
An alternate transfer source if the one listed in
<span class="command"><strong>transfer-source-v6</strong></span> fails and
<span class="command"><strong>use-alt-transfer-source</strong></span> is
set.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>no</strong></span>
otherwise it defaults to
<span class="command"><strong>yes</strong></span> (for BIND 8
compatibility).
</p></dd>
<dt><span class="term"><span class="command"><strong>notify-source</strong></span></span></dt>
<dd>
<p><span class="command"><strong>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 class="command"><strong>masters</strong></span> zone clause or
in an <span class="command"><strong>allow-notify</strong></span> clause. This
statement sets the <span class="command"><strong>notify-source</strong></span>
for all zones, but can be overridden on a per-zone or
per-view basis by including a
<span class="command"><strong>notify-source</strong></span> statement within
the <span class="command"><strong>zone</strong></span> or
<span class="command"><strong>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 class="command"><strong>notify-source-v6</strong></span></span></dt>
<dd><p>
Like <span class="command"><strong>notify-source</strong></span>,
but applies to notify messages sent to IPv6 addresses.
</p></dd>
</dl></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="port_lists"></a>UDP Port Lists</h4></div></div></div>
<p>
<span class="command"><strong>use-v4-udp-ports</strong></span>,
<span class="command"><strong>avoid-v4-udp-ports</strong></span>,
<span class="command"><strong>use-v6-udp-ports</strong></span>, and
<span class="command"><strong>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 class="xref" 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 class="command"><strong>named</strong></span> will be in one
of the following ranges: 32768 to 39999, 40001 to 49999,
and 60001 to 65535.
</p>
<p>
<span class="command"><strong>avoid-v4-udp-ports</strong></span> and
<span class="command"><strong>avoid-v6-udp-ports</strong></span> can be used
to prevent <span class="command"><strong>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 class="command"><strong>use-v4-udp-ports</strong></span> and
<span class="command"><strong>use-v6-udp-ports</strong></span>, and the
<span class="command"><strong>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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="resource_limits"></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 class="command"><strong>1G</strong></span> can be used instead of
<span class="command"><strong>1073741824</strong></span> to specify a limit of
one
gigabyte. <span class="command"><strong>unlimited</strong></span> requests
unlimited use, or the
maximum available amount. <span class="command"><strong>default</strong></span>
uses the limit
that was in force when the server was started. See the description
of <span class="command"><strong>size_spec</strong></span> in <a class="xref" 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 class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>max-cache-size</strong></span> and
<span class="command"><strong>recursive-clients</strong></span>
options instead.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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="section">
<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 class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>max-journal-size</strong></span> performs a
similar function in BIND 9.
</p></dd>
<dt><span class="term"><span class="command"><strong>max-journal-size</strong></span></span></dt>
<dd><p>
Sets a maximum size for each journal file
(see <a class="xref" 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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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"><a name="cpq_term"></a><span class="command"><strong>clients-per-query</strong></span>, </span><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>max-clients-per-query</strong></span> is set to zero,
then there is no upper bound other than imposed by
<span class="command"><strong>recursive-clients</strong></span>.
</p>
</dd>
<dt>
<a name="fetches-per-zone"></a><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>fetches-per-server</strong></span>
is reduced for that server. If the timeout ratio
drops below a "low" threshold, then
<span class="command"><strong>fetches-per-server</strong></span> is increased.
The <span class="command"><strong>fetch-quota-params</strong></span> options
can be used to adjust the parameters for this
calculation.
</p>
</dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>named</strong></span> listens on, <span class="command"><strong>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 class="command"><strong>max-cache-size</strong></span></span></dt>
<dd><p>
The maximum amount of memory to use for the
server's cache, in bytes or % of total physical memory.
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>90%</code></strong>.
On systems where detection of amount of physical
memory is not supported values represented as %
fall back to unlimited.
Note that the detection of physical memory is done only
once at startup, so <span class="command"><strong>named</strong></span> will not
adjust the cache size if the amount of physical memory
is changed during runtime.
</p></dd>
<dt><span class="term"><span class="command"><strong>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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="intervals"></a>Periodic Task Intervals</h4></div></div></div>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>heartbeat-interval</strong></span></span></dt>
<dd><p>
The server will perform zone maintenance tasks
for all zones marked as <span class="command"><strong>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 class="command"><strong>interface-interval</strong></span></span></dt>
<dd><p>
The server will scan the network interface list
every <span class="command"><strong>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 class="command"><strong>listen-on</strong></span> configuration), and
will
stop listening on interfaces that have gone away.
</p></dd>
<dt><span class="term"><span class="command"><strong>statistics-interval</strong></span></span></dt>
<dd>
<p>
Name server statistics will be logged
every <span class="command"><strong>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="section">
<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 class="command"><strong>topology</strong></span> statement
takes an <span class="command"><strong>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 class="command"><strong>topology</strong></span> option
is not implemented in <acronym class="acronym">BIND</acronym> 9.
</p>
</div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="the_sortlist_statement"></a>The <span class="command"><strong>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 class="command"><strong>rrset-order</strong></span>
statement in <a class="xref" 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 class="command"><strong>sortlist</strong></span> statement (see below)
takes
an <span class="command"><strong>address_match_list</strong></span> and
interprets it even
more specifically than the <span class="command"><strong>topology</strong></span>
statement
does (<a class="xref" href="Bv9ARM.ch06.html#topology" title="Topology">the section called &#8220;Topology&#8221;</a>).
Each top level statement in the <span class="command"><strong>sortlist</strong></span> must
itself be an explicit <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>address_match_list</strong></span> in
a <span class="command"><strong>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="section">
<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 class="command"><strong>rrset-order</strong></span> statement permits
configuration
of the ordering of the records in a multiple record response.
See also the <span class="command"><strong>sortlist</strong></span> statement,
<a class="xref" href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called &#8220;The <span class="command"><strong>sortlist</strong></span> Statement&#8221;</a>.
</p>
<p>
An <span class="command"><strong>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 class="command"><strong>ANY</strong></span>.
If no type is specified, the default is <span class="command"><strong>ANY</strong></span>.
If no name is specified, the default is "<span class="command"><strong>*</strong></span>" (asterisk).
</p>
<p>
The legal values for <span class="command"><strong>ordering</strong></span> are:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col width="0.750in" class="1">
<col width="3.750in" class="2">
</colgroup>
<tbody>
<tr>
<td>
<p><span class="command"><strong>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 class="command"><strong>random</strong></span></p>
</td>
<td>
<p>
Records are returned in some random order.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="tuning"></a>Tuning</h4></div></div></div>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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">30</code>
seconds; any higher value will be silently
reduced. The default is <code class="literal">1</code>
second.
</p>
</dd>
<dt><span class="term"><span class="command"><strong>max-ncache-ttl</strong></span></span></dt>
<dd><p>
To reduce network traffic and increase performance,
the server stores negative answers. <span class="command"><strong>max-ncache-ttl</strong></span> is
used to set a maximum retention time for these answers in
the server
in seconds. The default
<span class="command"><strong>max-ncache-ttl</strong></span> is <code class="literal">10800</code> seconds (3 hours).
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="xref" 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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>rndc signing -list <em class="replaceable"><code>zone</code></em></strong></span>.
Once <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>rndc signing -clear all <em class="replaceable"><code>zone</code></em></strong></span>.
</p>
</dd>
<dt>
<span class="term"><span class="command"><strong>min-refresh-time</strong></span>, </span><span class="term"><span class="command"><strong>max-refresh-time</strong></span>, </span><span class="term"><span class="command"><strong>min-retry-time</strong></span>, </span><span class="term"><span class="command"><strong>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 class="command"><strong>min-refresh-time</strong></span> 300 seconds,
<span class="command"><strong>max-refresh-time</strong></span> 2419200 seconds
(4 weeks), <span class="command"><strong>min-retry-time</strong></span> 500 seconds,
and <span class="command"><strong>max-retry-time</strong></span> 1209600 seconds
(2 weeks).
</p>
</dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>named</strong></span>
will default to plain DNS for future communications
with that server. (Periodically, <span class="command"><strong>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 class="command"><strong>named</strong></span> will advertise progressively
larger buffer sizes on successive queries, until
responses begin timing out or
<span class="command"><strong>edns-udp-size</strong></span> is reached.
</p>
<p>
The default buffer sizes used by <span class="command"><strong>named</strong></span>
are 512, 1232, 1432, and 4096, but never exceeding
<span class="command"><strong>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 class="command"><strong>max-udp-size</strong></span></span></dt>
<dd>
<p>
Sets the maximum EDNS UDP message size
<span class="command"><strong>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 class="command"><strong>edns-udp-size</strong></span>.
</p>
<p>
The usual reason for setting
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>masterfile-format</strong></span></span></dt>
<dd>
<p>Specifies
the file format of zone files (see
<a class="xref" 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 class="command"><strong>named-compilezone</strong></span> tool, or dumped by
<span class="command"><strong>named</strong></span>.
</p>
<p>
Note that when a zone file in a different format than
<code class="constant">text</code> is loaded, <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>masterfile-format</strong></span> for all zones,
but can be overridden on a per-zone or per-view basis
by including a <span class="command"><strong>masterfile-format</strong></span>
statement within the <span class="command"><strong>zone</strong></span> or
<span class="command"><strong>view</strong></span> block in the configuration
file.
</p>
</dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 domains 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 class="command"><strong>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 class="command"><strong>serial-query-rate</strong></span>.
</p>
</dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>prefetch</strong></span></span></dt>
<dd>
<p>
When a query is received for cached data which
is to expire shortly, <span class="command"><strong>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 class="command"><strong>named</strong></span> will silently
adjust it upward.
The default eligibility TTL is <code class="literal">9</code>.
</p>
</dd>
<dt><span class="term"><span class="command"><strong>v6-bias</strong></span></span></dt>
<dd><p>
When determining the next nameserver to try
preference IPv6 nameservers by this many milliseconds.
The default is <code class="literal">50</code> milliseconds.
</p></dd>
</dl></div>
</div>
<div class="section">
<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 class="command"><strong>CHAOS</strong></span> class. These zones are part
of a
built-in view (see <a class="xref" href="Bv9ARM.ch06.html#view_statement_grammar" title="view Statement Grammar">the section called &#8220;<span class="command"><strong>view</strong></span> Statement Grammar&#8221;</a>) of
class
<span class="command"><strong>CHAOS</strong></span> which is separate from the
default view of class <span class="command"><strong>IN</strong></span>. Most global
configuration options (<span class="command"><strong>allow-query</strong></span>,
etc) will apply to this view, but some are locally
overridden: <span class="command"><strong>notify</strong></span>,
<span class="command"><strong>recursion</strong></span> and
<span class="command"><strong>allow-new-zones</strong></span> are
always set to <strong class="userinput"><code>no</code></strong>, and
<span class="command"><strong>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 class="command"><strong>CHAOS</strong></span>
view by
defining an explicit view of class <span class="command"><strong>CHAOS</strong></span>
that matches all clients.
</p>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>TXT</strong></span>, class <span class="command"><strong>CHAOS</strong></span>.
The default is the real version number of this server.
Specifying <span class="command"><strong>version none</strong></span>
disables processing of the queries.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>TXT</strong></span>, class <span class="command"><strong>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 class="command"><strong>hostname none;</strong></span>
disables processing of the queries.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>TXT</strong></span>, class <span class="command"><strong>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 class="command"><strong>server-id none;</strong></span>
disables processing of the queries.
Specifying <span class="command"><strong>server-id hostname;</strong></span> will cause <span class="command"><strong>named</strong></span> to
use the hostname as found by the gethostname() function.
The default <span class="command"><strong>server-id</strong></span> is <span class="command"><strong>none</strong></span>.
</p></dd>
</dl></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="empty"></a>Built-in Empty Zones</h4></div></div></div>
<p>
The <span class="command"><strong>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 class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">10.IN-ADDR.ARPA</li>
<li class="listitem">16.172.IN-ADDR.ARPA</li>
<li class="listitem">17.172.IN-ADDR.ARPA</li>
<li class="listitem">18.172.IN-ADDR.ARPA</li>
<li class="listitem">19.172.IN-ADDR.ARPA</li>
<li class="listitem">20.172.IN-ADDR.ARPA</li>
<li class="listitem">21.172.IN-ADDR.ARPA</li>
<li class="listitem">22.172.IN-ADDR.ARPA</li>
<li class="listitem">23.172.IN-ADDR.ARPA</li>
<li class="listitem">24.172.IN-ADDR.ARPA</li>
<li class="listitem">25.172.IN-ADDR.ARPA</li>
<li class="listitem">26.172.IN-ADDR.ARPA</li>
<li class="listitem">27.172.IN-ADDR.ARPA</li>
<li class="listitem">28.172.IN-ADDR.ARPA</li>
<li class="listitem">29.172.IN-ADDR.ARPA</li>
<li class="listitem">30.172.IN-ADDR.ARPA</li>
<li class="listitem">31.172.IN-ADDR.ARPA</li>
<li class="listitem">168.192.IN-ADDR.ARPA</li>
<li class="listitem">64.100.IN-ADDR.ARPA</li>
<li class="listitem">65.100.IN-ADDR.ARPA</li>
<li class="listitem">66.100.IN-ADDR.ARPA</li>
<li class="listitem">67.100.IN-ADDR.ARPA</li>
<li class="listitem">68.100.IN-ADDR.ARPA</li>
<li class="listitem">69.100.IN-ADDR.ARPA</li>
<li class="listitem">70.100.IN-ADDR.ARPA</li>
<li class="listitem">71.100.IN-ADDR.ARPA</li>
<li class="listitem">72.100.IN-ADDR.ARPA</li>
<li class="listitem">73.100.IN-ADDR.ARPA</li>
<li class="listitem">74.100.IN-ADDR.ARPA</li>
<li class="listitem">75.100.IN-ADDR.ARPA</li>
<li class="listitem">76.100.IN-ADDR.ARPA</li>
<li class="listitem">77.100.IN-ADDR.ARPA</li>
<li class="listitem">78.100.IN-ADDR.ARPA</li>
<li class="listitem">79.100.IN-ADDR.ARPA</li>
<li class="listitem">80.100.IN-ADDR.ARPA</li>
<li class="listitem">81.100.IN-ADDR.ARPA</li>
<li class="listitem">82.100.IN-ADDR.ARPA</li>
<li class="listitem">83.100.IN-ADDR.ARPA</li>
<li class="listitem">84.100.IN-ADDR.ARPA</li>
<li class="listitem">85.100.IN-ADDR.ARPA</li>
<li class="listitem">86.100.IN-ADDR.ARPA</li>
<li class="listitem">87.100.IN-ADDR.ARPA</li>
<li class="listitem">88.100.IN-ADDR.ARPA</li>
<li class="listitem">89.100.IN-ADDR.ARPA</li>
<li class="listitem">90.100.IN-ADDR.ARPA</li>
<li class="listitem">91.100.IN-ADDR.ARPA</li>
<li class="listitem">92.100.IN-ADDR.ARPA</li>
<li class="listitem">93.100.IN-ADDR.ARPA</li>
<li class="listitem">94.100.IN-ADDR.ARPA</li>
<li class="listitem">95.100.IN-ADDR.ARPA</li>
<li class="listitem">96.100.IN-ADDR.ARPA</li>
<li class="listitem">97.100.IN-ADDR.ARPA</li>
<li class="listitem">98.100.IN-ADDR.ARPA</li>
<li class="listitem">99.100.IN-ADDR.ARPA</li>
<li class="listitem">100.100.IN-ADDR.ARPA</li>
<li class="listitem">101.100.IN-ADDR.ARPA</li>
<li class="listitem">102.100.IN-ADDR.ARPA</li>
<li class="listitem">103.100.IN-ADDR.ARPA</li>
<li class="listitem">104.100.IN-ADDR.ARPA</li>
<li class="listitem">105.100.IN-ADDR.ARPA</li>
<li class="listitem">106.100.IN-ADDR.ARPA</li>
<li class="listitem">107.100.IN-ADDR.ARPA</li>
<li class="listitem">108.100.IN-ADDR.ARPA</li>
<li class="listitem">109.100.IN-ADDR.ARPA</li>
<li class="listitem">110.100.IN-ADDR.ARPA</li>
<li class="listitem">111.100.IN-ADDR.ARPA</li>
<li class="listitem">112.100.IN-ADDR.ARPA</li>
<li class="listitem">113.100.IN-ADDR.ARPA</li>
<li class="listitem">114.100.IN-ADDR.ARPA</li>
<li class="listitem">115.100.IN-ADDR.ARPA</li>
<li class="listitem">116.100.IN-ADDR.ARPA</li>
<li class="listitem">117.100.IN-ADDR.ARPA</li>
<li class="listitem">118.100.IN-ADDR.ARPA</li>
<li class="listitem">119.100.IN-ADDR.ARPA</li>
<li class="listitem">120.100.IN-ADDR.ARPA</li>
<li class="listitem">121.100.IN-ADDR.ARPA</li>
<li class="listitem">122.100.IN-ADDR.ARPA</li>
<li class="listitem">123.100.IN-ADDR.ARPA</li>
<li class="listitem">124.100.IN-ADDR.ARPA</li>
<li class="listitem">125.100.IN-ADDR.ARPA</li>
<li class="listitem">126.100.IN-ADDR.ARPA</li>
<li class="listitem">127.100.IN-ADDR.ARPA</li>
<li class="listitem">0.IN-ADDR.ARPA</li>
<li class="listitem">127.IN-ADDR.ARPA</li>
<li class="listitem">254.169.IN-ADDR.ARPA</li>
<li class="listitem">2.0.192.IN-ADDR.ARPA</li>
<li class="listitem">100.51.198.IN-ADDR.ARPA</li>
<li class="listitem">113.0.203.IN-ADDR.ARPA</li>
<li class="listitem">255.255.255.255.IN-ADDR.ARPA</li>
<li class="listitem">0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
<li class="listitem">1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA</li>
<li class="listitem">8.B.D.0.1.0.0.2.IP6.ARPA</li>
<li class="listitem">D.F.IP6.ARPA</li>
<li class="listitem">8.E.F.IP6.ARPA</li>
<li class="listitem">9.E.F.IP6.ARPA</li>
<li class="listitem">A.E.F.IP6.ARPA</li>
<li class="listitem">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>
<p>
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.
</p>
</div>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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="section">
<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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>additional-from-cache</strong></span>
to <span class="command"><strong>no</strong></span> is recommended, since the current
implementation of <span class="command"><strong>acache</strong></span>
does not short-cut of additional section information from the
DNS cache data.
</p>
<p>
One obvious disadvantage of <span class="command"><strong>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 class="command"><strong>acache</strong></span> mechanism can be
disabled by setting <span class="command"><strong>acache-enable</strong></span> to
<span class="command"><strong>no</strong></span>.
It is also possible to specify the upper limit of memory
consumption
for acache by using <span class="command"><strong>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 class="command"><strong>acache</strong></span>,
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>acache</strong></span>.
</p>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><span class="command"><strong>acache-enable</strong></span></span></dt>
<dd><p>
If <span class="command"><strong>yes</strong></span>, additional section caching is
enabled. The default value is <span class="command"><strong>no</strong></span>.
</p></dd>
<dt><span class="term"><span class="command"><strong>acache-cleaning-interval</strong></span></span></dt>
<dd><p>
The server will remove stale cache entries, based on an LRU
based
algorithm, every <span class="command"><strong>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 class="command"><strong>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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="content_filtering"></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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>deny-answer-aliases</strong></span>
filter will not apply;
for example, even if "example.com" is specified for
<span class="command"><strong>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 class="command"><strong>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 class="link" 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 class="command"><strong>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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="rpz"></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 class="command"><strong>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 class="command"><strong>allow-query { localhost; };</strong></span>.
Note that zones using <span class="command"><strong>masterfile-format map</strong></span>
cannot be used as policy zones.
</p>
<p>
A <span class="command"><strong>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 class="command"><strong>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 class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>rpz-ip</strong></span>.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>RPZ-NSIP</strong></span></span></dt>
<dd>
<p>
NSIP triggers match the IP addresses of authoritative
servers. They are enncoded like IP triggers, except as
subdomains of <span class="command"><strong>rpz-nsip</strong></span>.
NSDNAME and NSIP triggers are checked only for names with at
least <span class="command"><strong>min-ns-dots</strong></span> dots.
The default value of <span class="command"><strong>min-ns-dots</strong></span> is
1, to exclude top level domains.
</p>
<p>
If a name server's IP address is not yet known,
<span class="command"><strong>named</strong></span> will recursively look up
the IP address before applying an RPZ-NSIP rule.
This can cause a processing delay. To speed up
processing at the cost of precision, the
<span class="command"><strong>nsip-wait-recurse</strong></span> option
can be used: when set to <strong class="userinput"><code>no</code></strong>,
RPZ-NSIP rules will only be applied when a name
servers's IP address has already been looked up and
cached. If a server's IP address is not in the
cache, then the RPZ-NSIP rule will be ignored,
but the address will be looked up in the
background, and the rule will be applied
to subsequent queries. The default is
<strong class="userinput"><code>yes</code></strong>, meaning RPZ-NSIP
rules should always be applied even if an
address needs to be looked up first.
</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 class="command"><strong>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 class="orderedlist" type="1">
<li class="listitem">Choose the triggered record in the zone that appears
first in the <span class="command"><strong>response-policy</strong></span> option.
</li>
<li class="listitem">Prefer CLIENT-IP to QNAME to IP to NSDNAME to NSIP
triggers in a single zone.
</li>
<li class="listitem">Among NSDNAME triggers, prefer the
trigger that matches the smallest name under the DNSSEC ordering.
</li>
<li class="listitem">Among IP or NSIP triggers, prefer the trigger
with the longest prefix.
</li>
<li class="listitem">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 class="command"><strong>TCP-only</strong></span> policy is
commonly used with <span class="command"><strong>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 class="variablelist">
<dt><span class="term"><span class="command"><strong>PASSTHRU</strong></span></span></dt>
<dd><p>
The whitelist policy is specified
by a CNAME whose target is <span class="command"><strong>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 class="command"><strong>DROP</strong></span></span></dt>
<dd><p>
The blacklist policy is specified
by a CNAME whose target is <span class="command"><strong>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 class="command"><strong>TCP-Only</strong></span></span></dt>
<dd><p>
The "slip" policy is specified
by a CNAME whose target is <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 asterisk (*)
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 class="command"><strong>policy</strong></span> clause in the
<span class="command"><strong>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 class="variablelist">
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>PASSTHRU</strong></span>, </span><span class="term"><span class="command"><strong>DROP</strong></span>, </span><span class="term"><span class="command"><strong>TCP-Only</strong></span>, </span><span class="term"><span class="command"><strong>NXDOMAIN</strong></span>, </span><span class="term"><span class="command"><strong>NODATA</strong></span></span>
</dt>
<dd><p>
override with the corresponding per-record policy.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>RPZRewrites</strong></span> statistics.
</p>
<p>
The <span class="command"><strong>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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="rrl"></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 class="command"><strong>rate-limit</strong></span> clause in an
<span class="command"><strong>options</strong></span> or <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>ipv4-prefix-length</strong></span> (default 24)
and <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>nodata-per-second</strong></span>
(default <span class="command"><strong>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 class="command"><strong>nxdomains-per-second</strong></span>
(default <span class="command"><strong>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 class="command"><strong>referrals-per-second</strong></span>
(default <span class="command"><strong>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 class="command"><strong>responses-per-second</strong></span> value,
but it can be set separately with
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>qps-scale</strong></span> value,
then the <span class="command"><strong>responses-per-second</strong></span>,
<span class="command"><strong>errors-per-second</strong></span>,
<span class="command"><strong>nxdomains-per-second</strong></span> and
<span class="command"><strong>all-per-second</strong></span> values are reduced by the
ratio of the current rate to the <span class="command"><strong>qps-scale</strong></span> value.
This feature can tighten defenses during attacks.
For example, with
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>rate-limit</strong></span> blocks
with different <span class="command"><strong>domain</strong></span> clauses.
The <span class="command"><strong>rate-limit</strong></span> statement's
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>rate-limit</strong></span> statement does not specify a
<span class="command"><strong>domain</strong></span>, then it applies to the root domain
(".") and thus affects the entire DNS namespace, except those
portions covered by other <span class="command"><strong>rate-limit</strong></span>
statements.
</p>
<p>
Communities of DNS clients can be given their own parameters or no
rate limiting by putting
<span class="command"><strong>rate-limit</strong></span> statements in <span class="command"><strong>view</strong></span>
statements instead of the global <span class="command"><strong>option</strong></span>
statement.
A <span class="command"><strong>rate-limit</strong></span> statement in a view replaces,
rather than supplementing, a <span class="command"><strong>rate-limit</strong></span>
statement among the main options.
DNS clients within a view can be exempted from rate limits
with the <span class="command"><strong>exempt-clients</strong></span> clause.
</p>
<p>
UDP responses of all kinds can be limited with the
<span class="command"><strong>all-per-second</strong></span> phrase. This rate
limiting is unlike the rate limiting provided by
<span class="command"><strong>responses-per-second</strong></span>,
<span class="command"><strong>errors-per-second</strong></span>, and
<span class="command"><strong>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 class="command"><strong>all-per-second</strong></span> limit
are always dropped; the <span class="command"><strong>slip</strong></span> value
has no effect. An <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>min-table-size</strong></span> (default 500)
can set the minimum table size.
Enable <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>RateDropped</strong></span> and <span class="command"><strong>QryDropped</strong></span>
statistics.
Responses that truncated by rate limits are included in
<span class="command"><strong>RateSlipped</strong></span> and <span class="command"><strong>RespTruncated</strong></span>.
</p>
</div>
<div class="section">
<div class="titlepage"></div>
<p>
Named supports NXDOMAIN redirection via two methods:
</p>
<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
<li class="listitem">Redirect zone <a class="xref" href="Bv9ARM.ch06.html#zone_statement_grammar" title="zone Statement Grammar">the section called &#8220;<span class="command"><strong>zone</strong></span>
Statement Grammar&#8221;</a>
</li>
<li class="listitem">Redirect namespace</li>
</ul></div>
<p>
</p>
<p>
With both methods when named gets a NXDOMAIN response
it examines a separate namespace to see if the NXDOMAIN
response should be replaced with an alternative response.
</p>
<p>
With a redirect zone (<span class="command"><strong>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 class="command"><strong>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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="server_statement_grammar"></a><span class="command"><strong>server</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span class="command"><strong>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"> 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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="server_statement_definition_and_usage"></a><span class="command"><strong>server</strong></span> Statement Definition and
Usage</h3></div></div></div>
<p>
The <span class="command"><strong>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 class="command"><strong>server</strong></span> statement can occur at
the top level of the
configuration file or inside a <span class="command"><strong>view</strong></span>
statement.
If a <span class="command"><strong>view</strong></span> statement contains
one or more <span class="command"><strong>server</strong></span> statements, only
those
apply to the view and any top-level ones are ignored.
If a view contains no <span class="command"><strong>server</strong></span>
statements,
any top-level <span class="command"><strong>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 class="command"><strong>bogus</strong></span> is <span class="command"><strong>no</strong></span>.
</p>
<p>
The <span class="command"><strong>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 class="command"><strong>yes</strong></span>, incremental transfer
will be provided
whenever possible. If set to <span class="command"><strong>no</strong></span>,
all transfers
to the remote server will be non-incremental. If not set, the
value
of the <span class="command"><strong>provide-ixfr</strong></span> option in the
view or
global options block is used as a default.
</p>
<p>
The <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>yes</strong></span> should always work.
The purpose of the <span class="command"><strong>provide-ixfr</strong></span> and
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>yes</strong></span>.
</p>
<p>
The <span class="command"><strong>edns</strong></span> clause determines whether
the local server will attempt to use EDNS when communicating
with the remote server. The default is <span class="command"><strong>yes</strong></span>.
</p>
<p>
The <span class="command"><strong>edns-udp-size</strong></span> option sets the
EDNS UDP size that is advertised by <span class="command"><strong>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 class="command"><strong>named</strong></span> will not deviate from
this value. This differs from the behavior of
<span class="command"><strong>edns-udp-size</strong></span> in <span class="command"><strong>options</strong></span>
or <span class="command"><strong>view</strong></span> statements, where it specifies
a maximum value. The <span class="command"><strong>server</strong></span> statement
behavior may be brought into conformance with the
<span class="command"><strong>options/view</strong></span> behavior in future releases.)
</p>
<p>
The <span class="command"><strong>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 class="command"><strong>max-udp-size</strong></span> option sets the
maximum EDNS UDP message size <span class="command"><strong>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 class="command"><strong>named</strong></span>.
</p>
<p>
The <span class="command"><strong>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 class="command"><strong>one-answer</strong></span>,
uses one DNS message per resource record transferred. <span class="command"><strong>many-answers</strong></span> packs
as many resource records as possible into a message. <span class="command"><strong>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 class="command"><strong>transfer-format</strong></span> option.
If <span class="command"><strong>transfer-format</strong></span> is not
specified, the <span class="command"><strong>transfer-format</strong></span>
specified
by the <span class="command"><strong>options</strong></span> statement will be
used.
</p>
<p><span class="command"><strong>transfers</strong></span>
is used to limit the number of concurrent inbound zone
transfers from the specified server. If no
<span class="command"><strong>transfers</strong></span> clause is specified, the
limit is set according to the
<span class="command"><strong>transfers-per-ns</strong></span> option.
</p>
<p>
The <span class="command"><strong>keys</strong></span> clause identifies a
<span class="command"><strong>key_id</strong></span> defined by the <span class="command"><strong>key</strong></span> statement,
to be used for transaction security (TSIG, <a class="xref" 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 class="command"><strong>transfer-source</strong></span> and
<span class="command"><strong>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 class="command"><strong>transfer-source</strong></span> can
be specified.
Similarly, for an IPv6 remote server, only
<span class="command"><strong>transfer-source-v6</strong></span> can be
specified.
For more details, see the description of
<span class="command"><strong>transfer-source</strong></span> and
<span class="command"><strong>transfer-source-v6</strong></span> in
<a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p>
<p>
The <span class="command"><strong>notify-source</strong></span> and
<span class="command"><strong>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 class="command"><strong>notify-source</strong></span>
can be specified. Similarly, for an IPv6 remote server,
only <span class="command"><strong>notify-source-v6</strong></span> can be specified.
</p>
<p>
The <span class="command"><strong>query-source</strong></span> and
<span class="command"><strong>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 class="command"><strong>query-source</strong></span> can
be specified. Similarly, for an IPv6 remote server,
only <span class="command"><strong>query-source-v6</strong></span> can be specified.
</p>
<p>
The <span class="command"><strong>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 class="command"><strong>request-nsid</strong></span> set at the view or
option level.
</p>
<p>
The <span class="command"><strong>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 class="command"><strong>send-cookie</strong></span> set at the view or
option level. The <span class="command"><strong>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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="statschannels"></a><span class="command"><strong>statistics-channels</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span class="command"><strong>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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="statistics_channels"></a><span class="command"><strong>statistics-channels</strong></span> Statement Definition and
Usage</h3></div></div></div>
<p>
The <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>inet</strong></span> control channel is a TCP socket
listening at the specified <span class="command"><strong>ip_port</strong></span> on the
specified <span class="command"><strong>ip_addr</strong></span>, which can be an IPv4 or IPv6
address. An <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>ip_port</strong></span>.
</p>
<p>
The attempt of opening a statistics channel is
restricted by the optional <span class="command"><strong>allow</strong></span> clause.
Connections to the statistics channel are permitted based on the
<span class="command"><strong>address_match_list</strong></span>.
If no <span class="command"><strong>allow</strong></span> clause is present,
<span class="command"><strong>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 class="command"><strong>statistics-channels</strong></span> statement is present,
<span class="command"><strong>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 class="link" href="http://127.0.0.1:8888/" target="_top">http://127.0.0.1:8888/</a> or
<a class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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 class="link" 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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="trusted-keys"></a><span class="command"><strong>trusted-keys</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span class="command"><strong>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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="trusted_keys"></a><span class="command"><strong>trusted-keys</strong></span> Statement Definition
and Usage</h3></div></div></div>
<p>
The <span class="command"><strong>trusted-keys</strong></span> statement defines
DNSSEC security roots. DNSSEC is described in <a class="xref" 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 class="command"><strong>trusted-keys</strong></span> are deemed to exist regardless
of what parent zones say. Similarly for all keys listed in
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>rndc nta</strong></span>.
</p>
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="managed_keys"></a><span class="command"><strong>managed-keys</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span class="command"><strong>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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="managed-keys"></a><span class="command"><strong>managed-keys</strong></span> Statement Definition
and Usage</h3></div></div></div>
<p>
The <span class="command"><strong>managed-keys</strong></span> statement, like
<span class="command"><strong>trusted-keys</strong></span>, defines DNSSEC
security roots. The difference is that
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>trusted-keys</strong></span> statement with the new key.
</p>
<p>
If, however, the zone were listed in a
<span class="command"><strong>managed-keys</strong></span> statement instead, then the
zone owner could add a "stand-by" key to the zone in advance.
<span class="command"><strong>named</strong></span> would store the stand-by key, and
when the original key was revoked, <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>managed-keys</strong></span> statement
appears similar to a <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>named</strong></span> runs, it
sees the <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>named</strong></span> runs after a name
has been <span class="emphasis"><em>removed</em></span> from the
<span class="command"><strong>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 class="command"><strong>named</strong></span> only maintains a single managed keys
database; consequently, unlike <span class="command"><strong>trusted-keys</strong></span>,
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>named</strong></span>.)
</p>
<p>
If the <span class="command"><strong>dnssec-validation</strong></span> option is
set to <strong class="userinput"><code>auto</code></strong>, <span class="command"><strong>named</strong></span>
will automatically initialize a managed key for the
root zone. Similarly, if the <span class="command"><strong>dnssec-lookaside</strong></span>
option is set to <strong class="userinput"><code>auto</code></strong>,
<span class="command"><strong>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 class="command"><strong>named</strong></span>,
and can be overridden from <span class="command"><strong>bindkeys-file</strong></span>.
</p>
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="view_statement_grammar"></a><span class="command"><strong>view</strong></span> Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span class="command"><strong>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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="view_statement"></a><span class="command"><strong>view</strong></span> Statement Definition and Usage</h3></div></div></div>
<p>
The <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>match-clients</strong></span> clause and its
destination IP address matches
the <code class="varname">address_match_list</code> of the
view's
<span class="command"><strong>match-destinations</strong></span> clause. If not
specified, both
<span class="command"><strong>match-clients</strong></span> and <span class="command"><strong>match-destinations</strong></span>
default to matching all addresses. In addition to checking IP
addresses
<span class="command"><strong>match-clients</strong></span> and <span class="command"><strong>match-destinations</strong></span>
can also take <span class="command"><strong>keys</strong></span> which provide an
mechanism for the
client to select the view. A view can also be specified
as <span class="command"><strong>match-recursive-only</strong></span>, which
means that only recursive
requests from matching clients will match that view.
The order of the <span class="command"><strong>view</strong></span> statements is
significant &#8212;
a client request will be resolved in the context of the first
<span class="command"><strong>view</strong></span> that it matches.
</p>
<p>
Zones defined within a <span class="command"><strong>view</strong></span>
statement will
only be accessible to clients that match the <span class="command"><strong>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 class="command"><strong>options</strong></span> statement
can also be used within a <span class="command"><strong>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 class="command"><strong>options</strong></span> statement
is used as a default. Also, zone options can have default values
specified
in the <span class="command"><strong>view</strong></span> statement; these
view-specific defaults
take precedence over those in the <span class="command"><strong>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 class="command"><strong>view</strong></span> statements in
the config
file, a default view that matches any client is automatically
created
in class IN. Any <span class="command"><strong>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 class="command"><strong>options</strong></span>
statement will
apply to the default view. If any explicit <span class="command"><strong>view</strong></span>
statements are present, all <span class="command"><strong>zone</strong></span>
statements must
occur inside <span class="command"><strong>view</strong></span> statements.
</p>
<p>
Here is an example of a typical split DNS setup implemented
using <span class="command"><strong>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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="zone_statement_grammar"></a><span class="command"><strong>zone</strong></span>
Statement Grammar</h3></div></div></div>
<pre class="programlisting"><span class="command"><strong>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 [<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">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"> 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"> 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">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"> 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"> 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>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</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>full</code></em> | <em class="replaceable"><code>terse</code></em> | <em class="replaceable"><code>none</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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="zone_statement"></a><span class="command"><strong>zone</strong></span> Statement Definition and Usage</h3></div></div></div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="zone_types"></a>Zone Types</h4></div></div></div>
<p>
The <span class="command"><strong>type</strong></span> keyword is required
for the <span class="command"><strong>zone</strong></span> configuration unless
it is an <span class="command"><strong>in-view</strong></span> configuration. Its
acceptable values include: <code class="varname">delegation-only</code>,
<code class="varname">forward</code>, <code class="varname">hint</code>,
<code class="varname">master</code>, <code class="varname">redirect</code>,
<code class="varname">slave</code>, <code class="varname">static-stub</code>,
and <code class="varname">stub</code>.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col class="1">
<col width="4.017in" class="2">
</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 class="command"><strong>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 class="command"><strong>server-addresses</strong></span> and
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>zone</strong></span> statement
of type <span class="command"><strong>forward</strong></span> can
contain a <span class="command"><strong>forward</strong></span>
and/or <span class="command"><strong>forwarders</strong></span>
statement,
which will apply to queries within the domain given by
the zone
name. If no <span class="command"><strong>forwarders</strong></span>
statement is present or
an empty list for <span class="command"><strong>forwarders</strong></span> is given, then no
forwarding will be done for the domain, canceling the
effects of
any forwarders in the <span class="command"><strong>options</strong></span> statement. Thus
if you want to use this type of zone to change the
behavior of the
global <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>rndc reload
<em class="replaceable"><code>zonename</code></em></strong></span>
to reload a redirect zone. However, when using
<span class="command"><strong>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 class="xref" href="Bv9ARM.ch06.html#root_delegation_only"><span class="command"><strong>root-delegation-only</strong></span></a>.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="class"></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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="zone_options"></a>Zone Options</h4></div></div></div>
<div class="variablelist"><dl class="variablelist">
<dt><span class="term"><span class="command"><strong>allow-notify</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>allow-notify</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>allow-query</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>allow-query</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>allow-query-on</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>allow-query-on</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>allow-transfer</strong></span></span></dt>
<dd><p>
See the description of <span class="command"><strong>allow-transfer</strong></span>
in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>allow-update</strong></span></span></dt>
<dd><p>
See the description of <span class="command"><strong>allow-update</strong></span>
in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>update-policy</strong></span></span></dt>
<dd><p>
Specifies a "Simple Secure Update" policy. See
<a class="xref" 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 class="command"><strong>allow-update-forwarding</strong></span></span></dt>
<dd><p>
See the description of <span class="command"><strong>allow-update-forwarding</strong></span>
in <a class="xref" href="Bv9ARM.ch06.html#access_control" title="Access Control">the section called &#8220;Access Control&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>also-notify</strong></span></span></dt>
<dd><p>
Only meaningful if <span class="command"><strong>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 class="command"><strong>also-notify</strong></span>. A port
may be specified
with each <span class="command"><strong>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 class="command"><strong>also-notify</strong></span> is not
meaningful for stub zones.
The default is the empty list.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>master</strong></span> zones the default is <span class="command"><strong>fail</strong></span>. For <span class="command"><strong>slave</strong></span>
zones the default is <span class="command"><strong>warn</strong></span>.
It is not implemented for <span class="command"><strong>hint</strong></span> zones.
</p></dd>
<dt><span class="term"><span class="command"><strong>check-mx</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>check-mx</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>check-spf</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>check-spf</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>check-wildcard</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>check-wildcard</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>check-integrity</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>check-integrity</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>check-sibling</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>check-sibling</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>zero-no-soa-ttl</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>zero-no-soa-ttl</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>update-check-ksk</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>update-check-ksk</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>dnssec-loadkeys-interval</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>dnssec-loadkeys-interval</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called &#8220;<span class="command"><strong>options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>dnssec-update-mode</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>dnssec-update-mode</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called &#8220;<span class="command"><strong>options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>dnssec-dnskey-kskonly</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>dnssec-dnskey-kskonly</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>try-tcp-refresh</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>try-tcp-refresh</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>dialup</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>dialup</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="xref" href="Bv9ARM.ch06.html#root_delegation_only"><span class="command"><strong>root-delegation-only</strong></span></a>.
</p>
</dd>
<dt><span class="term"><span class="command"><strong>forward</strong></span></span></dt>
<dd><p>
Only meaningful if the zone has a forwarders
list. The <span class="command"><strong>only</strong></span> value causes
the lookup to fail
after trying the forwarders and getting no answer, while <span class="command"><strong>first</strong></span> would
allow a normal lookup to be tried.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>forward</strong></span>,
no forwarding is done for the zone and the global options are
not used.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>master</strong></span> and <span class="command"><strong>slave</strong></span> zones.
</p></dd>
<dt><span class="term"><span class="command"><strong>max-journal-size</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>max-journal-size</strong></span> in <a class="xref" 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 class="command"><strong>max-transfer-time-in</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>max-transfer-time-in</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>max-transfer-idle-in</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>max-transfer-idle-in</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>max-transfer-time-out</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>max-transfer-time-out</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>max-transfer-idle-out</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>max-transfer-idle-out</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>notify</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>notify</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>notify-delay</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>notify-delay</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>notify-to-soa</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>notify-to-soa</strong></span> in
<a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>zone-statistics</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>zone-statistics</strong></span> in
<a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called &#8220;<span class="command"><strong>options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>sig-validity-interval</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>sig-validity-interval</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>sig-signing-nodes</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>sig-signing-nodes</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>sig-signing-signatures</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>sig-signing-signatures</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>sig-signing-type</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>sig-signing-type</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>transfer-source</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>transfer-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>transfer-source-v6</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>alt-transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>alt-transfer-source</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>alt-transfer-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>alt-transfer-source-v6</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>use-alt-transfer-source</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>use-alt-transfer-source</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>notify-source</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>notify-source</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>notify-source-v6</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>notify-source-v6</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called &#8220;Zone Transfers&#8221;</a>.
</p></dd>
<dt>
<span class="term"><span class="command"><strong>min-refresh-time</strong></span>, </span><span class="term"><span class="command"><strong>max-refresh-time</strong></span>, </span><span class="term"><span class="command"><strong>min-retry-time</strong></span>, </span><span class="term"><span class="command"><strong>max-retry-time</strong></span></span>
</dt>
<dd><p>
See the description in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>ixfr-from-differences</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>ixfr-from-differences</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
(Note that the <span class="command"><strong>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 class="command"><strong>key-directory</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>key-directory</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called &#8220;<span class="command"><strong>options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>auto-dnssec</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>auto-dnssec</strong></span> in
<a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called &#8220;<span class="command"><strong>options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>serial-update-method</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>serial-update-method</strong></span> in
<a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called &#8220;<span class="command"><strong>options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>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
behavior is disabled by default.
</p></dd>
<dt><span class="term"><span class="command"><strong>multi-master</strong></span></span></dt>
<dd><p>
See the description of <span class="command"><strong>multi-master</strong></span> in
<a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>masterfile-format</strong></span></span></dt>
<dd><p>
See the description of <span class="command"><strong>masterfile-format</strong></span>
in <a class="xref" href="Bv9ARM.ch06.html#tuning" title="Tuning">the section called &#8220;Tuning&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>max-zone-ttl</strong></span></span></dt>
<dd><p>
See the description of <span class="command"><strong>max-zone-ttl</strong></span>
in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called &#8220;<span class="command"><strong>options</strong></span> Statement Definition and
Usage&#8221;</a>.
</p></dd>
<dt><span class="term"><span class="command"><strong>dnssec-secure-to-insecure</strong></span></span></dt>
<dd><p>
See the description of
<span class="command"><strong>dnssec-secure-to-insecure</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called &#8220;Boolean Options&#8221;</a>.
</p></dd>
</dl></div>
</div>
<div class="section">
<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 class="command"><strong>allow-update</strong></span> and
<span class="command"><strong>update-policy</strong></span> option, respectively.
</p>
<p>
The <span class="command"><strong>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 class="command"><strong>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 class="command"><strong>update-policy</strong></span>
zone option, and are only meaningful for master zones.
When the <span class="command"><strong>update-policy</strong></span> statement
is present, it is a configuration error for the
<span class="command"><strong>allow-update</strong></span> statement to be
present. The <span class="command"><strong>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 class="command"><strong>update-policy</strong></span>
rule which can be switched on with the command
<span class="command"><strong>update-policy local;</strong></span>.
Switching on this rule in a zone causes
<span class="command"><strong>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 class="command"><strong>session-keyfile</strong></span>,
<span class="command"><strong>session-keyname</strong></span> and
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>grant</strong></span> | <span class="command"><strong>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 width="0.819in" class="1">
<col width="3.681in" class="2">
</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 class="command"><strong>update-policy</strong></span> statement
appears. This obviates the need to type the zone
name twice, and enables the use of a standard
<span class="command"><strong>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
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 class="command"><strong>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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="multiple_views"></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 class="command"><strong>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 class="command"><strong>in-view</strong></span> option cannot refer to a view
that is configured later in the configuration file.
</p>
<p>
A <span class="command"><strong>zone</strong></span> statement which uses the
<span class="command"><strong>in-view</strong></span> option may not use any other
options with the exception of <span class="command"><strong>forward</strong></span>
and <span class="command"><strong>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 class="command"><strong>in-view</strong></span> zone cannot be used as a
response policy zone.
</p>
<p>
An <span class="command"><strong>in-view</strong></span> zone is not intended to reference
a <span class="command"><strong>forward</strong></span> zone.
</p>
</div>
</div>
</div>
<div class="section">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="zone_file"></a>Zone File</h2></div></div></div>
<div class="section">
<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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="id-1.7.6.2.3"></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 class="xref" href="Bv9ARM.ch06.html#the_sortlist_statement" title="The sortlist Statement">the section called &#8220;The <span class="command"><strong>sortlist</strong></span> Statement&#8221;</a> and <a class="xref" 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 width="1.000in" class="1">
<col width="3.500in" class="2">
</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 width="0.875in" class="1">
<col width="3.625in" class="2">
</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>
AVC
</p>
</td>
<td>
<p>
Application Visibility and Control record.
</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>
CSYNC
</p>
</td>
<td>
<p>
Child-to-Parent Synchronization in DNS as described
in RFC 7477.
</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>
NINFO
</p>
</td>
<td>
<p>
Contains zone status information.
</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>
RKEY
</p>
</td>
<td>
<p>
Resource key.
</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>
SINK
</p>
</td>
<td>
<p>
The kitchen sink record.
</p>
</td>
</tr>
<tr>
<td>
<p>
SMIMEA
</p>
</td>
<td>
<p>
The S/MIME Security Certificate Association.
</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>
TA
</p>
</td>
<td>
<p>
Trust Anchor. Experimental.
</p>
</td>
</tr>
<tr>
<td>
<p>
TALINK
</p>
</td>
<td>
<p>
Trust Anchor Link. Experimental.
</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 width="0.875in" class="1">
<col width="3.625in" class="2">
</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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="rr_text"></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 width="1.381in" class="1">
<col width="1.020in" class="2">
<col width="2.099in" class="3">
</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 width="1.491in" class="1">
<col width="1.067in" class="2">
<col width="2.067in" class="3">
</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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="mx_records"></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 width="1.708in" class="1">
<col width="0.444in" class="2">
<col width="0.444in" class="3">
<col width="0.976in" class="4">
<col width="1.553in" class="5">
</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="section">
<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 width="0.750in" class="1">
<col width="4.375in" class="2">
</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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="ipv4_reverse"></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 width="1.125in" class="1">
<col width="4.000in" class="2">
</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 class="command"><strong>$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="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="zone_directives"></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 class="command"><strong>$ORIGIN</strong></span>, <span class="command"><strong>$INCLUDE</strong></span>,
and <span class="command"><strong>$TTL.</strong></span>
</p>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="atsign"></a>The <span class="command"><strong>@</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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="origin_directive"></a>The <span class="command"><strong>$ORIGIN</strong></span> Directive</h4></div></div></div>
<p>
Syntax: <span class="command"><strong>$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 class="command"><strong>$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 class="command"><strong>$ORIGIN</strong></span>
&lt;<code class="varname">zone_name</code>&gt;<span class="command"><strong>.</strong></span>
(followed by trailing dot).
The current <span class="command"><strong>$ORIGIN</strong></span> is appended to
the domain specified in the <span class="command"><strong>$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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="include_directive"></a>The <span class="command"><strong>$INCLUDE</strong></span> Directive</h4></div></div></div>
<p>
Syntax: <span class="command"><strong>$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 class="command"><strong>origin</strong></span> is
specified the file is processed with <span class="command"><strong>$ORIGIN</strong></span> set
to that value, otherwise the current <span class="command"><strong>$ORIGIN</strong></span> is
used.
</p>
<p>
The origin and the current domain name
revert to the values they had prior to the <span class="command"><strong>$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 class="command"><strong>$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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="ttl_directive"></a>The <span class="command"><strong>$TTL</strong></span> Directive</h4></div></div></div>
<p>
Syntax: <span class="command"><strong>$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 class="command"><strong>$TTL</strong></span>
is defined in RFC 2308.
</p>
</div>
</div>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="generate_directive"></a><acronym class="acronym">BIND</acronym> Master File Extension: the <span class="command"><strong>$GENERATE</strong></span> Directive</h3></div></div></div>
<p>
Syntax: <span class="command"><strong>$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 class="command"><strong>$GENERATE</strong></span>
is used to create a series of resource records that only
differ from each other by an
iterator. <span class="command"><strong>$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 width="0.875in" class="1">
<col width="4.250in" class="2">
</colgroup>
<tbody>
<tr>
<td>
<p><span class="command"><strong>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 class="command"><strong>lhs</strong></span></p>
</td>
<td>
<p>This
describes the owner name of the resource records
to be created. Any single <span class="command"><strong>$</strong></span>
(dollar sign)
symbols within the <span class="command"><strong>lhs</strong></span> string
are replaced by the iterator value.
To get a $ in the output, you need to escape the
<span class="command"><strong>$</strong></span> using a backslash
<span class="command"><strong>\</strong></span>,
e.g. <span class="command"><strong>\$</strong></span>. The
<span class="command"><strong>$</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 class="command"><strong>{</strong></span> (left brace) immediately following the
<span class="command"><strong>$</strong></span> as
<span class="command"><strong>${offset[,width[,base]]}</strong></span>.
For example, <span class="command"><strong>${-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 class="command"><strong>d</strong></span>), octal
(<span class="command"><strong>o</strong></span>), hexadecimal
(<span class="command"><strong>x</strong></span> or <span class="command"><strong>X</strong></span>
for uppercase) and nibble
(<span class="command"><strong>n</strong></span> or <span class="command"><strong>N</strong></span>\
for uppercase). The default modifier is
<span class="command"><strong>${0,0,d}</strong></span>. If the
<span class="command"><strong>lhs</strong></span> is not absolute, the
current <span class="command"><strong>$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 class="command"><strong>$$</strong></span> is still recognized as
indicating a literal $ in the output.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>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 class="command"><strong>class</strong></span>
and <span class="command"><strong>ttl</strong></span> can be
entered in either order.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>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 class="command"><strong>class</strong></span>
and <span class="command"><strong>ttl</strong></span> can be
entered in either order.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>type</strong></span></p>
</td>
<td>
<p>
Any valid type.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>rhs</strong></span></p>
</td>
<td>
<p>
<span class="command"><strong>rhs</strong></span>, optionally, quoted string.
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
The <span class="command"><strong>$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="section">
<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 class="command"><strong>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 class="command"><strong>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 class="command"><strong>masterfile-format</strong></span> option) when
<span class="command"><strong>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 class="command"><strong>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 class="command"><strong>named-compilezone</strong></span> command again.
</p>
<p>
Note that <span class="command"><strong>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="section">
<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 width="3.300in" class="1">
<col width="2.625in" class="2">
</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 class="command"><strong>zone-statistics</strong></span> is set to
<strong class="userinput"><code>full</code></strong> (or <strong class="userinput"><code>yes</code></strong>
for backward compatibility. See the description of
<span class="command"><strong>zone-statistics</strong></span> in <a class="xref" href="Bv9ARM.ch06.html#options" title="options Statement Definition and Usage">the section called &#8220;<span class="command"><strong>options</strong></span> Statement Definition and
Usage&#8221;</a>
for further details.
</p>
<p>
These statistics counters are shown with their zone and
view names. The view name is omitted when the server is
not configured with explicit views.</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 class="command"><strong>statistics-file</strong></span> configuration option.
The other is remotely accessible via a statistics channel
when the <span class="command"><strong>statistics-channels</strong></span> statement
is specified in the configuration file
(see <a class="xref" href="Bv9ARM.ch06.html#statschannels" title="statistics-channels Statement Grammar">the section called &#8220;<span class="command"><strong>statistics-channels</strong></span> Statement Grammar&#8221;</a>.)
</p>
<div class="section">
<div class="titlepage"><div><div><h3 class="title">
<a name="statsfile"></a>The Statistics File</h3></div></div></div>
<p>
The text format statistics dump begins with a line, like:
</p>
<p>
<span class="command"><strong>+++ 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 class="command"><strong>++ 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 class="command"><strong>--- Statistics Dump --- (973798949)</strong></span>
</p>
</div>
<div class="section">
<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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="stats_counters"></a>Name Server Statistics Counters</h4></div></div></div>
<div class="informaltable"><table border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="1.150in" class="2">
<col width="3.350in" class="3">
</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 class="command"><strong>Requestv4</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RQ</strong></span></p>
</td>
<td>
<p>
IPv4 requests received.
Note: this also counts non query requests.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Requestv6</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RQ</strong></span></p>
</td>
<td>
<p>
IPv6 requests received.
Note: this also counts non query requests.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ReqEdns0</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Requests with EDNS(0) received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ReqBadEDNSVer</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Requests with unsupported EDNS version received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ReqTSIG</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Requests with TSIG received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ReqSIG0</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Requests with SIG(0) received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ReqBadSIG</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Requests with invalid (TSIG or SIG(0)) signature.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ReqTCP</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RTCP</strong></span></p>
</td>
<td>
<p>
TCP requests received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>AuthQryRej</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RUQ</strong></span></p>
</td>
<td>
<p>
Authoritative (non recursive) queries rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>RecQryRej</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RURQ</strong></span></p>
</td>
<td>
<p>
Recursive queries rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>XfrRej</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RUXFR</strong></span></p>
</td>
<td>
<p>
Zone transfer requests rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>UpdateRej</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RUUpd</strong></span></p>
</td>
<td>
<p>
Dynamic update requests rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Response</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SAns</strong></span></p>
</td>
<td>
<p>
Responses sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>RespTruncated</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Truncated responses sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>RespEDNS0</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Responses with EDNS(0) sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>RespTSIG</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Responses with TSIG sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>RespSIG0</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Responses with SIG(0) sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QrySuccess</strong></span></p>
</td>
<td>
<p><span class="command"><strong></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 class="command"><strong>success</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryAuthAns</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Queries resulted in authoritative answer.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryNoauthAns</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SNaAns</strong></span></p>
</td>
<td>
<p>
Queries resulted in non authoritative answer.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryReferral</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Queries resulted in referral answer.
This corresponds to the
<span class="command"><strong>referral</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryNxrrset</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Queries resulted in NOERROR responses with no data.
This corresponds to the
<span class="command"><strong>nxrrset</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QrySERVFAIL</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SFail</strong></span></p>
</td>
<td>
<p>
Queries resulted in SERVFAIL.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryFORMERR</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SFErr</strong></span></p>
</td>
<td>
<p>
Queries resulted in FORMERR.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryNXDOMAIN</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SNXD</strong></span></p>
</td>
<td>
<p>
Queries resulted in NXDOMAIN.
This corresponds to the
<span class="command"><strong>nxdomain</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryRecursion</strong></span></p>
</td>
<td>
<p><span class="command"><strong>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 class="command"><strong>recursion</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryDuplicate</strong></span></p>
</td>
<td>
<p><span class="command"><strong>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 class="command"><strong>duplicate</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryDropped</strong></span></p>
</td>
<td>
<p><span class="command"><strong></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 class="command"><strong>clients-per-query</strong></span>
and
<span class="command"><strong>max-clients-per-query</strong></span>
options
(see the description about
<a class="xref" href="Bv9ARM.ch06.html#clients-per-query"><span class="command"><strong>clients-per-query</strong></span></a>.)
This corresponds to the
<span class="command"><strong>dropped</strong></span> counter
of previous versions of
<acronym class="acronym">BIND</acronym> 9.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryFailure</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Other query failures.
This corresponds to the
<span class="command"><strong>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 class="command"><strong>AuthQryRej</strong></span> and
<span class="command"><strong>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 class="command"><strong>QryNXRedir</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Queries resulted in NXDOMAIN that were redirected.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryNXRedirRLookup</strong></span></p>
</td>
<td>
<p><span class="command"><strong></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 class="command"><strong>XfrReqDone</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Requested zone transfers completed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>UpdateReqFwd</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Update requests forwarded.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>UpdateRespFwd</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Update responses forwarded.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>UpdateFwdFail</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Dynamic update forward failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>UpdateDone</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Dynamic updates completed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>UpdateFail</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Dynamic updates failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>UpdateBadPrereq</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Dynamic updates rejected due to prerequisite failure.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>RateDropped</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Responses dropped by rate limits.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>RateSlipped</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Responses truncated by rate limits.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>RPZRewrites</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Response policy zone rewrites.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="zone_stats"></a>Zone Maintenance Statistics Counters</h4></div></div></div>
<div class="informaltable"><table border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="3.350in" class="2">
</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 class="command"><strong>NotifyOutv4</strong></span></p>
</td>
<td>
<p>
IPv4 notifies sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>NotifyOutv6</strong></span></p>
</td>
<td>
<p>
IPv6 notifies sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>NotifyInv4</strong></span></p>
</td>
<td>
<p>
IPv4 notifies received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>NotifyInv6</strong></span></p>
</td>
<td>
<p>
IPv6 notifies received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>NotifyRej</strong></span></p>
</td>
<td>
<p>
Incoming notifies rejected.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>SOAOutv4</strong></span></p>
</td>
<td>
<p>
IPv4 SOA queries sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>SOAOutv6</strong></span></p>
</td>
<td>
<p>
IPv6 SOA queries sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>AXFRReqv4</strong></span></p>
</td>
<td>
<p>
IPv4 AXFR requested.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>AXFRReqv6</strong></span></p>
</td>
<td>
<p>
IPv6 AXFR requested.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>IXFRReqv4</strong></span></p>
</td>
<td>
<p>
IPv4 IXFR requested.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>IXFRReqv6</strong></span></p>
</td>
<td>
<p>
IPv6 IXFR requested.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>XfrSuccess</strong></span></p>
</td>
<td>
<p>
Zone transfer requests succeeded.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>XfrFail</strong></span></p>
</td>
<td>
<p>
Zone transfer requests failed.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="resolver_stats"></a>Resolver Statistics Counters</h4></div></div></div>
<div class="informaltable"><table border="1">
<colgroup>
<col width="1.150in" class="1">
<col width="1.150in" class="2">
<col width="3.350in" class="3">
</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 class="command"><strong>Queryv4</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SFwdQ</strong></span></p>
</td>
<td>
<p>
IPv4 queries sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Queryv6</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SFwdQ</strong></span></p>
</td>
<td>
<p>
IPv6 queries sent.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Responsev4</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RR</strong></span></p>
</td>
<td>
<p>
IPv4 responses received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Responsev6</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RR</strong></span></p>
</td>
<td>
<p>
IPv6 responses received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>NXDOMAIN</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RNXD</strong></span></p>
</td>
<td>
<p>
NXDOMAIN received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>SERVFAIL</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RFail</strong></span></p>
</td>
<td>
<p>
SERVFAIL received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>FORMERR</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RFErr</strong></span></p>
</td>
<td>
<p>
FORMERR received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>OtherError</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RErr</strong></span></p>
</td>
<td>
<p>
Other errors received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>EDNS0Fail</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
EDNS(0) query failures.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Mismatch</strong></span></p>
</td>
<td>
<p><span class="command"><strong>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 class="command"><strong>port</strong></span> option.)
This may be an indication of a cache
poisoning attempt.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Truncated</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Truncated responses received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Lame</strong></span></p>
</td>
<td>
<p><span class="command"><strong>RLame</strong></span></p>
</td>
<td>
<p>
Lame delegations received.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>Retry</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SDupQ</strong></span></p>
</td>
<td>
<p>
Query retries performed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QueryAbort</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Queries aborted due to quota control.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QuerySockFail</strong></span></p>
</td>
<td>
<p><span class="command"><strong></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 class="command"><strong>QueryTimeout</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Query timeouts.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>GlueFetchv4</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SSysQ</strong></span></p>
</td>
<td>
<p>
IPv4 NS address fetches invoked.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>GlueFetchv6</strong></span></p>
</td>
<td>
<p><span class="command"><strong>SSysQ</strong></span></p>
</td>
<td>
<p>
IPv6 NS address fetches invoked.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>GlueFetchv4Fail</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
IPv4 NS address fetch failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>GlueFetchv6Fail</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
IPv6 NS address fetch failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ValAttempt</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
DNSSEC validation attempted.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ValOk</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
DNSSEC validation succeeded.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ValNegOk</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
DNSSEC validation on negative information succeeded.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>ValFail</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
DNSSEC validation failed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>QryRTTnn</strong></span></p>
</td>
<td>
<p><span class="command"><strong></strong></span></p>
</td>
<td>
<p>
Frequency table on round trip times (RTTs) of
queries.
Each <span class="command"><strong>nn</strong></span> specifies the corresponding
frequency.
In the sequence of
<span class="command"><strong>nn_1</strong></span>,
<span class="command"><strong>nn_2</strong></span>,
...,
<span class="command"><strong>nn_m</strong></span>,
the value of <span class="command"><strong>nn_i</strong></span> is the
number of queries whose RTTs are between
<span class="command"><strong>nn_(i-1)</strong></span> (inclusive) and
<span class="command"><strong>nn_i</strong></span> (exclusive) milliseconds.
For the sake of convenience we define
<span class="command"><strong>nn_0</strong></span> to be 0.
The last entry should be represented as
<span class="command"><strong>nn_m+</strong></span>, which means the
number of queries whose RTTs are equal to or over
<span class="command"><strong>nn_m</strong></span> milliseconds.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="socket_stats"></a>Socket I/O Statistics Counters</h4></div></div></div>
<p>
Socket I/O statistics counters are defined per socket
types, which are
<span class="command"><strong>UDP4</strong></span> (UDP/IPv4),
<span class="command"><strong>UDP6</strong></span> (UDP/IPv6),
<span class="command"><strong>TCP4</strong></span> (TCP/IPv4),
<span class="command"><strong>TCP6</strong></span> (TCP/IPv6),
<span class="command"><strong>Unix</strong></span> (Unix Domain), and
<span class="command"><strong>FDwatch</strong></span> (sockets opened outside the
socket module).
In the following table <span class="command"><strong>&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 width="1.150in" class="1">
<col width="3.350in" class="2">
</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 class="command"><strong>&lt;TYPE&gt;Open</strong></span></p>
</td>
<td>
<p>
Sockets opened successfully.
This counter is not applicable to the
<span class="command"><strong>FDwatch</strong></span> type.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&lt;TYPE&gt;OpenFail</strong></span></p>
</td>
<td>
<p>
Failures of opening sockets.
This counter is not applicable to the
<span class="command"><strong>FDwatch</strong></span> type.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&lt;TYPE&gt;Close</strong></span></p>
</td>
<td>
<p>
Sockets closed.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&lt;TYPE&gt;BindFail</strong></span></p>
</td>
<td>
<p>
Failures of binding sockets.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&lt;TYPE&gt;ConnFail</strong></span></p>
</td>
<td>
<p>
Failures of connecting sockets.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&lt;TYPE&gt;Conn</strong></span></p>
</td>
<td>
<p>
Connections established successfully.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&lt;TYPE&gt;AcceptFail</strong></span></p>
</td>
<td>
<p>
Failures of accepting incoming connection requests.
This counter is not applicable to the
<span class="command"><strong>UDP</strong></span> and
<span class="command"><strong>FDwatch</strong></span> types.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&lt;TYPE&gt;Accept</strong></span></p>
</td>
<td>
<p>
Incoming connections successfully accepted.
This counter is not applicable to the
<span class="command"><strong>UDP</strong></span> and
<span class="command"><strong>FDwatch</strong></span> types.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&lt;TYPE&gt;SendErr</strong></span></p>
</td>
<td>
<p>
Errors in socket send operations.
This counter corresponds
to <span class="command"><strong>SErr</strong></span> counter of
<span class="command"><strong>BIND</strong></span> 8.
</p>
</td>
</tr>
<tr>
<td>
<p><span class="command"><strong>&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="section">
<div class="titlepage"><div><div><h4 class="title">
<a name="bind8_compatibility"></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 class="command"><strong>BIND</strong></span> 8 are also supported in
<span class="command"><strong>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 class="variablelist">
<dt><span class="term"><span class="command"><strong>RFwdR,SFwdR</strong></span></span></dt>
<dd><p>
These counters are not supported
because <span class="command"><strong>BIND</strong></span> 9 does not adopt
the notion of <span class="emphasis"><em>forwarding</em></span>
as <span class="command"><strong>BIND</strong></span> 8 did.
</p></dd>
<dt><span class="term"><span class="command"><strong>RAXFR</strong></span></span></dt>
<dd><p>
This counter is accessible in the Incoming Queries section.
</p></dd>
<dt><span class="term"><span class="command"><strong>RIQ</strong></span></span></dt>
<dd><p>
This counter is accessible in the Incoming Requests section.
</p></dd>
<dt><span class="term"><span class="command"><strong>ROpts</strong></span></span></dt>
<dd><p>
This counter is not supported
because <span class="command"><strong>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 xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0b1</p>
</body>
</html>