Lessons › Servers & virtualisation
DHCP across routers: relays and scopes
▶ Start the interactive lesson
Burrow opens a new floor. The DHCP server works perfectly for the server room, but laptops on the new floor sit on 169.254.x.x (no address). "DHCP starts with a broadcast," Maya says, "and routers don't forward broadcasts. Unless you ask them to."
Key points
- DHCP is DORA: Discover (broadcast), Offer, Request, Ack. The client uses UDP 68 and the server UDP 67. With no answer, Windows self-assigns 169.254.x.x (APIPA), which is a sign DHCP failed.
- A DHCP relay (Cisco: ip helper-address on the client-facing interface or SVI) catches the broadcast and forwards it as unicast to the server.
- The relay fills in the gateway address (giaddr): its own interface IP. The server uses it to pick the right scope / pool, which is how one server serves many subnets.
- A scope holds the address range, mask, default gateway, DNS servers, lease time, exclusions (for printers, servers) and reservations (a fixed IP for a MAC). A wrong gateway in the scope gives users an address that can't leave the subnet.
- Troubleshoot: is the client getting 169.254? Is the relay configured on the right interface? Can the router reach the server? Does a scope exist for that subnet? Is the pool exhausted?
The full lesson has more: animations, a hands-on exercise, 3 quiz questions and spaced review cards. Open it free →