[Yandex Cloud documentation](../../index.md) > [Yandex Cloud DNS](../index.md) > [Step-by-step guides](index.md) > DNS connections > Updating an inbound DNS connection

# Updating an inbound DNS connection

To update an [inbound DNS connection](../concepts/dns-connection.md#dns-inbound):

{% list tabs group=instructions %}

- Management console {#console}

  1. In the [management console](https://console.yandex.cloud), navigate to the DNS connection folder.
  1. Navigate to **Cloud DNS**.
  1. In the left-hand panel, select ![nodes-down](../../_assets/console-icons/nodes-down.svg) **Inbound endpoints**.
  1. In the row with the DNS connection, click ![ellipsis](../../_assets/console-icons/ellipsis.svg) and select ![pencil](../../_assets/console-icons/pencil.svg) **Edit**. In the window that opens:

      1. Optionally, change the DNS connection [name](*name) in the **Name** field.
      1. Optionally, provide any description in the **Description** field.
      1. Optionally, set [labels](../../resource-manager/concepts/labels.md) for the DNS connection in the **Labels** field.
      1. Optionally, enable or disable the **Deletion protection** setting based on whether you need to enable or disable protection of the connection from accidental deletion.
      1. Click **Save** to save your changes.

- CLI {#cli}

  If you do not have the Yandex Cloud CLI yet, [install and initialize it](../../cli/quickstart.md#install).

  The folder used by default is the one specified when [creating](../../cli/operations/profile/profile-create.md) 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:

      ```bash
      yc dns inbound-endpoint update --help
      ```
  1. Get a list of inbound DNS connections in the default folder:
     
     ```bash
     yc dns inbound-endpoint list
     ```
     
     Result:
     
     ```text
     +----------------------+----------------------+-------------+----------------------+----------------------+--------------------------------+---------------------+
     |          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                |                     |
     +----------------------+----------------------+-------------+----------------------+----------------------+--------------------------------+---------------------+
     ```
  1. Update the inbound DNS connection by specifying its name or ID:

      ```bash
      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](*name) for the inbound DNS connection. This is an optional setting.
      * `--description`: Connection description. This is an optional setting.
      * `--labels`: List of [labels](../../resource-manager/concepts/labels.md). 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:

      ```text
      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](../../cli/cli-ref/dns/cli-ref/inbound-endpoint/update.md).

- Terraform {#tf}

  With [Terraform](https://www.terraform.io/), 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](https://github.com/hashicorp/terraform/blob/main/LICENSE). The [Yandex Cloud provider for Terraform](https://github.com/yandex-cloud/terraform-provider-yandex) is distributed under the [MPL-2.0](https://www.mozilla.org/en-US/MPL/2.0/) license.
  
  For more information about the provider resources, see the guides on the [Terraform](https://www.terraform.io/docs/providers/yandex/index.html) website or [its mirror](../../terraform/index.md).

  If you do not have Terraform yet, [install it and configure the Yandex Cloud provider](../../tutorials/infrastructure-management/terraform-quickstart.md#install-terraform).
  
  
  To manage infrastructure using Terraform under a service account or user accounts (a Yandex account, a federated account, or a local user), [authenticate](../../terraform/authentication.md) using the appropriate method.

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

      ```hcl
      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](*name).
      * `description`: Connection description. This is an optional setting.
      * `network_id`: ID of the Virtual Private Cloud [network](../../vpc/concepts/network.md#network) where the inbound DNS connection was created.
      * `address_id`: ID of the [reserved](../../vpc/operations/private-ip-reserve.md) [private](../../vpc/concepts/address.md#internal-addresses) 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.

  1. Create the resources:

      1. In the terminal, navigate to the configuration file directory.
      1. Make sure the configuration is correct using this command:
      
         ```bash
         terraform validate
         ```
      
         If the configuration is valid, you will get this message:
      
         ```bash
         Success! The configuration is valid.
         ```
      
      1. Run this command:
      
         ```bash
         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.
      1. Apply the configuration changes:
      
         ```bash
         terraform apply
         ```
      
      1. 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](https://console.yandex.cloud) or this [CLI](../../cli/cli-ref/dns/cli-ref/inbound-endpoint/get.md) command:

      ```bash
      yc dns inbound-endpoint get <DNS_connection_name>
      ```

- API {#api}

  To update an inbound DNS connection, use the [update](../api-ref/DnsInboundEndpoint/update.md) REST API method for the [DnsInboundEndpoint](../api-ref/DnsInboundEndpoint/index.md) resource or the [DnsInboundEndpointService/Update](../api-ref/grpc/DnsInboundEndpoint/update.md) gRPC API call.

{% endlist %}

#### Useful links {#see-also}

* [DNS connections](../concepts/dns-connection.md)
* [Resolving cloud DNS names in a corporate network](../tutorials/dns-integration.md)

[*name]: 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.