Question

Your organization runs three separate VPC networks (prod-vpc, staging-vpc, and tools-vpc) that are not peered with each other. A central 'shared-services-vpc' hosts a Cloud DNS private zone (internal.example.com) plus an inbound forwarding configuration that resolves on-premises records. You need all three isolated VPCs to resolve both the internal.example.com records and the on-premises records managed in shared-services-vpc, without creating full mesh VPC peering and without duplicating zone data in each VPC. What should you implement?

Accepted Answer

Create a Cloud DNS peering zone in each of the three VPCs that targets shared-services-vpc as the DNS peering network.

Answer

Configure VPC Network Peering between each isolated VPC and shared-services-vpc, then rely on automatic DNS resolution across the peering.

Answer

Create a private DNS forwarding zone in each VPC pointing to the inbound forwarder IP of shared-services-vpc for all queries.

Answer

Attach all three VPCs as spokes to a Network Connectivity Center hub so DNS zones are shared automatically across the mesh.