Re: Problem named-xfer - ReadList.com

3 msg	Cannot Resolve .Net Domains
2 msg	domain 'state.gov' resolve time out
2 msg	log file entries
7 msg	Bind9(9.3.2p1) 'out of memory'
6 msg	Unexpected First Lookup Delay
6 msg	active directory, bind9, windows dns - TOGETHER
2 msg	Failover network strategy
3 msg	named 9.3.1 crashed
30 msg	bind-9.3.2-33.fc5
3 msg	strange reverse response
4 msg	how to check the version of BIND
2 msg	failed forwarder timeout
4 msg	Basic tips and hints.
3 msg	Multiple NSs or multiple glue records
1 msg	bind-9.3.2 - what could be the cause of these e...

Problem named-xfer
\ hudsonmelo (19 Sep 2006)
. \ Kevin Darcy (21 Sep 2006)

2 msg	Virtual Hosts, Reverse Lookup and Mailserver
1 msg	Question about blackhole substatement
5 msg	DNS update -- reverse zone
2 msg	Bind 9.2.3 existing

Subject:	Re: Problem named-xfer
Group:	Bind-users
From:	Kevin Darcy
Date:	21 Sep 2006

hudsonmelo wrote:
> I have a problem when restarting in.named in a secondary name server:
>
> 19-Sep-2006 14:59:11.091 default: notice: named-xfer "tradeb2b.com.br"
> exited with signal 4
>
> What is this?
>
I remember named-xfer! That's the program that BIND 4 and BIND 8 used to
invoke for zone transfers, isn't it? Boy, does that bring back memories.
You got that running in a museum somewhere? :-)

Seriously, signal 4 could theoretically mean different things on
different systems, but the standardized meaning -- possibly even an ISO
standard since my signal mnemonic listing on Solaris 9 appears to have
been moved to /usr/include/sys/iso/signal_iso.h -- seems to be "illegal
instruction". From that, my guess would be that your named-xfer binary
is corrupt somehow. A less plausible explanation is that you've managed
to stumble on a bug in named-xfer. If so, this bug may already be fixed
in a later version of BIND. You didn't specify what version of BIND you
were running, so it's impossible for us to tell that.

Rather than chase down the problem with named-xfer, though, I'd strongly
recommend investing the time and effort in upgrading/migrating to BIND
9. BIND 9 doesn't use named-xfer, so whatever problem you're having with
that should go away.

- Kevin