[TriLUG] DNS and DHCP

[Matt Flyer]

To offer a contrary point of view, I would say go with DHCP3 and Bind9.
Here is a link to a web site that I used about 1.5 years ago to get
dynamic DNS + DHCP running on my own LAN on the first day that I install
my home LAN server:
http://lani78.wordpress.com/2008/08/09/setting-up-a-dns-for-the-local-network/

***Be sure to check out the links on the right hand side of the page.
There are pages for DHCP setup and for the dynamic linking of DHCP and
DNS ***

I literally had it up and running in less than an hour with newbie level
experience with Linux.  Machines will receive a DHCP assigned address,
which is automatically updated in the DNS for both forward and reverse
lookups.  I have since extended it to two LAN servers and have
redundant-fail over DHCP and DNS so that I can take one machine off line
for maintenance, reboots, or whatever and not even notice.  I also use
the DNS server as my primary DNS resolver rather than relying on TWC's
(which always seems to be what would go down and fail on their end).

On Mon, 2011-08-08 at 23:26 -0400, Jonathan Woodbury wrote:
> DNSMasq probably is the way to go.  But it is worth also knowing about
> multicast DNS.  If you're running Apple's bonjour on Mac or Windows or the
> avahi-daemon on Linux (standard equipment with Ubuntu), you can probably
> already resolve your hosts at home by appending .local to their host names.
>  For example:
> 
> jpwoodbu at chapman:~$ ping fry.local -c 1
> PING fry.local (10.0.6.185) 56(84) bytes of data.
> 64 bytes from fry.local (10.0.6.185): icmp_req=1 ttl=64 time=0.794 ms
> 
> jpwoodbu at chapman:~$ ping mahler.local -c 1
> PING mahler.local (10.0.6.182) 56(84) bytes of data.
> 
> Fry is one of my Linux systems and mahler is running Windows 7 with iTunes
> (and therefore Bonjour) installed.  Neither of those hosts have A records in
> any local DNS zones.  Although they both have AAAA records in public DNS. ;)
> 
> Jonathan
> 
> On Mon, Aug 8, 2011 at 10:47 PM, Alan Porter <porter at trilug.org> wrote:
> 
> >
> > Give dnsmasq a try... it does exactly what you describe,
> > plus it's a DHCP server, so it knows what machines have
> > what addresses on the local network.  Normal setup is
> > really simple, and yet it can also do some advanced
> > stuff.
> >
> > --