Use case 1: HTTP-only, using a partner-owned DNS name

This use case involves usage of cloud partner-managed DNS hostnames to serve content to end-clients via the Akamai CDN.

For example, {sub-customer-prefix}.cloudplatform.net

Value Example
Partner Domain 
cloudplatform.net
End-Client-facing Domain CNAME 
{sub-customer-prefix}.cloudplatform.net {TTL} IN CNAME
cloudplatform-net.mdc.akamaized.net
Example End-Client-facing Domains 
static.sub-customer.com.cloudplatform.net
2358c713-a9dad7fd-f838fd35-8c85b331.cloudplatform.net
Complete End-Client CNAME Chain 
static.sub-customer.com.cloudplatform.net. {TTL} IN CNAME
cloudplatform-net.mdc.akamaized.net.

cloudplatform-net.mdc.akamaized.net. 21600 IN CNAME
a1234.dscw14.akamai.net.

a1234.dscw14.akamai.net. 20 IN A 72.246.199.74

This use case is based on our Multi-Domain Configura-tion (MDC) solution via an "Instant Config Hostname." When using the example domain cloudplatform.net in this example, a hypothetical CNAME chain observed by End-Clients might be as shown above. As the Cloud Partner, you can choose the “{TTL}” for the CNAME to the mdc.akamaized.net hostname. However, anything less than five (5) minutes is considered too low.

Note: Default TTLs are provided in the example for the remainder of the CNAME chain.

In addition, the Cloud Partner must provide a separate origin DNS hostname or IP address for each Sub-Customer domain. There are two possible mechanisms for deriving the origin DNS name:

  1. RECOMMENDED: As the Cloud Partner, you can use the ACE API to create a content delivery policy with an “origin” behavior for each subcustomer. This delivery policy may use the IP address of the origin that would normally have been handed out when the delivery policy is served without Akamai; that is, the A record that would normally be returned by the your DNS for the subcustomer hostname.

    However, we recommend that you use a separate DNS hostname in the “origin” behavior to allow migration of subcustomer origin IPs between your cloud partner data centers without having to update each subcustomer delivery policy.

  2. You can configure a static value as a prefix in front of the End-Client-facing hostname. For example, the base configuration can apply a default delivery policy that concatenates a static prefix, for example “origin-” and the End-Client domain. In such cases, the “origin” behavior is not required.

Following the example above, as the Cloud Partner, you need to provision a DNS entry for origin-static.sub-customer.com.cloudplatform.net. This might look like the following:

origin-static.sub-customer.com.cloudplatform.net. {TTL} IN A 77.76.75.74
As the Cloud Partner, you can also optionally do the following:
  • Set the TTL. Set it to a minimum of one (1) minute, with five (5) minutes (or more) being the recommended value.
  • Use additional intermediate CNAMEs or use DNS-based load balancing. For example, you could use Akamai’s Global Traffic Management solution.