SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0003307: DDNS not Working on 2.4.1 - MantisBT
MantisBT - Endian Firewall
View Issue Details
0003307Endian FirewallOther Servicespublic2010-11-17 17:322010-12-14 10:15
mschwenk 
max-endian 
normalmajoralways
resolvedfixed 
2.4 
 
0003307: DDNS not Working on 2.4.1
After my update to 2.4.1 Dyndns is not working anymore.
I need this urgent to be able to access my Servers from everywhere since thay have a dynamic IP. Can´t use vpn as well.
I use dyndns.org/com
/var/log/messages after force an update

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

I didn´t change anything after update and it didn´t work. I recreated my ddns entrys on the endian but it didn´t help.
No tags attached.
Issue History
2010-11-17 17:32mschwenkNew Issue
2010-11-22 14:31kfasonNote Added: 0005173
2010-11-22 19:19ReneeNote Added: 0005176
2010-11-22 23:11baldyNote Added: 0005177
2010-11-22 23:34ReneeNote Added: 0005178
2010-11-23 13:34ra-endianAssigned To => max-endian
2010-11-23 13:34ra-endianStatusnew => assigned
2010-11-23 16:46mschwenkNote Added: 0005187
2010-11-23 16:49mschwenkNote Edited: 0005187
2010-11-24 17:35max-endianNote Added: 0005197
2010-11-24 17:35max-endianStatusassigned => resolved
2010-11-24 17:35max-endianResolutionopen => fixed
2010-12-10 11:32anubisg1Note Added: 0005351
2010-12-10 11:32anubisg1Statusresolved => feedback
2010-12-10 11:32anubisg1Resolutionfixed => reopened
2010-12-14 10:15max-endianNote Added: 0005371
2010-12-14 10:15max-endianStatusfeedback => resolved
2010-12-14 10:15max-endianResolutionreopened => fixed

Notes
(0005173)
kfason   
2010-11-22 14:31   
I concur this does not work in 2.4.1. I use dyndns-custom.
(0005176)
Renee   
2010-11-22 19:19   
I have the same problem no update! Need fix!
(0005177)
baldy   
2010-11-22 23:11   
I am using dyndns.org and configured hosts in dyndns.info and dyndns.biz. System has been upgraded from 2.3 to 2.4 and to 2.4.1 and dyndns is working properly.

Have your systems been upgraded or cleanly installed ?

regards,

Baldy
(0005178)
Renee   
2010-11-22 23:34   
My system is upgraded from 2.4.0 via efw-upgrade the dyndns update does not work after reboot with the new kernel.

For me it was now finally with the Endian every time something does not function after an Upgrade and I have not the time to fix it per Remote vie Internet. So I will move the Remote system to the Astaro this works by me already since 2 months successfully. They have at least not thus a bad update politics for her Community (Home) variation!
(0005187)
mschwenk   
2010-11-23 16:46   
(edited on: 2010-11-23 16:49)
I did an upgrade from 2.4 to 2.4.1
If needed i can grant access to my efw. Of course only limited since I´m using dsl and my IP changes every night.

(0005197)
max-endian   
2010-11-24 17:35   
Hi.
There is a bug in the file /usr/local/bin/setddns.pl.
line ca. 387

Please replace the following if statment:

if ($settings{'SERVICE'} = 'zoneedit')
  {$serverdir = '-s'; $serveradd = 'dynamic.zoneedit.com';}
else
  {$serverdir = ''; $serveradd = '';}

with this one:

if ($settings{'SERVICE'} eq 'zoneedit')
  {$serverdir = '-s'; $serveradd = 'dynamic.zoneedit.com';}
else
  {$serverdir = ''; $serveradd = '';}
(0005351)
anubisg1   
2010-12-10 11:32   
i wonder if an official upgrade is on the way for this bug. a feature is broken!
(0005371)
max-endian   
2010-12-14 10:15   
Hi
The fix will be part of the next update, but we have not decided when the next updates comes. Sorry, please use until the update bugfix.