Yandex Cloud
  • Services
  • Solutions
  • Why Yandex Cloud
  • Blog
  • Pricing
  • Documentation
  • Contact us
Get started
Language / Region
Yandex project
© 2023 Intertech Services AG
Yandex Cloud DNS
  • Getting started
  • Step-by-step guides
  • Concepts
    • Overview
    • DNS zones
    • Resource records
    • Integration with Compute Cloud
    • Quotas and limits
  • Tutorials
  • Access management
  • Pricing policy
  • API reference
  • Questions and answers
  1. Concepts
  2. Integration with Compute Cloud

Integration with Compute Cloud

Written by
Yandex Cloud
  • Automatic zone selection
  • Using Cloud DNS for instance groups

You can immediately assign domain names to VMs when creating them in Compute Cloud:

  • All VMs are assigned an internal FQDN using the VM name or the hostname parameter.
  • In the network interface settings, you can create additional DNS records for a VM. They will be placed in your own private zones. If you don't specify a zone for an additional record explicitly, it's selected automatically. For more detail, please see below.

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 selection

If no zone for a VM's additional DNS record is specified explicitly, it's selected automatically. To enable this, specify the VM's FQDN with a dot at the end. In the management console, the dot is added automatically.

A DNS record is added to one of the private zones that are accessible from the VM's virtual network and are FQDN suffixes. The most specific private zone is selected based on the suitable suffix. If there are multiple suitable zones with the same domain name, one of them is selected.

For example, you specified an FQDN like hello.world.private. in the network settings and the following four private DNS zones are accessible from the virtual network:

  • Service ..
  • Custom: staging. and private.. And world.private..

The staging. zone is not suitable, since the staging. domain name is not a suffix of the hello.world.private. FQDN.

The zones that have the appropriate suffix are ., private., and world.private.. As a result, world.private. is selected as the most specific zone.

Using Cloud DNS for instance groups

When assigning an FQDN to a VM instance from a group, the name specified in the instance template is used for all instances in the group: a set of records with the same names but different IPs in the values is created.

You can use variables from instance templates when creating records. For example, if you specify a record name like web_server_{instance.index}, you can create records with unique names of instances from a group. If you set a name like web_server_{instance.zone_id}, you can create records for all instances within a single availability zone.

See also

  • Creating a VM

Was the article helpful?

Language / Region
Yandex project
© 2023 Intertech Services AG
In this article:
  • Automatic zone selection
  • Using Cloud DNS for instance groups