A cloud engineer is designing internal name resolution between a Virtual Private Cloud (VPC) network named `vpc-app` and an on-premises network connected via Cloud Interconnect. Compute Engine instances in `vpc-app` need to resolve corporate domain records hosted on an on-premises DNS server at `10.2.0.50`. Simultaneously, on-premises workloads need to resolve hostnames within a private Cloud DNS zone named `internal.example.com` attached to `vpc-app`. Which TWO configuration actions must be performed in Google Cloud to satisfy these bidirectional DNS requirements?
- Create a Cloud DNS forwarding zone for the on-premises domain, specifying `10.2.0.50` as the target name server, and authorize `vpc-app` to access the zone.Answer
- Create a Cloud DNS server policy for `vpc-app` with inbound DNS forwarding enabled, and configure the on-premises DNS server to forward queries for `internal.example.com` to the Cloud DNS inbound forwarder IP addresses.Answer
- CEnable the Cloud DNS API in the root organization resource level rather than the project hosting `vpc-app` to automatically allow cross-environment DNS routing.
- DDeploy a Regional External Application Load Balancer to proxy raw UDP port 53 DNS requests from `vpc-app` to the on-premises DNS server at `10.2.0.50`.
Answer
The correct configuration requires creating a Cloud DNS forwarding zone pointing to `10.2.0.50` for outbound resolution, and enabling inbound DNS forwarding on a server policy for `vpc-app` so on-premises clients can reach Cloud DNS via regional inbound entry point IPs.
Bidirectional DNS resolution requires two components: outbound forwarding from Cloud DNS to the on-premises DNS server (achieved via a Cloud DNS forwarding zone) and inbound forwarding from on-premises to Cloud DNS (achieved by enabling inbound DNS forwarding in a Cloud DNS server policy).
Step-by-Step Solution
Key Concept
Bidirectional Cloud DNS forwarding between VPC networks and on-premises DNS infrastructure.
Estimated Time:2m 0s