TSDNS using ts3.domain.co.uk domain name not working

[RickH]

Hello,

I was hoping SRV record support comes in soon as I have some trouble connecting using a DNS name using TSDNS.

We have a domain ending with .co.uk and thus TS3 will not look further than domain.co.uk as seen here:

26-9-2011 16:41:45	ClientUI	Info	Connecting to next server...	
26-9-2011 16:41:47		Info	No TSDNS found at "co.uk"	
26-9-2011 16:41:52		Info	No TSDNS found at "domain.co.uk"	
26-9-2011 16:52:09		Info	No TSDNS found at "domain.co.uk"	
26-9-2011 16:52:10		Info	No TSDNS found at "co.uk"

For obvious reasons I cannot change the domain.co.uk A record as that will break the website.

Also, why is it looking in other places than ts3.domain.co.uk as that is the requested address?

Any ideas?

Thanks,
Rick

[TexasTeamspeak]

This is by design actually, TSDNS currently looks for a response within 3 levels. These levels are denoted by the periods.

When using the domain "ts3.domain.co.uk" the TSDNS clients are looking for a response from the following places:

1 .uk (skipped as it is a top level domain)
2 .co.uk
3 domain.co.uk

For this to work for you as is, you would need the TSDNS server running on "domain.co.uk" as "ts3.domain.co.uk" is on the 4th level.

We noticed this with some users at ts3dns.com and contacted the Teamspeak developers about it. They said they would consider adding a 4th level to the TSDNS client lookups.

[RickH]

So basically this means no UK domains can be used with TSDNS as it will only look at the top 3 levels of a domain, and not the requested Address which is also pointing to that teamspeak box with TSDNS running. I'm not a hosting company that uses *.ts3.company.com to distribute TS to clients, but have a small league for us running and another clan division and its own TS virtual server and domain which points to that TS host as well.

The other domains ending with .com I don't have any issues with and takes over nicely, but for now I'll create another sub domain on our .com domain so it will look at the correct address, but this needs to be looked into to stop people exclusively using a .co.uk domain (and maybe other) having this issue.

Any ideas where on the roadmap DNS SRV record support is planned? As that will allow me to do what I want, even with .co.uk domains.