On Fri, 13 Mar 2020 15:22:49 +0300 Станислав armik900@gmail.com wrote:
13.03.2020, 14:55, "teor" teor@riseup.net: Hi, Post the entire file without shortening or removing any line. If it complains about parse error, there must be something wrong in it, but you don't noticeor don't think it is wrong. People on the mailing list can check if it's ok,but again only if you post the entire file (copy-paste or attach). С уважением, Станислав <resolv.conf> There could be a few things wrong here. Try setting ServerDNSResolvConfFile to /dev/null, or a world-readable empty file, and see if your problem goes away. If it does, here are some common issues to check: What are the permissions on /etc.resolv.conf ? Can the tor user read the file? Is the file a symlink? (macOS does this, not sure if some Linux distros do as well) Are there any hidden characters in the file? Does it use Unix newlines? Tor uses libevent's evdns_base_resolv_conf_parse() to parse the file. https://libevent.org/doc/dns_8h.html#a7e3a053e25ae7c045944a5db0947babb How old is your version of libevent?
FYI in a private discussion we figured out that the trailing dot in "search lan." was indeed what caused the issue.