Date: Thu, 6 Jul 2006 06:56:15 -0400 From: "Michael S" <msherman77@gmail.com> To: "David Stanford" <dthomas53@gmail.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: DNS beginner question Message-ID: <d5f57b9c0607060356j4874c3aaidfab02e3280f81ad@mail.gmail.com> In-Reply-To: <f2c91f770607051951s1864cf65j5443d90611368b@mail.gmail.com> References: <d5f57b9c0607051906g2b0f71b1h280594cd73d4a73@mail.gmail.com> <f2c91f770607051951s1864cf65j5443d90611368b@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
The "open" ports are simply port-forwarded from the router to my internal network (NAT). And I only have one public IP. For me the more important issue is whether DNS would work with private IP addresses. On 7/5/06, David Stanford <dthomas53@gmail.com> wrote: > > > On 7/5/06, Michael S <msherman77@gmail.com > wrote: > > Hi all. > > > > I am trying to set up a DNS service. I have 2 FreeBSD machines, one's > > web and DNS (that I am setting up) and the other FTP. Both machines > > are behind a router and get local addresses (i.e. 192.168....). If > > DNS, FTP and web ports in the router are open, will I be able to set > > up the DNS in a way such that when someone from the outside types > > www.mydomain.com, he'll be taken to the machine that runs apache, and > > when he types ftp.mydomain.com he'll be taken to the machine which > > runs ftp? > > By the way simply typing ftp://mydomain.com and http://mydomain.com > > does the trick, but I want it to work with prefixes too. > > > > Hopefully my question isn't too confusing. > > > > Thanks in advance. > > Michael > > > > Hi Michael, > > You'll have to clarify "open" regarding the WEB, DNS, and FTP ports on the > router. Are they simply port-forwarded to the internal servers (meaning > based on service ports) or do you have one-to-one NAT mapping a public IP to > an internal for each server? If it's the latter, and each machine has its > own public IP, then you can simply set DNS to point to each server > respectively: > > www.mydomain.com -> publicIP1 -> privateIP1 > ftp.mydomain.com -> publicIP2 -> privateIP2 > > The real question is whether you have a block of public IPs or just one. But > to be honest, you can probably get away with just having a single public IP > and using port forwarding as most browsers (including Firfox and IE) > recognize the "ftp" and "www" subdomains and automatically adjust to that > protocol. > > i.e. ftp.somedomain.com will automatically be translated to > ftp://ftp.somedomain.com (ftp.freebsd.org ). > > -David > -- > [root@fbsd ~]# fortune > Happiness is just an illusion, filled with sadness and confusion.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d5f57b9c0607060356j4874c3aaidfab02e3280f81ad>