IPv4 Special Addresses (1) — Loopback, Link-Local, Documentation
Not every one of the roughly 4.3 billion IPv4 addresses can be handed to a host. The IETF sets aside whole blocks for technical jobs — testing a host’s own stack, self-configuring a link with no DHCP, and writing safe examples. Learning these blocks, and the RFC behind each one, is guaranteed exam material.
Why some addresses are special
An IPv4 address has 32 bits, so there are only 232 — about 4.29 billion — possible addresses. A large part of that space is not available for ordinary assignment to hosts and routing across the public Internet. Instead, standards bodies (the IETF, through its RFC documents) carve out blocks for specific functions. These are the special-use addresses.
You need to know them for three reasons:
- They break things if misused. Putting
127.0.0.5on a server, or routing a documentation address across the Internet, is an error. - They are diagnostic clues. Seeing
169.254.x.xon a PC tells you, instantly, that DHCP failed. - They are exam favourites. The CCNA asks you to identify a range from its first octets and to name its function and RFC.
Loopback — 127.0.0.0/8
Block: 127.0.0.0/8 — that is every address from
127.0.0.0 through 127.255.255.255 (one full /8, 16,777,216 addresses).
Defined by RFC 1122.
Any packet sent to an address in 127.0.0.0/8 is processed entirely inside the sending
host by its own TCP/IP stack. The packet never leaves the machine and is never
placed on the network medium. The first octet 127 is the giveaway: if an address starts
with 127, it is loopback.
The conventional address is 127.0.0.1, known by the hostname
localhost. Running ping 127.0.0.1 is the most basic test of whether a
host’s own IP stack is installed and working — if it fails, the problem is on the host,
not the network. Loopback addresses are not routable: routers must never forward
them, and they cannot be assigned to a physical interface as a real address.
127.0.0.0/8 block is loopback, not just
127.0.0.1. A question may show 127.1.1.1 or 127.200.5.9
— these are loopback too. Loopback is not routable.Link-local — 169.254.0.0/16 (APIPA)
Block: 169.254.0.0/16 — from 169.254.0.0 through
169.254.255.255 (65,536 addresses). Defined by RFC 3927 and commonly
called APIPA (Automatic Private IP Addressing).
A link-local address is what a host gives itself when it is configured to get an address automatically from DHCP but no DHCP server answers. Instead of sitting with no address at all, the host:
- Selects an address at random in the
169.254.0.0/16block. - Probes the link with ARP to make sure no other host already uses it (an ARP Probe), then announces it.
- Uses that address so it can still talk to other devices on the same link.
RFC 3927 reserves the first 256 addresses (169.254.0.0/24) and the
last 256 (169.254.255.0/24) for future use, so the addresses a host may
actually self-assign run from 169.254.1.0 to 169.254.254.255.
Key properties:
- Local link only. It is valid only on the segment the host is attached to.
- Not routable. Routers do not forward link-local traffic between networks.
- No Internet access. You cannot reach the Internet with a 169.254 address alone.
- Diagnostic. A PC stuck with a
169.254.x.xaddress almost always means “DHCP server unreachable”.
fe80::/10 — covered in
Lesson 7.)Documentation — the TEST-NET ranges
RFC 5737 reserves three /24 blocks for use in documentation,
training material, and examples:
| Block | Name | Range |
|---|---|---|
| 192.0.2.0/24 | TEST-NET-1 | 192.0.2.0 – 192.0.2.255 |
| 198.51.100.0/24 | TEST-NET-2 | 198.51.100.0 – 198.51.100.255 |
| 203.0.113.0/24 | TEST-NET-3 | 203.0.113.0 – 203.0.113.255 |
These ranges are guaranteed never to be allocated as real public addresses, so a textbook, a diagram, or a sample configuration can use them without any risk of pointing at a real server on the Internet. That is their entire purpose.
They must not be used in a production network and must not be
routed on the public Internet. They are for documentation only. (The original TEST-NET,
192.0.2.0/24, dates back to RFC 5737’s predecessor; the current RFC defines all
three.)
/24s exactly: 192.0.2.0/24,
198.51.100.0/24, 203.0.113.0/24. If an exam question asks which address is safe to use in
an example, one of these is the answer.Limited broadcast and the unspecified address
Limited broadcast — 255.255.255.255
The all-ones address 255.255.255.255 is the limited
broadcast address, defined by RFC 919 and RFC 922. A
datagram addressed to it is delivered to every host on the local (sub)network and is
never forwarded by a router.
Its classic use is bootstrapping: a host that has no IP address yet sends its DHCP Discover
message from source 0.0.0.0 to destination 255.255.255.255, because it does
not yet know any address on the network — not even the DHCP server’s.
Do not confuse it with a directed (subnet) broadcast such as
192.168.1.255. That form targets all hosts in one specific subnet and is generally
disabled by RFC 1812, which states routers should not forward directed broadcasts. The
255.255.255.255 address is not routable. It sits inside the reserved
240.0.0.0/4 block but is singled out because of its special, all-ones meaning.
The unspecified address — 0.0.0.0
0.0.0.0 is the unspecified address (RFC 1122),
sometimes read as “this host” or “any host”. It has two distinct roles:
- As a source address — a host that has no address yet uses
0.0.0.0as the source while it asks for one (the same DHCP Discover above). It cannot be used as a destination. - As
0.0.0.0/0— the default route — in a routing table, the prefix0.0.0.0with mask0.0.0.0(prefix length 0) matches every destination. It is the route a router uses when no more specific route fits — the “catch-all” or default route. (Routing tables are covered in Lesson 11.)
0.0.0.0 and the route 0.0.0.0/0 are related but not the same
thing. As an address it means “I do not have one yet”; as a prefix it
means “match everything”.At a glance
The same facts in one table. Every value here is canonical and exam-ready:
| Range | RFC | Purpose | Routable? |
|---|---|---|---|
| 127.0.0.0/8 | RFC 1122 | Loopback; 127.0.0.1 = localhost, tests the local stack | No |
| 169.254.0.0/16 | RFC 3927 | Link-local / APIPA; self-config when no DHCP, local link only | No |
| 192.0.2.0/24 | RFC 5737 | Documentation — TEST-NET-1 | No |
| 198.51.100.0/24 | RFC 5737 | Documentation — TEST-NET-2 | No |
| 203.0.113.0/24 | RFC 5737 | Documentation — TEST-NET-3 | No |
| 255.255.255.255 | RFC 919/922 | Limited broadcast; all hosts on the local subnet | No |
| 0.0.0.0 | RFC 1122 | Unspecified / this host; also default route 0.0.0.0/0 | No |
Key terms
| Term | Meaning |
|---|---|
| Special-use address | An address block reserved by an RFC for a defined purpose rather than normal global assignment. |
| Loopback | 127.0.0.0/8; traffic to these addresses is handled by the host itself and never leaves it (RFC 1122). |
| Link-local / APIPA | 169.254.0.0/16; automatically self-assigned when no DHCP server is reachable, valid only on the local link (RFC 3927). |
| Documentation (TEST-NET) range | 192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24; reserved for examples (RFC 5737). |
| Limited broadcast | 255.255.255.255; delivered to all hosts on the local subnet, never forwarded (RFC 919/922). |
| Unspecified address | 0.0.0.0; source address before a host has one, and the 0.0.0.0/0 default route (RFC 1122). |
Review
Check what you have learned with these review questions.
Sources & references
- Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers
(1989), Section 3.2.1.3 (loopback
127.0.0.0/8; unspecified0.0.0.0). rfc-editor.org/rfc/rfc1122. - Cheshire, S., Aboba, B. & Guttman, E. RFC 3927: Dynamic Configuration of IPv4
Link-Local Addresses (2005). Link-local
169.254.0.0/16. rfc-editor.org/rfc/rfc3927. - Arkko, J., Cotton, M. & Vegoda, L. RFC 5737: IPv4 Address Blocks Reserved for Documentation (2010). TEST-NET-1/2/3. rfc-editor.org/rfc/rfc5737.
- Mogul, J. RFC 919: Broadcasting Internet Datagrams (1984) and RFC 922
(1984). Limited broadcast
255.255.255.255. rfc-editor.org/rfc/rfc919. - Cisco. CCNA (200-301) Exam Topics, IP Addressing. cisco.com.
Target exams: CCNA 200-301 v1.1 · CyberOps Associate 200-201. Last content verification: 2026-10-11.