> 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
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
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
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
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 config
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
> 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 lam
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
’stupi
> 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'
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 inclu
> 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. A
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
12 matches
Mail list logo
