Bv9ARM.ch03.html revision 990d0e893f5b70e735cdf990af66e9ec6e91fa78
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<!--
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd - Copyright (C) 2004-2014 Internet Systems Consortium, Inc. ("ISC")
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd - Copyright (C) 2000-2003 Internet Software Consortium.
4a56677aad9b66a36f3dc9fddbca8dc1230ad471rbowen -
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd - Permission to use, copy, modify, and/or distribute this software for any
a3d2b657dd7ca66251b562b6a82c2335135b9172nd - purpose with or without fee is hereby granted, provided that the above
031b91a62d25106ae69d4693475c79618dd5e884fielding - copyright notice and this permission notice appear in all copies.
031b91a62d25106ae69d4693475c79618dd5e884fielding -
031b91a62d25106ae69d4693475c79618dd5e884fielding - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
031b91a62d25106ae69d4693475c79618dd5e884fielding - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
031b91a62d25106ae69d4693475c79618dd5e884fielding - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
031b91a62d25106ae69d4693475c79618dd5e884fielding - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
a3d2b657dd7ca66251b562b6a82c2335135b9172nd - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
a3d2b657dd7ca66251b562b6a82c2335135b9172nd - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
a3d2b657dd7ca66251b562b6a82c2335135b9172nd - PERFORMANCE OF THIS SOFTWARE.
a3d2b657dd7ca66251b562b6a82c2335135b9172nd-->
a3d2b657dd7ca66251b562b6a82c2335135b9172nd<!-- $Id$ -->
a3d2b657dd7ca66251b562b6a82c2335135b9172nd<html>
a3d2b657dd7ca66251b562b6a82c2335135b9172nd<head>
a3d2b657dd7ca66251b562b6a82c2335135b9172nd<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
a3d2b657dd7ca66251b562b6a82c2335135b9172nd<title>Chapter�3.�Name Server Configuration</title>
a3d2b657dd7ca66251b562b6a82c2335135b9172nd<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<link rel="prev" href="Bv9ARM.ch02.html" title="Chapter�2.�BIND Resource Requirements">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<link rel="next" href="Bv9ARM.ch04.html" title="Chapter�4.�Advanced DNS Features">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</head>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="navheader">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<table width="100%" summary="Navigation header">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<tr><th colspan="3" align="center">Chapter�3.�Name Server Configuration</th></tr>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<tr>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<td width="20%" align="left">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<a accesskey="p" href="Bv9ARM.ch02.html">Prev</a>�</td>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<th width="60%" align="center">�</th>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch04.html">Next</a>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</td>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</tr>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</table>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<hr>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="chapter" lang="en">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="titlepage"><div><div><h2 class="title">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<a name="Bv9ARM.ch03"></a>Chapter�3.�Name Server Configuration</h2></div></div></div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="toc">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<p><b>Table of Contents</b></p>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dl>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dt><span class="sect1"><a href="Bv9ARM.ch03.html#sample_configuration">Sample Configurations</a></span></dt>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dd><dl>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2567778">A Caching-only Name Server</a></span></dt>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2567998">An Authoritative-only Name Server</a></span></dt>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</dl></dd>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568021">Load Balancing</a></span></dt>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dt><span class="sect1"><a href="Bv9ARM.ch03.html#id2568375">Name Server Operations</a></span></dt>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dd><dl>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2568380">Tools for Use With the Name Server Daemon</a></span></dt>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<dt><span class="sect2"><a href="Bv9ARM.ch03.html#id2569449">Signals</a></span></dt>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</dl></dd>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</dl>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<p>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd In this chapter we provide some suggested configurations along
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd with guidelines for their use. We suggest reasonable values for
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd certain option settings.
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd </p>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="sect1" lang="en">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="titlepage"><div><div><h2 class="title" style="clear: both">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<a name="sample_configuration"></a>Sample Configurations</h2></div></div></div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="sect2" lang="en">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="titlepage"><div><div><h3 class="title">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<a name="id2567778"></a>A Caching-only Name Server</h3></div></div></div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<p>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd The following sample configuration is appropriate for a caching-only
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd name server for use by clients internal to a corporation. All
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd queries
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd from outside clients are refused using the <span><strong class="command">allow-query</strong></span>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd option. Alternatively, the same effect could be achieved using
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd suitable
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd firewall rules.
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd </p>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<pre class="programlisting">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd// Two corporate subnets we wish to allow queries from.
d78d735dbf7c5ce5ae545eecd8ee2c052224db77ndacl corpnets { 192.168.4.0/24; 192.168.7.0/24; };
d78d735dbf7c5ce5ae545eecd8ee2c052224db77ndoptions {
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd // Working directory
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd directory "/etc/namedb";
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd allow-query { corpnets; };
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd};
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd// Provide a reverse mapping for the loopback
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd// address 127.0.0.1
d78d735dbf7c5ce5ae545eecd8ee2c052224db77ndzone "0.0.127.in-addr.arpa" {
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd type master;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd file "localhost.rev";
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd notify no;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd};
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</pre>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="sect2" lang="en">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="titlepage"><div><div><h3 class="title">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<a name="id2567998"></a>An Authoritative-only Name Server</h3></div></div></div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<p>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd This sample configuration is for an authoritative-only server
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd that is the master server for "<code class="filename">example.com</code>"
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd and a slave for the subdomain "<code class="filename">eng.example.com</code>".
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd </p>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<pre class="programlisting">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77ndoptions {
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd // Working directory
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd directory "/etc/namedb";
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd // Do not allow access to cache
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd allow-query-cache { none; };
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd // This is the default
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd allow-query { any; };
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd // Do not provide recursive service
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd recursion no;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd};
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd// Provide a reverse mapping for the loopback
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd// address 127.0.0.1
d78d735dbf7c5ce5ae545eecd8ee2c052224db77ndzone "0.0.127.in-addr.arpa" {
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd type master;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd file "localhost.rev";
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd notify no;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd};
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd// We are the master server for example.com
d78d735dbf7c5ce5ae545eecd8ee2c052224db77ndzone "example.com" {
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd type master;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd file "example.com.db";
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd // IP addresses of slave servers allowed to
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd // transfer example.com
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd allow-transfer {
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd 192.168.4.14;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd 192.168.5.53;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd };
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd};
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd// We are a slave server for eng.example.com
d78d735dbf7c5ce5ae545eecd8ee2c052224db77ndzone "eng.example.com" {
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd type slave;
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd file "eng.example.com.bk";
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd // IP address of eng.example.com master server
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd masters { 192.168.4.12; };
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd};
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</pre>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd</div>
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="sect1" lang="en">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<div class="titlepage"><div><div><h2 class="title" style="clear: both">
d78d735dbf7c5ce5ae545eecd8ee2c052224db77nd<a name="id2568021"></a>Load Balancing</h2></div></div></div>
<p>
A primitive form of load balancing can be achieved in
the <acronym class="acronym">DNS</acronym> by using multiple records
(such as multiple A records) for one name.
</p>
<p>
For example, if you have three WWW servers with network addresses
of 10.0.0.1, 10.0.0.2 and 10.0.0.3, a set of records such as the
following means that clients will connect to each machine one third
of the time:
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
<col>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p>
Name
</p>
</td>
<td>
<p>
TTL
</p>
</td>
<td>
<p>
CLASS
</p>
</td>
<td>
<p>
TYPE
</p>
</td>
<td>
<p>
Resource Record (RR) Data
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="literal">www</code>
</p>
</td>
<td>
<p>
<code class="literal">600</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.0.0.1</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">600</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.0.0.2</code>
</p>
</td>
</tr>
<tr>
<td>
<p></p>
</td>
<td>
<p>
<code class="literal">600</code>
</p>
</td>
<td>
<p>
<code class="literal">IN</code>
</p>
</td>
<td>
<p>
<code class="literal">A</code>
</p>
</td>
<td>
<p>
<code class="literal">10.0.0.3</code>
</p>
</td>
</tr>
</tbody>
</table></div>
<p>
When a resolver queries for these records, <acronym class="acronym">BIND</acronym> will rotate
them and respond to the query with the records in a different
order. In the example above, clients will randomly receive
records in the order 1, 2, 3; 2, 3, 1; and 3, 1, 2. Most clients
will use the first record returned and discard the rest.
</p>
<p>
For more detail on ordering responses, check the
<span><strong class="command">rrset-order</strong></span> sub-statement in the
<span><strong class="command">options</strong></span> statement, see
<a href="Bv9ARM.ch06.html#rrset_ordering">RRset Ordering</a>.
</p>
</div>
<div class="sect1" lang="en">
<div class="titlepage"><div><div><h2 class="title" style="clear: both">
<a name="id2568375"></a>Name Server Operations</h2></div></div></div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2568380"></a>Tools for Use With the Name Server Daemon</h3></div></div></div>
<p>
This section describes several indispensable diagnostic,
administrative and monitoring tools available to the system
administrator for controlling and debugging the name server
daemon.
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="diagnostic_tools"></a>Diagnostic Tools</h4></div></div></div>
<p>
The <span><strong class="command">dig</strong></span>, <span><strong class="command">host</strong></span>, and
<span><strong class="command">nslookup</strong></span> programs are all command
line tools
for manually querying name servers. They differ in style and
output format.
</p>
<div class="variablelist"><dl>
<dt><span class="term"><a name="dig"></a><span><strong class="command">dig</strong></span></span></dt>
<dd>
<p>
The domain information groper (<span><strong class="command">dig</strong></span>)
is the most versatile and complete of these lookup tools.
It has two modes: simple interactive
mode for a single query, and batch mode which executes a
query for
each in a list of several query lines. All query options are
accessible
from the command line.
</p>
<div class="cmdsynopsis"><p><code class="command">dig</code> [@<em class="replaceable"><code>server</code></em>] <em class="replaceable"><code>domain</code></em> [<em class="replaceable"><code>query-type</code></em>] [<em class="replaceable"><code>query-class</code></em>] [+<em class="replaceable"><code>query-option</code></em>] [-<em class="replaceable"><code>dig-option</code></em>] [%<em class="replaceable"><code>comment</code></em>]</p></div>
<p>
The usual simple use of <span><strong class="command">dig</strong></span> will take the form
</p>
<p>
<span><strong class="command">dig @server domain query-type query-class</strong></span>
</p>
<p>
For more information and a list of available commands and
options, see the <span><strong class="command">dig</strong></span> man
page.
</p>
</dd>
<dt><span class="term"><span><strong class="command">host</strong></span></span></dt>
<dd>
<p>
The <span><strong class="command">host</strong></span> utility emphasizes
simplicity
and ease of use. By default, it converts
between host names and Internet addresses, but its
functionality
can be extended with the use of options.
</p>
<div class="cmdsynopsis"><p><code class="command">host</code> [-aCdlnrsTwv] [-c <em class="replaceable"><code>class</code></em>] [-N <em class="replaceable"><code>ndots</code></em>] [-t <em class="replaceable"><code>type</code></em>] [-W <em class="replaceable"><code>timeout</code></em>] [-R <em class="replaceable"><code>retries</code></em>] [-m <em class="replaceable"><code>flag</code></em>] [-4] [-6] <em class="replaceable"><code>hostname</code></em> [<em class="replaceable"><code>server</code></em>]</p></div>
<p>
For more information and a list of available commands and
options, see the <span><strong class="command">host</strong></span> man
page.
</p>
</dd>
<dt><span class="term"><span><strong class="command">nslookup</strong></span></span></dt>
<dd>
<p><span><strong class="command">nslookup</strong></span>
has two modes: interactive and
non-interactive. Interactive mode allows the user to
query name servers for information about various
hosts and domains or to print a list of hosts in a
domain. Non-interactive mode is used to print just
the name and requested information for a host or
domain.
</p>
<div class="cmdsynopsis"><p><code class="command">nslookup</code> [-option...] [[<em class="replaceable"><code>host-to-find</code></em>] | [- [server]]]</p></div>
<p>
Interactive mode is entered when no arguments are given (the
default name server will be used) or when the first argument
is a
hyphen (`-') and the second argument is the host name or
Internet address
of a name server.
</p>
<p>
Non-interactive mode is used when the name or Internet
address
of the host to be looked up is given as the first argument.
The
optional second argument specifies the host name or address
of a name server.
</p>
<p>
Due to its arcane user interface and frequently inconsistent
behavior, we do not recommend the use of <span><strong class="command">nslookup</strong></span>.
Use <span><strong class="command">dig</strong></span> instead.
</p>
</dd>
</dl></div>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="admin_tools"></a>Administrative Tools</h4></div></div></div>
<p>
Administrative tools play an integral part in the management
of a server.
</p>
<div class="variablelist"><dl>
<dt>
<a name="named-checkconf"></a><span class="term"><span><strong class="command">named-checkconf</strong></span></span>
</dt>
<dd>
<p>
The <span><strong class="command">named-checkconf</strong></span> program
checks the syntax of a <code class="filename">named.conf</code> file.
</p>
<div class="cmdsynopsis"><p><code class="command">named-checkconf</code> [-jvz] [-t <em class="replaceable"><code>directory</code></em>] [<em class="replaceable"><code>filename</code></em>]</p></div>
</dd>
<dt>
<a name="named-checkzone"></a><span class="term"><span><strong class="command">named-checkzone</strong></span></span>
</dt>
<dd>
<p>
The <span><strong class="command">named-checkzone</strong></span> program
checks a master file for
syntax and consistency.
</p>
<div class="cmdsynopsis"><p><code class="command">named-checkzone</code> [-djqvD] [-c <em class="replaceable"><code>class</code></em>] [-o <em class="replaceable"><code>output</code></em>] [-t <em class="replaceable"><code>directory</code></em>] [-w <em class="replaceable"><code>directory</code></em>] [-k <em class="replaceable"><code>(ignore|warn|fail)</code></em>] [-n <em class="replaceable"><code>(ignore|warn|fail)</code></em>] [-W <em class="replaceable"><code>(ignore|warn)</code></em>] <em class="replaceable"><code>zone</code></em> [<em class="replaceable"><code>filename</code></em>]</p></div>
</dd>
<dt>
<a name="named-compilezone"></a><span class="term"><span><strong class="command">named-compilezone</strong></span></span>
</dt>
<dd><p>
Similar to <span><strong class="command">named-checkzone,</strong></span> but
it always dumps the zone content to a specified file
(typically in a different format).
</p></dd>
<dt>
<a name="rndc"></a><span class="term"><span><strong class="command">rndc</strong></span></span>
</dt>
<dd>
<p>
The remote name daemon control
(<span><strong class="command">rndc</strong></span>) program allows the
system
administrator to control the operation of a name server.
Since <acronym class="acronym">BIND</acronym> 9.2, <span><strong class="command">rndc</strong></span>
supports all the commands of the BIND 8 <span><strong class="command">ndc</strong></span>
utility except <span><strong class="command">ndc start</strong></span> and
<span><strong class="command">ndc restart</strong></span>, which were also
not supported in <span><strong class="command">ndc</strong></span>'s
channel mode.
If you run <span><strong class="command">rndc</strong></span> without any
options
it will display a usage message as follows:
</p>
<div class="cmdsynopsis"><p><code class="command">rndc</code> [-c <em class="replaceable"><code>config</code></em>] [-s <em class="replaceable"><code>server</code></em>] [-p <em class="replaceable"><code>port</code></em>] [-y <em class="replaceable"><code>key</code></em>] <em class="replaceable"><code>command</code></em> [<em class="replaceable"><code>command</code></em>...]</p></div>
<p>See <a href="man.rndc.html" title="rndc"><span class="refentrytitle"><span class="application">rndc</span></span>(8)</a> for details of
the available <span><strong class="command">rndc</strong></span> commands.
</p>
<p>
<span><strong class="command">rndc</strong></span> requires a configuration file,
since all
communication with the server is authenticated with
digital signatures that rely on a shared secret, and
there is no way to provide that secret other than with a
configuration file. The default location for the
<span><strong class="command">rndc</strong></span> configuration file is
<code class="filename">/etc/rndc.conf</code>, but an
alternate
location can be specified with the <code class="option">-c</code>
option. If the configuration file is not found,
<span><strong class="command">rndc</strong></span> will also look in
<code class="filename">/etc/rndc.key</code> (or whatever
<code class="varname">sysconfdir</code> was defined when
the <acronym class="acronym">BIND</acronym> build was
configured).
The <code class="filename">rndc.key</code> file is
generated by
running <span><strong class="command">rndc-confgen -a</strong></span> as
described in
<a href="Bv9ARM.ch06.html#controls_statement_definition_and_usage" title="controls Statement Definition and
Usage">the section called &#8220;<span><strong class="command">controls</strong></span> Statement Definition and
Usage&#8221;</a>.
</p>
<p>
The format of the configuration file is similar to
that of <code class="filename">named.conf</code>, but
limited to
only four statements, the <span><strong class="command">options</strong></span>,
<span><strong class="command">key</strong></span>, <span><strong class="command">server</strong></span> and
<span><strong class="command">include</strong></span>
statements. These statements are what associate the
secret keys to the servers with which they are meant to
be shared. The order of statements is not
significant.
</p>
<p>
The <span><strong class="command">options</strong></span> statement has
three clauses:
<span><strong class="command">default-server</strong></span>, <span><strong class="command">default-key</strong></span>,
and <span><strong class="command">default-port</strong></span>.
<span><strong class="command">default-server</strong></span> takes a
host name or address argument and represents the server
that will
be contacted if no <code class="option">-s</code>
option is provided on the command line.
<span><strong class="command">default-key</strong></span> takes
the name of a key as its argument, as defined by a <span><strong class="command">key</strong></span> statement.
<span><strong class="command">default-port</strong></span> specifies the
port to which
<span><strong class="command">rndc</strong></span> should connect if no
port is given on the command line or in a
<span><strong class="command">server</strong></span> statement.
</p>
<p>
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
<span><strong class="command">named</strong></span>. Its syntax is
identical to the
<span><strong class="command">key</strong></span> statement in <code class="filename">named.conf</code>.
The keyword <strong class="userinput"><code>key</code></strong> is
followed by a key name, which must be a valid
domain name, though it need not actually be hierarchical;
thus,
a string like "<strong class="userinput"><code>rndc_key</code></strong>" is a valid
name.
The <span><strong class="command">key</strong></span> statement has two
clauses:
<span><strong class="command">algorithm</strong></span> and <span><strong class="command">secret</strong></span>.
While the configuration parser will accept any string as the
argument
to algorithm, currently only the strings
"<strong class="userinput"><code>hmac-md5</code></strong>",
"<strong class="userinput"><code>hmac-sha1</code></strong>",
"<strong class="userinput"><code>hmac-sha224</code></strong>",
"<strong class="userinput"><code>hmac-sha256</code></strong>",
"<strong class="userinput"><code>hmac-sha384</code></strong>"
and "<strong class="userinput"><code>hmac-sha512</code></strong>"
have any meaning. The secret is a base-64 encoded string
as specified in RFC 3548.
</p>
<p>
The <span><strong class="command">server</strong></span> statement
associates a key
defined using the <span><strong class="command">key</strong></span>
statement with a server.
The keyword <strong class="userinput"><code>server</code></strong> is followed by a
host name or address. The <span><strong class="command">server</strong></span> statement
has two clauses: <span><strong class="command">key</strong></span> and <span><strong class="command">port</strong></span>.
The <span><strong class="command">key</strong></span> clause specifies the
name of the key
to be used when communicating with this server, and the
<span><strong class="command">port</strong></span> clause can be used to
specify the port <span><strong class="command">rndc</strong></span> should
connect
to on the server.
</p>
<p>
A sample minimal configuration file is as follows:
</p>
<pre class="programlisting">
key rndc_key {
algorithm "hmac-sha256";
secret
"c3Ryb25nIGVub3VnaCBmb3IgYSBtYW4gYnV0IG1hZGUgZm9yIGEgd29tYW4K";
};
options {
default-server 127.0.0.1;
default-key rndc_key;
};
</pre>
<p>
This file, if installed as <code class="filename">/etc/rndc.conf</code>,
would allow the command:
</p>
<p>
<code class="prompt">$ </code><strong class="userinput"><code>rndc reload</code></strong>
</p>
<p>
to connect to 127.0.0.1 port 953 and cause the name server
to reload, if a name server on the local machine were
running with
following controls statements:
</p>
<pre class="programlisting">
controls {
inet 127.0.0.1
allow { localhost; } keys { rndc_key; };
};
</pre>
<p>
and it had an identical key statement for
<code class="literal">rndc_key</code>.
</p>
<p>
Running the <span><strong class="command">rndc-confgen</strong></span>
program will
conveniently create a <code class="filename">rndc.conf</code>
file for you, and also display the
corresponding <span><strong class="command">controls</strong></span>
statement that you need to
add to <code class="filename">named.conf</code>.
Alternatively,
you can run <span><strong class="command">rndc-confgen -a</strong></span>
to set up
a <code class="filename">rndc.key</code> file and not
modify
<code class="filename">named.conf</code> at all.
</p>
</dd>
</dl></div>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2569449"></a>Signals</h3></div></div></div>
<p>
Certain UNIX signals cause the name server to take specific
actions, as described in the following table. These signals can
be sent using the <span><strong class="command">kill</strong></span> command.
</p>
<div class="informaltable"><table border="1">
<colgroup>
<col>
<col>
</colgroup>
<tbody>
<tr>
<td>
<p><span><strong class="command">SIGHUP</strong></span></p>
</td>
<td>
<p>
Causes the server to read <code class="filename">named.conf</code> and
reload the database.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">SIGTERM</strong></span></p>
</td>
<td>
<p>
Causes the server to clean up and exit.
</p>
</td>
</tr>
<tr>
<td>
<p><span><strong class="command">SIGINT</strong></span></p>
</td>
<td>
<p>
Causes the server to clean up and exit.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="Bv9ARM.ch02.html">Prev</a>�</td>
<td width="20%" align="center">�</td>
<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch04.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">Chapter�2.�<acronym class="acronym">BIND</acronym> Resource Requirements�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�Chapter�4.�Advanced DNS Features</td>
</tr>
</table>
</div>
</body>
</html>