Strange results from dnssec-dsfromkey

I don't understand the results I am getting from dnssec-dsfromkey (BIND 9.6.0-P1, Solaris 10_x86, Sun Studio 10 C compiler). For instance: $ /usr/local/sbin/dnssec-keygen -a RSASHA1 -b 512 -n ZONE -f KSK test Ktest.+005+21283 $ cat Ktest.+005+21283.key test. IN DNSKEY 257 3 5 AwEAAbmcz5O8Azmbw

Abort in dig after zone transfer

In the mood for bug reporting now ... :-) Sometimes dig gets into some sort of mess after doing a zone transfer from certain hosts, e.g. $ dig +nocmd +nostats axfr dlv.isc.org @ns-int.isc.org >dlv.new The complete zone is written to the output file, perfectly correct, but dig then sits there

question about root-delegation-only exclude list

Should I be using the root-delegation-only with exlude list?I currently have root-delegation-only exclude { "ad"; "af"; "ar"; "biz"; "bs"; "cr"; "cu"; "de"; "dm"; "id"; "lu"; "lv"; "md"; "ms"; "museum"; "name"; "no"; "pa"; "pf"; "se"; "sr"; "to"; "tw"; "us"; "

Re: Strange results from dnssec-dsfromkey

Looks like a silly bug that will be simple to fix. In message , Chris Thompson writes: > I don't understand the results I am getting from dnssec-dsfromkey > (BIND 9.6.0-P1, Solaris 10_x86, Sun Studio 10 C compiler). > > For instance: > > $ /usr/local/sbin/dnssec-keygen -a RSASHA1 -b 51