[jibs]

ooh, this looks really problematic on multiple levels (why wait for JS etc).

A simple solution, which I've used--and I think the OPs situation is similar--is to just have an additional A-record pointed to the ELB, this should work unless the OP is doing something really fancy. No need for route-53, even go-daddy will let you do this.

However, route-53 gives you much better TTL, so if you ever need to re-route..

[ceejayoz]

ELBs change IP if they have to scale up. You really shouldn't point an A record at one.

[jibs]

...which is why they recommend you never use the ip, instead AWS provides a hostname, which is invariant...

[ceejayoz]

Which is why you can't use an A record, as I stated.