1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
8 CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK
10 TITLE="BIND 9 Administrator Reference Manual"
11 HREF="Bv9ARM.html"><LINK
13 TITLE="Troubleshooting"
14 HREF="Bv9ARM.ch08.html"></HEAD
25 SUMMARY="Header navigation table"
34 >BIND 9 Administrator Reference Manual</TH
42 HREF="Bv9ARM.ch08.html"
67 >Appendix A. Appendices</H1
77 HREF="Bv9ARM.ch09.html#AEN4781"
82 HREF="Bv9ARM.ch09.html#historical_dns_information"
86 > Reference Information</A
90 HREF="Bv9ARM.ch09.html#bibliography"
91 >Bibliography (and Suggested Reading)</A
101 >A.1. Acknowledgments</A
109 >A.1.1. A Brief History of the <ACRONYM
118 >Although the "official" beginning of the Domain Name
119 System occurred in 1984 with the publication of RFC 920, the
120 core of the new system was described in 1983 in RFCs 882 and
121 883. From 1984 to 1987, the ARPAnet (the precursor to today's
122 Internet) became a testbed of experimentation for developing the
123 new naming/addressing scheme in an rapidly expanding,
124 operational network environment. New RFCs were written and
125 published in 1987 that modified the original documents to
126 incorporate improvements based on the working model. RFC 1034,
127 "Domain Names-Concepts and Facilities", and RFC 1035, "Domain
128 Names-Implementation and Specification" were published and
129 became the standards upon which all <ACRONYM
132 > implementations are
136 >The first working domain name server, called "Jeeves", was
137 written in 1983-84 by Paul Mockapetris for operation on DEC Tops-20
138 machines located at the University of Southern California's Information
139 Sciences Institute (USC-ISI) and SRI International's Network Information
140 Center (SRI-NIC). A <ACRONYM
143 > server for Unix machines, the Berkeley Internet
144 Name Domain (<ACRONYM
147 >) package, was written soon after by a group of
148 graduate students at the University of California at Berkeley under
149 a grant from the US Defense Advanced Research Projects Administration
150 (DARPA). Versions of <ACRONYM
153 > through 4.8.3 were maintained by the Computer
154 Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
155 Painter, David Riggle and Songnian Zhou made up the initial <ACRONYM
159 project team. After that, additional work on the software package
160 was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment Corporation
161 employee on loan to the CSRG, worked on <ACRONYM
164 > for 2 years, from 1985
165 to 1987. Many other people also contributed to <ACRONYM
169 during that time: Doug Kingston, Craig Partridge, Smoot Carl-Mitchell,
170 Mike Muuss, Jim Bloom and Mike Schwartz. <ACRONYM
173 > maintenance was subsequently
174 handled by Mike Karels and O. Kure.</P
179 > versions 4.9 and 4.9.1 were released by Digital Equipment
180 Corporation (now Compaq Computer Corporation). Paul Vixie, then
181 a DEC employee, became <ACRONYM
184 >'s primary caretaker. Paul was assisted
185 by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan Beecher, Andrew
186 Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat
187 Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
188 Wolfhugel, and others.</P
193 > Version 4.9.2 was sponsored by Vixie Enterprises. Paul
194 Vixie became <ACRONYM
197 >'s principal architect/programmer.</P
202 > versions from 4.9.3 onward have been developed and maintained
203 by the Internet Software Consortium with support being provided
204 by ISC's sponsors. As co-architects/programmers, Bob Halley and
205 Paul Vixie released the first production-ready version of <ACRONYM
214 > development work is made possible today by the sponsorship
215 of several corporations, and by the tireless work efforts of numerous
224 NAME="historical_dns_information"
225 >A.2. General <ACRONYM
228 > Reference Information</A
236 >A.2.1. IPv6 addresses (AAAA)</A
239 >IPv6 addresses are 128-bit identifiers for interfaces and
240 sets of interfaces which were introduced in the <ACRONYM
244 scalable Internet routing. There are three types of addresses: <SPAN
251 an identifier for a single interface; <SPAN
258 an identifier for a set of interfaces; and <SPAN
265 an identifier for a set of interfaces. Here we describe the global
266 Unicast address scheme. For more information, see RFC 2374.</P
268 >The aggregatable global Unicast address format is as follows:</P
270 CLASS="informaltable"
337 ><------ Public Topology
368 ><-Site Topology-></P
398 ><------ Interface Identifier ------></P
409 CLASS="informaltable"
431 >Format Prefix (001)</P
445 >Top-Level Aggregation Identifier</P
459 >Reserved for future use</P
473 >Next-Level Aggregation Identifier</P
487 >Site-Level Aggregation Identifier</P
501 >Interface Identifier</P
518 upstream provider or ISP, and (roughly) corresponds to the IPv4 <SPAN
525 of the address range. The <SPAN
532 where you can subnet this space, much the same as subnetting an
533 IPv4 /16 network into /24 subnets. The <SPAN
537 >Interface Identifier</I
540 the address of an individual interface on a given network. (With
541 IPv6, addresses belong to interfaces rather than machines.)</P
543 >The subnetting capability of IPv6 is much more flexible than
544 that of IPv4: subnetting can now be carried out on bit boundaries,
545 in much the same way as Classless InterDomain Routing (CIDR).</P
547 >The Interface Identifier must be unique on that network. On
548 ethernet networks, one way to ensure this is to set the address
549 to the first three bytes of the hardware address, "FFFE", then the
550 last three bytes of the hardware address. The lowest significant
551 bit of the first byte should then be complemented. Addresses are
552 written as 32-bit blocks separated with a colon, and leading zeros
553 of a block may be omitted, for example:</P
557 >2001:db8:201:9:a00:20ff:fe81:2b32</B
560 >IPv6 address specifications are likely to contain long strings
561 of zeros, so the architects have included a shorthand for specifying
562 them. The double colon (`::') indicates the longest possible string
563 of zeros that can fit, and can be used only once in an address.</P
572 >A.3. Bibliography (and Suggested Reading)</A
580 >A.3.1. Request for Comments (RFCs)</A
583 >Specification documents for the Internet protocol suite, including
587 >, are published as part of the Request for Comments (RFCs)
588 series of technical notes. The standards themselves are defined
589 by the Internet Engineering Task Force (IETF) and the Internet Engineering
590 Steering Group (IESG). RFCs can be obtained online via FTP at
592 HREF="ftp://www.isi.edu/in-notes/"
594 >ftp://www.isi.edu/in-notes/RFC<VAR
602 the number of the RFC). RFCs are also available via the Web at
604 HREF="http://www.ietf.org/rfc/"
606 >http://www.ietf.org/rfc/</A
630 >Mail Routing and the Domain System</I
633 CLASS="BIBLIOENTRYBLOCK"
634 STYLE="margin-left: 0.5in"
643 >[RFC1034] <SPAN
645 >P.V. Mockapetris</SPAN
647 >Domain Names — Concepts and Facilities</I
650 CLASS="BIBLIOENTRYBLOCK"
651 STYLE="margin-left: 0.5in"
660 >[RFC1035] <SPAN
662 >P. V. Mockapetris</SPAN
664 >Domain Names — Implementation and
668 CLASS="BIBLIOENTRYBLOCK"
669 STYLE="margin-left: 0.5in"
675 NAME="proposed_standards"
676 >Proposed Standards</A
684 >[RFC2181] <SPAN
686 >R., R. Bush Elz</SPAN
688 >Clarifications to the <ACRONYM
694 CLASS="BIBLIOENTRYBLOCK"
695 STYLE="margin-left: 0.5in"
704 >[RFC2308] <SPAN
708 >Negative Caching of <ACRONYM
714 CLASS="BIBLIOENTRYBLOCK"
715 STYLE="margin-left: 0.5in"
724 >[RFC1995] <SPAN
728 >Incremental Zone Transfer in <ACRONYM
734 CLASS="BIBLIOENTRYBLOCK"
735 STYLE="margin-left: 0.5in"
744 >[RFC1996] <SPAN
748 >A Mechanism for Prompt Notification of Zone Changes</I
751 CLASS="BIBLIOENTRYBLOCK"
752 STYLE="margin-left: 0.5in"
761 >[RFC2136] <SPAN
774 >Dynamic Updates in the Domain Name System</I
777 CLASS="BIBLIOENTRYBLOCK"
778 STYLE="margin-left: 0.5in"
787 >[RFC2845] <SPAN
792 >O. Gudmundsson, </SPAN
795 >D. Eastlake, 3rd, </SPAN
798 >and B. Wellington</SPAN
800 >Secret Key Transaction Authentication for <ACRONYM
806 CLASS="BIBLIOENTRYBLOCK"
807 STYLE="margin-left: 0.5in"
814 >Proposed Standards Still Under Development</A
822 >[RFC1886] <SPAN
827 >and C. Huitema</SPAN
832 > Extensions to support IP version 6</I
835 CLASS="BIBLIOENTRYBLOCK"
836 STYLE="margin-left: 0.5in"
845 >[RFC2065] <SPAN
847 >D. Eastlake, 3rd </SPAN
850 >and C. Kaufman</SPAN
852 >Domain Name System Security Extensions</I
855 CLASS="BIBLIOENTRYBLOCK"
856 STYLE="margin-left: 0.5in"
865 >[RFC2137] <SPAN
867 >D. Eastlake, 3rd</SPAN
869 >Secure Domain Name System Dynamic Update</I
872 CLASS="BIBLIOENTRYBLOCK"
873 STYLE="margin-left: 0.5in"
880 >Other Important RFCs About <ACRONYM
891 >[RFC1535] <SPAN
895 >A Security Problem and Proposed Correction With Widely Deployed <ACRONYM
901 CLASS="BIBLIOENTRYBLOCK"
902 STYLE="margin-left: 0.5in"
911 >[RFC1536] <SPAN
930 > Implementation Errors and Suggested Fixes</I
933 CLASS="BIBLIOENTRYBLOCK"
934 STYLE="margin-left: 0.5in"
943 >[RFC1982] <SPAN
950 >Serial Number Arithmetic</I
953 CLASS="BIBLIOENTRYBLOCK"
954 STYLE="margin-left: 0.5in"
961 >Resource Record Types</A
969 >[RFC1183] <SPAN
971 >C.F. Everhart, </SPAN
974 >L. A. Mamakos, </SPAN
980 >and P. Mockapetris</SPAN
988 CLASS="BIBLIOENTRYBLOCK"
989 STYLE="margin-left: 0.5in"
998 >[RFC1706] <SPAN
1003 >and R. Colella</SPAN
1008 > NSAP Resource Records</I
1011 CLASS="BIBLIOENTRYBLOCK"
1012 STYLE="margin-left: 0.5in"
1021 >[RFC2168] <SPAN
1026 >and M. Mealling</SPAN
1028 >Resolution of Uniform Resource Identifiers using
1029 the Domain Name System</I
1032 CLASS="BIBLIOENTRYBLOCK"
1033 STYLE="margin-left: 0.5in"
1042 >[RFC1876] <SPAN
1053 >and I. Dickinson</SPAN
1055 >A Means for Expressing Location Information in the Domain
1059 CLASS="BIBLIOENTRYBLOCK"
1060 STYLE="margin-left: 0.5in"
1069 >[RFC2052] <SPAN
1071 >A. Gulbrandsen </SPAN
1079 > RR for Specifying the Location of
1083 CLASS="BIBLIOENTRYBLOCK"
1084 STYLE="margin-left: 0.5in"
1093 >[RFC2163] <SPAN
1097 >Using the Internet <ACRONYM
1100 > to Distribute MIXER
1101 Conformant Global Address Mapping</I
1104 CLASS="BIBLIOENTRYBLOCK"
1105 STYLE="margin-left: 0.5in"
1114 >[RFC2230] <SPAN
1118 >Key Exchange Delegation Record for the <ACRONYM
1124 CLASS="BIBLIOENTRYBLOCK"
1125 STYLE="margin-left: 0.5in"
1135 > and the Internet</A
1143 >[RFC1101] <SPAN
1145 >P. V. Mockapetris</SPAN
1150 > Encoding of Network Names and Other Types</I
1153 CLASS="BIBLIOENTRYBLOCK"
1154 STYLE="margin-left: 0.5in"
1163 >[RFC1123] <SPAN
1167 >Requirements for Internet Hosts - Application and Support</I
1170 CLASS="BIBLIOENTRYBLOCK"
1171 STYLE="margin-left: 0.5in"
1180 >[RFC1591] <SPAN
1184 >Domain Name System Structure and Delegation</I
1187 CLASS="BIBLIOENTRYBLOCK"
1188 STYLE="margin-left: 0.5in"
1197 >[RFC2317] <SPAN
1202 >G. de Groot, </SPAN
1207 >Classless IN-ADDR.ARPA Delegation</I
1210 CLASS="BIBLIOENTRYBLOCK"
1211 STYLE="margin-left: 0.5in"
1229 >[RFC1537] <SPAN
1236 > Data File Configuration Errors</I
1239 CLASS="BIBLIOENTRYBLOCK"
1240 STYLE="margin-left: 0.5in"
1249 >[RFC1912] <SPAN
1256 > Operational and Configuration Errors</I
1257 >, February 1996.</P
1259 CLASS="BIBLIOENTRYBLOCK"
1260 STYLE="margin-left: 0.5in"
1269 >[RFC2010] <SPAN
1276 >Operational Criteria for Root Name Servers.</I
1279 CLASS="BIBLIOENTRYBLOCK"
1280 STYLE="margin-left: 0.5in"
1289 >[RFC2219] <SPAN
1294 >and R. Wright</SPAN
1299 > Aliases for Network Services.</I
1302 CLASS="BIBLIOENTRYBLOCK"
1303 STYLE="margin-left: 0.5in"
1321 >[RFC1464] <SPAN
1325 >Using the Domain Name System To Store Arbitrary String Attributes</I
1328 CLASS="BIBLIOENTRYBLOCK"
1329 STYLE="margin-left: 0.5in"
1338 >[RFC1713] <SPAN
1346 >, November 1994.</P
1348 CLASS="BIBLIOENTRYBLOCK"
1349 STYLE="margin-left: 0.5in"
1358 >[RFC1794] <SPAN
1365 > Support for Load Balancing</I
1368 CLASS="BIBLIOENTRYBLOCK"
1369 STYLE="margin-left: 0.5in"
1378 >[RFC2240] <SPAN
1382 >A Legal Basis for Domain Name Allocation</I
1383 >, November 1997.</P
1385 CLASS="BIBLIOENTRYBLOCK"
1386 STYLE="margin-left: 0.5in"
1395 >[RFC2345] <SPAN
1403 >and G. Oglesby</SPAN
1405 >Domain Names and Company Name Retrieval</I
1408 CLASS="BIBLIOENTRYBLOCK"
1409 STYLE="margin-left: 0.5in"
1418 >[RFC2352] <SPAN
1422 >A Convention For Using Legal Names as Domain Names</I
1425 CLASS="BIBLIOENTRYBLOCK"
1426 STYLE="margin-left: 0.5in"
1433 >Obsolete and Unimplemented Experimental RRs</A
1441 >[RFC1712] <SPAN
1449 >S. Pleitner, </SPAN
1452 >and D. Baldoni</SPAN
1457 > Encoding of Geographical
1459 >, November 1994.</P
1461 CLASS="BIBLIOENTRYBLOCK"
1462 STYLE="margin-left: 0.5in"
1471 NAME="internet_drafts"
1472 >A.3.2. Internet Drafts</A
1475 >Internet Drafts (IDs) are rough-draft working documents of
1476 the Internet Engineering Task Force. They are, in essence, RFCs
1477 in the preliminary stages of development. Implementors are cautioned not
1478 to regard IDs as archival, and they should not be quoted or cited
1479 in any formal documents unless accompanied by the disclaimer that
1480 they are "works in progress." IDs have a lifespan of six months
1481 after which they are deleted unless updated by their authors.
1490 >A.3.3. Other Documents About <ACRONYM
1513 >and Cricket Liu</SPAN
1524 CLASS="BIBLIOENTRYBLOCK"
1525 STYLE="margin-left: 0.5in"
1536 SUMMARY="Footer navigation table"
1547 HREF="Bv9ARM.ch08.html"
1571 >Troubleshooting</TD