Is there an easier way to update my signed zonefiles than having to do ldns-keygen -a RSASHA1_NSEC3 -b 1024 <domain> && ldns-keygen -a RSASHA1_NSEC3 -b 2048 -k <domain> && ldns-signzone <domain> <zone signing key> <key signing key> over and over?
Is there an easier way to update my signed zonefiles than having to do ldns-keygen -a RSASHA1_NSEC3 -b 1024 <domain> && ldns-keygen -a RSASHA1_NSEC3 -b 2048 -k <domain> && ldns-signzone <domain> <zone signing key> <key signing key> over and over?
Not in NSD, it does support in-line signing. So you need something else
to do the signing for you. You might be interested in OpenDNSSEC to the
the DNSSEC stuff for you:
Is there an easier way to update my signed zonefiles than having to do
ldns-keygen -a RSASHA1_NSEC3 -b 1024 <domain> && ldns-keygen -a
RSASHA1_NSEC3 -b 2048 -k <domain> && ldns-signzone <domain> <zone
signing key> <key signing key> over and over?
If you invoke `ldns-keygen` every time you change a zone file, you are
generating NEW keys at each run. I very much doubt you really want that,
as you'd have to submit your DS RRset to the parent zone each time!
I'm curious how everyone on this list sets up their NSD servers. Looking for interesting new ways to do things. Things I might have forgotten. Things I maybe shouldn't have added in the first place.