dcloud dns records updateChange the values or TTL of a record set
Fields left out keep their stored value. An ALIAS target sent here replaces the old one; healthCheckId null removes the check, but stored failoverValues must be cleared in the same call (failoverValues: []) or the change is refused.
Synopsis
dcloud dns records update id recordId [flags]Arguments
<id>Requiredstring
Also accepted as
--id. Constraints: uuid<recordId>Requiredstring
Also accepted as
--record-id. Constraints: uuid
Flags
--ttlOptionalnumber
Seconds resolvers may cache the set, 1 to 604800. Absent: the TTL is kept
Constraints: integer, 1-604800
--valuesOptionalarray of string
Replaces the values (at most 100 of at most 4096 characters each; a CNAME takes one). Absent: the values are kept. The name and type of a set cannot change
Constraints: 1-4096 chars
--app-idOptionalstring
ALIAS: the app whose address is answered
--load-balancer-idOptionalstring
ALIAS: a load balancer, answered with its IPv4 (A) and IPv6 (AAAA)
--bucketOptionalstring
ALIAS: a bucket name; the name answers with the bucket's static website
--distribution-idOptionalstring
ALIAS: a CDN distribution, answered with its healthy edge nodes (TTL at most 30 s); list the name among the distribution's aliases too, for its certificate
--health-check-idOptionalstring
A, AAAA, CNAME: an uptime check; null removes it
May be null.
--failover-valuesOptionalarray of string
Answered instead of values while the health check is down
--routingOptionalobject
Weighted ({policy:"weighted", variants:[{id, weight 0-255, values, healthCheckId?}]}) or geolocation ({policy:"geo", variants:[{id, country|continent, values, healthCheckId?}]}) routing; null removes it. For geo, values are the default answer.
Constraints: JSON
May be null.
Example
dcloud dns records update id recordIdGenerated from the API description, the same one the API checks requests against and the CLI is built from.