src - FreeBSD source tree

diff options


context:
space:
mode:

author	Doug Barton <dougb@FreeBSD.org>	2011-07-16 10:49:33 +0000
committer	Doug Barton <dougb@FreeBSD.org>	2011-07-16 10:49:33 +0000
commit	473038528ab5bd55332138ebf791ab91a25f747b (patch)
tree	cb160fa2acd93f24b5f5b9082cd3afc68396d51a /doc/arm/Bv9ARM.ch09.html
parent	46da9ebeb3b1241e2e7f0182d76c336966e91d20 (diff)

Vendor import of BIND 9.8.0-P4vendor/bind9/9.8.0-P4

Notes

Notes: svn path=/vendor/bind9/dist/; revision=224090 svn path=/vendor/bind9/9.8.0-P4/; revision=224091; tag=vendor/bind9/9.8.0-P4

Diffstat (limited to 'doc/arm/Bv9ARM.ch09.html')

-rw-r--r--

doc/arm/Bv9ARM.ch09.html

657

1 files changed, 566 insertions, 91 deletions

diff --git a/doc/arm/Bv9ARM.ch09.html b/doc/arm/Bv9ARM.ch09.html
index c5bd994e0bee..fd532377bad5 100644
--- a/doc/arm/Bv9ARM.ch09.html
+++ b/doc/arm/Bv9ARM.ch09.html

@@ -1,5 +1,5 @@

<!--

- Permission to use, copy, modify, and/or distribute this software for any

@@ -14,7 +14,7 @@

- OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR

- PERFORMANCE OF THIS SOFTWARE.

-->

-

+

<html>

<head>

@@ -45,21 +45,31 @@

Table of Contents

<dl>

-<dt><a href="Bv9ARM.ch09.html#id2599606">Acknowledgments</a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2603147">Acknowledgments</a></dt>

<dd><dl><dt><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></dt></dl></dd>

-<dt><a href="Bv9ARM.ch09.html#id2599778">General <acronym class="acronym">DNS</acronym> Reference Information</a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2603319">General <acronym class="acronym">DNS</acronym> Reference Information</a></dt>

<dd><dl><dt><a href="Bv9ARM.ch09.html#ipv6addresses">IPv6 addresses (AAAA)</a></dt></dl></dd>

<dt><a href="Bv9ARM.ch09.html#bibliography">Bibliography (and Suggested Reading)</a></dt>

<dt><a href="Bv9ARM.ch09.html#rfcs">Request for Comments (RFCs)</a></dt>

<dt><a href="Bv9ARM.ch09.html#internet_drafts">Internet Drafts</a></dt>

-<dt><a href="Bv9ARM.ch09.html#id2603126">Other Documents About <acronym class="acronym">BIND</acronym></a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2606462">Other Documents About <acronym class="acronym">BIND</acronym></a></dt>

+</dl></dd>

+<dt><a href="Bv9ARM.ch09.html#bind9.library">BIND 9 DNS Library Support</a></dt>

+<dd><dl>

+<dt><a href="Bv9ARM.ch09.html#id2608789">Prerequisite</a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2608798">Compilation</a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2608004">Installation</a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2608035">Known Defects/Restrictions</a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2608112">The dns.conf File</a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2608138">Sample Applications</a></dt>

+<dt><a href="Bv9ARM.ch09.html#id2609111">Library References</a></dt>

</dl></dd>

</dl>

</div>

-<a name="id2599606"></a>Acknowledgments</h2></div></div></div>

+<a name="id2603147"></a>Acknowledgments</h2></div></div></div>

<a name="historical_dns_information"></a>A Brief History of the <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym>

@@ -162,7 +172,7 @@

</div>

-<a name="id2599778"></a>General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div>

+<a name="id2603319"></a>General <acronym class="acronym">DNS</acronym> Reference Information</h2></div></div></div>

<a name="ipv6addresses"></a>IPv6 addresses (AAAA)</h3></div></div></div>

@@ -250,17 +260,17 @@

-<a name="id2599897"></a>Bibliography</h4></div></div></div>

+<a name="id2603507"></a>Bibliography</h4></div></div></div>

<h3 class="title">Standards</h3>

-<a name="id2599908"></a>[<abbr class="abbrev">RFC974</abbr>] C. Partridge. Mail Routing and the Domain System. January 1986.

+<a name="id2603517"></a>[<abbr class="abbrev">RFC974</abbr>] C. Partridge. Mail Routing and the Domain System. January 1986.

</div>

-<a name="id2599931"></a>[<abbr class="abbrev">RFC1034</abbr>] P.V. Mockapetris. Domain Names — Concepts and Facilities. November 1987.

+<a name="id2603541"></a>[<abbr class="abbrev">RFC1034</abbr>] P.V. Mockapetris. Domain Names — Concepts and Facilities. November 1987.

</div>

-<a name="id2600023"></a>[<abbr class="abbrev">RFC1035</abbr>] P. V. Mockapetris. Domain Names — Implementation and

+<a name="id2603564"></a>[<abbr class="abbrev">RFC1035</abbr>] P. V. Mockapetris. Domain Names — Implementation and

Specification. November 1987.

</div>

@@ -268,42 +278,42 @@

<a name="proposed_standards"></a>Proposed Standards</h3>

-<a name="id2600059"></a>[<abbr class="abbrev">RFC2181</abbr>] R., R. Bush Elz. Clarifications to the <acronym class="acronym">DNS</acronym>

+<a name="id2603601"></a>[<abbr class="abbrev">RFC2181</abbr>] R., R. Bush Elz. Clarifications to the <acronym class="acronym">DNS</acronym>

Specification. July 1997.

</div>

-<a name="id2600086"></a>[<abbr class="abbrev">RFC2308</abbr>] M. Andrews. Negative Caching of <acronym class="acronym">DNS</acronym>

+<a name="id2603627"></a>[<abbr class="abbrev">RFC2308</abbr>] M. Andrews. Negative Caching of <acronym class="acronym">DNS</acronym>

Queries. March 1998.

</div>

-<a name="id2600112"></a>[<abbr class="abbrev">RFC1995</abbr>] M. Ohta. Incremental Zone Transfer in <acronym class="acronym">DNS</acronym>. August 1996.

+<a name="id2603653"></a>[<abbr class="abbrev">RFC1995</abbr>] M. Ohta. Incremental Zone Transfer in <acronym class="acronym">DNS</acronym>. August 1996.

</div>

-<a name="id2600136"></a>[<abbr class="abbrev">RFC1996</abbr>] P. Vixie. A Mechanism for Prompt Notification of Zone Changes. August 1996.

