Another case where this would be useful: A vendor who supplies multiple TS servers from a single physical server, and his customers want to use DNS names of their own to name their server.
To facilitate this, how about adding an SDK hook in the client at the server name parsing step? If the hook is present, the plugin takes the text contents of the edit field and does all the DNS magic, returning an IP and port number to use. If not, you do your traditional parsing.
I don't know how your SDK will work, or whether you've given thought to plugins, but one way to hook this would be to add an INI parameter for ServerNameParser that takes a DLL (or SO) name and entrypoint as a parameter. The API would take two arguments, a C null-terminated string (input) and a pointer to a standard sockaddr structure to return the IP and port number in. Or two pointers to get the IP and port separately as 32 bit integers. I think Windows API's return a boolean indicating success.
I could then add code to do the SRV stuff and you could add that at your leisure to your main code base.
In practice, the TSS vendor creates a DNS record for each server that looks like this:
_teamspeak._udp.customer.vendor.com SRV 0 0 1234 ts4.vendor.com
The customer then puts a CNAME in his own DNS that looks like this:
_teamspeak._udp.ts.customer.com CNAME _teamspeak._udp.customer.vendor.com
The end user (who knows nothing of SRV records or DNS) puts "ts.customer.com" in his TS client. The client looks up a SRV record for _teamspeak._udp.ts.customer.com, follows the alias to _teamspeak._udp.customer.vendor.com, and finds a SRV record that says that the server is actually at ts4.vendor.com:1234.
BTW, here's MS' page explaining SRV:
http://support.microsoft.com/default...;EN-US;q232025
English
German
DNS SRV support to enable automagic failover
Linear Mode
