hessu
commented
12 years ago Mixed feelings - at some point it actually did use a random order. Some people wish to prefer some servers (i.e. connect to their own or the closest server first at startup), so they wish to have a known connect order. When that server goes down, aprsc will connect to the second configured Uplink. When that's breaks, it'll go to the third one, etc.
aprsc does randomize the starting point for DNS round robin, so if you connect to rotate.aprs.net, it'll always start from a random core server. T2 people could just as well have a hubrotate.aprs2.net for the leafs to use with 5 A records (that might have some other benefits too), so maybe this is just a configuration issue, and people can actually do whichever they prefer.
Please check out the linked message below - I'd like to use the tracker for keeping track of bugs and issues that I might forget about. Discussion and questions should go to the aprsc discussion group, where other aprsc users can read them and learn from them. They won't be reading through closed bug tickets. It would probably be good for them to see this.
On the other hand, maybe bug tickets updates should be mailed to the group. I don't know.
Would it be possible to randomly shuffle the upstream servers to avoid flooding the same server sequence?