Stale DNS entries not refreshed during startup
Summary
On a relay node with
Address some-dynamic-address.com
When the server starts up, tor will resolve the dns entry before the dynamic dns client refreshes the entry in the dns server. Tor will then fail to fully start up, continually testing the stale IP address, and failing to verify connectivity.
What is the expected behavior?
It would be ideal if tor would attempt to re-resolve dns entries (possibl respect DNS TTL?) after a number of failed startups.
Testimonial
This issue has effected me. My house suffered a power outage. On re-connection, my server rebooted, with a new, DHCP'd address. Tor resolved my ip address before my dynamic DNS client updated it, and was stuck looping with
Sep 05 19:52:37 router Tor[395]: Your server has not managed to confirm reachability for its ORPort(s) at 71.112.171.245:867. Relays do not publish descriptors until their ORPort and DirORPort(s) at 71.112.171.245:867. Relays do not publish descriptors until their ORPort and DirPort are reachable. Please check your firewalls, ports, address, /etc/hosts file, etc.