awesome-selfhosted VS Technitium DNS Server

For self-hosting, one that I enjoyed using in the past is YunoHost. [0]

But there are many, and you can find some lists on the web, eg. on awesome-selfhosted [1]

[0] https://yunohost.org/

[1] https://github.com/awesome-selfhosted/awesome-selfhosted?tab...

I think there are two aspects to this:

* The software: different open source solutions have very different requirements at a high level: language, platform or even system requirements. Say you want to take messaging off centralized platforms: you need to host something like Matrix, which is very well made and polished but takes a lot of resources to run. Alternatively, you could use Jabber, which scales like no other but is an absolute hell to setup and maintain. Same can be said about music, videos, movies and all other things

* Operations: probably simple if you ask someone on HN, but you still need to understand networking, operating systems and file systems. I started using Linux when I was 11 in the distant 2000, and even now I'm not very enthusiastic if I have to make some changes to my zfs. You also need to consider backups and security and resources. Say you wanna run openstreetmap(which we recently started doing at work). Awesome but that requires an ungodly amount of fiddling in addition to an astonishing amount of time needed to unpack, even on enterprise hardware.

If you are in the tech world, https://github.com/awesome-selfhosted/awesome-selfhosted is a great place to start. But if you want to make it simpler... Idk... A lot of people would need to put in a lot of effort, as in build a linux distro around this idea, along with "recommended hardware", one click install(a very dumbed down equivalent of portainer), and some backup and alerting mechanisms built into the system. It's a tough question and frankly I don't have the answer.

Nice but I'm surprised not to see anyone talking about awesome (https://github.com/awesome-selfhosted/awesome-selfhosted) which are lists of open source alternatives. It's in the form of github repositories

Teams: several options

Office 365: several options

OneDrive: several options

Check out https://github.com/awesome-selfhosted/awesome-selfhosted

3. Awesome Self-Hosted

None of these lists ever seem to be as fleshed out, up to date, or well organized as https://github.com/awesome-selfhosted/awesome-selfhosted , though imo any more attention on the self hosted scene is awesome. We're now self hosting everything at my co-op, and it's a dream. Saves us money, provides learning opportunities, potentially is getting us work (managed hosting providers asking if we can be a devshop for their clients, for example), and lets us give back to the FOSS community as we uncover bugs.

We use:

* Matrix / Synapse for comms (slack alternative) (managed hosting through etke.cc)

There are a ton of resources about HW aspects of home labs for beginners but not so much for what to run on them and why. There are lists like https://github.com/awesome-selfhosted/awesome-selfhosted but they are confusing for absolute beginners like me. Are there any good SE project guides you know?

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