Comment on DNS server
philpo@feddit.org 7 months agoI absolutely second Technitium as well. That thing is rock solid, can be used for basically everything, has blocking with a multitude of options and does provide a nice graphical GUI.
I have it running in a dual DNS setup (main server+a Zimablade nowadays) and that shit just works - it’s the container that has caused the least amount of problems in the last 3 years.
The API is fairly handy and quite easy - I have it integrated into HomeAssistant so I have a “Disable DNS Blocking” button in my “Network control” tab in the app.
The only downside is the fact that initially it can be quite overwhelming, especially if you are not an DNS guru and just did the step from AdGuard/PiHole - but soon you realise that you actually only need a few fields for basic operations.
The only downside is the fact that initially it can be quite overwhelming
On the other hand, Technitium comes with a fairly useful configuration straight out of the box. If you only want to use it on your home LAN (and therefore don’t necessarily need SSL), the only thing you really need to change is the block list field.
Yeah, absolutely - nevertheless it can inspire that reaction - which is a shame, because it’s indeed fairly easy.
I definitely bounced off of it as it had so much configuration I had no idea where to start. Adguard home was so much easier to set up, particularly because I also had to use it via DHCP as my router doesn’t have a dns option.
clb92@feddit.dk 7 months ago
I need that. I already have a bunch of physical buttons on my desk, which do things via Home Assistant, so that’d be an obvious one for me to add next.
philpo@feddit.org 7 months ago
Just saw that my way of doing this isn’t actually needed anymore, there is an integration now:
github.com/…/home-assistant-technitiumdns
clb92@feddit.dk 7 months ago
Works great for me, thanks.
Added a button on my Stream Deck too, which disables blocking on my two Technitium instances for 5 minutes.