external/bsd/bind/dist/doc/arm/man.nsupdate.html

   1 <!--
   2  - Copyright (C) 2004-2009 Internet Systems Consortium, Inc. ("ISC")
   3  - Copyright (C) 2000-2003 Internet Software Consortium.
   4  -
   5  - Permission to use, copy, modify, and/or distribute this software for any
   6  - purpose with or without fee is hereby granted, provided that the above
   7  - copyright notice and this permission notice appear in all copies.
   8  -
   9  - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
  10  - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
  11  - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
  12  - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
  13  - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
  14  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  15  - PERFORMANCE OF THIS SOFTWARE.
  16 -->
  17 <!-- Id: man.nsupdate.html,v 1.80 2009/12/04 22:22:25 tbox Exp -->
  18 <html>
  19 <head>
  20 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  21 <title>nsupdate</title>
  22 <meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
  23 <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
  24 <link rel="up" href="Bv9ARM.ch10.html" title="Manual pages">
  25 <link rel="prev" href="man.named-journalprint.html" title="named-journalprint">
  26 <link rel="next" href="man.rndc.html" title="rndc">
  27 </head>
  28 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
  29 <div class="navheader">
  30 <table width="100%" summary="Navigation header">
  31 <tr><th colspan="3" align="center"><span class="application">nsupdate</span></th></tr>
  32 <tr>
  33 <td width="20%" align="left">
  34 <a accesskey="p" href="man.named-journalprint.html">Prev</a> </td>
  35 <th width="60%" align="center">Manual pages</th>
  36 <td width="20%" align="right"> <a accesskey="n" href="man.rndc.html">Next</a>
  37 </td>
  38 </tr>
  39 </table>
  40 <hr>
  41 </div>
  42 <div class="refentry" lang="en">
  43 <a name="man.nsupdate"></a><div class="titlepage"></div>
  44 <div class="refnamediv">
  45 <h2>Name</h2>
  46 <p><span class="application">nsupdate</span> &#8212; Dynamic DNS update utility</p>
  47 </div>
  48 <div class="refsynopsisdiv">
  49 <h2>Synopsis</h2>
  50 <div class="cmdsynopsis"><p><code class="command">nsupdate</code>  [<code class="option">-d</code>] [<code class="option">-D</code>] [[<code class="option">-g</code>] |  [<code class="option">-o</code>] |  [<code class="option">-l</code>] |  [<code class="option">-y <em class="replaceable"><code>[<span class="optional">hmac:</span>]keyname:secret</code></em></code>] |  [<code class="option">-k <em class="replaceable"><code>keyfile</code></em></code>]] [<code class="option">-t <em class="replaceable"><code>timeout</code></em></code>] [<code class="option">-u <em class="replaceable"><code>udptimeout</code></em></code>] [<code class="option">-r <em class="replaceable"><code>udpretries</code></em></code>] [<code class="option">-R <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-v</code>] [filename]</p></div>
  51 </div>
  52 <div class="refsect1" lang="en">
  53 <a name="id2616486"></a><h2>DESCRIPTION</h2>
  54 <p><span><strong class="command">nsupdate</strong></span>
  55       is used to submit Dynamic DNS Update requests as defined in RFC 2136
  56       to a name server.
  57       This allows resource records to be added or removed from a zone
  58       without manually editing the zone file.
  59       A single update request can contain requests to add or remove more than
  60       one
  61       resource record.
  62     </p>
  63 <p>
  64       Zones that are under dynamic control via
  65       <span><strong class="command">nsupdate</strong></span>
  66       or a DHCP server should not be edited by hand.
  67       Manual edits could
  68       conflict with dynamic updates and cause data to be lost.
  69     </p>
  70 <p>
  71       The resource records that are dynamically added or removed with
  72       <span><strong class="command">nsupdate</strong></span>
  73       have to be in the same zone.
  74       Requests are sent to the zone's master server.
  75       This is identified by the MNAME field of the zone's SOA record.
  76     </p>
  77 <p>
  78       The
  79       <code class="option">-d</code>
  80       option makes
  81       <span><strong class="command">nsupdate</strong></span>
  82       operate in debug mode.
  83       This provides tracing information about the update requests that are
  84       made and the replies received from the name server.
  85     </p>
  86 <p>
  87       The <code class="option">-D</code> option makes <span><strong class="command">nsupdate</strong></span>
  88       report additional debugging information to <code class="option">-d</code>.
  89     </p>
  90 <p>
  91       The <code class="option">-L</code> option with an integer argument of zero or
  92       higher sets the logging debug level.  If zero, logging is disabled.
  93     </p>
  94 <p>
  95       Transaction signatures can be used to authenticate the Dynamic
  96       DNS updates.  These use the TSIG resource record type described
  97       in RFC 2845 or the SIG(0) record described in RFC 2535 and
  98       RFC 2931 or GSS-TSIG as described in RFC 3645.  TSIG relies on
  99       a shared secret that should only be known to
 100       <span><strong class="command">nsupdate</strong></span> and the name server.  Currently,
 101       the only supported encryption algorithm for TSIG is HMAC-MD5,
 102       which is defined in RFC 2104.  Once other algorithms are
 103       defined for TSIG, applications will need to ensure they select
 104       the appropriate algorithm as well as the key when authenticating
 105       each other.  For instance, suitable <span class="type">key</span> and
 106       <span class="type">server</span> statements would be added to
 107       <code class="filename">/etc/named.conf</code> so that the name server
 108       can associate the appropriate secret key and algorithm with
 109       the IP address of the client application that will be using
 110       TSIG authentication.  SIG(0) uses public key cryptography.
 111       To use a SIG(0) key, the public key must be stored in a KEY
 112       record in a zone served by the name server.
 113       <span><strong class="command">nsupdate</strong></span> does not read
 114       <code class="filename">/etc/named.conf</code>.
 115     </p>
 116 <p>
 117       GSS-TSIG uses Kerberos credentials.  Standard GSS-TSIG mode
 118       is switched on with the <code class="option">-g</code> flag.  A
 119       non-standards-compliant variant of GSS-TSIG used by Windows
 120       2000 can be switched on with the <code class="option">-o</code> flag.
 121     </p>
 122 <p><span><strong class="command">nsupdate</strong></span>
 123       uses the <code class="option">-y</code> or <code class="option">-k</code> option
 124       to provide the shared secret needed to generate a TSIG record
 125       for authenticating Dynamic DNS update requests, default type
 126       HMAC-MD5.  These options are mutually exclusive.
 127     </p>
 128 <p>
 129       When the <code class="option">-y</code> option is used, a signature is
 130       generated from
 131       [<span class="optional"><em class="parameter"><code>hmac:</code></em></span>]<em class="parameter"><code>keyname:secret.</code></em>
 132       <em class="parameter"><code>keyname</code></em> is the name of the key, and
 133       <em class="parameter"><code>secret</code></em> is the base64 encoded shared secret.
 134       Use of the <code class="option">-y</code> option is discouraged because the
 135       shared secret is supplied as a command line argument in clear text.
 136       This may be visible in the output from
 137       <span class="citerefentry"><span class="refentrytitle">ps</span>(1)</span>
 138       or in a history file maintained by the user's shell.
 139     </p>
 140 <p>
 141       With the
 142       <code class="option">-k</code> option, <span><strong class="command">nsupdate</strong></span> reads
 143       the shared secret from the file <em class="parameter"><code>keyfile</code></em>.
 144       Keyfiles may be in two formats: a single file containing
 145       a <code class="filename">named.conf</code>-format <span><strong class="command">key</strong></span>
 146       statement, which may be generated automatically by
 147       <span><strong class="command">ddns-confgen</strong></span>, or a pair of files whose names are
 148       of the format <code class="filename">K{name}.+157.+{random}.key</code> and
 149       <code class="filename">K{name}.+157.+{random}.private</code>, which can be
 150       generated by <span><strong class="command">dnssec-keygen</strong></span>.
 151       The <code class="option">-k</code> may also be used to specify a SIG(0) key used
 152       to authenticate Dynamic DNS update requests.  In this case, the key
 153       specified is not an HMAC-MD5 key.
 154     </p>
 155 <p>
 156       <span><strong class="command">nsupdate</strong></span> can be run in a local-host only mode
 157       using the <code class="option">-l</code> flag.  This sets the server address to
 158       localhost (disabling the <span><strong class="command">server</strong></span> so that the server
 159       address cannot be overridden).  Connections to the local server will
 160       use a TSIG key found in <code class="filename">/var/run/named/ddns.key</code>,
 161       which is automatically generated by <span><strong class="command">named</strong></span> if any
 162       local master zone has set <span><strong class="command">update-policy</strong></span> to
 163       <span><strong class="command">local</strong></span>.  The location of this key file can be
 164       overridden with the <code class="option">-k</code> option.
 165     </p>
 166 <p>
 167       By default, <span><strong class="command">nsupdate</strong></span>
 168       uses UDP to send update requests to the name server unless they are too
 169       large to fit in a UDP request in which case TCP will be used.
 170       The
 171       <code class="option">-v</code>
 172       option makes
 173       <span><strong class="command">nsupdate</strong></span>
 174       use a TCP connection.
 175       This may be preferable when a batch of update requests is made.
 176     </p>
 177 <p>
 178       The <code class="option">-p</code> sets the default port number to use for
 179       connections to a name server.  The default is 53.
 180     </p>
 181 <p>
 182       The <code class="option">-t</code> option sets the maximum time an update request
 183       can
 184       take before it is aborted.  The default is 300 seconds.  Zero can be
 185       used
 186       to disable the timeout.
 187     </p>
 188 <p>
 189       The <code class="option">-u</code> option sets the UDP retry interval.  The default
 190       is
 191       3 seconds.  If zero, the interval will be computed from the timeout
 192       interval
 193       and number of UDP retries.
 194     </p>
 195 <p>
 196       The <code class="option">-r</code> option sets the number of UDP retries. The
 197       default is
 198       3.  If zero, only one update request will be made.
 199     </p>
 200 <p>
 201       The <code class="option">-R <em class="replaceable"><code>randomdev</code></em></code> option
 202       specifies a source of randomness.  If the operating system
 203       does not provide a <code class="filename">/dev/random</code> or
 204       equivalent device, the default source of randomness is keyboard
 205       input.  <code class="filename">randomdev</code> specifies the name of
 206       a character device or file containing random data to be used
 207       instead of the default.  The special value
 208       <code class="filename">keyboard</code> indicates that keyboard input
 209       should be used.  This option may be specified multiple times.
 210     </p>
 211 </div>
 212 <div class="refsect1" lang="en">
 213 <a name="id2629654"></a><h2>INPUT FORMAT</h2>
 214 <p><span><strong class="command">nsupdate</strong></span>
 215       reads input from
 216       <em class="parameter"><code>filename</code></em>
 217       or standard input.
 218       Each command is supplied on exactly one line of input.
 219       Some commands are for administrative purposes.
 220       The others are either update instructions or prerequisite checks on the
 221       contents of the zone.
 222       These checks set conditions that some name or set of
 223       resource records (RRset) either exists or is absent from the zone.
 224       These conditions must be met if the entire update request is to succeed.
 225       Updates will be rejected if the tests for the prerequisite conditions
 226       fail.
 227     </p>
 228 <p>
 229       Every update request consists of zero or more prerequisites
 230       and zero or more updates.
 231       This allows a suitably authenticated update request to proceed if some
 232       specified resource records are present or missing from the zone.
 233       A blank input line (or the <span><strong class="command">send</strong></span> command)
 234       causes the
 235       accumulated commands to be sent as one Dynamic DNS update request to the
 236       name server.
 237     </p>
 238 <p>
 239       The command formats and their meaning are as follows:
 240       </p>
 241 <div class="variablelist"><dl>
 242 <dt><span class="term">
 243               <span><strong class="command">server</strong></span>
 244                {servername}
 245                [port]
 246             </span></dt>
 247 <dd><p>
 248               Sends all dynamic update requests to the name server
 249               <em class="parameter"><code>servername</code></em>.
 250               When no server statement is provided,
 251               <span><strong class="command">nsupdate</strong></span>
 252               will send updates to the master server of the correct zone.
 253               The MNAME field of that zone's SOA record will identify the
 254               master
 255               server for that zone.
 256               <em class="parameter"><code>port</code></em>
 257               is the port number on
 258               <em class="parameter"><code>servername</code></em>
 259               where the dynamic update requests get sent.
 260               If no port number is specified, the default DNS port number of
 261               53 is
 262               used.
 263             </p></dd>
 264 <dt><span class="term">
 265               <span><strong class="command">local</strong></span>
 266                {address}
 267                [port]
 268             </span></dt>
 269 <dd><p>
 270               Sends all dynamic update requests using the local
 271               <em class="parameter"><code>address</code></em>.
 272
 273               When no local statement is provided,
 274               <span><strong class="command">nsupdate</strong></span>
 275               will send updates using an address and port chosen by the
 276               system.
 277               <em class="parameter"><code>port</code></em>
 278               can additionally be used to make requests come from a specific
 279               port.
 280               If no port number is specified, the system will assign one.
 281             </p></dd>
 282 <dt><span class="term">
 283               <span><strong class="command">zone</strong></span>
 284                {zonename}
 285             </span></dt>
 286 <dd><p>
 287               Specifies that all updates are to be made to the zone
 288               <em class="parameter"><code>zonename</code></em>.
 289               If no
 290               <em class="parameter"><code>zone</code></em>
 291               statement is provided,
 292               <span><strong class="command">nsupdate</strong></span>
 293               will attempt determine the correct zone to update based on the
 294               rest of the input.
 295             </p></dd>
 296 <dt><span class="term">
 297               <span><strong class="command">class</strong></span>
 298                {classname}
 299             </span></dt>
 300 <dd><p>
 301               Specify the default class.
 302               If no <em class="parameter"><code>class</code></em> is specified, the
 303               default class is
 304               <em class="parameter"><code>IN</code></em>.
 305             </p></dd>
 306 <dt><span class="term">
 307               <span><strong class="command">ttl</strong></span>
 308                {seconds}
 309             </span></dt>
 310 <dd><p>
 311               Specify the default time to live for records to be added.
 312               The value <em class="parameter"><code>none</code></em> will clear the default
 313               ttl.
 314             </p></dd>
 315 <dt><span class="term">
 316               <span><strong class="command">key</strong></span>
 317                {name}
 318                {secret}
 319             </span></dt>
 320 <dd><p>
 321               Specifies that all updates are to be TSIG-signed using the
 322               <em class="parameter"><code>keyname</code></em> <em class="parameter"><code>keysecret</code></em> pair.
 323               The <span><strong class="command">key</strong></span> command
 324               overrides any key specified on the command line via
 325               <code class="option">-y</code> or <code class="option">-k</code>.
 326             </p></dd>
 327 <dt><span class="term">
 328               <span><strong class="command">prereq nxdomain</strong></span>
 329                {domain-name}
 330             </span></dt>
 331 <dd><p>
 332               Requires that no resource record of any type exists with name
 333               <em class="parameter"><code>domain-name</code></em>.
 334             </p></dd>
 335 <dt><span class="term">
 336               <span><strong class="command">prereq yxdomain</strong></span>
 337                {domain-name}
 338             </span></dt>
 339 <dd><p>
 340               Requires that
 341               <em class="parameter"><code>domain-name</code></em>
 342               exists (has as at least one resource record, of any type).
 343             </p></dd>
 344 <dt><span class="term">
 345               <span><strong class="command">prereq nxrrset</strong></span>
 346                {domain-name}
 347                [class]
 348                {type}
 349             </span></dt>
 350 <dd><p>
 351               Requires that no resource record exists of the specified
 352               <em class="parameter"><code>type</code></em>,
 353               <em class="parameter"><code>class</code></em>
 354               and
 355               <em class="parameter"><code>domain-name</code></em>.
 356               If
 357               <em class="parameter"><code>class</code></em>
 358               is omitted, IN (internet) is assumed.
 359             </p></dd>
 360 <dt><span class="term">
 361               <span><strong class="command">prereq yxrrset</strong></span>
 362                {domain-name}
 363                [class]
 364                {type}
 365             </span></dt>
 366 <dd><p>
 367               This requires that a resource record of the specified
 368               <em class="parameter"><code>type</code></em>,
 369               <em class="parameter"><code>class</code></em>
 370               and
 371               <em class="parameter"><code>domain-name</code></em>
 372               must exist.
 373               If
 374               <em class="parameter"><code>class</code></em>
 375               is omitted, IN (internet) is assumed.
 376             </p></dd>
 377 <dt><span class="term">
 378               <span><strong class="command">prereq yxrrset</strong></span>
 379                {domain-name}
 380                [class]
 381                {type}
 382                {data...}
 383             </span></dt>
 384 <dd><p>
 385               The
 386               <em class="parameter"><code>data</code></em>
 387               from each set of prerequisites of this form
 388               sharing a common
 389               <em class="parameter"><code>type</code></em>,
 390               <em class="parameter"><code>class</code></em>,
 391               and
 392               <em class="parameter"><code>domain-name</code></em>
 393               are combined to form a set of RRs.  This set of RRs must
 394               exactly match the set of RRs existing in the zone at the
 395               given
 396               <em class="parameter"><code>type</code></em>,
 397               <em class="parameter"><code>class</code></em>,
 398               and
 399               <em class="parameter"><code>domain-name</code></em>.
 400               The
 401               <em class="parameter"><code>data</code></em>
 402               are written in the standard text representation of the resource
 403               record's
 404               RDATA.
 405             </p></dd>
 406 <dt><span class="term">
 407               <span><strong class="command">update delete</strong></span>
 408                {domain-name}
 409                [ttl]
 410                [class]
 411                [type [data...]]
 412             </span></dt>
 413 <dd><p>
 414               Deletes any resource records named
 415               <em class="parameter"><code>domain-name</code></em>.
 416               If
 417               <em class="parameter"><code>type</code></em>
 418               and
 419               <em class="parameter"><code>data</code></em>
 420               is provided, only matching resource records will be removed.
 421               The internet class is assumed if
 422               <em class="parameter"><code>class</code></em>
 423               is not supplied.  The
 424               <em class="parameter"><code>ttl</code></em>
 425               is ignored, and is only allowed for compatibility.
 426             </p></dd>
 427 <dt><span class="term">
 428               <span><strong class="command">update add</strong></span>
 429                {domain-name}
 430                {ttl}
 431                [class]
 432                {type}
 433                {data...}
 434             </span></dt>
 435 <dd><p>
 436               Adds a new resource record with the specified
 437               <em class="parameter"><code>ttl</code></em>,
 438               <em class="parameter"><code>class</code></em>
 439               and
 440               <em class="parameter"><code>data</code></em>.
 441             </p></dd>
 442 <dt><span class="term">
 443               <span><strong class="command">show</strong></span>
 444             </span></dt>
 445 <dd><p>
 446               Displays the current message, containing all of the
 447               prerequisites and
 448               updates specified since the last send.
 449             </p></dd>
 450 <dt><span class="term">
 451               <span><strong class="command">send</strong></span>
 452             </span></dt>
 453 <dd><p>
 454               Sends the current message.  This is equivalent to entering a
 455               blank line.
 456             </p></dd>
 457 <dt><span class="term">
 458               <span><strong class="command">answer</strong></span>
 459             </span></dt>
 460 <dd><p>
 461               Displays the answer.
 462             </p></dd>
 463 <dt><span class="term">
 464               <span><strong class="command">debug</strong></span>
 465             </span></dt>
 466 <dd><p>
 467               Turn on debugging.
 468             </p></dd>
 469 </dl></div>
 470 <p>
 471     </p>
 472 <p>
 473       Lines beginning with a semicolon are comments and are ignored.
 474     </p>
 475 </div>
 476 <div class="refsect1" lang="en">
 477 <a name="id2672807"></a><h2>EXAMPLES</h2>
 478 <p>
 479       The examples below show how
 480       <span><strong class="command">nsupdate</strong></span>
 481       could be used to insert and delete resource records from the
 482       <span class="type">example.com</span>
 483       zone.
 484       Notice that the input in each example contains a trailing blank line so
 485       that
 486       a group of commands are sent as one dynamic update request to the
 487       master name server for
 488       <span class="type">example.com</span>.
 489
 490       </p>
 491 <pre class="programlisting">
 492 # nsupdate
 493 &gt; update delete oldhost.example.com A
 494 &gt; update add newhost.example.com 86400 A 172.16.1.1
 495 &gt; send
 496 </pre>
 497 <p>
 498     </p>
 499 <p>
 500       Any A records for
 501       <span class="type">oldhost.example.com</span>
 502       are deleted.
 503       And an A record for
 504       <span class="type">newhost.example.com</span>
 505       with IP address 172.16.1.1 is added.
 506       The newly-added record has a 1 day TTL (86400 seconds).
 507       </p>
 508 <pre class="programlisting">
 509 # nsupdate
 510 &gt; prereq nxdomain nickname.example.com
 511 &gt; update add nickname.example.com 86400 CNAME somehost.example.com
 512 &gt; send
 513 </pre>
 514 <p>
 515     </p>
 516 <p>
 517       The prerequisite condition gets the name server to check that there
 518       are no resource records of any type for
 519       <span class="type">nickname.example.com</span>.
 520
 521       If there are, the update request fails.
 522       If this name does not exist, a CNAME for it is added.
 523       This ensures that when the CNAME is added, it cannot conflict with the
 524       long-standing rule in RFC 1034 that a name must not exist as any other
 525       record type if it exists as a CNAME.
 526       (The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have
 527       RRSIG, DNSKEY and NSEC records.)
 528     </p>
 529 </div>
 530 <div class="refsect1" lang="en">
 531 <a name="id2672857"></a><h2>FILES</h2>
 532 <div class="variablelist"><dl>
 533 <dt><span class="term"><code class="constant">/etc/resolv.conf</code></span></dt>
 534 <dd><p>
 535             used to identify default name server
 536           </p></dd>
 537 <dt><span class="term"><code class="constant">/var/run/named/ddns.key</code></span></dt>
 538 <dd><p>
 539             sets the default TSIG key for use in local-only mode
 540           </p></dd>
 541 <dt><span class="term"><code class="constant">K{name}.+157.+{random}.key</code></span></dt>
 542 <dd><p>
 543             base-64 encoding of HMAC-MD5 key created by
 544             <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
 545           </p></dd>
 546 <dt><span class="term"><code class="constant">K{name}.+157.+{random}.private</code></span></dt>
 547 <dd><p>
 548             base-64 encoding of HMAC-MD5 key created by
 549             <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
 550           </p></dd>
 551 </dl></div>
 552 </div>
 553 <div class="refsect1" lang="en">
 554 <a name="id2673009"></a><h2>SEE ALSO</h2>
 555 <p>
 556       <em class="citetitle">RFC 2136</em>,
 557       <em class="citetitle">RFC 3007</em>,
 558       <em class="citetitle">RFC 2104</em>,
 559       <em class="citetitle">RFC 2845</em>,
 560       <em class="citetitle">RFC 1034</em>,
 561       <em class="citetitle">RFC 2535</em>,
 562       <em class="citetitle">RFC 2931</em>,
 563       <span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
 564       <span class="citerefentry"><span class="refentrytitle">ddns-confgen</span>(8)</span>,
 565       <span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>.
 566     </p>
 567 </div>
 568 <div class="refsect1" lang="en">
 569 <a name="id2673066"></a><h2>BUGS</h2>
 570 <p>
 571       The TSIG key is redundantly stored in two separate files.
 572       This is a consequence of nsupdate using the DST library
 573       for its cryptographic operations, and may change in future
 574       releases.
 575     </p>
 576 </div>
 577 </div>
 578 <div class="navfooter">
 579 <hr>
 580 <table width="100%" summary="Navigation footer">
 581 <tr>
 582 <td width="40%" align="left">
 583 <a accesskey="p" href="man.named-journalprint.html">Prev</a> </td>
 584 <td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch10.html">Up</a></td>
 585 <td width="40%" align="right"> <a accesskey="n" href="man.rndc.html">Next</a>
 586 </td>
 587 </tr>
 588 <tr>
 589 <td width="40%" align="left" valign="top">
 590 <span class="application">named-journalprint</span> </td>
 591 <td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
 592 <td width="40%" align="right" valign="top"> <span class="application">rndc</span>
 593 </td>
 594 </tr>
 595 </table>
 596 </div>
 597 </body>
 598 </html>