Boston Linux & Unix (BLU) Home | Calendar | Mail Lists | List Archives | Desktop SIG | Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings
Linux Cafe | Meeting Notes | Blog | Linux Links | Bling | About BLU

BLU Discuss list archive


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

apache



On Wed, 1 Sep 2004 13:20:12 -0400 (EDT)
David Backeberg <dave at math.mit.edu> wrote:

> If the inside-LAN machines are trying to use DNS to resolve the
> address of your website, that's your problem. Add an /etc/hosts line
> to those machines to alias that www.whatever.com to your inside IP
> address.
Good point. In my specific case, I happen to have port 80 blocked at my
firewall because I was tired of seeing code red :-).
But, the way I have my system set up is that I have a local domain where
I use /etc/host files that contain the interior LAN addresses.
The external address is served by a DNS server, and points to my
external IP address, and normally would be port-forwarded by the
firewall. 

In both cases you should be able to get at your web server from other
systems in the LAN, either by using the internal addresses or the
external addresses.
-- 
Jerry Feldman <gaf at blu.org>
Boston Linux and Unix user group
http://www.blu.org PGP key id:C5061EA9
PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.blu.org/pipermail/discuss/attachments/20040901/a538d21f/attachment.sig>



BLU is a member of BostonUserGroups
BLU is a member of BostonUserGroups
We also thank MIT for the use of their facilities.

Valid HTML 4.01! Valid CSS!



Boston Linux & Unix / webmaster@blu.org