[[["이해하기 쉬움","easyToUnderstand","thumb-up"],["문제가 해결됨","solvedMyProblem","thumb-up"],["기타","otherUp","thumb-up"]],[["이해하기 어려움","hardToUnderstand","thumb-down"],["잘못된 정보 또는 샘플 코드","incorrectInformationOrSampleCode","thumb-down"],["필요한 정보/샘플이 없음","missingTheInformationSamplesINeed","thumb-down"],["번역 문제","translationIssue","thumb-down"],["기타","otherDown","thumb-down"]],["최종 업데이트: 2025-03-26(UTC)"],[[["This guide outlines the process of creating a managed private zone with cross-project binding enabled, allowing it to be associated with a network in a different project within the same organization."],["To perform this task, users need `dns.networks.bindPrivateDNSZone` permission on the VPC network's project and `dns.managedZones.create` permission on the DNS zone's project, or the `roles/dns.admin` role."],["The projects involved must be within the same organization, and zones cannot be linked to VPC networks outside this organizational boundary."],["The process involves obtaining the VPC network's URL from the first project using the `gcloud compute networks describe` command and then using that URL when creating the private zone in the second project with the `gcloud dns managed-zones create` command."],["The VPC Network will be associated with a DNS zone in a different project within the organization so that all the VMs in that VPC network can resolve the DNS zones."]]],[]]