Opened 14 years ago

Last modified 8 years ago

#321 closed defect (Fixed)

TOR resolver appends localdomain to DNS requests

Reported by: peterpramb Owned by:
Priority: Low Milestone: 0.1.2.x-final
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: peterpramb Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


For some time now I see lots of AAAA requests in the query log of my domain's authoritative nameserver
looping back from my upstream resolvers. Here are some examples:

query:<mydomain> IN AAAA -E
query:<mydomain> IN AAAA -E
query:<mydomain> IN AAAA -E
query:<mydomain> IN AAAA -E
query:<mydomain> IN AAAA -E
query:<mydomain> IN AAAA -E

Since the host running TOR is IPv6 enabled the resolver first tries to lookup IPv6 addresses. However
the problem is not the AAAA query, which should be "resolved" by #280, but the fact that the host's
domain name is added if the first query failed.

This even works with non-FQDN names, eg. use this to access my webserver:


As a workaround someone can set LOCALDOMAIN=. in the TOR init script, but appending the default domain
and using the domain search list should really be disabled by TOR itself.

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (3)

comment:1 Changed 14 years ago by nickm

This should be fixed in 0.1.2.x-final, assuming that we move everything over to the new eventdns.c
internal resolver. But just to be sure, I'm making the dnsworker code work too.

comment:2 Changed 14 years ago by nickm

flyspray2trac: bug closed.
Fixed in svn repository as of r8225; should be fixed in next alpha release.

comment:3 Changed 8 years ago by nickm

Component: Tor Relay โ†’ Tor
Note: See TracTickets for help on using tickets.