[update, solved] It was apparmor, which was lying about being inactive. Ubuntu’s default profile denies bind write access to its config directory. Needed to add /etc/bind/dnskeys/** rw, reload apparmor, and it’s all good.
Trying to switch my internal domain from auto-dnssec maintain to dnssec-policy default. Zone is signed but not secure and logs are full of
zone_rekey:dns_dnssec_keymgr failed: error occurred writing key to disk
key-directory is /etc/bind/dnskeys, owned bind:bind, and named runs as bind
I’ve set every directory I could think of to 777: /etc/bind, /etc/bind/dnskeys, /var/lib/bind, /var/cache/bind, /var/log/bind. I disabled apparmor, in case it was blocking.
A signed zone file appears, but I can’t dig any DNSKEYs or RRSIGs. named-checkzone says there’s nsec records in the signed file, so something is happening, but I’m guessing it all stops when keymgr fails to write the key.
I tried manually generating a key and sticking it in dnskeys, but this doesn’t appear to be used.
I’d tried that…this has been going on for five days, and I can not describe my level of frustration. But I solved it, literally just now.
Despite
systemctl status apparmor.serviceclaiming it was inactive, it was secretly active. audit.log was so full of sudo that I failed to see all of theThat made me realize, when I thought I fixed the apparmor rule, I’d used
/etc/bind/dnskey/ rwinstead of/etc/bind/dnskey/** rwThe bind manual claims that you don’t need to manually create keys or manually include them in your zone file, if you use
dnssec-policy defaultor presumably any other policy with inline-signing. Claims that bind will generate its own keys, write them, and even manage timed rotation or migration to a new policy. I can’t confirm or deny that, because it definitely found the keys I had manually created (one of which was $INCLUDEd in the zone file, and one not) and used them. It also edited them and created .state files.I feel like I should take the rest of the day off and celebrate.