pfSense

To better work with pfSense I opened a ticket a while ago with the folks from desec.io. As the DynDNS service on pfSense only supplied one IP family (either IPv4 or v6) the problem with updating both to the same name was, that per their documentation:

https://desec.readthedocs.io/en/latest/dyndns/update-api.html

if the other family is not listed it gets deleted from the entry. So updating example.dedyn.io with two jobs on pfSense results in only one (the latest) being saved and the other address family getting removed from the entry. To remediate this, we introduced a new GET parameter to their API "preserve".
See the yellow Warning on this link:

https://desec.readthedocs.io/en/latest/dyndns/update-api.html#determine-ip-address-es

The parameter &preserve can now be set so that updating e.g. IPv6 won't remove a previously pushed IPv4 address from the interface, thus resulting in a fully dual-stack capable dedyn.io entry. :)

My forum post about this is a tad old but describes the same thing and the URIs I tested with "Custom v4" and "Custom v6" so the desec / desec (v6) provider can be changed accordingly.
https://forum.netgate.com/topic/175769/desec-io-dedyn-io-dyndns-now-supports-avoiding-overwriting-entries-with-dual-stack-ip4-6

On a side note (as in the forum thread): is there a possibility to somehow push both IP from an interface (eg WAN) at the same time or is that a limitation of DynDNS' inner workings?

Thanks!
\jens