[ previous ] [ next ] [ threads ]
 From:  Craig FALCONER <cfalconer at avonside dot school dot nz>
 To:  m0n0wall at lists dot m0n0 dot ch
 Subject:  RE: [m0n0wall] hostnames+NAT
 Date:  Thu, 13 Oct 2005 13:40:43 +1300
Depending on load, your web server should be able to handle any domains that
resolve to your IP.  Apache calls this virtual hosting - I run
http://criggie.dyndns.org and http://guyasoc.dyndns.org off the same web
server, while http://shell.clug.net.nz is redirected to
http://shell.clug.net.nz:8080 which is then NATted to another internal IP.

FTP can't really handle this approach though.  Also, it looks really ghetto,
and theres the chance that some anal ISPs/companies block access to
less-standard ports.  Port 81 is another workable choice.

-----Original Message-----
From: James W. McKeand [mailto:james at mckeand dot biz] 
Sent: Thursday, 13 October 2005 1:26 p.m.
To: m0n0wall at lists dot m0n0 dot ch
Subject: RE: [m0n0wall] hostnames+NAT

Hans Maaherra wrote:
> Hello
> I own a domain name, and now it is assigned to my m0n0wall's ip.
> Is there a way to get for example
> www.domain.com(:80) forwarded to
> john.domain.com(:80) forwarded to
> ftp.domain.com:21 forwarded to
> ftp2.domain.com:21 forwarded to
> and so on?

Only if you have more than one IP for the WAN on your m0n0wall. 

First thing is to add the additional IPs to the WAN interface. This can
be accomplished using Server NAT. 

Next, you can set Inbound NATs for the additional IP. Each of the
external IPs can be NATed to different internal hosts. You can use a
single external IP to different internal IPs for different services (www
and ftp to public IP 1 goes to different internal IPs .2 and .3)

Finally you will need to make changes in your DNS for your Domain. You
can assign public IP 1 to www.domain.com, public IP 2 to
john.domain.com, etc.

James W. McKeand

To unsubscribe, e-mail: m0n0wall dash unsubscribe at lists dot m0n0 dot ch
For additional commands, e-mail: m0n0wall dash help at lists dot m0n0 dot ch