Got a Docker Compose file? Your project goes live in seconds — one command on cdn.com.tr. See how

CDN.com.tr Help

Delivery points and DNS

Use this section for domains, CNAMEs, subdomains, DNS records, full transfer, and DNS readiness.

Delivery points and DNS

This section covers how your domains reach the CDN — from adding a delivery hostname to managing DNS records and, when you are ready, moving your whole domain to CDN.com.tr DNS. It is the starting point for putting a site or subdomain behind the CDN.

A delivery hostname is the name the CDN serves — your root domain or a subdomain like api.example.com. Before traffic and SSL can flow, the domain has to be verified, so the panel gives you the exact DNS records to add and a reconciliation preview that shows what will change before you apply it.

You can keep DNS at your current provider and only point the delivery hostname at the CDN, or move your nameservers to CDN.com.tr for full managed DNS — which unlocks wildcard coverage and keeps records and certificates in one place. Either way DNS changes propagate gradually, so the reconciliation step lets you switch without surprises.

Use cases

  • A customer adds `api.example.com` as a delivery hostname.
  • A full-transfer domain needs DNS scan and reconciliation.
  • A verification token is required before SSL or traffic can proceed.

Workflow

  1. Select account.
  2. Add root domain or subdomain.
  3. Connect DNS or CNAME target.
  4. Verify ownership.
  5. Reconcile DNS records when full transfer is used.

Checks

  • Domain belongs to selected account.
  • DNS target matches CDN.com.tr nameserver or CNAME expectation.
  • Critical SOA/NS records are protected during reconciliation.

Topics

Manage DNS records

Add, update, delete, import, export, and move eligible records to cloud DNS.

Related pages