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]

Trying to learn something but not sure what to Google...



On Fri, Sep 10, 2010 at 12:39:01PM -0400, Myrle Francis wrote:
> Hello (and as always thank you in advance)
> 
> I have a Linux web server that I use with dydns and understand with a
> single web server I set up port forwarding but..
> 
> what I don't understand is how to get two web servers working behind my
> router(dd-wrt) if they are both using port 80.
> 
> I understand on a LAN DNS would take the address web1.network.com and
> send it to the proper machine using dns with port 80.  How does this
> work with two web servers (ie web1.network.net and web2.network.net)
> behind my router.  do I have to set up a dns server in a dmz?
> 
> also in  my first example my web1 is not in in a DMZ (maybe that is a
> bad idea..) but on it own private network.
> 
> i'm just looking for what he buzz word is so I can  Google it and any
> help would be appreciated.

The problem isn't dyndns. The problem is with NAT.

Your ISP has assigned you one IP address. You can have as many
DNS names pointing to that IP as you want. You can run services
on any port you wish. But if you want multiple things to answer
the same IP:port combination, you need a single device that
answers and then funnels the packets to the right place.

One thing you could do, perhaps, is run all the virtual servers
on the same machine. Use your web browser's
virtual-server-by-name capability to decode HTTP1.1 requests and
answer appropriately. For Apache, see
http://httpd.apache.org/docs/2.2/vhosts/

Another thing you could do is run a reverse proxy to take the
same HTTP1.1 requests and farm them out to different machines.

A third thing you can do is ask your ISP for more IP addresses. 

A fourth thing you can do is hire an external service to accept
requests on your behalf and redirect them to various ports on
your single IP.

A fifth thing you can do is move your hosting to a virtual
machine instance where the provider will happily sell you as
many IPs as you need. Or a dedicated server, or many other kinds
of service.

-dsr-



-- 
http://tao.merseine.nu/~dsr/eula.html is hereby incorporated by reference.
You can't defend freedom by getting rid of it.






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