Please note that it can always take up to 24 hours before changes to DNS entries become active!
Forward domain to your TeamSpeak 3 server
You can either redirect your entire domain or just a subdomain to your TeamSpeak 3 server. This way, no one has to remember the complicated IP address consisting of numbers and can simply connect to your TeamSpeak 3 server using the domain.
How does it work?
Before we start creating entries in the DNS settings of the domain, here is some information in advance:
To forward the IP address, either create a subdomain that redirects to the IP address of the TeamSpeak 3 server, or forward the entire domain without a subdomain. This would be sufficient if the TeamSpeak 3 server uses the default port 9987. However, if the TeamSpeak 3 server is using a different port than the default port, an additional SRV entry will be added to the TeamSpeak 3 server's IP address is required to forward the domain or subdomain to the correct port.
The service name always begins with a underscore. For a TeamSpeak 3 server, the service name is always _ts3, with no exceptions.
As protocol we specify the Internet protocol used for the connection. Here UDP and TCP are available. The protocol specification also always starts with a underscore and is either _udp or _tcp. For a TeamSpeak 3 server, _udp is always used, without exception.
Forwarding the domain without subdomain
To forward your domain to a game server without creating a subdomain, first open your domain by on the dashboard, then open DNS Management from the menu on the left.
There you will see all existing DNS entries for your domain. If you have not yet created your own entries there, you can view all existing entries by clicking on the red trash can on the right side.
Then click New entry and you will be taken to the creation of a new DNS record. As Name we choose here the name of the domain, as an example teamspeak-server.de, the type is A and the value is the IP of your TeamSpeak 3 server, in this case 184.108.40.206. You can leave the TTL field untouched.
When you have entered everything, click on Save, the entry will be saved in the DNS settings and will be displayed within of 24 hours.
It can always take up to 24 hours until new DNS entries become active. Unfortunately nobody has influence on this.
Forwarding the domain with subdomain
If you want to create a subdomain, for example ts.teamspeak-server.de, you do it like in the previous example, However, for Name you do not enter the name of the domain, but the subdomain. This looks like this:
Forwarding the domain with port (SRV)
If the standard port 9987 is not used, an additional SRV entry must be created in order to not only protect the domain to the IP of the game server but also to the correct port.
First you either create a subdomain as described above, or you redirect the domain as described above directly to the TeamSpeak 3 server, both are possible.
Forwarding without subdomain
After you have forwarded your domain to the IP address of your TeamSpeak 3 server as described above, click on New Entry. and create an entry that looks like this:
The Name field contains the name of the service, which in this case is our TeamSpeak 3 server, so _ts3. It also contains the protocol type, in this case _udp as well as the domain name. The Type field indicates what type of entry it is, in this case it is a SRV entry. The field value contains the game port and the domain, in this case 0 1234 teamspeak-server.de, where 1234 is the port of the game and teamspeak-server.de is the domain to which the forwarding is done. The value 0 is no longer relevant and always remains the same. The fields TTL and Prio are also not affected.
Afterwards you can click on Save.
It is important that a dot is set in the value field at the end of the domain!
Forwarding with subdomain
With a subdomain it behaves almost exactly the same. First, you create a subdomain as described above and forward it to the IP address of your TeamSpeak 3 server. Then click on New Entry and create an entry with the following content:
The Name field contains the name of the service, which in this case is our TeamSpeak 3 server, so _ts3. It also contains the protocol type, in this case _udp as well as the domain name together with the subdomain, which is ts.teamspeak-server.de. The field Type indicates what type of entry it is, in this case it is a SRV entry. The field value contains the port and the domain with subdomain, in this case 0 1234 ts.teamspeak-server.de, where 1234 is the port of the TeamSpeak 3 server and ts.teamspeak-server.de is the domain with subdomain to which the forwarding is done. The value 0 is no longer relevant and always remains the same. The fields TTL and Prio are also not affected.