This possibly arises from bug #1003842.
What is possibly happening: the second or third nameserver on the list
of available nameservers supplied to dnsmasq replies quickly to
dnsmasq's query with a negative answer and dnsmasq immediately passes
that negative answer back to the resolver.
When dnsmasq is not used, the resolver tries the first nameserver on the
list first, only trying the second nameserver after a timeout period.
If this is the problem then the "correct" solution is to fix the
malfunctioning nameserver or to remove it from the list.
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1522057
Title:
DNS resolution stops working after some time
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1522057/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
