Gecko [ nbspublicschool.com ]

Name	Size	Permission
sample	[ DIR ]	drwxr-xr-x
Bv9ARM.ch01.html	26.11 KB	-rw-r--r--
Bv9ARM.ch02.html	7.18 KB	-rw-r--r--
Bv9ARM.ch03.html	30.38 KB	-rw-r--r--
Bv9ARM.ch04.html	129.65 KB	-rw-r--r--
Bv9ARM.ch05.html	6.29 KB	-rw-r--r--
Bv9ARM.ch06.html	684.15 KB	-rw-r--r--
Bv9ARM.ch07.html	19.56 KB	-rw-r--r--
Bv9ARM.ch08.html	6.32 KB	-rw-r--r--
Bv9ARM.ch09.html	10.27 KB	-rw-r--r--
Bv9ARM.ch10.html	6.92 KB	-rw-r--r--
Bv9ARM.ch11.html	53.24 KB	-rw-r--r--
Bv9ARM.ch12.html	20.45 KB	-rw-r--r--
Bv9ARM.ch13.html	9.88 KB	-rw-r--r--
Bv9ARM.html	29.71 KB	-rw-r--r--
Bv9ARM.pdf	1.24 MB	-rw-r--r--
CHANGES	528.76 KB	-rw-r--r--
README	22.46 KB	-rw-r--r--
isc-logo.pdf	281.24 KB	-rw-r--r--
man.arpaname.html	3.01 KB	-rw-r--r--
man.ddns-confgen.html	9.49 KB	-rw-r--r--
man.delv.html	23.87 KB	-rw-r--r--
man.dig.html	40.63 KB	-rw-r--r--
man.dnssec-checkds.html	5.35 KB	-rw-r--r--
man.dnssec-coverage.html	11.35 KB	-rw-r--r--
man.dnssec-dsfromkey.html	9.68 KB	-rw-r--r--
man.dnssec-importkey.html	9.58 KB	-rw-r--r--
man.dnssec-keyfromlabel.html	19.12 KB	-rw-r--r--
man.dnssec-keygen.html	22.31 KB	-rw-r--r--
man.dnssec-keymgr.html	15.15 KB	-rw-r--r--
man.dnssec-revoke.html	5.62 KB	-rw-r--r--
man.dnssec-settime.html	14.55 KB	-rw-r--r--
man.dnssec-signzone.html	30.69 KB	-rw-r--r--
man.dnssec-verify.html	7.43 KB	-rw-r--r--
man.dnstap-read.html	4.39 KB	-rw-r--r--
man.genrandom.html	4.13 KB	-rw-r--r--
man.host.html	12.74 KB	-rw-r--r--
man.isc-hmac-fixup.html	4.6 KB	-rw-r--r--
man.lwresd.html	12.45 KB	-rw-r--r--
man.mdig.html	23.18 KB	-rw-r--r--
man.named-checkconf.html	6.77 KB	-rw-r--r--
man.named-checkzone.html	20.21 KB	-rw-r--r--
man.named-journalprint.html	4.2 KB	-rw-r--r--
man.named-nzd2nzf.html	3.86 KB	-rw-r--r--
man.named-rrchecker.html	4.21 KB	-rw-r--r--
man.named.conf.html	73.42 KB	-rw-r--r--
man.named.html	19.07 KB	-rw-r--r--
man.nsec3hash.html	4.17 KB	-rw-r--r--
man.nslookup.html	14.49 KB	-rw-r--r--
man.nsupdate.html	28.11 KB	-rw-r--r--
man.pkcs11-destroy.html	5.57 KB	-rw-r--r--
man.pkcs11-keygen.html	7.13 KB	-rw-r--r--
man.pkcs11-list.html	5.46 KB	-rw-r--r--
man.pkcs11-tokens.html	3.73 KB	-rw-r--r--
man.rndc-confgen.html	11.48 KB	-rw-r--r--
man.rndc.conf.html	10.17 KB	-rw-r--r--
man.rndc.html	39.89 KB	-rw-r--r--
named.conf.default	1.76 KB	-rw-r--r--
notes.html	7.31 KB	-rw-r--r--
notes.pdf	50.96 KB	-rw-r--r--

