On Thu, 1 Oct 2020, Neal Gompa wrote:
Essentially, split-horizon DNS setups on Fedora systems become possible with this change.
As reported by libreswan and openvpn developers already in the last two days, these are already possible without systemd-resolved and people have relied on that for years. We have also seen reports like one where servers in an Active Directory domain with systemd-resolved have broken DNS due to load issues. Clearly, there is a case for making systemd-resolved "default with an option to opt-out". It makes no sense that these deployments must install and ensure to then disable and keep disabled, the systemd-resolved daemon. The argument against this so far has been "it makes things more complicated". I have asked for specific details on this so we can talk about potentially addressing those complications and make everybody happy. Paul _______________________________________________ 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
