On Thu, Dec 14, 2023 at 10:46:36PM +0000, Chris Green wrote: > Up until now I have the following in my /etc/dnsmasq.conf:- > > resolv-file=/run/NetworkManager/no-stub-resolv.conf > > This means that dnsmasq uses the upstream DNS that Network Manager > configures. When I'm on the local LAN this resolves to 'my' DNS > server at 192.168.1.2, when I'm connected somewhere else Network > Manager sorts things out accordingly and dnsmasq gets the right > upstream DNS server. > > However the latest Ubuntu update has tightened the permissions on > /etc/NetworkManager and dnsmasq can't read the file > /run/NetworkManager/no-stub-resolv.conf. > > I know this is a slightly non-standard configuration but it has worked > very nicely for me for some years. Can anyone suggest a way to fix > this?
One can answer that question. And with a very strong collaboration can the yes-no-question also be answered. > Obviously /run/NetworkManager/no-stub-resolv.conf is created > at every boot so the permissions will revert to 'too strict' every > time I start the system. Also obvisously: Explain the desired configuration with what is actual desired. Visit https://xyproblem.info for _why_ explaining more. Groeten Geert Stappers -- Silence is hard to parse _______________________________________________ Dnsmasq-discuss mailing list Dnsmasq-discuss@lists.thekelleys.org.uk https://lists.thekelleys.org.uk/cgi-bin/mailman/listinfo/dnsmasq-discuss
