Re: CGIDEV2 question

["Peter Dow (ML)" <maillist@xxxxxxxxxxxxxxx>]

Hi Scott,

I'm sure you're right -- it's a redirect.  In any case, it seemed to be 
a method of allowing a url without port#s from the client side, but 
providing port# separation on the server side, which is what I thought 
the op was asking for.
Peter Dow
Dow Software Services, Inc.
909 793-9050

web400@xxxxxxxxxxxxxxxx wrote:
> > I'm no expert on this, but I've used no-ip.com's DNS features to convert
> > a "sub-domain" url to a url with a port, e.g. sub.domain.com is
> > translated by the DNS to domain.com:1000.
> >     
> Hmmm... I've studied DNS fairly in-depth, and although there was at one 
> time a specification for looking up ports via DNS, nobody used it.  In any 
> case, DNS wouldn't take a domain name and return a port, you'd have to 
> supply a service to look up. Remember, DNS is not HTTP-specific, it 
> doesn't know what you're planning to use the domain name for.
> More likely, what you're seeing is a two-step process where it first looks 
> up the IP address, then the HTTP server on that IP address provides a 
> re-direct to the given port number.
> If that's the case, it's not pure DNS.  It's a combination of DNS to get 
> the IP address, and HTTP to send a re-direct.
>