Domains card
In the row of the hostname you want to move, pick where it should be served from: your own source or one of your apps. The rows you changed are marked; Discard selection puts them back. Nothing has changed yet.
CDN.com.tr Help
Choose where each hostname is served from: your own source or an app
You choose where each of your hostnames is served from, in the Domains card of the Platforms tab: your own server, or one of the apps in your account. No hostname moves until you pick it and confirm; you undo the choice in the same card.
Platforms and managed add-ons
Choose where each hostname is served from: your own source or an app
You choose where each of your hostnames is served from, in the Domains card of the Platforms tab: your own server, or one of the apps in your account. No hostname moves until you pick it and confirm; you undo the choice in the same card.
Panel path
- Management Panel
- Content Source Configuration
- Platforms tab
- Domains card
- Review changes
- Yes, apply
Screenshot checkpoints
Review changes
Click Review changes. The window names each hostname with where it is served from now and after. It also says how many of your delivery rules will not apply while the hostname is on the app. When the app has a test address, the window links to it: open the app there and check it before you confirm.
The change is live
The card follows the change: first The change is being published, then The change is live. This usually takes under a minute. If it cannot be published, the card says so and shows Publish again.
Use cases
Your site is live on Pull CDN and you run an app in the same account. You want to serve one or more of your hostnames from that app, and be able to go back.
Workflow
- Open the Platforms tab. When the account has at least one app, the Domains card is shown. It lists every hostname of yours, where it is served from now, and where it can be served from. Nothing is preselected for you.
- In the row of the hostname you want to move, pick where it should be served from: your own source or one of your apps. The rows you changed are marked; Discard selection puts them back. Nothing has changed yet.
- Click Review changes. The window names each hostname with where it is served from now and after. It also says how many of your delivery rules will not apply while the hostname is on the app. When the app has a test address, the window links to it: open the app there and check it before you confirm.
- Read the list and click Yes, apply. Only the list you were shown is applied. If something changed on your account in the meantime, the list is refreshed and you are asked to confirm again.
- The card follows the change: first The change is being published, then The change is live. This usually takes under a minute. If it cannot be published, the card says so and shows Publish again.
- To undo it, pick the previous destination in the same row of the same card and confirm. Your delivery rules apply again as you left them, cache settings included.
Checks
- Creating an app, enabling apps or updating an app moves no hostname on a Pull CDN or Push CDN account. A hostname moves only by your choice in this card.
- The choice is per hostname. example.com and www.example.com are separate rows; moving one leaves the other where it is.
- You can change several hostnames at once. The change is applied as a whole: if one of them cannot be applied, none of them changes and your hostnames keep being served from where they were.
- Your delivery rules are not deleted or edited. While a hostname is served by an app, your rules for that hostname do not apply; they apply again when you send the hostname back. The Delivery Rules page shows which hostnames are served by an app.
- Every change is told to the account owner by e-mail and a panel notification, and is recorded in Activity.
- For a hostname whose DNS does not point to the CDN yet, or whose certificate is not ready, your choice is saved and the hostname moves when it is ready. The card says so in the row.
- An app that is not running cannot be chosen. If the app serving a hostname stops later, the card warns in that row: start the app, or send the hostname back.
- On a Push CDN account your hostnames are served from your Push CDN storage. To serve a hostname from an app, the account's content source has to be Pull CDN or Platforms.
Frequently asked questions
If I add an app, does my site switch to it by itself?
No. On an account served by Pull CDN or Push CDN, creating an app does not touch your hostnames. The app opens at its own test address. Only you move a hostname to an app, by picking it in the Domains card and confirming.
When does the change go live, and how do I know?
Usually within a minute of your confirmation. The card follows the change and says The change is live when it is. You can leave the page; it continues.
What do visitors see during the change?
Until the change is live, visitors are served from where the hostname was. From the moment it is live, they are served from the new destination.
How do I undo it?
In the same card, pick the previous destination (your own server) in the hostname's row and confirm. Your delivery rules apply again as you left them. Keep your own server running so that you can go back.
What happens to my delivery rules?
They stay. While the hostname is served by an app, your rules for that hostname do not apply; the confirmation window says how many. When you send the hostname back, they apply again with nothing for you to do.
What if a change cannot be applied?
Nothing changes. Your hostnames keep being served from where they were, and the panel tells you it could not be done. This holds for all of them when you picked several at once.
What if I delete the app that serves a hostname?
The panel tells you which hostnames the app serves and asks you to confirm. If you do, those hostnames return to your account's own source.
Can I move a hostname from one app to another?
Yes. Pick the other app in the row and confirm. The new app takes the hostname over, then the previous one lets go.
I only use Platforms on my account. How does this card work for me?
The same way: you choose the app for each hostname. On an account with a single app and no other content source, the hostname is attached to that app and you are told. With several apps, the hostname shows as Not assigned until you choose.
What if two people make a change at the same time?
One change is applied to an account at a time. The second request is answered with a message asking you to try again in a few seconds.
My account uses Push CDN. Can I serve a hostname from an app?
Not while the content source is Push CDN: your hostnames are served from your Push CDN storage, and the card shows them without offering an app. To serve a hostname from an app, the account's content source has to be Pull CDN or Platforms.
Related pages
Choose a managed platform
Pick WordPress, PHP, AI, Knight Online, or Managed Container based on the workload.
Managed Container Apps migration
Create a container app, registry credential, env/secrets, imports, jobs, deploy, status, and logs from customer surfaces.
Object Storage and AWS CLI
Create buckets, rotate access keys, bind buckets to apps, and verify with the S3-compatible endpoint.
What you can run — capabilities and limits
A managed container platform (Kubernetes underneath), not a VM or shell server: you bring container images or a docker-compose.yml and the platform runs them, with managed Redis/PostgreSQL/MySQL/NATS add-ons, persistent volumes, internal service DNS, and HTTP(S) exposure through the CDN edge.
Persistent storage for a managed app
Give a container app a persistent volume so its data survives restarts and redeploys: enable storage, set the in-container mount path and size. One volume per app, mounted at one path, on CephFS.
Move a live Pull-CDN site to Platforms with no downtime
Run your origin services on cdn.com.tr Platforms while your site keeps serving via Pull CDN: enable apps alongside your current delivery, build and validate everything on ca-* subdomains, then cut the main domain over only when ready — fully reversible.