[Expired for dnsmasq (Ubuntu) because there has been no activity for 60
days.]
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete = Expired
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
Jérôme, it's nice to hear that it is working correctly, but which of the
following is the case?
1. Dnsmasq is working correctly in the standard factory configuration.
2. It is working with no-negcache mode activated.
3. It is working with clear-on-reload mode activated.
4. It is working and
It seems to be working correctly now, thank you!
--
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/1172467
Title:
Dnsmasq caches negative results if it starts before the network is up
Jérôme, can you please see if clear-on-reload fixes the problem,
without no-negcache?
** Changed in: dnsmasq (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
On 24/07/13 20:33, Thomas Hood wrote:
Hi Simon,
I think we've established that the submitter is having a problem with
dnsmasq server, not with NetworkManager-controlled dnsmasq. So it would
be interesting to know if clear-on-reload fixes the submitter's problem.
(He already said that
On 08/07/13 15:02, Thomas Hood wrote:
What do you think, Simon?
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete = New
I'm confused: dnsmasq won't cache a negative answer if it has no
upstream servers. To cache a negative answer it has to _receive_ a
negative answer (and the
Whatever is going on, it's more complex. Maybe the problem is that
dnsmasq gets a negative answer from some upstream server, and then
gets a new upstream server which has the correct information? The
solution then is --clear-on-reload but I think NM sets that?
but --clear-on-reload
Hi Simon,
I think we've established that the submitter is having a problem with
dnsmasq server, not with NetworkManager-controlled dnsmasq. So it would
be interesting to know if clear-on-reload fixes the submitter's problem.
(He already said that no-negcache fixes it.)
That clear-on-reload is
NetworkManager starts dnsmasq with caching completely disabled so that
seems unlikely to be a problem with the NM spawned dnsmasq.
However the fact that adding the setting to /etc/dnsmasq.d/network-
manager fixed it for you, shows that you're not using NetworkManager's
dnsmasq but a system
Stéphane wrote:
Can you confirm that you have the dnsmasq package installed and not only
dnsmasq-base?
If so, then that bug is invalid as when you install dnsmasq on your system,
that'll bypass NetworkManager's own instance and so will run with the
default dnsmasq settings (including
Well for 2), it clearly looks like a case of negative caching (dnsmasq
has no upstream server, therefore it only uses /etc/hosts only, if the
entry isn't in there, it considers it a NXDOMAIN), upstream also seems
to be aware of that behaviour as they offer the option to turn off
negative caching.
What do you think, Simon?
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete = 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/1172467
Title:
Dnsmasq caches negative
12 matches
Mail list logo
