Opened 10 months ago

Last modified 10 months ago

#31290 new enhancement

provide DNS health metrics for tor exit relay operators

Reported by: nusenu Owned by:
Priority: Medium Milestone:
Component: Core Tor/Tor Version:
Severity: Normal Keywords: network-health
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


every now and then I'm in contact with relay operators
about the "health" of their relays.
Following these 1:1 discussions and the discussion on tor-relays@
I'd like to rise this issue with you (the developers) with the goal
to help improve relay operations and end user experience in the long term:

Current situation:
Arthur Edelstein provides public measurements to tor exit relay operators via
his page at:
This page is updated once daily.

the process to use that data looks like this:

  • first they watch Arthur's measurement results
  • if their failure rate is non-zero they try to tweak/improve/change their setup
  • wait for another 24 hours (next measurement)

This is a somewhat suboptimal and slow feedback loop and is probably also
less accurate and less valuable data when compared to the data the tor
process can provide.

Suggestion for improvement:

Exposes the following DNS status information
via tor's controlport to help debug and detect DNS issues on exit relays:

(total numbers since startup)

  • amount of DNS queries send to the resolver
  • amount of DNS queries send to the resolver due to a RESOLVE request
  • DNS queries send to resolver due to a reverse RESOLVE request
  • amount of queries that did not result in any answer from the resolver
  • breakdown of number of responses by response code (RCODE)

  • max amount of DNS queries send per curcuit

If this causes a significant performance impact this feature should be disabled
by default.

Child Tickets

Change History (1)

comment:1 Changed 10 months ago by gk

Keywords: network-health added
Note: See TracTickets for help on using tickets.