Add a site
Onboard a site with the add-domain wizard: pick a plan, choose CNAME or nameserver setup, configure origins and update DNS.
This page shows how to put a website on Yeap Cloud CDN. The Add domain wizard walks you through choosing a plan, an onboarding method and your origin settings. The last step is pointing your DNS at the CDN.
Before you begin
- Have the domain you want to accelerate ready, for example
example.com. You need to be able to edit its DNS records or its nameservers. - Your origin server must be reachable on a public IP address or hostname and serve HTTP or HTTPS on the port you will configure.
- If you pick a paid plan, make sure you can pay for it from your account.
Step 1: Open the wizard
- Sign in to the console and go to CDN → CDN domains (
/cdn/domains). - Click Add domain to open the wizard at
/cdn/domains/new.
The wizard has five steps:
- Basic information
- Select plan
- Setup method
- Origin settings
- Setup guide
Step 2: Basics
| Field | Description |
|---|---|
| Domains | The site's main domain, for example example.com. You add individual hostnames such as www.example.com in a later step. |
| CDN routes / Groups | The delivery line this site uses. Once you select one, the console shows its CNAME target for setup. If you see "No access domain is configured for this group yet", choose another line or contact support. |
| Enable SSL | On by default. You request certificates for each hostname on the SSL/TLS tab after onboarding. See SSL/TLS. |
| Enable WAF | Turns the WAF on. It only takes effect on plans that include the WAF (Pro and Enterprise). |
| Advanced proxy settings | Origin HTTP version, WebSocket support and Proxy timeout in seconds. You can change these later on the site's Network tab. |
Click Next step.
Step 3: Choose a plan
- Select a plan card: Free, Starter, Pro or Enterprise. For plan quotas, see the CDN overview.
- For a paid plan, choose a Billing cycle.
- Click Next step. For paid plans the button reads Create order and continue. This step creates the site and its plan subscription:
- Free: the subscription takes effect immediately and you move to the next step.
- Paid plans: a pending invoice is created. Click Pay now and pay. Then return to the wizard and click I've paid, refresh status. You can continue once the subscription is active.
Each plan subscription can be bound to only one site. To onboard several sites, choose a plan for each of them.
Step 4: Choose an onboarding method
| Method | When to use it | What you do |
|---|---|---|
| CNAME setup | Your DNS stays with your current provider | Add one CNAME record per hostname at your current DNS provider, pointing to the target shown in the console |
| NS setup | You want Yeap DNS to host the domain's DNS | The platform creates a DNS zone for the domain (if none exists) and adds the CNAME records the CDN needs. You change the domain's nameservers at your registrar to the ones shown in the console |
Many DNS providers do not allow a CNAME on the zone apex (example.com). To accelerate the apex domain, use nameserver setup or your provider's CNAME flattening (ALIAS/ANAME) feature.
For managing zones and records in Yeap DNS, see the DNS docs.
Step 5: Configure the origin
Each Host configuration block is one hostname that serves traffic:
| Field | Description |
|---|---|
| Hostname | The full hostname, for example www.example.com. If you leave it empty, the domain from Step 2 is used. |
| Origin address | The origin's IP address or hostname, for example 203.0.113.10 or origin.example.com. |
| Protocol | Whether the CDN connects to the origin over HTTP or HTTPS. |
| Port | The origin port, for example 80 or 443. |
| Load mode | How requests are spread when a hostname has several origin addresses: Round robin or IP Hash, which always sends a given visitor IP to the same origin. |
To add more hostnames, click Add host configuration. The number of hostnames is capped by your plan's hostnames-per-site quota. When you are done, click Submit.
Step 6: Update DNS
After you submit, the wizard shows Setup guide.
CNAME setup: the list shows the CNAME target for each hostname. Click Copy and add the record at your DNS provider. For example:
www.example.com. CNAME <CNAME target shown in the console>Nameserver setup: the page lists the NS servers and the Generated CNAME records. Change the domain's nameservers at your registrar to the listed ones. If the DNS records could not be created automatically, the page shows the reason.
To confirm the change is live, click DNS check. It queries a public resolver for the current CNAME or NS answer. How long DNS changes take depends on the old record's TTL and on your registrar. It usually ranges from a few minutes to a few hours.
Site status
The Status column of the Domains list shows each site's status:
| Status | Meaning |
|---|---|
| Incomplete | The site exists, but its subscription is not active yet or it has no hostnames |
| Active | The subscription is active and at least one hostname is configured. Edge nodes serve the site with its configuration |
| Paused, Inactive, Terminated | The site is not being served because of its subscription or an administrative action |
Active means the CDN side is ready. It does not check whether your DNS points to the CDN yet. Visitor traffic only flows through the CDN after your DNS change takes effect.
Managing origins after onboarding
You can change hostnames and origins at any time on the site's Origin settings tab. Click Add origin or edit an existing entry:
| Field | Description |
|---|---|
| Hostname | The subdomain prefix, for example www. Use @ for the domain itself and * for a wildcard. |
| Origin address | One or more origin addresses (IP or hostname), each with an optional port. Click Add origin address to add more. If you list several addresses, give them all the same port. |
| Origin protocol | HTTP, HTTPS or Automatic. With Auto, the SSL/TLS encryption mode decides: Full and Full (Strict) use HTTPS, while Flexible and Off use HTTP. |
| Load balancing mode | Round robin or IP Hash. |
| Priority | Lower numbers come first. |
| Enable | When off, the hostname is no longer deployed to the edge. |
Origin parameters that apply to the whole site are set on the Network tab: origin HTTP version, proxy timeout, keep-alive and maximum request body size. They apply to every hostname on the site.
By default, the Host header sent to your origin is the hostname the visitor requested. Your origin must recognize that hostname, for example through a matching virtual host in your web server. To rewrite the origin Host header or route specific paths to a different origin, use Page rules.
Once everything is configured, open the site's Diagnostics tab, pick a hostname and run a check. It quickly flags DNS that has not taken effect, an unreachable origin, origin redirect loops and SSL mode mismatches.
Next steps
- Issue certificates and turn on HTTPS: SSL/TLS
- Tune caching: Cache and purge