From d6c0627d1e4d841eac9576427f2d4a0cf9a47e2c Mon Sep 17 00:00:00 2001 From: Mark Andrews Date: Mon, 11 Feb 2002 04:03:51 +0000 Subject: [PATCH] 1199. [doc] ARM reference to RFC 2157 should have been RFC 1918. [RT #2436] --- CHANGES | 3 +++ doc/arm/Bv9ARM-book.xml | 4 ++-- 2 files changed, 5 insertions(+), 2 deletions(-) diff --git a/CHANGES b/CHANGES index 88bad6b2b1..4c81d65290 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,6 @@ +1199. [doc] ARM reference to RFC 2157 should have been RFC 1918. + [RT #2436] + 1198. [bug] OPT printing style was not consistant with the way the header fields are printed. "do" was not reported if set. Report if any of the MBZ bits are set. diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml index 8ab9872195..8d88a69e4e 100644 --- a/doc/arm/Bv9ARM-book.xml +++ b/doc/arm/Bv9ARM-book.xml @@ -2,7 +2,7 @@ - + BIND 9 Administrator Reference Manual @@ -4558,7 +4558,7 @@ configured. 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 10.in-addr.arpa to use a set of internal name servers as the authoritative servers for that domain.