Re: ssh impacted by systemd.resolved

[Barry Scott <barry@xxxxxxxxxxxxxxxx>]

On 27 Apr 2022, at 13:05, Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote:

The only reason systemd-resolved exists is because glibc caches /etc/resolv.conf when a process performs its first DNS lookup. Having the means to have an existing process become aware that its been changed, and it should reread it, will completely eliminate the reason for systemd-resolved's existence. That, I think, is the right solution, and it was always the right solution.

Its not just the problem of glibc not being able to reload /etc/resolv.conf (that might be fixed in recent glibc - not sure).

I use and depend on the DNS split horizon features of systemd-resolved all the time.

Barry

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-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/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure