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

fixed XML syntax violations and duplicated paragraph in previous revision

Browse Source
This commit is contained in:
Andreas Gustafsson
2000-11-14 18:07:00 +00:00
parent 64291fce5a
commit cc831f51d5
1 changed files with 6 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files

24
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.36 2000/11/14 18:04:13 gson Exp $ --> <!-- File: $Id: Bv9ARM-book.xml,v 1.37 2000/11/14 18:07:00 gson Exp $ -->
<book> <book>
@@ -2660,7 +2660,7 @@ In BIND 8, <userinput>fetch-glue yes</userinput>
caused the server to attempt to fetch glue resource records it caused the server to attempt to fetch glue resource records it
didn't have when constructing the additional didn't have when constructing the additional
data section of a response. This is now considered a bad idea data section of a response. This is now considered a bad idea
and BIND 9 never does it. and BIND 9 never does it.</para>
</entry> </entry>
</row> </row>
<row rowsep = "0"> <row rowsep = "0">
@@ -2676,7 +2676,7 @@ the two separate options <command>auth-nxdomain</command> <userinput>yes</userin
<entry colname = "1"><para><command>host-statistics</command></para></entry> <entry colname = "1"><para><command>host-statistics</command></para></entry>
<entry colname = "2"><para>In BIND 8, this enables keeping of <entry colname = "2"><para>In BIND 8, this enables keeping of
statistics for every host that the nameserver interacts with. statistics for every host that the nameserver interacts with.
Not implemented in BIND 9. Not implemented in BIND 9.</para></entry>
</row> </row>
<row rowsep = "0"> <row rowsep = "0">
<entry colname = "1"><para><command>maintain-ixfr-base</command></para></entry> <entry colname = "1"><para><command>maintain-ixfr-base</command></para></entry>
@@ -3128,7 +3128,7 @@ implemented in <acronym>BIND</acronym> 9.</simpara></note></entry>
<row rowsep = "0"> <row rowsep = "0">
<entry colname = "1"><para><command>max-ixfr-log-size</command></para></entry> <entry colname = "1"><para><command>max-ixfr-log-size</command></para></entry>
<entry colname = "2"><para>This option is obsolete; it is accepted <entry colname = "2"><para>This option is obsolete; it is accepted
and ignored for BIND 8 compatibility.</entry> and ignored for BIND 8 compatibility.</para></entry>
</row> </row>
<row rowsep = "0"> <row rowsep = "0">
<entry colname = "1"><para><command>recursive-clients</command></para></entry> <entry colname = "1"><para><command>recursive-clients</command></para></entry>
@@ -4561,20 +4561,8 @@ the <command>touch</command> utility (to change file access and
modification times) or the <command>chown</command> utility (to modification times) or the <command>chown</command> utility (to
set the user id and/or group id) on files to which you want <acronym>BIND</acronym> set the user id and/or group id) on files to which you want <acronym>BIND</acronym>
to write.</para></sect2></sect1> to write.</para></sect2></sect1>
<sect1><title>Dynamic Updates</title> <sect1><title>Dynamic Updates</title>
<para>Access to the dynamic
<para>Access to the dynamic update facility should be strictly limited.
In earlier versions of <acronym>BIND</acronym> the only way to do this was based on
the IP address of the host requesting the update. <acronym>BIND9</acronym> also
supports authenticating updates cryptographically by means of transaction
signatures (TSIG). The use of TSIG is strongly recommended.</para>
<para>Some sites choose to keep all dynamically updated DNS data
in a subdomain and delegate that subdomain to a separate zone. This
way, the top-level zone containing critical data such as the IP addresses
of public web and mail servers need not allow dynamic update at
all.</para>
<sect1><title>Dynamic Updates</title> <para>Access to the dynamic
update facility should be strictly limited. In earlier versions of update facility should be strictly limited. In earlier versions of
<acronym>BIND</acronym> the only way to do this was based on the IP <acronym>BIND</acronym> the only way to do this was based on the IP
address of the host requesting the update, by listing an IP address or address of the host requesting the update, by listing an IP address or