+<a name="id2603677"></a>[<abbr class="abbrev">RFC1996</abbr>] P. Vixie. A Mechanism for Prompt Notification of Zone Changes. August 1996.

</div>

-<a name="id2600160"></a>[<abbr class="abbrev">RFC2136</abbr>] P. Vixie, S. Thomson, Y. Rekhter, and J. Bound. Dynamic Updates in the Domain Name System. April 1997.

+<a name="id2603701"></a>[<abbr class="abbrev">RFC2136</abbr>] P. Vixie, S. Thomson, Y. Rekhter, and J. Bound. Dynamic Updates in the Domain Name System. April 1997.

</div>

-<a name="id2600215"></a>[<abbr class="abbrev">RFC2671</abbr>] P. Vixie. Extension Mechanisms for DNS (EDNS0). August 1997.

+<a name="id2603756"></a>[<abbr class="abbrev">RFC2671</abbr>] P. Vixie. Extension Mechanisms for DNS (EDNS0). August 1997.

</div>

-<a name="id2600242"></a>[<abbr class="abbrev">RFC2672</abbr>] M. Crawford. Non-Terminal DNS Name Redirection. August 1999.

+<a name="id2603783"></a>[<abbr class="abbrev">RFC2672</abbr>] M. Crawford. Non-Terminal DNS Name Redirection. August 1999.

</div>

-<a name="id2600268"></a>[<abbr class="abbrev">RFC2845</abbr>] P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington. Secret Key Transaction Authentication for <acronym class="acronym">DNS</acronym> (TSIG). May 2000.

+<a name="id2603810"></a>[<abbr class="abbrev">RFC2845</abbr>] P. Vixie, O. Gudmundsson, D. Eastlake, 3rd, and B. Wellington. Secret Key Transaction Authentication for <acronym class="acronym">DNS</acronym> (TSIG). May 2000.

</div>

-<a name="id2600330"></a>[<abbr class="abbrev">RFC2930</abbr>] D. Eastlake, 3rd. Secret Key Establishment for DNS (TKEY RR). September 2000.

+<a name="id2603872"></a>[<abbr class="abbrev">RFC2930</abbr>] D. Eastlake, 3rd. Secret Key Establishment for DNS (TKEY RR). September 2000.

</div>

-<a name="id2600360"></a>[<abbr class="abbrev">RFC2931</abbr>] D. Eastlake, 3rd. DNS Request and Transaction Signatures (SIG(0)s). September 2000.

+<a name="id2603901"></a>[<abbr class="abbrev">RFC2931</abbr>] D. Eastlake, 3rd. DNS Request and Transaction Signatures (SIG(0)s). September 2000.

</div>

-<a name="id2600390"></a>[<abbr class="abbrev">RFC3007</abbr>] B. Wellington. Secure Domain Name System (DNS) Dynamic Update. November 2000.

+<a name="id2603931"></a>[<abbr class="abbrev">RFC3007</abbr>] B. Wellington. Secure Domain Name System (DNS) Dynamic Update. November 2000.

</div>

-<a name="id2600417"></a>[<abbr class="abbrev">RFC3645</abbr>] S. Kwan, P. Garg, J. Gilroy, L. Esibov, J. Westhead, and R. Hall. Generic Security Service Algorithm for Secret

+<a name="id2603958"></a>[<abbr class="abbrev">RFC3645</abbr>] S. Kwan, P. Garg, J. Gilroy, L. Esibov, J. Westhead, and R. Hall. Generic Security Service Algorithm for Secret

Key Transaction Authentication for DNS

(GSS-TSIG). October 2003.

</div>

@@ -312,19 +322,19 @@

<acronym class="acronym">DNS</acronym> Security Proposed Standards</h3>

-<a name="id2600499"></a>[<abbr class="abbrev">RFC3225</abbr>] D. Conrad. Indicating Resolver Support of DNSSEC. December 2001.

+<a name="id2604040"></a>[<abbr class="abbrev">RFC3225</abbr>] D. Conrad. Indicating Resolver Support of DNSSEC. December 2001.

</div>

-<a name="id2600525"></a>[<abbr class="abbrev">RFC3833</abbr>] D. Atkins and R. Austein. Threat Analysis of the Domain Name System (DNS). August 2004.

+<a name="id2604067"></a>[<abbr class="abbrev">RFC3833</abbr>] D. Atkins and R. Austein. Threat Analysis of the Domain Name System (DNS). August 2004.

</div>

-<a name="id2600562"></a>[<abbr class="abbrev">RFC4033</abbr>] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. DNS Security Introduction and Requirements. March 2005.

+<a name="id2604103"></a>[<abbr class="abbrev">RFC4033</abbr>] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. DNS Security Introduction and Requirements. March 2005.

</div>

-<a name="id2600627"></a>[<abbr class="abbrev">RFC4034</abbr>] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Resource Records for the DNS Security Extensions. March 2005.

+<a name="id2604168"></a>[<abbr class="abbrev">RFC4034</abbr>] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Resource Records for the DNS Security Extensions. March 2005.

</div>

-<a name="id2600692"></a>[<abbr class="abbrev">RFC4035</abbr>] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Protocol Modifications for the DNS

+<a name="id2604233"></a>[<abbr class="abbrev">RFC4035</abbr>] R. Arends, R. Austein, M. Larson, D. Massey, and S. Rose. Protocol Modifications for the DNS

Security Extensions. March 2005.

</div>

@@ -332,146 +342,146 @@

<h3 class="title">Other Important RFCs About <acronym class="acronym">DNS</acronym>

Implementation</h3>

-<a name="id2600765"></a>[<abbr class="abbrev">RFC1535</abbr>] E. Gavron. A Security Problem and Proposed Correction With Widely

+<a name="id2604375"></a>[<abbr class="abbrev">RFC1535</abbr>] E. Gavron. A Security Problem and Proposed Correction With Widely

Deployed <acronym class="acronym">DNS</acronym> Software.. October 1993.

</div>

-<a name="id2600791"></a>[<abbr class="abbrev">RFC1536</abbr>] A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller. Common <acronym class="acronym">DNS</acronym> Implementation

+<a name="id2604401"></a>[<abbr class="abbrev">RFC1536</abbr>] A. Kumar, J. Postel, C. Neuman, P. Danzig, and S. Miller. Common <acronym class="acronym">DNS</acronym> Implementation

Errors and Suggested Fixes. October 1993.

</div>

-<a name="id2600859"></a>[<abbr class="abbrev">RFC1982</abbr>] R. Elz and R. Bush. Serial Number Arithmetic. August 1996.

+<a name="id2604469"></a>[<abbr class="abbrev">RFC1982</abbr>] R. Elz and R. Bush. Serial Number Arithmetic. August 1996.

