ddclient ??
 

Fedora 8 x86_64
Setting up ddclient.conf , when I finnished I got one successful send to
my Dns server, see below;

Jan 30 16:58:39 localhost ddclient[1987]: SUCCESS: updating ******.homedns.org: good: IP address set to 78.258.237.180

It should have updated in another 10 minutes but it hasn't since then.

Below is the ddclient.conf file, Why isn't it updating, The ddclientd is running in services.


daemon=600
syslog=yes
pid=/var/run/ddclient/ddclient.pid
use=web, web=checkip.dyndns.org/
login=********
password=*******
bob.homedns.org
protocol=dyndns2
server=members.dyndns.org
wildcard=YES
#use=if, if=eth0
#example.dyndns.org
#custom=yes, example.com

The version of ddclient I'm running checks the file /etc/ddclient/ddclient.cache first. If the value cached is different to the actual value of the IP address, then it connects and updates the record. Otherwise, it doesn't need to connect again.

I don't have a /etc/ddclient/ddclient.cache directory.
The only thing I have in /etc is the ddclient.conf file.
My version of ddclient is ddclient-3.7.2-1.fc8

I'd confirm that it's running by checking the pid with:
If it's running, I'd try shutting it down and running it with debugging enabled:
If the output doesn't identify the problem I'd check the /etc/ddclient/ddclient.conf file to make sure the settings are correct. For example, you're using use=web - are you sure it's providing the correct IP address? I use use=if, if=ppp0 for my ADSL setup at home.

You may also be able to use wireshark to sniff the packets and see what is going wrong.

My ddclient.cache is in;

/var/cache/ddclient/ddclient.cache

I see what you mean, ddclient will check for new IP every 10 minutes if it doesn't change from what /var/cache/ddclient/ddclient.cache has stored it
won't do a update .

Exactly, and you can force it to run by deleting /var/cache/ddclient/ddclient.cache and running ddclient again.

Some DDNS providers don't like repeated attempts to update and treat it as cracking if it continues. Although I've had a warning message from DynDNS, I've never had a disruption to the service.

Thanks for your help guys.
Now all I have to do is get NX working on my x86_64, I have used it quit successfully on my i386 boxes.