The FortiMail unit cannot connect to the FDN servers to use FortiGuard Antivirus and/or FortiGuard Antispam services.
For all FortiGuard connection types, you must satisfy the following requirements:
- Register your FortiMail unit with the Fortinet Technical Support web site, https://support.fortinet.com/.
- Obtain a trial or purchased service contract for FortiGuard Antispam and/or FortiGuard Antivirus, and apply it to your FortiMail unit. If you have multiple FortiMail units, including those operating in high availability (HA), you must obtain separate contracts for each FortiMail unit. You can view service contracts applied to each of your registered FortiMail units by visiting the Fortinet Technical Support web site, https://support.fortinet.com/.
- Configure your FortiMail unit to connect with a DNS server that can resolve the domain names of FortiGuard servers. For more information, see Configuring DNS.
- Configure your FortiMail unit with at least one route so that the FortiMail unit can connect to the Internet. For more information, see Configuring static routes .
You can verify that you have satisfied DNS and routing requirements by using the following CLI commands.
To check DNS resolution of the FortiGuard antispam service, use:
execute nslookup name service.fortiguard.net
To check DNS resolution of the FortiGuard antivirus service, use:
execute nslookup name fds1.fortinet.com
To check network connectivity, use:
execute traceroute <address_ipv4>
<address_ipv4> is one of the FortiGuard servers.
If you have satisfied these requirements, verify that you have also satisfied the requirements specific to the type of connection that is failing, listed in Troubleshoot FortiGuard connection issues.
FortiGuard connectivity requirements
(FortiGuard Antivirus/FortiGuard Antispam)
(FortiGuard Antispam/FortiGuard Antivirus)
If you suspect that a device on your network is interfering with connectivity, you can analyze traffic and verify that the FortiMail unit is sending and receiving traffic on the required port numbers. Use the CLI command
diagnose sniffer to perform packet capture. If traffic is being corrupted or interrupted, you may need to perform packet capture at additional points on your network to locate the source of the interruption.