Create a record set

post

https://{hostname}/config-dns/v2/zones/{zone}/names/{name}/types/{type}

Creates a new Record set with the specified name and type.

Path Params

type

string

required

The record set type.

name

string

required

A domain name, including the parent zone.

zone

string

required

The name of the zone.

Query Params

accountSwitchKey

string

For customers who manage more than one account, this runs the operation from another account. The Identity and Access Management API provides a list of available account switch keys.

Body Params

A set of one or more resource records that share the same name, type, and TTL.

name

string

required

The fully qualified domain name (FQDN) of this record.

rdata

array of strings

required

Each string encodes the rdata for a single record. If you want to have three A records, you need three strings in the array. Each string is encoded in master file format. RFC 1035 defines master file format for most record types.

rdata*

ttl

integer

required

≥ 0

The number of seconds this record should live in a resolver's cache before being refetched. A value of 0 means the record is uncached.

type

string

required

The record type.

Headers

string

enum

Defaults to application/json

Generated from available response content types

Allowed:

Responses

Language

URL

Loading…

Response

Choose an example:

application/json

application/problem+json

201Successful operation.

400Bad Request. The request body is missing required data or contains an invalid field value.

401Unauthorized. Your credentials are missing or invalid.

404Not Found. The specified zone doesn't exist or isn't accessible.

409Conflict. The request conflicts with the current state of the zone or record set.

412Precondition Failed. The If-Match header value doesn't match the zone's current ETag.

415Unsupported Media Type. The request's Content-Type header is not supported. Use application/json.

422Unprocessable Entity. The request body contains a semantically invalid field value.