Updated on 2024-06-14 GMT+08:00

Step 3: Locally Verifying the Website Service Configuration

After the configuration takes effect, AAD is expected to forward the packets sent to the high-defense IP address or AAD CNAME to the origin servers. To ensure service stability, you are advised to verify the configuration.

This section uses the Telnet tool as an example to describe how to locally verify the website service configuration.

Prerequisite

The domain name to be protected has been added to AAD.

Procedure

  1. Log in to the management console.
  2. Select a region in the upper part of the page, click in the upper left corner of the page, and choose Security & Compliance > Anti-DDoS Service. The Anti-DDoS Service Center page is displayed.
  3. In the navigation pane on the left, choose Advanced Anti-DDoS > Domain Name Access. The Domain Name Acess page is displayed.

    Figure 1 Domain name access

  4. In the CNAME column of the target domain name, click to copy the CNAME value of the domain name.
  5. Enable Telnet and run the following command to check the connectivity between the origin server and AAD:

    telnet Origin_server_IP_address 80

    Take the port 80 as an example.

    • If the connection setup is successful, you can Telnet to the public IP address from your local network environment.
    • If the connection setup fails, change your test network environment and try again. Some enterprises may have internal network constraints that cause the failure of the verification. For example, you can connect to the personal hotspot of your phone to verify the connectivity.

  6. Run the following command to check whether the configuration for connecting the domain name to AAD is correct:

    telnet the_CNAME_value_copied_in_4 80
    • If you can telnet the domain name, the configuration is correct.
    • If you fail to telnet the domain name, check whether the domain name parameters are correctly configured.

For details about how to verify whether WAF basic protection is enabled, see Testing WAF.