Opened 2 years ago

Last modified 23 months ago

#21499 new defect

client_dns_incr_failures while passing not hostname but only IP

Reported by: acceleraTor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version: Tor: 0.2.4.7-alpha
Severity: Normal Keywords: tor-client, ipv6, triaged-out-20170308, annoying dns
Cc: Actual Points:
Parent ID: Points: 1
Reviewer: Sponsor:

Description

I frequently find in logs that while only passing IP to socksport instead of hostname, tor still tell me resolving failed while it shouldn´t have to resolve anything.
Feb 18 15:09:21.000 [info] {APP} client_dns_incr_failures(): Address [2001:41b8:202:deb:213:21ff:fe20:1426] now has 1 resolve failures.
Feb 18 15:09:22.000 [info] {APP} client_dns_incr_failures(): Address [2001:41b8:202:deb:213:21ff:fe20:1426] now has 2 resolve failures.
Feb 18 15:09:30.000 [info] {APP} client_dns_incr_failures(): Address [2001:41b8:202:deb:213:21ff:fe20:1426] now has 3 resolve failures.
Feb 18 15:09:40.000 [info] {APP} client_dns_incr_failures(): Address [2001:41b8:202:deb:213:21ff:fe20:1426] now has 1 resolve failures.
Feb 18 15:09:40.000 [info] {APP} client_dns_incr_failures(): Address [2001:41b8:202:deb:213:21ff:fe20:1426] now has 2 resolve failures.
Feb 18 15:09:45.000 [info] {APP} client_dns_incr_failures(): Address [2001:41b8:202:deb:213:21ff:fe20:1426] now has 3 resolve failures.
Feb 18 15:09:47.000 [info] {APP} client_dns_incr_failures(): Address [2001:41b8:202:deb:213:21ff:fe20:1426] now has 1 resolve failures.

Child Tickets

Change History (7)

comment:1 Changed 2 years ago by acceleraTor

Component: - Select a componentCore Tor/Tor

comment:2 Changed 2 years ago by teor

Keywords: ipv6 added
Version: Tor: 0.3.0.3-alphaTor: 0.2.4.7-alpha

This appears to be a duplicate of #21311 or perhaps #21346.
If so, it's been a bug since IPv6 support was introduced.
Does it only happen for IPv6 address literals?

Clients may not be choosing IPv6-supporting exits for these literals, and exits may not be responding correctly, either.

comment:3 Changed 2 years ago by nickm

Clients may not be choosing IPv6-supporting exits for these literals, and exits may not be responding correctly, either.

If that's the issue we might be able to solve this by setting some flags on the connection as we parse the address.

But if this is not a regression, should it maybe wait for 0.3.1?

comment:4 Changed 2 years ago by nickm

Milestone: Tor: 0.3.0.x-finalTor: 0.3.1.x-final

comment:5 Changed 2 years ago by nickm

Points: 1

comment:6 Changed 2 years ago by nickm

Keywords: triaged-out-20170308 added
Milestone: Tor: 0.3.1.x-finalTor: unspecified

Deferring all 0.3.1 tickets with status == new, owner == nobody, sponsor == nobody, points > 0.5, and priority < high.

I'd still take patches for most of these -- there's just nobody currently lined up to work on them in this timeframe.

comment:7 Changed 23 months ago by nickm

Keywords: annoying dns added
Note: See TracTickets for help on using tickets.