Static IP Addresses or DHCP Reservations for Cameras

An IP camera needs a local IP address so that a network recorder can find it. On many properties, the router also acts as the DHCP server and assigns that address. A DHCP reservation links the address to the camera’s MAC address; a manual static address stores the settings on the camera itself. The practical question behind static IP addresses or DHCP reservations for cameras is therefore not simply which method is more permanent. It is where you want administrative control to live, who can maintain it, and what happens when equipment is replaced.

How Static IP Addresses or DHCP Reservations Work

A local IP address is the camera’s identity within its local network. The NVR (network video recorder), VMS (video management software), configuration tools and authorised viewing devices use it to reach the camera. If the address changes unexpectedly, a recorder configured for the previous address may report the camera as unavailable even though the camera is still operating.

A DHCP server maintains an address pool and supplies network settings to connected devices. These usually include an IP address, subnet mask, default gateway and information needed to reach other network services. The router performs this role in many homes and small businesses, although a managed business network may use a different device.

Without a reservation, the server selects an available address from its pool. The camera may receive the same address repeatedly, but that is not an administrative guarantee. A reservation changes the arrangement: the DHCP server recognises the camera’s MAC address and supplies a chosen local address whenever that camera requests its settings.

Camera discovery is a separate process. An NVR or installation tool may locate compatible cameras automatically on the local network, but discovery does not make an address permanent. The recorder still needs a reliable way to reconnect after a restart, network interruption or equipment change.

The public IP used by an internet connection is separate from the local addresses assigned to cameras and the recorder. Changing a camera from DHCP to static addressing does not give the camera a fixed public IP. Remote viewing, local camera addressing and the internet connection should be treated as related but distinct parts of the design.

Static IP vs DHCP?

When should a camera use a static IP?

With a manual static configuration, the IP address, subnet mask and usually the default gateway are entered into the camera. Those values remain stored there until someone changes the network settings or resets the device. The camera does not need the DHCP server to recover its assigned address after restarting.

This gives direct control, but it also creates direct responsibility. The administrator must choose an unused address, keep it outside any unmanaged dynamic pool, enter every network value correctly and document the assignment. The router may not show why the address was chosen or which device owns it.

How do DHCP reservations keep cameras reachable?

A reservation lets the camera continue using automatic network settings while the DHCP server supplies a consistent address. Administration stays in one place. An installer or network manager can review the address pool, see reserved entries and change the plan without signing in to every camera individually.

Neither method is inherently more professional. A well-documented reservation is better than an unmanaged static address. A carefully planned static network is better than reservations stored in a router that nobody can administer. The choice should follow the ownership and maintenance model of the network.

Where Each Approach Fits

For an ordinary home network, a router reservation is usually the cleanest choice. The router remains authoritative, cameras receive complete network settings automatically, and the owner has one place to review assignments. This is particularly useful for new arrivals who inherited internet equipment with the property and want the camera system to remain understandable to another technician later.

A small business may need a central address plan covering cameras, the NVR, access points, printers and other fixed equipment. Reservations can still work well if the router or network controller is properly managed. On a larger or deliberately segmented installation, cameras may sit on a dedicated VLAN. In that case, the addressing method should match the wider network plan rather than being decided camera by camera.

Manual static addressing is often appropriate on an isolated recorder network. Some NVRs provide dedicated camera ports and create a private network that is separate from the property’s normal data network. If the recorder or installer controls that entire subnet, fixed settings can be simple and predictable. The important point is that the address plan belongs to the camera system and does not overlap with an unrelated DHCP pool.

Apartment buildings require an ownership check before a technical choice. A camera near a shared entrance may connect to a network controlled by the va’ad bayit, a building service provider or an individual property. A reservation is only useful if the person responsible for the camera system can administer the DHCP server and preserve its configuration. A private apartment camera should not quietly depend on shared network equipment whose access details are unavailable.

