Bv9ARM.ch09.html revision 74ae031d9d7780015c11242b71cecca905ada695
0N/A<!--
0N/A - Copyright (C) 2004-2014 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$ -->
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">
0N/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>
0N/A<tr>
0N/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>
0N/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#id2606677">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#id2606849">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>
0N/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#id2610197">Other Documents About <acronym class="acronym">BIND</acronym></a></span></dt>
0N/A</dl></dd>
0N/A<dt><span class="sect1"><a href="Bv9ARM.ch09.html#bind9.library">BIND 9 DNS Library Support</a></span></dt>
0N/A<dd><dl>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2611696">Prerequisite</a></span></dt>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2611705">Compilation</a></span></dt>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2611730">Installation</a></span></dt>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2611761">Known Defects/Restrictions</a></span></dt>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2611837">The dns.conf File</a></span></dt>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2611864">Sample Applications</a></span></dt>
0N/A<dt><span class="sect2"><a href="Bv9ARM.ch09.html#id2613110">Library References</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="id2606677"></a>Acknowledgments</h2></div></div></div>
0N/A<div class="sect2" lang="en">
0N/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
0N/A became the standards upon which all <acronym class="acronym">DNS</acronym> implementations are
0N/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
0N/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
0N/A a grant from the US Defense Advanced Research Projects
0N/A Administration
0N/A (DARPA).
0N/A </p>
0N/A<p>
0N/A Versions of <acronym class="acronym">BIND</acronym> through
0N/A 4.8.3 were maintained by the Computer
0N/A Systems Research Group (CSRG) at UC Berkeley. Douglas Terry, Mark
0N/A Painter, David Riggle and Songnian Zhou made up the initial <acronym class="acronym">BIND</acronym>
0N/A project team. After that, additional work on the software package
0N/A was done by Ralph Campbell. Kevin Dunlap, a Digital Equipment
0N/A Corporation
0N/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>
0N/A<p>
0N/A <acronym class="acronym">BIND</acronym> versions 4.9 and 4.9.1 were
0N/A released by Digital Equipment
0N/A Corporation (now Compaq Computer Corporation). Paul Vixie, then
0N/A a DEC employee, became <acronym class="acronym">BIND</acronym>'s
0N/A primary caretaker. He was assisted
0N/A by Phil Almquist, Robert Elz, Alan Barrett, Paul Albitz, Bryan
0N/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
0N/A architect/programmer.
0N/A </p>
0N/A<p>
0N/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="id2606849"></a>General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h3></div></div></div>
0N/A<p>
0N/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
0N/A <span class="emphasis"><em>interface identifier</em></span>.
0N/A </p>
0N/A<p>
0N/A The global routing prefix is provided by the
0N/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
0N/A same as subnetting an
0N/A IPv4 /16 network into /24 subnets.
0N/A
0N/A The interface identifier is the address of an individual
0N/A interface on a given network; in IPv6, addresses belong to
0N/A interfaces rather than to machines.
0N/A </p>
0N/A<p>
0N/A The subnetting capability of IPv6 is much more flexible than
0N/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.
0N/A </p>
0N/A<p>
0N/A The Interface Identifier must be unique on the local link,
0N/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
0N/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
0N/A of zeros, so the architects have included a shorthand for
0N/A specifying
0N/A them. The double colon (`::') indicates the longest possible
0N/A string
0N/A of zeros that can fit, and can be used only once in an address.
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="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">
0N/A<a name="rfcs"></a>Request for Comments (RFCs)</h3></div></div></div>
0N/A<p>
0N/A Specification documents for the Internet protocol suite, including
0N/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
0N/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>
0N/A<p>
0N/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
0N/A </a>
0N/A </p>
0N/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="id2607036"></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="id2607047"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2607070"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2607094"></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="id2607130"></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="id2607157"></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>
0N/A<div class="biblioentry">
0N/A<a name="id2607182"></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="id2607207"></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="id2607230"></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>
0N/A<div class="biblioentry">
0N/A<a name="id2607286"></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="id2607313"></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>
0N/A<div class="biblioentry">
0N/A<a name="id2607339"></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="id2607469"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2607499"></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>
0N/A<div class="biblioentry">
0N/A<a name="id2607529"></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="id2607556"></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
0N/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>
0N/A<div class="biblioentry">
0N/A<a name="id2607638"></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="id2607665"></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="id2607701"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2607766"></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="id2607831"></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>
0N/A<div class="biblioentry">
0N/A<a name="id2607905"></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="id2607930"></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">
0N/A<a name="id2607998"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2608034"></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>
0N/A</div>
0N/A</div>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">Resource Record Types</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2608080"></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="id2608137"></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="id2608174"></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="id2608210"></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="id2608332"></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="id2608371"></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="id2608396"></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="id2608422"></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="id2608449"></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="id2608475"></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="id2608515"></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="id2608545"></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="id2608574"></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="id2608617"></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="id2608650"></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="id2608677"></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="id2608700"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2608758"></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">
0N/A<h3 class="title">
0N/A<acronym class="acronym">DNS</acronym> and the Internet</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2608790"></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
0N/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="id2608816"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2608838"></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="id2608861"></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="id2608907"></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="id2608931"></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>
0N/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="id2608988"></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="id2609012"></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="id2609038"></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">
0N/A<a name="id2609065"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609101"></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>
0N/A<div class="bibliodiv">
0N/A<h3 class="title">Internationalized Domain Names</h3>
0N/A<div class="biblioentry">
0N/A<a name="id2609147"></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">
0N/A<a name="id2609179"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609225"></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="id2609260"></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>
0N/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="id2609442"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609464"></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="id2609490"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609515"></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="id2609539"></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>
0N/A<div class="biblioentry">
0N/A<a name="id2609585"></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="id2609608"></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="id2609635"></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="id2609660"></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">
0N/A<a name="id2609704"></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="id2609762"></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="id2609788"></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>
0N/A<div class="biblioentry">
0N/A<a name="id2609836"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609876"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609902"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609932"></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)
0N/A Signing Authority</i>. </span><span class="pubdate">November 2000. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609958"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2609985"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2610021"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2610057"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2610084"></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>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2610110"></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
0N/A (RR) Secure Entry Point (SEP) Flag</i>. </span><span class="pubdate">April 2004. </span></p>
0N/A</div>
0N/A<div class="biblioentry">
0N/A<a name="id2610155"></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>
0N/A</div>
0N/A</div>
0N/A</div>
0N/A</div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="internet_drafts"></a>Internet Drafts</h3></div></div></div>
0N/A<p>
0N/A Internet Drafts (IDs) are rough-draft working documents of
0N/A the Internet Engineering Task Force. They are, in essence, RFCs
0N/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
0N/A after which they are deleted unless updated by their authors.
0N/A </p>
0N/A</div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="id2610197"></a>Other Documents About <acronym class="acronym">BIND</acronym>
0N/A</h3></div></div></div>
0N/A<p></p>
0N/A<div class="bibliography">
0N/A<div class="titlepage"><div><div><h4 class="title">
0N/A<a name="id2610206"></a>Bibliography</h4></div></div></div>
0N/A<div class="biblioentry">
0N/A<a name="id2610209"></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>
0N/A</div>
0N/A</div>
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="bind9.library"></a>BIND 9 DNS Library Support</h2></div></div></div>
0N/A<p>This version of BIND 9 "exports" its internal libraries so
0N/A that they can be used by third-party applications more easily (we
0N/A call them "export" libraries in this document). In addition to
0N/A all major DNS-related APIs BIND 9 is currently using, the export
0N/A libraries provide the following features:</p>
0N/A<div class="itemizedlist"><ul type="disc">
0N/A<li><p>The newly created "DNS client" module. This is a higher
0N/A level API that provides an interface to name resolution,
0N/A single DNS transaction with a particular server, and dynamic
0N/A update. Regarding name resolution, it supports advanced
0N/A features such as DNSSEC validation and caching. This module
0N/A supports both synchronous and asynchronous mode.</p></li>
0N/A<li><p>The new "IRS" (Information Retrieval System) library.
0N/A It provides an interface to parse the traditional resolv.conf
0N/A file and more advanced, DNS-specific configuration file for
0N/A the rest of this package (see the description for the
0N/A dns.conf file below).</p></li>
0N/A<li><p>As part of the IRS library, newly implemented standard
0N/A address-name mapping functions, getaddrinfo() and
0N/A getnameinfo(), are provided. They use the DNSSEC-aware
0N/A validating resolver backend, and could use other advanced
0N/A features of the BIND 9 libraries such as caching. The
0N/A getaddrinfo() function resolves both A and AAAA RRs
0N/A concurrently (when the address family is unspecified).</p></li>
0N/A<li><p>An experimental framework to support other event
0N/A libraries than BIND 9's internal event task system.</p></li>
0N/A</ul></div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="id2611696"></a>Prerequisite</h3></div></div></div>
0N/A<p>GNU make is required to build the export libraries (other
0N/A part of BIND 9 can still be built with other types of make). In
0N/A the reminder of this document, "make" means GNU make. Note that
0N/A in some platforms you may need to invoke a different command name
0N/A than "make" (e.g. "gmake") to indicate it's GNU make.</p>
0N/A</div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="id2611705"></a>Compilation</h3></div></div></div>
0N/A<pre class="screen">
0N/A$ <strong class="userinput"><code>/configure --enable-exportlib <em class="replaceable"><code>[other flags]</code></em></code></strong>
0N/A$ <strong class="userinput"><code>make</code></strong>
0N/A</pre>
0N/A<p>
0N/A This will create (in addition to usual BIND 9 programs) and a
0N/A separate set of libraries under the lib/export directory. For
0N/A example, <code class="filename">lib/export/dns/libdns.a</code> is the archive file of the
0N/A export version of the BIND 9 DNS library. Sample application
0N/A programs using the libraries will also be built under the
0N/A lib/export/samples directory (see below).</p>
0N/A</div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="id2611730"></a>Installation</h3></div></div></div>
0N/A<pre class="screen">
0N/A$ <strong class="userinput"><code>cd lib/export</code></strong>
0N/A$ <strong class="userinput"><code>make install</code></strong>
0N/A</pre>
0N/A<p>
0N/A This will install library object files under the directory
0N/A specified by the --with-export-libdir configure option (default:
0N/A EPREFIX/lib/bind9), and header files under the directory
0N/A specified by the --with-export-includedir configure option
0N/A (default: PREFIX/include/bind9).
0N/A Root privilege is normally required.
0N/A "<span><strong class="command">make install</strong></span>" at the top directory will do the
0N/A same.
0N/A </p>
0N/A<p>
0N/A To see how to build your own
0N/A application after the installation, see
0N/A <code class="filename">lib/export/samples/Makefile-postinstall.in</code>.</p>
0N/A</div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="id2611761"></a>Known Defects/Restrictions</h3></div></div></div>
0N/A<div class="itemizedlist"><ul type="disc">
0N/A<li><p>Currently, win32 is not supported for the export
0N/A library. (Normal BIND 9 application can be built as
0N/A before).</p></li>
0N/A<li>
0N/A<p>The "fixed" RRset order is not (currently) supported in
0N/A the export library. If you want to use "fixed" RRset order
0N/A for, e.g. <span><strong class="command">named</strong></span> while still building the
0N/A export library even without the fixed order support, build
0N/A them separately:
0N/A </p>
0N/A<pre class="screen">
0N/A$ <strong class="userinput"><code>/configure --enable-fixed-rrset <em class="replaceable"><code>[other flags, but not --enable-exportlib]</code></em></code></strong>
0N/A$ <strong class="userinput"><code>make</code></strong>
0N/A$ <strong class="userinput"><code>/configure --enable-exportlib <em class="replaceable"><code>[other flags, but not --enable-fixed-rrset]</code></em></code></strong>
0N/A$ <strong class="userinput"><code>cd lib/export</code></strong>
0N/A$ <strong class="userinput"><code>make</code></strong>
0N/A</pre>
0N/A<p>
0N/A </p>
0N/A</li>
0N/A<li><p>The client module and the IRS library currently do not
0N/A support DNSSEC validation using DLV (the underlying modules
0N/A can handle it, but there is no tunable interface to enable
0N/A the feature).</p></li>
0N/A<li><p>RFC 5011 is not supported in the validating stub
0N/A resolver of the export library. In fact, it is not clear
0N/A whether it should: trust anchors would be a system-wide
0N/A configuration which would be managed by an administrator,
0N/A while the stub resolver will be used by ordinary applications
0N/A run by a normal user.</p></li>
0N/A<li><p>Not all common <code class="filename">/etc/resolv.conf</code>
0N/A options are supported
0N/A in the IRS library. The only available options in this
0N/A version are "debug" and "ndots".</p></li>
0N/A</ul></div>
0N/A</div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="id2611837"></a>The dns.conf File</h3></div></div></div>
0N/A<p>The IRS library supports an "advanced" configuration file
0N/A related to the DNS library for configuration parameters that
0N/A would be beyond the capability of the
0N/A <code class="filename">resolv.conf</code> file.
0N/A Specifically, it is intended to provide DNSSEC related
0N/A configuration parameters. By default the path to this
0N/A configuration file is <code class="filename">/etc/dns.conf</code>.
0N/A This module is very
0N/A experimental and the configuration syntax or library interfaces
0N/A may change in future versions. Currently, only the
0N/A <span><strong class="command">trusted-keys</strong></span>
0N/A statement is supported, whose syntax is the same as the same name
0N/A of statement for <code class="filename">named.conf</code>. (See
0N/A <a href="Bv9ARM.ch06.html#trusted-keys" title="trusted-keys Statement Grammar">the section called &#8220;<span><strong class="command">trusted-keys</strong></span> Statement Grammar&#8221;</a> for details.)</p>
0N/A</div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="id2611864"></a>Sample Applications</h3></div></div></div>
0N/A<p>Some sample application programs using this API are
0N/A provided for reference. The following is a brief description of
0N/A these applications.
0N/A </p>
0N/A<div class="sect3" lang="en">
0N/A<div class="titlepage"><div><div><h4 class="title">
0N/A<a name="id2611873"></a>sample: a simple stub resolver utility</h4></div></div></div>
0N/A<p>
0N/A It sends a query of a given name (of a given optional RR type) to a
0N/A specified recursive server, and prints the result as a list of
0N/A RRs. It can also act as a validating stub resolver if a trust
0N/A anchor is given via a set of command line options.</p>
0N/A<p>
0N/A Usage: sample [options] server_address hostname
0N/A </p>
0N/A<p>
0N/A Options and Arguments:
0N/A </p>
0N/A<div class="variablelist"><dl>
0N/A<dt><span class="term">
0N/A -t RRtype
0N/A </span></dt>
0N/A<dd><p>
0N/A specify the RR type of the query. The default is the A RR.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A [-a algorithm] [-e] -k keyname -K keystring
0N/A </span></dt>
0N/A<dd>
0N/A<p>
0N/A specify a command-line DNS key to validate the answer. For
0N/A example, to specify the following DNSKEY of example.com:
0N/A</p>
0N/A<div class="literallayout"><p><br>
0N/A����������������example.com.�3600�IN�DNSKEY�257�3�5�xxx<br>
0N/A</p></div>
0N/A<p>
0N/A specify the options as follows:
0N/A</p>
0N/A<pre class="screen">
0N/A<strong class="userinput"><code>
0N/A -e -k example.com -K "xxx"
0N/A</code></strong>
0N/A</pre>
0N/A<p>
0N/A -e means that this key is a zone's "key signing key" (as known
0N/A as "secure Entry point").
0N/A When -a is omitted rsasha1 will be used by default.
0N/A </p>
0N/A</dd>
0N/A<dt><span class="term">
0N/A -s domain:alt_server_address
0N/A </span></dt>
0N/A<dd><p>
0N/A specify a separate recursive server address for the specific
0N/A "domain". Example: -s example.com:2001:db8::1234
0N/A </p></dd>
0N/A<dt><span class="term">server_address</span></dt>
0N/A<dd><p>
0N/A an IP(v4/v6) address of the recursive server to which queries
0N/A are sent.
0N/A </p></dd>
0N/A<dt><span class="term">hostname</span></dt>
0N/A<dd><p>
0N/A the domain name for the query
0N/A </p></dd>
0N/A</dl></div>
0N/A</div>
0N/A<div class="sect3" lang="en">
0N/A<div class="titlepage"><div><div><h4 class="title">
0N/A<a name="id2612236"></a>sample-async: a simple stub resolver, working asynchronously</h4></div></div></div>
0N/A<p>
0N/A Similar to "sample", but accepts a list
0N/A of (query) domain names as a separate file and resolves the names
0N/A asynchronously.</p>
0N/A<p>
0N/A Usage: sample-async [-s server_address] [-t RR_type] input_file</p>
0N/A<p>
0N/A Options and Arguments:
0N/A </p>
0N/A<div class="variablelist"><dl>
0N/A<dt><span class="term">
0N/A -s server_address
0N/A </span></dt>
0N/A<dd>
0N/A an IPv4 address of the recursive server to which queries are sent.
0N/A (IPv6 addresses are not supported in this implementation)
0N/A </dd>
0N/A<dt><span class="term">
0N/A -t RR_type
0N/A </span></dt>
0N/A<dd>
0N/A specify the RR type of the queries. The default is the A
0N/A RR.
0N/A </dd>
0N/A<dt><span class="term">
0N/A input_file
0N/A </span></dt>
0N/A<dd>
0N/A a list of domain names to be resolved. each line
0N/A consists of a single domain name. Example:
0N/A <div class="literallayout"><p><br>
0N/A��www.example.com<br>
0N/A��mx.examle.net<br>
0N/A��ns.xxx.example<br>
0N/A</p></div>
0N/A</dd>
0N/A</dl></div>
0N/A</div>
0N/A<div class="sect3" lang="en">
0N/A<div class="titlepage"><div><div><h4 class="title">
0N/A<a name="id2612290"></a>sample-request: a simple DNS transaction client</h4></div></div></div>
0N/A<p>
0N/A It sends a query to a specified server, and
0N/A prints the response with minimal processing. It doesn't act as a
0N/A "stub resolver": it stops the processing once it gets any
0N/A response from the server, whether it's a referral or an alias
0N/A (CNAME or DNAME) that would require further queries to get the
0N/A ultimate answer. In other words, this utility acts as a very
0N/A simplified <span><strong class="command">dig</strong></span>.
0N/A </p>
0N/A<p>
0N/A Usage: sample-request [-t RRtype] server_address hostname
0N/A </p>
0N/A<p>
0N/A Options and Arguments:
0N/A </p>
0N/A<div class="variablelist"><dl>
0N/A<dt><span class="term">
0N/A -t RRtype
0N/A </span></dt>
0N/A<dd><p>
0N/A specify the RR type of
0N/A the queries. The default is the A RR.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A server_address
0N/A </span></dt>
0N/A<dd><p>
0N/A an IP(v4/v6)
0N/A address of the recursive server to which the query is sent.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A hostname
0N/A </span></dt>
0N/A<dd><p>
0N/A the domain name for the query
0N/A </p></dd>
0N/A</dl></div>
0N/A</div>
0N/A<div class="sect3" lang="en">
0N/A<div class="titlepage"><div><div><h4 class="title">
0N/A<a name="id2612354"></a>sample-gai: getaddrinfo() and getnameinfo() test code</h4></div></div></div>
0N/A<p>
0N/A This is a test program
0N/A to check getaddrinfo() and getnameinfo() behavior. It takes a
0N/A host name as an argument, calls getaddrinfo() with the given host
0N/A name, and calls getnameinfo() with the resulting IP addresses
0N/A returned by getaddrinfo(). If the dns.conf file exists and
0N/A defines a trust anchor, the underlying resolver will act as a
0N/A validating resolver, and getaddrinfo()/getnameinfo() will fail
0N/A with an EAI_INSECUREDATA error when DNSSEC validation fails.
0N/A </p>
0N/A<p>
0N/A Usage: sample-gai hostname
0N/A </p>
0N/A</div>
0N/A<div class="sect3" lang="en">
0N/A<div class="titlepage"><div><div><h4 class="title">
0N/A<a name="id2612915"></a>sample-update: a simple dynamic update client program</h4></div></div></div>
0N/A<p>
0N/A It accepts a single update command as a
0N/A command-line argument, sends an update request message to the
0N/A authoritative server, and shows the response from the server. In
0N/A other words, this is a simplified <span><strong class="command">nsupdate</strong></span>.
0N/A </p>
0N/A<p>
0N/A Usage: sample-update [options] (add|delete) "update data"
0N/A </p>
0N/A<p>
0N/A Options and Arguments:
0N/A </p>
0N/A<div class="variablelist"><dl>
0N/A<dt><span class="term">
0N/A -a auth_server
0N/A </span></dt>
0N/A<dd><p>
0N/A An IP address of the authoritative server that has authority
0N/A for the zone containing the update name. This should normally
0N/A be the primary authoritative server that accepts dynamic
0N/A updates. It can also be a secondary server that is configured
0N/A to forward update requests to the primary server.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A -k keyfile
0N/A </span></dt>
0N/A<dd><p>
0N/A A TSIG key file to secure the update transaction. The keyfile
0N/A format is the same as that for the nsupdate utility.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A -p prerequisite
0N/A </span></dt>
0N/A<dd><p>
0N/A A prerequisite for the update (only one prerequisite can be
0N/A specified). The prerequisite format is the same as that is
0N/A accepted by the nsupdate utility.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A -r recursive_server
0N/A </span></dt>
0N/A<dd><p>
0N/A An IP address of a recursive server that this utility will
0N/A use. A recursive server may be necessary to identify the
0N/A authoritative server address to which the update request is
0N/A sent.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A -z zonename
0N/A </span></dt>
0N/A<dd><p>
0N/A The domain name of the zone that contains
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A (add|delete)
0N/A </span></dt>
0N/A<dd><p>
0N/A Specify the type of update operation. Either "add" or "delete"
0N/A must be specified.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A "update data"
0N/A </span></dt>
0N/A<dd><p>
0N/A Specify the data to be updated. A typical example of the data
0N/A would look like "name TTL RRtype RDATA".
0N/A </p></dd>
0N/A</dl></div>
0N/A<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">
0N/A<h3 class="title">Note</h3>In practice, either -a or -r must be specified. Others can
0N/A be optional; the underlying library routine tries to identify the
0N/A appropriate server and the zone name for the update.</div>
0N/A<p>
0N/A Examples: assuming the primary authoritative server of the
0N/A dynamic.example.com zone has an IPv6 address 2001:db8::1234,
0N/A </p>
0N/A<pre class="screen">
0N/A$ <strong class="userinput"><code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key add "foo.dynamic.example.com 30 IN A 192.168.2.1"</code></strong></pre>
0N/A<p>
0N/A adds an A RR for foo.dynamic.example.com using the given key.
0N/A </p>
0N/A<pre class="screen">
0N/A$ <strong class="userinput"><code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com 30 IN A"</code></strong></pre>
0N/A<p>
0N/A removes all A RRs for foo.dynamic.example.com using the given key.
0N/A </p>
0N/A<pre class="screen">
0N/A$ <strong class="userinput"><code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com"</code></strong></pre>
0N/A<p>
0N/A removes all RRs for foo.dynamic.example.com using the given key.
0N/A </p>
0N/A</div>
0N/A<div class="sect3" lang="en">
0N/A<div class="titlepage"><div><div><h4 class="title">
0N/A<a name="id2613046"></a>nsprobe: domain/name server checker in terms of RFC 4074</h4></div></div></div>
0N/A<p>
0N/A It checks a set
0N/A of domains to see the name servers of the domains behave
0N/A correctly in terms of RFC 4074. This is included in the set of
0N/A sample programs to show how the export library can be used in a
0N/A DNS-related application.
0N/A </p>
0N/A<p>
0N/A Usage: nsprobe [-d] [-v [-v...]] [-c cache_address] [input_file]
0N/A </p>
0N/A<p>
0N/A Options
0N/A </p>
0N/A<div class="variablelist"><dl>
0N/A<dt><span class="term">
0N/A -d
0N/A </span></dt>
0N/A<dd><p>
0N/A run in the "debug" mode. with this option nsprobe will dump
0N/A every RRs it receives.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A -v
0N/A </span></dt>
0N/A<dd><p>
0N/A increase verbosity of other normal log messages. This can be
0N/A specified multiple times
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A -c cache_address
0N/A </span></dt>
0N/A<dd><p>
0N/A specify an IP address of a recursive (caching) name server.
0N/A nsprobe uses this server to get the NS RRset of each domain and
0N/A the A and/or AAAA RRsets for the name servers. The default
0N/A value is 127.0.0.1.
0N/A </p></dd>
0N/A<dt><span class="term">
0N/A input_file
0N/A </span></dt>
0N/A<dd><p>
0N/A a file name containing a list of domain (zone) names to be
0N/A probed. when omitted the standard input will be used. Each
0N/A line of the input file specifies a single domain name such as
0N/A "example.com". In general this domain name must be the apex
0N/A name of some DNS zone (unlike normal "host names" such as
0N/A "www.example.com"). nsprobe first identifies the NS RRsets for
0N/A the given domain name, and sends A and AAAA queries to these
0N/A servers for some "widely used" names under the zone;
0N/A specifically, adding "www" and "ftp" to the zone name.
0N/A </p></dd>
0N/A</dl></div>
0N/A</div>
0N/A</div>
0N/A<div class="sect2" lang="en">
0N/A<div class="titlepage"><div><div><h3 class="title">
0N/A<a name="id2613110"></a>Library References</h3></div></div></div>
0N/A<p>As of this writing, there is no formal "manual" of the
0N/A libraries, except this document, header files (some of them
0N/A provide pretty detailed explanations), and sample application
0N/A programs.</p>
0N/A</div>
0N/A</div>
0N/A</div>
0N/A<div class="navfooter">
0N/A<hr>
0N/A<table width="100%" summary="Navigation footer">
0N/A<tr>
0N/A<td width="40%" align="left">
0N/A<a accesskey="p" href="Bv9ARM.ch08.html">Prev</a>�</td>
0N/A<td width="20%" align="center">�</td>
0N/A<td width="40%" align="right">�<a accesskey="n" href="Bv9ARM.ch10.html">Next</a>
0N/A</td>
0N/A</tr>
0N/A<tr>
0N/A<td width="40%" align="left" valign="top">Chapter�8.�Troubleshooting�</td>
0N/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>
0N/A</table>
0N/A</div>
0N/A</body>
0N/A</html>
0N/A