Hi, my router is connected to a ADSL WAN Service that is interrupted by the ISP every 24hrs. To have it at a certan time I configured force reconnect at 6am. It worked good for several months.
Since two days DDNS is not reconnecting and URL is not reachable. Is it a router or a DDNS provider problem?
as the latest maintainer for Inadyn I guess I should comment on this issue.
Recently I picked up the 1.96.2 sources and started merging patches that we maintain at Westermo. When I was almost done I found Christoph Brill's SourceForge project and his 1.96.3 release. After having merged most of the relevant fixes from his tree I went ahead and worked on it some more. Eventually I ended up with the 1.97.x series and announced the project at Freshmeat: http://freshmeat.net/projects/inadyn
After having looked the the code I'm not sure the 1.97.x series has the bug reported here. On one of our routers, that had been running a while, I found the following log, which seems to indicate that the latest release does indeed recover:
The recurring RC_IP_CONNECT_FAILED errors above are OK. That's when the round-robin in the DNS resolves the (currently) stale IP number. But on the next attempt, as you can see, it recovers just fine.
I hope this helps.
answered Oct 26 '10 at 07:03 PM
For the last several days, one of the checkip.dyndns.servers has not been providing the checkip service.
A host name lookup of checkip.dyndns.org returns these addresses:
220.127.116.11 has been not responding for a while. Connection attempts currently hang, with an eventual timeout.
There is a bug in inadyn 1.96.2 such that when it gets an error trying to contact an IP server, it will continue to try that same server on every successive try until inadyn is restarted.
You will see these errors:
RC_IP_CONNECT_FAILED' (0x13) when talking to IP server
If you restart inadyn, it will probably try one of the other servers and succeed. But, if you run it as a service in the background it will eventually try the bad server and not recover.
Or you could change your ip_server_name to point to one of the other addresses: 18.104.22.168 or 22.214.171.124.
Or the server will be brought back up, and this bug will hide again.
I have created a patch for inadyn which has a fix for the problem, and have tested it on a Linux system. Until I post it to one of the download sites I could send the source to anyone who is interested.
It seems to work for me now on DD-WRT v24 preSP2[Beta]- Build 13064, but i have to watch it for the next days.
In DDNS configuration tab enter:
Hope it will keep on working !
I am still getting errors. Anyone else?
answered Nov 03 '10 at 11:06 PM
Hallo for all!!! The problem is in DynDNS service checkip.dyndns.org . After replace this link that one checkip.ns.zerigo.com (for example, or other IP-chek service) ALL WORKS GOOD!!! my config for DD-WRT is: