Check for overrides:
show full-configuration system fortiguard Look for set fortiguard-anycast or set fortiguard-address . If set, try disabling them: Always test changes in a maintenance window and
get system status | grep "Date" Compare with actual UTC. If incorrect, configure NTP: However, for long-term health, ensure the FortiGate can
If all else fails, Fortinet TAC can provide hotfixes or engineering builds for stubborn cases – but 98% of cases are resolved by the steps above. Always test changes in a maintenance window and have a rollback plan. DDNS failure does not impact general internet traffic, but it will break hostname-to-IP updates for remote access or site-to-site VPNs relying on DDNS. Clear it with:
diagnose test application fortiguard 1 Or restart the FortiGuard service:
For immediate relief, manually configuring the DDNS entry via CLI bypasses the list loading step entirely. However, for long-term health, ensure the FortiGate can reach services.fortiguard.net over HTTPS with correct time and valid certificates.
config system fortiguard set proxy-type proxy set proxy-server <proxy-ip> set proxy-port <port> set proxy-auth disable end Without this, HTTPS requests bypass the proxy and fail. Sometimes the local cache corrupts. Clear it with: