This document describes how to connect a website business to an Anti-DDoS Advanced instance and verify the forwarding configuration.
Currently, only website businesses in Beijing, Shanghai, and Guangzhou regions can be connected. Businesses outside Mainland China are not supported.
Business Scenario | Relevant Operation |
---|---|
Websites supporting only HTTP | Select **HTTP**. |
Websites supporting only HTTPS |
|
To prevent business interruption that occurs if the real server blocks the Anti-DDoS Advanced forwarding IP, you are recommended to configure allowlist policies for the real server infrastructure (such as firewall, web application firewall, intrusion protection system (IPS), and traffic management system) and disable the protection features of the server firewall and other security software tools (such as Safedog) or set allowlist policies for them, so that the forwarding IP will not be affected by the security policies of the real server.
You can log in to the new Anti-DDoS Advanced Console and click Instance List on the left sidebar to find the target instance ID.
Click the instance ID to enter the basic information page and view the Anti-DDoS Advanced forwarding IP range.
After the forwarding configuration is completed, the Anti-DDoS Advanced IP will forward the packets from the relevant port to the corresponding real server port according to the forwarding rule.
To ensure the stability of your business, a local test is recommended. The verification method is as follows:
Modify the local hosts
file to direct local requests to the protected site to your Anti-DDoS Advanced instance. The following uses Windows as an example to describe how to configure the local hosts
file:
Open the hosts
file in C:\Windows\System32\drivers\etc
and add the following content at the end of the file:
<Anti-DDoS Advanced IP address> <Domain name of the protected website>
For example, if the Anti-DDoS Advanced IP is 10.1.1.1
and the domain name is www.qq.com
, then add:
10.1.1.1 www.qqq.com
Save the hosts
file and run the ping
command on the local computer to ping the protected domain name. If the resolved IP address is the Anti-DDoS Advanced IP address bound in the hosts
file, the local hosts
configuration has taken effect.
If the resolved IP address is still the real server IP address, try running the
ipconfig /flushdns
command in Windows Command Prompt to clear the local DNS cache.
After successfully configuring the hosts
, check whether the domain name can be accessed. If it can be accessed properly, the configuration has taken effect.
If the verification still fails with the correct method, please log in to the Anti-DDoS Advanced Console and check whether the configuration is correct. If the problem persists after you fix any incorrect configuration items, please submit a ticket for assistance.
Was this page helpful?