Hey guys I have been looking around but haven't found one.  It would be nice to run this on my unraid box since its on 24/7 anyways.  

Hey guys I have been looking around but haven't found one.  It would be nice to run this on my unraid box since its on 24/7 anyways.  

If you are running unMENU you can download the .conf file attached to this post and put it in your /boot/unmenu folder or in your /boot/packages folder.

 

Then, in the unMENU package manager you'll find a dyndns package that will periodically update dyndns with your IP address.

 

I take no credit.  It was developed by a fellow unRAID user.   I'll get it on the google.code site for general deployment soon, but for now you can get it here as an attachment.

 

Joe L.

(If you don't use unMENU, but know anything about shell scripts, you'll be able to see how it is done and do something similar by looking at the PACKAGE_INSTALLATION lines in the .conf file.  They are basically the shell script commands run each time you install the package.)

dynamic-dns-unmenu-package.conf

Thanks a lot, this will be great!

Thanks a lot, this will be great!

The DynDNS update client script is now available for download as one of the unMENU packages in the package manager.

Found this package a while back, but had never tried it.  Thanks "gfjardim" and Joe.

 

Quick question...what is the best way to update the hyperlinks on unMENU to update with the dyndns address?

 

 

Ok, I installed this from unmenu, and entered my account information but when I login to the dyndns website and check the last time it was update it has not changed.  Is there something more I need to do?  Or does it only update if the IP has changed?

Ok, I installed this from unmenu, and entered my account information but when I login to the dyndns website and check the last time it was update it has not changed.  Is there something more I need to do?  Or does it only update if the IP has changed?

The script only updates the IP address if it changed. This avoid your account to be blocked by DynDNS.

Perfect!  Thank you. I keep finding more great things to do with this box.

Found this package a while back, but had never tried it.  Thanks "gfjardim" and Joe.

 

Quick question...what is the best way to update the hyperlinks on unMENU to update with the dyndns address?

 

 

unless dyndns changes their webste, nothing should need changing

 

I don't think I asked the right question and was not very clear.

 

 

I have a host named "xxxxx.com" through no-ip (also tested with dyndns)

Setup with port forwarding in my router, and my no-ip account has my dynamic IP address.

 

After going to "xxxxx.com:8080"

This brings up the unRAID main properly.

 

When I click on any of the links through unmenu it wants to direct me back to my LAN address.

 

Example:

If I click on "File Browser"

it wants to send me to...

"tower:8080/file_browser"

 

that will attempt to direct me to my LAN address.

192.168.1.112:8080/file_browser

 

If I manually insert

"xxxxx.com:8080/file_browser" it works.

 

See attached.

I don't think I asked the right question and was not very clear.

 

 

I have a host named "xxxxx.com" through no-ip (also tested with dyndns)

Setup with port forwarding in my router, and my no-ip account has my dynamic IP address.

 

After going to "xxxxx.com:8080"

This brings up the unRAID main properly.

 

When I click on any of the links through unmenu it wants to direct me back to my LAN address.

 

Example:

If I click on "File Browser"

it wants to send me to...

"tower:8080/file_browser"

 

that will attempt to direct me to my LAN address.

192.168.1.112:8080/file_browser

 

If I manually insert

"xxxxx.com:8080/file_browser" it works.

 

See attached.

unMENU is not secure in any way.  It would be a HUGE mistake in judgment to allow access to your server in the way you describe.  It was never meant for WAN use.

 

unMENU has no way to dynamically get the external address on the WAN.  Sorry.  You are just asking for hackers to invade your LAN they way you've set things up.  You'll just have to settle for "security through obscurity" and change the URLs yourself.

 

Joe L.

Thanks Joe.  As I was writing my reply, it made me realize that there are no security measures and I was making a mistake with the setup.  Thanks again.

What is the minimal interval to avoid blocking the client?

 

I used the initial 5 minutes and got blocked.

 

Now set it to 300 minutes and testing...

 

You should only update when the ip changes and every 20 + days or they will think your not using the service anymore.

 

It's like a bath - every 20 days whether I need it or not.

 

their policy is if your host is blocked, your update client is behaving abnormally, but the above rule has worked for me for the last ten plus years.

 

I use dd-wrt on my router to handle it.

 

 

What is the minimal interval to avoid blocking the client?

 

I used the initial 5 minutes and got blocked.

 

Now set it to 300 minutes and testing...

 

An equally good question is how long an interval can you use in the field on the unMENU form?

 

The answer is 59.

 

It is because it is used as */INTERVAL in the minutes field on the cron entry.

 

However... that is not the cause of your lockout.   The script should only update dyndns if your IP changes.

 

