This document shows you how to connect non-website applications to Anti-DDoS Advanced instances and verify forwarding configurations.
Anti-DDoS Advanced does not support ports 1433, 1434, 3306, 3389, 36000, and 56000. Port 843 is supported in the Guangzhou and Beijing regions.
18.104.22.168 50. If a domain name corresponds to multiple pairs of real server IP + weight, you can enter all of them and separate them with carriage return. Up to 20 entries are supported.
The weight ranges from 1 to 100.
- From left to right, paste the forwarding protocol, forwarding port, real server port, real server IP, and weight (or forwarding domain name); separate each one with a space; only one forwarding rule can be entered per line.
- The number of forwarding rule entries added in batches cannot exceed the current quota. Within the quota limit, up to 30 entries can be imported at a time.
To prevent the service unavailability that occurs when the real server blocks Anti-DDoS Advanced's forwarding IP, we recommend configuring allowlist policies for the real server infrastructure, including firewall, Web Application Firewall, intrusion prevention system (IPS), and traffic management, and disabling the protection feature of the host firewall and other security software (such as Safedog) or setting allowlist policies, so that the forwarding IP will not be affected by the security policies of the real server.
To view the detailed Anti-DDoS Advanced forwarding IP range, you can log in to the Anti-DDoS console, click Anti-DDoS Advanced -> Resource List on the left sidebar, find the row of the target Anti-DDoS Advanced instance, and click its ID/Name.
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 by following the forwarding rules.
To ensure the stability of your business, a local test is recommended. The verification methods are as follows:
For applications accessed via IPs
For applications accessed via IPs (such as games), run
telnet to check whether the Anti-DDoS Advanced port is accessible. You can also enter the Anti-DDoS Advanced IP as the server IP in your local client (if available) to check whether the local client can access the Anti-DDoS Advanced IP.
For example, the Anti-DDoS Advanced IP is
10.1.1.1 with the forwarding port 1234. And the real server IP is
10.2.2.2 with the real server port 1234. Run
telnet on your local client to connect to
10.1.1.1:1234. If the address can be accessed, it means that the forwarding is successful.
For applications accessed via domain names
For applications accessed via domain names, please try the followings:
Modify your local
hosts file to direct local requests to the protected website to the Anti-DDoS Advanced IP.
Take Windows operating system as an example:
C:\Windows\System32\drivers\etc, and add the following content at the end of the text:
<Anti-DDoS Advanced IP address> <Domain name of the protected website>
10.1.1.1and the domain name is
ping command on the local computer to test the protected domain name.
If the resolved IP address is the Anti-DDoS Advanced IP address bound in the
hosts file, the forwarding is successful.
If the resolved IP address is still the real server IP address, try running the
ipconfig/flushdnscommand in the Windows Command Prompt to clear the local DNS cache.
After successful configuration of
hosts, check whether the domain name can be accessed.
If yes, the configuration has taken effect.
If the verification still fails with the correct method, please log in to the Anti-DDoS console and check whether the configuration is correct. If the problem persists after you fix any incorrect configuration items, please contact Tencent Cloud technical support.
Before using Anti-DDoS Advanced, you need to configure the A record of your business domain name's DNS with an Anti-DDoS Advanced IP, so that all user access requests to your site will pass through Anti-DDoS Advanced first before arriving at the real server (that is, all traffic will be first directed to Anti-DDoS Advanced before getting to the real server).
The principle of domain name resolution configuration is consistent, but the configuration methods in different service providers may be different. Here the Tencent Cloud DNSPod is used.