Bv9ARM.ch07.html 18.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-2015 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
<div class="section">
Rob Austein's avatar
regen    
Rob Austein committed
49
50
<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
51
<p>
Automatic Updater's avatar
regen    
Automatic Updater committed
52
          Access Control Lists (ACLs) are address match lists that
Tinderbox User's avatar
Tinderbox User committed
53
          you can set up and nickname for future use in
Evan Hunt's avatar
Evan Hunt committed
54
55
56
57
          <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
58
        </p>
Tinderbox User's avatar
Tinderbox User committed
59
<p>
Rob Austein's avatar
regen    
Rob Austein committed
60
61
62
63
          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
64
<p>
Rob Austein's avatar
regen    
Rob Austein committed
65
66
          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
67
68
          outside parties can help prevent spoofing and denial of service
          (DoS) attacks against your server.
Rob Austein's avatar
regen    
Rob Austein committed
69
        </p>
Tinderbox User's avatar
Tinderbox User committed
70
<p>
Tinderbox User's avatar
Tinderbox User committed
71
72
73
74
75
          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
76
<p>
Tinderbox User's avatar
Tinderbox User committed
77
          Here is an example of ACLs based on client addresses:
Rob Austein's avatar
regen    
Rob Austein committed
78
79
        </p>
<pre class="programlisting">
Automatic Updater's avatar
regen    
Automatic Updater committed
80
81
82
// 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
83
acl bogusnets {
Automatic Updater's avatar
Automatic Updater committed
84
85
        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
86
};
Mark Andrews's avatar
regen    
Mark Andrews committed
87

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

101
102
103
104
105
zone "example.com" {
  type master;
  file "m/example.com";
  allow-query { any; };
};
Rob Austein's avatar
regen    
Rob Austein committed
106
</pre>
Tinderbox User's avatar
Tinderbox User committed
107
<p>
Tinderbox User's avatar
Tinderbox User committed
108
109
110
111
112
          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
113
<p>
Tinderbox User's avatar
Tinderbox User committed
114
115
116
117
118
119
120
121
          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
122
<p>
Tinderbox User's avatar
Tinderbox User committed
123
124
125
126
127
128
          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
129
          <span class="command"><strong>ecs <em class="replaceable"><code>prefix</code></em></strong></span>
Tinderbox User's avatar
Tinderbox User committed
130
131
132
133
134
135
          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
136
<p>
Tinderbox User's avatar
Tinderbox User committed
137
138
139
          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
140
          <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
141
        </p>
Tinderbox User's avatar
Tinderbox User committed
142
<p>
Tinderbox User's avatar
Tinderbox User committed
143
144
145
146
147
148
          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
149
<p>
Tinderbox User's avatar
Tinderbox User committed
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
          <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
165
<p>
Tinderbox User's avatar
Tinderbox User committed
166
167
168
169
170
171
172
173
174
175
176
177
178
179
          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
180
<p>
Tinderbox User's avatar
Tinderbox User committed
181
182
183
184
185
          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
186
          the <span class="command"><strong>geoip-use-ecs</strong></span> to <code class="literal">no</code>.
Tinderbox User's avatar
Tinderbox User committed
187
        </p>
Tinderbox User's avatar
Tinderbox User committed
188
<p>
Tinderbox User's avatar
Tinderbox User committed
189
190
          Some example GeoIP ACLs:
        </p>
Tinderbox User's avatar
Tinderbox User committed
191
<pre class="programlisting">geoip country US;
Tinderbox User's avatar
Tinderbox User committed
192
193
194
195
196
197
198
199
200
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
201
<p>
Tinderbox User's avatar
Tinderbox User committed
202
203
204
205
          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
206
          <span class="command"><strong> { 10/8; !10.0.0.1; }</strong></span> would actually
Tinderbox User's avatar
Tinderbox User committed
207
208
209
210
          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
211
<p>
Tinderbox User's avatar
Tinderbox User committed
212
213
214
215
216
217
218
219
220
          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
221
<pre class="programlisting">
Tinderbox User's avatar
Tinderbox User committed
222
223
allow-query { !{ !10/8; any; }; key example; };
</pre>
Tinderbox User's avatar
Tinderbox User committed
224
<p>
Tinderbox User's avatar
Tinderbox User committed
225
226
227
228
229
230
231
232
233
234
          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
235
        </p>
Tinderbox User's avatar
Tinderbox User committed
236
237
</div>
<div class="section">
Rob Austein's avatar
regen    
Rob Austein committed
238
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
Tinderbox User's avatar
Tinderbox User committed
239
<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
240
</h2></div></div></div>
Tinderbox User's avatar
Tinderbox User committed
241
<p>
Automatic Updater's avatar
regen    
Automatic Updater committed
242
243
          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
244
245
          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
246
247
248
          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
249
        </p>
Tinderbox User's avatar
Tinderbox User committed
250
<p>
Mark Andrews's avatar
regen    
Mark Andrews committed
251
          Another useful feature in the UNIX version of <acronym class="acronym">BIND</acronym> is the
Rob Austein's avatar
regen    
Rob Austein committed
252
          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
253
          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
254
        </p>
Tinderbox User's avatar
Tinderbox User committed
255
<p>
Evan Hunt's avatar
Evan Hunt committed
256
257
          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
258
259
          user 202:
        </p>
Tinderbox User's avatar
Tinderbox User committed
260
<p>
Automatic Updater's avatar
regen    
Automatic Updater committed
261
          <strong class="userinput"><code>/usr/local/sbin/named -u 202 -t /var/named</code></strong>
