66
Technitium DNS v15.1.0 released with OpenID Connect integration (github.com)
submitted 4 months ago* (last edited 4 months ago) by to c/selfhosted@lemmy.world
37 comments fedilink hide all child comments
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] 3 points 4 months ago (10 children)

I migrated from pihole to technitium a few weeks ago and it was so smooth.

Native support for clustering is huge. I didn't even realize how complex managing the pihole had gotten trying to get it to sync to multiple instances.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 10 child comments
    •
  • [–] 2 points 4 months ago (7 children)

    That's good to hear!

    One feature I wish I could find was automatic DNS record creation for new docker containers I spawn.

    Can't wait to check out Technitium.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 7 child comments
    •
  • [–] 2 points 4 months ago* (last edited 4 months ago) (6 children)

    Oh do I have a treat for you, check out DNSWeaver.

    It's designed to do exactly that, to automate creation of DNS records for container services. I use it with Traefik. It reads from the same labels that Traefik already uses to proxy services but if you already use another reverse proxy and don't want to switch it supports dnsweaver-specific labels as well which are easy to add to your current deploys.

    I used it both with pihole and technitium and actually used it to make the migration easier. Great tool.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 2 points 4 months ago (2 children)

    Oh my. I am so thankful you shared this! I will be reading up on this and testing it out likely.

    Currently I use Caddy. Which I eventually would like to automate Caddy with this: https://github.com/lucaslorentz/caddy-docker-proxy

    Currently I build my own Caddy based off the official image with the cloudflare plugin

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 2 points 4 months ago* (1 child)

    DNSWeaver has support for caddy labels too! Specifically for use with caddy-docker-proxy. So yeah, really good fit for your architecture.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 4 months ago (2 children)

    Good news is that I was playing around with DNSWeaver, and got it working with Pihole. However, this gives me incentive to move off from Pihole because DNSWeaver can't create TXT records for tracking which DNS records it creates so that it can clean up after itself.

    So now I am torn between Adguard Home and Technitium. I just wish I could find a guide for getting Technitium working to at least on par with what I have setup.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 4 months ago (1 child)

    Not very complex. Use nebula-sync in docker.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 4 months ago

    I was doing basically this with a different sync tool, but I had a couple issues with it:

    • If I needed to toggle ad blocking I had to go toggle it on both pihole instances
    • When troubleshooting an issue I had to check two log sources, or disable one and then reproduce the issue again
    • Sync was one directional so I could only make configuration changes from the primary instance

    I've been a very happy Pihole user for years and years and Pihole 6 is the best yet, but once you're dealing with multiple pihole instances, Nebula Sync and Unbound, then Technitium is actually simpler to manage since it does all that natively.

  • permalink
  • fedilink
  • source
  • parent