docs
Edgecast Console

Serving Traffic through Our Network

Serve traffic through Edgecast by updating the DNS records for each hostname registered with Edgecast to point to our service.
Before serving traffic through our network, please review our Acceptable Use Policy. Learn more.

Checklist

Before updating your DNS records, verify that you have performed the following tasks:
TaskDescription
Created hostname(s) through the Edgecast Console or CDN-as-code.Defined each hostname through which your site’s content will be delivered.
Created origin configuration(s) through the Edgecast Console or CDN-as-code.Created one or more origin configuration(s) that defines how Edgecast communicates with your web server(s).

If you are using CDN-as-code and do not plan on retrieving data from your web server(s), then you do not need to create an origin configuration.
Configured your firewall.If you have defined one or more origin configuration(s), then you must configure your firewall to accept traffic from our network.
Enabled HTTPS support.Enabled HTTPS support for each registered hostname by either autogenerating or uploading a TLS certificate to our network.
Deployed your configuration.Deployed the above configurations to Edgecast.
QATested your site by loading it through a deployment-specific link.

Firewall - Allowing Edgecast IP Addresses

As clients request your site, Edgecast sends traffic through our network to the servers associated with your origin configuration(s). You must configure your firewall to allow this traffic to ensure that these requests are not blocked.
IP blocks may vary by organization.
If you plan on using the Edgecast CLI to deploy to a development or CI/CD environment, then you will also need to allow traffic from the domain to which it connects. This domain is listed within the Allowlisting window.
To view our network’s IP blocks
  1. Load the Origins page.
    1. From the Edgecast Console, select the desired private space or organization.
    2. Select the desired property.
    3. From the left-hand pane, select the desired environment from under the Environments section.
    4. From the left-hand pane, select Origins.
  2. From the information bar at the top of the page, click instructions.
    Firewall instructions
    The Allowlisting window will display a list of IPv4 and IPv6 blocks for standard traffic, Perimeter 81 for network security, AWS NAT gateway for the Edgecast cloud, and the domain to which the Edgecast CLI connects when deploying to a development or CI/CD environment.
    We strongly recommend that you allow traffic for all IP blocks and the domain listed on the Allowlisting window.

DNS

Once you are ready to serve traffic through Edgecast, you will need to configure DNS for each hostname. DNS configuration consists of defining a CNAME record that points your hostname to our service.
If your hostname is at the zone apex (e.g., example.com), then you will need a DNS service provider that supports defining a CNAME record at the zone apex. Learn how to set this up through Route.
From your DNS service provider, point your hostname(s) to a service domain that is either specific to your property’s environment or space.
Sample Service Domain: 2af36ae6-2146-4b73-a5e7-f86c4a93bc06.edgio.link

Environment-Specific Service Domain

Edgecast assigns a different service domain to each of your environments. You may point any hostname defined within a specific environment to its service domain.
To view the service domain assigned to a specific environment
  1. Load the Hostnames page.
    1. From the Edgecast Console, select the desired private space or organization.
    2. Select the desired property.
    3. From the left-hand pane, select the desired environment from under the Environments section.
    4. From the left-hand pane, select Hostnames.
  2. From the DNS column, click Actions needed.
    DNS - Actions needed
    This button is disabled if you have not deployed a new hostname yet or when setting up a hostname for a new root domain and you have not already activated a TLS certificate.
    For example, this button will be enabled for images.example.com if you have already deployed this change and you currently serve traffic through cdn.example.com. However, it will be disabled for cdn.example.org until you set up a TLS certificate for it.
  3. From the DNS Configuration pane, click
    Copy to clipboard icon
    to copy this domain.

Space-Specific Service Domain

Edgecast assigns a different service domain to:
  • Your private space.
  • Each organization to which you belong.
You may point any hostname defined within a private space or organization to its service domain.
To view the service domain
  1. Load the space’s Settings page.
    1. From the Edgecast Console, select the desired private space or organization.
    2. Click Settings.
  2. From the Organization DNS Configuration section, click
    Copy to clipboard icon
    to copy this domain.

Serving Traffic at the Zone Apex

Edgecast requires a CNAME record to serve your site’s traffic. Some DNS service providers do not support defining a CNAME record for the zone apex (e.g., example.com). In order to serve traffic for a zone apex, you will need to use a DNS service provider that supports CNAME records at the zone apex. Instructions on how to use Edgecast Route to set up a CNAME record at the zone apex is provided below.
The zone apex is the point in your zone that contains your SOA and NS records.
To add a CNAME record at the zone apex through Route
Edgecast Route requires activation. Additionally, you will need to delegate your primary zone to Edgecast Route. Contact your account manager or our sales department at 1 (866) 200 - 5463 to upgrade your account.
  1. Navigate to the Route (DNS) page.
  2. Click on the desired zone.
  3. Click Add Record.
  4. In the Type option, select CNAME.
  5. Create the following CNAME record:
    • Name: @
    • TTL: Set the TTL to the length of time (in seconds) that a DNS server should cache the record.
    • Value: Set this value to a space-specific service domain.
  6. Click Add.
  7. Click Submit Group to save the zone.

DNS Verification

Once you have updated your DNS configuration, run the following command to verify it:
dig <HOSTNAME>
Example: The following example demonstrates how to verify the DNS configuration for cdn.example.com:
Bash
1> dig cdn.example.com
2

3# Result
4cdn.example.com.   599    IN    CNAME    2af36ae6-2146-4b73-a5e7-f86c4a93bc06.edgio.link

Acceptable Use

Unless otherwise agreed in writing by Edgecast, Application Services are solely intended for rendering the functional attributes of a website e.g., HTML, JavaScript, CSS, and APIs (subject to the restrictions herein), and are not to be used for video or audio streaming or for delivery of other large file types, including but not limited to images and software downloads or updates (“Unauthorized Traffic”) which require the purchase of other Edgecast Services. Edgecast may monitor, terminate, suspend, and/or restrict the use of the Application Services when it determines in its sole discretion that Unauthorized Traffic is being delivered.
View our: