Your organization needs to configure Google Cloud DNS to resolve internal service hostnames to private IP addresses within a Virtual Private Cloud (VPC) network. In what order should an engineer perform the administrative steps to establish and validate internal DNS resolution?
- 1Create a Cloud DNS private managed zone specifying the internal domain name.
- 2Authorize the target VPC network to access the private managed zone.
- 3Create an A record set within the private managed zone mapping the hostname to the private IP address.
- 4Execute a DNS lookup tool (such as dig or nslookup) from a Compute Engine VM inside the authorized VPC network.
Answer
The correct sequence is: 1) Create the Cloud DNS private managed zone, 2) Authorize the target VPC network, 3) Add the A record set mapping the hostname to the private IP address, and 4) Perform a DNS lookup test from a VM within the authorized VPC network.
The deployment workflow follows a logical dependency chain: First, create the private managed zone to establish the internal DNS namespace. Second, authorize the specific VPC network so instances in that network have permission to query the zone. Third, populate the zone by adding A records mapping service names to internal IP addresses. Fourth, test and verify resolution from a VM located inside the authorized network.
Step-by-Step Solution
Key Concept
Cloud DNS Private Zone Creation and VPC Network Authorization Sequence
Estimated Time:1m 30s