> From: Andre Müller <[email protected]> > Date: Thu, Mar 6, 2014 at 2:50 AM > Subject: Re: [hlds] Advertise a server using account ID > To: Half-Life dedicated Win32 server mailing list < [email protected]> > > Please read this http://en.wikipedia.org/wiki/SRV_record or > other better articles where srv is explained before you are > writing sensless stuff.
I am not seeing anything I said as "senseless". SRV's give a client (that know's what to query for) a mechanism to find what host+port to goto to find it. Quoting from that article you linked: > An SRV record has the form: > > _service._proto.name. TTL class SRV priority weight port target. > > service: the symbolic name of the desired service. > proto: the transport protocol of the desired service; this is usually either TCP or UDP. > name: the domain name for which this record is valid, ending in a dot. > TTL: standard DNS time to live field. > class: standard DNS class field (this is always IN). > priority: the priority of the target host, lower value means more preferred. > weight: A relative weight for records with the same priority. > port: the TCP or UDP port on which the service is to be found. > target: the canonical hostname of the machine providing the service, ending in a dot. > > An example SRV record in textual form that might be found in a zone file might be the following: > > _sip._tcp.example.com. 86400 IN SRV 0 5 5060 sipserver.example.com. So, if the clients know to query for "_hlds._udp." + whatever FQDN they were given, something like this would work: _hlds._udp.gameserver1.example.com. 86400 IN SRV 0 5 27015 gameserver1.example.com. Clients looking for "gameserver1.example.com", query for "_hlds._ udp.gameserver1.example.com.", and get told to connect using port 27015 (or whatever's in the SRV record) to the A-record matching " gameserver1.example.com." Those operators hosting multiple games on the same IP address, could just use different FQDN's for each: _hlds._udp.gameserver1.example.com. 86400 IN SRV 0 5 27015 gameserver1.example.com. _hlds._udp.gameserver2.example.com. 86400 IN SRV 0 5 28015 gameserver2.example.com. _hlds._udp.gameserver3.example.com. 86400 IN SRV 0 5 29015 gameserver3.example.com. _______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: https://list.valvesoftware.com/cgi-bin/mailman/listinfo/hlds_linux
