DDNS force update not possible?

[test011]

It is my understanding that, if WAN IP does not change for long time - by keeping the Router/Modem on for 24/7 - there is no way to force update DDNS, right? Even by manually hitting the DDNS pages apply button?

1. ez-ipupdate keeps an local IP cache and compares it before doing any updating. No IP changes, no (manual) force update.

2. almost every DDNS service rejects force update as long as registered IP matches newly supplied one - because there is no need to update - Thus, that DDNS account's inactivity period continues. (and after 30 days the account is going to be deactivated)

Please anybody can confirm this?

 

[joeybobo]

I'm having the same issue here with no-ip. Is there any setting or script we can use to force DDNS to update less than every 30 days to keep the accounts active?

 

[owine]

I'm having the same issue here with no-ip. Is there any setting or script we can use to force DDNS to update less than every 30 days to keep the accounts active?

You could set a cron to run every so often to force ez-ipupdate to run.

 

[lbradio]

You could set a cron to run every so often to force ez-ipupdate to run.

I wrote a little howto using cron and dnsomatic.
However, no-ip seems to not count these forced updates, and would like you to click on en email every month. Any solution is welcome.

http://forums.smallnetbuilder.com/showpost.php?p=119315&postcount=6

 

[owine]

I wrote a little howto using cron and dnsomatic.
However, no-ip seems to not count these forced updates, and would like you to click on en email every month. Any solution is welcome.

http://forums.smallnetbuilder.com/showpost.php?p=119315&postcount=6

I don't think DNS-o-Matic sends the update unless there is something to update. What about hard coding the update to send to No-Ip? Or sending an update of 127.0.0.1 immediately followed by a correct update?

 

[lbradio]

I don't think DNS-o-Matic sends the update unless there is something to update. What about hard coding the update to send to No-Ip? Or sending an update of 127.0.0.1 immediately followed by a correct update?

It seems this script (user rj.2001, found on wl500g.info) solved my issue.
Create a file IPupdate.sh in /jffs/scripts/. After running, the webinterface of noip.com shows todays update timestamp.

I already had a script "dnsomatic.sh" which is called by a cronjob every week.
Added:

IPupdate.sh <YourLogin> <YourPassword> <YourHostname>

#!/bin/sh

# Logfile parameter
# LOG=1/0 (On/Off)
# LOG=pathname to the logfile
LOG=0
LOGFILE=/tmp/IPupdate.log

# provider url's
# DynDNS
#URL="http://$1:$2@members.dyndns.org/nic/update?hostname=$3"
# NoIP
URL="http://dynupdate.no-ip.com/dns?username=$1&password=$2&hostname=$3"
# dyn.ee
#URL="http://dynserv.ca/dyn/dynengine.cgi?name=$1&pass=$2&func=set&domain=$3"
# ipactive
#URL="http://logon.ipactive.de/cgi-bin/logon_off.pl?V=2.1&B=$1&P=$2&IP=$3&F=1"


echo ""
if [ $# != 3 ] ; then
  echo "IPUpdate script"
    echo "usage: $0 <LOGIN-NAME> <PASSWORD> <HOSTNAME/DOMAIN/IPADR>"
      exit
      fi

      if [ $LOG == 1 ] ; then echo "$(date) Starting DNS entry update for $3 ..." >> $LOGFILE; fi
      echo "Starting DNS entry update for $3 ..."

      # Update Host entry
      RESULT=`wget -O - $URL | cat`
      if [ "$RESULT" == "" ] ; then RESULT=Error; fi
      if [ $LOG == 1 ] ; then echo "$(date) DNS entry update result for $3: $RESULT" >> $LOGFILE; fi
      echo "DNS entry update result for $3: $RESULT"

 

[joeybobo]

Nevermind...

no-ip forces you to login with CAPCHA protection on free accounts every 30 days regardless if it's updated or not.

Probably should have mentioned it was a free account. Scripts were still helpful, thanks!!

 

[jamestx10]

It seems this script (user rj.2001, found on wl500g.info) solved my issue.

Do you have a free no-ip.com account and this is working for you so you do not have to click through the email every 30 days?

 

[lbradio]

Do you have a free no-ip.com account and this is working for you so you do not have to click through the email every 30 days?

Hello,

I do have a noip.com account.
I use multiple hostnames within this account. One of these accounts (used by myself) is updated through the script. The other accounts are updated using the default DDNS options in several routers.

All accounts have to be updated manually after receiving a mail from noip.com EXCEPT my own account.

My previous post was at may 26th, I've implemented the script a few days earlier.
Until now I didn't have to update this specific noip.com account manually.