QuestionQ131

VerifiedEnsuring the successful operation of a cloud solution

Your organization follows a hybrid cloud strategy, with some applications running on Google Cloud. A VPN tunnel links your VPC in Google Cloud to your company's on-premises network. Several applications hosted in Google Cloud must connect to an on-premises database server, and you want to avoid having to update the IP configuration across all of your applications whenever the database's IP address changes.

What should you do?

Explanation

Creating a Cloud DNS private zone lets you map a stable DNS hostname to the on-premises database's IP address. Applications are then configured to reference the DNS name rather than a hard-coded IP. If the database's IP address changes, you simply update the single DNS record in the private zone, and every application automatically resolves the new IP the next time it performs a DNS lookup — no per-application reconfiguration is required. Cloud NAT only affects outbound egress translation for instances without external IPs and does not provide name resolution for on-premises resources. Custom instance metadata would still require manual updates on every instance whenever the IP changes, providing no abstraction benefit. Compute Engine's internal DNS resolves only internal Google Cloud VM names, not external on-premises hosts, so it cannot be used to reach the on-premises database.

Learn more

Community Discussion

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