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 the component for this ticket on trac)
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?
Has tor a limit on how much it can take?
https://trac.torproject.org/projects/tor/ticket/24937
On Tue, Jan 23, 2018 at 08:53:00AM +0000, 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, retrying in TCP mode.
I'm guessing that could be a good hint.
--Roger
-
blaze glory -
nusenu -
Roger Dingledine