APIPA — Why You Get a 169.254 Address and How to Fix It

APIPA (Automatic Private IP Addressing) is a Windows feature that automatically assigns an IP address in the 169.254.0.0/16 range when a device cannot reach a DHCP server. An APIPA address means your device has no valid IP from DHCP and cannot communicate beyond the local link.

Key takeaways

APIPA assigns IP addresses from 169.254.0.0/16 (169.254.0.1 to 169.254.255.254) when DHCP fails
APIPA addresses are link-local — devices can only communicate with other APIPA devices on the same subnet
A 169.254.x.x IP address means your DHCP server is unreachable or the network connection has a problem
APIPA is defined in RFC 3927 and is also called link-local addressing (Zeroconf on Linux/Mac)
To fix APIPA: check your network cable, restart DHCP service, or verify your router is working
APIPA subnet mask is always 255.255.0.0 (/16)
APIPA addresses are self-assigned via ARP probing to avoid conflicts with other devices

APIPA (Automatic Private IP Addressing) is the fallback that assigns a device an address from 169.254.0.0/16 when it asks for a DHCP lease and no server answers. Microsoft introduced it in Windows 98; the underlying mechanism is standardised as link-local addressing in RFC 3927 and is implemented on macOS and Linux too.

If you see a 169.254 address, DHCP failed. That is the entire diagnostic value of APIPA, and it is genuinely useful, it converts a silent failure into a visible symptom.

Table of Contents

How APIPA Works

The interface comes up and broadcasts a DHCP Discover.
No DHCP Offer arrives within the timeout, after several retries.
The host picks a pseudo-random address from 169.254.1.0 to 169.254.254.255. The first and last /24 of the range are reserved.
It sends an ARP probe for that address. If another host replies, it picks a different one and repeats, up to ten times.
It assigns the address with mask 255.255.0.0, no default gateway and no DNS server.
It keeps retrying DHCP in the background, typically every five minutes. If a server responds, the APIPA address is dropped immediately.

What an APIPA Address Can and Cannot Do

Capability	Works?
Communicate with other APIPA hosts on the same segment	Yes
File and printer sharing on the local link	Yes
mDNS / Bonjour discovery	Yes
Reach the internet	No, no default gateway
Reach another subnet	No, link-local addresses are never routed
Resolve DNS names	No, no DNS server assigned
Reach a server on the correct subnet	No, different subnet, and no gateway

Routers are required to drop 169.254.x.x traffic and never forward it. A 169.254 address is also one of the three things to check when WiFi says connected but there is no internet. Link-local means exactly that: one segment, no further.

Diagnosing the Underlying Failure

# Windows
ipconfig /all
ipconfig /release
ipconfig /renew

# Linux
ip addr show
sudo dhclient -v eth0

# macOS
ipconfig getpacket en0

Work through these in order, they are ordered by how often each turns out to be the cause:

Check	What you are looking for
1. Physical layer	Link light on, what the Ethernet lights mean. A dead cable produces the same symptom as a dead DHCP server. Swap the cable before anything else.
2. Switch port VLAN	Is the port in the VLAN you think it is? A port in an unused VLAN has no DHCP server reachable.
3. DHCP server running	Service up, scope active, and not in a stopped or unauthorised state.
4. Pool exhaustion	All addresses leased. Very common on guest networks with a small pool and a long lease time.
5. DHCP relay	If the server is on a different VLAN, the router needs `ip helper-address`. Missing it is the classic cause on a newly created VLAN.
6. DHCP snooping	If snooping is enabled, the port toward the server must be trusted, or the Offer is discarded.
7. Port security	An err-disabled port has link but no traffic. `show interfaces status err-disabled`.
8. Wireless authentication	On WiFi, an association that fails 802.1X leaves the client associated but unable to pass DHCP.
9. Firewall on the client	Blocking UDP 68 inbound prevents the Offer being received.

Router(config)# interface Vlan20
Router(config-if)# ip helper-address 10.10.10.5

Switch# show ip dhcp snooping
Switch# show interfaces status err-disabled

When You See APIPA on Multiple Machines at Once

One host with a 169.254 address is a host problem. Several at once is an infrastructure problem, and the shortlist is short:

The DHCP server or its VM is down.
The scope is exhausted or has been deactivated.
The uplink carrying DHCP traffic has failed.
A relay configuration was removed or a VLAN was renumbered.
DHCP snooping was enabled without trusting the uplink, this takes out an entire VLAN immediately.

Should You Disable APIPA?

Generally no. It is a diagnostic signal rather than a problem, and disabling it means a DHCP failure produces no address at all, which is harder to distinguish from a cable fault, not easier.

The one legitimate reason is where a device sitting on a link-local address masks a failure that monitoring should catch. If you do disable it, on Windows:

HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\{GUID}
IPAutoconfigurationEnabled = 0  (DWORD)

A better approach for devices that must always have an address is an alternate configuration, Windows lets you specify a fallback static address per adapter, used instead of APIPA when DHCP fails.

APIPA vs IPv6 Link-Local

	APIPA (IPv4)	IPv6 link-local
Range	169.254.0.0/16	fe80::/10
When assigned	Only when DHCP fails	Always, on every interface
Coexists with a routable address	No	Yes
Used by protocols	Rarely	Extensively, ND, RA, OSPFv3 all use it
Indicates a fault	Yes	No, entirely normal

This is the key difference: an IPv6 link-local address is expected and healthy. An IPv4 APIPA address means something broke.

Frequently Asked Questions

What does a 169.254 IP address mean?

The device asked for a DHCP lease and got no reply, so it assigned itself a link-local address. It can talk to other devices on the same segment and nothing else.

How do I fix an APIPA address?

Fix DHCP, the address is a symptom. Check the cable and link light, then the switch port VLAN, then whether the DHCP server is reachable and has free addresses. Run ipconfig /release and /renew once the underlying issue is resolved.

Can I access the internet with an APIPA address?

No. APIPA assigns no default gateway and no DNS server, and routers never forward 169.254 traffic.

Why do two computers with APIPA addresses see each other?

Because they are on the same link and both hold addresses in 169.254.0.0/16 with a /16 mask. That is exactly what link-local addressing is for, ad-hoc communication with no infrastructure.

Is APIPA the same as a private IP address?

No. RFC 1918 private ranges (10.x, 172.16 to 31.x, 192.168.x) are routable within your network and are translated to public addresses by NAT. APIPA addresses are link-local, never routed anywhere, and never NATed.

Does APIPA work on wireless?

Yes, identically. A device that associates to an access point but fails to get a lease will self-assign, which is why a phone can show “connected, no internet” while sitting on a 169.254 address.

Written by

Jaspreet Singh

Hey! I'm Jaspreet Singh and I completed a degree in Bachelor of Computer Applications. I have 7+ years of experience in the Network & Security Domain as well as the Cloud Infra Domain. So I love to explore my technical knowledge with you.