Bv9ARM.ch09.html revision 3cddb2c552ee6582e8db0849c28747f6b6ca57fe
0N/A<!--
0N/A - Copyright (C) 2004-2009 Internet Systems Consortium, Inc. ("ISC")
0N/A - Copyright (C) 2000-2003 Internet Software Consortium.
0N/A -
0N/A - Permission to use, copy, modify, and/or distribute this software for any
0N/A - purpose with or without fee is hereby granted, provided that the above
0N/A - copyright notice and this permission notice appear in all copies.
0N/A -
0N/A - THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
0N/A - REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
0N/A - AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
0N/A - INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
0N/A - LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
0N/A - OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
0N/A - PERFORMANCE OF THIS SOFTWARE.
0N/A-->
0N/A<!-- $Id: Bv9ARM.ch09.html,v 1.203 2009/07/15 01:13:11 tbox Exp $ -->
0N/A<html>
0N/A<head>
0N/A<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
0N/A<title>Appendix�A.�Appendices</title>
0N/A<meta name="generator" content="DocBook XSL Stylesheets V1.71.1">
0N/A<link rel="start" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
0N/A<link rel="up" href="Bv9ARM.html" title="BIND 9 Administrator Reference Manual">
867N/A<link rel="prev" href="Bv9ARM.ch08.html" title="Chapter�8.�Troubleshooting">
0N/A<link rel="next" href="Bv9ARM.ch10.html" title="Manual pages">
0N/A</head>
0N/A<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
0N/A<div class="navheader">
0N/A<table width="100%" summary="Navigation header">
0N/A<tr><th colspan="3" align="center">Appendix�A.�Appendices</th></tr>
204N/A<tr>
204N/A<td width="20%" align="left">
0N/A<a accesskey="p" href="Bv9ARM.ch08.html">Prev</a>�</td>
0N/A<th width="60%" align="center">�</th>
0N/A<td width="20%" align="right">�<a accesskey="n" href="Bv9ARM.ch10.html">Next</a>
0N/A</td>
112N/A</tr>
0N/A</table>
0N/A<hr>
0N/A</div>
0N/A<div class="appendix" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title">
0N/A<a name="Bv9ARM.ch09"></a>Appendix�A.�Appendices</h2></div></div></div>
0N/A<div class="toc">
0N/A<p><b>Table of Contents</b></p>
0N/A<dl>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2600555">Acknowledgments</a></span></dt>
0N/A<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#historical_dns_information">A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym></a></span></dt></dl></dd>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch09.html#id2600659">General <acronym class="acronym">DNS</acronym> Reference Information</a></span></dt>
0N/A<dd><dl><dt><span class="sect2"><a href="Bv9ARM.ch09.html#ipv6addresses">IPv6 addresses (AAAA)</a></span></dt></dl></dd>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch09.html#bibliography">Bibliography (and Suggested Reading)</a></span></dt>
0N/A<dd><dl>
165N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#rfcs">Request for Comments (RFCs)</a></span></dt>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#internet_drafts">Internet Drafts</a></span></dt>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2604007">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
0N/A</dl></dd>
0N/A</dl>
0N/A</div>
0N/A<div class="sect1" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
0N/A<a name="id2600555"></a>Acknowledgments</h2></div></div></div>
204N/A<div class="sect2" lang="en">
868N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="historical_dns_information"></a>A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym>
0N/A</h3></div></div></div>
0N/A<p>
0N/A Although the "official" beginning of the Domain Name
0N/A System occurred in 1984 with the publication of RFC 920, the
0N/A core of the new system was described in 1983 in RFCs 882 and
0N/A 883. From 1984 to 1987, the ARPAnet (the precursor to today's
0N/A Internet) became a testbed of experimentation for developing the
0N/A new naming/addressing scheme in a rapidly expanding,
0N/A operational network environment. New RFCs were written and
0N/A published in 1987 that modified the original documents to
0N/A incorporate improvements based on the working model. RFC 1034,
0N/A "Domain Names-Concepts and Facilities", and RFC 1035, "Domain
0N/A Names-Implementation and Specification" were published and
868N/A became the standards upon which all <acronym class="acronym">DNS</acronym> implementations are
868N/A built.
0N/A </p>
0N/A<p>
0N/A The first working domain name server, called "Jeeves", was
0N/A written in 1983-84 by Paul Mockapetris for operation on DEC
536N/A Tops-20
0N/A machines located at the University of Southern California's
0N/A Information
0N/A Sciences Institute (USC-ISI) and SRI International's Network
0N/A Information
0N/A Center (SRI-NIC). A <acronym class="acronym">DNS</acronym> server for
0N/A Unix machines, the Berkeley Internet
0N/A Name Domain (<acronym class="acronym">BIND</acronym>) package, was
0N/A written soon after by a group of
0N/A graduate students at the University of California at Berkeley
0N/A under
868N/A a grant from the US Defense Advanced Research Projects
0N/A Administration
0N/A (DARPA).
0N/A </p>
112N/A<p>
112N/A Versions of <acronym class="acronym">BIND</acronym> through
112N/A 4.8.3 were maintained by the Computer
204N/A Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
204N/A Painter, David Riggle and Songnian Zhou made up the initial <acronym class="acronym">BIND</acronym>
204N/A project team. After that, additional work on the software package
204N/A was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment
204N/A Corporation
204N/A employee on loan to the CSRG, worked on <acronym class="acronym">BIND</acronym> for 2 years, from 1985
0N/A to 1987. Many other people also contributed to <acronym class="acronym">BIND</acronym> development
0N/A during that time: Doug Kingston, Craig Partridge, Smoot
0N/A Carl-Mitchell,
0N/A Mike Muuss, Jim Bloom and Mike Schwartz. <acronym class="acronym">BIND</acronym> maintenance was subsequently
0N/A handled by Mike Karels and �ivind Kure.
0N/A </p>
112N/A<p>
112N/A <acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were
112N/A released by Digital Equipment
204N/A Corporation (now Compaq Computer Corporation). Paul Vixie, then
204N/A a DEC employee, became <acronym class="acronym">BIND</acronym>'s
0N/A primary caretaker. He was assisted
204N/A by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan
204N/A Beecher, Andrew
0N/A Partan, Andy Cherenson, Tom Limoncelli, Berthold Paffrath, Fuat
0N/A Baran, Anant Kumar, Art Harkin, Win Treese, Don Lewis, Christophe
0N/A Wolfhugel, and others.
0N/A </p>
0N/A<p>
0N/A In 1994, <acronym class="acronym">BIND</acronym> version 4.9.2 was sponsored by
0N/A Vixie Enterprises. Paul
0N/A Vixie became <acronym class="acronym">BIND</acronym>'s principal
112N/A architect/programmer.
112N/A </p>
204N/A<p>
204N/A <acronym class="acronym">BIND</acronym> versions from 4.9.3 onward
0N/A have been developed and maintained
0N/A by the Internet Systems Consortium and its predecessor,
0N/A the Internet Software Consortium, with support being provided
0N/A by ISC's sponsors.
0N/A </p>
0N/A<p>
0N/A As co-architects/programmers, Bob Halley and
0N/A Paul Vixie released the first production-ready version of
0N/A <acronym class="acronym">BIND</acronym> version 8 in May 1997.
0N/A </p>
0N/A<p>
0N/A BIND version 9 was released in September 2000 and is a
0N/A major rewrite of nearly all aspects of the underlying
0N/A BIND architecture.
0N/A </p>
0N/A<p>
0N/A BIND versions 4 and 8 are officially deprecated.
0N/A No additional development is done
0N/A on BIND version 4 or BIND version 8.
0N/A </p>
0N/A<p>
0N/A <acronym class="acronym">BIND</acronym> development work is made
0N/A possible today by the sponsorship
0N/A of several corporations, and by the tireless work efforts of
0N/A numerous individuals.
0N/A </p>
0N/A</div>
0N/A</div>
0N/A<div class="sect1" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
0N/A<a name="id2600659"></a>General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div>
868N/A<div class="sect2" lang="en">
868N/A<div class="titlepage"><div><div><h3 class="title">
868N/A<a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h3></div></div></div>
868N/A<p>
868N/A IPv6 addresses are 128-bit identifiers for interfaces and
0N/A sets of interfaces which were introduced in the <acronym class="acronym">DNS</acronym> to facilitate
0N/A scalable Internet routing. There are three types of addresses: <span class="emphasis"><em>Unicast</em></span>,
0N/A an identifier for a single interface;
0N/A <span class="emphasis"><em>Anycast</em></span>,
0N/A an identifier for a set of interfaces; and <span class="emphasis"><em>Multicast</em></span>,
0N/A an identifier for a set of interfaces. Here we describe the global
0N/A Unicast address scheme. For more information, see RFC 3587,
0N/A "Global Unicast Address Format."
0N/A </p>
0N/A<p>
0N/A IPv6 unicast addresses consist of a
0N/A <span class="emphasis"><em>global routing prefix</em></span>, a
0N/A <span class="emphasis"><em>subnet identifier</em></span>, and an
868N/A <span class="emphasis"><em>interface identifier</em></span>.
868N/A </p>
868N/A<p>
868N/A The global routing prefix is provided by the
868N/A upstream provider or ISP, and (roughly) corresponds to the
0N/A IPv4 <span class="emphasis"><em>network</em></span> section
0N/A of the address range.
0N/A
0N/A The subnet identifier is for local subnetting, much the
868N/A same as subnetting an
868N/A IPv4 /16 network into /24 subnets.
0N/A
868N/A The interface identifier is the address of an individual
868N/A interface on a given network; in IPv6, addresses belong to
868N/A interfaces rather than to machines.
868N/A </p>
0N/A<p>
0N/A The subnetting capability of IPv6 is much more flexible than
868N/A that of IPv4: subnetting can be carried out on bit boundaries,
0N/A in much the same way as Classless InterDomain Routing
0N/A (CIDR), and the DNS PTR representation ("nibble" format)
0N/A makes setting up reverse zones easier.
868N/A </p>
868N/A<p>
0N/A The Interface Identifier must be unique on the local link,
868N/A and is usually generated automatically by the IPv6
0N/A implementation, although it is usually possible to
0N/A override the default setting if necessary. A typical IPv6
536N/A address might look like:
0N/A <span><strong class="command">2001:db8:201:9:a00:20ff:fe81:2b32</strong></span>
0N/A </p>
0N/A<p>
0N/A IPv6 address specifications often contain long strings
868N/A of zeros, so the architects have included a shorthand for
868N/A specifying
868N/A them. The double colon (`::') indicates the longest possible
868N/A string
0N/A of zeros that can fit, and can be used only once in an address.
868N/A </p>
0N/A</div>
0N/A</div>
0N/A<div class="sect1" lang="en">
0N/A<div class="titlepage"><div><div><h2 class="title" style="clear: both">
0N/A<a name="bibliography"></a>Bibliography (and Suggested Reading)</h2></div></div></div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
868N/A<a name="rfcs"></a>Request for Comments (RFCs)</h3></div></div></div>
868N/A<p>
868N/A Specification documents for the Internet protocol suite, including
868N/A the <acronym class="acronym">DNS</acronym>, are published as part of
0N/A the Request for Comments (RFCs)
0N/A series of technical notes. The standards themselves are defined
868N/A by the Internet Engineering Task Force (IETF) and the Internet
0N/A Engineering Steering Group (IESG). RFCs can be obtained online via FTP at:
0N/A </p>
868N/A<p>
868N/A <a href="ftp://www.isi.edu/in-notes/" target="_top">
0N/A ftp://www.isi.edu/in-notes/RFC<em class="replaceable"><code>xxxx</code></em>.txt
868N/A </a>
0N/A </p>
536N/A<p>
0N/A (where <em class="replaceable"><code>xxxx</code></em> is
0N/A the number of the RFC). RFCs are also available via the Web at:
0N/A </p>
0N/A<p>
0N/A <a href="http://www.ietf.org/rfc/" target="_top">http://www.ietf.org/rfc/</a>.
0N/A </p>
0N/A<div class="bibliography">
0N/A<div class="titlepage"><div><div><h4 class="title">
0N/A<a name="id2601051"></a>Bibliography</h4></div></div></div>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">Standards</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2601062"></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>
868N/A</div>
868N/A<div class="biblioentry">
868N/A<a name="id2601085"></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>
868N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601109"></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
0N/A Specification</i>. </span><span class="pubdate">November 1987. </span></p>
0N/A</div>
0N/A</div>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">
0N/A<a name="proposed_standards"></a>Proposed Standards</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2601145"></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>
0N/A Specification</i>. </span><span class="pubdate">July 1997. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601172"></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>
0N/A Queries</i>. </span><span class="pubdate">March 1998. </span></p>
0N/A</div>
165N/A<div class="biblioentry">
0N/A<a name="id2601197"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601222"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601245"></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>
0N/A</div>
204N/A<div class="biblioentry">
0N/A<a name="id2601301"></a><p>[<abbr class="abbrev">RFC2671</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="title"><i>Extension Mechanisms for DNS (EDNS0)</i>. </span><span class="pubdate">August 1997. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601328"></a><p>[<abbr class="abbrev">RFC2672</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span>. </span><span class="title"><i>Non-Terminal DNS Name Redirection</i>. </span><span class="pubdate">August 1999. </span></p>
0N/A</div>
204N/A<div class="biblioentry">
0N/A<a name="id2601354"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601416"></a><p>[<abbr class="abbrev">RFC2930</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Secret Key Establishment for DNS (TKEY RR)</i>. </span><span class="pubdate">September 2000. </span></p>
165N/A</div>
165N/A<div class="biblioentry">
165N/A<a name="id2601446"></a><p>[<abbr class="abbrev">RFC2931</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>DNS Request and Transaction Signatures (SIG(0)s)</i>. </span><span class="pubdate">September 2000. </span></p>
0N/A</div>
204N/A<div class="biblioentry">
0N/A<a name="id2601476"></a><p>[<abbr class="abbrev">RFC3007</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Secure Domain Name System (DNS) Dynamic Update</i>. </span><span class="pubdate">November 2000. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601502"></a><p>[<abbr class="abbrev">RFC3645</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Kwan</span>, <span class="firstname">P.</span> <span class="surname">Garg</span>, <span class="firstname">J.</span> <span class="surname">Gilroy</span>, <span class="firstname">L.</span> <span class="surname">Esibov</span>, <span class="firstname">J.</span> <span class="surname">Westhead</span>, and <span class="firstname">R.</span> <span class="surname">Hall</span>. </span><span class="title"><i>Generic Security Service Algorithm for Secret
0N/A Key Transaction Authentication for DNS
134N/A (GSS-TSIG)</i>. </span><span class="pubdate">October 2003. </span></p>
0N/A</div>
0N/A</div>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">
0N/A<acronym class="acronym">DNS</acronym> Security Proposed Standards</h3>
134N/A<div class="biblioentry">
0N/A<a name="id2601585"></a><p>[<abbr class="abbrev">RFC3225</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Conrad</span>. </span><span class="title"><i>Indicating Resolver Support of DNSSEC</i>. </span><span class="pubdate">December 2001. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601611"></a><p>[<abbr class="abbrev">RFC3833</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Atkins</span> and <span class="firstname">R.</span> <span class="surname">Austein</span>. </span><span class="title"><i>Threat Analysis of the Domain Name System (DNS)</i>. </span><span class="pubdate">August 2004. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601648"></a><p>[<abbr class="abbrev">RFC4033</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>DNS Security Introduction and Requirements</i>. </span><span class="pubdate">March 2005. </span></p>
204N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601713"></a><p>[<abbr class="abbrev">RFC4034</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Resource Records for the DNS Security Extensions</i>. </span><span class="pubdate">March 2005. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601778"></a><p>[<abbr class="abbrev">RFC4035</abbr>] <span class="authorgroup"><span class="firstname">R.</span> <span class="surname">Arends</span>, <span class="firstname">R.</span> <span class="surname">Austein</span>, <span class="firstname">M.</span> <span class="surname">Larson</span>, <span class="firstname">D.</span> <span class="surname">Massey</span>, and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Protocol Modifications for the DNS
0N/A Security Extensions</i>. </span><span class="pubdate">March 2005. </span></p>
0N/A</div>
0N/A</div>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">Other Important RFCs About <acronym class="acronym">DNS</acronym>
0N/A Implementation</h3>
112N/A<div class="biblioentry">
112N/A<a name="id2601851"></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
0N/A Deployed <acronym class="acronym">DNS</acronym> Software.</i>. </span><span class="pubdate">October 1993. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2601877"></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
0N/A Errors and Suggested Fixes</i>. </span><span class="pubdate">October 1993. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
868N/A<a name="id2601945"></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>
868N/A</div>
868N/A<div class="biblioentry">
868N/A<a name="id2601980"></a><p>[<abbr class="abbrev">RFC4074</abbr>] <span class="authorgroup"><span class="firstname">Y.</span> <span class="surname">Morishita</span> and <span class="firstname">T.</span> <span class="surname">Jinmei</span>. </span><span class="title"><i>Common Misbehaviour Against <acronym class="acronym">DNS</acronym>
0N/A Queries for IPv6 Addresses</i>. </span><span class="pubdate">May 2005. </span></p>
536N/A</div>
536N/A</div>
536N/A<div class="bibliodiv">
868N/A<h3 class="title">Resource Record Types</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2602094"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602152"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602189"></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
0N/A the Domain Name System</i>. </span><span class="pubdate">June 1997. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602225"></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
0N/A Domain
0N/A Name System</i>. </span><span class="pubdate">January 1996. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602279"></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
0N/A Location of
0N/A Services.</i>. </span><span class="pubdate">October 1996. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602317"></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
0N/A Distribute MIXER
0N/A Conformant Global Address Mapping</i>. </span><span class="pubdate">January 1998. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602343"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602369"></a><p>[<abbr class="abbrev">RFC2536</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>DSA KEYs and SIGs in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602395"></a><p>[<abbr class="abbrev">RFC2537</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>RSA/MD5 KEYs and SIGs in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602422"></a><p>[<abbr class="abbrev">RFC2538</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span> and <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Storing Certificates in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602461"></a><p>[<abbr class="abbrev">RFC2539</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Storage of Diffie-Hellman Keys in the Domain Name System (DNS)</i>. </span><span class="pubdate">March 1999. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602491"></a><p>[<abbr class="abbrev">RFC2540</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Detached Domain Name System (DNS) Information</i>. </span><span class="pubdate">March 1999. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602521"></a><p>[<abbr class="abbrev">RFC2782</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Gulbrandsen</span>. </span><span class="author"><span class="firstname">P.</span> <span class="surname">Vixie</span>. </span><span class="author"><span class="firstname">L.</span> <span class="surname">Esibov</span>. </span><span class="title"><i>A DNS RR for specifying the location of services (DNS SRV)</i>. </span><span class="pubdate">February 2000. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602564"></a><p>[<abbr class="abbrev">RFC2915</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Mealling</span>. </span><span class="author"><span class="firstname">R.</span> <span class="surname">Daniel</span>. </span><span class="title"><i>The Naming Authority Pointer (NAPTR) DNS Resource Record</i>. </span><span class="pubdate">September 2000. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602597"></a><p>[<abbr class="abbrev">RFC3110</abbr>] <span class="author"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS)</i>. </span><span class="pubdate">May 2001. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602624"></a><p>[<abbr class="abbrev">RFC3123</abbr>] <span class="author"><span class="firstname">P.</span> <span class="surname">Koch</span>. </span><span class="title"><i>A DNS RR Type for Lists of Address Prefixes (APL RR)</i>. </span><span class="pubdate">June 2001. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602647"></a><p>[<abbr class="abbrev">RFC3596</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Thomson</span>, <span class="firstname">C.</span> <span class="surname">Huitema</span>, <span class="firstname">V.</span> <span class="surname">Ksinant</span>, and <span class="firstname">M.</span> <span class="surname">Souissi</span>. </span><span class="title"><i><acronym class="acronym">DNS</acronym> Extensions to support IP
0N/A version 6</i>. </span><span class="pubdate">October 2003. </span></p>
204N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602705"></a><p>[<abbr class="abbrev">RFC3597</abbr>] <span class="author"><span class="firstname">A.</span> <span class="surname">Gustafsson</span>. </span><span class="title"><i>Handling of Unknown DNS Resource Record (RR) Types</i>. </span><span class="pubdate">September 2003. </span></p>
0N/A</div>
0N/A</div>
0N/A<div class="bibliodiv">
204N/A<h3 class="title">
0N/A<acronym class="acronym">DNS</acronym> and the Internet</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2602737"></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
536N/A and Other Types</i>. </span><span class="pubdate">April 1989. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602762"></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
0N/A Support</i>. </span><span class="pubdate">October 1989. </span></p>
204N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602785"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602808"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602854"></a><p>[<abbr class="abbrev">RFC2826</abbr>] <span class="authorgroup"><span class="surname">Internet Architecture Board</span>. </span><span class="title"><i>IAB Technical Comment on the Unique DNS Root</i>. </span><span class="pubdate">May 2000. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602877"></a><p>[<abbr class="abbrev">RFC2929</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>, <span class="firstname">E.</span> <span class="surname">Brunner-Williams</span>, and <span class="firstname">B.</span> <span class="surname">Manning</span>. </span><span class="title"><i>Domain Name System (DNS) IANA Considerations</i>. </span><span class="pubdate">September 2000. </span></p>
0N/A</div>
0N/A</div>
536N/A<div class="bibliodiv">
0N/A<h3 class="title">
0N/A<acronym class="acronym">DNS</acronym> Operations</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2602935"></a><p>[<abbr class="abbrev">RFC1033</abbr>] <span class="author"><span class="firstname">M.</span> <span class="surname">Lottor</span>. </span><span class="title"><i>Domain administrators operations guide.</i>. </span><span class="pubdate">November 1987. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602958"></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
0N/A Configuration Errors</i>. </span><span class="pubdate">October 1993. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2602985"></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
0N/A Configuration Errors</i>. </span><span class="pubdate">February 1996. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
536N/A<a name="id2603012"></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>
536N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603048"></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
0N/A Network Services.</i>. </span><span class="pubdate">October 1997. </span></p>
0N/A</div>
0N/A</div>
536N/A<div class="bibliodiv">
536N/A<h3 class="title">Internationalized Domain Names</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2603094"></a><p>[<abbr class="abbrev">RFC2825</abbr>] <span class="authorgroup"><span class="surname">IAB</span> and <span class="firstname">R.</span> <span class="surname">Daigle</span>. </span><span class="title"><i>A Tangled Web: Issues of I18N, Domain Names,
0N/A and the Other Internet protocols</i>. </span><span class="pubdate">May 2000. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
204N/A<a name="id2603126"></a><p>[<abbr class="abbrev">RFC3490</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Faltstrom</span>, <span class="firstname">P.</span> <span class="surname">Hoffman</span>, and <span class="firstname">A.</span> <span class="surname">Costello</span>. </span><span class="title"><i>Internationalizing Domain Names in Applications (IDNA)</i>. </span><span class="pubdate">March 2003. </span></p>
204N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603172"></a><p>[<abbr class="abbrev">RFC3491</abbr>] <span class="authorgroup"><span class="firstname">P.</span> <span class="surname">Hoffman</span> and <span class="firstname">M.</span> <span class="surname">Blanchet</span>. </span><span class="title"><i>Nameprep: A Stringprep Profile for Internationalized Domain Names</i>. </span><span class="pubdate">March 2003. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603207"></a><p>[<abbr class="abbrev">RFC3492</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Costello</span>. </span><span class="title"><i>Punycode: A Bootstring encoding of Unicode
0N/A for Internationalized Domain Names in
0N/A Applications (IDNA)</i>. </span><span class="pubdate">March 2003. </span></p>
536N/A</div>
0N/A</div>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">Other <acronym class="acronym">DNS</acronym>-related RFCs</h3>
0N/A<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
0N/A<h3 class="title">Note</h3>
0N/A<p>
0N/A Note: the following list of RFCs, although
0N/A <acronym class="acronym">DNS</acronym>-related, are not
0N/A concerned with implementing software.
0N/A </p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603252"></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
0N/A Attributes</i>. </span><span class="pubdate">May 1993. </span></p>
536N/A</div>
536N/A<div class="biblioentry">
0N/A<a name="id2603274"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603300"></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
0N/A Balancing</i>. </span><span class="pubdate">April 1995. </span></p>
536N/A</div>
536N/A<div class="biblioentry">
0N/A<a name="id2603325"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603349"></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>
0N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603395"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603418"></a><p>[<abbr class="abbrev">RFC3071</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Klensin</span>. </span><span class="title"><i>Reflections on the DNS, RFC 1591, and Categories of Domains</i>. </span><span class="pubdate">February 2001. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603445"></a><p>[<abbr class="abbrev">RFC3258</abbr>] <span class="authorgroup"><span class="firstname">T.</span> <span class="surname">Hardie</span>. </span><span class="title"><i>Distributing Authoritative Name Servers via
0N/A Shared Unicast Addresses</i>. </span><span class="pubdate">April 2002. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603470"></a><p>[<abbr class="abbrev">RFC3901</abbr>] <span class="authorgroup"><span class="firstname">A.</span> <span class="surname">Durand</span> and <span class="firstname">J.</span> <span class="surname">Ihren</span>. </span><span class="title"><i>DNS IPv6 Transport Operational Guidelines</i>. </span><span class="pubdate">September 2004. </span></p>
0N/A</div>
0N/A</div>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">Obsolete and Unimplemented Experimental RFC</h3>
0N/A<div class="biblioentry">
204N/A<a name="id2603514"></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
0N/A Location</i>. </span><span class="pubdate">November 1994. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603572"></a><p>[<abbr class="abbrev">RFC2673</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span>. </span><span class="title"><i>Binary Labels in the Domain Name System</i>. </span><span class="pubdate">August 1999. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2603598"></a><p>[<abbr class="abbrev">RFC2874</abbr>] <span class="authorgroup"><span class="firstname">M.</span> <span class="surname">Crawford</span> and <span class="firstname">C.</span> <span class="surname">Huitema</span>. </span><span class="title"><i>DNS Extensions to Support IPv6 Address Aggregation
0N/A and Renumbering</i>. </span><span class="pubdate">July 2000. </span></p>
0N/A</div>
0N/A</div>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">Obsoleted DNS Security RFCs</h3>
0N/A<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
0N/A<h3 class="title">Note</h3>
0N/A<p>
0N/A Most of these have been consolidated into RFC4033,
0N/A RFC4034 and RFC4035 which collectively describe DNSSECbis.
0N/A </p>
0N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603646"></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>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603686"></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>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603713"></a><p>[<abbr class="abbrev">RFC2535</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Eastlake</span>, <span class="lineage">3rd</span>. </span><span class="title"><i>Domain Name System Security Extensions</i>. </span><span class="pubdate">March 1999. </span></p>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603742"></a><p>[<abbr class="abbrev">RFC3008</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span>. </span><span class="title"><i>Domain Name System Security (DNSSEC)
204N/A Signing Authority</i>. </span><span class="pubdate">November 2000. </span></p>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603768"></a><p>[<abbr class="abbrev">RFC3090</abbr>] <span class="authorgroup"><span class="firstname">E.</span> <span class="surname">Lewis</span>. </span><span class="title"><i>DNS Security Extension Clarification on Zone Status</i>. </span><span class="pubdate">March 2001. </span></p>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603795"></a><p>[<abbr class="abbrev">RFC3445</abbr>] <span class="authorgroup"><span class="firstname">D.</span> <span class="surname">Massey</span> and <span class="firstname">S.</span> <span class="surname">Rose</span>. </span><span class="title"><i>Limiting the Scope of the KEY Resource Record (RR)</i>. </span><span class="pubdate">December 2002. </span></p>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603831"></a><p>[<abbr class="abbrev">RFC3655</abbr>] <span class="authorgroup"><span class="firstname">B.</span> <span class="surname">Wellington</span> and <span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Redefinition of DNS Authenticated Data (AD) bit</i>. </span><span class="pubdate">November 2003. </span></p>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603867"></a><p>[<abbr class="abbrev">RFC3658</abbr>] <span class="authorgroup"><span class="firstname">O.</span> <span class="surname">Gudmundsson</span>. </span><span class="title"><i>Delegation Signer (DS) Resource Record (RR)</i>. </span><span class="pubdate">December 2003. </span></p>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603894"></a><p>[<abbr class="abbrev">RFC3755</abbr>] <span class="authorgroup"><span class="firstname">S.</span> <span class="surname">Weiler</span>. </span><span class="title"><i>Legacy Resolver Compatibility for Delegation Signer (DS)</i>. </span><span class="pubdate">May 2004. </span></p>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603921"></a><p>[<abbr class="abbrev">RFC3757</abbr>] <span class="authorgroup"><span class="firstname">O.</span> <span class="surname">Kolkman</span>, <span class="firstname">J.</span> <span class="surname">Schlyter</span>, and <span class="firstname">E.</span> <span class="surname">Lewis</span>. </span><span class="title"><i>Domain Name System KEY (DNSKEY) Resource Record
204N/A (RR) Secure Entry Point (SEP) Flag</i>. </span><span class="pubdate">April 2004. </span></p>
204N/A</div>
204N/A<div class="biblioentry">
204N/A<a name="id2603965"></a><p>[<abbr class="abbrev">RFC3845</abbr>] <span class="authorgroup"><span class="firstname">J.</span> <span class="surname">Schlyter</span>. </span><span class="title"><i>DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format</i>. </span><span class="pubdate">August 2004. </span></p>
204N/A</div>
204N/A</div>
204N/A</div>
204N/A</div>
204N/A<div class="sect2" lang="en">
204N/A<div class="titlepage"><div><div><h3 class="title">
204N/A<a name="internet_drafts"></a>Internet Drafts</h3></div></div></div>
204N/A<p>
204N/A Internet Drafts (IDs) are rough-draft working documents of
204N/A the Internet Engineering Task Force. They are, in essence, RFCs
204N/A in the preliminary stages of development. Implementors are
0N/A cautioned not
0N/A to regard IDs as archival, and they should not be quoted or cited
0N/A in any formal documents unless accompanied by the disclaimer that
0N/A they are "works in progress." IDs have a lifespan of six months
536N/A after which they are deleted unless updated by their authors.
536N/A </p>
536N/A</div>
536N/A<div class="sect2" lang="en">
536N/A<div class="titlepage"><div><div><h3 class="title">
536N/A<a name="id2604007"></a>Other Documents About <acronym class="acronym">BIND</acronym>
536N/A</h3></div></div></div>
536N/A<p></p>
536N/A<div class="bibliography">
536N/A<div class="titlepage"><div><div><h4 class="title">
536N/A<a name="id2604017"></a>Bibliography</h4></div></div></div>
536N/A<div class="biblioentry">
536N/A<a name="id2604019"></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>
536N/A</div>
536N/A</div>
536N/A</div>
536N/A</div>
536N/A</div>
867N/A<div class="navfooter">
536N/A<hr>
536N/A<table width="100%" summary="Navigation footer">
536N/A<tr>
536N/A<td width="40%" align="left">
536N/A<a accesskey="p" href="Bv9ARM.ch08.html">Prev</a>�</td>
536N/A<td width="20%" align="center">�</td>
536N/A<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch10.html">Next</a>
536N/A</td>
536N/A</tr>
536N/A<tr>
536N/A<td width="40%" align="left" valign="top">Chapter�8.�Troubleshooting�</td>
536N/A<td width="20%" align="center"><a accesskey="h" href="Bv9ARM.html">Home</a></td>
0N/A<td width="40%" align="right" valign="top">�Manual pages</td>
0N/A</tr>
536N/A</table>
536N/A</div>
536N/A</body>
0N/A</html>
0N/A