Opened 19 months ago

Last modified 17 months ago

#24937 new defect

tor failing to resolve some dns records

Reported by: baageg Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.9.11
Severity: Normal Keywords: tor-exit, tor-dns, 034-triage-20180328, 034-removed-20180328
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

I'm having a strange problem with torsocks and resolving some dns records - one of the example i've managed to replicate on torsocks v2.2.0 and v2.1., tor version 0.2.9.11 (git-aa8950022562be76), version 0.3.2.9 (git-64a719dd25a21acb).

I've tested this on several different machines/ips/isps so it not localized problem.

$ telnet node.moneroworld.com
Trying 45.63.14.175...
Trying 96.43.139.226...
^C
$ torsocks telnet node.moneroworld.com
1516143453 ERROR torsocks[4459]: Unable to resolve. Status reply: 4 (in socks5_recv_resolve_reply() at socks5.c:683)
telnet: could not resolve node.moneroworld.com/telnet: Non-recoverable failure in name resolution

same issue can be replicated with node.xmr.be. Both domain have round robin configured for this record - they return multiple A records. Could this be the issue with this?

Child Tickets

Change History (11)

comment:1 Changed 19 months ago by baageg

Summary: tor failing to resolve somedns recordstor failing to resolve some dns records

comment:2 Changed 19 months ago by cypherpunks

Component: Core Tor/TorsocksCore Tor/Tor

I can confirm that you can apparently not resolve
"node.moneroworld.com"
and
"node.xmr.be"
via tor.
I didn't test across multiple exits because I assume it is not related to the exit.

I tested it against tor's DNSPort, I don't think that has anything todo with torsocks.
(That is why I changed the component for this ticket on trac)

It is probably worth mentioning that
node.moneroworld.com resolves to 32 A records,
node.xmr.be resolve to 55 A records,
which might be the problem here?

Has tor a limit on how much it can take?

comment:3 Changed 19 months ago by cypherpunks

Owner: dgoulet deleted
Status: newassigned

(removing dgoulet as owner since it was only him because the component used to be torsocks)

comment:4 Changed 19 months ago by cypherpunks

Status: assignednew

comment:5 Changed 19 months ago by cypherpunks

When you do a "host node.moneroworld.com", its answer starts with:
;; Truncated, retrying in TCP mode.

I'm guessing that could be a good hint.

--Roger

comment:6 Changed 19 months ago by cypherpunks

Parent ID: #24968

comment:7 Changed 19 months ago by cypherpunks

Parent ID: #24968

removing parent ID since this has nothing todo with 0.3.2.9 (happens on 0.3.1.9 as well)

comment:8 Changed 19 months ago by teor

Keywords: tor-exit tor-dns added; dns resolving records removed
Milestone: Tor: 0.3.4.x-final
Points: 1
Priority: HighMedium
Version: Tor: 0.3.2.9Tor: 0.2.9.11

The next step is to test this on an exit, and see what the error is.
Chutney would be a good tool to run a client and exit, and log at info or debug level, without logging any user data.

comment:9 Changed 17 months ago by nickm

Keywords: 034-triage-20180328 added

comment:10 Changed 17 months ago by nickm

Keywords: 034-removed-20180328 added

Per our triage process, these tickets are pending removal from 0.3.4.

comment:11 Changed 17 months ago by nickm

Milestone: Tor: 0.3.4.x-finalTor: unspecified

These tickets, tagged with 034-removed-*, are no longer in-scope for 0.3.4. We can reconsider any of them, if time permits.

Note: See TracTickets for help on using tickets.