</div>

-<a name="id2600894"></a>[<abbr class="abbrev">RFC4074</abbr>] Y. Morishita and T. Jinmei. Common Misbehaviour Against <acronym class="acronym">DNS</acronym>

+<a name="id2604504"></a>[<abbr class="abbrev">RFC4074</abbr>] Y. Morishita and T. Jinmei. Common Misbehaviour Against <acronym class="acronym">DNS</acronym>

Queries for IPv6 Addresses. May 2005.

</div>

<h3 class="title">Resource Record Types</h3>

-<a name="id2600940"></a>[<abbr class="abbrev">RFC1183</abbr>] C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris. New <acronym class="acronym">DNS</acronym> RR Definitions. October 1990.

+<a name="id2604550"></a>[<abbr class="abbrev">RFC1183</abbr>] C.F. Everhart, L. A. Mamakos, R. Ullmann, and P. Mockapetris. New <acronym class="acronym">DNS</acronym> RR Definitions. October 1990.

</div>

-<a name="id2600998"></a>[<abbr class="abbrev">RFC1706</abbr>] B. Manning and R. Colella. <acronym class="acronym">DNS</acronym> NSAP Resource Records. October 1994.

+<a name="id2604608"></a>[<abbr class="abbrev">RFC1706</abbr>] B. Manning and R. Colella. <acronym class="acronym">DNS</acronym> NSAP Resource Records. October 1994.

</div>

-<a name="id2601035"></a>[<abbr class="abbrev">RFC2168</abbr>] R. Daniel and M. Mealling. Resolution of Uniform Resource Identifiers using

+<a name="id2604645"></a>[<abbr class="abbrev">RFC2168</abbr>] R. Daniel and M. Mealling. Resolution of Uniform Resource Identifiers using

the Domain Name System. June 1997.

</div>

-<a name="id2601070"></a>[<abbr class="abbrev">RFC1876</abbr>] C. Davis, P. Vixie, T., and I. Dickinson. A Means for Expressing Location Information in the

+<a name="id2604680"></a>[<abbr class="abbrev">RFC1876</abbr>] C. Davis, P. Vixie, T., and I. Dickinson. A Means for Expressing Location Information in the

Domain

Name System. January 1996.

</div>

-<a name="id2601125"></a>[<abbr class="abbrev">RFC2052</abbr>] A. Gulbrandsen and P. Vixie. A <acronym class="acronym">DNS</acronym> RR for Specifying the

+<a name="id2604734"></a>[<abbr class="abbrev">RFC2052</abbr>] A. Gulbrandsen and P. Vixie. A <acronym class="acronym">DNS</acronym> RR for Specifying the

Location of

Services.. October 1996.

</div>

-<a name="id2601163"></a>[<abbr class="abbrev">RFC2163</abbr>] A. Allocchio. Using the Internet <acronym class="acronym">DNS</acronym> to

+<a name="id2604773"></a>[<abbr class="abbrev">RFC2163</abbr>] A. Allocchio. Using the Internet <acronym class="acronym">DNS</acronym> to

Distribute MIXER

Conformant Global Address Mapping. January 1998.

</div>

-<a name="id2601189"></a>[<abbr class="abbrev">RFC2230</abbr>] R. Atkinson. Key Exchange Delegation Record for the <acronym class="acronym">DNS</acronym>. October 1997.

+<a name="id2604798"></a>[<abbr class="abbrev">RFC2230</abbr>] R. Atkinson. Key Exchange Delegation Record for the <acronym class="acronym">DNS</acronym>. October 1997.

</div>

-<a name="id2601214"></a>[<abbr class="abbrev">RFC2536</abbr>] D. Eastlake, 3rd. DSA KEYs and SIGs in the Domain Name System (DNS). March 1999.

+<a name="id2604824"></a>[<abbr class="abbrev">RFC2536</abbr>] D. Eastlake, 3rd. DSA KEYs and SIGs in the Domain Name System (DNS). March 1999.

</div>

-<a name="id2601241"></a>[<abbr class="abbrev">RFC2537</abbr>] D. Eastlake, 3rd. RSA/MD5 KEYs and SIGs in the Domain Name System (DNS). March 1999.

+<a name="id2604851"></a>[<abbr class="abbrev">RFC2537</abbr>] D. Eastlake, 3rd. RSA/MD5 KEYs and SIGs in the Domain Name System (DNS). March 1999.

</div>

-<a name="id2601268"></a>[<abbr class="abbrev">RFC2538</abbr>] D. Eastlake, 3rd and O. Gudmundsson. Storing Certificates in the Domain Name System (DNS). March 1999.

+<a name="id2604877"></a>[<abbr class="abbrev">RFC2538</abbr>] D. Eastlake, 3rd and O. Gudmundsson. Storing Certificates in the Domain Name System (DNS). March 1999.

</div>

-<a name="id2601307"></a>[<abbr class="abbrev">RFC2539</abbr>] D. Eastlake, 3rd. Storage of Diffie-Hellman Keys in the Domain Name System (DNS). March 1999.

+<a name="id2604917"></a>[<abbr class="abbrev">RFC2539</abbr>] D. Eastlake, 3rd. Storage of Diffie-Hellman Keys in the Domain Name System (DNS). March 1999.

</div>

-<a name="id2601337"></a>[<abbr class="abbrev">RFC2540</abbr>] D. Eastlake, 3rd. Detached Domain Name System (DNS) Information. March 1999.

+<a name="id2604947"></a>[<abbr class="abbrev">RFC2540</abbr>] D. Eastlake, 3rd. Detached Domain Name System (DNS) Information. March 1999.

</div>

-<a name="id2601367"></a>[<abbr class="abbrev">RFC2782</abbr>] A. Gulbrandsen. P. Vixie. L. Esibov. A DNS RR for specifying the location of services (DNS SRV). February 2000.

+<a name="id2604977"></a>[<abbr class="abbrev">RFC2782</abbr>] A. Gulbrandsen. P. Vixie. L. Esibov. A DNS RR for specifying the location of services (DNS SRV). February 2000.

</div>

-<a name="id2601410"></a>[<abbr class="abbrev">RFC2915</abbr>] M. Mealling. R. Daniel. The Naming Authority Pointer (NAPTR) DNS Resource Record. September 2000.

+<a name="id2605019"></a>[<abbr class="abbrev">RFC2915</abbr>] M. Mealling. R. Daniel. The Naming Authority Pointer (NAPTR) DNS Resource Record. September 2000.

</div>

-<a name="id2601443"></a>[<abbr class="abbrev">RFC3110</abbr>] D. Eastlake, 3rd. RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS). May 2001.

