Unable To Load Fortiguard Ddns Servers List On Fortigate Firewalls [exclusive] Access

Even if ping works, HTTPS might be blocked. Test the actual service endpoint:

config system dns set primary 208.91.112.53 set secondary 8.8.8.8 end Use code with caution. 3. Check Route and Source Interface

By following this sequence, the FortiGuard DDNS server list will successfully load, allowing you to establish stable, domain-mapped remote connectivity to your network.

diagnose test application ddns 1

This ensures your FortiGate uses its own, manually set DNS servers (preferably FortiGuard's) for its own requests, rather than ones supplied by your ISP.

show system dns

System DNS settings on the FortiGate often cause this issue, especially if the configured DNS servers cannot resolve Fortinet-specific domains. Go to . Even if ping works, HTTPS might be blocked

Common underlying issues include:

After a few minutes, verify update status:

The error message "Unable to load FortiGuard DDNS server list" typically appears when accessing the DDNS configuration section under . When this occurs, the dropdown menu for selecting a DDNS server remains empty, making it impossible to complete the setup through the graphical user interface (GUI). Check Route and Source Interface By following this

: When a FortiGate interface is configured with PPPoE or DHCP, it can automatically override the internal DNS settings with those provided by the ISP, which may conflict with FortiGuard services. Disabling this override is a crucial first step.

Do you see any specific when running execute update-now ?

Once enabled, navigate back to the page in the GUI to trigger a DDNS server list refresh. The CLI will output detailed logs. Look for specific errors such as SSL CA check failed , Connection timeout , or Authentication failed . To stop the debug stream, type: diagnose debug disable Use code with caution. Verifying the Solution To stop the debug stream