A quick look at IPv6 address scopes for private networks. Unique Local Addresses (ULA, fd00::/8) stay inside your organization, not reachable from the Internet, while global and link-local scopes have broader reach or are limited to a single link. This helps keep internal LAN traffic private and well organized.

Multiple Choice

Which IPv6 scope is used for addresses inside a private LAN?

IPv6 addresses include a scope that defines how far they are valid and routable. For a private LAN, you want addresses that aren’t meant to reach the global Internet but can be used across machines inside your organization. Unique Local Addresses are designed exactly for this purpose: they live in a private, non‑globally routable space (typically fd00::/8) and can be used throughout an internal network without conflicting with global addresses. Global scope would expose addresses to the Internet, which isn’t appropriate for private LAN use. Link-local addresses operate only on a single link and aren’t routable between routers, so they can’t serve as the private LAN’s main addressing. Unspecified scope is a placeholder used during address autoconfiguration and has no usable addressing for devices on a network. So the private LAN-friendly option is the unique local scope.

IPv6 scopes: why “private LAN” needs its own neighborhood

If you’ve ever set up a network, you know this little truth: not every address should behave the same way. Some addresses are meant to roam the wide internet, some stay tucked away on a single link, and some are designed to be shared inside a private organization without inviting every router in the world to join the party. IPv6 sips a lot of this logic from the same cup, but it labels it with a few handy terms that explain where traffic should travel. Today we’re zoning in on the private LAN—the little, cozy corner of your network—and why the unique local scope is the right fit there.

A quick map of IPv6 scopes

Think of IPv6 addresses as having different neighborhoods, each with its own rules about reachability:

  • Global scope: These are the addresses that can, in principle, be routed across the internet. They’re the “public streets” of IP space. If you put a device on a global address, it can be reached from anywhere that can route to it (subject to firewalls and ISP policies, of course).

  • Link-local scope: This is the neighborhood that exists only on a single network segment—the local link. Link-local addresses are not routable beyond the link. They’re great for essential tasks like automatic address configuration or neighbor discovery on one LAN, but you can’t send traffic to them from across a router.

  • Unique Local Addresses (ULAs): This is the private street inside your organization’s home. ULAs live in a space that isn’t supposed to be globally reachable. They’re designed for internal use, across multiple sites if you like, without colliding with the global internet address space.

  • Unspecified scope: Think of this as a placeholder. It isn’t a usable address for devices or routing; it’s what you see in certain configuration states when an address isn’t known yet.

The private LAN sweet spot: why ULAs fit so nicely

Let’s zoom in on the private LAN scenario. You’ve got a set of devices—servers, workstations, printers, maybe a few IoT gadgets—that need to talk to each other with predictable, stable addresses. You don’t want these devices to be directly addressable from the broader internet, at least not without a carefully planned gateway and access controls. Enter Unique Local Addresses.

What makes ULAs “unique” and “local” at the same time? Two key ideas:

  • Local: ULAs aren’t meant to be reachable on the global internet. They live in a private portion of the IPv6 space (the classic block is fd00::/8, though you’ll often see the more practical fdxx:yyzz::/48 used in networks). They’re designed to be used inside an organization, across sites if you have them, without leaking into the wider internet.

  • Unique: The word “unique” is a practical nod to avoiding clashes. In IPv6, you can generate ULAs in a way that minimizes chance of collision when you merge networks or connect sites. It’s not a guarantee of global uniqueness like a true public IPv6 block, but it’s good enough for internal consistency. If you’re building a private campus network or a small enterprise with multiple locations, ULAs let you keep a clean, non-overlapping address plan.

Why not global or link-local for the private LAN?

  • Global scope might feel like a luxury you can’t afford. Yes, it gives you reachability anywhere, but that comes with a price tag: exposure. Devices would appear on the global internet, which means more exposure to threats, more stringent filtering, more headaches coordinating with your security posture. For many private networks, the goal isn’t to be reachable from anywhere; it’s to be reachable from within the organization or across trusted interconnects.

  • Link-local scope is essential, but it’s not a complete solution for the LAN. These addresses are fantastic tools for single-link operations—awesome for auto-configuration and basic neighbor discovery on that one segment. But if you’ve got multiple subnets, or you want devices on different floors or sites to talk without awkward workarounds, link-local alone becomes a bottleneck. It also doesn’t scale beyond a single link.

Unspecified scope? That’s more of a machine’s first-day mood

Unspecified addresses are a different beast. They’re the placeholder of IPv6: a device uses an unspecified address during certain operations, like when it hasn’t yet received an address to use. It’s not something you’d deploy as a normal addressing plan. Think of it as a backstage pass, not a place you’d put a device to live.

ULDs, privacy, and practical deployment tips

