NAT loopback
What is NAT loopback?
NAT loopback (NAT hairpinning) is a router feature that lets a device on a local network reach another local device using its public IP address or domain name, instead of its internal one. Not every consumer router supports it, which AdminKit's My IP tool can help confirm by showing whether your public address even resolves back to your own network.
By AdminKit team, Netbase JSC · Updated
NAT loopback, also called NAT hairpinning, is a router feature named by analogy to the loopback address a device uses to address itself, extended here to let a whole local network reach its own public-facing address the same way — the same term and underlying mechanism show up in cloud networking too, where AWS’s Network Load Balancer documentation describes “NAT loopback, also known as hairpinning” as a specific, named connectivity case it must account for: it lets a device on a local network reach another device on the same network using its public IP address or domain name, instead of its internal address. Netgate’s pfSense documentation calls the same feature NAT reflection, defining it as the ability to reach external services from the internal network using the external IP address, “the same as if the client were on the Internet.” Without it, a request from inside the network to the router’s own public IP can simply fail or time out, because routers expect traffic to arrive from outside or leave from inside, not loop back on itself. This matters whenever a local user accesses a self-hosted service — a security camera, NAS, or web app — by its public address or DNS name while on the same Wi-Fi network as the server. Not every consumer router supports NAT loopback, which is a common cause of “works on mobile data but not on home Wi-Fi” reports; the usual workarounds are split-horizon DNS or using the device’s local IP address instead. RFC 4787 (a Best Current Practice per its IETF Datatracker entry) and RFC 5382 define this “hairpinning” behavior as a recommended NAT requirement for UDP and TCP respectively, though consumer routers implement it inconsistently. Checking your own public IP address with AdminKit’s My IP tool is a simple first step to confirm whether loopback support, rather than a bigger network problem, explains why a self-hosted service is unreachable.
AdminKit groups nAT loopback under its IP & network cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
Why can't I reach my own public IP address from my home network without NAT loopback?
Because routers typically expect traffic to arrive from outside or leave from inside, not loop back on itself -- without NAT loopback support, a request from inside the network to the router's own public address can simply fail or time out.
Does every router support NAT loopback?
No -- support is inconsistent across consumer routers even though RFC 4787 and RFC 5382 recommend hairpinning behavior for UDP and TCP respectively; this is a common cause of a self-hosted service working on mobile data but not on the same Wi-Fi network as the server.
What can I do if my router doesn't support NAT loopback?
The usual workarounds are split-horizon DNS, which gives devices on the local network a different (internal) answer for the same hostname, or simply using the device's local IP address instead of its public address or domain name.
Is NAT loopback the same as the loopback address (127.0.0.1)?
No, though the name is borrowed from it -- the loopback address lets a single device address itself; NAT loopback (hairpinning) extends that idea to a whole local network reaching its own public-facing address.