Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Tor Tor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 328
    • Issues 328
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 31
    • Merge requests 31
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Core
  • TorTor
  • Issues
  • #18580
Closed
Open
Issue created Mar 19, 2016 by Dhalgren@Dhalgren

exit relay fails with 'unbound' DNS resolver when lots of requests time-out

per

[tor-relays] What does this message mean in my tor logs? https://lists.torproject.org/pipermail/tor-relays/2016-January/008621.html

[tor-relays] unbound bogs down strangely, degrading exit relay https://lists.torproject.org/pipermail/tor-relays/2016-March/008918.html

Relay daemon ceases to service Tor Browser requests, timing out, when a local instance of 'unbound' is the DNS resolver and large numbers of DNS requests time-out.

Works fine when 'named' is swapped in place of 'unbound'.

GoDaddy DNS stops responding when large numbers of queries are submitted and this was observed as the particular trigger.

To reproduce, configure the SOA+NS records for several thousand dummy domains to point to a non-responding IP, then generate large numbers of requests against them.

The commands

unbound-control dump_requestlist unbound-control dump_infra

are helpful for identifying the state.

Have debug-level daemon trace taken when relay was in the unresponsive condition described.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking