dns entry incorporating web port number?

[John Heyer]

On 23 Aug 2001, Michael Davis wrote:

> Here's what I'd like to do: given that I have two (or more) web-based
> apps on the same box, distinguished only by port numbers, my users can
> go to a site such as xyz.belmont.edu:8950 for the first app, or
> xyz.belmont.edu:8960 for the second app, and so on.
> 
> I'd rather be able to create a DNS entry (I'm guessing a cname entry
> here) which would itself point to the correct port, thus something like
> app1.belmont.edu which would point over to xyz.belmont.edu:8950, and so
> on.
>
> It's just that users generally foul up on entering the correct port
> number.

If you have a web server handy, you could create a Virtual Host on the
desired DNS that forwards to itself to the real DNS on that port.  I do
this because we have an app that only works over SSL, and users kept
leaving out the s in https://.  In Apache, this would look like

<VirtualHost *>
	ServerName	app1.belmont.edu
	Redirect	/ xyz.belmont.edu:8950
</VirtualHost>

--
Johh Heyer - john at personal.supranet.net - http://heyer.supranet.net

"Me fail English?  That's unpossible!"  -- Ralph Wiggam