- Apr 25, 2015
- 1,845
- 2
- 2,199
- 327
I think TeamSpeak Systems GmbH should discontinue support for TSDNS. There is something called "service record" or SRV.
TSDNS is literally a nightmare. It is redundant as it tries to act like DNS, which TSDNS is simply not a good DNS application. As you can see from the above code, it is very simple using a DNS SRV record to make your TeamSpeak 3 server work with a domain/subdomain.
Want to check the records using CMD?
Just to provide some history, SRV records have been a standard record within DNS since early 2000 as shown at the below link.
http://tools.ietf.org/html/rfc2782
Here is a CERT post regarding a "srv bug" which impacted ISC BIND and some additional SRV security links, this may spark some security research ideas:
http://www.cert.org/historical/advisories/CA-2000-20.cfm?
http://tools.cisco.com/security/cen...SubId=0&softwareVersion=5.1&releaseVersion=S3
https://www.rapid7.com/db/modules/auxiliary/dos/windows/smb/ms10_054_queryfs_pool_overflow
https://pentestlab.wordpress.com/tag/dns-enumeration/
https://www.rapid7.com/db/modules/auxiliary/gather/enum_dns
http://tools.kali.org/information-gathering/dnsrecon
http://dns.vanrein.org/srv/tools/
A Service record (SRV record) is a specification of data in the Domain Name System defining the location, i.e. the hostname and port number, of servers for specified services. It is defined in RFC 2782, and its type code is 33.
Code:
Service name: _ts3, Protocol: UDP, Priority: 1, Weight: 1, Port: 9994, Target: 192.168.1.4
Service name: _tsdns, Protocol: TCP, ... all the same as UDP.
TSDNS is literally a nightmare. It is redundant as it tries to act like DNS, which TSDNS is simply not a good DNS application. As you can see from the above code, it is very simple using a DNS SRV record to make your TeamSpeak 3 server work with a domain/subdomain.
Want to check the records using CMD?
Code:
nslookup q=srv _ts3._udp.r4p3.net
nslookup q=srv _tsdns._tcp.r4p3.net
Just to provide some history, SRV records have been a standard record within DNS since early 2000 as shown at the below link.
http://tools.ietf.org/html/rfc2782
Here is a CERT post regarding a "srv bug" which impacted ISC BIND and some additional SRV security links, this may spark some security research ideas:
http://www.cert.org/historical/advisories/CA-2000-20.cfm?
http://tools.cisco.com/security/cen...SubId=0&softwareVersion=5.1&releaseVersion=S3
https://www.rapid7.com/db/modules/auxiliary/dos/windows/smb/ms10_054_queryfs_pool_overflow
https://pentestlab.wordpress.com/tag/dns-enumeration/
https://www.rapid7.com/db/modules/auxiliary/gather/enum_dns
http://tools.kali.org/information-gathering/dnsrecon
http://dns.vanrein.org/srv/tools/
Last edited: