Settings
The Settings configuration governs the core operational parameters of the FortiADC. Use this module to establish the appliance’s fundamental identity, synchronize system time, and manage the configuration lifecycle. Proper setup of these parameters is essential for accurate logging, reliable network communication, and effective system recovery.
This section describes how to perform the following administrative tasks:
Configuring basic system settings
Define the appliance hostname and management interface parameters. Use this section to set the global idle timeout for administrative sessions and configure the display settings for the web UI and CLI.
Sending FortiADC Threat Telemetry to FortiGuard
Enable the sharing of anonymized threat data with FortiGuard Labs. This telemetry helps identify emerging security trends and improves the effectiveness of real-time security updates for the global Fortinet ecosystem.
Configuring system time
Synchronize the appliance with an external NTP server or set the system clock manually. Precise time synchronization is a prerequisite for valid certificate verification, accurate log timestamps, and HA cluster consistency.
Configuring an SMTP mail server
Establish a connection to an external mail server to facilitate the delivery of system alerts and reports. This configuration ensures that administrators receive timely notifications regarding system health and security events.
Pushing/pulling configurations
Synchronize configuration data between different FortiADC units. Use this feature to maintain consistency across multiple appliances or to replicate specific settings from a master unit to one or more targets.
Backing up and restoring configuration
Manage the long-term preservation of system settings. This section covers manual and scheduled backup procedures to local or remote storage, as well as the steps for restoring a configuration to recover from a system failure or hardware replacement.
Configuring DNS settings for non-root VDOM
Define dedicated DNS resolvers for individual virtual domains. This configuration applies exclusively to non-root VDOMs, allowing them to bypass global system DNS settings and utilize independent name resolution services tailored to specific tenant or network requirements.