Problem description
The custom domain name configured for bucket protection is not mapped to the bucket.
Causes
You initiated an InitBucketAntiDDosInfo or UpdateBucketAntiDDosInfo request, and used the Cnames node in the XML request body to specify the domain names that you want to protect. However, at least one of the domain names is not mapped to the bucket.
Examples
For example, you initiate the following request:
PUT /?antiDDos HTTP/1.1
Date: GMT Date
Host: TargetBucket.oss-cn-hangzhou.aliyuncs.com
Authorization: SignatureValue
x-oss-defender-instance: cbcac8d2-4f75-4d6d-9f2e-c3447f73****
x-oss-defender-type: AntiDDosPremimum
<AntiDDOSConfiguration>
<Cnames>
<Domain>abc1.example.cn</Domain>
</Cnames>
</AntiDDOSConfiguration>An error is returned because the domain name abc1.example.cn is not mapped to the bucket.
Solutions
Make sure that all custom domain names are mapped to the bucket. For more information, see Map custom domain names.
