Public posts with this hashtag.
#France decided against the neutrality of #DNS and against #Quad9 on a court case that supposedly addressed #copyright infringement.
One can just hope that such rulings will not propagate to more national decisions, and interferes with neutral operation of critical internet infrastructure...
Here is the blog post of Quad9
Quad9Quad9 | A public and free DNS service for a better security and privacyA public and free DNS service for a better security and privacy
#DNS #revolving #quad9 @quad9dns
That's a pity, I'm disapointed
The French courts yesterday handed down an unfavorable ruling against Quad9 in a major case that undermines the transparency and stability of the internet. As a result, Quad9 will no longer be able to offer its free cyberprotection service to users located in France effective November 24.
Quad9Quad9 | A public and free DNS service for a better security and privacyA public and free DNS service for a better security and privacy
Let’s not forget .php could be a top level domain.
Be sure to let ICANN know on the 17th how much a file name ending in .php would improve your life, much like today.
https://newgtldprogram-aps.icann.org/applications/KKWT2621T-T46596-R/summary
ISC fixes four BIND 9 vulnerabilities, including CVE-2026-94300 memory corruption and denial of service bugs. Upgrade to BIND 9.20.30 or 9.21.27.
#BIND9 #ISC #DNS #CVE202694300 #CVE202619630 #CVE202697313 #DenialOfService #CyberSecurity
PowerDNS Recursor 5.3.13 Released
https://blog.powerdns.com/2026/10/21/powerdns-recursor-5.3.13-released
blog.powerdns.comPowerDNS Recursor 5.3.13 ReleasedRelease of PowerDNS Recursor 5.3.13
PowerDNS Security Advisory 2026-13 for PowerDNS Authoritative Server
(aka PowerDNS Authoritative Server 4.9.18, 5.0.8 and 5.1.5 Released)
blog.powerdns.comPowerDNS Security Advisory 2026-13 for PowerDNS Authoritative ServerPowerDNS Security Advisory 2026-03 for PowerDNS Authoritative Server
PowerDNS Security Advisory 2026-12 for PowerDNS Recursor
(aka PowerDNS Recursor 5.3.12 and 5.4.8 Released)
https://blog.powerdns.com/2026/10/21/powerdns-security-advisory-2026-12-for-powerdns-recursor
blog.powerdns.comPowerDNS Security Advisory 2026-12 for PowerDNS RecursorPowerDNS Security Advisories 2026-12 for PowerDNS Recursor: Multiple Issues
Wczoraj w nocy zrobiłem solidny upgrade swojego prywatnego resolvera DNS (Cloudflare Workers). Co dokładnie się zmieniło? 🛠️
Przede wszystkim zrezygnowałem z polegania wyłącznie na plikach z GitHuba. Wdrożyłem trójstopniową architekturę odpornościową:
1. Główna baza z 461 tysiącami domen trafiła do Cloudflare KV, co daje błyskawiczny start.
2. GitHub został bezpiecznikiem – jeśli KV zawiedzie, Worker po cichu pobiera dane stamtąd.
3. Ostateczność (Fail-Open): jeśli oba źródła padną, Worker nie zostawia Cię bez ochrony. Bezpiecznie przekazuje zapytania prosto do zaufanego resolvera Cloudflare (1.1.1.1), więc internet działa dalej, a Ty nie tracisz łączności.
Dodatkowo zoptymalizowałem kod, by nie przekraczał limitów procesora przy zimnych startach. Zero kosztów, maksymalna stabilność i pełna kontrola. Czasem warto posiedzieć w nocy, żeby doszlifować swój cyfrowy ogródek. 🛡️🚀
Well this is an interesting problem. I'm seeing 90x traffic on my DNS requests, but not translating to traffic on the site.
Unfortunately it's causing an increase in my bill due to logging.
This increase has happened over about a two week period.
What should I be looking at?
It's distributed traffic too, not a single IP.
