** Changed in: dnsmasq (Ubuntu)
Status: Expired = Confirmed
** Description changed:
- dnsmasq does not resolve DNS names correcty.
+ Dnsmasq sometimes does not resolve DNS names correcty.
- Applications like Thunderbird or tools like ssh rely on working name
- resolution. However, if
Arno,
Does disabling NetworkManager-controlled dnsmasq fix the problem? (To
disable NetworkManager-controlled dnsmasq, comment out dns=dnsmasq in
/etc/NetworkManager/NetworkManager.conf and then restart network-
manager.)
Hypothesis: dnsmasq is given two nameserver addresses. The first
I was experiencing a similar problem as described by submitter.
The name resolution of the short name failed, subsequently the name
resolution of the fqdn also failed. After 10-15 seconds, the fqdn
resolved again, only to fail again after trying the short name.
The solution described by Thomas
[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.
Lots of speculations here.
My internal DNS server is 10.1.0.4. My fallback is the secondary
10.1.0.254 which acts as DNS forwarder and proxy to the third and
others.
The resolver works its way down: All things well = 10.1.0.4
Main server down: 10.1.0.254 will serve rudimentary internal services
Well, we are lucky that you do have a good workaround for the problem,
even if we don't yet fully understand it.
Do I understand correctly that your two internal nameservers can resolve
exactly the same domain names, neither one more names than the other?
If that is not the case then bug #1003842
seems that strict-order is the way to go [...] Can that be automated
[...]?
There has been a discussion about the problem and possible solutions in
bug #1003842. I most recently expressed my opinion in comment #41 of
that ticket.
It takes a long time to resolve the name
Why do you think that
First the bad news.
Name resolution drops after a few minutes of inactivity (approx.
30mins).
Same phenomenon as before.
Second: The name server answers as soon as the request arrives. dnsmasq
obviously takes some time to determine if it can serve the name itself.
So back to square one:
The -o option is the same as the strict-order option.
The dnsmasq man page says that in strict-order mode dnsmasq uses the
order from /etc/resolv.conf but we shouldn't take that too literally
since dnsmasq obtains nameserver addresses from sources other than
/etc/resolv.conf. The dnsmasq process
When dnsmasq is malfunctioning, does sending the dnsmasq process a
SIGHUP fix it?
sudo kill -HUP $(pidof dnsmasq)
This signal causes dnsmasq to clear its cache, but I imagine it might
also kick dnsmasq out of whatever faulty state it has got into.
--
You received this bug notification
By the way, is it still the case that only domain name completion is
malfunctioning, not DNS lookups in general and lookups of fully
qualified domain names in particular?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in
Wolf, you wrote:
nm-tool | grep DNS gives
DNS: 10.1.0.4
DNS: 10.1.0.254
DNS: 195.202.128.3
You later wrote:
I can confirm that my DNS server serves any request from inside the
network.
Which server serves the requests, 10.1.0.4 or 10.1.0.254? Are these
nameservers completely
The unusual time-dependent character of the malfunction makes me
speculate about more exotic possibilities such as misconfigured
firewalls or flaky hardware.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
Did some testing
I set up the strict-order using the file approach as described above.
I see no different behaviour.
My bind does not get any queries at all. dnsmasq does not forward
requests.
Applications like Evolution or Thunderbird break on every reboot or
resume. It takes up to 3 minutes
Thanks for testing. My hypothesis from comment #31 is false.
Is there anything unusual about your resolver configuration? Do you have
a sortlist, options, etc., line in resolv.conf? What is the hosts
line in your /etc/nsswitch.conf?
--
You received this bug notification because you are a
BTW I just discovered that restart network-manager no longer suffices
to reload the configuration of nm-dnsmasq because nm-dnsmasq doesn't get
killed on stopping network-manager. So if you edit files in
/etc/NetworkManager/dnsmasq.d/ you have to stop network-manager ;
killall dnsmasq; start
I restarted my machine in order to test under correct circumstances. I
did restart the network manager but did not kill all dnsmasq explicitly.
Now after a reboot I can give you better results. Give me until tomorrow
for a complete test run
So far, Thunderbird did find the server immediately and
carried out some suspend/resume tests
worked fine.
tried some pings with name resolution:
It takes a long time to resolve the name but it works
seems that strict-order is the way to go in installations where an
internal DNS is supported by external backups / extensions
Can that be automated
My guess is that this bug is fundamentally bug #1003842 with the twist
that sometimes the lookup succeeds if the fully qualified internal
domain name is given on the command line explicitly.
(I don't think it's a coincidence that both Wolf and Reggie are on
networks with non-equivalent
Now I understand what you are getting at (took me a long time).
I can confirm that my DNS server serves any request from inside the
network. I have a log on the router monitoring outgoing traffic. Under
NO circumstances is a DNS request going out UNLESS the internal server
is down but the clients
@Wolf: Is it the case that when using the NM-controlled dnsmasq, fully
qualified domain names can always be resolved using the glibc resolver
but short domain names cannot be resolved using the resolver, despite
the correct search option being present in /etc/resolv.conf; that this
anomaly does
nm-tool | grep DNS gives
DNS: 10.1.0.4
DNS: 10.1.0.254
DNS: 195.202.128.3
dig s4 gives nothing
wolf@mbp:~$ dig s4
; DiG 9.8.1-P1 s4
;; global options: +cmd
;; Got answer:
;; -HEADER- opcode: QUERY, status: NXDOMAIN, id: 60009
;; flags: qr rd
In Ubuntu 12.10 this issue is as prominent as ever.
On resume from RAM or after boot, dnsmasq requires about 5 minutes to
resolve names correctly.
Workaround: For ssh I use IP addresses
Thunderbird requires a 5 Minute waiting period after resume
Evolution requires two or three attempts to start,
** 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.
https://bugs.launchpad.net/bugs/998712
Title:
domain name completion broken when dnsmasq is used
To
** Changed in: dnsmasq (Ubuntu)
Status: Expired = 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/998712
Title:
domain name completion broken when dnsmasq is used
To
[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.
Thanks for the update, Reggie.
Wolf, can you please put me in touch with one or more of the dozens of
people you mentioned above (#21) who have this (#998712) problem?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to dnsmasq in Ubuntu.
Thomas,
I'm not sure if an update has been pushed that has fixed my problem,
but I'm not seeing the issue at the moment, I was going to work on the
issue earlier this weekend, but some events come up. I have rebooted
several of my systems and I'm just not seeing the issue right now. I'll
Reggie: First of all, thanks for providing information about the
malfunction on your system. We will get to the bottom of this!
To get very clear on what's happening I will summarize. Let me know if
any of the following is wrong.
With the following resolv.conf (omitting comments)
Reggie, I wrote:
First I'd like to rule out the possibility of side-effects of #1003842.
Please eliminate the lines
server=24.177.176.38
server=97.81.22.195
from /run/nm-dns-dnsmasq.conf
Just thought of a hitch.
After removing these lines dnsmasq has to be restarted or it won't
notice
Thomas,
I understand that you have not set up a simulation test bed and that
your questions are directed to understand the problem. You have found
out that you may have misinterpreted some pieces.
Reggie seems to have the same problem as I (and to my knowledge more
than a dozen of others) have.
Wolf, dnsmasq is not going to be taken out of the distribution.
Probably you meant that NM-driven dnsmasq shouldn't be enabled by
default. If so then please file another report against network-manager
with the title Please don't enable dnsmasq by default so long as it's
so buggy. But that
Having just re-read the discussion, I realize that I may have
misunderstood the problem. I'll try to summarize it.
Wolf, are you saying that when using the NM-enslaved dnsmasq, fully
qualified domain names can always be resolved using the resolver(3) but
short domain names cannot be resolved
I'm havin a very simular issue with the new DNS setup in 12.04 on my
laptop. I run a server at home which runs bind. The server is setup
correctly, all my machines with 11.04 installed work as expected, but
the machines I have upgraded to 12.04 have issues. My server provides
name resolution
Wolf: I forgot to mention earlier that the reason I have to keep asking
questions is that I am unable to reproduce the problem here. On my
system, domain name completion works as expected with
NetworkManager+dnsmasq.
I just tried installing nscd to see if that made any difference, but it
did not
35 matches
Mail list logo