Code Editor : man.nsupdate.html

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">

<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
<title>nsupdate</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.78.1">
<link rel="home" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
<link rel="up" href="Bv9ARM.ch13.html" title="Manual pages">
<link rel="prev" href="man.named-rrchecker.html" title="named-rrchecker">
<link rel="next" href="man.rndc.html" title="rndc">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<div class="navheader">
<table width="100%" summary="Navigation header">
<tr><th colspan="3" align="center">nsupdate</th></tr>
<tr>
<td width="20%" align="left">
<a accesskey="p" href="man.named-rrchecker.html">Prev</a>�</td>
<th width="60%" align="center">Manual pages</th>
<td width="20%" align="right">�<a accesskey="n" href="man.rndc.html">Next</a>
</td>
</tr>
</table>
<hr>
</div>
<div class="refentry">
<a name="man.nsupdate"></a><div class="titlepage"></div>

<div class="refnamediv">
<h2>Name</h2>

 nsupdate
 &#8212; Dynamic DNS update utility
 
</div>

<div class="refsynopsisdiv">
<h2>Synopsis</h2>
 <div class="cmdsynopsis">
 <code class="command">nsupdate</code> 
 [<code class="option">-d</code>]
 [<code class="option">-D</code>]
 [<code class="option">-i</code>]
 [<code class="option">-L <code>level</code></code>]
 [
	[<code class="option">-g</code>]
	 | [<code class="option">-o</code>]
	 | [<code class="option">-l</code>]
	 | [<code class="option">-y <code>[hmac:]keyname:secret</code></code>]
	 | [<code class="option">-k <code>keyfile</code></code>]
 ]
 [<code class="option">-t <code>timeout</code></code>]
 [<code class="option">-u <code>udptimeout</code></code>]
 [<code class="option">-r <code>udpretries</code></code>]
 [<code class="option">-R <code>randomdev</code></code>]
 [<code class="option">-v</code>]
 [<code class="option">-T</code>]
 [<code class="option">-P</code>]
 [<code class="option">-V</code>]
 [filename]
 </div>
 </div>

<div class="refsection">
<a name="id-1.14.26.7"></a><h2>DESCRIPTION</h2>

nsupdate
 is used to submit Dynamic DNS Update requests as defined in RFC 2136
 to a name server.
 This allows resource records to be added or removed from a zone
 without manually editing the zone file.
 A single update request can contain requests to add or remove more than
 one
 resource record.
 
 
 Zones that are under dynamic control via
 nsupdate
 or a DHCP server should not be edited by hand.
 Manual edits could
 conflict with dynamic updates and cause data to be lost.
 
 
 The resource records that are dynamically added or removed with
 nsupdate
 have to be in the same zone.
 Requests are sent to the zone's master server.
 This is identified by the MNAME field of the zone's SOA record.
 
 
 Transaction signatures can be used to authenticate the Dynamic
 DNS updates. These use the TSIG resource record type described
 in RFC 2845 or the SIG(0) record described in RFC 2535 and
 RFC 2931 or GSS-TSIG as described in RFC 3645.
 
 
 TSIG relies on
 a shared secret that should only be known to
 nsupdate and the name server.
 For instance, suitable key and
 server statements would be added to
 <code class="filename">/etc/named.conf</code> so that the name server
 can associate the appropriate secret key and algorithm with
 the IP address of the client application that will be using
 TSIG authentication. You can use ddns-confgen
 to generate suitable configuration fragments.
 nsupdate
 uses the <code class="option">-y</code> or <code class="option">-k</code> options
 to provide the TSIG shared secret. These options are mutually exclusive.
 
 
 SIG(0) uses public key cryptography.
 To use a SIG(0) key, the public key must be stored in a KEY
 record in a zone served by the name server.
 
 
 GSS-TSIG uses Kerberos credentials. Standard GSS-TSIG mode
 is switched on with the <code class="option">-g</code> flag. A
 non-standards-compliant variant of GSS-TSIG used by Windows
 2000 can be switched on with the <code class="option">-o</code> flag.
 
 </div>

<div class="refsection">
<a name="id-1.14.26.8"></a><h2>OPTIONS</h2>

