And depending the number of nodes you have Bind would make things easy to manage.  I have a LAMP dev box on a private IP (all my nodes are on a private IP).  I use the Windows host file to resolve any sites hosted on my dev box.  I use the TLD of "dev", like SomeSite.dev.  I put the IP of the LAMP box along with the name of the domain in the host file like this : 192.168.30.55 SomeSite.dev . However I am not able to reach the dev site via a browser on any other computer on my network because there is no way to resolve to it.  If I had Bind setup then any computer on my network would be able to access the test sites I have on my LAMP box and it would be a great learning experience. I would definitely setup Bind for your private net if you want to learn. ------------------------ Keith Smith --- On Thu, 8/12/10, Stephen wrote: From: Stephen Subject: Re: Running BIND for home network name resolution To: "Main PLUG discussion list" Date: Thursday, August 12, 2010, 7:00 AM a very simple reason comes to my mind, one i am wanting to use so i can learn bind to add it to my list of skills. On Wed, Aug 11, 2010 at 6:12 PM, Eric Shubert wrote: > Eric Cope wrote: >> >> Hello all, >> I want to setup FQDNs for my home network. > > Why? What do you intend to accomplish? > (Too often people try implementing a solution for a problem they don't > really understand.) > >> Does anyone have a good tutorial on setting up BIND for a Mac/Windows/*nix >> environment? I was hoping to keep DHCP from my router (it supports static >> DHCP - yes I know that's contradictory). >> I have a dynDNS account, .dyndns.org . >> >> I want to be able to assign names like >> >> macbook..dyndns.org for my macbook >> crappy..dyndns.org for my windows machine >> e-server..dyndns.org for my freebsd server >> ... > > To be able to do this from the outside/wan, you simply need a client program > that tells dyndns.org what your (router's if you have cable, or  DSL modem's > if you use DSL) public IP address is, and when it changes. See > http://www.dyndns.com/support/clients/. That program (there are several from > which to choose, some of which are already built-in to firewalls such as > IPCop) can run on your router or any one of your computers behind it. There > are several ways you can do this, none of which directly involve bind. > DynDNS handles all the bind stuff for you on the public side. > > On the lan side of things, you can set up a private DNS server if you'd > like, but for a handful of computers, it's often easier to just edit the > hosts file on each machine. > >> My googling has come up short, mostly because my search terms are lame. >> Anyone have any ideas? tips? tutorials? good search terms? I don't want to >> rely on hosts files. > > Again, why (not)? > > Personally, I use IPCop, which takes care of all of this (and much more) for > me. IPCop is relatively simple, and very reliable. > > -- > -Eric 'shubes' > > --------------------------------------------------- > PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us > To subscribe, unsubscribe, or to change your mail settings: > http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss > -- A mouse trap, placed on top of your alarm clock, will prevent you from rolling over and going back to sleep after you hit the snooze button. Stephen --------------------------------------------------- PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us To subscribe, unsubscribe, or to change your mail settings: http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss