Cloud DNS Peering Zones and Hub-and-Spoke DNS Design

GCP Study Hub
November 8, 2026

A DNS peering zone tells Cloud DNS in one VPC network, the consumer, to resolve a domain using the resolution order of another VPC network, the target. Queries are answered as if they came from the target network, so the target's private zones and forwarding zones apply. DNS peering works only at the name resolution layer, so the consumer network needs no network path to the target network or to on-premises. That property is what makes peering zones useful for reusing one network's DNS configuration elsewhere, including in hub-and-spoke designs. For the Professional Cloud Network Engineer exam, it also explains where peering zones fall short.

How a peering zone resolves names

The consumer network holds the peering zone, names the domain it covers, and points at the target network. When a VM in the consumer network looks up a name in that domain, Cloud DNS answers it using whatever the target network can see. If the target has a forwarding zone for that domain, the query is forwarded from the target network to the target's name servers. If the target has a private zone for the domain, that zone answers.

Hub-and-spoke DNS

In a hub-and-spoke design, the hub VPC network holds the hybrid DNS configuration and the spokes borrow it:

  • A forwarding zone in the hub sends queries for the on-premises domain over the hub's hybrid connection to the on-premises DNS servers. It belongs in the hub because forwarded queries leave from the network that holds the zone, and the hub is the network with a route to those servers.
  • An inbound server policy in the hub creates entry points that on-premises DNS servers forward to when they need records in the hub's private zones.
  • A DNS peering zone in each spoke targets the hub, so spoke VMs resolve the on-premises domain and the hub's private zones without duplicating configuration.
  • A custom advertisement of 35.199.192.0/19 on the hub's Cloud Router gives the on-premises DNS servers a return path, because forwarded queries come from that range.

Because DNS peering works at the name resolution layer, spoke VMs resolve on-premises names through the hub without any network path of their own to the hub or to on-premises. Name resolution on its own therefore doesn't call for VPC Network Peering between the spokes and the hub. Network connectivity is a separate decision, driven by whether the spokes send other traffic on-premises.

DNS across organizations

Peering zones also work between companies. After two companies connect their networks, a peering zone in each company's network targets the partner's network for the partner's domain. The partner's existing forwarding zone then passes the query to the partner's own DNS servers, so both domains and both sets of DNS servers stay as they are.

The forwarded query leaves from the partner's network, so no return route for 35.199.192.0/19 is needed across the tunnel between the companies. Each company grants the other the DNS Peer role on its host project.

Limits of peering zones

  • VPC targets only. A peering zone can only target another VPC network, not DNS server IP addresses, so it cannot target on-premises servers directly. Reaching on-premises DNS takes a forwarding zone in a network with a route there.
  • Direction matters. The consumer must be the network that borrows resolution. Creating peering zones in the hub that target the spokes points them the wrong way.
  • Configuration dependency. A peering zone creates a dependency on the target network's configuration, which some compliance rules forbid. Where networks must stay fully independent, peering zones are not an option.
  • Visibility. Peering only exposes zones that are visible to the target network. A private zone that is not attached to the target network stays invisible to consumers.

Visibility and cross-project binding

Visibility depends on which networks a private zone is attached to, and cross-project binding is how a zone becomes visible to a network in another project. It lets a private zone created in one project be authorized on a VPC network that belongs to another project, such as a Shared VPC network in a host project. The zone stays owned and managed in the project where it was created, and VMs that use the bound network can resolve its records. A zone that is not attached to a network stays out of that network's resolution, whichever DNS feature points at it.

Choosing peering zones

For Professional Cloud Network Engineer scenarios, a peering zone fits when one VPC network should use DNS configuration that already exists in another VPC network, and no network path between them is required for resolution. It does not fit when the target is a set of DNS server addresses, when compliance forbids a dependency on another network, or when the records live in zones the target network cannot see.

Our Professional Cloud Network Engineer practice exams cover DNS peering zones alongside forwarding zones and inbound server policies, with detailed explanations that drill these distinctions.

Get tips and updates from GCP Study Hub

arrow