Got a Docker Compose file? Your project goes live in seconds — one command on cdn.com.tr. See how Built your app with AI? From folder to live URL with one command — no git, no registry: cdnctl deploy. See how Code on GitHub? Every push auto-deploys to cdn.com.tr — connect your repo and ship. See how

CDN.com.tr Help

Publish an existing website through CDN

Place the existing origin website behind CDN.com.tr with Pull CDN, then verify origin Host header, delivery hostname, DNS, SSL, Apply Changes, and public traffic.

Getting started

Publish an existing website through CDN

Place the existing origin website behind CDN.com.tr with Pull CDN, then verify origin Host header, delivery hostname, DNS, SSL, Apply Changes, and public traffic.

Where to go after this flow

The most common next steps for an existing site are DNS/SSL, Apply Changes, or revisiting the choice model.

Choice review

Compare source and delivery method again

Decide whether Pull is right, or whether Push/Hosting, CNAME, or Full DNS better fits the need.

Pull / Push / Hosting Default / CNAME / Full DNS
Open choice guide
Deploy

Apply Changes and watch Operations

Verify that origin, Host header, DNS, or SSL changes reached traffic config.

Pull CDN All delivery methods
Open apply guide

Panel path

  1. Management Panel
  2. CDN Accounts
  3. Pull CDN
  4. Origin Host Header
  5. CNAME / Delivery Hostnames
  6. DNS Settings
  7. SSL
  8. Apply Changes
  9. Operations

Practical scenarios for an existing site

This page is more than “add a CNAME”; the same Pull CDN source can use three delivery methods.

Test without DNS

Smoke-test the origin from the default endpoint

Use xyz.cdn.com.tr first to verify origin response and Host header behavior, then move to a custom domain model.

Pull CDN Default Endpoint
Move one host

Connect www or assets by CNAME

Only the chosen subdomain, such as www.example.com or assets.example.com, points to the CDN target.

Pull CDN Custom Subdomain
Full domain DNS management

Manage the root domain with Full DNS Transfer

Domain nameservers become CDN.com.tr; DNS records, SSL, and CDN features are managed from the same panel.

Pull CDN Full DNS Transfer

Prerequisites

  • The origin server is reachable over HTTP or HTTPS.
  • The expected Host header for the origin application is known.
  • The domain or subdomain belongs to the selected account.
  • Package purchase and assignment are completed in the panel.

Decision model

Origin Host header

When Keep the request header is selected, the backend receives the incoming $host; otherwise it receives the fixed value below the checkbox.

  • Selected: a request for player.videoon.ly reaches the backend as player.videoon.ly.
  • Not selected: every incoming domain is sent to the backend with the configured fixed origin host.
  • This contract should hold for Pull, Push, and Hosting flows except AI and Knight Online platform exceptions.

Delivery method

An existing site can use the same three public hostname models.

  • Default Endpoint: xyz.cdn.com.tr for quick testing.
  • Full DNS Transfer: root domain nameservers move to CDN.com.tr.
  • Custom Subdomain: www.example.com or assets.example.com points by CNAME.

Step-by-step guide

1

Verify account and package

Pull CDN settings are account-scoped, so start by confirming the selected account.

  • Select the account in CDN Accounts.
  • If needed, complete package purchase and assignment in the panel.
  • Prepare the current origin domain or IP.

Expected result: The Pull CDN screen shows origin settings for the selected account.

cdnctl equivalent 
cdnctl packages list --owned --format table
cdnctl accounts list
export ACCOUNT_UUID=<account_uuid>
2

Configure the Pull CDN origin

Origin address, path, port, and Host header behavior are configured here.

  • Open Pull CDN.
  • Set Source Address to the origin IP or domain.
  • Set Keep the request header according to the backend Host expectation.
  • Save Only or Activate the setting.

Expected result: Generated config matches the UI origin server and proxy Host value.

cdnctl equivalent 
curl -s -H "Authorization: Bearer $CDN_TOKEN" https://cdn.com.tr/api/accounts/show/$ACCOUNT_UUID
# The origin is set in the panel; this shows what the account is serving from now.
3

Add a delivery hostname

The CNAME screen is where a public domain or subdomain attaches to the selected account.

  • Open Delivery Hostnames.
  • Add the root domain or custom subdomain.
  • Use the generated CDN endpoint as the DNS target.

Expected result: The hostname belongs to the selected account and exposes DNS or verification status.

cdnctl equivalent 
curl -s -X POST -H "Authorization: Bearer $CDN_TOKEN" -H 'Content-Type: application/json' -d '{"domain":"www.example.com"}' https://cdn.com.tr/api/cname/$ACCOUNT_UUID/cnameStore
curl -s -H "Authorization: Bearer $CDN_TOKEN" https://cdn.com.tr/api/cname/$ACCOUNT_UUID
4

Verify DNS and SSL status

Traffic is not considered live until DNS and certificate readiness are visible.

  • Check DNS Settings for records and verification status.
  • Check SSL for automatic or manual certificate status.
  • Do not mark traffic live while the certificate is not ready.

Expected result: DNS and SSL readiness are customer-visible.

cdnctl equivalent 
curl -s -X POST -H "Authorization: Bearer $CDN_TOKEN" https://cdn.com.tr/api/cname/$ACCOUNT_UUID/check_verify_domain
curl -s -H "Authorization: Bearer $CDN_TOKEN" https://cdn.com.tr/api/certificates/$ACCOUNT_UUID
5

Apply changes and test public traffic

Origin, hostname, DNS, or SSL changes may require Apply Changes before traffic config is updated.

  • Run Apply Changes from CDN Accounts or the warning banner.
  • Watch the deployment result in Operations.
  • Test the public domain with a clean browser or curl.

Expected result: The public URL returns the intended origin response; wrong backend responses are debugged through Host header or DNS target.

cdnctl equivalent 
curl -I https://www.example.com/

Verification

  • The Pull CDN origin belongs to the selected account.
  • Keep the request header matches the backend Host expectation.
  • Delivery hostname CNAME or DNS target is clear.
  • SSL readiness is required before public success.
  • Operations success and a public 200/3xx response are verified after Apply Changes.

Use cases

A customer wants to keep the application on the current hosting provider while using CDN.com.tr for traffic, cache, security, SSL, and DNS management.

Quick workflow

  1. Account and purchased package are ready.
  2. Choose Pull CDN as the source.
  3. Configure origin address, port, path, and Host header behavior.
  4. Create a delivery hostname through Default Endpoint, Full DNS Transfer, or Custom Subdomain.
  5. Complete DNS and SSL verification.
  6. Apply changes and verify public traffic.

Checks

  • Origin Host header behavior is protected by ConfigServiceOriginHostHeaderContractTest.
  • Hostname APIs must enforce account ownership.
  • DNS and SSL readiness are required before declaring success.
  • Manual DB changes or hand-written server config are not the customer flow.