Yes, the 127.0.1.1:53 solution works so long as dnsmasq and others are
run in bind-interfaces (or equivalent) mode.
NM-dnsmasq currently (12.04) listens at 127.0.01:53 which prevents
others from listening on either ALL:53 or lo:53, i.e., 127.0.0.1:53.
The new (12.10) behavior allows others to listen on 127.0.0.1:53, but
still doesn't allow them to listen on ALL:53. Someone correct me if I'm
wrong.
> With bind, this is okay, mostly, because you can say to listen
> on everything for a particular interface
Are you sure? I am only aware of named.conf's "listen-on { IP_ADDRESS;
}". If there is a feature such as you describe then presumably named
binds ALL:53 and then filters according to the addresses on the
specified interfaces.
> (but then you can't listen on 127.0.0.1, because it's the same
interface as 127.0.1.1)
You don't listen on an interface, you listen on a socket --- an
address:port pair. So when nm-dnsmasq binds 127.0.1.1:53, others can
still bind lo:53, i.e., 127.0.0.1:53.
A question about the NSS plugin idea. Will this work only for software
that uses glibc? What about alternative resolver libraries? They all
read resolv.conf, but do they all read nsswitch.conf too? The djbdns
description
http://cr.yp.to/djbdns/blurb/library.html
for one doesn't mention this.
--
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:
Confirmed
Status in “dnsmasq” package in Ubuntu:
Fix Released
Status in “network-manager” package in Ubuntu:
Fix Released
Status in “pdns-recursor” package in Ubuntu:
Invalid
Status in “pdnsd” package in Ubuntu:
Invalid
Status in “djbdns” source package in Precise:
Confirmed
Status in “dnsmasq” source package in Precise:
Triaged
Status in “network-manager” source package in Precise:
Triaged
Status in “pdns-recursor” source package in Precise:
Invalid
Status in “pdnsd” source package in Precise:
Invalid
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
