Thanks for the reply. Yes AppControl is active. By going on Chrome settings and changing the Use Secure DNS to Google (Public DNS) instead of current service DNS the websites that were being blocked are working.
Is it possible to fix this issue from Fortigate please? Instead of having to change the Secure DNS from Chrome. Thank you.
As you informed after switching on DNS (UDP/53) from DNS settings you are able to access the website.
DNS primarily uses the UDP protocol on port 53 to serve the address resolve requests.
The FortiGate DNS Filter inspects the UDP protocol on port 53 traffic that traverse FortiGate, and based on the DNS Filter profile configuration, makes the Allow/Monitor/Block or Redirect decision for the inspected traffic.
DNS over TLS (DoT) is a security protocol for encrypting and encapsulating DNS queries and responses over the TLS protocol. DoT increases user privacy and security by preventing eavesdropping and manipulation of DNS data via man-in-the-middle attacks.
Before enabling DoT or DoH, ensure that they are supported by the DNS servers. The legacy FortiGuard DNS servers (18.104.22.168 and 22.214.171.124) do not support DoT or DoH queries, and will drop these packets. Disabling DoT and DoH is recommended when they are not supported by the DNS servers.
Please refer to the below documents for more understanding:
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.