Re: non-working DNSSEC after network outage

Ondřej Surý <[email protected]>
Newsgroups gmane.network.dns.bind.user
Message-ID <[email protected]>
Hi,

lets start with basics - what version of BIND 9 are you running?

Ondrej
--
Ondřej Surý (He/Him)
[email protected]

ADHD brain at work: I sometimes lose track of my inbox. Please feel free to send a gentle nudge if you're waiting on a reply!

My working hours and your working hours may be different. Please do not feel obligated to reply outside your normal working hours.

> On 20. 8. 2026, at 20:25, Marco Moock <[email protected]> wrote:
> Hello!
> 
> Yesterday I had a power outage and the server running named was online before the internet connection was, so it tried to resolve queries, but failed.
> 
> This led to messages like
> 
> [794]: no valid RRSIG resolving './DNSKEY/IN': 2001:500:a8::e#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 2001:500:1::53#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 202.12.27.33#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 192.58.128.30#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 192.33.4.12#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 192.5.5.241#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 192.203.230.10#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 198.41.0.4#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 192.36.148.17#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 170.247.170.2#53
> [794]: no valid RRSIG resolving './DNSKEY/IN': 199.7.91.13#53
> 
> And they were cached until I restarted named, as no queries were answered anymore.
> 
> Is that intended behavior and how can I change this?
> 
> --
> kind regards
> Marco
> 
> Junk-Mail bitte an [email protected]
> 
> --
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.
> <OpenPGP_signature.asc>

-- 
Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.