169.254.0.0/16 Link-Local (APIPA) Addresses
Learn about 169.254.x.x link-local addresses (APIPA). Understand when they appear, why they indicate DHCP failure, and how they enable zero-configuration networking.
Detailed Explanation
Link-Local Addresses: 169.254.0.0/16
The 169.254.0.0/16 range (169.254.0.0 – 169.254.255.255) is reserved for IPv4 link-local addresses, also known as APIPA (Automatic Private IP Addressing).
When Do You See 169.254.x.x?
A device assigns itself a 169.254.x.x address when:
- It is configured for DHCP but no DHCP server responds
- The DHCP lease expires and cannot be renewed
- The network cable is connected but no router/DHCP is present
How APIPA Works
1. Device sends DHCP Discover broadcast
2. No DHCP Offer received (timeout ~30 seconds)
3. Device randomly selects address from 169.254.1.0 – 169.254.254.255
4. Device performs ARP probe to check for conflicts
5. If no conflict, device claims the address
6. Device continues to retry DHCP in the background
Key Properties
| Property | Value |
|---|---|
| Range | 169.254.0.0 – 169.254.255.255 |
| Usable | 169.254.1.0 – 169.254.254.255 |
| Subnet Mask | 255.255.0.0 |
| Routable | No (link-local only) |
| RFC | RFC 3927 |
Practical Impact
Seeing a 169.254.x.x address usually means something is wrong with your network:
- Check the Ethernet cable or Wi-Fi connection
- Verify the DHCP server is running and reachable
- Check for IP conflicts — another device might have the same address
- On Windows, run
ipconfig /releasethenipconfig /renew
Valid Use: Zeroconf / Bonjour
Link-local addresses have a legitimate use in zero-configuration networking (mDNS / Bonjour), where devices on the same link discover each other without a router or DHCP server.
Use Case
A sysadmin troubleshooting a server that shows a 169.254.x.x address determines that the DHCP server is down, then manually assigns a static IP from the correct 10.0.1.0/24 range to restore connectivity.