<div class="variablelist"><dl class="variablelist">
<dt>-d</dt>
<dd>
	 
	 Debug mode. This provides tracing information about the
	 update requests that are made and the replies received
	 from the name server.
	 
	</dd>
<dt>-D</dt>
<dd>
	 
	 Extra debug mode.
	 
	</dd>
<dt>-i</dt>
<dd>
	 
	 Force interactive mode, even when standard input is not a terminal.
	 
	</dd>
<dt>-k <code>keyfile</code></dt>
<dd>
	 
	 The file containing the TSIG authentication key.
	 Keyfiles may be in two formats: a single file containing
	 a <code class="filename">named.conf</code>-format key
	 statement, which may be generated automatically by
	 ddns-confgen, or a pair of files whose names are
	 of the format <code class="filename">K{name}.+157.+{random}.key</code> and
	 <code class="filename">K{name}.+157.+{random}.private</code>, which can be
	 generated by dnssec-keygen.
	 The <code class="option">-k</code> may also be used to specify a SIG(0) key used
	 to authenticate Dynamic DNS update requests. In this case, the key
	 specified is not an HMAC-MD5 key.
	 
	</dd>
<dt>-l</dt>
<dd>
	 
	 Local-host only mode. This sets the server address to
	 localhost (disabling the server so that the server
	 address cannot be overridden). Connections to the local server will
	 use a TSIG key found in <code class="filename">/var/run/named/session.key</code>,
	 which is automatically generated by named if any
	 local master zone has set update-policy to
	 local. The location of this key file can be
	 overridden with the <code class="option">-k</code> option.
	 
	</dd>
<dt>-L <code>level</code></dt>
<dd>
	 
	 Set the logging debug level. If zero, logging is disabled.
	 
	</dd>
<dt>-p <code>port</code></dt>
<dd>
	 
	 Set the port to use for connections to a name server. The
	 default is 53.
	 
	</dd>
<dt>-P</dt>
<dd>
	 
	 Print the list of private BIND-specific resource record
	 types whose format is understood
	 by nsupdate. See also
	 the <code class="option">-T</code> option.
	 
	</dd>
<dt>-r <code>udpretries</code></dt>
<dd>
	 
	 The number of UDP retries. The default is 3. If zero, only
	 one update request will be made.
	 
	</dd>
<dt>-R <code>randomdev</code></dt>
<dd>
	
	 Where to obtain randomness. If the operating system
	 does not provide a <code class="filename">/dev/random</code> or
	 equivalent device, the default source of randomness is keyboard
	 input. <code class="filename">randomdev</code> specifies the name of
	 a character device or file containing random data to be used
	 instead of the default. The special value
	 <code class="filename">keyboard</code> indicates that keyboard input
	 should be used. This option may be specified multiple times.
	
	</dd>
<dt>-t <code>timeout</code></dt>
<dd>
	 
	 The maximum time an update request can take before it is
	 aborted. The default is 300 seconds. Zero can be used to
	 disable the timeout.
	 
	</dd>
<dt>-T</dt>
<dd>
	 
	 Print the list of IANA standard resource record types
	 whose format is understood by nsupdate.
	 nsupdate will exit after the lists are
	 printed. The <code class="option">-T</code> option can be combined
	 with the <code class="option">-P</code> option.
	 
	 
	 Other types can be entered using "TYPEXXXXX" where "XXXXX" is the
	 decimal value of the type with no leading zeros. The rdata,
	 if present, will be parsed using the UNKNOWN rdata format,
	 (&lt;backslash&gt; &lt;hash&gt; &lt;space&gt; &lt;length&gt;
	 &lt;space&gt; &lt;hexstring&gt;).
	 
	</dd>
<dt>-u <code>udptimeout</code></dt>
<dd>
	 
	 The UDP retry interval. The default is 3 seconds. If zero,
	 the interval will be computed from the timeout interval and
	 number of UDP retries.
	 
	</dd>
<dt>-v</dt>
<dd>
	 
	 Use TCP even for small update requests.
	 By default, nsupdate
	 uses UDP to send update requests to the name server unless they are too
	 large to fit in a UDP request in which case TCP will be used.
	 TCP may be preferable when a batch of update requests is made.
	 
	</dd>
