BIND 9 to BIND 8 downgrade
Jim McAtee
jmcatee at mediaodyssey.com
Wed Feb 6 20:11:41 UTC 2002
Because of the problems with the Win32 port of BIND 9.2, I'm in the midst of
switching our Win2k BIND 9 nameservers to BIND 8.3.1. Formerly, we were
running BIND 4.9, so I'm not completely familiar with the configuration
differences between BIND 8 and 9.
Will master zone files work well if they're unchanged from BIND 9? A
typical zone file on our servers looks like the one shown below. Is the
$TTL directive recognized by BIND 8.3, or would this zone file have a
default TTL on records of just 20 minutes?
$TTL 1d
@ IN SOA ns1.ourdomain.com. hostmaster.ourdomain.com. (
2001112701 ; serial
4h ; refresh
30m ; retry
28d ; expire
20m ) ; minimum
7d IN NS ns1.ourdomain.com.
7d IN NS ns2.ourdomain.com.
IN MX 10 mail.ourdomain.com.
IN MX 20 mail2.ourdomain.com.
IN A 204.138.18.100
www IN A 204.138.18.100
In the options section of the configuration file, we use at least a couple
of BIND 9 specific options. Is there a BIND 8 equivalent to notify-source
or transfer-source? When I set up the servers under BIND 9, I believe that
these options were necessary to make notifies and transfers function when
running on machines with multiple IP addresses.
acl "localmachines" {
204.138.47.0/25;
192.168.1.0/24;
};
acl "secondarydns" {
216.138.18.101;
216.138.18.84;
};
options {
directory "c:\named";
listen-on { 204.138.47.6; };
notify-source 204.138.47.6;
transfer-source 204.138.47.6;
allow-transfer { "localmachines"; "secondarydns"; };
};
Thanks,
Jim
More information about the bind-users
mailing list