
Hybrid DNS has two directions. VMs in Google Cloud need to resolve names that live on on-premises DNS servers, and on-premises clients need to resolve names in Cloud DNS private zones. Cloud DNS handles these with different features. A private forwarding zone sends queries for an on-premises domain out to on-premises name servers, and an inbound server policy lets on-premises resolvers send queries in. A third setting, alternative name servers, is easy to confuse with both and behaves very differently. On the Professional Cloud Network Engineer exam, hybrid DNS designs depend on picking the right feature for each direction and getting the network details around forwarded queries right.
A Cloud DNS private forwarding zone sends queries for one domain, such as corp.example.com, to target name servers, such as on-premises DNS servers. Every other lookup still goes to Cloud DNS, so Compute Engine internal names and Cloud DNS private zones keep working. Because Cloud DNS is a managed service, a forwarding zone works for every VM in the network without touching individual instances.
That network-wide behavior is a large part of why forwarding zones are the standard tool. Pointing each VM's resolver configuration at on-premises servers instead means manual work on every instance, and it bypasses the metadata server resolver that Google Cloud name resolution depends on.
When Cloud DNS forwards to a private target, the queries do not come from the VM addresses. They come from the Google-owned range 35.199.192.0/19, and they travel through the VPC network's own hybrid connection. Two things must be true on-premises:
The VM subnet ranges play no part in this exchange, because forwarded queries never use them as a source address.
The forwarding zone must live in a network that has a route to the target servers, because the forwarded queries leave from that network. A few designs follow from that rule:
A DNS server policy has two settings that are often confused, inbound forwarding and alternative name servers.
Inbound forwarding lets on-premises clients resolve names in Cloud DNS. When you enable it, Cloud DNS creates entry point addresses in your VPC subnets. On-premises resolvers reach these addresses over Cloud VPN or Cloud Interconnect and conditionally forward queries for your private zones to them. An inbound policy works in one direction only. It does not help VMs resolve on-premises names.
The entry points are what make Cloud DNS reachable from outside the VPC network. Other resolver addresses don't fill that role. Public resolvers have no view of Cloud DNS private zones, and the metadata server address, 169.254.169.254, is link-local to each VM, so it can't be reached from on-premises.
Alternative name servers in an outbound server policy replace Cloud DNS resolution for the whole network. Every query from the VPC network goes to the listed servers, so .internal names, Cloud DNS private zones and normal Cloud DNS lookups all stop resolving unless those servers know them. With a forwarding zone instead, every lookup outside the forwarded domain, including .internal names, is still answered by the metadata server resolver. When only one domain should go on-premises, a forwarding zone is the right choice.
A full hybrid DNS design combines the pieces that each handle one direction:
This keeps the normal VPC resolver in place for everything else. For the Professional Cloud Network Engineer exam, the pattern to remember is that forwarding zones handle queries going out, inbound policies handle queries coming in, and alternative name servers replace Cloud DNS entirely rather than adding to it.
Our Professional Cloud Network Engineer practice exams cover hybrid DNS with Cloud DNS alongside DNS peering zones and Cloud Router custom advertisements, with detailed explanations that drill these distinctions.