IPSec Phase1 DynamicDNS still not working in v2.6

[Vicedriver]

In IPSec configuration phase 1 if behind NAT (WAN with a private IP), the My identifier must be set with the public IP or 0.0.0.0. If we choose the option Dynamic DNS in My identifier it always retrieves the private IP of the WAN and not the public IP. Therefor in the case the connection is unsuccessful.
If there's an option to use DynamicDNS it should retrieve the public IP using for example the information of the DynamicDNS service configured in pfSense since it correctly obtains thee public IP address.

This issue comes from previous versions and persists in pfSense 2.6 / pfSense Plus v22.01

Does anybody have some more information about this?

[Bambos]

@vicedriver i have the same issue on 2.6 dynamic dns client, is not updating no-ip record and the vpn clients cannot connect.

The workaround is i have configure this pfsense as vpn client, so it can connect to my static ip pfsense and gain routing to itts interface. After that, i press the button save & force update to renew.