Selfhosted

40152 readers

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

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

156

leng - a fast DNS server with adblocking, built for self-hosting (github.com)

submitted 1 year ago by nico@r.dcotta.eu to c/selfhosted@lemmy.world

44 comments fedilink hide all child comments

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

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

If you mean CNAME flattening I have an issue for it. If you mean recursively resolving CNAME until the end record is found, it does support it.

For example, if you set a custom record mygoogle.lol IN CNAME google.com Leng will return a response with an A record with a google.com IP address when you visit mygoogle.lol

[–] MonkCanatella@sh.itjust.works 3 points 1 year ago (1 children)

I’m basically just wondering if I can replace my blocky+unbound setup with just leng!

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

I think the answer is yes (as leng is recursive) but can you explain your use-case and expected behaviour a bit so I can get a better idea of what you want unbound to do that blocky is not doing?

[–] MonkCanatella@sh.itjust.works 2 points 1 year ago (1 children)

I think it does caching because grimd does caching. I want a dns filter and dns resolver that's selfhosted but still performant and low latency. Caching of course is big part of that because if you're running recursive queries every time, your ping will be like 100-200ms.

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

Leng will cache each step of recursion, and it relies on upstream resolvers to do recursion for it as well (like grimd), so you should not be seeing 200ms resolution in any scenario.

I am keen for you to give it a shot - if you do please make an issue if it's not behaving like you were hoping for

[–] MonkCanatella@sh.itjust.works 1 points 1 year ago (1 children)

Ahh interesting. So do you have to manually set an upstream dns server?

[–] nico@r.dcotta.eu 1 points 1 year ago

Correct, and much like grimd you can specify several. But unlike grimd, leng will perform recursion when the upstream server is not capable of resolving queries completely (namely, because a CNAME resolved by upstream somewhere points to a domain that is part of your custom DNS records, or vice versa)