-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
We have a ticket open for this:
https://trac.torproject.org/projects/tor/ticket/11600
I think this is a libevent error.
It happened to me on FreeBSD 10 with Bind910, FreeBSD 10 with Unbound, Debian Wheezy with Unbound, Debian Wheezy with Bind, Debian Wheezy with ISP-assigned-resolvers (pretty much everything). Happened initially on Tor 0.2.4.21, followed to all upgrades of 0.2.4.x series and also happens currently on 0.2.5.10, but on the latest version the error appears not to occur as often as it used to in 0.2.4.x series.
On 2/21/2015 4:06 AM, Sebastian Urbach wrote:
On February 21, 2015 2:09:48 AM Libertas libertas@mykolab.com wrote:
Hi,
On 02/20/2015 06:31 PM, Jacob Corbin wrote:
I'm sorry for the late reply on this but I've been having problems
with my
Internet connection and am trying to catch up on emails. I've never
received
that message but months ago I started getting messages in the posts you referenced like:
Jan 05 12:36:58.138 [warn] eventdns: All nameservers have failed Jan 05 12:36:58.354 [notice] eventdns: Nameserver 192.0.2.7 is back up
I get this constantly on my exit node running OpenBSD with a local Unbound caching DNS server. I think libevent (this is part of libevent, right?) is just a little too trigger-happy with reporting DNS requests as failed, as my failures never last more than a second. I was considering opening a ticket about this.
Unbound@Debian here, the same effect. Thanks in advance if you do open a ticket.