Results 1 to 5 of 5
-
21-12-2011, 13:22 #1
-= TeamSpeak User =-
- Join Date
- Oct 2011
- Posts
- 5
Problem with TSNDS Subdomains and Wildcards.
I noticed a strange behaviour regarding subdomains, weildcards and TSDNS. Following happens with a correctly configured TSDNS server.
When I set up a wildcard A record like "*.ts3.domain.tld A 1.1.1.1" all connection attemps to subdomains like sub1.ts3.domain.tld, sub2.ts3.domain.tld, sub3.ts3.domain.tld and so on will be redirected to the virtual TS 3 server running on the default port.
The second I set up the A record "ts3.domain.tld A 1.1.1.1" the clients where redirected to the designated virtual servers.
Is this a bug or does TS 3 expect the rdns the (sub)domain to the subdomain the hostname and or rdns?
-
21-12-2011, 13:39 #2
-= TeamSpeak Guru =-
- Join Date
- May 2010
- Posts
- 6,372
Hello
Also please post the tsdns_settings file.
-
21-12-2011, 14:54 #3
-= TeamSpeak User =-
- Join Date
- Oct 2011
- Posts
- 5
sub1.ts3.domain.tld=1.1.1.1:9987
sub2.ts3.domain.tld=1.1.1.1:9988
sub3.ts3.domain.tld=1.1.1.1:9989
As long as the A record for ts3.domain.tld to 1.1.1.1 is not set all subs will be redirected to 1.1.1.1:9987. The second i created the record ts3.domain.tld the tsdns worked as it should. As I stated before I do not use ts3.domain.tld for a virtual server at all.
-
22-12-2011, 09:08 #4
-= TeamSpeak Guru =-
- Join Date
- May 2010
- Posts
- 6,372
So effectively, if you use a "dns wildcard" in the DNS settings (A), at the connection the client thinks to have the good connection address.
The DNS server return him a classical answer ("for this address I have this IP").
To force the client to search a tsdns server, you just have to set a A DNS rule for ts3.domain.tld
(And the client understand "Ok there is an IP for ts3.domain.tld but I have to search the info for the sub domain sub1 - e.g.)
And now the client trys to read the tsdns settings.Last edited by florian_fr40; 29-12-2011 at 13:27.
-
29-12-2011, 11:58 #5
-= TeamSpeak User =-
- Join Date
- Oct 2011
- Posts
- 5
I do not use a wildcard on connect. I use it at the nameserver settings. The connect is to sub2.ts3.domain.tld and so on.
As long as the A Record ts3.domain.tld does not exist a connect to sub2.ts3.domain.tld will be directed to 1.1.1.1:9987.
If I add an A record to the nameserver settings that puts ts3.domain.tld to 1.1.1.1 a connect to sub2.ts3.domain.tld ends up at 1.1.1.1:9989
The idea behind this is a small webpanel for my freinds. They should either be able to use a subdomain of their choice to ts3.domain.tld or can setup their own domains. To reduce my workload I configured a wildcard at the nameserver so I do not have to add or change records from my-clan.ts3.domain.tld to my-great-clan.ts3.domain.tld.
Thread Information
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)
Similar Threads
-
Separate virtual TS-Server with subdomains
By lukelukeluke in forum [TeamSpeak 2] Server SupportReplies: 1Last Post: 11-04-2006, 11:46 -
wildcards for bans
By hybridnfo in forum [TeamSpeak 2] Server SupportReplies: 3Last Post: 01-03-2005, 23:56


Reply With Quote