[Opendnssec-user] Large zone reading bug when signing?

Matthijs Mekking matthijs at nlnetlabs.nl
Mon Jun 25 09:06:44 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Paul,

Any chance if you tried to run that zone through ldns-read-zone?

Best regards,
  Matthijs

On 05/22/2012 09:55 AM, Matthijs Mekking wrote:
> Follow up.
> 
> When I copy those lines into my unsigned zone file, it works fine. 
> Perhaps I could get hold of the zone file that's causing this?
> 
> Best regards, Matthijs
> 
> On 05/15/2012 09:44 AM, Matthijs Mekking wrote:
>> Hi Paul,
> 
>> These errors come from ldns (Syntax error, could not parse the 
>> RR's TTL). Are you able to read the zone with ldns-read-zone?
> 
>> Best regards, Matthijs
> 
>> On 05/15/2012 03:53 AM, Paul Wouters wrote:
> 
>>> When signing a big zone (4M entries, opt out) I seem to be 
>>> getting some weird parse errors on the zone within the signer 
>>> daemon (1.4.0a1):
> 
>>> May 14 21:40:03 signer02 ods-signerd: [adapter] error parsing
>>> RR at line 2544568 (Syntax error, could not parse the RR's
>>> TTL): 000000848177. May 14 21:40:03 signer02 ods-signerd:
>>> [adapter] error reading RR at line 2544568 (Syntax error, could
>>> not parse the RR's TTL): 000000848177. May 14 21:40:03
>>> signer02 ods-signerd: [tools] unable to read zone test: adapter
>>> failed (General error) May 14 21:40:05 signer02 ods-signerd:
>>> [worker[1]] continue task [sign] for zone test
> 
>>> When i look at around those lines, I see nothing strange:
> 
>>> 000000848175.test.                      IN      NS 
>>> ns1.000000848175.test. IN      NS ns2.000000848175.com. IN NS
>>> ns3.000000848175.net. 000000848176.test. IN NS
>>> ns1.000000848176.test. IN      NS ns2.000000848176.com. IN NS
>>> ns3.000000848176.net. 000000848177.test. IN NS
>>> ns1.000000848177.test. IN      NS ns2.000000848177.com. IN NS
>>> ns3.000000848177.net. 000000848178.test. IN NS
>>> ns1.000000848178.test. IN      NS ns2.000000848178.com. IN NS
>>> ns3.000000848178.net. 000000848179.test. IN NS
>>> ns1.000000848179.test. IN      NS ns2.000000848179.com. IN NS
>>> ns3.000000848179.net. 000000848180.test. IN NS
>>> ns1.000000848180.test.
> 
>>> Note there are no TTL's mentioned anywhere, apart from the zone
>>>  top which has: $TTL 1d
> 
>>> It seems that the internal state got very confused. I am not 
>>> sure how to debug this further.
> 
>>> Paul _______________________________________________ 
>>> Opendnssec-user mailing list
>>> Opendnssec-user at lists.opendnssec.org 
>>> https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
> 
>> _______________________________________________ Opendnssec-user 
>> mailing list Opendnssec-user at lists.opendnssec.org 
>> https://lists.opendnssec.org/mailman/listinfo/opendnssec-user
> 
> _______________________________________________ Opendnssec-user
> mailing list Opendnssec-user at lists.opendnssec.org 
> https://lists.opendnssec.org/mailman/listinfo/opendnssec-user

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJP6CokAAoJEA8yVCPsQCW5cgkH/RrbkbuAGY4H55pop1bolNXv
aV//CVF9nTTFAfqMJx1/DXu1Z//B9QVJIEiNd3nP+Kw7WEOYnBvvuK0C7/6V2TlK
WeY3ppP8hRIzlS2Zu2K+OindQWe/4MggXYUAp1ju0KwF2bpZoV45mIyxIOy+A3OA
zyzLwCV4K5Aw/w4/IJXyY2raEKLYZCO38/XfaY85ScwQv7wfwaWkmEg8+1i0FoWy
JTqqky93uuNOHntSyCnC9e1n5EwG24Sy24DYGq5FfYutAq0Wr3g5wMnY2ZYsHZzJ
+ojlDptD45cUZ0cGPIj1fGF7NG0pC7q2sWrJ0HfrhBqS5aqA8uUrFgTUBJu//S0=
=FtNn
-----END PGP SIGNATURE-----



More information about the Opendnssec-user mailing list