Pretty simple question.

What is the industry best practice? In a small business which has computers which require static IP addresses is it better to set static IP addresses for devices on the devices themselves, or in the router/managed switch? All non-static IP requiring devices can use DHCP.


  • How do you want to set IP for an end device in router? The only way is by configuring DHCP on router which is again dynamic IP Address assignment for the end devices. If you have less number of devices then static IP assignment won't harm.
    – MUSR
    Commented Apr 14, 2016 at 3:35
  • I've clarified the question. Commented Apr 14, 2016 at 5:43
  • It's about what is economical for you. Setting a DHCP for, let's say, 5 devices is not economical. If you have 100 devices then you don't want to configure IP for all of them. The point is how many devices do you have and what kind of devices are they - PC, Phones etc. If you have DSL connection then your DSL modem already has an inbuilt DHCP. As soon as you connect a device it gets an IP Address. If you only have PCs and DSL Modem can accommodate all of them then you don't need to do anything.
    – MUSR
    Commented Apr 14, 2016 at 6:12
  • It's more a question of best practice. At a company where they have many computers that report to one server. The server requires a static IP on the network, and all the other computers on the network are happily over on DHCP. However when it comes time to remote into the server(Port forwarding or locally) it needs to have a static IP. Thus should the standard be to set everyones static IP in the router/managed switch, or should the static IP be set in each of the servers. I know it can be either, just want to know which is best practice. Commented Apr 14, 2016 at 6:16
  • How many devices do you have and what kind of devices are they? Do you have some special requirements for the devices? Please provide details.
    – MUSR
    Commented Apr 14, 2016 at 6:30

6 Answers 6


This is what I think you're trying to ask: When I have a DHCP network but want a handful of hosts to have static IPs, is it best to reserve the IPs on my DHCP server or set static IPs on the hosts themselves? If that's your question, edit it and I'll take out this paragraph.

The only benefit I see of configuring static IPs on select hosts themselves is that the address is permanently set and not relying on the interface's MAC to reacquire the "reserved" IP. However, reserving the address already handed out by DHCP is quick and easy and doesn't require any access to the host. For instance, if I put a wireless print server on my WLAN and want it to maintain a specific address but don't care what, I can reserve the address it is assigned without ever touching the print server.

As an aside, you mention this is a small business. For an office of five or 10 people I would personally set static IPs as a best practice. No DHCP server needed, nothing ever changes, and perhaps it adds just a tiny extra bit of security in that one can't just plug a device into the network and have instant access.

  • Peter Green notes an important point below: Setting a static IP on devices allows those devices to continue to communicate when the DHCP server is offline. Commented May 1, 2016 at 16:35

Theres advantages to both approaches. It's down to you to decide which is more relavent on your network.

The advantage of setting on the device is that the devices can still talk to each other if the dhcp server goes down or if a rouge DHCP server shows up.

The advantage of setting on the DHCP server is that you don't have to go round to every machine individually if you ever need to do a mass renumbering.


If you are planning a long term network, I guess you should use static IP address on your workstations, so that you can apply security policies on a domain controller, or control Internet access by user profiles. DHCP is the perfect way when you don't need to apply special policies to specific users, all PCs shares a profile and do what it permitted.


Consider yet another scenario. Imagine you have an external WIFI dongle, it has its own MAC address. Now if it stopped working and you will have to replace it, or you decided to change connection type to cable, the MAC address will change, so the IP to MAC assignment will become out of date. If you want to have stable static IP not dependent on the MAC address of the device responsible for connection, then configure static IP on the computer connected to the router, ignoring DHCP. If you are ok with having IP-MAC dependency, then you can configure it on Router's DHCP.

  • 1
    The static IP will likely be lost in any of the situations you've described, in Windows at least. Each network adapter has it's own IP so switching from wireless to wired will lose the IP. Installing a new adapter will likely be seen as a new adapter also and give a new IP. I think doing maintenance like this you should expect to reconfigure things anyway so I wouldn't count it as an argument for either apprach
    – MikeKulls
    Commented Mar 1, 2021 at 0:03

Here's a huge disadvantage to setting a static IP on the host that ran into. I had set an NAS with a static IP of Then I got a new router that insisted on working within the 192.168.68.xx range. I COULD NOT get access to the NAS, even resetting it didn't work. I eventually had to set the old router back up just to get access to the NAS to change it back to DHCP so that I could access it on the new router. If I didn't still have the old router, I'd have been hosed.

  • a new router that insisted on working within the 192.168.68.xx range - note that consumer-grade devices and home networking are explicitly off-topic here.
    – Zac67
    Commented Aug 16, 2020 at 8:12
  • I think the correct answer here is to not buy a router that forces a certain range.
    – MikeKulls
    Commented Feb 28, 2021 at 23:59

In a small business installation any disruption to the network will often require a professional to look at. For simplicity using DHCP with reservations is preferred.

  1. Adding/removing device to the network will only require connecting them. When a laptop is moved to another network (home) they user won't be required to manually switch back to DHCP.

  2. When reaching address exhaustion it will be clear what devices have reserved addresses (generally servers) making subnetting simpler.

  3. It greatly reduces the chance that a novice have two devices with the same IP address.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.