ddclient and Dynu DNS

Started by skydiver, July 15, 2023, 05:17:34 PM

Previous topic - Next topic
July 15, 2023, 05:17:34 PM Last Edit: July 18, 2023, 04:29:58 PM by skydiver
I am on my third DNS provider trying to find a provider that will work with both the new ddclient and also the new ACME client.
I am now working to get Dynu DNS after I was able to get NameCheap DYN DNS working but then found that NameCheap requires a history and more domains hosted than I need to enable my access to the API for use with ACME client.

I have an issue with DYNU setup in OPNSENSE as follows:
debug ddclient log:
2023-07-15T10:02:58-05:00 Notice ddclient[32333] 92754 - [meta sequenceId="7"] SUCCESS: wg.mydomain.com: skipped: IPv4 address was already set to 66.69.---.---.
2023-07-15T10:02:58-05:00 Notice ddclient[32333] 90378 - [meta sequenceId="6"] SUCCESS: synology.mydomain.com: skipped: IPv4 address was already set to 66.69.---.---.
2023-07-15T10:02:58-05:00 Notice ddclient[32333] 89244 - [meta sequenceId="5"] SUCCESS: plex.mydomain.com: skipped: IPv4 address was already set to 66.69.---.---.
2023-07-15T10:02:58-05:00 Notice ddclient[32333] 87399 - [meta sequenceId="4"] SUCCESS: ha.mydomain.com: skipped: IPv4 address was already set to 66.69.---.---.
2023-07-15T10:02:58-05:00 Notice ddclient[32333] 85050 - [meta sequenceId="3"] SUCCESS: fw.mydomain.com: skipped: IPv4 address was already set to 66.69.---.---.
2023-07-15T10:02:58-05:00 Notice ddclient[32333] 83060 - [meta sequenceId="2"] SUCCESS: dc.mydomain.com: skipped: IPv4 address was already set to 66.69.---.---.
2023-07-15T10:02:58-05:00 Notice ddclient[32333] 80525 - [meta sequenceId="1"] WARNING: 'if-skip' is deprecated and does nothing for IPv4


I dont know where OPENSENSE is finding that the IP it needs to update is already set.  All the DNS records that I have created at the other providers were changed to other IP addresses before I then deletes said accounts.
I also made sure the TTL for these records were set to 10 minutes then they were created while testing.
I have waited now 24 hours and it will is producing the same IP is already set message.

I have the ddclient logging set to debug but I am missing where the process is querying these A hosts for the current IP address.

Can anyone assist me to troubleshoot this?

Bumping this...
Can anyone point to where I can determine where the ddclient agent is querying the domain hosts to verify what needs to be updated and how I can either delete what is being cached or redirect the NS it is pointing to?

Is there anyone who can assist with answering my questions?  I have scoured log files when the ddclient starts to perform dyn dns processing by validating whether the IP needs to be updated. 

I still cannot determine our what command is being used to verify whether the target update DNS host to be updated because it looks to me this is where the breakdown occurs.  If I can determine this step it will let me investigate where is it getting a stale answer to the current dns entry IP and allow be to attempt to correct it

Quote from: skydiver on July 15, 2023, 05:17:34 PM
I am on my third DNS provider trying to find a provider that will work with both the new ddclient and also the new ACME client.

Cloudflare works wonderfully.
2x 23.7 VMs & CARP, 4x 2.1GHz, 8GB
Cisco L3 switch, ESXi, VDS, vmxnet3
DoT, Chrony, HAProxy + NAXSI, Suricata
VPN: IPSec, OpenVPN, Wireguard
MultiWAN: Fiber 500/500Mbit dual stack + 4G failover

--
Available for private support.
Did my answer help you? Feel free to click [applaud] to the left

What services are you subscribing to?

July 25, 2023, 09:39:21 PM #5 Last Edit: July 25, 2023, 09:42:02 PM by skydiver
So after a week seeing NO logging of ddclient,. I uninstalled the service plugin and the configured hosts then reinstalled and re-setup the plugin and host.