Bv9ARM.ch07.html 19.5 KB
Newer Older
1
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
Rob Austein's avatar
regen  
Rob Austein committed
2
<!--
Tinderbox User's avatar
Tinderbox User committed
3
 - Copyright (C) 2000-2017 Internet Systems Consortium, Inc. ("ISC")
Rob Austein's avatar
regen  
Rob Austein committed
4
 - 
Tinderbox User's avatar
Tinderbox User committed
5 6 7
 - This Source Code Form is subject to the terms of the Mozilla Public
 - License, v. 2.0. If a copy of the MPL was not distributed with this
 - file, You can obtain one at http://mozilla.org/MPL/2.0/.
Rob Austein's avatar
regen  
Rob Austein committed
8
-->
9
<html lang="en">
Rob Austein's avatar
regen  
Rob Austein committed
10 11 12
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>Chapter 7. BIND 9 Security Considerations</title>
Tinderbox User's avatar
Tinderbox User committed
13
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
Evan Hunt's avatar
Evan Hunt committed
14
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
Rob Austein's avatar
regen  
Rob Austein committed
15 16 17 18 19 20 21
<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="prev" href="Bv9ARM.ch06.html" title="Chapter 6. BIND 9 Configuration Reference">
<link rel="next" href="Bv9ARM.ch08.html" title="Chapter 8. Troubleshooting">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
Mark Andrews's avatar
regen  
Mark Andrews committed
22
<tr><th colspan="3" align="center">Chapter 7. <acronym class="acronym">BIND</acronym> 9 Security Considerations</th></tr>
Rob Austein's avatar
regen  
Rob Austein committed
23 24 25 26 27 28 29 30 31 32
<tr>
<td width="20%" align="left">
<a accesskey="p" href="Bv9ARM.ch06.html">Prev</a> </td>
<th width="60%" align="center"> </th>
<td width="20%" align="right"> <a accesskey="n" href="Bv9ARM.ch08.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
Tinderbox User's avatar
Tinderbox User committed
33 34 35
<div class="chapter">
<div class="titlepage"><div><div><h1 class="title">
<a name="Bv9ARM.ch07"></a>Chapter 7. <acronym class="acronym">BIND</acronym> 9 Security Considerations</h1></div></div></div>
Rob Austein's avatar
regen  
Rob Austein committed
36 37
<div class="toc">
<p><b>Table of Contents</b></p>
Tinderbox User's avatar
Tinderbox User committed
38
<dl class="toc">
Evan Hunt's avatar
Evan Hunt committed
39
<dt><span class="section"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
Tinderbox User's avatar
Tinderbox User committed
40
<dt><span class="section"><a href="Bv9ARM.ch07.html#chroot_and_setuid"><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span></a></span></dt>
Rob Austein's avatar
regen  
Rob Austein committed
41
<dd><dl>
Tinderbox User's avatar
Tinderbox User committed
42 43
<dt><span class="section"><a href="Bv9ARM.ch07.html#chroot">The <span class="command"><strong>chroot</strong></span> Environment</a></span></dt>
<dt><span class="section"><a href="Bv9ARM.ch07.html#setuid">Using the <span class="command"><strong>setuid</strong></span> Function</a></span></dt>
Rob Austein's avatar
regen  
Rob Austein committed
44
</dl></dd>
Evan Hunt's avatar
Evan Hunt committed
45
<dt><span class="section"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
Rob Austein's avatar
regen  
Rob Austein committed
46 47
</dl>
</div>
Tinderbox User's avatar
Tinderbox User committed
48 49

      <div class="section">
Rob Austein's avatar
regen  
Rob Austein committed
50 51
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="Access_Control_Lists"></a>Access Control Lists</h2></div></div></div>
Tinderbox User's avatar
Tinderbox User committed
52 53

        <p>
Automatic Updater's avatar
regen  
Automatic Updater committed
54
          Access Control Lists (ACLs) are address match lists that
