2025-10-13 13:13:34
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…
I write up some of my advice on surviving DNS outages as it seems timely #AWS #DNS https://adrianco.medium.com…
.gov #DNS notes
On 2025-01-19 there were two "biden" names, bidenlibrary and bidenwhitehouse. Not so unusual. Associated names for Obama and Trump were also there and remain still. These are exec branch names but the agency responsible for them is the National Archives and Records Administration (NARA).
As of today, there are four additional "trump" labels in the …
I had to migrate my #DNS today, and Hurricane Electric is such a pleasurable return to 90s.
Website obviously designed by a backend engineer. Has only tables and buttons. Buttons work and do things. It's fast. It support features fancy sites do not support. On top of it, free.
12/10
There is an ActivityPub proposal that involves the #DNS.
I have only just discovered it and have not considered it deeply so I am reluctant to make any grand statements. It is not obvious to me why this is useful or better than alternative approaches. It appears to involve the use of TXT RRs, any new de facto use of which makes me skeptical.
Why am I smelling #DNS again :mortysmile:
#DNS trivia, especially for those have ever used the "It was DNS" meme. What is wrong with this (real) dig response and what is the likely cause? AI probably won't help you.
dig @1.1.1.1 foobar.gov norecurse nocmd noquestion noauthority nostats
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1808
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, A…
Oh my, @… is fast ! Faster than Cloudflare or Google. With average response time of 12 ms.
Where cloudflare was 22 ms
And Google shited with 232 ms 😆
#dns
This is not the first time for #Microsoft #DNS-related problems. As I recall, the first one I remember from 2001 had something to do with their authoritative name servers residing on the same IP4 /24 that had an access or availability problem.
It was a rookie mistake even then, and they were …
Have you noticed that when the blame #DNS meme starts flying the root is perfectly operational, there is rarely a mention of the big registry operators, BIND, Unbound, Knot, and PowerDNS are absent the conversation, and many who can craft a reasonable dig query are getting responses from local and public resolvers to debug?
Even with all the misconfiguration, added complexity on top of it, a…