People don't believe me when I say how much DNS matters. So I wrote a song about it. https://soundcloud.com/ryan-flowers-916961339/dns-to-the-tun...
This made my day, thanks!
And this, mine! Thanks!
Akamai Edge DNS was down
191–200 of 229 posts
Re: Akamai Edge DNS was down
#192Re: Akamai Edge DNS was down
#193Earlier quoted context omitted.
Amazing that down detector manages to stay up during these kinds of outages. Noticed it has been a little slow but they really have done a good job keeping it up even though large portions of the internet is down right now.
Who detects if Down Detector is down? Is there a isdowndetectordown.com site?
Sounds like when Fuckedcompany put itself on Fuckedcompany.
Re: Akamai Edge DNS was down
#194[deleted]
Re: Akamai Edge DNS was down
#195Earlier quoted context omitted.
dns, DNS, dns, dns. The start of every process, dns. Love this.
Thank you! I'm glad that landed where I wanted it to. It was a lot of fun to put together. I keep threatening to make a video. I need a collection of DNS memes so that I can just sideshow them.
Haha please do, a video would be great. Your song reminded me of the song: "Find the Longest Path" which you may get a kick out of:
Re: Akamai Edge DNS was down
#196Earlier quoted context omitted.
What's frustrating is that DNS is returning an address, instead of just failing, and so macos is caching that value (though it might be cloudflare doing that).
Wildcard DNS should be a prosecutable crime, punishable by no less than 20 years of hard labor. (Edit: Probably should have made it clear that this was a joke)
Presumably you're referring to the practice of answering queries for nonexistent records with an A record belonging to an advertisement page? (instead of doing the right thing answering NXDOMAIN, presuming no records of another type also exist for the queried name.)
dnsmasq has a really useful feature for dealing with this: --bogus-nxdomain
Re: Akamai Edge DNS was down
#197Strange thing about the duration of this outage... From logs I have, it seems to have lasted exactly one hour, from 15:38 to 16:38. Their Twitter account also said "disruption lasted up to an hour", though they incorrectly said it started at 15:46 (did it take 8 minutes for their monitoring to notice?).
That makes me think that whatever the fix was, it had to wait for some one-hour cache to expire before it took effect. I'm very interested to find out what the cache issue was, more so than what the original bug was.
Re: Akamai Edge DNS was down
#198I ran DNS servers, among other things, in the late 90s with better uptime than these "multi-DC/AZ/geo redundant" services everyone uses these days.
Re: Akamai Edge DNS was down
#199People don't believe me when I say how much DNS matters. So I wrote a song about it. https://soundcloud.com/ryan-flowers-916961339/dns-to-the-tun...
Sounds amazing! Do you maybe have a direct link? Soundcloud doesn't want us privacy-conscious users browsing their website :(
Re: Akamai Edge DNS was down
#200Earlier quoted context omitted.
So here's a weird question: Supposing companies multi-home for DNS, or whatever other essential service, via multiple service providers. Whatever multi-home means, why can't there just be one service provider that does that ? And are we sure that these service providers aren't already doing that as best we might hope for? (For instance, Amazon already has multiple zones, etc.) I suppose the one thing this can't prote…
> Whatever multi-home means, why can't there just be one service provider that does that? Many of these outages are due to pushing broken artifacts or configuration to production. A single provider can pretty easily offer geographic or network topological redundancy, but administrative and/or technological independence is pretty hard to achieve in a single company.
I mean, I guess what I'm saying is that in theory a single provider could purposely keep two different departments that manage their own artifacts independently.