4 ms·
Hmm, I figured it was just the records being pointed to cloudflare, since everything I could find makes it sound like that, but you may be correct that the name
by Tiksi 12y ago
Hmm, I figured it was just the records being pointed to cloudflare, since everything I could find makes it sound like that, but you may be correct that the nameservers were changed, as cloudflare's nameservers look like they have a record for the domain, but are returning different records: http://paste.click/s/qKkejf http://paste.click/s/qKkejf [0]
Which appears to be down now anyways: http://paste.click/s/UlxsWA http://paste.click/s/UlxsWA [1]
However I suspect cloudflare's nameservers might just return A records pointing to cloudflare if they don't exist, I'm not sure.
Though that still doesn't answer the second part. Would Akamai not use the authoritative nameservers to resolve the origin? Cdn providers I've worked with (Level3, edgecast, Highwinds, and others) just resolve based on the authoritative nameservers, and I'm genuinely curious if Akamai doesn't do that.
Edit: forgot that my keybinding throws the js/syntax highlighted url into my clipboard, which is pointless for this, here are the plaintext links to the same thing:
[0] http://paste.click/qKkejf http://paste.click/qKkejf
[1] http://paste.click/UlxsWA http://paste.click/UlxsWA
- ryanlol 12y agoYou specify the nameserver for akamai to pull the zone from on the config site. Their "CDN" is quite a bit smarter than what L3 & co. run.