DHCP vs. Static IP for AV Devices

One of the earliest design decisions on any AV network project is whether to assign IP addresses dynamically (DHCP) or statically. The wrong choice causes devices that randomly change addresses after reboots, control systems that lose communication, and troubleshooting sessions chasing an address that moved. The right choice depends on what each device does in the system.

How DHCP Works

DHCP (Dynamic Host Configuration Protocol) is a network service that automatically assigns IP addresses to devices when they connect. A device sends a broadcast request; the DHCP server responds with an available address, subnet mask, default gateway, and DNS server. The address is leased for a set duration and must be renewed periodically.

DHCP is handled by the router, a dedicated server, or the network switch itself. In enterprise environments, a Windows Server or dedicated appliance runs DHCP. In smaller installations, the managed switch or the internet gateway handles it.

DHCP advantages:

• Zero configuration on the device itself
• Addresses are reused when devices leave the network
• New devices get valid network configuration automatically

DHCP disadvantages:

• Address can change when the lease expires or the device reboots (unless DHCP reservations are used)
• Requires a functioning DHCP server — if it's down, devices can't get addresses
• Harder to identify specific devices without a DHCP lease log

How Static IP Works

Static IP assignment means the IP address is configured directly on the device and never changes unless manually updated. No DHCP server is involved.

Static advantages:

• Address is predictable and permanent
• Works without a DHCP server
• Easy to reference in documentation and control system programming

Static disadvantages:

• Requires manual configuration on each device
• Risk of IP address conflicts if records aren't maintained
• More effort to reconfigure if the addressing scheme changes

The AV Rule: Static for Infrastructure, DHCP for User Devices

The clearest guidance for AV installations:

Use static IP for:

• DSP engines and processors (QSC Q-SYS cores, Biamp, BSS, etc.)
• Matrix switchers and video distribution
• PTZ cameras and video encoders/decoders
• AV control processors (Crestron, AMX, Extron)
• Network-attached amplifiers
• Room scheduling panels with fixed configurations
• All Dante audio devices (Dante Domain Manager requires static IPs; Dante without DDM benefits strongly from static IPs)
• Any device that other devices or control systems need to address by IP

Use DHCP (with reservations) for:

• Laptop connections (temporary AV sources)
• Bring-your-own-device wireless endpoints
• IP phones
• IT-managed workstations

Use DHCP without reservations for:

• Guest Wi-Fi clients
• Temporary connections

DHCP Reservations: The Best of Both Worlds

A DHCP reservation (sometimes called a static DHCP assignment or sticky DHCP) maps a specific MAC address to a specific IP address in the DHCP server. The device still uses DHCP, but it always receives the same address.

DHCP reservations are a good compromise for:

• Devices that support DHCP but where a consistent address is needed
• Environments where a centralized DHCP server manages the entire network
• Devices you want documented in the DHCP server rather than on each device individually

For Dante specifically: Dante devices support DHCP, but Audinate recommends static IPs or DHCP reservations for production installations. Dante devices that change IP addresses require re-routing in Dante Controller, which disrupts audio flows.

Link-Local Addressing (APIPA)

When a device is configured for DHCP but no DHCP server responds, it assigns itself a link-local address in the 169.254.0.0/16 range (called APIPA on Windows). Dante devices can use link-local addressing to discover each other on the same physical network segment.

Link-local addresses are not routable — they only work between devices on the same Layer 2 segment. A Dante device with a 169.254.x.x address cannot be reached from another VLAN or subnet. In small, single-room installations this may be acceptable, but it's not appropriate for production systems or multi-VLAN environments.

If you see 169.254.x.x addresses in Dante Controller, it means those devices didn't get proper IP addresses. Investigate whether the DHCP server is reachable from their VLAN, or assign static IPs.

DNS for AV Devices

DNS (Domain Name System) resolves human-readable hostnames to IP addresses. Most AV devices are accessed by IP address, not hostname, so DNS is often not critical for AV infrastructure. However:

• Software-based AV systems (NDI, Dante Virtual Soundcard, software-based control) benefit from DNS resolution
• API integrations and cloud-connected AV systems require DNS to resolve service endpoints
• Control systems that reference cloud services or licensing servers need reliable DNS

For AV VLANs: configure the DNS server address (usually the building's DNS server or a public resolver like 8.8.8.8 or 1.1.1.1) in the DHCP scope. Even for static-IP devices, configure a DNS server in case the device or any management software needs name resolution.

Address Documentation

Regardless of whether you use static or DHCP, maintain an IP address management record for every AV installation. At minimum, document:

• Device name and type
• MAC address
• IP address (static) or DHCP reservation entry
• VLAN assignment
• Physical location

Update this record whenever devices are added, moved, or replaced. Many integration firms use a spreadsheet; larger organizations use dedicated IPAM (IP Address Management) software. Undocumented static IPs are one of the most persistent sources of IP conflicts and troubleshooting headaches in AV maintenance.

Common Pitfalls

• Dante devices left on DHCP without reservations — After a switch reboot or DHCP lease renewal, a Dante device may get a different IP. Dante Controller loses the device and audio routing breaks until the route is re-established. Always use static IPs or DHCP reservations for Dante.
• Static IP conflicts from undocumented assignments — Two devices assigned the same static IP create an ARP conflict. Both devices see erratic network behavior. This happens when multiple technicians work on a system over time without a shared IP registry. Maintain documentation.
• Forgetting to set the gateway on static IP devices — A device with a static IP but no gateway can communicate within its subnet but cannot reach devices on other subnets. Control processors that can't reach external services often have a missing or incorrect gateway.
• DHCP server on a different VLAN without a relay agent — DHCP uses broadcast, which doesn't cross VLANs. If your DHCP server is on VLAN 1 and your AV devices are on VLAN 20, you need a DHCP relay agent (also called a DHCP helper) configured on the Layer 3 switch to forward DHCP broadcasts across VLANs. Without it, devices on AV VLANs never get DHCP responses and fall back to 169.254.x.x addresses.
• Using 169.254.x.x in multi-VLAN environments — Link-local addresses work only on a single Layer 2 segment. Any device that needs to communicate across VLANs must have a routable IP address.