Rob Austein's avatar
regen    
Rob Austein committed
262
        </p>
Tinderbox User's avatar
Tinderbox User committed
263
<div class="section">
Rob Austein's avatar
regen    
Rob Austein committed
264
<div class="titlepage"><div><div><h3 class="title">
Tinderbox User's avatar
Tinderbox User committed
265
<a name="chroot"></a>The <span class="command"><strong>chroot</strong></span> Environment</h3></div></div></div>
Tinderbox User's avatar
Tinderbox User committed
266
<p>
Evan Hunt's avatar
Evan Hunt committed
267
            In order for a <span class="command"><strong>chroot</strong></span> environment
Tinderbox User's avatar
Tinderbox User committed
268
269
270
271
272
273
274
275
276
            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
277
          </p>
Tinderbox User's avatar
Tinderbox User committed
278
<p>
Mark Andrews's avatar
regen    
Mark Andrews committed
279
            Unlike with earlier versions of BIND, you typically will
Evan Hunt's avatar
Evan Hunt committed
280
            <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
281
282
283
284
285
            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
286
            <code class="filename">/dev/log</code>, and
Rob Austein's avatar
regen    
Rob Austein committed
287
288
            <code class="filename">/etc/localtime</code>.
          </p>
Tinderbox User's avatar
Tinderbox User committed
289
290
</div>
<div class="section">
Rob Austein's avatar
regen    
Rob Austein committed
291
<div class="titlepage"><div><div><h3 class="title">
Tinderbox User's avatar
Tinderbox User committed
292
<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
293
<p>
Evan Hunt's avatar
Evan Hunt committed
294
            Prior to running the <span class="command"><strong>named</strong></span> daemon,
Rob Austein's avatar
regen    
Rob Austein committed
295
            use
Evan Hunt's avatar
Evan Hunt committed
296
            the <span class="command"><strong>touch</strong></span> utility (to change file
Rob Austein's avatar
regen    
Rob Austein committed
297
            access and
Evan Hunt's avatar
Evan Hunt committed
298
            modification times) or the <span class="command"><strong>chown</strong></span>
Rob Austein's avatar
regen    
Rob Austein committed
299
300
            utility (to
            set the user id and/or group id) on files
Mark Andrews's avatar
regen    
Mark Andrews committed
301
            to which you want <acronym class="acronym">BIND</acronym>
Mark Andrews's avatar
gregen    
Mark Andrews committed
302
            to write.
Rob Austein's avatar
regen    
Rob Austein committed
303
          </p>
Tinderbox User's avatar
Tinderbox User committed
304
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
Mark Andrews's avatar
gregen    
Mark Andrews committed
305
<h3 class="title">Note</h3>
Tinderbox User's avatar
Tinderbox User committed
306
307
<p>
            If the <span class="command"><strong>named</strong></span> daemon is running as an
Mark Andrews's avatar
gregen    
Mark Andrews committed
308
309
            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
310
311
          </p>
</div>
Tinderbox User's avatar
Tinderbox User committed
312
313
314
</div>
</div>
<div class="section">
Rob Austein's avatar
regen    
Rob Austein committed
315
316
<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
317
<p>
Rob Austein's avatar
regen    
Rob Austein committed
318
319
          Access to the dynamic
          update facility should be strictly limited.  In earlier versions of
Mark Andrews's avatar
regen    
Mark Andrews committed
320
          <acronym class="acronym">BIND</acronym>, the only way to do this was
Rob Austein's avatar
regen    
Rob Austein committed
321
322
323
          based on the IP
          address of the host requesting the update, by listing an IP address
          or
Evan Hunt's avatar
Evan Hunt committed
324
          network prefix in the <span class="command"><strong>allow-update</strong></span>
Rob Austein's avatar
regen    
Rob Austein committed
325
326
327
328
          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
329
          <span class="command"><strong>allow-update</strong></span> option include the
Rob Austein's avatar
regen    
Rob Austein committed
330
331
332
333
334
335
336
          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
337
<p>
Rob Austein's avatar
regen    
Rob Austein committed
338
339
          For these reasons, we strongly recommend that updates be
          cryptographically authenticated by means of transaction signatures
Evan Hunt's avatar
Evan Hunt committed
340
          (TSIG).  That is, the <span class="command"><strong>allow-update</strong></span>
Rob Austein's avatar
regen    
Rob Austein committed
341
342
          option should
          list only TSIG key names, not IP addresses or network
Evan Hunt's avatar
Evan Hunt committed
343
          prefixes. Alternatively, the new <span class="command"><strong>update-policy</strong></span>
Rob Austein's avatar
regen    
Rob Austein committed
344
345
          option can be used.
        </p>
Tinderbox User's avatar
Tinderbox User committed
346
<p>
Mark Andrews's avatar
regen    
Mark Andrews committed
347
          Some sites choose to keep all dynamically-updated DNS data
Rob Austein's avatar
regen    
Rob Austein committed
348
349
350
351
352
353
          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
354
355
</div>
</div>
Rob Austein's avatar
regen    
Rob Austein committed
356
357
358
359
360
361
362
363
364
365
366
<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
367
<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
368
369
370
371
372
<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>
Mark Andrews's avatar
Mark Andrews committed
373
<p xmlns:db="http://docbook.org/ns/docbook" style="text-align: center;">BIND 9.11.0rc2</p>
Rob Austein's avatar
regen    
Rob Austein committed
374
375
</body>
</html>