Tinderbox User's avatar
Tinderbox User committed
55
          you can set up and nickname for future use in
Evan Hunt's avatar
Evan Hunt committed
56 57 58 59
          <span class="command"><strong>allow-notify</strong></span>, <span class="command"><strong>allow-query</strong></span>,
          <span class="command"><strong>allow-query-on</strong></span>, <span class="command"><strong>allow-recursion</strong></span>,
          <span class="command"><strong>blackhole</strong></span>, <span class="command"><strong>allow-transfer</strong></span>,
          <span class="command"><strong>match-clients</strong></span>, etc.
Rob Austein's avatar
regen  
Rob Austein committed
60
        </p>
Tinderbox User's avatar
Tinderbox User committed
61
        <p>
Rob Austein's avatar
regen  
Rob Austein committed
62 63 64 65
          Using ACLs allows you to have finer control over who can access
          your name server, without cluttering up your config files with huge
          lists of IP addresses.
        </p>
Tinderbox User's avatar
Tinderbox User committed
66
        <p>
Rob Austein's avatar
regen  
Rob Austein committed
67 68
          It is a <span class="emphasis"><em>good idea</em></span> to use ACLs, and to
          control access to your server. Limiting access to your server by
Tinderbox User's avatar
Tinderbox User committed
69 70
          outside parties can help prevent spoofing and denial of service
          (DoS) attacks against your server.
Rob Austein's avatar
regen  
Rob Austein committed
71
        </p>
Tinderbox User's avatar
Tinderbox User committed
72
        <p>
Tinderbox User's avatar
Tinderbox User committed
73 74 75 76 77
          ACLs match clients on the basis of up to three characteristics:
          1) The client's IP address; 2) the TSIG or SIG(0) key that was
          used to sign the request, if any; and 3) an address prefix
          encoded in an EDNS Client Subnet option, if any.
        </p>
Tinderbox User's avatar
Tinderbox User committed
78
        <p>
Tinderbox User's avatar
Tinderbox User committed
79
          Here is an example of ACLs based on client addresses:
Rob Austein's avatar
regen  
Rob Austein committed
80
        </p>
Tinderbox User's avatar
Tinderbox User committed
81

Rob Austein's avatar
regen  
Rob Austein committed
82
<pre class="programlisting">
Automatic Updater's avatar
regen  
Automatic Updater committed
83 84 85
// Set up an ACL named "bogusnets" that will block
// RFC1918 space and some reserved space, which is
// commonly used in spoofing attacks.
Mark Andrews's avatar
gregen  
Mark Andrews committed
86
acl bogusnets {
Automatic Updater's avatar
Automatic Updater committed
87 88
        0.0.0.0/8;  192.0.2.0/24; 224.0.0.0/3;
        10.0.0.0/8; 172.16.0.0/12; 192.168.0.0/16;
Mark Andrews's avatar
gregen  
Mark Andrews committed
89
};
Mark Andrews's avatar
regen  
Mark Andrews committed
90

Automatic Updater's avatar
regen  
Automatic Updater committed
91 92
// Set up an ACL called our-nets. Replace this with the
// real IP numbers.
Mark Andrews's avatar
gregen  
Mark Andrews committed
93
acl our-nets { x.x.x.x/24; x.x.x.x/21; };
94 95 96 97 98 99 100 101 102
options {
  ...
  ...
  allow-query { our-nets; };
  allow-recursion { our-nets; };
  ...
  blackhole { bogusnets; };
  ...
};
Mark Andrews's avatar
regen  
Mark Andrews committed
103

104 105 106 107 108
zone "example.com" {
  type master;
  file "m/example.com";
  allow-query { any; };
};
Rob Austein's avatar
regen  
Rob Austein committed
109
</pre>
Tinderbox User's avatar
Tinderbox User committed
110 111

        <p>
Tinderbox User's avatar
Tinderbox User committed
112 113 114 115 116
          This allows authoritative queries for "example.com" from any
          address, but recursive queries only from the networks specified
          in "our-nets", and no queries at all from the networks
          specified in "bogusnets".
        </p>
Tinderbox User's avatar
Tinderbox User committed
117
        <p>
Tinderbox User's avatar
Tinderbox User committed
118 119 120 121 122 123 124 125
          In addition to network addresses and prefixes, which are
          matched against the source address of the DNS request, ACLs
          may include <code class="option">key</code> elements, which specify the
          name of a TSIG or SIG(0) key, or <code class="option">ecs</code>
          elements, which specify a network prefix but are only matched
          if that prefix matches an EDNS client subnet option included
          in the request.
        </p>
Tinderbox User's avatar
Tinderbox User committed
126
        <p>
Tinderbox User's avatar
Tinderbox User committed
127 128 129 130 131 132
          The EDNS Client Subnet (ECS) option is used by a recursive
          resolver to inform an authoritative name server of the network
          address block from which the original query was received, enabling
          authoritative servers to give different answers to the same
          resolver for different resolver clients.  An ACL containing
          an element of the form
Evan Hunt's avatar
Evan Hunt committed
133
          <span class="command"><strong>ecs <em class="replaceable"><code>prefix</code></em></strong></span>
Tinderbox User's avatar
Tinderbox User committed
134 135 136 137 138 139
          will match if a request arrives in containing an ECS option
          encoding an address within that prefix.  If the request has no
          ECS option, then "ecs" elements are simply ignored.  Addresses
          in ACLs that are not prefixed with "ecs" are matched only
          against the source address.
        </p>
Tinderbox User's avatar
Tinderbox User committed
140 141 142 143 144 145 146 147 148 149 150 151 152
        <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
<h3 class="title">Note</h3>
          <p>
            (Note: The authoritative ECS implementation in
            <span class="command"><strong>named</strong></span> is based on an early version of the
            specification, and is known to have incompatibilities with
            other implementations.  It is also inefficient, requiring
            a separate view for each client subnet to be sent different
            answers, and it is unable to correct for overlapping subnets in
            the configuration.  It can be used for testing purposes, but is
            not recommended for production use.)
          </p>
        </div>
Tinderbox User's avatar
Tinderbox User committed
153
        <p>
Tinderbox User's avatar
Tinderbox User committed
154 155 156
          When <acronym class="acronym">BIND</acronym> 9 is built with GeoIP support,
          ACLs can also be used for geographic access restrictions.
          This is done by specifying an ACL element of the form:
Evan Hunt's avatar
Evan Hunt committed
157
          <span class="command"><strong>geoip [<span class="optional">db <em class="replaceable"><code>database</code></em></span>] <em class="replaceable"><code>field</code></em> <em class="replaceable"><code>value</code></em></strong></span>
Tinderbox User's avatar
Tinderbox User committed
158
        </p>
Tinderbox User's avatar
Tinderbox User committed
159
        <p>
Tinderbox User's avatar
Tinderbox User committed
160 161 162 163 164 165
          The <em class="replaceable"><code>field</code></em> indicates which field
          to search for a match.  Available fields are "country",
          "region", "city", "continent", "postal" (postal code),
          "metro" (metro code), "area" (area code), "tz" (timezone),
          "isp", "org", "asnum", "domain" and "netspeed".
        </p>
Tinderbox User's avatar
Tinderbox User committed
166
        <p>
Tinderbox User's avatar
Tinderbox User committed
167 168 169 170 171 172 173 174 175 176 177 178 179 180 181
          <em class="replaceable"><code>value</code></em> is the value to search
          for within the database.  A string may be quoted if it
          contains spaces or other special characters.  If this is
          an "asnum" search, then the leading "ASNNNN" string can be
          used, otherwise the full description must be used (e.g.
          "ASNNNN Example Company Name").  If this is a "country"
          search and the string is two characters long, then it must
          be a standard ISO-3166-1 two-letter country code, and if it
          is three characters long then it must be an ISO-3166-1
          three-letter country code; otherwise it is the full name
          of the country.  Similarly, if this is a "region" search
          and the string is two characters long, then it must be a
          standard two-letter state or province abbreviation;
          otherwise it is the full name of the state or province.
        </p>