+<a name="id2605052"></a>[<abbr class="abbrev">RFC3110</abbr>] D. Eastlake, 3rd. RSA/SHA-1 SIGs and RSA KEYs in the Domain Name System (DNS). May 2001.

</div>

-<a name="id2601469"></a>[<abbr class="abbrev">RFC3123</abbr>] P. Koch. A DNS RR Type for Lists of Address Prefixes (APL RR). June 2001.

+<a name="id2605079"></a>[<abbr class="abbrev">RFC3123</abbr>] P. Koch. A DNS RR Type for Lists of Address Prefixes (APL RR). June 2001.

</div>

-<a name="id2601493"></a>[<abbr class="abbrev">RFC3596</abbr>] S. Thomson, C. Huitema, V. Ksinant, and M. Souissi. <acronym class="acronym">DNS</acronym> Extensions to support IP

+<a name="id2605102"></a>[<abbr class="abbrev">RFC3596</abbr>] S. Thomson, C. Huitema, V. Ksinant, and M. Souissi. <acronym class="acronym">DNS</acronym> Extensions to support IP

version 6. October 2003.

</div>

-<a name="id2601619"></a>[<abbr class="abbrev">RFC3597</abbr>] A. Gustafsson. Handling of Unknown DNS Resource Record (RR) Types. September 2003.

+<a name="id2605160"></a>[<abbr class="abbrev">RFC3597</abbr>] A. Gustafsson. Handling of Unknown DNS Resource Record (RR) Types. September 2003.

</div>

<acronym class="acronym">DNS</acronym> and the Internet</h3>

-<a name="id2601651"></a>[<abbr class="abbrev">RFC1101</abbr>] P. V. Mockapetris. <acronym class="acronym">DNS</acronym> Encoding of Network Names

+<a name="id2605192"></a>[<abbr class="abbrev">RFC1101</abbr>] P. V. Mockapetris. <acronym class="acronym">DNS</acronym> Encoding of Network Names

and Other Types. April 1989.

</div>

-<a name="id2601676"></a>[<abbr class="abbrev">RFC1123</abbr>] Braden. Requirements for Internet Hosts - Application and

+<a name="id2605218"></a>[<abbr class="abbrev">RFC1123</abbr>] Braden. Requirements for Internet Hosts - Application and

Support. October 1989.

</div>

-<a name="id2601699"></a>[<abbr class="abbrev">RFC1591</abbr>] J. Postel. Domain Name System Structure and Delegation. March 1994.

+<a name="id2605240"></a>[<abbr class="abbrev">RFC1591</abbr>] J. Postel. Domain Name System Structure and Delegation. March 1994.

</div>

-<a name="id2601790"></a>[<abbr class="abbrev">RFC2317</abbr>] H. Eidnes, G. de Groot, and P. Vixie. Classless IN-ADDR.ARPA Delegation. March 1998.

+<a name="id2605264"></a>[<abbr class="abbrev">RFC2317</abbr>] H. Eidnes, G. de Groot, and P. Vixie. Classless IN-ADDR.ARPA Delegation. March 1998.

</div>

-<a name="id2601836"></a>[<abbr class="abbrev">RFC2826</abbr>] Internet Architecture Board. IAB Technical Comment on the Unique DNS Root. May 2000.

+<a name="id2605309"></a>[<abbr class="abbrev">RFC2826</abbr>] Internet Architecture Board. IAB Technical Comment on the Unique DNS Root. May 2000.

</div>

-<a name="id2601860"></a>[<abbr class="abbrev">RFC2929</abbr>] D. Eastlake, 3rd, E. Brunner-Williams, and B. Manning. Domain Name System (DNS) IANA Considerations. September 2000.

+<a name="id2605333"></a>[<abbr class="abbrev">RFC2929</abbr>] D. Eastlake, 3rd, E. Brunner-Williams, and B. Manning. Domain Name System (DNS) IANA Considerations. September 2000.

</div>

<acronym class="acronym">DNS</acronym> Operations</h3>

-<a name="id2601917"></a>[<abbr class="abbrev">RFC1033</abbr>] M. Lottor. Domain administrators operations guide.. November 1987.

+<a name="id2605390"></a>[<abbr class="abbrev">RFC1033</abbr>] M. Lottor. Domain administrators operations guide.. November 1987.

</div>

-<a name="id2601941"></a>[<abbr class="abbrev">RFC1537</abbr>] P. Beertema. Common <acronym class="acronym">DNS</acronym> Data File

+<a name="id2605414"></a>[<abbr class="abbrev">RFC1537</abbr>] P. Beertema. Common <acronym class="acronym">DNS</acronym> Data File

Configuration Errors. October 1993.

</div>

-<a name="id2601968"></a>[<abbr class="abbrev">RFC1912</abbr>] D. Barr. Common <acronym class="acronym">DNS</acronym> Operational and

+<a name="id2605441"></a>[<abbr class="abbrev">RFC1912</abbr>] D. Barr. Common <acronym class="acronym">DNS</acronym> Operational and

Configuration Errors. February 1996.

</div>

-<a name="id2601994"></a>[<abbr class="abbrev">RFC2010</abbr>] B. Manning and P. Vixie. Operational Criteria for Root Name Servers.. October 1996.

+<a name="id2605467"></a>[<abbr class="abbrev">RFC2010</abbr>] B. Manning and P. Vixie. Operational Criteria for Root Name Servers.. October 1996.

</div>

-<a name="id2602030"></a>[<abbr class="abbrev">RFC2219</abbr>] M. Hamilton and R. Wright. Use of <acronym class="acronym">DNS</acronym> Aliases for

+<a name="id2605504"></a>[<abbr class="abbrev">RFC2219</abbr>] M. Hamilton and R. Wright. Use of <acronym class="acronym">DNS</acronym> Aliases for

Network Services.. October 1997.

</div>

<h3 class="title">Internationalized Domain Names</h3>

-<a name="id2602076"></a>[<abbr class="abbrev">RFC2825</abbr>] IAB and R. Daigle. A Tangled Web: Issues of I18N, Domain Names,

+<a name="id2605549"></a>[<abbr class="abbrev">RFC2825</abbr>] IAB and R. Daigle. A Tangled Web: Issues of I18N, Domain Names,

and the Other Internet protocols. May 2000.

</div>

-<a name="id2602108"></a>[<abbr class="abbrev">RFC3490</abbr>] P. Faltstrom, P. Hoffman, and A. Costello. Internationalizing Domain Names in Applications (IDNA). March 2003.

+<a name="id2605581"></a>[<abbr class="abbrev">RFC3490</abbr>] P. Faltstrom, P. Hoffman, and A. Costello. Internationalizing Domain Names in Applications (IDNA). March 2003.

</div>

