"Is there a concern or known issue that will cause systemd-resolved to
not work in your setup?"
I have a ton of experience with sssd and before that samba winbind so know the benefits and limitations of this software stack well. I'm new to systemd-resolved but have been reading the lively Fedora threads about it and think it could still do with some further improvements, which I'm sure will occur in the goodness of time, but as it stands right now the argument to jump to it isn't compelling enough for me.

nscd may be old and decrepit but it's still delivering the goods.

On Fri, 6 Nov 2020 at 03:47, Arjun Shankar <ashankar@redhat.com> wrote:
> Definitely happy to throw nscd out for something better that was just as
> simple and easy to set up.

> I'll leave systemd-resolved for the trail blazers.

Since systemd-resolved is already on by default since Fedora 33 [1],
the user base should be up quite a bit as users continue to upgrade.
It's not just trail blazers any more, and it's not just easy: it's already set
up.

Is there a concern or known issue that will cause systemd-resolved to
not work in your setup?

[1] https://fedoraproject.org/wiki/Changes/systemd-resolved
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-leave@lists.fedoraproject.org
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@lists.fedoraproject.org