On Wed, Apr 27, 2022 at 08:05:56AM -0400, Sam Varshavchik wrote: > > And in the instant case, we had: > > 1) A broken systemd-resolved scriptlet that ended up overwriting the > /etc/resolv.conf symlink. This was fixed in the -2 update, but the initial > reports were ignored, because we were told that the symlink gets created > only on the initial install, and not an upgrade. Well, it turns out this > wasn't the case. ignored by whom? I noted that there were bugs and fixed in the most recent versions. It's important to that basically everyone should have a 'according to what I know...' in front of any help you get. > > 2) Completely unaddressed was the reason all of that came to light: either > the original update also broke DNS resolution on the LAN, or it was always > broken and systemd-resolved never adds the DHCP-provided domain to the > "search" directory in its /etc/resolv.conf, but NetworkManager always does > that. I documented that. > > I don't know if the -2 update fixes this or not. But that's another bug that > at least was initially ignored. From all the looks it's still being ignored. Well, the users list is not a bug reporting medium. I don't think systemd-resolved maintainers read this list and act on it. Do report a bug to bugzilla.redhat.com or upstream to systemd on it. systemd-resolved does pick up the domain provided by dhcp here. what does 'resolvectl' show there? (if you still have it around) > The only reason systemd-resolved exists is because glibc caches > /etc/resolv.conf when a process performs its first DNS lookup. Having the no. It provides a number of advantages over a static resolv.conf file, this is just not the case. > 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. Well, I disagree, but such is life... kevin
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ 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
