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...
dns, DNS, dns, dns. The start of every process, dns.
Love this.
Akamai Edge DNS was down
181–190 of 229 posts
Re: Akamai Edge DNS was down
#182Earlier quoted context omitted.
Same path. It'll be very hard to move away from 1Password. App experience, sync, security features like key in addition to master password, family organizer-based recovery of an account, these are a few things that stand out.
I prefer the browser addon for bitwarden over 1Password. Try editing a site in 1Password. It forces you to log into the full sir, whereas bitwarden can do almost everything right there in the addon.
This is also possible with the 1Password X extension, however there's a lot of feature segmentation and unclear messaging between the Desktop app-based version and 1Password X so I don't blame you for using the old one.
Re: Akamai Edge DNS was down
#183You can see this on a lot of sites right now. You get the Akamai style error with something like: Reference: #11.453a2f17.1393u44848484.3aee33433 At the bottom of a very bland looking error page.
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).
To empty the macOS DNS cache:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Re: Akamai Edge DNS was down
#184People 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...
Thank you!! lol
Re: Akamai Edge DNS was down
#185People 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...
> People don't believe me when I say how much DNS matters.
That's weird to me. I have been working in sysadmin/DevOps for over a decade, but it did not take me very long to learn that DNS outages cause massive problems.
Re: Akamai Edge DNS was down
#186Earlier 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 believe EasyDNS can automatically push DNS settings to Route53 to host DNS in AWS. Doesn't protect you from fat-fingering a change, but you should be resilient to either EasyDNS or Route53 going down.
Re: Akamai Edge DNS was down
#187Absolutely amazing how many billion $+ companies are single homed for DNS. I wonder how much they spend on multi-AZ redundant architectures...
Using multiple providers for mostly static DNS is easy, pick one as primary and AXFR to the other and notifications and whatever. Or it's not too hard to keep a zone file in source control and sync it to the providers. Using multiple providers for fancy DNS, like only providing IPs that pass healthchecks or geotargetting users to datacenters gets pretty hard, because the different providers have similar capabilities,…
So much this. Keeping feature by feature parity is the tricky part.
Re: Akamai Edge DNS was down
#188Earlier quoted context omitted.
Their APIs are (or, were, last I suffered their use a few years ago) also terrible, eg blanket policy of refusing to cache any resource in the presence of "Vary" header, regardless of its value, and failure to honor standard HTTP headers... thankfully there are many other options for CDN, which are SO MUCH BETTER.
Surely it depends what you vary on? Content-Encoding should be well supported, User-Agent less so and for very good reasons (there's too much variation in UA strings)
It wasn't that simple — IIRC, for a while Vary meant “don't cache anything, ever, under any circumstances” unless you made some custom configuration changes. Over time they _added_ support for just “Vary: Accept-Encoding” (IIRC less than a decade ago) and that was fragile. They improved that over time but it was painful for a number of years because there were various failure modes which meant things wouldn't be cached, or (IIRC) compression would be disabled for certain URLs sporadically if the first request for the option did not request transfer compression.
Re: Akamai Edge DNS was down
#189People 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...
> People don't believe me when I say how much DNS matters. That's weird to me. I have been working in sysadmin/DevOps for over a decade, but it did not take me very long to learn that DNS outages cause massive problems.
Right, but everybody has to learn that at some point. And I happen to be somebody who teaches such things. The importance of DNS is hard to overstate, but I go to great lengths to do exactly that, to make a point ;)
Re: Akamai Edge DNS was down
#190People 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...
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.