Tinderbox User's avatar
Tinderbox User committed
182
        <p>
Tinderbox User's avatar
Tinderbox User committed
183 184 185 186 187 188 189 190 191 192 193 194 195 196
          The <em class="replaceable"><code>database</code></em> field indicates which
          GeoIP database to search for a match.  In most cases this is
          unnecessary, because most search fields can only be found in
          a single database.  However, searches for country can be
          answered from the "city", "region", or "country" databases,
          and searches for region (i.e., state or province) can be
          answered from the "city" or "region" databases.  For these
          search types, specifying a <em class="replaceable"><code>database</code></em>
          will force the query to be answered from that database and no
          other.  If <em class="replaceable"><code>database</code></em> is not
          specified, then these queries will be answered from the "city",
          database if it is installed, or the "region" database if it is
          installed, or the "country" database, in that order.
        </p>
Tinderbox User's avatar
Tinderbox User committed
197
        <p>
Tinderbox User's avatar
Tinderbox User committed
198 199 200 201 202
          By default, if a DNS query includes an EDNS Client Subnet (ECS)
          option which encodes a non-zero address prefix, then GeoIP ACLs
          will be matched against that address prefix.  Otherwise, they
          are matched against the source address of the query.  To
          prevent GeoIP ACLs from matching against ECS options, set
Evan Hunt's avatar
Evan Hunt committed
203
          the <span class="command"><strong>geoip-use-ecs</strong></span> to <code class="literal">no</code>.
Tinderbox User's avatar
Tinderbox User committed
204
        </p>
Tinderbox User's avatar
Tinderbox User committed
205
        <p>
Tinderbox User's avatar
Tinderbox User committed
206 207
          Some example GeoIP ACLs:
        </p>
Tinderbox User's avatar
Tinderbox User committed
208
        <pre class="programlisting">geoip country US;
Tinderbox User's avatar
Tinderbox User committed
209 210 211 212 213 214 215 216 217
geoip country JAP;
geoip db country country Canada;
geoip db region region WA;
geoip city "San Francisco";
geoip region Oklahoma;
geoip postal 95062;
geoip tz "America/Los_Angeles";
geoip org "Internet Systems Consortium";
</pre>
Tinderbox User's avatar
Tinderbox User committed
218 219

        <p>
Tinderbox User's avatar
Tinderbox User committed
220 221 222 223
          ACLs use a "first-match" logic rather than "best-match":
          if an address prefix matches an ACL element, then that ACL
          is considered to have matched even if a later element would
          have matched more specifically.  For example, the ACL
Evan Hunt's avatar
Evan Hunt committed
224
          <span class="command"><strong> { 10/8; !10.0.0.1; }</strong></span> would actually
Tinderbox User's avatar
Tinderbox User committed
225 226 227 228
          match a query from 10.0.0.1, because the first element
          indicated that the query should be accepted, and the second
          element is ignored.
        </p>
Tinderbox User's avatar
Tinderbox User committed
229
        <p>
Tinderbox User's avatar
Tinderbox User committed
230 231 232 233 234 235 236 237 238
          When using "nested" ACLs (that is, ACLs included or referenced
          within other ACLs), a negative match of a nested ACL will
          the containing ACL to continue looking for matches.  This
          enables complex ACLs to be constructed, in which multiple
          client characteristics can be checked at the same time. For
          example, to construct an ACL which allows queries only when
          it originates from a particular network <span class="emphasis"><em>and</em></span>
          only when it is signed with a particular key, use:
        </p>
Tinderbox User's avatar
Tinderbox User committed
239
        <pre class="programlisting">
