--h31gzZEtNLTqOjlF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Dec 06, 2001 at 07:12:01AM -0700, James Lee Bell wrote:
> Can't you have one of the DNS hosting services (like the dynamic ones)=20
> do port changes as well? IOW, I thought a couple of them at least=20
> offered with their pay services (~10/mo) the ability to take a FQDN of=20
> www(.yourdomain.com) and return real.ip.add.ress:81.

Sure. Dyndns.org provides both the dynamic dns entries and webpage
redirects. What you'd have to do use use both to get this effect -- one to
get your DNS of your site, the other to redirect to port 81.

> Thomas Mondoshawan Tate wrote:
>=20
> > On Wed, Dec 05, 2001 at 12:48:35AM -0700, Rick Rosinski wrote:
> >=20
> >>Are there any docs on changing the port to 81?  Others say it is a pain=
. =20
> >>WHy?  What are the consequences of changing the port?
> >>
> >=20
> > Yep. Read the docs at http://www.apache.org. It's not so much of a pain,
> > really, just that people can't go to http://www.yourhost.com and see the
> > page -- they have to go to http://www.yourhost.com:81. The consequences=
 are
> > that, since you're not using a standard port now, web browsers won't be=
 able
> > to communicate with the webserver software. As such, to even view the p=
age,
> > you have to specify the port in the URL (eg: http://www.yourhost.com:81=
).
> >=20
> > All it takes (in Apache) is a change of the directive in httpd.conf that
> > reads as "Port 80" to read "Port 81".

I didn't write this... =3Dop

--=20
Thomas "Mondoshawan" Tate
phoenix@psy.ed.asu.edu
http://tank.dyndns.org

--h31gzZEtNLTqOjlF
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE8D3+CYp5mUsPGjjwRAq+AAKCBbjiTp7Y4if7x8tKukqkaxgAS/wCffGik
S4+pVjb7SNBUYLVIKLcG7h8=
=uNmK
-----END PGP SIGNATURE-----

--h31gzZEtNLTqOjlF--