ULAs aren’t a silver bullet, but they’re a clean, tidy way to architect an internal IPv6 space. Here are a few practical angles you’ll encounter in real networks:

  • Address planning and hierarchy: A common approach is to allocate a dedicated ULA block (fd00::/8) and then sub-allocate within your organization. You might assign a 48-bit prefix for internal sites, like fd12:3456:789a::/48, and then carve /64 subnets for each network segment. The beauty here is predictability and sanity when you’re routing inside the campus.

  • Site-to-site and multi-site cohesion: ULAs shine when you have more than one location that must appear as a single, cohesive network for internal services. You can route between sites with internal routing policies, VPNs, or software-defined networking, all while keeping the addressing private. There’s something almost comforting about a private address map that doesn’t drift into global visibility.

  • Privacy considerations: IPv6 does a lot of heavy lifting on privacy by default, but ULAs also help you avoid inadvertently exposing devices. Since ULAs aren’t routable on the public internet, you can light up internal services with less risk of direct discovery by external scanners. It’s a practical friend when you’re hardening a LAN.

  • Avoiding collisions and future growth: In larger organizations, especially those spanning multiple buildings or campuses, you’ll want a disciplined plan to avoid overlapping prefixes. The “unique” angle helps, but it doesn’t absolve you from governance. A clear address assignment policy, documentation, and change control go a long way.

  • Transition and coexistence: Your private LAN might still have IPv4 devices or even older IPv4-only services. In mixed environments, you’ll often see dual-stack configurations where devices hold both IPv4 and IPv6 addresses. ULAs can sit alongside global IPv6 addresses or IPv4 addresses, providing a private lane for internal traffic while the public lanes handle external communication. It’s a pragmatic bridge that eases migration and keeps things smooth.

Analogies to make sense of the space

Picture the private LAN as a walled garden. The garden’s fence isn’t a hard boundary, but it’s clear where your garden ends and the public park begins. Global addresses are the park entrance—they invite traffic from everywhere, with the gatekeeping of security tools at the border. Link-local addresses are like garden path markers: useful for moving around within a single lawn, but you wouldn’t expect to stroll to a neighboring yard on a whim. ULAs are the garden’s internal addresses—the clubhouse and rooms where staff and devices chat, share files, and coordinate resources without the world listening in.

A practical mindset for network design

If you’re sketching out a private IPv6 plan, here are a few concrete steps you can take that keep things sane and scalable:

  • Start with the right block: Reserve a ULA prefix—typically fd00::/8, but many teams use a locally generated 48-bit sub-prefix for clarity. The goal is to have an internal addressing map that you own.

  • Subnet strategically: Break the internal space into /64 subnets for each LAN segment, floor, or department. You’ll find /64s friendly for auto-configuration and stability for devices joining the network.

  • Keep the door closed to the outside world (by default): Use a trusted gateway and firewall rules to control what internal traffic can reach the internet. ULAs don’t automatically grant internet reachability, so you’re free to lock down what matters most.

  • Document and automate: A good addressing plan isn’t a fortune cookie—no mystery to decipher later. Use diagrams, spreadsheets, or network management tools to track which device gets which UL prefix. If you’re automating, make sure your DHCPv6 or stateless address autoconfiguration policies align with the internal plan.

  • Plan for growth and inter-site connectivity: If you’ll add campuses or remote sites, consider how you’ll extend the ULA space without collisions. A consistent naming and scoping strategy makes merging networks painless rather than a messy puzzle.

The bigger picture: IPv6 patterns in everyday networks

It’s easy to get lost in the weeds of scopes and prefixes, but the real takeaway is that IPv6 gives you a richer, more flexible way to design networks. The old IPv4 constraints—where private addresses were a bit of a tricky dance with NAT and a patchwork of public routes—felt clunky after a while. IPv6 invites you to reimagine the interior of your network: a private, well-structured space that still respects the larger internet’s boundaries.

If you’ve ever rebuilt a LAN and watched devices start talking to each other with a little less friction, you know what this is about. It’s not just about avoiding the internet; it’s about making internal communications reliable, predictable, and manageable as you scale. ULAs are the quiet backbone for private, internal traffic—like a backstage pass that keeps things tight, efficient, and secure without inviting the world to every door.

A closing thought

Networks are, at their core, maps of trust. You decide what gets to pass from one point to another, what stays inside, and what needs extra gates. In IPv6, the scope labels are the compass. For a private LAN, the unique local scope offers a clean, practical home base that can expand with you—across floors, buildings, or even remote sites—without inviting unnecessary attention from the outside. It’s a thoughtful balance: accessibility where you want it, privacy where you need it, and a structure that makes day-to-day operations a touch less chaotic.

If you’re curious to see ULAs in action, you can sketch a small lab at home or in a classroom, assign a private fd block, carve a few /64s, and fire up a couple of devices. You’ll notice how the traffic stays within your own little world, how devices find each other with predictable addresses, and how the internet beckons only where you want it to. That’s the elegance of IPv6 in a private LAN: a quiet, well-ordered neighborhood where everything simply works together.