upstream/bind9
1
0
Fork 0
mirror of https://github.com/isc-projects/bind9.git synced 2026-04-29 09:59:08 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

pullup:

Browse source 
1199.  [doc]           ARM reference to RFC 2157 should have been RFC 1918.
                       [RT #2436]
This commit is contained in:
Mark Andrews 2003-05-12 02:06:01 +00:00
parent 2d1457e40a
commit 5361eb812c
2 changed files with 5 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

3
CHANGES
View file

@ -8,6 +8,9 @@
sharing the same port for listening and querying, and
changing listening addresses several times. [RT# 3509]
1199. [doc] ARM reference to RFC 2157 should have been RFC 1918.
[RT #2436]
992. [doc] dig: ~/.digrc is now documented.
--- 9.2.2 released ---

4
doc/arm/Bv9ARM-book.xml
View file

@ -2,7 +2,7 @@
<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.0//EN"
"http://www.oasis-open.org/docbook/xml/4.0/docbookx.dtd">
<!-- File: $Id: Bv9ARM-book.xml,v 1.155.2.24 2003/04/13 04:34:51 marka Exp $ -->
<!-- File: $Id: Bv9ARM-book.xml,v 1.155.2.25 2003/05/12 02:06:01 marka Exp $ -->
<book>
<title>BIND 9 Administrator Reference Manual</title>
@ -4329,7 +4329,7 @@ configured.</para>
<para>Stub zones can also be used as a way of forcing the resolution
of a given domain to use a particular set of authoritative servers.
For example, the caching name servers on a private network using
RFC2157 addressing may be configured with stub zones for
RFC1981 addressing may be configured with stub zones for
<literal>10.in-addr.arpa</literal>
to use a set of internal name servers as the authoritative
servers for that domain.</para>