Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
    • Cloud Interconnect
    • Cloud Backup
    • Cloud Registry
    • Yandex AI Studio
    • Compute Cloud
    • Object Storage
    • Managed Service for Kubernetes®
    • Yandex BareMetal
    • Smart Web Security
    • Security Deck
    • Managed Service for PostgreSQL
    • Managed Service for ClickHouse®
    • Monium
    • Cloud CDN
    • Network Load Balancer
    • Virtual Private Cloud
    • Cloud DNS
    • Application Load Balancer
    • Yandex Cloud Video
    • Stackland
    • Yandex Cloud Router
    • Yandex Managed Service for Trino
    • Managed Service for MySQL®
    • Managed Service for Valkey™
    • Managed Service for Apache Spark™
    • Yandex StoreDoc
    • Managed Service for OpenSearch
    • Managed Service for Apache Kafka®
    • Data Transfer
    • Yandex MPP Analytics Engine for PostgreSQL
    • Yandex Managed Service for Apache Airflow®
    • Data Processing
    • Yandex MetaData Hub
    • Managed Service for YDB
    • Managed Service for Sharded PostgreSQL
    • Managed Service for YTsaurus
    • Yandex WebSQL
    • DataLens
    • Yandex Search API
    • SpeechSense
    • SpeechKit
    • DataSphere
    • Vision OCR
    • Translate
    • Yandex Identity Hub
    • Key Management Service
    • Certificate Manager
    • Yandex Lockbox
    • Audit Trails
    • SmartCaptcha
    • Cloud Desktop
    • Yandex SIEM
    • SourceCraft Code Assistant
    • Container Registry
    • Managed Service for GitLab
    • Managed Service for Prometheus®
    • Cloud Functions
    • API Gateway
    • Yandex Cloud Postbox
    • Message Queue
    • Serverless Integrations
    • IoT Core
    • Data Streams
    • Serverless Containers
    • Cloud Notification Service
    • Yandex Query
    • Identity and Access Management
    • Yandex Cloud Console
    • Resource Manager
    • Yandex Cloud Billing
    • Yandex Cloud Quota Manager
    • Cloud Apps
  • System Status
  • Marketplace
    • Featured
    • Infrastructure & Network
    • Data Platform
    • AI for business
    • Security
    • DevOps tools
    • Serverless
    • Monitoring & Resources
  • All Solutions
    • By industry
    • By use case
    • Economics and Pricing
    • Security
    • Technical Support
    • Start testing with double trial credits
    • Cloud credits to scale your IT product
    • Gateway to Russia
    • Cloud for Startups
    • Center for Technologies and Society
    • Yandex Cloud Partner program
    • Price calculator
    • Pricing plans
  • Customer Stories
  • Documentation
  • Blog
© 2026 Direct Cursus Technology L.L.C.
Yandex Cloud DNS
  • Getting started
    • All guides
      • Creating an inbound DNS connection
      • Updating an inbound DNS connection
      • Deleting an inbound DNS connection
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ
  1. Step-by-step guides
  2. DNS connections
  3. Updating an inbound DNS connection

Updating an inbound DNS connection

Written by
Yandex Cloud
Improved by
Danila N.
Updated at August 11, 2026
View in Markdown

To update an inbound DNS connection:

Management console
CLI
Terraform
API
  1. In the management console, navigate to the DNS connection folder.

  2. Navigate to Cloud DNS.

  3. In the left-hand panel, select  Inbound endpoints.

  4. In the row with the DNS connection, click and select Edit. In the window that opens:

    1. Optionally, change the DNS connection name in the Name field.
    2. Optionally, provide any description in the Description field.
    3. Optionally, set labels for the DNS connection in the Labels field.
    4. Optionally, enable or disable the Deletion protection setting based on whether you need to enable or disable protection of the connection from accidental deletion.
    5. Click Save to save your changes.

If you do not have the Yandex Cloud CLI yet, install and initialize it.

