Copying a configuration from one resource to another
You can use CDN resource settings from a configuration of another CDN resource. To do this, select an existing CDN resource in the Copy a configuration field. Keep in mind the following:
- A domain name is unique within a single resource, i.e., you cannot create another resource with the same domain name. A configuration copy does not inherit the domain name.
- You can copy settings only from a CDN resource residing within the same folder.
- If the existing resource indicates
POST,PUT,PATCH, orDELETEunder Allowed methods, these methods will not be available to users of the new resource. To find out if you can use these methods, contact support. When contacting, describe your use case. - If you uploaded a TLS certificate for the original resource, the system will re-use it in the new resource. You do not need to upload it again.
-
In the management console, select the folder where you want to create a resource.
-
Navigate to Cloud CDN.
-
Click Create resource.
-
Under Copy a configuration, select an existing CDN resource whose settings you want to copy to a new one.
-
If required, adjust the settings.
Warning
The Domain name parameter must be unique for each resource.
-
Click Continue.
-
If required, adjust the settings under Caching, HTTP headers and methods, and Additional settings, and then click Continue.
Once the CDN resource is created, get the CDN provider's domain name and create a CNAME resource record for the specified name in your DNS hosting settings, e.g., in Yandex Cloud DNS. For more information, see Domain names for content distribution.
Sample resource record:
cdn.example.com. CNAME e1b83ae3********.topology.gslb.yccdn.ru
The new resource will start working properly after the CNAME record you created on your DNS hosting (see the section on host names for content distribution) gets propagated across the DNS servers. This may take a few hours.
Note
Do not use an ANAME resource record with domain names for content distribution; otherwise, the end user will get a response from a CDN server not linked to the user geolocation. The response will always be the same for all users.