DOES TEASPEAK SUPPORT DNS SRV RECORDS?

[hellmind]

Can it work with these registries? _ts3._udp.host.com. 86400 IN SRV 0 5 9987 voice.host.com. ?

[WolverinDEV]

Hey, sorry for the late reply. Yes it does.

The TeaSpeak srv prefix is _ts. Example: _ts._udp.teaspeak.de. 86400 IN SRV 0 5 9987 ts.teaspeak.de

[hellmind]

so the only way to make it work for both clients its to duplicate the registries? is there any reason to not use the same _ts3 string?

On Sat, May 8, 2021 at 6:58 AM WolverinDEV @.***> wrote:

Hey, sorry for the late reply. Yes it does.

The TeaSpeak srv prefix is _ts. Example: _ts._udp.teaspeak.de. 86400 IN SRV 0 5 9987 ts.teaspeak.de

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/TeaSpeak/TeaClient/issues/61#issuecomment-835258735, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABIZ5W45P5VV2PNDLMJGZD3TMUDM5ANCNFSM44A6H7DA .

[WolverinDEV]

No. The TeaSpeak client actually parses _ts3 records as well since we're supporting TS3 servers with our client as well.

[hellmind]

Then how is the client connecting procedure? first check _ts then _ts3? It is documented somewhere? How can I debug my client to see that?

[WolverinDEV]

It's not really documented but here is the code: https://github.com/TeaSpeak/TeaWeb/blob/master/web/app/dns/resolver.ts#L331 It first checks for _ts and then for _ts3.

[hellmind]

Nice, How can I debug the connection procedure? teaclient -d doesnt shows that.

[WolverinDEV]

Well you can run the TeaSpeak client with the -t parameter. This allows you to get access to the developer console.

To actually activate trace logging set log.level to 0 within the TeaClient registry (Tools -> Registry)

[hellmind]

And there in the dev con I can see that info. I just get:

/usr/lib/teaclient/resources/app.asar/modules/renderer/Logger.js:42 [Client ] Failed to resolve hostname: "no results"