On Tue, Nov 03, 2020 at 09:08:04AM -0600, Ian Pilcher wrote: > On 11/2/20 10:37 AM, Jonathan Billings wrote: > > I have a similar configuration, and at first I tried to get the > > dnsmasq to be used by systemd-resolved but it kept "forgetting" it and > > switching back to what DHCP used, so I just stopped, disabled and > > masked systemd-resolved.service, deleted /etc/resolv.conf and > > restarted NetworkManager to get a working configuration back. > > What problem did systemd-resolved cause? I have my NM dnsmasq refer a particular local subdomain to the dnsmasq that libvirt runs, so DNS names are automatically populated locally on my workstation. This lets me build VMs running Kerberos and OpenAFS servers with resolvable DNS entries. (DNS is important for krb5) I also run a pihole container and use it for external queries. > And my original question still stands, if /etc/resolv.conf is pointing > to systemd-resolved, is the NM-managed dnsmasq instance actually doing > anything for me? It won't if systemd-resolved isn't configured to look at 127.0.0.1 (or wherever you have your NM dnsmasq listening). Check 'resolvectl' to check. In my case, it kept switching to the DNS entries that my wifi DHCP request got back, even though I had overridden it in NetworkManager. If anyone has a suggestion on how to force systemd-resolved to use a particular DNS server and not have local DHCP sessions override it, I'd like to know. -- Jonathan Billings <billings@xxxxxxxxxx> _______________________________________________ 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
