Bv9ARM.ch01.html revision 71c66a876ecca77923638d3f94cc0783152b2f03
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<!--
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - Copyright (C) 2004-2006 Internet Systems Consortium, Inc. ("ISC")
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - Copyright (C) 2000-2003 Internet Software Consortium.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews -
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - Permission to use, copy, modify, and distribute this software for any
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - purpose with or without fee is hereby granted, provided that the above
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - copyright notice and this permission notice appear in all copies.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews -
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews - PERFORMANCE OF THIS SOFTWARE.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews-->
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<!-- $Id: Bv9ARM.ch01.html,v 1.30 2006/06/29 13:03:32 marka Exp $ -->
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<html>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<head>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<title>Chapter�1.�Introduction</title>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<meta name="generator" content="DocBook XSL Stylesheets V1.70.1">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<link rel="prev" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<link rel="next" href="Bv9ARM.ch02.html" title="Chapter�2.�BIND Resource Requirements">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</head>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="navheader">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<table width="100%" summary="Navigation header">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr><th colspan="3" align="center">Chapter�1.�Introduction</th></tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td width="20%" align="left">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a accesskey="p" href="Bv9ARM.html">Prev</a>�</td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<th width="60%" align="center">�</th>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch02.html">Next</a>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</table>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<hr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="chapter" lang="en">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="titlepage"><div><div><h2 class="title">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a name="Bv9ARM.ch01"></a>Chapter�1.�Introduction</h2></div></div></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="toc">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p><b>Table of Contents</b></p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dl>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2569838">Scope of Document</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2568778">Organization of This Document</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2569737">Conventions Used in This Document</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect1"><a href="Bv9ARM.ch01.html#id2570192">The Domain Name System (<acronym class="acronym">DNS</acronym>)</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dd><dl>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570213">DNS Fundamentals</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570247">Domains and Domain Names</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2570331">Zones</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2572661">Authoritative Name Servers</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2572970">Caching Name Servers</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<dt><span class="sect2"><a href="Bv9ARM.ch01.html#id2573032">Name Servers in Multiple Roles</a></span></dt>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</dl></dd>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</dl>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The Internet Domain Name System (<acronym class="acronym">DNS</acronym>)
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews consists of the syntax
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews to specify the names of entities in the Internet in a hierarchical
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews manner, the rules used for delegating authority over names, and the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews system implementation that actually maps names to Internet
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews addresses. <acronym class="acronym">DNS</acronym> data is maintained in a
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews group of distributed
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews hierarchical databases.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="sect1" lang="en">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="titlepage"><div><div><h2 class="title" style="clear: both">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a name="id2569838"></a>Scope of Document</h2></div></div></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The Berkeley Internet Name Domain
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews (<acronym class="acronym">BIND</acronym>) implements an
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews domain name server for a number of operating systems. This
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews document provides basic information about the installation and
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews care of the Internet Systems Consortium (<acronym class="acronym">ISC</acronym>)
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <acronym class="acronym">BIND</acronym> version 9 software package for
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews system administrators.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews This version of the manual corresponds to BIND version 9.4.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="sect1" lang="en">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="titlepage"><div><div><h2 class="title" style="clear: both">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a name="id2568778"></a>Organization of This Document</h2></div></div></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews In this document, <span class="emphasis"><em>Section 1</em></span> introduces
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews the basic <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym> concepts. <span class="emphasis"><em>Section 2</em></span>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews describes resource requirements for running <acronym class="acronym">BIND</acronym> in various
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews environments. Information in <span class="emphasis"><em>Section 3</em></span> is
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>task-oriented</em></span> in its presentation and is
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews organized functionally, to aid in the process of installing the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <acronym class="acronym">BIND</acronym> 9 software. The task-oriented
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews section is followed by
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>Section 4</em></span>, which contains more advanced
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews concepts that the system administrator may need for implementing
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews certain options. <span class="emphasis"><em>Section 5</em></span>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews describes the <acronym class="acronym">BIND</acronym> 9 lightweight
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews resolver. The contents of <span class="emphasis"><em>Section 6</em></span> are
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews organized as in a reference manual to aid in the ongoing
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews maintenance of the software. <span class="emphasis"><em>Section 7</em></span> addresses
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews security considerations, and
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>Section 8</em></span> contains troubleshooting help. The
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews main body of the document is followed by several
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>Appendices</em></span> which contain useful reference
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews information, such as a <span class="emphasis"><em>Bibliography</em></span> and
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews historic information related to <acronym class="acronym">BIND</acronym>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews and the Domain Name
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews System.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="sect1" lang="en">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="titlepage"><div><div><h2 class="title" style="clear: both">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a name="id2569737"></a>Conventions Used in This Document</h2></div></div></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews In this document, we use the following general typographic
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews conventions:
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="informaltable"><table border="1">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<colgroup>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<col>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<col>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</colgroup>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tbody>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>To describe:</em></span>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>We use the style:</em></span>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews a pathname, filename, URL, hostname,
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews mailing list name, or new term or concept
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <code class="filename">Fixed width</code>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews literal user
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews input
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <strong class="userinput"><code>Fixed Width Bold</code></strong>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews program output
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <code class="computeroutput">Fixed Width</code>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tbody>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</table></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The following conventions are used in descriptions of the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <acronym class="acronym">BIND</acronym> configuration file:</p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="informaltable"><table border="1">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<colgroup>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<col>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<col>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</colgroup>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tbody>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>To describe:</em></span>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>We use the style:</em></span>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews keywords
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <code class="literal">Fixed Width</code>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews variables
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <code class="varname">Fixed Width</code>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews Optional input
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews [<span class="optional">Text is enclosed in square brackets</span>]
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </td>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tr>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</tbody>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</table></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="sect1" lang="en">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="titlepage"><div><div><h2 class="title" style="clear: both">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a name="id2570192"></a>The Domain Name System (<acronym class="acronym">DNS</acronym>)</h2></div></div></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The purpose of this document is to explain the installation
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews and upkeep of the <acronym class="acronym">BIND</acronym> software
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews package, and we
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews begin by reviewing the fundamentals of the Domain Name System
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews (<acronym class="acronym">DNS</acronym>) as they relate to <acronym class="acronym">BIND</acronym>.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="sect2" lang="en">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="titlepage"><div><div><h3 class="title">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a name="id2570213"></a>DNS Fundamentals</h3></div></div></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The Domain Name System (DNS) is a hierarchical, distributed
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews database. It stores information for mapping Internet host names to
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews IP
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews addresses and vice versa, mail routing information, and other data
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews used by Internet applications.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews Clients look up information in the DNS by calling a
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>resolver</em></span> library, which sends queries to one or
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews more <span class="emphasis"><em>name servers</em></span> and interprets the responses.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The <acronym class="acronym">BIND</acronym> 9 software distribution
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews contains a
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews name server, <span><strong class="command">named</strong></span>, and two resolver
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews libraries, <span><strong class="command">liblwres</strong></span> and <span><strong class="command">libbind</strong></span>.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="sect2" lang="en">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="titlepage"><div><div><h3 class="title">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a name="id2570247"></a>Domains and Domain Names</h3></div></div></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The data stored in the DNS is identified by <span class="emphasis"><em>domain names</em></span> that are organized as a tree according to
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews organizational or administrative boundaries. Each node of the tree,
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews called a <span class="emphasis"><em>domain</em></span>, is given a label. The domain
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews name of the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews node is the concatenation of all the labels on the path from the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews node to the <span class="emphasis"><em>root</em></span> node. This is represented
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews in written form as a string of labels listed from right to left and
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews separated by dots. A label need only be unique within its parent
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews domain.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews For example, a domain name for a host at the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews company <span class="emphasis"><em>Example, Inc.</em></span> could be
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <code class="literal">ourhost.example.com</code>,
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews where <code class="literal">com</code> is the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews top level domain to which
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <code class="literal">ourhost.example.com</code> belongs,
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <code class="literal">example</code> is
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews a subdomain of <code class="literal">com</code>, and
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <code class="literal">ourhost</code> is the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews name of the host.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews For administrative purposes, the name space is partitioned into
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews areas called <span class="emphasis"><em>zones</em></span>, each starting at a node and
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews extending down to the leaf nodes or to nodes where other zones
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews start.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The data for each zone is stored in a <span class="emphasis"><em>name server</em></span>, which answers queries about the zone using the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>DNS protocol</em></span>.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews The data associated with each domain name is stored in the
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews form of <span class="emphasis"><em>resource records</em></span> (<acronym class="acronym">RR</acronym>s).
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews Some of the supported resource record types are described in
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <a href="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them" title="Types of Resource Records and When to Use Them">the section called &#8220;Types of Resource Records and When to Use Them&#8221;</a>.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews For more detailed information about the design of the DNS and
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews the DNS protocol, please refer to the standards documents listed in
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <a href="Bv9ARM.ch09.html#rfcs" title="Request for Comments (RFCs)">the section called &#8220;Request for Comments (RFCs)&#8221;</a>.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews</div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="sect2" lang="en">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<div class="titlepage"><div><div><h3 class="title">
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<a name="id2570331"></a>Zones</h3></div></div></div>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews To properly operate a name server, it is important to understand
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews the difference between a <span class="emphasis"><em>zone</em></span>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews and a <span class="emphasis"><em>domain</em></span>.
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews </p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews<p>
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews As stated previously, a zone is a point of delegation in
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews the <acronym class="acronym">DNS</acronym> tree. A zone consists of
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews those contiguous parts of the domain
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews tree for which a name server has complete information and over which
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews it has authority. It contains all domain names from a certain point
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews downward in the domain tree except those which are delegated to
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews other zones. A delegation point is marked by one or more
ac0680e9ebb2dc4235e4381232c457876fae792fMark Andrews <span class="emphasis"><em>NS records</em></span> in the
parent zone, which should be matched by equivalent NS records at
the root of the delegated zone.
</p>
<p>
For instance, consider the <code class="literal">example.com</code>
domain which includes names
such as <code class="literal">host.aaa.example.com</code> and
<code class="literal">host.bbb.example.com</code> even though
the <code class="literal">example.com</code> zone includes
only delegations for the <code class="literal">aaa.example.com</code> and
<code class="literal">bbb.example.com</code> zones. A zone can
map
exactly to a single domain, but could also include only part of a
domain, the rest of which could be delegated to other
name servers. Every name in the <acronym class="acronym">DNS</acronym>
tree is a
<span class="emphasis"><em>domain</em></span>, even if it is
<span class="emphasis"><em>terminal</em></span>, that is, has no
<span class="emphasis"><em>subdomains</em></span>. Every subdomain is a domain and
every domain except the root is also a subdomain. The terminology is
not intuitive and we suggest that you read RFCs 1033, 1034 and 1035
to
gain a complete understanding of this difficult and subtle
topic.
</p>
<p>
Though <acronym class="acronym">BIND</acronym> is called a "domain name
server",
it deals primarily in terms of zones. The master and slave
declarations in the <code class="filename">named.conf</code> file
specify
zones, not domains. When you ask some other site if it is willing to
be a slave server for your <span class="emphasis"><em>domain</em></span>, you are
actually asking for slave service for some collection of zones.
</p>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2572661"></a>Authoritative Name Servers</h3></div></div></div>
<p>
Each zone is served by at least
one <span class="emphasis"><em>authoritative name server</em></span>,
which contains the complete data for the zone.
To make the DNS tolerant of server and network failures,
most zones have two or more authoritative servers, on
different networks.
</p>
<p>
Responses from authoritative servers have the "authoritative
answer" (AA) bit set in the response packets. This makes them
easy to identify when debugging DNS configurations using tools like
<span><strong class="command">dig</strong></span> (<a href="Bv9ARM.ch03.html#diagnostic_tools" title="Diagnostic Tools">the section called &#8220;Diagnostic Tools&#8221;</a>).
</p>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2572684"></a>The Primary Master</h4></div></div></div>
<p>
The authoritative server where the master copy of the zone
data is maintained is called the
<span class="emphasis"><em>primary master</em></span> server, or simply the
<span class="emphasis"><em>primary</em></span>. Typically it loads the zone
contents from some local file edited by humans or perhaps
generated mechanically from some other local file which is
edited by humans. This file is called the
<span class="emphasis"><em>zone file</em></span> or
<span class="emphasis"><em>master file</em></span>.
</p>
<p>
In some cases, however, the master file may not be edited
by humans at all, but may instead be the result of
<span class="emphasis"><em>dynamic update</em></span> operations.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2572714"></a>Slave Servers</h4></div></div></div>
<p>
The other authoritative servers, the <span class="emphasis"><em>slave</em></span>
servers (also known as <span class="emphasis"><em>secondary</em></span> servers)
load
the zone contents from another server using a replication process
known as a <span class="emphasis"><em>zone transfer</em></span>. Typically the data
are
transferred directly from the primary master, but it is also
possible
to transfer it from another slave. In other words, a slave server
may itself act as a master to a subordinate slave server.
</p>
</div>
<div class="sect3" lang="en">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2572736"></a>Stealth Servers</h4></div></div></div>
<p>
Usually all of the zone's authoritative servers are listed in
NS records in the parent zone. These NS records constitute
a <span class="emphasis"><em>delegation</em></span> of the zone from the parent.
The authoritative servers are also listed in the zone file itself,
at the <span class="emphasis"><em>top level</em></span> or <span class="emphasis"><em>apex</em></span>
of the zone. You can list servers in the zone's top-level NS
records that are not in the parent's NS delegation, but you cannot
list servers in the parent's delegation that are not present at
the zone's top level.
</p>
<p>
A <span class="emphasis"><em>stealth server</em></span> is a server that is
authoritative for a zone but is not listed in that zone's NS
records. Stealth servers can be used for keeping a local copy of
a
zone to speed up access to the zone's records or to make sure that
the
zone is available even if all the "official" servers for the zone
are
inaccessible.
</p>
<p>
A configuration where the primary master server itself is a
stealth server is often referred to as a "hidden primary"
configuration. One use for this configuration is when the primary
master
is behind a firewall and therefore unable to communicate directly
with the outside world.
</p>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2572970"></a>Caching Name Servers</h3></div></div></div>
<p>
The resolver libraries provided by most operating systems are
<span class="emphasis"><em>stub resolvers</em></span>, meaning that they are not
capable of
performing the full DNS resolution process by themselves by talking
directly to the authoritative servers. Instead, they rely on a
local
name server to perform the resolution on their behalf. Such a
server
is called a <span class="emphasis"><em>recursive</em></span> name server; it performs
<span class="emphasis"><em>recursive lookups</em></span> for local clients.
</p>
<p>
To improve performance, recursive servers cache the results of
the lookups they perform. Since the processes of recursion and
caching are intimately connected, the terms
<span class="emphasis"><em>recursive server</em></span> and
<span class="emphasis"><em>caching server</em></span> are often used synonymously.
</p>
<p>
The length of time for which a record may be retained in
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">
<div class="titlepage"><div><div><h4 class="title">
<a name="id2573005"></a>Forwarding</h4></div></div></div>
<p>
Even a caching name server does not necessarily perform
the complete recursive lookup itself. Instead, it can
<span class="emphasis"><em>forward</em></span> some or all of the queries
that it cannot satisfy from its cache to another caching name
server,
commonly referred to as a <span class="emphasis"><em>forwarder</em></span>.
</p>
<p>
There may be one or more forwarders,
and they are queried in turn until the list is exhausted or an
answer
is found. Forwarders are typically used when you do not
wish all the servers at a given site to interact directly with the
rest of
the Internet servers. A typical scenario would involve a number
of internal <acronym class="acronym">DNS</acronym> servers and an
Internet firewall. Servers unable
to pass packets through the firewall would forward to the server
that can do it, and that server would query the Internet <acronym class="acronym">DNS</acronym> servers
on the internal server's behalf.
</p>
</div>
</div>
<div class="sect2" lang="en">
<div class="titlepage"><div><div><h3 class="title">
<a name="id2573032"></a>Name Servers in Multiple Roles</h3></div></div></div>
<p>
The <acronym class="acronym">BIND</acronym> name server can
simultaneously act as
a master for some zones, a slave for other zones, and as a caching
(recursive) server for a set of local clients.
</p>
<p>
However, since the functions of authoritative name service
and caching/recursive name service are logically separate, it is
often advantageous to run them on separate server machines.
A server that only provides authoritative name service
(an <span class="emphasis"><em>authoritative-only</em></span> server) can run with
recursion disabled, improving reliability and security.
A server that is not authoritative for any zones and only provides
recursive service to local
clients (a <span class="emphasis"><em>caching-only</em></span> server)
does not need to be reachable from the Internet at large and can
be placed inside a firewall.
</p>
</div>
</div>
</div>
<div class="navfooter">
<hr>
<table width="100%" summary="Navigation footer">
<tr>
<td width="40%" align="left">
<a accesskey="p" href="Bv9ARM.html">Prev</a>�</td>
<td width="20%" align="center">�</td>
<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch02.html">Next</a>
</td>
</tr>
<tr>
<td width="40%" align="left" valign="top">BIND 9 Administrator Reference Manual�</td>
<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
<td width="40%" align="right" valign="top">�Chapter�2.�<acronym class="acronym">BIND</acronym> Resource Requirements</td>
</tr>
</table>
</div>
</body>
</html>