Error with axfr-get

Good morning,

I have a djbdns install that is transferring zone from client maintained 
servers. I have begun seeing an error with one zone, from one client. 
The error is "axfr-get: fatal: unable to parse AXFR results: protocol 
error". I compared the zone giving the error to a zone that does not and 
I see little difference between them. Here are the zones in question as 
dig results (axfr-get returns no data).

First a zone without error,
bash-3.2# dig @ns0.centra.org centralink.org axfr +tcp

; <<>> DiG 9.3.2 <<>> @ns0.centra.org centralink.org axfr +tcp
; (1 server found)
;; global options:  printcmd
centralink.org.         172800  IN      SOA     ns0.centra.org. 
admin.centra.org. 79 300 300 5184000 172800
centralink.org.         172800  IN      A       67.133.220.30
centralink.org.         172800  IN      NS      ns1auth.tls.net.
centralink.org.         172800  IN      NS      ns2auth.tls.net.
centralink.org.         172800  IN      NS      ns3auth.tls.net.
centralink.org.         172800  IN      MX      10 
centra.org.p1.rp.binc.net.
centralink.org.         172800  IN      MX      20 
centra.org.s1.rp.binc.net.
centralink.org.         172800  IN      RP      admin.centra.org. .
ns1auth.tls.net.        172800  IN      A       65.124.104.30
ns2auth.tls.net.        172800  IN      A       65.123.104.30
ns3auth.tls.net.        172800  IN      A       65.124.110.14
demo.centralink.org.    172800  IN      A       67.133.220.33
ems.centralink.org.     172800  IN      CNAME   spam1.centra.org.
webloan.centralink.org. 172800  IN      A       67.133.220.34
centralink.org.         172800  IN      SOA     ns0.centra.org. 
admin.centra.org. 79 300 300 5184000 172800
;; Query time: 262 msec
;; SERVER: 67.133.220.31#53(67.133.220.31)
;; WHEN: Thu Jan 15 14:11:41 2009
;; XFR size: 15 records (messages 15)

Then the zone that throws the error,
; <<>> DiG 9.3.2 <<>> @ns0.centra.org centrahomeloans.com axfr +tcp
; (1 server found)
;; global options:  printcmd
centrahomeloans.com.    3600    IN      SOA     ns0.centra.org. 
admin.centra.org. 29 900 600 86400 3600
centrahomeloans.com.    3600    IN      NS      ns1auth.tls.net.
centrahomeloans.com.    3600    IN      NS      ns2auth.tls.net.
centrahomeloans.com.    3600    IN      NS      ns3auth.tls.net.
centrahomeloans.com.    3600    IN      CNAME 
tcox-centralo.mortgagewebcenter.com.
ns1auth.tls.net.        3600    IN      A       65.124.104.30
ns2auth.tls.net.        3600    IN      A       65.123.104.30
ns3auth.tls.net.        3600    IN      A       65.124.110.14
www.centrahomeloans.com. 3600   IN      CNAME 
tcox-centralo.mortgagewebcenter.com.
centrahomeloans.com.    3600    IN      SOA     ns0.centra.org. 
admin.centra.org. 29 900 600 86400 3600
;; Query time: 245 msec
;; SERVER: 67.133.220.31#53(67.133.220.31)
;; WHEN: Thu Jan 15 14:12:21 2009
;; XFR size: 10 records (messages 10)

Finally, the axfer-get failure.
bash-3.2# /usr/local/bin/tcpclient -vR  "ns0.centra.org" 53 
/usr/local/bin/axfr-get  "centrahomeloans.com" 
/usr/local/scripts/domain-xfer/new_zone/centrahomeloans.com 
/usr/local/scripts/domain-xfer/new_zone/centrahomeloans.com.tmp
tcpclient: connected to 67.133.220.31 port 53
axfr-get: fatal: unable to parse AXFR results: protocol error

Searching showed only one other hit on this error and the author didn't 
get a reply, and didn't post a solution.

http://www.unixadmintalk.com/djb-dns/922889-axfr-get-fatal-unable-parse-axfr-results-protocol-error.html

The only difference I see is the lack of an A record for the zone that 
fails. Any help would be appreciated.

DAve
-- 
The whole internet thing is sucking the life out of me,
there ain't no pony in there.