Technitium DNS Server v15.1.0 has been released with support for OIDC! Now you can use your preferred identity provider to log in to Technitium accounts, and manage your DHCP/DNS deployments with approriately granular permissions controls.
I’ve played around with it, and safe to say that the SSO integration works well. I’ve written a guide to set it up against Kanidm here. There were some OIDC/clustering bugs in prior v15 releases, and with v15.1.0 they have been squashed and solved.
The major release of version 15 also include various important changes, such as the following highlights:
- A new API call for Prometheus metrics
- Query Logs apps can now follow live updates
- Codebase updated to .NET 10 runtime
- HTTP tokens are now accepted via the
Authorization: Bearer <token>header - Many other bugfixes, secfixes, and improvements…
Technitium is pretty great. Hope everyone enjoy the release :)
Has anyone used this and Pihole and have some thoughts on which they would use and why?
Currently using Pihole myself. For adblocking, and a local DNS server. I also have Unbound configured and installed which my Pihole uses.
Anyone have any insight on this before I work on spinning something like this up?
I never could get Technitium working correctly, it’s like there’s some switch you need to throw to actually get it to accept requests. I posted that and had a couple of other say the same thing. I didn’t spend a lot of time with it, IMO a DNS server should serve requests out of the box.
Went back to Unbound on my OPNsense router.
Went back to Unbound on my OPNsense router.
Yeah. I get more mileage with pFsense + unbound
I’ve used PiHole and have switched to Technitium. Basically there’s vastly more options available. A lot of DNS records and zones that simply isn’t available with PiHole.
Also much better support for more advanced protocols (DoH, DoT, …).
But to get the best out of it you do need to use the “Advanced Blocking app”, which is a sort of a plugin. And it doesn’t always play nice with defaults in terms of blockint.
It’s best if one uses one or another, also because of how temporary disabling works.
Sounds like I am going to dig into some documentation for Technitium.
When you mention the “Advanced Blocking App” can you provide a link that for more info by chance?
I had zero plans of running both, more of a situation where I would want to try Technitium and then switch once I know everything is working!
Thank you for the info!
It’s an addon that you enable/install inside Technitium, you only need to configure it in the Admin ui.
Perfect! I saw there were addons once I spun up a quick docker container for it. Though, I feel I may have a bit of configuring to do to get this working. My host server uses systemd-resolv so I may have to wrestle with that.
Thank you!
I’ve used both.
Pihole is fine for a standard replacement of DNS for record lookups with the ad blocking most ppl want. But pihole is just fancy dnsmasq, you can’t manage much more DNS than A records. (That was 4 years ago, though, things might have changed).
Technitium is a real DNS server with all the things DNS I supposed to be able to do. I use it for the zone transfers.
Performance is better than pihole, too, but that may also have changed.
With my Pihole setup I currently use A records and CNAMES for my local DNS entries. What interests me with Technitium is that it supports DoH, DoT, and DoQ. Which I would like to see if I could implement.
I remember a while back looking into setting up DoH or DoT with Unbound on my Pihole box, but that didn’t work well for me (likely a me issue.)
But I am constantly looking to improve my homelab setup.
I have used Pi-Hole but not Technitium. As I understand it, Technitium has some more options than that of Pi-Hole + Unbound that power users may appreciate.
