Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
© 2022 Yandex.Cloud LLC
Yandex Cloud DNS
  • Getting started
  • Step-by-step instructions
    • All instructions
    • Zones
      • Creating an internal DNS zone
      • Creating a public DNS zone
      • Updating a DNS zone
      • Deleting a DNS zone
    • Records
      • Creating a record
      • Updating a record
      • Deleting a record
  • Concepts
    • Overview
    • DNS zones
    • Resource records
    • Integration with Yandex Compute Cloud
    • Quotas and limits
  • Practical guidelines
    • Configuring a local caching DNS resolver
    • Migrating DNS zones from Yandex 360
    • Integrating with a corporate DNS service
    • Configuring Cloud DNS for access to managed database clusters from other cloud networks
    • Creating an ACME resolver webhook for responses to DNS01 checks
  • Access management
  • Pricing policy
  • API reference
    • Authentication in the API
    • gRPC
      • Overview
      • DnsZoneService
      • OperationService
    • REST
      • Overview
      • DnsZone
        • Overview
        • create
        • delete
        • get
        • getRecordSet
        • list
        • listAccessBindings
        • listOperations
        • listRecordSets
        • setAccessBindings
        • update
        • updateAccessBindings
        • updateRecordSets
        • upsertRecordSets
  • Questions and answers
  1. API reference
  2. REST
  3. DnsZone
  4. create

Method create

Written by
Yandex Cloud
  • HTTP request
  • Body parameters
  • Response

Creates a DNS zone in the specified folder.

HTTP request

POST https://dns.api.cloud.yandex.net/dns/v1/zones

Body parameters

{
  "folderId": "string",
  "name": "string",
  "description": "string",
  "labels": "object",
  "zone": "string",
  "privateVisibility": {
    "networkIds": [
      "string"
    ]
  },
  "publicVisibility": {}
}
Field Description
folderId string

Required. ID of the folder to create DNS zones in.

To get a folder ID, make a list request.

The maximum string length in characters is 50.

name string

Name of the DNS zone. The name must be unique within the folder.

Value must match the regular expression |[a-z]([-a-z0-9]{0,61}[a-z0-9])?.

description string

Description of the DNS zone.

The maximum string length in characters is 256.

labels object

DNS zone labels as key:value pairs.

No more than 64 per resource. The string length in characters for each key must be 1-63. Each key must match the regular expression [a-z][-_./\@0-9a-z]*. The maximum string length in characters for each value is 63. Each value must match the regular expression [-_./\@0-9a-z]*.

zone string

Required. DNS zone suffix.

The maximum string length in characters is 255. Value must match the regular expression [.]|[a-z0-9][-a-z0-9.]*\..

privateVisibility object

Privately visible zone settings. At least one of two visibility fields must be set.

Configuration for privately visible zones.

privateVisibility.
networkIds[]
string

Network IDs.

The number of elements must be in the range 0-10. The string length in characters for each value must be equal to 20.

publicVisibility object

Publicly visible zone settings. At least one of two visibility fields must be set.

Configuration for publicly visible zones.

Response

HTTP Code: 200 - OK

{
  "id": "string",
  "description": "string",
  "createdAt": "string",
  "createdBy": "string",
  "modifiedAt": "string",
  "done": true,
  "metadata": "object",

  //  includes only one of the fields `error`, `response`
  "error": {
    "code": "integer",
    "message": "string",
    "details": [
      "object"
    ]
  },
  "response": "object",
  // end of the list of possible fields

}

An Operation resource. For more information, see Operation.

Field Description
id string

ID of the operation.

description string

Description of the operation. 0-256 characters long.

createdAt string (date-time)

Creation timestamp.

String in RFC3339 text format.

createdBy string

ID of the user or service account who initiated the operation.

modifiedAt string (date-time)

The time when the Operation resource was last modified.

String in RFC3339 text format.

done boolean (boolean)

If the value is false, it means the operation is still in progress. If true, the operation is completed, and either error or response is available.

metadata object

Service-specific metadata associated with the operation. It typically contains the ID of the target resource that the operation is performed on. Any method that returns a long-running operation should document the metadata type, if any.

error object
The error result of the operation in case of failure or cancellation.
includes only one of the fields error, response
error.
code
integer (int32)

Error code. An enum value of google.rpc.Code.

error.
message
string

An error message.

error.
details[]
object

A list of messages that carry the error details.

response object
includes only one of the fields error, response

The normal response of the operation in case of success. If the original method returns no data on success, such as Delete, the response is google.protobuf.Empty. If the original method is the standard Create/Update, the response should be the target resource of the operation. Any method that returns a long-running operation should document the response type, if any.

Was the article helpful?

Language / Region
© 2022 Yandex.Cloud LLC
In this article:
  • HTTP request
  • Body parameters
  • Response