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

0000539: DynDNS-Update works only manually - MantisBT Endian Bugtracker
Endian Issue Tracker

Please see now our new Bugtracker system: JIRA

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000539Endian FirewallOther Servicespublic2008-02-02 18:052010-09-23 14:16
Reporterbodo olschewski 
Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
PlatformOSOS Version
Product Version2.2-beta3 
Target VersionfutureFixed in Version 
Summary0000539: DynDNS-Update works only manually
DescriptionDynDNS-Update works only manually (same like in 2.2-beta 2)
please write here how to fix this, that I can test on this release!
TagsNo tags attached.
Attached Files

- Relationships
child of 0001937confirmedpeter-endian issues to fix with ddns 

-  Notes
bodo olschewski (reporter)
2008-02-03 19:38

It looks like, it only doesn't work on start / restart; after "normal" reconnect (after 24 hours disconnection) it seems to work.
ra-endian (administrator)
2008-04-24 13:36

can you please retry with beta 4 ?
x_pedro_x (reporter)
2008-04-27 19:19

I tried this with beta 4 and it seams to work fine :)
bodo olschewski (reporter)
2008-04-27 21:59


because of problems with voip I use a AVM VoIP 5188 Gateway as a router in front of endian firewall meanwhile.

For testing this old problem, I made an extra account by and after restarting the endian firewall 2.2b4, the account was updated correctly.
Because of line problems my internet connection has connected today a lot of times new, but the dyndns account which is entered in endian firewall still has the address from last endian restart; not the actual address.
So it looks like, that there is maybe another problem with dyndns service.

- Issue History
Date Modified Username Field Change
2008-02-02 18:05 bodo olschewski New Issue
2008-02-03 19:38 bodo olschewski Note Added: 0000883
2008-02-04 14:19 ra-endian Target Version => 2.2-rc1
2008-03-04 14:42 ra-endian Target Version 2.2-rc1 => 2.2-beta4
2008-04-22 13:20 ra-endian Target Version 2.2-beta4 => 2.2-rc1
2008-04-24 13:36 ra-endian Note Added: 0001047
2008-04-24 13:36 ra-endian Status new => feedback
2008-04-27 19:19 x_pedro_x Note Added: 0001084
2008-04-27 21:59 bodo olschewski Note Added: 0001085
2008-05-09 12:44 peter-endian Target Version 2.2-rc1 => 2.2
2008-09-10 15:41 chris-endian Target Version 2.2 => 2.3
2008-09-10 15:53 chris-endian Target Version 2.3 => future
2009-06-10 13:53 peter-endian Relationship added child of 0001937
2010-09-23 14:16 peter-endian Status feedback => closed

Copyright © 2005-2008 Endian, SRL. All rights reserved.

Copyright © 2000 - 2012 MantisBT Group
Powered by Mantis Bugtracker