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
    • 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
    • Overview
    • DNS zones
    • Resource records
    • DNS filters
    • DNS resolver
    • DNS connections
    • Integration with Compute Cloud
    • Quotas and limits
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Release notes
  • FAQ

In this article:

  • Automatic zone selection
  • Using Cloud DNS for instance groups
  • Use cases
  1. Concepts
  2. Integration with Compute Cloud

Integration with Compute Cloud

Written by
Yandex Cloud
Updated at July 13, 2026
View in Markdown
  • Automatic zone selection
  • Using Cloud DNS for instance groups
  • Use cases

You can assign domain names (FQDNs) to VMs as soon as you create them in Compute Cloud.

To add a VM to a zone when creating it, select the zone you need and set a domain name under DNS settings for internal addresses of Network settings. You can add multiple records, including in different zones. If you do not specify a zone, the VM will get a domain name in the standard zone of the subnet it will be connected to. For instructions on how to create a VM, see Creating a VM from a public Linux image.

For a VM's public IP address, integration with Compute Cloud is currently not supported. You can add an A record to a public zone manually after creating a VM. Learn more about how to create a record.

Automatic zone selectionAutomatic zone selection

If no zone is specified explicitly for a VM's additional DNS record, it will be selected automatically. For this you need to specify an FQDN ending with a period. In the management console, the period is added automatically.

A DNS record will be added to one of the private zones that can be accessed from the VM's virtual network and are FQDN suffixes. The most specific private zone will be selected from among those with suitable suffixes. If there are several suitable zones with the same domain name, one of them will be selected.

For example, in the network settings, FQDN is set to hello.world.private., and the following four private DNS zones can be accessed from the virtual network:

  • Service zone: .
  • Custom zones: staging., private., and world.private.

The staging. zone is out of consideration because the staging. domain name is not a suffix of the hello.world.private. FQDN.

From among of the zones with suitable suffixes (., private., and world.private.), world.private. will be selected ans the most specific one.

Using Cloud DNS for instance groupsUsing Cloud DNS for instance groups

When creating a VM group, the name specified in the VM template will apply to all the VMs in the group. As a result, the created records will have the same FQDNs but different IPs.

To generate unique names, you can use variables in the template. For example, if the record name is web_server_{instance.index}, you can create records with unique names of the group's VMs. If the name is web_server_{instance.zone_id}, you can create records common for all VMs in the same availability zone.

Use casesUse cases

  • Assigning a domain name to a web server VM

Useful linksUseful links

  • Creating a VM

Was the article helpful?

Previous
DNS connections
Next
Quotas and limits
© 2026 Direct Cursus Technology L.L.C.