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
    May 2012
    Location
    The 3rd dimension
    Posts
    956

    Angry SRV retrieved yet failed to connect to working server via SRV. Client log included

    Code:
    26/09/2013 19:11:26		Info	TeamSpeak 3 Client 3.0.13 (2013-09-24 07:47:44)	
    26/09/2013 19:11:26		Info	SystemInformation: Windows 8 (9200) x64 (AMD or Intel) Binary: 32bit	
    26/09/2013 19:11:26	Direct Sound	Debug	setting timer resolution to 1ms	
    26/09/2013 19:11:26		Info	*** Time [SPAWN_EVENTCONVERTER]: 262	
    26/09/2013 19:11:26	Query	Info	listening on 127.0.0.1:25639	
    26/09/2013 19:11:26		Info	Api version is not compatible for plugin: C:\Program Files (x86)\TeamSpeak 3 Client\plugins\winamp4ts3-x86.dll	
    26/09/2013 19:11:26		Info	*** Time [PLUGINS]: 126	
    26/09/2013 19:11:26	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - enter	
    26/09/2013 19:11:26	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - leave	
    26/09/2013 19:11:26		Info	*** Time [SERVERVIEWMANAGER]: 122	
    26/09/2013 19:11:26	Input	Info	Keyboard & mouse monitoring enabled	
    26/09/2013 19:11:27		Info	*** Time [MAINWINDOW]: 871	
    26/09/2013 19:11:27		Info	*** Time [INIT]: 872	
    26/09/2013 19:11:27	ClientUI	Info	Qt version: 4.8.3	
    26/09/2013 19:11:27	ClientUI	Info	Using configuration location: C:\Users\Username\AppData\Roaming\TS3Client\settings.db	
    26/09/2013 19:11:27	ClientUI	Info	Last update check was: Thu 26. Sep 00:23:53 2013	
    26/09/2013 19:11:27	ClientUI	Info	Connect to server: subdomain.domain.com	
    26/09/2013 19:11:27	ClientUI	Info	Trying to resolve subdomain.domain.com	
    26/09/2013 19:11:27	TSDNS	Info	DNS resolve successful, "subdomain.domain.com"=192.168.0.1	
    26/09/2013 19:11:28	ClientUI	Info	Lookup finished: 192.168.0.1 9987 subdomain.domain.com 0 0	
    26/09/2013 19:11:28	ClientUI	Info	Resolve successful: 192.168.0.1:9987	
    26/09/2013 19:11:28	ClientUI	Info	Blacklist check ok	
    26/09/2013 19:11:28	ClientUI	Info	Initiating connection: 192.168.0.1:9987 subdomain.domain.com	
    26/09/2013 19:11:28	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - enter	
    26/09/2013 19:11:28	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - leave	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::openDevice-enter	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS Buffer size: 960	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::openDevice-leave	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::startDevice-enter	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::startDevice-leave	
    26/09/2013 19:11:28	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - enter	
    26/09/2013 19:11:28	Windows Audio Session	Devel	DeviceDeleteList::waitForDeletes - leave	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::openDevice-enter	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS Buffer size: 960	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::openDevice-leave	
    26/09/2013 19:11:28	PreProSpeex	Info	Speex version: speex-1.2beta3	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::startDevice-enter	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::startDevice-leave	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::associateAECDevice-enter	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS Buffer size: 960	
    26/09/2013 19:11:28	Windows Audio Session	Debug	WAS::associateAECDevice-leave	
    26/09/2013 19:11:28	ClientUI	Info	Connect status: Connecting	
    26/09/2013 19:11:28	PktHandler	Devel	Puzzle solve time: 13	
    26/09/2013 19:11:29	TSDNS	Info	SRV DNS resolve successful, "_ts3._udp.subdomain.domain.com"=>"apollo.typefrag.com:9987" = 54.208.111.122:9987	
    26/09/2013 19:11:29	ClientUI	Info	Connect status: Connected	
    26/09/2013 19:11:30	ClientUI	Info	Connect status: Establishing connection	
    26/09/2013 19:11:30	ClientUI	Info	Connect status: Connection established	
    26/09/2013 19:11:30	PermManager	Info	Loading permissions from cache
    I have altered the domain and subdomain and IP but this is the actual log. As you can see the "subdomain.domain.com" SRV record was retrieved and thus should have connected to "54.208.111.122:9987" (port has been altered from the real port) but in fact it didn't it only connected to a server running actually on subdomain.domain.com instead of connecting to the SRV record that was indeed retrieved. This clearly must be a bug. It is intermittent and I see every day many times during a day people get sent to the other server and then they reconnect and get to the real server detailed in the SRV record.

    There is nothing wrong with the actual server detailed in the SRV record and it is a professionally hosted server. When I connect directly using the DNS and port the provider gives me I never get any failed connection attempts.

  2. #2
    Join Date
    May 2007
    Location
    Eastern NC
    Posts
    1,801
    So you are saying it connected to 192.168.0.1 9987 instead of 54.208.111.122:9987? It looks like a race condition, TS3 throws out several queries at once and the DNS resolved the 192.168.0.1 9987 address first and a server was found there, so even though SRV returned 54.208.111.122:9987 it was not used since a sucessful connection was made to 192.168.0.1 9987.

    Do I understand it right? If so I would say don't run a server at 192.168.0.1 9987 or change to a non-default port on this server. This should cause it to use the SRV result if it came in after the DNS one. I think.

  3. #3
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266
    So why do you have a A record and a SRV record with the same "subdomain.domain.com"? Just chance one and this race condition can't occur. There is no real need to have a A record for the teamspeak server itself. It's enough if the host has it's A record.

    You might want to consider something like: ts3.domain.com for the teamspeak and host.domain.com for the server. Then the SRV record would point to host.domain.com:9987.

    This race condition is also not a but to my mind.

  4. #4
    Join Date
    January 2010
    Location
    El Prat de Llobregat (Barcelona, Spain)
    Posts
    2,698
    Quote Originally Posted by Morthawt View Post
    Code:
    26/09/2013 19:11:26		Info	TeamSpeak 3 Client 3.0.13 (2013-09-24 07:47:44)	
    26/09/2013 19:11:27	ClientUI	Info	Connect to server: subdomain.domain.com	
    26/09/2013 19:11:27	ClientUI	Info	Trying to resolve subdomain.domain.com	
    26/09/2013 19:11:27	TSDNS	Info	DNS resolve successful, "subdomain.domain.com"=192.168.0.1	
    26/09/2013 19:11:28	ClientUI	Info	Lookup finished: 192.168.0.1 9987 subdomain.domain.com 0 0
    But 192.168.x.y is a private address. Using a SRV record to resolve a private address is "curious" and not always the connection to a private address from the outside is well done, or accepted, by all the routers.

  5. #5
    Join Date
    April 2011
    Location
    Germany
    Posts
    1,266
    Quote Originally Posted by PotaBlava View Post
    But 192.168.x.y is a private address. Using a SRV record to resolve a private address is "curious" and not always the connection to a private address from the outside is well done, or accepted, by all the routers.
    The SRV record delivers a public IP... just look again.

  6. #6
    Join Date
    January 2010
    Location
    El Prat de Llobregat (Barcelona, Spain)
    Posts
    2,698
    Quote Originally Posted by Barungar View Post
    The SRV record delivers a public IP... just look again.
    True, I was confused, I thought that the public IP resolved by the SRV and the private one were the same but reading again the initial post it is clear the server is in the public IP. Sorry.

    In any case, having a DNS pointing to a private IP and a SRV record pointing to a public IP is "risky" due to the race condition you comment in post #3 and better he follows your consideration.

  7. #7
    Join Date
    May 2012
    Location
    The 3rd dimension
    Posts
    956
    The reason I have a server actually running at the sub-domain as well is because people would get the problem where they fail to connect using my SRV record. So rather than be failed to connect I decided to alter my port to a default port so if they cannot get to the main server the will at least be in another server. I like the SRV record because it saves me making everyone type in a long dns name and then add a port because it is all contained in the SRV record.

    As for the public/private IP debate, I already stated I have altered some IP's and domain names etc. I am only dealing with public IP's

Thread Information

Users Browsing this Thread

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

Similar Threads

  1. TS3 client failed to connect to server
    By inferno321 in forum Windows
    Replies: 0
    Last Post: February 10th, 2014, 08:34 PM
  2. Replies: 1
    Last Post: March 15th, 2013, 02:41 PM
  3. Replies: 5
    Last Post: November 23rd, 2011, 02:09 PM
  4. Client: Failed to connect to server - until I reset my Network
    By sniperNZSAS in forum Bug Reports [EN/DE]
    Replies: 3
    Last Post: November 22nd, 2011, 09:39 AM

Posting Permissions

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