odd problem with named-xfer
phn at icke-reklam.ipsec.nu
phn at icke-reklam.ipsec.nu
Thu Aug 8 18:14:26 UTC 2002
Steve Foster <fosters at uk.psi.com> wrote:
> hi there,
> i am trying to use named-xfer to get a domains info, ( we are allowed to
> axfr it) , but i am getting the following error in daemon.log:
> named-xfer[2204]: premature EOF, fetching "<some-domain>"
> It works for all other domains on this primary, they all named-xfer
> perfectly, however i can also dig axfr it as well, so i know i have access,
> it just won't let me named-xfer it....
> i have turned the debug level up on named-xfer, but it is telling me
> nothing , not even a refused message, all i get is:
> domain `<somedomain>'; file `/var/tmp/zone'; serial 0
> zone found (2): "<somedomain>", source = /var/tmp/zone
> addrcnt = 1
> getzone() <somedomain> secondary
> address [<primary IP>] AXFR
> connecting to server #1 [<primary IP>].53
> close(6) succeeded
> and thats it.....the error messaghe suggest the far end is closing the
> connection , but we have tried removing zone information from the primaries
> zonefile but to no avail..
> has anyone seen this before??
My guess is that the zone contains illegal records and that
use a more strictversion of bind then the master uses.
--
Peter Håkanson
IPSec Sverige ( At Gothenburg Riverside )
Sorry about my e-mail address, but i'm trying to keep spam out,
remove "icke-reklam" if you feel for mailing me. Thanx.
More information about the bind-users
mailing list