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