Bv9ARM.ch04.html revision e21a2904f02a03fa06b6db04d348f65fe9c67b2b
220a21d38f675eb835f5758e3d23e896573aa5eaLennart Poettering - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC")
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - Copyright (C) 2000-2003 Internet Software Consortium.
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - Permission to use, copy, modify, and distribute this software for any
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - purpose with or without fee is hereby granted, provided that the above
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - copyright notice and this permission notice appear in all copies.
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann - PERFORMANCE OF THIS SOFTWARE.
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<!-- $Id: Bv9ARM.ch04.html,v 1.72 2006/12/12 01:45:21 marka Exp $ -->
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<title>Chapter�4.�Advanced DNS Features</title>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<link rel="prev" href="Bv9ARM.ch03.html" title="Chapter�3.�Name Server Configuration">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<link rel="next" href="Bv9ARM.ch05.html" title="Chapter�5.�The BIND 9 Lightweight Resolver">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<table width="100%" summary="Navigation header">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<tr><th colspan="3" align="center">Chapter�4.�Advanced DNS Features</th></tr>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<a accesskey="p" href="Bv9ARM.ch03.html">Prev</a>�</td>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch05.html">Next</a>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<div class="titlepage"><div><div><h2 class="title">
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<a name="Bv9ARM.ch04"></a>Chapter�4.�Advanced DNS Features</h2></div></div></div>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect1"><a href="Bv9ARM.ch04.html#notify">Notify</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect1"><a href="Bv9ARM.ch04.html#dynamic_update">Dynamic Update</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch04.html#journal">The journal file</a></span></dt></dl></dd>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect1"><a href="Bv9ARM.ch04.html#incremental_zone_transfers">Incremental Zone Transfers (IXFR)</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2571238">Split DNS</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect1"><a href="Bv9ARM.ch04.html#tsig">TSIG</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571621">Generate Shared Keys for Each Pair of Hosts</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571694">Copying the Shared Secret to Both Machines</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571705">Informing the Servers of the Key's Existence</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571745">Instructing the Server to Use the Key</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571802">TSIG Key Based Access Control</a></span></dt>
e57eaef8a187762ca92838c24b9b6460878a800cDavid Herrmann<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2571847">Errors</a></span></dt>
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2571861">TKEY</a></span></dt>
5541c88977e63215e74b7517fb33cb27e5a04f17David Herrmann<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2572046">SIG(0)</a></span></dt>
861b02ebd6ec997a6880824960ba8903bac74f7dKay Sievers<dt><span class="sect1"><a href="Bv9ARM.ch04.html#DNSSEC">DNSSEC</a></span></dt>
861b02ebd6ec997a6880824960ba8903bac74f7dKay Sievers<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572251">Generating Keys</a></span></dt>
861b02ebd6ec997a6880824960ba8903bac74f7dKay Sievers<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572389">Signing the Zone</a></span></dt>
861b02ebd6ec997a6880824960ba8903bac74f7dKay Sievers<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572468">Configuring Servers</a></span></dt>
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann<dt><span class="sect1"><a href="Bv9ARM.ch04.html#id2572542">IPv6 Support in <acronym class="acronym">BIND</acronym> 9</a></span></dt>
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572809">Address Lookups Using AAAA Records</a></span></dt>
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann<dt><span class="sect2"><a href="Bv9ARM.ch04.html#id2572830">Address to Name Lookups Using Nibble Format</a></span></dt>
5541c88977e63215e74b7517fb33cb27e5a04f17David Herrmann<div class="titlepage"><div><div><h2 class="title" style="clear: both">
5541c88977e63215e74b7517fb33cb27e5a04f17David Herrmann<a name="notify"></a>Notify</h2></div></div></div>
9b361114f568e839784a3aeba5c1df5a95e86832Daniel Mack <acronym class="acronym">DNS</acronym> NOTIFY is a mechanism that allows master
9b361114f568e839784a3aeba5c1df5a95e86832Daniel Mack servers to notify their slave servers of changes to a zone's data. In
9b361114f568e839784a3aeba5c1df5a95e86832Daniel Mack response to a <span><strong class="command">NOTIFY</strong></span> from a master server, the
9b361114f568e839784a3aeba5c1df5a95e86832Daniel Mack slave will check to see that its version of the zone is the
9b361114f568e839784a3aeba5c1df5a95e86832Daniel Mack current version and, if not, initiate a zone transfer.
9b361114f568e839784a3aeba5c1df5a95e86832Daniel Mack For more information about <acronym class="acronym">DNS</acronym>
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann <span><strong class="command">NOTIFY</strong></span>, see the description of the
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann <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
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann the description of the zone option <span><strong class="command">also-notify</strong></span> in
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann <a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>. The <span><strong class="command">NOTIFY</strong></span>
5541c88977e63215e74b7517fb33cb27e5a04f17David Herrmann protocol is specified in RFC 1996.
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
2d1ca11270e66777c90a449096203afebc37ec9cDavid Herrmann As a slave zone can also be a master to other slaves, named,
2d1ca11270e66777c90a449096203afebc37ec9cDavid Herrmann by default, sends <span><strong class="command">NOTIFY</strong></span> messages for every zone
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann it loads. Specifying <span><strong class="command">notify master-only;</strong></span> will
2d1ca11270e66777c90a449096203afebc37ec9cDavid Herrmann cause named to only send <span><strong class="command">NOTIFY</strong></span> for master
0db83ad7334809a6605501e24bad55f3b652c072David Herrmann zones that it loads.
5f92d24fa85d6652c4754e3b3b2a3393026bd0b9Kay Sievers<div class="titlepage"><div><div><h2 class="title" style="clear: both">
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering<a name="dynamic_update"></a>Dynamic Update</h2></div></div></div>
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering Dynamic Update is a method for adding, replacing or deleting
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering records in a master server by sending it a special form of DNS
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering messages. The format and meaning of these messages is specified
5f92d24fa85d6652c4754e3b3b2a3393026bd0b9Kay Sievers Dynamic update is enabled by including an
0f0467e63b0e0688ae9edb1512c1a2637d62ddb4Martin Pitt <span><strong class="command">allow-update</strong></span> or <span><strong class="command">update-policy</strong></span>
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering clause in the <span><strong class="command">zone</strong></span> statement. The
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering <span><strong class="command">tkey-gssapi-credential</strong></span> and
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering <span><strong class="command">tkey-domain</strong></span> clauses in the
c65514649680e5d5ee6a118db6e5b20438cb1710Ronny Chevalier <span><strong class="command">options</strong></span> statement enable the
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering server to negotiate keys that can be matched against those
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering in <span><strong class="command">update-policy</strong></span> or
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering <span><strong class="command">allow-update</strong></span>.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering Updating of secure zones (zones using DNSSEC) follows
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering RFC 3007: RRSIG and NSEC records affected by updates are automatically
0f0467e63b0e0688ae9edb1512c1a2637d62ddb4Martin Pitt regenerated by the server using an online zone key.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering Update authorization is based
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering on transaction signatures and an explicit server policy.
0aee49d5fba2b2ec94e5c069d937004858a04b4fThomas Hindoe Paaboel Andersen<div class="titlepage"><div><div><h3 class="title">
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering<a name="journal"></a>The journal file</h3></div></div></div>
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering All changes made to a zone using dynamic update are stored
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering in the zone's journal file. This file is automatically created
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering by the server when the first dynamic update takes place.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering The name of the journal file is formed by appending the extension
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering <code class="filename">.jnl</code> to the name of the
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering corresponding zone
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering file unless specifically overridden. The journal file is in a
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering binary format and should not be edited manually.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering The server will also occasionally write ("dump")
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering the complete contents of the updated zone to its zone file.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering This is not done immediately after
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering each dynamic update, because that would be too slow when a large
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering zone is updated frequently. Instead, the dump is delayed by
0aee49d5fba2b2ec94e5c069d937004858a04b4fThomas Hindoe Paaboel Andersen up to 15 minutes, allowing additional updates to take place.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering When a server is restarted after a shutdown or crash, it will replay
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering the journal file to incorporate into the zone any updates that
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering place after the last zone dump.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering Changes that result from incoming incremental zone transfers are
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering journalled in a similar way.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering The zone files of dynamic zones cannot normally be edited by
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering hand because they are not guaranteed to contain the most recent
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering dynamic changes — those are only in the journal file.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering The only way to ensure that the zone file of a dynamic zone
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering is up to date is to run <span><strong class="command">rndc stop</strong></span>.
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering If you have to make changes to a dynamic zone
b912e251812bb65bed1d545d9748f5b0918f1559Lennart Poettering manually, the following procedure will work: Disable dynamic updates
b912e251812bb65bed1d545d9748f5b0918f1559Lennart Poettering to the zone using
b912e251812bb65bed1d545d9748f5b0918f1559Lennart Poettering <span><strong class="command">rndc freeze <em class="replaceable"><code>zone</code></em></strong></span>.
b912e251812bb65bed1d545d9748f5b0918f1559Lennart Poettering This will also remove the zone's <code class="filename">.jnl</code> file
b912e251812bb65bed1d545d9748f5b0918f1559Lennart Poettering and update the master file. Edit the zone file. Run
470e72d4081c7d0fd74666b7a45358d5ee2abee1Lennart Poettering <span><strong class="command">rndc thaw <em class="replaceable"><code>zone</code></em></strong></span>
b912e251812bb65bed1d545d9748f5b0918f1559Lennart Poettering to reload the changed zone and re-enable dynamic updates.
f7a73a2558bceffd983eb7642680e718cd981122David Herrmann<div class="titlepage"><div><div><h2 class="title" style="clear: both">
f7a73a2558bceffd983eb7642680e718cd981122David Herrmann<a name="incremental_zone_transfers"></a>Incremental Zone Transfers (IXFR)</h2></div></div></div>
f7a73a2558bceffd983eb7642680e718cd981122David Herrmann The incremental zone transfer (IXFR) protocol is a way for
f7a73a2558bceffd983eb7642680e718cd981122David Herrmann slave servers to transfer only changed data, instead of having to
f7a73a2558bceffd983eb7642680e718cd981122David Herrmann transfer the entire zone. The IXFR protocol is specified in RFC
f7a73a2558bceffd983eb7642680e718cd981122David Herrmann 1995. See <a href="Bv9ARM.ch09.html#proposed_standards">Proposed Standards</a>.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering When acting as a master, <acronym class="acronym">BIND</acronym> 9
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering supports IXFR for those zones
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering where the necessary change history information is available. These
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering include master zones maintained by dynamic update and slave zones
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering whose data was obtained by IXFR. For manually maintained master
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering zones, and for slave zones obtained by performing a full zone
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering transfer (AXFR), IXFR is supported only if the option
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering <span><strong class="command">ixfr-from-differences</strong></span> is set
29d1fcb4a3c921a3d4490353474e9775f7b13b0eZbigniew Jędrzejewski-Szmek to <strong class="userinput"><code>yes</code></strong>.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering When acting as a slave, <acronym class="acronym">BIND</acronym> 9 will
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering attempt to use IXFR unless
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering it is explicitly disabled. For more information about disabling
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering IXFR, see the description of the <span><strong class="command">request-ixfr</strong></span> clause
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering of the <span><strong class="command">server</strong></span> statement.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering<div class="titlepage"><div><div><h2 class="title" style="clear: both">
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering<a name="id2571238"></a>Split DNS</h2></div></div></div>
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Setting up different views, or visibility, of the DNS space to
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering internal and external resolvers is usually referred to as a
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering <span class="emphasis"><em>Split DNS</em></span> setup. There are several
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering reasons an organization would want to set up its DNS this way.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering One common reason for setting up a DNS system this way is
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering to hide "internal" DNS information from "external" clients on the
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Internet. There is some debate as to whether or not this is actually
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Internal DNS information leaks out in many ways (via email headers,
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering for example) and most savvy "attackers" can find the information
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering they need using other means.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering However, since listing addresses of internal servers that
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering external clients cannot possibly reach can result in
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering connection delays and other annoyances, an organization may
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering choose to use a Split DNS to present a consistant view of itself
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering to the outside world.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Another common reason for setting up a Split DNS system is
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering to allow internal networks that are behind filters or in RFC 1918
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering space (reserved IP space, as documented in RFC 1918) to resolve DNS
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering on the Internet. Split DNS can also be used to allow mail from outside
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering back in to the internal network.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Here is an example of a split DNS setup:
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Let's say a company named <span class="emphasis"><em>Example, Inc.</em></span>
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering (<code class="literal">example.com</code>)
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering has several corporate sites that have an internal network with
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering Internet Protocol (IP) space and an external demilitarized zone (DMZ),
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering or "outside" section of a network, that is available to the public.
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering <span class="emphasis"><em>Example, Inc.</em></span> wants its internal clients
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering to be able to resolve external hostnames and to exchange mail with
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering people on the outside. The company also wants its internal resolvers
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering to have access to certain internal-only zones that are not available
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering at all outside of the internal network.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering In order to accomplish this, the company will set up two sets
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering of name servers. One set will be on the inside network (in the
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering IP space) and the other set will be on bastion hosts, which are
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering hosts that can talk to both sides of its network, in the DMZ.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering The internal servers will be configured to forward all queries,
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering except queries for <code class="filename">site1.internal</code>, <code class="filename">site2.internal</code>, <code class="filename">site1.example.com</code>,
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering and <code class="filename">site2.example.com</code>, to the servers
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering DMZ. These internal servers will have complete sets of information
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering for <code class="filename">site1.example.com</code>, <code class="filename">site2.example.com</code>,<span class="emphasis"><em></em></span> <code class="filename">site1.internal</code>,
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering and <code class="filename">site2.internal</code>.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering To protect the <code class="filename">site1.internal</code> and <code class="filename">site2.internal</code> domains,
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering the internal name servers must be configured to disallow all queries
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering to these domains from any external hosts, including the bastion
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering The external servers, which are on the bastion hosts, will
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering be configured to serve the "public" version of the <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering This could include things such as the host records for public servers
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering (<code class="filename">www.example.com</code> and <code class="filename">ftp.example.com</code>),
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering and mail exchange (MX) records (<code class="filename">a.mx.example.com</code> and <code class="filename">b.mx.example.com</code>).
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering In addition, the public <code class="filename">site1</code> and <code class="filename">site2.example.com</code> zones
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering should have special MX records that contain wildcard (`*') records
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering pointing to the bastion hosts. This is needed because external mail
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering servers do not have any other way of looking up how to deliver mail
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering to those internal hosts. With the wildcard records, the mail will
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering be delivered to the bastion host, which can then forward it on to
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering internal hosts.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Here's an example of a wildcard MX record:
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering<pre class="programlisting">* IN MX 10 external1.example.com.</pre>
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Now that they accept mail on behalf of anything in the internal
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering network, the bastion hosts will need to know how to deliver mail
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering to internal hosts. In order for this to work properly, the resolvers
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering the bastion hosts will need to be configured to point to the internal
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering name servers for DNS resolution.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Queries for internal hostnames will be answered by the internal
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering servers, and queries for external hostnames will be forwarded back
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering out to the DNS servers on the bastion hosts.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering In order for all this to work properly, internal clients will
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering need to be configured to query <span class="emphasis"><em>only</em></span> the internal
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering name servers for DNS queries. This could also be enforced via
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering filtering on the network.
1579dd2c9b8f97e5ec4016d3928d73fea160e55aLennart Poettering If everything has been set properly, <span class="emphasis"><em>Example, Inc.</em></span>'s
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering internal clients will now be able to:
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering<div class="itemizedlist"><ul type="disc">
1a2d5fbe7efa04181a2d5518bc510b84b280baf9David Herrmann Look up any hostnames in the <code class="literal">site1</code>
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering <code class="literal">site2.example.com</code> zones.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Look up any hostnames in the <code class="literal">site1.internal</code> and
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering <code class="literal">site2.internal</code> domains.
1a2d5fbe7efa04181a2d5518bc510b84b280baf9David Herrmann<li>Look up any hostnames on the Internet.</li>
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering<li>Exchange mail with both internal and external people.</li>
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Hosts on the Internet will be able to:
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering<div class="itemizedlist"><ul type="disc">
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Look up any hostnames in the <code class="literal">site1</code>
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering <code class="literal">site2.example.com</code> zones.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Exchange mail with anyone in the <code class="literal">site1</code> and
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering <code class="literal">site2.example.com</code> zones.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Here is an example configuration for the setup we just
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering described above. Note that this is only configuration information;
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering 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>.
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering Internal DNS server config:
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poetteringacl internals { 172.16.72.0/24; 192.168.1.0/24; };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poetteringacl externals { <code class="varname">bastion-ips-go-here</code>; };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering forwarders { // forward to external servers
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering <code class="varname">bastion-ips-go-here</code>;
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-transfer { none; }; // sample allow-transfer (no one)
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-query { internals; externals; }; // restrict query access
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-recursion { internals; }; // restrict recursion
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poetteringzone "site1.example.com" { // sample master zone
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering forwarders { }; // do normal iterative
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering // resolution (do not forward)
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-query { internals; externals; };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-transfer { internals; };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poetteringzone "site2.example.com" { // sample slave zone
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering masters { 172.16.72.3; };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering forwarders { };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-query { internals; externals; };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-transfer { internals; };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering forwarders { };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-query { internals; };
481a0aa2c9803a62cda413b8a1d05571957bb4b5Lennart Poettering allow-transfer { internals; }
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering masters { 172.16.72.3; };
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering forwarders { };
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering allow-query { internals };
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering allow-transfer { internals; }
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering External (bastion host) DNS server config:
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poetteringacl internals { 172.16.72.0/24; 192.168.1.0/24; };
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poetteringacl externals { bastion-ips-go-here; };
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering allow-transfer { none; }; // sample allow-transfer (no one)
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering allow-query { any; }; // default query access
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering allow-query-cache { internals; externals; }; // restrict cache access
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering allow-recursion { internals; externals; }; // restrict recursion
7edecf218e5884ec8d1549707b4c7a0572c2d93bThomas Hindoe Paaboel Andersenzone "site1.example.com" { // sample slave zone
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering allow-transfer { internals; externals; };
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering masters { another_bastion_host_maybe; };
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering allow-transfer { internals; externals; }
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering In the <code class="filename">resolv.conf</code> (or equivalent) on
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering the bastion host(s):
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poetteringnameserver 172.16.72.2
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poetteringnameserver 172.16.72.3
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poetteringnameserver 172.16.72.4
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h2 class="title" style="clear: both">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="tsig"></a>TSIG</h2></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering This is a short guide to setting up Transaction SIGnatures
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering (TSIG) based transaction security in <acronym class="acronym">BIND</acronym>. It describes changes
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering to the configuration file as well as what changes are required for
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering different features, including the process of creating transaction
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering keys and using transaction signatures with <acronym class="acronym">BIND</acronym>.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <acronym class="acronym">BIND</acronym> primarily supports TSIG for server
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering to server communication.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering This includes zone transfer, notify, and recursive query messages.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering Resolvers based on newer versions of <acronym class="acronym">BIND</acronym> 8 have limited support
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering TSIG can also be useful for dynamic update. A primary
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering server for a dynamic zone should control access to the dynamic
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering update service, but IP-based access control is insufficient.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The cryptographic access control provided by TSIG
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering is far superior. The <span><strong class="command">nsupdate</strong></span>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering program supports TSIG via the <code class="option">-k</code> and
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <code class="option">-y</code> command line options or inline by use
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering of the <span><strong class="command">key</strong></span>.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571621"></a>Generate Shared Keys for Each Pair of Hosts</h3></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering A shared secret is generated to be shared between <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host2</em></span>.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering An arbitrary key name is chosen: "host1-host2.". The key name must
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering be the same on both hosts.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h4 class="title">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571638"></a>Automatic Generation</h4></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The following command will generate a 128-bit (16 byte) HMAC-MD5
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering key as described above. Longer keys are better, but shorter keys
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering are easier to read. Note that the maximum key length is 512 bits;
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering keys longer than that will be digested with MD5 to produce a
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <strong class="userinput"><code>dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.</code></strong>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The key is in the file <code class="filename">Khost1-host2.+157+00000.private</code>.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering Nothing directly uses this file, but the base-64 encoded string
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering following "<code class="literal">Key:</code>"
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering can be extracted from the file and used as a shared secret:
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<pre class="programlisting">Key: La/E5CjG9O+os1jq0a2jdA==</pre>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The string "<code class="literal">La/E5CjG9O+os1jq0a2jdA==</code>" can
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering be used as the shared secret.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h4 class="title">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571676"></a>Manual Generation</h4></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The shared secret is simply a random sequence of bits, encoded
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering in base-64. Most ASCII strings are valid base-64 strings (assuming
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering the length is a multiple of 4 and only valid characters are used),
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering so the shared secret can be manually generated.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering Also, a known string can be run through <span><strong class="command">mmencode</strong></span> or
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering a similar program to generate base-64 encoded data.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571694"></a>Copying the Shared Secret to Both Machines</h3></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering This is beyond the scope of DNS. A secure transport mechanism
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering should be used. This could be secure FTP, ssh, telephone, etc.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571705"></a>Informing the Servers of the Key's Existence</h3></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering Imagine <span class="emphasis"><em>host1</em></span> and <span class="emphasis"><em>host 2</em></span>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering both servers. The following is added to each server's <code class="filename">named.conf</code> file:
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poetteringkey host1-host2. {
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering algorithm hmac-md5;
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The algorithm, hmac-md5, is the only one supported by <acronym class="acronym">BIND</acronym>.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The secret is the one generated above. Since this is a secret, it
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering is recommended that either <code class="filename">named.conf</code> be non-world
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering readable, or the key directive be added to a non-world readable
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering file that is included by
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <code class="filename">named.conf</code>.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering At this point, the key is recognized. This means that if the
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering server receives a message signed by this key, it can verify the
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering signature. If the signature is successfully verified, the
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering response is signed by the same key.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571745"></a>Instructing the Server to Use the Key</h3></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering Since keys are shared between two hosts only, the server must
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering be told when keys are to be used. The following is added to the <code class="filename">named.conf</code> file
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering for <span class="emphasis"><em>host1</em></span>, if the IP address of <span class="emphasis"><em>host2</em></span> is
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poetteringserver 10.1.2.3 {
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering keys { host1-host2. ;};
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering Multiple keys may be present, but only the first is used.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering This directive does not contain any secrets, so it may be in a
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering world-readable
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering If <span class="emphasis"><em>host1</em></span> sends a message that is a request
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering to that address, the message will be signed with the specified key. <span class="emphasis"><em>host1</em></span> will
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering expect any responses to signed messages to be signed with the same
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering A similar statement must be present in <span class="emphasis"><em>host2</em></span>'s
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering configuration file (with <span class="emphasis"><em>host1</em></span>'s address) for <span class="emphasis"><em>host2</em></span> to
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering sign request messages to <span class="emphasis"><em>host1</em></span>.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571802"></a>TSIG Key Based Access Control</h3></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <acronym class="acronym">BIND</acronym> allows IP addresses and ranges
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering to be specified in ACL
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering definitions and
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <span><strong class="command">allow-{ query | transfer | update }</strong></span>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering This has been extended to allow TSIG keys also. The above key would
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering be denoted <span><strong class="command">key host1-host2.</strong></span>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering An example of an allow-update directive would be:
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poetteringallow-update { key host1-host2. ;};
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering This allows dynamic updates to succeed only if the request
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering was signed by a key named "<span><strong class="command">host1-host2.</strong></span>".
dd2fd155901a965ec0efa3adc460b33d2048d4c2Lennart Poettering You may want to read about the more powerful
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <span><strong class="command">update-policy</strong></span> statement in
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <a href="Bv9ARM.ch06.html#dynamic_update_policies" title="Dynamic Update Policies">the section called “Dynamic Update Policies”</a>.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571847"></a>Errors</h3></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The processing of TSIG signed messages can result in
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering several errors. If a signed message is sent to a non-TSIG aware
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering server, a FORMERR (format error) will be returned, since the server will not
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering understand the record. This is a result of misconfiguration,
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering since the server must be explicitly configured to send a TSIG
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering signed message to a specific server.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering If a TSIG aware server receives a message signed by an
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering unknown key, the response will be unsigned with the TSIG
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering extended error code set to BADKEY. If a TSIG aware server
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering receives a message with a signature that does not validate, the
7edecf218e5884ec8d1549707b4c7a0572c2d93bThomas Hindoe Paaboel Andersen response will be unsigned with the TSIG extended error code set
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering to BADSIG. If a TSIG aware server receives a message with a time
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering outside of the allowed range, the response will be signed with
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering the TSIG extended error code set to BADTIME, and the time values
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering will be adjusted so that the response can be successfully
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering verified. In any of these cases, the message's rcode is set to
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering NOTAUTH (not authenticated).
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h2 class="title" style="clear: both">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2571861"></a>TKEY</h2></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<p><span><strong class="command">TKEY</strong></span>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering is a mechanism for automatically generating a shared secret
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering between two hosts. There are several "modes" of
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <span><strong class="command">TKEY</strong></span> that specify how the key is generated
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering or assigned. <acronym class="acronym">BIND</acronym> 9 implements only one of
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering these modes, the Diffie-Hellman key exchange. Both hosts are
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering required to have a Diffie-Hellman KEY record (although this
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering record is not required to be present in a zone). The
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <span><strong class="command">TKEY</strong></span> process must use signed messages,
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering signed either by TSIG or SIG(0). The result of
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <span><strong class="command">TKEY</strong></span> is a shared secret that can be used to
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering sign messages with TSIG. <span><strong class="command">TKEY</strong></span> can also be
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering used to delete shared secrets that it had previously
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering The <span><strong class="command">TKEY</strong></span> process is initiated by a
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering or server by sending a signed <span><strong class="command">TKEY</strong></span>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering (including any appropriate KEYs) to a TKEY-aware server. The
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering server response, if it indicates success, will contain a
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <span><strong class="command">TKEY</strong></span> record and any appropriate keys.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering this exchange, both participants have enough information to
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering determine the shared secret; the exact process depends on the
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <span><strong class="command">TKEY</strong></span> mode. When using the
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering Diffie-Hellman
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <span><strong class="command">TKEY</strong></span> mode, Diffie-Hellman keys are
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering and the shared secret is derived by both participants.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<div class="titlepage"><div><div><h2 class="title" style="clear: both">
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering<a name="id2572046"></a>SIG(0)</h2></div></div></div>
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering <acronym class="acronym">BIND</acronym> 9 partially supports DNSSEC SIG(0)
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering transaction signatures as specified in RFC 2535 and RFC2931.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering uses public/private keys to authenticate messages. Access control
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering is performed in the same manner as TSIG keys; privileges can be
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering granted or denied based on the key name.
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering When a SIG(0) signed message is received, it will only be
615aaf412c441e67c7cad2e5ae966b03fca1fae7Lennart Poettering verified if the key is known and trusted by the server; the server
11ea2781eea4b912d2feb26785ece475e504c57bLennart Poettering will not attempt to locate and/or validate the key.
d2c643c662e2cb3b6d1445c17c80b4b2998d5c61Lennart Poettering SIG(0) signing of multiple-message TCP streams is not
d2c643c662e2cb3b6d1445c17c80b4b2998d5c61Lennart Poettering The only tool shipped with <acronym class="acronym">BIND</acronym> 9 that
d2c643c662e2cb3b6d1445c17c80b4b2998d5c61Lennart Poettering generates SIG(0) signed messages is <span><strong class="command">nsupdate</strong></span>.
d2c643c662e2cb3b6d1445c17c80b4b2998d5c61Lennart Poettering<div class="titlepage"><div><div><h2 class="title" style="clear: both">
d2c643c662e2cb3b6d1445c17c80b4b2998d5c61Lennart Poettering<a name="DNSSEC"></a>DNSSEC</h2></div></div></div>
11ea2781eea4b912d2feb26785ece475e504c57bLennart Poettering Cryptographic authentication of DNS information is possible
11ea2781eea4b912d2feb26785ece475e504c57bLennart Poettering through the DNS Security (<span class="emphasis"><em>DNSSEC-bis</em></span>) extensions,
11ea2781eea4b912d2feb26785ece475e504c57bLennart Poettering defined in RFC 4033, RFC 4034 and RFC 4035.
11ea2781eea4b912d2feb26785ece475e504c57bLennart Poettering This section describes the creation and use of DNSSEC signed zones.
11ea2781eea4b912d2feb26785ece475e504c57bLennart Poettering In order to set up a DNSSEC secure zone, there are a series
d2c643c662e2cb3b6d1445c17c80b4b2998d5c61Lennart Poettering of steps which must be followed. <acronym class="acronym">BIND</acronym>
11ea2781eea4b912d2feb26785ece475e504c57bLennart Poettering with several tools
d2c643c662e2cb3b6d1445c17c80b4b2998d5c61Lennart Poettering that are used in this process, which are explained in more detail
11ea2781eea4b912d2feb26785ece475e504c57bLennart Poettering below. In all cases, the <code class="option">-h</code> option prints a
d4f5a1f47dbd04f26f2ddf951c97c4cb0ebbbe62David Herrmann full list of parameters. Note that the DNSSEC tools require the
d4f5a1f47dbd04f26f2ddf951c97c4cb0ebbbe62David Herrmann keyset files to be in the working directory or the
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering directory specified by the <code class="option">-d</code> option, and
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering that the tools shipped with BIND 9.2.x and earlier are not compatible
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering with the current ones.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering There must also be communication with the administrators of
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering the parent and/or child zone to transmit keys. A zone's security
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering status must be indicated by the parent zone for a DNSSEC capable
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering resolver to trust its data. This is done through the presence
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering or absence of a <code class="literal">DS</code> record at the
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering For other servers to trust data in this zone, they must
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering either be statically configured with this zone's zone key or the
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering zone key of another zone above this one in the DNS tree.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering<a name="id2572251"></a>Generating Keys</h3></div></div></div>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering The <span><strong class="command">dnssec-keygen</strong></span> program is used to
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering generate keys.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering A secure zone must contain one or more zone keys. The
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering zone keys will sign all other records in the zone, as well as
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering the zone keys of any secure delegated zones. Zone keys must
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering have the same name as the zone, a name type of
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <span><strong class="command">ZONE</strong></span>, and must be usable for
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering authentication.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering It is recommended that zone keys use a cryptographic algorithm
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering designated as "mandatory to implement" by the IETF; currently
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering the only one is RSASHA1.
122676c9d9737f8591429fd5ffc9b454a994741dLennart Poettering The following command will generate a 768-bit RSASHA1 key for
122676c9d9737f8591429fd5ffc9b454a994741dLennart Poettering the <code class="filename">child.example</code> zone:
122676c9d9737f8591429fd5ffc9b454a994741dLennart Poettering <strong class="userinput"><code>dnssec-keygen -a RSASHA1 -b 768 -n ZONE child.example.</code></strong>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering Two output files will be produced:
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <code class="filename">Kchild.example.+005+12345.key</code> and
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <code class="filename">Kchild.example.+005+12345.private</code>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering 12345 is an example of a key tag). The key file names contain
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering the key name (<code class="filename">child.example.</code>),
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering is DSA, 1 is RSAMD5, 5 is RSASHA1, etc.), and the key tag (12345 in
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering The private key (in the <code class="filename">.private</code>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering used to generate signatures, and the public key (in the
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <code class="filename">.key</code> file) is used for signature
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering To generate another key with the same properties (but with
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering a different key tag), repeat the above command.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering The public keys should be inserted into the zone file by
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering including the <code class="filename">.key</code> files using
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <span><strong class="command">$INCLUDE</strong></span> statements.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering<a name="id2572389"></a>Signing the Zone</h3></div></div></div>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering The <span><strong class="command">dnssec-signzone</strong></span> program is used
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering Any <code class="filename">keyset</code> files corresponding
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering to secure subzones should be present. The zone signer will
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering generate <code class="literal">NSEC</code> and <code class="literal">RRSIG</code>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering records for the zone, as well as <code class="literal">DS</code>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering the child zones if <code class="literal">'-d'</code> is specified.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering If <code class="literal">'-d'</code> is not specified, then
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering the secure child zones need to be added manually.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering The following command signs the zone, assuming it is in a
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering file called <code class="filename">zone.child.example</code>. By
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering default, all zone keys which have an available private key are
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering used to generate signatures.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <strong class="userinput"><code>dnssec-signzone -o child.example zone.child.example</code></strong>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering One output file is produced:
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <code class="filename">zone.child.example.signed</code>. This
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering should be referenced by <code class="filename">named.conf</code>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering input file for the zone.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering<p><span><strong class="command">dnssec-signzone</strong></span>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering will also produce a keyset and dsset files and optionally a
d4f5a1f47dbd04f26f2ddf951c97c4cb0ebbbe62David Herrmann dlvset file. These are used to provide the parent zone
d4f5a1f47dbd04f26f2ddf951c97c4cb0ebbbe62David Herrmann administators with the <code class="literal">DNSKEYs</code> (or their
d4f5a1f47dbd04f26f2ddf951c97c4cb0ebbbe62David Herrmann corresponding <code class="literal">DS</code> records) that are the
d4f5a1f47dbd04f26f2ddf951c97c4cb0ebbbe62David Herrmann secure entry point to the zone.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering<div class="titlepage"><div><div><h3 class="title">
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering<a name="id2572468"></a>Configuring Servers</h3></div></div></div>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering To enable <span><strong class="command">named</strong></span> to respond appropriately
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering to DNS requests from DNSSEC aware clients,
17c29493dc5c4c3ca886adfdc632d297c5eb06ebRonny Chevalier <span><strong class="command">dnssec-enable</strong></span> must be set to yes.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering To enable <span><strong class="command">named</strong></span> to validate answers from
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering other servers both <span><strong class="command">dnssec-enable</strong></span> and
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <span><strong class="command">dnssec-validate</strong></span> must be set and some
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <span><strong class="command">trusted-keys</strong></span> must be configured
997b2b438c2d272e3bc8df6e4b42dba3b70cb056Josh Triplett into <code class="filename">named.conf</code>.
997b2b438c2d272e3bc8df6e4b42dba3b70cb056Josh Triplett <span><strong class="command">trusted-keys</strong></span> are copies of DNSKEY RRs
997b2b438c2d272e3bc8df6e4b42dba3b70cb056Josh Triplett for zones that are used to form the first link in the
997b2b438c2d272e3bc8df6e4b42dba3b70cb056Josh Triplett cryptographic chain of trust. All keys listed in
997b2b438c2d272e3bc8df6e4b42dba3b70cb056Josh Triplett <span><strong class="command">trusted-keys</strong></span> (and corresponding zones)
997b2b438c2d272e3bc8df6e4b42dba3b70cb056Josh Triplett are deemed to exist and only the listed keys will be used
997b2b438c2d272e3bc8df6e4b42dba3b70cb056Josh Triplett to validated the DNSKEY RRset that they are from.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering <span><strong class="command">trusted-keys</strong></span> are described in more detail
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering later in this document.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering Unlike <acronym class="acronym">BIND</acronym> 8, <acronym class="acronym">BIND</acronym>
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering 9 does not verify signatures on load, so zone keys for
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering authoritative zones do not need to be specified in the
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering configuration file.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering After DNSSEC gets established, a typical DNSSEC configuration
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering will look something like the following. It has a one or
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering more public keys for the root. This allows answers from
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering outside the organization to be validated. It will also
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering have several keys for parts of the namespace the organization
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering controls. These are here to ensure that named is immune
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering to compromises in the DNSSEC components of the security
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering of parent zones.
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering /* Root Key */
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering"." 257 3 3 "BNY4wrWM1nCfJ+CXd0rVXyYmobt7sEEfK3clRbGaTwSJxrGkxJWoZu6I7PzJu/
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering E9gx4UC1zGAHlXKdE4zYIpRhaBKnvcC2U9mZhkdUpd1Vso/HAdjNe8LmMlnzY3
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering zy2Xy4klWOADTPzSv9eamj8V18PHGjBLaVtYvk/ln5ZApjYghf+6fElrmLkdaz
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering MQ2OCnACR817DF4BBa7UR/beDHyp5iWTXWSi6XmoJLbG9Scqc7l70KDqlvXR3M
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering /lUUVRbkeg1IPJSidmK3ZyCllh4XSKbje/45SKucHgnwU5jefMtq66gKodQj+M
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering iA21AfUVe7u99WzTLzY3qlxDhxYQQ20FQ97S+LKUTpQcq27R7AT3/V5hRQxScI
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering Nqwcz4jYqZD2fQdgxbcDTClU0CRBdiieyLMNzXG3";
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering/* Key for our organization's forward zone */
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poetteringexample.com. 257 3 5 "AwEAAaxPMcR2x0HbQV4WeZB6oEDX+r0QM65KbhTjrW1ZaARmPhEZZe
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering 3Y9ifgEuq7vZ/zGZUdEGNWy+JZzus0lUptwgjGwhUS1558Hb4JKUbb
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering OTcM8pwXlj0EiX3oDFVmjHO444gLkBO UKUf/mC7HvfwYH/Be22GnC
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering lrinKJp1Og4ywzO9WglMk7jbfW33gUKvirTHr25GL7STQUzBb5Usxt
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering 8lgnyTUHs1t3JwCY5hKZ6CqFxmAVZP20igTixin/1LcrgX/KMEGd/b
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering iuvF4qJCyduieHukuY3H4XMAcR+xia2 nIUPvm/oyWR8BW/hWdzOvn
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering/* Key for our reverse zone. */
f9e00a9f5870a9bcae2de8bf1cb3ce04703112e1Lennart Poettering2.0.192.IN-ADDRPA.NET. 257 3 5 "AQOnS4xn/IgOUpBPJ3bogzwcxOdNax071L18QqZnQQQA
13e92f3966552091085982f4ebdeb38721f04a30Lennart Poettering VVr+iLhGTnNGp3HoWQLUIzKrJVZ3zggy3WwNT6kZo6c0
13e92f3966552091085982f4ebdeb38721f04a30Lennart Poettering tszYqbtvchmgQC8CzKojM/W16i6MG/ea fGU3siaOdS0
13e92f3966552091085982f4ebdeb38721f04a30Lennart Poettering yOI6BgPsw+YZdzlYMaIJGf4M4dyoKIhzdZyQ2bYQrjyQ
13e92f3966552091085982f4ebdeb38721f04a30Lennart Poettering 4LB0lC7aOnsMyYKHHYeRv PxjIQXmdqgOJGq+vsevG06
13e92f3966552091085982f4ebdeb38721f04a30Lennart Poettering zW+1xgYJh9rCIfnm1GX/KMgxLPG2vXTD/RnLX+D3T3UL
13e92f3966552091085982f4ebdeb38721f04a30Lennart Poettering 7HJYHJhAZD5L59VvjSPsZJHeDCUyWYrvPZesZDIRvhDD
7da81d33c147f4d6397efa1fdd08ba0a40c9c457Lennart Poettering dnssec-enable yes;
7da81d33c147f4d6397efa1fdd08ba0a40c9c457Lennart Poettering dnssec-validation yes;
7da81d33c147f4d6397efa1fdd08ba0a40c9c457Lennart Poettering<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
7da81d33c147f4d6397efa1fdd08ba0a40c9c457Lennart Poettering None of the keys listed in this example are valid. In particular,
13e92f3966552091085982f4ebdeb38721f04a30Lennart Poettering the root key is not valid.
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering<div class="titlepage"><div><div><h2 class="title" style="clear: both">
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering<a name="id2572542"></a>IPv6 Support in <acronym class="acronym">BIND</acronym> 9</h2></div></div></div>
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering <acronym class="acronym">BIND</acronym> 9 fully supports all currently
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek defined forms of IPv6
a65b82457735df2ef58736a55846f400124a8dc0Zbigniew Jędrzejewski-Szmek name to address and address to name lookups. It will also use
a65b82457735df2ef58736a55846f400124a8dc0Zbigniew Jędrzejewski-Szmek IPv6 addresses to make queries when running on an IPv6 capable
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek For forward lookups, <acronym class="acronym">BIND</acronym> 9 supports
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek only AAAA records. RFC 3363 deprecated the use of A6 records,
4bdc60cb6fab336d455abbbd269e5bfccf760c91Lennart Poettering and client-side support for A6 records was accordingly removed
4bdc60cb6fab336d455abbbd269e5bfccf760c91Lennart Poettering from <acronym class="acronym">BIND</acronym> 9.
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering However, authoritative <acronym class="acronym">BIND</acronym> 9 name servers still
4bdc60cb6fab336d455abbbd269e5bfccf760c91Lennart Poettering load zone files containing A6 records correctly, answer queries
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek for A6 records, and accept zone transfer for a zone containing A6
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek For IPv6 reverse lookups, <acronym class="acronym">BIND</acronym> 9 supports
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek the traditional "nibble" format used in the
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek <span class="emphasis"><em>ip6.arpa</em></span> domain, as well as the older, deprecated
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek <span class="emphasis"><em>ip6.int</em></span> domain.
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek Older versions of <acronym class="acronym">BIND</acronym> 9
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering supported the "binary label" (also known as "bitstring") format,
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering but support of binary labels has been completely removed per
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering Many applications in <acronym class="acronym">BIND</acronym> 9 do not understand
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering the binary label format at all any more, and will return an
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering error if given.
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering In particular, an authoritative <acronym class="acronym">BIND</acronym> 9
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering name server will not load a zone file containing binary labels.
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering For an overview of the format and structure of IPv6 addresses,
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering see <a href="Bv9ARM.ch09.html#ipv6addresses" title="IPv6 addresses (AAAA)">the section called “IPv6 addresses (AAAA)”</a>.
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering<div class="titlepage"><div><div><h3 class="title">
4ffd29fda1a2621d8f1711ccaad723d327fef93aLennart Poettering<a name="id2572809"></a>Address Lookups Using AAAA Records</h3></div></div></div>
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek The IPv6 AAAA record is a parallel to the IPv4 A record,
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek and, unlike the deprecated A6 record, specifies the entire
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek IPv6 address in a single record. For example,
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmekhost 3600 IN AAAA 2001:db8::1
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering Use of IPv4-in-IPv6 mapped addresses is not recommended.
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering If a host has an IPv4 address, use an A record, not
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering a AAAA, with <code class="literal">::ffff:192.168.42.1</code> as
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek<div class="titlepage"><div><div><h3 class="title">
ba8df74bb643c0f7c343fef78bba3661b0f9c31cKay Sievers<a name="id2572830"></a>Address to Name Lookups Using Nibble Format</h3></div></div></div>
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek When looking up an address in nibble format, the address
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek components are simply reversed, just as in IPv4, and
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek <code class="literal">ip6.arpa.</code> is appended to the
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek For example, the following would provide reverse name lookup for
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek a host with address
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek <code class="literal">2001:db8::1</code>.
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering$ORIGIN 0.0.0.0.0.0.0.0.8.b.d.0.1.0.0.2.ip6.arpa.
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 14400 IN PTR host.example.com.
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek<table width="100%" summary="Navigation footer">
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek<a accesskey="p" href="Bv9ARM.ch03.html">Prev</a>�</td>
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek<td width="20%" align="center">�</td>
b62a309a47dd11e11729616767421397b6ca7053Zbigniew Jędrzejewski-Szmek<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch05.html">Next</a>
ba8df74bb643c0f7c343fef78bba3661b0f9c31cKay Sievers<td width="40%" align="left" valign="top">Chapter�3.�Name Server Configuration�</td>
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
78b6b7ceb2c76a3e29aeaa4b00c257be0706bffcLennart Poettering<td width="40%" align="right" valign="top">�Chapter�5.�The <acronym class="acronym">BIND</acronym> 9 Lightweight Resolver</td>