Week 6 · Lesson 5

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.

CCNA 200-301 IPv4 Addressing Verified 2026-10-11
Part 1

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:

Definition — special-use address. An address block reserved by an RFC for a defined purpose (loopback, link-local, documentation, broadcast, and so on) rather than for ordinary global assignment.
Which block is this? · type an address

Part 2

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.

Exam tip. The whole 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.
Part 3

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:

  1. Selects an address at random in the 169.254.0.0/16 block.
  2. Probes the link with ARP to make sure no other host already uses it (an ARP Probe), then announces it.
  3. 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:

Memory hook. 169.254 = “no DHCP here”. The block is often written with a /16 mask even though no router ever sees it. Windows uses the name APIPA; the RFC calls it IPv4 link-local. (IPv6 has its own link-local block, fe80::/10 — covered in Lesson 7.)
How a host ends up at 169.254.x.x · step through
Step 1 of 4
1

Part 4

Documentation — the TEST-NET ranges

RFC 5737 reserves three /24 blocks for use in documentation, training material, and examples:

BlockNameRange
192.0.2.0/24TEST-NET-1192.0.2.0 – 192.0.2.255
198.51.100.0/24TEST-NET-2198.51.100.0 – 198.51.100.255
203.0.113.0/24TEST-NET-3203.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.)

Exam tip. Memorise the three documentation /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.
Part 5

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.

Which broadcast? · pick one

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:

Note. The address 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”.
0.0.0.0 · two meanings

Part 6

At a glance

The same facts in one table. Every value here is canonical and exam-ready:

RangeRFCPurposeRoutable?
127.0.0.0/8RFC 1122Loopback; 127.0.0.1 = localhost, tests the local stackNo
169.254.0.0/16RFC 3927Link-local / APIPA; self-config when no DHCP, local link onlyNo
192.0.2.0/24RFC 5737Documentation — TEST-NET-1No
198.51.100.0/24RFC 5737Documentation — TEST-NET-2No
203.0.113.0/24RFC 5737Documentation — TEST-NET-3No
255.255.255.255RFC 919/922Limited broadcast; all hosts on the local subnetNo
0.0.0.0RFC 1122Unspecified / this host; also default route 0.0.0.0/0No

Key terms

TermMeaning
Special-use addressAn address block reserved by an RFC for a defined purpose rather than normal global assignment.
Loopback127.0.0.0/8; traffic to these addresses is handled by the host itself and never leaves it (RFC 1122).
Link-local / APIPA169.254.0.0/16; automatically self-assigned when no DHCP server is reachable, valid only on the local link (RFC 3927).
Documentation (TEST-NET) range192.0.2.0/24, 198.51.100.0/24, 203.0.113.0/24; reserved for examples (RFC 5737).
Limited broadcast255.255.255.255; delivered to all hosts on the local subnet, never forwarded (RFC 919/922).
Unspecified address0.0.0.0; source address before a host has one, and the 0.0.0.0/0 default route (RFC 1122).
Part 7 · Your turn

Review

Check what you have learned with these review questions.

Review · 6 questions

Sources

Sources & references

  1. Braden, R. RFC 1122: Requirements for Internet Hosts — Communication Layers (1989), Section 3.2.1.3 (loopback 127.0.0.0/8; unspecified 0.0.0.0). rfc-editor.org/rfc/rfc1122.
  2. 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.
  3. 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.
  4. Mogul, J. RFC 919: Broadcasting Internet Datagrams (1984) and RFC 922 (1984). Limited broadcast 255.255.255.255. rfc-editor.org/rfc/rfc919.
  5. 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.