But enough dreaming.  Given the world as it is, the immediate challenge
is to make NM+dnsmasq compatible with standalone nameservers.
(Otherwise network-manager should Conflict with those nameservers'
packages.)

Solutions mentioned earlier:
* Tell the administrator to comment out "dns=dnsmasq" in 
/etc/NetworkManager/NetworkManager.conf after installing dnsmasq or another DNS 
server package.
* Change NM so that it acts as if "dns=dnsmasq" is absent if a DNS server 
package is installed.
* Change standalone dnsmasq such that it doesn't listen on 0.0.0.0:53, doesn't 
listen on 127.0.1.1:53 and change NM so that its dnsmasq listens only on 
127.0.1.1:53.

Here's a new idea.

* Enhance the resolver(3) so that nameservers can be specified in resolv.conf 
using the <address>:<port> notation
* Change NM such that it causes its slave dnsmasq to listen on another (than 
53) port number P and sends "nameserver 127.0.0.1:P" to resolvconf.

-- 
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 running, yet
  network-manager doesn't Conflict with their packages

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     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to