Overview of Domain Name Access

Background

As online services expand, websites, web applications, and APIs face increasingly sophisticated cyber threats, including DDoS attacks, CC attacks, malicious bots, SQL injection, and web tampering. These security risks directly impact service availability, data security, and user experience. Building a distributed security architecture at edge nodes has become essential to ensuring service stability. Within this architecture, configuring domain name access is the foundational step that enables end-to-end protection.

Configuring Domain Name Access

Configuring domain name access associates a registered, ICP-licensed service domain name with the EIP of a target server through DNS resolution. This establishes a precise mapping between the domain name and backend service resources, enabling external users to access websites, application systems, and service APIs using easy-to-remember domain names. In addition to basic service deployment, this step is a critical prerequisite for deploying protection, scheduling traffic, and scrubbing traffic. Only after the domain name is bound to the target resource can the protection system accurately identify and protect incoming traffic.

Before enabling EdgeSec, you must connect the service domain name to the edge security platform and associate it with the protection service so traffic can be diverted to edge security nodes. From there, you can configure security policies, including anti-DDoS, CC attack protection, access control, web application protection, IP address blacklist and whitelist, and bot behavior management as needed. These policies intercept and scrub malicious traffic at edge nodes before it reaches the origin server. This builds a distributed, highly reliable, and low-latency defense that ensures continuous, stable service operations.