On Monday, 28 September 2020 at 15:30, Zbigniew Jędrzejewski-Szmek wrote: [...] > What was the setup you were using? If this is something that we can > reliably detect, I think it it would make sense to adjust the scriptlet > that enables systemd-resolved to print a hint about needing to set DNSSEC=yes. > (Or maybe even set that itself?). Having dnssec-trigger package installed would be an indicator in my case. Also, it does write its own comment in /etc/resolv.conf: $ rpm -qa dnssec\* dnssec-trigger-0.15-12.fc32.x86_64 dnssec-trigger-panel-0.15-12.fc32.x86_64 $ cat /etc/resolv.conf # Generated by dnssec-trigger-script nameserver 127.0.0.1 It uses a local unbound instance for local DNSSEC resolution. Regards, Dominik -- Fedora https://getfedora.org | RPM Fusion http://rpmfusion.org There should be a science of discontent. People need hard times and oppression to develop psychic muscles. -- from "Collected Sayings of Muad'Dib" by the Princess Irulan _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