-<a name="id2602154"></a>[<abbr class="abbrev">RFC3491</abbr>] P. Hoffman and M. Blanchet. Nameprep: A Stringprep Profile for Internationalized Domain Names. March 2003.

+<a name="id2605627"></a>[<abbr class="abbrev">RFC3491</abbr>] P. Hoffman and M. Blanchet. Nameprep: A Stringprep Profile for Internationalized Domain Names. March 2003.

</div>

-<a name="id2602189"></a>[<abbr class="abbrev">RFC3492</abbr>] A. Costello. Punycode: A Bootstring encoding of Unicode

+<a name="id2605662"></a>[<abbr class="abbrev">RFC3492</abbr>] A. Costello. Punycode: A Bootstring encoding of Unicode

for Internationalized Domain Names in

Applications (IDNA). March 2003.

</div>

@@ -487,47 +497,47 @@

</div>

-<a name="id2602234"></a>[<abbr class="abbrev">RFC1464</abbr>] R. Rosenbaum. Using the Domain Name System To Store Arbitrary String

+<a name="id2605707"></a>[<abbr class="abbrev">RFC1464</abbr>] R. Rosenbaum. Using the Domain Name System To Store Arbitrary String

Attributes. May 1993.

</div>

-<a name="id2602257"></a>[<abbr class="abbrev">RFC1713</abbr>] A. Romao. Tools for <acronym class="acronym">DNS</acronym> Debugging. November 1994.

+<a name="id2605730"></a>[<abbr class="abbrev">RFC1713</abbr>] A. Romao. Tools for <acronym class="acronym">DNS</acronym> Debugging. November 1994.

</div>

-<a name="id2602282"></a>[<abbr class="abbrev">RFC1794</abbr>] T. Brisco. <acronym class="acronym">DNS</acronym> Support for Load

+<a name="id2605755"></a>[<abbr class="abbrev">RFC1794</abbr>] T. Brisco. <acronym class="acronym">DNS</acronym> Support for Load

Balancing. April 1995.

</div>

-<a name="id2602308"></a>[<abbr class="abbrev">RFC2240</abbr>] O. Vaughan. A Legal Basis for Domain Name Allocation. November 1997.

+<a name="id2605781"></a>[<abbr class="abbrev">RFC2240</abbr>] O. Vaughan. A Legal Basis for Domain Name Allocation. November 1997.

</div>

-<a name="id2602331"></a>[<abbr class="abbrev">RFC2345</abbr>] J. Klensin, T. Wolf, and G. Oglesby. Domain Names and Company Name Retrieval. May 1998.

+<a name="id2605804"></a>[<abbr class="abbrev">RFC2345</abbr>] J. Klensin, T. Wolf, and G. Oglesby. Domain Names and Company Name Retrieval. May 1998.

</div>

-<a name="id2602377"></a>[<abbr class="abbrev">RFC2352</abbr>] O. Vaughan. A Convention For Using Legal Names as Domain Names. May 1998.

+<a name="id2605850"></a>[<abbr class="abbrev">RFC2352</abbr>] O. Vaughan. A Convention For Using Legal Names as Domain Names. May 1998.

</div>

-<a name="id2602401"></a>[<abbr class="abbrev">RFC3071</abbr>] J. Klensin. Reflections on the DNS, RFC 1591, and Categories of Domains. February 2001.

+<a name="id2605874"></a>[<abbr class="abbrev">RFC3071</abbr>] J. Klensin. Reflections on the DNS, RFC 1591, and Categories of Domains. February 2001.

</div>

-<a name="id2602427"></a>[<abbr class="abbrev">RFC3258</abbr>] T. Hardie. Distributing Authoritative Name Servers via

+<a name="id2605900"></a>[<abbr class="abbrev">RFC3258</abbr>] T. Hardie. Distributing Authoritative Name Servers via

Shared Unicast Addresses. April 2002.

</div>

-<a name="id2602453"></a>[<abbr class="abbrev">RFC3901</abbr>] A. Durand and J. Ihren. DNS IPv6 Transport Operational Guidelines. September 2004.

+<a name="id2605926"></a>[<abbr class="abbrev">RFC3901</abbr>] A. Durand and J. Ihren. DNS IPv6 Transport Operational Guidelines. September 2004.

</div>

<h3 class="title">Obsolete and Unimplemented Experimental RFC</h3>

-<a name="id2602497"></a>[<abbr class="abbrev">RFC1712</abbr>] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni. <acronym class="acronym">DNS</acronym> Encoding of Geographical

+<a name="id2605970"></a>[<abbr class="abbrev">RFC1712</abbr>] C. Farrell, M. Schulze, S. Pleitner, and D. Baldoni. <acronym class="acronym">DNS</acronym> Encoding of Geographical

Location. November 1994.

</div>

-<a name="id2602554"></a>[<abbr class="abbrev">RFC2673</abbr>] M. Crawford. Binary Labels in the Domain Name System. August 1999.

+<a name="id2606027"></a>[<abbr class="abbrev">RFC2673</abbr>] M. Crawford. Binary Labels in the Domain Name System. August 1999.

</div>

-<a name="id2602581"></a>[<abbr class="abbrev">RFC2874</abbr>] M. Crawford and C. Huitema. DNS Extensions to Support IPv6 Address Aggregation

+<a name="id2606054"></a>[<abbr class="abbrev">RFC2874</abbr>] M. Crawford and C. Huitema. DNS Extensions to Support IPv6 Address Aggregation

and Renumbering. July 2000.

</div>

@@ -541,39 +551,39 @@

</div>

-<a name="id2602629"></a>[<abbr class="abbrev">RFC2065</abbr>] D. Eastlake, 3rd and C. Kaufman. Domain Name System Security Extensions. January 1997.

+<a name="id2606102"></a>[<abbr class="abbrev">RFC2065</abbr>] D. Eastlake, 3rd and C. Kaufman. Domain Name System Security Extensions. January 1997.

</div>

-<a name="id2602737"></a>[<abbr class="abbrev">RFC2137</abbr>] D. Eastlake, 3rd. Secure Domain Name System Dynamic Update. April 1997.

+<a name="id2606141"></a>[<abbr class="abbrev">RFC2137</abbr>] D. Eastlake, 3rd. Secure Domain Name System Dynamic Update. April 1997.

</div>

-<a name="id2602763"></a>[<abbr class="abbrev">RFC2535</abbr>] D. Eastlake, 3rd. Domain Name System Security Extensions. March 1999.

+<a name="id2606168"></a>[<abbr class="abbrev">RFC2535</abbr>] D. Eastlake, 3rd. Domain Name System Security Extensions. March 1999.

</div>

