Gave up switched to 'named' and now it's working fine.
Entered BUG: https://trac.torproject.org/projects/tor/ticket/18580
Be advised, anyone running a fast exit with 'unbound' should switch to
using 'named'.
___
tor-relays mailing list
tor-relays@lists.
Brian,
That's all quite interesting. Thanks for sharing. I hope this work
goes well. It would help move Tor forward toward the cloud-based
software model that's becoming more and more popular.
Greg
On Mon, Mar 14, 2016 at 12:29 PM, Brian 'redbeard' Harrington
wrote:
> Greg,
>
> Thank *you* for th
Hit a repeat of an earlier incident:
https://lists.torproject.org/pipermail/tor-relays/2016-January/008621.html
message from tor daemon is
Resolved [scrubbed] which was already resolved; ignoring
About 5400 of these messages over 37 hours, during which the relay
dropped down to 30% of usual
Dhalgren Tor wrote:
> Bug #18580: exit relay fails with 'unbound' DNS resolver when lots of
> requests time-out
>
> https://trac.torproject.org/projects/tor/ticket/18580
I wouldn't go that far. I've been running with Unbound for ~1.5 years
now (AFAIK) without issue. I've also been told that the c
Nothing wrong with 'unbound'. Problem is bug in Tor daemon
interaction with 'unbound' that brings exit effectively offline when
GoDaddy blocks requests from it. This can happen to any fast exit
anytime. GoDaddy has been blocking high-volume DNS requesters since
2011, and recent activity by some
Bug #18580: exit relay fails with 'unbound' DNS resolver when lots of
requests time-out
https://trac.torproject.org/projects/tor/ticket/18580
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinf
