"Dnsmasq cascade" (#72) has maintenance advantages. For example it
makes it easy for the distromaestros to switch to other software to
perform the same limited task as nm-dnsmasq now performs, without any
chance of disturbing admins' standalone dnsmasq setups.
Does dnsmasq-cascade have drawbacks compared with "Single dnsmasq" as
described by Alkis in #73?
Yes...
* Dnsmasq cascade requires that standalone dnsmasq run in bind-interfaces mode.
-- Solvable by moving nm-dnsmasq to another port:
http://sourceware.org/bugzilla/show_bug.cgi?id=14242
* Dnsmasq cascade requires two processes rather than one.
-- but resource usage is low so this doesn't seem important
But are there other drawbacks?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in 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-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
