On Thu, 13 Jan 2011, Mark Andrews wrote:
dnssec-signzone uses multiple threads to sign the zone a node at a
time. These work items finish in a non-deterministic manner leading
to a different order in the resulting text file being produced.
This is done after the zone was sorted to generate the
In message , Paul Wou
ters writes:
> On Wed, 12 Jan 2011, Mark Elkins wrote:
>
> > dnssec-signzone -3 "abcd" -o example.com -p -t -A -d keyset -g -a -N
> > increment -s 2011061553 -e 20110210161553 -f example.com.sign-1
> > example.com.signed
> >
> > A minute later - I run the same command -
On 01/12/11 17:58, Mark Elkins wrote:
> Still playing with DNSSEC and signing zones.
>
> I'm resigning an already signed zone.
>
> I'm doing this on a hyper-threaded 4-core i7 (Intel(R) Core(TM) i7 CPU
> 920 @ 2.67GHz) which under linux gives me 8 cores.
>
> I'm using the command:
>
> dnssec-si
On Wed, 12 Jan 2011, Mark Elkins wrote:
dnssec-signzone -3 "abcd" -o example.com -p -t -A -d keyset -g -a -N
increment -s 2011061553 -e 20110210161553 -f example.com.sign-1
example.com.signed
A minute later - I run the same command - but output to a different
file... -f example.com.sign-
Still playing with DNSSEC and signing zones.
I'm resigning an already signed zone.
I'm doing this on a hyper-threaded 4-core i7 (Intel(R) Core(TM) i7 CPU
920 @ 2.67GHz) which under linux gives me 8 cores.
I'm using the command:
dnssec-signzone -3 "abcd" -o example.com -p -t -A -d keyset -g -a
5 matches
Mail list logo