Tinderbox User's avatar
Tinderbox User committed
240 241
allow-query { !{ !10/8; any; }; key example; };
</pre>
Tinderbox User's avatar
Tinderbox User committed
242
        <p>
Tinderbox User's avatar
Tinderbox User committed
243 244 245 246 247 248 249 250 251 252
          Within the nested ACL, any address that is
          <span class="emphasis"><em>not</em></span> in the 10/8 network prefix will
          be rejected, and this will terminate processing of the
          ACL.  Any address that <span class="emphasis"><em>is</em></span> in the 10/8
          network prefix will be accepted, but this causes a negative
          match of the nested ACL, so the containing ACL continues
          processing. The query will then be accepted if it is signed
          by the key "example", and rejected otherwise.  The ACL, then,
          will only matches when <span class="emphasis"><em>both</em></span> conditions
          are true.
Rob Austein's avatar
regen  
Rob Austein committed
253
        </p>
Tinderbox User's avatar
Tinderbox User committed
254 255 256
      </div>

      <div class="section">
Rob Austein's avatar
regen  
Rob Austein committed
257
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
Tinderbox User's avatar
Tinderbox User committed
258
<a name="chroot_and_setuid"></a><span class="command"><strong>Chroot</strong></span> and <span class="command"><strong>Setuid</strong></span>
Mark Andrews's avatar
regen  
Mark Andrews committed
259
</h2></div></div></div>
Tinderbox User's avatar
Tinderbox User committed
260 261

        <p>
Automatic Updater's avatar
regen  
Automatic Updater committed
262 263
          On UNIX servers, it is possible to run <acronym class="acronym">BIND</acronym>
          in a <span class="emphasis"><em>chrooted</em></span> environment (using
Evan Hunt's avatar
Evan Hunt committed
264 265
          the <span class="command"><strong>chroot()</strong></span> function) by specifying
          the <code class="option">-t</code> option for <span class="command"><strong>named</strong></span>.
Automatic Updater's avatar
regen  
Automatic Updater committed
266 267 268
          This can help improve system security by placing
          <acronym class="acronym">BIND</acronym> in a "sandbox", which will limit
          the damage done if a server is compromised.
Rob Austein's avatar
regen  
Rob Austein committed
269
        </p>
Tinderbox User's avatar
Tinderbox User committed
270
        <p>
Mark Andrews's avatar
regen  
Mark Andrews committed
271
          Another useful feature in the UNIX version of <acronym class="acronym">BIND</acronym> is the
Rob Austein's avatar
regen  
Rob Austein committed
272
          ability to run the daemon as an unprivileged user ( <code class="option">-u</code> <em class="replaceable"><code>user</code></em> ).
Evan Hunt's avatar
Evan Hunt committed
273
          We suggest running as an unprivileged user when using the <span class="command"><strong>chroot</strong></span> feature.
Rob Austein's avatar
regen  
Rob Austein committed
274
        </p>
Tinderbox User's avatar
Tinderbox User committed
275
        <p>
Evan Hunt's avatar
Evan Hunt committed
276 277
          Here is an example command line to load <acronym class="acronym">BIND</acronym> in a <span class="command"><strong>chroot</strong></span> sandbox,
          <span class="command"><strong>/var/named</strong></span>, and to run <span class="command"><strong>named</strong></span> <span class="command"><strong>setuid</strong></span> to
Rob Austein's avatar
regen  
Rob Austein committed
278 279
          user 202:
        </p>
Tinderbox User's avatar
Tinderbox User committed
280
        <p>
Automatic Updater's avatar
regen  
Automatic Updater committed
281
          <strong class="userinput"><code>/usr/local/sbin/named -u 202 -t /var/named</code></strong>
Rob Austein's avatar
regen  
Rob Austein committed
282
        </p>
Tinderbox User's avatar
Tinderbox User committed
283 284

        <div class="section">
