named-xfer error

[Jonathan Fanti]

I checked my named.conf file and it reads:

options {
	directory "/etc/namedb";
	pid-file "/var/run/named.pid";
	named-xfer "/bin/named-xfer";
}


I have only installed the compiled versions of named-xfer and named 
within the sandbox - but I did double check this by moving named-xfer 
into the sandbox again, just in case.

Would it be better installing a named-xfer and named with lib's 
statically compiled into them, rather than making copies of the required 
lib's in <sandboxdir>/usr/lib?

Cheers,

Jon.

	
	

Jim Reid wrote:

>>>>>> "Jonathan" == Jonathan Fanti <jonathan.fanti at unique.com> writes:
>>>>> 
> 
>     Jonathan> The logs looks something like this:
> 
>     Jonathan> Jan 10 09:29:16 ns1 named[109]: named-xfer "alimango.co.uk" exited with signal 6
>     Jonathan> Jan 10 09:29:18 ns1 named[109]: named-xfer "hazlewoodmotorsport.co.uk" exited with signal 6
> 
>     Jonathan> Blah, blah, blah.... goes on like this all domains.
> 
>     Jonathan> when I transfer the domains manually
>     Jonathan> This works fine, and the domain is transfered.
> 
> Try using the version of named-xfer that came with the version of
> named you're running. The two programs must be installed as pairs.
> A named-xfer for another BIND version would run OK stand-alone, but
> not when it was invoked by named.