Configuration using Admin UI
If you followed the installation steps for Debian 10 or if you are using the virtual appliance for VMware or Microsoft Azure, all settings of DNS Safety can be easily managed using your browser.
Navigate to the IP address of the server where DNS Safety is installed and you should see the following login page. Use root and Passw0rd credentials to logon.
The Admin UI is implemented using Django Python module and is run by Apache. All files of Admin UI are installed into
/opt/dnssafety-ui folder. The folder is owned by standard
daemon user (just like core DNS Safety daemon).
Configure DNS Filter
After login you will find yourself in the Dashboard. This page shows some useful information about the DNS server. It is possible to configure the hostname, network settings, view logs and system status.
After any change of the configuration, click the Apply Settings followed by Save and Restart/Reload button in the top right corner.
The UI / Traffic Monitor tab allows you to see the summary of DNS requests within your network.
By default the config file has 4 different filtering policies pre-installed. Default policy blocks all advertisements (like does for example Pi-Hole), well known adult sites and site promoting weapons, cracks, hacking, illegal activity and self harm. Other policies allow you to adjust filtering level based on your requirements.
Policies are used to organize devices within a LAN into groups (based on their MAC or IP address, range or subnet) and apply common filtering settings to them. Such pair of devices and rules applied to them constitutes a Filtering Policy.
As an example consider having two groups of devices - those belonging to students and teachers. Teachers would like to block web site ads and students should not be able to get access to web sites with explicit contents. To solve this problem we create two policies - Strict and Relaxed, adjust blocking rules as needed and then assign teachers to Relaxed policy and students to the Strict one.
Verify it Works
In order to verify DNS Safety works as expected try to navigate to welcome.dnssafety.io. This domain name SHOULD NOT BE ACCESSIBLE. If it is not so then please check all installation/configuration steps once again. Be sure to force refresh your browser!
Please note, DNS responses are usually heavily cached by both the operating system and the browser, so in order to verify everything was installed correctly it is recommended to open a new Incognito Window in the browser and test access to welcome.dnssafety.io as explained above. Running ipconfig /flushdns prior to opening of Incognito Window is also strongly recommended!