bind-8.2.2_p7 chrooted / named-xfer fails (sigpipe)
Ricardo Manuel Oliveira
rmo at eurotux.com
Fri Nov 24 16:16:22 UTC 2000
Jim Reid wrote:
>
> >>>>> "Ricardo" == Ricardo Manuel Oliveira <rmo at eurotux.com> writes:
>
> Ricardo> Hi everyone. First post on the list :)
>
> Ricardo> I have a bind-8.2.2P7 running perfectly, chrooted,
> Ricardo> except for the zone-transfers; I get these kind of
> Ricardo> messages in the logs:
>
> Ricardo> ns named[30012]: named-xfer "domain.com" exited with signal 13
>
> Ricardo> I have verified that, running the named-xfer by hand, it
> Ricardo> works like a charm.
>
> Are you running the version of named-xfer that comes with the version
> of BIND that you're running? If so, can you run named-xfer by hand
> successfully from your chroot jail? ie
> # chroot chroot-jail-dir
> # /usr/sbin/named-xfer .....
chroot /chroot/dns
bash# named-xfer -z domain.com -f BLA xxx.xxx.xxx.xxx
I get the BLA file, with the complete zone, as well as a
ns named[31012]: IP/TCP connection from
[xxx.xxx.xxx.xxx].1234 (fd 8) in
the primary server's logs.
Any ideas?
----
Ricardo Manuel Oliveira
Eurotux Informática, SA
More information about the bind-users
mailing list