Man this takes me back to ... 1998-1999 ... editing my hosts file so I could just type "connect servername in hosts file". Even back then, server ops wanted better DNS support, mainly for the dreaded IP change. If users stored their favorite servers as a hostname, then IP changes would be 1 less thing to worry about (worst case scenario would be a very long TTL value making your clients connect to the old IP).
SRV records support would be awesome ... it's one of those ideas that makes you go "Why hasn't this support been implemented YEARS ago?" Oh well. SRV records have only been around 11+ years now ... why take advantage of them now, when damn near every (if not all?) *current* OS understands them? --mauirixxx -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Thursday, August 16, 2012 7:21 PM To: [email protected]; Half-Life dedicated Win32 server mailing list Subject: Re: [hlds] srcds vhosting The good thing about DNS is that, apart from CNAME, it's one-to-many. So in theory, assuming hypothetical DNS support on Source, you could set up 20 SRV records for the same subdomain, and if the user adds that to their favourites they then get a grouped list of all your servers. On 17/08/2012, at 3:08 PM, Kameron Gasso <[email protected]> wrote: > On 8/16/12 4:31 PM, [email protected] wrote: >> As far as I know, Source doesn't use DNS at all, it's completely >> IPv4-address-based. Lookups are done at connect time or adding-to-favourites >> time, completely by the client. There's no official or unofficial way to do >> HTTP-style vhosting as far as I am aware. > > I dug into this in-depth a while ago and came to the same determination: > the existing DNS support is pretty much useless beyond the initial connect. > > Favoriting or connecting a host by name is nice, but it's a one-time > thing. IMHO, the client really should support saving by name so > resolution occurs later too, but instead saves by IP. Hosting > providers, ISPs, and network infrastructures can change often, why not > take advantage of DNS when it's already supports making these changes > transparent to end users? > > Changing a server's "hostname" field to redirect users after an IP > renumbering just feels like a crummy hack to me. > > Sorry to go so far off-topic here, but this has been a pet peeve of > mine with Source's network support for a while. And as for the OP, > even proper DNS support won't help you here. If it ever comes along, > maybe Valve can add SRV record support as others have mentioned and > make us both very happy. :) > > Cheers, > -- > Kameron Gasso | [email protected] > > _______________________________________________ > To unsubscribe, edit your list preferences, or view the list archives, please > visit: > https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds
