QuestionQ32

VerifiedConfiguring and implementing hybrid and multi-cloud network interconnectivity

You are designing the DNS topology for an enterprise migrating its applications to Google Cloud. The company has a robust on-premises Active Directory and DNS infrastructure that remains authoritative for its existing internal domains. New Google Cloud applications will require their own private DNS records.

You need to provide seamless resolution for all internal resources across both on-premises and cloud workloads, without publicly exposing internal DNS records, while minimizing the administrative effort of DNS management in the hybrid environment.

What should you do?

Explanation

Cloud DNS server policies support managed hybrid name resolution. Inbound DNS forwarding lets on-premises resolvers query private Cloud DNS zones through internal forwarding entry points, and outbound DNS forwarding lets VPC workloads use on-premises DNS servers for existing internal domains. This keeps private records private and retains the on-premises DNS service as authoritative without operating self-managed DNS proxy servers or migrating all existing records.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!