|
I'm a long time user of the DynDNS service - but recently migrated my update-client from my aging linux host to a Mac mini. I downloaded and properly configured the update-client for mac. It does reflect the proper WAN address using the web detection address, and is set to update the account. The update-client shows the status is OK, followed by the WAN IP. But in the three or four months that I've had this client installed - it has never updated the account. Lucky for me my IP address is very sticky and has not changed in probably 8 or 10 months. But every month I receive an email from DynDNS stating that my account is about to expire due to lack of update within 30 days. So I'm a little confused about why the client is not working properly. The Mac in question is running 10.5.8, and the update-client was actually just updated to version 3.0. This intel core-duo mini is my media server and is up and running approx 16 hours per day. The mini auto sleeps around 3am and is back in service 6 to 10 hours later. The mini is Ethernet attached to my network. The mini has been rebooted several times during this four month period ... trying to force the update-client to contact the dyndns service. After the first failure - I disabled the internal firewall on the mini. Note that the mini and the aging linux host are on the same network - behind the same Cisco 2651xm router. I've been through the FAQ, and searched the forums without finding any solution. I'm guessing that the client keeps record of the current address and if it changes - it triggers an update to the service. But is there a mechanism in the client where it senses the age of the last update? If anyone has any advise or words-of-wisdom, I'd really appreciate the input. Thanks in advance to all. |
The question has been closed Sep 12 at 04:27 PM ago by Cry Havok for the following reason "Abandoned question".
|
The official Mac & Windows clients do not force an update every X days, they only send updates when an IP actually changes. This is something that likely won't be changed, as no idle account expiration is one of the benefits of having a paid service on an account. Something like DynDNS Pro would prevent account expiration, though really any paid service on the account will prevent expiration. Take care, -Dan Interesting - when did that change?
Jan 25 at 08:50 PM
Cry Havok ♦
The 4.x Windows updater has been that way since the first version as far as I know, and the Mac OS X updater has since at least version 2.3 - that's the earliest version of the source code I've seen since we took over development of the client for 2.4+.
Jan 26 at 01:57 PM
Dan McCombs ♦♦
|
|
Same with me. I'm running an OS X server and it seems my IP hasn't changed lately so the client sent no update. Last week I had an account expiration mail, checked the client, found it was working and thought I forced the update. Obviously didn't. Now I'm on the road with no access to my server. Any way to retrieve the last IP connected to that address? Sadly no. Best to switch to a different update client, or upgrade to Dynamic DNS Pro.
Sep 12 at 04:27 PM
Cry Havok ♦
It is sufficient if you login to your account on the website once monthly. Or make a bookmark with the update link, so you can manually update at any time. (Don't do it much often...)
Sep 12 at 07:30 PM
RotBlitz ♦
|