<dt>-V</dt>
<dd>
	 
	 Print the version number and exit.
	 
	</dd>
<dt>-y <code>[hmac:]keyname:secret</code></dt>
<dd>
	 
	 Literal TSIG authentication key.
	 <code>keyname</code> is the name of the key, and
	 <code>secret</code> is the base64 encoded shared secret.
	 <code>hmac</code> is the name of the key algorithm;
	 valid choices are <code class="literal">hmac-md5</code>,
	 <code class="literal">hmac-sha1</code>, <code class="literal">hmac-sha224</code>,
	 <code class="literal">hmac-sha256</code>, <code class="literal">hmac-sha384</code>, or
	 <code class="literal">hmac-sha512</code>. If <code>hmac</code>
	 is not specified, the default is <code class="literal">hmac-md5</code>
	 or if MD5 was disabled <code class="literal">hmac-sha256</code>.
	 
	 
	 NOTE: Use of the <code class="option">-y</code> option is discouraged because the
	 shared secret is supplied as a command line argument in clear text.
	 This may be visible in the output from
	 
	 ps(1)
	 
	 or in a history file maintained by the user's shell.
	 
	</dd>
</dl></div>
 </div>

<div class="refsection">
<a name="id-1.14.26.9"></a><h2>INPUT FORMAT</h2>

nsupdate
 reads input from
 <code>filename</code>
 or standard input.
 Each command is supplied on exactly one line of input.
 Some commands are for administrative purposes.
 The others are either update instructions or prerequisite checks on the
 contents of the zone.
 These checks set conditions that some name or set of
 resource records (RRset) either exists or is absent from the zone.
 These conditions must be met if the entire update request is to succeed.
 Updates will be rejected if the tests for the prerequisite conditions
 fail.
 
 
 Every update request consists of zero or more prerequisites
 and zero or more updates.
 This allows a suitably authenticated update request to proceed if some
 specified resource records are present or missing from the zone.
 A blank input line (or the send command)
 causes the
 accumulated commands to be sent as one Dynamic DNS update request to the
 name server.
 
 
 The command formats and their meaning are as follows:
 
<div class="variablelist"><dl class="variablelist">
<dt>
	 server
	 {servername}
	 [port]
	 </dt>
<dd>
	 
	 Sends all dynamic update requests to the name server
	 <code>servername</code>.
	 When no server statement is provided,
	 nsupdate
	 will send updates to the master server of the correct zone.
	 The MNAME field of that zone's SOA record will identify the
	 master
	 server for that zone.
	 <code>port</code>
	 is the port number on
	 <code>servername</code>
	 where the dynamic update requests get sent.
	 If no port number is specified, the default DNS port number of
	 53 is
	 used.
	 
	 </dd>
<dt>
	 local
	 {address}
	 [port]
	 </dt>
<dd>
	 
	 Sends all dynamic update requests using the local
	 <code>address</code>.

When no local statement is provided,
	 nsupdate
	 will send updates using an address and port chosen by the
	 system.
	 <code>port</code>
	 can additionally be used to make requests come from a specific
	 port.
	 If no port number is specified, the system will assign one.
	 
	 </dd>
<dt>
	 zone
	 {zonename}
	 </dt>
<dd>
	 
	 Specifies that all updates are to be made to the zone
	 <code>zonename</code>.
	 If no
	 <code>zone</code>
	 statement is provided,
	 nsupdate
	 will attempt determine the correct zone to update based on the
	 rest of the input.
	 
	 </dd>
<dt>
	 class
	 {classname}
	 </dt>
<dd>
	 
	 Specify the default class.
	 If no <code>class</code> is specified, the
	 default class is
	 <code>IN</code>.
	 
	 </dd>
<dt>
	 ttl
	 {seconds}
	 </dt>
<dd>
	 
	 Specify the default time to live for records to be added.
	 The value <code>none</code> will clear the default
	 ttl.
	 
	 </dd>
<dt>
	 key
	 [hmac:] {keyname}
	 {secret}
	 </dt>
