DNS beginner question

[Michael S]

Derek,

Actually my domain is a subdomain (e.g. mysubdomain.domain.com), and
obviously the domain server for domain.com points correctly to my
site.
What I want to have (mostly for the sake of configuring DNS) is
something like www.mysubdomain.domain.com, and
ftp.mysubdomain.domain.com.

Can my second BSD machine be the secondary DNS?

When you say set it up correctly on the router, you mean forwarding
the requests from port 53 to the BSD machine, running BIND? Or there
are extra steps that I need to take?


Thanks a lot.
Michael

On 7/6/06, Derek Ragona <derek at computinginnovations.com> wrote:
>
>  Yes DNS will work with your port forwarding assuming you have it set up
> correctly on your router.
>
>  Are you trying to be the authoritative DNS for your domain?  If you are you
> will still need a secondary DNS.
>
>          -Derek
>
>
>
>  At 05:56 AM 7/6/2006, Michael S wrote:
>
>
> 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 at gmail.com> wrote:
>
>
>
>  On 7/5/06, Michael S <msherman77 at 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 at fbsd ~]# fortune
>  Happiness is just an illusion, filled with sadness and confusion.
> _______________________________________________
>  freebsd-questions at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>  To unsubscribe, send any mail to
> "freebsd-questions-unsubscribe at freebsd.org"
>
>  --
>  This message has been scanned for viruses and
>  dangerous content by MailScanner, and is
>  believed to be clean.
>  MailScanner thanks transtec Computers for their support.
>
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
> MailScanner thanks transtec Computers for their support.