Chapters0/30 ▾
Chapter 6 · Lesson 4 of 5
Addressing and service failures: masks, DHCP, duplicates, loops, ACLs, DNS
1 min read
Each of these faults has a fingerprint. Match the pattern before choosing a fix.
- Wrong mask: local peers inside the host's block work, but the gateway and everything remote fail. Example: 10.0.8.130/26 sits in 10.0.8.128 to 10.0.8.191, so a gateway of 10.0.8.65 is off-subnet.
- 169.254.x.x with no gateway on a new VLAN that has never worked, while the DHCP server's own VLAN is fine: the VLAN's router interface lacks a DHCP relay.
- One IP address mapping to two different MACs over time, plus a conflict warning: a duplicate address, often a static address inside the DHCP scope.
- One MAC flapping between two ports, CPU near 100% and a whole VLAN down after a second cable was added: a Layer 2 loop that spanning tree should have blocked.
- Ping and one application work but another port times out: the ACL's implicit deny is catching the port with no permit.
- The site loads by IP but not by name, and a lookup returns the old address: a stale DNS record; update it and flush caches, since the TTL keeps old answers alive.
Check yourself
1. A host is configured with the address 192.168.10.75/28 and default gateway 192.168.10.1. It can reach a printer at 192.168.10.70 but cannot reach the gateway or any remote network. What is wrong?
2. A user cannot open intranet.example.com, but browsing directly to 10.20.5.40 loads the site normally. A name lookup from the user's PC returns 'Name: intranet.example.com Address: 10.20.5.12'. The server was migrated to 10.20.5.40 during the last maintenance window. What does this output prove?
Facts checked 2026-11-16 · Sources: CompTIA Network+ certification overview, RFC 3927: Dynamic Configuration of IPv4 Link-Local Addresses
CompTIA Network+ cheat sheet: every key fact on one page →