mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-09-03 08:05:21 +00:00
Code Issues Releases Wiki Activity

minor spacing and font fixes

Browse Source
This commit is contained in:
Andreas Gustafsson
2000-10-19 17:22:53 +00:00
parent 54cd4dbd01
commit 9349d49b7f
1 changed files with 26 additions and 26 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
doc/arm/Bv9ARM-book.xml
View File

@@ -2,7 +2,7 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN" <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN"
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd"> "http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd">
<!-- File: $Id: Bv9ARM-book.xml,v 1.18 2000/10/19 17:15:24 gson Exp $ --> <!-- File: $Id: Bv9ARM-book.xml,v 1.19 2000/10/19 17:22:53 gson Exp $ -->
<book> <book>
@@ -140,7 +140,7 @@ called <command>named</command> and a <command>resolver</command> library.
The <acronym>BIND</acronym> server runs in the background, servicing queries on a well The <acronym>BIND</acronym> server runs in the background, servicing queries on a well
known network port. The standard port for the User Datagram Protocol known network port. The standard port for the User Datagram Protocol
(UDP) and Transmission Control Protocol (TCP), usually port 53, (UDP) and Transmission Control Protocol (TCP), usually port 53,
is specified in<command> </command><filename>/etc/services</filename>. is specified in <filename>/etc/services</filename>.
The <emphasis>resolver</emphasis> is a set of routines residing The <emphasis>resolver</emphasis> is a set of routines residing
in a system library that provides the interface that programs can in a system library that provides the interface that programs can
use to access the domain name services.</para> use to access the domain name services.</para>
@@ -1644,7 +1644,7 @@ defined by the <command>acl</command> statement.</para></entry>
</row> </row>
<row rowsep = "0"> <row rowsep = "0">
<entry colname = "1"><para><varname>address_match_list</varname></para></entry> <entry colname = "1"><para><varname>address_match_list</varname></para></entry>
<entry colname = "2"><para>A list of one or more <varname>ip_addr</varname><command>, </command><varname>ip_prefix</varname><command>, </command><varname>key_id</varname><command>, </command>or <varname>acl_name</varname> elements, see <entry colname = "2"><para>A list of one or more <varname>ip_addr</varname>, <varname>ip_prefix</varname>, <varname>key_id</varname>, or <varname>acl_name</varname> elements, see
<xref linkend="address_match_lists"/>.</para></entry> <xref linkend="address_match_lists"/>.</para></entry>
</row> </row>
<row rowsep = "0"> <row rowsep = "0">
@@ -1668,7 +1668,7 @@ in <varname>dotted_decimal</varname> notation.</para></entry>
</row> </row>
<row rowsep = "0"> <row rowsep = "0">
<entry colname = "1"><para><varname>ip_addr</varname></para></entry> <entry colname = "1"><para><varname>ip_addr</varname></para></entry>
<entry colname = "2"><para>An <varname>ip4_addr</varname> or<command> </command><varname>ip6_addr</varname>.</para></entry> <entry colname = "2"><para>An <varname>ip4_addr</varname> or <varname>ip6_addr</varname>.</para></entry>
</row> </row>
<row rowsep = "0"> <row rowsep = "0">
<entry colname = "1"><para><varname>ip_port</varname></para></entry> <entry colname = "1"><para><varname>ip_port</varname></para></entry>
@@ -1717,7 +1717,7 @@ value of <varname>size_spec</varname> is that of unsigned long integers
on the machine. An <varname>unlimited</varname> <varname>size_spec</varname> requests unlimited on the machine. An <varname>unlimited</varname> <varname>size_spec</varname> requests unlimited
use, or the maximum available amount. A <varname>default size_spec</varname> uses use, or the maximum available amount. A <varname>default size_spec</varname> uses
the limit that was in force when the server was started.</para><para>A <varname>number</varname> can the limit that was in force when the server was started.</para><para>A <varname>number</varname> can
optionally be followed by a scaling factor: <userinput>K</userinput> or <userinput>k</userinput><command> </command>for optionally be followed by a scaling factor: <userinput>K</userinput> or <userinput>k</userinput> for
kilobytes, <userinput>M</userinput> or <userinput>m</userinput> for kilobytes, <userinput>M</userinput> or <userinput>m</userinput> for
megabytes, and <userinput>G</userinput> or <userinput>g</userinput> for gigabytes, megabytes, and <userinput>G</userinput> or <userinput>g</userinput> for gigabytes,
which scale by 1024, 1024*1024, and 1024*1024*1024 respectively.</para><para>Integer which scale by 1024, 1024*1024, and 1024*1024*1024 respectively.</para><para>Integer
@@ -2564,8 +2564,8 @@ the obsolete DNS query type IQUERY. <acronym>BIND</acronym> 9 never does IQUERY
nodes in the zone is called <emphasis>glue</emphasis> information). nodes in the zone is called <emphasis>glue</emphasis> information).
If <userinput>yes</userinput> (the default), the server will fetch If <userinput>yes</userinput> (the default), the server will fetch
glue resource records it doesn't have when constructing the additional glue resource records it doesn't have when constructing the additional
data section of a response. <command>fetch-glue </command><userinput>no</userinput><command> </command>can data section of a response. <command>fetch-glue</command> <userinput>no</userinput> can
be used in conjunction with <command>recursion </command><userinput>no</userinput><command> </command>to be used in conjunction with <command>recursion</command> <userinput>no</userinput> to
prevent the server's cache from growing or becoming corrupted (at prevent the server's cache from growing or becoming corrupted (at
the cost of requiring more work from the client).</para><note> the cost of requiring more work from the client).</para><note>
<simpara>Not yet <simpara>Not yet
@@ -3147,7 +3147,7 @@ records, or <varname>RRset</varname>, you must use the <command>sortlist</comman
linkend="types_of_resource_records_and_when_to_use_them"/>. Specifications for RRs linkend="types_of_resource_records_and_when_to_use_them"/>. Specifications for RRs
are documented in RFC 1035.</para> are documented in RFC 1035.</para>
<para>When returning multiple RRs the nameserver will normally return <para>When returning multiple RRs the nameserver will normally return
them in <varname>Round Robin</varname><varname> </varname>order, them in <varname>Round Robin</varname> order,
that is, after each request the first RR is put at the end of the that is, after each request the first RR is put at the end of the
list. The client resolver code should rearrange the RRs as appropriate, list. The client resolver code should rearrange the RRs as appropriate,
that is, using any addresses on the local net in preference to other addresses. that is, using any addresses on the local net in preference to other addresses.