Sent with Proton Mail secure email.

On Monday, 23 December 2024 at 14:00, Kevin P. Fleming 
<lists.systemd-de...@kevin.km6g.us> wrote:

> The simplest fix is to set "DNSSEC=no" 

That seems to me to be a bit of a "sledgehammer to crack a nut".

The man page for resolved.conf says:

"It is recommended to set DNSSEC= to true on systems where it is known that the 
DNS server supports DNSSEC correctly "

I know that my DNS servers do, since they are all modern implementations which 
have no issues with DNSSEC support.

Also DNSSEC=no would also kill DANE which is not a desirable outcome ?

Reply via email to