GitHub - Cottand/leng: :zap: fast dns server, built to block advertisements and malware servers
github.com
:zap: fast dns server, built to block advertisements and malware servers - GitHub - Cottand/leng: :zap: fast dns server, built to block advertisements and malware servers

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

    • @nico@r.dcotta.euOPEnglish
      1•1 year ago

      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

        • @nico@r.dcotta.euOPEnglish
          1•1 year ago

          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.worksEnglish
            2•1 year ago

            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.euOPEnglish
              1•1 year ago

              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

                • @nico@r.dcotta.euOPEnglish
                  1•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)