Configuring a DHCP Relay Agent on Cisco IOS Routers In many enterprise networks, DHCP servers are centralized in a data center while client devices exist across many different subnets and VLANs. Since DHCP discovery packets are broadcast-based, they cannot cross Layer 3 boundaries by default. This is where a DHCP Relay Agent becomes essential. Cisco routers can relay DHCP broadcast messages from clients to a remote DHCP server using the ip helper-address command. The router listens for DHCP broadcasts on a local subnet and forwards them as unicast packets to the configured DHCP server. Typical DHCP Relay Architecture Consider the following scenario: Client subnet: 192.168.10.0/24 Router interface: 192.168.10.1 Central DHCP Server: 10.0.0.10 Without a relay agent, DHCP requests would never reach the server because broadcast traffic does not traverse routers. The Cisco router solves this problem by forwarding DHCP messages to the server. Step 1: Configure the Router Interface The first step is to configure the router interface that connects to the client subnet. Router(config)# interface GigabitEthernet0/1 Router(config-if)# ip address 192.168.10.1 255.255.255.0 Router(config-if)# no shutdown This interface becomes the default gateway for devices on the subnet. Step 2: Configure the DHCP Relay Agent Now configure the router to forward DHCP broadcast traffic to the DHCP server using ip helper-address. Router(config)# interface GigabitEthernet0/1 Router(config-if)# ip helper-address 10.0.0.10 This command tells the router to forward DHCP broadcasts received on the interface to the specified DHCP server. The router converts the broadcast request into a unicast packet directed at the DHCP server. How the DHCP Relay Process Works When a new device connects to the network, the following DHCP sequence occurs: Client sends a DHCPDISCOVER broadcast Router receives broadcast on the interface Router forwards request to DHCP server via ip helper-address DHCP server responds with DHCPOFFER Router relays response back to the client The router inserts its interface address into the GIADDR (Gateway IP Address) field so the DHCP server knows which scope to assign. Services Forwarded by ip helper-address By default, Cisco IOS forwards several UDP services when ip helper-address is configured: UDP 67 – DHCP Server UDP 68 – DHCP Client UDP 69 – TFTP UDP 53 – DNS UDP 37 – Time UDP 49 – TACACS If necessary, administrators can disable unwanted forwarded services. Router(config)# no ip forward-protocol udp tftp Verification Commands After configuration, verify the router is correctly relaying DHCP traffic. Check interface configuration: show running-config interface GigabitEthernet0/1 Monitor DHCP traffic: debug ip dhcp server packet View DHCP bindings: show ip dhcp binding Troubleshooting DHCP Relay Issues If clients are not receiving IP addresses, check the following: Verify ip helper-address points to the correct DHCP server Ensure routing exists between the router and DHCP server Confirm DHCP scope exists for the client subnet Check firewall rules that might block UDP ports 67 or 68 You can also capture DHCP packets using debugging tools to confirm requests are reaching the server. Security Considerations DHCP relay agents should be deployed carefully in enterprise networks. Unauthorized DHCP servers can lead to rogue address assignments and network disruption. Consider implementing: DHCP Snooping Port Security Network Access Control (NAC) These protections help ensure only trusted DHCP infrastructure is used within your environment. Final Thoughts DHCP relay agents allow organizations to centralize IP address management while maintaining segmented networks across many VLANs and subnets. Using Cisco IOS ip helper-address makes it simple to forward DHCP requests across routed networks and ensures devices can automatically obtain IP addresses regardless of their location in the infrastructure. For large enterprise deployments, DHCP relay is a fundamental component of scalable network design.