Your organization is establishing a hybrid cloud architecture connecting an on-premises data center to a Google Cloud Virtual Private Cloud (VPC) network via Cloud VPN. On-premises client machines need to resolve private DNS queries for instances hosted in GCP ending with `.internal.example.com`. You need to configure Cloud DNS to allow on-premises systems to resolve these names. Which TWO configuration steps are required to satisfy this requirement?
- Create an Inbound DNS server policy in Cloud DNS assigned to the target VPC network.Cevap
- Configure the on-premises DNS servers to forward queries for `.internal.example.com` to the Cloud DNS Inbound forwarder IP addresses.Cevap
- CEnable the Cloud DNS API within the on-premises directory project management workspace instead of the GCP VPC host project.
- DCreate a Cloud DNS Outbound forwarding zone pointing to the on-premises DNS server IP addresses to handle client requests originating from on-premises.
Cevap
To enable on-premises clients to resolve GCP private DNS records over Cloud VPN, you must create an Inbound DNS server policy assigned to the VPC network to allocate inbound forwarder IP addresses, and then configure the on-premises DNS servers to forward domain queries for `.internal.example.com` to those entry-point IP addresses.
Enabling on-premises resolution of GCP private DNS names requires an Inbound DNS server policy attached to the VPC network. This creates entry-point IP addresses inside the VPC subnets. The on-premises DNS server must then be configured with conditional forwarding to target those entry-point IPs for the GCP internal domain name space.
Adım Adım Çözüm
Anahtar Kavram
Cloud DNS Inbound Forwarding for Hybrid Architecture