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

   1 <!--
   2  - Copyright (C) 2004-2006 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.35 2006/11/15 04:33:42 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.70.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#id2592339">Acknowledgments</a></span></dt>
  47 <dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2592344">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#id2594702">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="id2592339"></a>Acknowledgments</h2></div></div></div>
  61 <div class="sect2" lang="en">
  62 <div class="titlepage"><div><div><h3 class="title">
  63 <a name="id2592344"></a>A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></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 a 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 <acronym class="acronym">DNS</acronym> 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 <acronym class="acronym">DNS</acronym> server for Unix machines, the Berkeley Internet
  83 Name Domain (<acronym class="acronym">BIND</acronym>) 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).
  87 </p>
  88 <p>
  89 Versions of <acronym class="acronym">BIND</acronym> through 4.8.3 were maintained by the Computer
  90 Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
  91 Painter, David Riggle and Songnian Zhou made up the initial <acronym class="acronym">BIND</acronym>
  92 project team. After that, additional work on the software package
  93 was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation
  94 employee on loan to the CSRG, worked on <acronym class="acronym">BIND</acronym> for 2 years, from 1985
  95 to 1987. Many other people also contributed to <acronym class="acronym">BIND</acronym> development
  96 during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell,
  97 Mike Muuss, Jim Bloom and Mike Schwartz. <acronym class="acronym">BIND</acronym> maintenance was subsequently
  98 handled by Mike Karels and O. Kure.</p>
  99 <p><acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were released by Digital Equipment
 100 Corporation (now Compaq Computer Corporation). Paul Vixie, then
 101 a DEC employee, became <acronym class="acronym">BIND</acronym>'s primary caretaker. He was assisted
 102 by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew
 103 Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat
 104 Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
 105 Wolfhugel, and others.</p>
 106 <p><acronym class="acronym">BIND</acronym> version 4.9.2 was sponsored by Vixie Enterprises. Paul
 107 Vixie became <acronym class="acronym">BIND</acronym>'s principal architect/programmer.</p>
 108 <p><acronym class="acronym">BIND</acronym> versions from 4.9.3 onward have been developed and maintained
 109 by the Internet Software Consortium with support being provided
 110 by ISC's sponsors. As co-architects/programmers, Bob Halley and
 111 Paul Vixie released the first production-ready version of <acronym class="acronym">BIND</acronym> version
 112 8 in May 1997.</p>
 113 <p><acronym class="acronym">BIND</acronym> development work is made possible today by the sponsorship
 114 of several corporations, and by the tireless work efforts of numerous
 115 individuals.</p>
 116 </div>
 117 </div>
 118 <div class="sect1" lang="en">
 119 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 120 <a name="historical_dns_information"></a>General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div>
 121 <div class="sect2" lang="en">
 122 <div class="titlepage"><div><div><h3 class="title">
 123 <a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h3></div></div></div>
 124 <p>IPv6 addresses are 128-bit identifiers for interfaces and
 125 sets of interfaces which were introduced in the <acronym class="acronym">DNS</acronym> to facilitate
 126 scalable Internet routing. There are three types of addresses: <span class="emphasis"><em>Unicast</em></span>,
 127 an identifier for a single interface; <span class="emphasis"><em>Anycast</em></span>,
 128 an identifier for a set of interfaces; and <span class="emphasis"><em>Multicast</em></span>,
 129 an identifier for a set of interfaces. Here we describe the global
 130 Unicast address scheme. For more information, see RFC 2374.</p>
 131 <p>The aggregatable global Unicast address format is as follows:</p>
 132 <div class="informaltable"><table border="1">
 133 <colgroup>
 134 <col>
 135 <col>
 136 <col>
 137 <col>
 138 <col>
 139 <col>
 140 </colgroup>
 141 <tbody>
 142 <tr>
 143 <td><p>3</p></td>
 144 <td><p>13</p></td>
 145 <td><p>8</p></td>
 146 <td><p>24</p></td>
 147 <td><p>16</p></td>
 148 <td><p>64 bits</p></td>
 149 </tr>
 150 <tr>
 151 <td><p>FP</p></td>
 152 <td><p>TLA ID</p></td>
 153 <td><p>RES</p></td>
 154 <td><p>NLA ID</p></td>
 155 <td><p>SLA ID</p></td>
 156 <td><p>Interface ID</p></td>
 157 </tr>
 158 <tr>
 159 <td colspan="4"><p>&lt;------ Public Topology
 160 ------&gt;</p></td>
 161 <td><p></p></td>
 162 <td><p></p></td>
 163 </tr>
 164 <tr>
 165 <td><p></p></td>
 166 <td><p></p></td>
 167 <td><p></p></td>
 168 <td><p></p></td>
 169 <td><p>&lt;-Site Topology-&gt;</p></td>
 170 <td><p></p></td>
 171 </tr>
 172 <tr>
 173 <td><p></p></td>
 174 <td><p></p></td>
 175 <td><p></p></td>
 176 <td><p></p></td>
 177 <td><p></p></td>
 178 <td><p>&lt;------ Interface Identifier ------&gt;</p></td>
 179 </tr>
 180 </tbody>
 181 </table></div>
 182 <p>Where
 183 </p>
 184 <div class="informaltable"><table border="1">
 185 <colgroup>
 186 <col>
 187 <col>
 188 <col>
 189 </colgroup>
 190 <tbody>
 191 <tr>
 192 <td><p>FP</p></td>
 193 <td><p>=</p></td>
 194 <td><p>Format Prefix (001)</p></td>
 195 </tr>
 196 <tr>
 197 <td><p>TLA ID</p></td>
 198 <td><p>=</p></td>
 199 <td><p>Top-Level Aggregation Identifier</p></td>
 200 </tr>
 201 <tr>
 202 <td><p>RES</p></td>
 203 <td><p>=</p></td>
 204 <td><p>Reserved for future use</p></td>
 205 </tr>
 206 <tr>
 207 <td><p>NLA ID</p></td>
 208 <td><p>=</p></td>
 209 <td><p>Next-Level Aggregation Identifier</p></td>
 210 </tr>
 211 <tr>
 212 <td><p>SLA ID</p></td>
 213 <td><p>=</p></td>
 214 <td><p>Site-Level Aggregation Identifier</p></td>
 215 </tr>
 216 <tr>
 217 <td><p>INTERFACE ID</p></td>
 218 <td><p>=</p></td>
 219 <td><p>Interface Identifier</p></td>
 220 </tr>
 221 </tbody>
 222 </table></div>
 223 <p>The <span class="emphasis"><em>Public Topology</em></span> is provided by the
 224 upstream provider or ISP, and (roughly) corresponds to the IPv4 <span class="emphasis"><em>network</em></span> section
 225 of the address range. The <span class="emphasis"><em>Site Topology</em></span> is
 226 where you can subnet this space, much the same as subnetting an
 227 IPv4 /16 network into /24 subnets. The <span class="emphasis"><em>Interface Identifier</em></span> is
 228 the address of an individual interface on a given network. (With
 229 IPv6, addresses belong to interfaces rather than machines.)</p>
 230 <p>The subnetting capability of IPv6 is much more flexible than
 231 that of IPv4: subnetting can now be carried out on bit boundaries,
 232 in much the same way as Classless InterDomain Routing (CIDR).</p>
 233 <p>The Interface Identifier must be unique on that network. On
 234 ethernet networks, one way to ensure this is to set the address
 235 to the first three bytes of the hardware address, "FFFE", then the
 236 last three bytes of the hardware address. The lowest significant
 237 bit of the first byte should then be complemented. Addresses are
 238 written as 32-bit blocks separated with a colon, and leading zeros
 239 of a block may be omitted, for example:</p>
 240 <p><span><strong class="command">2001:db8:201:9:a00:20ff:fe81:2b32</strong></span></p>
 241 <p>IPv6 address specifications are likely to contain long strings
 242 of zeros, so the architects have included a shorthand for specifying
 243 them. The double colon (`::') indicates the longest possible string
 244 of zeros that can fit, and can be used only once in an address.</p>
 245 </div>
 246 </div>
 247 <div class="sect1" lang="en">
 248 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
 249 <a name="bibliography"></a>Bibliography (and Suggested Reading)</h2></div></div></div>
 250 <div class="sect2" lang="en">
 251 <div class="titlepage"><div><div><h3 class="title">
 252 <a name="rfcs"></a>Request for Comments (RFCs)</h3></div></div></div>
 253 <p>Specification documents for the Internet protocol suite, including
 254 the <acronym class="acronym">DNS</acronym>, are published as part of the Request for Comments (RFCs)
 255 series of technical notes. The standards themselves are defined
 256 by the Internet Engineering Task Force (IETF) and the Internet Engineering
 257 Steering Group (IESG). RFCs can be obtained online via FTP at
 258 <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
 259 the number of the RFC). RFCs are also available via the Web at
 260 <a href="http://www.ietf.org/rfc/" target="_top">http://www.ietf.org/rfc/</a>.
 261 </p>
 262 <div class="bibliography">
 263 <div class="titlepage"><div><div><h4 class="title">
 264 <a name="id2593259"></a>Bibliography</h4></div></div></div>
 265 <div class="bibliodiv">
 266 <h3 class="title">Standards</h3>
 267 <div class="biblioentry">
 268 <a name="id2593270"></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>
 269 </div>
 270 <div class="biblioentry">
 271 <a name="id2593293"></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>
 272 </div>
 273 <div class="biblioentry">
 274 <a name="id2593317"></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
 275 Specification</i>. </span><span class="pubdate">November 1987. </span></p>
 276 </div>
 277 </div>
 278 <div class="bibliodiv">
 279 <h3 class="title">
 280 <a name="proposed_standards"></a>Proposed Standards</h3>
 281 <div class="biblioentry">
 282 <a name="id2593354"></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>
 283 </div>
 284 <div class="biblioentry">
 285 <a name="id2593380"></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>
 286 </div>
 287 <div class="biblioentry">
 288 <a name="id2593405"></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>
 289 </div>
 290 <div class="biblioentry">
 291 <a name="id2593430"></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>
 292 </div>
 293 <div class="biblioentry">
 294 <a name="id2593522"></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>
 295 </div>
 296 <div class="biblioentry">
 297 <a name="id2593577"></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>
 298 </div>
 299 </div>
 300 <div class="bibliodiv">
 301 <h3 class="title">Proposed Standards Still Under Development</h3>
 302 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
 303 <h3 class="title">Note</h3>
 304 <p><span class="emphasis"><em>Note:</em></span> the following list of
 305 RFCs are undergoing major revision by the IETF.</p>
 306 </div>
 307 <div class="biblioentry">
 308 <a name="id2593653"></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>
 309 </div>
 310 <div class="biblioentry">
 311 <a name="id2593691"></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>
 312 </div>
 313 <div class="biblioentry">
 314 <a name="id2593731"></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>
 315 </div>
 316 </div>
 317 <div class="bibliodiv">
 318 <h3 class="title">Other Important RFCs About <acronym class="acronym">DNS</acronym> Implementation</h3>
 319 <div class="biblioentry">
 320 <a name="id2593767"></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>
 321 </div>
 322 <div class="biblioentry">
 323 <a name="id2593793"></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>
 324 </div>
 325 <div class="biblioentry">
 326 <a name="id2593860"></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>
 327 </div>
 328 </div>
 329 <div class="bibliodiv">
 330 <h3 class="title">Resource Record Types</h3>
 331 <div class="biblioentry">
 332 <a name="id2593901"></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>
 333 </div>
 334 <div class="biblioentry">
 335 <a name="id2593959"></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>
 336 </div>
 337 <div class="biblioentry">
 338 <a name="id2593996"></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
 339 the Domain Name System</i>. </span><span class="pubdate">June 1997. </span></p>
 340 </div>
 341 <div class="biblioentry">
 342 <a name="id2594032"></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
 343 Name System</i>. </span><span class="pubdate">January 1996. </span></p>
 344 </div>
 345 <div class="biblioentry">
 346 <a name="id2594086"></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
 347 Services.</i>. </span><span class="pubdate">October 1996. </span></p>
 348 </div>
 349 <div class="biblioentry">
 350 <a name="id2594125"></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
 351 Conformant Global Address Mapping</i>. </span><span class="pubdate">January 1998. </span></p>
 352 </div>
 353 <div class="biblioentry">
 354 <a name="id2594152"></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>
 355 </div>
 356 </div>
 357 <div class="bibliodiv">
 358 <h3 class="title">
 359 <acronym class="acronym">DNS</acronym> and the Internet</h3>
 360 <div class="biblioentry">
 361 <a name="id2594186"></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>
 362 </div>
 363 <div class="biblioentry">
 364 <a name="id2594212"></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>
 365 </div>
 366 <div class="biblioentry">
 367 <a name="id2594235"></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>
 368 </div>
 369 <div class="biblioentry">
 370 <a name="id2594257"></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>
 371 </div>
 372 </div>
 373 <div class="bibliodiv">
 374 <h3 class="title">
 375 <acronym class="acronym">DNS</acronym> Operations</h3>
 376 <div class="biblioentry">
 377 <a name="id2594311"></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>
 378 </div>
 379 <div class="biblioentry">
 380 <a name="id2594337"></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>
 381 </div>
 382 <div class="biblioentry">
 383 <a name="id2594363"></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>
 384 </div>
 385 <div class="biblioentry">
 386 <a name="id2594400"></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>
 387 </div>
 388 </div>
 389 <div class="bibliodiv">
 390 <h3 class="title">Other <acronym class="acronym">DNS</acronym>-related RFCs</h3>
 391 <div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
 392 <h3 class="title">Note</h3>
 393 <p>Note: the following list of RFCs, although
 394 <acronym class="acronym">DNS</acronym>-related, are not concerned with implementing software.</p>
 395 </div>
 396 <div class="biblioentry">
 397 <a name="id2594459"></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>
 398 </div>
 399 <div class="biblioentry">
 400 <a name="id2594482"></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>
 401 </div>
 402 <div class="biblioentry">
 403 <a name="id2594506"></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>
 404 </div>
 405 <div class="biblioentry">
 406 <a name="id2594531"></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>
 407 </div>
 408 <div class="biblioentry">
 409 <a name="id2594553"></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>
 410 </div>
 411 <div class="biblioentry">
 412 <a name="id2594599"></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>
 413 </div>
 414 </div>
 415 <div class="bibliodiv">
 416 <h3 class="title">Obsolete and Unimplemented Experimental RRs</h3>
 417 <div class="biblioentry">
 418 <a name="id2594630"></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
 419 Location</i>. </span><span class="pubdate">November 1994. </span></p>
 420 </div>
 421 </div>
 422 </div>
 423 </div>
 424 <div class="sect2" lang="en">
 425 <div class="titlepage"><div><div><h3 class="title">
 426 <a name="internet_drafts"></a>Internet Drafts</h3></div></div></div>
 427 <p>Internet Drafts (IDs) are rough-draft working documents of
 428 the Internet Engineering Task Force. They are, in essence, RFCs
 429 in the preliminary stages of development. Implementors are cautioned not
 430 to regard IDs as archival, and they should not be quoted or cited
 431 in any formal documents unless accompanied by the disclaimer that
 432 they are "works in progress." IDs have a lifespan of six months
 433 after which they are deleted unless updated by their authors.
 434 </p>
 435 </div>
 436 <div class="sect2" lang="en">
 437 <div class="titlepage"><div><div><h3 class="title">
 438 <a name="id2594702"></a>Other Documents About <acronym class="acronym">BIND</acronym></h3></div></div></div>
 439 <p></p>
 440 <div class="bibliography">
 441 <div class="titlepage"><div><div><h4 class="title">
 442 <a name="id2594712"></a>Bibliography</h4></div></div></div>
 443 <div class="biblioentry">
 444 <a name="id2594714"></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>
 445 </div>
 446 </div>
 447 </div>
 448 </div>
 449 </div>
 450 <div class="navfooter">
 451 <hr>
 452 <table width="100%" summary="Navigation footer">
 453 <tr>
 454 <td width="40%" align="left">
 455 <a accesskey="p" href="Bv9ARM.ch08.html">Prev</a> </td>
 456 <td width="20%" align="center"> </td>
 457 <td width="40%" align="right"> </td>
 458 </tr>
 459 <tr>
 460 <td width="40%" align="left" valign="top">Chapter 8. Troubleshooting </td>
 461 <td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
 462 <td width="40%" align="right" valign="top"> </td>
 463 </tr>
 464 </table>
 465 </div>
 466 </body>
 467 </html>