[Bug 959037] Re: NM-controlled dnsmasq prevents other DNS servers from starting

[Svartalf]

This is a bad idea as it's been implemented, guys- there's tons of local
installations that use internal DNS (My CenturyLink router or my day-
job's setup, for example...) that this flatly breaks out of box.  You've
got to do a bunch of manual interventions for MANY corporate desktop and
home desktop situations.  It doesn't honor lookups against the local,
specified by DHCP, DNS servers- it goes out to the DNS roots and goes
from there.  Works FINE for JUST surfing the 'net.  It's an EPIC FAIL
for normal, typical DNS use right now because there's no honoring any
internal only DNS entries with it as it is out of box.

It's nice that you're trying to make it easier for VPN, etc. but in the
corporate desktop story, you're using OpenVPN, PPTP, or something like
Sonicwall's solution.  This means it's going to re-direct DNS on you
ANYHOW, defeating the nice thing you're attempting here.  If you think
you're changing their minds, think again.

As it stands, I'm going off to cripple this less than well thought out
design decision so that things MIGHT work better on my setups.  I
suggest thinking through *ALL* prospective use-cases of things before
implementing something like this in the future- it really, really ticks
people off when it doesn't work like it's supposed to.

-- 
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