On Thu, 2020-12-03 at 12:58 +0100, [email protected] wrote: > In F33 the name resolution is done via systems-resolved by default, > not NetworkManager (and systemd-resolve was the origin of this > thread, if I remember correctly). And /etc/resolve.conf is now a > symbolic link managed by systemd. > > systemd-resolved is configured in /etc/systemd/resolved.conf. There > you can statically specify your name server and your search > domain(s). > > NetworkManager is still used to configure the network devices and > connection. You can statically configure your IP address(es) in the > usual way. I don’t know if NetworkManager can configure systems- > resolved for you. Last time I checked it didn’t.
I used nm-connection-editor because I needed two search domains for a VPN connection. Only one was provided by DHCP so systemd-resolved wouldn't send DNS requests for the second domain through the tunnel after upgrading to F33 until I manually added the additional domain. I can't see any reason it wouldn't work with a staticly configured LAN connection too. The reason I said "there are probably other ways" in my post was because I'm still not versed enough in systemd-resolved and didn't want to dive into the learning the format of /etc/systemd/resolved.conf and spinning up a VM to test it.
_______________________________________________ users mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected]
