I had to modify my default BIND options to disable DNSSEC:
options {
dnssec-enable no;
dnssec-validation no;I think it’s a dead tech.
This dnssec/ntp dependency loop is absurd, and it is incomprehensible that ntp/dns can break this way.
Both show how silly it all is, IMO.
In fact, I run my own private Internet complete with DNSSEC for my white lab.
I used Bind v9.16+ and wrote some bash tools to generate in a flexible manner the named configuration files.
Can generate private root servers, private TLD, split-horizon, bastion, and hidden-master.
Adding DNSSEC to a domain name is more work. You need a registrar that support it, and then depending on what DNS server program you are running you might need to install a signer, a key storage, monitoring and scripts that talks between the different parts of the chain. I have heard that the latest version of bind might now ship with all the required parts built in, but I have yet to test it. It a bit far yet from simply uncommenting an option, and the protocols for talking with registrars is being actively discussed and worked on during technical conferences.
There are tools to automate resigning, but personally I just do it manually once a year for fun.
Sure, fixing that squeaky door is "easy," but have you ever heard the adage that every home project involves three trips to the hardware store? There may be technical aspects that few of us can implement from scratch and on the first try, but at the same time I also don't know how to build a good broom. These concerns are not insurmountable, especially with the network effects of people being in the same boat. How easy is it to find a good handyman without asking anybody? You don't have to.