AutomapHostsOnResolve often returns real IP

Hi,

I'm running a small node for years. Few months ago a started using auto-mapping hosts to virtual IP. Tor often returns real IP address instead of virtual one. For example:

root@host:~# host www.torproject.org www.torproject.org has address 38.229.72.14 www.torproject.org has address 38.229.72.14 Host www.torproject.org not found: 4(NOTIMP)

I have to send HUP signal to the running process to return to normal behavior:

root@host:~# host www.torproject.org www.torproject.org has address 10.230.198.145 www.torproject.org has address 10.230.198.145 Host www.torproject.org not found: 4(NOTIMP)

But after several hours or minutes tor begin returning real addresses again, after sending SIGHUP it's OK or several hours/minutes.

Currently i'm running tor 0.2.4.23 (git-598c61362f1b3d3e).

I created crontab entry, it sends SIGHUP every hour, but it's not enough.

See attached config file.

Best regards

Trac:
Username: operator_from_earth

changed milestone to %Tor: 0.2.6.x-final

added AutomapHostsOnResolve address component::core tor/tor ip milestone::Tor: 0.2.6.x-final priority::medium proxy reporter::operator_from_earth resolution::duplicate status::closed transparent type::defect version::tor unspecified virtual labels

Trac:
Username: operator_from_earth

tor.conf

Trac:
Username: operator_from_earth

This should be solved in 0.2.6.3-alpha; it appears to be a duplicate of #12509 (moved)

Trac:
Resolution: N/A to duplicate
Milestone: Tor: 0.2.4.x-final to Tor: 0.2.6.x-final
Status: new to closed

closed

moved to tpo/core/tor#12912 (closed)