-<a name="id2602793"></a>[<abbr class="abbrev">RFC3008</abbr>] B. Wellington. Domain Name System Security (DNSSEC)

+<a name="id2606198"></a>[<abbr class="abbrev">RFC3008</abbr>] B. Wellington. Domain Name System Security (DNSSEC)

Signing Authority. November 2000.

</div>

-<a name="id2602819"></a>[<abbr class="abbrev">RFC3090</abbr>] E. Lewis. DNS Security Extension Clarification on Zone Status. March 2001.

+<a name="id2606224"></a>[<abbr class="abbrev">RFC3090</abbr>] E. Lewis. DNS Security Extension Clarification on Zone Status. March 2001.

</div>

-<a name="id2602845"></a>[<abbr class="abbrev">RFC3445</abbr>] D. Massey and S. Rose. Limiting the Scope of the KEY Resource Record (RR). December 2002.

+<a name="id2606250"></a>[<abbr class="abbrev">RFC3445</abbr>] D. Massey and S. Rose. Limiting the Scope of the KEY Resource Record (RR). December 2002.

</div>

-<a name="id2602950"></a>[<abbr class="abbrev">RFC3655</abbr>] B. Wellington and O. Gudmundsson. Redefinition of DNS Authenticated Data (AD) bit. November 2003.

+<a name="id2606286"></a>[<abbr class="abbrev">RFC3655</abbr>] B. Wellington and O. Gudmundsson. Redefinition of DNS Authenticated Data (AD) bit. November 2003.

</div>

-<a name="id2602986"></a>[<abbr class="abbrev">RFC3658</abbr>] O. Gudmundsson. Delegation Signer (DS) Resource Record (RR). December 2003.

+<a name="id2606323"></a>[<abbr class="abbrev">RFC3658</abbr>] O. Gudmundsson. Delegation Signer (DS) Resource Record (RR). December 2003.

</div>

-<a name="id2603013"></a>[<abbr class="abbrev">RFC3755</abbr>] S. Weiler. Legacy Resolver Compatibility for Delegation Signer (DS). May 2004.

+<a name="id2606349"></a>[<abbr class="abbrev">RFC3755</abbr>] S. Weiler. Legacy Resolver Compatibility for Delegation Signer (DS). May 2004.

</div>

-<a name="id2603040"></a>[<abbr class="abbrev">RFC3757</abbr>] O. Kolkman, J. Schlyter, and E. Lewis. Domain Name System KEY (DNSKEY) Resource Record

+<a name="id2606376"></a>[<abbr class="abbrev">RFC3757</abbr>] O. Kolkman, J. Schlyter, and E. Lewis. Domain Name System KEY (DNSKEY) Resource Record

(RR) Secure Entry Point (SEP) Flag. April 2004.

</div>

-<a name="id2603084"></a>[<abbr class="abbrev">RFC3845</abbr>] J. Schlyter. DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. August 2004.

+<a name="id2606421"></a>[<abbr class="abbrev">RFC3845</abbr>] J. Schlyter. DNS Security (DNSSEC) NextSECure (NSEC) RDATA Format. August 2004.

</div>

@@ -594,16 +604,481 @@

</div>

-<a name="id2603126"></a>Other Documents About <acronym class="acronym">BIND</acronym>

+<a name="id2606462"></a>Other Documents About <acronym class="acronym">BIND</acronym>

</h3></div></div></div>

-<a name="id2603136"></a>Bibliography</h4></div></div></div>

+<a name="id2606472"></a>Bibliography</h4></div></div></div>

-<a name="id2603138"></a>Paul Albitz and Cricket Liu. <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym>. Copyright � 1998 Sebastopol, CA: O'Reilly and Associates.

+<a name="id2606474"></a>Paul Albitz and Cricket Liu. <acronym class="acronym">DNS</acronym> and <acronym class="acronym">BIND</acronym>. Copyright � 1998 Sebastopol, CA: O'Reilly and Associates.

+</div>

+<div class="sect1" lang="en">

+<div class="titlepage"><div><div><h2 class="title" style="clear: both">

+<a name="bind9.library"></a>BIND 9 DNS Library Support</h2></div></div></div>

+This version of BIND 9 "exports" its internal libraries so

+ that they can be used by third-party applications more easily (we

+ call them "export" libraries in this document). In addition to

+ all major DNS-related APIs BIND 9 is currently using, the export

+ libraries provide the following features:

+<div class="itemizedlist"><ul type="disc">

+<li>The newly created "DNS client" module. This is a higher

+ level API that provides an interface to name resolution,

+ single DNS transaction with a particular server, and dynamic

+ update. Regarding name resolution, it supports advanced

+ features such as DNSSEC validation and caching. This module

+ supports both synchronous and asynchronous mode.</li>

+<li>The new "IRS" (Information Retrieval System) library.

+ It provides an interface to parse the traditional resolv.conf

+ file and more advanced, DNS-specific configuration file for

+ the rest of this package (see the description for the

+ dns.conf file below).</li>

+<li>As part of the IRS library, newly implemented standard

+ address-name mapping functions, getaddrinfo() and

+ getnameinfo(), are provided. They use the DNSSEC-aware

+ validating resolver backend, and could use other advanced

+ features of the BIND 9 libraries such as caching. The

+ getaddrinfo() function resolves both A and AAAA RRs

+ concurrently (when the address family is unspecified).</li>

+<li>An experimental framework to support other event

+ libraries than BIND 9's internal event task system.</li>

+</ul></div>

+<div class="sect2" lang="en">

+<div class="titlepage"><div><div><h3 class="title">

+<a name="id2608789"></a>Prerequisite</h3></div></div></div>

+GNU make is required to build the export libraries (other

+ part of BIND 9 can still be built with other types of make). In

+ the reminder of this document, "make" means GNU make. Note that

+ in some platforms you may need to invoke a different command name

+ than "make" (e.g. "gmake") to indicate it's GNU make.

+</div>

+<div class="sect2" lang="en">

+<div class="titlepage"><div><div><h3 class="title">

+<a name="id2608798"></a>Compilation</h3></div></div></div>

+<pre class="screen">

+$ <code>./configure --enable-exportlib <code>[other flags]</code></code>

+$ <code>make</code>

+</pre>

+

+ This will create (in addition to usual BIND 9 programs) and a

+ separate set of libraries under the lib/export directory. For

+ example, <code class="filename">lib/export/dns/libdns.a</code> is the archive file of the

+ export version of the BIND 9 DNS library. Sample application

+ programs using the libraries will also be built under the

+ lib/export/samples directory (see below).

+</div>

+<div class="sect2" lang="en">

+<div class="titlepage"><div><div><h3 class="title">

