SRV resolution doesn't work

TeamSpeak 3 Server
1

Hi there,

since yesterday, I have been encountering an issue with resolving my server’s SRV record.

I made some entries for a subdomain SRV resolution years ago and they worked for literally years. Still, since yesterday, 2025-11-24, the teamspeak client prompt’s an error instantly, as if he didn’t even sent the DNS request, when I try to connect.

<15:40:43> Trying to resolve hostname ts.<domain>
<15:40:43> Failed to resolve hostname 'ts.<domain>'

While, when I connect via domain:port, it works as intended.

<15:44:37> Trying to resolve hostname <domain>
<15:44:39> Trying to connect to server on <domain>:1337
<15:44:39> Connected to Server: "[...]"

However, the SRV resolution works perfectly fine, as you can see here.

$ dig +search +short srv _ts3._udp.ts.<domain> @1.1.1.1
0 10 1337 ts.<domain>.
$ dig +search +short srv _ts3._udp.ts.<domain> @8.8.8.8
0 10 1337 ts.<domain>.
$ dig +search +short srv _ts3._udp.ts.<domain> @217.237.150.51 # Deutsche Telekom DNS
0 10 1337 ts.<domain>.

Also, not only I have this issue, but my friends who want to connect to my server as well.

I checked the teamspeak 6 beta client as well and I can confirm the same issue there.

Is anyone else experiencing this?

EDIT:
I can also confirm this to not be working when I connect to different NordVPN Nodes.

2

Since there was no update for the TS3 or TS6 client yesterday (or recently at all) I highly doubt that this is a TeamSpeak problem.

I did however notice one thing in your config.
Your SRV record points to the A/AAAA record ts.<domain> while when you try to connect with the specified port you connect to the IP behind the A/AAAA record <domain>.
So you should check that either and A or AAAA record for ts.<domain> exists, or change the SRV record to point to the <domain> directly and not the subdomain.

3 Likes
3

Thanks for your reply, you pinpointed me into the right direction.
I checked the client log file and saw, that the DNS answer sections is empty.

So I checked, if I can resolve the subdomain and that didn’t work, even though there is a wildcard rule configured in my DNS zone by my VPS provider.

I guess I have to take it up with them.

Thanks!

1 Like