Earlier quoted context omitted.
It's night. Somebody has to fill a form to approve night work first.
And send it by post for approval, which will take 5-30 business days.
Dont be ridiculous, thats what FAX is for.
DNSSEC disruption affecting .de domains – Resolved
131–140 of 440 posts
Re: DNSSEC disruption affecting .de domains – Resolved
#132Apparently the DENIC team was on a party this evening! Party hard, but not too hard.
https://bsky.app/profile/denic.de/post/3ml4r2lvcjg2h
Re: DNSSEC disruption affecting .de domains – Resolved
#133Earlier quoted context omitted.
I love how I work with IT for 20 years and don't understand a single acronym here other than DNSSEC
To be fair, advanced real world knowledge of public/private key PKIs (x.509 or other), things like root CAs, are a fairly esoteric and very specialized field of study. There's people whose regular day jobs are nothing but doing stuff with PKI infrastructure and their depth of knowledge on many other non-PKI subjects is probably surface level only.
I know quite a bit about PKI and X.509, and I can tell you that much: the overlap with how DNSSEC works is limited.
Re: DNSSEC disruption affecting .de domains – Resolved
#134Denic will be added to the "Major DNSSEC Outages and Validation Failures" list:
https://ianix.com/pub/dnssec-outages.html
Re: DNSSEC disruption affecting .de domains – Resolved
#135Apparently the DENIC team was on a party this evening! Party hard, but not too hard. https://bsky.app/profile/denic.de/post/3ml4r2lvcjg2h
A real party killer if I have ever seen one.
Re: DNSSEC disruption affecting .de domains – Resolved
#136Earlier quoted context omitted.
Luckily it's not Sunday. Everyone would be out in the country hiking.
Or reading the latest prints about tax filings and how to conduct a compliance audit with pen and paper.
Or sweeping.
Re: DNSSEC disruption affecting .de domains – Resolved
#137Re: DNSSEC disruption affecting .de domains – Resolved
#138Earlier quoted context omitted.
I love how I work with IT for 20 years and don't understand a single acronym here other than DNSSEC
To be fair, advanced real world knowledge of public/private key PKIs (x.509 or other), things like root CAs, are a fairly esoteric and very specialized field of study. There's people whose regular day jobs are nothing but doing stuff with PKI infrastructure and their depth of knowledge on many other non-PKI subjects is probably surface level only.
Is that actually true, though? Even though it's not really my job, I find myself debugging certificates and keys at least once a month, and that's after automating as much as possible with certbot and cloud certificates. PKI always seems to demand attention.
Re: DNSSEC disruption affecting .de domains – Resolved
#139I just spent the better half of an hour to debug unbound and the pihole because I thought it's a me problem... Good news though, if you add domain-insecure: "de" to your unbound config everything works fine
Just before the outage happened I updated multiple client servers. That was a very stressfull hour trying to figure out why nothing works.
Re: DNSSEC disruption affecting .de domains – Resolved
#140Apparently the DENIC team was on a party this evening! Party hard, but not too hard. https://bsky.app/profile/denic.de/post/3ml4r2lvcjg2h
Interesting "bus problem" to have in a scenario where everyone who is qualified, experienced and trusted enough to commit lives changes (or perform a revert, undo results of a botched maintenance, etc) in an emergency situation is not completely sober.