DNS instead of IP when adding server to favorites

TeamSpeak Server Suggestions and Feedback
21

I drew a littel graohic for you showing what exactly is wanted here.
At no time is any actual resolving by TeamSpeak services needed.
The idea is that the Server tells any client the correct domain to connect to.

E.g. you have your local server with the IP 1.2.3.4. You connect to this.
Then you save it and it get’s synced with myTS. When you then try to connect to this bookmark with your laptop on the go it wont do as the local IP is saved. Thus if the server had reported the correct domain to connect to the bookmark should contain the domain and not the IP.

       |-----------|
       | TS Server |
       |-----------|
       1./|\   |
 connects |    | 2. reports
    to IP |    | domain back
          |   \|/
        |--------|            |---------------|
        | Client |----------->| DynDNS Server | 
        |--------| 3. resolve |---------------|
             |
             | 4. if connected IP
             | == resolved IP
            \|/
        client saves
       domain instead
           of IP

Also servernames won’t work here because the server list is done by either reporting or scraping and the nicknames are just a resolver. This a feature currently missing in TeamSpeak server.

2 Likes
22

Yes servernames are resolver and that is the point here, you CAN add you dyndns domain to this servernames what i don’t know is if TeamSpeak give Servernames priority or instead IP and if TeamSpeak priority Servernames over DynIP he got what he want.

23

What you connect to gets saved, no matter whether there are servernames or not. This would again require reverse lookups that just are not usefull here.

25

…
He has as DynDNS Domain who is UpToDate, so Servernames will do a reverse lookup on his current DynDNS Domain with the current ip…
Servername → Resolv → DynDNS Domain → Current IP → Teamspeak.
Look at myteamspeak.com, if he add his DynDNS Domain this should workout.

The point is easy to understand currently TeamSpeak add the IP address as Server.
What he wants is that Teamspeak add his DynDNS Domain instead of his IP, but thats currently not possible, so best option is to pointing the DynDNS Domain to a MyTeamspeak Servername.

And if Teamspeak priority IP over Servername the only option is what @FakE said.

EOF

26

This is not a reverse lookup. This is a forward lookup.

And assuming that you are referring to server nicknames as “servername”: Those won’t help here.

Server nicknames - when pointing to a domain name - merely act as an alias for something that already is a human-readable representation of an IP address.

You don’t really need this confusing proprietary feature when you already got a domain, be it “dynamic” or not.

All that is really missing is a way to configure a static name for the server which is reported to clients so they can connect to it.

And that’s exactly what I wrote wayyyy up there. Why is there this ongoing discussion now?

1 Like
27

Thanks!