TSDNS TEAMSPEAK 3
- Thread starter Pai
- Start date
- May 20, 2016
- 264
- 107
- 136
- Jun 25, 2015
- 83
- 125
- 124
yes the last teamspeak client update need to add srv record
- Jun 25, 2015
- 83
- 125
- 124
for example
service: tsdns
protokoll: tcp
priority: 0
weight: 5
port: 41144
target: yourdomain
Code:
srv record _tsdns _tcp 0 5 41144 yourdomainservice: tsdns
protokoll: tcp
priority: 0
weight: 5
port: 41144
target: yourdomain
- Jan 1, 2016
- 459
- 286
- 122
I can show you when i'm home in a few mins if you still need help.
Google helps too if you cant wait
I added the SRV record correctly as you can see in the image:
But after that the server does not connect to any of the addresses of that domain.
And if I leave without this SRV the 3.1 client displays a message on the server that the configuration is deprecated.
- Jan 1, 2016
- 459
- 286
- 122
Replace tcp with udp and tsdns with ts3. Then replace the port with the port of you ts server
With that configuration you will only be able to connect with "mydomain.com" to your TS.
- Jan 1, 2016
- 459
- 286
- 122
Yep I'm home now.
This is what my config looks like:
Put the address you want people to use when they want to get on your ts. For example if people should join the TS over the address "joints3.mydomain.com", you simply put that in there.
Where it says Port, you enter the port of your teamspeak server.
Target is the A record that resolves to the IP of your TS server.
You have to add an extra A record with the subdomain inside Target like here:
EDIT: Wow thanks r4p3. Puush images are still not fixed... It showed them as images in the editor but oh well
I made these settings but still can not connect to the server
- Jan 1, 2016
- 459
- 286
- 122
Does domain.com in your case resolve to the teamspeak IP?
And is the port correct? Still looks like the port from Ghostrider.
You also have 2 SRVs now. Remove the top one and change the port.
Clear Explanation:
Service Name: The name of the service you want to use the SRV on. Here _ts3
Protocol: The protocol you want to use for the SRV. Here UDP.
Name: The address you want people to use to join your TS Server.
Priority & Weight: Only really necessary if you want to spread loads across servers. Not sure myself how they work
Port: The port your TS runs on
Target: A record to your TS IP.
Last edited:
- Jan 1, 2016
- 459
- 286
- 122
Here is my full DNS:
https://puu.sh/tU2u3/a9617acab9.png
Just change "Name", "Port" and "Target"
You might have to wait a few minutes for the changes to take effect.
https://puu.sh/tU2u3/a9617acab9.png
Just change "Name", "Port" and "Target"
You might have to wait a few minutes for the changes to take effect.
I've done the setup now see if it's correct:
I still own an A record - for the same SRV address, this can mess up and should I delete the A record - or leave it?
I still own an A record - for the same SRV address, this can mess up and should I delete the A record - or leave it?
- Jan 1, 2016
- 459
- 286
- 122
Okay this looks correct. You need to have an A-Record with the name "marginalx11" and the IP of your TS Server.
OK, actually now I can access the server.
However, the deprecated configuration message is still being displayed when logging on to the server.
Does this have anything to do with using the tsdns_server program that comes with the server files?
Before I used only a registry A pointing to the IP of the server, and then in the TSDNS program in my VPS I did the following:
Tsadress.mydomain.com:162.59.29.124:32600
Should I turn off the tsdns program?
However, the deprecated configuration message is still being displayed when logging on to the server.
Does this have anything to do with using the tsdns_server program that comes with the server files?
Before I used only a registry A pointing to the IP of the server, and then in the TSDNS program in my VPS I did the following:
Tsadress.mydomain.com:162.59.29.124:32600
Should I turn off the tsdns program?
- Jan 1, 2016
- 459
- 286
- 122
Yes try disabling it. I don't get the message and I don't use the program.
- Jan 1, 2016
- 459
- 286
- 122
Then for every server you have to create an SRV. For example "server1.domain.com", "server2.domain.com" etc, change the Port but put Target to the same address.
If server1 has port 25900, then put the port in the server1 SRV record to 25900.