Opened 9 months ago

Last modified 9 months ago

#26089 new enhancement

collect and archive DNS resolver data of tor exits

Reported by: cypherpunks Owned by: metrics-team
Priority: Medium Milestone:
Component: Metrics/CollecTor Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #26091 Points:
Reviewer: Sponsor:

Description

context:
https://medium.com/@nusenu/who-controls-tors-dns-traffic-a74a7632e8ca

"

  1. Add DNS related information to Relay Search (a long term item)

It would be nice and probably effective to have information about DNS resolvers show up on Relay Search, because it is a popular tool for relay operators to check on their relay state. Operators could easily see if they use any less desirable DNS resolvers if that information is shown on Relay Search. That way we could even reach operators who have no or invalid ContactInfo data, but multiple steps are required before this could happen:
The currently unavailable data needs to be

collected and regularly updated

"

Child Tickets

Change History (2)

comment:1 Changed 9 months ago by cypherpunks

Parent ID: #26091

comment:2 Changed 9 months ago by irl

I think this is a great idea and something we should do. Exit address information comes from exit lists, and resolver information should probably be part of those lists generated by the exit scanner (currently TorDNSEL but maybe exitmap in the future).

For now though, this is a big task and not very high priority.

Note: See TracTickets for help on using tickets.