SRV Record is not working correctly

TeamSpeak Server
1

Hello, my dears,

I have a tiny problem that I might need your help with. A long time ago I made an SRV record in my DNS settings:

SRV _ts3._udp.mydomain.de 0 5 9987 ts 86400

For this I found the following entry in the client protocol:

08/04/2021 14:44:09 ClientUI Info Connect to server: ts.mydomain.de
08/04/2021 2:44:09 PM ClientUI Info Trying to resolve ts.mydomain.de
04.08.2021 14:44:09 TSDNS Info A / AAAA DNS resolve successful, "ts.mydomain.de" = (h: 2a01: 4f8: xxxx: xxxx :: 1 p: 0), (h: xxx.xxx. xxx.xx p: 0)
04.08.2021 14:44:09 TSDNS Info A / AAAA DNS resolve for possible TSDNS successful, "ts.mydomain.de" = (h: 2a01: 4f8: xxxx: xxxx :: 1 p: 0), (h: xxx .xxx.xxx.xx p: 0)
04.08.2021 14:44:09 TSDNS Info A / AAAA DNS resolve for possible TSDNS successful, "mydomain.de" = (h: 2a01: 4f8: xxxx: xxxx :: 1 p: 0), (h: xxx.xxx .xxx.xx p: 0)
04.08.2021 14:44:09 TSDNS Info SRV DNS resolve unsuccessful, "_tsdns._tcp.mydomain.de" DNS server returned answer with no data
04.08.2021 14:44:09 TSDNS Info SRV DNS resolve unsuccessful, "_ts3._udp.ts.mydomain.de" Domain name not found
04.08.2021 14:44:11 TSDNS Info TSDNS queried unsuccessfully 2a01: 4f8: xxxx: xxxx :: 1: 41144
04.08.2021 14:44:11 TSDNS Info TSDNS queried unsuccessfully 2a01: 4f8: xxxx: xxxx :: 1: 41144
04.08.2021 14:44:13 TSDNS Info TSDNS queried unsuccessfully xxx.xxx.xxx.xx: 41144
08/04/2021 14:44:13 TSDNS Info No TSDNS found
04.08.2021 14:44:13 TSDNS Info TSDNS queried unsuccessfully xxx.xxx.xxx.xx: 41144
08/04/2021 14:44:13 TSDNS Info No TSDNS found

This morning I changed the SRV entry to:

SRV _ts3._udp.mydomain.de 0 5 9987 ts.mydomain.de. 86400

Unfortunately nothing has changed in the client protocol, the same errors are still there. Can you tell me or write where my mistake is? Oh, server is operated by Hetzner when it is important.

Forget: The A and AAAA records are set correctly and refer to the IP of the server.

Thanks

3

Ahhh, now I understand. Very good explanation from you :slight_smile:

if I only get the _ts3._udp.ts.mydomain.de. then the “route” to ts.mydomain.de is correct. The way I have it now, of course, it explains why the client connects faster to the server under mydomain.de than with ts.mydomain.de. Right?

Thank you for the very detailed explanation!

I just looked again: At home I can actually connect to our server at “the speed of light”. Goil!

But if I enter ts.mydomain.de via Google dig, it says Record not found.

I’m sure that the Google name servers are faster than Telekom’s :slight_smile:

1 Like
5

Good Morning,

it all worked like you said I thank you for the help and especially for the detailed explanation :slight_smile:

1 Like