Hi,
Thank you for your prompt response.
I configured the logging severity as dynamic to allow me to change the
severity level at any time using the rndc command. I have also reviewed the
release notes for all versions released after BIND 9.18.16, but I did not
find any bug fixes related to debug
I wonder…. What do you think that
severity dynamic;
does in your configuration file and why you have it configured? Have you read
the documentation on the logging in the ARM?
Also - don’t run old versions of BIND 9, you are almost 20 versions behind the
latest 9.18 release, that’s year an half
US Federal civilian agencies have been required to do DNSSEC validation for
over ten years.
On Mon, Jan 27, 2025 at 7:42 PM Grant Taylor via bind-users <
bind-users@lists.isc.org> wrote:
> On 1/27/25 07:02, Carlos Horowicz via bind-users wrote:
> > IMHO this has nothing to do with DNSSEC,
>
> HEA
Dear Team,
I am currently using BIND 9.18.16 and have encountered an issue where debug
level 3, 5, and 99 logs are being recorded in the named.log, even though
the debug level is explicitly set to 0.
Could you confirm if there are any hardcoded logging configurations within
BIND that might cause
On 1/27/25 07:02, Carlos Horowicz via bind-users wrote:
IMHO this has nothing to do with DNSSEC,
HEAVYsigh
Why do things seem to focus on the encryption of DNS traffic and ignore
authentication of the information?
I'm sure that all of us are aware that it's perfectly possible for a DoT
/ D
I found this RFC https://www.rfc-editor.org/info/rfc9076 pretty
interesting as it covers all topics related to DNS privacy, including
the need to prepare for quantum-resistant algorithms and encrypting DNS
traffic ... I guess the author is not only referring to resolver traffic
that should use
On Mon, Jan 27, 2025 at 12:55:08PM +,
Marc wrote
a message of 36 lines which said:
> What is this referring to DNSSEC?
The way I understand it, it is referring to DoH and DoT.
> What is the point of encrypting data with the current implementation
> of certificates.
I fail to see the rel
IMHO this has nothing to do with DNSSEC, it sounds more like the urge to
encrypt resolver traffic (I guess they're referring to DoT)
On 27/01/2025 13:55, Marc wrote:
FYI - EO 14144 has the following provision related to encrypting DNS:
(c) Encrypting Domain Name System (DNS) traffic in transit
>
> FYI - EO 14144 has the following provision related to encrypting DNS:
>
> (c) Encrypting Domain Name System (DNS) traffic in transit is a critical
> step to protecting both the confidentiality of the information being
> transmitted to, and the integrity of the communication with, the DNS
> re
FYI - EO 14144 has the following provision related to encrypting DNS:
(c) Encrypting Domain Name System (DNS) traffic in transit is a critical step
to protecting both the confidentiality of the information being transmitted to,
and the integrity of the communication with, the DNS resolver.
(i
Hi,
ISC provides BIND 9 packages via:
- Launchpad:
- BIND 9.18: https://launchpad.net/~isc/+archive/ubuntu/bind-esv
- BIND 9.20: https://launchpad.net/~isc/+archive/ubuntu/bind
- BIND 9.21: https://launchpad.net/~isc/+archive/ubuntu/bind-dev
- Debian custom repositories:
- BIND 9.18: https://
11 matches
Mail list logo
