CDN.com.tr Help

Getting started

This section is a decision hub, not a plain article list: prepare the account and package foundation first, then choose where the content comes from and which domain model will serve it. Source type and delivery method can be changed later from the related panel screens; the first choice only helps the user start in the right guide.

Back to Help Center

Getting started

This section is a decision hub, not a plain article list: prepare the account and package foundation first, then choose where the content comes from and which domain model will serve it. Source type and delivery method can be changed later from the related panel screens; the first choice only helps the user start in the right guide.

Which guide matches the need?

Find the need first. Each card shows the source type and recommended starting delivery method; the same account can move to another delivery model later.

Foundation first

Prepare account and package foundation

Before domain, storage, or platform settings, make the account UUID, selected account, and purchased-package boundary explicit.

Before source choice Before delivery choice
Open account foundation
Existing website

Put an existing origin behind CDN

Your hosting keeps serving the app; CDN.com.tr manages origin, Host header, DNS, SSL, cache, and security in front of it.

Pull CDN CNAME or Full DNS
Open existing site guide
Fast static files

Publish files from CDN.com.tr storage

Start with `xyz.cdn.com.tr` without connecting your own domain; move to CNAME or Full DNS later when needed.

Push CDN Default Endpoint
Open Simple Transfer guide
Application runtime

Publish an application on Platforms

For WordPress, PHP, or Managed Container runtime on CDN.com.tr, follow entitlement, deploy, logs, and public domain steps.

CDN Hosting/Platforms CNAME or Default Endpoint
Open platform guide
Not sure yet

Choose source and delivery together

Compare Pull/Push/Hosting with Default Endpoint/CNAME/Full DNS as a 3x3 model with examples.

Pull + Push + Hosting Default + CNAME + Full DNS
Open choice guide
Change not live

Apply Changes and watch Operations

Track whether a saved setting was deployed to traffic config and what the operation result says.

All sources All delivery methods
Open apply guide

3x3 source and delivery matrix

Source type decides where the content lives; delivery method decides which domain serves it. Both can be changed from the related screens after setup, and Apply Changes may be required.

Pull CDN: content lives on the existing origin

Default Endpoint

Use `xyz.cdn.com.tr` to test an origin without changing DNS or to create a temporary preview.

Custom Subdomain

Put `www.example.com`, `assets.example.com`, or `api.example.com` behind CDN by CNAME.

Full DNS Transfer

Move the root domain DNS to CDN.com.tr nameservers and manage the website with the full CDN/DNS feature set.

Push CDN: files live in CDN.com.tr storage

Default Endpoint

Simple Transfer: upload a file and serve static content quickly without a custom domain.

Custom Subdomain

Connect asset subdomains such as `images.example.com` or `static.example.com` to uploaded files.

Full DNS Transfer

Publish a static site or asset area from CDN.com.tr storage while CDN.com.tr manages root DNS.

CDN Hosting/Platforms: runtime runs on CDN.com.tr

Default Endpoint

Preview or smoke-test the platform app before connecting DNS.

Custom Subdomain

Connect application hosts such as `app.example.com` or `panel.example.com` to platform output.

Full DNS Transfer

Use when the platform application serves the root domain and DNS is managed by CDN.com.tr.

Use cases

  • Create the first account and keep the package boundary in the right place.
  • Put CDN.com.tr in front of an existing hosting origin.
  • Upload files to CDN.com.tr storage and serve them from the default endpoint or the customer domain.
  • Publish a WordPress, PHP, or container application on CDN.com.tr Platforms.

Workflow

  1. Prepare the account and package foundation from the first CDN account guide.
  2. Choose the source type: Pull CDN, Push CDN, or CDN Hosting/Platforms.
  3. Choose the delivery method: Default Endpoint, Custom Subdomain, or Full DNS Transfer.
  4. Continue to the guide for the selected combination.
  5. If source or delivery changes later, save it from the related product screen and run Apply Changes.

Checks

  • Package purchase stays in the panel; cdnctl/API/AI agents use already purchased packages.
  • Source type explains where the content lives; delivery method explains which domain serves it.
  • Default Endpoint needs no DNS; CNAME is for a custom subdomain; Full DNS Transfer moves DNS management to CDN.com.tr nameservers.
  • The first choice is not a permanent lock; settings can be changed later in the panel and deployed with Apply Changes.

Topics

Create the first CDN account

Create the account shell from CDN Accounts, buy and assign the package in the panel when required, and prepare the account UUID for DNS, storage, platform, or cdnctl workflows.

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.

Host static content with Simple Transfer

In the Add Your Website wizard, choose Push CDN as the content source and Default Endpoint as the delivery method, then publish files from the generated CDN.com.tr endpoint.

Publish an application on Platforms

Use CDN Hosting/Platforms to publish WordPress, PHP, or Managed Container workloads through account, package entitlement, platform settings, deploy/status/logs, and delivery method verification.

Apply Changes and watch Operations

Use Apply Changes and Operations to understand when saved origin, hostname, DNS, SSL, cache, or platform changes are actually deployed to traffic.