I can confirm this behaviour with any hostname I tried (including e.g. www.google.com).
The "problem" seems the interaction between links2 and "torsocks" (and also "torify" which does more or less the same). It surely not a DNS or TLD detection issue, because both, "links2 https://dev.lemmy.ml/communities/page/1"; as well as "links2 -socks-proxy localhost:9050 -only-proxies 1 https://dev.lemmy.ml/communities/page/1"; (which is the official way of using links2 with Tor). And "tor-resolve dev.lemmy.ml" works as expected, too. It is though currently unclear to me, _why_ links2 doesn't seem to work with "torsocks" or "torify". ** Changed in: links2 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1853458 Title: "host not found" when navigating to dev.lemmy.ml To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/links2/+bug/1853458/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
