Skip to content

GitLab

  • Menu
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 823
    • Issues 823
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 30
    • Merge requests 30
  • 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
  • #3536
Closed
Open
Created Jul 07, 2011 by Trac@tracbot

Tor sends a RESOLVEFAILED event when a reverse lookup succeeds.

Having SETEVENTS ADDRMAP and STREAM, I get

650 STREAM 23575 NEWRESOLVE 0 8.8.8.8:0 PURPOSE=DNS_REQUEST
650 STREAM 23575 NEW 7180 8.8.8.8:0 SOURCE_ADDR=(Tor_internal):58649 PURPOSE=DNS_REQUEST
650 STREAM 23575 SENTRESOLVE 7180 8.8.8.8:0
650 ADDRMAP REVERSE[8.8.8.8] google-public-dns-a.google.com "2011-07-07 01:55:07" EXPIRES="2011-07-07 05:55:07"
650 STREAM 23575 FAILED 7180 8.8.8.8:0 REASON=RESOLVEFAILED
650 STREAM 23575 CLOSED 7180 8.8.8.8:0 REASON=DONE

or something similar with any successful reverse DNS request. I'm using 0.2.3.1-alpha-dev (git-e273890b).

Trac:
Username: katmagic

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