$ cat /run/nm-dns-dnsmasq.conf
server=/17.172.in-addr.arpa/172.17.1.2
server=192.168.1.254
server=...
The first "server=" line reflects the fact that I am connected to a VPN.
This can't be expressed in resolv.conf syntax.
No doubt dnsmasq could be enhanced to poll its configuration files. But
it remains a question whether it's advisable for NM to make use of the
standalone dnsmasq for the purposes for which nm-dnsmasq was introduced.
Effectively this revisits the discussion that led to the introduction of
nm-dnsmasq in the first place. Part of that discussion (which I wasn't
party to) can be read here:
https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns-
resolving
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
NM-controlled dnsmasq prevents other DNS servers from starting
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
