This KB article shows the process on how to use the DNS filtering in order to block websites.
This release includes significant user interface changes and many new features that are different from the SonicOS 6.5 and earlier firmware. The below resolution is for customers using SonicOS 7.X firmware.
Configuring the DNS on the firewall
1.Go to Network|DNSlSettings, configure the DNS (manually or to inherit dynamically from WAN) and enable the option Enable proxying of split DNS servers.
2. Navigate to Policy|Rules and Policies|Access Rules and create the following:

Method 2 - Blocking via App Rules:
1. Navigate to Objects|Match Objects|Match Objects and create the following:

2. Navigate to Policy|Rules and Policies|App rules and create the following:

Method 3 - Blocking via the browser:
1. Open up the web browser and type in the bar chrome://flags/ for Chrome browser and edge://flags/ for Edge browser. Search for the Experimental QUIC Protocol, select Disabled and restart the browser.

2. For Firefox browser type in the bar about:config. Search for the network.http.http3.enable and set it to false:

This release includes significant user interface changes and many new features that are different from the SonicOS 6.2 and earlier firmware. The below resolution is for customers using SonicOS 6.5 firmware.
Method 1 - Blocking via Access Rules:
1. Create a Service Group named QUIC ports containing the ports UDP 80 and 443. Click MANAGE in the top navigation menu. Navigate Objects|Sservice Objects:


2. Navigate to Rules|Access Rules and create the following:

Method 2 - Blocking via App Rules:
1. Navigate to Objects|Match Objects and create the following:
2. Navigate to Rules|App rules and create the following:

Method 3 - Blocking via the browser:
1. Open up the web browser and type in the bar chrome://flags/ for Chrome browser and edge://flags/ for Edge browser. Search for the Experimental QUIC Protocol, select Disabled and restart the browser.

2. For Firefox browser type in the bar about:config. Search for the network.http.http3.enable and set it to false:
