DNS-O-Matic add-on

super-poussin wrote:
I have done a new version which should solve problem for people having system set-up to another language than English :)

Hello Super-Poussin,
I noticed that since 1.6 version you have changed the format of DOW
from : DOW=$(date +%A) ; for date name (Monday, Tuesday...)
to : DOW=$(date +%w) ; I guess it's for day number of the week ; 1 for Sunday, 2 for Monday...
Is that correct ?

Thanks in advance.

yes because %A will display the day (short) like Monday or Lundi or Montag .... depending the language you set up in Frontview so I dont want to make a test for each language , using %w you will always have the same number

super-poussin wrote:
yes because %A will display the day (short) like Monday or Lundi or Montag .... depending the language you set up in Frontview so I dont want to make a test for each language , using %w you will always have the same number

That's OK, I understand we now have number from 1 to 7, but does 1 is corresponding to Sunday or Monday ?

0 to 6

1 is monday

1-7 were only possible if it date was written by a french guy :)

super-poussin wrote:
1-7 were only possible if it date was written by a french guy :)

Good perspicacity :) and Thanks for your reply.

Hi, i've recently bought a ReadyNas Duo and started to install some add-ons
But i ran into problems getting DNS-o-matic to work. It keeps waiting for the first update.
This is what i've done.

Registered account at DNS-o-matic and setup DynDNS to test
Install the dns-o-matic via the Local Updater
Disabled the service
Change the user/password to the account i've registered with DNS-o-matic using notepad (or am i supposed to edit it another way)
Enable the service
Wait for 5mins, but nothing happened.

So i went to search around and found this thread. Is Shell access needed? I've installed PHP and shell access login on this DUO as well as transmission, does it matter? Can anyone help me on this?
Thank you in advance ^^

Super-Poussin great work as usual! Thanks. I am a NV user running TRANSMISSION and did have to make modifications, mostly pointed out already in various posts, and optionally made available in the script. It did take me a while to figure out what the problem was, which seems to be the location of curl. So for my fellow ReadyNAS NV users, these are the modifications that I had to make to get DNS-O-Matic to work.

1. Stop the service

2. Comment out the first IP line and use the second..

#IP=$(`which curl` -s http://myip.dnsomatic.com/)
IP=$(/usr/local/bin/curl -s http://myip.dnsomatic.com/)

3. Modify the RETURN line to also use the same routing..

 RETURN=$(/usr/local/bin/curl -k -s https://${USER}:${PASS}@updates.dnsomatic.com/nic/update?hostname=${HOSTNAME}&myip=$IP&wi

4. Restart

5. Check the last line of your logfile to confirm its working...

# tail -f /var/log/DNS-O-Matic.log 
Fri Jul 10 21:40:01 SGT 2009 : PB 21:40
Fri Jul 10 21:40:01 SGT 2009 : found: 218.180.45.0  cached IP:
Fri Jul 10 21:40:01 SGT 2009 : Return message of DNS-O-Matic :  good 218.180.45.0

for me

#IP=$(`which curl` -s http://myip.dnsomatic.com/) IP=$(/usr/local/bin/curl -s http://myip.dnsomatic.com/)

are the same which curl will answer : /usr/local/bin/curl


the which is useful for me cause with it I'm not forced to write a specific code for each architecture of NAS (x86 vs sparc)

super-poussin,

Yes, the 'which curl' also got the correct path if executed by me, but perhaps when executed within the script it results in a different path? The script does not work for me unless I put the path directly.

I need some assistance. I've fully read this thread twice and it seems that RWRight had the same issue as I have. Unfortunately, my permissions on the script are 777 so his fix won't work for me. I'm running v1.9 and can manually run the script with success. When I try to let it run on its own I always get the following:

XRAID:~# tail -f /var/log/DNS-O-Matic.log
Sun Jul 12 12:25:01 EDT 2009 : PB 12:25
Sun Jul 12 12:30:01 EDT 2009 : Running 0 12:30
Sun Jul 12 12:30:01 EDT 2009 : NO Internet IP : exiting
Sun Jul 12 12:30:01 EDT 2009 : found: cached IP:

When I run manually here is what I get:

XRAID:~# sh /c/addons-scripts/DnsOMatic/dnsomatic
XRAID:~# tail -f /var/log/DNS-O-Matic.log
Sun Jul 12 12:25:01 EDT 2009 : PB 12:25
Sun Jul 12 12:30:01 EDT 2009 : Running 0 12:30
Sun Jul 12 12:30:01 EDT 2009 : NO Internet IP : exiting
Sun Jul 12 12:30:01 EDT 2009 : found: cached IP:
Sun Jul 12 12:30:01 EDT 2009 : PB 12:30
Sun Jul 12 12:30:55 EDT 2009 : Running 0 12:30 96.228.246.16
Sun Jul 12 12:30:55 EDT 2009 : found: 96.228.246.16 cached IP:
Sun Jul 12 12:30:55 EDT 2009 : PB 12:30
Sun Jul 12 12:30:55 EDT 2009 : found: 96.228.246.16 cached IP:
Sun Jul 12 12:30:55 EDT 2009 : Return message of DNS-O-Matic : good 96.228.246.16

Note that the first four lines of the tail on the log are from the previous run. I've installed, disabled, edited the script or user/pass, then reenabled. Obviously it works when I do the sh command. It just doesn't want to work on its own. Any ideas?

Thanks for the help.