Rob Austein's avatar
regen  
Rob Austein committed
285
<div class="titlepage"><div><div><h3 class="title">
Tinderbox User's avatar
Tinderbox User committed
286
<a name="chroot"></a>The <span class="command"><strong>chroot</strong></span> Environment</h3></div></div></div>
Tinderbox User's avatar
Tinderbox User committed
287 288

          <p>
Evan Hunt's avatar
Evan Hunt committed
289
            In order for a <span class="command"><strong>chroot</strong></span> environment
Tinderbox User's avatar
Tinderbox User committed
290 291 292 293 294 295 296 297 298
            to work properly in a particular directory (for example,
            <code class="filename">/var/named</code>), you will need to set
            up an environment that includes everything
            <acronym class="acronym">BIND</acronym> needs to run.  From
            <acronym class="acronym">BIND</acronym>'s point of view,
            <code class="filename">/var/named</code> is the root of the
            filesystem.  You will need to adjust the values of
            options like <span class="command"><strong>directory</strong></span> and
            <span class="command"><strong>pid-file</strong></span> to account for this.
Rob Austein's avatar
regen  
Rob Austein committed
299
          </p>
Tinderbox User's avatar
Tinderbox User committed
300
          <p>
Mark Andrews's avatar
regen  
Mark Andrews committed
301
            Unlike with earlier versions of BIND, you typically will
Evan Hunt's avatar
Evan Hunt committed
302
            <span class="emphasis"><em>not</em></span> need to compile <span class="command"><strong>named</strong></span>
Rob Austein's avatar
regen  
Rob Austein committed
303 304 305 306 307
            statically nor install shared libraries under the new root.
            However, depending on your operating system, you may need
            to set up things like
            <code class="filename">/dev/zero</code>,
            <code class="filename">/dev/random</code>,
Mark Andrews's avatar
regen  
Mark Andrews committed
308
            <code class="filename">/dev/log</code>, and
Rob Austein's avatar
regen  
Rob Austein committed
309 310
            <code class="filename">/etc/localtime</code>.
          </p>
Tinderbox User's avatar
Tinderbox User committed
311 312 313
        </div>

        <div class="section">
Rob Austein's avatar
regen  
Rob Austein committed
314
<div class="titlepage"><div><div><h3 class="title">
Tinderbox User's avatar
Tinderbox User committed
315
<a name="setuid"></a>Using the <span class="command"><strong>setuid</strong></span> Function</h3></div></div></div>
Tinderbox User's avatar
Tinderbox User committed
316 317

          <p>
Evan Hunt's avatar
Evan Hunt committed
318
            Prior to running the <span class="command"><strong>named</strong></span> daemon,
Rob Austein's avatar
regen  
Rob Austein committed
319
            use
Evan Hunt's avatar
Evan Hunt committed
320
            the <span class="command"><strong>touch</strong></span> utility (to change file
Rob Austein's avatar
regen  
Rob Austein committed
321
            access and
Evan Hunt's avatar
Evan Hunt committed
322
            modification times) or the <span class="command"><strong>chown</strong></span>
Rob Austein's avatar
regen  
Rob Austein committed
323 324
            utility (to
            set the user id and/or group id) on files
Mark Andrews's avatar
regen  
Mark Andrews committed
325
            to which you want <acronym class="acronym">BIND</acronym>
Mark Andrews's avatar
gregen  
Mark Andrews committed
326
            to write.
Rob Austein's avatar
regen  
Rob Austein committed
327
          </p>
Tinderbox User's avatar
Tinderbox User committed
328
          <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
Mark Andrews's avatar
gregen  
Mark Andrews committed
329
<h3 class="title">Note</h3>
Tinderbox User's avatar
Tinderbox User committed
330 331
<p>
            If the <span class="command"><strong>named</strong></span> daemon is running as an
Mark Andrews's avatar
gregen  
Mark Andrews committed
332 333
            unprivileged user, it will not be able to bind to new restricted
            ports if the server is reloaded.
