Public Tunnel use case
Access a home server without port forwarding.
Reach a home-server web app, NAS dashboard, or self-hosted panel even when the router cannot be changed or inbound access is blocked.
No router changesThe tunnel starts outbound from your network, so you do not need to expose a new inbound port.
Web-first accessStart with browser-based services such as dashboards, panels, and self-hosted web apps.
Good next step after DDNSUse it when a hostname alone is not enough because the service cannot receive inbound traffic.
Common examples
- Home Assistant or lab dashboards
- NAS and storage web panels
- Self-hosted apps and admin portals
- Small family or project websites
When this beats Dynamic DNS
Dynamic DNS is enough when the home network already accepts inbound traffic and only the public IP changes. Public Tunnel is the better fit when the router cannot be opened, the ISP blocks inbound access, or you want a simpler browser-access path.
Need your home web app reachable?
Get started and tell us which home-server workflow you want DNSExit to support first.