No I'm not using ELB IPs directly. My concern is this scenario: 1) ELB with IP 1.2.3.4 develops an issue (AWS internal outage) 2) DNS resolver for an end user

No I'm not using ELB IPs directly. My concern is this scenario: 1) ELB with IP 1.2.3.4 develops an issue (AWS internal outage) 2) DNS resolver for an end user of my app has the pair myapp.elb.amazonaws.com/1.2.3.4 cached previously for longer than the TTL (resolvers are notorious for this) 3) When end user resumes work within the app, they're referencing the LB at 1.2.3.4, which is down. Hence my question. Is the mapping of 1.2.3.4 to its respective LB static or virtual? Meaning, does AWS keep moving the 1.2.3.4 around to a healthy LB service seamlessly? Thanks