external/bsd/bind/dist/bin/nsupdate/nsupdate.html

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