A-record gone after update with empty value
laurensbl opened this issue · comments
ddclient couldn't fetch an IP and subsequently updated the host with "" (empty value), effectively deleting the A-record at the DDNS provider.
Should this be possible?
Log message:
WARNING: cannot connect to checkipv4.dedyn.io:443 socket: Connection reset by peer SSL connect attempt failed
WARNING: found neither IPv4 nor IPv6 address
SUCCESS: updating domain_and_tld_obfuscated.tld: good: IP address set to
regards,
ddclient@lb001 (version 3.10.0)
Subsequent log message seems to confirm it updated the host with an empty value (nothing):
WARNING: skipping update of domain_and_tld_obfuscated.tld from <nothing> to correct_ip_(obfuscated).
WARNING: last updated <never> but last attempt on Wed Apr 3 22:39:53 2024 failed.
WARNING: Wait at least 5 minutes between update attempts.
I tested to see if ddclient could create an A-record, but it didn't work, Had to make the A-record manually at the web interface of the DDNS provider. So this behavior is quite damaging, as the A-record is absent until manual intervention can be performed to recreate the A-record at the DDNS provider.
Prior to v3.11.0 ddclient used to proceed with bogus updates after IP acquisition failed. (See 1715bd3)
Ah, OK. Let's hope this change will be implemented into Debian Bookworm soon, otherwise the risk of crippling DNS will be there for the remainder of Deb12's lifetime.