HOWTO Configure Freedns (afraid.org) service with Inadyn (Lucid)

**mpgarate** · December 16th, 2012

It appears to be working correctly, except that I'm unable to ping at the end. Here's my output:

Code:

mike@mike-1001PXD:~$ more /var/log/syslog |grep INADYN
Dec 15 23:22:11 mike-1001PXD INADYN[2243]: INADYN: Started 'INADYN version 1.96.2' - dynamic DNS updater.
Dec 15 23:22:11 mike-1001PXD INADYN[2243]: I:INADYN: IP address for alias 'mooo.ignorelist.com' needs update to 'xxx.xxx.xx.74'
Dec 15 23:22:12 mike-1001PXD INADYN[2243]: I:INADYN: Alias 'mooo.ignorelist.com' to IP 'xxx.xxx.xx.74' updated successful.
Dec 15 23:22:43 mike-1001PXD INADYN[2243]: I:INADYN: IP address for alias 'mooo.ignorelist.com' needs update to 'xxx.xxx.xx.78'
Dec 15 23:22:43 mike-1001PXD INADYN[2243]: I:INADYN: Alias 'mooo.ignorelist.com' to IP 'xxx.xxx.xx.78' updated successful.
Dec 15 23:23:01 mike-1001PXD INADYN[2254]: INADYN: Started 'INADYN version 1.96.2' - dynamic DNS updater.
Dec 15 23:23:01 mike-1001PXD INADYN[2254]: I:INADYN: IP address for alias 'mooo.ignorelist.com' needs update to 'xxx.xxx.xxx.79'
Dec 15 23:23:02 mike-1001PXD INADYN[2254]: I:INADYN: Alias 'mooo.ignorelist.com' to IP 'xxx.xxx.xx.79' updated successful.
Dec 15 23:23:14 mike-1001PXD INADYN[2243]: I:INADYN: IP address for alias 'mooo.ignorelist.com' needs update to 'xxx.xxx.xx.79'
Dec 15 23:23:14 mike-1001PXD INADYN[2243]: I:INADYN: Alias 'mooo.ignorelist.com' to IP 'xxx.xxx.xx.79' updated successful.
Dec 15 23:23:33 mike-1001PXD INADYN[2254]: I:INADYN: IP address for alias 'mooo.ignorelist.com' needs update to 'xxx.xxx.xx.72'
Dec 15 23:23:34 mike-1001PXD INADYN[2254]: I:INADYN: Alias 'mooo.ignorelist.com' to IP 'xxx.xxx.xx.72' updated successful.
Dec 15 23:23:46 mike-1001PXD INADYN[2243]: I:INADYN: IP address for alias 'mooo.ignorelist.com' needs update to 'xxx.xxx.xx.73'
Dec 15 23:23:46 mike-1001PXD INADYN[2243]: I:INADYN: Alias 'mooo.ignorelist.com' to IP 'xxx.xxx.xx.73' updated successful.
Dec 15 23:24:05 mike-1001PXD INADYN[2254]: I:INADYN: IP address for alias 'mooo.ignorelist.com' needs update to 'xxx.xxx.xx.74'
Dec 15 23:24:05 mike-1001PXD INADYN[2254]: I:INADYN: Alias 'mooo.ignorelist.com' to IP 'xxx.xxx.xx.74' updated successful.
Dec 15 23:24:17 mike-1001PXD INADYN[2243]: I:INADYN: IP address for alias 'mooo.ignorelist.com' needs update to 'xxx.xxx.xx.74'
Dec 15 23:24:17 mike-1001PXD INADYN[2243]: I:INADYN: Alias 'mooo.ignorelist.com' to IP 'xxx.xxx.xx.74' updated successful.

If I go to freedns.afraid.org/subdomain/ I can see the dns refresh when it's updated (every few seconds on my network). I am unable to ping my alias, however.

**dentaku65** · January 4th, 2013

Originally Posted by mpgarate

It appears to be working correctly, except that I'm unable to ping at the end. Here's my output:

If I go to freedns.afraid.org/subdomain/ I can see the dns refresh when it's updated (every few seconds on my network). I am unable to ping my alias, however.

Are u able to ping your current public IP address? If not maybe should be firewall setting of your box.

**tehjolly81** · March 25th, 2013

Originally Posted by pedm

To run inadyn every 5 minutes:

Code:

export EDITOR=nano && sudo crontab -e

Add bellow @reboot /usr/sbin/inadyn :

Code:

# m h  dom mon dow   command
@reboot /usr/sbin/inadyn
*/5 * * * * /usr/sbin/inadyn

Thanks to all who have contributed to this thread for helping me get up and running with inadyn and freedns.afraid.org. A couple of things I noticed as I read through this thread that tripped me up:

-Scheduling inadyn to start at reboot using cron is a good idea, however scheduling it to run every 5 minutes as previously suggested might be a bad idea. The reason for this is that every 5 minutes, cron starts a new instance of inadyn while the old instance is still running.. so after an hour, you'd have 12 instances, after a day, 288 instances, etc.

-I couldn't get forced update checking to work - inadyn was updating the IP when cron started it right after a reboot, but it wasn't updating every 5 minutes as it was supposed to after that, even though the daemon was still running. I was starting to think I was going to have to kill the daemon after every update and then have cron run it every 5 minutes as previously discussed... until I realized that the --forced_update_period argument is in SECONDS, not MS. Updating the inadyn.conf file to show:

--forced_update_period 300

fixed the problem for me and allowed inadyn to update my IP every 5 minutes as intended. It is a bit confusing that update_period uses MS and forced_update_period uses SECONDS.

The OP's post shows a forced_update_period of 320000. This results in a forced update every 88 hours. Not sure if this was intended or not, but if you are wanting to force an update more frequently like I did, make sure you are calculating this value in SECONDS.