<dd>
	 
	 Specifies that all updates are to be TSIG-signed using the
	 <code>keyname</code> <code>secret</code> pair.
	 If <code>hmac</code> is specified, then it sets the
	 signing algorithm in use; the default is
	 <code class="literal">hmac-md5</code> or if MD5 was disabled
	 <code class="literal">hmac-sha256</code>. The key
	 command overrides any key specified on the command line via
	 <code class="option">-y</code> or <code class="option">-k</code>.
	 
	 </dd>
<dt>
	 gsstsig
	 </dt>
<dd>
	 
	 Use GSS-TSIG to sign the updated. This is equivalent to
	 specifying <code class="option">-g</code> on the command line.
	 
	 </dd>
<dt>
	 oldgsstsig
	 </dt>
<dd>
	 
	 Use the Windows 2000 version of GSS-TSIG to sign the updated.
	 This is equivalent to specifying <code class="option">-o</code> on the
	 command line.
	 
	 </dd>
<dt>
	 realm
	 {[realm_name]}
	 </dt>
<dd>
	 
	 When using GSS-TSIG use <code>realm_name</code> rather
	 than the default realm in <code class="filename">krb5.conf</code>. If no
	 realm is specified the saved realm is cleared.
	 
	 </dd>
<dt>
	 check-names
	 {[yes_or_no]}
	 </dt>
<dd>
	 
	 Turn on or off check-names processing on records to
	 be added. Check-names has no effect on prerequisites
	 or records to be deleted. By default check-names
	 processing is on. If check-names processing fails
	 the record will not be added to the UPDATE message.
	 
	 </dd>
<dt>
	 [prereq] nxdomain
	 {domain-name}
	 </dt>
<dd>
	 
	 Requires that no resource record of any type exists with name
	 <code>domain-name</code>.
	 
	 </dd>
<dt>
	 [prereq] yxdomain
	 {domain-name}
	 </dt>
<dd>
	 
	 Requires that
	 <code>domain-name</code>
	 exists (has as at least one resource record, of any type).
	 
	 </dd>
<dt>
	 [prereq] nxrrset
	 {domain-name}
	 [class]
	 {type}
	 </dt>
<dd>
	 
	 Requires that no resource record exists of the specified
	 <code>type</code>,
	 <code>class</code>
	 and
	 <code>domain-name</code>.
	 If
	 <code>class</code>
	 is omitted, IN (internet) is assumed.
	 
	 </dd>
<dt>
	 [prereq] yxrrset
	 {domain-name}
	 [class]
	 {type}
	 </dt>
<dd>
	 
	 This requires that a resource record of the specified
	 <code>type</code>,
	 <code>class</code>
	 and
	 <code>domain-name</code>
	 must exist.
	 If
	 <code>class</code>
	 is omitted, IN (internet) is assumed.
	 
	 </dd>
<dt>
	 [prereq] yxrrset
	 {domain-name}
	 [class]
	 {type}
	 {data...}
	 </dt>
<dd>
	 
	 The
	 <code>data</code>
	 from each set of prerequisites of this form
	 sharing a common
	 <code>type</code>,
	 <code>class</code>,
	 and
	 <code>domain-name</code>
	 are combined to form a set of RRs. This set of RRs must
	 exactly match the set of RRs existing in the zone at the
	 given
	 <code>type</code>,
	 <code>class</code>,
	 and
	 <code>domain-name</code>.
	 The
	 <code>data</code>
	 are written in the standard text representation of the resource
	 record's
	 RDATA.
	 
	 </dd>
<dt>
	 [update] del[ete]
	 {domain-name}
	 [ttl]
	 [class]
	 [type [data...]]
	 </dt>
<dd>
	 
	 Deletes any resource records named
	 <code>domain-name</code>.
	 If
	 <code>type</code>
	 and
	 <code>data</code>
	 is provided, only matching resource records will be removed.
	 The internet class is assumed if
	 <code>class</code>
	 is not supplied. The
	 <code>ttl</code>
	 is ignored, and is only allowed for compatibility.
	 
	 </dd>
<dt>
	 [update] add
	 {domain-name}
	 {ttl}
	 [class]
	 {type}
	 {data...}
	 </dt>
<dd>
	 
	 Adds a new resource record with the specified
	 <code>ttl</code>,
	 <code>class</code>
	 and
	 <code>data</code>.
	 
	 </dd>
