Fast connect to demo server

[napok]

When connecting to your demo server, it connects almost instantly.
With the amount of spam going on you would expect a slower connect, but it connects faster than any other (empty) server.

What is your secret?

[dante696]

The ping is related to this.

And for client 3.0.8 we do not use the DNS, we use SRV instead, this makes it much faster too.

I guess this is the secret. I'm not the hoster of that server

[napok]

Interesting...

I am using version 3.0.7 and as far as I know that is the latest version available.
Hopefully all servers will connect that fast in the nearby future.

[Peter]

Hi,

when you connect to a server via DNS (hostname) there will be a short delay (~4s on first connect, ~0.5s on following connects), while the TS3 clients wait for a TSDNS server to answer. The solution to this is to add a TSDNS server that actually answers . TSDNS connect-speed > DNS connect speed. Alternatively you could also just use IP:Port to connect, which is a tiny (depending on your ping) bit faster than even TSDNS connect.

With the upcoming 3.0.8 client you can also use a ts3 SRV record for fast resolving, since ts3 SRV records take precedence over TSDNS and DNS resolve methods.

[napok]

In that case I am unable to understand why the TeamSpeak client does not cache the DNS response.

You would assume that if you have connected to a server before, using a domain with a time-to-live value of 86400, that its remaining connects are lightning fast until the 24 hours have passed.

[dante696]

The client does cache the dns repsonse as long the client was not closed. This won't be saved in any file and is not planned.

[napok]

If that is so, why are reconnects just as slow?
In the meantime I have tested the SRV feature in client 3.0.8 and it is blazing fast.

[dante696]

I can't say that it is slow, it needs the same time for me, when i connect per bookmark again.
but it needs ~18 seconds for a timeout, before a reconnect will be started.

[napok]

It seems like it still searches for a TSDNS server, and then it sees that it has a DNS record cached (client 3.0.7).
Correct me if I am wrong.

[Peter]

The priority in resolving is:

#1 _ts3 SRV record
#2 _tsdns SRV record
#3 tsdns server
#4 regular DNS resolve

So, even if the DNS resolve is cached it will still have to wait a short while (0.5s) to see if a tsdns server answers, since that answer has a higher priority than the regular DNS resolve.

[napok]

Thanks for confirming this.
Client 3.0.7 does not have SRV support, hence I did not include the two SRV records in my last post.