ddclient DDNS updates returning 702 ("too soon") errors

[AlexH]

For the past few months, I have been unable to update the www host address on the DYN record for my domain, using clients such as ddclient (and previously zoneclient).

This was working ok for years previously, but suddenly changed - I have been trying to locate the problem ever since. I have reviewed other posts, and made sure that I have implemented suggestions from them, but I just can't seem to get it to behave unfortunately.

The root @ record for the same domain does update ok, it's just the www one that won't.
Both records update fine using the portal gui, so it is a problem isolated to the webservice method.

I have set the TTL to 10 minutes, and configured ddclient to loop every 11 minutes - the timestamps in the logs show that this has taken effect.
I have turned off updates for the @ record, and just left the www record in play, and even started ddclient afresh after being shutdown for a for a few hours, and I still get the "702: Minimum 600 seconds between requests" error as soon as I restart the service (on the www record).
There aren't any other machines also trying to update this domain.

Can you see anything in the back-end logs that might shed some light?

Here are the details (timestamps are UTC+11h):

ddclient.conf:

# Configuration file for ddclient generated by debconf
#
# /etc/ddclient.conf

protocol=zoneedit1 \
use=web, web=zoneedit \
login=<my login> \
password='<my passcode>' \
www.cozeyecan.com

ddclient service status:

* ddclient.service - Update dynamic domain name service entries
Loaded: loaded (/lib/systemd/system/ddclient.service; enabled; preset: enabled)
Active: active (running) since Sun 2025-01-26 08:04:14 AEDT; 2h 45min ago
Docs: man:ddclient(8)
Process: 2229 ExecStart=/usr/bin/ddclient -daemon $daemon_interval -syslog -pid /run/ddclient.pid (code=exited, status=0/SUCCESS)
Main PID: 2230 (ddclient - slee)
Tasks: 1 (limit: 8736)
CPU: 4.801s
CGroup: /system.slice/ddclient.service
`-2230 "ddclient - sleeping for 660 seconds"

Jan 26 08:04:14 finch systemd[1]: Starting ddclient.service - Update dynamic domain name service entries...
Jan 26 08:04:14 finch systemd[1]: Started ddclient.service - Update dynamic domain name service entries.

Log entries:

Jan 26 08:04:14 finch systemd[1]: Starting ddclient.service - Update dynamic domain name service entries...
Jan 26 08:04:14 finch systemd[1]: Started ddclient.service - Update dynamic domain name service entries.
Jan 26 08:04:16 finch ddclient[2234]: FAILED: updating www.cozeyecan.com: 702: Minimum 600 seconds between requests
Jan 26 08:15:18 finch ddclient[2316]: FAILED: updating www.cozeyecan.com: 702: Minimum 600 seconds between requests
Jan 26 08:26:21 finch ddclient[2391]: FAILED: updating www.cozeyecan.com: 702: Minimum 600 seconds between requests
Jan 26 08:37:23 finch ddclient[2408]: FAILED: updating www.cozeyecan.com: 702: Minimum 600 seconds between requests
Jan 26 08:48:24 finch ddclient[2475]: WARNING: skipping update of www.cozeyecan.com from <nothing> to 14.2.176.37.
Jan 26 08:48:24 finch ddclient[2475]: WARNING: last updated <never> but last attempt on Sun Jan 26 08:46:41 2025 failed.
Jan 26 08:48:24 finch ddclient[2475]: WARNING: Wait at least 5 minutes between update attempts.

 

[AlexH]

Leave this with me for the moment please - I think I might have found it.

Despite what I said above about there not being any other machines updating these addresses, today I remembered that I have an old NAS that runs 24x7 - it has been in place for many years, and I had forgotten about it.

I checked it out, and sure enough it was running zoneclient from way back when.

So I disabled it and will wait and see what happens the next time my public ip address changes - in a few days by recent experience.

Fingers crossed!