BIND 9.21.20: DNS Error Reporting Logging and Resolver IP Addresses
Scott Hollenbeck
sah at sahollenbeck.com
Tue May 5 11:36:21 UTC 2026
> -----Original Message-----
> From: bind-users <bind-users-bounces at lists.isc.org> On Behalf Of Petr
> Špacek
> Sent: Tuesday, May 5, 2026 4:58 AM
> To: bind-users at lists.isc.org
> Subject: Re: BIND 9.21.20: DNS Error Reporting Logging and Resolver IP
> Addresses
>
> On 02. 05. 26 17:22, Scott Hollenbeck via bind-users wrote:
> > I've recently been experimenting with the DNS error reporting features in
> > BIND 9.21.20. I've noticed that when a monitoring agent logs a received
> > error report, the log entry doesn't include the IP address of the resolver
> > that sent the report. Is this by design? If so, is it something that might
> > be added in the future? My logging config looks like this:
> >
> > logging {
> > channel error_reporting {
> > file "/var/log/named/agent.log" versions 30 size 25k;
> > severity info;
> > print-time iso8601-utc;
> > };
> > channel query_log {
> > file "/var/log/named/query.log" versions 30 size 25k;
> > severity info;
> > print-time iso8601-utc;
> > print-category yes;
> > print-severity yes;
> > };
> > category default { default_syslog; default_debug; };
> > category dns-reporting-agent { error_reporting; };
> > category queries { query_log; };
> > category unmatched { null; };
> > };
>
> Hello Scott.
>
> I think most likely explanation is nobody is using this feature for any
> real analysis work - nobody noticed.
>
> We are currently stretched pretty thin. I suggest you open support
> ticket if you are a support customer, or open a public issue in case you
> are not.
>
> That way it will be at least tracked.
[SAH] Thanks, Petr. I'll open a public issue.
Scott
More information about the bind-users
mailing list