Re: systemd-resolved breakage

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, Nov 15, 2020 at 10:15 AM Anthony F McInerney
<afm404@xxxxxxxxx> wrote:


> Can someone explain why systemd-resolved needs to symlink
> /etc/resolv.conf to 4(or more) different places, instead of just
> having those 'detected things' as options in
> /etc/systemd/resolved.conf ?

The different symlinks/files provide different options.

/etc/resolv.conf is a symlink to /run/systemd/resolve/stub-resolv.conf
so
/etc/resolv.conf has "127.0.0.53" and "search"
resolved forwards queries to the upstream server

/etc/resolv.conf is a symlink to /usr/lib/systemd/resolv.conf
so
/etc/resolv.conf has "127.0.0.53"
resolved forwards queries to the upstream server

/etc/resolv.conf is a symlink to /run/systemd/resolve/resolv.conf
so
/etc/resolv.conf has "upstream server" and "search"
resolved only creates this file as if it were "resolvconf"

/etc/resolv.conf is a file
so
resolved uses the configured "server" and "search" as its "upstream
server" and "search"

I doubt that anyone would want resolved to create/modify the symlinks
depending on "/etc/systemd/resolved.conf".

Sam's idea of using the "alternatives" infrastrucure would be better.
But that would create other problems.

Assume that you're using networkd and resolved. If you install
NetworkManager, the preferred, higher-priority alternative'll be
"/run/NetworkManager/resolv.conf" whether you want it or not.


> Also spotted this on the Arch Wiki
>
> "systemd-resolved will work out of the box with a network manager
> using /etc/resolv.conf. No particular configuration is required
> since systemd-resolved will be detected by following the
> /etc/resolv.conf symlink. This is going to be the case with
> systemd-networkd or NetworkManager."

Sure, but this isn't the problem here. When you upgrade from F32 to
F33, the systemd post-install script enables resolved and creates a
resolved symlink.
_______________________________________________
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



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux