■Background
Designed to migrate on-premise servers to the AWS environment.
We assume HTTP access from an in-house client to a web server installed in a VPN or leased-line AWS environment.
The client belongs to the corporate domain and refers to the corporate DNS server.
■Question
How do clients resolve ALB names when installing ALB to distribute load to web servers?
I checked online and found out that ALB cannot have a fixed IP.
Therefore, I think the client will access it by specifying the DNS name of ALB.
I imagined that Route 53 probably associates the DNS name assigned when creating ALB with the dynamically assigned IP each time, but I think that would mean that clients would have to go to Route 53 as DNS to resolve ALB's name.
I'm still studying AWS, so I don't know how it works.
Internal ALB endpoint name resolution returns the private IP address of the VPC, but this DNS record appears to be visible not only on the VPC internal DNS server but also on the outward DNS server.
Can external dns resolve the name of the aws internal elb?
Therefore, I think you can access it with the ALB endpoint name, or register the appropriate hostname to refer to the ALB endpoint in CNAME with the corporate DNS server.
I think clients will have to go to Route 53 as DNS to resolve ALB's name.
As a pre-AWS issue, you don't seem to understand how Internet DNS works.Please study DNS operation yourself.For example, Internet 10-minute course: DNS illustrates the "Inquiry Flow in DNS", but on a typical PC, the "Server to Contact DNS Server" is configured as a DNS server."The ""Server for Contacting DNS Servers"" connects to DNS servers around the world, including root servers, and obtains address information."Of course, AWS addresses such as amazonaws.com will be retrieved from the DNS server provided by Amazon Route 53.
Therefore, "Server for Contacting DNS Servers" = If the "Internal DNS Server" in the questionnaire is configured to obtain addresses from all over the world, including ALB.
© 2024 OneMinuteCode. All rights reserved.