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
    • Yandex SIEM
    • 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
  1. Concepts
  2. DNS connections

DNS connections

Written by
Yandex Cloud
Updated at August 11, 2026
View in Markdown

To resolve FQDNs in Yandex Virtual Private Cloud networks, you normally need a cloud DNS resolver to handle DNS queries from cloud resources. The DNS resolver is only accessible from within virtual machines and cannot be used outside of VMs.

At the same time, you can use DNS connections to set up the integration of your corporate DNS services with internal DNS zones in Yandex Cloud. Currently, only one DNS connection type is supported: inbound DNS endpoints.

Note

To configure integration of corporate DNS servers with DNS servers in Yandex Cloud, your corporate network must be connected to the cloud network using Yandex Cloud Interconnect resources.

Inbound DNS connectionInbound DNS connection

An incoming DNS connection is a special Yandex Cloud DNS resource created in the cloud network that allows you to use the cloud DNS resolver to resolve domain names in the cloud network and its subnets from outside the Yandex Cloud network. To do this, corporate DNS servers must send DNS queries addressed to Yandex Cloud internal DNS zones to the IP address of the incoming DNS connection.

To receive DNS queries, the incoming connection uses a private IP address reserved in any of the cloud network subnets.

Note

You can only create one inbound DNS connection per Virtual Private Cloud cloud network.

Useful linksUseful links

  • DNS resolver
  • DNS zones
  • Creating an inbound DNS connection
  • Cloud Interconnect overview
  • Resolving cloud DNS names in a corporate network

Was the article helpful?

Previous
DNS resolver
Next
Integration with Compute Cloud
© 2026 Direct Cursus Technology L.L.C.