Simon, do you think that dnsmasq could misbehave as described here?
** 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.launchpa
>Simon, do you think that dnsmasq could misbehave as described here?
The only way I can see for this to occur is if a DNS server is return wrong (ie
NXDOMAIN or NODATA) answers, no answer shouldn't be a problem.
I suggest adding --log-queries to the dnsmasq configuration to try and
get a handle
Well when I did a manual dig @75.75.76.76 it timed out half of the
queries. The few responses it gave did seem good. That may not have been
representative though of the overall.
Unfortunately (or fortunately) the issue has stopped happening.
Thank you for your attention to this issue.
--
You re
aparently I spoke to soon =(
--
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/991308
Title:
DNS Querying fails if any DNS server is unreachable
To manage notifications about this bug
Does the standalone dnsmasq behave the same way?
To find out, disable nm-dnsmasq by commenting out the line "dns=dnsmasq"
in /etc/NetworkManager/NetworkManager.com. Restart network-manager.
Then install the dnsmasq package.
If standalone dnsmasq also misbehaves then turn on log-queries mode: add
In bug #979067 there is a similar description of apparent dnsmasq
misbehavior.
There Guillaume Melquiond writes:
> It takes a lot of failures before all the unreachable servers
> have been exhausted, which makes for a poor user experience.
--
You received this bug notification because you are a
Yes, it happens with dnsmasq by itself. However it appears that dnsmasq
is caching the result, so when it sees a good one it will keep serving
it.
Here is some example output from the syslog:
Jun 22 13:42:18 archon dnsmasq[9635]: started, version 2.59 cachesize 150
Jun 22 13:42:18 archon dnsmasq[
Just noticed this as well:
http://mydeviceinfo.comcast.net/device.php?tier=-1&devid=298&e=0&d3=0&s=n&so=0&sc=1546
To quote the red bit at top:
"Comcast has identified a software defect on the Arris TG852 and TG862, which
may cause problems for a small number of users attempting to use third party
Here is what I get when routing to the DNS servers goes through the
wrong interfaces. See bug #979067 for additional details on my setup.
Jun 25 12:50:51 dnsmasq[3799]: reading /var/run/dnsmasq/resolv.conf
Jun 25 12:50:51 dnsmasq[3799]: using nameserver yy.yy.36.37#53
Jun 25 12:50:51 dnsmasq[3799]
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/99
Guillaume wrote in #979067:
> [Dnsmasq] tries to access DNS servers from the wireless
> network [...and...] fails to resolve requests. It takes a lot of
> failures before all the unreachable servers have been
> exhausted, which makes for a poor user experience.
William reports that dnsmasq does n
What I meant is that DNS resolution always fails at first, and then
after lots of tries, it starts to work. But now that I look at the logs,
it may just have been a fluke: it eventually works because one of the
reachable nameservers happens to reply fast enough.
--
You received this bug notificat
What do you mean by "fast enough", though? Do you mean that all the
listed nameservers are very slow, some of them infinitely so (perhaps
because of a routing problem) and dnsmasq either always (William's case)
or usually (your case) times out before any nameserver replies?
--
You received this
No, that's the contrary, they reply too fast, in a sense. If you look at
the log I posted, dnsmasq does receive some kind of reply from the
unreachable nameservers. I don't know whether this is a crafted reply by
the firewall or whether the query actually reached the nameserver but it
replied with
14 matches
Mail list logo
