After the DDoS high defense instance expires, there is no defense capability. The forwarding rule configuration takes effect normally within 7 days after the expiration, and the traffic exceeding the limit will trigger the traffic rate limit, which may cause random packet loss. Service traffic forwarding will be stopped after 7 days after the expiration. In this case, if your business access address still resolves to the DDoS high-defense instance, the business will not be accessible.
The service bandwidth of a DDoS high-defense instance refers to the normal service traffic that accesses the protection service of the current instance. The larger value of the inbound and outbound traffic is taken, in Mbps. You can upgrade the instance on the instance management page of the DDoS Anti-DDoS console to increase the service bandwidth of the current instance. For more information, see Upgrade DDoS High Defense Instance Specifications.
If your business traffic exceeds the business bandwidth of the purchased DDoS Anti-DDoS instance, the traffic rate limit will be triggered, which may cause random packet loss.
Anti-DDoS Premium (International): Not currently supported.
You can view the back-to-source IP network segment of DDoS Anti-DDoS on the domain name access page of the DDoS Anti-DDoS console. For more information, see Release DDoS High Anti-Back-to-Source IP.
Not possible. Anti-DDoS Premium returns to the source through the public network, and does not support directly filling in the internal network IP.
There is a delay. After modifying the source site IP protected by the Anti-DDoS Premium service, it takes about five minutes to take effect. It is recommended that you perform the change operation during the low peak period of the business. For more information, see Replacing the public network IP of the source site ECS.
In response to the high-traffic DDoS attack behavior of Anti-DDoS Premium, it is impossible to distinguish which website was attacked from the data packet level. It is recommended that you use multiple sets of high-defense DDoS instances and deploy your website on different high-defense DDoS instances to view the attack status of each website.
Yes,
The health check is enabled by default for website services. The health check is not enabled for non-website services by default, but it can be enabled through the Anti-DDoS Premium console. For details, see Setting Health Check. For more information about health check, please refer to Health Check Overview.
The website business is load balanced through source address HASH. Non-website services can be polled and forwarded by weighted polling.
Support.
For non-website services, you can enable session retention through the Anti-DDoS Premium console. For specific operations, see Setting Session Retention.
After opening the session hold, the Anti-DDoS Premium service will continue to send requests for the same IP to a server in the origin site during the set period of session hold. However, if the client's network environment changes (for example, switching from wired to wireless, 4G network to wireless, etc.), the session will remain invalid due to IP changes.
900 seconds. For non-website services, you can adjust this setting through the Anti-DDoS Premium console. For specific operations, see Setting Session Retention.
120 seconds
Not currently supported.
Support. For more information, see Anti-DDoS Premium WebSocket configuration.
The website access method does not support HTTPS two-way authentication. When non-website access and TCP forwarding are used, HTTPS two-way authentication is supported.
It may be because the client does not support SNI authentication. Please confirm whether the client supports SNI authentication. For problems that may be caused by SNI authentication, see HTTPS access exceptions that may be caused by SNI.
支持的SSL協議:
- TLS v1.0- TLS v1.1
- TLS v1.2支持的加密套件:
- ECDHE-ECDSA-AES128-GCM-SHA256
- ECDHE-ECDSA-AES256-GCM-SHA384
- ECDHE-ECDSA-AES128-SHA256
- ECDHE-ECDSA-AES256-SHA384
- ECDHE-RSA-AES128-GCM-SHA256
- ECDHE-RSA-AES256-GCM-SHA384
- ECDHE-RSA-AES128-SHA256
- ECDHE-RSA-AES256-SHA384
- AES128-GCM-SHA256
- AES256-GCM-SHA384
- AES128-SHA256
- AES256-SHA256
- ECDHE-ECDSA-AES128-SHA
- ECDHE-ECDSA-AES256-SHA
- ECDHE-RSA-AES128-SHA
- ECDHE-RSA-AES256-SHA
- AES128-SHA
- AES256-SHA
- DES-CBC3-SHA
- RSA+3DES
Number of protected ports:
A DDoS Anti-DDoS instance supports 5 ports by default and supports expansion to 400 ports.
Number of supported domain names:
A DDoS high defense instance supports 10 domain name configurations by default, and the maximum can be expanded to 200.
After the DDoS high defense instance expires, there is no defense capability.
The forwarding rule configuration takes effect normally within 7 days after the expiration, and the traffic exceeding the limit will trigger the traffic rate limit, which may cause random packet loss.
Service traffic forwarding will be stopped after 7 days after the expiration. In this case, if your business access address still resolves to the DDoS high-defense instance, the business will not be accessible.
Number of protected ports:
An Anti-DDoS Premium instance supports 5 ports by default and supports expansion to 400 ports.Number of supported domain names:
An Anti-DDoS Premium instance supports 10 domain name configurations by default, and the maximum can be expanded to 200.
For services that have been connected to the Anti-DDoS Premium service, Anti-DDoS Premium will automatically filter some malformed packets in the network traffic (such as SYN packets, abnormal SYN flags, and other data packets that do not conform to the TCP protocol) to make your business The server does not need to waste resources processing these obviously malformed packets. Such filtered malformed packets will also be included in the cleaning traffic, so even if your server traffic does not reach the cleaning threshold, cleaning traffic may still occur.
not support. The access request forwarded by Anti-DDoS Premium may not pass the NTLM authentication of the origin server, and the client will repeatedly display authentication prompts. It is recommended that your website use other methods for authentication.