Forum

Results 1 to 6 of 6
  1. #1
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266

    TeamSpeak Android App wrong SRV record evaluation

    The current TeamSpeak Android App is not working properly with multiple SRV records! I use a SRV based fail over configuration with three seperate TeamSpeak-Servers sharing basicly the same setup in geographically disjunct locations and netwroks to get a level of desaster and ddos protection. This works absolutly fine with the windows desktop client. That allways connects first to server "munin". If "munin" has problems, all connect clients will switch to "odin" with the auto-reconnect feature of TeamSpeak. New connects in the case of "munin" having problems will be directed to "odin" also.

    The android client on the other hand with a stupid chance of >66% connects to "hugin" on the first try. You'll have to "play" the connect/disconnect game until at some point you got a connection to "munin". You'll probably have to connect to "odin" and "hugin" multiple times before that stupid Android App reaches "munin" in the end.

    Please fix that, so that the Android App honors the SRV priority!

    Code:
    # dig _ts3._udp.ts.xxxxx.de SRV
    
    ; <<>> DiG 9.9.4-RedHat-9.9.4-38.el7_3.3 <<>> _ts3._udp.ts.xxxxx.de SRV
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9283
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 4096
    ;; QUESTION SECTION:
    ;_ts3._udp.ts.xxxxx.de. IN      SRV
    
    ;; ANSWER SECTION:
    _ts3._udp.ts.xxxxx.de. 85668 IN SRV     1 0 20022 munin.xxxx.de.
    _ts3._udp.ts.xxxxx.de. 85668 IN SRV     3 0 20022 odin.xxxx.de.
    _ts3._udp.ts.xxxxx.de. 85668 IN SRV     5 0 20022 hugin.xxxx.de.
    
    ;; Query time: 22 msec
    ;; SERVER: 172.22.172.22#53(172.22.172.22)
    ;; WHEN: So Jun 11 10:32:42 CEST 2017
    ;; MSG SIZE  rcvd: 142

  2. #2
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,365
    The high chance might be the result of mixing up Weight and Priority (results in 55.5%).

  3. #3
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266
    Well accordning to the RFC thar behavior is is not ok.

    The priority field determines the precedence of use of the record's data. Clients should use the SRV records with the lowest-numbered priority value first, and fall back to records of higher value if the connection fails. If a service has multiple SRV records with the same priority value, clients should load balance them in proportion to the values of their weight fields.
    As you might have noticed... the weight on all record is "0", the priority is 1, 3 and 5. So tell my why on earth he prefers the record with priority 5 that is simply wrong... As I have said the windows client handles it correct.

    If load balancing would have been a desired feature I would have set priority for all record to "1" and then weight to 49, 34, 17 ...

  4. #4
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,365
    Of course it is not. It was just a guess what TeamSpeak might have done wrong.

  5. #5
    Join Date
    June 2008
    Posts
    18,229
    We will evaluate and eventually improve that behaviour for the Android client.
    When sending me private messages: Please make sure to include reference link to your forum thread or post.

    TeamSpeak FAQ || What should i report, when i open a client thread?

  6. #6
    Join Date
    December 2009
    Location
    Portugal
    Posts
    492
    Just wanted to say that this just happened to me. Here is a sample of our records

    Code:
    ; <<>> DiG 9.9.5-9+deb8u12-Raspbian <<>> _ts3._udp.ts.xxx.eu SRV
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12165
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 2, ADDITIONAL: 3
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 1280
    ;; QUESTION SECTION:
    ;_ts3._udp.ts.xxx.eu.    IN      SRV
    
    ;; ANSWER SECTION:
    _ts3._udp.ts.xxx.eu. 10800 IN    SRV     10 100 9989 ts.yyy.net.
    _ts3._udp.ts.xxx.eu. 10800 IN    SRV     20 100 9987 ts-backup.zzz.eu.
    
    ...
    Thanks

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. Replies: 2
    Last Post: June 5th, 2014, 10:33 AM
  2. [Resolved] _tsdns SRV record in Android
    By PotaBlava in forum Android
    Replies: 19
    Last Post: January 17th, 2014, 09:51 AM
  3. [No BUG] Permission Evaluation
    By borstenwolf in forum Bug Reports [EN/DE]
    Replies: 2
    Last Post: June 1st, 2010, 04:51 PM

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •