[tor-bugs] #18580 [Tor]: exit relay fails with 'unbound' DNS resolver when lots of requests time-out

[Tor Bug Tracker & Wiki]

#18580: exit relay fails with 'unbound' DNS resolver when lots of requests time-out
----------------------+------------------------------
 Reporter:  Dhalgren  |          Owner:
     Type:  defect    |         Status:  new
 Priority:  Medium    |      Milestone:
Component:  Tor       |        Version:  Tor: 0.2.7.6
 Severity:  Major     |     Resolution:
 Keywords:            |  Actual Points:
Parent ID:            |         Points:
 Reviewer:            |        Sponsor:  None
----------------------+------------------------------
Changes (by Dhalgren):

 * status:  needs_information => new
 * severity:  Normal => Major


Comment:

 Affects `tor` running against `Unbound`.  After putting `named` up the
 GoDaddy block remains in effect even now.  Exit ranked about 60 works
 perfectly with `named` and becomes absolutely unusable with Unbound in
 place.  To my eyes that is a major severity bug (though perhaps not high
 priority).  Fairly obvious the problem is tor daemon's handing of some
 quirk of timed-out request failures done the `Unbound` way.  My guess is
 nothing wrong with Unbound.

 Am the second operator to experience this problem and fix it with `named`.

 Have debug level trace of about 3-5 minutes of the relay-unresponsive
 state with known test queries being made via TBB.  Too big to put here,
 will upload to another service if someone asks.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/18580#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online