[Opendnssec-user]IXFR Bugs in 1.4.0 release

[Matthijs Mekking]

Hi Stuart,

I see a lot of messages like this:

Apr 27 17:17:57 index ods-signerd: [xfrd] bad packet: zone xn--siq2a91a
received bad xfr packet (202.173.9.4)

So why does the signer mark this as a bad packet? Would it be possible
to capture the packet (pcap)? Could you send it to me? Also the
{conf,zonelist,kasp,addns}.xml files and the contents of the signer
working directory (/var/opendnssec/tmp/) could be useful for debugging,
off list if you want.

Best regards,
  Matthijs



On 04/27/2013 11:24 AM, shuoleo at 126 wrote:
> Hi Matthijs,
>  
> I'm testing the 1.4.0 release version these days with its AXFR/IXFR ability.
> But I'm sorry to tell you that there may be some bugs in it.
> I'm using a script to add RRs into BIND1 which plays the role of INBOUND
> of opendnssec in crontab, and there is a BIND2 as the OUTBOUND of
> opendnssec.
> The script will also dig the RRs from BIND2 after a specific long time
> to make sure the RRs exist and are signed.
>  
> The logs and script are attached for you to check.
>  
> Good luck.
>  
> Best Regards,
> Stuart


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 553 bytes
Desc: OpenPGP digital signature
URL: <http://lists.opendnssec.org/pipermail/opendnssec-user/attachments/20130429/0446e7ad/attachment.bin>