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

Mention allow-query changes and allow-query-cache. [RT #17726]

Browse Source 
And add new copyright year too.
This commit is contained in:
Jeremy Reed
2008-03-18 15:42:53 +00:00
parent f7e10e70a0
commit 59c0977bed
1 changed files with 12 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
doc/misc/migration
View File

@@ -1,4 +1,4 @@
Copyright (C) 2004, 2007 Internet Systems Consortium, Inc. ("ISC") Copyright (C) 2004, 2007, 2008 Internet Systems Consortium, Inc. ("ISC")
Copyright (C) 2000, 2001, 2003 Internet Software Consortium. Copyright (C) 2000, 2001, 2003 Internet Software Consortium.
See COPYRIGHT in the source root or http://isc.org/copyright.html for terms. See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
@@ -26,6 +26,16 @@ understand the many-answers zone transfer format (e.g., BIND 4.9.5 or
older) you need to explicitly specify "transfer-format one-answer;" in older) you need to explicitly specify "transfer-format one-answer;" in
either the options block or a server statement. either the options block or a server statement.
BIND 9.4 onwards implements "allow-query-cache". The "allow-query"
option is no longer used to specify access to the cache. The
"allow-query" option continues to specify which hosts are allowed
to ask ordinary DNS questions. The new "allow-query-cache" option
is used to specify which hosts are allowed to get answers from the
cache. Since BIND 9.4.1, if "allow-query-cache" is not set then
"allow-recursion" is used if it is set, otherwise "allow-query" is
used if it is set, otherwise the default localnets and localhost
is used.
1.2. Handling of Configuration File Errors 1.2. Handling of Configuration File Errors
In BIND 9, named refuses to start if it detects an error in In BIND 9, named refuses to start if it detects an error in
@@ -254,4 +264,4 @@ necessary, the umask should be set explicitly in the script used to
start the named process. start the named process.
$Id: migration,v 1.48 2007/08/23 23:46:43 tbox Exp $ $Id: migration,v 1.49 2008/03/18 15:42:53 jreed Exp $