diff options
Diffstat (limited to 'usr.sbin/bind/doc/arm')
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch01.html | 297 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Bv9ARM.ch02.html | 129 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/Makefile.in | 19 | ||||
| -rw-r--r-- | usr.sbin/bind/doc/arm/README-SGML | 3 |
4 files changed, 186 insertions, 262 deletions
diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch01.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch01.html index ab899fa0919..5b3659e6101 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch01.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch01.html @@ -1,11 +1,11 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >Introduction </TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.73 -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="BIND 9 Administrator Reference Manual" HREF="Bv9ARM.html"><LINK @@ -70,8 +70,8 @@ CLASS="chapter" ><H1 ><A NAME="ch01" ->Chapter 1. Introduction </A -></H1 +></A +>Chapter 1. Introduction </H1 ><DIV CLASS="TOC" ><DL @@ -81,40 +81,40 @@ CLASS="TOC" ></DT ><DT >1.1. <A -HREF="Bv9ARM.ch01.html#AEN13" +HREF="Bv9ARM.ch01.html#AEN15" >Scope of Document</A ></DT ><DT >1.2. <A -HREF="Bv9ARM.ch01.html#AEN20" +HREF="Bv9ARM.ch01.html#AEN22" >Organization of This Document</A ></DT ><DT >1.3. <A -HREF="Bv9ARM.ch01.html#AEN40" +HREF="Bv9ARM.ch01.html#AEN42" >Conventions Used in This Document</A ></DT ><DT >1.4. <A -HREF="Bv9ARM.ch01.html#AEN105" ->The Domain Name System (<SPAN +HREF="Bv9ARM.ch01.html#AEN107" +>The Domain Name System (<ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM >)</A ></DT ></DL ></DIV ><P ->The Internet Domain Name System (<SPAN +>The Internet Domain Name System (<ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM >) consists of the syntax to specify the names of entities in the Internet in a hierarchical manner, the rules used for delegating authority over names, and the system implementation that actually maps names to Internet - addresses. <SPAN + addresses. <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > data is maintained in a group of distributed hierarchical databases.</P ><DIV @@ -122,34 +122,34 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN13" +NAME="AEN15" >1.1. Scope of Document</A ></H1 ><P ->The Berkeley Internet Name Domain (<SPAN +>The Berkeley Internet Name Domain (<ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM >) implements an domain name server for a number of operating systems. This document provides basic information about the installation and - care of the Internet Software Consortium (<SPAN + care of the Internet Software Consortium (<ACRONYM CLASS="acronym" ->ISC</SPAN +>ISC</ACRONYM >) - <SPAN + <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > version 9 software package for system administrators.</P ><P ->This version of the manual corresponds to BIND version 9.2.</P +>This version of the manual corresponds to BIND version 9.3.</P ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN20" +NAME="AEN22" >1.2. Organization of This Document</A ></H1 ><P @@ -160,12 +160,12 @@ CLASS="emphasis" >Section 1</I ></SPAN > introduces - the basic <SPAN + the basic <ACRONYM CLASS="acronym" ->DNS</SPAN -> and <SPAN +>DNS</ACRONYM +> and <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > concepts. <SPAN CLASS="emphasis" ><I @@ -173,9 +173,9 @@ CLASS="emphasis" >Section 2</I ></SPAN > - describes resource requirements for running <SPAN + describes resource requirements for running <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > in various environments. Information in <SPAN CLASS="emphasis" @@ -192,9 +192,9 @@ CLASS="emphasis" ></SPAN > in its presentation and is organized functionally, to aid in the process of installing the - <SPAN + <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > 9 software. The task-oriented section is followed by <SPAN CLASS="emphasis" @@ -211,9 +211,9 @@ CLASS="emphasis" >Section 5</I ></SPAN > - describes the <SPAN + describes the <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > 9 lightweight resolver. The contents of <SPAN CLASS="emphasis" @@ -253,9 +253,9 @@ CLASS="emphasis" >Bibliography</I ></SPAN > and - historic information related to <SPAN + historic information related to <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > and the Domain Name System.</P ></DIV @@ -264,7 +264,7 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN40" +NAME="AEN42" >1.3. Conventions Used in This Document</A ></H1 ><P @@ -272,11 +272,11 @@ NAME="AEN40" conventions:</P ><DIV CLASS="informaltable" -><A -NAME="AEN43" -></A ><P ></P +><A +NAME="AEN45" +></A ><TABLE CELLPADDING="3" BORDER="1" @@ -284,9 +284,6 @@ CLASS="CALSTABLE" ><TBODY ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" > <P ><SPAN CLASS="emphasis" @@ -298,9 +295,6 @@ describe:</I ></P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" > <P ><SPAN CLASS="emphasis" @@ -313,17 +307,11 @@ CLASS="emphasis" ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" > <P >a pathname, filename, URL, hostname, mailing list name, or new term or concept</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P ><TT CLASS="filename" @@ -333,42 +321,28 @@ CLASS="filename" ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >literal user input</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P -><TT +><KBD CLASS="userinput" -><B ->Fixed Width Bold</B -></TT +>Fixed Width Bold</KBD ></P ></TD ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >program output</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P -><TT +><SAMP CLASS="computeroutput" ->Fixed Width</TT +>Fixed Width</SAMP ></P ></TD ></TR @@ -379,16 +353,16 @@ CLASS="computeroutput" ></DIV ><P >The following conventions are used in descriptions of the -<SPAN +<ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > configuration file:<DIV CLASS="informaltable" -><A -NAME="AEN75" -></A ><P ></P +><A +NAME="AEN77" +></A ><TABLE CELLPADDING="3" BORDER="1" @@ -396,9 +370,6 @@ CLASS="CALSTABLE" ><TBODY ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P ><SPAN CLASS="emphasis" @@ -410,9 +381,6 @@ describe:</I ></P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P ><SPAN CLASS="emphasis" @@ -425,54 +393,36 @@ CLASS="emphasis" ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >keywords</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P -><TT +><VAR CLASS="literal" ->Fixed Width</TT +>Fixed Width</VAR ></P ></TD ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >variables</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P -><TT +><VAR CLASS="varname" ->Fixed Width</TT +>Fixed Width</VAR ></P ></TD ></TR ><TR ><TD -WIDTH="288" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >Optional input</P ></TD ><TD -WIDTH="252" -ALIGN="LEFT" -VALIGN="MIDDLE" ><P >[<SPAN CLASS="optional" @@ -492,25 +442,25 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN105" ->1.4. The Domain Name System (<SPAN +NAME="AEN107" +>1.4. The Domain Name System (<ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM >)</A ></H1 ><P >The purpose of this document is to explain the installation -and upkeep of the <SPAN +and upkeep of the <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > software package, and we begin by reviewing the fundamentals of the Domain Name System -(<SPAN +(<ACRONYM CLASS="acronym" ->DNS</SPAN ->) as they relate to <SPAN +>DNS</ACRONYM +>) as they relate to <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM >. </P ><DIV @@ -518,7 +468,7 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN112" +NAME="AEN114" >1.4.1. DNS Fundamentals</A ></H2 ><P @@ -542,18 +492,29 @@ CLASS="emphasis" >name servers</I ></SPAN > and interprets the responses. -The <SPAN +The <ACRONYM CLASS="acronym" ->BIND 9</SPAN -> software distribution contains both a -name server and a resolver library.</P +>BIND</ACRONYM +> 9 software distribution contains a +name server, <B +CLASS="command" +>named</B +>, and two resolver +libraries, <B +CLASS="command" +>liblwres</B +> and <B +CLASS="command" +>libbind</B +>. +</P ></DIV ><DIV CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN119" +NAME="AEN124" >1.4.2. Domains and Domain Names</A ></H2 ><P @@ -593,30 +554,30 @@ CLASS="emphasis" >Example, Inc.</I ></SPAN > could be -<TT +<VAR CLASS="literal" ->mail.example.com</TT +>mail.example.com</VAR >, -where <TT +where <VAR CLASS="literal" ->com</TT +>com</VAR > is the top level domain to which -<TT +<VAR CLASS="literal" ->ourhost.example.com</TT +>ourhost.example.com</VAR > belongs, -<TT +<VAR CLASS="literal" ->example</TT +>example</VAR > is -a subdomain of <TT +a subdomain of <VAR CLASS="literal" ->com</TT +>com</VAR >, and -<TT +<VAR CLASS="literal" ->ourhost</TT +>ourhost</VAR > is the name of the host.</P ><P @@ -653,9 +614,9 @@ CLASS="emphasis" CLASS="emphasis" >resource records</I ></SPAN -> (<SPAN +> (<ACRONYM CLASS="acronym" ->RR</SPAN +>RR</ACRONYM >s). Some of the supported resource record types are described in <A @@ -667,7 +628,7 @@ HREF="Bv9ARM.ch06.html#types_of_resource_records_and_when_to_use_them" the DNS protocol, please refer to the standards documents listed in <A HREF="Bv9ARM.ch09.html#rfcs" ->Section A.4.1</A +>Section A.3.1</A >.</P ></DIV ><DIV @@ -675,7 +636,7 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN143" +NAME="AEN148" >1.4.3. Zones</A ></H2 ><P @@ -696,12 +657,12 @@ CLASS="emphasis" >.</P ><P >As we stated previously, a zone is a point of delegation in -the <SPAN +the <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > tree. A zone consists of those contiguous parts of the domain -tree for which a a name server has complete information and over which +tree for which a name server has complete information and over which it has authority. It contains all domain names from a certain point downward in the domain tree except those which are delegated to other zones. A delegation point is marked by one or more @@ -715,36 +676,36 @@ CLASS="emphasis" parent zone, which should be matched by equivalent NS records at the root of the delegated zone.</P ><P ->For instance, consider the <TT +>For instance, consider the <VAR CLASS="literal" ->example.com</TT +>example.com</VAR > domain which includes names -such as <TT +such as <VAR CLASS="literal" ->host.aaa.example.com</TT +>host.aaa.example.com</VAR > and -<TT +<VAR CLASS="literal" ->host.bbb.example.com</TT +>host.bbb.example.com</VAR > even though -the <TT +the <VAR CLASS="literal" ->example.com</TT +>example.com</VAR > zone includes -only delegations for the <TT +only delegations for the <VAR CLASS="literal" ->aaa.example.com</TT +>aaa.example.com</VAR > and -<TT +<VAR CLASS="literal" ->bbb.example.com</TT +>bbb.example.com</VAR > zones. A zone can map exactly to a single domain, but could also include only part of a domain, the rest of which could be delegated to other -name servers. Every name in the <SPAN +name servers. Every name in the <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > tree is a <SPAN CLASS="emphasis" @@ -772,9 +733,9 @@ not intuitive and we suggest that you read RFCs 1033, 1034 and 1035 to gain a complete understanding of this difficult and subtle topic.</P ><P ->Though <SPAN +>Though <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > is called a "domain name server", it deals primarily in terms of zones. The master and slave declarations in the <TT @@ -796,7 +757,7 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN166" +NAME="AEN171" >1.4.4. Authoritative Name Servers</A ></H2 ><P @@ -821,14 +782,14 @@ CLASS="command" >dig</B > (<A HREF="Bv9ARM.ch03.html#diagnostic_tools" ->Section 3.4.1.1</A +>Section 3.3.1.1</A >).</P ><DIV CLASS="sect3" ><H3 CLASS="sect3" ><A -NAME="AEN173" +NAME="AEN178" >1.4.4.1. The Primary Master</A ></H3 ><P @@ -868,7 +829,7 @@ CLASS="sect3" ><H3 CLASS="sect3" ><A -NAME="AEN180" +NAME="AEN185" >1.4.4.2. Slave Servers</A ></H3 ><P @@ -903,7 +864,7 @@ CLASS="sect3" ><H3 CLASS="sect3" ><A -NAME="AEN186" +NAME="AEN191" >1.4.4.3. Stealth Servers</A ></H3 ><P @@ -960,7 +921,7 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN195" +NAME="AEN200" >1.4.5. Caching Name Servers</A ></H2 ><P @@ -1017,7 +978,7 @@ CLASS="sect3" ><H3 CLASS="sect3" ><A -NAME="AEN205" +NAME="AEN210" >1.4.5.1. Forwarding</A ></H3 ><P @@ -1045,14 +1006,14 @@ and they are queried in turn until the list is exhausted or an answer is found. Forwarders are typically used when you do not wish all the servers at a given site to interact directly with the rest of the Internet servers. A typical scenario would involve a number -of internal <SPAN +of internal <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > servers and an Internet firewall. Servers unable to pass packets through the firewall would forward to the server -that can do it, and that server would query the Internet <SPAN +that can do it, and that server would query the Internet <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > servers on the internal server's behalf. An added benefit of using the forwarding feature is that the central machine develops a much more complete @@ -1065,13 +1026,13 @@ CLASS="sect2" ><H2 CLASS="sect2" ><A -NAME="AEN213" +NAME="AEN218" >1.4.6. Name Servers in Multiple Roles</A ></H2 ><P ->The <SPAN +>The <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > name server can simultaneously act as a master for some zones, a slave for other zones, and as a caching (recursive) server for a set of local clients.</P @@ -1158,9 +1119,9 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" -><SPAN +><ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > Resource Requirements</TD ></TR ></TABLE diff --git a/usr.sbin/bind/doc/arm/Bv9ARM.ch02.html b/usr.sbin/bind/doc/arm/Bv9ARM.ch02.html index 2abd8a9ac15..0b293c7edfd 100644 --- a/usr.sbin/bind/doc/arm/Bv9ARM.ch02.html +++ b/usr.sbin/bind/doc/arm/Bv9ARM.ch02.html @@ -1,11 +1,11 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <HTML ><HEAD ><TITLE >BIND Resource Requirements</TITLE ><META NAME="GENERATOR" -CONTENT="Modular DocBook HTML Stylesheet Version 1.73 -"><LINK +CONTENT="Modular DocBook HTML Stylesheet Version 1.7"><LINK REL="HOME" TITLE="BIND 9 Administrator Reference Manual" HREF="Bv9ARM.html"><LINK @@ -13,7 +13,7 @@ REL="PREVIOUS" TITLE="Introduction " HREF="Bv9ARM.ch01.html"><LINK REL="NEXT" -TITLE="Nameserver Configuration" +TITLE="Name Server Configuration" HREF="Bv9ARM.ch03.html"></HEAD ><BODY CLASS="chapter" @@ -70,11 +70,11 @@ CLASS="chapter" ><H1 ><A NAME="ch02" ->Chapter 2. <SPAN +></A +>Chapter 2. <ACRONYM CLASS="acronym" ->BIND</SPAN -> Resource Requirements</A -></H1 +>BIND</ACRONYM +> Resource Requirements</H1 ><DIV CLASS="TOC" ><DL @@ -84,27 +84,27 @@ CLASS="TOC" ></DT ><DT >2.1. <A -HREF="Bv9ARM.ch02.html#AEN223" +HREF="Bv9ARM.ch02.html#AEN228" >Hardware requirements</A ></DT ><DT >2.2. <A -HREF="Bv9ARM.ch02.html#AEN231" +HREF="Bv9ARM.ch02.html#AEN236" >CPU Requirements</A ></DT ><DT >2.3. <A -HREF="Bv9ARM.ch02.html#AEN235" +HREF="Bv9ARM.ch02.html#AEN240" >Memory Requirements</A ></DT ><DT >2.4. <A -HREF="Bv9ARM.ch02.html#AEN240" ->Nameserver Intensive Environment Issues</A +HREF="Bv9ARM.ch02.html#AEN245" +>Name Server Intensive Environment Issues</A ></DT ><DT >2.5. <A -HREF="Bv9ARM.ch02.html#AEN243" +HREF="Bv9ARM.ch02.html#AEN248" >Supported Operating Systems</A ></DT ></DL @@ -114,30 +114,30 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN223" +NAME="AEN228" >2.1. Hardware requirements</A ></H1 ><P -><SPAN +><ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > hardware requirements have traditionally been quite modest. For many installations, servers that have been pensioned off from -active duty have performed admirably as <SPAN +active duty have performed admirably as <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > servers.</P ><P ->The DNSSEC and IPv6 features of <SPAN +>The DNSSEC and IPv6 features of <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > 9 may prove to be quite CPU intensive however, so organizations that make heavy use of these features may wish to consider larger systems for these applications. -<SPAN +<ACRONYM CLASS="acronym" ->BIND</SPAN -> 9 is now fully multithreaded, allowing full utilization of +>BIND</ACRONYM +> 9 is fully multithreaded, allowing full utilization of multiprocessor systems for installations that need it.</P ></DIV ><DIV @@ -145,13 +145,13 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN231" +NAME="AEN236" >2.2. CPU Requirements</A ></H1 ><P ->CPU requirements for <SPAN +>CPU requirements for <ACRONYM CLASS="acronym" ->BIND</SPAN +>BIND</ACRONYM > 9 range from i486-class machines for serving of static zones without caching, to enterprise-class machines if you intend to process many dynamic updates and DNSSEC @@ -162,7 +162,7 @@ CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN235" +NAME="AEN240" >2.3. Memory Requirements</A ></H1 ><P @@ -172,92 +172,53 @@ CLASS="command" >max-cache-size</B > option can be used to limit the amount of memory used by the cache, -at the expense of reducing cache hit rates and causing more <SPAN +at the expense of reducing cache hit rates and causing more <ACRONYM CLASS="acronym" ->DNS</SPAN +>DNS</ACRONYM > traffic. It is still good practice to have enough memory to load all zone and cache data into memory — unfortunately, the best way -to determine this for a given installation is to watch the nameserver +to determine this for a given installation is to watch the name server in operation. After a few weeks the server process should reach a relatively stable size where entries are expiring from the cache as -fast as they are being inserted. Ideally, the resource limits should -be set higher than this stable size.</P +fast as they are being inserted.</P ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN240" ->2.4. Nameserver Intensive Environment Issues</A +NAME="AEN245" +>2.4. Name Server Intensive Environment Issues</A ></H1 ><P ->For nameserver intensive environments, there are two alternative +>For name server intensive environments, there are two alternative configurations that may be used. The first is where clients and -any second-level internal nameservers query a main nameserver, which +any second-level internal name servers query a main name server, which has enough memory to build a large cache. This approach minimizes the bandwidth used by external name lookups. The second alternative -is to set up second-level internal nameservers to make queries independently. +is to set up second-level internal name servers to make queries independently. In this configuration, none of the individual machines needs to have as much memory or CPU power as in the first alternative, but this has the disadvantage of making many more external queries, -as none of the nameservers share their cached data.</P +as none of the name servers share their cached data.</P ></DIV ><DIV CLASS="sect1" ><H1 CLASS="sect1" ><A -NAME="AEN243" +NAME="AEN248" >2.5. Supported Operating Systems</A ></H1 ><P ->ISC <SPAN +>ISC <ACRONYM CLASS="acronym" ->BIND</SPAN -> 9 compiles and runs on the following operating -systems:</P -><P -></P -><UL -><LI -><P ->IBM AIX 4.3</P -></LI -><LI -><P ->Compaq Digital/Tru64 UNIX 4.0D</P -></LI -><LI -><P ->Compaq Digital/Tru64 UNIX 5 (with IPv6 EAK)</P -></LI -><LI -><P ->HP HP-UX 11</P -></LI -><LI -><P ->IRIX64 6.5</P -></LI -><LI -><P ->Sun Solaris 2.6, 7, 8</P -></LI -><LI -><P ->NetBSD 1.5 (with unproven-pthreads 0.17)</P -></LI -><LI -><P ->FreeBSD 3.4-STABLE, 3.5, 4.0, 4.1</P -></LI -><LI -><P ->Red Hat Linux 6.0, 6.1, 6.2, 7.0</P -></LI -></UL +>BIND</ACRONYM +> 9 compiles and runs on a large number +of Unix-like operating system and on Windows NT / 2000. For an up-to-date +list of supported systems, see the README file in the top level directory +of the BIND 9 source distribution.</P ></DIV ></DIV ><DIV @@ -314,7 +275,7 @@ VALIGN="top" WIDTH="33%" ALIGN="right" VALIGN="top" ->Nameserver Configuration</TD +>Name Server Configuration</TD ></TR ></TABLE ></DIV diff --git a/usr.sbin/bind/doc/arm/Makefile.in b/usr.sbin/bind/doc/arm/Makefile.in index ef8944dd0a5..b74245961e7 100644 --- a/usr.sbin/bind/doc/arm/Makefile.in +++ b/usr.sbin/bind/doc/arm/Makefile.in @@ -1,19 +1,19 @@ +# Copyright (C) 2004 Internet Systems Consortium, Inc. ("ISC") # Copyright (C) 2001, 2002 Internet Software Consortium. # # Permission to use, copy, modify, and distribute this software for any # purpose with or without fee is hereby granted, provided that the above # copyright notice and this permission notice appear in all copies. # -# THE SOFTWARE IS PROVIDED "AS IS" AND INTERNET SOFTWARE CONSORTIUM -# DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL -# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL -# INTERNET SOFTWARE CONSORTIUM BE LIABLE FOR ANY SPECIAL, DIRECT, -# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING -# FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, -# NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION -# WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. +# THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH +# REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY +# AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT, +# INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM +# LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE +# OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR +# PERFORMANCE OF THIS SOFTWARE. -# $ISC: Makefile.in,v 1.8.2.2 2002/02/12 06:05:51 marka Exp $ +# $ISC: Makefile.in,v 1.8.2.2.8.3 2004/03/08 09:04:24 marka Exp $ srcdir = @srcdir@ VPATH = @srcdir@ @@ -39,6 +39,7 @@ Bv9ARM.html: Bv9ARM-book.xml nominum-docbook-html.dsl -t sgml \ -d ./nominum-docbook-html.dsl \ ${XMLDCL} ./Bv9ARM-book.xml + rm -f HTML.index HTML.manifest Bv9ARM-book.rtf: Bv9ARM-book.xml nominum-docbook-print.dsl ${OPENJADE} -v \ diff --git a/usr.sbin/bind/doc/arm/README-SGML b/usr.sbin/bind/doc/arm/README-SGML index eb70cc7aa95..02f9dc23834 100644 --- a/usr.sbin/bind/doc/arm/README-SGML +++ b/usr.sbin/bind/doc/arm/README-SGML @@ -1,9 +1,10 @@ +Copyright (C) 2004 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2000, 2001 Internet Software Consortium. See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. The BIND v9 ARM master document is now kept in DocBook XML format. -Version: $ISC: README-SGML,v 1.16 2001/02/15 22:00:32 scanner Exp $ +Version: $ISC: README-SGML,v 1.16.206.1 2004/03/06 13:16:14 marka Exp $ The entire ARM is in the single file: |