Configuring Intelligent Scheduling

Last updated: 2020-04-02 10:00:58

    Introduction

    Each account can have multiple Anti-DDoS instances, and each instance has at least one protective line; therefore, there can be multiple protective lines under one account. Once your business is added to an Anti-DDoS instance, a protective line will be configured for it. If multiple protective lines have been configured, you need to choose the optimal business traffic scheduling method, i.e., how to schedule business traffic to the optimal line for protection while ensuring high business access speed and availability.
    Anti-DDoS features priority-based CNAME intelligent scheduling, where you can select an Anti-DDoS instance and set the priority of its protective line as needed.

    Anti-DDoS Pro (includes single-IP and multi-IP instances), Anti-DDoS Advanced and Anti-DDoS Ultimate instances support setting resolution.

    Priority-based Scheduling

    This refers to using the protective line of the highest priority to respond to all DNS requests, i.e., all access traffic will be scheduled to the protective line of the currently highest priority. You can adjust the priority value of protective line, which is 100 by default. The smaller the value, the higher the priority. The specific scheduling rules are as follows:

    • If the protective instance configured for your business contains multiple protective lines from different ISPs and of the same priority, response will be made based on the ISP of the specific DNS request. If one of the lines is blocked, access traffic will be scheduled in the order of BGP > China Telecom > China Unicom > China Mobile > ISP outside Mainland China.
    • If all the lines of the same priority are blocked, access traffic will be automatically scheduled to the currently available protective line of the second-highest priority.

      If no protective lines of the second-highest priority are available, automatic scheduling cannot be completed, and business access will be interrupted.

    • If the protective instance configured for your business contains multiple protective lines from the same ISP and of the same priority, access traffic will be scheduled by way of load balancing, i.e., evenly distributed to such lines.

    Samples

    Assume that you have the following Anti-DDoS instances: BGP protective IPs 1.1.1.1 and 1.1.1.2, China Telecom protective IP 2.2.2.2, and China Unicom protective IP 3.3.3.3, of which the priority of 1.1.1.2 is 2 and that of the rest is 1. Normally, all traffic will be scheduled to the protective lines with the current priority of 1. Specifically, traffic from China Unicom will be scheduled to 3.3.3.3, that from China Telecom to 2.2.2.2, and that from other ISPs to 1.1.1.1. If 1.1.1.1 is blocked, access traffic under this IP will be automatically scheduled to 2.2.2.2. If both 1.1.1.1 and 3.3.3.3 are blocked, traffic supposed to be scheduled to them will be distributed to 2.2.2.2, and if 2.2.2.2 is blocked too, traffic will be scheduled to 1.1.1.2.

    Prerequisites

    • Before enabling intelligent scheduling, please connect your business to be protected to your Anti-DDoS instance.

    • To modify the DNS resolution, you need to purchase the domain name resolution product.

    Setting Line Priority

    Please follow the steps below to set priorities for your protective lines based on your scheduling scheme.

    1. Log in to the Anti-DDoS Console, select Intelligent Scheduling > Domain Name List on the left sidebar, and click Create Intelligent Scheduling. Then, a CNAME record will be generated automatically by the system.
    2. Locate the row of the CNAME record and click Add Anti-DDoS Instance to enter the intelligent scheduling editing page.
    3. On the intelligent scheduling editing page, the TTL value is 60s by default, which can range from 1s to 3,600s, and the default scheduling method is priority-based.
    4. Go to the "Add Anti-DDoS Instance" page, select an instance (Single IP, Multi-IP, Anti-DDoS Advanced or Anti-DDoS Ultimate instance) for which you want to set line priority, and then click OK.
    5. After the instance is selected, DNS will be enabled for its protective line by default. At this point, you can set the line priority.

    Samples

    Assume that you want to implement the following scheme: The business traffic will be scheduled to a BGP protective line first; if it is blocked due to attacks, the traffic will be automatically scheduled to a China Telecom protective line; if it is blocked too, the traffic will be scheduled to a China Unicom protective line; and after the BGP protective line is unblocked, the traffic will be scheduled to it automatically.
    To implement this scheduling scheme, set the priority of the BGP line in the protective instance to 1 and that of the China Telecom line to 2, and keep the priority of the China Unicom line unchanged.

    If you do not want the China Unicom protective line to be in the traffic scheduling scheme, click to disable DNS for it, and you can enable DNS again and set its priority when necessary. If you want to delete it from the current scheduling scheme, you can locate the row of its corresponding instance and click Unbind.

    Was this page helpful?

    Was this page helpful?

    • Not at all
    • Not very helpful
    • Somewhat helpful
    • Very helpful
    • Extremely helpful
    Send Feedback
    Help