Bypasses round-robin DNS pool by locking into first IP only

What is the issue?

A round-robin DNS entry helps distribute load and avoid degraded service. transmission-daemon ignores all but the first address DNS returns and then hits only that single IP for every announce for as long as the DNS cache lives.

So if one out of five (for example) trackers has degraded service, but that's the one that was first in the list of the IP address returned when the DNS cache was populate, then every single transmission announce is going to the same tracker with degraded service, rather than rotating through them, for up to 24 hours if the DNS TTL is set to 86400. In fact, every single transmission announce going to the same tracker in the pool is likely to further degrade the service on that tracker!

Transmission should rotate among the returned IP addresses.

Which application of Transmission?

transmission-daemon

Which version of Transmission?

Transmission 4.1.2 (f234716f3e)