DHCP versus static: how do you choose?

Home Forums Microsoft Networking and Management Services DHCP DHCP versus static: how do you choose?

This topic contains 2 replies, has 3 voices, and was last updated by Avatar Anonymous 1 year, 5 months ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
  • Avatar

    In my networking textbook, it specifies that sometimes, server administrators will pick different schemes related to DHCP and static network configurations. One of the set ups is to use the lower end of the spectrum as static and the upper end of the spectrum as DHCP. Mixing them together. Why bother making them at all? Isn’t it better to have dynamic configured hosts? Minus servers, of course, because you want those the always have a static IP address I’ve heard


    It’s a judgement call on your part. If there’s no reason for fixed IPs in your client subnet(s), then stick with DHCP. If fixed addresses end up being necessary for some clients, reserve those addresses in the DHCP scope. Simple, single point of admin, regardless of the size of the client pool(s). If you only have a few clients and don’t want to spend the few minutes time setting up a DHCP scope, then manually fix your IPs. It all comes down to how much effort you wish to spend. Just bear in mind how much growth you expect over the next 1-5 years, say, and think about the address admin effort needed at that point.

    And yes, your servers should always be fixed IPs.


    Static IPs (or reservations) for servers and network devices, and DHCP for everything else (IMHO)

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.