Finally, complete these steps before throwing the switch

To go live and serve traffic through the Akamai production network, you'll need to do a couple of things.

How to

  1. (optional) Change your DNS Time to Live (TTL).
    Two DNS TTL settings affect the speed of the go-live process. The first setting is on your existing web server’s DNS A records. The DNS TTL set on those records will affect how long it takes for all users to start using Akamai after you go live.

    The second setting is the DNS TTL on your CNAME record (addressed in Step 3). This TTL affects how long it takes your users to revert directly to your origin if you need to turn Akamai off.

    Changing your DNS TTL is up to you, but it’s best to start low, say 10 minutes (600 seconds). That way you won’t have to wait so long to make sure any modifications work correctly. You can increase it later if you choose.

  2. Review how you use your logs and IP addresses.
    If you’re using your origin web server’s logs or relying on incoming IP addresses for analytics or geo-targeting purposes, you’ll need to make some changes before going live with Akamai.
    Web server logs
    Once you’re using Akamai, requests for cached content won’t always show up on your web server origin logs. If you’re relying on your origin server logs for analytics or debugging, you’ll want to turn on Log Delivery Service (LDS). When using LDS, Akamai sends you the logs from the Akamai edge servers so you won’t miss important data.

    Check the Log Delivery Service User Guide on Control Center to learn more about the server logs you’re using. The object ID should match your primary domain.

    Client IP Addresses
    After you go live, Akamai servers operate between your web server and your end user, and the client IP addresses connecting to your origin web server will be Akamai IP addresses instead of your end user IP addresses. Note that Akamai makes sure the end user IP information is still available to you. Every request that travels from an Akamai server to your origin will have a new HTTP header added to it called True-Client-IP. You can see the end user IP address in that header.
  3. Update your DNS record and add a CNAME as follows:
    A DNS CNAME (or canonical name) record specifies that a domain is an alias for another domain. Most DNS providers offer detailed instructions on the process of creating CNAME entries.
    1. Log into your DNS provider account for the domains you’re onboarding to Akamai.
    2. Find the page to update/edit your domain's DNS records. This might be called something like, DNS Management or Name Server Management.
    3. Locate the entry for your domain. If there is an A record currently, change the record type to a CNAME record. If there is currently a CNAME record, change the target to the Akamai provided value.
    4. Save the changes and wait for them to take effect.
      Note: The time it takes for the change to take effect is dependent on the prior TTL applied to that DNS record, typically measured in seconds (for example, 84600 = 24 hours). Refer to changing your TTL for lowering your DNS TTL.
    CNAME record
    Host/Name/Alias Time to Live (TTL) Record Type Value/Answer/Destination
    www 600 CNAME

    If you lower your DNS TTL to 600 (10 minutes) before preparing to go live, that is how long it should take for all name servers to pick up the changes to your site.