10 50 5060 server-0.aws.domain.com
10 50 5060 server-1.aws.domain.com
I don't think you need this record... SRV records need to start with _sip._tcp as far as I've read. If you're trying to use it for http load balancing, I'm afraid no browsers honor this. Kind of sucks.
Thanks guys for mentioning that there can be multiple A records for the same domain address. This was very helpful.
Now it seems that just having the A records and the SRV records isn't enough... I'm just getting a round robin across the A records... (this is on one of the new Grandstream GRP2614 deskphones... even though I told it to specifically use SRV to resolve DNS).
I'm going to try a NAPTR record to see if this fixes it so that the SRV priority and weight parameters work.