> I'd agree that DHCP is a good idea, (I runs it 'ere) > > But why a static IP for webmail etc? I assume you mean for the 'server'. > The server always should have a static address, and the workstations are > 'dynamic' managed by dhcp. Another good idea is to set up bind (dns server) > with a fake root domain as well, means you don't have to have any hosts > files on workstations, and you can pass out the dns server IP in the DHCP > setup..
That is what i meant for servers - mail, web, ftp etc... I use DHCP on workstations too.. as it is better to recycle an IP than waste it.. > DHCP can be annoying if you're doing 'peer to peer' things on your LAN, as > your workstations may change IP addresses, but if you're only intending to > share resources from a single point (server) dhcp is a good option. There > are some gotcha's with setting it up hough, and at least one of the how-to's > I've read on it are total garbage... thats where a Static would come it handy :)) > Thinking of this meeting agenda... Someone should do a brief talk about IP > networking fundamentals... Very fundamental that is, and stay away from > classical geek arguments about classless vs classed routing etc. I'd be > happy to give it a bash. (or sh, if that's your thing..) Unless someone > else is keen... I'm a bit conscious that I can ramble on endlessly... :-) I would be interested in a talk like that... altho i know a little bit etc.. and how things work.. you can always learn more from what other people say... :)) Johnno > ----- Original Message ----- > From: "Johnno" > > > From what I have read DHCP would make it alot easier for this expansion. > > > > it sure does.. tho if you are doing to run a server type app Web, Mail > > etc.. static will is better... > > > >
