From adb6b4397091d2380f0cb412c603816610638f95 Mon Sep 17 00:00:00 2001 From: Brian Wellington Date: Sun, 11 Mar 2001 18:39:19 +0000 Subject: [PATCH] fix grammar & spelling, remove specific auth-nxdomain text as the warning is no longer printed. --- doc/misc/migration | 14 +++----------- 1 file changed, 3 insertions(+), 11 deletions(-) diff --git a/doc/misc/migration b/doc/misc/migration index 54fa9ceb0c..7dbd9f80aa 100644 --- a/doc/misc/migration +++ b/doc/misc/migration @@ -12,21 +12,13 @@ upgrading an existing BIND 8 installation to use BIND 9. 1.1. Unimplemented Options and Changed Defaults -BIND 9.1 supports most, but not all but not of the named.conf options -of BIND 8. For a complete list of implmented options, see -doc/misc/options. +BIND 9.1 supports most, but not all of the named.conf options of BIND 8. +For a complete list of implemented options, see doc/misc/options. If your named.conf file uses an unimplemented option, named will log a warning message. A message is also logged about each option whose default has changed unless the option is set explicitly in named.conf. -In particular, if you see a warning message about the default for the -"auth-nxdomain" option having changed, you can suppress it by adding -one of the following lines to the named.conf options { } block: - - auth-nxdomain no; # conform to RFC1035 - auth-nxdomain yes; # do what BIND 8 did by default - 1.2. Handling of Configuration File Errors In BIND 9, named refuses to start if it detects an error in @@ -187,4 +179,4 @@ directing queries for a given domain to a particular set of name servers. -$Id: migration,v 1.25 2001/03/05 20:58:57 gson Exp $ +$Id: migration,v 1.26 2001/03/11 18:39:19 bwelling Exp $