Your team is deploying an internal microservices application across two Google Cloud Virtual Private Cloud (VPC) networks, `backend-vpc` and `analytics-vpc`, within the same project. You have created a Cloud DNS private zone named `internal-dev-zone` managing the domain `dev.example.internal`. Virtual machines in both VPC networks must be able to resolve domain names defined inside this private zone. Which TWO of the following actions are required to successfully enable DNS resolution for both networks?
- Add both `backend-vpc` and `analytics-vpc` to the list of authorized VPC networks in the private zone settings.Cevap
- Ensure the Cloud DNS API is explicitly enabled in the Google Cloud project where the DNS private zone is created.Cevap
- CRely on IAM policy inheritance from the Organization resource level to automatically authorize all VPC networks across child projects for private DNS resolution.
- DDeploy a Regional External Application Load Balancer between `backend-vpc` and `analytics-vpc` to route port 53 DNS queries between the networks.
Cevap
The correct actions are to add both VPC networks (`backend-vpc` and `analytics-vpc`) to the authorized networks list of the Cloud DNS private zone and to ensure the Cloud DNS API is enabled in the host project.
To allow VMs across multiple VPC networks to resolve records in a Cloud DNS private zone, each VPC network must be explicitly added to the private zone's authorized networks list. Additionally, the Cloud DNS API must be enabled in the project containing the DNS resources for the service to function.
Adım Adım Çözüm
Anahtar Kavram
Cloud DNS Private Zone Authorization & VPC Network Scope