Zone Transfer Prob.
Stephens, Bill {PBSG}
Bill.Stephens at pbsg.com
Thu Jun 20 19:49:41 UTC 2002
I have a zone (1 out of about 120) that absolutely refuses to transfer to
other ISC BIND slave servers, but transfers to NT slave servers. The ISC
BIND servers are all running BIND 8.3.1 on RedHat Linux 7.0 systems (kernel
2.2.19). I can successfully do a dig axfr. I've double checked my soa
records etc. It was working until a couple of days ago, then just stopped.
Named zone def Pri:
zone "myzone.com" IN
{
type master;
file "db.myzone.com";
check-names warn;
};
named zone def slave:
zone "myzone.com" {
type slave;
file "sec/db.myzone.com";
masters {
156.81.229.50;
};
check-names ignore;
};
SOA Primary:
$ttl 86400
$ORIGIN com.
myzone 300 IN SOA pbslcm00004.myzone.com. dnsadmin.pbsg.com.
(
2002062000
10800
3600
604800
86400 )
86400 IN NS pbslcm00004.myzone.com.
86400 IN NS pbslcm00005.myzone.com.
I have the logging set to debug, and I'm not seeing anything. The zone is
loaded on the primary, with the correct serial, no errors. The slave
receives the notify. An AXFR is approved, but the slave never creates the
file, not even the temporary. I've been fighting it all day, and have had
no luck. I must be missing something obvious. Any ideas? Is there a limit
to the number of zones BIND will support?
Bill Stephens
PepsiCo Business Solutions Group
Bill.Stephens at pbsg.com
972.376.7155 fax: 972.376.6019
More information about the bind-users
mailing list