I've been using the free DynDNS for a few months but recently I noticed that the dns ip from my cablem modem was changing at the DynDNS servers but not on the cable modem.
My set up is to use the DynDNS client on my pc to update the DynDNS servers of the ip of my cable modem. For some odd reason the ip on the DynDNS servers appears as 82.47.x.x which is way out from the one I have on my my modem 92.232.x.x. The ip of the cable modem has been the same for the past few weeks.
So why does the DynDNS records show the incorrect ip? Is this an effort from them to make buy the Premium service?
By the way I can only update the ip via my account logged on to DynDNS websie as the client doesn't update it - no errors just. Client log file below.
DynDNS Updater v4.1.7 User agent: DynDNS-Client-Win32/4.1.7 Windows version: Microsoft Windows XP Professional Running as: Service
[App] Username=xxxxxx Fresh=0 Dynguide=0 NetworkInterfaceDescriptionBlacklist=TAP-Win32,VPN,WAN (PPP/SLIP) Interface
0 08-05-2011 21:45:46 Updater: Service started. 0 08-05-2011 21:45:48 DNS update issued: User: xxxxx, Hosts: xxxxx.dyndns.org, IP: 92.232.x.x 0 08-05-2011 21:45:48 xxxxx.dyndns.org: good - Host updated. 0 08-05-2011 22:22:14 Updater: Service stopped. 0 08-06-2011 19:05:06 Updater: Service started. 0 08-06-2011 19:25:59 Updater: Service stopped. 0 08-07-2011 02:26:05 Updater: Service started. 0 08-07-2011 02:39:25 Updater: Service stopped. 0 08-07-2011 14:07:03 Updater: Service started. 0 08-07-2011 14:50:20 Updater: Service stopped. 0 08-07-2011 15:13:31 Updater: Service started. 0 08-07-2011 15:51:02 Updater: Service stopped. 0 08-07-2011 17:16:19 Updater: Service started.Please advise.
It could be that your ISP has put you behind a proxy.
Visit http://rotblitz.byethost7.com/client.php to see if
If there is any discrepancy, then your ISP does funny things with your internet connection, and you're most likely out of luck with reaching your network from outside.
It also could be that there is another Update Client running out of another network against your hostname. Did you ever leave or sell a device where an Update Client for your DynDNS hostname was activated? In this case a password change at the website and in the Update Client would help.
This assumption is nonsense. No money in the world would give you any different effect.