Tsdns Issues not resolving correctly. Is there a Guidance page for tsdns?

I am looking for specific manual on tsdns for teamspeak3 having issues with mine not working.

root@vmi839185:/home# su - ts3server
ts3server@vmi839185:~$ ls
lgsm  linuxgsm.sh  log  serverfiles  ts3server
ts3server@vmi839185:~$ cd serverfiles/
ts3server@vmi839185:~/serverfiles$ ls
CHANGELOG        libts3db_mariadb.so     LICENSE          privilege_key.txt       serverquerydocs   ts3server.ini                   ts3server.sqlitedb        tsdns
doc              libts3db_postgresql.so  licensekey2.dat  query_ip_allowlist.txt  sql               ts3server_license_accepted      ts3server.sqlitedb-shm
files            libts3db_sqlite3.so     licensekey.dat   query_ip_denylist.txt   ssh_host_rsa_key  ts3server_minimal_runscript.sh  ts3server.sqlitedb-wal
libmariadb.so.2  libts3_ssh.so           logs             redist                  ts3server         ts3server.pid                   ts3server_startscript.sh
ts3server@vmi839185:~/serverfiles$ cd tsdns
ts3server@vmi839185:~/serverfiles/tsdns$ ls
README  tsdnsserver  tsdns_settings.ini  tsdns_settings.ini.sample  USAGE
ts3server@vmi839185:~/serverfiles/tsdns$ cat tsdns
tsdnsserver                tsdns_settings.ini         tsdns_settings.ini.sample
ts3server@vmi839185:~/serverfiles/tsdns$ cat tsdns
tsdnsserver                tsdns_settings.ini         tsdns_settings.ini.sample
ts3server@vmi839185:~/serverfiles/tsdns$ cat tsdns_settings.ini

This is what tsdns_settings.ini looks like.

#   ***This is the configuration file for the TSDNS server***
#
# The format is always "ident=value", where:
# ident is a host-name, which should at least for the right hand side be a
# valid (DNS) host-name.
# On a box known via DNS as "myrootserver.com" sensible idents might be
# "myrootserver.com" or "any.combination.of.weird.words.myrootserver.com".
# Also allowed is "*" as first character of an ident, which matches any
# queries that end with what follows the star. For example "*" matches
# always, providing a default answer. "*.myserver.eu" matches every query
# that ends with ".myserver.eu", like "foo.myserver.eu".
#
# The value side is always an IP address followed by a ':' and then either a
# port or the special string "$PORT".
#
# Also allowed as value is the special string "NORESPONSE", which makes the
# TSDNS server answer not answer this query. This can be useful in scenarios
# where multiple TSDNS servers exist and you wish to let "the other" TSDNS
# server handle this request. Or you wish regular domain resolving to take
# place for some cases.
#
# Example: The TSDNS server runs on on a box reachable as both as
# "teamspeak.com" and as "teamspeak-systems.de"
# So we might configure:
# public.teamspeak.com=12.13.14.15:10000
# test.teamspeak.com=12.13.14.15:12000
# private.teamspeak.com=12.13.14.15:14000
# voice.teamspeak.com=NORESPONSE
# *.teamspeak-systems.de=1.2.3.4:15000
# *=12.13.14.15:$PORT
ts3.domain1.com=ip1:9987
ts3.domain2.com=ip2:9988

# This way, now clients can connect to "test.teamspeak.com" to reach the test
# server, but if they still have the old "teamspeak.com:12000" in their
# bookmarks, it will also work thanks to the "*=12.13.14.15:$PORT" line, which
# acts as a backwards compatibility mechanism in this case, for everybody not
# using the new TSDNS names to connect.
#
# Starting server version 3.0.13 ipv6 values can also be specified. These are
# formated along the line of rfc2732 using [ and ] to encapsulate the address.
# For example the localhost port 9987 in ipv6 format would be [::1]:9987. Also
# starting 3.0.13, it is possible to specify a list of ip's on a line. An
# example would be to specify an ipv4 and ipv6 address, but multiple ipv4 and
# ipv6 addresses seperated by a space are allowed. Older clients that do not
# support ipv6 and multi value replies, will only recieve the first ipv4
# address on the line. For example:
# public2.teamspeak.com=[2001:0db8::1]:9987 1.2.3.4:9987 5.6.7.8:9987
# will only send 1.2.3.4:9987 to the older clients.
#
# Lines starting with "#" are ignored by the tsdns server, so to make any
# actual configuration you must remove the "#" infront.
#
# Note that if you want to use any non ascii characters you may do so,
# but you should make sure to store this configuration file as UTF8 encoded
# document.
#
ts3server@vmi839185:~/serverfiles/tsdns$

I restarted the server what am I missing here?

Don’t forget to start the tsdnsserver binary.
And it is important that IP exists on the machine where the TSDNS server runs on.

The exmaple domain and IP you gave looks ok, but that’s all i can say for that point.


We recommend to use own Domain to setup a DNS resolve.

3 Likes

Yeah that was my issue… My bad… I am so sorry… I am using Linuxgsm and didn’t think about that… So I ran it in screen everything working fine now.

1 Like