On Tue, Jan 23, 2018 at 08:53:00AM +, nusenu wrote:
> It is probably worth mentioning that
> node.moneroworld.com resolves to 32 A records,
> node.xmr.be resolve to 55 A records,
> which might be the problem here?
When you do a "host node.moneroworld.com", its answer starts with:
;; Truncated
I can confirm that you can apparently not resolve
"node.moneroworld.com"
and
"node.xmr.be"
via tor.
I didn't test across multiple exits because I assume it is not related to the
exit.
I tested it against a tor DNSPort, I don't think that has anything todo with
torsocks.
(That is why I changed
I'm having a strange problem with torsocks and resolving some dns records - one of the example i've managed to replicate on torsocks v2.2.0 and v2.1., tor version 0.2.9.11 (git-aa8950022562be76), version 0.3.2.9 (git-64a719dd25a21acb).. I've tested this on several different machines/ips/isps so it
