DynDNS Update Stopped Working with 2.26

[dj0qn]

Although I find 2.26 to be stable and a good improvement, I noticed that
the DynDNS update no longer works, and returns an error message. I
use the RemoteRig as a backup to my router's DynDNS with a different
address, so it is not mission critical, which is why I just now noticed the
problem.

In checking my log on DynDNS.com, it indicates my last update took place
the evening of Oct. 28th, which is when I installed 2.26.

73,
Mitch DJ0QN / K7DX

[sm2o]

It's no problem with the DynDns client. I have tested it my self, at my summer house RRC.

73 de mike

[dj0qn]

Which service are you using? Maybe the problem is
specific to dyndns.com? I tried reentering my information,
even though it was still there, with no change.

73,
Mitch DJ0QN / K7DX

[sm2o]

Is there more than one ?

I log in at http://www.dyndns.com/index3.html

i have an free account since 5-6 years I think with five adresses.

I changed the dyndns name at the summer house to a name that hadn't been updated for long time.

then after reset I checked at dyndns and after 10 seconds it was updated.

At the statuspage in the RRC dyndns status was changed to OK also

73 de mike

[dj0qn]

Yes, there are several, but dyndns.com is the largest one.

I have a paid account and have several host names. At my
remote QTH, I have different ones on four devices, since my
router sometimes does not update. This allows me to have
fallback host names in case I can't reach my station.

Anyway, I just deactivated it in the RRC-1258 and then
reactivated it again, now it finally updated. If anyone was
using dyndns before 2.26, they need to apparently do this
in order to make it work again.

Thanks & 73,
Mitch DJ0QN / K7DX

[Jan (Microbit)]

Although I find 2.26 to be stable and a good improvement, I noticed that
the DynDNS update no longer works, and returns an error message.

Which error message did you get? And where did you see it?

[dj0qn]

On the "Status" page, next to last is "DYNDNS status".
It said error until I deactivated and reactivated it, now
it says "OK" as it should (and I double checked the DynDNS
web site to make sure it updated).

73,
Mitch DJ0QN / K7DX

[Jan (Microbit)]

OK, I see. But I don't see how deactivating and reactivating it could have helped. I would have better understood if a power reset had helped. Also it seems strange if 2.26 is like that in general, demanding deactivation and reactivation for the DynDNS to work.

[LB9GE]

Had the same issue, but that was happening on an other device also. So it seems that it was only dyndns that had a problem those days because of some internal changes at dyndns.
I only powerd off and on the devices.

73 de LB9GE

[dj0qn]

Then I have a question: when DynDNS returns an error, does it continue to
try at the defined intervals, or does it give-up and stop at that point?

If it gives-up, then this would mean the problem was coincidentally with
DynDNS at the time I installed 2.26 and simply changing the password, etc.
has no effect. You must disable/re-enable or recycle the power. This would
also explain why only I had that problem.

Since 2.26 solved the stability issue with the web page accessibility, I had
no reason to recycle the power since installing it.

73,
Mitch DJ0QN / K7DX

[Jan (Microbit)]

Then I have a question: when DynDNS returns an error, does it continue to
try at the defined intervals, or does it give-up and stop at that point?
......
Since 2.26 solved the stability issue with the web page accessibility, I had
no reason to recycle the power since installing it.

It should continue retrying at the defined intervals. At least that is the intention

You mean that 2.26 has fixed the web page accessibility?! We haven't actually found what has caused some of you having such problems, though one minor thing was spotted during the search for it, and fixed in 2.26. If that "fixed" that problem then it really is great news! From which version did you upgrade?

[dj0qn]

I would check to see if it does indeed continue retrying, since that
is the only plausible explanation of why I had this problem, but no
one else did.

Yes, I was one of the guys that reported the web page accessibility
problem with 2.25 (and only with 2.25!). 2.26 has definitely
solved this, it hasn't died once since I installed 2.26.

73,
Mitch DJ0QN / K7DX

[Jan (Microbit)]

I would check to see if it does indeed continue retrying, since that
is the only plausible explanation of why I had this problem, but no
one else did.

We will give it a check, but I would say based on experience that there are often more reasons for a failure than one can imaging

Yes, I was one of the guys that reported the web page accessibility
problem with 2.25 (and only with 2.25!). 2.26 has definitely
solved this, it hasn't died once since I installed 2.26.

That is even more strange! Can't think of any reason 2.25 would have been different than all other versions, including the older ones. (But the previous mentioned more reasons for a failure than imaginable might apply here too, hehe!)

[ski]

I also have problems with DynDNS and ver. 2.26.
Indicates DynDNS errors in the status panel.
Uses NET1 as ISP (CDMA 450)

//Chris SM7SKI

[sm2o]

We haven't changed anything concerning Dyndns for long time. We got one mail from a guy who had logged the data traffic against dyndns and in that specific case we saw that some part of the message from Dyndns was missing, either not sent or cut away when sent over the Internet. So if some one who have probelm and can handle WireShark can send us some info we will check it up. We are not able to find any problem from here and with the DynDns accounts we have.

It can also be useful if we can "borrow" a problematic dyndns account so we can test with it.

73 de mike