NSEC3: verify rdataset
(keyid=47948): You must use the keyboard to create entropy, since
your system is lacking
/dev/random (or equivalent)
Linh Khuu
-Original Message-
From: Warren Kumari [mailto:war...@kumari.net]
Sent: Tuesday, April 13, 2010 3:43 PM
To: Khuu, Linh MicroTech
Cc
I just turned on the dnssec-validation today, and I saw lots of messages:
13-Apr-2010 15:17:17.122 dnssec: debug 3: validating @202be918:
3e77469i48du24agcu5ftfumd6iocmrk.org NSEC3: verify rdataset (keyid=47948): You
must use the keyboard to create entropy, since your system is lacking
Thanks Stephane!!! Adding ::1 in the ACL did the trick.
Linh Khuu
-Original Message-
From: Stephane Bortzmeyer [mailto:bortzme...@nic.fr]
Sent: Thursday, February 25, 2010 11:09 AM
To: Khuu, Linh MicroTech
Cc: 'bind-users@lists.isc.org'
Subject: Re: Question about dig command
On Thu
Hi,
I have question about “dig” command in IPV6.
I have bind-9.6.1-P3 compiled with ipv6 enable. So far it’s running great. But
when I use the “dig” command from 9.6.1-P3, I get the following error when
query record:
client ::1#33086: query (cache) 'dnssec12.datamtn.com//IN' denied
Hi,
I have question about the DNSSEC NS record.
We have the parent zone, for example, example.net being signed with DNSSEC. We
have a child zone test.example.net delegating to glbl.example.net as NS record.
glbl.example.net is not a DNSSEC. Will nslookup for anything in
test.example.net fail?
5 matches
Mail list logo