An organization is establishing hybrid connectivity between their Google Cloud environment and their on-premises data center using Cloud VPN. Compute Engine instances located in a Virtual Private Cloud (VPC) named `prod-vpc` need to resolve domain names under the custom corporate domain `internal.example.com`, which are managed by an on-premises authoritative DNS server at IP address `192.168.1.50`. Which action should you take in Cloud DNS to enable internal name resolution for these on-premises hosts from `prod-vpc`?
- Create a Cloud DNS forwarding zone for the domain `internal.example.com`, specify the DNS server IP `192.168.1.50` as the target DNS server, and set `prod-vpc` as the authorized network.Cevap
- BEnable the Cloud DNS API inside the host project hosting the VPN gateway and configure an Inbound DNS Policy on `prod-vpc` pointing to IP `192.168.1.50`.
- CCreate a public Cloud DNS zone for `internal.example.com` at the GCP Organization level and apply an IAM boundary policy to block Internet access.
- DDeploy an Internal Regional Application Load Balancer with a backend service pointing to `192.168.1.50` on UDP port 53 and map `internal.example.com` to the load balancer forwarding rule IP.
Cevap
Create a Cloud DNS forwarding zone for the domain internal.example.com, specify the DNS server IP 192.168.1.50 as the target DNS server, and set prod-vpc as the authorized network.
To allow Compute Engine instances in a GCP VPC to resolve domain names hosted on an on-premises DNS server, you create a Cloud DNS private zone configured for DNS forwarding (an outbound forwarding zone). By setting the target domain to `internal.example.com`, specifying the destination on-premises DNS server IP `192.168.1.50`, and authorizing `prod-vpc`, Cloud DNS proxies all incoming queries for that domain from the VPC across the Cloud VPN tunnel.
Adım Adım Çözüm
Anahtar Kavram
Cloud DNS Outbound Forwarding Zones
Tahmini Süre:2m 0s