Hi Stuart, The signer is unable to parse the packet because either it failed to parse the RRs in the packet, or found an incomplete transfer over UDP. Failing to parse an RR is possible when
* The packet buffer is too small to hold an RR. * If it is a SOA RR, it encountered an IXFR but required an AXFR (first zone transfer) * If it is a SOA RR, the serial does not match the inbound serial on disk. I could make the "bad rr" message more fine grained. Best regards, Matthijs On 02/10/2013 07:47 AM, 刘硕 wrote: > Hi, > > I have found lots of messages bellow and I don't know why: > > Feb 4 20:26:52 index ods-signerd: [xfrd] bad packet: zone dstest received > bad xfr packet (bad rr) > Feb 4 20:26:52 index ods-signerd: [xfrd] bad packet: zone dstest received > bad xfr packet (bad rr) > Feb 4 20:26:52 index ods-signerd: [xfrd] bad packet: zone dstest received > bad xfr packet (bad rr) > Feb 4 20:30:01 index ods-signerd: [xfrd] bad packet: zone dstest received > bad xfr packet (bad rr) > > > Best regards, > Stuart > >
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Opendnssec-user mailing list [email protected] https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
