<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<small><font face="Courier New, Courier, monospace">Yes, I can see
exactly where it stopped, but I can't find a reason why it did
so. It seems to me as a typical host A record like all the
others - it responds to dig queries as well.<br>
<br>
I exported it and it looks like that (I left only the hostname
as is, i.e. bpsil1):<br>
</font></small>
<blockquote><small><font face="Courier New, Courier, monospace">dn:
dc=bpsil1,dc=xxx,dc=example,dc=com,ou=dns,dc=example,dc=com</font></small><br>
<small><font face="Courier New, Courier, monospace">objectClass:
dNSDomain2</font></small><br>
<small><font face="Courier New, Courier, monospace">objectClass:
domainRelatedObject</font></small><br>
<small><font face="Courier New, Courier, monospace">dc: bpsil1</font></small><br>
<small><font face="Courier New, Courier, monospace">associatedDomain:
bpsil1.xxx.example.com</font></small><br>
<small><font face="Courier New, Courier, monospace">aRecord:
10.10.10.10</font></small><br>
</blockquote>
<small><font face="Courier New, Courier, monospace">After all, all
records where automatically converted from BIND8 zone files
using zone2ldap.<br>
<br>
The AXFR stops at a particular record, then includes the SOA
record and ends: <br>
</font></small>
<blockquote><small><font face="Courier New, Courier, monospace">#
dig example.com AXFR @dns.example.com<br>
<br>
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-4.P1.el5_4.2
<<>> example.com AXFR @dns.example.com<br>
;; global options:ÃÂ printcmd<br>
example.com.ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ 3600ÃÂ ÃÂ ÃÂ INÃÂ ÃÂ ÃÂ ÃÂ ÃÂ SOAÃÂ ÃÂ ÃÂ ÃÂ
dns.example.com. sysadmin.example.com. 2010090804 3600 180
604800 10800<br>
</font></small><small><font face="Courier New, Courier,
monospace"><first record (MX) in AXFR set><br>
...<br>
</font></small><small><font face="Courier New, Courier,
monospace"><last A record in AXFR set><br>
example.com.ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ ÃÂ 3600ÃÂ ÃÂ ÃÂ INÃÂ ÃÂ ÃÂ ÃÂ ÃÂ SOAÃÂ ÃÂ ÃÂ ÃÂ
dns.example.com. sysadmin.example.com. 2010090804 3600 180
604800 10800<br>
;; Query time: 192 msec<br>
;; SERVER: 195.251.204.236#53(195.251.204.236)<br>
;; WHEN: Thu SepÃÂ 9 00:01:50 2010<br>
;; XFR size: 510 records (messages 8)<br>
</font></small></blockquote>
<small><font face="Courier New, Courier, monospace">Any ideas?<br>
<br>
Nick.</font></small><br>
<br>
On 9/9/2010 12:19 ÃÂÃÅ, bert hubert wrote:
<blockquote cite="mid:20100908211859.GB30856@xs.powerdns.com"
type="cite">Usually this is because of a badly formatted record in
the database, one<br>
<pre wrap="">that cannot be sent out over AXFR. Can you figure out where it stops
exactly, and what would've been the "next" record?
</pre>
</blockquote>
</body>
</html>