Some attackers may record real server IP history, and the exposed IPs allow them to bypass Anti-DDoS Pro and directly attack your real server. In this case, we recommend that you change the real server IP.
Before changing the real server IP, you can refer to this document to check the risk factors to prevent the new IP from disclosure.
Checklist
Checking DNS records
Check all DNS records of the attacked real server IP, including the DNS records of subdomain names, MX (Mail Exchanger) records, and NS (Name Server) records. Make sure all these records are configured to point to the Anti-DDoS Advanced IP, so that the DNS is not resolving to the new real server IP directly.
Checking for information disclosure and command execution vulnerabilities
Check websites or business systems for possible information disclosure vulnerabilities, such as phpinfo() disclosure and sensitive information leakage on Github.
Check websites or business systems for command execution vulnerabilities.
Checking for trojans and backdoors
Check the real server for potential trojans, backdoors, and other hidden dangers.
Other suggestions
To prevent attackers from scanning the C range or other similar IP ranges, do not use the same IP or an IP similar to the old IP as the new real server IP.
We recommend you prepare the backup linkage and the backup IP in advance.
We recommend you set the scope of access sources to prevent malicious scanning.