--- title: "CDN FAQ" description: "Short answers about E2E CDN, turning it on for your account, billing, buckets, your own domain name, caching, and what distributions support." content_type: "faq" product: "cdn" platform: "MyAccount" url: "/myaccount/cdn/faq/" --- # CDN FAQ ## How do I turn on CDN for my account? Send **Request CDN**, once for the whole account. In MyAccount, under **Network**, click **CDN**, then **Request CDN** on **Manage CDN Services**. Enter a **Reason** about your business and what you will serve, up to 500 characters, and send it. E2E reviews the request. See [Request CDN](/myaccount/cdn/how-to/request-cdn/). ## How do I know my CDN request is approved? Open **Manage CDN Services**. Once E2E approves the request, **Create CDN** shows there in place of **Request CDN**, and **Add to CDN** on your buckets opens the distribution form. While the request waits, **Request CDN** opens a message that it is under process. See [See whether the request is approved](/myaccount/cdn/how-to/request-cdn/#see-whether-the-request-is-approved). ## My CDN request is still waiting. What can I do? Get your origin ready, so you can create the distribution as soon as CDN is on: make your bucket public and upload your files, or set up your web server with a domain name. If you need CDN by a certain date, contact support with your account's CRN, the date you sent the request, and what you will serve. See [While you wait](/myaccount/cdn/how-to/request-cdn/#while-you-wait). ## Can I send another CDN request? No. An account sends one request. Clicking **Request CDN** again shows that the request is under process. To follow it up, contact support. See [Request CDN](/myaccount/cdn/how-to/request-cdn/). ## Do I need to request CDN for each project? No. The CDN request and the CDN plan belong to the whole account. Distributions belong to a project, and each project lists only its own. See [Request CDN](/myaccount/cdn/how-to/request-cdn/). ## Why does Add to CDN ask me to request CDN? Your account is still waiting for CDN approval. **Add to CDN** asks for the same request as **Manage CDN Services**. See [Request CDN](/myaccount/cdn/how-to/request-cdn/). ## Is CDN tied to a region? No. The same distributions show whether you have Delhi or Chennai selected, and each distribution serves visitors from edge locations around the world. A bucket's distribution uses the address of the bucket's region as its origin. See [Create a distribution](/myaccount/cdn/how-to/create-a-distribution/#before-you-begin). ## How is CDN billed? Through a CDN plan for the whole account. The plan's price is billed each calendar month as the full cost, or deducted from infra credits on a prepaid account. The plan renews on the first day of every month until you change it. Bandwidth beyond the plan is charged per GB. For prices, see [E2E's pricing page](https://www.e2enetworks.com/pricing). See [Choose a CDN plan the first time](/myaccount/cdn/how-to/create-a-distribution/#choose-a-cdn-plan-the-first-time). ## Does disabling a distribution stop billing? No. You pay for the CDN until the distribution is deleted. See [Disable or delete a distribution](/myaccount/cdn/how-to/disable-or-delete-a-distribution/). ## How do I change or cancel my CDN plan? On **Manage CDN Services**, click **CDN Plan**, pick a plan in **Choose a new plan**, and click **Save and Apply**. The new plan takes effect on the first day of next calendar month. There is no option to cancel the plan. See [Change your CDN plan](/myaccount/cdn/how-to/change-your-cdn-plan/). ## Can I serve a bucket at my own domain name? No. A bucket's distribution always uses the E2E certificate, and serves files at its own Distribution URL. To serve files at your own domain name, such as `cdn.example.com`, the origin must be on your own domain too, such as a web server at `origin.example.com`. See [Serve files at your own domain name](/myaccount/cdn/how-to/create-a-distribution/#optional-serve-files-at-your-own-domain-name). ## Can I use my own domain name with a distribution? Yes, for an origin on your own domain. On **Create CDN**, choose **Custom Certificate (example.com)**, list your names, such as `cdn.example.com`, and choose a certificate from **SSL Certificates**. The names must be on the same domain as the origin. With a wildcard certificate such as `*.example.com`, the origin and every name must end in `example.com`. See [Serve files at your own domain name](/myaccount/cdn/how-to/create-a-distribution/#optional-serve-files-at-your-own-domain-name). ## What is my distribution's address? Its **Distribution URL**, shown on **Manage CDN Services**. It is the first part of your origin's domain name followed by 10 random letters and digits. A file at `/images/logo.png` on the origin is served at `https:///images/logo.png`. See [CDN](/myaccount/cdn/). ## How long does a new distribution take to work? Up to 30 minutes to deploy. **Manage CDN Services** shows **Deployed** up to 15 minutes after that. Each edit, enable, and disable takes up to 30 minutes too. See [State and status](/myaccount/cdn/#state-and-status). ## Can I create two distributions for the same origin? No. A project can have one distribution for each origin domain name; a second is refused with **Domain already exists for this user.** See [Domain already exists for this user](/myaccount/cdn/troubleshooting/cdn/#domain-already-exists-for-this-user). ## Can a distribution have more than one origin? No. A distribution has one origin and one cache behaviour. To serve a second origin, create a second distribution. See [Create a distribution](/myaccount/cdn/how-to/create-a-distribution/). ## Can I change a distribution's origin? No. **Origin path** can change, while **Origin Domain Name** and **Origin ID** stay as they were created. To use a different origin, create a new distribution. See [Change the origin settings](/myaccount/cdn/how-to/change-distribution-settings/#change-the-origin-settings). ## I changed a file. Why do visitors still get the old one? The CDN serves its cached copy until the file's TTL runs out. To serve the new version sooner, clear the file from the cache with **Flush Cache** on the distribution's **Invalidations** tab. See [Clear the cache](/myaccount/cdn/how-to/clear-the-cache/). ## Does the CDN pass query strings to my origin? No. Query strings and cookies are not passed to your origin and do not change what is cached: `/images/logo.png?v=2` gets the same cached file as `/images/logo.png`. To publish a changed file, clear its cache or give it a new name. See [Avoid clearing the cache](/myaccount/cdn/how-to/clear-the-cache/#avoid-clearing-the-cache). ## Does the CDN compress files? No. The CDN serves files as your origin sends them. To serve compressed files, compress them at your origin. See [Change distribution settings](/myaccount/cdn/how-to/change-distribution-settings/). ## Do distributions answer over IPv6? No. Distributions answer over IPv4. See [Create a distribution](/myaccount/cdn/how-to/create-a-distribution/#check-that-the-distribution-is-live). ## Can visitors use http:// addresses? Yes, once you allow it. Every new distribution starts with **Viewer Protocol Policy** set to **HTTPS Only**. To accept `http://` too, change it to **Redirect HTTP to HTTPS** or **HTTP and HTTPS**. See [How visitors connect](/myaccount/cdn/how-to/change-distribution-settings/#how-visitors-connect). ## Can I serve videos through the CDN? Yes. Videos are files like any other: upload them to a public bucket, or put them on your web server, and serve them through a distribution. See [Serve a bucket through the CDN](/myaccount/cdn/how-to/serve-a-bucket-through-the-cdn/). ## Can I restore a deleted distribution? No. To serve the files again, create a new distribution, which gets a new Distribution URL. See [Disable or delete a distribution](/myaccount/cdn/how-to/disable-or-delete-a-distribution/).