错误码
|
HTTP status code |
错误码 |
错误信息 |
描述 |
操作 |
| addRRfail | 添加解析记录失败! | 诊断 | ||
| addSoafail | 创建域名失败 | 诊断 | ||
| 400 | Alidns.InvalidPostBusinessStatus | Invalid post business status. | 云解析后付费服务状态无效 | 诊断 |
| 400 | Alidns.PostBusinessNotOpened | Post business not opened. | 云解析后付费服务已开通 | 诊断 |
| 400 | Alidns.PostBusinessOpened | Post business opened. | 云解析后付费服务未开通 | 诊断 |
| 400 | Alidns.Ptr.Exist | alidns ptr is exist. | PTR记录已存在 | 诊断 |
| 400 | Alidns.Ptr.InvalidBusinessStatus | The ptr business status is invalid. | PTR 付费状态无效 | 诊断 |
| 400 | Alidns.Ptr.InvalidEndDate | The ptr end date is invalid. | PTR 结束时间参数无效 | 诊断 |
| 400 | Alidns.Ptr.InvalidName | The ptr name is invalid. | PTR 记录名称无效 | 诊断 |
| 400 | Alidns.Ptr.InvalidParam | The ptr param is invalid. | PTR 记录参数无效 | 诊断 |
| 400 | Alidns.Ptr.InvalidStartDate | The ptr start date is invalid. | PTR 起始时间参数无效 | 诊断 |
| 400 | Alidns.Ptr.InvalidValue | The ptr value is invalid. | PTR 记录值参数无效 | 诊断 |
| 400 | Alidns.Ptr.IpAddressNotExist | alidns ptr ipAddress is not exist. | PTR ip地址参数不存在 | 诊断 |
| 400 | Alidns.Ptr.IpInfoNotMatch | The ptr ip info is not match. | PTR ip信息不匹配,可能当前ip已经不属于当前用户 | 诊断 |
| 400 | Alidns.Ptr.NotExist | alidns ptr is not exist. | PTR记录不存在 | 诊断 |
| 400 | Alidns.Ptr.RecordSetNotExist | alidns ptr record set is not exist. | PTR记录集不存在 | 诊断 |
| 400 | Alidns.Ptr.UserIdNotExist | alidns ptr userId is not exist. | PTR 用户id参数不存在 | 诊断 |
| AliyunDomainAddedByOthers | 该域名非本账户域名 | 诊断 | ||
| AliyunDomainAddedByOthers | The domain name does not belong to the current user. | 该域名非本账户域名 | 诊断 | |
| Authentication.domain | 需要通过域名持有者身份验证,才可以进行添加。 点击这里验证身份 | 诊断 | ||
| BatchOperation.illegal | 批量操作参数非法 | 诊断 | ||
| BatchOperation.illegal | The specified BatchOperation is invalid. | 批量操作参数非法 | 诊断 | |
| BatchOperation.timeout | 批量导入系统繁忙,请稍后重试! | 诊断 | ||
| Binding.Error | 绑定错误 | 诊断 | ||
| Binding.Error | An error occured while binding. | 绑定错误 | 诊断 | |
| 400 | CacheReserveDomain.EffectiveScopeEmpty | Effective scope is empty. | 缓存保持域名没有关联生效范围 | 诊断 |
| CancelOrderFailed | 作废订单失败。 | 诊断 | ||
| chgRRfail | 修改解析记录失败 | 诊断 | ||
| CHNDomainInfoNotMatch | 该域名与注册局域名信息库不匹配,无法添加,请输入全简体域名或全繁体域名。 | 诊断 | ||
| CloseDnsSlbFailed | 关闭 加权轮询 失败 | 诊断 | ||
| 400 | CloudGtm.Address.AvailableModeInvalid | gtm address availableMode is invalid. | 地址的“探测异常切换方式”参数配置错误 | 诊断 |
| 400 | CloudGtm.Address.AvailableStatusInvalid | gtm address availableStatus is invalid. | 地址手动切换方式下的“地址状态”参数配置错误 | 诊断 |
| 400 | CloudGtm.Address.DispatchTypeNotMatchMonitorTemplate | the address dispatchType is not match for the monitor template. | 地址的“地址类型”与所选的探测模板的“探测类型”冲突 | 诊断 |
| 400 | CloudGtm.Address.EnableParamInvalid | gtm address enable param is invalid. | 地址的“启用状态”参数配置错误 | 诊断 |
| 400 | CloudGtm.Address.EnableStatusInvalid | gtm address enableStatus is invalid. | 地址的“启用状态”参数配置错误 | 诊断 |
| 400 | CloudGtm.Address.ExcessMaxBeReferencedCount | excess max be referenced count. | 地址的被引用次数已超过允许的最大限额 | 诊断 |
| 400 | CloudGtm.Address.HasExsited | gtm address has exsited. | 已存在相同名称的地址 | 诊断 |
| 400 | CloudGtm.Address.HasInstanceConfigReference | gtm address has instanceConfig reference. | 地址存在实例的关联引用 | 诊断 |
| 400 | CloudGtm.Address.HealthJudgementInvalid | gtm address healthJudgement is invalid. | 地址的“健康状态判定条件”参数配置错误 | 诊断 |
| 400 | CloudGtm.Address.InnerIpCanNotHasMonitorTask | the inner IP address can not has monitor task | 内网地址不允许配置监控探测任务 | 诊断 |
| 400 | CloudGtm.Address.ManualAvailableParamInvalid | gtm address manual available param is invalid. | 地址手动切换方式的参数配置错误 | 诊断 |
| 400 | CloudGtm.Address.MonitorTaskQuotaExceed | gtm monitor task in address quota exceed. | 地址配置的探测任务数超过地址配额 | 诊断 |
| 400 | CloudGtm.Address.NameConflict | gtm address name is conflict. | 已存在相同名称的地址 | 诊断 |
| 400 | CloudGtm.Address.NameSearchConditionParamInvalid | gtm address param nameSearchCondition is invalid. | 查询地址的“地址名称”参数错误。 | 诊断 |
| 400 | CloudGtm.Address.NotExsit | gtm address is not exist. | 未找到符合条件的地址 | 诊断 |
| 400 | CloudGtm.Address.QuotaExceed | gtm address quota exceed. | 地址的数量已经超过了允许的最大限额 | 诊断 |
| 400 | CloudGtm.Address.ReferenceStandardInstanceUseUltimateQuota | gtm address reference standardInstance use ultimate quota. address:%s. | 地址所引用的探测模板配置参数与其所关联的实例套餐版本冲突。地址Id:%s | 诊断 |
| 400 | CloudGtm.Address.RemarkSearchConditionParamInvalid | gtm address param remarkSearchCondition is invalid. | 查询地址的“备注”参数错误。 | 诊断 |
| 400 | CloudGtm.Address.TypeConflictWithAddressPoolType | gtm address type is conflict with address pool type. | 地址类型与地址池类型冲突. | 诊断 |
| 400 | CloudGtm.Address.TypeInvalid | gtm address type is invalid. | 地址的“地址类型”参数配置错误 | 诊断 |
| 400 | CloudGtm.Address.ValueDomainFormatInvalid | the DOMAIN address value format is invalid. | 输入的域名地址格式不正确 | 诊断 |
| 400 | CloudGtm.Address.ValueFormatInvalid | the IPv6 address value format is invalid. | 输入的IPv6地址格式不正确 | 诊断 |
| 400 | CloudGtm.Address.ValueFormatInvalid | the IPv4 address value format is invalid. | 输入的IPv4地址格式不正确 | 诊断 |
| 400 | CloudGtm.Address.ValueIpv4FormatInvalid | the IPv4 address value format is invalid. | 地址的IPv4地址值不合法 | 诊断 |
| 400 | CloudGtm.Address.ValueIpv6FormatInvalid | the IPv6 address value format is invalid. | 地址的IPv6地址值不合法 | 诊断 |
| 400 | CloudGtm.AddressPool.AddressReferenceSerialNumberInvalid | address serial number is invalid. | 地址顺序号无效 | 诊断 |
| 400 | CloudGtm.AddressPool.ExceedMaxCount | address pool exceed max count. | 地址池数量超过最大数量限制。 | 诊断 |
| 400 | CloudGtm.AddressPool.ExcessMaxBeReferencedCount | excess max be referenced count. | 地址池的被引用次数已超过允许的最大限额 | 诊断 |
| 400 | CloudGtm.AddressPool.NameDuplicate | gtm addressPool name duplicate. | 已存在相同名称的地址池 | 诊断 |
| 400 | CloudGtm.AddressPool.NotExist | gtm addressPool not exist. | 地址池不存在 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamAddressDuplicate | address duplicate. | 已存在相同的地址 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamAddressPoolTypeInvalid | address pool type invalid. | 地址池配置的“地址池类型”参数配置错误 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamAvailableStatusInvalid | available status invalid. | 可用性状态参数无效 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamEnableStatusInvalid | enable status invalid. | 地址池配置的“启用状态”参数配置错误 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamExcessMaxAddress | excess max address count. | 地址池引用的地址数量已超过允许的最大限额 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamHealthJudgementInvalid | health judgement invalid. | 地址池配置的“地址池健康状态判定条件”参数配置错误 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamHealthStatusInvalid | health status invalid. | 健康状态参数无效。 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamRequestSourceInvalid | request source invalid. | 地址池来源就近策略的“请求来源”参数配置错误 | 诊断 |
| 400 | CloudGtm.AddressPool.ParamWeightInvalid | weight invalid. | 地址池引用地址的权重值无效。 | 诊断 |
| 400 | CloudGtm.AddressPool.SameEnableStatus | same enable status. | 地址池的启用状态保持原状,未进行任何更改 | 诊断 |
| 400 | CloudGtm.AddressPool.TypeConflictWithLbStrategy | gtm address pool type is conflict with lb strategy. | 接入域名引用了多种类型地址池,与该域名配置的负载均衡策略冲突 | 诊断 |
| 400 | CloudGtm.AddressPool.TypeConflictWithScheduleRrType | address pool type is conflict with schedule rr type. | 地址池类型与调度域名类型冲突。 | 诊断 |
| 400 | CloudGtm.AlertLog.ParamInvalid | AlertLog Param is Invalid. | 告警日志参数错误 | 诊断 |
| 400 | CloudGtm.AlertNotify.ParamInvalid | AlertNotify Param is Invalid. | 告警通知参数错误 | 诊断 |
| 400 | CloudGtm.GlobalAlert.NotExist | global alert not exist. | 全局告警配置不存在 | 诊断 |
| 400 | CloudGtm.GlobalAlert.ParamAlertGroupExceedMaxLength | alert group exceed max length. | 全局告警配置“报警通知组”整体字符已经超过了允许的最大限额 | 诊断 |
| 400 | CloudGtm.Instance.ChargeTypeDoesNotMatch | The charge type of instance does not match. | 实例的付费类型不匹配 | 诊断 |
| 400 | CloudGtm.Instance.MonitorTaskQuotaExceed | gtm monitor task in instance quota exceed. | 配置的探测任务数量超过了实例的配额。 | 诊断 |
| 400 | CloudGtm.Instance.NameDuplicate | gtm instance name duplicate. | gtm实例名称重复了 | 诊断 |
| 400 | CloudGtm.Instance.NotExist | gtm instance not exist. | GTM实例不存在 | 诊断 |
| 400 | Cloudgtm.Instance.ScheduleDomainExcessMaxCount | schedule domain excess max count. | 实例下的接入域名数量超过限制 | 诊断 |
| 400 | CloudGtm.Instance.ScheduleDomainExcessMaxCount | schedule domain excess max count . | 实例下的接入域名数量超过限制 | 诊断 |
| 400 | Cloudgtm.instanceConfig.addressPoolReferenceSerialNumberInvalid | address pool serial number is invalid. | 地址池顺序号无效 | 诊断 |
| 400 | CloudGtm.instanceConfig.addressPoolReferenceSerialNumberInvalid | address pool serial number is invalid . | 地址池顺序号无效 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ExceedMaxCount | instance config exceed max count. | 接入域名数量超过最大数量限制。 | 诊断 |
| 400 | CloudGtm.InstanceConfig.HasExist | gtm instance config has exist. | 已存在相同的域名实例配置 | 诊断 |
| 400 | CloudGtm.InstanceConfig.NotExist | gtm instance config not exist. | GTM域名配置不存在 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamAddressPoolDuplicate | address pool duplicate. | 已存在相同的地址池 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamAlertGroupExceedMaxLength | alert Group Exceed Max Length. | 自定义报警配置“报警通知组”整体字符已经超过了允许的最大限额 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamAlertModeInvalid | alert mode invalid. | 域名实例配置的“报警通知模式”参数配置错误 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamAlertNoticeTypeInvalid | alert notice type invalid. | 域名实例配置的“报警事件类型”参数配置错误 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamAvailableStatusInvalid | available status invalid. | 可用性状态参数无效 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamEnableStatusInvalid | enable status invalid. | 域名实例配置的“启用状态”参数配置错误 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamExcessMaxAddressPool | excess max address pool. | 域名实例引用的地址池数量已超过允许的最大限额 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamHealthStatusInvalid | health status invalid. | 健康状态参数无效 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamLbStrategyInvalid | lb strategy invalid. | 域名实例配置的“负载策略”参数配置错误 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamRequestSourceInvalid | request source invalid. | 接入域名引用的地址池的请求来源无效。 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamScheduleRrTypeConflict | schedule rr type conflict. | 域名实例配置的“记录类型”冲突 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamScheduleRrTypeInvalid | schedule rr type invalid. | 域名实例配置的“记录类型”参数配置错误 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamScheduleZoneModeInvalid | schedule zone mode invalid. | 域名实例配置的接入域名模式无效 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamSequenceLbStrategyModeInvalid | sequence load balance Strategy mode invalid. | 域名实例顺序策略的“前序资源异常恢复服务模式”参数配置错误 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ParamWeightInvalid | weight invalid. | 接入域名引用的地址池的权重值无效。 | 诊断 |
| 400 | CloudGtm.InstanceConfig.SameEnableStatus | same enable status. | 域名实例的启用状态保持原状,未进行任何更改 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ScheduleDomainExpired | schedule domain is expired. | 域名实例配置的接入域名已过期 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ScheduleDomainGtmForbidden | schedule domain gtm forbidden. | 调度域名被GTM禁止操作。 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ScheduleDomainLockedForbidden | schedule domain is locked. | 实例配置接入域名被锁定 | 诊断 |
| 400 | Cloudgtm.InstanceConfig.ScheduleDomainNameLockedForbidden | schedule domain is locked. | 实例配置接入域名被锁定 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ScheduleDomainNotBelongToUser | schedule domain is not belong to user. | 域名实例配置的接入域名不归属当前用户 | 诊断 |
| 400 | CloudGtm.InstanceConfig.ScheduleDomainRiskControlForbidden | your account is at risk. contact customer support for more details.. | 域名实例配置接入域名存在安全风险,已被管控 | 诊断 |
| 400 | Cloudgtm.instanceConfig.scheduleDomainRistControlForbidden | your account is at risk. contact customer support for more details. | 实例配置接入域名的操作被风险控制系统禁止 | 诊断 |
| 400 | CloudGtm.Monitor.CmsTaskQuotaExceed | gtm monitor task quota exceed. | 探测任务数量已经超过了允许的最大限额 | 诊断 |
| 400 | CloudGtm.Monitor.CmsTaskQuotaUltimateExceed | gtm monitor task ultimate quota exceed. | 旗舰版域名实例配置的探测任务数量已经超过了允许的最大限额 | 诊断 |
| 400 | CloudGtm.Monitor.MonitorStatusInvalid | gtm monitor status invalid. | 探测任务状态值参数错误 | 诊断 |
| 400 | CloudGtm.Monitor.MonitorTaskCmsAlaramIdNotExsit | gtm monitor task cms alarm id not exist. | 探测任务的云监控的任务 ID 不存在 | 诊断 |
| 400 | CloudGtm.Monitor.MonitorTaskCmsAlaramIdNotExsit | gtm monitor task cms alaram id not exist. | GTM探测任务所关联的云监控任务ID无效 | 诊断 |
| 400 | CloudGtm.Monitor.MonitorTaskNotExsit | gtm monitor task not exist. | 未找到符合条件的探测模板 | 诊断 |
| 400 | CloudGtm.Monitor.NodeIpVersionNotSupport | gtm monitorNode not support this ip version. | 探测模板中配置的探测节点不支持模板设置的探测类型 | 诊断 |
| 400 | CloudGtm.Monitor.NodeIsDisable | gtm monitorNode is disable. | 探测模板中配置的探测节点已被禁用 | 诊断 |
| 400 | CloudGtm.Monitor.NodeNotExsit | gtm monitorNode is not exist. | 探测模板中配置的探测节点不存在 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateCodeInvalid | gtm monitorTemplate code is invalid. | 探测模板的“校验内容”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateCountInvalid | gtm monitorTemplate count is invalid. | 探测模板的数量已经超过了允许的最大限额 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateEffectiveMonitorNodesCountInvalid | gtm monitorTemplate effectiveMonitorNodes count is invalid. | 探测模板的“探测节点”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateEvaluationCountInvalid | gtm monitorTemplate evaluationCount is invalid. | 探测模板的“重试次数”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateExtendInvalid | gtm monitorTemplate extend is invalid. | 探测模板的"extend”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateFailureRateInvalid | gtm monitorTemplate failureRate is invalid. | 探测模板的“所选节点探测失败比例”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateFollowRedirectInvalid | gtm monitorTemplate followRedirect is invalid. | 探测模板的“跟随3XX重定向”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateHasExsited | gtm monitorTemplate has exsited. | 已存在相同名称的探测模板 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateHostInvalid | gtm monitorTemplate host is invalid. | 探测模板的“HOST设置”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateIntervalInvalid | gtm monitorTemplate interval is invalid. | 探测模板的“检查间隔”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateInUse | gtm monitorTemplate is still inUse. | 探测模板仍在使用中 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateIpVersionInvalid | gtm monitorTemplate ipVersion is invalid. | 探测模板的“探测类型”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateNameConflict | Gtm monitor template name is conflict. | 探测模板名称已存在 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateNameConflict | gtm monitorTemplate name is conflict. | 已存在相同名称的探测模板 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateNotExsit | Gtm monitor Template is not exist. | 未找到符合条件的探测模板 | 诊断 |
| 400 | CloudGtm.Monitor.TemplatePacketLossRateInvalid | gtm monitorTemplate packetLossRate is invalid. | 探测模板的“异常时丢包率”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplatePacketNumInvalid | gtm monitorTemplate packetNum is invalid. | 探测模板的“ICMP发送包数量”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplatePathInvalid | gtm monitorTemplate path is invalid. | 探测模板的“HTTP路径”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplatePortInvalid | gtm monitorTemplate port is invalid. | 地址的“服务端口”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateProtocolInvalid | gtm monitorTemplate protocol is invalid. | 探测模板的“探测协议”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateReferenceCountExceedLimit | gtm monitorTemplate reference count exceed limit. | 探测模板的被引用次数已超过允许的最大限额 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateReferenceInstanceUseUltimateQuota | gtm monitorTemplate reference standardInstance use ultimate quota. | 探测模板的配置参数与其所关联的实例套餐版本冲突 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateResponseContextInvalid | gtm monitorTemplate responseContext is invalid. | 探测模板的“应答内容”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateSniInvalid | gtm monitorTemplate sni is invalid. | 探测模板的“启用SNI”参数配置错误 | 诊断 |
| 400 | CloudGtm.Monitor.TemplateTimeoutInvalid | gtm monitorTemplate timeout is invalid. | 探测模板的“超时时间”参数配置错误 | 诊断 |
| 400 | CloudGtm.OperationForbidden.FusionControlled | The Global Traffic Management (GTM) has been locked. Please make modifications uniformly through the Fusion Cloud DNS Console. | 全局流量管理(GTM)已被锁定,请通过融合云控制台统一修改 | 诊断 |
| 400 | CloudGtm.Param.ScheduleDomainInvalid | schedule domain is invalid. | 调度域名无效。 | 诊断 |
| 400 | CloudGtm.PayOrderCallBack.OnlySupportCloudGtm | Payorder callback Only Support CloudGtm. | 新购/续费/升级回调暂不支持GTM 3.0 | 诊断 |
| 400 | CloudGtm.QuotaUsed.IncrParamInvalid | Increase QuotaUsed Param is INvalid. | 规格用量参数错误 | 诊断 |
| 400 | CloudGtm.Refund.OnlySupportCloudGtm | Refund Only Support CloudGtm. | 退款/退续费回调暂不支持GTM 3.0 | 诊断 |
| 400 | CloudGtm.Refund.ParamNewExpireTimeInvalid | gtm refund param newExpireTime is invalid. | CluodGtm退费参数newExpireTime错误 | 诊断 |
| 400 | CloudGtm.ScheduleDomainConflictWithAuthorityNsRecord | GTM scheduling domain name conflicts with authoritative NS record. | GTM调度域名与权威NS记录冲突。 | 诊断 |
| 400 | CloudMonitor.Alert.InvalidMonitorItem | The alert monitor item is invalid. | 探测任务的探测项错误 | 诊断 |
| 400 | CloudMonitor.Alert.InvalidMonitorItemStatus | The alert monitor item status is invalid. | 探测任务探测类型状态错误 | 诊断 |
| 400 | CloudMonitor.Alert.MonitorItemMonitorStatusDifferent | The alert monitor item same timestamp but different monitor status. | 探测项状态已经修改 | 诊断 |
| 400 | CloudMonitor.Alert.MonitorItemStatusDisable | The alert monitor item status is disable. | 探测任务未启用 | 诊断 |
| 400 | CloudMonitor.AlertConfig.alertGroupExceedMaxSize | Maximum number of selected alarm groups exceeded. | 选择报警组超过最大个数限制 | 诊断 |
| 400 | Cloudmonitor.AlertConfig.AlertGroupNotExists | The alarm group selected for alarm configuration does not exist. | 报警配置选择的报警组不存在 | 诊断 |
| 400 | CloudMonitor.AlertConfig.InvalidAlertCount | Same alarm repetition times parameter error. | 相同报警重复次数参数错误 | 诊断 |
| 400 | CloudMonitor.AlertConfig.InvalidAlertMode | The configuration method is incorrect. It can only be [Inherit Global] or [Custom]. | 配置方式错误,只能是【继承全局】、【自定义】 | 诊断 |
| 400 | CloudMonitor.AlertConfig.InvalidAlertNoticeType | The alarm notification method is invalid. | 报警通知方式错误,只能是监控任务探测异常、监控任务探测异常恢复 | 诊断 |
| 400 | CloudMonitor.InvalidUserId | User ID is invalid. | 用户ID错误。 | 诊断 |
| 400 | CloudMonitor.Probe.CityHasExisted | The probe city has existed. | 城市已经存在 | 诊断 |
| 400 | CloudMonitor.Probe.CityNotExisted | The probe city not existed. | 探针城市不存在 | 诊断 |
| 400 | CloudMonitor.Probe.CityOrderHasExisted | The probe city order has existed. | 城市展示顺序已经被占用 | 诊断 |
| 400 | CloudMonitor.Probe.HasExisted | Probe already exists when probe is created. | 创建探针时,探针已经存在 | 诊断 |
| 400 | CloudMonitor.Probe.InvalidCityCode | The probe city code is invalid. | 城市CODE错误 | 诊断 |
| 400 | CloudMonitor.Probe.InvalidIpVersion | The network protocol version of the monitoring node is incorrect. | 监控节点网络协议版本错误,只支持IPv4 | 诊断 |
| 400 | CloudMonitor.Probe.InvalidIspCode | The probe isp code is invalid. | 运营商CODE错误 | 诊断 |
| 400 | CloudMonitor.Probe.InvalidProbeStatus | Probe enable status is invalid. | 探针启用状态错误。 | 诊断 |
| 400 | CloudMonitor.Probe.InvalidTypeCode | The probe type code is invalid. | 监控探针类型错误 | 诊断 |
| 400 | CloudMonitor.Probe.IspHasExisted | The probe ISP has existed. | 运营商已经存在 | 诊断 |
| 400 | CloudMonitor.Probe.IspNotExisted | The probe isp not existed. | 探针运营商不存在 | 诊断 |
| 400 | CloudMonitor.Probe.IspOrderHasExisted | The probe isp order has existed. | 展示顺序已被占用 | 诊断 |
| 400 | CloudMonitor.Probe.NotExisted | Probe does not exist. | 探针不存在 | 诊断 |
| 400 | CloudMonitor.Probe.typeHasExisted | Monitor probe type already exists. | 监控探针类型已经存在 | 诊断 |
| 400 | CloudMonitor.Probe.TypeNotExisted | The probe type not existed. | 监控探针类型不存在 | 诊断 |
| 400 | CloudMonitor.Probe.typeOrderHasExisted | Monitoring probe display sequence number already exists. | 监控探针展示顺序号已经存在 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.HasExisted | The probe endpoint has existed. | Endpoint IP已经存在 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.InvalidDispatchStatus | The probe endpoint dispatch status is invalid. | 设置endpoint数据下发状态错误 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.InvalidEndpointStatus | The probe endpoint status is invalid. | 设置endpoint状态错误 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.InvalidPort | The probe endpoint port is invalid. | endpoint 地址端口格式不正确 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.InvalidPreloadId | The probe endpoint preload id is invalid. | 重点域名监控任务增量ID错误 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.InvalidPreloadStatus | The probe endpoint preload status is invalid. | 设置 CloudMonitor 探针Endpoint增量状态,设置的状态参数错误 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.Ipv4FormatInvalid | The probe endpoint IPv4 address value format is invalid. | IPv4协议的endpoint 地址格式不正确. | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.Ipv6FormatInvalid | The probe endpoint IPv6 address value format is invalid. | IPv6协议的endpoint 地址格式不正确 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.NeedDispatchStatusOffline | The probe endpoint need dispatch status offline. | endpoit数据下发状态需要置为offline状态 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.NeedDispatchStatusOnline | The probe endpoint need dispatch status online. | 数据下发endpoint时,endpoint下发状态需为online | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.NeedStatusOffline | The probe endpoint need status offline. | endpoit启用状态需要置为offline状态 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.NotExisted | The probe endpoint not existed. | Endpoint 不存在 | 诊断 |
| 400 | CloudMonitor.ProbeEndpoint.PreloadInRunning | There is already a running preload task for the probe endpoint. | 存在正在增量中的任务 | 诊断 |
| 400 | CloudMonitor.Task.InvalidAddress | The task address is invalid. | 探测任务地址不正确 | 诊断 |
| 400 | CloudMonitor.Task.InvalidCount | The task count is invalid. | 探测任务超过最大个数 | 诊断 |
| 400 | CloudMonitor.Task.InvalidEnableStatus | The task enable status is invalid. | 探测任务可用状态错误 | 诊断 |
| 400 | CloudMonitor.Task.InvalidId | The task id is invalid. | 探测任务不存在 | 诊断 |
| 400 | CloudMonitor.Task.InvalidMonitorExtend | The task monitor extend is invalid. | 探测任务配置错误 | 诊断 |
| 400 | CloudMonitor.Task.InvalidMonitorNsTamperConfig | The task monitor ns tamper config is invalid. | 域名NS篡改监控配置错误 | 诊断 |
| 400 | CloudMonitor.Task.InvalidMonitorResolveResultConfig | The task monitor resolve result config is invalid. | 解析结果监控配置错误 | 诊断 |
| 400 | CloudMonitor.Task.InvalidMonitorResolveTamperConfig | The task monitor resolve tamper config is invalid. | 自定义DNS服务器解析时延监控配置错误 | 诊断 |
| 400 | CloudMonitor.Task.InvalidName | The task name is invalid. | 探测任务名称格式不对 | 诊断 |
| 400 | CloudMonitor.Task.InvalidNetworkType | The task network type is invalid. | 选择的网络类型不对,应该是内网、公网 | 诊断 |
| 400 | CloudMonitor.Task.InvalidProbe | The task probe is invalid. | 探测任务探针错误 | 诊断 |
| 400 | CloudMonitor.Task.InvalidProtocol | The task protocol is invalid. | 探测任务协议错误 | 诊断 |
| 400 | CloudMonitor.Task.InvalidRemark | The task remark is invalid. | 探测任务备注格式错误 | 诊断 |
| 400 | CloudMonitor.Task.nameDuplicate | The task name is duplicate. | 探测任务名称重复 | 诊断 |
| 400 | CloudMonitor.Task.NotExists | The task does not exist. | 探测任务相关操作,探测任务不存在 | 诊断 |
| 400 | CloudMonitor.Task.ProbeDuplicate | The task probe is duplicate. | 探测任务探针配置重复 | 诊断 |
| 400 | CloudMonitor.Task.ProbeInvalidCount | The task probe count is invalid. | 探测任务探针总个数错误 | 诊断 |
| 400 | CloudMonitor.Task.ProbeInvalidNodeCount | The task probe node count is invalid. | 探测任务探针内节点个数错误 | 诊断 |
| 400 | CloudMonitor.Task.ProbeNotExisted | The task probe is not existed. | 探测任务探针不存在 | 诊断 |
| 400 | CloudMonitor.Task.ProbeOffline | The task probe is offline. | 探测任务探针已经下线 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.EnabledItemAtLeastOne | The task monitor config enabled item at least one. | 重点域名监控任务至少配置一个监控项。 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.ExpectedResolveResultDuplicate | The task monitor config expected resolve result is duplicate. | 解析结果监控期望解析结果重复 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidExpectedResolveResult | The task monitor config expected resolve result is invalid. | 期望解析结果配置错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidExpectedResolveResultCount | The task monitor config expected resolve result count is invalid. | 解析结果监控期望解析结果个数超过最大限制 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidItem | The task monitor config item is invalid. | 监控项错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidItemStatus | The task monitor config item status is invalid. | 探测任务启用状态错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidNsTamperEvaluationCount | The task monitor config ns tamper evaluation count is invalid. | 域名NS篡改监控重试次数错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidNsTamperInterval | The task monitor config ns tamper interval is invalid. | 域名NS篡改监控拨测配置错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidNsTamperIntervalByTimeout | The task monitor config ns tamper interval is invalid by timeout. | 域名NS篡改监控拨测超时时间不能小于拨测频率 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidNsTamperTimeout | The task monitor config ns tamper timeout is invalid. | 域名NS篡改监控超时时间错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidRecordType | The task monitor config record type is invalid. | 解析结果监控拨测域名记录类型错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveResCustomNsesCnt | The task monitor config resolve result custom nses count is invalid. | 自解析结果监控定义DNS服务器解析结果个数超过最大值 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveResIntervalTimeout | The task monitor config resolve result interval is invalid by timeout. | 解析结果监控探测频率时间大于超时时间 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveResultCustomNses | The task monitor config resolve result custom nses is invalid. | 解析结果监控自定义DNS服务器解析结果输入错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveResultInterval | The task monitor config resolve result interval is invalid. | 解析结果监控拨测频率错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveResultMatchRule | The task monitor config resolve result match rule is invalid. | 解析结果匹配规则错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveResultTimeout | The task monitor config resolve result timeout is invalid. | 解析结果监控超时时间错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveTamperInterval | The task monitor config resolve tamper interval is invalid. | 解析时延与TTL篡改监控:监控频率错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveTamperLatencyTtl | The task monitor config resolve tamper latency ttl is invalid. | 解析时延与TTL篡改监控:ttl设置错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveTamperTimeout | The task monitor config resolve tamper timeout is invalid. | 解析时延与TTL篡改监控:超时时间配置错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResolveTamperTtlCustomNses | The task monitor config resolve tamper ttl custom nses is invalid. | 解析时延与TTL篡改监控:自定义DNS服务器解析时延监控ttl错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidResultEvaluationCount | The task monitor config resolve result evaluation count is invalid. | 解析结果监控重试次数错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidTamperEvaluationCount | The task monitor config resolve tamper evaluation count is invalid. | 解析时延与TTL篡改监控:重复次数配置错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidTamperIntervalByTimeout | The task monitor config resolve tamper interval is invalid by timeout. | 解析时延与TTL篡改监控:超时时间错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidtamperLatencyCustomNsCnt | The task monitor config resolve tamper latency custom nses count is invalid. | 解析时延与TTL篡改监控:自定义DNS服务器解析时延监控服务个数超限制 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidTamperLatencyCustomNses | The task monitor config resolve tamper latency custom nses is invalid. | 解析时延与TTL篡改监控:自定义DNS服务器解析时延监控服务器配置错误 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.InvalidTamperTtlCustomNsesCount | The task monitor config resolve tamper ttl custom nses count is invalid. | 解析时延与TTL篡改监控:自定义DNS服务器解析时延监控重复 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.itemDuplicate | The task monitor config item is duplicate. | 监控项重复 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.itemEmpty | The task monitor config item is empty. | 监控项为空 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.itemMustIspDnsResolveConsistency | The task monitor config item must contains isp dns resolve consistency. | 探测节点本地运营商解析结果需要与预期结果一致 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.resolveResultCustomNsesDuplicate | The task monitor config resolve result custom nses is duplicate. | 解析结果监控自定义DNS服务器解析结果重复 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.tamperLatencyCustomNsesDuplicate | The task monitor config resolve tamper latency custom nses is duplicate. | 解析时延与TTL篡改监控:自定义DNS服务器解析时延监控输入的服务器重复 | 诊断 |
| 400 | CloudMonitor.TaskMonitorConfig.tamperTtlCustomNsesDuplicate | The task monitor config resolve tamper ttl custom nses is duplicate. | 解析时延与TTL篡改监控:自定义DNS服务器解析时延监控配置错误 | 诊断 |
| 400 | ClouGtm.AddressPool.TypeConflictWithLbStrategy | gtm address pool type is conflict with lb strategy. | 接入域名引用了多种类型地址池,与该域名配置的负载均衡策略冲突 | 诊断 |
| CreateOrderFailed | 创建订单失败 | 诊断 | ||
| 400 | Data.Log.ExceedReadDataMax | Maximum read limit exceeded. | 超过最大读取限制 | 诊断 |
| DataFormatError | 数据格式不正确 | 诊断 | ||
| DefaultlineNotadded | 没有添加过默认线路,请先添加默认线路。 | 诊断 | ||
| DeleteDomain.Empty | 域名不能为空,请选择域名。 | 诊断 | ||
| DeleteDomain.Empty | The domain name is required. Please select a domain name. | 域名不能为空,请选择域名。 | 诊断 | |
| delRRfail | 删除解析记录失败 | 诊断 | ||
| delSoafail | 删除域名失败! | 诊断 | ||
| DisableDNSSLB | 子域名未开启 加权轮询 | 诊断 | ||
| DisableDNSSLB | You have not enabled the weighted round robin for the subdomain. | 子域名未开启 加权轮询 | 诊断 | |
| 400 | DnsCache.Invalid.SourceIp | the source DNS server is invalid. Enter a domain name or an IPv4 address. | 源站DNS服务器 %s 错误,只能是域名或者IPv4地址。 | 诊断 |
| 400 | DnsCache.Invalid.SourceServer | The source DNS server is invalid. Enter a domain name or an IPv4 address. | 源站DNS服务器 %s 错误,只能是有效的域名或者IPv4地址。 | 诊断 |
| 400 | DnsCustomLine.Invalid.IP | The IP address range is incorrectly formatted. | IP地址段 %s 格式不正确 | 诊断 |
| 400 | DnsCustomLine.Invalid.IPOverlap | The IP address range overlaps with the existing IP address range. | IP地址段%s与已存在地址段%s重叠 | 诊断 |
| 400 | DnsCustomLine.Invalid.IPSegment | The IP address range is invalid. | IP地址段范围%s错误 | 诊断 |
| 400 | DnsCustomLine.IP.Exceeds | The maximum number of IP address ranges is exceeded. | IP地址段超过最大个数 %s. | 诊断 |
| 400 | DnsCustomLine.Number.Exceeds | The maximum number of custom lines is exceeded. | 自定义线路超过最大个数 %s. | 诊断 |
| DNSnotfound | 域名未分配DNS,请联系阿里云客服! | 诊断 | ||
| DnsSLB.InvalidType | The turn on/off option is not available for CNAME records. | CNAME记录无法使用[开启/关闭]功能 | 诊断 | |
| DnsTemplate.QuotaExceededTemplate | The number of templates exceeds the limit. | 解析模板个数超过最大限制。 | 诊断 | |
| 400 | Domain.Delete.Forbidden | Domain names are forbidden to be deleted. | 域名禁止被删除 | 诊断 |
| DomainAddedByOthers | 域名被其他账户添加 | 诊断 | ||
| DomainEmpty | 域名不能为空 | 诊断 | ||
| DomainEmpty | The domain name is required. | 域名不能为空 | 诊断 | |
| DomainExpiredDNSForbidden | 禁止操作:域名已过期,解析已被锁定。 | 诊断 | ||
| 400 | DomainLoggingSwitch.Duplicate | The logging switch is duplicate. | 日志开关重复 | 诊断 |
| 400 | DomainLoggingSwitch.InvalidPostBusinessStatus | Invalid post business status. | 云解析后付费服务状态无效 | 诊断 |
| 400 | DomainLoggingSwitch.InvalidStatus | The logging switch status is invalid. | 日志开关状态无效 | 诊断 |
| DomainNotFound | 域名不存在! | 诊断 | ||
| DomainNotFound | The domain name does not exist. | 域名不存在! | 诊断 | |
| DomainRecordConflict | 与其他记录冲突,不能添加 | 诊断 | ||
| DomainRecordDisable | 解析记录被暂停 | 诊断 | ||
| DomainRecordDisable | The DNS record is suspended. | 解析记录被暂停 | 诊断 | |
| DomainRecordDuplicate | 解析记录已存在 | 诊断 | ||
| DomainRecordLocked | 禁止操作:解析记录被锁定 | 诊断 | ||
| DomainRecordNotBelongToUser | 解析记录在本账户下不存在 | 诊断 | ||
| 400 | DomainRecordSvcbModeConflict | The type records have conflict between alias mode and service mode. | “%s”记录别名模式和服务模式冲突 | 诊断 |
| 400 | DomainTransfer.TransferredToOthers | This domain has been transferred to another account. | 该域名曾被转移到其他账号管理。 | 诊断 |
| 400 | EdgeDns.Alert.AccessKeyExceedMaxLength | Access key exceed max length. | AccessKey长度超过最大限制 | 诊断 |
| 400 | EdgeDns.Alert.AlertGeneralConfigNotExist | Alert general config not exist. | 告警基础配置不存在 | 诊断 |
| 400 | EdgeDns.Alert.AlertNotifyInvalidUserId | Alert notify invalid userId. | 无效的用户Id | 诊断 |
| 400 | EdgeDns.Alert.ContactsMustNotBeEmpty | Contacts must not be empty. | 邮件通知人不能为空 | 诊断 |
| 400 | EdgeDns.Alert.EmailAlertNotifyConfigInvalid | Email alert notify config invalid. | 邮件通知配置不合法 | 诊断 |
| 400 | EdgeDns.Alert.EmailContactsInvalid | Email contacts invalid. | 邮件联系人不合法 | 诊断 |
| 400 | EdgeDns.Alert.InvalidEmailUsername | Invalid email user name. | 邮箱名称不合法 | 诊断 |
| 400 | EdgeDns.Alert.InvalidSenderAddress | Invalid sender address. | 发件人地址不合法 | 诊断 |
| 400 | EdgeDns.Alert.InvalidSmtpServerAddress | Invalid smtp server address. | 无效的smtp服务地址 | 诊断 |
| 400 | EdgeDns.Alert.InvalidSyslogSendProtocol | Invalid syslog send protocol. | Syslog发送协议不合法 | 诊断 |
| 400 | EdgeDns.Alert.InvalidSyslogServerAddress | Invalid syslog server address. | Syslog服务器地址不合法 | 诊断 |
| 400 | EdgeDns.Alert.InvalidUsername | Invalid user name. | 用户名不合法 | 诊断 |
| 400 | EdgeDns.Alert.NotifyGatewayConfigNotExist | Notify gateway config not exist. | 通知网关配置不存在 | 诊断 |
| 400 | EdgeDns.Alert.SecretExceedMaxLength | Secret exceed max length. | 密码超过最大长度限制 | 诊断 |
| 400 | EdgeDns.Alert.SignatureExceedMaxLength | Signature exceed max length. | 签名超过最大长度限制 | 诊断 |
| 400 | EdgeDns.Alert.SmsAlertNotifyConfigInvalid | Sms alert notify config invalid. | 短信通知配置不合法 | 诊断 |
| 400 | EdgeDns.Alert.SmsContactsInvalid | Sms contacts invalid. | 短信联系人不合法 | 诊断 |
| 400 | EdgeDns.Alert.SmsTemplateCodeMustNotBeEmpty | Sms template code must not be empty. | 短信模版code不能为空 | 诊断 |
| 400 | EdgeDns.Alert.SyslogAlertNotifyConfigInvalid | Syslog alert notify config invalid. | Syslog告警通知配置不合法 | 诊断 |
| 400 | EdgeDns.Alert.WebhookAlertNotifyConfigInvalid | Webhook alert notify config invalid. | Webhook通知配置不合法 | 诊断 |
| 400 | EdgeDns.Alert.WebhookUrlMustNotBeEmpty | Webhook url must not be empty. | Webhook url不能为空 | 诊断 |
| 400 | EdgeDns.AppAgent.InvalidPlatform | The app agent platform is invalid. | 自建DNS软件平台不合法 | 诊断 |
| 400 | EdgeDns.AppAgent.InvalidVersion | The app agent version is invalid. | 自建DNS软件版本不合法 | 诊断 |
| 400 | EdgeDns.AppReleasedVersionNotExisted | The app released version not existed. | 自建DNS没有已经发布的软件版本 | 诊断 |
| 400 | EdgeDns.AppVersion.InvalidPlatform | The app version platform is invalid. | 自建DNS软件版本平台不合法 | 诊断 |
| 400 | EdgeDns.AppVersion.InvalidStatus | The app version status is invalid. | 自建DNS软件版本状态不合法 | 诊断 |
| 400 | EdgeDns.AppVersion.NotExisted | The app version not existed. | 自建DNS软件版本不存在 | 诊断 |
| 400 | EdgeDns.CallEdgeDnsServerFailed | Call edge dns server failed. | 调用自建DNS服务器失败。 | 诊断 |
| 400 | Edgedns.Cluster.AppVersionExpired | Edge dns cluster app version is expired. | 自建DNS集群软件版本已过期。 | 诊断 |
| 400 | EdgeDns.Cluster.BindCountExceedLimit | The number of clusters bound to the resource exceeds the limit. | 资源关联的自建DNS解析集群超过上限。 | 诊断 |
| 400 | EdgeDns.Cluster.CacheReserveDomainDuplicate | Edge dns cluster is bind to same domain name. | 自建DNS集群关联了同名的缓存保持域名。 | 诊断 |
| 400 | EdgeDns.Cluster.ExceedMaxCount | Cluster exceed max count. | 集群数量超过最大值 | 诊断 |
| 400 | Edgedns.Cluster.ForbiddenRetryResourceActionJob | Access forbidden to retry resource action job. | 已有进行中的数据同步任务,禁止重复提交。 | 诊断 |
| 400 | EdgeDns.Cluster.HasNodes | Cluster has nodes. | 集群下存在节点 | 诊断 |
| 400 | EdgeDns.Cluster.NameExist | Cluster name exist. | 集群名称已存在 | 诊断 |
| 400 | EdgeDns.Cluster.NameInvalid | Cluster name invalid. | 集群名称不合法 | 诊断 |
| 400 | EdgeDns.Cluster.NodeEmpty | The cluster node is empty. | 自建DNS集群下的节点列表为空,不能执行操作 | 诊断 |
| 400 | EdgeDns.Cluster.NoNodes | Cluster does not have nodes. | 自建DNS集群下无有效节点。 | 诊断 |
| 400 | EdgeDns.Cluster.NotBelongToUser | Cluster does not belong to user. | 自建DNS集群不属于当前用户。 | 诊断 |
| 400 | EdgeDns.Cluster.NotExist | Cluster not exist. | 集群不存在 | 诊断 |
| 400 | EdgeDns.Cluster.NotExists | Cluster does not exist. | 自建DNS集群不存在 | 诊断 |
| 400 | Edgedns.Cluster.NotSupportCurrentEnv | Edge dns cluster not support current env. | 自建DNS集群环境属性非法。 | 诊断 |
| 400 | Edgedns.Cluster.NotSupportOperator | Edge dns cluster not support operator. | 不支持操作自建DNS运维集群 | 诊断 |
| 400 | EdgeDns.Cluster.RecurseEnableStatusInvalid | The cluster recurse enable status invalid. | 自建DNS集群开启递归状态不合法 | 诊断 |
| 400 | EdgeDns.Cluster.ResolveRuleDuplicate | Edge dns cluster is bind to same forward zone name. | 自建DNS集群关联了同名的转发规则。 | 诊断 |
| 400 | EdgeDns.Cluster.ResourceTypeInvalid | The cluster resource type invalid. | 自建DNS集群关联资源类型不合法 | 诊断 |
| 400 | EdgeDns.Cluster.TypeDefaultCannotDelete | Cluster type default cannot delete. | 默认集群不允许删除 | 诊断 |
| 400 | EdgeDns.Cluster.TypeInvalid | Cluster type invalid. | 集群类型不合法 | 诊断 |
| 400 | EdgeDns.Cluster.ZoneDuplicate | Edge dns cluster is bind to same authority zone name. | 自建DNS集群关联了同名权威Zone | 诊断 |
| 400 | EdgeDns.Deploy.ClusterExistedNotFinalStatusTask | The cluster existed not final status task. | 自建DNS集群存在未完成的部署任务 | 诊断 |
| 400 | EdgeDns.Deploy.ClusterNodeServiceNotAllowed | The cluster node service not allowed. | 自建DNS部署节点不支持部署该服务 | 诊断 |
| 400 | EdgeDns.Deploy.CreateTaskFailed | Create task failed. | 自建DNS创建部署任务失败 | 诊断 |
| 400 | EdgeDns.Deploy.InstallServiceExisted | The install service is existed. | 自建DNS要安装的服务已存在 | 诊断 |
| 400 | EdgeDns.Deploy.InvalidService | The service is invalid. | 自建DNS部署任务服务不合法 | 诊断 |
| 400 | EdgeDns.Deploy.InvalidTaskCode | The task code is invalid. | 自建DNS部署任务类型不合法 | 诊断 |
| 400 | EdgeDns.Deploy.InvalidTaskParam | The task param is invalid. | 自建DNS部署任务参数不合法 | 诊断 |
| 400 | EdgeDns.Deploy.InvalidTaskStatus | The task status is invalid. | 自建DNS部署任务状态不合法 | 诊断 |
| 400 | EdgeDns.Deploy.InvalidVersion | The version is invalid. | 自建DNS部署版本不合法 | 诊断 |
| 400 | EdgeDns.Deploy.NodeIpNetworkError | The node ip network error. | 自建DNS用户节点ip网络错误 | 诊断 |
| 400 | EdgeDns.Deploy.RunTaskFailed | Run task failed. | 自建DNS执行部署任务失败 | 诊断 |
| 400 | EdgeDns.Deploy.ServiceNotExisted | The service not existed. | 自建DNS服务不存在 | 诊断 |
| 400 | EdgeDns.Deploy.SessionNotExisted | The cluster session not existed. | 自建DNS用户集群无法连接 | 诊断 |
| 400 | EdgeDns.Deploy.TaskCodeNotSupport | The task code not support. | 自建DNS不支持的部署任务类型 | 诊断 |
| 400 | EdgeDns.Deploy.TaskNotExisted | The task not existed. | 自建DNS部署任务不存在 | 诊断 |
| 400 | EdgeDns.Deploy.TaskStatusNotAllowFinish | Task status not allow finish. | 自建DNS部署任务状态不允许结束 | 诊断 |
| 400 | EdgeDns.Deploy.TaskStatusNotAllowRetry | Task status not allow retry. | 自建DNS部署任务状态不允许重试 | 诊断 |
| 400 | EdgeDns.Deploy.UserNodeIpExisted | The user node ip existed. | 自建DNS用户节点ip已存在 | 诊断 |
| 400 | EdgeDns.Deploy.UserNodeIpMustConnected | The user node ip must connected. | 自建DNS用户节点ip无法连接 | 诊断 |
| 400 | EdgeDns.DeployAddNode.FirstNodeServiceNotContainsManagement | The first node service not contains management. | 自建DNS首个部署节点不包含管理服务 | 诊断 |
| 400 | EdgeDns.InvalidFeature | The feature is invalid. | 自建DNS配置的功能不合法 | 诊断 |
| 400 | EdgeDns.InvalidResourceType | The resource type is invalid. | 自建DNS删除节点时,查询的资源类型不合法 | 诊断 |
| 400 | EdgeDns.InvalidToken | The token is invalid. | 自建DNS凭证不合法 | 诊断 |
| 400 | EdgeDns.InvalidUserId | The user id is invalid. | 自建DNS用户id不合法 | 诊断 |
| 400 | EdgeDns.Log.InvalidSearchTarget | Invalid search target. | 搜索字段无效 | 诊断 |
| 400 | EdgeDns.Monitor.InvalidAction | Invalid action. | 不支持的监控action | 诊断 |
| 400 | EdgeDns.Node.Existed | The node already existed. | 自建DNS集群节点已经存在 | 诊断 |
| 400 | EdgeDns.Node.InvalidName | The node name is invalid. | 节点名称已存在 | 诊断 |
| 400 | EdgeDns.Node.InvalidNodeId | The node id is invalid. | 节点Id不合法 | 诊断 |
| 400 | EdgeDns.Node.InvalidRemark | The node remark is invalid. | 节点备注不合法 | 诊断 |
| 400 | EdgeDns.Node.NoServiceExistAfterOperation | Node no service exist after operation. | 自建DNS部署任务操作后不存在服务 | 诊断 |
| 400 | EdgeDns.Node.NotExist | Node not exist. | 节点不存在 | 诊断 |
| 400 | EdgeDns.Node.OnlyResolveNodeExistAfterOperation | Only resolve node exist after operation. | 自建DNS部署任务操作后只存在解析节点 | 诊断 |
| 400 | EdgeDns.Node.QuotaExceed | The node in cluster quota exceed. | 自建DNS集群节点数超过限制 | 诊断 |
| 400 | EdgeDns.Node.UtilityNotExist | Node utility not exist | 节点服务不存在 | 诊断 |
| 400 | EdgeDns.Retry.NoRetryTask | No need retry task. | 没有需要重试的数据同步任务。 | 诊断 |
| 400 | EdgeDns.ServiceAlreadyUserLatestVersion | The service already user latest version. | 自建DNS要升级的服务已经是用户名下最新版本,需要版本全部拉齐一致后才能升级 | 诊断 |
| 400 | EdgeDns.TokenExpired | The token is expired. | 自建DNS凭证已经过期 | 诊断 |
| 400 | EdgeDns.UserAppVersionAllNotAvailable | User app version number greater than or equal to two and all not available. | 自建DNS用户名下版本号大于等于2个且全部不可用 | 诊断 |
| EnableDnsSlbFailed | 打开 加权轮询 失败。 | 诊断 | ||
| Fobidden.DefaultGroup | 默认域名分组无法删除 | 诊断 | ||
| Fobidden.DefaultGroup | Cannot delete the default domain group. | 默认域名分组无法删除 | 诊断 | |
| Fobidden.NotEmptyGroup | 含有域名的分组无法删除 | 诊断 | ||
| Fobidden.RecordLocked | 域名含有锁定解析 | 诊断 | ||
| Forbidden | 操作被禁止 | 诊断 | ||
| Forbidden | You are not authorized to operate the specified resource. | 操作被禁止 | 诊断 | |
| Forbidden.DomainType | 阿里云注册域名,不能进行此操作 。 | 诊断 | ||
| Forbidden.miitBlackList | 工信部黑名单域名 | 诊断 | ||
| 400 | Forbidden.MteeRiskControl | RT001, the domain is at risk. Contact customer support for more details. | RT001,抱歉,该域名因安全问题无法添加,您可通过工单进行申诉 | 诊断 |
| Forbidden.NotAliyunDomain | 域名不是阿里云域名。 | 诊断 | ||
| Forbidden.NotAliyunDomain | The domain name is not registered with Alibaba Cloud. | 域名不是阿里云域名。 | 诊断 | |
| Forbidden.NotHichinaDomain | This action cannot be performed on the domain. Only hichina domains permit this action. | 域名不是阿里云域名 | 诊断 | |
| Forbidden.ProtectedDomain | 找回白名单域名不允许找回 | 诊断 | ||
| Forbidden.ProtectedDomain | The domain names in the whitelist cannot be retrieved. | 找回白名单域名不允许找回 | 诊断 | |
| Forbidden.RiskControl | 该操作被风险控制系统禁止。 | 诊断 | ||
| Forbidden.RiskControl | Your account is at risk. Contact customer support for more details. | 您的帐户存在风险,详情请联系客服。 | 诊断 | |
| Forbidden.TooOfen | 90秒内不允许重复找回 | 诊断 | ||
| Forbidden.TooOfen | Please wait 90 seconds before retrieving again. | 90秒内不允许重复找回 | 诊断 | |
| Forbidden.UserVerification | 无实名验证 | 诊断 | ||
| 400 | FusionClient.CountExceeded | fusionClient count exceeded limits. | 当前账户绑定融合云客户端数量超过允许的最大限额 | 诊断 |
| 400 | Gtm.Invalid.Id | The specified ID is invalid. | id不合法 | 诊断 |
| 400 | Gtm.VerifySign.Failed | An error occurred while verifying the signature. | 验签失败 | 诊断 |
| 400 | GtmAccessStrategy.AccessLine.Conflict | The specified access region is in conflict with an existing region. | 访问区域冲突 | 诊断 |
| 400 | GtmAccessStrategy.AccessLine.Forbidden | The specified access region is already in use. | 该访问区域已被占用 | 诊断 |
| 400 | GtmAccessStrategy.AccessStatus.Failover | The current access status is failover. | 当前访问状态是Failover地址池 | 诊断 |
| 400 | GtmAccessStrategy.AddrPool.Same | The specified default address pool and failover address pool are the same. | 默认地址池和failover地址池一样 | 诊断 |
| 400 | GtmAccessStrategy.Invalid.AccessLine | The specified access region list is invalid. | 无效的访问区域列表 | 诊断 |
| 400 | GtmAccessStrategy.Invalid.AccessMode | The specified access mode is invalid. | 无效的访问模式 | 诊断 |
| 400 | GtmAccessStrategy.Invalid.DefaultPool | The default address pool is invalid. | 默认地址池无效 | 诊断 |
| 400 | GtmAccessStrategy.Invalid.FailoverPool | The specified failover address pool is invalid. | failover地址池无效 | 诊断 |
| 400 | GtmAccessStrategy.Invalid.Id | The specified access strategy ID is invalid. | 无效的访问策略id | 诊断 |
| 400 | GtmAccessStrategy.Invalid.InstanceId | The specified instance ID is invalid. | 无效的实例Id | 诊断 |
| 400 | GtmAccessStrategy.Invalid.Name | The specified strategy name is invalid. | 无效的策略名称 | 诊断 |
| 400 | GtmAccessStrategy.Invalid.StrategyMode | The specified strategy mode is invalid. | 无效的策略模式 | 诊断 |
| 400 | GtmAccessStrategy.Invalid.UserId | The specified user ID is invalid. | 无效的用户id | 诊断 |
| 400 | GtmAccessStrategy.Name.ExceedsLimit | The specified strategy name exceeds the character limit. | 策略名称超长 | 诊断 |
| 400 | GtmAccessStrategy.NotExists | The specified access strategy does not exist. | 访问策略不存在 | 诊断 |
| 400 | GtmAccessStrategy.Num.ExceedsLimit | You cannot create more access strategies. | 访问策略超出限制 | 诊断 |
| 400 | GtmAddr.Invalid.LbaWeight | The specified address weight is invalid. | 地址权重不合法 | 诊断 |
| 400 | GtmAddr.Invalid.Mode | The specified address mode is invalid. | 地址mode不合法 | 诊断 |
| 400 | GtmAddr.Invalid.Value | The specified address is invalid. | 地址值不合法 | 诊断 |
| 400 | GtmAddr.NotExists | The specified address does not exist. | 地址不存在 | 诊断 |
| 400 | GtmAddr.Num.ExceedsLimit | The number of addresses in the specified address pool exceeds the limit. | 地址池的地址个数不合法 | 诊断 |
| 400 | GtmAddr.Value.Duplicate | The specified address already exists. | 地址值重复 | 诊断 |
| 400 | GtmAddrPool.Invalid.Id | The specified address pool ID is invalid. | 地址池id不合法 | 诊断 |
| 400 | GtmAddrPool.Invalid.MinAvailableAddrNum | The specified value for minimum available addresses is invalid. | 最小可用地址数量超过限制 | 诊断 |
| 400 | GtmAddrPool.Invalid.Name | The specified address pool name is invalid. | 地址池name不合法 | 诊断 |
| 400 | GtmAddrPool.Invalid.Type | The specified address pool type is invalid. | 地址池类型不合法 | 诊断 |
| 400 | GtmAddrPool.Invalid.UserId | The specified address pool user ID is invalid. | 地址池用户id不合法 | 诊断 |
| 400 | GtmAddrPool.NotExists | The specified address pool does not exist. | 地址池不存在 | 诊断 |
| 400 | GtmAddrPool.Num.ExceedsLimit | You cannot create more address pools. | 地址池个数超过上限 | 诊断 |
| 400 | GtmAddrPool.RelatedAccessStrategy | The specified address pool already has an access strategy and cannot be deleted. | 地址池已经关联访问策略,不能删除 | 诊断 |
| 400 | GtmHealthCheck.Exist | The specified health check already exists. | 健康检查已经存在 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Code | The specified health check return code is invalid. | 健康检查返回码不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.FailureRate | The specified health check failure ratio is invalid. | 健康检查失败比率不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Host | The specified health check host is invalid. | 健康检查host不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Id | The specified health check ID is invalid. | 健康检查id不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Interval | The specified health check interval value is invalid. | 健康检查间隔不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Name | The specified health check name is invalid. | 健康检查名称不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.PacketLossRate | The specified health check packet loss ratio is invalid. | 健康检查丢包率不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.PacketNum | The specified number of ping packets for the health check is invalid. | 健康检查ping包数目不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Path | The specified health check URL path is invalid. | 健康检查URL路径不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Port | The specified port number is invalid. | 端口号不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Protocol | The specified health check protocol is invalid. | 健康检查协议不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.Status | The specified health check status is invalid. | 健康检查状态不合法 | 诊断 |
| 400 | GtmHealthCheck.Invalid.UserId | The specified health user ID does not exist. | 健康检查用户id不合法 | 诊断 |
| 400 | GtmHealthCheck.NodeNum.ExceedsLimit | The specified number of monitoring nodes for the health check is invalid. | 健康检查监控节点个数不合法 | 诊断 |
| 400 | GtmHealthCheck.NotExists | The specified health check configuration does not exist. | 健康检查配置不存在 | 诊断 |
| 400 | GtmInstance.AlertGroup.ExceedsLimit | The specified alarm group exceeds the alarm limit. | 报警组超过数量限制 | 诊断 |
| 400 | GtmInstance.InstanceName.ExceedsLimit | The specified instance name exceeds the character limit. | 实例名称字符超出限制 | 诊断 |
| 400 | GtmInstance.Invalid.AlertGroup | The specified alarm group is invalid. | 无效的报警组 | 诊断 |
| 400 | GtmInstance.Invalid.Cname | The specified CNAME is invalid. | cname值无效 | 诊断 |
| 400 | GtmInstance.Invalid.ExpireDate | The specified expiration date is invalid. | 到期日无效 | 诊断 |
| 400 | GtmInstance.Invalid.Id | The specified ID is invalid. | 无效的id | 诊断 |
| 400 | GtmInstance.Invalid.InstanceId | The specified instance ID is invalid. | 无效的实例Id | 诊断 |
| 400 | GtmInstance.Invalid.LbaStrategy | The specified balancing strategy is invalid. | 无效的均衡策略 | 诊断 |
| 400 | GtmInstance.Invalid.Name | The specified instance name is invalid. | 无效的实例名称 | 诊断 |
| 400 | GtmInstance.Invalid.Ttl | The specified TTL is invalid. | 无效的TTl | 诊断 |
| 400 | GtmInstance.Invalid.UserDomainName | The specified primary domain is invalid. | 主域名无效 | 诊断 |
| 400 | GtmInstance.Invalid.UserId | The specified user ID is invalid. | 无效的用户id | 诊断 |
| 400 | GtmInstance.Invalid.VersionCode | The specified version is invalid. | 无效的版本号 | 诊断 |
| 400 | GtmInstance.NotExists | The specified instance does not exist. | 实例不存在 | 诊断 |
| 400 | GtmInstance.UserDomainNameExceedsLimit | The specified primary domain name exceeds the character limit. | 主域名字符超出限制 | 诊断 |
| IdentityVerification.TxtRecord | TXT记录未设置或者暂时还未生效,请稍后再试。 | 诊断 | ||
| IllegalUser | 未被授权的用户ID | 诊断 | ||
| IllegalUser | The specified user ID is not authorized. | 未被授权的用户ID | 诊断 | |
| IncorrectDomainUser | 该域名非本账户域名,阿里云域名不能进行跨账号解析,您可以将该域名进行账号间转移来实现域名绑定与解析设置。 | 诊断 | ||
| IncorrectDomainUser | The domain name belongs to other users. Transfer the domain name to the current user and then try the binding and setting actions. | 该域名非本账户域名,阿里云域名不能进行跨账号解析,您可以将该域名进行账号间转移来实现域名绑定与解析设置。 | 诊断 | |
| InstanceHasUnpaidOrder | 您有尚未支付的订单,请先处理后再进行此次操作 | 诊断 | ||
| InstanceHasUnpaidOrder | You have an incomplete order. Please complete the order before continuing with this operation. | 您有尚未支付的订单,请先处理后再进行此次操作 | 诊断 | |
| InternalError | 服务器无法完成对请求的处理 | 诊断 | ||
| 400 | InternalError | The server cannot process this request. | 服务器无法完成对请求的处理 | 诊断 |
| InvalidAccessKeyId.NotFound | 无效的Access Key | 诊断 | ||
| InvalidBinding.BoundDomain | This Domain is already associated with another advanced DNS instance. Changing the associated instance may affect the DNS setting of this domain name. Are you sure you want to use this domain name? | 当前域名已绑定云解析DNS实例,更换实例可能会改变当前记录设置,请确认! | 诊断 | |
| InvalidBinding.SpecialDomain | 特殊域名绑定无效 | 诊断 | ||
| InvalidDnsProduct | 云解析产品不存在 | 诊断 | ||
| InvalidDnsProduct | The DNS product does not exist. | 云解析产品不存在 | 诊断 | |
| InvalidDomainGroup.Duplicate | 分组名称已存在 | 诊断 | ||
| InvalidDomainGroup.Duplicate | The name of the domain group already exists. | 分组名称已存在 | 诊断 | |
| InvalidDomainGroup.EmptyName | 分组名称为空 | 诊断 | ||
| InvalidDomainGroup.NotExist | 域名分组不存在 | 诊断 | ||
| InvalidDomainName.DupDot | 域名格式错误:“.”仅作为分隔符使用,且不能连续; | 诊断 | ||
| InvalidDomainName.Duplicate | 域名已存在于解析列表中,无需再次添加。点击解析列表中的域名即可开始解析 | 诊断 | ||
| InvalidDomainName.Format | 域名格式错误:请输入正确的域名格式 | 诊断 | ||
| InvalidDomainName.Idn | 不支持此格式:如为punycode码,请输入中文域名 | 诊断 | ||
| InvalidDomainName.Illegalcharacter | 域名格式错误:域名一般由英文字母、汉字、阿拉伯数字、“.”、“-”组成。 | 诊断 | ||
| InvalidDomainName.Label | 域名格式错误:请以“.”进行分隔。 | 诊断 | ||
| InvalidDomainName.Length | 域名格式错误:以“."分割的每部分不超过63字符,包含点的全长不超过255字符(含最后的“.“) | 诊断 | ||
| InvalidDomainName.MiddleLine | 域名格式错误:“-”不能放到开头和结尾 | 诊断 | ||
| InvalidDomainName.NeedRegistered | 未注册域名,提交注册 | 诊断 | ||
| InvalidDomainName.NoExist | 您操作的域名已经不存在,请刷新页面重试。 | 诊断 | ||
| InvalidDomainName.NoExist | The specified domain name does not exist. Refresh the page and try again. | 您操作的域名已经不存在,请刷新页面重试。 | 诊断 | |
| InvalidDomainName.Number | 域名格式错误:不能全为数字 | 诊断 | ||
| InvalidDomainName.StartWithDot | 域名格式错误:字符串不能以“."开始 | 诊断 | ||
| InvalidDomainName.Suffix | 系统暂不支持该域名后缀解析 | 诊断 | ||
| InvalidDomainName.Unregistered | 未注册域名,阿里云不支持此域名注册 | 诊断 | ||
| InvalidParameter | 参数取值{0}无效 | 诊断 | ||
| InvalidParameter | The parameter value {0} is invalid. | 参数取值{0}无效 | 诊断 | |
| 400 | InvalidRegionId | Invalid region id. | 无效的地域ID参数。 | 诊断 |
| InvalidRetrievedomain.delete | 被找回域名被删除,此次找回已失效 | 诊断 | ||
| InvalidRetrievedomain.delete | The domain name you want to retrieve has been deleted. | 被找回域名被删除,此次找回已失效 | 诊断 | |
| InvalidRR.AAAAValue | 请输入正确的IPv6地址。 | 诊断 | ||
| InvalidRR.AAARecordUnderLine | AAAA记录不支持主机记录(RR)值含"_" | 诊断 | ||
| InvalidRR.AAARecordUnderLine | Underscores (_) are not allowed in the hostname (RR value) of an AAAA record. | AAAA记录不支持主机记录(RR)值含"_" | 诊断 | |
| InvalidRR.ARecordUnderLine | A记录不支持主机记录(RR)值含"_" | 诊断 | ||
| InvalidRR.ARecordUnderLine | Underscores (_) are not allowed in the hostname (RR value) of an A record. | A记录不支持主机记录(RR)值含"_" | 诊断 | |
| InvalidRR.AValue | 请输入正确的IP地址,例如:10.10.10.10。 | 诊断 | ||
| InvalidRR.DupDot | RR值不能有连续的'.'字符。 | 诊断 | ||
| InvalidRR.DupDot | Do not use two consecutive periods (.) in the RR value. | RR值不能有连续的'.'字符。 | 诊断 | |
| InvalidRR.Empty | RR值中逗点之间不允许为空。 | 诊断 | ||
| InvalidRR.Format | 主机记录(RR)值合法字符包含a--z、A--Z、0--9、'-' 、'_' 、'.'、'*'、'@'、'中文汉字'。 | 诊断 | ||
| InvalidRR.Format.Dot | RR值不能以“逗点”符号开头或结尾。 | 诊断 | ||
| InvalidRR.Format.Dot | Do not start or end the RR value with a comma (,). | RR值不能以“逗点”符号开头或结尾。 | 诊断 | |
| InvalidRR.FWDValue | URL转发记录的值为域名或URL地址,请重新填写。 | 诊断 | ||
| InvalidRR.FWDValueLength | URL转发记录的值最长不能超过500个字符,请重新填写。 | 诊断 | ||
| InvalidRR.FWDValueLength | The maximum length of the value for a URL forwarding record is 500 characters. Re-enter the value. | URL转发记录的值最长不能超过500个字符,请重新填写。 | 诊断 | |
| InvalidRR.Length | “.”分割的每个字符串长度最长为63字符。 | 诊断 | ||
| InvalidRR.MiddleLine | RR值中不能以字符 “-”开头和结尾。 | 诊断 | ||
| InvalidRR.MXRecordUnderLine | MX记录不支持主机记录(RR)值含"_" | 诊断 | ||
| InvalidRR.MXRecordUnderLine | Underscores (_) are not allowed in the hostname (RR value) of a MX record. | MX记录不支持主机记录(RR)值含"_" | 诊断 | |
| InvalidRR.MXValue | 记录值输入有误,请输入正确的域名,例如:www.net.cn。 | 诊断 | ||
| InvalidRR.NoExist | 您操作的解析记录已经不存在,请刷新页面重试 | 诊断 | ||
| InvalidRR.NoExist | The DNS record no longer exists. Refresh the page and try again. | 您操作的解析记录已经不存在,请刷新页面重试 | 诊断 | |
| InvalidRR.NSRecordPan | NS记录不支持主机记录(RR)值为"*" | 诊断 | ||
| InvalidRR.NSRecordPan | Asterisks (*) are not allowed in the hostname (RR value) of a NS record. | NS记录不支持主机记录(RR)值为"*" | 诊断 | |
| InvalidRR.NSRecordRrEmpty | NS记录不支持主机记录(RR)值为"@"或为空 | 诊断 | ||
| InvalidRR.NSValue | NS记录的值为域名,请输入正确域名。 | 诊断 | ||
| InvalidRR.NSValueLength | NS记录的值的长度不能超过253个字符 | 诊断 | ||
| InvalidRR.NSValueLength | The maximum length of the value is 253 characters for a NS record. | NS记录的值的长度不能超过253个字符 | 诊断 | |
| InvalidRR.PanDomainRecord | 泛解析只能以'*.'字符开头。 | 诊断 | ||
| InvalidRR.RrEmpty | 主机记录(RR)不能为空值,请您输入。 | 诊断 | ||
| InvalidRR.SRVRecordPan | SRV记录不支持主机记录(RR)值为"*" | 诊断 | ||
| InvalidRR.SRVRecordPan | Asterisks (*) are not allowed in the hostname (RR value) of a SRV record. | SRV记录不支持主机记录(RR)值为"*" | 诊断 | |
| InvalidRR.SRVValueEmpty | SRV的值不能为空 | 诊断 | ||
| InvalidRR.SRVValueEmpty | The SRV record is required. | SRV的值不能为空 | 诊断 | |
| InvalidRR.SRVValueFormat | SRV记录值格式错误 | 诊断 | ||
| InvalidRR.TXTRecordPan | TXT记录不支持主机记录(RR)值为"*" | 诊断 | ||
| InvalidRR.TXTRecordPan | Asterisks (*) are not allowed in the hostname (RR value) of a TXT record. | TXT记录不支持主机记录(RR)值为"*" | 诊断 | |
| InvalidRR.TXTValueIllegalChar | TXT正文内容不能包含非法字符。 | 诊断 | ||
| InvalidRR.TXTValueIllegalChar | Invalid characters are not allowed in a TXT record. | TXT正文内容不能包含非法字符。 | 诊断 | |
| InvalidRR.TXTValueLength | TXT正文内容的值的长度不能超过253个字符 | 诊断 | ||
| InvalidRR.TXTValueUnicode | TXT正文内容不能包含中文字符 | 诊断 | ||
| InvalidRR.TypeEmpty | 解析类型不能为空 | 诊断 | ||
| InvalidRR.TypeEmpty | The record type is required. | 解析类型不能为空 | 诊断 | |
| InvalidRR.ValueDupDot | 记录值中不能有连续的'.'字符。 | 诊断 | ||
| InvalidRR.ValueDupDot | Two consecutive periods (.) are not allowed in the record. | 记录值中不能有连续的'.'字符。 | 诊断 | |
| InvalidStatus | 无效的状态 | 诊断 | ||
| InvalidStatus | The status is invalid. | 无效的状态 | 诊断 | |
| InvalidTraceId | 无效的TraceId | 诊断 | ||
| InvalidTraceId | The TraceId is invalid. | 无效的TraceId | 诊断 | |
| 400 | InvalidVpcId | Invalid vpc id. | 无效的VPC ID。 | 诊断 |
| 400 | InvalidVpcType | Invalid vpc type. | 无效的VPC类型 | 诊断 |
| 400 | InvalidVpcUserId | Invalid vpc user id. | 无效的VpcUserId参数 | 诊断 |
| Invalidweightvalue | 该解析的权重值不合法,权重仅允许1-100间整数 | 诊断 | ||
| InvalidWeigth | 无效的权重值 | 诊断 | ||
| LineDnsSlb.Cname | 全局负载均衡暂不支持CNAME记录,请关闭CNAME记录后再尝试开启。 | 诊断 | ||
| LineDnsSlb.Cname | The cross-region load balancer does not support CNAME records. Disable CNAME records and try again. | 全局负载均衡暂不支持CNAME记录,请关闭CNAME记录后再尝试开启。 | 诊断 | |
| LineDnsSlb.Monitor | 全局负载均衡需要主机记录开启网站监控,请前往配置。 | 诊断 | ||
| LineDnsSlb.Monitor | Please add the hostname to the site monitoring list before enabling the cross-region load balancer. | 全局负载均衡需要主机记录开启网站监控,请前往配置。 | 诊断 | |
| LineDnsSlb.QuotaExceeded | A/AAAA记录条数超过限制,无法开启 加权轮询 | 诊断 | ||
| MissingParameter | 缺少参数:{0} | 诊断 | ||
| Monitor.Fail | 监控操作失败 | 诊断 | ||
| Monitor.GetISPCityList | 获取运营商可用的城市列表失败 | 诊断 | ||
| Monitor.GetISPFailed | 获取运营商列表失败 | 诊断 | ||
| Monitor.GetMonitorMap | 获取监控地图详情失败 | 诊断 | ||
| Monitor.GetMonitorNodes | 获取可用节点失败! | 诊断 | ||
| Monitor.NoBackupIp | 监控的自定义切换无备用IP! | 诊断 | ||
| Monitor.NoRecord | 无可用的值(指定的解析记录已删除或暂停) | 诊断 | ||
| Monitor.NotExist | 用户名下没有监控 | 诊断 | ||
| Monitor.NotSameDomain | 监控项不完全属于同一个域名 | 诊断 | ||
| Monitor.NotSameUser | 监控项不完全属于同一个用户 | 诊断 | ||
| Monitor.NotSupport | 免费版解析暂不支持监控操作。 | 诊断 | ||
| Monitor.NotSupport | The free version of DNS does not support monitoring. | 免费版解析暂不支持监控操作。 | 诊断 | |
| Monitor.TaskNoExists | 要操作的监控不存在! | 诊断 | ||
| Monitor.TaskNoExists | The monitoring task does not exist. | 要操作的监控不存在! | 诊断 | |
| Monitor.Unpaid | 尚未购买网站监控 | 诊断 | ||
| Monitor.Unpaid | You have not purchased site monitoring. | 尚未购买网站监控 | 诊断 | |
| NoSuchVersion | 无效的版本 | 诊断 | ||
| NotSupport.Line | 当前云解析配置不支持此线路 | 诊断 | ||
| NotSupport.LineType | 您没有购买地域线路,无法切换线路类型 | 诊断 | ||
| NotSupport.SMS | 不支持短消息通知类型 | 诊断 | ||
| OperationDomain.NoPermission | 没有权限操作此域名,请先执行找回操作! | 诊断 | ||
| OperationDomain.NoPermission | You are not authorized to operate the domain. Please retrieve the domain name first. | 没有权限操作此域名,请先执行找回操作! | 诊断 | |
| OperationThreadInUsed | 批量操作线程已满,请稍后重试! | 诊断 | ||
| PanDomainRecord | 泛解析不允许修改权重 | 诊断 | ||
| PanDomainRecord | The weight value of wildcard DNS records cannot be modified. | 泛解析不允许修改权重 | 诊断 | |
| 400 | ParamsError | params error. | 参数错误 | 诊断 |
| 400 | Pdns.InvalidDirection | The orderBy direction is invalid. | 排序方向无效 | 诊断 |
| 400 | Pdns.InvalidOrderByName | orderBy field is invalid. | 排序字段无效 | 诊断 |
| 400 | PdnsRecord.DecordConflict | The record is conflict. | 解析记录冲突 | 诊断 |
| 400 | PdnsRecord.DuplicateRecordIds | record id is duplicate. | 解析记录ID重复 | 诊断 |
| 400 | PdnsRecord.DuplicateRecords | record is duplicate. | 解析记录重复 | 诊断 |
| 400 | PdnsRecord.InvalidEnableStatus | The record enable status is invalid. | 解析记录启用状态值无效 | 诊断 |
| 400 | PdnsRecord.InvalidRecordValue | record value is invalid. | 解析记录值无效 | 诊断 |
| 400 | PdnsRecord.InvalidRequestSource | request source is invalid. | 请求来源无效 | 诊断 |
| 400 | PdnsRecord.InvalidRr | record rr is invalid. | 内置权威解析记录rr无效 | 诊断 |
| 400 | PdnsRecord.InvalidTtl | ttl is invalid. | TTL无效 | 诊断 |
| 400 | PdnsRecord.InvalidType | record type is invalid. | 解析记录类型无效 | 诊断 |
| 400 | PdnsRecord.InvalidWeight | record weight is invalid. | 解析记录权重值无效 | 诊断 |
| 400 | PdnsRecord.InvalidWeightEnableStatus | weight enable status is invalid. | 权重算法启用状态无效 | 诊断 |
| 400 | PdnsRecord.NotExists | Record is not exists. | 解析记录不存在 | 诊断 |
| 400 | PdnsRecord.RecordConflict | The record is conflict. | 解析记录冲突 | 诊断 |
| 400 | PdnsRecord.RecordTypeNotSupportAlgorithm | record type not support algorithm. | 解析记录类型不支持权重算法 | 诊断 |
| 400 | PdnsRecord.RecordTypeNotSupportWeight | record type not support weight. | 解析记录类型不支持权重 | 诊断 |
| 400 | PdnsRecord.SameEnableStatus | same record enable status. | 解析记录启用状态未发生变化 | 诊断 |
| 400 | PdnsRecord.SameRrCountMaximum | zone same rr count exceed the maximum. | Zone下相同rr的解析记录数量超过限制 | 诊断 |
| 400 | PdnsRecord.SameWeightEnableStatus | The weight enable status is same. | 权重算法启用状态未发生变化 | 诊断 |
| 400 | PdnsRecord.ZoneRrCountMaximum | rr count exceed the maximum. | Zone下的解析记录数量超过限制 | 诊断 |
| 400 | PdnsService.Unavailable | service status is unavailable. | 服务状态为不可用 | 诊断 |
| 400 | PdnsZone.EffectiveScopeExists | zone has effective scope. | 关联生效范围时无法删除Zone,先取消关联 | 诊断 |
| 400 | PdnsZone.EffectiveScopeRepeated | same effective scope with same zone name. | Zone关联范围重复 | 诊断 |
| 400 | PdnsZone.InvalidEffectiveScope | the effective scope is invalid. | 内置权威zone关联范围无效 | 诊断 |
| 400 | PdnsZone.InvalidEffectiveType | The effective type is invalid. | 内置权威zone关联类型无效 | 诊断 |
| 400 | PdnsZone.InvalidProxyPattern | The proxy pattern is invalid. | 递归解析代理模式无效 | 诊断 |
| 400 | PdnsZone.invalidZoneName | The zone name is invalid. | Zone名称无效 | 诊断 |
| 400 | PdnsZone.InvalidZoneName | The zone name is invalid. | Zone名称无效 | 诊断 |
| 400 | PdnsZone.invalidZoneNameGovForbidden | The zone name forbidden for gov. | 不允许定义政府事业单位相关的域名。 | 诊断 |
| 400 | PdnsZone.InvalidZoneNameGovForbidden | The zone name forbidden for gov. | 不允许定义政府事业单位相关的域名 | 诊断 |
| 400 | PdnsZone.Maximum | total zone count exceed the maximum. | Zone数量超过限制 | 诊断 |
| 400 | PdnsZone.NotExists | Zone is not exists. | Zone不存在 | 诊断 |
| 400 | PostBusiness.InvalidParam | alidns service param invalid. | DNS云解析后付费服务参数无效 | 诊断 |
| 400 | PostBusiness.InvalidService | post business service not activated. | 后付费服务没有开通 | 诊断 |
| 400 | PostBusiness.InvalidServiceModule | post business service module not activated. | 后付费服务模块没有开通 | 诊断 |
| 400 | PostBusiness.ServiceInDebt | post business service inDebt. | 后付费服务欠费 | 诊断 |
| 400 | PostBusiness.ServiceInDebtRelease | post business service inDebt instance release. | 后付费服务欠费,实例释放 | 诊断 |
| 400 | PostBusiness.ServiceModuleAlreadyExist | post business service module has been activated. | 后付费服务模块已经开通完成 | 诊断 |
| QueryInstanceUnpaidOrderFailed | 查询实例未付款订单失败。 | 诊断 | ||
| QueryRenewPriceFailed | 查询续费价格失败。 | 诊断 | ||
| QuotaExceeded.ARecord | 超出数量限制,当前配置的最大设置数量为 {0} 条记录 | 诊断 | ||
| QuotaExceeded.ARecord | The maximum number of {0} records is exceeded. | 超出当前配置的最大A记录设置数量 {0}。 | 诊断 | |
| 400 | QuotaExceeded.ARecord | The maximum number of %s records is exceeded. | 超出当前记录类型配置的最大数量 %s。 | 诊断 |
| QuotaExceeded.Batchdelete | 超出限制,批量删除的解析记录不能超过100个 | 诊断 | ||
| QuotaExceeded.Batchdelete | Up to 100 DNS records can be selected for batch deletion. | 超出限制,批量删除的解析记录不能超过100个 | 诊断 | |
| QuotaExceeded.BatchNumber | 批量操作的数量超过限制 | 诊断 | ||
| QuotaExceeded.BatchNumber | The maximum number of selections available for the batch operation is exceeded. | 批量操作的数量超过限制 | 诊断 | |
| QuotaExceeded.Binding | 绑定次数超过版本规定的限制 | 诊断 | ||
| QuotaExceeded.domainlist | 域名数目已经达到产品定义的最大值 | 诊断 | ||
| QuotaExceeded.FreeDnsRecord | A(AAAA)记录数量超出限制,云解析免费版可以添加10个相同主机记录相同线路的A(AAAA)记录。 | 诊断 | ||
| QuotaExceeded.GroupCount | 域名分组数量超过限制 | 诊断 | ||
| QuotaExceeded.GroupNameLength | 分组名称长度超过限制 | 诊断 | ||
| 400 | QuotaExceeded.HTTPSRecord | The number of HTTPS records exceeds the maximum number. | 超出HTTPS记录类型配置的最大数量 %s。 | 诊断 |
| QuotaExceeded.Monitor | 云解析添加监控超过限制 | 诊断 | ||
| QuotaExceeded.Monitor | The maximum number of monitors is exceeded. | 云解析添加监控超过限制 | 诊断 | |
| QuotaExceeded.MonitoringFrequency | 设置异常,当前配置允许的监控间隔为 {0} 分钟。 | 诊断 | ||
| QuotaExceeded.MonitoringIp | 超出数量限制,当前配置的最大备用 IP/CNAME 数量为 {0} 个 | 诊断 | ||
| QuotaExceeded.MonitoringSwitchingStrategy | 超出限制,当前配置不允许添加此切换策略的监控。 | 诊断 | ||
| QuotaExceeded.MonitoringSwitchingStrategy | Adding a monitor for the switching policy is not allowed. | 超出限制,当前配置不允许添加此切换策略的监控。 | 诊断 | |
| QuotaExceeded.MonitoringTask | 超出数量限制,当前配置的最大监控任务数量为 {0} 个 | 诊断 | ||
| QuotaExceeded.MonitoringTask | The number of monitor tasks exceeds the maximum number ({0}). | 超出数量限制,当前配置的最大监控任务数量为 {0} 个 | 诊断 | |
| QuotaExceeded.MonitorNodes | 超出数量限制,当前配置的监控节点最多为 {0} 个 | 诊断 | ||
| QuotaExceeded.MonitorNodes | The number of monitor nodes exceeds the maximum number ({0}). | 超出数量限制,当前配置的监控节点最多为 {0} 个 | 诊断 | |
| QuotaExceeded.Record | 超出解析记录数量最大值90 | 诊断 | ||
| QuotaExceeded.SubDomain | 子域名长度超出数量限制,当前配置的最大允许子域名级数为 {0} | 诊断 | ||
| QuotaExceeded.SubDomain | The subdomain level exceeds the limit. | 超出当前配置的最大允许子域名级数 {0}。 | 诊断 | |
| 400 | QuotaExceeded.SVCBRecord | The number of SVCB records exceeds the maximum number. | 超出SVCB记录类型配置的最大数量 %s。 | 诊断 |
| QuotaExceeded.Time | 只能查询最近90天的记录 | 诊断 | ||
| QuotaExceeded.Time | You can only query the record of the latest 90 days. | 只能查询最近90天的记录 | 诊断 | |
| QuotaExceeded.TTL | 超出数量限制,当前配置的最小允许TTL值为 {0} | 诊断 | ||
| QuotaExceeded.URLRecord | 超出数量限制,当前配置的最大设置数量为 {0} 条URL转发 | 诊断 | ||
| Record.empty | 部分记录字段为空! | 诊断 | ||
| Record.illegal | 部分记录字段内容非法 | 诊断 | ||
| Record.illegal | Some fields of the record are invalid. | 部分记录字段内容非法 | 诊断 | |
| 400 | Record.Invalid.Action | Pause record with Disalbe, resume with Enable. | 解析记录启用状态参数不合法。 | 诊断 |
| 400 | Record.Invalid.Rr | rr is invalid. | 参照OpenAPI文档说明,输入正确的rr | 诊断 |
| 400 | RecordCount.SaveSubdomain.Exceed | Refresh Subdomain: the number of records cannot exceed %d. | 刷新子域名:解析记录个数不能超过 %d 条。 | 诊断 |
| RecordDisable.fail | 暂停解析失败 | 诊断 | ||
| RecordEnable.fail | 启用解析失败 | 诊断 | ||
| RecordFobidden.BlackHole | 您的域名正在遭受恶意攻击,且攻击量已超过您购买的域名解析防护量,当前处于黑洞状态(暂停解析),黑洞期间暂不支持解析的增删改操作!建议您立即升级配置或者等待攻击结束 | 诊断 | ||
| RecordForbidden.BlackHole | Some DNS records are in the DNS server blackhole. | 域名解析防护进入黑洞 | 诊断 | |
| RecordForbidden.DNSChange | 操作失败!产品配置发生变化,系统正在为您切换,切换期间,暂不支持解析的增删改操作!请您稍后再试! | 诊断 | ||
| RecordLocked.fail | 锁定解析失败 | 诊断 | ||
| RecordUnLocked.fail | 解锁解析失败 | 诊断 | ||
| 400 | ResolveLog.EndTimestamp.Invalid | EndTimestamp is invalid. | 结束时间无效 | 诊断 |
| 400 | ResolveLog.EndTimestamp.NotExists | EndTimestamp not exists. | 结束时间不存在 | 诊断 |
| 400 | ResolveLog.ExceedReadDataMax | Maximum read limit exceeded. | 超过最大读取限制 | 诊断 |
| 400 | ResolveLog.InvalidAlidnsDomainAuthLogConfig | Invalid alidns authority domain log config. | 云解析权威域名日志开关无效 | 诊断 |
| 400 | ResolveLog.InvalidAlidnsPostBusinessStatus | Invalid post business status. | 云解析后付费服务状态无效 | 诊断 |
| 400 | ResolveLog.InvalidDomainName | Invalid authority domain name. | 权威域名无效 | 诊断 |
| 400 | ResolveLog.InvalidUserId | User id is invalid. | 用户ID无效 | 诊断 |
| 400 | ResolveLog.QueryLogFailed | Query log failed. | 请求日志失败 | 诊断 |
| 400 | ResolveLog.StartTimestamp.NotExists | StartTimestamp not exists. | 开始时间不存在 | 诊断 |
| 400 | ResolverRule.BindEdgeDnsCluster | The forwarding rule is already bound to a edge dns cluster. | 转发规则已关联自建集群 | 诊断 |
| 400 | Resource.Count.Exceeds | The operation failed because the number of resources reaches the upper limit. | 操作失败,资源数超出上限%s | 诊断 |
| 400 | Resource.EffectiveScope.OperationTypeInvalid | Invalid operation type. | 操作类型无效。 | 诊断 |
| 400 | Resource.TagCount.Exceeds | The operation failed because the number of tags that are specified for a single resource reaches the upper limit. | 操作失败,单资源设置标签超出上限 %s | 诊断 |
| 400 | Resource.TagTotalCount.Exceeds | The operation failed because the number of tags that are specified for a single resource reaches the upper limit. | 操作失败,设置总标签数超出上限%s | 诊断 |
| RestrictedDomain | 该域名为受限域名,不能设置解析,故不能添加到该解析列表 | 诊断 | ||
| ScanningOperationError | 操作扫描任务出错! | 诊断 | ||
| ServiceUnavailable | 服务器当前无法处理请求 | 诊断 | ||
| ServiceUnavailable | The server cannot process your request at this time. | 服务器当前无法处理请求 | 诊断 | |
| SignatureDoesNotMatch | 无效的签名 | 诊断 | ||
| 400 | SlaveDns.BoundVPCandClusterForbidden | Zone that support secondary DNS cannot bind both VPC and cluster. | 配置辅助DNS的ZONE不能同时绑定VPC与自建DNS集群 | 诊断 |
| 400 | SlaveDns.EdgeClusterAdded | Secondary DNS of cluster has already been added. Please delete it before the operation. | ZONE已经配置辅助DNS功能,请删除后再进行绑定自建DNS集群 | 诊断 |
| 400 | SlaveDns.RegionVpcAdded | Secondary DNS of private zone has already been added. Please delete it before the operation. | ZONE已经配置辅助DNS功能,请删除后再进行绑定VPC | 诊断 |
| 400 | Statistics.TooManyResults | Your query has produced too many results, please narrow down the search scope. | 您的查询结果太多,请缩小查询范围。 | 诊断 |
| SubDomainInvalid.Line | 超出线路限制,当前配置不支持设置此线路类型 | 诊断 | ||
| SubDomainInvalid.Priority | MX解析无效的优先级 | 诊断 | ||
| SubDomainInvalid.TTL | 无效的解析ttl | 诊断 | ||
| SubDomainInvalid.Type | 主机记录类型输入无效,主机记录类型只支持NS、CNAME、A记录、AAAA、MX、TXT、SRV记录 | 诊断 | ||
| 400 | Tag.TotalCount.Exceeds | The operation failed because the total number of tags that are specified reaches the upper limit. | 操作失败,设置标签总量超出上限 %s | 诊断 |
| TaskExecutio | 已经存在导入任务,请等待任务完成后再提交! | 诊断 | ||
| TaskExecutio | An import task already exists. Wait until that task is completed and try again. | 已经存在导入任务,请等待任务完成后再提交! | 诊断 | |
| Throttling | 您这个时段的流量已经超限。如果不能满足现有业务要求可以提工单进行申请。 | 诊断 | ||
| 400 | Throttling.User | Request was denied due to user flow control. | 由于请求频次达到阈值,请求被拒绝,请稍后重试。 | 诊断 |
| UnableToGetWhoisEmail | Whois邮箱未获取到 | 诊断 | ||
| UnabletoGetWoisInfo | 获取不到Whois信息 | 诊断 | ||
| UnKnownError | 未知错误,请稍后重试! | 诊断 | ||
| UnsupportedLine | 当前版本不支持的解析线路 | 诊断 | ||
| UnsupportedOperation | 无效的接口 | 诊断 | ||
| URLForwardAddError | URL转发添加失败 | 诊断 | ||
| URLForwardChangeError | URL转发修改失败 | 诊断 | ||
| URLForwardDeleteError | URL转发删除失败! | 诊断 | ||
| URLForwardError.ChineseChar | URL转发目标地址中不能包含中文字符 | 诊断 | ||
| URLForwardError.ChineseChar | Chinese characters are not allowed in the target address of a URL forwarding record. | URL转发目标地址中不能包含中文字符 | 诊断 | |
| URLForwardError.NotDefaultLine | URL转发不支持非default线路 | 诊断 | ||
| URLForwardError.NotDefaultLine | The URL forwarding record only supports default line. | URL转发不支持非default线路 | 诊断 | |
| URLForwardError.NotVerifyDomain | URL备案异常 | 诊断 | ||
| URLForwardError.PanRecord | URL跳转不支持泛解析 | 诊断 | ||
| URLForwardError.PanRecord | The URL forwarding does not support wildcard DNS. | URL跳转不支持泛解析 | 诊断 | |
| 400 | Zone.BindEdgeDnsCluster | Zone is already bound to a edge dns cluster. | 权威Zone已绑定该集群,不可操作。 | 诊断 |
| 400 | Zone.BindEdgeDnsCluster.OnlySupportFastZone | Binding an Edge DNS cluster is only supported for Fast Zones. | 仅快速区权威Zone支持关联自建DNS集群。 | 诊断 |
| 400 | Zone.BindEdgeDnsCluster.RecordCountExceed | You cannot bind the cluster, because record count exceed the maximum. | 权威Zone下解析记录数量超过上限。禁止关联自建DNS集群。 | 诊断 |
| 400 | Zone.DnsGroupChange.Forbidden | You cannot change dns group. | 禁止切换位置区。 | 诊断 |
| 400 | Zone.DnsGroupChange.Forbidden4FastZone | You cannot change dns group, because can only use fast zone. | 当前zone被禁止进行位置区切换,因为用户只能使用快速区。 | 诊断 |
该文章对您有帮助吗?