An enterprise is implementing internal name resolution across multiple Virtual Private Cloud (VPC) networks in Google Cloud. A Cloud DNS private managed zone named `corp.internal` was created in `project-a` and initially bound to `vpc-a`. Compute Engine virtual machine instances residing in `vpc-b` (located in `project-b`) require name resolution for endpoints within `corp.internal`. Currently, DNS queries originating from virtual machines in `vpc-b` fail to resolve these internal domain names. How should the cloud engineer configure Cloud DNS to grant `vpc-b` access to resolve names in the private managed zone?
- Update the existing private managed zone configuration for `corp.internal` to add `vpc-b` to the list of authorized VPC networks.Cevap
- BEnable the Cloud DNS API within `project-b` and deploy a duplicate public managed zone with identical resource record sets.
- CRecreate the `corp.internal` private zone at the Organization resource level so child VPC networks inherit private DNS resolution permissions.
- DDeploy a Global External HTTP(S) Load Balancer in `vpc-a` to intercept and forward port 53 DNS traffic coming from `vpc-b`.
Cevap
Update the existing private managed zone configuration for `corp.internal` to add `vpc-b` to the list of authorized VPC networks.
In Google Cloud DNS, private zones provide internal DNS resolution exclusively to VPC networks configured as authorized networks. To allow virtual machines in a secondary VPC network to resolve records in a private zone, the secondary VPC network must be explicitly added to the private zone's authorized networks list.
Adım Adım Çözüm
Anahtar Kavram
Cloud DNS Private Zone Authorized Networks