50H 1.39 firmware DDNS error?

kelmi

After upgrading from 1.38 to 1.39, DDNS stopped working. Dyny Basic. It keeps informing "user field is empty". It is not empty, profile was working perfectly with 1.38. Deleting and reimplementing the profile does not help.

K

PeterUK

What bit says "user field is empty"? screenshot

kelmi

Here we go.

K

username empty.png

PeterUK

Hmm I think I know the issue it seems Dyny Basic is missing Username box for DDNS Account ? Could you check in 1.38 if it was ever there?

but to workaround it use DDNS Type user custom

with the Username as Email and password add your Domain and in the following

URL Hostname: apiserver.dynu.com

URL Path: /nic/update?hostname=

and that will work

kelmi

Dynu seems to be the only DDNS account, where the Username- field is missing in 1.39. I don't recall, if Username-field was in 1.38, according to User Manual, seems to be so.

I'm not sure I understand what you mean with your idea? I'm not too familiar with this topic.

K

Zyxel_Melen

Hi @kelmi,

We are checking on this issue since we can replicate it. I will update you once I get further information.

PeterUK

as said you can do the Dynu Basic by user custom

Maverick87

There is a note on dynu website.

For the Zyxel USG50, latest firmware has removed "Username" field but that does not affect the IP update process. As long as you enter the correct "Domain name" and "Password", IP address for your domain name will be updated. The password should not have any symbols.

Probably this affect also the newest H series.

kelmi

https://community.zyxel.com/en/discussion/comment/86487#Comment_86487

Thank's for the info. Seems to be not the case. It really affects the IP update process within or with USG50H.

K

Zyxel_Melen

Hi @PeterUK @Maverick87 @kelmi

Thanks for your discussion. Let me to update the behavior for Dynu Basic DDNS service option.

This option doesn't need to enter username. You only need to enter the options in setup page(domain/password). This issue is because of the new feature.

The issue has been addressed and will be fixed in the next firmware release.