+<a name="id2608004"></a>Installation</h3></div></div></div>

+<pre class="screen">

+$ <code>cd lib/export</code>

+$ <code>make install</code>

+</pre>

+

+ This will install library object files under the directory

+ specified by the --with-export-libdir configure option (default:

+ EPREFIX/lib/bind9), and header files under the directory

+ specified by the --with-export-includedir configure option

+ (default: PREFIX/include/bind9).

+ Root privilege is normally required.

+ "make install" at the top directory will do the

+ same.

+

+

+ To see how to build your own

+ application after the installation, see

+ <code class="filename">lib/export/samples/Makefile-postinstall.in</code>.

+</div>

+<div class="sect2" lang="en">

+<div class="titlepage"><div><div><h3 class="title">

+<a name="id2608035"></a>Known Defects/Restrictions</h3></div></div></div>

+<div class="itemizedlist"><ul type="disc">

+<li>Currently, win32 is not supported for the export

+ library. (Normal BIND 9 application can be built as

+ before).</li>

+<li>

+The "fixed" RRset order is not (currently) supported in

+ the export library. If you want to use "fixed" RRset order

+ for, e.g. named while still building the

+ export library even without the fixed order support, build

+ them separately:

+

+<pre class="screen">

+$ <code>./configure --enable-fixed-rrset <code>[other flags, but not --enable-exportlib]</code></code>

+$ <code>make</code>

+$ <code>./configure --enable-exportlib <code>[other flags, but not --enable-fixed-rrset]</code></code>

+$ <code>cd lib/export</code>

+$ <code>make</code>

+</pre>

+

+

+</li>

+<li>The client module and the IRS library currently do not

+ support DNSSEC validation using DLV (the underlying modules

+ can handle it, but there is no tunable interface to enable

+ the feature).</li>

+<li>RFC 5011 is not supported in the validating stub

+ resolver of the export library. In fact, it is not clear

+ whether it should: trust anchors would be a system-wide

+ configuration which would be managed by an administrator,

+ while the stub resolver will be used by ordinary applications

+ run by a normal user.</li>

+<li>Not all common <code class="filename">/etc/resolv.conf</code>

+ options are supported

+ in the IRS library. The only available options in this

+ version are "debug" and "ndots".</li>

+</ul></div>

+</div>

+<div class="sect2" lang="en">

+<div class="titlepage"><div><div><h3 class="title">

+<a name="id2608112"></a>The dns.conf File</h3></div></div></div>

+The IRS library supports an "advanced" configuration file

+ related to the DNS library for configuration parameters that

+ would be beyond the capability of the

+ <code class="filename">resolv.conf</code> file.

+ Specifically, it is intended to provide DNSSEC related

+ configuration parameters. By default the path to this

+ configuration file is <code class="filename">/etc/dns.conf</code>.

+ This module is very

+ experimental and the configuration syntax or library interfaces

+ may change in future versions. Currently, only the

+ trusted-keys

+ statement is supported, whose syntax is the same as the same name

+ of statement for <code class="filename">named.conf</code>. (See

+ <a href="Bv9ARM.ch06.html#trusted-keys" title="trusted-keys Statement Grammar">the section called “trusted-keys Statement Grammar”</a> for details.)

+</div>

+<div class="sect2" lang="en">

+<div class="titlepage"><div><div><h3 class="title">

+<a name="id2608138"></a>Sample Applications</h3></div></div></div>

+Some sample application programs using this API are

+ provided for reference. The following is a brief description of

+ these applications.

+

+<div class="sect3" lang="en">

+<div class="titlepage"><div><div><h4 class="title">

+<a name="id2608147"></a>sample: a simple stub resolver utility</h4></div></div></div>

+

+ It sends a query of a given name (of a given optional RR type) to a

+ specified recursive server, and prints the result as a list of

+ RRs. It can also act as a validating stub resolver if a trust

+ anchor is given via a set of command line options.

+

+ Usage: sample [options] server_address hostname

+

+

+ Options and Arguments:

+

+<div class="variablelist"><dl>

+<dt>

+ -t RRtype

+ </dt>

+<dd>

+ specify the RR type of the query. The default is the A RR.

+ </dd>

+<dt>

+ [-a algorithm] [-e] -k keyname -K keystring

+ </dt>

+<dd>

+

+ specify a command-line DNS key to validate the answer. For

+ example, to specify the following DNSKEY of example.com:

+

+<div class="literallayout">

+��example.com.�3600�IN�DNSKEY�257�3�5�xxx

+</div>

+

+ specify the options as follows:

+

+<pre class="screen">

+<code>

+ -e -k example.com -K "xxx"

+</code>

+</pre>

+

+ -e means that this key is a zone's "key signing key" (as known

+ as "secure Entry point").

+ When -a is omitted rsasha1 will be used by default.

+

+</dd>

+<dt>

+ -s domain:alt_server_address

+ </dt>

+<dd>

+ specify a separate recursive server address for the specific

+ "domain". Example: -s example.com:2001:db8::1234

+ </dd>

+<dt>server_address</dt>

+<dd>

+ an IP(v4/v6) address of the recursive server to which queries

+ are sent.

+ </dd>

+<dt>hostname</dt>

+<dd>

+ the domain name for the query

+ </dd>

+</dl></div>

+</div>

+<div class="sect3" lang="en">

+<div class="titlepage"><div><div><h4 class="title">

+<a name="id2608237"></a>sample-async: a simple stub resolver, working asynchronously</h4></div></div></div>

+

+ Similar to "sample", but accepts a list

+ of (query) domain names as a separate file and resolves the names

+ asynchronously.

+

+ Usage: sample-async [-s server_address] [-t RR_type] input_file

+

+ Options and Arguments:

+

+<div class="variablelist"><dl>

+<dt>

+ -s server_address

+ </dt>

+<dd>

+ an IPv4 address of the recursive server to which queries are sent.

+ (IPv6 addresses are not supported in this implementation)

+ </dd>

+<dt>

+ -t RR_type

+ </dt>

+<dd>

+ specify the RR type of the queries. The default is the A

+ RR.

+ </dd>

+<dt>

+ input_file

+ </dt>

+<dd>

+ a list of domain names to be resolved. each line

+ consists of a single domain name. Example:

+ <div class="literallayout">

+��www.example.com

+��mx.examle.net

+��ns.xxx.example

+</div>

+</dd>

+</dl></div>

+</div>

+<div class="sect3" lang="en">

+<div class="titlepage"><div><div><h4 class="title">

+<a name="id2608291"></a>sample-request: a simple DNS transaction client</h4></div></div></div>

+

+ It sends a query to a specified server, and

+ prints the response with minimal processing. It doesn't act as a

