#24968 closed defect (user disappeared)

Tor's DNSPort become unreliable after I upgraded to latest 0329 stable.

Reported by: cypherpunks Owned by:
Priority: Medium Milestone: Tor: 0.3.3.x-final
Component: Core Tor/Tor Version: Tor: 0.3.2.9
Severity: Normal Keywords: tor-dns, regression?, 033-triage-20180320, 033-removed-20180320
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

I'm using DNSPort to query A record for a long time.
Thing turned to sh*t after I upgraded my Tor to Tor.exe(hash sha1=b7c79fb686dcabacd046fc7812c782c990c398b5).

Before upgrade, DNSPort query my responses with 90%+ availability.
Now, it just doesn't work. About 50-60%.

What did go wrong?

So I queried DNS over Tor[0]. It works about 80-90% avail.

[0]

User ---(8.8.8.8/8.8.4.4/udp)--- tor ---> torexit ---> 8.8.8.8/4/4

Child Tickets

Change History (7)

comment:1 Changed 14 months ago by cypherpunks

And if I use SOCKS5, tor just works. SOmething wrong on DNSPort code.

comment:2 Changed 14 months ago by teor

Keywords: tor-dns regression? added
Milestone: Tor: 0.3.3.x-final
Points: 1
Priority: Very HighMedium
Severity: CriticalNormal
Type: taskdefect
Version: Tor: 0.3.2.9

Setting priorities does not get your bug looked at faster.

comment:3 Changed 14 months ago by nickm

When you say you upgraded to tor 0.3.2.9 -- what did you upgrade _from_? What is the last release where DNSPort works well for you?

comment:4 Changed 14 months ago by nickm

Status: newneeds_information

comment:5 Changed 12 months ago by nickm

Keywords: 033-triage-20180320 added

Marking all tickets reached by current round of 033 triage.

comment:6 Changed 12 months ago by nickm

Keywords: 033-removed-20180320 added

Mark all not-already-included tickets as pending review for removal from 0.3.3 milestone.

comment:7 Changed 12 months ago by nickm

Resolution: user disappeared
Status: needs_informationclosed

No answer in 2 months; closing.

Note: See TracTickets for help on using tickets.