ULA (Unique Local Address)
What is ULA (Unique Local Address)?
A Unique Local Address (ULA, RFC 4193) is an IPv6 range reserved for private, local-network use, playing a role similar to RFC 1918 private IPv4 ranges. Each site generates its own /48 prefix pseudo-randomly, so independently configured networks rarely collide. AdminKit's subnet calculator computes a ULA block's network range and host count.
By AdminKit team, Netbase JSC · Updated
A Unique Local Address (ULA, RFC 4193) is an IPv6 address range reserved for private, local-network use, listed as the “Unique-Local” entry in IANA’s IPv6 Special-Purpose Address Registry, and playing a role similar to RFC 1918 private ranges (like 192.168.0.0/16) in IPv4. ULAs fall within fc00::/7, with fd00::/8 the portion in practical use, and each site generates its own /48 prefix from a pseudo-random algorithm so two independently configured networks are very unlikely to collide if they’re later merged or interconnected. Container platforms use ULAs the same way: Docker’s IPv6 networking documentation suggests a Unique Local Address subnet from fd00::/8 in place of the documentation-only 2001:db8::/64 prefix its examples use.
Unlike a public IPv6 address, a ULA is not supposed to be routed on the open internet, making it useful for internal services, inter-device communication, or dual-stack networks that want stable local addressing independent of whatever public IPv6 prefix an ISP assigns, which can change over time — a use case NIST’s IPv6 deployment guidelines cover when discussing local-only addressing options. That routability across a whole private network is what distinguishes a ULA from the narrower, single-segment scope of a link-local address, which every interface holds regardless of ULA deployment.
AdminKit groups uLA (Unique Local Address) under its IP & network cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
What address range does a ULA fall within?
fc00::/7, with fd00::/8 the portion actually in practical use -- each site generates its own /48 prefix from a pseudo-random algorithm within that range.
Is a ULA routable on the public internet?
No -- unlike a public IPv6 address, a ULA is not supposed to be routed on the open internet, making it useful for internal services and stable local addressing instead.
Why are two independently generated ULA prefixes unlikely to collide?
Because each site generates its own /48 prefix pseudo-randomly rather than drawing from a shared sequential pool, so two networks merged or interconnected later are very unlikely to have picked the same prefix.
How is a ULA different from a link-local address?
A ULA is routable across an entire private network, while a link-local address is scoped to a single segment that every interface holds regardless of whether ULAs are deployed at all.