Seattle, Redmond. WA. Upon another recent outage, DNS was quoted saying… “see! It’s not ALWAYS DNS!!” The event started in the hosted cloud infrastructure with an unfortunate impact causing identity outages for thousands of customers. The twitterverse was afire with DNS prognosticators for several hours. The early information proved incorrect, with an official statement from AWS noting that a certificate renewal was to blame.

In a follow-up interview, DNS is quoted, “Look… it’s SOMETIMES DNS, or even MOST of the time DNS, but frankly it’s not always DNS. This recent disaster is clearly on those certificate services bozos”. The tech community followed up with a ho-hum tone, which although the issue was initially tagged for the wrong cause, the historical issues were still the rule.

In a interview with Tech Hub Satire, Jennifer Xi indicated, “even though this time DNS is off the hook, the body of evidence still is overwhelming that ‘it’s always DNS’ is still a relevant meme and even cause. I bet DNS is still culpable in there somewhere”.

In another interview, Danny Boy questioned, “FAKE NEWS… I bet it is just the DNS folks showing shade that is causing the issue to be blamed on certificate services”.