Yandex Cloud
Search
Contact UsTry it for free
  • Customer Stories
  • Documentation
  • Blog
  • All Services
  • System Status
    • 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
© 2025 Direct Cursus Technology L.L.C.
All solutions
    • All solutions for the Yandex Cloud Terraform provider
    • Resolving the `Failed to query available provider packages` error when using Terraform
    • Zone appears as both public and private
    • Resolving the `Invalid provider registry host` error

In this article:

  • Issue description
  • Solution
  1. Yandex Cloud Terraform provider
  2. Zone appears as both public and private

Zone appears as both public and private

Written by
Yandex Cloud
Updated at December 17, 2025
  • Issue description
  • Solution

Issue descriptionIssue description

When you create a Cloud DNS zone, it appears as both public and private.

SolutionSolution

The Terraform provider creates a public-private zone so you can make it accessible from private networks without recreating it. As long as the private_visibility.network_ids list is empty, such a zone behaves like a regular public zone.

This is to make sure that most of the zones can be updated without recreation.

Was the article helpful?

Previous
Resolving the `Failed to query available provider packages` error when using Terraform
Next
Resolving the `Invalid provider registry host` error
© 2025 Direct Cursus Technology L.L.C.