Hey,

according to this http://forum.teamspeak.com/threads/1...light=priority the client should follow the srv-prio given in the dns-record (if they implemented it)
But instead, if you setup two srv-records with different priority at once it does weird stuff

Code:
12.04.2017 18:11:36	ClientUI	Info	Connect to server: exampledomain.de	
12.04.2017 18:11:36	ClientUI	Info	Trying to resolve exampledomain.de	
12.04.2017 18:11:36	TSDNS	Info	SRV DNS resolve successful, "_tsdns._tcp.exampledomain.de" =(h: tsdns.exampledomain.de p:41144)	
12.04.2017 18:11:36	TSDNS	Info	SRV DNS resolve successful, "_ts3._udp.exampledomain.de" =(h: ts3.exampledomain.de p:9986), (h: ts3backup.exampledomain.de p:9986)	
12.04.2017 18:11:36	TSDNS	Info	A/AAAA DNS resolve successful, "exampledomain.de" =(h: 88.2.38.120 p:0)	
12.04.2017 18:11:37	TSDNS	Info	A/AAAA DNS resolve for possible TSDNS successful, "exampledomain.de" =(h: 88.2.38.120 p:0)	
12.04.2017 18:11:37	TSDNS	Info	A/AAAA DNS resolve successful, "ts3.exampledomain.de" =(h: 88.2.38.118 p:0)	
12.04.2017 18:11:37	TSDNS	Info	A/AAAA DNS resolve successful, "ts3backup.exampledomain.de" =(h: 88.99.227.155 p:0)	
12.04.2017 18:11:37	ClientUI	Info	Lookup finished: ip=88.2.38.118 port=9986 query=exampledomain.de error=0	
12.04.2017 18:11:37	ClientUI	Info	Resolve successful: 88.2.38.118:998688.99.227.155:9986
Somehow it works, but maybe not for erveryone who tries to join the server

Especially the android client got problems while attempting to connect. It seems it switches randomly between the two entries every time you try it but it shouldn't because of different priorities in the srv records, right?

Any ideas?