home.social

#dnsdist — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dnsdist, aggregated by home.social.

fetched live
  1. There's an interesting conversation going on on the #NANOG #mailinglist. It's about running a #DNS resolver for a medium-sized service provider network:

    Recommended DNS server for a medium 20-30k users isp

    I particularly love that the people from @quad9dns chipped in, and revealed how they split their front- and backend with #dnsdist. Splitting the front- and backend of internet-facing services is something that I already learned in University as a best-practice.

  2. There's an interesting conversation going on on the #NANOG #mailinglist. It's about running a #DNS resolver for a medium-sized service provider network:

    Recommended DNS server for a medium 20-30k users isp

    I particularly love that the people from @quad9dns chipped in, and revealed how they split their front- and backend with #dnsdist. Splitting the front- and backend of internet-facing services is something that I already learned in University as a best-practice.

  3. PowerDNS Security Advisory 2025-02 for DNSdist: Denial of service via crafted DoH exchange

    Impact: Denial of service
    Exploit: This problem can be triggered by an attacker crafting a DoH exchange

    CVE-2025-30194

    dnsdist.org/security-advisorie

    #dnsdist

  4. The goal was to shrink #dnsdist to fit in a CPE router, using OpenWRT on small hardware.

    #FOSDEM

  5. The goal was to shrink #dnsdist to fit in a CPE router, using OpenWRT on small hardware.

    #FOSDEM

  6. And to end the day at the #DNS devroom, "Honey, I shrunk DNSdist" by @habbie (replacing @rgacogne, the maintainer who is sick without even the fault of the FOSDEM)

    Disclaimer: #dnsdist is used by the public DNS resolver {doh,dot,doq}.bortzmeyer.fr

    #FOSDEM

  7. And to end the day at the #DNS devroom, "Honey, I shrunk DNSdist" by @habbie (replacing @rgacogne, the maintainer who is sick without even the fault of the FOSDEM)

    Disclaimer: #dnsdist is used by the public DNS resolver {doh,dot,doq}.bortzmeyer.fr

    #FOSDEM

  8. @SIDNlabs Thanks for contributing to the #DNS resolution diversity.
    The original part is that you use many proxies (@PowerDNS #dnsdist ) and only a few backends (@nlnetlabs #unbound ). I know by experience that both work well together (esp. with PROXYv2).
    What were the advantages (practical, technical, financial) that lead to this setup?
    Also, do you share cache between nodes either at the proxy or backend (cachedb)?

  9. The Custom API widget from #hompage is super dope! I can now see some stats from #dnsdist and my other #dns server that it doesn't have integrations for.

    #homelab #selfhosted #selfhosting

  10. The Custom API widget from #hompage is super dope! I can now see some stats from #dnsdist and my other #dns server that it doesn't have integrations for.

    #homelab #selfhosted #selfhosting

  11. Ugh, Turns out letting your #dns server mirror the root zone is a good way to amplify ddos attacks...

    Added a rule to #dnsdist that drops incoming packets with RD set while I come up with something more elegant.

    The victim seems to be a small Brazilian ISP Jupiter. :(

  12. As I always say reboot the shit out of your #homelab! I thought I had HA on my #dnsdist dns loadbalancer. Updated my #incus deployment and some kernel and zfs stuff and.... boom, I don't have fucking internet!

    HA huh!! 🤣💥🫤

    #selfhosted

  13. As I always say reboot the shit out of your #homelab! I thought I had HA on my #dnsdist dns loadbalancer. Updated my #incus deployment and some kernel and zfs stuff and.... boom, I don't have fucking internet!

    HA huh!! 🤣💥🫤

    #selfhosted

  14. Ah bah finalement pas de #DoH3 et #DoQ pour @DNS_Shaftinc 😢

    Je pensais que quiche, la bibliothèque de Cloudflare pour faire du Quic, était dans le tarball de #dnsdist, mais après vérif, il y a plutôt un script qui télécharge quiche et compile le truc.

    Meh :/

  15. Ah bah finalement pas de #DoH3 et #DoQ pour @DNS_Shaftinc 😢

    Je pensais que quiche, la bibliothèque de Cloudflare pour faire du Quic, était dans le tarball de #dnsdist, mais après vérif, il y a plutôt un script qui télécharge quiche et compile le truc.

    Meh :/

  16. I keep getting brought back to #nextdns. So I decided to use #dnsdist to balance between internal domains and pushing everything else out to nextdns to see if that works as a thing in the #homelab !

  17. I keep getting brought back to #nextdns. So I decided to use #dnsdist to balance between internal domains and pushing everything else out to nextdns to see if that works as a thing in the #homelab !

  18. you know, it is always great when you report an issue and it actually gets fixed.

    Like what happened today! github.com/PowerDNS/pdns/pull/

    #dnsdist

  19. @tuhgy I use netdata agents to expose prometheus metrics and then graph that with grafana. I'm using this dns load balancer called #dnsdist and that exposes prometheus metrics that I scrape and gives me all of the DNS stuff. I balance 2 dns servers with it.

  20. @tuhgy I use netdata agents to expose prometheus metrics and then graph that with grafana. I'm using this dns load balancer called #dnsdist and that exposes prometheus metrics that I scrape and gives me all of the DNS stuff. I balance 2 dns servers with it.

  21. I had to mess with #dns cause.. I don't fucking know! Anyways I got 2 #dnsdist boxes and noticed the second one aint really getting any traffic. So I decided to move it to more of a failover rather than an active one. #vrrp ( keepalived) for the win!

    #homelab #selfhosted #selfhosting

  22. I had to mess with #dns cause.. I don't fucking know! Anyways I got 2 #dnsdist boxes and noticed the second one aint really getting any traffic. So I decided to move it to more of a failover rather than an active one. #vrrp ( keepalived) for the win!

    #homelab #selfhosted #selfhosting

  23. ok #dnsdist heads! This damn console is stupid! is there a way to tie(view) a client to a domain and how much it has been served/requested/whatever?

    #homelab

  24. ok #dnsdist heads! This damn console is stupid! is there a way to tie(view) a client to a domain and how much it has been served/requested/whatever?

    #homelab

  25. PSA: don't update to 1.9.2 as it contains a crasher regression. 1.9.3 will be released soon.

  26. PSA: don't update to #dnsdist 1.9.2 as it contains a crasher regression. 1.9.3 will be released soon.

  27. I been having my #dns set up not be the best with failover in the #homelab . Right now i'm using #dnsdist as a dns load-balancer. It can use the Proxy-Protocol to pass source IP to the backend dns server that also has this capability. Here is the problem. The health checking mechanism #dnsdist has doesn't play nice with my DNS. So I have to force the backend services up! Well, when the backend dns goes down, #dnsdist doesn't know that and still try's to pass it traffic and it's all bad.

    #dns

  28. I been having my #dns set up not be the best with failover in the #homelab . Right now i'm using #dnsdist as a dns load-balancer. It can use the Proxy-Protocol to pass source IP to the backend dns server that also has this capability. Here is the problem. The health checking mechanism #dnsdist has doesn't play nice with my DNS. So I have to force the backend services up! Well, when the backend dns goes down, #dnsdist doesn't know that and still try's to pass it traffic and it's all bad.

    #dns

  29. @[email protected] @wutti Good candidate for upstream DNS encryption provider might be also . Versatile thing with also DoH and DoQ support, which could be used together with pihole's dnsmasq. But haven't tried to compile it on openwrt myself. Visit dnsdist.org for help.

  30. @joel @wutti Good candidate for upstream DNS encryption provider might be also #dnsdist. Versatile thing with also DoH and DoQ support, which could be used together with pihole's dnsmasq. But haven't tried to compile it on openwrt myself. Visit dnsdist.org for help.

  31. Sorry for short #DNS #downtime, host operating system is now upgraded to latest release and all latest #security patches have been applied, #python and #dnsdist upgraded.
    All good! @ https://dnskv.com
  32. @zrail I'm still considering keeping #coredns just for my #homelab services. #dnsdist has the ability for me to move traffic between "pools" via source. So right now I'm doing that for all of my homelab sources and everything else runs through the "home" stuff.

  33. @zrail I'm still considering keeping #coredns just for my #homelab services. #dnsdist has the ability for me to move traffic between "pools" via source. So right now I'm doing that for all of my homelab sources and everything else runs through the "home" stuff.

  34. I couldn't leave well enough alone in the #homelab I put #dnsdist back in the mix balancing 2 #coredns servers for my services based on source and then the rest going to #blocky. I gotta set vrrp with one more instance of dns dist and I got so much overkill of DNS for no for fucking reason!

  35. I couldn't leave well enough alone in the #homelab I put #dnsdist back in the mix balancing 2 #coredns servers for my services based on source and then the rest going to #blocky. I gotta set vrrp with one more instance of dns dist and I got so much overkill of DNS for no for fucking reason!

  36. I'm not exactly sure how I got here! I been trying to figure out my DNS infra for some damn reason. It's DNS who the fuck cares. I can't let it go!

    I just want to exercise my second DNS server, cause it's just there. So lets put #dnsdist in front of it, solid!. It gave me a promfana endpoint to see shit. Dope! Then I'm like I want that for my DNS servers! Insert #coredns. It's coo! Fast! Easy to use! Ad blocking, not so much. Insert #blocky. Ok WTF is going on!

    #homelab #selfhosted

  37. I'm not exactly sure how I got here! I been trying to figure out my DNS infra for some damn reason. It's DNS who the fuck cares. I can't let it go!

    I just want to exercise my second DNS server, cause it's just there. So lets put #dnsdist in front of it, solid!. It gave me a promfana endpoint to see shit. Dope! Then I'm like I want that for my DNS servers! Insert #coredns. It's coo! Fast! Easy to use! Ad blocking, not so much. Insert #blocky. Ok WTF is going on!

    #homelab #selfhosted

  38. Been on this DNS kick in the #homelab. I'm really enjoying g #dnsdist as a #dns loadbalancer with #coredns backing at least one of my servers. I'm going to add 2 more dns servers to the mix and have them funnel down to an adblocker type! I'm still thinking about nextdns. I just can't seem to get over paying for something that you can do with pi-hole or the likes.

  39. Spent a good time with #dnsdist as a #dns load balancer and it works seems to be working pretty well so I don't just have a second DNS server just chilling. I tried to get the source ip address to get passed to the backend but still missing something there. Good to get back into the #homelab #selfhosting #selfhosted

  40. In other news, all of our domains fell off the internet for a couple of minutes. The reason? DNS. It's always DNS ;-) I did some autumn cleaning and restructured and simplified the way we're doing DNS here. It's a pretty neat setup based on #dnsdist and #PowerDNS. Unfortunately, I managed to screw up the TSIG key, and the newly reinstalled DNS servers were unable to do domain transfers from the hidden primary PowerDNS server, so - no DNS entries for you! :-) Error was fixed fast, and we're back online - fast and resilient as fuck. At least when it comes to handling DNS queries.

  41. #dnsdist just showed up in the #homelab. It load balances DNS servers and some other things. I'm messing with it and so far so good, but if you wanted to LB your dns servers it seems like a pretty dope project from #powerdns

    #selfhosted
    #selfhosting

  42. #dnsdist wil get DoQ support from the next release, meaning so will UncensoredDNS. Looking forward to it!

  43. @pemensik The reason why you uninstall it as the first thing on a fresh install, then you install either Powerdns's #recursor (+ #dnsdist ) or #Unbound and then you are #RFC compliant

  44. Wow, la conso mémoire de #dnsdist 1.8.0, c'est quelque chose. Sur la 1.7.x on était stable à env. 60 Mo, et là on est déjà à 114 Mo à trafic constant (env. 1,3 req/s qui arrivent)

    Je ne vois rien dans le changelog qui indique un possible changement de comportement (ou un changement de la métrique).

    J'ai de la marge sur la machine (usage de la RAM : 33%), mais je vais continuer à surveiller