I am wondering if DNS entries will be supported in the near future?
Tried to add a CNAME record to my own domain so I could connect with that rather than the teamspeak.com domain.
It seems to be resolving the DNS entry when checking it with nslookup, but it still doesn’t let me connect to the community with it.
3 Likes
+1
I have a big problem that my domain that I have rented from Livingbots can’t connect to the community IP because I don’t have a number IP. I have constantly tried with ALIAS etc. to connect the community ip, but it does not work.
u can do this
RECORD ADD
cname | @ , * or ts | user1.domain.tdl
no that doenst work. It would be better to just give the normal ip in numbers.
It’s not working because TeamSpeak is using an AWS load balancer, which causes the IP address to change every time you connect.
A TeamSpeak Team member needs to help find a proper solution here. I’ve tested everything CNAME, SRV, and other methods. but none of them work reliably. Right now, there’s only about a 3.33% chance of hitting the correct IP due to the AWS load balancer constantly changing it.
Test Domain:
- SRV from TeamSpeak: plenetotaku.fra1.teamspeak.com
- SRV Test: ts6-srv.aow.red
- CNAME Test: ts6-cname.aow.red
Doesn’t it work with using the tmspk.gg links? (Right click the server → Create Invite)
2 Likes
ok i try
That won’t work for our use case, because we want users to be able to connect using a regular domain directly via the TeamSpeak client. While it might work as an invite link, it won’t function reliably when entering the domain manually in the client.
Okay, I’ve found a solution! it’s a bit of a hack, but it actually works. Basically, we just ignore the load balancer. Instead, we perform a DNS lookup on the TeamSpeak SRV domain (in my case: plenetotaku.fra1.teamspeak.com), pick one of the resolved IPs that seems stable, and use that. Next, we find the port our TeamSpeak 6 server uses for me, it’s 30239 and then we create a custom SRV record pointing to that specific IP and port. With that, connections work consistently.
However, this isn’t a proper or long-term solution. It’s not well tested and could break at any time. It would really be better if the TeamSpeak team provided an official and stable way to handle this.
SRV target must be a hostname.
you can use this IP for the A and SRV Record
fra1 Server Only:
(209.38.243.225)
I’ll check with the team.
3 Likes
We’ve checked now and you need to set up a CNAME for the and then you need to add a SRV record which then links to our subdomain.
SRV: _ts3._udp.testcname, Port, Target = SUBDOMAIN.REGION.teamspeak.com
and then a CNAME with the SUBDOMAIN.REGION.teamspeak.com
4 Likes
but how to get the port without checking the clientlog
You can do a dig +short _ts3._udp.SUBDOMAIN.REGION.teamspeak.com SRV on a Linux machine or use 3rd party software to get the port.
3 Likes
Ye I know but wouldn’t it be easier for everyone, especially for regular users, if that information was just added to the website?
thats way too complicated for a normal user for me. Pls give me reasons why theres no normal ip
1 Like
The servers don’t have a static IP as they can get moved to different nodes on the go if resources are available on a different node.
I am not sure how this will change in the future as we currently also can not display the IP of the user in the client database which leads to the problem that they do not have a country flag in their user card.
For now this is the only solution I can offer you to solve the problem.
3 Likes
