DHCP troubleshooting labs
Follow a lease request from client to relay to server. Investigate missing offers, policy decisions, failover differences and the DNS updates that follow a lease.
What you can practise
- Scope capacity, relays and competing DHCP servers
- Option 82, failover reservations and secure updates
- DHCPv6 addressing and Router Advertisement dependencies
A running DHCP service does not establish that a particular client can complete a lease exchange.
Choose an investigation
11 playable cases. Each includes simulated evidence, interactive checks and a guided verdict.
- CASE 005 / Foundation
Diagnose DHCP pool exhaustion
The server is up. The pool is full.
- CASE 006 / Foundation
Troubleshoot DHCP relay helper addresses
The request never reaches the right desk.
- CASE 009 / Advanced
Troubleshoot Windows DHCP and stale DNS records
New lease. Old name. No amount of flushing helps.
- CASE 010 / Advanced
Troubleshoot DHCP Option 82 policy mismatches
The packets arrive. The new policy says no.
- CASE 012 / Advanced
Investigate stale DHCP-to-DNS update retries
The record updates correctly. Then somebody updates it again.
- CASE 013 / Advanced
Detect an unauthorised DHCP server
Two offers. Only one belongs here.
- CASE 017 / Advanced
Investigate Infoblox fixed-address DDNS
A fixed-address client receives its expected lease, but no DNS record appears.
- CASE 019 / Advanced
Investigate Infoblox DDNS destinations
NIOS DHCP allocates successfully, but the expected authoritative DNS record remains unchanged.
- CASE 020 / Advanced
Investigate Windows secure DNS update permissions
A Windows client moves scopes and gets a new lease, but authoritative DNS still contains the previous address.
- CASE 021 / Advanced
Troubleshoot Windows DHCP failover configuration replication
A client gets its reserved address from DHCP-A but a different address when DHCP-B responds.
- CASE 035 / Advanced
DHCPv6 troubleshooting: missing Router Advertisement default route
A valid lease is not a default route.