[olug] DNS & NAT examples needed

[home slice]

pfSense is really good.
Clark Connect (Community Edition)is also worth mentioning.

I used to have a cox biz line with 16 IPs, my roomate's Linksys didnt work
too well with alot of concurrent connections, we swapped it out with a Clark
Connect box, then later a bare DSL distro with IPforward.  The original
swapout provided about 1-3ms decrease in network latency, allowed more
connections, and didnt hiccup every 12 hours and drop SIP traffic.

I dont know what your budget is, but I would go with a small block of IPs,
and pfSense as a router.
Just my 2 cents.

Charles





On Wed, Dec 31, 2008 at 2:09 PM, Curtis LaMasters <curtislamasters at gmail.com
> wrote:

> PAT is actually the term to use here (port address translation).  So
> instead
> of using a single IP with all ports NAT'd to an internal IP, you can NAT a
> single port on your single external IP to a host on your LAN.  In the
> information you've given you'll need UDP/53, TCP/80, TCP/443 and TCP/25
> (DNS, HTTP, HTTPS, SMTP).
>
> Curtis LaMasters
> http://www.curtis-lamasters.com
> http://www.builtnetworks.com
>
>
> On Wed, Dec 31, 2008 at 2:02 PM, <webtrekker at cox.net> wrote:
>
> > Hi Curtis,
> > I will be hosting a couple of different domains (nchea.org, nchea.net,
> > houseofswartz.*, and couple of other non-profits in 09), for web and mail
> > (scalix or zimbra) for each domain.
> > What I can't seem to get my head wrapped around is how to translate all
> of
> > the services/servers back out through a single public IP.
> >
> > I hadn't heard of pfSense, so I am heading there now... thanks for the
> tip.
> >
> > Patrick
> >
> > ---- Curtis LaMasters <curtislamasters at gmail.com> wrote:
> > > I may not fully understand what you want but I would replace the
> Linksys
> > > with something that does load balancing for your hosts behind (pfSense
> > comes
> > > to mind), setup UDP/53 (DNS) to round robin between your two (I assume
> > > you'll have two) DNS servers and setup host header based web access on
> > > TCP/80.  What other services will you be offering?
> > >
> > > Curtis LaMasters
> > > http://www.curtis-lamasters.com
> > > http://www.builtnetworks.com
> > >
> > >
> > > On Wed, Dec 31, 2008 at 12:07 PM, <webtrekker at cox.net> wrote:
> > >
> > > > Hi All,
> > > > After several attempts of finding a vps service that I liked or could
> > > > afford, I have taken the plunge and upgraded to Cox's business line
> and
> > now
> > > > have my very own IP (cheers all around...).
> > > > Anyway, I now need to setup DNS to support the different web, mail
> > servers
> > > > for a couple of different domains.  I have done this in the past, but
> I
> > had
> > > > plenty of public IP addresses available to work with.  Now, I only
> have
> > one
> > > > and need to use NAT for all of the servers behind it.
> > > > Can someone lend some guidance on how to set this up?  I have a XEN
> box
> > > > that will be running most of the servers and a Linksys wireless
> router
> > that
> > > > is doing the NATing for those and the rest of the PCs in the house.
> > > >
> > > > Not sure if I should take out the Linksys (or move it down stream)
> and
> > put
> > > > up a Linux box w/multiple nics and run my first nameserver there. or
> > just
> > > > run bind as one of the virtual hosts.
> > > >
> > > > I apologize for the long winded request, but your help is greatly
> > > > appreciated.
> > > >
> > > > Patrick
> > > >
> > > > _______________________________________________
> > > > OLUG mailing list
> > > > OLUG at olug.org
> > > > https://lists.olug.org/mailman/listinfo/olug
> > > >
> > > _______________________________________________
> > > OLUG mailing list
> > > OLUG at olug.org
> > > https://lists.olug.org/mailman/listinfo/olug
> >
> >
> _______________________________________________
> OLUG mailing list
> OLUG at olug.org
> https://lists.olug.org/mailman/listinfo/olug
>