this post was submitted on 15 Nov 2023
156 points (95.9% liked)

Selfhosted

40219 readers
977 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

A few months ago I went on a quest for a DNS server and was dissatisfied with current maintained projects. They were either good at adblocking (Blocky, grimd...) or good at specifying custom DNS (CoreDNS...).

So I forked grimd and embarked on rewriting a good chunk of it for it to address my needs - the result is leng.

  • it is fast
  • it is small
  • it is easy
  • you can specify blocklists and it will fetch them for you
  • you can specify custom DNS records with proper zone file syntax (SRV records, etc)
  • it supports DNS-over-HTTPS so you can stay private
  • it is well-documented
  • can be deployed on systemd, docker, or Nix

I have been running it as my nameserver in a Nomad cluster since! I plan to keep maintaining and improving it, so feel free to give it a try if it also fulfils your needs

you are viewing a single comment's thread
view the rest of the comments
[–] BaroqueInMind@kbin.social 26 points 1 year ago (3 children)
[–] Appoxo@lemmy.dbzer0.com 23 points 1 year ago (2 children)

Or Technitium...

[–] ikidd@lemmy.world 1 points 1 year ago (1 children)

Probably speed. I find pihole really slow, and I'm running it as a VM on a Xeon server.

[–] Appoxo@lemmy.dbzer0.com 1 points 1 year ago

Talking about a Xeon CPU in a context vacuum is like talking about a car.
A car is anything between 100€ rust bowl on wheels and a multi million € vehicle.

So either we need a benchmark score like Passmark (or other platform of choice) score for single and multicore or your cpu model.
Giving a piHole VM 1 or 2 cores from a CPU with a single core performance equal to a Raspberry Pi 3 is quite obvious why it isnt performing as well as say a shiny new Ryzen 7900X.

Context is key.

Mine runs in docker with full hardware access (no cpu/ram limits) on a i5-1135g7. The performance is (to me) pretty good.
BUT I only tried a comparison with unbound which gave me so-so results.

[–] nico@r.dcotta.eu 11 points 1 year ago (2 children)

I am working on adding a feature comparison to the docs. But in the meantime: leng has less features (like no web UI, no DHCP server) which means it is lighter (50MB RAM vs 150MB for adguard, 512MB for pihole), and easier to reproducibly configure because it is stateless (no web UI settings).

I believe blocky and coredns are better comparisons for leng than "tries to achieve it all" solutions like adguard, pihole...

[–] SpaceRanger@lemmy.world 5 points 1 year ago (1 children)

My pihole runs at 40MB in an LXC container...

[–] mea_rah@lemmy.world 2 points 1 year ago

Same with Adguard Home here sitting at 38MB.

[–] blackbarn@lemm.ee 1 points 1 year ago

I'll likely stick with Blocky as it seems to offer similar plus more. But good efforts!

[–] pimeys@lemmy.nauk.io 3 points 1 year ago

You can script this with nix quite easily without needing a UI. For many this is a big plus.