zone transfer exits
A. van Drie
av3 at xs4all.nl
Fri Jan 14 23:48:57 UTC 2000
Hi,
i'm running into a problem with zone transfers. This is gonna be a bit of
long story.
The setup:
ns2:
stripped redhat 6 linux firewall (ip masquerading), running sendmail and
bind, only 6 zonefiles (primary and secondary together). Chrooted bind.
Running fine, zone xfers no problem.
ns1:
same os, less stripped, no firewalling, single ip, running: sendmail,
httpd and bind. Also chrooted, containg five primary zonefiles, and three
secondary for subdomains running primary on ns2. And on this machine those
three zonetransfers exit with a code 13
ns2 allows transfers for ns1. That is confirmed by the logs:
Jan 11 18:27:30 ns2 named[26369]: Sent NOTIFY for "subdomain IN SOA"
(subdomain); 1 NS, 1 A
Jan 11 18:27:30 ns2 named[26369]: Received NOTIFY answer from
IPADDR for "subdomain IN SOA"
It is even confirmed by ns1.
Then ns1. Logs:
Jan 14 23:45:15 ns1 named[9118]: rcvd NOTIFY(subdomain, IN, SOA)
from [IPADDR].53
Jan 14 23:45:15 ns1 named[9118]: named-xfer "subdomain" exited
with signal 13
and in the 'secondary' dir it writes a file called
subdomain.9HB45b
or another seemingly random 6 char string after 'subdomain.' being 0
bytes of size.
As user 'bind' (of course the user under which bind runs) i issue the
command:
./usr/sbin/named-xfer -d 2 -l /tmp/xfer.loggie -z subdomain -f \
zone/secondary/subdomain ns2
works fine.
Can anyone already point me in the right direction?
Thank you,
Arjen van Drie.
More information about the bind-users
mailing list