There is a DHCP server (dhcpd) and a DHCP client (usually pump or dhcpcd).
A DHCP client (dhcpcd) sends out a broadcast request to your LAN [OK,
uber-geeks I know about IP helper so let's not muddy the waters here].
asking for an IP address. A DHCP server (actually anything on the LAN, but
only the DHCP listens for and works with a DHCP request) hears that request
and provides the client an address.
BIND is DNS and provides name resolution only. It does not provide IP
Addresses. I have some easy to read reference material on DNS and BIND at
http://web.tampabay.rr.com/sjohnson/ Just click the "Linux Resources" tab
on the left.
Now, there is something called Dynamic DNS. This is probably what you were
thinking of. The basic premise of this is that the DHCP server doles out the
IP address to the client and then contacts a DNS server (can be the same
server) to put in the "A" and "PTR" records for you. In this case, *in
effect* the DHCP server is also maintaining DNS information as well *sort
of*.
----Original Message Follows----
From: Paul M Foster <paulf@quillandmouse.com>
Reply-To: slug@nks.net
To: SLUG List <slug@nks.net>
Subject: [SLUG] DHCP or BIND
Date: Wed, 13 Feb 2002 22:13:52 -0500
I've never really untangled DNS for myself, but I'm working on
understanding it right now. One question comes up that I don't seem to
have an answer for. I know there's a dhcpcd, which grabs an IP address
from a nameserver. And I know there's BIND, which serves up IP
addresses. I thought there was a DHCP server daemon as well, which
would perform the function of serving up IP addresses on small networks.
Is that not the case, or do I need to run BIND to hand out IP addresses?
Paul
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 16:04:54 EDT