#dnsdist — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #dnsdist, aggregated by home.social.
-
Today's open source bug report day I guess
https://github.com/PowerDNS/pdns/issues/16712
#PowerDNS #dnsdist -
Today's open source bug report day I guess
https://github.com/PowerDNS/pdns/issues/16712
#PowerDNS #dnsdist -
Today's open source bug report day I guess
https://github.com/PowerDNS/pdns/issues/16712
#PowerDNS #dnsdist -
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.
-
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.
-
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.
-
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.
-
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.
-
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 exchangeCVE-2025-30194
https://www.dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2025-02.html
-
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 exchangeCVE-2025-30194
https://www.dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2025-02.html
-
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 exchangeCVE-2025-30194
https://www.dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2025-02.html
-
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 exchangeCVE-2025-30194
https://www.dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2025-02.html
-
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 exchangeCVE-2025-30194
https://www.dnsdist.org/security-advisories/powerdns-advisory-for-dnsdist-2025-02.html
-
-
-
-
-
-
@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)? -
@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)? -
@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)? -
@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)? -
@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)? -
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 :/
-
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 :/
-
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 :/
-
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 :/
-
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 :/
