This morning (9:30 UTC), my relay (nebo.xmmswap.com) printed
09:30:08.000 Your IP seems to have changed to <<Search Guide AS36029 range>> (METHOD=GETHOSTNAME HOSTNAME=nebo). Updating. 09:30:08.000 Our IP Address has changed from 217.182.198.76 to <<Search Guide AS36029 range>>; rebuilding descriptor (source: METHOD=GETHOSTNAME HOSTNAME=nebo). ...
Six minutes later it was back to normal:
09:36:08.000 Your IP address seems to have changed to 217.192.198.76 (METHOD=INTERFACE). Updating.
What was that? A DNS hijack?
I'm running 0.3.2.10 on NetBSD. My DNS upstream is GoDaddy. Secondary DNS is OVH.
Alexander Nasonov wrote:
This morning (9:30 UTC), my relay (nebo.xmmswap.com) printed
09:30:08.000 Your IP seems to have changed to <<Search Guide AS36029 range>> (METHOD=GETHOSTNAME HOSTNAME=nebo). Updating.
It looks like a bad exit because my local resolver is configured to use a different tor instance on the box. I should probably change it to use my own xmmswap.com resolver.
On 18 Mar 2018, at 22:35, Alexander Nasonov alnsn@yandex.ru wrote:
Alexander Nasonov wrote:
This morning (9:30 UTC), my relay (nebo.xmmswap.com) printed
09:30:08.000 Your IP seems to have changed to <<Search Guide AS36029 range>> (METHOD=GETHOSTNAME HOSTNAME=nebo). Updating.
It looks like a bad exit because my local resolver is configured to use a different tor instance on the box. I should probably change it to use my own xmmswap.com resolver.
Your relay uses its local resolver to discover its own IP address. It doesn't ask an exit.
T
teor wrote:
Your relay uses its local resolver to discover its own IP address. It doesn't ask an exit.
My local resolver was dnsmasq and it was configured to forward all requests to port 9053.
I updated /etc/hosts and added a special rule for my domain in dnsmasq.conf. This should fix the issue.
tor-relays@lists.torproject.org
-
Alexander Nasonov -
teor