Tor DNS resolver only supports UDP sockets so can't resolve large RRs
When Tor attempts to resolve a RR and receives truncated required, it gives up and fails rather than trying again over a TCP socket, as an example:
tor-resolve test2.pho.be # works, whilst tor-resolve test1.pho.be # always fails.
The problem seems to be in evdns.c / libevent
Trac:
Username: murble
Activity
changed milestone to %Tor: unspecified in legacy/trac
added component::core tor/tor in Legacy / Trac dns in Legacy / Trac milestone::Tor: unspecified in Legacy / Trac needs-design in Legacy / Trac priority::low in Legacy / Trac prop219 in Legacy / Trac reporter::murble in Legacy / Trac severity::normal in Legacy / Trac status::new in Legacy / Trac tor-relay in Legacy / Trac type::enhancement in Legacy / Trac labels
This probably make the most sense to tackle as part of a larger effort to support real DNS requests over Tor. Right now, even if Tor servers could receive a record larger than a UDP packet will support, it wouldn't be enough, since there would be no specified way in the Tor lookup protocol to send it back to a client.
So for starters, we're going to need a "get dns right in tor" proposal. That'll probably want a ticket of its own, unless we already have one
Trac:
Keywords: dns deleted, dns needs-proposal added
Milestone: N/A to Tor: unspecified
Version: Tor: unspecified to N/A
Type: defect to enhancement
Trac:
Cc: N/A to intrigeri@boum.orgSee legacy/trac#11741 (moved) too. It happens for real.
Trac:
Username: ToBeFree
Cc: intrigeri@boum.org to intrigeri@boum.org, tobias@freiwuppertal.dementioned in issue legacy/trac#11741 (moved)
moved from legacy/trac#4734 (moved)
added Feature label and removed 1 deleted label