named-xfer: premature EOF
Barry Margolin
barmar at genuity.net
Fri Jan 25 00:27:32 UTC 2002
In article <a2q38n$em4 at pub3.rc.vix.com>, chris <cherbst at hotpop.com> wrote:
>
>I am trying to troubleshoot a zone transfer problem on a BIND 4 server.
>Running named-xfer -z somedomain.com -f test.db 1.2.3.4 results in:
>
>named-xfer[10616]: premature EOF, fetching "somedomain.com"
>
>the same syntax works fine on other hosts, so I suspect a networking
>issue, not BIND configuration.
What version of BIND is the master running? If it's BIND 9, make sure
you've configured "transfer-format one-answer".
Another thing that often causes this error is not having the slave in the
"allow-transfer" access list on the master.
--
Barry Margolin, barmar at genuity.net
Genuity, Woburn, MA
*** DON'T SEND TECHNICAL QUESTIONS DIRECTLY TO ME, post them to newsgroups.
Please DON'T copy followups to me -- I'll assume it wasn't posted to the group.
More information about the bind-users
mailing list