Opened 12 years ago

Closed 2 years ago

#634 closed defect (wontfix)

can not resolve A records for domains ending with *.in-addr.arpa

Reported by: Safari Owned by:
Priority: Very Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version: 0.1.2.19
Severity: Normal Keywords: dns tor-relay prop219,
Cc: Safari, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description (last modified by nickm)

Local dnscache, no tor:
$ DNSCACHEIP=127.0.0.1 dnsqr a 130.14.169.217.in-addr.arpa
1 130.14.169.217.in-addr.arpa:
61 bytes, 1+1+0+0 records, response, noerror
query: 1 130.14.169.217.in-addr.arpa
answer: 130.14.169.217.in-addr.arpa 3285 A 217.169.14.130

Local dnscache, forwarding queries to tor:
$ DNSCACHEIP=127.0.0.69 dnsqr a 130.14.169.217.in-addr.arpa
1 130.14.169.217.in-addr.arpa:
temporary failure

2008-03-18 21:22:17.921528231 [info] addressmap_register(): Temporary addressmap ('REVERSE[130.14.169.217.in-addr.arpa]' to '130.14.169.217.in-addr.arpa') not performed, since it's already mapped to '130.14.169.217.in-addr.arpa'
Tor version 0.2.1.0-alpha-dev (r14110).

[Automatically added by flyspray2trac: Operating System: All]

Child Tickets

Change History (7)

comment:1 Changed 11 years ago by nickm

I think this is a limitation of the current in-Tor name resolution protocol, which only handles a few common
cases of DNS. If so, solving this would probably require a richer resolution system, mapping more DNS request types.
That would be neat, though it would require somebody to do a design proposal and code it all up.

Is the actual case of A records for .in-addr.arpa domains actually something with practical value?

comment:2 Changed 11 years ago by Safari

I don't know about the practical value, but it would be nice if it behaved consistently.

What if in the future there comes a need for TXT records for in-addr.arpa domains?
Now not even TXT is supported.

comment:3 Changed 11 years ago by nickm

The right solution here is a more general DNS-over-Tor protocol; the one right now is really only designed for cheap
gethostbyname/gethostaddr emulation. If somebody wrote a design proposal for this (see 001-process.txt), that would
be great.

comment:4 Changed 9 years ago by nickm

Description: modified (diff)
Keywords: dns added
Milestone: post 0.2.1.xTor: unspecified

Moving to the unspecified milestone: it is not hurting anything for now, but it would be neat to fix as a part of any DNS revamp.

comment:5 Changed 7 years ago by nickm

Keywords: tor-relay added

comment:6 Changed 7 years ago by nickm

Component: Tor RelayTor

comment:7 Changed 2 years ago by nickm

Cc: Safari,nickmSafari, nickm
Keywords: prop219 added
Resolution: Nonewontfix
Severity: Normal
Status: newclosed

We'll get an implementation for this dubious feature if we eventually implement prop219, I guess. But I don't think we'd do this for its own sake; it's just silly.

Note: See TracTickets for help on using tickets.