Le 10/07/2023 à 21:54, Richard T.A. Neal a écrit :
Jul 10 19:49:07 flons3 named[1140]: /etc/bind/named.conf.logging:147:
undefined category: 'delegation-only'
Jul 10 19:49:07 flons3 named[1140]: loading configuration: failure
Jul 10 19:49:07 flons3 named[1140]: exiting (due to fatal error)
Hi Richard,
It looks like you have an error in the configuration file
/etc/bind/named.conf.logging on line 147:
Jul 10 19:49:07 flons3 named[1140]: /etc/bind/named.conf.logging:147:
undefined category: 'delegation-only'
Jul 10 19:49:07 flons3 named[1140]: loading configuration: failure
I assume
For the past few releases I've been unable to successfully upgrade my BIND
v9.19.11 on Ubuntu 22.04.2 LTS.
The upgrade appears to go OK at first but then it stumbles at the following
line. I've had to re-type this because my console tool can't copy/paste this
segment for some reason:
Process:
> I was curious about the additional section count dig is
> reporting. I had to do a packet capture to prove it to myself,
> but there is an additional records section returned in the
> answer from 183.47.126.169. It is the edns OPT pseudosection
> which is also shown in my dig output:
You
Hi Håvard,
I was curious about the additional section count dig is reporting. I
had to do a packet capture to prove it to myself, but there is an
additional records section returned in the answer from 183.47.126.169.
It is the edns OPT pseudosection which is also shown in my dig output:
% dig
> You are wrong if you think the SOA record is only informal.
> It's not, see https://www.rfc-editor.org/rfc/rfc2308 for more
> details.
Exactly. The SOA record included in the "Authority section" of an
NXDOMAIN ("name does not exist") or NODATA ("answer count" = 0,
i.e. indicating "name exists,
6 matches
Mail list logo
