Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #12582

Closed
Open
Opened Jul 09, 2014 by Arturo Filasto@art

Add support for detecting the DNS resolver used by a probe

Currently when running the dns_consistency test if no resolvers are specified we attempt to read it from /etc/resolv.conf. Sometimes what is found inside of resolv.conf is the actual address of a DNS resolver, but it may be something in the local network.

To understand where censorship is actually happening it would be ideal to know the address of the true resolver that is being used. This can be achieved by delegating a subdomain of ooni.nu to a nameserver that is controlled by us. This way every time a DNS query for <RANDOM_STRING>..ooni.nu is done we will see a query to our nameserver.

This nameserver will simply return to every A query the IP address that issued the request. A test helper for this has already been implemented: https://github.com/TheTorProject/ooni-backend/blob/master/oonib/testhelpers/dns_helpers.py#L26.

What needs to be done is added support to ooni-probe for performing this lookup and using the data in the report.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#12582