DynDNS blocked me
-
update_file.sh /etc/inc/dyndns.class
Thanks for helping debug this!
-
Yipppeeeee!
less dyndns.cache
<my wan="" ip="">:1134688795 (=updated timestamp!)
logs:
Dec 16 00:19:55 php: : phpDynDNS: (Success) IP Address Changed Successfully! (<my wan="" ip="">)
Dec 16 00:19:54 php: : phpDynDNS: updating cache file /cf/conf/dyndns.cache:
Dec 16 00:19:54 php: : DynDns: Current Service: dyndns
Dec 16 00:19:54 php: : DynDns: DynDns _checkStatus() starting.
Dec 16 00:19:53 php: : DynDns: DynDns _update() starting.
Dec 16 00:19:53 php: : DynDns: cacheIP != wan_ip. Updating.
Dec 16 00:19:53 php: : DynDns: Cached IP: <bogus cache="" ip="">Dec 16 00:19:53 php: : DynDns: Current WAN IP: <my wan="" ip="">Dec 16 00:19:53 php: : DynDns: _detectChange() starting.
Dec 16 00:19:53 php: : DynDns: updatedns() starting
Dec 16 00:19:53 php: : DynDns: Running updatedns()No thanks!, just keep up the good work you're doing. If I can be of any help, I'm gladly willing to!
Goodnight!
MickeyByte
:)</my></bogus></my></my> -
Checked my logs again this morning (getting paranoid here?), but all was running fine:
Dec 16 07:04:06 php: : phpDynDNS: No Change In My IP Address and/or 28 Days Has Not Past. Not Updating Dynamic DNS Entry.
Dec 16 07:04:06 php: : DynDns: Cached IP: <my cached="" wan="" ip="">Dec 16 07:04:06 php: : DynDns: Current WAN IP: <my wan="" ip="">Dec 16 07:04:06 php: : DynDns: _detectChange() starting.
Dec 16 07:04:06 php: : DynDns: updatedns() starting
Dec 16 07:04:06 php: : DynDns: Running updatedns()</my></my> -
So, the question is, is this fixed on 0.96.4?
Guess not, right?
Has a ticket been raised to solve this?
How can we check in the tickets page if a ticket has been fixed in a new version?
Sorry but I want to make sure that my dyndns account is not deleted again ;).
Cheers -
Yes, the output looks ok, so if you've done this after Scott had updated the files, you'll have the correct versions for dyndns to work smoothly
And yes, I'm still running fine with dyndns.
I also find it hard to search through the ticket system to find out if something is fixed in a new release
It would be nice if there would be a changes.txt file that is updated at each new release stating what has been fixed, updated, added, deleted
e.g.0.96.6:
- fixed dyndns cachedIP issue
- updated Intel NIC drivers to version 999.0.2.99stable
- …
0.96.4:
- ...
MickeyByte
-
It would be nice if there would be a changes.txt file that is updated at each new release stating what has been fixed, updated, added, deleted
e.g.0.96.6:
- fixed dyndns cachedIP issue
- updated Intel NIC drivers to version 999.0.2.99stable
- …
0.96.4:
- ...
You bet it would.
But since they're working so hard and are such a small team, I wonder if that is not asking too much of them ::).…so if you've done this after Scott had updated the files, you'll have the correct versions for dyndns to work smoothly...
Bear with me just this once more mickeybyte…
What commands do I have to enter in an SSH session in order that my box doesn't screw up dyndns?
I'm sorry that this may look too obvious for you but it ain't for me :-[.
Cheers -
Bear with me just this once more mickeybyte…
What commands do I have to enter in an SSH session in order that my box doesn't screw up dyndns?
I'm sorry that this may look too obvious for you but it ain't for me.
Cheersno problem, that's why we are here for…
in a SSH session enter following commands
update_file.sh /etc/crontab <enter>update_file.sh /etc/inc/dyndns.class <enter>after that reboot your firewall through the web interface, or by entering following command in the ssh session: shutdown -r now <enter>Greetz,
MickeyByte</enter></enter></enter> -
Ok, the same ones that I had already used a couple of days ago.
Seems like that way the box will update something through the web, right?
Just wanted to make sure that there were no new commands issued here.
Hope this gets fixed on newer releases permanently ;)
Cheers -
It is fixed on new releases.
-
Thanks to both of you, then :).
-
Yes, the output looks ok, so if you've done this after Scott had updated the files, you'll have the correct versions for dyndns to work smoothly
And yes, I'm still running fine with dyndns.
I also find it hard to search through the ticket system to find out if something is fixed in a new release
It would be nice if there would be a changes.txt file that is updated at each new release stating what has been fixed, updated, added, deleted
e.g.0.96.6:
- fixed dyndns cachedIP issue
- updated Intel NIC drivers to version 999.0.2.99stable
- …
0.96.4:
- ...
MickeyByte
The discriptions are so vague I find it impossible to spend so long looking through so many entries to see if something is fixed.
Would be nice for at least the major fixes to be mentioned to stop a few of the questions poping up.Someone that can understand the CVS could volenteer to make a changes post? :) Doesn't have to be the devs
-
The discriptions are so vague I find it impossible to spend so long looking through so many entries to see if something is fixed.
Would be nice for at least the major fixes to be mentioned to stop a few of the questions poping up.
Someone that can understand the CVS could volenteer to make a changes post? :) Doesn't have to be the devsThis will change once we release. Right now we do not have the resources to document every change seperately.
Sorry!
-
Kind of started to think about the cachedIP thing used in dyndns (yes, it's me again ;D)
Just making a change request, don't know if that's the right place…
What if you checked the current WAN IP against the current IP in the DynDNS service in stead of keeping a cachedIP at the firewall?
Started thinking about this when I manually changed my dyndns IP using the website of dyndns.org to check if it would update, but it didn't because the CachedIP in the firewall was still the same as current WAN IP.
Don't know if those situatiions happen frequently, but it could!Greetz,
MickeyByte -
Hi,
You probably won't believe it, but I just got mail from DynDNS telling me my hostname is about to expire in 5 days!
In the system logs it nicely says each hour: IP not changed and 28 days not passed, so not updating.
Had to clean my dyndns.cache file to make it update!Something wit the timestamp in the file? of the script?
M.
-
It expires in 30 days? So that would be 25 days? So it hasn't quite hit 28 days?
-
Well, better make it less than 25 days then in stead of 28, because getting an e-mail that it will expire is not really the type of e-mails I want to get.
One thing for sure, it'll take another month to know if it would really update at the 28th day, cause I've forced it right now :-)M.
-
I got blocked to. I'm running beta2 and followed the instructions but it says command not found. Do you have that script available for download?
Thanks,
Tom -
These problems have been solved for a long time. Are you sure that you are not running multiple clients?
-
hopefully these steps will work for the DHS client too. i having the same trouble.
*edit nope it doesn't
update_file.sh /etc/inc/dyndns.class
update_file.sh: Command not found.
4 18:28:22 php: /services_dyndns.php: Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Current Service: dhs Jan 4 18:28:22 php: /services_dyndns.php: DynDns: DynDns _checkStatus() starting. Jan 4 18:28:22 php: /services_dyndns.php: Curl errror occured: Couldn't resolve host '{$server}{$port}' Jan 4 18:28:22 php: /services_dyndns.php: DynDns: DynDns _update() starting. Jan 4 18:28:22 php: /services_dyndns.php: DynDns: cacheIP != wan_ip. Updating. Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Cached IP: 0.0.0.0 Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Current WAN IP: *.*.*.* Jan 4 18:28:22 php: /services_dyndns.php: DynDns: _detectChange() starting. Jan 4 18:28:22 php: /services_dyndns.php: DynDns: updatedns() starting Jan 4 18:28:22 php: /services_dyndns.php: DynDns: Running updatedns()