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

   1 <!--
   2  - Copyright (C) 2004-2008 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.44 2008/01/19 01:52:15 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.71.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#id2587012">Acknowledgments</a></span></dt>
  47 <dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2587017">A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></a></span></dt></dl></dd>
  48 <dt><span class="sect1"><a href="Bv9ARM.ch09.html#historical_dns_information">General <acronym class="acronym">DNS</acronym> 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#id2589386">Other Documents About <acronym class="acronym">BIND</acronym></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="id2587012"></a>Acknowledgments</h2></div></div></div>
  61 <div class="sect2" lang="en">
  62 <div class="titlepage"><div><div><h3 class="title">
  63 <a name="id2587017"></a>A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym>
  64 </h3></div></div></div>
  65 <p>Although the "official" beginning of the Domain Name
  66       System occurred in 1984 with the publication of RFC 920, the
  67       core of the new system was described in 1983 in RFCs 882 and
  68       883. From 1984 to 1987, the ARPAnet (the precursor to today's
  69       Internet) became a testbed of experimentation for developing the
  70       new naming/addressing scheme in a rapidly expanding,
  71       operational network environment.  New RFCs were written and
  72       published in 1987 that modified the original documents to
  73       incorporate improvements based on the working model. RFC 1034,
  74       "Domain Names-Concepts and Facilities", and RFC 1035, "Domain
  75       Names-Implementation and Specification" were published and
  76       became the standards upon which all <acronym class="acronym">DNS</acronym> implementations are
  77       built.
  78 </p>
  79 <p>The first working domain name server, called "Jeeves", was
  80 written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20
  81 machines located at the University of Southern California's Information
  82 Sciences Institute (USC-ISI) and SRI International's Network Information
  83 Center (SRI-NIC). A <acronym class="acronym">DNS</acronym> server for Unix machines, the Berkeley Internet
  84 Name Domain (<acronym class="acronym">BIND</acronym>) package, was written soon after by a group of
  85 graduate students at the University of California at Berkeley under
  86 a grant from the US Defense Advanced Research Projects Administration
  87 (DARPA).
  88 </p>
  89 <p>
  90 Versions of <acronym class="acronym">BIND</acronym> through 4.8.3 were maintained by the Computer
  91 Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
  92 Painter, David Riggle and Songnian Zhou made up the initial <acronym class="acronym">BIND</acronym>
  93 project team. After that, additional work on the software package
  94 was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation
  95 employee on loan to the CSRG, worked on <acronym class="acronym">BIND</acronym> for 2 years, from 1985
  96 to 1987. Many other people also contributed to <acronym class="acronym">BIND</acronym> development
  97 during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell,
  98 Mike Muuss, Jim Bloom and Mike Schwartz. <acronym class="acronym">BIND</acronym> maintenance was subsequently
  99 handled by Mike Karels and Øivind Kure.</p>
 100 <p><acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were released by Digital Equipment
 101 Corporation (now Compaq Computer Corporation). Paul Vixie, then
 102 a DEC employee, became <acronym class="acronym">BIND</acronym>'s primary caretaker. He was assisted
 103 by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew
 104 Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat
 105 Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
 106 Wolfhugel, and others.</p>
 107 <p>In 1994, <acronym class="acronym">BIND</acronym> version 4.9.2 was sponsored by Vixie Enterprises. Paul
 108 Vixie became <acronym class="acronym">BIND</acronym>'s principal architect/programmer.</p>
 109 <p><acronym class="acronym">BIND</acronym> versions from 4.9.3 onward have been developed and maintained
 110 by the Internet Software Consortium with support being provided
 111 by ISC's sponsors.
 112       </p>
 113 <p>As co-architects/programmers, Bob Halley and
 114 Paul Vixie released the first production-ready version of <acronym class="acronym">BIND</acronym> version
 115 8 in May 1997.</p>
 116 <p>
 117           BIND version 9 was released in September 2000 and is a
 118           major rewrite of nearly all aspects of the underlying
 119           BIND architecture.
 120           </p>
 121 <p>
 122           BIND version 4 is officially deprecated and BIND version
 123           8 development is considered maintenance-only in favor
 124           of BIND version 9. No additional development is done
 125           on BIND version 4 or BIND version 8 other than for
 126           security-related patches.
 127         </p>
 128 <p><acronym class="acronym">BIND</acronym> development work is made possible today by the sponsorship
 129 of several corporations, and by the tireless work efforts of numerous
 130 individuals.</p>
 131 </div>
 132 </div>
 133 <div class="sect1" lang="en">
 134 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 135 <a name="historical_dns_information"></a>General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div>
 136 <div class="sect2" lang="en">
 137 <div class="titlepage"><div><div><h3 class="title">
 138 <a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h3></div></div></div>
 139 <p>IPv6 addresses are 128-bit identifiers for interfaces and
 140 sets of interfaces which were introduced in the <acronym class="acronym">DNS</acronym> to facilitate
 141 scalable Internet routing. There are three types of addresses: <span class="emphasis"><em>Unicast</em></span>,
 142 an identifier for a single interface; <span class="emphasis"><em>Anycast</em></span>,
 143 an identifier for a set of interfaces; and <span class="emphasis"><em>Multicast</em></span>,
 144 an identifier for a set of interfaces. Here we describe the global
 145 Unicast address scheme. For more information, see RFC 3587,
 146 "Global Unicast Address Format."</p>
 147 <p>The aggregatable global Unicast address format is as follows:</p>
 148 <div class="informaltable"><table border="1">
 149 <colgroup>
 150 <col>
 151 <col>
 152 <col>
 153 <col>
 154 <col>
 155 <col>
 156 </colgroup>
 157 <tbody>
 158 <tr>
 159 <td><p>3</p></td>
 160 <td><p>13</p></td>
 161 <td><p>8</p></td>
 162 <td><p>24</p></td>
 163 <td><p>16</p></td>
 164 <td><p>64 bits</p></td>
 165 </tr>
 166 <tr>
 167 <td><p>FP</p></td>
 168 <td><p>TLA ID</p></td>
 169 <td><p>RES</p></td>
 170 <td><p>NLA ID</p></td>
 171 <td><p>SLA ID</p></td>
 172 <td><p>Interface ID</p></td>
 173 </tr>
 174 <tr>
 175 <td colspan="4"><p>&lt;------ Public Topology
 176 ------&gt;</p></td>
 177 <td><p></p></td>
 178 <td><p></p></td>
 179 </tr>
 180 <tr>
 181 <td><p></p></td>
 182 <td><p></p></td>
 183 <td><p></p></td>
 184 <td><p></p></td>
 185 <td><p>&lt;-Site Topology-&gt;</p></td>
 186 <td><p></p></td>
 187 </tr>
 188 <tr>
 189 <td><p></p></td>
 190 <td><p></p></td>
 191 <td><p></p></td>
 192 <td><p></p></td>
 193 <td><p></p></td>
 194 <td><p>&lt;------ Interface Identifier ------&gt;</p></td>
 195 </tr>
 196 </tbody>
 197 </table></div>
 198 <p>Where
 199 </p>
 200 <div class="informaltable"><table border="1">
 201 <colgroup>
 202 <col>
 203 <col>
 204 <col>
 205 </colgroup>
 206 <tbody>
 207 <tr>
 208 <td><p>FP</p></td>
 209 <td><p>=</p></td>
 210 <td><p>Format Prefix (001)</p></td>
 211 </tr>
 212 <tr>
 213 <td><p>TLA ID</p></td>
 214 <td><p>=</p></td>
 215 <td><p>Top-Level Aggregation Identifier</p></td>
 216 </tr>
 217 <tr>
 218 <td><p>RES</p></td>
 219 <td><p>=</p></td>
 220 <td><p>Reserved for future use</p></td>
 221 </tr>
 222 <tr>
 223 <td><p>NLA ID</p></td>
 224 <td><p>=</p></td>
 225 <td><p>Next-Level Aggregation Identifier</p></td>
 226 </tr>
 227 <tr>
 228 <td><p>SLA ID</p></td>
 229 <td><p>=</p></td>
 230 <td><p>Site-Level Aggregation Identifier</p></td>
 231 </tr>
 232 <tr>
 233 <td><p>INTERFACE ID</p></td>
 234 <td><p>=</p></td>
 235 <td><p>Interface Identifier</p></td>
 236 </tr>
 237 </tbody>
 238 </table></div>
 239 <p>The <span class="emphasis"><em>Public Topology</em></span> is provided by the
 240 upstream provider or ISP, and (roughly) corresponds to the IPv4 <span class="emphasis"><em>network</em></span> section
 241 of the address range. The <span class="emphasis"><em>Site Topology</em></span> is
 242 where you can subnet this space, much the same as subnetting an
 243 IPv4 /16 network into /24 subnets. The <span class="emphasis"><em>Interface Identifier</em></span> is
 244 the address of an individual interface on a given network. (With
 245 IPv6, addresses belong to interfaces rather than machines.)</p>
 246 <p>The subnetting capability of IPv6 is much more flexible than
 247 that of IPv4: subnetting can now be carried out on bit boundaries,
 248 in much the same way as Classless InterDomain Routing (CIDR).</p>
 249 <p>The Interface Identifier must be unique on that network. On
 250 ethernet networks, one way to ensure this is to set the address
 251 to the first three bytes of the hardware address, "FFFE", then the
 252 last three bytes of the hardware address. The lowest significant
 253 bit of the first byte should then be complemented. Addresses are
 254 written as 32-bit blocks separated with a colon, and leading zeros
 255 of a block may be omitted, for example:</p>
 256 <p><span><strong class="command">2001:db8:201:9:a00:20ff:fe81:2b32</strong></span></p>
 257 <p>IPv6 address specifications are likely to contain long strings
 258 of zeros, so the architects have included a shorthand for specifying
 259 them. The double colon (`::') indicates the longest possible string
 260 of zeros that can fit, and can be used only once in an address.</p>
 261 </div>
 262 </div>
 263 <div class="sect1" lang="en">
 264 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 265 <a name="bibliography"></a>Bibliography (and Suggested Reading)</h2></div></div></div>
 266 <div class="sect2" lang="en">
 267 <div class="titlepage"><div><div><h3 class="title">
 268 <a name="rfcs"></a>Request for Comments (RFCs)</h3></div></div></div>
 269 <p>Specification documents for the Internet protocol suite, including
 270 the <acronym class="acronym">DNS</acronym>, are published as part of the Request for Comments (RFCs)
 271 series of technical notes. The standards themselves are defined
 272 by the Internet Engineering Task Force (IETF) and the Internet Engineering
 273 Steering Group (IESG). RFCs can be obtained online via FTP at
 274 <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
 275 the number of the RFC). RFCs are also available via the Web at
 276 <a href="http://www.ietf.org/rfc/" target="_top">http://www.ietf.org/rfc/</a>.
 277 </p>
 278 <div class="bibliography">
 279 <div class="titlepage"><div><div><h4 class="title">
 280 <a name="id2587943"></a>Bibliography</h4></div></div></div>
 281 <div class="bibliodiv">
 282 <h3 class="title">Standards</h3>
 283 <div class="biblioentry">
 284 <a name="id2587954"></a><p>[<abbr class="abbrev">RFC974</abbr>] <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>
 285 </div>
 286 <div class="biblioentry">
 287 <a name="id2587977"></a><p>[<abbr class="abbrev">RFC1034</abbr>] <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>
 288 </div>
 289 <div class="biblioentry">
 290 <a name="id2588001"></a><p>[<abbr class="abbrev">RFC1035</abbr>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i>Domain Names &#8212; Implementation and
 291 Specification</i>. </span><span class="pubdate">November 1987. </span></p>
 292 </div>
 293 </div>
 294 <div class="bibliodiv">
 295 <h3 class="title">
 296 <a name="proposed_standards"></a>Proposed Standards</h3>
 297 <div class="biblioentry">
 298 <a name="id2588038"></a><p>[<abbr class="abbrev">RFC2181</abbr>] <span class="author"><span class="firstname">R., R. Bush</span> <span class="surname">Elz</span>. </span><span class="title"><i>Clarifications to the <acronym class="acronym">DNS</acronym> Specification</i>. </span><span class="pubdate">July 1997. </span></p>
 299 </div>
 300 <div class="biblioentry">
 301 <a name="id2588064"></a><p>[<abbr class="abbrev">RFC2308</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Andrews</span>. </span><span class="title"><i>Negative Caching of <acronym class="acronym">DNS</acronym> Queries</i>. </span><span class="pubdate">March 1998. </span></p>
 302 </div>
 303 <div class="biblioentry">
 304 <a name="id2588089"></a><p>[<abbr class="abbrev">RFC1995</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Ohta</span>. </span><span class="title"><i>Incremental Zone Transfer in <acronym class="acronym">DNS</acronym></i>. </span><span class="pubdate">August 1996. </span></p>
 305 </div>
 306 <div class="biblioentry">
 307 <a name="id2588114"></a><p>[<abbr class="abbrev">RFC1996</abbr>] <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>
 308 </div>
 309 <div class="biblioentry">
 310 <a name="id2588137"></a><p>[<abbr class="abbrev">RFC2136</abbr>] <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>
 311 </div>
 312 <div class="biblioentry">
 313 <a name="id2588193"></a><p>[<abbr class="abbrev">RFC2845</abbr>] <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 <acronym class="acronym">DNS</acronym> (TSIG)</i>. </span><span class="pubdate">May 2000. </span></p>
 314 </div>
 315 </div>
 316 <div class="bibliodiv">
 317 <h3 class="title">Proposed Standards Still Under Development</h3>
 318 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
 319 <h3 class="title">Note</h3>
 320 <p><span class="emphasis"><em>Note:</em></span> the following list of
 321 RFCs are undergoing major revision by the IETF.</p>
 322 </div>
 323 <div class="biblioentry">
 324 <a name="id2588268"></a><p>[<abbr class="abbrev">RFC1886</abbr>] <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><acronym class="acronym">DNS</acronym> Extensions to support IP version 6</i>. </span><span class="pubdate">December 1995. </span></p>
 325 </div>
 326 <div class="biblioentry">
 327 <a name="id2588307"></a><p>[<abbr class="abbrev">RFC2065</abbr>] <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>
 328 </div>
 329 <div class="biblioentry">
 330 <a name="id2588346"></a><p>[<abbr class="abbrev">RFC2137</abbr>] <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>
 331 </div>
 332 </div>
 333 <div class="bibliodiv">
 334 <h3 class="title">Other Important RFCs About <acronym class="acronym">DNS</acronym> Implementation</h3>
 335 <div class="biblioentry">
 336 <a name="id2588382"></a><p>[<abbr class="abbrev">RFC1535</abbr>] <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 <acronym class="acronym">DNS</acronym> Software.</i>. </span><span class="pubdate">October 1993. </span></p>
 337 </div>
 338 <div class="biblioentry">
 339 <a name="id2588408"></a><p>[<abbr class="abbrev">RFC1536</abbr>] <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 <acronym class="acronym">DNS</acronym> Implementation Errors and Suggested Fixes</i>. </span><span class="pubdate">October 1993. </span></p>
 340 </div>
 341 <div class="biblioentry">
 342 <a name="id2588475"></a><p>[<abbr class="abbrev">RFC1982</abbr>] <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>
 343 </div>
 344 </div>
 345 <div class="bibliodiv">
 346 <h3 class="title">Resource Record Types</h3>
 347 <div class="biblioentry">
 348 <a name="id2588517"></a><p>[<abbr class="abbrev">RFC1183</abbr>] <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 <acronym class="acronym">DNS</acronym> RR Definitions</i>. </span><span class="pubdate">October 1990. </span></p>
 349 </div>
 350 <div class="biblioentry">
 351 <a name="id2588574"></a><p>[<abbr class="abbrev">RFC1706</abbr>] <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><acronym class="acronym">DNS</acronym> NSAP Resource Records</i>. </span><span class="pubdate">October 1994. </span></p>
 352 </div>
 353 <div class="biblioentry">
 354 <a name="id2588612"></a><p>[<abbr class="abbrev">RFC2168</abbr>] <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
 355 the Domain Name System</i>. </span><span class="pubdate">June 1997. </span></p>
 356 </div>
 357 <div class="biblioentry">
 358 <a name="id2588647"></a><p>[<abbr class="abbrev">RFC1876</abbr>] <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
 359 Name System</i>. </span><span class="pubdate">January 1996. </span></p>
 360 </div>
 361 <div class="biblioentry">
 362 <a name="id2588701"></a><p>[<abbr class="abbrev">RFC2052</abbr>] <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 <acronym class="acronym">DNS</acronym> RR for Specifying the Location of
 363 Services.</i>. </span><span class="pubdate">October 1996. </span></p>
 364 </div>
 365 <div class="biblioentry">
 366 <a name="id2588741"></a><p>[<abbr class="abbrev">RFC2163</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Allocchio</span>. </span><span class="title"><i>Using the Internet <acronym class="acronym">DNS</acronym> to Distribute MIXER
 367 Conformant Global Address Mapping</i>. </span><span class="pubdate">January 1998. </span></p>
 368 </div>
 369 <div class="biblioentry">
 370 <a name="id2588768"></a><p>[<abbr class="abbrev">RFC2230</abbr>] <span class="author"><span class="firstname">R.</span> <span class="surname">Atkinson</span>. </span><span class="title"><i>Key Exchange Delegation Record for the <acronym class="acronym">DNS</acronym></i>. </span><span class="pubdate">October 1997. </span></p>
 371 </div>
 372 </div>
 373 <div class="bibliodiv">
 374 <h3 class="title">
 375 <acronym class="acronym">DNS</acronym> and the Internet</h3>
 376 <div class="biblioentry">
 377 <a name="id2588802"></a><p>[<abbr class="abbrev">RFC1101</abbr>] <span class="author"><span class="firstname">P. V.</span> <span class="surname">Mockapetris</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Encoding of Network Names and Other Types</i>. </span><span class="pubdate">April 1989. </span></p>
 378 </div>
 379 <div class="biblioentry">
 380 <a name="id2588827"></a><p>[<abbr class="abbrev">RFC1123</abbr>] <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>
 381 </div>
 382 <div class="biblioentry">
 383 <a name="id2588851"></a><p>[<abbr class="abbrev">RFC1591</abbr>] <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>
 384 </div>
 385 <div class="biblioentry">
 386 <a name="id2588872"></a><p>[<abbr class="abbrev">RFC2317</abbr>] <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>
 387 </div>
 388 </div>
 389 <div class="bibliodiv">
 390 <h3 class="title">
 391 <acronym class="acronym">DNS</acronym> Operations</h3>
 392 <div class="biblioentry">
 393 <a name="id2588995"></a><p>[<abbr class="abbrev">RFC1537</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Beertema</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Data File Configuration Errors</i>. </span><span class="pubdate">October 1993. </span></p>
 394 </div>
 395 <div class="biblioentry">
 396 <a name="id2589020"></a><p>[<abbr class="abbrev">RFC1912</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Barr</span>. </span><span class="title"><i>Common <acronym class="acronym">DNS</acronym> Operational and Configuration Errors</i>. </span><span class="pubdate">February 1996. </span></p>
 397 </div>
 398 <div class="biblioentry">
 399 <a name="id2589047"></a><p>[<abbr class="abbrev">RFC2010</abbr>] <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>
 400 </div>
 401 <div class="biblioentry">
 402 <a name="id2589083"></a><p>[<abbr class="abbrev">RFC2219</abbr>] <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 <acronym class="acronym">DNS</acronym> Aliases for Network Services.</i>. </span><span class="pubdate">October 1997. </span></p>
 403 </div>
 404 </div>
 405 <div class="bibliodiv">
 406 <h3 class="title">Other <acronym class="acronym">DNS</acronym>-related RFCs</h3>
 407 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
 408 <h3 class="title">Note</h3>
 409 <p>Note: the following list of RFCs, although
 410 <acronym class="acronym">DNS</acronym>-related, are not concerned with implementing software.</p>
 411 </div>
 412 <div class="biblioentry">
 413 <a name="id2589143"></a><p>[<abbr class="abbrev">RFC1464</abbr>] <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>
 414 </div>
 415 <div class="biblioentry">
 416 <a name="id2589165"></a><p>[<abbr class="abbrev">RFC1713</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Romao</span>. </span><span class="title"><i>Tools for <acronym class="acronym">DNS</acronym> Debugging</i>. </span><span class="pubdate">November 1994. </span></p>
 417 </div>
 418 <div class="biblioentry">
 419 <a name="id2589190"></a><p>[<abbr class="abbrev">RFC1794</abbr>] <span class="author"><span class="firstname">T.</span> <span class="surname">Brisco</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Support for Load Balancing</i>. </span><span class="pubdate">April 1995. </span></p>
 420 </div>
 421 <div class="biblioentry">
 422 <a name="id2589214"></a><p>[<abbr class="abbrev">RFC2240</abbr>] <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>
 423 </div>
 424 <div class="biblioentry">
 425 <a name="id2589237"></a><p>[<abbr class="abbrev">RFC2345</abbr>] <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>
 426 </div>
 427 <div class="biblioentry">
 428 <a name="id2589283"></a><p>[<abbr class="abbrev">RFC2352</abbr>] <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>
 429 </div>
 430 </div>
 431 <div class="bibliodiv">
 432 <h3 class="title">Obsolete and Unimplemented Experimental RRs</h3>
 433 <div class="biblioentry">
 434 <a name="id2589314"></a><p>[<abbr class="abbrev">RFC1712</abbr>] <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><acronym class="acronym">DNS</acronym> Encoding of Geographical
 435 Location</i>. </span><span class="pubdate">November 1994. </span></p>
 436 </div>
 437 </div>
 438 </div>
 439 </div>
 440 <div class="sect2" lang="en">
 441 <div class="titlepage"><div><div><h3 class="title">
 442 <a name="internet_drafts"></a>Internet Drafts</h3></div></div></div>
 443 <p>Internet Drafts (IDs) are rough-draft working documents of
 444 the Internet Engineering Task Force. They are, in essence, RFCs
 445 in the preliminary stages of development. Implementors are cautioned not
 446 to regard IDs as archival, and they should not be quoted or cited
 447 in any formal documents unless accompanied by the disclaimer that
 448 they are "works in progress." IDs have a lifespan of six months
 449 after which they are deleted unless updated by their authors.
 450 </p>
 451 </div>
 452 <div class="sect2" lang="en">
 453 <div class="titlepage"><div><div><h3 class="title">
 454 <a name="id2589386"></a>Other Documents About <acronym class="acronym">BIND</acronym>
 455 </h3></div></div></div>
 456 <p></p>
 457 <div class="bibliography">
 458 <div class="titlepage"><div><div><h4 class="title">
 459 <a name="id2589396"></a>Bibliography</h4></div></div></div>
 460 <div class="biblioentry">
 461 <a name="id2589398"></a><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><acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></i>. </span><span class="copyright">Copyright © 1998 Sebastopol, CA: O'Reilly and Associates. </span></p>
 462 </div>
 463 </div>
 464 </div>
 465 </div>
 466 </div>
 467 <div class="navfooter">
 468 <hr>
 469 <table width="100%" summary="Navigation footer">
 470 <tr>
 471 <td width="40%" align="left">
 472 <a accesskey="p" href="Bv9ARM.ch08.html">Prev</a> </td>
 473 <td width="20%" align="center"> </td>
 474 <td width="40%" align="right"> </td>
 475 </tr>
 476 <tr>
 477 <td width="40%" align="left" valign="top">Chapter 8. Troubleshooting </td>
 478 <td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
 479 <td width="40%" align="right" valign="top"> </td>
 480 </tr>
 481 </table>
 482 </div>
 483 </body>
 484 </html>