mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-30 22:15:20 +00:00
Code Issues Releases Wiki Activity

RT #169: note that logging categories have changed from BIND 8

Browse Source
This commit is contained in:
Andreas Gustafsson
2000-07-14 17:11:07 +00:00
parent da892e9733
commit 074ae7bf09
1 changed files with 17 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

18
doc/misc/migration
View File

@@ -25,6 +25,22 @@ warning message. A message is also logged about each option whose
default has changed unless the option is set explicitly in named.conf. default has changed unless the option is set explicitly in named.conf.
1.2. Logging
The set of logging categories in BIND 9 is different from that
in BIND 8. If you have customized your logging on a per-category
basis, you need to modify your logging statement to use the
new categories.
Another difference is that the "logging" statement only takes effect
after the entire named.conf file has been read. This means that when
the server starts up, any messages about errors in the configuration
file are always logged to the default destination (syslog) when the
server first starts up, regardless of the contents of the "logging"
statement. In BIND 8, the new logging configuration took effect
immediately after the "logging" statement was read.
2. Zone File Compatibility 2. Zone File Compatibility
2.1. Strict RFC1035 Interpretation of TTLs in Zone Files 2.1. Strict RFC1035 Interpretation of TTLs in Zone Files
@@ -79,4 +95,4 @@ completely. We have contacted the manufacturer of the name server in
case and are trying to resolve the issue with them. case and are trying to resolve the issue with them.
$Id: migration,v 1.2 2000/07/12 05:06:33 gson Exp $ $Id: migration,v 1.3 2000/07/14 17:11:07 gson Exp $