I've seen lots of issues in the past with either ISPs with non-compliant DNS services or routers with non-compliant DNS services (including transparent filtering/redirection). This can cause erroneous DNS responses to end up being cached, or resolvers being marked as unreachable.
I wonder if this is the issue here? I would debug this sort of issue with tcpdump and wireshark, using dig to generate DNS queries locally, using tcpdump to see what dnsmasq is sending out after the hang, and checking all previous requests and replies to make sure that dnsmasq is really doing something wrong. I'm not sure how to do this without a developer having the ability to reproduce the problem though. I'll set the Priority of the dnsmasq task to Medium for now, but if it turns out that a wide range of Ubuntu users are affected (ie. lots of routers or lots of ISPs) then we may need to review this. ** Changed in: dnsmasq (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994963 Title: DNS stops working after some time To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/994963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