It does a ping of your dyndns address.  If that is not equal to the IP address returned from checkip.mydns.org it sends an update.

If it is equal it does nothing.

 

Looking at the source code for cron, it appears as if only two characters after the "/" will be used, so your interval is probably 30 minutes, not 300.

 

Joe L.

An equally good question is how long an interval can you use in the field on the unMENU form?

 

The answer is 59.

 

It is because it is used as */INTERVAL in the minutes field on the cron entry.

 

However... that is not the cause of your lockout.   The script should only update dyndns if your IP changes.

 

It does a ping of your dyndns address.  If that is not equal to the IP address returned from checkip.mydns.org it sends an update.

If it is equal it does nothing.

 

Looking at the source code for cron, it appears as if only two characters after the "/" will be used, so your interval is probably 30 minutes, not 300.

 

Joe L.

 

If not that then  what could be the reason for the lockout?

 

I had an issue with a client - he had a few pc's running the client to update the ip - you get locked if you make more than a request every 15 minutes if not mistaken

Try this instead.

 

Maybe I fixed something in the unMenu post and Joe didn't see it.

 

dynamic-dns-unmenu-package.conf

Try this instead.

 

Maybe I fixed something in the unMenu post and Joe didn't see it.

 

 

That is substantially identical to what I have.

I just got an email from DynDNS that I had to manually confirm my account was active because I had not updated it in a month (basically, since I started using unRAID).  In the past with my Synology NAS the DynDNS updater made sure to ping DynDNS often enough to keep my account active even if my ip address had not changed. 

 

If I am reading this thread correctly the DynDNS updater package for unMenu does not have this functionality, is that correct?  If so, what is everyone using to keep their DynDNS accounts active?  Are you guys just logging in once a month manually or maybe just using an update client that does not run on your unRAID server?

 

Any tips are appreciated.

I just got an email from DynDNS that I had to manually confirm my account was active because I had not updated it in a month (basically, since I started using unRAID).  In the past with my Synology NAS the DynDNS updater made sure to ping DynDNS often enough to keep my account active even if my ip address had not changed. 

The script that was submitted to me by "gfjardim" pings your dynamic address every "Check Interval" minutes.

 

Is that what you were referring to?

 

What do you see when you type

crontab -l

(Is the dyndns "script" scheduled )

 

Joe L.

Just ran that command and it shows it scheduled.  What I am referring to is generating an update every 20 days or so even if the address has not changed.  DynDNS doesnt just let you keep an address for years on end (or even months) if it hasn't changed, you must renew it monthly or they purge it to prevent orphaned accounts.  They will ban you if you renew it too often but they will drop you if you don't renew often enough, which is why an automated updater tool is so nice for handling DynDNS accounts.

 

http://www.dyndnscommunity.com/questions/3065/what-does-update-monthly-to-avoid-expiration-mean

 

 

Try this attached slightly modified .conf file.

 

It adds an additional line in the crontab to force an update on the 1st, 10th, and 20th of the month at 8:01 AM.

It also modifies the script slightly to recognize when it is being forced.

 

This file will NOT  be replaced by the "official" one if you install it and then check for unmenu updates.  It has an extra line at the top requesting it not be updated.  If you want the "official" version you'll need to delete the added line or delete the entire .conf file.

 

To force a re-install, you'll need to disable re-install on re-boot

then remove the existing script by typing:

rm /usr/bin/dynamic_dns

 

then refresh the "Package Manager" page in unMENU.  It should allow you to re-install the package using the new .conf file.

 

Joe L.

dynamic-dns-unmenu-package.conf

Thanks for your help.  Sorry for the delayed response, I have been away for a while.  I just updated unmenu on my server today, backed up the flash drive, and prepared to try this patch but when I compared the file attached here with my current file I see only four lines that are different, none of them appear to be related to the cron job.  Am I missing something or have you already pushed this update out to me and I didn't realize it?

 

The only four lines that are different between the file attached to your previous post and my current file are lines 19-22.

 

 

PACKAGE_VARIABLE Service Address:||vADDRESS=lime-technology.com||User's dynamic address.

PACKAGE_VARIABLE Service User:||vUSERNAME=unRAID||User's login.

PACKAGE_VARIABLE Service Password:||vPASSWORD=unRAID||User's password.

PACKAGE_VARIABLE Check interval(minutes)|vUPTIME=5||Check interval in minutes (5-59).

 

What about this line?

PACKAGE_INSTALLATION echo "1 8 1,10,20 * * /usr/bin/dynamic_dns autoupdate 1>/dev/null 2>&1" >>/tmp/crontab