Create a CDN resource for the entire site

What is the CDN resource for the entire site used for?

A CDN resource of this type is a feature that allows you to accelerate and protect the entire site with Gcore CDN and Managed DNS services. This CDN resource helps accelerate both kinds of content delivery: static and dynamic. If you only need to deliver static assets, use a separate CDN resource for static content.

We explain the difference in delivery in the "How to speed up dynamic content delivery using a CDN" article.

Create and integrate a CDN resource for the entire site

You don't need to change the site's code to create and integrate a CDN resource for the entire site.

Note: If one of the services (CDN or Managed DNS) stops working, the site will also stop accelerating and working.

To create a CDN resource for the entire site:

1. Choose the acceleration type

Go to the CDN resources tab and click Create CDN resource.

The new page will open. Select "Accelerate and protect entire site" and click Confirm.

2. Enter a site name

Note: This step requires the creation of a DNS zone (similar to the site name) in the Gcore Managed DNS service. In our example, a DNS zone will be testdomain.com. If you haven’t used the Managed DNS before, the Free plan will activate automatically at this step. If you have already used the DNS service, the specified DNS zone will also be created automatically, and you can view it in the Gcore Customer Portal.

Enter the domain of the site you want to create a CDN resource. You can use as a site name the following values:

• a second-level domain (testdomain.com),
• a third-level domain (store.testdomain.com, blog.testdomain.com, etc.),
• or a higher-level domain (sales.store.testdomain.com).

In all cases, a DNS zone in our control panel will be a second-level domain (e.g., testdomain.com). The only exception is for eTLD (effective top-level domains) like co.uk, where the DNS zone will consist of a subdomain and an effective top-level domain: example.co.uk.

You can also optionally enter the description of this CDN resource. The maximum comment length is 512 characters. When you complete the configuration, click Confirm.

Note:

1. If you try to specify a site name that already exists on another client's account, the procedure will be declined.

2. If you specify a site whose domain matches an existing DNS zone in your account, this DNS zone will be used for settings. The zone is not duplicated.

3. Review your DNS records

Our system looks for DNS records associated with your site domain at this step.

• If DNS records exist, they will be displayed automatically. You can edit or delete them or add a new record if necessary. Alternatively, you can skip this step. Click Confirm when the configuration is complete.

• If no DNS records are found, a warning indicates that at least an A record should be added. Specify the subdomain or empty the "Name" field and the IP address. Then click Add and Confirm.

4. Change name servers

If all the steps are completed successfully, a CDN resource and DNS zone will be automatically created for the site you specified in step 2.

To complete the site acceleration setup, log into your domain registrar account and replace the current name servers with the Gcore name servers and click Confirm:

      Copy
      
    ns1.gcorelabs.net  
ns2.gcdn.services

Note: The name servers can change. The current values will be specified on the wizard page.

Remember that the name server change can take up to 24 hours.

5. (Optional) Setup additional options

Optionally, you can activate additional features for your CDN resource. You can skip this step and return to additional settings later. Click Confirm to complete the creation and setup of your CDN resource.

After completing the creation and setup of your CDN resource, you will be automatically directed to the page of CDN resource settings. The resource settings header will show the name of the associated DNS zone. A warning will be displayed if the zone is not delegated to Gcore. This warning may persist for up to 24 hours until the NS servers are changed.