yes, it’s the same thing. The workaround to add a dependency on network up or
systemd-resolved.service work (either one).
A static /etc/resolv.conf also works, but I’m going to use the extra startup dependency.
We didn’t have the problem on a system with static configuration. The one with the problem
There’s one other workaround I considered, but can’t make happen. If you install
libnss-resolve, it should use that library rather than depending upon /etc/resolv.conf.
That should avoid the whole issue with /etc/resolv.conf. I can’t try it, because after the
security update, i have a version of systemd for which there’s no version of
libnss-resolve that will install.
On Aug 13, 2019, at 1:02 PM, Andreas Hasenack
On Tue, Aug 13, 2019 at 1:01 PM Charles Hedrick <hedrick(a)rutgers.edu> wrote:
> On our Ubuntu 18.04 servers, sssd won’t start. Logging shows that it can’t find any
DNS servers. Restarting sssd fixes it.
Sounds like https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1723350
sssd-users mailing list -- sssd-users(a)lists.fedorahosted.org
To unsubscribe send an email to sssd-users-leave(a)lists.fedorahosted.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines