** 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.
@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
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
@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
** 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
Bugs, which is subscribed to Ubuntu.
@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
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
@Alkis: Your title Dont... is not a description of a problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
Don't start local resolver if a DNS server is installed
To manage
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.
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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
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
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
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
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.
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
Bugs, which is subscribed to Ubuntu.
** 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
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
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/959037
Title:
Don't start local resolver if a DNS server is installed
To
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
You need to restart network-manager after changing the configuration
value.
It's unfortunate that the configuration needs to be changed, but it's
needed. I sympathize with your use case, but there is sufficient benefit
in using NM together with dnsmasq and resolvconf to solve other DNS
resolution
At this point though, the simplest way to deal with this remains to
edit interfaces= to map to the relevant external interfaces (eth0,
wlan0, etc.) and let the NM-spawned instance get started on lo.
We can't do that; we need DNS caching for thin client sessions which run
on the server with
caching That's one good reason where this is currently failing. The NM
instance won't cache. That's disabled on purpose, but we'll re-enable
for 12.10 or later once we can have per-user caches and something
secure.
library unfortunately, that won't help. library use, with not being
able to keep
Mathieu, some help please?
After my ltsp-pnp package comments out dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf, it runs
invoke-rc.d dnsmasq restart from its postinst,
but that fails as the nm-spawned dnsmasq instance is still listening on port 53.
And if I kill it before starting the
This isn't just a simple fix for this; the default shipped
configuration for dnsmasq is just as guilty as network-manager for
assuming it should bind on all addresses and all interfaces.
I disagree; most system services bind to all addresses and interfaces by
default (sshd, cupsd, bind, dnsmasq,
I run ltsp also, and even if I remove NM completely, I think that Alkis's setup
is interesting and would love to be able to use it also in the near future, so
this breakage will affect me too.
As general consideration I find scaring that installing a package can bring
such problems just because
Me, too. Fix this one. '#dns=dnsmasq' is ugly hack, not for real
humans, who run ltsp server at school.
Here is my bug report:
https://bugs.launchpad.net/ubuntu/+source/ltsp/+bug/955785
Best Regards Asmo Koskinen.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Please read the whole thread and see the various other workarounds
provided; granted the default shipped configuration for dnsmasq doesn't
play well with NetworkManager, but it's easy to adjust to your
particular needs and workaround this issue; which also only happens if
the system acting as a
Hi Mathieu,
If you're installing dnsmasq on top of the standard desktop install, why is
it such an issue to edit the NetworkManager configuration to cater it to your
needs?
except-interface=lo may be a good idea here to avoid listening on the
loopback interface
It's not about me; it's
The parsing of /etc/default/dnsmasq won't fly.
Please, do post your dnsmasq configuration so we can try to figure out
the right way to integrate this with the current setup.
As for the set of resolvers on the network, that's not exactly the
plan: all systems used to have the libc resolver. Now
Please, do post your dnsmasq configuration so we can try to figure out
the right way to integrate this with the current setup.
Just assume the default dnsmasq configuration, any other settings we have there
are completely unrelated to this problem.
When one installs dnsmasq, it's supposed to
Then at this point the issue is that dnsmasq is shipped with a default
configuration that while it's technically correct; binds on all
interfaces and should normally be modified by the admin to suit the
needs of their network. That configuration will break with NM making use
of dnsmasq-base as a
Please, tell me more about your setup so we can make sure we cater for
this use case before release.
1) Install precise-desktop-i386.iso to some-pc.
2) Install dnsmasq. Fails to start. OK, annoying but let's see if the problem
goes away after reboot.
3) Reboot. Try to `dig @some-pc ubuntu.com`
Another idea would be to create a spawn-local-resolver sysvinit or
upstart job that lists dnsmasq and bind in its dependencies, so that it
always starts after any known DNS servers, ensuring that no race
conditions occur for the :53 port checking.
--
You received this bug notification because
And yet another idea would be to make a package out of the local resolver
configuration, and declare that it Breaks: dnsmasq, bind9.
That way anyone installing dnsmasq or bind9 would get rid of the local resolver
package and its conflicting configuration.
--
You received this bug notification
If you're installing dnsmasq on top of the standard desktop install, why
is it such an issue to edit the NetworkManager configuration to cater it
to your needs? Wouldn't it make sense it this case to go further steps
and make sure the network connection is setup in /etc/network/interfaces
rather
Does it help any if the daemon dnsmasq is configured to only listen on
the interface meant for the ltsp clients, if there's a specific
interface for this?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There's other probably far simpler (and safer) workarounds. What's your
configuration for the dnsmasq like?
Upstream mentions some configurations at the dnsmasq level that are very
relevant for this particular case:
in /etc/dnsmasq.conf:
#except-interface=
# Or which to listen on by address
Well, that's already partly done. dnsmasq will fail to start with bind
is running, as it should; based on port 53 already being in use or not.
As another option, you may also wish to switch dns=dnsmasq to dns=bind
to use bind directly as a resolver. There are other reasons to have
dnsmasq and/or
I don't think we'll cover this particular use case for Precise. I
understand your requirement and how the need to change the settings in
/etc/NetworkManager/NetworkManager.conf isn't great, but it's a one-time
thing and isn't something we can safely do as part of the install
processes for dnsmasq
I don't think we'll cover this particular use case for Precise.
Excuse me, but how is installing bind9 or dnsmasq a particular use case?
I'm talking about the default installation, not some corner case...
most cases will not actually see bind and NetworkManager installed on
the same system
We
What I mean here is that default installs normally don't involve
installing a local DNS server, except perhaps as a caching resolver. The
caching resolver use case is covered by spawning dnsmasq from
NetworkManager; the local DNS server isn't. We do think that there is
relatively few such installs
I think I've been unclear. Using NetworkManager with *bind* is a
relatively unusual use case. dnsmasq with NetworkManager for resolution
is what we're aiming for *by default*, and that's what also part of the
default install. Everything has been put in place so that split VPN and
such are
43 matches
Mail list logo
