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
  • #635
Closed
Open
Issue created Mar 18, 2008 by Trac@tracbot

eventdns and caching of NXDOMAIN

Local DNS proxy might not include the SOA record (in case of NXDOMAIN) when it is resolving for tor, but faking a SOA record should be easy... maybe a config option or #define for the TTL of cached NXDOMAIN?

Now in case of NXDOMAIN, eventdns does not include Authority RR with SOA record, so clients querying tor can not cache the NXDOMAIN. They just keep on querying the same thing again and again.

[Automatically added by flyspray2trac: Operating System: All]

Trac:
Username: Safari

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