Dynamic DNS issues with ddclient

[iBROX]

Hi,

Got an interesting issue with os-ddclient and I've done a fair bit of testing relating to the issue, I'll try and explain the scenario best I can.

Primary Link : Always on 24/7 - assigned a Public IP - lets say it is 116.255.4.225
Secondary Link : Only active when primary link goes down - assigned a public IP - lets say it is 1.144.230.31

os-ddclient updates my domain with no problem when the primary link is active.  Now when I test failover and all traffic is routed out via the Secondary link, give it about 5-10 minutes and os-ddclient then updates my domain to be given the Secondary link IP, no issues here. 

I check my control panel with my domain provider and you can see it has been updated when the primary link fails with the secondary link IP.

The problem I see is when the primary link comes back and os-ddclient attempts to update the DNS record it fails and says that the IP was already set to 116.255.4.225. log below :

<29>1 2023-02-13T14:13:25+11:00 gateway. client[28050] 34812 - [meta sequenceId="1"] SUCCESS:  DNSNAME: skipped: IP address was already set to 116.255.4.225.

I then check the DNS provider control panel and its still got the secondary link IP in there, I have to actually go in and manually add back in my primary link IP to get things working again.


I then deployed a Debian VM and installed ddclient on that with the exact same config as Opnsense and on this VM it works perfectly as expected :

Primary Link fails and it updates the DNS record with the Secondary link IP, then I bring the Primary link back and it says to wait for 5 minutes which is fine, but then on the next attempt 5 minutes later it correctly updates the DNS record with the Primary link IP, there is no manual intervention required basically.

Any ideas why Opnsense is failing to act properly in the above scenario ?

[iBROX]

Bump, anyone?