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 user 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 :)

  • Konraddo@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    2 hours ago

    I’m just barely okay at self hosting applications, so using Unbound together with Pi-hole poses a great challenge. Technitum DNS is a whole package and the GUI is user-friendly to me. But, after using Netbird on VPS (for the reverse proxy mostly), because of a different sub-domain being used, I think I don’t need Technitium anymore though it continues to work so I have no reason to change.

    • hellmo_luciferrari@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      43 minutes ago

      Pihole + unbound on the same box as my DNS has been super simple for me. I didnt do a lot of extra configuration for Unbound, I used mostly the guide that was on Pihole official documentation.

      As for reverse proxy, I have Caddy setup. And to access my homelab I use wireguard.

      Most of my services run on a separate box running docker.

      I’ve woven most of it together bit by bit. I’m slowly upgrading different pieces and its lead me down a rabbit hole. So I found this post intriguing.

      Biggest hurdle with Technitium for me is the lack of documentation. I can say the compose file they provided has lots of comments. That doesn’t solve for a few pieces for me though. Systemd-resolv uses port 53 on my host box, and I have to find out the ramifications for disabling that and using Technitium. That and I am unsure of what extra capabilities I have to grant that container. And I have to find out how adding it to my reverse proxy docker network.

      So its gonna be trial and error I suppose! I’m looking forward to getting DoT or DoH or DoQ setup.