Dynamic DNS IP address only updated with forced update

[fleximus]

Dynamic DNS is used at the WAN interface using the service of DNSexit.
OPNsense is used behind a FritzBox Cable and WAN ip address is used from the FritzBox LAN pool 192.168.178.0/24.

Cached IP address not up to date and therefore red colored. Edit + forced update leads to an updated IP.

[fichtner]

Does this happen on reboot, too? It looks like a larger issue in the WAN IP change trigger area.

[fichtner]

It's a little different from what is describe at http://www.dnsexit.com/Direct.sv?cmd=ipClients but if you say this works when forced I'd rather not switch away from HTTPS.

[fleximus]

Yes, I'd also stick to HTTPS as it works communicating the IP address to their system. I would suspect that the bug resides not in the communication itself but rather more at the time it should be invoked/updated.

I'll test if it's set at reboot and let you know later.

[fichtner]

also see https://forum.opnsense.org/index.php?topic=1165.0

[fleximus]

The IP address is updated and in green state after a reboot. Hope this helps.

[fichtner]

@fleximus can you confirm the following?

I'm getting this with my first DDNS service entry ONLY but the
others are working absolutely fine - even for the same service.

[fleximus]

@fichtner I cannot confirm. Two times DNSExit used with exactly the same settings and OPNsense report two different IP addresses. First IP appears in green and is actual, second is an older IP and appears in red. After official IP change, both turn red. Same numbers as before, but still different to each. Caching problem?

[fichtner]

Fixed since 15.7.22.

[MinesweeperM]

I have a same trouble on 18.7.8 - Cached IP becomes red, but updates only when forced.

[fichtner]

You can set a nightly cron job under System: Settings: Cron.

[MinesweeperM]

Thank you for answer :) Yes, i do so and it works...