DNS-O-Matic add-on

[super_poussin]

I have done a new version which should solve problem for people having system set-up to another language than English 🙂

[dl78]

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.

[super_poussin]

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

[dl78]

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 ?

[super_poussin]

0 to 6

1 is monday

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

[dl78]

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

Good perspicacity 🙂 and Thanks for your reply.

[xenozelda]

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

[yachtman]

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

[super_poussin]

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)

[yachtman]

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.

[HereToday]

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.

[yachtman]

Heretoday, I had the identical results in my log. Changed my path in settings.json (put the exact path) and it worked. I did not investigate the permissioning.

[HereToday]

yachtman,

Thanks for the response. One follow on question - where is the settings.json file? I haven't heard of this one before.

[yachtman]

HereToday,

My mistake. Settings.json is used for Transmission (have too many config files in my head). The config file for DNS-O-Matic (which I think you already know) is:

#/c/addons-scripts/DnsOMatic/dnsomatic

Here is mine (unedited sections removed):

titanium:/c/addons-scripts/DnsOMatic# cat dnsomatic 
#!/bin/bash
HOSTNAME="all.dnsomatic.com"
USER="..."
PASS="..."
.....
#IP=$(`which curl` -s http://myip.dnsomatic.com/)
IP=$(/usr/local/bin/curl -s http://myip.dnsomatic.com/)
#IP=$(curl -s http://myip.dk/ | egrep -m1 -o '[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}')
.....
RETURN=$(/usr/local/bin/curl -k -s https://${USER}:${PASS}@updates.dnsomatic.com/nic/update?hostname=${HOSTNAME}&myip=$IP&wildcard=NOCHG&mx=NOCHG&backmx=NOCHG)
.....

But make sure that the locations above are the actual locations for 'curl'. You can do a '#which curl' for it. I can't figure out why super-poussin's original code didn't work for me, but the mod made it goo.

[super_poussin]

ytachman

if you do this in command line :

IP=$(`which curl` -s http://myip.dnsomatic.com/)
echo $ IP

what is the result ?

[yachtman]

super-poussin,

The command results in my correct ip.

However, if I modify the script with the following additional lines, the log results reveal that the commands don't seem to get the path from within the script?

#/c/addons-scripts/DnsOMatic/dnsomatic

IP=$(`which curl` -s http://myip.dnsomatic.com/)                                                         
IP2=$(/usr/local/bin/curl -s http://myip.dnsomatic.com/)                                                 
WI=$('which curl')                                                                                       
                                                                                                         
echo $IP ": = IP address with which curl" >> $LOGFILE                                                    
echo $WI ": = which curl path" >> $LOGFILE                                                               
echo $IP2 ": = IP with full path" >> $LOGFILE                                                            
  

From the logfile:

: = IP address with which curl
: = which curl path
218.186.45.146 : = IP with full path

[super_poussin]

ok will publish a 2.0 with fixed path

[HereToday]

yacthman,

That did the trick. I also ran the code you had and saw the same thing...the path wasn't getting passed to the variable even though the location was correct from the #which curl command.

super-poussin,

Great add-on. One which I will definitely upgrade to 2.0 once released. I also plan to donate. Thank you for your hard work on this one.

[super_poussin]

2.0 is out 🙂

[cmcloughlin]

Hi

I'm new with the readyNAS so please forgive my ignorance.

I have downloaded and installed the DNS-O-Matic addon and toggled SSH. I also have installed PuTTy on my Vista PC. However, I have not been able to log into mt ReadyNAS Duo to edit the /addons-scripts/DnsOMatic/dnsomatic file to add my user name and password.

Could someone please post a step by step idiots guide to this process for me as a complete newbie to anything linux based.

If there already is one please give me a link as my searches have been unsucessful

Thanks in advance

[secret_rivals]

Hi,

I have the Dns-O-Matic addon installed and it isn't updating to the dns-o-matic severs. Where do I find the dns-o-matic logs on the ReadyNAS so I can find out where it is failing? Do any ports need to be opened on a firewall, I persume it sends updates out over port 80.

[super_poussin]

logs are in /var/log/

DNSoMatic use https to send info to DNSoMatic

let me check if opendns/dnsomatic change something in the way to access the service

[secret_rivals]

xenozelda wrote:

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

I have exactly this problem does anyone have a resolution to this?

[super_poussin]

try the 2.1 http://www.readynas.com/contributed/sup ... ic_2.1.bin

for x86 : http://www.readynas.com/contributed/sup ... ic_1.5.bin

all logs will be in : /c/addons-config/DnsOMatic/

[secret_rivals]

I appear to be having the same problem with DNS-O-Matic that I had with the OpenDNS addon. OpenDNS isn't getting the IP updates and no logs are being created. Could this be a permission problem on the addons-config share? The folders within are created e.g. OpenDNS or DnsDnsOMatic but these folders aren't being populated with log files. I haven't tweaked the permissions on the addons-config share since it was created so it should have the default permissions associated with it. I have also updated the DNS-O-Matic addon to V2.1.

I have been trying to get OpenDNS to update for months now with both addons but no updates happen and no log files are created so I can't troubleshoot the problem. Has anyone else had the no log files problem when using either of these addons. I now have two seperate posts addressing this problem one for OpenDNS, the other for DNS-O-Matic. ANy suggestions would be welcomed.

Thanks.