On Sat, 2022-12-17 at 21:36 +0100, Herbert Graeber wrote:
Am Samstag, 17. Dezember 2022, 17:52:32 CET schrieb Andrei Borzenkov:
On 17.12.2022 19:27, Herbert Graeber wrote:
So, is NetworkManager-dns-dnsmasq really necessary? Isn't it better to use the NetworkManager option?
Define "better". This package is for updating external dnsmasq instance outside of NetworkManager.
With "better" I mean using tools like are meant to be used...
I have found the "dns" option searching for a solution for easily switching between multiple VPNs. The restriction to have only 3 servers in resolve.conf (I known that's lifted to 6 meanwhile) was a problem. I decided to use dnsmasq as a caching dns server and use it's forwarder list. Investigateing this I found that NetworkManager already supports such a configuration, but dnsmasq has to be started by NetworkManager instead by systemd.
Maybe this NetworkManager feature has simply been overlooked and there is no need for the dns-dnsmasq.sh script.
I was using dns=dnsmasq, too. I was just about to write that a "native" dnsmasq instance was preferred because of improved configurability. But there's actually no difference, except that the config dir is /etc/dnsmasq.d for native dnsmasq and /etc/NetworkManager/dnsmasq.d with NM. So, I agree that the usefulness of NetworkManager-dns-dnsmasq is questionable. It adds another configuration variant without obvious benefit. It might even cause confusion or errors if users inadvertently enable both dnsmasq instances at the same time. It's possible to have several dnsmasq instances running in parallel, but it's probably not a good idea to use multiple instances for the same interface/network. Regards Martin