<dt>
	 show
	 </dt>
<dd>
	 
	 Displays the current message, containing all of the
	 prerequisites and
	 updates specified since the last send.
	 
	 </dd>
<dt>
	 send
	 </dt>
<dd>
	 
	 Sends the current message. This is equivalent to entering a
	 blank line.
	 
	 </dd>
<dt>
	 answer
	 </dt>
<dd>
	 
	 Displays the answer.
	 
	 </dd>
<dt>
	 debug
	 </dt>
<dd>
	 
	 Turn on debugging.
	 
	 </dd>
<dt>
	 version
	 </dt>
<dd>
	 
	 Print version number.
	 
	 </dd>
<dt>
	 help
	 </dt>
<dd>
	 
	 Print a list of commands.
	 
	 </dd>
</dl></div>

Lines beginning with a semicolon are comments and are ignored.

</div>

<div class="refsection">
<a name="id-1.14.26.10"></a><h2>EXAMPLES</h2>

The examples below show how
 nsupdate
 could be used to insert and delete resource records from the
 example.com
 zone.
 Notice that the input in each example contains a trailing blank line so
 that
 a group of commands are sent as one dynamic update request to the
 master name server for
 example.com.

<pre class="programlisting">
# nsupdate
&gt; update delete oldhost.example.com A
&gt; update add newhost.example.com 86400 A 172.16.1.1
&gt; send
</pre>

 
 
 Any A records for
 oldhost.example.com
 are deleted.
 And an A record for
 newhost.example.com
 with IP address 172.16.1.1 is added.
 The newly-added record has a 1 day TTL (86400 seconds).
 
<pre class="programlisting">
# nsupdate
&gt; prereq nxdomain nickname.example.com
&gt; update add nickname.example.com 86400 CNAME somehost.example.com
&gt; send
</pre>

 
 
 The prerequisite condition gets the name server to check that there
 are no resource records of any type for
 nickname.example.com.

If there are, the update request fails.
 If this name does not exist, a CNAME for it is added.
 This ensures that when the CNAME is added, it cannot conflict with the
 long-standing rule in RFC 1034 that a name must not exist as any other
 record type if it exists as a CNAME.
 (The rule has been updated for DNSSEC in RFC 2535 to allow CNAMEs to have
 RRSIG, DNSKEY and NSEC records.)
 
 </div>

<div class="refsection">
<a name="id-1.14.26.11"></a><h2>FILES</h2>

<div class="variablelist"><dl class="variablelist">
<dt><code class="constant">/etc/resolv.conf</code></dt>
<dd>
	 
	 used to identify default name server
	 
	</dd>
<dt><code class="constant">/var/run/named/session.key</code></dt>
<dd>
	 
	 sets the default TSIG key for use in local-only mode
	 
	</dd>
<dt><code class="constant">K{name}.+157.+{random}.key</code></dt>
<dd>
	 
	 base-64 encoding of HMAC-MD5 key created by
	 
	 dnssec-keygen(8)
	 .
	 
	</dd>
<dt><code class="constant">K{name}.+157.+{random}.private</code></dt>
<dd>
	 
	 base-64 encoding of HMAC-MD5 key created by
	 
	 dnssec-keygen(8)
	 .
	 
	</dd>
</dl></div>
 </div>

RFC 2136,
 RFC 3007,
 RFC 2104,
 RFC 2845,
 RFC 1034,
 RFC 2535,
 RFC 2931,
 
	named(8)
 ,
 
	ddns-confgen(8)
 ,
 
	dnssec-keygen(8)
 .
 
 </div>

The TSIG key is redundantly stored in two separate files.
 This is a consequence of nsupdate using the DST library
 for its cryptographic operations, and may change in future
 releases.
 
 </div>

</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="man.named-rrchecker.html">Prev</a>�</td>
<td width="20%" align="center"><a accesskey="u" href="Bv9ARM.ch13.html">Up</a></td>
<td width="40%" align="right">�<a accesskey="n" href="man.rndc.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">
named-rrchecker�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�rndc
</td>
</tr>
</table>
</div>
BIND 9.11.4-P2 (Extended Support Version)
</body>
</html>

${this.title}

Code Editor : man.nsupdate.html