PART 2:
2. "(...) there is actually a relatively low demand [for dynamic DNS support].": Notice the usage of the word 'relatively', it stands there as a precaution because, actually and in fact, there is a significant demand for dynamic DNS support but since users are mostly ignored by GT staff, they can come up with sentences like that and use the term 'relatively' to mean relatively pretty much anything they deem an answer to the question. The matter of fact is that the so called “low demand” is directly proportional to GT’s will to implement it and support it, anyone that reads through GT topics on the subject quickly realizes that it is a no go;

Now, about the detailed "Dungeons & Dragons" of dynamic DNS support implementation, it is stated that the problem is two-fold, so let’s try to address the specifics:
a) "Whenever the IP changes, a safer way to get it tracking under the new IP would require the server owner to reclaim the server each and every time before it tracks under a new IP. If there would be no mechanism like this, servers could change IP's to any server not already on the website. Obviously this would get annoying for server owners. If there was no moderation, you could set a domain name to resolve to a very popular server that is not currently on the website and switch it to your server IP when it gets a good rank."

PART 3:
This looks as more of an excuse than a problem. The current GT implementation works that way, but if dynamic DNS support would be implemented, then the domain name would be the primary identifier for the server and not the IP address as it is now. The IP would not matter for the claiming process, just to collect the stats and data, for connecting to it, ya know? And about the pseudo-exploitation... Okay, so how about this: When using dynamic DNS, you shouldn’t allow the user to manually change the IP of his server in GT, it should always be resolved by GT server through DNS;

b) "I could set up a domain name, like (burnscutebunnies.com), to resolve to any IP address and add it as that, so the actual owner of that server would have to go above and beyond to get that removed."

This one is a bit odd in a way that it is stupid... this makes no sense whatsoever since you can do pretty much the same thing using any IP address of any website.
Why is a domain name any different or exceptional? Don't answer, it isn't and the point made in the above quote is absent thought.

PART 4:
Okay, it seems that those two problems worth mentioning are only the tip of the iceberg "among a variety of [other] issues", but I really don't see it. And the fact that GT admin mentioned 2 issues that actually don't exist, it does say quite something about the possibility of other random made-up issues... All in all, GT doesn't support dynamic DNS for reasons that have nothing to do with lack of demand, and also probably not because of supposed mighty security issues or otherwise. And in case you're wondering how do I know what I've just said, I don't. I'm just pulling stuff out of my ass in the same way GT staff does, looks legit doesn't it? Right...
With all due respect.

Last but not least, it has been stated over and over, by GT staff members, that dynamic DNS support is way back on their list of priorities. This is not necessarily a contradiction, it just goes on to prove that they don't give a damn because everybody rents servers and whatnot.

Thanks for your feedback, ner0xy. I can understand you are very passionate about tracking via domain name / Dynamic DNS.

You are very correct. There would be no "significant" technical changes required to physically support DNS in the existing system. Significant would be a relative term, which you do not like, since a large number of GT components would need to be adjusted. Relative, in many cases can be the result of number of users it would affect, internal need, or the number of requests. If you need any further explanation of the term, you might check out http://dictionary.reference.com/browse/relative

If GT were to publicly post "abuse" statistics, you'd might be surprised to hear that the current GT system automatically (with manual input as well) bans abuse that probably ranges from 1000-10000 servers on a daily basis. Dynamic DNS addressing would have a significant impact on this number.

Finally, if you do have a good idea of how to deal with the process which actually addresses the issues associated with implementing such a system, feel free to provide that to me via PM. We do understand that users like you would not abuse the system, however, a significant number of users would be impacted if there was no well-defined abuse measure.

GameTracker now supports DNS addressing! Thanks for your enthusiasm.

maul wrote:
All,

Based on popular demand, we are trying out a new feature on GameTracker which allows you to track your servers with DNS.

If you have a server on GT and want to try it, visit the "manage" page of your server. At the bottom of the page is a text area where you can specify a DNS name. Once you specify a DNS name, all URLs related to your server and players will update to contain the DNS name.

Any feedback is welcomed.