Hi,
thank you for your report and your help to make Ubuntu better!
I checked the old bug and wondered as that got upstream in version 1.10
and Trusty onward is >=1.11 so this issue should not occur on your
Ubuntu 16.04 system with sssd 1.13.
I found in the patches linked a note that mentioned:
"To avoid the problem mentioned in the ticket above, option
dns_discovery_domain must be set properly."
It is documented as:
dns_discovery_domain (string)
If service discovery is used in the back end, specifies
the domain part of the service discovery DNS query.
Default: Use the domain part of machine's hostname
That should be a safe default IMHO, but did you set that in your config (or
would you have to)?
Not sure I could find anything in it, but sharing your sssd config (if not
confidential in any way) might be helpful.
I don't know your setup but in the past I often found it challenging to
verify sssd issues due to the setup complexity. As kind of a start to
check if that issue is fixed upstream as well I wanted to ask if you
could try your on a test system check with the new zesty release - that
is about to get the newer 1.14.2-1 the next few days (currently passing
through some tests, but should be there soon).
** Changed in: sssd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1642486
Title:
SSSD SRV Lookup Failover Fails when primary DNS Server is unresponsive
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1642486/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
