DNS-O-Matic add-on

Thanks Super-poussin for your help.
- I don't see /tmp from Windows but I found it using PuTTY (SSH).
- The addon installation didn't reset/remove the oldip.DNS-O-Matic file.
Solution was to delete the file using PuTTY : rm oldip.DNS-O-Matic
Then after when I run "sh /c/addons-scripts/DnsOMatic/dnsomatic" the WAN IP update once only
If you reset the WAN IP from DynDNS.org then it will not be updated until your WAN IP change (not tested) or you delete the /tmp/oldip.DNS-O-Matic (this can be an issue).

Now, I am checking if addon update properly the WAN IP each time I delete the /tmp/oldip.DNS-O-Matic

it should update the IP , you shouldn't have to remove the file in /tmp

the remove I asked for is only to be sure we start with a good situation

Hello again,
The addon is working OK but I confirm that if you reset manualy the IP from DynDNS account and if your WAN IP do not change (same as IP in /tmp/oldip.DNS-O-Matic file) then DynDNS & DnsOMatic will not be updated.

I understand that /tmp/oldip.DNS-O-Matic file has been used to avoid DnsOMatic frequently update (one every 5 minutes) when WAN IP is not changing but DynDNS request an update at least once per month otherwise we have to do it manualy.

I had similar issue when using DynDns addon with DUO and the workaround solution was to restart DUO with Power Timer once per day or week.

Is there any way to setup DNS-O-Matic addon in order to force update (once per day or week) even if the WAN IP did not change ? (May be something in the script to delete /tmp/oldip.DNS-O-Matic when $TIMENOW is 0:00)

Thanks for your help and your support.

I will see if I can do something for this

super-poussin wrote:
I will see if I can do something for this

Many thanks again !

I've installed 1.50 and it still does not appear to be running.

It updates if I run the script manually but does not seem to run automatically. According to FrontView, the add-on is running but I have checked the logs and they are not being updated.

My understanding is that it should check every 5 minutes. Is this still the case ?

Can anyone suggest how I can confirm that the process is running and suggest anything else I can check.

Thanks in advance.

I found the problem.

The permissions were wrong on the script file. Not sure how they changed but I suspect that my editor reset the permissions when I updated the script.

Thanks again super-poussin for all your support.

Super Puossin,
You are doing a great job for all the ReadyNAS users.
I'm happy to give you help for such simple things.
Please continue to develop more addons !
Regards
Sergio

I'm happy that this is now working correctly so I've changed the script slightly so that it only writes to the log if the IP has changed.

Just curious but I was wondering about why you have to stop and start the service when editing the script. Does this mean that it is being cached when the service starts ?

Thanks again.

I'm using 1.2 for the Pro (latest version available) and it's not working. The log says no IP:

Sun Jun 7 14:40:01 CDT 2009 : Running Sunday 14:40
Sun Jun 7 14:40:01 CDT 2009 : NO Internet IP : exiting

When running from shell:

NAS:/var/log# sh /c/addons-scripts/DnsOMatic/dnsomatic
/c/addons-scripts/DnsOMatic/dnsomatic: line 16: /usr/local/bin/curl: No such file or directory

This NAS is fresh from an Factory Reset, so I haven't changed any permissions. Any ideas?