OpenWrt Forum Archive

Topic: Error on DDNS update due to error on "wget http://checkip.dyndns.com"

The content of this topic has been archived on 30 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

"wget http://checkip.dyndns.com" shows sometimes errors which causes problems on OpenWRT update client.
It is used by the OpenWRT DDNS update client to determine the current IP address.

A query of "checkip.dyndns.com" via the command "wget" ends sometimes with the following error messages:
"Connection refused" or "Connection reset by peer"

It happens mostly when the following two IP addresses get queried, so I guess its a server side problem.
216.146.38.70 / 91.198.22.142

My colleague told me that he is having the same problem on another proprietary router firmware right now.
Did anyone make the same experience on OpenWRT or other alternative update clients?

I did run a couple queries with a test script, please find the output via the following link:
https://dl.dropboxusercontent.com/u/168 … Martin.txt

I am also having this problem on different locations (Nicaragau, Croatia, Austria...)

(Last edited by michaeluray on 29 Jun 2016, 11:14)

216.146.38.70 / 91.198.22.142

tried these IPs and they work fine for me, throwing me a simple text file with my ip address on it.

although cant really tell if the actual thing works since I use minidns.net using custom url (since openwrt doesnt have this on ddns selection) and it works for me since 2004 I used it when my first DSL connection reached my house.

Yea, sometimes it works with these IPs, sometimes not.
Sometimes it takes below 1s to receive an answer, sometimes it takes more than 20-30s, sometimes it aborts with the mentioned errors.

You can see that in the file which I provided via the link.

michaeluray wrote:

"wget http://checkip.dyndns.com"
I did run a couple queries with a test script, please find the output via the following link:
https://dl.dropboxusercontent.com/u/168 … Martin.txt

The issue seems to be that the OPENWRT client is not as robust as one would like it to be, since the DDNS package is openwrt specific going to the Dyn community is not going to fix the lack of robustness. Now you might argue that Dyn should "up their game" but that is orthogonal to the OPs reported issue.

Best Regards
       M.

moeller0 wrote:

The issue seems to be that the OPENWRT client is not as robust as one would like it to be, since the DDNS package is openwrt specific going to the Dyn community is not going to fix the lack of robustness.

That is exactly the point. I guess the official DynDNS update client uses the same mechanism to determine the IP, but I also guess it handles the error on a different way.

Regarding that "http://checkip.dyndns.com" is the OpenWRT DDNS default check IP URL I would say it also is related to OpenWRT somehow.

(Last edited by michaeluray on 29 Jun 2016, 13:14)

BTW, you can change the option ip_url in /etc/config/ddns (the default is checkip.dyndns.com)

Sorry, I was offline for some days.
Does your DDNS provider offer it's own url to detect you IP? Many of them do. If yes, you should use this one.
I also recognised that the use of checkip.dyndns.com inside my browser sometimes takes up to 3-5 seconds before an answer.
I don't know Austrian urls.
I'm using http://myip.spdns.de for IPv4 and http://checkip6.spdns.de for IPv6
Try these instead of dyndns.com

chris5560 wrote:

Does your DDNS provider offer it's own url to detect you IP? Many of them do. If yes, you should use this one.
I also recognised that the use of checkip.dyndns.com inside my browser sometimes takes up to 3-5 seconds before an answer.

My DDNS provider is actually DynDNS.
Yes, it is the same thing in the browser. Sometimes it takes a few seconds and sometimes it does not work anyway.
I have almost hundred DDNS clients in the field and so it is not so easy to change the checkip URL, especially when you cannot reach them due to the update problem.

(Last edited by michaeluray on 5 Jul 2016, 11:02)

Are I am the only one who has problems accessing "http://checkip.dyndns.org" via "wget checkip.dyndns.org -O-"?
Is there actually no one else who is effected by this problem?

The discussion might have continued from here.