Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Akamai Edge DNS was down

edgedns.status.akamai.com

Post reply on HN
Print view View original

161–170 of 229 posts

Re: Akamai Edge DNS was down

#161

Post by lxgr »

orblivion wrote: post #129
foobarbazetc wrote: post #114

Absolutely amazing how many billion $+ companies are single homed for DNS. I wonder how much they spend on multi-AZ redundant architectures...

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.

Re: Akamai Edge DNS was down

#162

Post by paradite »

sakisv wrote: post #49
davidjgraph wrote: post #15

Serious question, has anyone properly solved the issue of DNS as a single point of failure?

Depending on what point you draw the line of "single point of failure" you could use multiple providers for your dns. GOV.UK for example uses both aws and gcp for DNS

Last time I tried setting NS to both cloudflare and digital ocean in my domain registry, cloudflare sent me an email saying the configuration is invalid and asked me to revert. Am I doing something wrong?

Re: Akamai Edge DNS was down

#163

Post by youngtaff »

chrisweekly wrote: post #135
halfmatthalfcat wrote: post #104

Earlier quoted context omitted.

You could argue Akamai is the blandest of the CDN bunch; their UIs are atrocious.

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)

Re: Akamai Edge DNS was down

#164

Post by decrypt »

arnado wrote: post #153
chewmieser wrote: post #134

Earlier quoted context omitted.

My favorite feature personally is the built-in 2FA support. Click and it logs into your account and copies the 2fa code to clipboard so just paste on next screen. Multiple vaults too is nice but I know others have ways to limit exposure of passwords in similar manners.

Bitwarden offers this as well, but I don't really understand why you would want it. If someone compromises your password manager, 2FA is now worthless. Or am I misunderstanding how it works?

Your understanding is correct. 1Password requires a key in addition to the master password. And finally, 1Password can have 2FA for itself, which is stored on my Authy. These are reasons why I am comfortable storing my 2FA codes on it.

Bitwarden has 2FA support too, but does not have the unique key feature that 1Password has.

Re: Akamai Edge DNS was down

#165

Post by cube00 »

mindcrime wrote: post #50
cpgeier wrote: post #24

Earlier 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?

"I dunno. Coast Guard?"

Re: Akamai Edge DNS was down

#166

Post by zxcvbn4038 »

chrisweekly wrote: post #135
halfmatthalfcat wrote: post #104

Earlier quoted context omitted.

You could argue Akamai is the blandest of the CDN bunch; their UIs are atrocious.

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.

Akamai is their own worst enemy most of the time. Their prices are the highest, they trail on features, their documentation opaque, it takes an hour to propagate changes, etc. Only a few years ago you could only use SSL if you purchased their ridiculously expensive pci-dss plan - I thought they would defend that to their grave.

Better alternatives are Cloudflare, Fastly, AWS CloudFront.

Google Cloud CDN always seems to have very good latency but a very bare bones feature set and no edge compute I can identify. Support is always a huge red mark for Google anything.

Re: Akamai Edge DNS was down

#167

Post by tjpnz »

lxgr wrote: post #155
tjpnz wrote: post #58

Just got booted out of Netflix on the PS4 because the console could no longer connect to Sony's license server. Netflix was working just fine by the way.

Was the app installed/running using a secondary PSN account by any chance? This shouldn't be happening on a primary account/console pair.

It should be my primary although I've often seen it revert back after setting it. I did try setting it as my primary again but you know.

Re: Akamai Edge DNS was down

#168

Post by judge2020 »

youngtaff wrote: post #163
chrisweekly wrote: post #135

Earlier 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)

https://learn.akamai.com/en-us/webhelp/adaptive-media-delive...

> AMD automatically strips these headers out of requests to support caching for faster delivery.

> I need the Vary HTTP headers: AMD can cache the associated object if the Vary HTTP header contains only "Accept-Encoding" and "Gzip" is present in the Content-Encoding header

(AMD in this case standing for Akamai Media Delivery)

Re: Akamai Edge DNS was down

#169

Post by remram »

slim wrote: post #143
sebmellen wrote: post #91

Earlier quoted context omitted.

Is this a serious argument for long TTLs? Always wondered why they exist… How interesting.

Yes it is. The longer the TTL the longer you stay independent from third parties. It's what makes the internet stable.

Long TTL makes you independent from DNS third parties, in that your name is still know by clients if DNS is down.

Short TTL makes you independent from hosting third parties, in that you can quickly change which hosting provider your domain name points to.

You can't win this one by only changing your TTL. The best solution is to use short TTLs and multiple nameservers on different providers.

Post reply on HN