[Tauri App] Failed to resolve turnserver

[Wolf-Seisenbacher]

Describe the bug

This appears to be an issue in the Tauri app specifically, as the web client of 1.20.0 fetches my TURN credentials correctly. Relevant log is:

[214240:214248:0804/102951.871215:ERROR:services/network/p2p/socket_manager.cc:137] Failed to resolve address for [REDACTED]., errorcode: -105

the . after my URI exists, redacted my TURN server address just in case. (So, turn.mywebpage.com., errorcode ...)

I am wondering if there is a . in the code resulting in failing to resolve the TURN URI? I tested on the web client and it communicates with my TURN appropriately. If there is a way to get more info via the Tauri app I don't know how to, and would like to if possible to help pin this down

Reproduction

Open Tauri app /w Console open
Join voice call

Expected behavior

TURN to be resolved properly.

Platform and versions

Gentoo Linux
Sable v1.20.1-nightly.260804125813-dev (90900c6)

Additional context

Tested the TURN server and it is currently functioning as expected, and can be reached by older Sable clients, and other services such as Nextcloud Talk.

[eleboucher]

the . is fine it's chromium behavior

you can test with
getent ahosts turn.example.com
getent ahosts turn.example.com.
you will see it works the same

[Wolf-Seisenbacher]

While the . may be fine, it still is confusing that it's reporting it's failing to resolve the address for my turnserver, despite the turnserver working fine, being reachable, and accessible in other clients. I am however just a tester of 1 and my turnserver is on my local network in my server stack. I am unsure on how to get more information through the Tauri app like I can via a browser console about the handshakes during connection to a voice call.