Remote properties create a similar concern. A reservation is easy to manage when reliable router administration is available. If the internet router is routinely replaced or reset by someone who does not maintain the camera configuration, the reservations may disappear. Manual settings can reduce that dependency, but only if the replacement router continues using the expected subnet and does not assign the same addresses to other devices.

What Can Go Wrong?

The most disruptive addressing faults are usually ordinary configuration mistakes. They can make a healthy camera look defective, particularly when the recorder reports only that the device is offline.

• Duplicate local addresses: A manually assigned address can conflict with another device if it was not excluded from the DHCP pool or recorded in the network plan. Communication may become intermittent or fail completely.
• Changed DHCP address: A camera using unreserved DHCP can receive a different address. A recorder that expects the old address may no longer connect to it.
• Wrong subnet mask: The address may look correct, but the camera can misjudge which devices are local and which must be reached through a gateway.
• Wrong default gateway: Local viewing may work while communication beyond the camera subnet fails. This can complicate remote management and time synchronisation.
• Lost reservations: Router replacement, reset or reconfiguration can remove the entries unless the relevant configuration is restored or rebuilt.
• Changed MAC address: A replacement camera is a different network device. A reservation tied to the previous camera’s MAC address must be updated.

Dust, coastal humidity, strong sunlight and power interruptions can all affect equipment in Israeli properties, but they should not distract from basic network diagnosis. When one camera disappears, first check its current address, physical link, PoE (power over Ethernet) status and subnet. Replacing hardware before confirming those details often leaves the underlying addressing problem untouched.

Why does a camera change its IP address?

A camera usually changes address because it is using unreserved DHCP, because the DHCP server’s configuration changed, or because the camera was reset to automatic settings. A changed router can also introduce a different local subnet. The useful question is not only what address the camera has now, but which device supplied it and whether the NVR is configured to follow that change.

Plan Before Assigning Addresses

Start with an inventory. Record every camera, the NVR, relevant network switches and the device providing DHCP. For each camera, note its installation location, MAC address, assigned IP address and whether the assignment is manual, reserved or dynamic. A label such as “front gate” is more useful during maintenance than an unexplained row of addresses.

Define the subnet and decide which part of it belongs to ordinary dynamic devices and which part is used for fixed infrastructure. Reservations may technically sit within the server’s managed pool, depending on how that server operates. Manual static addresses should be deliberately separated from addresses that the server can hand out without checking your written plan.

This documentation is sometimes described as CCTV IP addressing, but the useful deliverable is broader than a camera list. It should identify the router or DHCP server, the network range, the recorder address, VLAN details where relevant, and the method used for each fixed device.

• Confirm who owns and administers the router or DHCP server.
• Keep authorised login and recovery details in a secure location available to the responsible owner.
• Record whether cameras connect through the property network or an isolated NVR network.
• Note any addresses that must be recreated after router replacement.
• Document the camera MAC addresses used as reservation keys.
• Update the inventory whenever a camera, recorder or router is replaced.

Choose the Right Addressing Method

Choose DHCP reservations when the router or another DHCP server is intended to remain the authority for the network. This is generally the most manageable arrangement for homes, street-front businesses and small offices where one known administrator controls the network equipment.

Choose manual static addressing when cameras operate on an isolated network, when the NVR controls a private camera subnet, or when a network administrator maintains a deliberate fixed-address plan without depending on router reservations. Check every setting, not just the final part of the IP address.

Whichever method you choose, apply it consistently. A mixed installation can be valid, but each exception should have a reason. Unexplained mixtures of static addresses, reservations and unreserved DHCP make fault-finding slower because nobody knows which system is authoritative.

Hand the owner a clear record of the assignments and the location of the administrative credentials. For remotely managed properties, identify who can make changes locally if network access is lost. After any router, camera or recorder replacement, review the address plan rather than assuming the previous relationships survived.

Stable camera addressing comes from a maintained plan, not from the word “static” alone.