DDNS error since 19.1.4

[RickNY]

Hi all. I’ve had DDNS setup for quite some time to update Dnsomatic with Opnsense. I have several records in Dnsomatic that get updated, but ever since I updated from 19.1.3 to 19.1.4, I get an error from Cloudflare when Dnsomatic tries to update. This started with the first boot after the update where I immediately got an error. I have other services that update on the same Dnsomatic account, it just seems to be Cloudflare that complains. I get the error every 24 hours.
The error Cloudflare returns is “err A record with those settings already exists. (81058)”

Did something change with the DDNS client in 19.1.4?
Thanks
Rick

[mow4cash]

Wondering the same thing. I've been having issues with Cloudflare ddns and let's encrypt plugin. I'm not sure if it's something I'm doing but never had an issue before.

[franco]

Hmm, no changes since 19.1.2. Maybe they changed something at their side?


Cheers,
Franco

[RickNY]

I'm not sure what changed.. I disabled them in Dns-o-matic and just added them separately as Cloudflare services in OPNSense, and they update without issue.  From what I can tell, OpenDNS now requires a Cisco Umbrella account to post on their community pages, and it doesn't look like its seen much action lately.

[franco]

Hrm, ok, thanks for the heads-up. Let's keep observing this. Maybe the older service should be removed when this trend continues.


Cheers,
Franco

[RickNY]

Ended up being able to post a message to the DNS-O-Matic community about this.. I'll update this if anyone responds over there.. DNS-O-Matic is working within OPNSense -- its just the Cloudflare service when updated through DNS-O-Matic is failing.. I have a couple other services in the DNS-O-Matic account that are updating properly (Tunnelbroker, DSLReports, Zoneedit)