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 Managed Service for OpenSearch
  • Getting started
    • All guides
      • Pre-configuration
      • FQDNs of hosts
      • Connecting from applications
      • Code examples
      • Configuring SAML authentication
    • Managing users
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ

In this article:

  • Getting a host FQDN
  • Special FQDN
  1. Step-by-step guides
  2. Connection
  3. FQDNs of hosts

FQDNs of OpenSearch hosts

Written by
Yandex Cloud
Updated at March 5, 2026
View in Markdown
  • Getting a host FQDN
  • Special FQDN

To connect to a host, you need its fully qualified domain name (FQDN). You can use the FQDN of a particular host in the cluster or a special FQDN always pointing to the available host with the DASHBOARDS role.

Here is a host FQDN example:

rc1a-goh2a9tr********.mdb.yandexcloud.net

Getting a host FQDNGetting a host FQDN

There are several ways to get a OpenSearch host's FQDN:

  • Look up the FQDN in the management console:

    1. Navigate to the cluster page.
    2. Navigate to Hosts.
    3. Copy the Host FQDN column value.
  • In the management console, copy the cluster connection command (it contains the host’s FQDN). To get this command, navigate to the cluster page and click Connect.

  • Get the list of cluster hosts using the CLI or API.

Special FQDNSpecial FQDN

An FQDN in c-<cluster_ID>.rw.mdb.yandexcloud.net format always points to the available OpenSearch host with the DASHBOARDS role in the cluster. You can get the cluster ID with the list of clusters in the folder.

You can connect to hosts with the DATA role using a special FQDN with port 9200. In which case the load balancer located on the host with the DASHBOARDS role will redirect the request to one of the hosts with the DATA role using the round-robin scheduling algorithm. To implement this connection scheme, your cluster must have at least one host with the DASHBOARDS role.

You can use a special FQDN to send requests to a specific host group with the DATA role. To do this, add the X-Yandex-OpenSearch-NodeGroup=<host_group_name> header to the request.

You can get the host group name with cluster details.

In clusters with multiple DATA or DASHBOARDS hosts, a special FQDN may temporarily point to an unavailable host (for up to 10 minutes). This is because it takes time to update DNS records for special FQDNs. If your request returns an error, repeat it later.

Warning

Use special FQDN-based connections only for processes that allow for indexes being not available for writing for up to 10 minutes.

Was the article helpful?

Previous
Pre-configuration
Next
Connecting from applications
© 2026 Direct Cursus Technology L.L.C.