Google Professional Cloud Network Engineer Question 528
Single answerGoogle Cloud PlatformYour company is migrating its on-premises DNS infrastructure to Google Cloud DNS. As part of the migration, you need to ensure that internal resources in your company’s private network can continue to resolve private DNS names while also resolving public domains. What is the best configuration to achieve this in Google Cloud DNS?
- A
Create a public DNS zone for the private domain and configure it to resolve internal IPs.
- B
Set up a private DNS zone for the private domain and ensure the VPC network is attached to the zone.
- C
Set up a forwarding zone to forward queries for the private domain to your existing on-premises DNS server.
- D
Set up a split-horizon DNS with both private and public zones for the private domain.
Show answer and explanation
Correct answer: B
Explanation
To securely resolve private domain names within your VPC, using a private DNS zone in Google Cloud DNS is the best option. This ensures that DNS queries for private resources are handled within the VPC and are not exposed to the public internet. The private zone must be attached to the appropriate VPC network to function correctly.
- A. Incorrect.
Creating a public DNS zone for private domains is not secure or appropriate because it exposes internal DNS records to the internet.
- B. Correct.
Setting up a private DNS zone in Google Cloud DNS is the correct approach. It ensures that private DNS names are resolved securely within your VPC network.
- C. Incorrect.
Forwarding zones are used to forward DNS queries to an external DNS server, but this does not fully migrate the DNS to Google Cloud and may introduce latency or reliability concerns.
- D. Incorrect.
Split-horizon DNS is a valid concept for managing both public and private domains, but it is not directly supported as a single feature in Google Cloud DNS. You would need to configure separate public and private zones manually.