<HTML ><HEAD ><TITLE >Appendices</TITLE ><META NAME="GENERATOR" CONTENT="Modular DocBook HTML Stylesheet Version 1.73 "><LINK REL="HOME" TITLE="BIND 9 Administrator Reference Manual" HREF="Bv9ARM.html"><LINK REL="PREVIOUS" TITLE="Troubleshooting" HREF="Bv9ARM.ch08.html"></HEAD ><BODY CLASS="appendix" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#840084" ALINK="#0000FF" ><DIV CLASS="NAVHEADER" ><TABLE SUMMARY="Header navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TH COLSPAN="3" ALIGN="center" >BIND 9 Administrator Reference Manual</TH ></TR ><TR ><TD WIDTH="10%" ALIGN="left" VALIGN="bottom" ><A HREF="Bv9ARM.ch08.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="80%" ALIGN="center" VALIGN="bottom" ></TD ><TD WIDTH="10%" ALIGN="right" VALIGN="bottom" > </TD ></TR ></TABLE ><HR ALIGN="LEFT" WIDTH="100%"></DIV ><DIV CLASS="appendix" ><H1 ><A NAME="ch09" >Appendix A. Appendices</A ></H1 ><DIV CLASS="TOC" ><DL ><DT ><B >Table of Contents</B ></DT ><DT >A.1. <A HREF="Bv9ARM.ch09.html#AEN4306" >Acknowledgements</A ></DT ><DT >A.2. <A HREF="Bv9ARM.ch09.html#historical_dns_information" >Historical <SPAN CLASS="acronym" >DNS</SPAN > Information</A ></DT ><DT >A.3. <A HREF="Bv9ARM.ch09.html#AEN4347" >General <SPAN CLASS="acronym" >DNS</SPAN > Reference Information</A ></DT ><DT >A.4. <A HREF="Bv9ARM.ch09.html#bibliography" >Bibliography (and Suggested Reading)</A ></DT ></DL ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A NAME="AEN4306" >A.1. Acknowledgements</A ></H1 ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="AEN4308" >A.1.1. A Brief History of the <SPAN CLASS="acronym" >DNS</SPAN > and <SPAN CLASS="acronym" >BIND</SPAN ></A ></H2 ><P >Although the "official" beginning of the Domain Name System occurred in 1984 with the publication of RFC 920, the core of the new system was described in 1983 in RFCs 882 and 883. From 1984 to 1987, the ARPAnet (the precursor to today's Internet) became a testbed of experimentation for developing the new naming/addressing scheme in an rapidly expanding, operational network environment. New RFCs were written and published in 1987 that modified the original documents to incorporate improvements based on the working model. RFC 1034, "Domain Names-Concepts and Facilities," and RFC 1035, "Domain Names-Implementation and Specification" were published and became the standards upon which all <SPAN CLASS="acronym" >DNS</SPAN > implementations are built. </P ><P >The first working domain name server, called "Jeeves," was written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20 machines located at the University of Southern California's Information Sciences Institute (USC-ISI) and SRI International's Network Information Center (SRI-NIC). A <SPAN CLASS="acronym" >DNS</SPAN > server for Unix machines, the Berkeley Internet Name Domain (<SPAN CLASS="acronym" >BIND</SPAN >) package, was written soon after by a group of graduate students at the University of California at Berkeley under a grant from the US Defense Advanced Research Projects Administration (DARPA). Versions of <SPAN CLASS="acronym" >BIND</SPAN > through 4.8.3 were maintained by the Computer Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark Painter, David Riggle and Songnian Zhou made up the initial <SPAN CLASS="acronym" >BIND</SPAN > project team. After that, additional work on the software package was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation employee on loan to the CSRG, worked on <SPAN CLASS="acronym" >BIND</SPAN > for 2 years, from 1985 to 1987. Many other people also contributed to <SPAN CLASS="acronym" >BIND</SPAN > development during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell, Mike Muuss, Jim Bloom and Mike Schwartz. <SPAN CLASS="acronym" >BIND</SPAN > maintenance was subsequently handled by Mike Karels and O. Kure.</P ><P ><SPAN CLASS="acronym" >BIND</SPAN > versions 4.9 and 4.9.1 were released by Digital Equipment Corporation (now Compaq Computer Corporation). Paul Vixie, then a DEC employee, became <SPAN CLASS="acronym" >BIND</SPAN >'s primary caretaker. Paul was assisted by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe Wolfhugel, and others.</P ><P ><SPAN CLASS="acronym" >BIND</SPAN > Version 4.9.2 was sponsored by Vixie Enterprises. Paul Vixie became <SPAN CLASS="acronym" >BIND</SPAN >'s principal architect/programmer.</P ><P ><SPAN CLASS="acronym" >BIND</SPAN > versions from 4.9.3 onward have been developed and maintained by the Internet Software Consortium with support being provided by ISC's sponsors. As co-architects/programmers, Bob Halley and Paul Vixie released the first production-ready version of <SPAN CLASS="acronym" >BIND</SPAN > version 8 in May 1997.</P ><P ><SPAN CLASS="acronym" >BIND</SPAN > development work is made possible today by the sponsorship of several corporations, and by the tireless work efforts of numerous individuals.</P ></DIV ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A NAME="historical_dns_information" >A.2. Historical <SPAN CLASS="acronym" >DNS</SPAN > Information</A ></H1 ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="classes_of_resource_records" >A.2.1. Classes of Resource Records</A ></H2 ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A NAME="AEN4338" >A.2.1.1. HS = hesiod</A ></H3 ><P >The [<SPAN CLASS="optional" >hesiod</SPAN >] class is an information service developed by MIT's Project Athena. It is used to share information about various systems databases, such as users, groups, printers and so on. The keyword <B CLASS="command" >hs</B > is a synonym for hesiod.</P ></DIV ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A NAME="AEN4343" >A.2.1.2. CH = chaos</A ></H3 ><P >The <B CLASS="command" >chaos</B > class is used to specify zone data for the MIT-developed CHAOSnet, a LAN protocol created in the mid-1970s.</P ></DIV ></DIV ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A NAME="AEN4347" >A.3. General <SPAN CLASS="acronym" >DNS</SPAN > Reference Information</A ></H1 ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="ipv6addresses" >A.3.1. IPv6 addresses (A6)</A ></H2 ><P >IPv6 addresses are 128-bit identifiers for interfaces and sets of interfaces which were introduced in the <SPAN CLASS="acronym" >DNS</SPAN > to facilitate scalable Internet routing. There are three types of addresses: <SPAN CLASS="emphasis" ><I CLASS="emphasis" >Unicast</I ></SPAN >, an identifier for a single interface; <SPAN CLASS="emphasis" ><I CLASS="emphasis" >Anycast</I ></SPAN >, an identifier for a set of interfaces; and <SPAN CLASS="emphasis" ><I CLASS="emphasis" >Multicast</I ></SPAN >, an identifier for a set of interfaces. Here we describe the global Unicast address scheme. For more information, see RFC 2374.</P ><P >The aggregatable global Unicast address format is as follows:</P ><DIV CLASS="informaltable" ><A NAME="AEN4358" ></A ><P ></P ><TABLE CELLPADDING="3" BORDER="1" CLASS="CALSTABLE" ><TBODY ><TR ><TD WIDTH="46" ALIGN="LEFT" VALIGN="MIDDLE" ><P >3</P ></TD ><TD WIDTH="48" ALIGN="LEFT" VALIGN="MIDDLE" ><P >13</P ></TD ><TD WIDTH="50" ALIGN="LEFT" VALIGN="MIDDLE" ><P >8</P ></TD ><TD WIDTH="70" ALIGN="LEFT" VALIGN="MIDDLE" ><P >24</P ></TD ><TD WIDTH="129" ALIGN="LEFT" VALIGN="MIDDLE" ><P >16</P ></TD ><TD WIDTH="243" ALIGN="LEFT" VALIGN="MIDDLE" ><P >64 bits</P ></TD ></TR ><TR ><TD WIDTH="46" ALIGN="LEFT" VALIGN="MIDDLE" ><P >FP</P ></TD ><TD WIDTH="48" ALIGN="LEFT" VALIGN="MIDDLE" ><P >TLA ID</P ></TD ><TD WIDTH="50" ALIGN="LEFT" VALIGN="MIDDLE" ><P >RES</P ></TD ><TD WIDTH="70" ALIGN="LEFT" VALIGN="MIDDLE" ><P >NLA ID</P ></TD ><TD WIDTH="129" ALIGN="LEFT" VALIGN="MIDDLE" ><P >SLA ID</P ></TD ><TD WIDTH="243" ALIGN="LEFT" VALIGN="MIDDLE" ><P >Interface ID</P ></TD ></TR ><TR ><TD COLSPAN="4" ALIGN="LEFT" VALIGN="MIDDLE" ><P ><------ Public Topology ------></P ></TD ><TD WIDTH="129" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="243" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ></TR ><TR ><TD WIDTH="46" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="48" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="50" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="70" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="129" ALIGN="LEFT" VALIGN="MIDDLE" ><P ><-Site Topology-></P ></TD ><TD WIDTH="243" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ></TR ><TR ><TD WIDTH="46" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="48" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="50" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="70" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="129" ALIGN="LEFT" VALIGN="MIDDLE" ><P ></P ></TD ><TD WIDTH="243" ALIGN="LEFT" VALIGN="MIDDLE" ><P ><------ Interface Identifier ------></P ></TD ></TR ></TBODY ></TABLE ><P ></P ></DIV ><P >Where <DIV CLASS="informaltable" ><A NAME="AEN4427" ></A ><P ></P ><TABLE CELLPADDING="3" BORDER="1" CLASS="CALSTABLE" ><TBODY ><TR ><TD WIDTH="132" ALIGN="LEFT" VALIGN="MIDDLE" ><P >FP</P ></TD ><TD WIDTH="24" ALIGN="LEFT" VALIGN="MIDDLE" ><P >=</P ></TD ><TD WIDTH="336" ALIGN="LEFT" VALIGN="MIDDLE" ><P >Format Prefix (001)</P ></TD ></TR ><TR ><TD WIDTH="132" ALIGN="LEFT" VALIGN="MIDDLE" ><P >TLA ID</P ></TD ><TD WIDTH="24" ALIGN="LEFT" VALIGN="MIDDLE" ><P >=</P ></TD ><TD WIDTH="336" ALIGN="LEFT" VALIGN="MIDDLE" ><P >Top-Level Aggregation Identifier</P ></TD ></TR ><TR ><TD WIDTH="132" ALIGN="LEFT" VALIGN="MIDDLE" ><P >RES</P ></TD ><TD WIDTH="24" ALIGN="LEFT" VALIGN="MIDDLE" ><P >=</P ></TD ><TD WIDTH="336" ALIGN="LEFT" VALIGN="MIDDLE" ><P >Reserved for future use</P ></TD ></TR ><TR ><TD WIDTH="132" ALIGN="LEFT" VALIGN="MIDDLE" ><P >NLA ID</P ></TD ><TD WIDTH="24" ALIGN="LEFT" VALIGN="MIDDLE" ><P >=</P ></TD ><TD WIDTH="336" ALIGN="LEFT" VALIGN="MIDDLE" ><P >Next-Level Aggregation Identifier</P ></TD ></TR ><TR ><TD WIDTH="132" ALIGN="LEFT" VALIGN="MIDDLE" ><P >SLA ID</P ></TD ><TD WIDTH="24" ALIGN="LEFT" VALIGN="MIDDLE" ><P >=</P ></TD ><TD WIDTH="336" ALIGN="LEFT" VALIGN="MIDDLE" ><P >Site-Level Aggregation Identifier</P ></TD ></TR ><TR ><TD WIDTH="132" ALIGN="LEFT" VALIGN="MIDDLE" ><P >INTERFACE ID</P ></TD ><TD WIDTH="24" ALIGN="LEFT" VALIGN="MIDDLE" ><P >=</P ></TD ><TD WIDTH="336" ALIGN="LEFT" VALIGN="MIDDLE" ><P >Interface Identifier</P ></TD ></TR ></TBODY ></TABLE ><P ></P ></DIV ></P ><P >The <SPAN CLASS="emphasis" ><I CLASS="emphasis" >Public Topology</I ></SPAN > is provided by the upstream provider or ISP, and (roughly) corresponds to the IPv4 <SPAN CLASS="emphasis" ><I CLASS="emphasis" >network</I ></SPAN > section of the address range. The <SPAN CLASS="emphasis" ><I CLASS="emphasis" >Site Topology</I ></SPAN > is where you can subnet this space, much the same as subnetting an IPv4 /16 network into /24 subnets. The <SPAN CLASS="emphasis" ><I CLASS="emphasis" >Interface Identifier</I ></SPAN > is the address of an individual interface on a given network. (With IPv6, addresses belong to interfaces rather than machines.)</P ><P >The subnetting capability of IPv6 is much more flexible than that of IPv4: subnetting can now be carried out on bit boundaries, in much the same way as Classless InterDomain Routing (CIDR).</P ><P >The internal structure of the Public Topology for an A6 global unicast address consists of:</P ><DIV CLASS="informaltable" ><A NAME="AEN4482" ></A ><P ></P ><TABLE CELLPADDING="3" BORDER="1" CLASS="CALSTABLE" ><TBODY ><TR ><TD WIDTH="49" ALIGN="LEFT" VALIGN="MIDDLE" ><P >3</P ></TD ><TD WIDTH="64" ALIGN="LEFT" VALIGN="MIDDLE" ><P >13</P ></TD ><TD WIDTH="53" ALIGN="LEFT" VALIGN="MIDDLE" ><P >8</P ></TD ><TD WIDTH="79" ALIGN="LEFT" VALIGN="MIDDLE" ><P >24</P ></TD ></TR ><TR ><TD WIDTH="49" ALIGN="LEFT" VALIGN="MIDDLE" ><P >FP</P ></TD ><TD WIDTH="64" ALIGN="LEFT" VALIGN="MIDDLE" ><P >TLA ID</P ></TD ><TD WIDTH="53" ALIGN="LEFT" VALIGN="MIDDLE" ><P >RES</P ></TD ><TD WIDTH="79" ALIGN="LEFT" VALIGN="MIDDLE" ><P >NLA ID</P ></TD ></TR ></TBODY ></TABLE ><P ></P ></DIV ><P >A 3 bit FP (Format Prefix) of 001 indicates this is a global Unicast address. FP lengths for other types of addresses may vary.</P ><P >13 TLA (Top Level Aggregator) bits give the prefix of your top-level IP backbone carrier.</P ><P >8 Reserved bits</P ><P >24 bits for Next Level Aggregators. This allows organizations with a TLA to hand out portions of their IP space to client organizations, so that the client can then split up the network further by filling in more NLA bits, and hand out IPv6 prefixes to their clients, and so forth.</P ><P >There is no particular structure for the Site topology section. Organizations can allocate these bits in any way they desire.</P ><P >The Interface Identifier must be unique on that network. On ethernet networks, one way to ensure this is to set the address to the first three bytes of the hardware address, "FFFE", then the last three bytes of the hardware address. The lowest significant bit of the first byte should then be complemented. Addresses are written as 32-bit blocks separated with a colon, and leading zeros of a block may be omitted, for example:</P ><P ><B CLASS="command" >3ffe:8050:201:9:a00:20ff:fe81:2b32</B ></P ><P >IPv6 address specifications are likely to contain long strings of zeros, so the architects have included a shorthand for specifying them. The double colon (`::') indicates the longest possible string of zeros that can fit, and can be used only once in an address.</P ></DIV ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A NAME="bibliography" >A.4. Bibliography (and Suggested Reading)</A ></H1 ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="rfcs" >A.4.1. Request for Comments (RFCs)</A ></H2 ><P >Specification documents for the Internet protocol suite, including the <SPAN CLASS="acronym" >DNS</SPAN >, are published as part of the Request for Comments (RFCs) series of technical notes. The standards themselves are defined by the Internet Engineering Task Force (IETF) and the Internet Engineering Steering Group (IESG). RFCs can be obtained online via FTP at <A HREF="ftp://www.isi.edu/in-notes/" TARGET="_top" >ftp://www.isi.edu/in-notes/RFC<TT CLASS="replaceable" ><I >xxx</I ></TT >.txt</A > (where <TT CLASS="replaceable" ><I >xxx</I ></TT > is the number of the RFC). RFCs are also available via the Web at <A HREF="http://www.ietf.org/rfc/" TARGET="_top" >http://www.ietf.org/rfc/</A >. </P ><H3 ><A NAME="AEN4526" >Bibliography</A ></H3 ><H2 CLASS="bibliodiv" ><A NAME="AEN4527" >Standards</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4529" ></A ><P >[RFC974] <SPAN CLASS="AUTHOR" >C. Partridge</SPAN >, <I >Mail Routing and the Domain System</I >, January 1986.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4536" ></A ><P >[RFC1034] <SPAN CLASS="AUTHOR" >P.V. Mockapetris</SPAN >, <I >Domain Names — Concepts and Facilities</I >, November 1987.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4543" ></A ><P >[RFC1035] <SPAN CLASS="AUTHOR" >P. V. Mockapetris</SPAN >, <I >Domain Names — Implementation and Specification</I >, November 1987.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><H2 CLASS="bibliodiv" ><A NAME="proposed_standards" >Proposed Standards</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4552" ></A ><P >[RFC2181] <SPAN CLASS="AUTHOR" >R., R. Bush Elz</SPAN >, <I >Clarifications to the <SPAN CLASS="acronym" >DNS</SPAN > Specification</I >, July 1997.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4560" ></A ><P >[RFC2308] <SPAN CLASS="AUTHOR" >M. Andrews</SPAN >, <I >Negative Caching of <SPAN CLASS="acronym" >DNS</SPAN > Queries</I >, March 1998.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4568" ></A ><P >[RFC1995] <SPAN CLASS="AUTHOR" >M. Ohta</SPAN >, <I >Incremental Zone Transfer in <SPAN CLASS="acronym" >DNS</SPAN ></I >, August 1996.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4576" ></A ><P >[RFC1996] <SPAN CLASS="AUTHOR" >P. Vixie</SPAN >, <I >A Mechanism for Prompt Notification of Zone Changes</I >, August 1996.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4583" ></A ><P >[RFC2136] <SPAN CLASS="AUTHOR" >P. Vixie, </SPAN ><SPAN CLASS="AUTHOR" >S. Thomson, </SPAN ><SPAN CLASS="AUTHOR" >Y. Rekhter, </SPAN ><SPAN CLASS="AUTHOR" >and J. Bound</SPAN >, <I >Dynamic Updates in the Domain Name System</I >, April 1997.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4600" ></A ><P >[RFC2845] <SPAN CLASS="AUTHOR" >P. Vixie, </SPAN ><SPAN CLASS="AUTHOR" >O. Gudmundsson, </SPAN ><SPAN CLASS="AUTHOR" >D. Eastlake, 3rd, </SPAN ><SPAN CLASS="AUTHOR" >and B. Wellington</SPAN >, <I >Secret Key Transaction Authentication for <SPAN CLASS="acronym" >DNS</SPAN > (TSIG)</I >, May 2000.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><H2 CLASS="bibliodiv" ><A NAME="AEN4619" >Proposed Standards Still Under Development</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4624" ></A ><P >[RFC1886] <SPAN CLASS="AUTHOR" >S. Thomson </SPAN ><SPAN CLASS="AUTHOR" >and C. Huitema</SPAN >, <I ><SPAN CLASS="acronym" >DNS</SPAN > Extensions to support IP version 6</I >, December 1995.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4636" ></A ><P >[RFC2065] <SPAN CLASS="AUTHOR" >D. Eastlake, 3rd </SPAN ><SPAN CLASS="AUTHOR" >and C. Kaufman</SPAN >, <I >Domain Name System Security Extensions</I >, January 1997.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4648" ></A ><P >[RFC2137] <SPAN CLASS="AUTHOR" >D. Eastlake, 3rd</SPAN >, <I >Secure Domain Name System Dynamic Update</I >, April 1997.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><H2 CLASS="bibliodiv" ><A NAME="AEN4656" >Other Important RFCs About <SPAN CLASS="acronym" >DNS</SPAN > Implementation</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4659" ></A ><P >[RFC1535] <SPAN CLASS="AUTHOR" >E. Gavron</SPAN >, <I >A Security Problem and Proposed Correction With Widely Deployed <SPAN CLASS="acronym" >DNS</SPAN > Software.</I >, October 1993.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4667" ></A ><P >[RFC1536] <SPAN CLASS="AUTHOR" >A. Kumar, </SPAN ><SPAN CLASS="AUTHOR" >J. Postel, </SPAN ><SPAN CLASS="AUTHOR" >C. Neuman, </SPAN ><SPAN CLASS="AUTHOR" >P. Danzig, </SPAN ><SPAN CLASS="AUTHOR" >and S. Miller</SPAN >, <I >Common <SPAN CLASS="acronym" >DNS</SPAN > Implementation Errors and Suggested Fixes</I >, October 1993.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4688" ></A ><P >[RFC1982] <SPAN CLASS="AUTHOR" >R. Elz </SPAN ><SPAN CLASS="AUTHOR" >and R. Bush</SPAN >, <I >Serial Number Arithmetic</I >, August 1996.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><H2 CLASS="bibliodiv" ><A NAME="AEN4699" >Resource Record Types</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4701" ></A ><P >[RFC1183] <SPAN CLASS="AUTHOR" >C.F. Everhart, </SPAN ><SPAN CLASS="AUTHOR" >L. A. Mamakos, </SPAN ><SPAN CLASS="AUTHOR" >R. Ullmann, </SPAN ><SPAN CLASS="AUTHOR" >and P. Mockapetris</SPAN >, <I >New <SPAN CLASS="acronym" >DNS</SPAN > RR Definitions</I >, October 1990.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4719" ></A ><P >[RFC1706] <SPAN CLASS="AUTHOR" >B. Manning </SPAN ><SPAN CLASS="AUTHOR" >and R. Colella</SPAN >, <I ><SPAN CLASS="acronym" >DNS</SPAN > NSAP Resource Records</I >, October 1994.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4731" ></A ><P >[RFC2168] <SPAN CLASS="AUTHOR" >R. Daniel </SPAN ><SPAN CLASS="AUTHOR" >and M. Mealling</SPAN >, <I >Resolution of Uniform Resource Identifiers using the Domain Name System</I >, June 1997.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4742" ></A ><P >[RFC1876] <SPAN CLASS="AUTHOR" >C. Davis, </SPAN ><SPAN CLASS="AUTHOR" >P. Vixie, </SPAN ><SPAN CLASS="AUTHOR" >T., </SPAN ><SPAN CLASS="AUTHOR" >and I. Dickinson</SPAN >, <I >A Means for Expressing Location Information in the Domain Name System</I >, January 1996.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4759" ></A ><P >[RFC2052] <SPAN CLASS="AUTHOR" >A. Gulbrandsen </SPAN ><SPAN CLASS="AUTHOR" >and P. Vixie</SPAN >, <I >A <SPAN CLASS="acronym" >DNS</SPAN > RR for Specifying the Location of Services.</I >, October 1996.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4771" ></A ><P >[RFC2163] <SPAN CLASS="AUTHOR" >A. Allocchio</SPAN >, <I >Using the Internet <SPAN CLASS="acronym" >DNS</SPAN > to Distribute MIXER Conformant Global Address Mapping</I >, January 1998.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4779" ></A ><P >[RFC2230] <SPAN CLASS="AUTHOR" >R. Atkinson</SPAN >, <I >Key Exchange Delegation Record for the <SPAN CLASS="acronym" >DNS</SPAN ></I >, October 1997.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><H2 CLASS="bibliodiv" ><A NAME="AEN4787" ><SPAN CLASS="acronym" >DNS</SPAN > and the Internet</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4790" ></A ><P >[RFC1101] <SPAN CLASS="AUTHOR" >P. V. Mockapetris</SPAN >, <I ><SPAN CLASS="acronym" >DNS</SPAN > Encoding of Network Names and Other Types</I >, April 1989.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4798" ></A ><P >[RFC1123] <SPAN CLASS="AUTHOR" >Braden</SPAN >, <I >Requirements for Internet Hosts - Application and Support</I >, October 1989.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4805" ></A ><P >[RFC1591] <SPAN CLASS="AUTHOR" >J. Postel</SPAN >, <I >Domain Name System Structure and Delegation</I >, March 1994.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4812" ></A ><P >[RFC2317] <SPAN CLASS="AUTHOR" >H. Eidnes, </SPAN ><SPAN CLASS="AUTHOR" >G. de Groot, </SPAN ><SPAN CLASS="AUTHOR" >and P. Vixie</SPAN >, <I >Classless IN-ADDR.ARPA Delegation</I >, March 1998.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><H2 CLASS="bibliodiv" ><A NAME="AEN4826" ><SPAN CLASS="acronym" >DNS</SPAN > Operations</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4829" ></A ><P >[RFC1537] <SPAN CLASS="AUTHOR" >P. Beertema</SPAN >, <I >Common <SPAN CLASS="acronym" >DNS</SPAN > Data File Configuration Errors</I >, October 1993.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4837" ></A ><P >[RFC1912] <SPAN CLASS="AUTHOR" >D. Barr</SPAN >, <I >Common <SPAN CLASS="acronym" >DNS</SPAN > Operational and Configuration Errors</I >, February 1996.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4845" ></A ><P >[RFC1912] <SPAN CLASS="AUTHOR" >D. Barr</SPAN >, <I >Common <SPAN CLASS="acronym" >DNS</SPAN > Operational and Configuration Errors</I >, February 1996.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4853" ></A ><P >[RFC2010] <SPAN CLASS="AUTHOR" >B. Manning </SPAN ><SPAN CLASS="AUTHOR" >and P. Vixie</SPAN >, <I >Operational Criteria for Root Name Servers.</I >, October 1996.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4864" ></A ><P >[RFC2219] <SPAN CLASS="AUTHOR" >M. Hamilton </SPAN ><SPAN CLASS="AUTHOR" >and R. Wright</SPAN >, <I >Use of <SPAN CLASS="acronym" >DNS</SPAN > Aliases for Network Services.</I >, October 1997.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><H2 CLASS="bibliodiv" ><A NAME="AEN4876" >Other <SPAN CLASS="acronym" >DNS</SPAN >-related RFCs</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4882" ></A ><P >[RFC1464] <SPAN CLASS="AUTHOR" >R. Rosenbaum</SPAN >, <I >Using the Domain Name System To Store Arbitrary String Attributes</I >, May 1993.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4889" ></A ><P >[RFC1713] <SPAN CLASS="AUTHOR" >A. Romao</SPAN >, <I >Tools for <SPAN CLASS="acronym" >DNS</SPAN > Debugging</I >, November 1994.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4897" ></A ><P >[RFC1794] <SPAN CLASS="AUTHOR" >T. Brisco</SPAN >, <I ><SPAN CLASS="acronym" >DNS</SPAN > Support for Load Balancing</I >, April 1995.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4905" ></A ><P >[RFC2240] <SPAN CLASS="AUTHOR" >O. Vaughan</SPAN >, <I >A Legal Basis for Domain Name Allocation</I >, November 1997.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4912" ></A ><P >[RFC2345] <SPAN CLASS="AUTHOR" >J. Klensin, </SPAN ><SPAN CLASS="AUTHOR" >T. Wolf, </SPAN ><SPAN CLASS="AUTHOR" >and G. Oglesby</SPAN >, <I >Domain Names and Company Name Retrieval</I >, May 1998.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><DIV CLASS="biblioentry" ><A NAME="AEN4926" ></A ><P >[RFC2352] <SPAN CLASS="AUTHOR" >O. Vaughan</SPAN >, <I >A Convention For Using Legal Names as Domain Names</I >, May 1998.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ><H2 CLASS="bibliodiv" ><A NAME="AEN4933" >Obsolete and Unimplemented Experimental RRs</A ></H2 ><DIV CLASS="biblioentry" ><A NAME="AEN4935" ></A ><P >[RFC1712] <SPAN CLASS="AUTHOR" >C. Farrell, </SPAN ><SPAN CLASS="AUTHOR" >M. Schulze, </SPAN ><SPAN CLASS="AUTHOR" >S. Pleitner, </SPAN ><SPAN CLASS="AUTHOR" >and D. Baldoni</SPAN >, <I ><SPAN CLASS="acronym" >DNS</SPAN > Encoding of Geographical Location</I >, November 1994.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="internet_drafts" >A.4.2. Internet Drafts</A ></H2 ><P >Internet Drafts (IDs) are rough-draft working documents of the Internet Engineering Task Force. They are, in essence, RFCs in the preliminary stages of development. Implementors are cautioned not to regard IDs as archival, and they should not be quoted or cited in any formal documents unless accompanied by the disclaimer that they are "works in progress." IDs have a lifespan of six months after which they are deleted unless updated by their authors. </P ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A NAME="AEN4956" >A.4.3. Other Documents About <SPAN CLASS="acronym" >BIND</SPAN ></A ></H2 ><P ></P ><H3 ><A NAME="AEN4960" >Bibliography</A ></H3 ><DIV CLASS="biblioentry" ><A NAME="AEN4961" ></A ><P ><SPAN CLASS="AUTHOR" >Paul Albitz </SPAN ><SPAN CLASS="AUTHOR" >and Cricket Liu</SPAN >, <I ><SPAN CLASS="acronym" >DNS</SPAN > and <SPAN CLASS="acronym" >BIND</SPAN ></I >, 1998.</P ><DIV CLASS="BIBLIOENTRYBLOCK" STYLE="margin-left=0.5in" ></DIV ></DIV ></DIV ></DIV ></DIV ><DIV CLASS="NAVFOOTER" ><HR ALIGN="LEFT" WIDTH="100%"><TABLE SUMMARY="Footer navigation table" WIDTH="100%" BORDER="0" CELLPADDING="0" CELLSPACING="0" ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" ><A HREF="Bv9ARM.ch08.html" ACCESSKEY="P" >Prev</A ></TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" ><A HREF="Bv9ARM.html" ACCESSKEY="H" >Home</A ></TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" > </TD ></TR ><TR ><TD WIDTH="33%" ALIGN="left" VALIGN="top" >Troubleshooting</TD ><TD WIDTH="34%" ALIGN="center" VALIGN="top" > </TD ><TD WIDTH="33%" ALIGN="right" VALIGN="top" > </TD ></TR ></TABLE ></DIV ></BODY ></HTML >