Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • 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 Valkey™
  • Getting started
    • All guides
      • Pre-configuration
      • FQDNs of hosts
      • Connecting from applications
  • Access management
  • Pricing policy
  • Terraform reference
  • Monitoring metrics
  • Audit Trails events
  • Public materials
  • Release notes
  • FAQ
  1. Step-by-step guides
  2. Connection
  3. FQDNs of hosts

FQDNs of Valkey™ hosts

Written by
Yandex Cloud
Updated at February 13, 2026

To connect to a host, you need its FQDN (fully qualified domain name). You can get it using one of the following methods:

  • Request a list of cluster hosts.

  • In the management console, copy the cluster connection command (it contains the host’s FQDN). To get the command, go to the cluster page and click Connect.

  • 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.

To connect to a non-sharded cluster, you can also use a special FQDN.

Special FQDNSpecial FQDN

Yandex Managed Service for Valkey™ provides a special FQDN that can be used instead of regular host FQDNs to connect to non-sharded clusters.

In a non-sharded cluster, an FQDN of c-<cluster_ID>.rw.mdb.yandexcloud.net format always points to the current master host. You can get the cluster ID with the list of clusters in the folder. When connecting to this FQDN, you can perform read and write operations.

In multi-host clusters, a special FQDN may temporarily point to a replica host (for up to 10 minutes). This is because it takes time to update DNS records for special FQDNs. If your write request returns an error, repeat it later.

Warning

If automatic failover promotes a host without public access to master, you will not be able to connect to that host from the internet. To avoid this, enable public access for all cluster hosts.

Here is an example of an SSL-encrypted connection to a master host for a cluster with the c9qash3nb1v9******** ID:

redis-cli -h c-c9qash3nb1v9********.rw.mdb.yandexcloud.net \
  -p 6380 \
  --tls \
  --cacert ~/.redis/YandexInternalRootCA.crt \
  -a <Valkey™_password>

Warning

Use master host special FQDN-based connections only for processes that can cope with database being unavailable 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.