Re: Nice new logging feature
> On 20 Dec 2021, at 17:56, Reindl Harald wrote: > > > > Am 20.12.21 um 17:53 schrieb Petr Menšík: >> sure I confused that. I read it wrong way and thought they are present >> on *BSD but not on Fedora. I know some messages are removed in Fedora >> builds. I apologize for a confusion. Nobody complained on Fedora builds, >> that is a good message to me. > > OP was "I am trying 9.17 at home and I just noticed a very useful new > lame-servers log message: 2021-12-16T08:08:20.505Z lame-servers: timed out > resolving ’stupiddomain.com/ANY/IN': X.Y.Z.T#53. I haven’t seen this on 9.16" > > i looked at my Fedora lame-log and answered with "exists in 9.16 here and i > doubt Fedora has backports for this" Old thread, I know. The differente is just that 9.16 doesn´t log timeouts in the lame-server category. All of the rest do work, like unreachable or connection refused. 9.17 does log timeouts which is very useful. Borja. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Nice new logging feature
Am 20.12.21 um 17:53 schrieb Petr Menšík:
sure I confused that. I read it wrong way and thought they are present
on *BSD but not on Fedora. I know some messages are removed in Fedora
builds. I apologize for a confusion. Nobody complained on Fedora builds,
that is a good message to me.
OP was "I am trying 9.17 at home and I just noticed a very useful new
lame-servers log message: 2021-12-16T08:08:20.505Z lame-servers: timed
out resolving ’stupiddomain.com/ANY/IN': X.Y.Z.T#53. I haven’t seen this
on 9.16"
i looked at my Fedora lame-log and answered with "exists in 9.16 here
and i doubt Fedora has backports for this"
On 12/20/21 17:39, Reindl Harald wrote:
Am 20.12.21 um 17:32 schrieb Petr Menšík:
Hi Borja,
In fact there is ancient patch [1] still applied to Fedora builds, which
hides some lame servers warnings. It makes some lame servers category
logs as debug only, shown only when -d 1 option is used.
I was thinking about removing this change some time ago and replace it
with just configuration snippet dropping lame servers message if needed.
But no one complained for years. If you think those messages should be
available, please fill bug on Red Hat Bugzilla [2], bind component.
I have minimized changes to BIND done for Fedora, but this one remained
due lack of feedback. I think configuration example to hide lame servers
messages might be more appropriate, because it would allow changes
without recompilation, just with simple configuration change. Current
builds cannot enable without debug level 1 I am afraid.
you confused something!
Borja don't have that in older named versions and does not use Fedora,
i have them on Fedora as you see in my quote and it's not about the
messsages as such but about "45.79.19.196#53" at the end of lame-logs
maybe because of my logging configuration which is unchanged for years
logging
{
channel default_log
{
file "data/named.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
channel transfer_log
{
file "data/transfer.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
channel rate_limit_log
{
file "data/rate_limit.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
channel lame_servers_log
{
file "data/lame_servers.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
channel query_errors_log
{
file "data/query_errors.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
category default {default_log;};
category resolver {default_log;};
category security {default_log;};
category xfer-in {transfer_log;};
category xfer-out {transfer_log;};
category config {default_log;};
category queries {default_log;};
category notify {default_log;};
category database {default_log;};
category rate-limit {rate_limit_log;};
category lame-servers {lame_servers_log;};
category query-errors {query_errors_log;};
};
On 12/16/21 13:15, Reindl Harald wrote:
Am 16.12.21 um 10:02 schrieb Borja Marcos:
Hi,
I am trying 9.17 at home and I just noticed a very useful new
lame-servers log message:
2021-12-16T08:08:20.505Z lame-servers: timed out resolving
’stupiddomain.com/ANY/IN': X.Y.Z.T#53
I haven’t seen this on 9.16. Are there any plans to include it?
bind-9.16.23-1.fc34.x86_64
16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving
'ns2.serverion.eu/A/IN': 94.228.210.122#53
16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving
'250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53
16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving
'250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53
16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53
16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53
16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53
16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53
16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53
16-Dec-2021 13:12:46.937 lame-servers: connection refused resolving
'mx4.itronic.at/A/IN': 85.124.85.125#53
16-Dec-2021 13:13:41.202 lame-servers: host unreachable resolving
'70.84.141.45.in-addr.arpa/PTR/IN': 72.14.185.43#53
16-Dec-2021 13:13:45.334 lame-servers: host unreachable resolving
'70.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53
Re: Nice new logging feature
Oh, Hi Reindl,
sure I confused that. I read it wrong way and thought they are present
on *BSD but not on Fedora. I know some messages are removed in Fedora
builds. I apologize for a confusion. Nobody complained on Fedora builds,
that is a good message to me.
Thanks!
Merry Christmas folks.
On 12/20/21 17:39, Reindl Harald wrote:
>
>
> Am 20.12.21 um 17:32 schrieb Petr Menšík:
>> Hi Borja,
>>
>> In fact there is ancient patch [1] still applied to Fedora builds, which
>> hides some lame servers warnings. It makes some lame servers category
>> logs as debug only, shown only when -d 1 option is used.
>>
>> I was thinking about removing this change some time ago and replace it
>> with just configuration snippet dropping lame servers message if needed.
>> But no one complained for years. If you think those messages should be
>> available, please fill bug on Red Hat Bugzilla [2], bind component.
>>
>> I have minimized changes to BIND done for Fedora, but this one remained
>> due lack of feedback. I think configuration example to hide lame servers
>> messages might be more appropriate, because it would allow changes
>> without recompilation, just with simple configuration change. Current
>> builds cannot enable without debug level 1 I am afraid.
>
> you confused something!
>
> Borja don't have that in older named versions and does not use Fedora,
> i have them on Fedora as you see in my quote and it's not about the
> messsages as such but about "45.79.19.196#53" at the end of lame-logs
>
> maybe because of my logging configuration which is unchanged for years
>
> logging
> {
> channel default_log
> {
> file "data/named.log" versions 0 size 1m;
> severity dynamic;
> print-time yes;
> print-category yes;
> };
> channel transfer_log
> {
> file "data/transfer.log" versions 0 size 1m;
> severity dynamic;
> print-time yes;
> print-category yes;
> };
> channel rate_limit_log
> {
> file "data/rate_limit.log" versions 0 size 1m;
> severity dynamic;
> print-time yes;
> print-category yes;
> };
> channel lame_servers_log
> {
> file "data/lame_servers.log" versions 0 size 1m;
> severity dynamic;
> print-time yes;
> print-category yes;
> };
> channel query_errors_log
> {
> file "data/query_errors.log" versions 0 size 1m;
> severity dynamic;
> print-time yes;
> print-category yes;
> };
> category default {default_log;};
> category resolver {default_log;};
> category security {default_log;};
> category xfer-in {transfer_log;};
> category xfer-out {transfer_log;};
> category config {default_log;};
> category queries {default_log;};
> category notify {default_log;};
> category database {default_log;};
> category rate-limit {rate_limit_log;};
> category lame-servers {lame_servers_log;};
> category query-errors {query_errors_log;};
> };
>
>> On 12/16/21 13:15, Reindl Harald wrote:
>>>
>>>
>>> Am 16.12.21 um 10:02 schrieb Borja Marcos:
Hi,
I am trying 9.17 at home and I just noticed a very useful new
lame-servers log message:
2021-12-16T08:08:20.505Z lame-servers: timed out resolving
’stupiddomain.com/ANY/IN': X.Y.Z.T#53
I haven’t seen this on 9.16. Are there any plans to include it?
>>>
>>> bind-9.16.23-1.fc34.x86_64
>>>
>>> 16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving
>>> 'ns2.serverion.eu/A/IN': 94.228.210.122#53
>>> 16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving
>>> '250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53
>>> 16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving
>>> '250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53
>>> 16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving
>>> '166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53
>>> 16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving
>>> '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53
>>> 16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving
>>> '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53
>>> 16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving
>>> '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53
>>> 16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving
>>> '166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53
>>> 16-Dec-2021 13:12:46.937 lame-servers: connection refused resolving
>>> 'mx4.itronic.at/A/IN': 85.124.85.125#53
>>> 16-Dec-2021 13:13:41.202 lame-servers: host unreachable resolving
>>> '70.84.141.45.in-addr.arpa/PTR/IN': 72.14.185.43#53
>>> 16-Dec-2021 13:13:45.334 lame-servers: host unreachable resolving
>>> '70.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53
>>> 16-Dec-2021 13:13:46.953 lame-servers: REFUSED unexpected RCODE
>>> resolving
Re: Nice new logging feature
Am 20.12.21 um 17:32 schrieb Petr Menšík:
Hi Borja,
In fact there is ancient patch [1] still applied to Fedora builds, which
hides some lame servers warnings. It makes some lame servers category
logs as debug only, shown only when -d 1 option is used.
I was thinking about removing this change some time ago and replace it
with just configuration snippet dropping lame servers message if needed.
But no one complained for years. If you think those messages should be
available, please fill bug on Red Hat Bugzilla [2], bind component.
I have minimized changes to BIND done for Fedora, but this one remained
due lack of feedback. I think configuration example to hide lame servers
messages might be more appropriate, because it would allow changes
without recompilation, just with simple configuration change. Current
builds cannot enable without debug level 1 I am afraid.
you confused something!
Borja don't have that in older named versions and does not use Fedora, i
have them on Fedora as you see in my quote and it's not about the
messsages as such but about "45.79.19.196#53" at the end of lame-logs
maybe because of my logging configuration which is unchanged for years
logging
{
channel default_log
{
file "data/named.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
channel transfer_log
{
file "data/transfer.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
channel rate_limit_log
{
file "data/rate_limit.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
channel lame_servers_log
{
file "data/lame_servers.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
channel query_errors_log
{
file "data/query_errors.log" versions 0 size 1m;
severity dynamic;
print-time yes;
print-category yes;
};
category default {default_log;};
category resolver {default_log;};
category security {default_log;};
category xfer-in {transfer_log;};
category xfer-out {transfer_log;};
category config {default_log;};
category queries {default_log;};
category notify {default_log;};
category database {default_log;};
category rate-limit {rate_limit_log;};
category lame-servers {lame_servers_log;};
category query-errors {query_errors_log;};
};
On 12/16/21 13:15, Reindl Harald wrote:
Am 16.12.21 um 10:02 schrieb Borja Marcos:
Hi,
I am trying 9.17 at home and I just noticed a very useful new
lame-servers log message:
2021-12-16T08:08:20.505Z lame-servers: timed out resolving
’stupiddomain.com/ANY/IN': X.Y.Z.T#53
I haven’t seen this on 9.16. Are there any plans to include it?
bind-9.16.23-1.fc34.x86_64
16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving
'ns2.serverion.eu/A/IN': 94.228.210.122#53
16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving
'250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53
16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving
'250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53
16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53
16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53
16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53
16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53
16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53
16-Dec-2021 13:12:46.937 lame-servers: connection refused resolving
'mx4.itronic.at/A/IN': 85.124.85.125#53
16-Dec-2021 13:13:41.202 lame-servers: host unreachable resolving
'70.84.141.45.in-addr.arpa/PTR/IN': 72.14.185.43#53
16-Dec-2021 13:13:45.334 lame-servers: host unreachable resolving
'70.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53
16-Dec-2021 13:13:46.953 lame-servers: REFUSED unexpected RCODE
resolving '_.93.226.171.in-addr.arpa/A/IN': 203.113.131.1#53
16-Dec-2021 13:13:47.315 lame-servers: FORMERR resolving
'_.93.226.171.in-addr.arpa/A/IN': 203.113.188.2#53
16-Dec-2021 13:13:47.601 lame-servers: REFUSED unexpected RCODE
resolving '110.93.226.171.in-addr.arpa/PTR/IN': 203.113.131.1#53
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
Re: Nice new logging feature
Hi Borja, In fact there is ancient patch [1] still applied to Fedora builds, which hides some lame servers warnings. It makes some lame servers category logs as debug only, shown only when -d 1 option is used. I was thinking about removing this change some time ago and replace it with just configuration snippet dropping lame servers message if needed. But no one complained for years. If you think those messages should be available, please fill bug on Red Hat Bugzilla [2], bind component. I have minimized changes to BIND done for Fedora, but this one remained due lack of feedback. I think configuration example to hide lame servers messages might be more appropriate, because it would allow changes without recompilation, just with simple configuration change. Current builds cannot enable without debug level 1 I am afraid. Cheers, Petr 1. https://src.fedoraproject.org/rpms/bind/blob/rawhide/f/bind97-rh645544.patch 2. https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora On 12/16/21 13:15, Reindl Harald wrote: > > > Am 16.12.21 um 10:02 schrieb Borja Marcos: >> >> Hi, >> >> I am trying 9.17 at home and I just noticed a very useful new >> lame-servers log message: >> >> 2021-12-16T08:08:20.505Z lame-servers: timed out resolving >> ’stupiddomain.com/ANY/IN': X.Y.Z.T#53 >> >> I haven’t seen this on 9.16. Are there any plans to include it? > > bind-9.16.23-1.fc34.x86_64 > > 16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving > 'ns2.serverion.eu/A/IN': 94.228.210.122#53 > 16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving > '250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53 > 16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving > '250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 > 16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53 > 16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53 > 16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53 > 16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53 > 16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 > 16-Dec-2021 13:12:46.937 lame-servers: connection refused resolving > 'mx4.itronic.at/A/IN': 85.124.85.125#53 > 16-Dec-2021 13:13:41.202 lame-servers: host unreachable resolving > '70.84.141.45.in-addr.arpa/PTR/IN': 72.14.185.43#53 > 16-Dec-2021 13:13:45.334 lame-servers: host unreachable resolving > '70.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53 > 16-Dec-2021 13:13:46.953 lame-servers: REFUSED unexpected RCODE > resolving '_.93.226.171.in-addr.arpa/A/IN': 203.113.131.1#53 > 16-Dec-2021 13:13:47.315 lame-servers: FORMERR resolving > '_.93.226.171.in-addr.arpa/A/IN': 203.113.188.2#53 > 16-Dec-2021 13:13:47.601 lame-servers: REFUSED unexpected RCODE > resolving '110.93.226.171.in-addr.arpa/PTR/IN': 203.113.131.1#53 > ___ > Please visit https://lists.isc.org/mailman/listinfo/bind-users to > unsubscribe from this list > > ISC funds the development of this software with paid support > subscriptions. Contact us at https://www.isc.org/contact/ for more > information. > > > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users -- Petr Menšík Software Engineer Red Hat, http://www.redhat.com/ email: pemen...@redhat.com PGP: DFCF908DB7C87E8E529925BC4931CA5B6C9FC5CB ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Nice new logging feature
On 12/16/21 06:42, Borja Marcos wrote:
On 16 Dec 2021, at 14:55, Reindl Harald wrote:
Am 16.12.21 um 14:49 schrieb Borja Marcos:
bind-9.16.23-1.fc34.x86_64
16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving
'ns2.serverion.eu/A/IN': 94.228.210.122#53
16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving
'250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53
16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving
'250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53
16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53
16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53
16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53
16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53
16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving
'166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53
Not for me definitely, but I am not running Linux. This is a FreeBSD port of
the ISC release.
Does that version include some back ported code from bind 9.17?
i doubt that Fedora does any functional patching, maybe some of the build flags
while i'm not sure if the stuff shown at startup is really all
Hmm. Doesn’t look like that, I have compared the build options and it doesn’t
explain it.
I can confirm the same logs are appearing in my 'lamers.log' file on a
FreeBSD 12.2 system running BIND 9.16.22 (about to be upgraded). Maybe
your `logging {}` stanza is missing the appropriate incantation?
Mine are fairly plain:
[...]
channel lamers {
file "/var/log/named/lamers.log" versions 9;
print-time yes;
};
[...]
category lame-servers { lamers; };
[...]
michael
___
Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
from this list
ISC funds the development of this software with paid support subscriptions.
Contact us at https://www.isc.org/contact/ for more information.
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: Nice new logging feature
> On 16 Dec 2021, at 14:55, Reindl Harald wrote: > > > > Am 16.12.21 um 14:49 schrieb Borja Marcos: >>> >>> bind-9.16.23-1.fc34.x86_64 >>> >>> 16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving >>> 'ns2.serverion.eu/A/IN': 94.228.210.122#53 >>> 16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving >>> '250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53 >>> 16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving >>> '250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 >>> 16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving >>> '166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53 >>> 16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving >>> '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53 >>> 16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving >>> '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53 >>> 16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving >>> '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53 >>> 16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving >>> '166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 >> Not for me definitely, but I am not running Linux. This is a FreeBSD port of >> the ISC release. >> Does that version include some back ported code from bind 9.17? > > i doubt that Fedora does any functional patching, maybe some of the build > flags while i'm not sure if the stuff shown at startup is really all Hmm. Doesn’t look like that, I have compared the build options and it doesn’t explain it. Thanks! Borja. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Nice new logging feature
Am 16.12.21 um 14:49 schrieb Borja Marcos: On 16 Dec 2021, at 13:15, Reindl Harald wrote: Am 16.12.21 um 10:02 schrieb Borja Marcos: Hi, I am trying 9.17 at home and I just noticed a very useful new lame-servers log message: 2021-12-16T08:08:20.505Z lame-servers: timed out resolving ’stupiddomain.com/ANY/IN': X.Y.Z.T#53 I haven’t seen this on 9.16. Are there any plans to include it? bind-9.16.23-1.fc34.x86_64 16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving 'ns2.serverion.eu/A/IN': 94.228.210.122#53 16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving '250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53 16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving '250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53 16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53 16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53 16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53 16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 Not for me definitely, but I am not running Linux. This is a FreeBSD port of the ISC release. Does that version include some back ported code from bind 9.17? i doubt that Fedora does any functional patching, maybe some of the build flags while i'm not sure if the stuff shown at startup is really all Dec 16 14:51:56 srv-rhsoft named[352730]: built with '--build=x86_64-redhat-linux-gnu' '--host=x86_64-redhat-linux-gnu' '--program-prefix=' '--disable-dependency-tracking' '--prefix=/usr' '--exec-prefix=/usr' '--bindir=/usr/bin' '--sbindir=/usr/sbin' '--sysconfdir=/etc' '--datadir=/usr/share' '--includedir=/usr/include' '--libdir=/usr/lib64' '--libexecdir=/usr/libexec' '--sharedstatedir=/var/lib' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--with-python=/usr/bin/python3' '--with-libtool' '--localstatedir=/var' '--with-pic' '--disable-static' '--includedir=/usr/include/bind9' '--with-tuning=large' '--with-libidn2' '--with-maxminddb' '--enable-native-pkcs11' '--with-pkcs11=/usr/lib64/pkcs11/libsofthsm2.so' '--with-dlopen=yes' '--with-gssapi=yes' '--with-lmdb=yes' '--without-libjson' '--with-json-c' '--enable-dnstap' '--enable-fixed-rrset' '--enable-full-report' 'build_alias=x86_64-redhat-linux-gnu' 'host_alias=x86_64-redhat-linux-gnu' 'CC=gcc' 'CFLAGS= -O2 -flto=auto -ffat-lto-objects -fexceptions -g -grecord-gcc-switches -pipe -Wall -Werror=format-security -Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS -specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong -specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic -fasynchronous-unwind-tables -fstack-clash-protection -fcf-protection' 'LDFLAGS=-Wl,-z,relro -Wl,--as-needed -Wl,-z,now -specs=/usr/lib/rpm/redhat/redhat-hardened-ld ' 'LT_SYS_LIBRARY_PATH=/usr/lib64:' 'PKG_CONFIG_PATH=:/usr/lib64/pkgconfig:/usr/share/pkgconfig' Dec 16 14:51:56 srv-rhsoft named[352730]: running as: named -4 -f -u named -t /var/named/chroot ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Nice new logging feature
> On 16 Dec 2021, at 13:15, Reindl Harald wrote: > > > > Am 16.12.21 um 10:02 schrieb Borja Marcos: >> Hi, >> I am trying 9.17 at home and I just noticed a very useful new lame-servers >> log message: >> 2021-12-16T08:08:20.505Z lame-servers: timed out resolving >> ’stupiddomain.com/ANY/IN': X.Y.Z.T#53 >> I haven’t seen this on 9.16. Are there any plans to include it? > > bind-9.16.23-1.fc34.x86_64 > > 16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving > 'ns2.serverion.eu/A/IN': 94.228.210.122#53 > 16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving > '250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53 > 16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving > '250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 > 16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53 > 16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53 > 16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53 > 16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53 > 16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving > '166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 Not for me definitely, but I am not running Linux. This is a FreeBSD port of the ISC release. Does that version include some back ported code from bind 9.17? Borja. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Nice new logging feature
Am 16.12.21 um 10:02 schrieb Borja Marcos: Hi, I am trying 9.17 at home and I just noticed a very useful new lame-servers log message: 2021-12-16T08:08:20.505Z lame-servers: timed out resolving ’stupiddomain.com/ANY/IN': X.Y.Z.T#53 I haven’t seen this on 9.16. Are there any plans to include it? bind-9.16.23-1.fc34.x86_64 16-Dec-2021 13:08:10.598 lame-servers: connection refused resolving 'ns2.serverion.eu/A/IN': 94.228.210.122#53 16-Dec-2021 13:11:29.269 lame-servers: host unreachable resolving '250.84.141.45.in-addr.arpa/PTR/IN': 45.79.19.196#53 16-Dec-2021 13:11:31.804 lame-servers: host unreachable resolving '250.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 16-Dec-2021 13:12:10.567 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 198.58.118.167#53 16-Dec-2021 13:12:13.903 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.18.44#53 16-Dec-2021 13:12:14.034 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53 16-Dec-2021 13:12:15.773 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 45.33.23.183#53 16-Dec-2021 13:12:15.938 lame-servers: host unreachable resolving '166.84.141.45.in-addr.arpa/PTR/IN': 96.126.123.244#53 16-Dec-2021 13:12:46.937 lame-servers: connection refused resolving 'mx4.itronic.at/A/IN': 85.124.85.125#53 16-Dec-2021 13:13:41.202 lame-servers: host unreachable resolving '70.84.141.45.in-addr.arpa/PTR/IN': 72.14.185.43#53 16-Dec-2021 13:13:45.334 lame-servers: host unreachable resolving '70.84.141.45.in-addr.arpa/PTR/IN': 45.33.2.79#53 16-Dec-2021 13:13:46.953 lame-servers: REFUSED unexpected RCODE resolving '_.93.226.171.in-addr.arpa/A/IN': 203.113.131.1#53 16-Dec-2021 13:13:47.315 lame-servers: FORMERR resolving '_.93.226.171.in-addr.arpa/A/IN': 203.113.188.2#53 16-Dec-2021 13:13:47.601 lame-servers: REFUSED unexpected RCODE resolving '110.93.226.171.in-addr.arpa/PTR/IN': 203.113.131.1#53 ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: Nice new logging feature
> On 16 Dec 2021, at 10:02, Borja Marcos wrote: > > > Hi, > > I am trying 9.17 at home and I just noticed a very useful new lame-servers > log message: > > 2021-12-16T08:08:20.505Z lame-servers: timed out resolving > ’stupiddomain.com/ANY/IN': X.Y.Z.T#53 > > I haven’t seen this on 9.16. Are there any plans to include it? It would > _really_ be useful. Our setup now includes > 9.11 and 9.16 and soon I will have to switch to 9.16 and 9.18. Let me elaborate a bit, it is really useful to have a description of what triggered a SERVFAIL (a FORMERR, timeout, etc) _and_ the IP address of the authoritative server involved. I have been missing this! Borja. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Nice new logging feature
Hi, I am trying 9.17 at home and I just noticed a very useful new lame-servers log message: 2021-12-16T08:08:20.505Z lame-servers: timed out resolving ’stupiddomain.com/ANY/IN': X.Y.Z.T#53 I haven’t seen this on 9.16. Are there any plans to include it? It would _really_ be useful. Our setup now includes 9.11 and 9.16 and soon I will have to switch to 9.16 and 9.18. Cheers, Borja. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
