Either that or just utilize any portable DNS query library. Google suggests this one: http://sourceforge.net/projects/adns/Originally Posted by bofh999
We are migrating towards a new forum system located at community.teamspeak.com, as such this forum will become read-only on January 29, 2020
-= TeamSpeak Addict =-
Either that or just utilize any portable DNS query library. Google suggests this one: http://sourceforge.net/projects/adns/
Our next client release 3.0.8 will support SRV and TSDNS SRV records.
This has been tested and tweaked so far.
The clients priority for a connection will be:
1. TSDNS SRV > 2. SRV > 3. TSDNS > 4. DNS > 5. IP
-Logging for clients will show some extended informations about the connection.
-Android and Iphone won't support this feature, when it is released for the normal client 3.0.8. It is planned to include this later.
There is no release date yet, for a beta or stable version.
Last edited by dante696; June 27th, 2012 at 10:51 AM.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
-= TeamSpeak User =-
That's awesome thank you!
-= TeamSpeak User =-
Awesome!
Does this fix the bug where TSDNS lookups are done when an IP address is given? And when a port is given I assume it bypasses any TSDNS or SRV lookups?
-= TeamSpeak Addict =-
Thank you very much!
-= TeamSpeak User =-
-= TeamSpeak Fanatic =-
Curious about what TSDNS SRV is going to be? SRV Record that specifies the Server to query for TSDNS which will then answer with the IP:Port Info as it used to do up till now?
TSDNS SRV, is your domain, that guides to a TSDNS server, that is running on the same machine or another server/computer.
This TSDN server does the old job then.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
-= TeamSpeak Team =-
No such bug is known to me. Looking at the code it should not happen, IPs are detected and not resolved.
I am not sure I understand what exactly you mean here. Obviously when you do IPAnd when a port is given I assume it bypasses any TSDNS or SRV lookups?ort neither TSDNS or SRV lookups take place. When you do domain
-= TeamSpeak User =-
cname: example.net example.com
srv: _ts3._udp.ts 3600 IN SRV 0 100 9187 example.com
not support ?
Thread was merged
-= TeamSpeak Fanatic =-
SRV Records are supported since TeamSpeak Client Version 3.0.8 See Changelog.
The Reason yours is not working is because the DNS Entry is invalid... (See Wikipedia).
It needs to be _ts3._udp.example.com 3600 IN SRV 0 100 9187 example.com. you forgot the Domain Name which I wrote in bold for you.
-= TeamSpeak User =-
cname: example.net example.com -> srv record
support ?
-= TeamSpeak User =-
AFAICT, SRV records are not fully working as expected in TS.
My records:
The expected behaviour is to try to connect to machine1, and then try to connect to machine2 if it fails. Currently, it just fails. Too bad.Code:_ts3._udp.ts 86400 IN SRV 0 5 9987 machine1 _ts3._udp.ts 86400 IN SRV 10 5 9987 machine2
-= TeamSpeak Fanatic =-
As mentioned before on the forums, the SRV records only considers the highest priority. Not usable for a fallback setup.
-= TeamSpeak User =-
And that is exactly the reason I post here for someone to reopen this request as SRV records are just bloody useful for a fallback setup and TeamSpeak should really support that. If you really need to go this route, just add something in TSDNS to do the same but fallback servers are something needed to have a reliable service.
When I said “as expected” it was “as expected by any sysadmin using SRV records”. Please, make TeamSpeak more standard-compliant…
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
Reply With Quote
