Project

General

Profile

Feature #6070

Support arbitrary DNS queries

Added by Tails over 4 years ago. Updated over 3 years ago.

Status:
Confirmed
Priority:
Low
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

QA Check:
Feature Branch:
Type of work:
Code
Blueprint:
Easy:
No
Affected tool:

Description

Rationale

The Tor DNS resolver Tails is currently using lacks support for most types of DNS queries except "A". A better user experience would be provided if Tails was able to resolve any kind of DNS queries out of the box.

Implementation

Inserting ttdnsd into the DNS resolver loop is the obvious solution. ttdnsd listens for UDP DNS requests and forwards these via the Tor SOCKS proxy to an open recursive DNS resolver on the Internet.

But we cannot just replace pdnsd with ttdnsd as the latter, unlike the former, does no caching at all. The DNS resolution process could then be:

bc. resolv.conf -> DNS forwarding+caching proxy -> ttdnsd -> Tor

Forwarding+caching DNS proxy candidates:

  • pdnsd: already installed on Tails
  • dnsmasq: very flexible DNS forwarder
  • unbound: "recursive-only" caching DNS server which can perform DNSSEC validation of results; the DNSSEC feature is appealing; its "forward zones" feature seems to allow plugging it into the proposed DNS resolution process: forwarding a zone called "." seems sufficient; see Haven SVN for examples that may not be working yet (as of June 2011, see tor-talk ML)

=> keeping our known-working pdnsd configuration seems to be the safe choice.

Work is being done on this topic in our feature/support_arbitrary_dns_queries Git branch.

<blockquote>

Merged in devel, with everything but .onion / .exit being resolved using ttdnsd because of bug #3369 on Tor Project's Trac. This bug was fixed in the Tor 0.2.2.x branch; let's wait for this release to be stabilized; once we ship it, we can move to "try the Tor resolver first, fallback on ttdnsd if the former fails".

<blockquote>

The feature/support_arbitrary_dns_queries Git branch implements the above described policy. Only thing missing is Tor 0.2.2.x.

<blockquote>

Tor 0.2.2 is now the official Tor stable tree. Time to merge.

done in 0.8

</blockquote>

</blockquote>

</blockquote>


Related issues

Related to Tails - Feature #6158: Fix secure Icedove autoconfig wizard in Tails Resolved
Blocks Tails - Bug #7453: Pidgin cannot find out the correct XMPP server to connect to, without SRV DNS lookups Confirmed 06/23/2014

History

#1 Updated by intrigeri over 4 years ago

  • Type of work set to Code

Type of work: Code

#2 Updated by intrigeri about 4 years ago

  • Status changed from Resolved to Confirmed
  • Priority changed from Normal to Low
  • Easy set to No

Reopening, as we've removed ttdnsd (too buggy) from the default DNS loop.

#3 Updated by BitingBird over 3 years ago

  • Subject changed from support arbitrary dns queries to Support arbitrary dns queries

#4 Updated by intrigeri over 3 years ago

  • Subject changed from Support arbitrary dns queries to Support arbitrary DNS queries

#5 Updated by intrigeri almost 3 years ago

  • Blocks Bug #7453: Pidgin cannot find out the correct XMPP server to connect to, without SRV DNS lookups added

Also available in: Atom PDF