<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from rtf -->
<style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<font face="Arial" size="2">
<div>-----BEGIN PGP SIGNED MESSAGE-----</div>
<div>Hash: SHA256</div>
<div> </div>
<div>Hi</div>
<div> </div>
<div>The ldns 1.6.4 has been released. So now I started to test everything once again. My normal zones just works great, but I found one extra zone in our SVN to test with, all.rr.binary.org.</div>
<div> </div>
<div>The Auditor did not like the result. But it looks like ldns is doing it right. The records are present in the signed zone, but with trailing dots in the rdata (which dnsruby seems to believe that they shouldn't).</div>
<div> </div>
<div>3: Output zone does not contain non-DNSSEC RRSet : NS, \\.all.rr.binary.org. 60 IN NS ns1.example.com.\000</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : TXT, selector._domainkey.all.rr.binary.org. 60 IN TXT "v=DKIM1; n=Use=20DKIM; p=AwEAAZfbYw8SffZwsbrCLbC+JLErREIF6Yfe9aqsa1Pz6tpGWiLxm9rSL6/YoBvNP3UWX91YDF0JMo6lhu3UIZjITvIwDhx+RJYko9vLzaaJKXGf3ygy6z+deWoZJAV1lTY0Ltx9genboe88CSCHw9aSLkh0obN9Ck8R6zAMYR19ciM/;
t=s"</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : SRV, _http._tcp.all.rr.binary.org. 60 IN SRV 0 5 80 ns1.example.com</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : MINFO, all.a{ll.all.rr.binary.org. 60 IN MINFO minfo-rmailbx.example.com minfo-emailbx.example.com</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : PTR, foo.all.rr.binary.org. 60 IN PTR \000\\.ns1.all.rr.org</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : CNAME, \032.foo\..all.rr.binary.org. 60 IN CNAME \\\\\..ns1.all.rr.org</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : DNAME, frobozz.all.rr.binary.org. 60 IN DNAME frobozz-division.acme.example</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : MB, nall.all.rr.binary.org. 60 IN MB mb-madname.\000.example.com</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : A, ns1\..all.rr.binary.org. 60 IN A 10.1.0.52</div>
<div>3: Output zone does not contain non-DNSSEC RRSet : DS, sub.all.rr.binary.org. 60 IN DS 12345 DSA 1 ( 123456789ABCDEF67890123456789ABCDEF67890 )</div>
<div> </div>
<div>So it looks to me that the problem is in dnsruby. We can have a release of RC3, but perhaps stating that the auditor has some problems with binary domain names.</div>
<div> </div>
<div>Or what do you say Matthijs?</div>
<div> </div>
<div>// Rickard</div>
<div> </div>
<div>-----BEGIN PGP SIGNATURE-----</div>
<div>Version: 9.8.3 (Build 4028)</div>
<div>Charset: utf-8</div>
<div> </div>
<div>wsBVAwUBS1gZb+CjgaNTdVjaAQgoKQf9Gb3y8lBkb+JnzviSWDY7aEUpgWlPU7wv</div>
<div>DqwqxfXvB4eXht/uVTze4f9lzNMSWEAwop2zxnGRinTJEutEbBWOi/ilfgxlPAZ9</div>
<div>M7FN6EeVa9ouNq89v6xX5O0EJwQOPuwN3dogTZA2IWkpnqy99gH1yAfOL9RBzDg/</div>
<div>h+hMQ/2HfctTxoJqdhAAhrb+rmsOP6JKogQXkPhX58Qp1T/pkPoXLYlPna/Jg+/l</div>
<div>Jo4/gMjmc56SzrqoevuQLhgmXP5/3PYr68uiyxxXD8gUTWCWdewilppzw6UCsc9G</div>
<div>HRw9EFS4JI/5oRow+JdLv6sSymRuoligAY0TzPOTeQUb8gmW9C3N1A==</div>
<div>=BfnZ</div>
<div>-----END PGP SIGNATURE-----</div>
<div> </div>
<div> </div>
</font>
</body>
</html>