Your opinion helps us make a better documentation.
This document contains information to help you successfully create a CNAME record for your customized Edge Services domain, and troubleshoot any potential DNS problems.
A Canonical Name (CNAME) record is a type of DNS record. Generally, DNS records hold information for translating a domain or subdomain to an IP address, mail server or other domain/subdomain. They are crucial in directing internet traffic to the correct servers. More specifically, CNAME records map one domain name (an alias) to another (the canonical name).
A CNAME record may look like the following:
| Hostname / Alias | Destination / Canonical Name |
|---|---|
videos.example.com | otherdomain.com |
In this case, when a DNS server sees this record for videos.example.com it will know not to direct traffic to videos.example.com’s own IP address, but to that of otherdomain.com. It will find othercomain.com’s IP address via its A record.
When the client actually connects to otherdomain.com’s IP address, the web server can see that the requested URL was videos.example.com, and deliver the relevant content.
When you create an Edge Services pipeline to an origin (Object Storage bucket or Load Balancer), initially the origin content is served through the standard Edge Services endpoint, e.g. pipeline-id.svc.edge.scw.cloud. If you do not want to customize the standard Edge Services endpoint, you do not need to worry about CNAME records.
However, if you choose to customize your Edge Services endpoint with your own subdomain, a CNAME record must be created to point your subdomain to the Edge Services endpoint.
If your domain is managed with Scaleway Domains and DNS, we take care of auto-generating the appropriate CNAME record for you, as well as deleting it if and when you deactivate Edge Services. There is no action for you to take. You should not attempt to modify or delete the CNAME record (which will be visible among your Domains and DNS records in the console).
If your domain is managed by an external provider, Scaleway is unable to create the appropriate CNAME record for you. You will be prompted, as part of the process for customizing your Edge Services domain, to create this record yourself with your domain provider.
Log into your domain provider, and locate the DNS settings for your domain. Create a new CNAME record pointing your subdomain to the Edge Services endpoint for your bucket or Load Balancer origin. This endpoint can be retrieved from the Scaleway console.
The interface used by different domain providers varies, but creating your CNAME record may look like one of the following examples:
| Record | Destination |
|---|---|
my-chosen-subdomain.beautiful-domain.com | pipeline-id.svc.edge.scw.cloud. |
| Subdomain | Target host |
|---|---|
my-chosen-subdomain | pipeline-id.svc.edge.scw.cloud. |
| Host record | Points to |
|---|---|
my-chosen-subdomain | pipeline-id.svc.edge.scw.cloud. |
my-chosen-subdomain | Record Type | Value |
|---|---|---|
@ | CNAME | is an alias of pipeline-id.svc.edge.scw.cloud. |
The trailing dot at the end of the target endpoint (pipeline-id.svc.edge.scw.cloud.) is implicitly added by some domain and DNS providers, and must be explicitly added for others. Check with yours whether the dot is necessary.
You may also see a TTL field, which stands for Time To Live. This tells the DNS resolver how long it can cache this record, before it must re-check the origin source in case something has changed. TTL is measured in seconds, and the default value is usually 12 hours (43200 seconds) or 24 hours (86400 seconds).
See our dedicated documentation for help resolving any error message you may get related to your CNAME record.
Your opinion helps us make a better documentation.