I'm getting this exact same message. ddclient appears to have stopped working for me quite some time ago as I'm unable to locate any logging over the past few months. I grabbed the 3.6.6 figuring DynDNS had made some back end changes that the client I had installed (mandrake rpm versioned 3.6.5) was not aware of. Follows is the output using the above command suggested:
I think you're missing a use-statement in your ddclient.conf Oh, btw, the location of ddclient.conf has changed. To make it possible to run it as a different user as root, ddclient expects his configuration in /etc/ddclient/ddclient.conf
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I have tried to install ddclient on Ubuntu. It worked fine once and now this time, I get this message where it cant resolve the IP!!
$ddclient
WARNING: unable to determine IP address
What can cause this?? and how to fix it? (I am behind a router, here is the results of my ifconfig)
Thanks
root@ubuntu:/etc # ifconfig
eth0 Link encap:Ethernet HWaddr 00:11:2F:44:F1:47
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::211:2fff:fe44:f147/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:277317 errors:0 dropped:0 overruns:0 frame:0
TX packets:181744 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:376384552 (358.9 MiB) TX bytes:14872917 (14.1 MiB)
Interrupt:22 Memory:feaf8000-0
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:433817 errors:0 dropped:0 overruns:0 frame:0
TX packets:433817 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:31631917 (30.1 MiB) TX bytes:31631917 (30.1 MiB)
Please post the full result of ddclient -daemon=0 -debug -verbose -noquiet and your ddclient.conf for further debugging.
I'm getting this exact same message. ddclient appears to have stopped working for me quite some time ago as I'm unable to locate any logging over the past few months. I grabbed the 3.6.6 figuring DynDNS had made some back end changes that the client I had installed (mandrake rpm versioned 3.6.5) was not aware of. Follows is the output using the above command suggested:
=== opt ====
opt{cache} : <undefined>
opt{cmd} : <undefined>
opt{cmd-skip} : <undefined>
opt{daemon} : 0
opt{debug} : 1
opt{exec} : <undefined>
opt{facility} : <undefined>
opt{file} : <undefined>
opt{force} : <undefined>
opt{fw} : <undefined>
opt{fw-login} : <undefined>
opt{fw-password} : <undefined>
opt{fw-skip} : <undefined>
opt{geturl} : <undefined>
opt{help} : <undefined>
opt{host} : <undefined>
opt{if} : <undefined>
opt{if-skip} : <undefined>
opt{ip} : <undefined>
opt{login} : <undefined>
opt{mail} : <undefined>
opt{mail-failure} : <undefined>
opt{max-interval} : 1296000
opt{min-error-interval} : 300
opt{min-interval} : 30
opt{options} : <undefined>
opt{password} : <undefined>
opt{pid} : <undefined>
opt{priority} : <undefined>
opt{protocol} : <undefined>
opt{proxy} : <undefined>
opt{query} : <undefined>
opt{quiet} : 0
opt{retry} : <undefined>
opt{server} : <undefined>
opt{syslog} : <undefined>
opt{test} : <undefined>
opt{timeout} : <undefined>
opt{use} : <undefined>
opt{verbose} : 1
opt{web} : <undefined>
opt{web-skip} : <undefined>
=== globals ====
globals{daemon} : 60
globals{debug} : 1
globals{mail} : root
globals{mail-failure} : root
globals{pid} : /var/run/ddclient.pid
globals{quiet} : 0
globals{syslog} : 1
globals{verbose} : 1
=== config ====
config{fragfest.homelinux.net}{atime} : 0
config{fragfest.homelinux.net}{backupmx} : 0
config{fragfest.homelinux.net}{cacheable} : ARRAY(0x82b5194)
config{fragfest.homelinux.net}{custom} : 0
config{fragfest.homelinux.net}{host} : [EDITED]
config{fragfest.homelinux.net}{ip} : <undefined>
config{fragfest.homelinux.net}{login} : [EDITED]
config{fragfest.homelinux.net}{max-interval} : 1296000
config{fragfest.homelinux.net}{min-error-interval} : 300
config{fragfest.homelinux.net}{min-interval} : 30
config{fragfest.homelinux.net}{mtime} : 0
config{fragfest.homelinux.net}{mx} :
config{fragfest.homelinux.net}{password} : [EDITED]
config{fragfest.homelinux.net}{protocol} : dyndns2
config{fragfest.homelinux.net}{server} : members.dyndns.org
config{fragfest.homelinux.net}{static} : 0
config{fragfest.homelinux.net}{status} :
config{fragfest.homelinux.net}{warned-min-error-interval} : 0
config{fragfest.homelinux.net}{warned-min-interval} : 0
config{fragfest.homelinux.net}{wildcard} : 0
config{fragfest.homelinux.net}{wtime} : 30
=== cache ====
DEBUG: get_ip: using ip, ip reports <undefined>
WARNING: unable to determine IP address
Ahh, yes, further information to the above. The machien the client is running on is on a private subnet behind a NAT enabled router.
Disregard, the information in the post below titled "client not updating DNS" contained the suggested fix.
I think you're missing a use-statement in your ddclient.conf Oh, btw, the location of ddclient.conf has changed. To make it possible to run it as a different user as root, ddclient expects his configuration in /etc/ddclient/ddclient.conf