|
I have an update client, DynDNS Updater for Mac OS X on a machine running 10.4.11 and a database via the FileMaker Pro 6 Web Companion. (I know, it's dated equipment, but it works.) The Updater is properly configured; the virtual host at [myname].dnsalias.com successfully points to the server running DynDNS Updater. For a while, that is. After a few hours, the virtual host just stops working. I go to http://DynDNS.com, and I see that the IP number associated with [myname].dnsalias.com is some other legitimate but random IP number. I have to manually reset [myname].dnsalias.com to my server's current IP. Can anyone explain why DynDNS would suddenly change the IP number? Am I missing something here? Do I have to pay to make it work indefinitely, or will I always have to manually reset it every few hours? |
|
Hello thecinemat, I assume that the updater had previously been updating the IP at DynDNS successfully. Is the errant IP at DynDNS an old IP you had previously? The only way to change the IP is by manually logging in to your account an making a change, or an update client logging into your account and making a change. Two things come to mind.
Change the password to the account at DynDNS and in your local update client. If the problem stops, then it is an update client somewhere doing the deed.
No, you don't have to pay to make it work, and you shouldn't have to reset it every few hours. regards... There is no other update client running on my network. I have a simple broadband modem from Comcast, connected to an Apple AirPort Express router, and that's it. I will try changing the password on my account.
Apr 05 at 10:40 PM
thecinemat
I changed the password. Sure enough, the domain has stayed up for more than two days now. How weird...thanks for the tip!
Apr 07 at 08:48 PM
thecinemat
|
