Question

A retail company runs applications on Compute Engine instances in a VPC connected to their on-premises data center via Cloud VPN. The Compute Engine workloads must resolve private hostnames for internal on-premises services (e.g., ldap.corp.internal), and on-premises servers must resolve the private DNS names of Google Cloud resources managed in a Cloud DNS private zone. What should the architect configure to enable bidirectional private DNS resolution?

Accepted Answer

Configure Cloud DNS with a private forwarding zone pointing to the on-premises DNS servers, and set up an inbound DNS server policy so on-premises servers can query Cloud DNS via forwarding to Google Cloud.

Answer

Enable public Cloud DNS zones for both the on-premises domain and the Google Cloud domain, and allow public internet resolution.

Answer

Add host entries for every on-premises and Google Cloud resource to the /etc/hosts file on each Compute Engine instance and each on-premises server.

Answer

Deploy a self-managed BIND DNS server on a Compute Engine instance and repoint all resolution to it without using Cloud DNS features.