Compute
Elastic Cloud Server
Huawei Cloud Flexus
Bare Metal Server
Auto Scaling
Image Management Service
Dedicated Host
FunctionGraph
Cloud Phone Host
Huawei Cloud EulerOS
Networking
Virtual Private Cloud
Elastic IP
Elastic Load Balance
NAT Gateway
Direct Connect
Virtual Private Network
VPC Endpoint
Cloud Connect
Enterprise Router
Enterprise Switch
Global Accelerator
Management & Governance
Cloud Eye
Identity and Access Management
Cloud Trace Service
Resource Formation Service
Tag Management Service
Log Tank Service
Config
OneAccess
Resource Access Manager
Simple Message Notification
Application Performance Management
Application Operations Management
Organizations
Optimization Advisor
IAM Identity Center
Cloud Operations Center
Resource Governance Center
Migration
Server Migration Service
Object Storage Migration Service
Cloud Data Migration
Migration Center
Cloud Ecosystem
KooGallery
Partner Center
User Support
My Account
Billing Center
Cost Center
Resource Center
Enterprise Management
Service Tickets
HUAWEI CLOUD (International) FAQs
ICP Filing
Support Plans
My Credentials
Customer Operation Capabilities
Partner Support Plans
Professional Services
Analytics
MapReduce Service
Data Lake Insight
CloudTable Service
Cloud Search Service
Data Lake Visualization
Data Ingestion Service
GaussDB(DWS)
DataArts Studio
Data Lake Factory
DataArts Lake Formation
IoT
IoT Device Access
Others
Product Pricing Details
System Permissions
Console Quick Start
Common FAQs
Instructions for Associating with a HUAWEI CLOUD Partner
Message Center
Security & Compliance
Security Technologies and Applications
Web Application Firewall
Host Security Service
Cloud Firewall
SecMaster
Anti-DDoS Service
Data Encryption Workshop
Database Security Service
Cloud Bastion Host
Data Security Center
Cloud Certificate Manager
Edge Security
Situation Awareness
Managed Threat Detection
Blockchain
Blockchain Service
Web3 Node Engine Service
Media Services
Media Processing Center
Video On Demand
Live
SparkRTC
MetaStudio
Storage
Object Storage Service
Elastic Volume Service
Cloud Backup and Recovery
Storage Disaster Recovery Service
Scalable File Service Turbo
Scalable File Service
Volume Backup Service
Cloud Server Backup Service
Data Express Service
Dedicated Distributed Storage Service
Containers
Cloud Container Engine
SoftWare Repository for Container
Application Service Mesh
Ubiquitous Cloud Native Service
Cloud Container Instance
Databases
Relational Database Service
Document Database Service
Data Admin Service
Data Replication Service
GeminiDB
GaussDB
Distributed Database Middleware
Database and Application Migration UGO
TaurusDB
Middleware
Distributed Cache Service
API Gateway
Distributed Message Service for Kafka
Distributed Message Service for RabbitMQ
Distributed Message Service for RocketMQ
Cloud Service Engine
Multi-Site High Availability Service
EventGrid
Dedicated Cloud
Dedicated Computing Cluster
Business Applications
Workspace
ROMA Connect
Message & SMS
Domain Name Service
Edge Data Center Management
Meeting
AI
Face Recognition Service
Graph Engine Service
Content Moderation
Image Recognition
Optical Character Recognition
ModelArts
ImageSearch
Conversational Bot Service
Speech Interaction Service
Huawei HiLens
Video Intelligent Analysis Service
Developer Tools
SDK Developer Guide
API Request Signing Guide
Terraform
Koo Command Line Interface
Content Delivery & Edge Computing
Content Delivery Network
Intelligent EdgeFabric
CloudPond
Intelligent EdgeCloud
Solutions
SAP Cloud
High Performance Computing
Developer Services
ServiceStage
CodeArts
CodeArts PerfTest
CodeArts Req
CodeArts Pipeline
CodeArts Build
CodeArts Deploy
CodeArts Artifact
CodeArts TestPlan
CodeArts Check
CodeArts Repo
Cloud Application Engine
MacroVerse aPaaS
KooMessage
KooPhone
KooDrive

Step 4: Modify the DNS Records of the Domain Name

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

After a domain name is connected to WAF, WAF functions as a reverse proxy between the client and server. The real IP address of the server is hidden, and only the IP address of WAF is visible to web visitors. You must point the DNS resolution of the domain name to the CNAME record provided by WAF. In this way, access requests can be resolved to WAF.

