@Gertjan said in Dynamic DNS client "extracted from local system":

To know if the WAN IP really changed ? Easy. Store the latest succeeded updated WAN IPv4 address locally. This is the cache file. Compare the actual WAN IPv4 with the cache ;:

Just going to take this opportunity to point out that this causes a problem in the case where we restore to a replacement router in our lab before delivery. DDNS is updated to our office IP. Live router will not update because its cached IP didn’t change. (Workaround is to manually modify the file on disk to fool it, as I recall)

@madtrick
The IP variable is the same, but you have to set up a special IPv6 update client so that pfSense takes the IPv6 interface address.
https://dyndns.inwx.com/nic/update?myipv6=%IP%

@kilburnflyer
Solved:

subscriptions/[YOURSUBSCRIPTIONID/resourceGroups/north-europe-default/providers/Microsoft.Network/dnsZones/[YOURDOMAIN]

do not put api version in there.

in hostname only put value before i.e. RECORD

i.e.

RECORD.[YOURDOMAIN]

Relevant link in source code helped debug

@gertjan Thank you, I am trying it out right now to see, if the behavior of showing red IPs in the ddns-widget is changing.

No more red IPs... will stick with gertjans service for now.

🖖

Hello!

https://redmine.pfsense.org/issues/9296

?

John

The address does not change. Most devices use dynamic IP addresses, which are assigned by the network when they connect and change over time.

@Gertjan said in Dynamic DNS resolved to wrong IP:

Activate "Verbose logging" so you can when the wrong IP is set - this will be shown in the logs.

You mean activate it in the DDNS client, right? There it resolves to the right IP. Only not in the VPN-client on my smartphone.