When you create a Load Balancer, AWS assigns a public domain name to your Load Balancer. In your application, you can use the domain name as-is or create a CNAME  (i.e app.cloudsolutions.academy) in your DNS configuration, which maps to your AWS assigned domain name (…amazonaws.com).

When the application sends a request to the Load balancer , AWS responds with one of more ip addresses and the request is served by the ip address. Based on your application traffic load,  AWS Load balancer updates the ip address associated with the domain name. With AWS Load balancer, you always deal with domain name and not the ip address directly. This is different from Google Cloud Load Balancer, which uses a single Any cast IP address for load balancer implementation. For more details, refer to – What is Anycast IP address and how does Google Cloud Load Balancer works

Any changes to domain name configuration, usually have some lag, as it takes time to propagate across the global DNS network. Client may also cache the DNS, so the cache needs to be invalidated.  To overcome the caching issue, you need to set Time to Live  (TTL) parameter in the DNS settings, so DNS lookups and refresh can happen based on TTL value. The recommended value is 60 seconds.