uvok cheetahFeb 2
My #DNSSEC broke and I don't know why - I didn't change anything on #powerdns !!!
Show threaduvok cheetahFeb 2
Okay, apparently this is a problem with some secondaries not working as I would expect D:
Show threaduvok cheetahFeb 2

...
I am angry and confused!
And I'm not gonna fix this today, it's after 8 p.m.
I know better than to do some late night server admin stuff.

I'm interested in DNSSEC monitoring options, though. (Not willing to pay money).

Show threaduvok cheetahFeb 3
I *think* I can't recommend 1984.hosting for secondary DNS if you use DNSSEC at the moment.
It *appears to me* they don't replicate/refresh the RRSIGs.
So I **assume** they simply check the SOA serial and only fetch the data if it changed.
Show threaduvok cheetah
Since I'm already on this topic:
Reminder of an old blog post of mine:
Migrating DNS providers
https://blog.uvokchee.de/2025/01/migrating-dns-servers.html
Migrating DNS providers

An in-depth look into how to switch DNS providers without downtime.

Uvoks Blog
Feb 3 at 4:06pmWeb
Show threaduvok cheetahFeb 3

Don't you love it when #DENIC says "UPDATE FAILED", because you have to edit *your own zone's* NS entries *first*, and only then go to your registrar to edit the nameservers there.

I keep forgetting that,

#dns

Show threaduvok cheetahFeb 3
dnssec is fixed again!
it was indeed a malfunctioning secondary.