Dyndns ddclient update problem

iacopop · 02-25-2007, 06:52 AM

Hello,
i have the dinamic ip service (dyndns) in my server.
I used ddclient to update my remote configuration at dyndns.org....
Until yesterday all work well, but today my ddclient can't update the ip address of my computer and so my server is no more accessible from the net.
I don't change the ddclient.conf file. Can yuou help me?
This is my conf file...i know that it is correct:

# Configuration file for ddclient generated by debconf
#
# /etc/ddclient.conf
daemon=120
syslog=yes
pid=/var/run/ddclient.pid
ssl=yes
protocol=dyndns2
use=web,web=checkip.dyndns.org/,web-skip='IP Address'
protocol=dyndns2
server=members.dyndns.org
login=*****
password='*****'
custom=yes, *****.net

I tried also with this command:

ddclient -daemon=0 -debug -verbose -noquiet 2 /etc/ddclient.conf

and the result is:

DEBUG: proxy =
DEBUG: url = checkip.dyndns.org/
DEBUG: server = checkip.dyndns.org
DEBUG: opt(fw =
Use of uninitialized value in concatenation (.) or string at /usr/sbin/ddclient line 1660.
DEBUG: glo fw =
CONNECT: checkip.dyndns.org
CONNECTED: using HTTP
SENDING: GET / HTTP/1.0
SENDING: Host: checkip.dyndns.org
SENDING: User-Agent: ddclient/3.7.1
SENDING: Connection: close
SENDING:
RECEIVE: HTTP/1.1 200 OK
RECEIVE: Content-Type: text/html
RECEIVE: Server: DynDNS-CheckIP/1.0
RECEIVE: Connection: close
RECEIVE: Cache-Control: no-cache
RECEIVE: Pragma: no-cache
RECEIVE: Content-Length: 103
RECEIVE:
RECEIVE: <html><head><title>Current IP Check</title></head><body>Current IP Address: 82.53.60.*</body></html>
DEBUG: get_ip: using web, checkip.dyndns.org/ reports 82.53.60.*
WARNING: skipping update of *.net from 82.53.59.* to 82.53.60.*
WARNING: last updated Fri Mar 23 14:40:09 2007.
WARNING: Wait at least 30 seconds between update attempts.

Why it tell me skipping update?

Thanks

Matir · 02-26-2007, 03:12 PM

It seems that, according to the error, you attempted to update less than 30 seconds previously.

Aleks` · 11-05-2008, 02:51 PM

I have the same problem, but I think I have a solution, add "-force" as an argument, and see if it updates the IP