AnsweredAssumed Answered

Service Unavailable - DNS failure

Question asked by Antoine Guy on Feb 19, 2016
Latest reply on Feb 22, 2016 by Desmond Tam



We changed our origin for a DSA property recently and we're seeing a lot of errors like this, apparently akamai fails to resolve our origin hostname.


Our new origin is on AWS, and the domain of our origin is on Route53 which is supposed to be very reliable.

The only thing I can see is that our origin entry has a TTL of 60s, but there is nothing we can do about it, it's specific to AWS ELB.


Is there a specific setting to avoid this issue ? and how to avoid the ugly AWS Error page, and serve a custom page in case it still happens.