Update – 10. November 2021: It seems that the server “45.75.200.89” is not in use anymore – it is “not reachable” at the moment. Please use “194.69.172.53” instead. Blogpost – 3. November 2020: From time to time customers noticed that the Fortigate cannot reach the Fortiguard Servers anymore. This is…
10,004 total views, 35 views today
Some of you may have noticed that a Fortigate – configured to use the FortiGuard DNS Servers – is not resolving some DNS names anymore. Consequences can be that FQDN address objects can not be resolved or a configured mail server can not be used anymore. 766 total views, 3 views today
766 total views, 3 views today
For some reasons Fortigates are are not able to load the FortiGuard DDNS server list. Therefore you are not able to configure DynDNS on your Fortigate anymore. In the WebUI you will see following error message under Network > DNS > FortiGuard DDNS and you are not able to list…
1,139 total views, 4 views today
Last update from 12.05.2021 at 09:40 Swiss local time: We have noticed an improvement in the situation. Some rare rating timeouts still show up from time to time, but the majority of requests are being answered correctly. Also the DNS servers are working as usual again. We have noticed an…
There seems to be a vulnerarbility in some FortiMail versions, that allow an unauthenticated remote attacker to access the system by requesting a password change. Please refer to the FortiGuard PSIRT article. The problem here is not only the unauthorized access to the system, but also the change of the…
2,445 total views, 2 views today
FortiOS v6.2 has been released in March this year and we are still gaining experience with this version. In this article we would like to draw you attention to the protocol which is used for FortiGuard service communication. Up to v6.0 udp has been used, with 6.2 the default protocol…
Sind Sie interessiert, den BOLL Blog als RSS Feed zu abonnieren?