I'm currently running a MeteorJS application on Amazon. MeteorJS has a plugin that allows each server to act as a load balancer or a worker for said load balancers. I can spin up any number of workers with no problems as the workers check in with the load balancers and they are added to the pool.
The issue I'm having is scaling the load balancers. Each load balancer needs a valid DNS A record. I was thinking that perhaps I would add a bunch of A records pointing to IP addresses that will be used if I need to spin up additional load balancers. However, my concern is that this will result in poor performance due to users browsers trying multiple addresses.
Is it poor practice to have dead A records behind your primary domain? i.e.
somewebsite.com
loadbalancer1.somewebsite.com -> Online
loadbalancer2.somewebsite.com -> Online
loadbalancer3.somewebsite.com -> Offline
loadbalancer4.somewebsite.com -> Offline
I was hoping that Amazon Route 53 would help me with this, but they only provide failover services. Ideally these records that point to offline servers would not be published