Question

A retail company runs an internal application in a Google Cloud VPC. The same hostname, app.retail.internal, must resolve to a private RFC 1918 address for clients inside the VPC, but to a public-facing external IP for clients querying from the internet. The DNS team wants a Google-managed solution that avoids maintaining separate hostnames and works without deploying custom DNS servers. Which Cloud DNS approach should they implement?

Accepted Answer

Create a Cloud DNS private zone and a separate public managed zone, both named for a domain you own such as corp.retailexample.com, and add differing A records for app.corp.retailexample.com in each — using Cloud DNS split-horizon (response policy is not required).

Answer

Create a single public managed zone with two A records for app.retail.internal and rely on Cloud DNS to return the private record only to internal VPC clients.

Answer

Deploy BIND on a Compute Engine instance to serve split-horizon views, and point the VPC's DNS server policy to that instance.

Answer

Use Cloud DNS DNS peering to forward app.retail.internal queries from the VPC to the public zone while internet clients query the public zone directly.