IPSec Tunnel with dyndns not working after public IP renewal

[MarcP1]

Hi all,

in a hand full of sites we have got problems with our dyndns connected ipsec sites.

These tunnels have to be manually reseted from time to time.

Within the logs I can see the tunnel is getting down and our HQ Fortigate tries to connect to the old public IP address.

Also shown in the log, the new public IP is trying to initiate a connection to the HQ FG. 

Seams like the FG is not updating its dns entry for this site. 

After disable/enable the tunnel the site is up immediately. 

Anyone got an idea on this? Can´t be the solution to restart a tunnel from time to time.

Regards

Marc

[MarcP1]

Would like to, but the command does not exist.

[MarcP1]

Do I have to write it in there / like this?

config System ddns

edit 1

set monitor interface "TunnelName"          - or the WAN Interface in general?

set use-public-ip enable

 set update-interval 60

end

[AEK]

use-public-ip will be available once you set ddns-server to FortiGuardDDNS