zone transfer problem

[Jim Reid]

>>>>> "Edwin" == Edwin Pijper <e.pijper at zonnet.nl> writes:

    Edwin> I tried (as root) to transfer the zone "test.bel.nl" from
    Edwin> the aplabu44 (10.8.60.44) with the following commands:

    Edwin> named-xfer -s 0 -z test.bel.nl -f db.test 10.8.60.39 
    Edwin> echo $?  4

    Edwin> When I configure a slave nameserver (on the aplabu44) after
    Edwin> this test, the transfer won't work. How can I resolv this?

What do you mean "won't work"? What's in the logs? It's a shame that
you provided a lot of detail from your named.conf and some log
entries, but you barely provided any data that actually mattered. Most
of the stuff you showed was for nothing. What's needed to identify the
problem are the logs showing what the name server did after you added
the slave zone{} statement and "ndc reconfig" 'ed the server. A copy
of that slave zone{} statement you added would have been nice too.

If named-xfer works by hand but not when run from the name server, it
usually means that the version of named-xfer is not the one for the
version of the name server. Perhaps you didn't install named-xfer when
you last upgraded the name server? Other possible causes for failing
zone transfers at this stage are fork() failures because of system
resource problems or exec() failing because named-xfer isn't where
named expects to find it. The logs would tell us about them. When you
ran named-xfer by hand, you've shown that there are no connectivity
problems between the servers and that the remote name server is
authoritative and allowing transfers for the zone in question.
Therefore those possibilities can be eliminated.

Another thought: maybe the slave zone statement quoted the same zone
file name for test.bel.nl as the server had when it was master for
that zone? [It loads that file, then checks the zone's SOA with the
master, finds the serial number is unchanged so doesn't do a zone
transfer.] Or maybe you tried to make the server master and slave for
the same zone?