DynDNS to no-ip not updating IP-address

[Guest]

[jonaskellens]

When I do a "force update" to update my IP-address to no-ip, the IP-address is never updated.

The system logfile states the following :

Code:

sudo: nobody TTY=unknown ; PWD=/home/httpd/cgi-bin ; USER=root ; COMMAND=/usr/local/bin/setddns.pl -f 2

Is there a bug ?

Using Endian 2.3.

[cclayden]

I have the exact same issue.  I am using zoneedit and dyndns, both are not updating and have the same log message...

[cclayden]

I forgot to mention that i am running 2.4.1.  Tx.

[cclayden]

I found a bug on this issue, looks like the whole script needs to be rewritten.

I was able to work around zoneedit.  Zoneedit will not update without a hostname.  So I added a new hostname under my domain and all is good for this sub domain.

As for gotdns, still no joy.  I hope someone with an account can update the bug to reflect gotdns.

Hope this helps.

Cheers.

[tadaog]

YES! There's a bug in /usr/local/bin/setddns.pl around line 384 (I don't remember exactly because of several other bugs in 2.4.1 that makes it unusable for me), like:

if ($settings{'SERVICE'} = 'zoneedit'

in Perl, = is the assignment operator, the comparator is "eq" like you can see in the other similar before this buggy one!
So it must be (as the other ones in the same code):

if ($settings{'SERVICE'} eq 'zoneedit'


So it seems that this version programmers really didn't pay much attention to testing before releasing!!!

Another example:

In the OpenVPN configuration field to specify the network in the new way, the width doesn't allow sufficient characters to type, for example, 192.168.192.0/24 !!!

There's others glitches, like the waiting screens not dismissing when applying changes to proxy, or even not showing up when doing backups.



quote author=cclayden link=topic=1109.msg5992#msg5992 date=1289776323]
I found a bug on this issue, looks like the whole script needs to be rewritten.

I was able to work around zoneedit.  Zoneedit will not update without a hostname.  So I added a new hostname under my domain and all is good for this sub domain.

As for gotdns, still no joy.  I hope someone with an account can update the bug to reflect gotdns.

Hope this helps.

Cheers.

[/quote]

[war6763]

First post!

Thanks for the info! This also fixes dyndns.org!! Use nano to edit the file and you're set!

Cheers!