Set up a DHCP server to manage IP addresses
An anonymous reader writes "The second in a three-part series on how to leverage Linux to get the most from your network, this tutorial shows how to set up a Dynamic Host Configuration Protocol (DHCP) server with Internet Systems Consortium (ISC) DHCP. Sample code and configuration files are provided throughout to aid understanding."
On my network at home, my DHCP server sets itself up according to my DNS. So if I want to change a few IP addresses, or change my entire network to run in a different netblock, or whatever, it's a simple matter of modifying the two name server zones (something I'd have to do anyway), and restarting everything.
I, admittedly, have a relatively large network for a home user (not that it's that big by /. standards), but it's not large by general standards.
Different people will appreciate different tools for the jobs. Some people like those dedicated router things, but most of them have never left a secure shell session to the office open for fifteen minutes...
You are not alone. This is not normal. None of this is normal.
At the school where I work, we do exactly this. The idea is that workstations can be exact copies of a master image, but of course each must have a unique IP address. It's a lot nicer to set these up at the server, than going through the boxes separately. Especially when some of them are Windows machines.
Escher was the first MC and Giger invented the HR department.
I don't know what's wrong with dnsmasq+exim (and I'm too lazy to search google), but dnsmasq is under very active development and has fixed a lot of bugs, some esotheric, some really nasty. Details are in the changelog. Perhaps the trouble with exim has already been solved. You may want to give dnsmasq a second chance. ;-)
I still use sendmail from Slackware 8 in my LAN, it just works, with both my now disabled bind and with dnsmasq 2.something. I want to change to some other mailer, but I've not yet found the time to learn and install exim or postfix.
Tux2000
Denken hilft.
is there a functioning Linux distribution that DOESN'T come with a fully functioning DHCP server preinstalled, that you have to kill if you have more than one box on your network?? I don't think so..
at least, after installing three Fedora boxes and a Debian box on my network, I had a hell of a time getting my networking to work on the systems, until I realised that without asking me, all of them installed a function DHCP client and server..
(Linux distribution install programs suck)
"Champagne for my real friends - and real pain for my sham friends!" http://ericblade.postalboard.com/
Some tips on getting dhcpd and bind to "play nicely together" would be useful. It's not rocket science, but it's not exactly obvious, either.