Yandex Cloud
Search
Discuss with expertTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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.
Terraform in Yandex Cloud
  • Getting started
  • Solution library
    • Overview
    • Release notes
          • dns_firewall
          • dns_firewall_iam_binding
          • dns_inbound_endpoint
          • dns_inbound_endpoint_iam_binding
          • dns_recordset
          • dns_zone
          • dns_zone_iam_binding

In this article:

  • Example usage
  • Arguments & Attributes Reference
  • Import
  1. Terraform reference
  2. Resources
  3. Cloud DNS
  4. Resources
  5. dns_inbound_endpoint

yandex_dns_inbound_endpoint (Resource)

Written by
Yandex Cloud
Updated at May 29, 2026
  • Example usage
  • Arguments & Attributes Reference
  • Import

Example usageExample usage

//
// Create a new DNS Inbound Endpoint.
//
resource "yandex_dns_inbound_endpoint" "endpoint1" {
  name        = "my-inbound-endpoint"
  description = "My DNS inbound endpoint"

  labels = {
    label1 = "label-1-value"
  }

  folder_id   = "my-folder-id"
  network_id  = yandex_vpc_network.foo.id
  address_id  = yandex_vpc_address.addr1.id

  deletion_protection = true
}

// Auxiliary resources for DNS Inbound Endpoint
resource "yandex_vpc_network" "foo" {}

resource "yandex_vpc_subnet" "subnet1" {
  name           = "my-subnet"
  zone           = "ru-central1-a"
  network_id     = yandex_vpc_network.foo.id
  v4_cidr_blocks = ["192.168.0.0/24"]
}

resource "yandex_vpc_address" "addr1" {
  name        = "my-addr"
  description = "internal address for DNS inbound endpoint"

  internal_ipv4_address {
    subnet_id = yandex_vpc_subnet.subnet1.id
  }
  deletion_protection = false
}

Arguments & Attributes ReferenceArguments & Attributes Reference

  • address (Read-Only) (String). IP address of the DNS inbound endpoint.
  • address_id (Required)(String). ID of the address resource.
  • created_at (Read-Only) (String). Creation timestamp.
  • deletion_protection (Bool). Prevents accidental endpoint removal.
  • description (String). Description of the DNS inbound endpoint.
  • dns_inbound_endpoint_id (String). ID of the DNS inbound endpoint to return.
  • folder_id (String). ID of the folder that the DNS inbound endpoint belongs to.
  • id (String). ID of the DNS inbound endpoint to return.
  • labels (Map Of String). DNS inbound endpoint labels as key:value pairs.
  • name (String). Name of the DNS inbound endpoint.
    The name is unique within the folder.
  • network_id (Required)(String). ID of the network that the DNS inbound endpoint belongs to.
  • status (Read-Only) (String). Status of the DNS inbound endpoint.
  • timeouts [Block].
    • create (String). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).
    • delete (String). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Setting a timeout for a Delete operation is only applicable if changes are saved into state before the destroy operation occurs.
    • read (String). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours). Read operations occur during any refresh or planning operation when refresh is enabled.
    • update (String). A string that can be parsed as a duration consisting of numbers and unit suffixes, such as "30s" or "2h45m". Valid time units are "s" (seconds), "m" (minutes), "h" (hours).

ImportImport

The resource can be imported by using their resource ID. For getting it you can use Yandex Cloud Web Console or Yandex Cloud CLI.

# terraform import yandex_dns_inbound_endpoint.<resource Name> <resource Id>
terraform import yandex_dns_inbound_endpoint.endpoint1 dns7ie**********dkhh6

Was the article helpful?

Previous
dns_firewall_iam_binding
Next
dns_inbound_endpoint_iam_binding
© 2026 Direct Cursus Technology L.L.C.