<html><head></head><body><div dir="auto">I don't use Ubuntu variants but it may be worth checking if the Network manager package installs a systemd permissions file for the file in /run. If that's the case, you can override the permissions with your own version in /etc.</div><br><br><div class="gmail_quote"><div dir="auto">On 14 December 2023 22:46:36 GMT, Chris Green <cl@isbd.net> wrote:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail"><div dir="auto">Up until now I have the following in my /etc/dnsmasq.conf:-<br><br> resolv-file=/run/NetworkManager/no-stub-resolv.conf<br><br>This means that dnsmasq uses the upstream DNS that Network Manager<br>configures. When I'm on the local LAN this resolves to 'my' DNS<br>server at 192.168.1.2, when I'm connected somewhere else Network<br>Manager sorts things out accordingly and dnsmasq gets the right<br>upstream DNS server.<br><br>However the latest Ubuntu update has tightened the permissions on<br>/etc/NetworkManager and dnsmasq can't read the file<br>/run/NetworkManager/no-stub-resolv.conf.<br><br>I know this is a slightly non-standard configuration but it has worked<br>very nicely for me for some years. Can anyone suggest a way to fix<br>this? Obviously /run/NetworkManager/no-stub-resolv.conf is created<br>at every boot so the permissions will revert to 'too strict' every<br>time I start the system.<br><br></div></pre></blockquote></div></body></html>