Yandex Cloud
Documentation
PresentationContact UsTry it for free
© 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:

  • How Cloud DNS works
  • Integration with Compute Cloud
  • Basic concepts of the service
  • Use cases
  1. Concepts
  2. Overview

Concepts Cloud DNS

Written by
Yandex Cloud
Updated at November 9, 2026
View in Markdown
  • How Cloud DNS works
  • Integration with Compute Cloud
  • Basic concepts of the service
  • Use cases

Yandex Cloud DNS is a service that handles DNS requests and facilitates Domain Name System (DNS) administration.

With Cloud DNS, you can:

  • Create DNS zones in the DNS hierarchy. Public zones enable the use of domain names for websites and online services. Private zones assist in organizing a namespace of cloud resources in selected networks, e.g., for the production and test environments.

  • Manage resource records in the created zones. Records associate domain names with resource IP addresses and specify other domain parameters. For example, you can associate a domain with a server IP address, set up an alias, or specify the domain’s mail servers.

  • Configure filtering of DNS requests from cloud resources. You can use allowing and restricting lists to control domain name resolution via the cloud DNS resolver. This helps you block DNS requests to phishing and malicious websites or limit requests in an isolated environment to trusted domains only.

  • Configure DNS connections for your corporate network and Yandex BareMetal servers. This helps applications access cloud resources in private DNS zones, such as VMs and managed database clusters, by their name. To enable this, the corporate network or private BareMetal subnet must be linked to the cloud network via Yandex Cloud Interconnect.

How Cloud DNS worksHow Cloud DNS works

Cloud DNS processes two types of DNS requests: to public and private domain zones.

  1. You create a public or private DNS zone. In a public zone, domain names are available from the internet. In a private zone, names are available from associated Yandex Virtual Private Cloud networks, and when an inbound DNS connection is configured, from the corporate network and BareMetal servers linked to the cloud network via Cloud Interconnect.

  2. You add resource records to the zone you created. Records associate domain names with IP addresses, aliases, or other resources.

  3. Servers process a DNS request to a domain name from your zone:

    1. For public zones, the Yandex Cloud name servers (ns1.yandexcloud.net. and ns2.yandexcloud.net.) process the request. To give these servers an authority over your domain, delegate it. To do this, specify the addresses of the Yandex Cloud name servers in your registrar’s NS records.
    2. For private zones, the requests are processed by a cloud DNS resolver. The second IP address from the subnet range is reserved for it, e.g., x.x.x.2. This address is by default provided to the VM over DHCP.

If the cloud does not have custom zones, except for service zones, Cloud DNS still processes public DNS requests from cloud resources, e.g., from a VM to external domains.

To reduce the number of public DNS requests and lower the costs, use caching resolvers, such as systemd-resolved, dnsmasq, or unbound.

Integration with Compute CloudIntegration with Compute Cloud

When creating VM instances in Yandex Compute Cloud, you can assign them domain names (FQDNs) and automatically add VMs to DNS zones.

If you specify a zone and domain name in DNS settings when creating a VM, the relevant resource record will appear in this zone. If you do not specify a zone explicitly when an FQDN is specified, it will be selected automatically.

For details, see Integration with Compute Cloud.

Basic concepts of the serviceBasic concepts of the service

Cloud DNS uses the following basic terms:

  • A DNS zone is a logical space that combines the domain names of resources and stores the resource records. DNS zones can be public, private, or reverse.
  • A resource record is the main unit of information in a DNS. Using resource records, you determine where to route requests that come to specific domain names.
  • A DNS filter is a tool for controlling and filtering outbound DNS requests from cloud resources using FQDN lists.
  • A DNS resolver is a DNS server in the Yandex Cloud infrastructure that processes DNS requests from resources in Virtual Private Cloud cloud networks and resolves domain names in private DNS zones.
  • A DNS connection is a resource that resolves domain names in private Yandex Cloud DNS zones from a corporate network and BareMetal servers.
  • Quotas and limits are service use limitations.

See also the Yandex Cloud general resource hierarchy.

Use casesUse cases

  • Configuring a local caching DNS resolver
  • Resolving cloud DNS names in a corporate network
  • Configuring DNS name resolution from a private Yandex BareMetal network
  • Assigning a domain name to a web server VM

A virtual machine is similar to a server in cloud infrastructures.
For details, see VMs in Compute Cloud.

A subnet is a range of IP addresses in a cloud network. Addresses from this range can be assigned to cloud resources, such as VMs and DB clusters.
For more information, see Subnets.

When creating a VM, it is assigned a host name and internal FQDN that can be used to access a certain VM from another VM within the same cloud network.
For more information, see Host name and internal FQDN.

Was the article helpful?

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