Forum


Notice to all users

We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020

Results 1 to 7 of 7
  1. #1
    Join Date
    August 2016
    Posts
    6

    TeamSpeak 3.1 [Beta] on Windows (tsdns error)

    for the domain does not go through a tsdns server

  2. #2
    Join Date
    April 2014
    Posts
    2
    Hi,

    I'm having the same issue, I'm using SRV redirections that were working so far. Since the last update, it won't resolve my root domain or subdomains.

  3. #3
    Join Date
    October 2003
    Location
    Germany
    Posts
    2,527
    Any examples for domain names that are no longer working?

  4. #4
    Join Date
    January 2013
    Location
    Thüringen
    Posts
    342

    I have the same Problem.

    21.08.2016 17:14:26 ClientUI Info Connect to server: voice.teamspeak.com
    21.08.2016 17:14:26 ClientUI Info Trying to resolve voice.teamspeak.com
    21.08.2016 17:14:26 TSDNS Info A/AAAA DNS resolve successful, "voice.teamspeak.com" =(h: 194.97.114.2 p:0)
    21.08.2016 17:14:26 TSDNS Info SRV DNS resolve successful, "_tsdns._tcp.teamspeak.com" =(h: voice.teamspeak.com p:41144)
    21.08.2016 17:14:26 TSDNS Info SRV DNS resolve unsuccessful, "_ts3._udp.voice.teamspeak.com" DNS server returned answer with no data
    21.08.2016 17:14:26 TSDNS Info A/AAAA DNS resolve successful, "voice.teamspeak.com" =(h: 194.97.114.2 p:0)
    21.08.2016 17:14:28 TSDNS Info TSDNS queried unsuccessfully 194.97.114.2:41144
    21.08.2016 17:14:28 TSDNS Info No TSDNS found
    21.08.2016 17:14:28 ClientUI Info Lookup finished: query= wasTSDNS=1 error=2
    21.08.2016 17:14:28 ClientUI Info Failed to resolve voice.teamspeak.com

    When i wrote the normal IP than is it working.

  5. #5
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,368
    Quote Originally Posted by Rikku View Post
    Code:
    21.08.2016 17:14:26    ClientUI    Info    Connect to server: voice.teamspeak.com    
    21.08.2016 17:14:26    ClientUI    Info    Trying to resolve voice.teamspeak.com    
    21.08.2016 17:14:26    TSDNS    Info    A/AAAA DNS resolve successful, "voice.teamspeak.com" =(h: 194.97.114.2 p:0)    
    21.08.2016 17:14:26    TSDNS    Info    SRV DNS resolve successful, "_tsdns._tcp.teamspeak.com" =(h: voice.teamspeak.com p:41144)    
    21.08.2016 17:14:26    TSDNS    Info    SRV DNS resolve unsuccessful, "_ts3._udp.voice.teamspeak.com" DNS server returned answer with no data    
    21.08.2016 17:14:26    TSDNS    Info    A/AAAA DNS resolve successful, "voice.teamspeak.com" =(h: 194.97.114.2 p:0)    
    21.08.2016 17:14:28    TSDNS    Info    TSDNS queried unsuccessfully 194.97.114.2:41144    
    21.08.2016 17:14:28    TSDNS    Info    No TSDNS found    
    21.08.2016 17:14:28    ClientUI    Info    Lookup finished: query= wasTSDNS=1 error=2    
    21.08.2016 17:14:28    ClientUI    Info    Failed to resolve voice.teamspeak.com
    Of the succeeding lookups, SRV TSDNS is the one with the highest priority. However, this should not keep the client from connecting as TSDNS allows the user to intentionally refuse to answer a query.
    Only question: Why didn't the TSDNS server answer?
    Code:
    21.08.2016 20:29:58    ClientUI    Info    Connect to server: voice.teamspeak.com    
    21.08.2016 20:29:58    ClientUI    Info    Trying to resolve voice.teamspeak.com    
    21.08.2016 20:29:58    TSDNS    Info    SRV  DNS resolve successful, "_tsdns._tcp.teamspeak.com" =(h:  voice.teamspeak.com p:41144)    
    21.08.2016 20:29:58    TSDNS    Info    A/AAAA DNS resolve successful, "voice.teamspeak.com" =(h: 194.97.114.2 p:0)    
    21.08.2016 20:29:58    TSDNS    Info    SRV DNS resolve unsuccessful,  "_ts3._udp.voice.teamspeak.com" DNS server returned answer with no data     
    21.08.2016 20:29:58    TSDNS    Info    A/AAAA DNS resolve successful, "voice.teamspeak.com" =(h: 194.97.114.2 p:0)    
    21.08.2016 20:29:58    TSDNS    Info    TSDNS found at  194.97.114.2:41144 and queried successfully. Result: (h: 194.97.114.2  p:9987)    
    21.08.2016 20:29:58    ClientUI    Info    Lookup finished:  ip=194.97.114.2 port=9987 query=voice.teamspeak.com wasTSDNS=1 error=0     
    21.08.2016 20:29:58    ClientUI    Info    Resolve successful: 194.97.114.2:9987

  6. #6
    Join Date
    January 2013
    Location
    Thüringen
    Posts
    342

    Solved its now working :)

    23.08.2016 15:22:01 ClientUI Info Trying to resolve voice.teamspeak.com
    23.08.2016 15:22:01 TSDNS Info A/AAAA DNS resolve successful, "voice.teamspeak.com" =(h: 194.97.114.2 p:0)
    23.08.2016 15:22:01 TSDNS Info SRV DNS resolve successful, "_tsdns._tcp.teamspeak.com" =(h: voice.teamspeak.com p:41144)
    23.08.2016 15:22:01 TSDNS Info SRV DNS resolve unsuccessful, "_ts3._udp.voice.teamspeak.com" DNS server returned answer with no data
    23.08.2016 15:22:01 TSDNS Info A/AAAA DNS resolve successful, "voice.teamspeak.com" =(h: 194.97.114.2 p:0)
    23.08.2016 15:22:01 TSDNS Info TSDNS found at 194.97.114.2:41144 and queried successfully. Result: (h: 194.97.114.2 p:9988)
    23.08.2016 15:22:01 ClientUI Info Lookup finished: ip=194.97.114.2 port=9988 query=voice.teamspeak.com wasTSDNS=1 error=0
    23.08.2016 15:22:01 ClientUI Info Resolve successful: 194.97.114.2:9988
    23.08.2016 15:22:01 ClientUI Info Blacklist check ok
    23.08.2016 15:22:01 ClientUI Info Initiating connection: 194.97.114.2:9988
    23.08.2016 15:22:01 TSDNS Info A/AAAA DNS resolve successful, "blacklist.teamspeak.com" =(h: 46.105.112.65 p:0)
    23.08.2016 15:22:01 ClientUI Info Connect status: Connecting

  7. #7
    Join Date
    June 2011
    Location
    Germany
    Posts
    4,368
    Quote Originally Posted by tsdns_settings.ini.sample
    Code:
    # Also allowed as value is the special string "NORESPONSE", which makes the
    # TSDNS server answer not answer this query...this can be useful in scenarios
    # where multiple TSDNS servers exist and you wish to let "the other" TSDNS
    # server handle this request. Or you wish regular domain resolving to take
    # place for some cases.
    This wouldn't make any sense anymore then.

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. TSDNS Error
    By Qieme in forum Android
    Replies: 7
    Last Post: July 11th, 2014, 04:25 PM
  2. Teamspeak 3 windows audio error
    By Berttactical in forum Windows
    Replies: 4
    Last Post: May 8th, 2014, 12:02 AM
  3. TSDNS as Windows Service?
    By bakura in forum Server Support
    Replies: 0
    Last Post: July 10th, 2012, 04:22 PM
  4. Replies: 3
    Last Post: July 18th, 2011, 04:00 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
  •