Tootfinder

« Cloudflare 1.1.1.1 Incident on July 14, 2025 »
Perhaps it’s time to return to DNS’s original distributed design.
#dns #distributed #cloudflare

Cloudflare 1.1.1.1 Incident on July 14, 2025
On July 14th, 2025, Cloudflare made a change to our service topologies that caused an outage for 1.1.1.1 on the edge, resulting in downtime for 62 minutes for customers using the 1.1.1.1 public DNS Resolver as well as intermittent degradation of service for Gateway DNS. We’re deeply sorry for this outage. This outage was the result of an internal configuration error and not the result of an attack or a BGP hijack. In this blog post, we’re going to talk about what the failure was, why it o…

This is on the obscure side, but I wouldn't be surprised if some people get bit by this...
If you're using the Perl Net::DNS library for, say a custom #DNS server daemon, once you upgrade to 1.42 or later (Debian 12 had 1.36, Debian 13 has 1.50), your server is probably going to break or mysteriously stop working.
main_loop(), which effectively gave you a listener until the prog…

TIL about DNS.
#til #sysadmin #dns

Considering the issue of the state of #DNS resolution on #Linux again, I don't think anyone got it quite right so far:
* Going through NSS's host database is pluggable, and the #mDNS plugin can convey zone i…

TIL that all those "network." "broadcast.", and "unknown.severcentral.net." #DNS PTR names are not just a default, but Summit (formerly Deft, formerly ServerCentral) cannot remove an individual PTR RR. You can set it a non-null value however.
And yes... if you want to know how SCnet subnets, look for "network." and "broadcast." PTR names of …

Ähm … hat Google grad Stress mit der Nasa oder so?
#google #nasa #dns

The overlap of people trying to self-host authoritative DNS with nsd and integrate it with kubernetes via external-dns and cert-manager is extremely low.
#selfhosted #kubernetes #dns