The folder used by default is the one specified when creating the CLI profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also specify a different folder for any command using --folder-name or --folder-id. If you access a resource by its name, the search will be limited to the default folder. If you access a resource by its ID, the search will be global, i.e., through all folders based on access permissions.

  1. See the description of the CLI command for updating an inbound DNS connection:

    yc dns inbound-endpoint update --help
    
  2. Get a list of inbound DNS connections in the default folder:

    yc dns inbound-endpoint list
    

    Result:

    +----------------------+----------------------+-------------+----------------------+----------------------+--------------------------------+---------------------+
    |          ID          |         NAME         | DESCRIPTION |      NETWORK ID      |      ADDRESS ID      |           CREATED AT           | DELETION PROTECTION |
    +----------------------+----------------------+-------------+----------------------+----------------------+--------------------------------+---------------------+
    | dns2n8fakpev******** | new-inbound-endpoint |             | enpg0adn0uv6******** | e2l8n7uup1j3******** | seconds:1783270956             | true                |
    |                      |                      |             |                      |                      | nanos:37000000                 |                     |
    | dns6h5q0h2ic******** | inbound-endpoint     |             | enpcfncr6uld******** | fl8not0e596n******** | seconds:1783270908             | false               |
    |                      |                      |             |                      |                      | nanos:107000000                |                     |
    +----------------------+----------------------+-------------+----------------------+----------------------+--------------------------------+---------------------+
    
  3. Update the inbound DNS connection by specifying its name or ID:

    yc dns inbound-endpoint update <DNS_connection_name_or_ID> \
      --new-name <new_connection_name> \
      --description '<connection_description>' \
      --labels <key>=<value>[,<key>=<value>] \
      --deletion-protection
    

    Where:

    • --new-name: New name for the inbound DNS connection. This is an optional setting.

    • --description: Connection description. This is an optional setting.

    • --labels: List of labels. This is an optional setting. You can specify one or more labels separated by commas in <key1>=<value1>,<key2>=<value2> format.

    • --deletion-protection: Enables protection of the inbound DNS connection from accidental deletion. This is an optional setting.

      If you want to disable deletion protection, provide --deletion-protection=false in the command

    Result:

    id: dns0uullmbcn********
    folder_id: b1gt6g8ht345********
    created_at: "2026-07-05T15:40:39.595Z"
    name: my-inbound-endpoint
    network_id: enpcfncr6uld********
    address: 192.168.3.3
    address_id: fl8not0e596n********
    status: AVAILABLE
    deletion_protection: true
    

    For more information about the yc dns inbound-endpoint update command, see the CLI reference.

With Terraform, you can quickly create a cloud infrastructure in Yandex Cloud and manage it using configuration files. These files store the infrastructure description written in HashiCorp Configuration Language (HCL). If you change the configuration files, Terraform automatically detects which part of your configuration is already deployed, and what should be added or removed.

Terraform is distributed under the Business Source License. The Yandex Cloud provider for Terraform is distributed under the MPL-2.0 license.

For more information about the provider resources, see the guides on the Terraform website or its mirror.

If you do not have Terraform yet, install it and configure the Yandex Cloud provider.

To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), authenticate using the appropriate method.

  1. Specify the inbound DNS connection properties in the configuration file:

    resource "yandex_vpc_network" "my_net" {}
    
    resource "yandex_vpc_subnet" "subnet1" {
      network_id     = yandex_vpc_network.my_net.id
      v4_cidr_blocks = ["192.168.3.0/24"]
    }
    
    resource "yandex_vpc_address" "dns_address" {
      name        = "my-address"
      description = "inbound endpoint address"
    
      internal_ipv4_address {
        subnet_id = yandex_vpc_subnet.subnet1.id
        address   = "192.168.3.3"
      }
      deletion_protection = false
    }
    
    resource "yandex_dns_inbound_endpoint" "dns_connection" {
      name        = "my-inbound-endpoint"
      description = "DNS Inbound Endpoint"
    
      network_id  = yandex_vpc_network.my_net.id
      address_id  = yandex_vpc_address.dns_address.id
    
      deletion_protection = false
    }
    

    Where:

    • name: DNS connection name.
    • description: Connection description. This is an optional setting.
    • network_id: ID of the Virtual Private Cloud network where the inbound DNS connection was created.
    • address_id: ID of the reserved private IP address that will be used for the inbound DNS connection.
    • deletion_protection: Enables protection of the inbound DNS connection from accidental deletion. This is an optional setting.
  2. Create the resources:

    1. In the terminal, navigate to the configuration file directory.

    2. Make sure the configuration is correct using this command:

      terraform validate
      

      If the configuration is valid, you will get this message:

      Success! The configuration is valid.
      
    3. Run this command:

      terraform plan
      

      You will see a list of resources and their properties. No changes will be made at this step. Terraform will show any errors in the configuration.

    4. Apply the configuration changes:

      terraform apply
      
    5. Type yes and press Enter to confirm the changes.

    Terraform will create all the required resources. You can check the new resources using the management console or this CLI command:

    yc dns inbound-endpoint get <DNS_connection_name>
    

To update an inbound DNS connection, use the update REST API method for the DnsInboundEndpoint resource or the DnsInboundEndpointService/Update gRPC API call.

Useful linksUseful links

  • DNS connections
  • Resolving cloud DNS names in a corporate network

The naming requirements are as follows:

  • Length: between 3 and 63 characters.
  • It can only contain lowercase Latin letters, numbers, and hyphens.
  • It must start with a letter and cannot end with a hyphen.

Was the article helpful?

Previous
Creating an inbound DNS connection
Next
Deleting an inbound DNS connection
© 2026 Direct Cursus Technology L.L.C.