Integrating DHCP & DNS (Or WINS)?

smcavoy asks: "Hello, I am working on a growing network (30+ now, more added daily!). We do a lot of development on Linux (Redhat/Debian) and use Remote X a lot. Currently the network is all static IPs, each server has a /etc/hosts file, containing all name/ip mappings. I am looking to use DHCP to make it easier to add systems quickly, but we use many scripts that use system names for remote displays (xterm -display [systemname]:0). So I need to integrate name resolution with DHCP. Any Ideas?"

ISC-DHCPD

[The Madpostal Worker]

There are perl scritps that will update a DNS zone based on the leases file(check freshmeat). Also consider using DHCP to issue leases based on MAC address(basically static assignment) and then using DNS for name resoultion.

/*
*Not a Sermon, Just a Thought
*/

http://www.cpl.net/~carville/DHCP-DNS/

[matthewg]

If you're using Debian, apt-get install dhcp-dns. Otherwise, check the above URL. [cpl.net]

V3

[Anonymous Coward]

DHCP version 3 from ISC takes care of this. I've been using it for 9 or 10 months without a single problem.

http://www.isc.org/products/DHCP/dhcp-v3.html [isc.org]

Windows 2000

[supergumby]

I was originally planning to play flamebait, but now I've got a different version of my original comment.

What about *nix DHCP solutions that interface with the Windows 2000 DNS server? MS' own can dynamically update IPs for DHCP clients.

Dynamic DNS

[vrt3]

We're using dynamic DNS updates with BIND v8.2.1 and the ISC DHCP Server V3.0b2pl6, with no problems. The relevant lines from /etc/dhcpd.conf: ddns-domainname "ourdomain"; ddns-rev-domainname "in-addr.arpa"; In /etc/named.conf: in the relevant zones, include the line allow-update { list of hosts that are allowed to update the dns };

Static DHCP possibly. Be aware of security.

[embobo]

Static DHCP may not be the most flexible solution but it is easy. First, keep a regular, non-dynamic dns setup. Then configure your dhcp to always give the same ip addr to the same host. There are multiple ways to do this, based in MAC address or whoever the client claims it is.

Keep in mind that using DHCP or allowing a client to update the DNS easily leads to a huge reduction in the security of the systems on the network because IP spoofing can become as easy as asking the DHCP server for a certain IP addr.

Re:ISC-DHCPD

[Omega996]

i've used DHCP to assign static IP addresses based on MAC address for over 200 hosts. Works great...

Re:Static DHCP possibly. Be aware of security.

[sharkey]

This is what I have been doing for the last year or so. It's a bit of a pain to keep both DHCP and DNS updated, but it's wonderful if I have to change a gateway or other global variable. With DHCP you can just push it on down with the next lease request. Just don't set the leases for too long;)

--

And another? perl solution:

[kwerle]

See also http://www.sector13.org/kaz in/ projects/dhcp_dns.html [sector13.org], though it looks like it is being obsoleted...

DNS vs. WINS

[Ino]

As far as I know - M$ understanding of DHCP is somewhat b0rken. Although I know that the client can send it's hostname to the server - with a M$ based DHCP server you cannot do this. Whether you send the hostname or not to the DHCP server you won't get registered in the DNS. Go figure.

Bottom line is - if you go for DHCP - use some *STANDARD* implementation (which bloody well excludes M$). ISC's DHCP v.3 is a good start for you.

--
Click here [ecrix.com]to win a free 66GB tape drive!