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 Cloud CDN
    • All guides
      • Creating a resource
      • Copying configuration from one resource to another
      • Updating basic settings of a resource
      • Getting information about a resource
      • Configuring resource caching
      • Configuring log export
      • Prefetching files to the CDN server cache
      • Purging resource cache
      • Configuring request and response headers
      • Configuring CORS for responses to clients
      • Configuring HTTP methods
      • Setting up an HTTP response
      • Enabling file compression
      • Enabling file segmentation
      • Enabling origin shielding
      • Setting up a request redirect
      • Enabling a resource to follow request redirects
      • Setting up hiding of origin headers
      • Setting up access via a secure token
      • Setting up location rules
      • Setting up a server name for SNI
      • Suspending and resuming a resource
      • Managing resource labels
      • Configuring dedicated IP addressing
      • Configuring a TLS profile
      • Deleting a resource
      • Viewing resource statistics
  • Access management
  • Pricing policy
  • Terraform reference
  • Metrics Monitoring
  • Request logs
  • Audit Trails events
  • Release notes
  • Troubleshooting
  1. Step-by-step guides
  2. Resources
  3. Configuring dedicated IP addressing

Configuring dedicated IP addressing of CDN resources

Written by
Yandex Cloud
Updated at July 20, 2026
View in Markdown

Warning

The dedicated IP addressing service is subject to the Yandex Cloud CDN pricing policy. The number of allocated IP addresses is limited.

To get a dedicated IP address for CDN resources from a specific folder:

Note

Dedicated IP addressing is enabled for the entire folder. If you select to pay per individual CDN resource, you will be charged for all CDN resources in the folder. If you need dedicated IP addresses only for some of the resources, we recommend creating additional folders for them.

  1. Make sure the folder you are requesting dedicated IP addressing for already contains at least one CDN resource.

  2. Submit a ticket to Yandex Cloud support.

    Specify the following:

    • Service: Cloud CDN.
    • Subject: Dedicated IP addressing of CDN resources.
    • Ticket text: ID of the folder in question.
  3. After you get a response, in your ticket:

    • Confirm your consent to the dedicated IP addressing pricing policy.

    • Agree on the date and time of switching to dedicated IP addressing.

      Alert

      When dedicated IP addressing is being activated, you get a traffic balancing type update during which time your resources get no service. This takes up to 15 minutes.

    • Learn the dedicated public IP address that is going to be used for the folder’s CDN resources.

  4. Optionally, to avoid the temporary unavailability of your content when activating dedicated IP addressing, redirect traffic from the Yandex Cloud CDN resources ahead of time, e.g., by routing it directly to the origin.

    Note

    When you are activating dedicated IP addressing and temporarily rerouting traffic from your CDN resource, the cached content is saved on the CDN servers.

    To redirect traffic:

    1. In your DNS hosting settings, change the CNAME record value from the one pointing to the Yandex Cloud CDN domain name to a temporary one, e.g., the origin’s FQDN:


      Example of an original record:

      cdn.example.com. CNAME e1b83ae3********.topology.gslb.yccdn.ru
      

      Example of an updated record:

      cdn.example.com. CNAME <origin_FQDN>
      

      Tip

      If you use Yandex Cloud DNS for DNS hosting, check out this guide.

    2. Wait for the updated CNAME record to get propagated across DNS servers. This may take a few hours.

    3. To make sure the CDN resource receives no more requests, check the resource statistics.

  5. Wait until support informs you that dedicated IP addressing is activated. Check that the Yandex Cloud CDN domain name of your CDN resource has a dedicated IP address specified in the support ticket, e.g.:

    host e1b83ae3********.topology.gslb.yccdn.ru
    

    Result:

    e1b83ae3********.topology.gslb.yccdn.ru has address 188.72.111.11
    

    From this point on, you start paying for dedicated IP addressing.

  6. If you had redirected traffic from your CDN resource, restore the original CNAME record.

Useful linksUseful links

  • Dedicated IP addressing of CDN resources
  • Cloud CDN quotas and limits

Was the article helpful?

Previous
Managing resource labels
Next
Configuring a TLS profile
© 2026 Direct Cursus Technology L.L.C.