GitHub - TechnitiumSoftware/DnsServer: Technitium DNS Server
github.com
Technitium DNS Server. Contribute to TechnitiumSoftware/DnsServer development by creating an account on GitHub.

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

  • unitedwithme@lemmy.todayEnglish
    61·
    3 days ago

    Someone should do a write up for pihole vs adguard vs technitium vs eBlockerOS

    https://eblocker.org/en/ (German product?) (BTW you’re all welcome that I showed you a new thing)

    Edit May 7: eBlockerOS seems geared towards better packet* inspection, hidden trackers protection, and fingerprinting. You can install a HTTPS cert* on your current machine so it does MITM packet inspection where it can scan*, inspect, and reencrypt from the looks of it.

    Im probably going to run this at work on my test environment to see how well it does overall. Maybe less granular control, but I like is more* than just an adblocker like pihole.

    • eutampieri@feddit.itEnglish
      2·
      4 days ago

      eBlocker does indeed seem German. It’s also much more than PiHole (it MITMs your packets, it seems) https://eblocker.org/en/how-eblocker-works/

      eBlocker uses SSL bumping with a unique root certificate to decrypt possibly encrypted TCP/IP packets. After this deep packet inspection a pattern matching to the target URI is performed. In case of a match, the request is answered by the eBlocker (instead of being sent to the target URI).

      As a slightly less accurate alternative, eBlocker uses DNS blocking for fallback, where the domains of known data collectors are blocked. This way, even devices that do not allow to install root certificates are also protected.