DNS-over-HTTPS VS Technitium DNS Server

It works on minimal hardware. I am running it on an Orange Pi 3 LTS.

https://technitium.com/dns/

#!/bin/bash # Check input file if [ $# -eq 0 ]; then echo "Usage: $0 " exit 1 fi # Configurable value for zip file suffix SUFFIX="daily" # Get input file DNS_FILE=$1 # Read lines while read -r line; do HOSTNAME=$(echo $line | cut -d',' -f1) IP=$(echo $line | cut -d',' -f2) TOKEN=$(echo $line | cut -d',' -f3) # Construct API URL with IP and token, change any unwanted settings below to false as documented in https://github.com/TechnitiumSoftware/DnsServer/blob/master/APIDOCS.md#backup-settings URL="http://$IP:5380/api/settings/backup?token=$TOKEN&blockLists=true&logs=true&scopes=true&apps=true&stats=true&zones=true&allowedZones=true&blockedZones=true&dnsSettings=true&logSettings=true&authConfig=true" # Construct output file name FILE_NAME=$HOSTNAME-$IP-$(date +%Y%m%d)-$SUFFIX.zip # Call API curl -o $FILE_NAME $URL done < $DNS_FILE

You can try using a DNS/DHCP server other than the Windows one, e.g. Technitium I use this on Linux but as it is written in Dotnet it will of course also work on Windows https://technitium.com/dns/

I recently made an effort to harden my network due to (technically) exposing more of it with FireZone (WireGuard). For the curious, I shared some details in a recent comment. I didn't mention it in the comment, but I also set up local DNS (Technitium) with block lists.

Thanks for asking. There is already a feature request on Github for it. It is not planned to be implemented for now since there are some core features that are prioritized to be implemented. But it should come later once the planned features are implemented.

See what's new in this release: https://github.com/TechnitiumSoftware/DnsServer/blob/master/CHANGELOG.md

How would this compare to https://technitium.com/dns/?