Inadyn Client Blocked for Abuse

After stepping through the source code, it's clear that the inadyn does not verify the current DNS value before trying the first update.

So it will always update your IP on the first run, therefore the only way this program will work is if you leave it running in the background.

My powers are too weak to "op" mauirc, but he's correct. You need to keep inadyn running in the background to get continuously updated status.

Put something like this in your /etc/inadyn.cfg:

--syslog
--forced_update_period 604800
--wildcard
--username USER
--password PASS
--dyndns_system dyndns@dyndns.org
--alias YOUR.DYNDNS-ALIAS.TLD
--update_period_sec 600

It would probably also be useful, like mauirc says, to use a patched up inadyn that supports IP caching. For the benefit of everyone I've recently picked up inadyn and have merged most sane patches I've found lingering on the web. See project details and download the latest v1.97.1 at http://freshmeat.net/projects/inadyn

Good Luck!

I created a script to check the DNS value before performing the update. Use at your own risk:

#!/bin/bash

while getopts "f" opt; do
   case $opt in
      f) shift; FORCE=1;;
      *) exit -1 ;;
   esac
done

if ! [ "$1" -a "$2" -a "$3" ]; then
   echo "missing args: [login] [password] [hostname]"
   exit -1
fi

LOGIN=$1
PASSWORD=$2
HOST=$3

IP_ADDRESS=$(wget -q -O - http://checkip.dyndns.com/index.html |
      grep -Eo "[0-9]+\.[0-9]+\.[0-9]+\.[0-9]+")
DNS_ADDRESS=$(dig $HOST +short)

if ! [ "$IP_ADDRESS" ]; then
   echo "Bad IP Address: '$IP_ADDRESS'"
   exit -1
fi
if ! [ "$DNS_ADDRESS" ]; then
   echo "Bad DNS Address: '$DNS_ADDRESS'"
   exit -1
fi

if [ "$IP_ADDRESS" != "$DNS_ADDRESS" -o "$FORCE" ]; then
   echo "old IP: $DNS_ADDRESS"
   echo "new IP: $IP_ADDRESS"
   wget -q -O - \
      "http://${LOGIN}:${PASSWORD}@members.dyndns.org/nic/update?hostname=${HOST}"
fi

Update:

Do not call this script more than once every 10 min, as it relies on http://checkip.dyndns.com. Doing so would violate the client policies set in place.

Note that checking the current value through DNS lookups is against the DynDNS guidelines and may itself lead an account to being blocked for abuse.

Either leave it running as a daemon, use a patched version that supports caching the value or use ddclient, which is correctly behaved.