Date: Fri, 27 Jun 2003 19:21:02 -0300 From: "Han Hwei Woo" <hhwoo@argosy.ca> To: "John DeStefano" <deesto@yahoo.com>, <freebsd-questions@freebsd.org> Subject: Re: Mask IP:port with Domain Name Message-ID: <003d01c33cfa$64ae7030$0200a8c0@a7n8x> References: <20030627150110.76721.qmail@web40609.mail.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Sorry, I missed the original reply to this. What you can do is setup an extra redirect to the URL. i.e. have your redirection service point to a different URL (vhost) that still points to your machine. Since it seems you do not have a lot of flexibility with DNS, it would probably be easiest to run this vhost on a different port. Then, on your vhost, setup your own http redirect http://httpd.apache.org/docs/mod/mod_alias.html#redirect to your actual site with the URL you want your clients to see, and the client's browser should then show this URL. The port will still show up using this method, but this is the only way to go if you want your own domain to show up without paying for any additional services. The masking method dyndns uses, is to essentially serve up a frameset, and redirect to your URL through a frame, thus the original URL is what will show in the client's address bar. Dyndns charges for this service however, and you will not be able to use it with your own domain name unless you buy their custom dns service. Hope this answers your questions. ----- Original Message ----- From: "John DeStefano" <deesto@yahoo.com> To: "Han Hwei Woo" <hhwoo@argosy.ca>; <freebsd-questions@freebsd.org> Sent: Friday, June 27, 2003 12:01 PM Subject: Re: Mask IP:port with Domain Name > > > Han Hwei Woo <hhwoo@argosy.ca> wrote: > >I believe the ServerName directive in Apache is what you're looking for; > >it's what people's browser address field will show once they connect to your > >site. > Thanks, but as I mentioned when Chuck brought this up yesterday, my > "ServerName" directive is set properly in the format: > ServerName www.mydomain.com > in httpd.conf. This does not seem to make any difference at all. > > >As far as your security concerns go, you can not run a website without > >exposing the IP address of the webserver machine, with or without masking. > >If a client machine didn't know your IP address, it would not know where to > >retrieve your web pages from. > Agreed (though not entirely true; you can use a web redirect service to > successfully cloak a true IP address; I've done this successfully), but that's not > really what I'm after. > I just don't want my IP address and port number combination glaring in a web > browser's address bar when a user visits my web site. I realize that if someone > really wanted to resolve my IP, they could, but I'm also thinking of people who > don't know what an IP address is, and are asking me questions like "What > happened to the web site? I typed in the words you told me to, and it turned > into a bunch of numbers!" > > > --------------------------------- > Do you Yahoo!? > SBC Yahoo! DSL - Now only $29.95 per month! > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?003d01c33cfa$64ae7030$0200a8c0>