@Alkis: Your title "Dont..." is not a description of a problem.
--
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:
Don't start local resolver if a DNS server is installed
Listening on lo is fine; and blocking other DNS servers from being
started isn't. I think we're in violent agreement there. The problem is
how to fix this.
I'm not saying dnsmasq should be crippled, but that it should special-
case lo and not just listen on 0.0.0.0; because that binds to any
furth
@jdthood: the "Standalone dnsmasq is not compatible out of the box with
NM+dnsmasq" title hints that the problem is caused by the dnsmasq
package, i.e. that it should be crippled and not listen on "lo" by
default in order to coexist with the local resolver implementation.
I don't think this is the
** Summary changed:
- Standalone dnsmasq is not compatible out of the box with NM+dnsmasq
+ Don't start local resolver if a DNS server is installed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
https://bugs.launchp
Just as a short reminder, there are more DNS-resolver/server available as
packages out there than just bind and dnsmasq, i.e. djbdns and it's derivates.
Until I removed the annoying dns=dnsmasq line in /e/N/Nconf, NM disconnected
the WLAN after a couple of minutes, throwing an error about dnsmas
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: dnsmasq (Ubuntu)
Status: New => Confirmed
--
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/95
> The configuration itself shipped by default should be patched
If you mean something like:
except-interface=lo
bind-interfaces
...I just tested them and they do allow both dnsmasq instances to run.
But of course those settings won't be acceptable to most dnsmasq users,
as listening on "lo" is u
That wouldn't be the right process though. The configuration itself
shipped by default should be patched, that can be done with a simple
patch to the dnsmasq package.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
ht
Since this won't be fixed for Precise from the network-manager side, the
dnsmasq package now is broken by default in desktop installations.
So I've added the dnsmasq package in the "Affects:" list, to make it easier for
people to locate the cause of the problem so that fewer duplicate bug reports
** Also affects: dnsmasq (Ubuntu)
Importance: Undecided
Status: New
--
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:
Don't start local resolver if a DNS server
10 matches
Mail list logo