To ensure that your WAF instance works properly, test it according to the instructions in Step 3: Test WAF before routing your business traffic to WAF.

Prerequisites

Constraints

WAF protection takes effect only for real client IP addresses where requests originate. To ensure that WAF obtains real client IP addresses, if your website has layer-7 proxies such as CDN and cloud acceleration products deployed in front of WAF, Yes must be selected for Proxy Configured.

Specification Limitations

After your website is connected to WAF, you can upload a file no larger than 10 GB each time.

How WAF Works

  • No proxy used

    DNS resolves your domain name to the origin server IP address before the site is connected to WAF. DNS resolves your domain name to the CNAME of WAF after the site is connected to WAF. Then WAF inspects the incoming traffic and filters out malicious traffic.

  • A proxy (such as anti-DDoS service) used

    If a proxy such as anti-DDoS service is used on your site before it is connected to WAF, DNS resolves the domain name of your site to the anti-DDoS IP address. The traffic goes to the anti-DDoS service and the anti-DDoS service then routes the traffic back to the origin server. After you connect your website to WAF, change the back-to-source address of the proxy (such as anti-DDoS service) to the CNAME of WAF. In this way, the proxy forwards the traffic to WAF. WAF then filters out illegitimate traffic and only routes legitimate traffic back to the origin server.

    NOTE:
    • To ensure that WAF can properly forward requests, test WAF by referring to Testing WAF before modifying the DNS configuration.
    • To prevent other users from configuring your domain names on WAF in advance (this will cause interference on your domain name protection), add the subdomain name and TXT record on your DNS management platform. WAF can determine which user owns the domain name based on the subdomain name and TXT record.

Operation Guide

After a domain name is added, WAF generates a CNAME record, or CNAME, subdomain name, and TXT record for DNS to resolve the domain name to WAF so that website traffic can pass through WAF for detection. For details, see Table 1.

Table 1 Operation guide

Scenario

Generated Parameter Value

Operation Related to Domain Name Resolution

No proxy used

CNAME

The DNS obtains the CNAME of WAF.

Proxy used

CNAME, subdomain name, and TXT record

  • Change the back-to-source IP address of the proxy, such as anti-DDoS service, to the CNAME of WAF.
  • (Optional) Add a WAF subdomain name and TXT record at your DNS provider.

Procedure

  1. Log in to the management console.
  2. Click in the upper left corner of the management console and select a region or project.
  3. Click in the upper left corner and choose Security > Web Application Firewall to go to the Dashboard page.
  4. In the navigation pane on the left, choose Website Settings.
  5. In the row containing the desired domain name, click the domain name to go to the Basic Information page.
  6. In the CNAME row, click to copy the CNAME record.

    If the message "CNAME copied successfully" is displayed in the upper right corner of the page, the CNAME record is copied successfully.

  7. Connect the domain name to WAF.

    • No proxy used

      Configure the CNAME record at your DNS provider. For details, contact your DNS provider.

    • Proxy used

      Change the back-to-source IP address of the used proxy, such as anti-DDoS and CDN services, to the copied CNAME record.

      NOTE:

      To prevent other users from configuring your domain names on WAF in advance (this will cause interference on your domain name protection), add the subdomain name and TXT record on your DNS management platform.

      1. Add Subdomain Name at the DNS provider and configure TXT Record for the subdomain name.

      WAF determines which user owns the domain name based on the configured Subdomain Name and TXT Record.

  8. Verify that the CNAME of the domain name has been configured.

    1. In Windows, choose Start > Run. Then enter cmd and press Enter.
    2. Run a nslookup command to query the CNAME record.

      If the configured CNAME is returned, the configuration is successful.

      Example command:

      nslookup www.example.com

Follow-up Procedure

  • If your server uses other network firewalls, disable these network firewalls or add the WAF IP address range to the IP address whitelist of these network firewalls. Otherwise, these firewalls may regard the WAF IP address as a malicious IP address.
  • If your web server is using personal security software, replace it with enterprise security software and whitelist the WAF IP address ranges.

Verification

  • By default, WAF detects the Access Status of each protected domain name on an hourly basis.
  • Generally, if you have performed domain connection and Access Status is Accessible, the domain name is connected to WAF.

We use cookies to improve our site and your experience. By continuing to browse our site you accept our cookie policy. Find out more

Feedback

Feedback

Feedback

0/500

Selected Content

Submit selected content with the feedback