Hello, yes you're right. It looks like I accidentally routed all traffic through tor due to a faulty firewall rule. It was a bit confusing, because of the quickly updates with the right IP. It took me a while to understand the background.
Thanks a lot for your help Regards, On 20.12.2016 19:35, anondroid wrote: > I'm familiar with DynDNS and the client. The client tries to detect your > external IP address in order to keep your dynamic DNS record pointed at > your current IP. It looks to me like you're running it on a machine > that's routing through Tor. So it picks up the IP address of the Exit > you're routed through, and incorrectly tries to update your dynamic DNS > with this Exit IP instead of your actual IP. > > If this theory is correct, there's not really a "bug" here. It's working > as expected. You can't run the DynDNS client if you're routing traffic > through Tor. > > > > > > > > _______________________________________________ > tor-relays mailing list > tor-relays@lists.torproject.org > https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays > _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
