On 18/06/12 21:08, Thomas Hood wrote:
> @Simon: This is pretty much what I had in mind (comment #88) as a long-
> term solution.  How difficult do you think that this would be?

Don't know. I'm working on it now: seems to be behaving:

dnsmasq: new IPv4: 192.168.3.1
dnsmasq: new IPv6: fe80::f0f6:48ff:fe15:70b0

>
> (Moving nm-dnsmasq listening to another port than 53 is at best a veeery
> long-term solution since it requires first getting glibc enhanced, then
> getting all other resolver libraries enhanced, then waiting for third-
> party static binaries to be replaced by new versions built against
> enhanced libraries.  That's a ten-year project.)
>
> If "bind-interfaces-dynamically" works well then I see no reason why it
> shouldn't be the default mode of operation.  Indeed, I see no reason why
> it shouldn't be the *only* mode on OSs with support for it.
I see reasons: I've been burned by releasing changes that "won;t affect 
anything" too many times, I like the idea of making the new behaviour 
opt-in.

Simon.

>

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/959037

Title:
  NM-controlled dnsmasq prevents other DNS servers from starting

Status in “djbdns” package in Ubuntu:
  New
Status in “dnsmasq” package in Ubuntu:
  Confirmed
Status in “network-manager” package in Ubuntu:
  Triaged

Bug description:
  As described in
  https://blueprints.launchpad.net/ubuntu/+spec/foundations-p-dns-
  resolving, network manager now starts a dnsmasq instance for local DNS
  resolving.

  That breaks the default bind9 and dnsmasq installations, for people that 
actually want to install a DNS server.
  Having to manually comment out "#dns=dnsmasq" in 
/etc/NetworkManager/NetworkManager.conf doesn't sound good, and if it stays 
that way, it should be moved to the bind9 and dnsmasq postinst scripts.

  Please make network-manager smarter so that it checks if bind9 or
  dnsmasq are installed, so that it doesn't start the local resolver in
  that case.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/djbdns/+bug/959037/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : [email protected]
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to