Unable To Load Fortiguard Ddns Servers List On Fortigate Firewalls ((free)) -

. It is also unavailable on high-end appliances, FortiGate-VMs, or when in transparent mode. For persistent issues, you can review detailed logs using diagnose debug application ddnscd -1 diagnose debug enable for your particular FortiOS version to ensure the syntax matches? Unable to load FortiGuard DDNS server list

When attempting to configure a new Dynamic DNS entry, the FortiGate cannot retrieve the list of available DDNS service providers (e.g., FortiGuard DDNS, No-IP, DynDNS). This results in an inability to select a server type, blocking the configuration of DDNS services.

: Ensure the FortiGate can resolve and reach Fortinet domains. execute ping service.fortiguard.net execute ping update.fortiguard.net Check DDNS Daemon

The issue "Unable to load FortiGuard DDNS server list" on FortiGate firewalls typically prevents you from selecting a DDNS server in the GUI, often occurring after firmware upgrades or due to DNS/network configuration conflicts. Common Root Causes Unable to load FortiGuard DDNS server list When

config system fortiguard set fortiguard-anycast disable set protocol udp end

The “Unable to load FortiGuard DDNS servers list” error typically stems from connectivity or DNS problems, not the DDNS service itself. By following this guide—testing DNS, verifying policies, and using CLI workarounds—you can restore DDNS functionality. If issues persist, contact Fortinet Support with the debug output from diagnose debug application update -1 and diagnose debug enable .

If the DDNS list remains blank, use the FortiOS built-in diagnostic sniffer and debugging tools to look at the raw exchange. 1. Sniff FortiGuard Packets execute ping service

If fortiguard.com isn’t recognized, use the IP-based workaround (temporary):

: If uptime is critical, consider configuring DDNS with both FortiGuard and a secondary provider. The FortiGate can be configured to use multiple DDNS services simultaneously, providing redundancy in case one fails.

If the issue is specifically with the fortiguard-ddns list, try using a third-party provider like No-IP or DynDNS if you have those credentials. Summary Table Description Why it helps Set to 8.8.8.8 or 1.1.1.1 Ensures FortiGate can resolve fortiguard.net . Check WAN Verify IP and Route Ensures traffic can reach the internet. CLI update-now Run execute update-now Debugs FortiGuard connectivity. Set Source IP config system fortiguard Forces traffic through the correct WAN. Use CLI Config Configure via CLI Bypasses GUI load failure. If the hostname does not resolve

A known bug occasionally stops the FortiOS GUI from fetching the server dropdown menu correctly, even if the firewall has active backend connectivity. Step-by-Step Solutions 1. Disable "Override Internal DNS" on WAN Interfaces

If you have exhausted all troubleshooting steps and the problem persists, it is time to contact Fortinet Support. Provide them with the output of the diagnostic commands you have run, especially the results of the diagnose debug application update -1 command, which will help them identify the root cause more quickly.

If the hostname does not resolve, the problem is likely DNS-related. Verify that the DNS server settings in are correct and reachable. Also, check whether the external interface is overriding these settings with DNS values obtained from DHCP or PPPoE; if so, disable the "Override internal DNS" option.