DynDNS blocked me

rds_correia

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 ::).

@mickeybyte:

…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

mickeybyte

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

no 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>

rds_correia

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

sullrich

It is fixed on new releases.

rds_correia

Thanks to both of you, then :).

Jesse7

@mickeybyte:

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

sullrich

@Jesse7:

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

This will change once we release. Right now we do not have the resources to document every change seperately.

Sorry!

mickeybyte

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

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.

sullrich

It expires in 30 days? So that would be 25 days? So it hasn't quite hit 28 days?

mickeybyte

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.

tom4465

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

sullrich

These problems have been solved for a long time. Are you sure that you are not running multiple clients?

codegrinder

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()