mir/bind
2
0
Fork 0
mirror of https://gitlab.isc.org/isc-projects/bind9 synced 2025-08-29 05:28:00 +00:00
Code Issues Releases Wiki Activity

split off the BIND 4 to BIND 9 migration docs into a separate

Browse Source 
file 'migration-4to9'
This commit is contained in:
Andreas Gustafsson 2001-02-15 00:09:33 +00:00
parent 2d556761c2
commit 39f1df3fbd
2 changed files with 49 additions and 47 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

48
doc/misc/migration
View File

@ -1,52 +1,6 @@
Copyright (C) 2000, 2001 Internet Software Consortium.
See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
BIND 4 to BIND 9 Migration Notes
To transition from BIND 4 to BIND 9 you first need to convert your
configuration file to the new format. There is a conversion tool in
contrib/named-bootconf that allows you to do this.
named-bootconf.sh < /etc/named.boot > /etc/named.conf
BIND 9 uses a system assigned port for the UDP queries it makes rather
than port 53 that BIND 4 uses. This may conflict with some firewalls.
The following directives in /etc/named.conf allows you to specify
a port to use.
query-source address * port 53;
transfer-source * port 53;
notify-source * port 53;
BIND 9 no longer uses the minimum field to specify the TTL of records
without a explicit TTL. Use the $TTL directive to specify a default TTL
before the first record without a explicit TTL.
$TTL 3600
@ IN SOA ns1.example.com. hostmaster.example.com. (
2001021100
7200
1200
3600000
7200 )
BIND 9 does not support multiple CNAMEs with the same owner name.
Illegal:
www.example.com. CNAME host1.example.com.
www.example.com. CNAME host2.example.com.
BIND 9 does not support "CNAMEs with other data" with the same owner name,
ignoring the DNSSEC records (SIG, NXT, KEY) that BIND 4 did not support.
Illegal:
www.example.com. CNAME host1.example.com.
www.example.com. MX 10 host2.example.com.
BIND 9 is less tolerant of errors in master files, so check your logs and
fix any errors reported. The named-checkzone program can also be to check
master files.
BIND 8 to BIND 9 Migration Notes
BIND 9 is designed to be mostly upwards compatible with BIND 8, but
@ -256,4 +210,4 @@ directing queries for a given domain to a particular set of name
servers.
$Id: migration,v 1.23 2001/02/12 02:02:06 bwelling Exp $
$Id: migration,v 1.24 2001/02/15 00:09:32 gson Exp $

48
doc/misc/migration-4to9 Normal file
View File

@ -0,0 +1,48 @@
Copyright (C) 2000, 2001 Internet Software Consortium.
See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.
BIND 4 to BIND 9 Migration Notes
To transition from BIND 4 to BIND 9 you first need to convert your
configuration file to the new format. There is a conversion tool in
contrib/named-bootconf that allows you to do this.
named-bootconf.sh < /etc/named.boot > /etc/named.conf
BIND 9 uses a system assigned port for the UDP queries it makes rather
than port 53 that BIND 4 uses. This may conflict with some firewalls.
The following directives in /etc/named.conf allows you to specify
a port to use.
query-source address * port 53;
transfer-source * port 53;
notify-source * port 53;
BIND 9 no longer uses the minimum field to specify the TTL of records
without a explicit TTL. Use the $TTL directive to specify a default TTL
before the first record without a explicit TTL.
$TTL 3600
@ IN SOA ns1.example.com. hostmaster.example.com. (
2001021100
7200
1200
3600000
7200 )
BIND 9 does not support multiple CNAMEs with the same owner name.
Illegal:
www.example.com. CNAME host1.example.com.
www.example.com. CNAME host2.example.com.
BIND 9 does not support "CNAMEs with other data" with the same owner name,
ignoring the DNSSEC records (SIG, NXT, KEY) that BIND 4 did not support.
Illegal:
www.example.com. CNAME host1.example.com.
www.example.com. MX 10 host2.example.com.
BIND 9 is less tolerant of errors in master files, so check your logs and
fix any errors reported. The named-checkzone program can also be to check
master files.