+ "stub resolver": it stops the processing once it gets any

+ response from the server, whether it's a referral or an alias

+ (CNAME or DNAME) that would require further queries to get the

+ ultimate answer. In other words, this utility acts as a very

+ simplified dig.

+

+

+ Usage: sample-request [-t RRtype] server_address hostname

+

+

+ Options and Arguments:

+

+<div class="variablelist"><dl>

+<dt>

+ -t RRtype

+ </dt>

+<dd>

+ specify the RR type of

+ the queries. The default is the A RR.

+ </dd>

+<dt>

+ server_address

+ </dt>

+<dd>

+ an IP(v4/v6)

+ address of the recursive server to which the query is sent.

+ </dd>

+<dt>

+ hostname

+ </dt>

+<dd>

+ the domain name for the query

+ </dd>

+</dl></div>

+</div>

+<div class="sect3" lang="en">

+<div class="titlepage"><div><div><h4 class="title">

+<a name="id2608355"></a>sample-gai: getaddrinfo() and getnameinfo() test code</h4></div></div></div>

+

+ This is a test program

+ to check getaddrinfo() and getnameinfo() behavior. It takes a

+ host name as an argument, calls getaddrinfo() with the given host

+ name, and calls getnameinfo() with the resulting IP addresses

+ returned by getaddrinfo(). If the dns.conf file exists and

+ defines a trust anchor, the underlying resolver will act as a

+ validating resolver, and getaddrinfo()/getnameinfo() will fail

+ with an EAI_INSECUREDATA error when DNSSEC validation fails.

+

+

+ Usage: sample-gai hostname

+

+</div>

+<div class="sect3" lang="en">

+<div class="titlepage"><div><div><h4 class="title">

+<a name="id2608370"></a>sample-update: a simple dynamic update client program</h4></div></div></div>

+

+ It accepts a single update command as a

+ command-line argument, sends an update request message to the

+ authoritative server, and shows the response from the server. In

+ other words, this is a simplified nsupdate.

+

+

+ Usage: sample-update [options] (add|delete) "update data"

+

+

+ Options and Arguments:

+

+<div class="variablelist"><dl>

+<dt>

+ -a auth_server

+ </dt>

+<dd>

+ An IP address of the authoritative server that has authority

+ for the zone containing the update name. This should normally

+ be the primary authoritative server that accepts dynamic

+ updates. It can also be a secondary server that is configured

+ to forward update requests to the primary server.

+ </dd>

+<dt>

+ -k keyfile

+ </dt>

+<dd>

+ A TSIG key file to secure the update transaction. The keyfile

+ format is the same as that for the nsupdate utility.

+ </dd>

+<dt>

+ -p prerequisite

+ </dt>

+<dd>

+ A prerequisite for the update (only one prerequisite can be

+ specified). The prerequisite format is the same as that is

+ accepted by the nsupdate utility.

+ </dd>

+<dt>

+ -r recursive_server

+ </dt>

+<dd>

+ An IP address of a recursive server that this utility will

+ use. A recursive server may be necessary to identify the

+ authoritative server address to which the update request is

+ sent.

+ </dd>

+<dt>

+ -z zonename

+ </dt>

+<dd>

+ The domain name of the zone that contains

+ </dd>

+<dt>

+ (add|delete)

+ </dt>

+<dd>

+ Specify the type of update operation. Either "add" or "delete"

+ must be specified.

+ </dd>

+<dt>

+ "update data"

+ </dt>

+<dd>

+ Specify the data to be updated. A typical example of the data

+ would look like "name TTL RRtype RDATA".

+ </dd>

+</dl></div>

+<div class="note" style="margin-left: 0.5in; margin-right: 0.5in;">

+<h3 class="title">Note</h3>In practice, either -a or -r must be specified. Others can

+ be optional; the underlying library routine tries to identify the

+ appropriate server and the zone name for the update.</div>

+

+ Examples: assuming the primary authoritative server of the

+ dynamic.example.com zone has an IPv6 address 2001:db8::1234,

+

+<pre class="screen">

+$ <code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key add "foo.dynamic.example.com 30 IN A 192.168.2.1"</code></pre>

+

+ adds an A RR for foo.dynamic.example.com using the given key.

+

+<pre class="screen">

+$ <code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com 30 IN A"</code></pre>

+

+ removes all A RRs for foo.dynamic.example.com using the given key.

+

+<pre class="screen">

+$ <code>sample-update -a sample-update -k Kxxx.+nnn+mmmm.key delete "foo.dynamic.example.com"</code></pre>

+

+ removes all RRs for foo.dynamic.example.com using the given key.

+

+</div>

+<div class="sect3" lang="en">

+<div class="titlepage"><div><div><h4 class="title">

+<a name="id2609047"></a>nsprobe: domain/name server checker in terms of RFC 4074</h4></div></div></div>

+

+ It checks a set

+ of domains to see the name servers of the domains behave

+ correctly in terms of RFC 4074. This is included in the set of

+ sample programs to show how the export library can be used in a

+ DNS-related application.

+

+

+ Usage: nsprobe [-d] [-v [-v...]] [-c cache_address] [input_file]

+

+

+ Options

+

+<div class="variablelist"><dl>

+<dt>

+ -d

+ </dt>

+<dd>

+ run in the "debug" mode. with this option nsprobe will dump

+ every RRs it receives.

+ </dd>

+<dt>

+ -v

+ </dt>

+<dd>

+ increase verbosity of other normal log messages. This can be

+ specified multiple times

+ </dd>

+<dt>

+ -c cache_address

+ </dt>

+<dd>

+ specify an IP address of a recursive (caching) name server.

+ nsprobe uses this server to get the NS RRset of each domain and

+ the A and/or AAAA RRsets for the name servers. The default

+ value is 127.0.0.1.

+ </dd>

+<dt>

+ input_file

+ </dt>

+<dd>

+ a file name containing a list of domain (zone) names to be

+ probed. when omitted the standard input will be used. Each

+ line of the input file specifies a single domain name such as

+ "example.com". In general this domain name must be the apex

+ name of some DNS zone (unlike normal "host names" such as

+ "www.example.com"). nsprobe first identifies the NS RRsets for

+ the given domain name, and sends A and AAAA queries to these

+ servers for some "widely used" names under the zone;

+ specifically, adding "www" and "ftp" to the zone name.

+ </dd>

+</dl></div>

</div>

+<div class="sect2" lang="en">

+<div class="titlepage"><div><div><h3 class="title">

+<a name="id2609111"></a>Library References</h3></div></div></div>

+As of this writing, there is no formal "manual" of the

+ libraries, except this document, header files (some of them

+ provide pretty detailed explanations), and sample application

+ programs.

</div>