Integrating DHCP & DNS (Or WINS)? 10
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 (Score:1)
*Not a Sermon, Just a Thought
*/
http://www.cpl.net/~carville/DHCP-DNS/ (Score:4)
V3 (Score:1)
http://www.isc.org/products/DHCP/dhcp-v3.html [isc.org]
Windows 2000 (Score:1)
What about *nix DHCP solutions that interface with the Windows 2000 DNS server? MS' own can dynamically update IPs for DHCP clients.
Dynamic DNS (Score:1)
Static DHCP possibly. Be aware of security. (Score:1)
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 (Score:1)
Re:Static DHCP possibly. Be aware of security. (Score:1)
--
And another? perl solution: (Score:1)
DNS vs. WINS (Score:1)
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!