All Products
Search
Document Center

Edge Security Acceleration:UpdateSiteVanityNS

Last Updated:Jan 14, 2026

Updates the custom nameserver names for a single website.

Debugging

You can run this interface directly in OpenAPI Explorer, saving you the trouble of calculating signatures. After running successfully, OpenAPI Explorer can automatically generate SDK code samples.

Authorization information

The following table shows the authorization information corresponding to the API. The authorization information can be used in the Action policy element to grant a RAM user or RAM role the permissions to call this API operation. Description:

  • Operation: the value that you can use in the Action element to specify the operation on a resource.
  • Access level: the access level of each operation. The levels are read, write, and list.
  • Resource type: the type of the resource on which you can authorize the RAM user or the RAM role to perform the operation. Take note of the following items:
    • For mandatory resource types, indicate with a prefix of * .
    • If the permissions cannot be granted at the resource level, All Resources is used in the Resource type column of the operation.
  • Condition Key: the condition key that is defined by the cloud service.
  • Associated operation: other operations that the RAM user or the RAM role must have permissions to perform to complete the operation. To complete the operation, the RAM user or the RAM role must have the permissions to perform the associated operations.
OperationAccess levelResource typeCondition keyAssociated operation
esa:UpdateSiteVanityNSnone
*Site
acs:esa:{#regionId}:{#accountId}:site/{#SiteId}
    none
none

Request parameters

ParameterTypeRequiredDescriptionExample
SiteIdlongYes

The website ID. You can call the ListSites operation to obtain the ID.

1234567890123
VanityNSListstringNo

The custom nameserver names. You can specify two to five custom nameserver names. Separate multiple names with commas (,).

ns1.example.com,ns2.example.com

Response parameters

ParameterTypeDescriptionExample
object

Schema of Response

RequestIdstring

The request ID.

0AEDAF20-4DDF-4165-8750-47FF9C1929C9

Examples

Sample success responses

JSONformat

{
  "RequestId": "0AEDAF20-4DDF-4165-8750-47FF9C1929C9"
}

Error codes

HTTP status codeError codeError messageDescription
400InvalidParameterThe specified parameter is invalid.The specified parameter is invalid.
400ApplyVanityNSErrorFailed to apply for vanity NS resources. Please contact customer service.Failed to apply for vanity NS resources. Please contact customer service.
400OperationDenied.VanityNSUnavailableOnly sites in NS access type can use vanity nameservers. Convert your site to NS access type and try again.Sites that are accessed only by NS mode can use custom NS. Please adjust your site access mode and try again.
400InvalidParameter.InvalidVanityNSNumEnter 2 to 5 vanity nameservers. Correct them and try again.Custom NS requires 2~5 names, please adjust and resubmit.
400InvalidParameter.InvalidVanityNSNameA vanity nameserver must be an absolute domain name. Correct it and try again.You need to enter the full domain name to customize the NS name. Please adjust and submit it again.
400InvalidParameter.VanityNSNameDuplicateThe vanity nameservers are duplicated. Please delete it and try again.Duplicate custom NS name exists, please delete and resubmit.
400InternalExceptionFailed to call the service. Try again later or contact technical support.Failed to call the service. Try again later or contact technical support.
400Instance.NotOnlineYour plan is unavailable due to an overdue payment. Complete the payment first.Your plan is unavailable due to an overdue payment. Complete the payment first.
400QuotaCheckFailed.CustomNSCustom nameservers are not allowed in your plan. Check the plan description and upgrade the plan.Custom nameservers are not allowed in your plan. Check the plan description and upgrade the plan.
400Site.ServiceBusyThis website is being configured. Try again later.This website is being configured. Try again later.
400Record.ConflictThe specified record content conflicts with existing records. Adjust your configurations based on the related product documentation.The specified record content conflicts with existing records. Adjust your configurations based on the related product documentation.
400InvalidParameter.RecordsExceedLimitThe number of incoming records exceeds the maximum limit.The number of incoming records exceeds the maximum limit.

For a list of error codes, visit the Service error codes.

Change history

Change timeSummary of changesOperation
2025-12-01The Error code has changedView Change Details
2024-11-05The Error code has changedView Change Details
2024-09-18The Error code has changedView Change Details