Tinderbox User's avatar
Tinderbox User committed
334 335
          </p>
</div>
Tinderbox User's avatar
Tinderbox User committed
336 337 338 339
        </div>
      </div>

      <div class="section">
Rob Austein's avatar
regen  
Rob Austein committed
340 341
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="dynamic_update_security"></a>Dynamic Update Security</h2></div></div></div>
Tinderbox User's avatar
Tinderbox User committed
342 343

        <p>
Rob Austein's avatar
regen  
Rob Austein committed
344 345
          Access to the dynamic
          update facility should be strictly limited.  In earlier versions of
Mark Andrews's avatar
regen  
Mark Andrews committed
346
          <acronym class="acronym">BIND</acronym>, the only way to do this was
Rob Austein's avatar
regen  
Rob Austein committed
347 348 349
          based on the IP
          address of the host requesting the update, by listing an IP address
          or
Evan Hunt's avatar
Evan Hunt committed
350
          network prefix in the <span class="command"><strong>allow-update</strong></span>
Rob Austein's avatar
regen  
Rob Austein committed
351 352 353 354
          zone option.
          This method is insecure since the source address of the update UDP
          packet
          is easily forged.  Also note that if the IP addresses allowed by the
Evan Hunt's avatar
Evan Hunt committed
355
          <span class="command"><strong>allow-update</strong></span> option include the
Rob Austein's avatar
regen  
Rob Austein committed
356 357 358 359 360 361 362
          address of a slave
          server which performs forwarding of dynamic updates, the master can
          be
          trivially attacked by sending the update to the slave, which will
          forward it to the master with its own source IP address causing the
          master to approve it without question.
        </p>
Tinderbox User's avatar
Tinderbox User committed
363 364

        <p>
Rob Austein's avatar
regen  
Rob Austein committed
365 366
          For these reasons, we strongly recommend that updates be
          cryptographically authenticated by means of transaction signatures
Evan Hunt's avatar
Evan Hunt committed
367
          (TSIG).  That is, the <span class="command"><strong>allow-update</strong></span>
Rob Austein's avatar
regen  
Rob Austein committed
368 369
          option should
          list only TSIG key names, not IP addresses or network
Evan Hunt's avatar
Evan Hunt committed
370
          prefixes. Alternatively, the new <span class="command"><strong>update-policy</strong></span>
Rob Austein's avatar
regen  
Rob Austein committed
371 372
          option can be used.
        </p>
Tinderbox User's avatar
Tinderbox User committed
373 374

        <p>
Mark Andrews's avatar
regen  
Mark Andrews committed
375
          Some sites choose to keep all dynamically-updated DNS data
Rob Austein's avatar
regen  
Rob Austein committed
376 377 378 379 380 381
          in a subdomain and delegate that subdomain to a separate zone. This
          way, the top-level zone containing critical data such as the IP
          addresses
          of public web and mail servers need not allow dynamic update at
          all.
        </p>
Tinderbox User's avatar
Tinderbox User committed
382 383 384

      </div>
    </div>
Rob Austein's avatar
regen  
Rob Austein committed
385 386 387 388 389 390 391 392 393 394 395
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="Bv9ARM.ch06.html">Prev</a> </td>
<td width="20%" align="center"> </td>
<td width="40%" align="right"> <a accesskey="n" href="Bv9ARM.ch08.html">Next</a>
</td>
</tr>
<tr>
Mark Andrews's avatar
regen  
Mark Andrews committed
396
<td width="40%" align="left" valign="top">Chapter 6. <acronym class="acronym">BIND</acronym> 9 Configuration Reference </td>
Rob Austein's avatar
regen  
Rob Austein committed
397 398 399 400 401
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top"> Chapter 8. Troubleshooting</td>
</tr>
</table>
</div>
Tinderbox User's avatar
Tinderbox User committed
402
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.12.0-pre-alpha</p>
Rob Austein's avatar
regen  
Rob Austein committed
403 404
</body>
</html>