doc/arm/Bv9ARM.ch09.html

	Bv9ARM.ch09.html revision 3ba6d0298ae3414ab12f1a6ae35e14b119f4311e
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes<HTML
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><HEAD
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><TITLE
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>Appendices</TITLE
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><META
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesNAME="GENERATOR"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCONTENT="Modular DocBook HTML Stylesheet Version 1.61
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes"><LINK
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesREL="HOME"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesTITLE="BIND 9 Administrator Reference Manual"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesHREF="Bv9ARM.html"><LINK
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesREL="PREVIOUS"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesTITLE="Troubleshooting"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesHREF="Bv9ARM.ch08.html"></HEAD
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><BODY
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="appendix"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesBGCOLOR="#FFFFFF"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesTEXT="#000000"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesLINK="#0000FF"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesVLINK="#840084"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesALINK="#0000FF"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DIV
70953fb44a7140fe206c3a5f011e24209c8c5c6abnicholesCLASS="NAVHEADER"
70953fb44a7140fe206c3a5f011e24209c8c5c6abnicholes><TABLE
70953fb44a7140fe206c3a5f011e24209c8c5c6abnicholesWIDTH="100%"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesBORDER="0"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCELLPADDING="0"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCELLSPACING="0"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><TR
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><TH
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCOLSPAN="3"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesALIGN="center"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND 9 Administrator Reference Manual</TH
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></TR
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><TR
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><TD
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesWIDTH="10%"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesALIGN="left"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesVALIGN="bottom"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesHREF="Bv9ARM.ch08.html"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>Prev</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></TD
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><TD
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesWIDTH="80%"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesALIGN="center"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesVALIGN="bottom"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></TD
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><TD
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesWIDTH="10%"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesALIGN="right"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesVALIGN="bottom"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>&nbsp;</TD
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></TR
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></TABLE
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><HR
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesALIGN="LEFT"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesWIDTH="100%"></DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="appendix"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><H1
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesNAME="ch09"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>Appendix A. Appendices</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></H1
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="TOC"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DL
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><B
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>Table of Contents</B
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.1. <A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesHREF="Bv9ARM.ch09.html#AEN4036"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>Acknowledgements</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.2. <A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesHREF="Bv9ARM.ch09.html#historical_dns_information"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>Historical <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>DNS</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> Information</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.3. <A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesHREF="Bv9ARM.ch09.html#AEN4077"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>General <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>DNS</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> Reference Information</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.4. <A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesHREF="Bv9ARM.ch09.html#bibliography"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>Bibliography (and Suggested Reading)</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DT
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DL
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect1"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><H1
0a39e7683f6611d66c55712f50bb240428d832a1bnicholesCLASS="sect1"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesNAME="AEN4036"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.1. Acknowledgements</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></H1
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect2"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><H2
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect2"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesNAME="AEN4038"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.1.1. A Brief History of the <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>DNS</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> and <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></H2
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>Although the "official" beginning of the Domain Name
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      System occurred in 1984 with the publication of RFC 920, the
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      core of the new system was described in 1983 in RFCs 882 and
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      883. From 1984 to 1987, the ARPAnet (the precursor to today's
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      Internet) became a testbed of experimentation for developing the
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      new naming/addressing scheme in an rapidly expanding,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      operational network environment.  New RFCs were written and
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      published in 1987 that modified the original documents to
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      incorporate improvements based on the working model. RFC 1034,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      "Domain Names-Concepts and Facilities," and RFC 1035, "Domain
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      Names-Implementation and Specification" were published and
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      became the standards upon which all <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>DNS</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> implementations are
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes      built.
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes</P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>The first working domain name server, called "Jeeves," was
cb2846ded4de1abbb5934b92132baf826f1babfebnicholeswritten in 1983-84 by Paul Mockapetris for operation on DEC Tops-20
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesmachines located at the University of Southern California's Information
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesSciences Institute (USC-ISI) and SRI International's Network Information
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCenter (SRI-NIC). A <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>DNS</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> server for Unix machines, the Berkeley Internet
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesName Domain (<SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>) package, was written soon after by a group of
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesgraduate students at the University of California at Berkeley under
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesa grant from the US Defense Advanced Research Projects Administration
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes(DARPA). Versions of <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> through 4.8.3 were maintained by the Computer
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesSystems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesPainter, David Riggle and Songnian Zhou made up the initial <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesproject team. After that, additional work on the software package
cb2846ded4de1abbb5934b92132baf826f1babfebnicholeswas done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesemployee on loan to the CSRG, worked on <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
bf1e7c075ccc3e6597d17de7641332ff6ff92e8astriker>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> for 2 years, from 1985
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesto 1987. Many other people also contributed to <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> development
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesduring that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell,
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesMike Muuss, Jim Bloom and Mike Schwartz. <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> maintenance was subsequently
cb2846ded4de1abbb5934b92132baf826f1babfebnicholeshandled by Mike Karels and O. Kure.</P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> versions 4.9 and 4.9.1 were released by Digital Equipment
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCorporation (now Compaq Computer Corporation). Paul Vixie, then
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesa DEC employee, became <SPAN
9046ab142ed19505e034af0afb8c15be512b8526bnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>'s primary caretaker. Paul was assisted
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesby Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesPartan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesBaran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesWolfhugel, and others.</P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> Version 4.9.2 was sponsored by Vixie Enterprises. Paul
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesVixie became <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>'s principal architect/programmer.</P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> versions from 4.9.3 onward have been developed and maintained
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesby the Internet Software Consortium with support being provided
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesby ISC's sponsors. As co-architects/programmers, Bob Halley and
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesPaul Vixie released the first production-ready version of <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
e75db68cd3a838dfe6de1553907416c3834ebb40bnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> version
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes8 in May 1997.</P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>BIND</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> development work is made possible today by the sponsorship
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesof several corporations, and by the tireless work efforts of numerous
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesindividuals.</P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect1"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><H1
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect1"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesNAME="historical_dns_information"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.2. Historical <SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="acronym"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>DNS</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes> Information</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></H1
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect2"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><H2
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect2"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesNAME="classes_of_resource_records"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.2.1. Classes of Resource Records</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></H2
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><DIV
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect3"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><H3
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="sect3"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesNAME="AEN4068"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>A.2.1.1. HS = hesiod</A
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes></H3
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes><P
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>The [<SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholesCLASS="optional"
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>hesiod</SPAN
cb2846ded4de1abbb5934b92132baf826f1babfebnicholes>] 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="AEN4073"
>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="AEN4077"
>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: <I
CLASS="emphasis"
>Unicast</I
>,
an identifier for a single interface; <I
CLASS="emphasis"
>Anycast</I
>,
an identifier for a set of interfaces; and <I
CLASS="emphasis"
>Multicast</I
>,
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="AEN4088"
></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
>&#60;------ Public Topology
------&#62;</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
>&#60;-Site Topology-&#62;</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
>&#60;------ Interface Identifier ------&#62;</P
></TD
></TR
></TBODY
></TABLE
><P
></P
></DIV
><P
>Where
<DIV
CLASS="informaltable"
><A
NAME="AEN4157"
></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 <I
CLASS="emphasis"
>Public Topology</I
> is provided by the
upstream provider or ISP, and (roughly) corresponds to the IPv4 <I
CLASS="emphasis"
>network</I
> section
of the address range. The <I
CLASS="emphasis"
>Site Topology</I
> is
where you can subnet this space, much the same as subnetting an
IPv4 /16 network into /24 subnets. The <I
CLASS="emphasis"
>Interface Identifier</I
> 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="AEN4212"
></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="AEN4256"
>Bibliography</A
></H3
><H1
CLASS="bibliodiv"
><A
NAME="AEN4257"
>Standards</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4259"
></A
><P
>[RFC974]&nbsp;<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="AEN4266"
></A
><P
>[RFC1034]&nbsp;<SPAN
CLASS="AUTHOR"
>P.V. Mockapetris</SPAN
>, <I
>Domain Names &#8212; Concepts and Facilities</I
>, November 1987.</P
><DIV
CLASS="BIBLIOENTRYBLOCK"
STYLE="margin-left=0.5in"
></DIV
></DIV
><DIV
CLASS="biblioentry"
><A
NAME="AEN4273"
></A
><P
>[RFC1035]&nbsp;<SPAN
CLASS="AUTHOR"
>P. V. Mockapetris</SPAN
>, <I
>Domain Names &#8212; Implementation and
Specification</I
>, November 1987.</P
><DIV
CLASS="BIBLIOENTRYBLOCK"
STYLE="margin-left=0.5in"
></DIV
></DIV
><H1
CLASS="bibliodiv"
><A
NAME="proposed_standards"
>Proposed Standards</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4282"
></A
><P
>[RFC2181]&nbsp;<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="AEN4290"
></A
><P
>[RFC2308]&nbsp;<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="AEN4298"
></A
><P
>[RFC1995]&nbsp;<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="AEN4306"
></A
><P
>[RFC1996]&nbsp;<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="AEN4313"
></A
><P
>[RFC2136]&nbsp;<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="AEN4330"
></A
><P
>[RFC2845]&nbsp;<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
><H1
CLASS="bibliodiv"
><A
NAME="AEN4349"
>Proposed Standards Still Under Development</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4354"
></A
><P
>[RFC1886]&nbsp;<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="AEN4366"
></A
><P
>[RFC2065]&nbsp;<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="AEN4378"
></A
><P
>[RFC2137]&nbsp;<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
><H1
CLASS="bibliodiv"
><A
NAME="AEN4386"
>Other Important RFCs About <SPAN
CLASS="acronym"
>DNS</SPAN
> Implementation</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4389"
></A
><P
>[RFC1535]&nbsp;<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="AEN4397"
></A
><P
>[RFC1536]&nbsp;<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="AEN4418"
></A
><P
>[RFC1982]&nbsp;<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
><H1
CLASS="bibliodiv"
><A
NAME="AEN4429"
>Resource Record Types</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4431"
></A
><P
>[RFC1183]&nbsp;<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="AEN4449"
></A
><P
>[RFC1706]&nbsp;<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="AEN4461"
></A
><P
>[RFC2168]&nbsp;<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="AEN4472"
></A
><P
>[RFC1876]&nbsp;<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="AEN4489"
></A
><P
>[RFC2052]&nbsp;<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="AEN4501"
></A
><P
>[RFC2163]&nbsp;<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="AEN4509"
></A
><P
>[RFC2230]&nbsp;<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
><H1
CLASS="bibliodiv"
><A
NAME="AEN4517"
><SPAN
CLASS="acronym"
>DNS</SPAN
> and the Internet</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4520"
></A
><P
>[RFC1101]&nbsp;<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="AEN4528"
></A
><P
>[RFC1123]&nbsp;<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="AEN4535"
></A
><P
>[RFC1591]&nbsp;<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="AEN4542"
></A
><P
>[RFC2317]&nbsp;<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
><H1
CLASS="bibliodiv"
><A
NAME="AEN4556"
><SPAN
CLASS="acronym"
>DNS</SPAN
> Operations</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4559"
></A
><P
>[RFC1537]&nbsp;<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="AEN4567"
></A
><P
>[RFC1912]&nbsp;<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="AEN4575"
></A
><P
>[RFC1912]&nbsp;<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="AEN4583"
></A
><P
>[RFC2010]&nbsp;<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="AEN4594"
></A
><P
>[RFC2219]&nbsp;<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
><H1
CLASS="bibliodiv"
><A
NAME="AEN4606"
>Other <SPAN
CLASS="acronym"
>DNS</SPAN
>-related RFCs</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4612"
></A
><P
>[RFC1464]&nbsp;<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="AEN4619"
></A
><P
>[RFC1713]&nbsp;<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="AEN4627"
></A
><P
>[RFC1794]&nbsp;<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="AEN4635"
></A
><P
>[RFC2240]&nbsp;<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="AEN4642"
></A
><P
>[RFC2345]&nbsp;<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="AEN4656"
></A
><P
>[RFC2352]&nbsp;<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
><H1
CLASS="bibliodiv"
><A
NAME="AEN4663"
>Obsolete and Unimplemented Experimental RRs</A
></H1
><DIV
CLASS="biblioentry"
><A
NAME="AEN4665"
></A
><P
>[RFC1712]&nbsp;<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="AEN4686"
>A.4.3. Other Documents About <SPAN
CLASS="acronym"
>BIND</SPAN
></A
></H2
><P
></P
><H3
><A
NAME="AEN4690"
>Bibliography</A
></H3
><DIV
CLASS="biblioentry"
><A
NAME="AEN4691"
></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
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="Bv9ARM.ch08.html"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="Bv9ARM.html"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Troubleshooting</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
>&nbsp;</TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>&nbsp;</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>