contrib/bind9/doc/arm/Bv9ARM.ch09.html

   1 <!--
   2  - Copyright (C) 2004, 2005 Internet Systems Consortium, Inc. ("ISC")
   3  - Copyright (C) 2000-2003 Internet Software Consortium.
   4  -
   5  - Permission to use, copy, modify, and distribute this software for any
   6  - purpose with or without fee is hereby granted, provided that the above
   7  - copyright notice and this permission notice appear in all copies.
   8  -
   9  - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
  10  - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
  11  - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
  12  - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
  13  - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
  14  - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
  15  - PERFORMANCE OF THIS SOFTWARE.
  16 -->
  17 <!-- $Id: Bv9ARM.ch09.html,v 1.50.2.9.2.25 2005/10/13 02:34:03 marka Exp $ -->
  18 <html>
  19 <head>
  20 <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
  21 <title>Appendix A. Appendices</title>
  22 <meta name="generator" content="DocBook XSL Stylesheets V1.69.1">
  23 <link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
  24 <link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
  25 <link rel="prev" href="Bv9ARM.ch08.html" title="Chapter 8. Troubleshooting">
  26 </head>
  27 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
  28 <div class="navheader">
  29 <table width="100%" summary="Navigation header">
  30 <tr><th colspan="3" align="center">Appendix A. Appendices</th></tr>
  31 <tr>
  32 <td width="20%" align="left">
  33 <a accesskey="p" href="Bv9ARM.ch08.html">Prev</a> </td>
  34 <th width="60%" align="center"> </th>
  35 <td width="20%" align="right"> </td>
  36 </tr>
  37 </table>
  38 <hr>
  39 </div>
  40 <div class="appendix" lang="en">
  41 <div class="titlepage"><div><div><h2 class="title">
  42 <a name="Bv9ARM.ch09"></a>Appendix A. Appendices</h2></div></div></div>
  43 <div class="toc">
  44 <p><b>Table of Contents</b></p>
  45 <dl>
  46 <dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2567795">Acknowledgments</a></span></dt>
  47 <dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2567800">A Brief History of the <span class="acronym">DNS</span> and <span class="acronym">BIND</span></a></span></dt></dl></dd>
  48 <dt><span class="sect1"><a href="Bv9ARM.ch09.html#historical_dns_information">General <span class="acronym">DNS</span> Reference Information</a></span></dt>
  49 <dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt></dl></dd>
  50 <dt><span class="sect1"><a href="Bv9ARM.ch09.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt>
  51 <dd><dl>
  52 <dt><span class="sect2"><a href="Bv9ARM.ch09.html#rfcs">Request for Comments (RFCs)</a></span></dt>
  53 <dt><span class="sect2"><a href="Bv9ARM.ch09.html#internet_drafts">Internet Drafts</a></span></dt>
  54 <dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2570087">Other Documents About <span class="acronym">BIND</span></a></span></dt>
  55 </dl></dd>
  56 </dl>
  57 </div>
  58 <div class="sect1" lang="en">
  59 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
  60 <a name="id2567795"></a>Acknowledgments</h2></div></div></div>
  61 <div class="sect2" lang="en">
  62 <div class="titlepage"><div><div><h3 class="title">
  63 <a name="id2567800"></a>A Brief History of the <span class="acronym">DNS</span> and <span class="acronym">BIND</span></h3></div></div></div>
  64 <p>Although the "official" beginning of the Domain Name
  65       System occurred in 1984 with the publication of RFC 920, the
  66       core of the new system was described in 1983 in RFCs 882 and
  67       883. From 1984 to 1987, the ARPAnet (the precursor to today's
  68       Internet) became a testbed of experimentation for developing the
  69       new naming/addressing scheme in an rapidly expanding,
  70       operational network environment.  New RFCs were written and
  71       published in 1987 that modified the original documents to
  72       incorporate improvements based on the working model. RFC 1034,
  73       "Domain Names-Concepts and Facilities", and RFC 1035, "Domain
  74       Names-Implementation and Specification" were published and
  75       became the standards upon which all <span class="acronym">DNS</span> implementations are
  76       built.
  77 </p>
  78 <p>The first working domain name server, called "Jeeves", was
  79 written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20
  80 machines located at the University of Southern California's Information
  81 Sciences Institute (USC-ISI) and SRI International's Network Information
  82 Center (SRI-NIC). A <span class="acronym">DNS</span> server for Unix machines, the Berkeley Internet
  83 Name Domain (<span class="acronym">BIND</span>) package, was written soon after by a group of
  84 graduate students at the University of California at Berkeley under
  85 a grant from the US Defense Advanced Research Projects Administration
  86 (DARPA). Versions of <span class="acronym">BIND</span> through 4.8.3 were maintained by the Computer
  87 Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
  88 Painter, David Riggle and Songnian Zhou made up the initial <span class="acronym">BIND</span>
  89 project team. After that, additional work on the software package
  90 was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation
  91 employee on loan to the CSRG, worked on <span class="acronym">BIND</span> for 2 years, from 1985
  92 to 1987. Many other people also contributed to <span class="acronym">BIND</span> development
  93 during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell,
  94 Mike Muuss, Jim Bloom and Mike Schwartz. <span class="acronym">BIND</span> maintenance was subsequently
  95 handled by Mike Karels and O. Kure.</p>
  96 <p><span class="acronym">BIND</span> versions 4.9 and 4.9.1 were released by Digital Equipment
  97 Corporation (now Compaq Computer Corporation). Paul Vixie, then
  98 a DEC employee, became <span class="acronym">BIND</span>'s primary caretaker. Paul was assisted
  99 by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew
 100 Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat
 101 Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
 102 Wolfhugel, and others.</p>
 103 <p><span class="acronym">BIND</span> Version 4.9.2 was sponsored by Vixie Enterprises. Paul
 104 Vixie became <span class="acronym">BIND</span>'s principal architect/programmer.</p>
 105 <p><span class="acronym">BIND</span> versions from 4.9.3 onward have been developed and maintained
 106 by the Internet Software Consortium with support being provided
 107 by ISC's sponsors. As co-architects/programmers, Bob Halley and
 108 Paul Vixie released the first production-ready version of <span class="acronym">BIND</span> version
 109 8 in May 1997.</p>
 110 <p><span class="acronym">BIND</span> development work is made possible today by the sponsorship
 111 of several corporations, and by the tireless work efforts of numerous
 112 individuals.</p>
 113 </div>
 114 </div>
 115 <div class="sect1" lang="en">
 116 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 117 <a name="historical_dns_information"></a>General <span class="acronym">DNS</span> Reference Information</h2></div></div></div>
 118 <div class="sect2" lang="en">
 119 <div class="titlepage"><div><div><h3 class="title">
 120 <a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h3></div></div></div>
 121 <p>IPv6 addresses are 128-bit identifiers for interfaces and
 122 sets of interfaces which were introduced in the <span class="acronym">DNS</span> to facilitate
 123 scalable Internet routing. There are three types of addresses: <span class="emphasis"><em>Unicast</em></span>,
 124 an identifier for a single interface; <span class="emphasis"><em>Anycast</em></span>,
 125 an identifier for a set of interfaces; and <span class="emphasis"><em>Multicast</em></span>,
 126 an identifier for a set of interfaces. Here we describe the global
 127 Unicast address scheme. For more information, see RFC 2374.</p>
 128 <p>The aggregatable global Unicast address format is as follows:</p>
 129 <div class="informaltable"><table border="1">
 130 <colgroup>
 131 <col>
 132 <col>
 133 <col>
 134 <col>
 135 <col>
 136 <col>
 137 </colgroup>
 138 <tbody>
 139 <tr>
 140 <td><p>3</p></td>
 141 <td><p>13</p></td>
 142 <td><p>8</p></td>
 143 <td><p>24</p></td>
 144 <td><p>16</p></td>
 145 <td><p>64 bits</p></td>
 146 </tr>
 147 <tr>
 148 <td><p>FP</p></td>
 149 <td><p>TLA ID</p></td>
 150 <td><p>RES</p></td>
 151 <td><p>NLA ID</p></td>
 152 <td><p>SLA ID</p></td>
 153 <td><p>Interface ID</p></td>
 154 </tr>
 155 <tr>
 156 <td colspan="4"><p>&lt;------ Public Topology
 157 ------&gt;</p></td>
 158 <td><p></p></td>
 159 <td><p></p></td>
 160 </tr>
 161 <tr>
 162 <td><p></p></td>
 163 <td><p></p></td>
 164 <td><p></p></td>
 165 <td><p></p></td>
 166 <td><p>&lt;-Site Topology-&gt;</p></td>
 167 <td><p></p></td>
 168 </tr>
 169 <tr>
 170 <td><p></p></td>
 171 <td><p></p></td>
 172 <td><p></p></td>
 173 <td><p></p></td>
 174 <td><p></p></td>
 175 <td><p>&lt;------ Interface Identifier ------&gt;</p></td>
 176 </tr>
 177 </tbody>
 178 </table></div>
 179 <p>Where
 180 </p>
 181 <div class="informaltable"><table border="1">
 182 <colgroup>
 183 <col>
 184 <col>
 185 <col>
 186 </colgroup>
 187 <tbody>
 188 <tr>
 189 <td><p>FP</p></td>
 190 <td><p>=</p></td>
 191 <td><p>Format Prefix (001)</p></td>
 192 </tr>
 193 <tr>
 194 <td><p>TLA ID</p></td>
 195 <td><p>=</p></td>
 196 <td><p>Top-Level Aggregation Identifier</p></td>
 197 </tr>
 198 <tr>
 199 <td><p>RES</p></td>
 200 <td><p>=</p></td>
 201 <td><p>Reserved for future use</p></td>
 202 </tr>
 203 <tr>
 204 <td><p>NLA ID</p></td>
 205 <td><p>=</p></td>
 206 <td><p>Next-Level Aggregation Identifier</p></td>
 207 </tr>
 208 <tr>
 209 <td><p>SLA ID</p></td>
 210 <td><p>=</p></td>
 211 <td><p>Site-Level Aggregation Identifier</p></td>
 212 </tr>
 213 <tr>
 214 <td><p>INTERFACE ID</p></td>
 215 <td><p>=</p></td>
 216 <td><p>Interface Identifier</p></td>
 217 </tr>
 218 </tbody>
 219 </table></div>
 220 <p>The <span class="emphasis"><em>Public Topology</em></span> is provided by the
 221 upstream provider or ISP, and (roughly) corresponds to the IPv4 <span class="emphasis"><em>network</em></span> section
 222 of the address range. The <span class="emphasis"><em>Site Topology</em></span> is
 223 where you can subnet this space, much the same as subnetting an
 224 IPv4 /16 network into /24 subnets. The <span class="emphasis"><em>Interface Identifier</em></span> is
 225 the address of an individual interface on a given network. (With
 226 IPv6, addresses belong to interfaces rather than machines.)</p>
 227 <p>The subnetting capability of IPv6 is much more flexible than
 228 that of IPv4: subnetting can now be carried out on bit boundaries,
 229 in much the same way as Classless InterDomain Routing (CIDR).</p>
 230 <p>The Interface Identifier must be unique on that network. On
 231 ethernet networks, one way to ensure this is to set the address
 232 to the first three bytes of the hardware address, "FFFE", then the
 233 last three bytes of the hardware address. The lowest significant
 234 bit of the first byte should then be complemented. Addresses are
 235 written as 32-bit blocks separated with a colon, and leading zeros
 236 of a block may be omitted, for example:</p>
 237 <p><span><strong class="command">2001:db8:201:9:a00:20ff:fe81:2b32</strong></span></p>
 238 <p>IPv6 address specifications are likely to contain long strings
 239 of zeros, so the architects have included a shorthand for specifying
 240 them. The double colon (`::') indicates the longest possible string
 241 of zeros that can fit, and can be used only once in an address.</p>
 242 </div>
 243 </div>
 244 <div class="sect1" lang="en">
 245 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 246 <a name="bibliography"></a>Bibliography (and Suggested Reading)</h2></div></div></div>
 247 <div class="sect2" lang="en">
 248 <div class="titlepage"><div><div><h3 class="title">
 249 <a name="rfcs"></a>Request for Comments (RFCs)</h3></div></div></div>
 250 <p>Specification documents for the Internet protocol suite, including
 251 the <span class="acronym">DNS</span>, are published as part of the Request for Comments (RFCs)
 252 series of technical notes. The standards themselves are defined
 253 by the Internet Engineering Task Force (IETF) and the Internet Engineering
 254 Steering Group (IESG). RFCs can be obtained online via FTP at
 255 <a href="ftp://www.isi.edu/in-notes/" target="_top">ftp://www.isi.edu/in-notes/RFC<em class="replaceable"><code>xxx</code></em>.txt</a> (where <em class="replaceable"><code>xxx</code></em> is
 256 the number of the RFC). RFCs are also available via the Web at
 257 <a href="http://www.ietf.org/rfc/" target="_top">http://www.ietf.org/rfc/</a>.
 258 </p>
 259 <div class="bibliography">
 260 <div class="titlepage"><div><div><h4 class="title">
 261 <a name="id2568712"></a>Bibliography</h4></div></div></div>
 262 <div class="bibliodiv">
 263 <h3 class="title">Standards</h3>
 264 <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>
 265 <div class="biblioentry"><p>[<span class="abbrev">RFC1034</span>] <span class="author"><span class="firstname">P.V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names &#8212; Concepts and Facilities</i>. </span><span class="pubdate">November 1987. </span></p></div>
 266 <div class="biblioentry"><p>[<span class="abbrev">RFC1035</span>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names &#8212; Implementation and
 267 Specification</i>. </span><span class="pubdate">November 1987. </span></p></div>
 268 </div>
 269 <div class="bibliodiv">
 270 <h3 class="title">
 271 <a name="proposed_standards"></a>Proposed Standards</h3>
 272 <div class="biblioentry"><p>[<span class="abbrev">RFC2181</span>] <span class="author"><span class="firstname">R., R. Bush</span> <span class="surname">Elz</span>. </span><span class="title"><i>Clarifications to the <span class="acronym">DNS</span> Specification</i>. </span><span class="pubdate">July 1997. </span></p></div>
 273 <div class="biblioentry"><p>[<span class="abbrev">RFC2308</span>] <span class="author"><span class="firstname">M.</span> <span class="surname">Andrews</span>. </span><span class="title"><i>Negative Caching of <span class="acronym">DNS</span> Queries</i>. </span><span class="pubdate">March 1998. </span></p></div>
 274 <div class="biblioentry"><p>[<span class="abbrev">RFC1995</span>] <span class="author"><span class="firstname">M.</span> <span class="surname">Ohta</span>. </span><span class="title"><i>Incremental Zone Transfer in <span class="acronym">DNS</span></i>. </span><span class="pubdate">August 1996. </span></p></div>
 275 <div class="biblioentry"><p>[<span class="abbrev">RFC1996</span>] <span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>A Mechanism for Prompt Notification of Zone Changes</i>. </span><span class="pubdate">August 1996. </span></p></div>
 276 <div class="biblioentry"><p>[<span class="abbrev">RFC2136</span>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">Y.</span> <span class="surname">Rekhter</span>, and <span class="firstname">J.</span> <span class="surname">Bound</span>. </span><span class="title"><i>Dynamic Updates in the Domain Name System</i>. </span><span class="pubdate">April 1997. </span></p></div>
 277 <div class="biblioentry"><p>[<span class="abbrev">RFC2845</span>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>, <span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, and <span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Secret Key Transaction Authentication for <span class="acronym">DNS</span> (TSIG)</i>. </span><span class="pubdate">May 2000. </span></p></div>
 278 </div>
 279 <div class="bibliodiv">
 280 <h3 class="title">Proposed Standards Still Under Development</h3>
 281 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
 282 <h3 class="title">Note</h3>
 283 <p><span class="emphasis"><em>Note:</em></span> the following list of
 284 RFCs are undergoing major revision by the IETF.</p>
 285 </div>
 286 <div class="biblioentry"><p>[<span class="abbrev">RFC1886</span>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Thomson</span> and <span class="firstname">C.</span> <span class="surname">Huitema</span>. </span><span class="title"><i><span class="acronym">DNS</span> Extensions to support IP version 6</i>. </span><span class="pubdate">December 1995. </span></p></div>
 287 <div class="biblioentry"><p>[<span class="abbrev">RFC2065</span>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">C.</span> <span class="surname">Kaufman</span>. </span><span class="title"><i>Domain Name System Security Extensions</i>. </span><span class="pubdate">January 1997. </span></p></div>
 288 <div class="biblioentry"><p>[<span class="abbrev">RFC2137</span>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Secure Domain Name System Dynamic Update</i>. </span><span class="pubdate">April 1997. </span></p></div>
 289 </div>
 290 <div class="bibliodiv">
 291 <h3 class="title">Other Important RFCs About <span class="acronym">DNS</span> Implementation</h3>
 292 <div class="biblioentry"><p>[<span class="abbrev">RFC1535</span>] <span class="author"><span class="firstname">E.</span> <span class="surname">Gavron</span>. </span><span class="title"><i>A Security Problem and Proposed Correction With Widely Deployed <span class="acronym">DNS</span> Software.</i>. </span><span class="pubdate">October 1993. </span></p></div>
 293 <div class="biblioentry"><p>[<span class="abbrev">RFC1536</span>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Kumar</span>, <span class="firstname">J.</span> <span class="surname">Postel</span>, <span class="firstname">C.</span> <span class="surname">Neuman</span>, <span class="firstname">P.</span> <span class="surname">Danzig</span>, and <span class="firstname">S.</span> <span class="surname">Miller</span>. </span><span class="title"><i>Common <span class="acronym">DNS</span> Implementation Errors and Suggested Fixes</i>. </span><span class="pubdate">October 1993. </span></p></div>
 294 <div class="biblioentry"><p>[<span class="abbrev">RFC1982</span>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Elz</span> and <span class="firstname">R.</span> <span class="surname">Bush</span>. </span><span class="title"><i>Serial Number Arithmetic</i>. </span><span class="pubdate">August 1996. </span></p></div>
 295 </div>
 296 <div class="bibliodiv">
 297 <h3 class="title">Resource Record Types</h3>
 298 <div class="biblioentry"><p>[<span class="abbrev">RFC1183</span>] <span class="authorgroup"><span class="firstname">C.F.</span> <span class="surname">Everhart</span>, <span class="firstname">L. A.</span> <span class="surname">Mamakos</span>, <span class="firstname">R.</span> <span class="surname">Ullmann</span>, and <span class="firstname">P.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>New <span class="acronym">DNS</span> RR Definitions</i>. </span><span class="pubdate">October 1990. </span></p></div>
 299 <div class="biblioentry"><p>[<span class="abbrev">RFC1706</span>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">R.</span> <span class="surname">Colella</span>. </span><span class="title"><i><span class="acronym">DNS</span> NSAP Resource Records</i>. </span><span class="pubdate">October 1994. </span></p></div>
 300 <div class="biblioentry"><p>[<span class="abbrev">RFC2168</span>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Daniel</span> and <span class="firstname">M.</span> <span class="surname">Mealling</span>. </span><span class="title"><i>Resolution of Uniform Resource Identifiers using
 301 the Domain Name System</i>. </span><span class="pubdate">June 1997. </span></p></div>
 302 <div class="biblioentry"><p>[<span class="abbrev">RFC1876</span>] <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Davis</span>, <span class="firstname">P.</span> <span class="surname">Vixie</span>, <span class="firstname">T.</span>, and <span class="firstname">I.</span> <span class="surname">Dickinson</span>. </span><span class="title"><i>A Means for Expressing Location Information in the Domain
 303 Name System</i>. </span><span class="pubdate">January 1996. </span></p></div>
 304 <div class="biblioentry"><p>[<span class="abbrev">RFC2052</span>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>A <span class="acronym">DNS</span> RR for Specifying the Location of
 305 Services.</i>. </span><span class="pubdate">October 1996. </span></p></div>
 306 <div class="biblioentry"><p>[<span class="abbrev">RFC2163</span>] <span class="author"><span class="firstname">A.</span> <span class="surname">Allocchio</span>. </span><span class="title"><i>Using the Internet <span class="acronym">DNS</span> to Distribute MIXER
 307 Conformant Global Address Mapping</i>. </span><span class="pubdate">January 1998. </span></p></div>
 308 <div class="biblioentry"><p>[<span class="abbrev">RFC2230</span>] <span class="author"><span class="firstname">R.</span> <span class="surname">Atkinson</span>. </span><span class="title"><i>Key Exchange Delegation Record for the <span class="acronym">DNS</span></i>. </span><span class="pubdate">October 1997. </span></p></div>
 309 </div>
 310 <div class="bibliodiv">
 311 <h3 class="title">
 312 <span class="acronym">DNS</span> and the Internet</h3>
 313 <div class="biblioentry"><p>[<span class="abbrev">RFC1101</span>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i><span class="acronym">DNS</span> Encoding of Network Names and Other Types</i>. </span><span class="pubdate">April 1989. </span></p></div>
 314 <div class="biblioentry"><p>[<span class="abbrev">RFC1123</span>] <span class="author"><span class="surname">Braden</span>. </span><span class="title"><i>Requirements for Internet Hosts - Application and Support</i>. </span><span class="pubdate">October 1989. </span></p></div>
 315 <div class="biblioentry"><p>[<span class="abbrev">RFC1591</span>] <span class="author"><span class="firstname">J.</span> <span class="surname">Postel</span>. </span><span class="title"><i>Domain Name System Structure and Delegation</i>. </span><span class="pubdate">March 1994. </span></p></div>
 316 <div class="biblioentry"><p>[<span class="abbrev">RFC2317</span>] <span class="authorgroup"><span class="firstname">H.</span> <span class="surname">Eidnes</span>, <span class="firstname">G.</span> <span class="surname">de Groot</span>, and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Classless IN-ADDR.ARPA Delegation</i>. </span><span class="pubdate">March 1998. </span></p></div>
 317 </div>
 318 <div class="bibliodiv">
 319 <h3 class="title">
 320 <span class="acronym">DNS</span> Operations</h3>
 321 <div class="biblioentry"><p>[<span class="abbrev">RFC1537</span>] <span class="author"><span class="firstname">P.</span> <span class="surname">Beertema</span>. </span><span class="title"><i>Common <span class="acronym">DNS</span> Data File Configuration Errors</i>. </span><span class="pubdate">October 1993. </span></p></div>
 322 <div class="biblioentry"><p>[<span class="abbrev">RFC1912</span>] <span class="author"><span class="firstname">D.</span> <span class="surname">Barr</span>. </span><span class="title"><i>Common <span class="acronym">DNS</span> Operational and Configuration Errors</i>. </span><span class="pubdate">February 1996. </span></p></div>
 323 <div class="biblioentry"><p>[<span class="abbrev">RFC2010</span>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Manning</span> and <span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Operational Criteria for Root Name Servers.</i>. </span><span class="pubdate">October 1996. </span></p></div>
 324 <div class="biblioentry"><p>[<span class="abbrev">RFC2219</span>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Hamilton</span> and <span class="firstname">R.</span> <span class="surname">Wright</span>. </span><span class="title"><i>Use of <span class="acronym">DNS</span> Aliases for Network Services.</i>. </span><span class="pubdate">October 1997. </span></p></div>
 325 </div>
 326 <div class="bibliodiv">
 327 <h3 class="title">Other <span class="acronym">DNS</span>-related RFCs</h3>
 328 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
 329 <h3 class="title">Note</h3>
 330 <p>Note: the following list of RFCs, although
 331 <span class="acronym">DNS</span>-related, are not concerned with implementing software.</p>
 332 </div>
 333 <div class="biblioentry"><p>[<span class="abbrev">RFC1464</span>] <span class="author"><span class="firstname">R.</span> <span class="surname">Rosenbaum</span>. </span><span class="title"><i>Using the Domain Name System To Store Arbitrary String Attributes</i>. </span><span class="pubdate">May 1993. </span></p></div>
 334 <div class="biblioentry"><p>[<span class="abbrev">RFC1713</span>] <span class="author"><span class="firstname">A.</span> <span class="surname">Romao</span>. </span><span class="title"><i>Tools for <span class="acronym">DNS</span> Debugging</i>. </span><span class="pubdate">November 1994. </span></p></div>
 335 <div class="biblioentry"><p>[<span class="abbrev">RFC1794</span>] <span class="author"><span class="firstname">T.</span> <span class="surname">Brisco</span>. </span><span class="title"><i><span class="acronym">DNS</span> Support for Load Balancing</i>. </span><span class="pubdate">April 1995. </span></p></div>
 336 <div class="biblioentry"><p>[<span class="abbrev">RFC2240</span>] <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span><span class="title"><i>A Legal Basis for Domain Name Allocation</i>. </span><span class="pubdate">November 1997. </span></p></div>
 337 <div class="biblioentry"><p>[<span class="abbrev">RFC2345</span>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>, <span class="firstname">T.</span> <span class="surname">Wolf</span>, and <span class="firstname">G.</span> <span class="surname">Oglesby</span>. </span><span class="title"><i>Domain Names and Company Name Retrieval</i>. </span><span class="pubdate">May 1998. </span></p></div>
 338 <div class="biblioentry"><p>[<span class="abbrev">RFC2352</span>] <span class="author"><span class="firstname">O.</span> <span class="surname">Vaughan</span>. </span><span class="title"><i>A Convention For Using Legal Names as Domain Names</i>. </span><span class="pubdate">May 1998. </span></p></div>
 339 </div>
 340 <div class="bibliodiv">
 341 <h3 class="title">Obsolete and Unimplemented Experimental RRs</h3>
 342 <div class="biblioentry"><p>[<span class="abbrev">RFC1712</span>] <span class="authorgroup"><span class="firstname">C.</span> <span class="surname">Farrell</span>, <span class="firstname">M.</span> <span class="surname">Schulze</span>, <span class="firstname">S.</span> <span class="surname">Pleitner</span>, and <span class="firstname">D.</span> <span class="surname">Baldoni</span>. </span><span class="title"><i><span class="acronym">DNS</span> Encoding of Geographical
 343 Location</i>. </span><span class="pubdate">November 1994. </span></p></div>
 344 </div>
 345 </div>
 346 </div>
 347 <div class="sect2" lang="en">
 348 <div class="titlepage"><div><div><h3 class="title">
 349 <a name="internet_drafts"></a>Internet Drafts</h3></div></div></div>
 350 <p>Internet Drafts (IDs) are rough-draft working documents of
 351 the Internet Engineering Task Force. They are, in essence, RFCs
 352 in the preliminary stages of development. Implementors are cautioned not
 353 to regard IDs as archival, and they should not be quoted or cited
 354 in any formal documents unless accompanied by the disclaimer that
 355 they are "works in progress." IDs have a lifespan of six months
 356 after which they are deleted unless updated by their authors.
 357 </p>
 358 </div>
 359 <div class="sect2" lang="en">
 360 <div class="titlepage"><div><div><h3 class="title">
 361 <a name="id2570087"></a>Other Documents About <span class="acronym">BIND</span></h3></div></div></div>
 362 <p></p>
 363 <div class="bibliography">
 364 <div class="titlepage"><div><div><h4 class="title">
 365 <a name="id2570097"></a>Bibliography</h4></div></div></div>
 366 <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>
 367 </div>
 368 </div>
 369 </div>
 370 </div>
 371 <div class="navfooter">
 372 <hr>
 373 <table width="100%" summary="Navigation footer">
 374 <tr>
 375 <td width="40%" align="left">
 376 <a accesskey="p" href="Bv9ARM.ch08.html">Prev</a> </td>
 377 <td width="20%" align="center"> </td>
 378 <td width="40%" align="right"> </td>
 379 </tr>
 380 <tr>
 381 <td width="40%" align="left" valign="top">Chapter 8. Troubleshooting </td>
 382 <td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
 383 <td width="40%" align="right" valign="top"> </td>
 384 </tr>
 385 </table>
 386 </div>
 387 </body>
 388 </html>