Re: Internal load balancing and DNS names

mountaincode2 · 11-26-2024 09:30 PM

What is the purpose of having an internal DNS name for the forwarding rule of a load balancer:

https://cloud.google.com/load-balancing/docs/dns-names

What is the problem that we are trying to solve by creating a service label, which is then used to create an internal DNS name?

kensan

Hi @mountaincode2 ,

Welcome to Google Cloud Community!

An internal DNS name facilitates seamless VM-to-VM communication within a Virtual Private Cloud (VPC). It allows virtual machines (VMs) in the same network to access each other using easily resolvable internal DNS names instead of relying on changing IP addresses.

When used in the forwarding rule of a load balancer, an internal DNS name simplifies both configuration and maintenance. Rather than depending on IP addresses which may change over time due to scaling, failover, or maintenance the DNS name remains consistent, ensuring stable connections.

Additionally, using an internal DNS name enhances security by restricting access to trusted internal services only. It prevents external clients from reaching the load balancer through a public IP or DNS, thus ensuring that the load balancer is isolated within the internal network and is only accessible by authorized services.

I hope the information above is helpful.

mountaincode2

Thank you, @kensan .

Your explanation is v helpful.

The documentation talks about creating a forwarding rule with a service label for the following load balancers:

https://cloud.google.com/load-balancing/docs/dns-names#adding_label

But how does one create a forwarding rule with a service label when the load balancer is created using GKE (https://cloud.google.com/kubernetes-engine/docs/how-to/internal-load-balancing#deploy). Does the same process apply.

mountaincode2

Can someone please provide any insight on this.

mountaincode2

Seeking help on this one please. Thank you!