Every day I see a huge number of messages like in the subject, posted to syslog... a full example of a few lines from "logwatch" might help:
address not available resolving './DNSKEY/IN': 2001:500:2::c#53: 24 Time(s)
[...]
address not available resolving './NS/IN': 2001:500:2::c#53: 25 Time(s)
[...]
address not available resolving 'E.ROOT-SERVERS.NET/AAAA/IN': 2001:500:1::53#53: 5 Time(s)
[...]
address not available resolving 'G.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2::c#53: 1 Time(s)
What is causing this? And, what do I need to tweek to satisfy whatever is happening?
The confusing part, to me, is that these errors are logged even when no one is using the system except for a cloud backup that runs 24/7
The entries end with:
any newly configured zones are now loaded: 1 Time(s)
configuring command channel from '/etc/bind/rndc.key': 2 Time(s)
flushing caches in all views succeeded: 1 Time(s)
initializing GeoIP AS (type 9) DB: 1 Time(s)
initializing GeoIP City (IPv4) (type 2) DB: 1 Time(s)
initializing GeoIP Country (IPv4) (type 1) DB: 1 Time(s)
initializing GeoIP Country (IPv6) (type 12) DB: 1 Time(s)
managed-keys-zone: No DNSKEY RRSIGs found for '.': success: 1 Time(s)
managed-keys-zone: Unable to fetch DNSKEY set '.': SERVFAIL: 24 Time(s)
using built-in root key for view _default: 1 Time(s)
Scheduled Maintenance: We are aware of an issue with Google, AOL, and Yahoo services as email providers which are blocking new registrations. We are trying to fix the issue and we have several internal and external support tickets in process to resolve the issue. Please see: viewtopic.php?t=158230
address not available resolving './DNSKEY/IN':
address not available resolving './DNSKEY/IN':
4.19.0-9-amd64 #1 SMP Debian 4.19.118-2+deb10u1
CPU: AMD FX(tm)-8350 Eight-Core Processor
RAM: 32GB (8x8GB) DDR3 DRAM
Video: GeForce 8400 GS to VIZIO E320VA Monitor
CPU: AMD FX(tm)-8350 Eight-Core Processor
RAM: 32GB (8x8GB) DDR3 DRAM
Video: GeForce 8400 GS to VIZIO E320VA Monitor