Technitium DNS Server VS nextdns

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/?

I am working on open source DNS server project since a few years adding features to it whenever I get time: https://github.com/TechnitiumSoftware/DnsServer

Block 45.76.93.104 and 2001:19f0:6c00:1b0e:5400:4ff:fecd:7828 at the firewall if possible.

Ensure that DNS-over-HTTP (DoH) is enabled where it can be.

Set upstream DNS servers that block malware, such as 1.1.1.2 or NextDNS

Delete "fritz.box" from the domain search list in DNS settings.

Educate your parents to be cautious about directly typing domain names or searching from the OmniBox.

https://nextdns.io/

https://blog.cloudflare.com/introducing-1-1-1-1-for-families...

I've tried hosted Pi-Hole and AdGuard Home. They are good as long as I'm around to fix stuffs. Then I tested something which can be global (home) and also for individual devices -- Control-D, NextDNS, and Adguard DNS. All of them works pretty well. If I really have to choose, then it would be in the order of NextDNS > Control-D > AdGuard DNS. Affiliated with none, and have decided to subscribe to all three to further test them for this year.

https://controld.com

https://nextdns.io

https://adguard-dns.io

Okay but NextDNS' own homepage says it "blocks ads and trackers on websites and in apps" - https://nextdns.io

I first used Safari on Windows around 2006. Put me off forever.

You just need Firefox and the extensions that mean ads are never seen.

That said, take a look at https://nextdns.io

just run snort and get nextdns.io account and use those DNS servers to control your DNS.

I'm using NextDNS which can be integrated into TailScale MagicDNS. It works seamlessly. You may need to pay if you have a high usage rate. I pay for the Pro version but that's less than $30 CAD a year. I did have in house Raspberry PI and Pi-Hole DNS but it was a lot of work.

pretty much to the same effect of a pihole, yet you can get up and running in minutes. You can then configure wherever you please: your browser, your laptop, your phone, or even your router.

[0]: https://nextdns.io