-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm DNSSEC enabling the .ip6.arpa zone for my IPv6 allocation and
registering it with dlv.isc.org. Using bind-9.7.0-p2 dnssec tools.
Everything seems to be working well, but when I test using the Sandia
Labs dnsviz.net tool I get inconsistent
On Jun 2 2010, Matthew Seaman wrote:
I'm DNSSEC enabling the .ip6.arpa zone for my IPv6 allocation and
registering it with dlv.isc.org. Using bind-9.7.0-p2 dnssec tools.
Everything seems to be working well, but when I test using the Sandia
Labs dnsviz.net tool I get inconsistent results.
My
On Wed, Jun 2, 2010 at 8:40 AM, Paul Vixie vi...@isc.org wrote:
Chris Thompson c...@cam.ac.uk writes:
Nothing that I can see. Maybe dnsviz can't cope with multiple PTR
records in an RRset, as your first case has? (On the other hand it
handles multiple A records in forward zones OK.)
to
On Wed, Jun 2, 2010 at 7:44 AM, Chris Thompson c...@cam.ac.uk wrote:
On Jun 2 2010, Matthew Seaman wrote:
I'm DNSSEC enabling the .ip6.arpa zone for my IPv6 allocation and
registering it with dlv.isc.org. Using bind-9.7.0-p2 dnssec tools.
Everything seems to be working well, but when I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 02/06/2010 18:49:44, Casey Deccio wrote:
This has been fixed. The problem had to do with establishing a canonical
ordering of RRs within an RRset for the purposes of verifying an RRSIG.
dnspython's default comparison operators don't follow
5 matches
Mail list logo