TSDNS ".com.br"

[vLewinsky]

For some reason TeamSpeak don't connect to TSDNS with addres ended by ".com.br"
The TSDNS is configured and resolve all the other, but not resolve ".com.br" addres like ts3.armedforces.com.br

[dante696]

I can not say, that it does not work. It worked fine on my first try.

Server Chat Tab

<08:13:52>  Trying to resolve hostname ts3.armedforces.com.br
<08:13:55>  Trying to connect to server on ts3.armedforces.com.br
<08:13:56>  Connected to Server: ArmedForces™
<08:13:56>  Bem vindo ao clã ArmedForces™!

Client Log

26.06.2012 08:13:55	ClientUI	Info	Initiating connection: 177.71.178.104:32083 ts3.armedforces.com.br

[vLewinsky]

Still does not work for me and other users in Brazil, even without the translation enabled.

07/07/2012 09:08:17 ClientUI Info Connect to server: ts3.armedforces.com.br
07/07/2012 09:08:17 ClientUI Info Trying to resolve ts3.armedforces.com.br
07/07/2012 09:08:17 Info creating 0000000002237D50
07/07/2012 09:08:17 StringHelp Warning Invalid UTF-8 string passed to function, returning as-is
07/07/2012 09:08:17 StringHelp Warning Invalid UTF-8 string passed to function, returning as-is
07/07/2012 09:08:17 Warning getaddrinfo error: Este host n�o � conhecido.
07/07/2012 09:08:18 ClientUI Info Lookup finished: 177.71.178.104 9987 ts3.armedforces.com.br 0 0
07/07/2012 09:08:18 ClientUI Info Resolve successful: 177.71.178.104:9987
07/07/2012 09:08:18 ClientUI Info Checking blacklist
07/07/2012 09:08:18 Info Trying to resolve blacklist server
07/07/2012 09:08:18 Info creating2 000000000227BAA0
07/07/2012 09:08:18 ClientUI Info Blacklist check ok
07/07/2012 09:08:18 ClientUI Info Initiating connection: 177.71.178.104:9987 ts3.armedforces.com.br
07/07/2012 09:08:18 Info Blacklist server resolved
07/07/2012 09:08:18 Info Data sent to blacklist server
07/07/2012 09:08:18 ClientUI Info Connect status: Connecting
07/07/2012 09:08:18 Info Data received from blacklist server: 1,
07/07/2012 09:08:20 StringHelp Warning Invalid UTF-8 string passed to function, returning as-is
07/07/2012 09:08:20 StringHelp Warning Invalid UTF-8 string passed to function, returning as-is
07/07/2012 09:08:20 Warning getaddrinfo error: Este host n�o � conhecido.
07/07/2012 09:08:22 Info deleting 000000000227BAA0
07/07/2012 09:08:22 Info deleting 0000000002237D50
07/07/2012 09:08:24 ClientUI Info Connect status: Disconnected
07/07/2012 09:08:24 ClientUI Info Failed to connect to server, want autoreconnect = 0

[PotaBlava]

Still does not work for me and other users in Brazil, even without the translation enabled.

My client says there isn't TSDSN working or found...

07/07/2012 15:11:11	ClientUI	Info	Connect to server: ts3.armedforces.com.br	
07/07/2012 15:11:11	ClientUI	Info	Trying to resolve ts3.armedforces.com.br	
07/07/2012 15:11:11		Info	creating 0897AD28	
07/07/2012 15:11:11		Warning	 getaddrinfo error: Host desconocido. 	
07/07/2012 15:11:11		Warning	 getaddrinfo error: Host desconocido. 	
07/07/2012 15:11:11		Info	No TSDNS found at "armedforces.com.br"	
07/07/2012 15:11:12	ClientUI	Info	Lookup finished: 177.71.178.104 9987 ts3.armedforces.com.br 0 0	
07/07/2012 15:11:12	ClientUI	Info	Resolve successful: 177.71.178.104:9987	
07/07/2012 15:11:12	ClientUI	Info	Checking blacklist	
07/07/2012 15:11:12		Info	Trying to resolve blacklist server	
07/07/2012 15:11:12		Info	creating2 0897AC78	
07/07/2012 15:11:12	ClientUI	Info	Blacklist check ok	
07/07/2012 15:11:12	ClientUI	Info	Initiating connection: 177.71.178.104:9987 ts3.armedforces.com.br

[SilentStorm]

I remember something about TSDNS only checking the last 3 parts of a Domain, so in this case it would be checking for the TSDNS Server on armedforces.com.br, on com.br and on .br (stupid in my opinion but whatever, there will definitely never ever be a TS DNS Server running on .com.br or .br or any other TLD). iirc it won't check ts3.armedforces.com.br as its too far down the line so that is probably why "it isn't working".

[vLewinsky]

This is not true, I have addresses as:
ragnasbn.tsvlew.net
deathlessbrotherhood.nossots.net
thatslvs.tsvlew.net
sealteam6.meuts.net
clantfm.brasilts.net
And all work.

[dante696]

It seems , that armedforces.com.br is not configured correctly, this is the only time i heared about such a problem.

I send that whole thread to the developer, maybe he has an idea, but yeah in my opinion .com.br is a weired address.

[Peter]

Hi,

TSDNS used to only check the last 3 parts of the domain for a running TSDNS server, so if your domain is:

"ts3.armedforces.com.br"
it will check for a running TSDNS server on "br" (wont work), on "com.br" (wont work) and on "armedforces.com.br".

I checked for you, and "armedforces.com.br" does not resolve to an IP, so there is no way it will find a TSDNS server on it. This is why it doesn't work.

With the upcoming 3.0.8 client we have increased the "search range" from 3 domain parts to 4 domain parts, so the newer clients can actually connect to your server since they find the TSDNS on "ts3.armedforces.com.br".

[SilentStorm]

While you are at changing stuff in TSDNS why not just make it so it won't ever check on TLDs (which include .com.* .org.* etc.)? Would make much more sense, since there is never ever going to run a TSDNS on any of them anyway, and querying them is just causing unsolicited Traffic on those Servers!
Either just check on the last x which are not TLD (from right) or just check the first x Levels from the left (again which are not TLD).

[vLewinsky]

The strange thing is that the TS3 identifies ts3.armedforces.com.br correct IP which is 177.71.187.183 and not armedforces.com.br which is 67.215.65.132, but not looking for TSDNS

But okay, in this new version 3.0.8 the problem was resolved

[SilentStorm]

The strange thing is that the TS3 identifies ts3.armedforces.com.br correct IP which is 177.71.187.183 and not armedforces.com.br which is 67.215.65.132, but not looking for TSDNS

But okay, in this new version 3.0.8 the problem was resolved

Nothing strange about that...
Up to 3.0.8 TS3 Client only checked the last 3 parts of the FQDN for TSDNS Servers... in your case neither of them was running a TSDNS which is why the Client just connected to the domain directly using DNS to resolve it into an IP Address. DNS System is independent from TS3 and gave the correct IP where there is a TS3 Server running, so the connection worked.