[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: (FWD) Re: IP resolving

If you're NATed with a dynamic IP, get a subdomain redirect (dyndys.org?) and just edit the subdomain redirect when your IP changed. Then put the subdomain address in your tor config. Some dynamic dns services even have programs that run on your computer that will automatically update the DNS listing every x hours.

On 4/21/06, Roger Dingledine <arma@xxxxxxx> wrote:
[Forwarding since Dennis isn't subscribed to the list as this
address -RD]

----- Forwarded message from owner-or-talk@xxxxxxxxxxxxx -----

From: Dennis Roberts <denrober@xxxxxxxxxxxxxxx>
Subject: Re: IP resolving
Date: Fri, 21 Apr 2006 17:55:03 -0700
To: or-talk@xxxxxxxxxxxxx

Looks like you might be going through a NAT.

Add the following to your tor server config file:

Address [your external ip address]

Normally tor tries to figure this out on its own, in your case it

On Apr 21, 2006, at 3:43 PM, Brian C wrote:

> I just started getting these warnings in my tor server logs.
> Running and wondering how to resolve. (I did a little
> scrubbing of domain names and IP addresses below).
> Apr 21 14:12:23.936 [notice] resolve_my_address(): Could not resolve
> guessed local hostname 'subdomain.domain.tld'. Trying something else.
> Apr 21 14:12:23.937 [notice] resolve_my_address(): Learned IP address
> '' for local interface. Using that.
> Apr 21 14:12:23.937 [warn] resolve_my_address(): Address '<guessed
> from
> interfaces>' resolves to private IP '192.168.#.##'. Tor servers
> that use
> the default DirServers must have public IP addresses.
> Apr 21 14:12:23.937 [warn] check_descriptor_ipaddress_changed():
> options->Address didn't resolve into an IP.
> Brian

----- End forwarded message -----