[ryanlol]

Which would imply that their backend was compromised, not just DNS.

[zkhalique]

The CDN could have simply refreshed its DNS cache couldn't it? That would mean it loaded the files from somewhere else.

[ryanlol]

Unless there was something horribly wrong with their setup, akamai would have prevented that from happening.

[Tiksi]

I'm not sure how they are supposed to prevent this. If you have access to the dns, you can change the record for the origin server that the cdn pulls from. Nothing "horribly wrong" with that.

[ryanlol]

Akamai makes you to set your own DNS server for it to pull records from, the domain getting hijacked should not have any effect on what that DNS server is returning.

[Tiksi]

I may be missing something, but this:

>It added that its domain name system was compromised.

sounds like their DNS server was compromised.

Also, I've never worked with Akamai, but every cdn I have worked with just follows the ns records and resolves against that, which could be changed with access to the domain/registrar. Does Akamai not do that?

[ryanlol]

Their domains DNS servers were switched to cloudflare, I'd imagine that's the DNS compromise they're referring to.

Not _their_ DNS servers getting compromised.