Yes, you can configure a custom hostname for your TeamSpeak server. Access the TeamSpeak control panel at https://tspanel.aspnix.com/ and click the Server Hostname option to set it up. This gives you a clean address such as myclan.ts.aspnix.com that users enter directly in the client address field. The panel handles the underlying configuration so no port needs to be manually specified in supported clients.

Custom hostnames matter because raw IP addresses and ports are difficult to remember and communicate. A branded hostname improves user experience for gaming clans, communities, or business teams by simplifying connections and presenting a more professional appearance. It leverages DNS SRV records to direct clients to the correct port and target server automatically.

#Prerequisites

You must have an active TeamSpeak server account to access the control panel. Gather your login credentials beforehand. All connecting users should run TeamSpeak client version 3.0.8 or newer, since this is the minimum version with SRV record support. Confirm your server is running and accessible via its default IP and port before changing hostname settings. No additional software is required beyond a modern web browser to reach the control panel.

#Step-by-Step Setup Instructions

Setting the hostname takes only a minute. Log into the panel, navigate to the correct server, and enter the name you want. The system validates the input against the allowed character set and activates the corresponding DNS records. After saving, test the new hostname from a client that meets the version requirement. Changes typically become active within minutes, but DNS caching on some networks can introduce a short delay.

  • - Navigate to https://tspanel.aspnix.com/ and log in with your account credentials - Locate and select the TeamSpeak server you want to configure - Click the "Server Hostname" option in the management interface - Enter your chosen prefix in the hostname field following the rules below - Save the configuration and wait for the DNS update to propagate - Test by connecting to the new hostname from the TeamSpeak client

#Supported Hostname Formats and Character Rules

Hostnames must adhere to strict rules so that DNS resolution works reliably. Only alphanumeric characters, dots, dashes, and underscores are permitted. The final hostname will be something like yourchoice.ts.aspnix.com where the part before .ts.aspnix.com is what you control. Using any other characters will cause the control panel to reject the submission.

  • - myclan.ts.aspnix.com - my-clan.ts.aspnix.com - my_clan.ts.aspnix.com - my.clan.ts.aspnix.com

These examples demonstrate the flexibility within the rules. You can combine dots, dashes, and underscores to create readable names, but avoid starting or ending with a dot or dash. Keep the total length reasonable; excessively long hostnames can become unwieldy for users even though they remain technically valid.

#How Custom Hostnames Work With SRV Records

When you save a custom hostname the control panel automatically provisions the required DNS SRV record. The TeamSpeak client queries this record when given only the hostname, learns the target server and port, then connects without any extra information from the user. This is why you can simply type the hostname into the address field and the client does the rest. The mechanism removes a common source of support requests around incorrect ports or connection failures.

#Client Version Compatibility

This feature only works with TeamSpeak client v3.0.8 and higher. These clients understand and follow SRV DNS records, allowing seamless use of the custom hostname. TeamSpeak clients below v3.0.8 do not support SRV DNS records and as a result cannot utilize the custom hostname. Users stuck on older releases must instead enter the full connection string including the port number, typically in the format hostname.ts.aspnix.com:9987.

Upgrading the client is strongly recommended. Newer versions not only enable custom hostnames but also include security updates, performance improvements, and additional features. Instruct all regular users to update before you announce the new hostname to avoid confusion.

#Troubleshooting Common Issues

  • - Hostname rejected by panel: Double-check that only alphanumeric characters, dots, dashes, and underscores are used - Connection refused with new hostname: Confirm the client is version 3.0.8 or newer and that the hostname was saved successfully - Old client behavior: Instruct users to append the port manually or upgrade their TeamSpeak installation - DNS not resolving: Verify the record using a command-line query and allow time for propagation across caching resolvers
bash 
nslookup -q=SRV _ts3._tcp.myclan.ts.aspnix.com

After configuring your custom hostname, test connectivity from both supported and unsupported clients to confirm expected behavior. A well-chosen hostname reduces friction for your user base and cuts down on connection-related questions. Explore the remaining options in the control panel for additional server tuning such as voice codec settings or user privilege adjustments.