mirror of
https://github.com/isc-projects/bind9.git
synced 2026-06-11 04:30:00 -04:00
regen
This commit is contained in:
parent
49810c555f
commit
b05bdb520d
18 changed files with 269 additions and 269 deletions
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch01.html,v 1.28 2006/05/08 15:46:26 marka Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch01.html,v 1.29 2006/06/08 02:44:04 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -482,7 +482,7 @@
|
|||
</p>
|
||||
<p>
|
||||
The length of time for which a record may be retained in
|
||||
in the cache of a caching name server is controlled by the
|
||||
the cache of a caching name server is controlled by the
|
||||
Time To Live (TTL) field associated with each resource record.
|
||||
</p>
|
||||
<div class="sect3" lang="en">
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch03.html,v 1.55 2006/05/17 02:39:16 marka Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch03.html,v 1.56 2006/06/08 02:44:04 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -463,7 +463,7 @@ zone "eng.example.com" {
|
|||
[<span class="optional"><em class="replaceable"><code>view</code></em></span>]</span>]</span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Suspend updates to a dynamic zone. If no zone is
|
||||
specified
|
||||
specified,
|
||||
then all zones are suspended. This allows manual
|
||||
edits to be made to a zone normally updated by dynamic
|
||||
update. It
|
||||
|
|
@ -480,7 +480,7 @@ zone "eng.example.com" {
|
|||
<dd><p>
|
||||
Enable updates to a frozen dynamic zone. If no zone
|
||||
is
|
||||
specified then all frozen zones are enabled. This
|
||||
specified, then all frozen zones are enabled. This
|
||||
causes
|
||||
the server to reload the zone from disk, and
|
||||
re-enables dynamic updates
|
||||
|
|
@ -524,10 +524,10 @@ zone "eng.example.com" {
|
|||
[<span class="optional">-all|-cache|-zone</span>]
|
||||
[<span class="optional"><em class="replaceable"><code>view ...</code></em></span>]</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Dump the server's caches (default) and / or zones to
|
||||
Dump the server's caches (default) and/or zones to
|
||||
the
|
||||
dump file for the specified views. If no view is
|
||||
specified all
|
||||
specified, all
|
||||
views are dumped.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>stop [<span class="optional">-p</span>]</code></strong></span></dt>
|
||||
|
|
@ -573,9 +573,9 @@ zone "eng.example.com" {
|
|||
<dt><span class="term"><strong class="userinput"><code>status</code></strong></span></dt>
|
||||
<dd><p>
|
||||
Display status of the server.
|
||||
Note the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone
|
||||
Note that the number of zones includes the internal <span><strong class="command">bind/CH</strong></span> zone
|
||||
and the default <span><strong class="command">./IN</strong></span>
|
||||
hint zone if there is not a
|
||||
hint zone if there is not an
|
||||
explicit root zone configured.
|
||||
</p></dd>
|
||||
<dt><span class="term"><strong class="userinput"><code>recursing</code></strong></span></dt>
|
||||
|
|
@ -647,7 +647,7 @@ zone "eng.example.com" {
|
|||
<span><strong class="command">server</strong></span> statement.
|
||||
</p>
|
||||
<p>
|
||||
The <span><strong class="command">key</strong></span> statement defines an
|
||||
The <span><strong class="command">key</strong></span> statement defines a
|
||||
key to be used
|
||||
by <span><strong class="command">rndc</strong></span> when authenticating
|
||||
with
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch04.html,v 1.67 2006/05/17 02:39:16 marka Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch04.html,v 1.68 2006/06/08 02:44:04 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -158,7 +158,7 @@
|
|||
<p>
|
||||
The zone files of dynamic zones cannot normally be edited by
|
||||
hand because they are not guaranteed to contain the most recent
|
||||
dynamic changes - those are only in the journal file.
|
||||
dynamic changes — those are only in the journal file.
|
||||
The only way to ensure that the zone file of a dynamic zone
|
||||
is up to date is to run <span><strong class="command">rndc stop</strong></span>.
|
||||
</p>
|
||||
|
|
@ -328,7 +328,7 @@
|
|||
<code class="literal">site2.internal</code> domains.
|
||||
</li>
|
||||
<li>Look up any hostnames on the Internet.</li>
|
||||
<li>Exchange mail with internal AND external people.</li>
|
||||
<li>Exchange mail with both internal and external people.</li>
|
||||
</ul></div>
|
||||
<p>
|
||||
Hosts on the Internet will be able to:
|
||||
|
|
@ -489,11 +489,11 @@ nameserver 172.16.72.4
|
|||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2551833"></a>Automatic Generation</h4></div></div></div>
|
||||
<p>
|
||||
The following command will generate a 128 bit (16 byte) HMAC-MD5
|
||||
The following command will generate a 128-bit (16 byte) HMAC-MD5
|
||||
key as described above. Longer keys are better, but shorter keys
|
||||
are easier to read. Note that the maximum key length is 512 bits;
|
||||
keys longer than that will be digested with MD5 to produce a 128
|
||||
bit key.
|
||||
keys longer than that will be digested with MD5 to produce a
|
||||
128-bit key.
|
||||
</p>
|
||||
<p>
|
||||
<strong class="userinput"><code>dnssec-keygen -a hmac-md5 -b 128 -n HOST host1-host2.</code></strong>
|
||||
|
|
@ -764,7 +764,7 @@ allow-update { key host1-host2. ;};
|
|||
the only one is RSASHA1.
|
||||
</p>
|
||||
<p>
|
||||
The following command will generate a 768 bit RSASHA1 key for
|
||||
The following command will generate a 768-bit RSASHA1 key for
|
||||
the <code class="filename">child.example</code> zone:
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -811,7 +811,7 @@ allow-update { key host1-host2. ;};
|
|||
records for the zone, as well as <code class="literal">DS</code>
|
||||
for
|
||||
the child zones if <code class="literal">'-d'</code> is specified.
|
||||
If <code class="literal">'-d'</code> is not specified then
|
||||
If <code class="literal">'-d'</code> is not specified, then
|
||||
DS RRsets for
|
||||
the secure child zones need to be added manually.
|
||||
</p>
|
||||
|
|
@ -845,7 +845,7 @@ allow-update { key host1-host2. ;};
|
|||
<a name="id2552595"></a>Configuring Servers</h3></div></div></div>
|
||||
<p>
|
||||
To enable <span><strong class="command">named</strong></span> to respond appropriately
|
||||
to DNS requests from DNSSEC aware clients
|
||||
to DNS requests from DNSSEC aware clients,
|
||||
<span><strong class="command">dnssec-enable</strong></span> must be set to yes.
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -895,7 +895,7 @@ trusted-keys {
|
|||
iA21AfUVe7u99WzTLzY3qlxDhxYQQ20FQ97S+LKUTpQcq27R7AT3/V5hRQxScI
|
||||
Nqwcz4jYqZD2fQdgxbcDTClU0CRBdiieyLMNzXG3";
|
||||
|
||||
/* Key for out organizations forward zone */
|
||||
/* Key for our organization's forward zone */
|
||||
example.com. 257 3 5 "AwEAAaxPMcR2x0HbQV4WeZB6oEDX+r0QM65KbhTjrW1ZaARmPhEZZe
|
||||
3Y9ifgEuq7vZ/zGZUdEGNWy+JZzus0lUptwgjGwhUS1558Hb4JKUbb
|
||||
OTcM8pwXlj0EiX3oDFVmjHO444gLkBO UKUf/mC7HvfwYH/Be22GnC
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch06.html,v 1.138 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch06.html,v 1.139 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -55,7 +55,7 @@
|
|||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2554882"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#acl"><span><strong class="command">acl</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2555072"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2555140"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2555432"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt>
|
||||
|
|
@ -77,23 +77,23 @@
|
|||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2565882"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2565931"><span><strong class="command">trusted-keys</strong></span> Statement Definition
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2565889"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2565938"><span><strong class="command">trusted-keys</strong></span> Statement Definition
|
||||
and Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span><strong class="command">view</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2566011"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2566018"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span>
|
||||
Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2567457"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2567395"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2569739">Zone File</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2569676">Zone File</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2571556">Discussion of MX Records</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2571629">Discussion of MX Records</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572244">Inverse Mapping in IPv4</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572371">Other Zone File Directives</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572696"><span class="acronym">BIND</span> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572317">Inverse Mapping in IPv4</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572444">Other Zone File Directives</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572701"><span class="acronym">BIND</span> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
|
||||
</dl></dd>
|
||||
</dl>
|
||||
|
|
@ -165,7 +165,7 @@
|
|||
<td>
|
||||
<p>
|
||||
A named list of one or more <code class="varname">ip_addr</code>
|
||||
with optional <code class="varname">key_id</code> and / or
|
||||
with optional <code class="varname">key_id</code> and/or
|
||||
<code class="varname">ip_port</code>.
|
||||
A <code class="varname">masters_list</code> may include other
|
||||
<code class="varname">masters_lists</code>.
|
||||
|
|
@ -270,7 +270,7 @@
|
|||
through 65535, with values
|
||||
below 1024 typically restricted to use by processes running
|
||||
as root.
|
||||
In some cases an asterisk (`*') character can be used as a
|
||||
In some cases, an asterisk (`*') character can be used as a
|
||||
placeholder to
|
||||
select a random high-numbered port.
|
||||
</p>
|
||||
|
|
@ -332,7 +332,7 @@
|
|||
</td>
|
||||
<td>
|
||||
<p>
|
||||
A non-negative 32 bit integer
|
||||
A non-negative 32-bit integer
|
||||
(i.e., a number between 0 and 4294967295, inclusive).
|
||||
Its acceptable value might further
|
||||
be limited by the context in which it is used.
|
||||
|
|
@ -857,7 +857,7 @@
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2555072"></a><span><strong class="command">controls</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="id2555140"></a><span><strong class="command">controls</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting"><span><strong class="command">controls</strong></span> {
|
||||
[ inet ( ip_addr | * ) [ port ip_port ] allow { <em class="replaceable"><code> address_match_list </code></em> }
|
||||
keys { <em class="replaceable"><code>key_list</code></em> }; ]
|
||||
|
|
@ -965,9 +965,9 @@
|
|||
<span><strong class="command">named</strong></span> is running as) can access it.
|
||||
If you
|
||||
desire greater flexibility in allowing other users to access
|
||||
<span><strong class="command">rndc</strong></span> commands then you need to create
|
||||
an
|
||||
<code class="filename">rndc.conf</code> and make it group
|
||||
<span><strong class="command">rndc</strong></span> commands, then you need to create
|
||||
a
|
||||
<code class="filename">rndc.conf</code> file and make it group
|
||||
readable by a group
|
||||
that contains the users who should have access.
|
||||
</p>
|
||||
|
|
@ -1147,9 +1147,9 @@
|
|||
option, then
|
||||
<span><strong class="command">named</strong></span> will retain that many backup
|
||||
versions of the file by
|
||||
renaming them when opening. For example, if you choose to keep 3
|
||||
old versions
|
||||
of the file <code class="filename">lamers.log</code> then just
|
||||
renaming them when opening. For example, if you choose to keep
|
||||
three old versions
|
||||
of the file <code class="filename">lamers.log</code>, then just
|
||||
before it is opened
|
||||
<code class="filename">lamers.log.1</code> is renamed to
|
||||
<code class="filename">lamers.log.2</code>, <code class="filename">lamers.log.0</code> is renamed
|
||||
|
|
@ -1563,7 +1563,7 @@ category notify { null; };
|
|||
</p>
|
||||
<p>
|
||||
The query log entry reports the client's IP address and
|
||||
port number. The
|
||||
port number, and the
|
||||
query name, class and type. It also reports whether the
|
||||
Recursion Desired
|
||||
flag was set (+ if set, - if not set), EDNS was in use
|
||||
|
|
@ -2006,7 +2006,7 @@ digits</code>" + "<code class="varname">tkey-domain</code>". In most cases,
|
|||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">preferred-glue</strong></span></span></dt>
|
||||
<dd><p>
|
||||
If specified the listed type (A or AAAA) will be emitted
|
||||
If specified, the listed type (A or AAAA) will be emitted
|
||||
before other glue
|
||||
in the additional section of a query response.
|
||||
The default is not to preference any type (NONE).
|
||||
|
|
@ -2019,7 +2019,7 @@ digits</code>" + "<code class="varname">tkey-domain</code>". In most cases,
|
|||
exclude list.
|
||||
</p>
|
||||
<p>
|
||||
Note some TLDs are NOT delegation only (e.g. "DE", "LV", "US"
|
||||
Note some TLDs are not delegation only (e.g. "DE", "LV", "US"
|
||||
and "MUSEUM").
|
||||
</p>
|
||||
<pre class="programlisting">
|
||||
|
|
@ -2038,7 +2038,7 @@ options {
|
|||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">dnssec-lookaside</strong></span></span></dt>
|
||||
<dd><p>
|
||||
When set <span><strong class="command">dnssec-lookaside</strong></span>
|
||||
When set, <span><strong class="command">dnssec-lookaside</strong></span>
|
||||
provides the
|
||||
validator with an alternate method to validate DNSKEY records
|
||||
at the
|
||||
|
|
@ -2056,12 +2056,12 @@ options {
|
|||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">dnssec-must-be-secure</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Specify hierarchies which must / may not be secure (signed and
|
||||
Specify hierarchies which must be or may not be secure (signed and
|
||||
validated).
|
||||
If <strong class="userinput"><code>yes</code></strong> then named will only accept
|
||||
If <strong class="userinput"><code>yes</code></strong>, then named will only accept
|
||||
answers if they
|
||||
are secure.
|
||||
If <strong class="userinput"><code>no</code></strong> then normal dnssec validation
|
||||
If <strong class="userinput"><code>no</code></strong>, then normal dnssec validation
|
||||
applies
|
||||
allowing for insecure answers to be accepted.
|
||||
The specified domain must be under a <span><strong class="command">trusted-key</strong></span> or
|
||||
|
|
@ -2097,7 +2097,7 @@ options {
|
|||
If <strong class="userinput"><code>yes</code></strong>, then the
|
||||
server treats all zones as if they are doing zone transfers
|
||||
across
|
||||
a dial on demand dialup link, which can be brought up by
|
||||
a dial-on-demand dialup link, which can be brought up by
|
||||
traffic
|
||||
originating from this server. This has different effects
|
||||
according
|
||||
|
|
@ -2116,7 +2116,7 @@ options {
|
|||
option.
|
||||
</p>
|
||||
<p>
|
||||
If the zone is a master zone then the server will send out a
|
||||
If the zone is a master zone, then the server will send out a
|
||||
NOTIFY
|
||||
request to all the slaves (default). This should trigger the
|
||||
zone serial
|
||||
|
|
@ -2600,7 +2600,7 @@ options {
|
|||
<dt><span class="term"><span><strong class="command">ixfr-from-differences</strong></span></span></dt>
|
||||
<dd>
|
||||
<p>
|
||||
When 'yes' and the server loads a new version of a master
|
||||
When <strong class="userinput"><code>yes</code></strong> and the server loads a new version of a master
|
||||
zone from its zone file or receives a new version of a slave
|
||||
file by a non-incremental zone transfer, it will compare
|
||||
the new version to the previous one and calculate a set
|
||||
|
|
@ -2633,7 +2633,7 @@ options {
|
|||
<dd><p>
|
||||
This should be set when you have multiple masters for a zone
|
||||
and the
|
||||
addresses refer to different machines. If 'yes' named will
|
||||
addresses refer to different machines. If <strong class="userinput"><code>yes</code></strong>, named will
|
||||
not log
|
||||
when the serial number on the master is less than what named
|
||||
currently
|
||||
|
|
@ -2641,7 +2641,7 @@ options {
|
|||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">dnssec-enable</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Enable DNSSEC support in named. Unless set to <strong class="userinput"><code>yes</code></strong>
|
||||
Enable DNSSEC support in named. Unless set to <strong class="userinput"><code>yes</code></strong>,
|
||||
named behaves as if it does not support DNSSEC.
|
||||
The default is <strong class="userinput"><code>yes</code></strong>.
|
||||
</p></dd>
|
||||
|
|
@ -2654,14 +2654,14 @@ options {
|
|||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">dnssec-accept-expired</strong></span></span></dt>
|
||||
<dd><p>
|
||||
When verifying DNSSEC signatures accept expired signatures.
|
||||
Accept expired signatures when verifying DNSSEC signatures.
|
||||
The default is <strong class="userinput"><code>no</code></strong>.
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">querylog</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Specify whether query logging should be started when named
|
||||
start.
|
||||
If <span><strong class="command">querylog</strong></span> is not specified
|
||||
starts.
|
||||
If <span><strong class="command">querylog</strong></span> is not specified,
|
||||
then the query logging
|
||||
is determined by the presence of the logging category <span><strong class="command">queries</strong></span>.
|
||||
</p></dd>
|
||||
|
|
@ -2677,11 +2677,11 @@ options {
|
|||
<span><strong class="command">master</strong></span> zones the default is <span><strong class="command">fail</strong></span>.
|
||||
For <span><strong class="command">slave</strong></span> zones the default
|
||||
is <span><strong class="command">warn</strong></span>.
|
||||
For answer received from the network (<span><strong class="command">response</strong></span>)
|
||||
For answers received from the network (<span><strong class="command">response</strong></span>)
|
||||
the default is <span><strong class="command">ignore</strong></span>.
|
||||
</p>
|
||||
<p>
|
||||
The rules for legal hostnames or mail domains are derived
|
||||
The rules for legal hostnames and mail domains are derived
|
||||
from RFC 952 and RFC 821 as modified by RFC 1123.
|
||||
</p>
|
||||
<p><span><strong class="command">check-names</strong></span>
|
||||
|
|
@ -2737,7 +2737,7 @@ options {
|
|||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">check-sibling</strong></span></span></dt>
|
||||
<dd><p>
|
||||
When performing integrity checks also check that
|
||||
When performing integrity checks, also check that
|
||||
sibling glue exists. The default is <span><strong class="command">yes</strong></span>.
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">zero-no-soa-ttl</strong></span></span></dt>
|
||||
|
|
@ -2772,7 +2772,7 @@ options {
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2561272"></a>Forwarding</h4></div></div></div>
|
||||
<a name="id2561278"></a>Forwarding</h4></div></div></div>
|
||||
<p>
|
||||
The forwarding facility can be used to create a large site-wide
|
||||
cache on a few servers, reducing traffic over links to external
|
||||
|
|
@ -2789,8 +2789,8 @@ options {
|
|||
This option is only meaningful if the
|
||||
forwarders list is not empty. A value of <code class="varname">first</code>,
|
||||
the default, causes the server to query the forwarders
|
||||
first, and
|
||||
if that doesn't answer the question the server will then
|
||||
first — and
|
||||
if that doesn't answer the question, the server will then
|
||||
look for
|
||||
the answer itself. If <code class="varname">only</code> is
|
||||
specified, the
|
||||
|
|
@ -2816,7 +2816,7 @@ options {
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2561331"></a>Dual-stack Servers</h4></div></div></div>
|
||||
<a name="id2561337"></a>Dual-stack Servers</h4></div></div></div>
|
||||
<p>
|
||||
Dual-stack servers are used as servers of last resort to work
|
||||
around
|
||||
|
|
@ -2828,11 +2828,11 @@ options {
|
|||
<dt><span class="term"><span><strong class="command">dual-stack-servers</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Specifies host names or addresses of machines with access to
|
||||
both IPv4 and IPv6 transports. If a hostname is used the
|
||||
both IPv4 and IPv6 transports. If a hostname is used, the
|
||||
server must be able
|
||||
to resolve the name using only the transport it has. If the
|
||||
machine is dual
|
||||
stacked then the <span><strong class="command">dual-stack-servers</strong></span> have no effect unless
|
||||
stacked, then the <span><strong class="command">dual-stack-servers</strong></span> have no effect unless
|
||||
access to a transport has been disabled on the command line
|
||||
(e.g. <span><strong class="command">named -4</strong></span>).
|
||||
</p></dd>
|
||||
|
|
@ -2976,7 +2976,7 @@ options {
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2561670"></a>Interfaces</h4></div></div></div>
|
||||
<a name="id2561676"></a>Interfaces</h4></div></div></div>
|
||||
<p>
|
||||
The interfaces and ports that the server will answer queries
|
||||
from may be specified using the <span><strong class="command">listen-on</strong></span> option. <span><strong class="command">listen-on</strong></span> takes
|
||||
|
|
@ -3056,20 +3056,20 @@ listen-on-v6 port 1234 { !2001:db8::/32; any; };
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2561827"></a>Query Address</h4></div></div></div>
|
||||
<a name="id2561765"></a>Query Address</h4></div></div></div>
|
||||
<p>
|
||||
If the server doesn't know the answer to a question, it will
|
||||
query other name servers. <span><strong class="command">query-source</strong></span> specifies
|
||||
the address and port used for such queries. For queries sent over
|
||||
IPv6, there is a separate <span><strong class="command">query-source-v6</strong></span> option.
|
||||
If <span><strong class="command">address</strong></span> is <span><strong class="command">*</strong></span> or is omitted,
|
||||
If <span><strong class="command">address</strong></span> is <span><strong class="command">*</strong></span> (asterisk) or is omitted,
|
||||
a wildcard IP address (<span><strong class="command">INADDR_ANY</strong></span>)
|
||||
will be used.
|
||||
If <span><strong class="command">port</strong></span> is <span><strong class="command">*</strong></span> or is omitted,
|
||||
a random unprivileged port will be used, <span><strong class="command">avoid-v4-udp-ports</strong></span>
|
||||
and <span><strong class="command">avoid-v6-udp-ports</strong></span> can be used
|
||||
a random unprivileged port will be used. The <span><strong class="command">avoid-v4-udp-ports</strong></span>
|
||||
and <span><strong class="command">avoid-v6-udp-ports</strong></span> options can be used
|
||||
to prevent named
|
||||
from selecting certain ports. The defaults are
|
||||
from selecting certain ports. The defaults are:
|
||||
</p>
|
||||
<pre class="programlisting">query-source address * port *;
|
||||
query-source-v6 address * port *;
|
||||
|
|
@ -3281,7 +3281,7 @@ query-source-v6 address * port *;
|
|||
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
|
||||
<h3 class="title">Note</h3>
|
||||
If you do not wish the alternate transfer source
|
||||
to be used you should set
|
||||
to be used, you should set
|
||||
<span><strong class="command">use-alt-transfer-source</strong></span>
|
||||
appropriately and you should not depend upon
|
||||
getting a answer back to the first refresh
|
||||
|
|
@ -3336,7 +3336,7 @@ query-source-v6 address * port *;
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2562710"></a>Bad UDP Port Lists</h4></div></div></div>
|
||||
<a name="id2562716"></a>Bad UDP Port Lists</h4></div></div></div>
|
||||
<p><span><strong class="command">avoid-v4-udp-ports</strong></span>
|
||||
and <span><strong class="command">avoid-v6-udp-ports</strong></span> specify a list
|
||||
of IPv4 and IPv6 UDP ports that will not be used as system
|
||||
|
|
@ -3350,7 +3350,7 @@ query-source-v6 address * port *;
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2562725"></a>Operating System Resource Limits</h4></div></div></div>
|
||||
<a name="id2562800"></a>Operating System Resource Limits</h4></div></div></div>
|
||||
<p>
|
||||
The server's usage of many system resources can be limited.
|
||||
Scaled values are allowed when specifying resource limits. For
|
||||
|
|
@ -3409,7 +3409,7 @@ query-source-v6 address * port *;
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2562977"></a>Server Resource Limits</h4></div></div></div>
|
||||
<a name="id2562915"></a>Server Resource Limits</h4></div></div></div>
|
||||
<p>
|
||||
The following options set limits on the server's
|
||||
resource consumption that are enforced internally by the
|
||||
|
|
@ -3435,7 +3435,7 @@ query-source-v6 address * port *;
|
|||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">host-statistics-max</strong></span></span></dt>
|
||||
<dd><p>
|
||||
In BIND 8, specifies the maximum number of host statistic
|
||||
In BIND 8, specifies the maximum number of host statistics
|
||||
entries to be kept.
|
||||
Not implemented in BIND 9.
|
||||
</p></dd>
|
||||
|
|
@ -3487,7 +3487,7 @@ query-source-v6 address * port *;
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2563178"></a>Periodic Task Intervals</h4></div></div></div>
|
||||
<a name="id2563116"></a>Periodic Task Intervals</h4></div></div></div>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term"><span><strong class="command">cleaning-interval</strong></span></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -3495,7 +3495,7 @@ query-source-v6 address * port *;
|
|||
from the cache every <span><strong class="command">cleaning-interval</strong></span> minutes.
|
||||
The default is 60 minutes. The maximum value is 28 days
|
||||
(40320 minutes).
|
||||
If set to 0, no periodic cleaning will occur.
|
||||
If set to 0, no periodic cleaning will occur.
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">heartbeat-interval</strong></span></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -3600,7 +3600,7 @@ query-source-v6 address * port *;
|
|||
other addresses.
|
||||
However, not all resolvers can do this or are correctly
|
||||
configured.
|
||||
When a client is using a local server the sorting can be performed
|
||||
When a client is using a local server, the sorting can be performed
|
||||
in the server, based on the client's address. This only requires
|
||||
configuring the name servers, not all the clients.
|
||||
</p>
|
||||
|
|
@ -3714,7 +3714,7 @@ query-source-v6 address * port *;
|
|||
<p>
|
||||
If no class is specified, the default is <span><strong class="command">ANY</strong></span>.
|
||||
If no type is specified, the default is <span><strong class="command">ANY</strong></span>.
|
||||
If no name is specified, the default is "<span><strong class="command">*</strong></span>".
|
||||
If no name is specified, the default is "<span><strong class="command">*</strong></span>" (asterisk).
|
||||
</p>
|
||||
<p>
|
||||
The legal values for <span><strong class="command">ordering</strong></span> are:
|
||||
|
|
@ -3796,13 +3796,13 @@ query-source-v6 address * port *;
|
|||
Sets the number of seconds to cache a
|
||||
lame server indication. 0 disables caching. (This is
|
||||
<span class="bold"><strong>NOT</strong></span> recommended.)
|
||||
Default is <code class="literal">600</code> (10 minutes).
|
||||
Maximum value is
|
||||
The default is <code class="literal">600</code> (10 minutes) and the
|
||||
maximum value is
|
||||
<code class="literal">1800</code> (30 minutes).
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">max-ncache-ttl</strong></span></span></dt>
|
||||
<dd><p>
|
||||
To reduce network traffic and increase performance
|
||||
To reduce network traffic and increase performance,
|
||||
the server stores negative answers. <span><strong class="command">max-ncache-ttl</strong></span> is
|
||||
used to set a maximum retention time for these answers in
|
||||
the server
|
||||
|
|
@ -3823,7 +3823,7 @@ query-source-v6 address * port *;
|
|||
<p>
|
||||
The minimum number of root servers that
|
||||
is required for a request for the root servers to be
|
||||
accepted. Default
|
||||
accepted. The default
|
||||
is <strong class="userinput"><code>2</code></strong>.
|
||||
</p>
|
||||
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
|
||||
|
|
@ -3871,11 +3871,11 @@ query-source-v6 address * port *;
|
|||
</dd>
|
||||
<dt><span class="term"><span><strong class="command">edns-udp-size</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Sets the advertised EDNS UDP buffer size. Valid
|
||||
Sets the advertised EDNS UDP buffer size in bytes. Valid
|
||||
values are 512 to 4096 (values outside this range
|
||||
will be silently adjusted). The default value is
|
||||
4096. The usual reason for setting edns-udp-size to
|
||||
a non default value it to get UDP answers to pass
|
||||
a non-default value it to get UDP answers to pass
|
||||
through broken firewalls that block fragmented
|
||||
packets and/or block UDP packets that are greater
|
||||
than 512 bytes.
|
||||
|
|
@ -3883,10 +3883,10 @@ query-source-v6 address * port *;
|
|||
<dt><span class="term"><span><strong class="command">max-udp-size</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Sets the maximum EDNS UDP message size named will
|
||||
send. Valid values are 512 to 4096 (values outside
|
||||
send in bytes. Valid values are 512 to 4096 (values outside
|
||||
this range will be silently adjusted). The default
|
||||
value is 4096. The usual reason for setting
|
||||
max-udp-size to a non default value it to get UDP
|
||||
max-udp-size to a non-default value is to get UDP
|
||||
answers to pass through broken firewalls that
|
||||
block fragmented packets and/or block UDP packets
|
||||
that are greater than 512 bytes.
|
||||
|
|
@ -3898,7 +3898,7 @@ query-source-v6 address * port *;
|
|||
The default value is <code class="constant">text</code>, which is the
|
||||
standard textual representation. Files in other formats
|
||||
than <code class="constant">text</code> are typically expected
|
||||
to be generated by the <span><strong class="command">named-compilezone</strong></span>.
|
||||
to be generated by the <span><strong class="command">named-compilezone</strong></span> tool.
|
||||
Note that when a zone file in a different format than
|
||||
<code class="constant">text</code> is loaded, <span><strong class="command">named</strong></span>
|
||||
may omit some of the checks which would be performed for a
|
||||
|
|
@ -3931,20 +3931,20 @@ query-source-v6 address * port *;
|
|||
<p>
|
||||
This value should reflect how many queries come in for
|
||||
a given name in the time it takes to resolve that name.
|
||||
If the number of queries exceed this value named will
|
||||
If the number of queries exceed this value, named will
|
||||
assume that it is dealing with a non-responsive zone
|
||||
and will drop additional queries. If it gets a response
|
||||
after dropping queries it will raise the estimate. The
|
||||
after dropping queries, it will raise the estimate. The
|
||||
estimate will then be lowered in 20 minutes if it has
|
||||
remained unchanged.
|
||||
</p>
|
||||
<p>
|
||||
If <span><strong class="command">clients-per-query</strong></span> is set to zero
|
||||
If <span><strong class="command">clients-per-query</strong></span> is set to zero,
|
||||
then there is no limit on the number of clients per query
|
||||
and no queries will be dropped.
|
||||
</p>
|
||||
<p>
|
||||
If <span><strong class="command">max-clients-per-query</strong></span> is set to zero
|
||||
If <span><strong class="command">max-clients-per-query</strong></span> is set to zero,
|
||||
then there is no upper bound other than imposed by
|
||||
<span><strong class="command">recursive-clients</strong></span>.
|
||||
</p>
|
||||
|
|
@ -4071,7 +4071,7 @@ query-source-v6 address * port *;
|
|||
views of class IN. Disabled empty zones are only inherited
|
||||
from options if there are no disabled empty zones specified
|
||||
at the view level. To override the options list of disabled
|
||||
zones you can disable the root zone at the view level, for example:
|
||||
zones, you can disable the root zone at the view level, for example:
|
||||
</p>
|
||||
<pre class="programlisting">
|
||||
disable-empty-zone ".";
|
||||
|
|
@ -4079,7 +4079,7 @@ query-source-v6 address * port *;
|
|||
<p>
|
||||
</p>
|
||||
<p>
|
||||
If you are using the address ranges covered here you should
|
||||
If you are using the address ranges covered here, you should
|
||||
already have reverse zones covering the addresses you use.
|
||||
In practice this appears to not be the case with many queries
|
||||
being made to the infrustructure servers for names in these
|
||||
|
|
@ -4091,30 +4091,30 @@ query-source-v6 address * port *;
|
|||
<h3 class="title">Note</h3>
|
||||
The real parent servers for these zones should disable all
|
||||
empty zone under the parent zone they serve. For the real
|
||||
root servers this is all built in empty zones. This will
|
||||
root servers, this is all built in empty zones. This will
|
||||
enable them to return referrals to deeper in the tree.
|
||||
</div>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term"><span><strong class="command">empty-server</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Specify what server name will appear in the returned
|
||||
SOA record for empty zones. If none is specified then
|
||||
SOA record for empty zones. If none is specified, then
|
||||
the zone's name will be used.
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">empty-contact</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Specify what contact name will appear in the returned
|
||||
SOA record for empty zones. If none is specified then
|
||||
SOA record for empty zones. If none is specified, then
|
||||
"." will be used.
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">empty-zones-enable</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Enable / disable all empty zones. By default they
|
||||
Enable or disable all empty zones. By default they
|
||||
are enabled.
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">disable-empty-zone</strong></span></span></dt>
|
||||
<dd><p>
|
||||
Disable a indiviual empty zones. By default none are
|
||||
Disable individual empty zones. By default none are
|
||||
disabled. This option can be specified multiple times.
|
||||
</p></dd>
|
||||
</dl></div>
|
||||
|
|
@ -4321,15 +4321,14 @@ query-source-v6 address * port *;
|
|||
based
|
||||
algorithm, every <span><strong class="command">acache-cleaning-interval</strong></span> minutes.
|
||||
The default is 60 minutes.
|
||||
If set to 0, no periodic cleaning will occur.
|
||||
If set to 0, no periodic cleaning will occur.
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">max-acache-size</strong></span></span></dt>
|
||||
<dd><p>
|
||||
The maximum amount of memory to use for the server's acache,
|
||||
in bytes.
|
||||
The maximum amount of memory in bytes to use for the server's acache.
|
||||
When the amount of data in the acache reaches this limit,
|
||||
the server
|
||||
will clean more aggressivly so that the limit is not
|
||||
will clean more aggressively so that the limit is not
|
||||
exceeded.
|
||||
In a server with multiple views, the limit applies
|
||||
separately to the
|
||||
|
|
@ -4372,7 +4371,7 @@ query-source-v6 address * port *;
|
|||
The <span><strong class="command">server</strong></span> statement defines
|
||||
characteristics
|
||||
to be associated with a remote name server. If a prefix length is
|
||||
specified then a range of servers is covered. Only the most
|
||||
specified, then a range of servers is covered. Only the most
|
||||
specific
|
||||
server clause applies regardless of the order in
|
||||
<code class="filename">named.conf</code>.
|
||||
|
|
@ -4445,7 +4444,7 @@ query-source-v6 address * port *;
|
|||
<p>
|
||||
The <span><strong class="command">edns-udp-size</strong></span> option sets the EDNS UDP size
|
||||
that is advertised by named when querying the remote server.
|
||||
Valid values are 512 to 4096 (values outside this range will be
|
||||
Valid values are 512 to 4096 bytes (values outside this range will be
|
||||
silently adjusted). This option is useful when you wish to
|
||||
advertises a different value to this server than the value you
|
||||
advertise globally, for example, when there is a firewall at the
|
||||
|
|
@ -4454,7 +4453,7 @@ query-source-v6 address * port *;
|
|||
<p>
|
||||
The <span><strong class="command">max-udp-size</strong></span> option sets the
|
||||
maximum EDNS UDP message size named will send. Valid
|
||||
values are 512 to 4096 (values outside this range will
|
||||
values are 512 to 4096 bytes (values outside this range will
|
||||
be silently adjusted). This option is useful when you
|
||||
know that there is a firewall that is blocking large
|
||||
replies from named.
|
||||
|
|
@ -4509,7 +4508,7 @@ query-source-v6 address * port *;
|
|||
Similarly, for an IPv6 remote server, only
|
||||
<span><strong class="command">transfer-source-v6</strong></span> can be
|
||||
specified.
|
||||
Form more details, see the description of
|
||||
For more details, see the description of
|
||||
<span><strong class="command">transfer-source</strong></span> and
|
||||
<span><strong class="command">transfer-source-v6</strong></span> in
|
||||
<a href="Bv9ARM.ch06.html#zone_transfers" title="Zone Transfers">the section called “Zone Transfers”</a>.
|
||||
|
|
@ -4535,7 +4534,7 @@ query-source-v6 address * port *;
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2565882"></a><span><strong class="command">trusted-keys</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<a name="id2565889"></a><span><strong class="command">trusted-keys</strong></span> Statement Grammar</h3></div></div></div>
|
||||
<pre class="programlisting">trusted-keys {
|
||||
<em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ;
|
||||
[<span class="optional"> <em class="replaceable"><code>string</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>number</code></em> <em class="replaceable"><code>string</code></em> ; [<span class="optional">...</span>]</span>]
|
||||
|
|
@ -4544,7 +4543,7 @@ query-source-v6 address * port *;
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2565931"></a><span><strong class="command">trusted-keys</strong></span> Statement Definition
|
||||
<a name="id2565938"></a><span><strong class="command">trusted-keys</strong></span> Statement Definition
|
||||
and Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span><strong class="command">trusted-keys</strong></span> statement defines
|
||||
|
|
@ -4562,7 +4561,7 @@ query-source-v6 address * port *;
|
|||
<span><strong class="command">trusted-keys</strong></span> are deemed to exist regardless
|
||||
of what parent zones say. Similarly for all keys listed in
|
||||
<span><strong class="command">trusted-keys</strong></span> only those keys are
|
||||
used to validate the DNSKEY RRset. The parents DS RRset
|
||||
used to validate the DNSKEY RRset. The parent's DS RRset
|
||||
will not be used.
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -4587,7 +4586,7 @@ query-source-v6 address * port *;
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2566011"></a><span><strong class="command">view</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<a name="id2566018"></a><span><strong class="command">view</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<p>
|
||||
The <span><strong class="command">view</strong></span> statement is a powerful
|
||||
feature
|
||||
|
|
@ -4670,7 +4669,7 @@ query-source-v6 address * port *;
|
|||
</p>
|
||||
<p>
|
||||
Here is an example of a typical split DNS setup implemented
|
||||
using <span><strong class="command">view</strong></span> statements.
|
||||
using <span><strong class="command">view</strong></span> statements:
|
||||
</p>
|
||||
<pre class="programlisting">view "internal" {
|
||||
// This should match our internal networks.
|
||||
|
|
@ -4839,10 +4838,10 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2567457"></a><span><strong class="command">zone</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<a name="id2567395"></a><span><strong class="command">zone</strong></span> Statement Definition and Usage</h3></div></div></div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2567464"></a>Zone Types</h4></div></div></div>
|
||||
<a name="id2567402"></a>Zone Types</h4></div></div></div>
|
||||
<div class="informaltable"><table border="1">
|
||||
<colgroup>
|
||||
<col>
|
||||
|
|
@ -4898,7 +4897,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
numbers (in the
|
||||
tens or hundreds of thousands) of zones per server, it
|
||||
is best to
|
||||
use a two level naming scheme for zone file names. For
|
||||
use a two-level naming scheme for zone file names. For
|
||||
example,
|
||||
a slave server for the zone <code class="literal">example.com</code> might place
|
||||
the zone contents into a file called
|
||||
|
|
@ -4993,8 +4992,8 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
if you want to use this type of zone to change the
|
||||
behavior of the
|
||||
global <span><strong class="command">forward</strong></span> option
|
||||
(that is, "forward first
|
||||
to", then "forward only", or vice versa, but want to
|
||||
(that is, "forward first"
|
||||
to, then "forward only", or vice versa, but want to
|
||||
use the same
|
||||
servers as set globally) you need to re-specify the
|
||||
global forwarders.
|
||||
|
|
@ -5030,14 +5029,14 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</td>
|
||||
<td>
|
||||
<p>
|
||||
This is used to enforce the delegation only
|
||||
This is used to enforce the delegation-only
|
||||
status of infrastructure zones (e.g. COM, NET, ORG).
|
||||
Any answer that
|
||||
is received without a explicit or implicit delegation
|
||||
is received without an explicit or implicit delegation
|
||||
in the authority
|
||||
section will be treated as NXDOMAIN. This does not
|
||||
apply to the zone
|
||||
apex. This SHOULD NOT be applied to leaf zones.
|
||||
apex. This should not be applied to leaf zones.
|
||||
</p>
|
||||
<p>
|
||||
<code class="varname">delegation-only</code> has no
|
||||
|
|
@ -5051,7 +5050,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2567883"></a>Class</h4></div></div></div>
|
||||
<a name="id2567958"></a>Class</h4></div></div></div>
|
||||
<p>
|
||||
The zone's name may optionally be followed by a class. If
|
||||
a class is not specified, class <code class="literal">IN</code> (for <code class="varname">Internet</code>),
|
||||
|
|
@ -5073,7 +5072,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2567916"></a>Zone Options</h4></div></div></div>
|
||||
<a name="id2567991"></a>Zone Options</h4></div></div></div>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term"><span><strong class="command">allow-notify</strong></span></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -5203,7 +5202,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
<dt><span class="term"><span><strong class="command">delegation-only</strong></span></span></dt>
|
||||
<dd><p>
|
||||
The flag only applies to hint and stub zones. If set
|
||||
to <strong class="userinput"><code>yes</code></strong> then the zone will also be
|
||||
to <strong class="userinput"><code>yes</code></strong>, then the zone will also be
|
||||
treated as if it
|
||||
is also a delegation-only type zone.
|
||||
</p></dd>
|
||||
|
|
@ -5219,7 +5218,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
<dd><p>
|
||||
Used to override the list of global forwarders.
|
||||
If it is not specified in a zone of type <span><strong class="command">forward</strong></span>,
|
||||
no forwarding is done for the zone; the global options are
|
||||
no forwarding is done for the zone and the global options are
|
||||
not used.
|
||||
</p></dd>
|
||||
<dt><span class="term"><span><strong class="command">ixfr-base</strong></span></span></dt>
|
||||
|
|
@ -5506,7 +5505,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
name to update, where the key has the same
|
||||
name as the name to be updated. The
|
||||
<em class="replaceable"><code>identity</code></em> would
|
||||
be specified as <code class="constant">*</code> in
|
||||
be specified as <code class="constant">*</code> (an asterisk) in
|
||||
this case.
|
||||
</p>
|
||||
</td>
|
||||
|
|
@ -5561,7 +5560,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="sect1" lang="en">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id2569739"></a>Zone File</h2></div></div></div>
|
||||
<a name="id2569676"></a>Zone File</h2></div></div></div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="types_of_resource_records_and_when_to_use_them"></a>Types of Resource Records and When to Use Them</h3></div></div></div>
|
||||
|
|
@ -5574,7 +5573,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</p>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2569757"></a>Resource Records</h4></div></div></div>
|
||||
<a name="id2569763"></a>Resource Records</h4></div></div></div>
|
||||
<p>
|
||||
A domain name identifies a node. Each node has a set of
|
||||
resource information, which may be empty. The set of resource
|
||||
|
|
@ -5614,7 +5613,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</td>
|
||||
<td>
|
||||
<p>
|
||||
An encoded 16 bit value that specifies
|
||||
An encoded 16-bit value that specifies
|
||||
the type of the resource record.
|
||||
</p>
|
||||
</td>
|
||||
|
|
@ -5627,8 +5626,8 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</td>
|
||||
<td>
|
||||
<p>
|
||||
The time to live of the RR. This field
|
||||
is a 32 bit integer in units of seconds, and is
|
||||
The time-to-live of the RR. This field
|
||||
is a 32-bit integer in units of seconds, and is
|
||||
primarily used by
|
||||
resolvers when they cache RRs. The TTL describes how
|
||||
long a RR can
|
||||
|
|
@ -5644,7 +5643,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</td>
|
||||
<td>
|
||||
<p>
|
||||
An encoded 16 bit value that identifies
|
||||
An encoded 16-bit value that identifies
|
||||
a protocol family or instance of a protocol.
|
||||
</p>
|
||||
</td>
|
||||
|
|
@ -5898,7 +5897,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
<td>
|
||||
<p>
|
||||
Identifies a mail exchange for the domain with
|
||||
a 16 bit preference value (lower is better)
|
||||
a 16-bit preference value (lower is better)
|
||||
followed by the host name of the mail exchange.
|
||||
Described in RFC 974, RFC 1035.
|
||||
</p>
|
||||
|
|
@ -6225,7 +6224,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2571104"></a>Textual expression of RRs</h4></div></div></div>
|
||||
<a name="id2571109"></a>Textual expression of RRs</h4></div></div></div>
|
||||
<p>
|
||||
RRs are represented in binary form in the packets of the DNS
|
||||
protocol, and are usually represented in highly encoded form
|
||||
|
|
@ -6369,13 +6368,13 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</tbody>
|
||||
</table></div>
|
||||
<p>
|
||||
The MX RRs have an RDATA section which consists of a 16 bit
|
||||
The MX RRs have an RDATA section which consists of a 16-bit
|
||||
number followed by a domain name. The address RRs use a
|
||||
standard
|
||||
IP address format to contain a 32 bit internet address.
|
||||
IP address format to contain a 32-bit internet address.
|
||||
</p>
|
||||
<p>
|
||||
This example shows six RRs, with two RRs at each of three
|
||||
The above example shows six RRs, with two RRs at each of three
|
||||
domain names.
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -6428,7 +6427,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2571556"></a>Discussion of MX Records</h3></div></div></div>
|
||||
<a name="id2571629"></a>Discussion of MX Records</h3></div></div></div>
|
||||
<p>
|
||||
As described above, domain servers store information as a
|
||||
series of resource records, each of which contains a particular
|
||||
|
|
@ -6615,7 +6614,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="Setting_TTLs"></a>Setting TTLs</h3></div></div></div>
|
||||
<p>
|
||||
The time to live of the RR field is a 32 bit integer represented
|
||||
The time-to-live of the RR field is a 32-bit integer represented
|
||||
in units of seconds, and is primarily used by resolvers when they
|
||||
cache RRs. The TTL describes how long a RR can be cached before it
|
||||
should be discarded. The following three types of TTL are
|
||||
|
|
@ -6686,7 +6685,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2572244"></a>Inverse Mapping in IPv4</h3></div></div></div>
|
||||
<a name="id2572317"></a>Inverse Mapping in IPv4</h3></div></div></div>
|
||||
<p>
|
||||
Reverse name resolution (that is, translation from IP address
|
||||
to name) is achieved by means of the <span class="emphasis"><em>in-addr.arpa</em></span> domain
|
||||
|
|
@ -6747,7 +6746,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2572371"></a>Other Zone File Directives</h3></div></div></div>
|
||||
<a name="id2572444"></a>Other Zone File Directives</h3></div></div></div>
|
||||
<p>
|
||||
The Master File Format was initially defined in RFC 1035 and
|
||||
has subsequently been extended. While the Master File Format
|
||||
|
|
@ -6762,7 +6761,7 @@ zone <em class="replaceable"><code>zone_name</code></em> [<span class="optional"
|
|||
</p>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2572393"></a>The <span><strong class="command">$ORIGIN</strong></span> Directive</h4></div></div></div>
|
||||
<a name="id2572467"></a>The <span><strong class="command">$ORIGIN</strong></span> Directive</h4></div></div></div>
|
||||
<p>
|
||||
Syntax: <span><strong class="command">$ORIGIN</strong></span>
|
||||
<em class="replaceable"><code>domain-name</code></em>
|
||||
|
|
@ -6790,7 +6789,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2572590"></a>The <span><strong class="command">$INCLUDE</strong></span> Directive</h4></div></div></div>
|
||||
<a name="id2572596"></a>The <span><strong class="command">$INCLUDE</strong></span> Directive</h4></div></div></div>
|
||||
<p>
|
||||
Syntax: <span><strong class="command">$INCLUDE</strong></span>
|
||||
<em class="replaceable"><code>filename</code></em>
|
||||
|
|
@ -6826,7 +6825,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
|
|||
</div>
|
||||
<div class="sect3" lang="en">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2572660"></a>The <span><strong class="command">$TTL</strong></span> Directive</h4></div></div></div>
|
||||
<a name="id2572665"></a>The <span><strong class="command">$TTL</strong></span> Directive</h4></div></div></div>
|
||||
<p>
|
||||
Syntax: <span><strong class="command">$TTL</strong></span>
|
||||
<em class="replaceable"><code>default-ttl</code></em>
|
||||
|
|
@ -6845,7 +6844,7 @@ WWW.EXAMPLE.COM. CNAME MAIN-SERVER.EXAMPLE.COM.
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2572696"></a><span class="acronym">BIND</span> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</h3></div></div></div>
|
||||
<a name="id2572701"></a><span class="acronym">BIND</span> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</h3></div></div></div>
|
||||
<p>
|
||||
Syntax: <span><strong class="command">$GENERATE</strong></span>
|
||||
<em class="replaceable"><code>range</code></em>
|
||||
|
|
@ -6890,7 +6889,7 @@ $GENERATE 1-127 $ CNAME $.0</pre>
|
|||
<td>
|
||||
<p>
|
||||
This can be one of two forms: start-stop
|
||||
or start-stop/step. If the first form is used then step
|
||||
or start-stop/step. If the first form is used, then step
|
||||
is set to
|
||||
1. All of start, stop and step must be positive.
|
||||
</p>
|
||||
|
|
@ -6904,6 +6903,7 @@ $GENERATE 1-127 $ CNAME $.0</pre>
|
|||
<p><span><strong class="command">lhs</strong></span>
|
||||
describes the owner name of the resource records
|
||||
to be created. Any single <span><strong class="command">$</strong></span>
|
||||
(dollar sign)
|
||||
symbols within the <span><strong class="command">lhs</strong></span> side
|
||||
are replaced by the iterator value.
|
||||
|
||||
|
|
@ -6921,7 +6921,7 @@ $GENERATE 1-127 $ CNAME $.0</pre>
|
|||
<span><strong class="command">${offset[,width[,base]]}</strong></span>.
|
||||
For example, <span><strong class="command">${-20,3,d}</strong></span>
|
||||
subtracts 20 from the current value, prints the
|
||||
result as a decimal in a zero padded field of
|
||||
result as a decimal in a zero-padded field of
|
||||
width 3.
|
||||
|
||||
Available output forms are decimal
|
||||
|
|
@ -6935,7 +6935,7 @@ $GENERATE 1-127 $ CNAME $.0</pre>
|
|||
to the name.
|
||||
</p>
|
||||
<p>
|
||||
For compatibility with earlier versions <span><strong class="command">$$</strong></span> is still
|
||||
For compatibility with earlier versions, <span><strong class="command">$$</strong></span> is still
|
||||
recognized as indicating a literal $ in the output.
|
||||
</p>
|
||||
</td>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch07.html,v 1.125 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch07.html,v 1.126 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -46,10 +46,10 @@
|
|||
<p><b>Table of Contents</b></p>
|
||||
<dl>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2573238"><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span></a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2573309"><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span></a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2573450">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2573510">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2573386">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2573446">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
|
||||
</dl>
|
||||
|
|
@ -72,7 +72,7 @@
|
|||
<p>
|
||||
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
|
||||
outside parties can help prevent spoofing and DoS attacks against
|
||||
outside parties can help prevent spoofing and denial of service (DoS) attacks against
|
||||
your server.
|
||||
</p>
|
||||
<p>
|
||||
|
|
@ -118,10 +118,10 @@ zone "example.com" {
|
|||
</div>
|
||||
<div class="sect1" lang="en">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id2573238"></a><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span></h2></div></div></div>
|
||||
<a name="id2573309"></a><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span></h2></div></div></div>
|
||||
<p>
|
||||
On UNIX servers, it is possible to run <span class="acronym">BIND</span> in a <span class="emphasis"><em>chrooted</em></span> environment
|
||||
(<span><strong class="command">chroot()</strong></span>) by specifying the "<code class="option">-t</code>"
|
||||
(using the <span><strong class="command">chroot()</strong></span> function) by specifying the "<code class="option">-t</code>"
|
||||
option. This can help improve system security by placing <span class="acronym">BIND</span> in
|
||||
a "sandbox", which will limit the damage done if a server is
|
||||
compromised.
|
||||
|
|
@ -132,7 +132,7 @@ zone "example.com" {
|
|||
We suggest running as an unprivileged user when using the <span><strong class="command">chroot</strong></span> feature.
|
||||
</p>
|
||||
<p>
|
||||
Here is an example command line to load <span class="acronym">BIND</span> in a <span><strong class="command">chroot()</strong></span> sandbox,
|
||||
Here is an example command line to load <span class="acronym">BIND</span> in a <span><strong class="command">chroot</strong></span> sandbox,
|
||||
<span><strong class="command">/var/named</strong></span>, and to run <span><strong class="command">named</strong></span> <span><strong class="command">setuid</strong></span> to
|
||||
user 202:
|
||||
</p>
|
||||
|
|
@ -141,7 +141,7 @@ zone "example.com" {
|
|||
</p>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2573450"></a>The <span><strong class="command">chroot</strong></span> Environment</h3></div></div></div>
|
||||
<a name="id2573386"></a>The <span><strong class="command">chroot</strong></span> Environment</h3></div></div></div>
|
||||
<p>
|
||||
In order for a <span><strong class="command">chroot</strong></span> environment
|
||||
to
|
||||
|
|
@ -169,7 +169,7 @@ zone "example.com" {
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2573510"></a>Using the <span><strong class="command">setuid</strong></span> Function</h3></div></div></div>
|
||||
<a name="id2573446"></a>Using the <span><strong class="command">setuid</strong></span> Function</h3></div></div></div>
|
||||
<p>
|
||||
Prior to running the <span><strong class="command">named</strong></span> daemon,
|
||||
use
|
||||
|
|
@ -195,7 +195,7 @@ zone "example.com" {
|
|||
<p>
|
||||
Access to the dynamic
|
||||
update facility should be strictly limited. In earlier versions of
|
||||
<span class="acronym">BIND</span> the only way to do this was
|
||||
<span class="acronym">BIND</span>, the only way to do this was
|
||||
based on the IP
|
||||
address of the host requesting the update, by listing an IP address
|
||||
or
|
||||
|
|
@ -222,7 +222,7 @@ zone "example.com" {
|
|||
option can be used.
|
||||
</p>
|
||||
<p>
|
||||
Some sites choose to keep all dynamically updated DNS data
|
||||
Some sites choose to keep all dynamically-updated DNS data
|
||||
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
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch08.html,v 1.124 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch08.html,v 1.125 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -45,18 +45,18 @@
|
|||
<div class="toc">
|
||||
<p><b>Table of Contents</b></p>
|
||||
<dl>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573726">Common Problems</a></span></dt>
|
||||
<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2573732">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573744">Incrementing and Changing the Serial Number</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573761">Where Can I Get Help?</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573662">Common Problems</a></span></dt>
|
||||
<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2573668">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573680">Incrementing and Changing the Serial Number</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573697">Where Can I Get Help?</a></span></dt>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="sect1" lang="en">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id2573726"></a>Common Problems</h2></div></div></div>
|
||||
<a name="id2573662"></a>Common Problems</h2></div></div></div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2573732"></a>It's not working; how can I figure out what's wrong?</h3></div></div></div>
|
||||
<a name="id2573668"></a>It's not working; how can I figure out what's wrong?</h3></div></div></div>
|
||||
<p>
|
||||
The best solution to solving installation and
|
||||
configuration issues is to take preventative measures by setting
|
||||
|
|
@ -68,7 +68,7 @@
|
|||
</div>
|
||||
<div class="sect1" lang="en">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id2573744"></a>Incrementing and Changing the Serial Number</h2></div></div></div>
|
||||
<a name="id2573680"></a>Incrementing and Changing the Serial Number</h2></div></div></div>
|
||||
<p>
|
||||
Zone serial numbers are just numbers-they aren't date
|
||||
related. A lot of people set them to a number that represents a
|
||||
|
|
@ -95,7 +95,7 @@
|
|||
</div>
|
||||
<div class="sect1" lang="en">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id2573761"></a>Where Can I Get Help?</h2></div></div></div>
|
||||
<a name="id2573697"></a>Where Can I Get Help?</h2></div></div></div>
|
||||
<p>
|
||||
The Internet Systems Consortium
|
||||
(<span class="acronym">ISC</span>) offers a wide range
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.ch09.html,v 1.125 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: Bv9ARM.ch09.html,v 1.126 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -45,21 +45,21 @@
|
|||
<div class="toc">
|
||||
<p><b>Table of Contents</b></p>
|
||||
<dl>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2573822">Acknowledgments</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2573827">Acknowledgments</a></span></dt>
|
||||
<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#historical_dns_information">A Brief History of the <span class="acronym">DNS</span> and <span class="acronym">BIND</span></a></span></dt></dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2573916">General <span class="acronym">DNS</span> Reference Information</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2573921">General <span class="acronym">DNS</span> Reference Information</a></span></dt>
|
||||
<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt></dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch09.html#rfcs">Request for Comments (RFCs)</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch09.html#internet_drafts">Internet Drafts</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2577288">Other Documents About <span class="acronym">BIND</span></a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2577292">Other Documents About <span class="acronym">BIND</span></a></span></dt>
|
||||
</dl></dd>
|
||||
</dl>
|
||||
</div>
|
||||
<div class="sect1" lang="en">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id2573822"></a>Acknowledgments</h2></div></div></div>
|
||||
<a name="id2573827"></a>Acknowledgments</h2></div></div></div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="historical_dns_information"></a>A Brief History of the <span class="acronym">DNS</span> and <span class="acronym">BIND</span></h3></div></div></div>
|
||||
|
|
@ -69,7 +69,7 @@
|
|||
core of the new system was described in 1983 in RFCs 882 and
|
||||
883. From 1984 to 1987, the ARPAnet (the precursor to today's
|
||||
Internet) became a testbed of experimentation for developing the
|
||||
new naming/addressing scheme in an rapidly expanding,
|
||||
new naming/addressing scheme in a rapidly expanding,
|
||||
operational network environment. New RFCs were written and
|
||||
published in 1987 that modified the original documents to
|
||||
incorporate improvements based on the working model. RFC 1034,
|
||||
|
|
@ -116,7 +116,7 @@
|
|||
released by Digital Equipment
|
||||
Corporation (now Compaq Computer Corporation). Paul Vixie, then
|
||||
a DEC employee, became <span class="acronym">BIND</span>'s
|
||||
primary caretaker. Paul was assisted
|
||||
primary caretaker. He was assisted
|
||||
by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan
|
||||
Beecher, Andrew
|
||||
Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat
|
||||
|
|
@ -124,7 +124,7 @@
|
|||
Wolfhugel, and others.
|
||||
</p>
|
||||
<p>
|
||||
<span class="acronym">BIND</span> Version 4.9.2 was sponsored by
|
||||
<span class="acronym">BIND</span> version 4.9.2 was sponsored by
|
||||
Vixie Enterprises. Paul
|
||||
Vixie became <span class="acronym">BIND</span>'s principal
|
||||
architect/programmer.
|
||||
|
|
@ -148,7 +148,7 @@
|
|||
</div>
|
||||
<div class="sect1" lang="en">
|
||||
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
|
||||
<a name="id2573916"></a>General <span class="acronym">DNS</span> Reference Information</h2></div></div></div>
|
||||
<a name="id2573921"></a>General <span class="acronym">DNS</span> Reference Information</h2></div></div></div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h3></div></div></div>
|
||||
|
|
@ -235,7 +235,7 @@
|
|||
</p>
|
||||
<div class="bibliography">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2574172"></a>Bibliography</h4></div></div></div>
|
||||
<a name="id2574177"></a>Bibliography</h4></div></div></div>
|
||||
<div class="bibliodiv">
|
||||
<h3 class="title">Standards</h3>
|
||||
<div class="biblioentry"><p>[<span class="abbrev">RFC974</span>] <span class="author"><span class="firstname">C.</span> <span class="surname">Partridge</span>. </span><span class="title"><i>Mail Routing and the Domain System</i>. </span><span class="pubdate">January 1986. </span></p></div>
|
||||
|
|
@ -380,7 +380,7 @@
|
|||
and Renumbering</i>. </span><span class="pubdate">July 2000. </span></p></div>
|
||||
</div>
|
||||
<div class="bibliodiv">
|
||||
<h3 class="title">Obsoleted DNS Security RFC</h3>
|
||||
<h3 class="title">Obsoleted DNS Security RFCs</h3>
|
||||
<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
|
||||
<h3 class="title">Note</h3>
|
||||
<p>
|
||||
|
|
@ -420,11 +420,11 @@
|
|||
</div>
|
||||
<div class="sect2" lang="en">
|
||||
<div class="titlepage"><div><div><h3 class="title">
|
||||
<a name="id2577288"></a>Other Documents About <span class="acronym">BIND</span></h3></div></div></div>
|
||||
<a name="id2577292"></a>Other Documents About <span class="acronym">BIND</span></h3></div></div></div>
|
||||
<p></p>
|
||||
<div class="bibliography">
|
||||
<div class="titlepage"><div><div><h4 class="title">
|
||||
<a name="id2577298"></a>Bibliography</h4></div></div></div>
|
||||
<a name="id2577302"></a>Bibliography</h4></div></div></div>
|
||||
<div class="biblioentry"><p><span class="authorgroup"><span class="firstname">Paul</span> <span class="surname">Albitz</span> and <span class="firstname">Cricket</span> <span class="surname">Liu</span>. </span><span class="title"><i><span class="acronym">DNS</span> and <span class="acronym">BIND</span></i>. </span><span class="copyright">Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. </span></p></div>
|
||||
</div>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: Bv9ARM.html,v 1.135 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: Bv9ARM.html,v 1.136 2006/06/08 02:44:04 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -133,7 +133,7 @@
|
|||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2554882"><span><strong class="command">acl</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#acl"><span><strong class="command">acl</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2555072"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2555140"><span><strong class="command">controls</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage"><span><strong class="command">controls</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2555432"><span><strong class="command">include</strong></span> Statement Grammar</a></span></dt>
|
||||
|
|
@ -155,54 +155,54 @@
|
|||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_grammar"><span><strong class="command">server</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#server_statement_definition_and_usage"><span><strong class="command">server</strong></span> Statement Definition and
|
||||
Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2565882"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2565931"><span><strong class="command">trusted-keys</strong></span> Statement Definition
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2565889"><span><strong class="command">trusted-keys</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2565938"><span><strong class="command">trusted-keys</strong></span> Statement Definition
|
||||
and Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#view_statement_grammar"><span><strong class="command">view</strong></span> Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2566011"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2566018"><span><strong class="command">view</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zone_statement_grammar"><span><strong class="command">zone</strong></span>
|
||||
Statement Grammar</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2567457"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2567395"><span><strong class="command">zone</strong></span> Statement Definition and Usage</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2569739">Zone File</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch06.html#id2569676">Zone File</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them">Types of Resource Records and When to Use Them</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2571556">Discussion of MX Records</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2571629">Discussion of MX Records</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#Setting_TTLs">Setting TTLs</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572244">Inverse Mapping in IPv4</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572371">Other Zone File Directives</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572696"><span class="acronym">BIND</span> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572317">Inverse Mapping in IPv4</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572444">Other Zone File Directives</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#id2572701"><span class="acronym">BIND</span> Master File Extension: the <span><strong class="command">$GENERATE</strong></span> Directive</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch06.html#zonefile_format">Additional File Formats</a></span></dt>
|
||||
</dl></dd>
|
||||
</dl></dd>
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch07.html">7. <span class="acronym">BIND</span> 9 Security Considerations</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch07.html#Access_Control_Lists">Access Control Lists</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2573238"><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span></a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch07.html#id2573309"><span><strong class="command">chroot</strong></span> and <span><strong class="command">setuid</strong></span></a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2573450">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2573510">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2573386">The <span><strong class="command">chroot</strong></span> Environment</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch07.html#id2573446">Using the <span><strong class="command">setuid</strong></span> Function</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch07.html#dynamic_update_security">Dynamic Update Security</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="chapter"><a href="Bv9ARM.ch08.html">8. Troubleshooting</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573726">Common Problems</a></span></dt>
|
||||
<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2573732">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573744">Incrementing and Changing the Serial Number</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573761">Where Can I Get Help?</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573662">Common Problems</a></span></dt>
|
||||
<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch08.html#id2573668">It's not working; how can I figure out what's wrong?</a></span></dt></dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573680">Incrementing and Changing the Serial Number</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch08.html#id2573697">Where Can I Get Help?</a></span></dt>
|
||||
</dl></dd>
|
||||
<dt><span class="appendix"><a href="Bv9ARM.ch09.html">A. Appendices</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2573822">Acknowledgments</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2573827">Acknowledgments</a></span></dt>
|
||||
<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#historical_dns_information">A Brief History of the <span class="acronym">DNS</span> and <span class="acronym">BIND</span></a></span></dt></dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2573916">General <span class="acronym">DNS</span> Reference Information</a></span></dt>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2573921">General <span class="acronym">DNS</span> Reference Information</a></span></dt>
|
||||
<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt></dl></dd>
|
||||
<dt><span class="sect1"><a href="Bv9ARM.ch09.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt>
|
||||
<dd><dl>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch09.html#rfcs">Request for Comments (RFCs)</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch09.html#internet_drafts">Internet Drafts</a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2577288">Other Documents About <span class="acronym">BIND</span></a></span></dt>
|
||||
<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2577292">Other Documents About <span class="acronym">BIND</span></a></span></dt>
|
||||
</dl></dd>
|
||||
</dl></dd>
|
||||
<dt><span class="reference"><a href="Bv9ARM.ch10.html">I. Manual pages</a></span></dt>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.dig.html,v 1.29 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.dig.html,v 1.30 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -52,7 +52,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">dig</code> [global-queryopt...] [query...]</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2544858"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2544862"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">dig</strong></span>
|
||||
(domain information groper) is a flexible tool
|
||||
for interrogating DNS name servers. It performs DNS lookups and
|
||||
|
|
@ -91,7 +91,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2552988"></a><h2>SIMPLE USAGE</h2>
|
||||
<a name="id2552993"></a><h2>SIMPLE USAGE</h2>
|
||||
<p>
|
||||
A typical invocation of <span><strong class="command">dig</strong></span> looks like:
|
||||
</p>
|
||||
|
|
@ -137,7 +137,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2553099"></a><h2>OPTIONS</h2>
|
||||
<a name="id2553104"></a><h2>OPTIONS</h2>
|
||||
<p>
|
||||
The <code class="option">-b</code> option sets the source IP address of the query
|
||||
to <em class="parameter"><code>address</code></em>. This must be a valid
|
||||
|
|
@ -237,7 +237,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2602994"></a><h2>QUERY OPTIONS</h2>
|
||||
<a name="id2603066"></a><h2>QUERY OPTIONS</h2>
|
||||
<p><span><strong class="command">dig</strong></span>
|
||||
provides a number of query options which affect
|
||||
the way in which lookups are made and the results displayed. Some of
|
||||
|
|
@ -556,7 +556,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2628420"></a><h2>MULTIPLE QUERIES</h2>
|
||||
<a name="id2628424"></a><h2>MULTIPLE QUERIES</h2>
|
||||
<p>
|
||||
The BIND 9 implementation of <span><strong class="command">dig </strong></span>
|
||||
supports
|
||||
|
|
@ -602,7 +602,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2628505"></a><h2>IDN SUPPORT</h2>
|
||||
<a name="id2628578"></a><h2>IDN SUPPORT</h2>
|
||||
<p>
|
||||
If <span><strong class="command">dig</strong></span> has been built with IDN (internationalized
|
||||
domain name) support, it can accept and display non-ASCII domain names.
|
||||
|
|
@ -616,14 +616,14 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2628534"></a><h2>FILES</h2>
|
||||
<a name="id2628606"></a><h2>FILES</h2>
|
||||
<p><code class="filename">/etc/resolv.conf</code>
|
||||
</p>
|
||||
<p><code class="filename">${HOME}/.digrc</code>
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2628624"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2628696"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">host</span>(1)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
|
||||
|
|
@ -631,7 +631,7 @@ dig +qr www.isc.org any -x 127.0.0.1 isc.org ns +noqr
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2628661"></a><h2>BUGS</h2>
|
||||
<a name="id2628733"></a><h2>BUGS</h2>
|
||||
<p>
|
||||
There are probably too many query options.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.dnssec-keygen.html,v 1.29 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.dnssec-keygen.html,v 1.30 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">dnssec-keygen</code> {-a <em class="replaceable"><code>algorithm</code></em>} {-b <em class="replaceable"><code>keysize</code></em>} {-n <em class="replaceable"><code>nametype</code></em>} [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-e</code>] [<code class="option">-f <em class="replaceable"><code>flag</code></em></code>] [<code class="option">-g <em class="replaceable"><code>generator</code></em></code>] [<code class="option">-h</code>] [<code class="option">-k</code>] [<code class="option">-p <em class="replaceable"><code>protocol</code></em></code>] [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-s <em class="replaceable"><code>strength</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] {name}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2578452"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2578524"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">dnssec-keygen</strong></span>
|
||||
generates keys for DNSSEC (Secure DNS), as defined in RFC 2535
|
||||
and RFC <TBA\>. It can also generate keys for use with
|
||||
|
|
@ -58,7 +58,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2578466"></a><h2>OPTIONS</h2>
|
||||
<a name="id2578538"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-a <em class="replaceable"><code>algorithm</code></em></span></dt>
|
||||
<dd>
|
||||
|
|
@ -166,7 +166,7 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2579150"></a><h2>GENERATED KEYS</h2>
|
||||
<a name="id2579428"></a><h2>GENERATED KEYS</h2>
|
||||
<p>
|
||||
When <span><strong class="command">dnssec-keygen</strong></span> completes
|
||||
successfully,
|
||||
|
|
@ -212,7 +212,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2579258"></a><h2>EXAMPLE</h2>
|
||||
<a name="id2580696"></a><h2>EXAMPLE</h2>
|
||||
<p>
|
||||
To generate a 768-bit DSA key for the domain
|
||||
<strong class="userinput"><code>example.com</code></strong>, the following command would be
|
||||
|
|
@ -233,7 +233,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2579315"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2580753"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">dnssec-signzone</span>(8)</span>,
|
||||
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
|
||||
<em class="citetitle">RFC 2535</em>,
|
||||
|
|
@ -242,7 +242,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2582554"></a><h2>AUTHOR</h2>
|
||||
<a name="id2580784"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.dnssec-signzone.html,v 1.28 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.dnssec-signzone.html,v 1.29 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">dnssec-signzone</code> [<code class="option">-a</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-d <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-e <em class="replaceable"><code>end-time</code></em></code>] [<code class="option">-f <em class="replaceable"><code>output-file</code></em></code>] [<code class="option">-g</code>] [<code class="option">-h</code>] [<code class="option">-k <em class="replaceable"><code>key</code></em></code>] [<code class="option">-l <em class="replaceable"><code>domain</code></em></code>] [<code class="option">-i <em class="replaceable"><code>interval</code></em></code>] [<code class="option">-I <em class="replaceable"><code>input-format</code></em></code>] [<code class="option">-j <em class="replaceable"><code>jitter</code></em></code>] [<code class="option">-N <em class="replaceable"><code>soa-serial-format</code></em></code>] [<code class="option">-o <em class="replaceable"><code>origin</code></em></code>] [<code class="option">-O <em class="replaceable"><code>output-format</code></em></code>] [<code class="option">-p</code>] [<code class="option">-r <em class="replaceable"><code>randomdev</code></em></code>] [<code class="option">-s <em class="replaceable"><code>start-time</code></em></code>] [<code class="option">-t</code>] [<code class="option">-v <em class="replaceable"><code>level</code></em></code>] [<code class="option">-z</code>] {zonefile} [key...]</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2579912"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2580053"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">dnssec-signzone</strong></span>
|
||||
signs a zone. It generates
|
||||
NSEC and RRSIG records and produces a signed version of the
|
||||
|
|
@ -61,7 +61,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2579931"></a><h2>OPTIONS</h2>
|
||||
<a name="id2580072"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-a</span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -257,7 +257,7 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2586078"></a><h2>EXAMPLE</h2>
|
||||
<a name="id2583966"></a><h2>EXAMPLE</h2>
|
||||
<p>
|
||||
The following command signs the <strong class="userinput"><code>example.com</code></strong>
|
||||
zone with the DSA key generated in the <span><strong class="command">dnssec-keygen</strong></span>
|
||||
|
|
@ -283,14 +283,14 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2586144"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2584032"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">dnssec-keygen</span>(8)</span>,
|
||||
<em class="citetitle">BIND 9 Administrator Reference Manual</em>,
|
||||
<em class="citetitle">RFC 2535</em>.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2586168"></a><h2>AUTHOR</h2>
|
||||
<a name="id2584056"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.host.html,v 1.28 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.host.html,v 1.29 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">host</code> [<code class="option">-aCdlnrsTwv</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-N <em class="replaceable"><code>ndots</code></em></code>] [<code class="option">-R <em class="replaceable"><code>number</code></em></code>] [<code class="option">-t <em class="replaceable"><code>type</code></em></code>] [<code class="option">-W <em class="replaceable"><code>wait</code></em></code>] [<code class="option">-m <em class="replaceable"><code>flag</code></em></code>] [<code class="option">-4</code>] [<code class="option">-6</code>] {name} [server]</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2577762"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2577698"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">host</strong></span>
|
||||
is a simple utility for performing DNS lookups.
|
||||
It is normally used to convert names to IP addresses and vice versa.
|
||||
|
|
@ -202,7 +202,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2578139"></a><h2>IDN SUPPORT</h2>
|
||||
<a name="id2578144"></a><h2>IDN SUPPORT</h2>
|
||||
<p>
|
||||
If <span><strong class="command">host</strong></span> has been built with IDN (internationalized
|
||||
domain name) support, it can accept and display non-ASCII domain names.
|
||||
|
|
@ -216,12 +216,12 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584176"></a><h2>FILES</h2>
|
||||
<a name="id2578241"></a><h2>FILES</h2>
|
||||
<p><code class="filename">/etc/resolv.conf</code>
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584189"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2578254"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">dig</span>(1)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>.
|
||||
</p>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.named-checkconf.html,v 1.28 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.named-checkconf.html,v 1.29 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -50,14 +50,14 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">named-checkconf</code> [<code class="option">-v</code>] [<code class="option">-j</code>] [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>] {filename} [<code class="option">-z</code>]</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2578700"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2580821"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">named-checkconf</strong></span>
|
||||
checks the syntax, but not the semantics, of a named
|
||||
configuration file.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2580421"></a><h2>OPTIONS</h2>
|
||||
<a name="id2580835"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-t <em class="replaceable"><code>directory</code></em></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -88,20 +88,20 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2580522"></a><h2>RETURN VALUES</h2>
|
||||
<a name="id2580936"></a><h2>RETURN VALUES</h2>
|
||||
<p><span><strong class="command">named-checkconf</strong></span>
|
||||
returns an exit status of 1 if
|
||||
errors were detected and 0 otherwise.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2580536"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2580950"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2580557"></a><h2>AUTHOR</h2>
|
||||
<a name="id2580971"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.named-checkzone.html,v 1.30 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.named-checkzone.html,v 1.31 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -51,7 +51,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">named-compilezone</code> [<code class="option">-d</code>] [<code class="option">-j</code>] [<code class="option">-q</code>] [<code class="option">-v</code>] [<code class="option">-c <em class="replaceable"><code>class</code></em></code>] [<code class="option">-C <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-f <em class="replaceable"><code>format</code></em></code>] [<code class="option">-F <em class="replaceable"><code>format</code></em></code>] [<code class="option">-i <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-k <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-m <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-n <em class="replaceable"><code>mode</code></em></code>] [<code class="option">-o <em class="replaceable"><code>filename</code></em></code>] [<code class="option">-s <em class="replaceable"><code>style</code></em></code>] [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-w <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-D</code>] [<code class="option">-W <em class="replaceable"><code>mode</code></em></code>] {zonename} {filename}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2581207"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2581962"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">named-checkzone</strong></span>
|
||||
checks the syntax and integrity of a zone file. It performs the
|
||||
same checks as <span><strong class="command">named</strong></span> does when loading a
|
||||
|
|
@ -71,7 +71,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2603376"></a><h2>OPTIONS</h2>
|
||||
<a name="id2582081"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-d</span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -251,21 +251,21 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2619721"></a><h2>RETURN VALUES</h2>
|
||||
<a name="id2604638"></a><h2>RETURN VALUES</h2>
|
||||
<p><span><strong class="command">named-checkzone</strong></span>
|
||||
returns an exit status of 1 if
|
||||
errors were detected and 0 otherwise.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2619735"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2604652"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
<em class="citetitle">RFC 1035</em>,
|
||||
<em class="citetitle">BIND 9 Administrator Reference Manual</em>.
|
||||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2619760"></a><h2>AUTHOR</h2>
|
||||
<a name="id2604677"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.named.html,v 1.31 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.named.html,v 1.32 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">named</code> [<code class="option">-4</code>] [<code class="option">-6</code>] [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>] [<code class="option">-d <em class="replaceable"><code>debug-level</code></em></code>] [<code class="option">-f</code>] [<code class="option">-g</code>] [<code class="option">-n <em class="replaceable"><code>#cpus</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-s</code>] [<code class="option">-t <em class="replaceable"><code>directory</code></em></code>] [<code class="option">-u <em class="replaceable"><code>user</code></em></code>] [<code class="option">-v</code>] [<code class="option">-x <em class="replaceable"><code>cache-file</code></em></code>]</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2581613"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2582300"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">named</strong></span>
|
||||
is a Domain Name System (DNS) server,
|
||||
part of the BIND 9 distribution from ISC. For more
|
||||
|
|
@ -65,7 +65,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2581644"></a><h2>OPTIONS</h2>
|
||||
<a name="id2582331"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-4</span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -198,7 +198,7 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2582151"></a><h2>SIGNALS</h2>
|
||||
<a name="id2584408"></a><h2>SIGNALS</h2>
|
||||
<p>
|
||||
In routine operation, signals should not be used to control
|
||||
the nameserver; <span><strong class="command">rndc</strong></span> should be used
|
||||
|
|
@ -219,7 +219,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2604661"></a><h2>CONFIGURATION</h2>
|
||||
<a name="id2586643"></a><h2>CONFIGURATION</h2>
|
||||
<p>
|
||||
The <span><strong class="command">named</strong></span> configuration file is too complex
|
||||
to describe in detail here. A complete description is provided
|
||||
|
|
@ -228,7 +228,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2604680"></a><h2>FILES</h2>
|
||||
<a name="id2586662"></a><h2>FILES</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term"><code class="filename">/etc/named.conf</code></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -241,7 +241,7 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2604724"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2586706"></a><h2>SEE ALSO</h2>
|
||||
<p><em class="citetitle">RFC 1033</em>,
|
||||
<em class="citetitle">RFC 1034</em>,
|
||||
<em class="citetitle">RFC 1035</em>,
|
||||
|
|
@ -252,7 +252,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2604775"></a><h2>AUTHOR</h2>
|
||||
<a name="id2586757"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.rndc-confgen.html,v 1.31 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.rndc-confgen.html,v 1.32 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -48,7 +48,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">rndc-confgen</code> [<code class="option">-a</code>] [<code class="option">-b <em class="replaceable"><code>keysize</code></em></code>] [<code class="option">-c <em class="replaceable"><code>keyfile</code></em></code>] [<code class="option">-h</code>] [<code class="option">-k <em class="replaceable"><code>keyname</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-r <em class="replaceable"><code>randomfile</code></em></code>] [<code class="option">-s <em class="replaceable"><code>address</code></em></code>] [<code class="option">-t <em class="replaceable"><code>chrootdir</code></em></code>] [<code class="option">-u <em class="replaceable"><code>user</code></em></code>]</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2585063"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2586228"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">rndc-confgen</strong></span>
|
||||
generates configuration files
|
||||
for <span><strong class="command">rndc</strong></span>. It can be used as a
|
||||
|
|
@ -64,7 +64,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2585129"></a><h2>OPTIONS</h2>
|
||||
<a name="id2586294"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-a</span></dt>
|
||||
<dd>
|
||||
|
|
@ -171,7 +171,7 @@
|
|||
</dl></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2586403"></a><h2>EXAMPLES</h2>
|
||||
<a name="id2587226"></a><h2>EXAMPLES</h2>
|
||||
<p>
|
||||
To allow <span><strong class="command">rndc</strong></span> to be used with
|
||||
no manual configuration, run
|
||||
|
|
@ -188,7 +188,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2605028"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2587283"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">rndc</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">rndc.conf</span>(5)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
|
|
@ -196,7 +196,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2605066"></a><h2>AUTHOR</h2>
|
||||
<a name="id2606572"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.rndc.conf.html,v 1.31 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.rndc.conf.html,v 1.32 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">rndc.conf</code> </p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584379"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2579537"></a><h2>DESCRIPTION</h2>
|
||||
<p><code class="filename">rndc.conf</code> is the configuration file
|
||||
for <span><strong class="command">rndc</strong></span>, the BIND 9 name server control
|
||||
utility. This file has a similar structure and syntax to
|
||||
|
|
@ -135,7 +135,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584551"></a><h2>EXAMPLE</h2>
|
||||
<a name="id2585511"></a><h2>EXAMPLE</h2>
|
||||
<pre class="programlisting">
|
||||
options {
|
||||
default-server localhost;
|
||||
|
|
@ -209,7 +209,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584673"></a><h2>NAME SERVER CONFIGURATION</h2>
|
||||
<a name="id2586042"></a><h2>NAME SERVER CONFIGURATION</h2>
|
||||
<p>
|
||||
The name server must be configured to accept rndc connections and
|
||||
to recognize the key specified in the <code class="filename">rndc.conf</code>
|
||||
|
|
@ -219,7 +219,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584698"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2586068"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">rndc</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">rndc-confgen</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">mmencode</span>(1)</span>,
|
||||
|
|
@ -227,7 +227,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584737"></a><h2>AUTHOR</h2>
|
||||
<a name="id2586106"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
|
|
@ -14,7 +14,7 @@
|
|||
- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
|
||||
- PERFORMANCE OF THIS SOFTWARE.
|
||||
-->
|
||||
<!-- $Id: man.rndc.html,v 1.31 2006/06/04 23:38:17 marka Exp $ -->
|
||||
<!-- $Id: man.rndc.html,v 1.32 2006/06/08 02:44:05 marka Exp $ -->
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
|
|
@ -50,7 +50,7 @@
|
|||
<div class="cmdsynopsis"><p><code class="command">rndc</code> [<code class="option">-b <em class="replaceable"><code>source-address</code></em></code>] [<code class="option">-c <em class="replaceable"><code>config-file</code></em></code>] [<code class="option">-k <em class="replaceable"><code>key-file</code></em></code>] [<code class="option">-s <em class="replaceable"><code>server</code></em></code>] [<code class="option">-p <em class="replaceable"><code>port</code></em></code>] [<code class="option">-V</code>] [<code class="option">-y <em class="replaceable"><code>key_id</code></em></code>] {command}</p></div>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2582714"></a><h2>DESCRIPTION</h2>
|
||||
<a name="id2584630"></a><h2>DESCRIPTION</h2>
|
||||
<p><span><strong class="command">rndc</strong></span>
|
||||
controls the operation of a name
|
||||
server. It supersedes the <span><strong class="command">ndc</strong></span> utility
|
||||
|
|
@ -79,7 +79,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2582764"></a><h2>OPTIONS</h2>
|
||||
<a name="id2584680"></a><h2>OPTIONS</h2>
|
||||
<div class="variablelist"><dl>
|
||||
<dt><span class="term">-b <em class="replaceable"><code>source-address</code></em></span></dt>
|
||||
<dd><p>
|
||||
|
|
@ -152,7 +152,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2583939"></a><h2>LIMITATIONS</h2>
|
||||
<a name="id2585104"></a><h2>LIMITATIONS</h2>
|
||||
<p><span><strong class="command">rndc</strong></span>
|
||||
does not yet support all the commands of
|
||||
the BIND 8 <span><strong class="command">ndc</strong></span> utility.
|
||||
|
|
@ -166,7 +166,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584243"></a><h2>SEE ALSO</h2>
|
||||
<a name="id2585203"></a><h2>SEE ALSO</h2>
|
||||
<p><span class="citerefentry"><span class="refentrytitle">rndc.conf</span>(5)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named</span>(8)</span>,
|
||||
<span class="citerefentry"><span class="refentrytitle">named.conf</span>(5)</span>
|
||||
|
|
@ -175,7 +175,7 @@
|
|||
</p>
|
||||
</div>
|
||||
<div class="refsect1" lang="en">
|
||||
<a name="id2584290"></a><h2>AUTHOR</h2>
|
||||
<a name="id2585250"></a><h2>AUTHOR</h2>
|
||||
<p><span class="corpauthor">Internet Systems Consortium</span>
|
||||
</p>
|
||||
</div>
|
||||
|
|
|
|||
Loading…
Reference in a new issue