Bv9ARM.ch04.html revision af40ebed6257e4ac1996144530b3de317cf4da11
1fdd2470b625a58b57d0b155e6caf8c4fc0afe8aAutomatic Updater - Copyright (C) 2004-2015 Internet Systems Consortium, Inc. ("ISC")
75c0816e8295e180f4bc7f10db3d0d880383bc1cMark Andrews - Copyright (C) 2000-2003 Internet Software Consortium.
4a14ce5ba00ab7bc55c99ffdcf59c7a4ab902721Automatic Updater - Permission to use, copy, modify, and/or distribute this software for any
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - purpose with or without fee is hereby granted, provided that the above
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - copyright notice and this permission notice appear in all copies.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein - PERFORMANCE OF THIS SOFTWARE.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
e21a2904f02a03fa06b6db04d348f65fe9c67b2bMark Andrews<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<link rel="prev" href="Bv9ARM.ch03.html" title="Chapter�3.�Name Server Configuration">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<link rel="next" href="Bv9ARM.ch05.html" title="Chapter�5.�The BIND 9 Lightweight Resolver">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<tr><th colspan="3" align="center">Chapter�4.�Advanced DNS Features</th></tr>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a accesskey="p" href="Bv9ARM.ch03.html">Prev</a>�</td>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch05.html">Next</a>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h1 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="Bv9ARM.ch04"></a>Chapter�4.�Advanced DNS Features</h1></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#notify">Notify</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#split_dns">Split DNS</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dd><dl><dt><span class="section"><a href="Bv9ARM.ch04.html#split_dns_sample">Example split DNS setup</a></span></dt></dl></dd>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.5">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.6">Copying the Shared Secret to Both Machines</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.7">Informing the Servers of the Key's Existence</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.8">Instructing the Server to Use the Key</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.9">TSIG Key Based Access Control</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.6.10">Errors</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#tkey">TKEY</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#sig0">SIG(0)</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_keys">Generating Keys</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_signing">Signing the Zone</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec_config">Configuring Servers</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#dnssec.dynamic.zones">DNSSEC, Dynamic Zones, and Automatic Signing</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.3">Converting from insecure to secure</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.8">Dynamic DNS update method</a></span></dt>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.16">Fully automatic zone signing</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.25">Private-type records</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.32">DNSKEY rollovers</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.34">Dynamic DNS update method</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.39">Automatic key rollovers</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.41">NSEC3PARAM rollovers via UPDATE</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.43">Converting from NSEC to NSEC3</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.45">Converting from NSEC3 to NSEC</a></span></dt>
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.47">Converting from secure to insecure</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.51">Periodic re-signing</a></span></dt>
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.10.53">NSEC3 and OPTOUT</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#rfc5011.support">Dynamic Trust Anchor Management</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.3">Validating Resolver</a></span></dt>
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.11.4">Authoritative Server</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#pkcs11">PKCS#11 (Cryptoki) support</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.6">Prerequisites</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.7">Native PKCS#11</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.8">OpenSSL-based PKCS#11</a></span></dt>
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.9">PKCS#11 Tools</a></span></dt>
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.10">Using the HSM</a></span></dt>
58d9e9169e7ab4355a0b0bfc13bc616bc5247dfeAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.11">Specifying the engine on the command line</a></span></dt>
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.12.12">Running named with automatic zone re-signing</a></span></dt>
58d9e9169e7ab4355a0b0bfc13bc616bc5247dfeAutomatic Updater<dt><span class="section"><a href="Bv9ARM.ch04.html#dlz-info">DLZ (Dynamically Loadable Zones)</a></span></dt>
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.6">Configuring DLZ</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.13.7">Sample DLZ Driver</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#dyndb-info">DynDB (Dynamic Database)</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.14.5">Configuring DynDB</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.14.6">Sample DynDB Module</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#ipv6">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.15.6">Address Lookups Using AAAA Records</a></span></dt>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<dt><span class="section"><a href="Bv9ARM.ch04.html#id-1.5.15.7">Address to Name Lookups Using Nibble Format</a></span></dt>
852ccdd42a71550c974111b49415204ffeca6573Automatic Updater<div class="titlepage"><div><div><h2 class="title" style="clear: both">
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<a name="notify"></a>Notify</h2></div></div></div>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater <acronym class="acronym">DNS</acronym> NOTIFY is a mechanism that allows master
ca67ebfe9eef0b8f04179f7e511a19e0337a5422Automatic Updater servers to notify their slave servers of changes to a zone's data. In
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater response to a <span class="command"><strong>NOTIFY</strong></span> from a master server, the
852ccdd42a71550c974111b49415204ffeca6573Automatic Updater slave will check to see that its version of the zone is the
852ccdd42a71550c974111b49415204ffeca6573Automatic Updater current version and, if not, initiate a zone transfer.
852ccdd42a71550c974111b49415204ffeca6573Automatic Updater For more information about <acronym class="acronym">DNS</acronym>
acb72d5e2c83b597332e3eb0c7d59e1142f1adfdMark Andrews <span class="command"><strong>NOTIFY</strong></span>, see the description of the
acb72d5e2c83b597332e3eb0c7d59e1142f1adfdMark Andrews <span class="command"><strong>notify</strong></span> option in <a class="xref" href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a> and
acb72d5e2c83b597332e3eb0c7d59e1142f1adfdMark Andrews the description of the zone option <span class="command"><strong>also-notify</strong></span> in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <a class="xref" href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. The <span class="command"><strong>NOTIFY</strong></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein protocol is specified in RFC 1996.
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater As a slave zone can also be a master to other slaves, <span class="command"><strong>named</strong></span>,
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater by default, sends <span class="command"><strong>NOTIFY</strong></span> messages for every zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein it loads. Specifying <span class="command"><strong>notify master-only;</strong></span> will
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein cause <span class="command"><strong>named</strong></span> to only send <span class="command"><strong>NOTIFY</strong></span> for master
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein zones that it loads.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h2 class="title" style="clear: both">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="dynamic_update"></a>Dynamic Update</h2></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Dynamic Update is a method for adding, replacing or deleting
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein records in a master server by sending it a special form of DNS
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein messages. The format and meaning of these messages is specified
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein in RFC 2136.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Dynamic update is enabled by including an
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>allow-update</strong></span> or an <span class="command"><strong>update-policy</strong></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein clause in the <span class="command"><strong>zone</strong></span> statement.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein If the zone's <span class="command"><strong>update-policy</strong></span> is set to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <strong class="userinput"><code>local</code></strong>, updates to the zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein will be permitted for the key <code class="varname">local-ddns</code>,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein which will be generated by <span class="command"><strong>named</strong></span> at startup.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein See <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a> for more details.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Dynamic updates using Kerberos signed requests can be made
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein using the TKEY/GSS protocol by setting either the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>tkey-gssapi-keytab</strong></span> option, or alternatively
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein by setting both the <span class="command"><strong>tkey-gssapi-credential</strong></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein and <span class="command"><strong>tkey-domain</strong></span> options. Once enabled,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Kerberos signed requests will be matched against the update
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein policies for the zone, using the Kerberos principal as the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein signer for the request.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Updating of secure zones (zones using DNSSEC) follows RFC
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 3007: RRSIG, NSEC and NSEC3 records affected by updates are
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein automatically regenerated by the server using an online
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein zone key. Update authorization is based on transaction
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein signatures and an explicit server policy.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="journal"></a>The journal file</h3></div></div></div>
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews All changes made to a zone using dynamic update are stored
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein in the zone's journal file. This file is automatically created
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein by the server when the first dynamic update takes place.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The name of the journal file is formed by appending the extension
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <code class="filename">.jnl</code> to the name of the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein corresponding zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein file unless specifically overridden. The journal file is in a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein binary format and should not be edited manually.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The server will also occasionally write ("dump")
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the complete contents of the updated zone to its zone file.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This is not done immediately after
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein each dynamic update, because that would be too slow when a large
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein zone is updated frequently. Instead, the dump is delayed by
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews up to 15 minutes, allowing additional updates to take place.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein During the dump process, transient files will be created
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein with the extensions <code class="filename">.jnw</code> and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <code class="filename">.jbk</code>; under ordinary circumstances, these
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein will be removed when the dump is complete, and can be safely
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein When a server is restarted after a shutdown or crash, it will replay
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the journal file to incorporate into the zone any updates that
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews place after the last zone dump.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Changes that result from incoming incremental zone transfers are
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein journalled in a similar way.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The zone files of dynamic zones cannot normally be edited by
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater hand because they are not guaranteed to contain the most recent
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein dynamic changes — those are only in the journal file.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The only way to ensure that the zone file of a dynamic zone
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews is up to date is to run <span class="command"><strong>rndc stop</strong></span>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein If you have to make changes to a dynamic zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein manually, the following procedure will work:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Disable dynamic updates to the zone using
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>rndc freeze <em class="replaceable"><code>zone</code></em></strong></span>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This will update the zone's master file with the changes
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein stored in its <code class="filename">.jnl</code> file.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Edit the zone file. Run
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>rndc thaw <em class="replaceable"><code>zone</code></em></strong></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to reload the changed zone and re-enable dynamic updates.
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews <span class="command"><strong>rndc sync <em class="replaceable"><code>zone</code></em></strong></span>
a1b05dea35aa30b152a47115e18bbe679d3fcf19Mark Andrews will update the zone file with changes from the journal file
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews without stopping dynamic updates; this may be useful for viewing
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the current zone state. To remove the <code class="filename">.jnl</code>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein file after updating the zone file, use
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>rndc sync -clean</strong></span>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h2 class="title" style="clear: both">
bea931e17b7567f09107f93ab7e25c7f00abeb9cMark Andrews<a name="incremental_zone_transfers"></a>Incremental Zone Transfers (IXFR)</h2></div></div></div>
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater The incremental zone transfer (IXFR) protocol is a way for
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein slave servers to transfer only changed data, instead of having to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein transfer the entire zone. The IXFR protocol is specified in RFC
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 1995. See <a class="xref" href="Bv9ARM.ch11.html#proposed_standards" title="Proposed Standards">Proposed Standards</a>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein When acting as a master, <acronym class="acronym">BIND</acronym> 9
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein supports IXFR for those zones
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein where the necessary change history information is available. These
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein include master zones maintained by dynamic update and slave zones
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein whose data was obtained by IXFR. For manually maintained master
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein zones, and for slave zones obtained by performing a full zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein transfer (AXFR), IXFR is supported only if the option
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>ixfr-from-differences</strong></span> is set
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to <strong class="userinput"><code>yes</code></strong>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein When acting as a slave, <acronym class="acronym">BIND</acronym> 9 will
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein attempt to use IXFR unless
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein it is explicitly disabled. For more information about disabling
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein IXFR, see the description of the <span class="command"><strong>request-ixfr</strong></span> clause
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein of the <span class="command"><strong>server</strong></span> statement.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h2 class="title" style="clear: both">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="split_dns"></a>Split DNS</h2></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Setting up different views, or visibility, of the DNS space to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein internal and external resolvers is usually referred to as a
2cc6eb92f9443695bc32fa6eed372d983d261a35Automatic Updater <span class="emphasis"><em>Split DNS</em></span> setup. There are several
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein reasons an organization would want to set up its DNS this way.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein One common reason for setting up a DNS system this way is
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to hide "internal" DNS information from "external" clients on the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Internet. There is some debate as to whether or not this is actually
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Internal DNS information leaks out in many ways (via email headers,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein for example) and most savvy "attackers" can find the information
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein they need using other means.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein However, since listing addresses of internal servers that
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein external clients cannot possibly reach can result in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein connection delays and other annoyances, an organization may
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein choose to use a Split DNS to present a consistent view of itself
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to the outside world.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Another common reason for setting up a Split DNS system is
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to allow internal networks that are behind filters or in RFC 1918
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein space (reserved IP space, as documented in RFC 1918) to resolve DNS
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein on the Internet. Split DNS can also be used to allow mail from outside
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein back in to the internal network.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="split_dns_sample"></a>Example split DNS setup</h3></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Let's say a company named <span class="emphasis"><em>Example, Inc.</em></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein has several corporate sites that have an internal network with
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Internet Protocol (IP) space and an external demilitarized zone (DMZ),
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein or "outside" section of a network, that is available to the public.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="emphasis"><em>Example, Inc.</em></span> wants its internal clients
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to be able to resolve external hostnames and to exchange mail with
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein people on the outside. The company also wants its internal resolvers
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to have access to certain internal-only zones that are not available
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein at all outside of the internal network.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein In order to accomplish this, the company will set up two sets
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein of name servers. One set will be on the inside network (in the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein IP space) and the other set will be on bastion hosts, which are
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein hosts that can talk to both sides of its network, in the DMZ.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The internal servers will be configured to forward all queries,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein except queries for <code class="filename">site1.internal</code>, <code class="filename">site2.internal</code>, <code class="filename">site1.example.com</code>,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein and <code class="filename">site2.example.com</code>, to the servers
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein DMZ. These internal servers will have complete sets of information
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein for <code class="filename">site1.example.com</code>, <code class="filename">site2.example.com</code>, <code class="filename">site1.internal</code>,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein and <code class="filename">site2.internal</code>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein To protect the <code class="filename">site1.internal</code> and <code class="filename">site2.internal</code> domains,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the internal name servers must be configured to disallow all queries
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to these domains from any external hosts, including the bastion
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The external servers, which are on the bastion hosts, will
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein be configured to serve the "public" version of the <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This could include things such as the host records for public servers
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein (<code class="filename">www.example.com</code> and <code class="filename">ftp.example.com</code>),
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein and mail exchange (MX) records (<code class="filename">a.mx.example.com</code> and <code class="filename">b.mx.example.com</code>).
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein In addition, the public <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein should have special MX records that contain wildcard (`*') records
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein pointing to the bastion hosts. This is needed because external mail
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein servers do not have any other way of looking up how to deliver mail
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to those internal hosts. With the wildcard records, the mail will
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein be delivered to the bastion host, which can then forward it on to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein internal hosts.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Here's an example of a wildcard MX record:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<pre class="programlisting">* IN MX 10 external1.example.com.</pre>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Now that they accept mail on behalf of anything in the internal
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein network, the bastion hosts will need to know how to deliver mail
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to internal hosts. In order for this to work properly, the resolvers
c71787bd6356c92e9c7d0a174cd63ab17fcf34c6Eric Luce the bastion hosts will need to be configured to point to the internal
c71787bd6356c92e9c7d0a174cd63ab17fcf34c6Eric Luce name servers for DNS resolution.
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce Queries for internal hostnames will be answered by the internal
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce servers, and queries for external hostnames will be forwarded back
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce out to the DNS servers on the bastion hosts.
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater In order for all this to work properly, internal clients will
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews need to be configured to query <span class="emphasis"><em>only</em></span> the internal
c71787bd6356c92e9c7d0a174cd63ab17fcf34c6Eric Luce name servers for DNS queries. This could also be enforced via
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater filtering on the network.
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater If everything has been set properly, <span class="emphasis"><em>Example, Inc.</em></span>'s
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater internal clients will now be able to:
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
c71787bd6356c92e9c7d0a174cd63ab17fcf34c6Eric Luce Look up any hostnames in the <code class="literal">site1</code>
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <code class="literal">site2.example.com</code> zones.
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater Look up any hostnames in the <code class="literal">site1.internal</code> and
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <code class="literal">site2.internal</code> domains.
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce<li class="listitem">Look up any hostnames on the Internet.</li>
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce<li class="listitem">Exchange mail with both internal and external people.</li>
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater Hosts on the Internet will be able to:
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce<div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; ">
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce Look up any hostnames in the <code class="literal">site1</code>
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce <code class="literal">site2.example.com</code> zones.
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce Exchange mail with anyone in the <code class="literal">site1</code> and
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce <code class="literal">site2.example.com</code> zones.
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce Here is an example configuration for the setup we just
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce described above. Note that this is only configuration information;
c71787bd6356c92e9c7d0a174cd63ab17fcf34c6Eric Luce for information on how to configure your zone files, see <a class="xref" href="Bv9ARM.ch03.html#sample_configuration" title="Sample Configurations">the section called “Sample Configurations”</a>.
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce Internal DNS server config:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinacl externals { <code class="varname">bastion-ips-go-here</code>; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein forward only;
c71787bd6356c92e9c7d0a174cd63ab17fcf34c6Eric Luce // forward to external servers
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce forwarders {
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce // sample allow-transfer (no one)
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce allow-transfer { none; };
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater // restrict query access
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater allow-query { internals; externals; };
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater // restrict recursion
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater allow-recursion { internals; };
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce// sample master zone
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce type master;
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater // do normal iterative resolution (do not forward)
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater forwarders { };
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce allow-query { internals; externals; };
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce allow-transfer { internals; };
c71787bd6356c92e9c7d0a174cd63ab17fcf34c6Eric Luce// sample slave zone
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce masters { 172.16.72.3; };
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce forwarders { };
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce allow-query { internals; externals; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein allow-transfer { internals; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein type master;
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein forwarders { };
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce allow-query { internals; };
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce allow-transfer { internals; }
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein masters { 172.16.72.3; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein forwarders { };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein allow-query { internals };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein allow-transfer { internals; }
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews External (bastion host) DNS server config:
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrewsacl internals { 172.16.72.0/24; 192.168.1.0/24; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinacl externals { bastion-ips-go-here; };
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews // sample allow-transfer (no one)
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews allow-transfer { none; };
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews // default query access
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein allow-query { any; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein // restrict cache access
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein allow-query-cache { internals; externals; };
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews // restrict recursion
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews allow-recursion { internals; externals; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein// sample slave zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein type master;
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein allow-transfer { internals; externals; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein masters { another_bastion_host_maybe; };
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein allow-transfer { internals; externals; }
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein In the <code class="filename">resolv.conf</code> (or equivalent) on
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the bastion host(s):
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinnameserver 172.16.72.2
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinnameserver 172.16.72.3
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinnameserver 172.16.72.4
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h2 class="title" style="clear: both">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This is a short guide to setting up Transaction SIGnatures
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein (TSIG) based transaction security in <acronym class="acronym">BIND</acronym>. It describes changes
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater to the configuration file as well as what changes are required for
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein different features, including the process of creating transaction
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein keys and using transaction signatures with <acronym class="acronym">BIND</acronym>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <acronym class="acronym">BIND</acronym> primarily supports TSIG for server
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to server communication.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This includes zone transfer, notify, and recursive query messages.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Resolvers based on newer versions of <acronym class="acronym">BIND</acronym> 8 have limited support
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein TSIG can also be useful for dynamic update. A primary
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein server for a dynamic zone should control access to the dynamic
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein update service, but IP-based access control is insufficient.
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater The cryptographic access control provided by TSIG
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein is far superior. The <span class="command"><strong>nsupdate</strong></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein program supports TSIG via the <code class="option">-k</code> and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <code class="option">-y</code> command line options or inline by use
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein of the <span class="command"><strong>key</strong></span>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<a name="id-1.5.6.5"></a>Generate Shared Keys for Each Pair of Hosts</h3></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein A shared secret is generated to be shared between <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host2</em></span>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein An arbitrary key name is chosen: "host1-host2.". The key name must
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein be the same on both hosts.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h4 class="title">
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce<a name="id-1.5.6.5.3"></a>Automatic Generation</h4></div></div></div>
f293a69bcd1c1dd7bdac8f4102fc2398b9e475c8Eric Luce The following command will generate a 128-bit (16 byte) HMAC-SHA256
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein key as described above. Longer keys are better, but shorter keys
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein are easier to read. Note that the maximum key length is the digest
9c6a5d1f22f972232d7a9fd5c5fa64f10bacbdffAutomatic Updater length, here 256 bits.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <strong class="userinput"><code>dnssec-keygen -a hmac-sha256 -b 128 -n HOST host1-host2.</code></strong>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The key is in the file <code class="filename">Khost1-host2.+163+00000.private</code>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Nothing directly uses this file, but the base-64 encoded string
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein can be extracted from the file and used as a shared secret:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<pre class="programlisting">Key: La/E5CjG9O+os1jq0a2jdA==</pre>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The string "<code class="literal">La/E5CjG9O+os1jq0a2jdA==</code>" can
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein be used as the shared secret.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h4 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="id-1.5.6.5.4"></a>Manual Generation</h4></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The shared secret is simply a random sequence of bits, encoded
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein in base-64. Most ASCII strings are valid base-64 strings (assuming
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the length is a multiple of 4 and only valid characters are used),
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein so the shared secret can be manually generated.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Also, a known string can be run through <span class="command"><strong>mmencode</strong></span> or
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein a similar program to generate base-64 encoded data.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="id-1.5.6.6"></a>Copying the Shared Secret to Both Machines</h3></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This is beyond the scope of DNS. A secure transport mechanism
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein should be used. This could be secure FTP, ssh, telephone, etc.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="id-1.5.6.7"></a>Informing the Servers of the Key's Existence</h3></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Imagine <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host 2</em></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein both servers. The following is added to each server's <code class="filename">named.conf</code> file:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinkey host1-host2. {
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews algorithm hmac-sha256;
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The secret is the one generated above. Since this is a secret, it
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein is recommended that either <code class="filename">named.conf</code> be
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein non-world readable, or the key directive be added to a non-world
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein readable file that is included by <code class="filename">named.conf</code>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein At this point, the key is recognized. This means that if the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein server receives a message signed by this key, it can verify the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein signature. If the signature is successfully verified, the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein response is signed by the same key.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<a name="id-1.5.6.8"></a>Instructing the Server to Use the Key</h3></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Since keys are shared between two hosts only, the server must
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein be told when keys are to be used. The following is added to the <code class="filename">named.conf</code> file
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein for <span class="emphasis"><em>host1</em></span>, if the IP address of <span class="emphasis"><em>host2</em></span> is
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinserver 10.1.2.3 {
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein keys { host1-host2. ;};
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Multiple keys may be present, but only the first is used.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This directive does not contain any secrets, so it may be in a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein world-readable
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein If <span class="emphasis"><em>host1</em></span> sends a message that is a request
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to that address, the message will be signed with the specified key. <span class="emphasis"><em>host1</em></span> will
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein expect any responses to signed messages to be signed with the same
bea931e17b7567f09107f93ab7e25c7f00abeb9cMark Andrews A similar statement must be present in <span class="emphasis"><em>host2</em></span>'s
47012ae6dbf18a2503d7b33c1c9583dc38625cb7Mark Andrews configuration file (with <span class="emphasis"><em>host1</em></span>'s address) for <span class="emphasis"><em>host2</em></span> to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein sign request messages to <span class="emphasis"><em>host1</em></span>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater<a name="id-1.5.6.9"></a>TSIG Key Based Access Control</h3></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <acronym class="acronym">BIND</acronym> allows IP addresses and ranges
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to be specified in ACL
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein definitions and
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews <span class="command"><strong>allow-{ query | transfer | update }</strong></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This has been extended to allow TSIG keys also. The above key would
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein be denoted <span class="command"><strong>key host1-host2.</strong></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein An example of an <span class="command"><strong>allow-update</strong></span> directive would be:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austeinallow-update { key host1-host2. ;};
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This allows dynamic updates to succeed only if the request
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein was signed by a key named "<span class="command"><strong>host1-host2.</strong></span>".
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein See <a class="xref" href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a> for a discussion of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the more flexible <span class="command"><strong>update-policy</strong></span> statement.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="id-1.5.6.10"></a>Errors</h3></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The processing of TSIG signed messages can result in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein several errors. If a signed message is sent to a non-TSIG aware
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein server, a FORMERR (format error) will be returned, since the server will not
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein understand the record. This is a result of misconfiguration,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein since the server must be explicitly configured to send a TSIG
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein signed message to a specific server.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein If a TSIG aware server receives a message signed by an
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews unknown key, the response will be unsigned with the TSIG
a1ad6695ed6f988406cf155aa26376f84f73bcb9Automatic Updater extended error code set to BADKEY. If a TSIG aware server
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein receives a message with a signature that does not validate, the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein response will be unsigned with the TSIG extended error code set
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein to BADSIG. If a TSIG aware server receives a message with a time
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein outside of the allowed range, the response will be signed with
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the TSIG extended error code set to BADTIME, and the time values
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein will be adjusted so that the response can be successfully
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein verified. In any of these cases, the message's rcode (response code) is set to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein NOTAUTH (not authenticated).
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h2 class="title" style="clear: both">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<p><span class="command"><strong>TKEY</strong></span>
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews is a mechanism for automatically generating a shared secret
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein between two hosts. There are several "modes" of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>TKEY</strong></span> that specify how the key is generated
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein or assigned. <acronym class="acronym">BIND</acronym> 9 implements only one of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein these modes, the Diffie-Hellman key exchange. Both hosts are
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein required to have a Diffie-Hellman KEY record (although this
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein record is not required to be present in a zone). The
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>TKEY</strong></span> process must use signed messages,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein signed either by TSIG or SIG(0). The result of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>TKEY</strong></span> is a shared secret that can be used to
bea931e17b7567f09107f93ab7e25c7f00abeb9cMark Andrews sign messages with TSIG. <span class="command"><strong>TKEY</strong></span> can also be
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews used to delete shared secrets that it had previously
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews The <span class="command"><strong>TKEY</strong></span> process is initiated by a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein or server by sending a signed <span class="command"><strong>TKEY</strong></span>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein (including any appropriate KEYs) to a TKEY-aware server. The
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein server response, if it indicates success, will contain a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>TKEY</strong></span> record and any appropriate keys.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein this exchange, both participants have enough information to
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein determine the shared secret; the exact process depends on the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>TKEY</strong></span> mode. When using the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Diffie-Hellman
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>TKEY</strong></span> mode, Diffie-Hellman keys are
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein and the shared secret is derived by both participants.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h2 class="title" style="clear: both">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <acronym class="acronym">BIND</acronym> 9 partially supports DNSSEC SIG(0)
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein transaction signatures as specified in RFC 2535 and RFC 2931.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein uses public/private keys to authenticate messages. Access control
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein is performed in the same manner as TSIG keys; privileges can be
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein granted or denied based on the key name.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein When a SIG(0) signed message is received, it will only be
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein verified if the key is known and trusted by the server; the server
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein will not attempt to locate and/or validate the key.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein SIG(0) signing of multiple-message TCP streams is not
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The only tool shipped with <acronym class="acronym">BIND</acronym> 9 that
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein generates SIG(0) signed messages is <span class="command"><strong>nsupdate</strong></span>.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h2 class="title" style="clear: both">
b05bdb520d83f7ecaad708fe305268c3420be01dMark Andrews<a name="DNSSEC"></a>DNSSEC</h2></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Cryptographic authentication of DNS information is possible
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein through the DNS Security (<span class="emphasis"><em>DNSSEC-bis</em></span>) extensions,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein defined in RFC 4033, RFC 4034, and RFC 4035.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This section describes the creation and use of DNSSEC signed zones.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein In order to set up a DNSSEC secure zone, there are a series
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein of steps which must be followed. <acronym class="acronym">BIND</acronym>
bea931e17b7567f09107f93ab7e25c7f00abeb9cMark Andrews with several tools
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein that are used in this process, which are explained in more detail
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein below. In all cases, the <code class="option">-h</code> option prints a
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein full list of parameters. Note that the DNSSEC tools require the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein keyset files to be in the working directory or the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein directory specified by the <code class="option">-d</code> option, and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein that the tools shipped with BIND 9.2.x and earlier are not compatible
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein with the current ones.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein There must also be communication with the administrators of
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the parent and/or child zone to transmit keys. A zone's security
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein status must be indicated by the parent zone for a DNSSEC capable
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein resolver to trust its data. This is done through the presence
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein or absence of a <code class="literal">DS</code> record at the
28b3569d6248168e6c00caab951521cc8141a49dAutomatic Updater For other servers to trust data in this zone, they must
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein either be statically configured with this zone's zone key or the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein zone key of another zone above this one in the DNS tree.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="titlepage"><div><div><h3 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="dnssec_keys"></a>Generating Keys</h3></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The <span class="command"><strong>dnssec-keygen</strong></span> program is used to
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater generate keys.
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater A secure zone must contain one or more zone keys. The
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein zone keys will sign all other records in the zone, as well as
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the zone keys of any secure delegated zones. Zone keys must
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater have the same name as the zone, a name type of
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater <span class="command"><strong>ZONE</strong></span>, and must be usable for
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater authentication.
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater It is recommended that zone keys use a cryptographic algorithm
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater designated as "mandatory to implement" by the IETF; currently
38417cbfb1a328c20b5b723b8584a02c57f88897Automatic Updater the only one is RSASHA1.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The following command will generate a 768-bit RSASHA1 key for
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the <code class="filename">child.example</code> zone:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <strong class="userinput"><code>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</code></strong>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein Two output files will be produced:
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <code class="filename">Kchild.example.+005+12345.key</code> and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <code class="filename">Kchild.example.+005+12345.private</code>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 12345 is an example of a key tag). The key filenames contain
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the key name (<code class="filename">child.example.</code>),
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein algorithm (3
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein is DSA, 1 is RSAMD5, 5 is RSASHA1, etc.), and the key tag (12345 in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The private key (in the <code class="filename">.private</code>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein used to generate signatures, and the public key (in the
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews <code class="filename">.key</code> file) is used for signature
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein verification.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein To generate another key with the same properties (but with
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein a different key tag), repeat the above command.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The <span class="command"><strong>dnssec-keyfromlabel</strong></span> program is used
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater to get a key pair from a crypto hardware and build the key
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein files. Its usage is similar to <span class="command"><strong>dnssec-keygen</strong></span>.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews The public keys should be inserted into the zone file by
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater including the <code class="filename">.key</code> files using
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>$INCLUDE</strong></span> statements.
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater<div class="titlepage"><div><div><h3 class="title">
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater<a name="dnssec_signing"></a>Signing the Zone</h3></div></div></div>
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater The <span class="command"><strong>dnssec-signzone</strong></span> program is used
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater to sign a zone.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews Any <code class="filename">keyset</code> files corresponding to
47012ae6dbf18a2503d7b33c1c9583dc38625cb7Mark Andrews secure subzones should be present. The zone signer will
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews generate <code class="literal">NSEC</code>, <code class="literal">NSEC3</code>
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews and <code class="literal">RRSIG</code> records for the zone, as
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews well as <code class="literal">DS</code> for the child zones if
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews <code class="literal">'-g'</code> is specified. If <code class="literal">'-g'</code>
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews is not specified, then DS RRsets for the secure child
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews zones need to be added manually.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews The following command signs the zone, assuming it is in a
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews file called <code class="filename">zone.child.example</code>. By
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews default, all zone keys which have an available private key are
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews used to generate signatures.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews <strong class="userinput"><code>dnssec-signzone -o child.example zone.child.example</code></strong>
d3907d27cc138f45772d3d63082ae02c7659148aAutomatic Updater One output file is produced:
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews <code class="filename">zone.child.example.signed</code>. This
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews should be referenced by <code class="filename">named.conf</code>
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews input file for the zone.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews<p><span class="command"><strong>dnssec-signzone</strong></span>
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews will also produce a keyset and dsset files and optionally a
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews dlvset file. These are used to provide the parent zone
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews administrators with the <code class="literal">DNSKEYs</code> (or their
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews corresponding <code class="literal">DS</code> records) that are the
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater secure entry point to the zone.
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater<div class="titlepage"><div><div><h3 class="title">
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater<a name="dnssec_config"></a>Configuring Servers</h3></div></div></div>
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater To enable <span class="command"><strong>named</strong></span> to respond appropriately
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater to DNS requests from DNSSEC aware clients,
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <span class="command"><strong>dnssec-enable</strong></span> must be set to yes.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews (This is the default setting.)
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater To enable <span class="command"><strong>named</strong></span> to validate answers from
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater other servers, the <span class="command"><strong>dnssec-enable</strong></span> option
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater must be set to <strong class="userinput"><code>yes</code></strong>, and the
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <span class="command"><strong>dnssec-validation</strong></span> options must be set to
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <strong class="userinput"><code>yes</code></strong> or <strong class="userinput"><code>auto</code></strong>.
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater If <span class="command"><strong>dnssec-validation</strong></span> is set to
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <strong class="userinput"><code>auto</code></strong>, then a default
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater trust anchor for the DNS root zone will be used.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews If it is set to <strong class="userinput"><code>yes</code></strong>, however,
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews then at least one trust anchor must be configured
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater with a <span class="command"><strong>trusted-keys</strong></span> or
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <span class="command"><strong>managed-keys</strong></span> statement in
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <code class="filename">named.conf</code>, or DNSSEC validation
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater will not occur. The default setting is
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <strong class="userinput"><code>yes</code></strong>.
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <span class="command"><strong>trusted-keys</strong></span> are copies of DNSKEY RRs
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater for zones that are used to form the first link in the
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater cryptographic chain of trust. All keys listed in
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater <span class="command"><strong>trusted-keys</strong></span> (and corresponding zones)
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater are deemed to exist and only the listed keys will be used
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater to validated the DNSKEY RRset that they are from.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews <span class="command"><strong>managed-keys</strong></span> are trusted keys which are
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews automatically kept up to date via RFC 5011 trust anchor
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews maintenance.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews <span class="command"><strong>trusted-keys</strong></span> and
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews <span class="command"><strong>managed-keys</strong></span> are described in more detail
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews later in this document.
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews Unlike <acronym class="acronym">BIND</acronym> 8, <acronym class="acronym">BIND</acronym>
6101b9f0d904a708e900a74abc16d1e0eda67264Mark Andrews 9 does not verify signatures on load, so zone keys for
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater authoritative zones do not need to be specified in the
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater configuration file.
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater After DNSSEC gets established, a typical DNSSEC configuration
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater will look something like the following. It has one or
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater more public keys for the root. This allows answers from
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater outside the organization to be validated. It will also
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater have several keys for parts of the namespace the organization
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater controls. These are here to ensure that <span class="command"><strong>named</strong></span>
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater is immune to compromises in the DNSSEC components of the security
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater of parent zones.
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater /* Root Key */
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater "." initial-key 257 3 3 "BNY4wrWM1nCfJ+CXd0rVXyYmobt7sEEfK3clRbGaTwS
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater JxrGkxJWoZu6I7PzJu/E9gx4UC1zGAHlXKdE4zYIpRh
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater aBKnvcC2U9mZhkdUpd1Vso/HAdjNe8LmMlnzY3zy2Xy
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater 4klWOADTPzSv9eamj8V18PHGjBLaVtYvk/ln5ZApjYg
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater hf+6fElrmLkdaz MQ2OCnACR817DF4BBa7UR/beDHyp
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater 5iWTXWSi6XmoJLbG9Scqc7l70KDqlvXR3M/lUUVRbke
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater g1IPJSidmK3ZyCllh4XSKbje/45SKucHgnwU5jefMtq
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater 66gKodQj+MiA21AfUVe7u99WzTLzY3qlxDhxYQQ20FQ
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater 97S+LKUTpQcq27R7AT3/V5hRQxScINqwcz4jYqZD2fQ
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater dgxbcDTClU0CRBdiieyLMNzXG3";
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater /* Key for our organization's forward zone */
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater example.com. 257 3 5 "AwEAAaxPMcR2x0HbQV4WeZB6oEDX+r0QM6
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater 5KbhTjrW1ZaARmPhEZZe3Y9ifgEuq7vZ/z
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater GZUdEGNWy+JZzus0lUptwgjGwhUS1558Hb
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater 4JKUbbOTcM8pwXlj0EiX3oDFVmjHO444gL
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein g4ywzO9WglMk7jbfW33gUKvirTHr25GL7S
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein TQUzBb5Usxt8lgnyTUHs1t3JwCY5hKZ6Cq
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater F4qJCyduieHukuY3H4XMAcR+xia2nIUPvm
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater /* Key for our reverse zone. */
cbf7f1435f332b31f51a98611ccbfcd07c42c032Automatic Updater 2.0.192.IN-ADDRPA.NET. 257 3 5 "AQOnS4xn/IgOUpBPJ3bogzwc
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein xOdNax071L18QqZnQQQAVVr+i
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein LhGTnNGp3HoWQLUIzKrJVZ3zg
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews gy3WwNT6kZo6c0tszYqbtvchm
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews siaOdS0yOI6BgPsw+YZdzlYMa
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews IJGf4M4dyoKIhzdZyQ2bYQrjy
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews Q4LB0lC7aOnsMyYKHHYeRvPxj
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein IQXmdqgOJGq+vsevG06zW+1xg
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein 59VvjSPsZJHeDCUyWYrvPZesZ
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein DIRvhDD52SKvbheeTJUm6Ehkz
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews dnssec-enable yes;
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews dnssec-validation yes;
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
71c66a876ecca77923638d3f94cc0783152b2f03Mark Andrews None of the keys listed in this example are valid. In particular,
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews the root key is not valid.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein When DNSSEC validation is enabled and properly configured,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein the resolver will reject any answers from signed, secure zones
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein which fail to validate, and will return SERVFAIL to the client.
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater Responses may fail to validate for any of several reasons,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein including missing, expired, or invalid signatures, a key which
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews does not match the DS RRset in the parent zone, or an insecure
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews response from a zone which, according to its parent, should have
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews been secure.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein When the validator receives a response from an unsigned zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein that has a signed parent, it must confirm with the parent
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews that the zone was intentionally left unsigned. It does
5a4557e8de2951a2796676b5ec4b6a90caa5be14Mark Andrews this by verifying, via signed and validated NSEC/NSEC3 records,
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein that the parent zone contains no DS records for the child.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein If the validator <span class="emphasis"><em>can</em></span> prove that the zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein is insecure, then the response is accepted. However, if it
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein cannot, then it must assume an insecure response to be a
3cddb2c552ee6582e8db0849c28747f6b6ca57feAutomatic Updater forgery; it rejects the response and logs an error.
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein The logged error reads "insecurity proof failed" and
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein "got insecure response; parent indicates it should be secure".
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein (Prior to BIND 9.7, the logged error was "not insecure".
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein This referred to the zone, not the response.)
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater<div class="titlepage"><div><div><h2 class="title" style="clear: both">
ac93437301f55ed69bf85883a497a75598c628f9Automatic Updater<a name="dnssec.dynamic.zones"></a>DNSSEC, Dynamic Zones, and Automatic Signing</h2></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<p>As of BIND 9.7.0 it is possible to change a dynamic zone
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein from insecure to signed and back again. A secure zone can use
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein either NSEC or NSEC3 chains.</p>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<div class="section"><div class="titlepage"><div><div><h3 class="title">
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<a name="id-1.5.10.3"></a>Converting from insecure to secure</h3></div></div></div></div>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<p>Changing a zone from insecure to secure can be done in two
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein ways: using a dynamic DNS update, or the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>auto-dnssec</strong></span> zone option.</p>
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein<p>For either method, you need to configure
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>named</strong></span> so that it can see the
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <code class="filename">K*</code> files which contain the public and private
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein parts of the keys that will be used to sign the zone. These files
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein will have been generated by
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein <span class="command"><strong>dnssec-keygen</strong></span>. You can do this by placing them
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein in the key-directory, as specified in
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein type master;
60e5e10f8d2e2b0c41e8abad38cacd867caa6ab2Rob Austein update-policy local;
> update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
> update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
> update add example.net DNSKEY 256 3 7 AwEAAZn17pUF0KpbPA2c7Gz76Vb18v0teKT3EyAGfBfL8eQ8al35zz3Y I1m/SAQBxIqMfLtIwqWPdgthsu36azGQAX8=
> update add example.net DNSKEY 257 3 7 AwEAAd/7odU/64o2LGsifbLtQmtO8dFDtTAZXSX2+X3e/UNlq9IHq3Y0 XtC0Iuawl/qkaKVxXe2lo8Ct+dM6UehyCqk=
> update add example.net NSEC3PARAM 1 1 100 1234567890
(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
<a class="xref" href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a> for more information.)
<span class="command"><strong>rndc sign</strong></span> or <span class="command"><strong>rndc loadkeys</strong></span>
<span class="command"><strong>dnssec-keygen</strong></span> or <span class="command"><strong>dnssec-settime</strong></span>),
<p>In any secure zone which supports dynamic updates, <span class="command"><strong>named</strong></span>
<a class="xref" href="Bv9ARM.ch06.html#managed-keys" title="managed-keys Statement Definition and Usage">the section called “<span class="command"><strong>managed-keys</strong></span> Statement Definition
$ <strong class="userinput"><code>dnssec-keygen -K keys -f KSK -P now -A now+2y example.net</code></strong>
and the <span class="command"><strong>dnssec-*</strong></span> and <span class="command"><strong>pkcs11-*</strong></span>
<span class="command"><strong>dnssec-*</strong></span> tools, or the <code class="option">-m</code> in
$ <strong class="userinput"><code> configure --with-crypto-backend=openssl --prefix=/opt/pkcs11/usr --enable-gost </code></strong>
$ <strong class="userinput"><code> /opt/pkcs11/usr/bin/softhsm-util --init-token 0 --slot 0 --label softhsmv2 </code></strong>
$ <strong class="userinput"><code>wget <a class="link" href="" target="_top">http://www.openssl.org/source/openssl-0.9.8zc.tar.gz</a></code></strong>
$ <strong class="userinput"><code>cp pkcs11.GCC4.0.2.so.4.05 /opt/pkcs11/usr/lib/libpkcs11.so</code></strong>
and "<span class="command"><strong>make test</strong></span>". If "<span class="command"><strong>make
$ <strong class="userinput"><code> echo "0:/opt/pkcs11/softhsm.db" > $SOFTHSM_CONF </code></strong>
$ <strong class="userinput"><code> /opt/pkcs11/usr/bin/softhsm --init-token 0 --slot 0 --label softhsm </code></strong>
<span class="quote">“<span class="quote"><code class="literal">[ available ]</code></span>”</span>.
<a name="id-1.5.12.8.18"></a>Configuring BIND 9 for Linux with the AEP Keyper</h4></div></div></div>
<a name="id-1.5.12.8.19"></a>Configuring BIND 9 for Solaris with the SCA 6000</h4></div></div></div>
$ <strong class="userinput"><code>export LD_LIBRARY_PATH=/opt/pkcs11/usr/lib:${LD_LIBRARY_PATH}</code></strong>
$ <strong class="userinput"><code>export KEYPER_LIBRARY_PATH=/opt/Keyper/PKCS11Provider</code></strong>
"sample-ksk" as the key-signing key for "example.net":
$ <strong class="userinput"><code>dnssec-keyfromlabel -l sample-ksk -f KSK example.net</code></strong>
<a class="xref" href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel"><span class="refentrytitle"><span class="application">dnssec-keyfromlabel</span></span>(8)</a> for details.)
then <span class="command"><strong>named</strong></span> must have access to the HSM PIN. In OpenSSL-based PKCS#11,
this is accomplished by placing the PIN into the openssl.cnf file
The location of the openssl.cnf file can be overridden by
Historically, DLZ drivers had to be statically linked with the <span class="command"><strong>named</strong></span>
"dlopen" driver is linked into <span class="command"><strong>named</strong></span> by default, so configure options
When the DLZ module provides data to <span class="command"><strong>named</strong></span>, it does so in text format.
The response is converted to DNS wire format by <span class="command"><strong>named</strong></span>. This
dynamically-linkable DLZ module--i.e., one which can be
"example.nil", which can answer queries and AXFR requests, and
example.nil. 1800 IN A 10.53.0.1
e.g., by providing different address records for a particular name
(see <a class="xref" href="Bv9ARM.ch04.html#dlz-info" title="DLZ (Dynamically Loadable Zones)">the section called “DLZ (Dynamically Loadable Zones)”</a>), allows zone data to be
<a class="link" href="https://fedorahosted.org/bind-dyndb-ldap/" target="_top">https://fedorahosted.org/bind-dyndb-ldap/</a>.
dyndb example "driver.so" {
"example.nil", which can answer queries and AXFR requests, and
example.nil. 86400 IN A 127.0.0.1
whether the updated RR is an address (i.e., type A or AAAA) and if
see <a class="xref" href="Bv9ARM.ch11.html#ipv6addresses" title="IPv6 addresses (AAAA)">the section called “IPv6 addresses (AAAA)”</a>.
$ORIGIN example.com.