![]() ![]() The DDNS server list is obtained from FortiGuard, so FortiGuard settings may need to be reviewed. In this case, user may try to restart the DDNS connection: But in some cases it may be the only thing displayed (no other output even after 15min) > this is not an error, but a repeating timer-message to show the DDNS is active. See this article for details (last steps) ![]() Check the FortiGuard settings and change accordingly. Set use-public-ip enable this shows a problem connecting to FortiGuard servers. Svr= 208.91.113.230 this usually points to a routing errorĪ possible fix if the ISP router and a local subnet are used on the wan interface, is to change the following in the DDNS setup: Run the following command from the CLI to find out the IP address used by FortiGate for the DDNS server:ĭdns_ip=208.91.113.230 ddns_port=443 svr_num=1 domain_num=3 If not correct, try the following commands to see if correctly updated: Make sure this is the correct public IP user wants to update in DDNS. This is reflected in Dashboard status widget, or in Network - > DNS. One common solution is to configure a static route to a known FortiGuard IP through specific ISP Internet connection.įirst of all, make sure that the FortiGate knows the new IP address. ![]() This is shown below, and also other possible causes for this. One possible way to solve this, users need to configure static routing to allow the traffic from FortiGate to the FortiGuard IP addresses through that specific internet connection. When the public IP of the FortiGate has changed, FortiGuard DDNS updates are required over one specific ISP interface and sometimes FortiGuard DDNS does not update the IP. This article describes how to fix the 'IP not-updating' problem with FortiGuard DDNS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |