Feature request: Add support for AAAA and PTR queries

[phantomcraft]

Tor manual says:

DNSPort [address:]port|auto [isolation flags]
f non-zero, open this port to listen for UDP DNS requests, and resolve them anonymously. This port only handles A, AAAA, and PTR requests---it doesn’t handle arbitrary DNS request types. Set the port to
"auto" to have Tor pick a port for you. This directive can be specified multiple times to bind to multiple addresses/ports. See SocksPort for an explanation of isolation flags. (Default: 
0)

I cannot forward DNSPort using unix sockets to provide AAAA and PTR support for network namespaces without veth tunnels, that's why I'm requesting.

[phantomcraft]

This small program can serve as a basis: https://github.com/zeroshirts/anotherproxy/blob/dev/main.go

Can you implement this feature?

[bfix]

Sorry, I am currently busy doing other things, but feel free to fork the repository and send a merge request. Thanks. >Y<

[phantomcraft]

@bfix

I don't know how to program in Go.

I found this plugin for CoreDNS: https://github.com/schoentoon/tordns/blob/master/tordns.go

Perhaps could serve as a basis.

[phantomcraft]

I tested the latest commit, but doesn't work still.

goo.gl has two IPs, one is IPv4 the other 6.

user@localhost:/dev/shm/Tor-DNS$ host -p 53 goo.gl
goo.gl has address 74.125.24.139
goo.gl has address 74.125.24.138
goo.gl has address 74.125.24.113
goo.gl has address 74.125.24.100
goo.gl has address 74.125.24.101
goo.gl has address 74.125.24.102
goo.gl has IPv6 address 2404:6800:4003:c03::71

When queried with Tor-DNS, it only shows the IPv4 address:

user@localhost:/dev/shm/Tor-DNS$ ./tor-dns -p "[::]:1053" -v
[Query:7a:1] goo.gl
[Response:7a] 216.58.208.46
[Query:a62c:28] goo.gl
[Response:a62c] 216.58.208.46
[Query:3d3b:15] goo.gl
[Response:3d3b] 216.58.208.46

user@localhost:/dev/shm/Tor-DNS$ host -p 1053 goo.gl
goo.gl has address 216.58.208.46
goo.gl has address 216.58.208.46
goo.gl has address 216.58.208.46

[mtrojnar]

The feature you requested was AAAA and PTR support, and not returning more than one response. If you requested returning more than one response we could close your request without any further development, because SOCKS returns only one response, and there is nothing we can do about it.