[Eisfair] bind9 - dnssec Fehler

[Stephan Manske]

Hi!

nachdem ich mein eigentliches Problem mit dem nicht auflösenden bind 
lösen konnte (BIND9_ALLOW_QUERY=any) bleiben dennoch diese Meldungen im 
logfile. Soll das so sein!?

Können andere Nutzer mal in /var/lib/named/log/named.log nachgucken?

11-Aug-2020 17:49:57.119 lame-servers: no valid RRSIG resolving 
'forter.com/DS/IN': 83.169.184.98#53
11-Aug-2020 17:49:58.707 lame-servers: timed out resolving 
'3.6.c.f.a.9.e.f.f.f.5.7.6.9.a.a.8.d.6.0.0.0.4.8.9.0.1.8.2.0.a.2.ip6.arpa/PTR/IN': 
83.169.184.98#53
11-Aug-2020 17:49:59.136 lame-servers: no valid RRSIG resolving 
'ip6.arpa/DS/IN': 83.169.184.98#53
11-Aug-2020 17:49:59.180 lame-servers: no valid RRSIG resolving 
'ip6.arpa/DS/IN': 83.169.184.34#53
11-Aug-2020 17:49:59.236 dnssec:   validating ip6.arpa/SOA: got insecure 
response; parent indicates it should be secure
11-Aug-2020 17:49:59.236 lame-servers: no valid RRSIG resolving 
'2.ip6.arpa/DS/IN': 83.169.184.98#53
11-Aug-2020 17:49:59.592 dnssec:   validating ip6.arpa/SOA: got insecure 
response; parent indicates it should be secure
11-Aug-2020 17:49:59.592 lame-servers: no valid RRSIG resolving 
'2.ip6.arpa/DS/IN': 83.169.184.34#53
11-Aug-2020 17:50:00.660 dnssec: validating ip6.arpa/DNSKEY: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:00.660 lame-servers: insecurity proof failed resolving 
'ip6.arpa/DNSKEY/IN': 83.169.184.98#53
11-Aug-2020 17:50:00.684 dnssec: validating ip6.arpa/DNSKEY: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:00.684 lame-servers: insecurity proof failed resolving 
'ip6.arpa/DNSKEY/IN': 83.169.184.34#53
11-Aug-2020 17:50:01.304 dnssec:   validating ip6.arpa/SOA: got insecure 
response; parent indicates it should be secure
11-Aug-2020 17:50:01.304 lame-servers: no valid RRSIG resolving 
'a.2.ip6.arpa/DS/IN': 83.169.184.98#53
11-Aug-2020 17:50:01.332 dnssec:   validating ip6.arpa/SOA: got insecure 
response; parent indicates it should be secure
11-Aug-2020 17:50:01.332 lame-servers: no valid RRSIG resolving 
'a.2.ip6.arpa/DS/IN': 83.169.184.34#53
11-Aug-2020 17:50:01.384 lame-servers: no valid RRSIG resolving 
'0.a.2.ip6.arpa/DS/IN': 83.169.184.98#53
11-Aug-2020 17:50:01.412 lame-servers: no valid RRSIG resolving 
'0.a.2.ip6.arpa/DS/IN': 83.169.184.34#53
11-Aug-2020 17:50:01.652 dnssec:   validating 0.a.2.ip6.arpa/SOA: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:01.652 lame-servers: no valid RRSIG resolving 
'2.0.a.2.ip6.arpa/DS/IN': 83.169.184.98#53
11-Aug-2020 17:50:01.756 dnssec:   validating 0.a.2.ip6.arpa/SOA: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:01.756 lame-servers: no valid RRSIG resolving 
'2.0.a.2.ip6.arpa/DS/IN': 83.169.184.34#53
11-Aug-2020 17:50:02.068 dnssec: validating 0.a.2.ip6.arpa/DNSKEY: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:02.068 lame-servers: insecurity proof failed resolving 
'0.a.2.ip6.arpa/DNSKEY/IN': 83.169.184.98#53
11-Aug-2020 17:50:02.100 dnssec: validating 0.a.2.ip6.arpa/DNSKEY: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:02.100 lame-servers: insecurity proof failed resolving 
'0.a.2.ip6.arpa/DNSKEY/IN': 83.169.184.34#53
11-Aug-2020 17:50:04.060 dnssec:   validating 0.a.2.ip6.arpa/SOA: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:04.060 lame-servers: no valid RRSIG resolving 
'8.2.0.a.2.ip6.arpa/DS/IN': 83.169.184.98#53
11-Aug-2020 17:50:04.088 dnssec:   validating 0.a.2.ip6.arpa/SOA: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:04.088 lame-servers: no valid RRSIG resolving 
'8.2.0.a.2.ip6.arpa/DS/IN': 83.169.184.34#53
11-Aug-2020 17:50:05.140 dnssec:   validating 0.a.2.ip6.arpa/SOA: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:05.140 lame-servers: no valid RRSIG resolving 
'1.8.2.0.a.2.ip6.arpa/DS/IN': 83.169.184.98#53
11-Aug-2020 17:50:05.176 dnssec:   validating 0.a.2.ip6.arpa/SOA: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:05.176 lame-servers: no valid RRSIG resolving 
'1.8.2.0.a.2.ip6.arpa/DS/IN': 83.169.184.34#53
11-Aug-2020 17:50:05.228 dnssec:   validating 0.a.2.ip6.arpa/SOA: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:05.228 lame-servers: no valid RRSIG resolving 
'0.1.8.2.0.a.2.ip6.arpa/DS/IN': 83.169.184.34#53
11-Aug-2020 17:50:05.372 dnssec:   validating 0.a.2.ip6.arpa/SOA: got 
insecure response; parent indicates it should be secure
11-Aug-2020 17:50:05.372 lame-servers: no valid RRSIG resolving 
'0.1.8.2.0.a.2.ip6.arpa/DS/IN': 83.169.184.98#53
11-Aug-2020 17:51:47.682 dnssec:   validating net/SOA: got insecure 
response; parent indicates it should be secure
11-Aug-2020 17:51:47.682 lame-servers: no valid RRSIG resolving 
'footprint.net/DS/IN': 83.169.184.98#53
11-Aug-2020 17:51:47.702 dnssec:   validating net/SOA: got insecure 
response; parent indicates it should be secure
11-Aug-2020 17:51:47.702 lame-servers: no valid RRSIG resolving 
'footprint.net/DS/IN': 83.169.184.34#53
11-Aug-2020 17:52:54.990 dnssec:   validating com/SOA: got insecure 
response; parent indicates it should be secure
11-Aug-2020 17:52:54.990 lame-servers: no valid RRSIG resolving 
'google.com/DS/IN': 83.169.184.98#53
11-Aug-2020 17:52:55.046 dnssec:   validating com/SOA: got insecure 
response; parent indicates it should be secure
11-Aug-2020 17:52:55.046 lame-servers: no valid RRSIG resolving 
'google.com/DS/IN': 83.169.184.34#53
11-Aug-2020 17:52:55.214 dnssec:   validating com/SOA: got insecure 
response; parent indicates it should be secure