> On Ubuntu I changed the configuration of the resolver in /etc/resolv.conf > to use the DNS directly instead of the local systemd-resolved from > "nameserver 127.0.0.53" to "nameserver 10.148.231.1" and it fixes the issue.
Could you also check what the status of the systemd resolver was? sudo systemd-resolve --status In particular which DNS servers it had available and was using for each network interface, and globally. FWIW, since a few ubuntu releases I've seen a 5s delay in some name resolutions that happen for the first time: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1765477 So maybe sssd was doing the DNS query to obtain the FQDN of the host, but it took too long and it gave up? Hence fedora's suggestion to set `hostname` to the fqdn, instead of relying on `hostname -f`, which does a DNS query? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1893438 Title: Cannot resolve users without an existing /etc/krb5.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/1893438/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
