To stop the CDN acceleration service, temporarily disable or permanently delete a CDN accelerated domain name. Temporary disablement is reversible, but permanent deletion is not.
Compare temporary disablement and permanent deletion
You can stop the acceleration service in two ways: temporarily disable it or permanently delete it. If you may need acceleration for the domain name again, temporarily disable it. If you are replacing the domain name or no longer need the service, permanently delete it.
If your acceleration service was not stopped manually, your account or domain name may have met the conditions for passive offline status. See Changes to the offline rules for domain names to troubleshoot the reason for the passive offline status.
Temporarily disable
Temporary disablement stops the CDN acceleration service for a specified domain name. After you disable an accelerated domain name, its status in the console becomesDisabled.
Scenarios
Maintenance and updates — Your origin server requires significant updates or maintenance.
Other needs — You need to temporarily stop the CDN service while retaining the configured site settings.
Effect on the CNAME
After the CDN service is temporarily disabled, the CNAME points to an invalid address when a user requests the CDN accelerated domain name.
Reversibility
You can re-enable CDN acceleration without reconfiguration.
Billing
The CDN acceleration service may still incur CDN charges after the service is temporarily disabled. For details, see .
Permanently delete
Permanent deletion stops the CDN acceleration service for a specified domain name by deleting the accelerated domain name.
Scenarios
Domain name migration — When you replace an accelerated domain name, stop the acceleration service for the old domain name and then use the new domain name.
Service termination — When you no longer use the CDN service.
Effect on the CNAME
After you delete a CDN accelerated domain name, the CNAME record associated with the accelerated domain name is also deleted.
Reversibility
Deletion is permanent. If you delete an accelerated domain name and need to use the CDN acceleration service for the domain name again, add the accelerated domain name again and configure the corresponding acceleration policies.
Prerequisites
Migrate traffic away from the accelerated domain name
Before you disable or delete an accelerated domain name, migrate traffic away from the accelerated domain name to avoid business interruptions caused by the subsequent disablement or deletion. Methods for migrating traffic away from an accelerated domain name include, but are not limited to, the following:
Add a new accelerated domain name and direct users to it instead of the old accelerated domain name, to gradually reduce traffic on the old accelerated domain name to zero.
Change the DNS resolution policy of the accelerated domain name from the CNAME address to the addresses of the origin server.
Confirm that the domain name belongs to your current account
If the domain name that you want to delete belongs to another Alibaba Cloud account, such as an account used for Yunmeng website building, transfer the domain name to your current account first. The API for deleting accelerated domain names cannot delete a domain name that you do not own. Deleting a domain name that you do not own returns the InvalidDomain.NotFound: The domain does not belong to you error.
Transfer path: CDN console > Domain Names > Transfer In Domain Names. During the transfer, verify domain name ownership by using DNS resolution verification (a TXT record) or file verification. After the transfer is complete, the domain name appears in the domain name list of your current account, and you can disable and delete it.
Considerations
No one-click shutdown — Because the CDN service is associated with many system processes after it is activated, shutting it down directly may affect your business. Alibaba Cloud does not currently provide a one-click option to shut down the CDN service.
Billing — No fees are incurred for the CDN service as long as you do not add CDN accelerated domain names or enable related features such as Edge Routine. A temporarily disabled accelerated domain name, however, may still incur charges. For details, see How to disable the Alibaba Cloud CDN service or stop billing and the FAQ section in this topic.
Procedure
Temporarily disable an accelerated domain name
-
Log on to the CDN console.
-
In the left navigation pane, click Domain Names.
On theDomain Names page, locate the target domain name. In theActions column, choose
> Disable.In the confirmation dialog box for stopping the domain name, clickOK.
The status of the accelerated domain name changes to Disabled on the Domain Names page.
Permanently delete an accelerated domain name
Deleting an accelerated domain name cannot be undone, and the CNAME record associated with the domain name is also deleted. If you need to use the acceleration service for this domain name again, you must add the accelerated domain name again and configure the corresponding acceleration policies.
-
Log on to the CDN console.
-
In the left navigation pane, click Domain Names.
On theDomain Names page, locate the target domain name. In theActions column, choose
> Delete.In the confirmation dialog box for deleting the domain name, clickOK.
The acceleration service stops for the accelerated domain name, and the domain name is deleted.
If you add an accelerated domain name with the same name again after deleting it, the new domain name enters the Configuring state. This is normal. The system usually needs about 3 minutes to deliver the configuration, after which the status automatically changes to Enabled.
FAQ
Why are there still charges after I temporarily disable an accelerated domain name?
After you temporarily disable the CDN acceleration service, requests to the original accelerated domain name usually resolve to an invalid address and do not pass through CDN points of presence. However, in some cases, requests may still pass through CDN points of presence after the CDN acceleration service is temporarily disabled.
Cause 1: DNS server cache
If the DNS resolution service used is Local DNS, the resolution server may still have cached records for the original domain name because of its long update cycle.
When a user accesses the accelerated domain name, although the CNAME points to an invalid address, the local DNS record still contains the address of the CDN point of presence to which the CNAME points. The user can still retrieve origin content through the CDN point of presence. Once a request passes through a CDN point of presence, corresponding traffic and charges are incurred.
Cause 2: Bind a hosts file directly to a CDN point of presence
After obtaining the IP address of a CDN point of presence, a user directly binds the accelerated domain name to the CDN point of presence IP address in the hosts file.
When a user accesses the accelerated domain name, the request should resolve to an invalid address through DNS, but the hosts record causes the request to bypass DNS and access the CDN point of presence to retrieve origin content. Once a request passes through a CDN point of presence, corresponding traffic and charges are incurred.
Solution
Both preceding causes are irregular access patterns on the user side. To avoid any further charges after you stop the CDN acceleration service, see .