Name Server Behind Router

[McNutt, Justin M.]

Because it's still easier to set up a centrally-run DHCP server (especially
if it's ISC's) than it is to keep up with client configurations,
particularly if your other services (DNS servers, for instance) change very
much.

In one of the private networks I operate, this saves oodles of time.  It's
only five machines, but when a new machine is added, just turn it on.  The
maintenance involved in worrying about whether or not I've already assigned
that IP address is well worth the initial effort of setting up the DHCP
server.

...and we're getting off-topic.

--J

> -----Original Message-----
> From: Danny Mayer [mailto:mayer at gis.net]
> Sent: Saturday, November 10, 2001 5:55 AM
> To: Cricket Liu; Jonathan Hilgeman; bind-users at isc.org
> Subject: RE: Name Server Behind Router
> 
> 
> 
> At 05:42 PM 11/9/01, Cricket Liu wrote:
> 
> >I'd run dhcpd on the FreeBSD box to assign internal IP addresses.  If
> >you run the ISC's DHCP server, you can configure it to dynamically
> >add forward and reverse mappings for your DHCP clients.
> I disagree will you on this.  If you have a private address space like
> 10.x.x.x why go to the bother of setting up and managing yet another
> server? Just give all of your boxes fixed 10.x.x.x addresses 
> and forget
> about it. Managing yet another service is a headache you don't need to
> deal with if it's not necessary.
> 
>          Danny
> 
>