Bv9ARM.ch04.html revision 892503bd484c106493e3c8053155b364a522ec03
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - Copyright (C) 2004-2014 Internet Systems Consortium, Inc. ("ISC")
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - Copyright (C) 2000-2003 Internet Software Consortium.
52671ce4f644d565b2acd71a8ce4f6d20829a67cAdam Moore - Permission to use, copy, modify, and/or distribute this software for any
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - purpose with or without fee is hereby granted, provided that the above
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - copyright notice and this permission notice appear in all copies.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
02fc09f797e83e80199c96adc4751c230dccc973Adam Moore - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore - PERFORMANCE OF THIS SOFTWARE.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<!-- $Id$ -->
08e054017132cdd838955bc0af15889f1f2a7b42Adam Moore<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
b46f3d670b654847b0ce60afdba1b461c492a5c9Adam Moore<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
b46f3d670b654847b0ce60afdba1b461c492a5c9Adam Moore<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
08e054017132cdd838955bc0af15889f1f2a7b42Adam Moore<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
52671ce4f644d565b2acd71a8ce4f6d20829a67cAdam Moore<link rel="prev" href="Bv9ARM.ch03.html" title="Chapter�3.�Name Server Configuration">
0771d781138a507b3e657573703f511291640bf3Adam Moore<link rel="next" href="Bv9ARM.ch05.html" title="Chapter�5.�The BIND 9 Lightweight Resolver">
52671ce4f644d565b2acd71a8ce4f6d20829a67cAdam Moore<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
0771d781138a507b3e657573703f511291640bf3Adam Moore<tr><th colspan="3" align="center">Chapter�4.�Advanced DNS Features</th></tr>
0771d781138a507b3e657573703f511291640bf3Adam Moore<a accesskey="p" href="Bv9ARM.ch03.html">Prev</a>�</td>
9c42541e375e7bb70c53012b3012d70f1a380254Adam Moore<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch05.html">Next</a>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<div class="titlepage"><div><div><h2 class="title">
2690c090ce850e485d15cf691f59e8aaeb3b4bb1Adam Moore<a name="Bv9ARM.ch04"></a>Chapter�4.�Advanced DNS Features</h2></div></div></div>
abdfe7cf11d34f89f17b26e4779bf6079d22a910Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#notify">Notify</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2569819">Split DNS</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2569906">Example split DNS setup</a></span></dt></dl></dd>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570544">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
2690c090ce850e485d15cf691f59e8aaeb3b4bb1Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570617">Copying the Shared Secret to Both Machines</a></span></dt>
fb49666327c2cb6ea5a7d2dea5160b649bc07c51Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570628">Informing the Servers of the Key's Existence</a></span></dt>
2690c090ce850e485d15cf691f59e8aaeb3b4bb1Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570664">Instructing the Server to Use the Key</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570722">TSIG Key Based Access Control</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2570771">Errors</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2570785">TKEY</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2570834">SIG(0)</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571038">Generating Keys</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571117">Signing the Zone</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571267">Configuring Servers</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#dnssec.dynamic.zones">DNSSEC, Dynamic Zones, and Automatic Signing</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2610851">Converting from insecure to secure</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563443">Dynamic DNS update method</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563479">Fully automatic zone signing</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563719">Private-type records</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563825">DNSKEY rollovers</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563837">Dynamic DNS update method</a></span></dt>
abdfe7cf11d34f89f17b26e4779bf6079d22a910Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2563870">Automatic key rollovers</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2584718">NSEC3PARAM rollovers via UPDATE</a></span></dt>
abdfe7cf11d34f89f17b26e4779bf6079d22a910Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2584728">Converting from NSEC to NSEC3</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2584738">Converting from NSEC3 to NSEC</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2584750">Converting from secure to insecure</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2610866">Periodic re-signing</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2610875">NSEC3 and OPTOUT</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#rfc5011.support">Dynamic Trust Anchor Management</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2611386">Validating Resolver</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2584853">Authoritative Server</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#pkcs11">PKCS#11 (Cryptoki) support</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2665777">Prerequisites</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2665786">Native PKCS#11</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2610981">OpenSSL-based PKCS#11</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2638295">PKCS#11 Tools</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2638331">Using the HSM</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2638549">Specifying the engine on the command line</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2638733">Running named with automatic zone re-signing</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#dlz-info">DLZ (Dynamically Loadable Zones)</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2638866">Configuring DLZ</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2611291">Sample DLZ Driver</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2571627">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571757">Address Lookups Using AAAA Records</a></span></dt>
eab87f0881fdf3e80c2a1af9224c50f0bf033644Adam Moore<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571779">Address to Name Lookups Using Nibble Format</a></span></dt>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<div class="titlepage"><div><div><h2 class="title" style="clear: both">
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<a name="notify"></a>Notify</h2></div></div></div>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore <acronym class="acronym">DNS</acronym> NOTIFY is a mechanism that allows master
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore servers to notify their slave servers of changes to a zone's data. In
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore response to a <span><strong class="command">NOTIFY</strong></span> from a master server, the
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore slave will check to see that its version of the zone is the
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore current version and, if not, initiate a zone transfer.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore For more information about <acronym class="acronym">DNS</acronym>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore <span><strong class="command">NOTIFY</strong></span>, see the description of the
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore <span><strong class="command">notify</strong></span> option in <a href="Bv9ARM.ch06.html#boolean_options" title="Boolean Options">the section called “Boolean Options”</a> and
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore the description of the zone option <span><strong class="command">also-notify</strong></span> in
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. The <span><strong class="command">NOTIFY</strong></span>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore protocol is specified in RFC 1996.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore As a slave zone can also be a master to other slaves, <span><strong class="command">named</strong></span>,
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore by default, sends <span><strong class="command">NOTIFY</strong></span> messages for every zone
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore it loads. Specifying <span><strong class="command">notify master-only;</strong></span> will
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore cause <span><strong class="command">named</strong></span> to only send <span><strong class="command">NOTIFY</strong></span> for master
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore zones that it loads.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<div class="titlepage"><div><div><h2 class="title" style="clear: both">
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<a name="dynamic_update"></a>Dynamic Update</h2></div></div></div>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore Dynamic Update is a method for adding, replacing or deleting
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore records in a master server by sending it a special form of DNS
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore messages. The format and meaning of these messages is specified
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore in RFC 2136.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore Dynamic update is enabled by including an
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore <span><strong class="command">allow-update</strong></span> or an <span><strong class="command">update-policy</strong></span>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore clause in the <span><strong class="command">zone</strong></span> statement.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore If the zone's <span><strong class="command">update-policy</strong></span> is set to
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore <strong class="userinput"><code>local</code></strong>, updates to the zone
abdfe7cf11d34f89f17b26e4779bf6079d22a910Adam Moore will be permitted for the key <code class="varname">local-ddns</code>,
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore which will be generated by <span><strong class="command">named</strong></span> at startup.
abdfe7cf11d34f89f17b26e4779bf6079d22a910Adam Moore See <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a> for more details.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore Dynamic updates using Kerberos signed requests can be made
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore using the TKEY/GSS protocol by setting either the
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore <span><strong class="command">tkey-gssapi-keytab</strong></span> option, or alternatively
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore by setting both the <span><strong class="command">tkey-gssapi-credential</strong></span>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore and <span><strong class="command">tkey-domain</strong></span> options. Once enabled,
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore Kerberos signed requests will be matched against the update
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore policies for the zone, using the Kerberos principal as the
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore signer for the request.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore Updating of secure zones (zones using DNSSEC) follows RFC
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore 3007: RRSIG, NSEC and NSEC3 records affected by updates are
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore automatically regenerated by the server using an online
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore zone key. Update authorization is based on transaction
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore signatures and an explicit server policy.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<div class="titlepage"><div><div><h3 class="title">
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<a name="journal"></a>The journal file</h3></div></div></div>
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore All changes made to a zone using dynamic update are stored
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore in the zone's journal file. This file is automatically created
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore by the server when the first dynamic update takes place.
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore The name of the journal file is formed by appending the extension
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore <code class="filename">.jnl</code> to the name of the
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore corresponding zone
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore file unless specifically overridden. The journal file is in a
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore binary format and should not be edited manually.
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore The server will also occasionally write ("dump")
9c69eb57afb13ae0ffed8e442449f04922fe30adAdam Moore the complete contents of the updated zone to its zone file.
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore This is not done immediately after
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore each dynamic update, because that would be too slow when a large
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore zone is updated frequently. Instead, the dump is delayed by
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore up to 15 minutes, allowing additional updates to take place.
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore During the dump process, transient files will be created
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore with the extensions <code class="filename">.jnw</code> and
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore <code class="filename">.jbk</code>; under ordinary circumstances, these
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore will be removed when the dump is complete, and can be safely
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore When a server is restarted after a shutdown or crash, it will replay
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore the journal file to incorporate into the zone any updates that
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore place after the last zone dump.
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore Changes that result from incoming incremental zone transfers are
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore journalled in a similar way.
9c69eb57afb13ae0ffed8e442449f04922fe30adAdam Moore The zone files of dynamic zones cannot normally be edited by
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore hand because they are not guaranteed to contain the most recent
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore dynamic changes — those are only in the journal file.
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore The only way to ensure that the zone file of a dynamic zone
7aa876bc6c31de0d6ada455f2125dd549aaa0ee0Adam Moore is up to date is to run <span><strong class="command">rndc stop</strong></span>.
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore If you have to make changes to a dynamic zone
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore manually, the following procedure will work: Disable dynamic updates
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore to the zone using
8c73ff96cdb702124fb8ca87e9135cee38195253Adam Moore <span><strong class="command">rndc freeze <em class="replaceable"><code>zone</code></em></strong></span>.
7aa876bc6c31de0d6ada455f2125dd549aaa0ee0Adam Moore This will also remove the zone's <code class="filename">.jnl</code> file
7aa876bc6c31de0d6ada455f2125dd549aaa0ee0Adam Moore and update the master file. Edit the zone file. Run
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore <span><strong class="command">rndc thaw <em class="replaceable"><code>zone</code></em></strong></span>
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore to reload the changed zone and re-enable dynamic updates.
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore<div class="titlepage"><div><div><h2 class="title" style="clear: both">
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore<a name="incremental_zone_transfers"></a>Incremental Zone Transfers (IXFR)</h2></div></div></div>
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore The incremental zone transfer (IXFR) protocol is a way for
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore slave servers to transfer only changed data, instead of having to
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore transfer the entire zone. The IXFR protocol is specified in RFC
9c69eb57afb13ae0ffed8e442449f04922fe30adAdam Moore 1995. See <a href="Bv9ARM.ch09.html#proposed_standards">Proposed Standards</a>.
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore When acting as a master, <acronym class="acronym">BIND</acronym> 9
7aa876bc6c31de0d6ada455f2125dd549aaa0ee0Adam Moore supports IXFR for those zones
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore where the necessary change history information is available. These
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore include master zones maintained by dynamic update and slave zones
9bc9c1474a84983bd254adc2bc425c5b24d25526Adam Moore whose data was obtained by IXFR. For manually maintained master
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore zones, and for slave zones obtained by performing a full zone
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore transfer (AXFR), IXFR is supported only if the option
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore <span><strong class="command">ixfr-from-differences</strong></span> is set
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore to <strong class="userinput"><code>yes</code></strong>.
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore When acting as a slave, <acronym class="acronym">BIND</acronym> 9 will
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore attempt to use IXFR unless
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore it is explicitly disabled. For more information about disabling
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore IXFR, see the description of the <span><strong class="command">request-ixfr</strong></span> clause
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore of the <span><strong class="command">server</strong></span> statement.
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore<div class="titlepage"><div><div><h2 class="title" style="clear: both">
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore<a name="id2569819"></a>Split DNS</h2></div></div></div>
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore Setting up different views, or visibility, of the DNS space to
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore internal and external resolvers is usually referred to as a
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore <span class="emphasis"><em>Split DNS</em></span> setup. There are several
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore reasons an organization would want to set up its DNS this way.
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore One common reason for setting up a DNS system this way is
8aa0880cd494c951e0f4aa7d82d8bdac7692c7d0Adam Moore to hide "internal" DNS information from "external" clients on the
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore Internet. There is some debate as to whether or not this is actually
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore Internal DNS information leaks out in many ways (via email headers,
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore for example) and most savvy "attackers" can find the information
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore they need using other means.
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore However, since listing addresses of internal servers that
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore external clients cannot possibly reach can result in
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore connection delays and other annoyances, an organization may
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore choose to use a Split DNS to present a consistent view of itself
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore to the outside world.
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore Another common reason for setting up a Split DNS system is
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore to allow internal networks that are behind filters or in RFC 1918
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore space (reserved IP space, as documented in RFC 1918) to resolve DNS
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore on the Internet. Split DNS can also be used to allow mail from outside
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore back in to the internal network.
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore<div class="titlepage"><div><div><h3 class="title">
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore<a name="id2569906"></a>Example split DNS setup</h3></div></div></div>
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore Let's say a company named <span class="emphasis"><em>Example, Inc.</em></span>
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore has several corporate sites that have an internal network with
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore Internet Protocol (IP) space and an external demilitarized zone (DMZ),
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore or "outside" section of a network, that is available to the public.
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore <span class="emphasis"><em>Example, Inc.</em></span> wants its internal clients
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore to be able to resolve external hostnames and to exchange mail with
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore people on the outside. The company also wants its internal resolvers
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore to have access to certain internal-only zones that are not available
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore at all outside of the internal network.
52671ce4f644d565b2acd71a8ce4f6d20829a67cAdam Moore In order to accomplish this, the company will set up two sets
a52b18b7d9a83c1bf7e94949c160ec4b679ae713Adam Moore of name servers. One set will be on the inside network (in the
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore IP space) and the other set will be on bastion hosts, which are
ba9518d6366a8c1c3a1d027fdc652d92759e101bAdam Moore hosts that can talk to both sides of its network, in the DMZ.
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore The internal servers will be configured to forward all queries,
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore except queries for <code class="filename">site1.internal</code>, <code class="filename">site2.internal</code>, <code class="filename">site1.example.com</code>,
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore and <code class="filename">site2.example.com</code>, to the servers
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore DMZ. These internal servers will have complete sets of information
ed130182a3af03d1123fae83204a804c7a2ac0d3Adam Moore for <code class="filename">site1.example.com</code>, <code class="filename">site2.example.com</code>, <code class="filename">site1.internal</code>,
ed130182a3af03d1123fae83204a804c7a2ac0d3Adam Moore and <code class="filename">site2.internal</code>.
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore To protect the <code class="filename">site1.internal</code> and <code class="filename">site2.internal</code> domains,
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore the internal name servers must be configured to disallow all queries
2d71b4319c515f49ca328e3e00bb08d35ed5c161Adam Moore to these domains from any external hosts, including the bastion
bd6676c46a56d23b5e6f4702054bbd52e3d6f05fAdam Moore The external servers, which are on the bastion hosts, will
52671ce4f644d565b2acd71a8ce4f6d20829a67cAdam Moore be configured to serve the "public" version of the <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones.
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore This could include things such as the host records for public servers
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore (<code class="filename">www.example.com</code> and <code class="filename">ftp.example.com</code>),
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore and mail exchange (MX) records (<code class="filename">a.mx.example.com</code> and <code class="filename">b.mx.example.com</code>).
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore In addition, the public <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore should have special MX records that contain wildcard (`*') records
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore pointing to the bastion hosts. This is needed because external mail
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore servers do not have any other way of looking up how to deliver mail
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore to those internal hosts. With the wildcard records, the mail will
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore be delivered to the bastion host, which can then forward it on to
df5cf7dae3c20d8c50c036ea90987ec21f59614aAdam Moore internal hosts.
b3bd569e322a241dcb9aa531d7a7d9ed13766007Adam Moore Here's an example of a wildcard MX record:
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore<pre class="programlisting">* IN MX 10 external1.example.com.</pre>
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore Now that they accept mail on behalf of anything in the internal
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore network, the bastion hosts will need to know how to deliver mail
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore to internal hosts. In order for this to work properly, the resolvers
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore the bastion hosts will need to be configured to point to the internal
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore name servers for DNS resolution.
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore Queries for internal hostnames will be answered by the internal
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore servers, and queries for external hostnames will be forwarded back
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore out to the DNS servers on the bastion hosts.
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore In order for all this to work properly, internal clients will
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore need to be configured to query <span class="emphasis"><em>only</em></span> the internal
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore name servers for DNS queries. This could also be enforced via
3f3aa287185afb5d48d7ef0717054a154c372dc9Adam Moore filtering on the network.
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore If everything has been set properly, <span class="emphasis"><em>Example, Inc.</em></span>'s
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore internal clients will now be able to:
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore Look up any hostnames in the <code class="literal">site1</code>
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore <code class="literal">site2.example.com</code> zones.
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore Look up any hostnames in the <code class="literal">site1.internal</code> and
4ed6c4c5fd18811cfc57f26a1c593307d1867746Adam Moore <code class="literal">site2.internal</code> domains.
eaa291029af365353cfdc18d7cd1014a2f43bbe4Adam Moore<li>Exchange mail with both internal and external people.</li>
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore Hosts on the Internet will be able to:
b3bd569e322a241dcb9aa531d7a7d9ed13766007Adam Moore Look up any hostnames in the <code class="literal">site1</code>
b3bd569e322a241dcb9aa531d7a7d9ed13766007Adam Moore <code class="literal">site2.example.com</code> zones.
eaa291029af365353cfdc18d7cd1014a2f43bbe4Adam Moore Exchange mail with anyone in the <code class="literal">site1</code> and
b3bd569e322a241dcb9aa531d7a7d9ed13766007Adam Moore <code class="literal">site2.example.com</code> zones.
b3bd569e322a241dcb9aa531d7a7d9ed13766007Adam Moore Here is an example configuration for the setup we just
b3bd569e322a241dcb9aa531d7a7d9ed13766007Adam Moore described above. Note that this is only configuration information;
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore for information on how to configure your zone files, see <a href="Bv9ARM.ch03.html#sample_configuration" title="Sample Configurations">the section called “Sample Configurations”</a>.
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore Internal DNS server config:
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Mooreacl internals { 172.16.72.0/24; 192.168.1.0/24; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Mooreacl externals { <code class="varname">bastion-ips-go-here</code>; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore forward only;
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore // forward to external servers
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore forwarders {
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore <code class="varname">bastion-ips-go-here</code>;
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore // sample allow-transfer (no one)
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore allow-transfer { none; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore // restrict query access
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore allow-query { internals; externals; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore // restrict recursion
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore allow-recursion { internals; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore// sample master zone
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore type master;
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore // do normal iterative resolution (do not forward)
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore forwarders { };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore allow-query { internals; externals; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore allow-transfer { internals; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore// sample slave zone
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore masters { 172.16.72.3; };
fb49666327c2cb6ea5a7d2dea5160b649bc07c51Adam Moore forwarders { };
fb49666327c2cb6ea5a7d2dea5160b649bc07c51Adam Moore allow-query { internals; externals; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore allow-transfer { internals; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore type master;
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore forwarders { };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore allow-query { internals; };
5740f3112d19859eebaba7b3b8b95e6bc14beffbAdam Moore allow-transfer { internals; }
fb49666327c2cb6ea5a7d2dea5160b649bc07c51Adam Moore masters { 172.16.72.3; };
fb49666327c2cb6ea5a7d2dea5160b649bc07c51Adam Moore forwarders { };
fb49666327c2cb6ea5a7d2dea5160b649bc07c51Adam Moore allow-query { internals };
fb49666327c2cb6ea5a7d2dea5160b649bc07c51Adam Moore allow-transfer { internals; }
13060ea8e194930917f0243edd6ca469a91472e8Adam Moore External (bastion host) DNS server config:
eaa291029af365353cfdc18d7cd1014a2f43bbe4Adam Mooreacl internals { 172.16.72.0/24; 192.168.1.0/24; };
0f2f588af92633581627b768ccac61af079d87cfAdam Mooreacl externals { bastion-ips-go-here; };
0f2f588af92633581627b768ccac61af079d87cfAdam Moore // sample allow-transfer (no one)
0f2f588af92633581627b768ccac61af079d87cfAdam Moore allow-transfer { none; };
0f2f588af92633581627b768ccac61af079d87cfAdam Moore // default query access
eaa291029af365353cfdc18d7cd1014a2f43bbe4Adam Moore allow-query { any; };
bec687aba7976035d86626c750ea65c65ce13733Adam Moore // restrict cache access
0f2f588af92633581627b768ccac61af079d87cfAdam Moore allow-query-cache { internals; externals; };
0f2f588af92633581627b768ccac61af079d87cfAdam Moore // restrict recursion
0f2f588af92633581627b768ccac61af079d87cfAdam Moore allow-recursion { internals; externals; };
0f2f588af92633581627b768ccac61af079d87cfAdam Moore// sample slave zone
0f2f588af92633581627b768ccac61af079d87cfAdam Moore type master;
0f2f588af92633581627b768ccac61af079d87cfAdam Moore allow-transfer { internals; externals; };
bec687aba7976035d86626c750ea65c65ce13733Adam Moore masters { another_bastion_host_maybe; };
0f2f588af92633581627b768ccac61af079d87cfAdam Moore allow-transfer { internals; externals; }
bec687aba7976035d86626c750ea65c65ce13733Adam Moore In the <code class="filename">resolv.conf</code> (or equivalent) on
0f2f588af92633581627b768ccac61af079d87cfAdam Moore the bastion host(s):
0f2f588af92633581627b768ccac61af079d87cfAdam Moorenameserver 172.16.72.2
0f2f588af92633581627b768ccac61af079d87cfAdam Moorenameserver 172.16.72.3
bec687aba7976035d86626c750ea65c65ce13733Adam Moorenameserver 172.16.72.4
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore<div class="titlepage"><div><div><h2 class="title" style="clear: both">
52671ce4f644d565b2acd71a8ce4f6d20829a67cAdam Moore This is a short guide to setting up Transaction SIGnatures
0771d781138a507b3e657573703f511291640bf3Adam Moore (TSIG) based transaction security in <acronym class="acronym">BIND</acronym>. It describes changes
0771d781138a507b3e657573703f511291640bf3Adam Moore to the configuration file as well as what changes are required for
0771d781138a507b3e657573703f511291640bf3Adam Moore different features, including the process of creating transaction
0771d781138a507b3e657573703f511291640bf3Adam Moore keys and using transaction signatures with <acronym class="acronym">BIND</acronym>.
0771d781138a507b3e657573703f511291640bf3Adam Moore <acronym class="acronym">BIND</acronym> primarily supports TSIG for server
0771d781138a507b3e657573703f511291640bf3Adam Moore to server communication.
0771d781138a507b3e657573703f511291640bf3Adam Moore This includes zone transfer, notify, and recursive query messages.
52671ce4f644d565b2acd71a8ce4f6d20829a67cAdam Moore Resolvers based on newer versions of <acronym class="acronym">BIND</acronym> 8 have limited support
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore TSIG can also be useful for dynamic update. A primary
80d2034f65b9348e5fd36291f03b0819181efb89Adam Moore server for a dynamic zone should control access to the dynamic
A shared secret is generated to be shared between <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host2</em></span>.
<strong class="userinput"><code>dnssec-keygen -a hmac-sha256 -b 128 -n HOST host1-host2.</code></strong>
Imagine <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host 2</em></span>
both servers. The following is added to each server's <code class="filename">named.conf</code> file:
be told when keys are to be used. The following is added to the <code class="filename">named.conf</code> file
for <span class="emphasis"><em>host1</em></span>, if the IP address of <span class="emphasis"><em>host2</em></span> is
to that address, the message will be signed with the specified key. <span class="emphasis"><em>host1</em></span> will
configuration file (with <span class="emphasis"><em>host1</em></span>'s address) for <span class="emphasis"><em>host2</em></span> to
See <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a> for a discussion of
that the tools shipped with BIND 9.2.x and earlier are not compatible
<strong class="userinput"><code>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</code></strong>
<strong class="userinput"><code>yes</code></strong> or <strong class="userinput"><code>auto</code></strong>.
example.com. 257 3 5 "AwEAAaxPMcR2x0HbQV4WeZB6oEDX+r0QM6
<a name="dnssec.dynamic.zones"></a>DNSSEC, Dynamic Zones, and Automatic Signing</h2></div></div></div>
zone example.net {
> 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 href="man.dnssec-keygen.html" title="dnssec-keygen"><span class="refentrytitle"><span class="application">dnssec-keygen</span></span>(8)</a> and
<a href="man.dnssec-settime.html" title="dnssec-settime"><span class="refentrytitle"><span class="application">dnssec-settime</span></span>(8)</a> for more information.)
<span><strong class="command">rndc sign</strong></span> or <span><strong class="command">rndc loadkeys</strong></span>
<span><strong class="command">dnssec-keygen</strong></span> or <span><strong class="command">dnssec-settime</strong></span>),
and Usage">the section called “<span><strong class="command">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><strong class="command">dnssec-*</strong></span> and <span><strong class="command">pkcs11-*</strong></span>
<span><strong class="command">dnssec-*</strong></span> tools, or the <code class="option">-m</code> in
$ <strong class="userinput"><code>wget <a href="" target="_top">http://www.openssl.org/source/openssl-0.9.8y.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><strong class="command">make test</strong></span>". If "<span><strong class="command">make
project (http://www.opendnssec.org) which provides a PKCS#11
$ <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>
$ <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 href="man.dnssec-keyfromlabel.html" title="dnssec-keyfromlabel"><span class="refentrytitle"><span class="application">dnssec-keyfromlabel</span></span>(8)</a> for details.)
this is accomplished by placing the PIN into the openssl.cnf file
The location of the openssl.cnf file can be overridden by
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
<a name="id2571627"></a>IPv6 Support in <acronym class="acronym">BIND</acronym> 9</h2></div></div></div>
see <a href="Bv9ARM.ch09.html#ipv6addresses" title="IPv6 addresses (AAAA)">the section called “IPv6 addresses (AAAA)”</a>.
$ORIGIN example.com.