Every time I try to connect to my server, I get an error message, that seems to be a problem since 2013.
Could anyone help me out with this?
It’s a TSDNS error, which says that couldn’t find any domain with that (name).
That’s not an Error at all. Else log would print error.
Either no TSDNS is not setup.
Or it was setup but whatever was set in there is no longer valid.
You should not longer use it anyways and use A / AAAA DNS / SRV Records instead. But client will try to resolve for legacy support.
1 Like
So what’s the best thing to do in this case?
Cause it’s not even my server, it’s from my IT corp.
Let me know, please and thank you!
Contact the owner of the server to fix or remove his TSDNS entries.
2 Likes
I’m posting this because I don’t know what to do anymore… I’m having issues setting up the SRV records to redirect to the server… According to the logs Teamspeak 3 sees the IP from SRV and then goes to check TSDNS (I have a TSDNS set it up for the server, but there are no records mentioning the DNS domain I’m trying to connect) and then it returns to something like "The TSDNS server “domain.com” doesn’t know “domain.com”, like what?
So, according to what I saw from other posts both of them can co-exist and reason it’s trying to check TSDNS is because SRV record failed.
I tried to find the solution and I saw here in the forums other people had the same issue, but the message is incomplete, it seems they were talking with someone that got the account suspended or deleted so the topics are very vague, really wish someone that could help me because I’m certain someone in the future will look to this same post and find the solution…
I set in the domain a A type and SRV type, should I do something else?
I see in my logs this also: "SRV DNS resolve unsucceful for “_ts3._udp.domain.com”
“No SRV TSDNS found”
then…
“DNS resolve successful, “domain”=IP”
“SRV TSDNS found at “domains”, but could not find TSDNS server there”
That actually doesn’t help me, since for what I can understand it’s connecting in your server using IPv6 which it’s not my case since I’m trying to use Ipv4 with TSDNS setup… I wonder if I need to port forward TCP for port 9987 as well to make this work, although it should be using UDP not TCP… I port forward the TCP port for TSDNS and it works every time…
This is my log, but like I said for TSDNS it just works SRV record it doesn’t… I wanted to use SRV records since it’s priority number 1, but it seems in my case I cannot…
It is normal that TSDNS uses TCP port 41144.
TSDNS is not the voice server itself. It is a small name-resolution service used by TeamSpeak clients.
When a user connects with a hostname (for example ts.example.com), the client first contacts TSDNS, which returns the real IP address and port of the voice server. Without it, users would have to manually enter IP:9987.
So seeing port 41144/TCP listening on a TeamSpeak server is expected behaviour and not a security issue or unknown service.
Default TeamSpeak ports:
| Service | Port | Proto | Role |
|---|---|---|---|
| Voice | 9987 | UDP | Audio (actual voice server) |
| Query | 10011 | TCP | Admin / ServerQuery interface |
| File transfer | 30033 | TCP | Upload / download of icons and files |
| TSDNS | 41144 | TCP | TeamSpeak name resolution service |
You only need to open 41144/TCP if you want clients to connect using a hostname without relying on DNS SRV records. Otherwise, users can still connect directly using IP:9987.
1 Like